When to use Domain Separation?

persahlstrom · ‎12-23-2015

Hello,

I understand that Domain Separation is a way do divide one instance to "multiple instances", is that correct? I'm also wondering in what kind of situation you might have to do it? In my company we are currently having a IT-support group which are the only business entity that use Servicenow as a way of handling incomming cases. Now, we want another business enity within our company to be able to use Servicenow, but not in the same way as our IT-support group. Might this be a typical situation to use domain separation or could there be another solution? I'm pretty new to Servicenow and it's amazing features so please be gentle and bare with me

Best regards,

Per

Uncle Rob · ‎12-23-2015

Per,

Here's the straight answer. The use case you describe is probably the worst justification for domain separation possible. Further, it undermines one of the most important advantages of ServiceNow (acting as a single source of engagement for service consumption). Not meaning this as a slight against inexperience, just wanting to give you a super clear answer.

Consider the following:

- How does separating the domain help you customers engage the services within the company? (hint: it doesn't)

- Why 2x the labor required to manage what could be a single deployment?

- Domain separation is irreversible. If you find out a year from now it was the wrong solution to the problem, then it sucks to be you.

- Most existing and emerging services are not naturally silo'd. Take onboarding for example. List out all the players involved in employee acquisition and you have recruiting, benefits processing, legal, training, facilities, security, and IT too if you're into that kind of thing. The service owners who call for their own privately managed instance of SN (usually via domain sep) seldom have to tell the stakeholders "Hey, if you want to hire someone, please enter a request into these 8 different systems".

The whole point of ServiceNow is to put as many business services as possible into one instance, to reap the benefits of multi-participant workflow, task relationships, unified consumption platform, and collapsed development/support resources.

View solution in original post

Sri45 · ‎02-16-2021

Hi Per,

In addition to comments from others, you may find this article beneficial to read:

https://community.servicenow.com/community?id=community_blog&sys_id=e36caea1dbd0dbc01dcaf3231f961991&view_source=searchResult

Regards,

Sri