Adding dependencies of impacted assets
Summarize
Summary of Adding dependencies of impacted assets
The Yokohama release enables ServiceNow Business Continuity Management (BCM) customers to add dependencies of impacted assets in events and exercises. These dependencies are based on source data and relationships defined in the Configuration Management Database (CMDB), Business Impact Analyses (BIAs), and plans. This capability helps BCM users understand and manage asset dependencies during continuity planning and event management.
Show less
Key Features
- Event Dependency Source Configuration Module: BCM administrators configure sources for fetching event dependencies through this module, accessible via Business Continuity Workspace > General Administration > Event dependency source configuration. This is a one-time setup that defines target records, filter conditions, and sources such as BIA upstream/downstream dependencies, CMDB, plan primary assets, and related assets.
- Manual and Automated Dependency Updates: Dependencies are added to events only when users select the Update dependencies UI action. Manual source dependencies are added explicitly, while configured sources are fetched in real-time based on filter matches.
- Roles and Permissions: BCM program managers, planners, and managers typically update dependencies within events. BCM administrators manage the configuration of dependency sources.
- Workflow for Manual Updates: When the Update dependencies action is selected, the system checks event records against configuration filters and fetches dependencies accordingly, ensuring the impacted asset dependencies are current.
- Data Relationships Framework Support: Starting with Yokohama, the BCM application leverages the Data Relationships Framework (installed by default) to underpin the management of asset dependencies in events and exercises, enhancing data relationship handling.
Practical Benefits for ServiceNow Customers
- Improved accuracy in identifying impacted assets and their dependencies during continuity events and exercises.
- Streamlined management of dependencies through configurable sources and manual update options, tailored to organizational needs.
- Enhanced visibility into asset relationships, supporting better risk assessment and recovery planning.
- Clear role-based controls to ensure proper governance and administration of dependency data.
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
The BCM administrators can configure the sources to get the event dependencies in the Event dependency source configuration module. You can access the auto-update configuration module by navigating to .
The Event dependency source configuration module is shown in the following example.
When the BCM administrators can update the target records, filter condition for the records, and sources to fetch the event dependency.
- BIA upstream dependency
- BIA downstream dependencies
- CMDB
- Plan primary assets
- Plan related assets
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.
Roles associated with event dependency updates
- The BCM program managers, BCM planners, and BCM managers can update the latest dependencies.
- BCM administrators can configure the Event dependency source configuration module.
Workflow for updating the dependencies manually in the events and exercises
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 following example.
- The BCM planner navigates to the event record.
- The BCM planner selects the Update dependencies UI action to add the assets manually.
The application checks if the event record matches any configuration filter.
- If the event record matches any configuration filter, the system gets the dependencies of the added assets in real-time according to the sources defined in the configuration (Event dependency source configuration module).
- If the event record does not match any configuration filter, the events workflow then continues for the next steps.
For more information on updating the event dependencies manually, see Update the event dependencies.
Data Relationships Framework
Beginning with the Yokohama release, the Data Relationships Framework (com.sn_app_grc_relationship_config) application supports the BCM application with the underlying framework to add the dependencies of the impacted assets in the 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.