Dependency Configuration records
Summarize
Summary of Dependency Configuration records
BCM administrators manage Dependency Configuration records within the Business Continuity Management module to automate updates of Business Impact Analysis (BIA) dependencies, related assets, and sources based on data and relationships from the CMDB. This capability is crucial for ensuring accurate and timely updates in BCM processes.
Show less
Key Features
- Access to updated dependency information starting with the Xanadu release.
- Options to pull dependencies from "All records" or "Latest record only" based on the selected configuration.
- Integration of various sources for dependency updates, including BIA upstream and downstream dependencies and CMDB.
- Configuration records necessary for the Update dependencies UI action and scheduled jobs.
Key Outcomes
By properly configuring the dependency updates, BCM administrators can expect:
- Efficient retrieval of dependencies for impact analysis, plans, and events.
- Streamlined updates that reflect the latest information from BIA and CMDB.
- Enhanced accuracy in planning and executing business continuity strategies.
For further details on configuring specific dependency updates, refer to the relevant configuration guides mentioned within the content.
The BCM administrators configure the Dependency Configuration records.
Administrators configure the Dependency Configuration records in the administrator view (UI 16 view) to schedule an auto-update of the BIA dependencies, related assets, and sources based on the source data and relationships in the CMDB.
The following example shows the Planning dependency update configuration record.
Consider an example where you have 2 BIAs done on Acrobat and the configuration is shown in the example. When All records option is selected and you select Update dependencies UI action from the plan record, the application pulls all the dependencies in all BIA records that satisfy the requirement. As shown in the example, dependencies of both BIA Latest and BIA Old records are pulled into the plan.
When Latest record only option is selected and you select Update dependencies UI action from the plan record, the application considers one of the record of the two BIAs and it fetches the dependency assessment of that BIA record.
For the Update dependencies UI action in the plan record and the Update BCP dependencies snapshot scheduled job to function, it is necessary to have the Impact analysis dependency update configuration, Planning dependency update configuration, and Event dependency source configuration records established.
Pulling latest dependency updates for impact analysis, plans, and events
You can pull latest dependency updates for impact analysis, plans, and events. Choosing All records or Latest record only functionality is applicable for Impact analysis dependency update configuration, Planning dependency update configuration, and Event dependency source configuration records.
For Impact analysis dependency updates, pulling all BIA records or the latest BIA record may yield the same information. For planning dependency updates and event dependency updates, pulling all BIA records or the latest BIA record pulls the latest dependency updates.
- BIA upstream dependency
- BIA downstream dependencies
- CMDB
- BIA upstream dependency
- BIA downstream dependencies
- CMDB
- Plan primary assets
- Plan related assets
For information on configuring the impact analysis dependency updates, see Configuring the impact analysis dependency updates.
For information on configuring the planning dependency updates, see Configuring the planning dependency updates.
For information on configuring the sources for adding the event dependencies, see Configuring the sources for adding the event dependencies.