Can you have multiple CMDB

[Brian Lancaster]

We have a requirement where we will be getting our CMDB from out customer will all the Services they order from us.   As part of this we are not allowed to modify the CMDB data.   Is there a way to have a second CMDB that we can use to be able to integrate CIs from other vendors that help support our overall customer?

[andymcdonald]

This is a simpler solution that avoids what could be a difficult and error prone effort to create a separate CMDB.   I would encourage all efforts at finding a solution that satisfies the spirit of the requirement without actually building and maintaining a separate CMDB.

[Brian Lancaster]

Ok so we have 1 client and we are setting up our ServiceNow instance to be the system of record for all external services provided to them.   The CMDB is going to be coming from their CMDB into ours and we cannot modify any data in the CMDB without having a financial penalty.   They also have Other vendors that will need to be able to create incidents thought rest calls into our ServiceNow.   We need to create incidents for them but their CI's will not be in our CMDB and we cannot add them.   I don't see any way around this without creating a CMDB for each vendor based on the way the contract is written.

[Dave Smith1]

We need to create incidents for them but their CI's will not be in our CMDB and we cannot add them.

You'll need to make "them" aware that you can create incidents, but without useful and accurate CI information will severely hamper incident investigation and resolution.   Is that what they want?

Ultimately, if they want to manage the CMDB, they need to see themselves as being YOUR service provider, providing an accurate and useful CMDB to assist with incident management.   Without them taking on that task, their own business will suffer.

This isn't a CMDB problem, this is a contractual issue where a supplier isn't providing value to their customer by omitting utility aspects.