--- sourceDocument: Yokohama Governance, Risk, and Compliance sourceDocumentLink: https://www.servicenow.com/docs/r/yokohama/governance-risk-compliance Release : - yokohama ft:locale : - en-US ft:publication_title : - Yokohama Governance, Risk, and Compliance ft:clusterId : - grc bundleId : - grc workflow : - Technology --- # Relationships between CSDM objects # Relationships between CSDM objects {#ariaid-title1} * Release version: Yokohama * * Updated July 31, 2025 * * ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read Summarize ![AI sparkle icon](https://servicenow.com/docs/portal-asset/ai-sparkle-icon) Summarized using AI This content was generated using new OpenAI-powered functionality. Results are provided on an as is basis and are not guaranteed to be accurate or complete. ## Summary of Relationships between CSDM objects This guide explains how to configure and manage relationships between various Common Service Data Model (CSDM) objects such as business services, service offerings, business processes, and application services within ServiceNow. These relationships are essential for accurately mapping dependencies and service structures in Operational Resilience, enabling effective reporting and impact analysis. Show full answer Show less ## Key Features * **Main node configurations:** Used to establish and manage relationships between CSDM objects. Configuration relies on the `sngrcm2mprofileprofile` table as the source. * **Entity relationships:** Support relationships between business services, service offerings, business processes, and application services, including dependencies. * **Dependency mapping:** Dependencies such as underlying components (e.g., servers or applications) linked to business processes or services can be defined and visualized. * **CI relationships table:** All configuration management database (CMDB) relationships are stored in the `cmdbrelci` table. * **Integration with Operational Resilience:** Entities must be set up in Operational Resilience to enable relationship establishment and data synchronization for reporting. ## Practical Application For example, a business service (BS1) can include service offerings (SO1, SO3), business processes (BP1, BP2), and application services (AS1). Service offerings and business processes have dependencies such as specific servers or application services. When configured correctly: * The **Applies to** field in a Business Impact Analysis (BIA) reflects accurate dependency relationships. * Parent-child relationships, like a service offering's parent being a business service, are automatically fetched and maintained through scheduled jobs. * The same relationship types can be applied across multiple forms, enhancing flexibility in modeling service dependencies. ## Key Outcomes * Establishing these relationships enables comprehensive visibility into service and process dependencies, critical for impact analysis and resilience planning. * Accurate data synchronization with Operational Resilience ensures that risk assessments and reporting reflect the true state of service dependencies. * Streamlined management of relationships improves the quality of CMDB data and supports better decision-making around service continuity and risk mitigation. You can configure relationships between various CSDM objects such as business services, service offerings, business processes, and application services by using the Main node configurations. The \[sn_grc_m2m_profile_profile table\] serves as the source table for establishing these relationships. ## Establishing relationships between different objects {#build-up-relationships__section_ujl_fxk_v2c} To illustrate the relationships between different CSDM objects, consider the following example of a business service (BS1). The business service (BS1) includes the following objects as shown in the example. * Service offering (SO1) * Business process (BP2) * Application service (AS1) * Service offering (SO3) {#build-up-relationships__ul_kzz_2fj_bfc} The Service offering (SO1) is related to the Business process (BP1) and Service offering (SO2). BP1 has the following dependencies: * Acer * PS Apache01 {#build-up-relationships__ul_mzz_2fj_bfc} BP2 has a dependency on PS Apache02. AS1 has a dependency on AS2 and AS2 has a dependency on PS Apache03. Note: When you set up the Main node configurations, you must ensure that the entities are set up in Operational Resilience. Only when these entities exist, relationships can be established between the CSDM objects and then data is brought into Operational Resilience for reporting. The Applies to field in a business impact analysis (BIA) shows the object that has the dependency. The example shows that the business process (BP1) has Acer as a dependency. The dependency is also brought from the Parent field into Operational Resilience for the service offerings and application services. For example, the parent for service offering (SO3) is business service (BS1). Therefore, when the scheduled job is executed, it fetches SO3 as a configured relationship for business service (BS1). All the CMDB relationships, as shown in the example, are maintained in the CI relationships \[cmdb_rel_ci\] table. To bring these relationships into Operational Resilience, you must use the Main node configurations. For more information, see [Configure the Main node configurations](https://www.servicenow.com/docs/y2fn_ZvGjrtSqXZlucbdtA "Create the Main node configuration record to fetch data into Operational Resilience for reporting. Main node configurations are available with the base system. You can use the existing Main node configurations or create new Main node configurations for your business needs."). You can establish the following relationships between objects such as business services, service offerings, and business processes. {#build-up-relationships__table_zpx_rxk_v2c__entry__2} | Entity | Relationships | |-|-| | Business services | * Service offering for a business service: BS -\> SO1, SO2 * Business process for a business service * Application service for a business service * Dependencies for a business service {#build-up-relationships__ul_w4v_gxk_v2c} | | Service offerings | * Business process for a service offering * Application service for a service offering * Dependencies for a service offering {#build-up-relationships__ul_b5d_kxk_v2c} | | Business processes | * Application service for a business process * Dependencies for a business process {#build-up-relationships__ul_clw_yxk_v2c} | [Table 1. Establishing relationships] {#build-up-relationships__table_zpx_rxk_v2c} The same relationship can be applied and used on multiple forms. For example, the business process relationship can be used on both Business service and Service offering forms. For information on the Main node configurations, see [Main node configurations: A component of the Data Relationships Framework](https://www.servicenow.com/docs/ySn9cOzE68eueRJpssgjdA "Starting with Release 20.1.x, the Main node configurations, supported by the Data Relationships Framework, are available with Operational Resilience to define dependency roll-up chains. Operational Resilience administrators configure the entity types and pillars, generate the entities, and then establish relationships between different CSDM objects. After this setup is complete, data from the CMDB is fetched into Operational Resilience, displaying rolled-up dependencies in the Workspace view.").