Domain separation implementation

[minasamaan]

Hello, 

for SIAM or multi-supplier model, were ServiceNow plays the SM plus integration layer between SIAM provider and others MSPs, customers have customized ebonding with thier SM tool (SNOW and non SNOW)

SIAM desk is different in processes than Standard desk.

will domain separation will be useful here?  any similar practices ?

thanks

[Tony Chatfield1]

Hi, unfortunately your configuration and question are not clear form the details in your post.
Perhaps you could update this thread with clear and specific information, so that the community can better understand your requirement.

[Barry Kant]

Hi Minasamaan,

the way I look at it is: 

An IT party is managing IT solutions to consumers and provides that via Service Offerings.
The IT is managed via multiple internal and external parties. This is also managed via Service Offerings. 
I don't see the need to have a domain separated instance (I would avoid if I can). 
The trigger to parties is done via Service Offerings (it triggers e-bonding). Beside that you can make a integration user per external party to manage the data/scope as well as using data mappings. 

BR,
Barry

[Ed Laar]

Hi Minasamaan,

The intential use of a domain separated instance is when data separation comes into play. CSM provides capabilities where many parties/customers can create cases etc. on their own services and service components. When a case needs an ITSM ticket it can be created and assigned to an assignment group to solve that ticket and so that case.
When multiple parties have to work on ITSM tickets and probably also on CSM cases in the same instance that is where domain separation comes into play.
When external parties have to work on tickets but they are connected to the instance using an integration (I call this 'indirect working') domain separation is not needed. So an MSP can have an instance supporting multiple customers with their own or better direct assignment groups working in the instance and indirect assignment groups working in their own systems connected to the instance.
Attention to the CMDB: When multiple parties have to work on the CMDB and are only allowed to work on a specific part of the CMDB (example in the CMDB there is data from different customers and a party is only allowed to work on data from selected customers) as far as I know domain separation is needed.

Hope this helps.

Cheers,

Ed