IDR (Instance Data Replication) Vs Service Bridge

[snehapatel]

If you have 2 service instances (one for the parent company & one for the child company), could you please suggest what is the right choice to be used (IDR Or Service Bridge or any other option) to achieve the following for the data synch/replication

1) The incident is raised in child company instance. However when it is being assigned to a particular assignment group, it should be created in parent company instance as this assignment group access the parent company instance. Thereafter the comments posted by the assignment group in the parent instance should be replicated to child instance.

2) A service request of particular type raised in child instance should be created in parent instance as this service request would be worked upon by assignment group using the parent instance. Once the service request is updated on the parent instance, the respective updates should be reflected in the child instance as well

Also would like to understand the options from pricing perspective - which one would be cheaper if both IDR and Service Bridge can fulfil the above requirements

Thanks,

Sneha

[JC Moller]

Why not just integrate the two instances with a REST API integration?

And if you really need to invest in a well working integration landscape, then have a look at Sharelogic's Unifi integration framework. Best store app available and a massive time / expense saver when it comes to implementing quality integrations in no time. Have been using this with several customers and altogether have implemented +70 integrations with fast ROI.

https://store.servicenow.com/sn_appstore_store.do#!/store/application/74f0b4550f8ca20094f3c09ce1050e...

[Kalyan Madineni]

In this case I believe Service Bridge will be more appropriate as it allows a Business Process level Integrations.

Service Bridge is an application that uses Instance Data Replication (IDR) as a core component to enable high-level business process integration, such as sharing service catalogs and handling requests between different ServiceNow instances. In contrast, IDR is a lower-level data replication tool that solely replicates data from one or more "producer" instances to "consumer" instances, without the business logic and user interface features of Service Bridge.

Feature	Service Bridge	Instance Data Replication (IDR)
Primary Function	A business-focused application for cross-instance collaboration, service request management, and workflow automation.	A technical tool for replicating specific data tables between instances.
User-facing features	Provides features for both providers and consumers, such as publishing remote catalogs, tracking requests, and managing bidirectional task integration.	Offers no user-facing features; it's a background process for data synchronization.
Level of integration	High-level, business-process integration, creating a seamless experience for end-users to interact with other instances.	Low-level, data-level integration, focused on keeping specific tables in sync between instances.
How it works	Leverages IDR to synchronize data, but adds a framework for managing business processes like service requests and tasks.	Replicates data based on a defined configuration, including specific tables and any hierarchy within them.
Typical use case	A managed service provider (MSP) or a large organization integrating with partners to share services and support requests.	Replicating a "User" table from one instance to another for general user management or a "Location" table for a business-wide location list.