Adding the dependencies of the impacted assets

  • Release version: Washingtondc
  • Updated August 1, 2024
  • 2 minutes to read
    • Summarize
    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 the dependencies of the impacted assets

    This guide covers how to add dependencies of impacted assets within Business Continuity Management (BCM) using the Event dependency source configuration module. It enables users to effectively manage and synchronize dependencies during events and exercises based on data from the Configuration Management Database (CMDB), Business Impact Analyses (BIAs), and plans.

    Show full answer Show less

    Key Features

    • Event Dependency Source Configuration: BCM administrators can configure sources to fetch event dependencies, accessed via Business Continuity Workspace > General Administration.
    • Dependency Sources: Dependencies can be sourced from BIA upstream and downstream dependencies, CMDB, plan primary assets, and plan-related assets. Manual sources allow for manual dependency entries.
    • One-Time Configuration: Setting up the Event dependency source configuration is a one-time activity that ensures synchronization of updates across events.
    • Workflow for Manual Updates: Users can manually add dependencies through the Update dependencies UI action, triggering a workflow to check configuration filters and update records accordingly.

    Key Outcomes

    By utilizing these features, BCM program managers, planners, and administrators can maintain accurate and up-to-date dependencies for impacted assets during BCM events and exercises. This ensures effective risk management and continuity planning, enhancing the overall resilience of the organization.

    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 Business Continuity Workspace > General Administration > Event dependency source configuration.

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

    When the BCM administrators can update the target records, filter condition for the records, 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 the following sources for the events:
    • BIA upstream dependency
    • BIA downstream dependencies
    • CMDB
    • Plan primary assets
    • Plan related assets
    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 the Event dependency source configuration record.

    Roles associated with event dependency updates

    Users with the following roles typically 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.

    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.

    Updating the dependencies manually in the events and exercises.

    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 gets the dependencies of the added assets in real time according to the sources defined in the configuration (Event dependency source configuration module).
    5. If the event record does not match any configuration filter, the events workflow then continues for the next steps, 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 Washington DC 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.