--- sourceDocument: Australia Governance, Risk, and Compliance sourceDocumentLink: https://www.servicenow.com/docs/r/australia/governance-risk-compliance Release : - australia ft:locale : - en-US ft:publication_title : - Australia Governance, Risk, and Compliance ft:clusterId : - grc bundleId : - grc workflow : - Technology --- # Data Relationships Framework # Data Relationships Framework {#ariaid-title1} Release version: Australia Updated March 12, 2026 ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 5 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 Data Relationships Framework The Data Relationships Framework (application sngrcrelconfig) is a foundational component installed by default with the BCM (Business Continuity Management) application starting from the Australia release. It facilitates fetching and managing dependencies across BIAs (Business Impact Analyses), plans, and events by retrieving data from multiple sources such as the CMDB, BIA, and BCP. Show full answer Show less This framework enables BCM users to configure how main object types relate to child object types, manage dependency updates through scheduled jobs, and consolidate dependency data efficiently. ## Key Features * **Unified Dependency Retrieval:** Provides a single API to fetch dependencies from varied sources ensuring consistency and simplified integration. * **Configurable Main and Child Nodes:** Allows configuration of main nodes (sources) and their relationships with child nodes like assets and risks. * **Scheduled Dependency Updates:** Regularly scans configured objects to identify and fetch updated dependencies automatically. * **Performance Control:** Enables users to select different sources to balance performance and data needs. * **Role-Based Access:** Includes specific roles for administration (configuring relationships) and reading (viewing data), with all BCM users granted reader access by default. * **Configurable Tables and Modules:** Utilizes new and existing tables for storing main node configurations, node relationships, and relationship registries. Provides modules to configure main nodes, relationship registries, and framework properties. ## Practical Configuration and Use BCM administrators can use the Data Relationships Framework modules to: * Create and configure **main node configurations** specifying source, table, and filter conditions to control how dependencies are fetched. * Define **node relationship configurations** to establish connections between main nodes and child nodes. * Set up **relationship registries** to specify how objects relate within the system's 360-degree configuration. * Adjust framework **properties** to tailor behavior and performance. Use cases include mapping incidents, assets, and risks to represent complex dependency relationships, which supports impact analysis, planning, and event management. ## Limitations * Dependency data fetched for one object cannot be reused for other purposes. * Only the predefined sources within the framework can be used for fetching dependency updates; custom sources cannot be configured. ## Next Steps for ServiceNow Customers * Leverage the Data Relationships Framework to improve dependency tracking and impact analysis across BCM processes. * Use the provided roles to manage configuration securely and grant appropriate access to BCM users. * Configure main nodes and relationship registries carefully to optimize data retrieval and reduce unnecessary data load. * Stay aware of framework limitations when planning integrations or customizations involving dependency data. The Data Relationships Framework application (sn_grc_rel_config) supports the BCM application with the underlying framework to fetch dependencies in BIAs, plans, and events. It retrieves data from different sources such as CMDB, BIA, and BCP. Beginning with the Australia release, the Data Relationships Framework (sn_grc_rel_config) application is installed with the BCM application by default. The video gives you an overview of the Data Relationships Framework and how it fetches dependencies in BIAs, plans, and events from different sources. ## Framework for fetching the dependencies {#data-relationship-framework__section_zpt_fj3_nzb} The Data Relationships Framework (sn_grc_rel_config) stores the configurations for how a main object type can relate to other object types. It enables you to configure the source (main node) for the dependency updates and configure its relationship with the child nodes. You can fetch the dependencies for the selected object. A scheduled job scans the object configuration data at regular intervals and checks if any dependencies have been updated. If any changes are observed, the scheduled job fetches the dependencies of the selected object. The dependencies are fetched from one of the configured sources such as BIA, BCP, or CMDB. ## Benefits of the Data Relationships Framework {#data-relationship-framework__section_qzc_xvh_nzb} The Data Relationships Framework provides the following benefits for the BCM application users: * Provides a single API to fetch the dependencies from different sources. * Supports the configuration of the main node (source) and maintains its relationships with its child nodes such as assets, risks, and so on. * Enables the users to control the performance by selecting different sources. {#data-relationship-framework__ul_ovf_1wh_nzb} ## Roles associated with the Data Relationships Framework {#data-relationship-framework__section_e45_ppg_rzb} The following roles are associated with the Data Relationships Framework application.{#data-relationship-framework__table_tbw_wpg_rzb__entry__2} | Roles | Description | |-|-| | Data Relationships Framework administrator \[sn_grc_rel_config.admin\] | Configures the relationship of the object types such as the relationship of the main node to the child nodes. | | Data Relationships Framework reader \[sn_grc_rel_config.reader\] | Views the data for the object types as defined in the Data Relationships Framework. Note: All BCM application users have the Data Relationships Framework reader role. | [Table 1. Roles associated with the Data Relationships Framework] {#data-relationship-framework__table_tbw_wpg_rzb} ## Tables for the framework {#data-relationship-framework__section_ysr_vwh_nzb} To support the Data Relationships Framework, the following new tables have been added and existing tables have been revised. {#data-relationship-framework__table_gkf_zwh_nzb__entry__3} | New and existing tables | Table | Description | |-|-|-| | New table | Main node configuration \[sn_grc_rel_config_main_node_confi\] | Table to store the configuration of the main node from where the dependencies are fetched. | | New table | Node relationship configuration \[sn_grc_rel_config_node_rel_config\] | Table to store the configuration that determines the dependencies of the main node and child nodes. It also maintains a reference to the main node configuration. | | Existing table | Relationship registries \[sn_data_registry_relationship\] | Table to determine the relationship of an object with other objects. | [Table 2. Tables used for the Data Relationships Framework] {#data-relationship-framework__table_gkf_zwh_nzb} ## Modules for configuring the relationships {#data-relationship-framework__section_fyt_hdg_rzb} The BCM application users can navigate to Data Relationship Framework in the application navigator and access its modules for configuring the relationships. The Data Relationships Framework application consists of the following modules: 1. Main node configuration: Configure the details of the main node such as its name, source, table name, filer conditions, and so on as shown in the following examples. The following main node configurations are provided as sources with the base system as shown in the following example: * BIA upstream dependency * BIA downstream dependencies * CMDB * Plan primary assets * Plan related assets {#data-relationship-framework__ul_alv_rfg_rzb} The BCM administrators use the main node configuration to perform the following tasks: * Configure the Impact analysis dependency update configuration module and fetch the dependency updates into a BIA (add the dependency updates to the BIA) from these sources. * Configure the Planning dependency update configuration module and fetch the planning dependency updates into a plan (add the updated related assets to the plan) from these sources. * Configure the Event dependency source configuration module and configure the sources for the event dependency updates (add the updated impacted assets to a recovery event). {#data-relationship-framework__ul_umb_mr4_rzb} Note: All the information on how data should be pulled is stored in the Main node configuration, which is attached to the records. This configuration determines the order in which the data is pulled. To reduce the amount of data pulled and how it is pulled, you need to configure the conditions in both the Main node configuration and the records. This ensures that only the necessary data is retrieved. The main node configuration records for plans and CMDB are shown in the following examples. For information on creating a main node configuration record, see [Create a main node configuration record](https://www.servicenow.com/docs/Km2jUTQ_5E~YkgvyX72Lyw "Create a main node configuration record to configure the source for fetching the dependencies. You can configure the details of the main node such as its name, source, table name, filter conditions, and so on."). 2. Relationship registries: Configure the relationship registries for the main node. Relationship registries are part of the 360-degree configuration in GRC where a user can define how one object has a related object. The configuration details of a relationship registry record such as its name, table, relationship type, relationship table, and so on are shown in the form. A sample relationship registry record for a BIA and BIA template is shown in the following example. For information on creating a relationship registry record, see [Create a relationship registry record](https://www.servicenow.com/docs/gvr0SZj41NwGluyNMrKSTQ "Create a relationship registry record to set up relationship between the record and object defined in the table. You can configure the details of the main node such as its name, source, table name, filter conditions, and so on."). 3. Properties: Configure the properties of the Data Relationships Framework as shown in the following example. For information on configuring the properties, see [Configure the properties for the Data Relationships Framework](https://www.servicenow.com/docs/ZdZIipMKly~m9fS5MLzr0g "Configure the properties for the Data Relationships Framework application."). {#data-relationship-framework__ol_ckw_sdg_rzb} ## Use cases for the Data Relationships Framework {#data-relationship-framework__section_owz_pwh_nzb} The Data Relationships Framework is used to configure the node and asset relationships such as mapping a main node to its child node or mapping an asset to a risk. Consider the following use case that shows the main node configuration and its relationships. In this example, INC1010 is the main node where the source is an Incident. INC1010 has two child nodes: 1. Asset A: The affected configuration item for Asset A is Risk A. 2. INC1011: The affected configuration items (CIs) for INC1011 are Asset B and Asset C. For Asset B, the affected configuration item is Risk B. {#data-relationship-framework__ol_uvf_nxf_rzb} With the underlying Data Relationships Framework, the following relationships are configured: * Main nodes: * INC1010 -\> Asset A * INC1010 -\> INC1011 {#data-relationship-framework__ul_pj3_d1g_rzb} * Node relationships: * Asset A -\> Risk A * INC1011 -\> Asset B * INC1011 -\> Asset C * Asset B -\> Risk B {#data-relationship-framework__ul_vr2_21g_rzb} * Input nodes: * Source = Incident * Record = INC1010 * Max Levels = 5 * Max Nodes = 1000 {#data-relationship-framework__ul_n2b_31g_rzb} * Output nodes: * INC1010 * Asset A * INC1011 * Risk A * Asset B * Asset C * Risk B {#data-relationship-framework__ul_w3m_k1g_rzb} * Edges: * INC1010 -\> Asset A * INC1010 -\> INC1011 * Asset A -\> Risk A * INC1011 -\> Asset B * INC1011 -\> Asset C * Asset B -\> Risk B {#data-relationship-framework__ul_ysr_n1g_rzb} {#data-relationship-framework__ul_aqh_lyf_rzb} ## Limitations of using the Data Relationships Framework {#data-relationship-framework__section_ugb_2wh_nzb} The Data Relationships Framework has the following limitations: * The data fetched for an object cannot be reused for another purpose. * The sources provided in the framework must be used for fetching the dependency updates into an object. It is not possible to configure your own sources for fetching the data. {#data-relationship-framework__ul_g5s_fwh_nzb} For more information on the administrative setup for the configuration records, see [Dependency Configuration records](https://www.servicenow.com/docs/WxjjmIUFl_QAREWzdNHaQw "The BCM administrators configure the Dependency Configuration records."). * **[Create a main node configuration record](https://www.servicenow.com/docs/Km2jUTQ_5E~YkgvyX72Lyw)** Create a main node configuration record to configure the source for fetching the dependencies. You can configure the details of the main node such as its name, source, table name, filter conditions, and so on. * **[Update the node relationship configuration](https://www.servicenow.com/docs/UBMDOiVtmJu1~H5KKKz1gg)** Update the node relationship configuration for each main node configuration. In the Node relationship configurations related list, select the sequence and update the source table, relationship registry, relationship table, target table, and target conditions. * **[Create a relationship registry record](https://www.servicenow.com/docs/gvr0SZj41NwGluyNMrKSTQ)** Create a relationship registry record to set up relationship between the record and object defined in the table. You can configure the details of the main node such as its name, source, table name, filter conditions, and so on. * **[Configure the properties for the Data Relationships Framework](https://www.servicenow.com/docs/ZdZIipMKly~m9fS5MLzr0g)** Configure the properties for the Data Relationships Framework application.