---
sourceDocument: Australia Governance, Risk, and Compliance
sourceDocumentLink: https://servicenow-prod.fluidtopics.net/r/governance-risk-compliance

 Release :

    - australia

ft:locale :

    - en-US

ft:publication_title :

    - Australia Governance, Risk, and Compliance

ft:clusterId :

    - grc

bundleId :

    - grc

workflow :

    - Technology


---

# Adding dependencies of impacted assets

# Adding dependencies of impacted assets {#ariaid-title1}

* Release version: Australia
* 
* Updated March 12, 2026
* 
* ![](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 Adding dependencies of impacted assets

ServiceNow's Business Continuity Management (BCM) application allows you to add dependencies of impacted assets in events and exercises by leveraging source data and relationships from the Configuration Management Database (CMDB), Business Impact Analyses (BIAs), and plans.
This functionality helps you accurately reflect asset dependencies and improve event impact assessments.
Show full answer Show less  

## Configuring Event Dependency Sources

BCM administrators configure the sources for event dependencies within the Event dependency source configuration module, accessible from the Administration menu in the Core UI. This configuration is a one-time setup that defines which records, filters, and data sources (such as BIA upstream/downstream dependencies, CMDB, and plan assets) are used to fetch dependencies.

Once configured, dependency updates synchronize automatically within events when triggered by users via the **Update dependencies** UI action.

Note that dependencies with a source marked as Manual must be added manually for each event.

## Roles and Responsibilities

* **BCM Program Managers, Planners, and Managers:** Responsible for updating dependencies in events to ensure data currency.
* **BCM Administrators:** Responsible for configuring the Event dependency source configuration module.

## Manual Update Workflow

When a BCM planner selects the **Update dependencies** UI action in an event record, the system manually adds dependencies for assets sourced as Manual. The application then:

* Checks if the event record matches any configured filter.
* If matched, retrieves asset dependencies in real time from configured sources.
* If not matched, continues with the event workflow for subsequent steps.

This process ensures that impacted asset dependencies are current and aligned with your organizational data.

## Data Relationships Framework

Starting with the Australia release, the Data Relationships Framework (com.snappgrcrelationshipconfig) underpins the addition of impacted asset dependencies in events and exercises. This framework is included by default with the BCM application and provides a standardized, scalable approach to managing asset relationships critical to business continuity.  
You can add the dependencies of the impacted assets in the events and exercises based on the source data and relationships in the CMDB, BIAs, and plans.

## Configuring the sources in the Event dependency source configuration module {#import-event-dep-updates__id_gsb_lwf_xzb}

The BCM administrators can configure the sources to get the event dependencies in the Event dependency source configuration module. You can access the Event dependency source
configuration module from the Administration menu in the Core UI.

The Event dependency source configuration module is shown in the example.

The BCM administrators can update the target records, filter conditions, and sources to fetch the event dependency.  
Dependencies are added in the events only when the user selects the Update dependencies UI action. Dependencies are fetched from these sources for the events:

* BIA upstream dependency
* BIA downstream dependencies
* CMDB
* Plan primary assets
* Plan related assets

{#import-event-dep-updates__ul_uhy_mv4_b1c}  
Note:  
In an event, the dependencies of all assets are added manually where the source is Manual.

Setting up the Event dependency source configuration module is a one-time activity. Once the sources are configured in the Event dependency source configuration module, the updates are synchronized in the events.

For more information on setting up the Event dependency source configuration module, see [Configure Event dependency source configuration record](https://servicenow-prod.fluidtopics.net/kGmmKZtY9lhvOASznwPy0g "Configure the sources for adding the event dependencies in the Event dependency source configuration record.").

## Roles associated with event dependency updates {#import-event-dep-updates__section_yps_f3q_hzb}

Users with these roles check for the dependency updates in an event:

* The BCM program managers, BCM planners, and BCM managers can update the latest dependencies.
* BCM administrators can configure the Event dependency source configuration module.
{#import-event-dep-updates__ul_pdp_mnl_mzb}

## Workflow for updating the dependencies manually in the events and exercises {#import-event-dep-updates__section_d5r_bym_zyb}

As the BCM application user, when you select the Update dependencies UI action in the Event record, the dependencies of all assets are added manually where the
source is Manual.

The BCM application executes a workflow to update the impacted assets in the events and exercises as shown in the example.

1. The BCM planner navigates to the event record.
2. The BCM planner selects the Update dependencies UI action to add the assets manually.
3. The application checks if the event record matches any configuration filter.

4. If the event record matches any configuration filter, the system retrieves asset dependencies in real time based on sources defined in the Event dependency source configuration.
5. If the event record does not match any configuration filter, the events workflow then continues for the next steps.

{#import-event-dep-updates__ol_n1l_n3z_czb}

For more information on updating the event dependencies manually, see [Update the event dependencies](https://servicenow-prod.fluidtopics.net/fF1GZIn2pB8wl2Imm5keJA "Update the event dependencies manually by selecting the Update dependencies UI action. You can update the dependencies in an active event.").

## Data Relationships Framework {#import-event-dep-updates__section_cm5_2hl_mzb}

Beginning with the Australia release, the Data Relationships Framework (com.sn_app_grc_relationship_config) provides the framework to add impacted asset dependencies in events and exercises. The Data Relationships Framework application is installed with the BCM application by default.

For more information on the Data Relationships Framework, see [Data Relationships Framework](https://servicenow-prod.fluidtopics.net/XY8p9NXpWII1Lr6oTtFWjQ "The Data Relationships Framework application (sn_grc_rel_config) supports the BCM application with the underlying framework to fetch the dependencies in the BIAs, plans, and events 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.").