Dependency Configuration records
Summarize
Summary of Dependency Configuration Records
The Dependency Configuration records allow BCM administrators to schedule auto-updates of Business Impact Analysis (BIA) dependencies, related assets, and sources based on the Configuration Management Database (CMDB) data. This feature is accessible in the administrator view (UI 16) and is particularly important for maintaining up-to-date information on dependencies related to BIAs, Plans, and Events, especially after the Xanadu release.
Show less
Key Features
- Update Options: Administrators can select either "All records" or "Latest record only" from the Source records to consider in dependency updates.
- Dependency Pulling: Depending on the selection, the application fetches dependencies from all relevant sources or just the latest record for each source.
- Auto-Update Configuration: The configuration records for Impact analysis, Planning, and Event dependencies must be established to enable the Update dependencies UI action and scheduled jobs.
- Dependency Sources: Dependencies are pulled from BIA upstream and downstream dependencies and CMDB for plans and events.
Key Outcomes
By configuring these records, administrators can ensure that the latest dependencies are accurately reflected in their BIAs, plans, and events. This results in enhanced decision-making and improved risk management based on up-to-date data. For effective configuration, refer to specific guides on impact analysis, planning, and event dependency updates.
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 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 records 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 impact analysis dependency updates.
For information on configuring the planning dependency updates, see Configuring planning dependency updates.
For information on configuring the sources for adding the event dependencies, see Configuring sources for adding event dependencies.