{"revision":"c10276e953456835cdbb1f3a60d58ae1980be353","document":{"id":18649,"path":"governance-risk-compliance/update-impactanalysis-dep-based-on-cmdb-changes.md","title":"Scheduling an auto-update of dependencies","bundle":null,"doc_type":null,"release":"australia","body":"\n# Scheduling an auto-update of dependencies\n\nYou can schedule an auto-update of the dependencies in the business impact analysis based on the source data and relationships in the CMDB. You can receive an email notification with details of the BIA dependency updates from the BCM application.\n\n\\[Omitted video\\] Description: An overview of how to update dependencies\n\nThe video shows how BCM Managers can use the CMDB as a source to update dependencies in a Business Impact Analysis \\(BIA\\). The same process applies to Business Continuity Plans \\(BCPs\\) and events.\n\n## Scheduling an auto-update of the dependencies\n\nThe BCM administrators can schedule an auto-update of the BIA dependencies in the Impact analysis dependency update configuration module, based on CMDB data and relationships. You can access the auto-update configuration module by navigating to **Business Continuity Workspace** &gt; **General Administration** &gt; **Impact analysis dependency update configuration**.\n\nThe Impact analysis dependency update configuration module is shown in the example.\n\n\\[Omitted image \"impact-ana-dep-update-config.png\"\\] Alt text: Updating the BIA dependencies.\n\nYou can create multiple rules for the same record. The system evaluates configurations in ascending order and applies the first configuration whose filter condition the record satisfies. For example, you can define another configuration rule for archived BIA records as shown in the example.\n\n\\[Omitted image \"archived-and-non-archived-BIA-records.png\"\\] Alt text: Archived BIA records.\n\nWhen the BCM administrators select the **Auto-update dependencies** option, the BCM application schedules an auto-update of the dependencies in the BIAs. Similarly, when the **Send notification** option is selected, the BCM application sends automated emails to the BIA owners about the dependency updates.\n\nThe source for the BIA dependencies is CMDB.\n\n**Note:** The dependencies are fetched for the BIA that is listed in the **Applies to** field of the BIA record such as HR Application BIA, Accounts Receivable BIA.\n\nSetting up the Impact analysis dependency update configuration module is a one-time activity. Once the sources are configured in the Impact analysis dependency update configuration module, the dependency updates are synchronized in the BIA.\n\nFor more information on setting up the Impact analysis dependency update configuration module, see [Configuring impact analysis dependency updates](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/imp-ana-dep-update-config-module.md).\n\n## Using the updated dependencies with the Xanadu release\n\nBeginning with the Xanadu release, you can use updated dependencies from the latest BIA record to conduct a dependency assessment on an asset. The Related item BIA, Recovery Time Objective \\(RTO\\), Recovery Point Objective \\(RPO\\), and Recovery Tier columns determine required recovery timeframes and data backup needs. The details are then displayed in the Required Recovery Timeframe and Required Data Backup columns of the BIA record.\n\nFor more information on the source BIA records option in the Dependency configuration modules, see [Set up Planning dependency update configuration](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/conf-plan-dep-update-confi-module.md).\n\n## Using the scheduled job to auto-update the dependencies\n\nThe **Update BIA dependencies snapshot** scheduled job is shipped as part of the base system. It runs at regular intervals and fetches the dependency updates. The scheduled job is shown in the example.\n\n\\[Omitted image \"bia-scheduled-job.png\"\\] Alt text: Scheduled job workflow diagram for auto-updating BIA dependencies.\n\nThe scheduled job is not marked as Active by default. To run the scheduled job at regular intervals, the system administrators can select the **Active** option and select **Execute now** to set up a schedule. The scheduled job then runs at regular intervals, scans the BIA records for the changes, and fetches the dependency updates for the updated BIA records. It creates a snapshot record for each BIA update.\n\n**Note:**\n\nThe application is configured with an out-of-the-box \\(OOB\\) limit of 1000 Business Impact Analyses \\(BIA\\) records, as defined by the **sn\\_irm\\_shared\\_cmn.config.get\\_gliderecord\\_limit** system property. This means that the system processes up to 1000 BIA records only, as it cannot exceed this threshold.\n\nThe 1,000 BIA limit applies only if you have more than 1,000 BIAs in the system and have enabled the **Update BIA dependencies snapshot** scheduled job. This scheduled job is inactive by default. If you have enabled it, you must confirm that you review the note. The scheduled job processes records only up to the limit defined in the **sn\\_irm\\_shared\\_cmn.config.get\\_gliderecord\\_limit** property.\n\nThe scheduled job processes a workflow to check for the changes in the relationships and save the dependency updates automatically as shown in the example.\n\n\\[Omitted image \"workflow-for-sche-job-bia-plan.png\"\\] Alt text: Workflow for the scheduled job.\n\n1.  The scheduled job runs weekly, checks the dependency configuration for each BIA record, and fetches the BIA dependencies from CMDB as defined in the **Sources** tab of the Impact analysis dependency update configuration module. It generates a list of all active BIAs and the primary and dependent assets of each BIA. If any new dependencies are added, updated, or deleted for a BIA, the scheduled job creates a snapshot record for the BIA that displays the changes for the user.\n\n    **Note:** By default, the scheduled job checks all the BIA records that are not in the **Archived** state for any updated dependencies.\n\n2.  The scheduled job refers to the filter condition that is set in the configuration \\(Impact analysis dependency update configuration module\\). If the condition matches the BIA record, the scheduled job fetches and stores BIA dependencies in the snapshot record based on sources defined in the configuration. If the filter condition does not match the BIA record, the application skips the record.\n3.  The application combines the assets list into a single list that is based on the priority defined in the Impact analysis dependency update configuration module. The application compares the asset list with the existing asset list and assigns either the **Added**, **Updated**, or **Deleted** state to each asset.\n4.  The application also compares the new assets to the assets listed in the Element definition and verifies the element definition condition. The application creates a snapshot of the asset and auto-completes the dependency updates in the Dependency snapshot record.\n5.  When **Send notification** is set to **True** in the Impact analysis dependency update configuration module, users of the BIA record receive notifications about dependency updates via scheduled job.\n6.  When the **Auto-update dependencies** option is set to **True** in the Impact analysis dependency update configuration module, the scheduled job automatically applies the dependencies snapshot to the BIA record.\n7.  As the final step, the scheduled job updates the BIA record according to the fields to be updated in the configuration.\n\n## Updating the dependencies manually\n\nAs the BCM application user, you can update the BIA dependencies instantaneously by using the **Update dependencies** UI action. In this way, you can update the dependencies manually before the scheduled job runs as per the weekly schedule. The **Update dependencies** UI action is listed in the Dependency assessment of the BIA. The dependencies are then updated in the sources and a snapshot record of the BIA update is created.\n\nSee the workflow for using the **Update dependencies** UI action and updating the dependencies manually:\n\n\\[Omitted image \"bia-plan-update-dependencies.png\"\\] Alt text: Workflow for updating the dependencies manually.\n\n1.  The BCM planner navigates to a BIA record. The application fetches the dependencies of the asset defined in the **Applies to** field of the BIA.\n2.  The BCM planner selects the **Update dependencies** UI action that is listed in the Dependency assessment of the BIA.\n3.  If the snapshot record exists for the BIA update, the system applies the dependencies through the snapshot and updates the BIA according to the **Fields to be updated** in the configuration. The BIA workflow then continues for the next steps such as requesting review and approval.\n\n    If the snapshot record does not exist for the BIA update, the BCM planner checks if the BIA record matches any configuration filter:\n\n    -   If the BIA record matches any configuration filter, the application gets the dependencies in real time according to the sources in the configuration. Then, update the BIA record according to the **Fields to be updated** in the configuration. The BIA workflow then continues for the next steps.\n    -   If the BIA record does not match the configuration filter, the BIA workflow then continues for the next steps.\n\nFor more information on updating the dependencies manually, see [Update the BIA dependencies](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/imp-analysis-dep-update-config.md).\n\n**Note:**\n\n**Note:** The Impact analysis dependency update configuration module is used for using the scheduled job and for updating the dependencies manually \\(by using the **Update dependencies** UI action\\).​\n\n## Snapshot records of the BIA\n\nA snapshot record is created for each BIA update either with the scheduled job or with the **Update dependencies** manual UI action. If any new dependencies are added, updated, or deleted for a BIA, the snapshot record displays the delta of the changes. The snapshot records are listed in the Pending updates module in the Business Impact Analysis list view of the Business Continuity Workspace. A snapshot record is shown in the example.\n\n\\[Omitted image \"snapshot-record.png\"\\] Alt text: Snapshot record.\n\nWhen a snapshot record gets created, the application displays a UI message in the Dependency assessment of the BIA to inform the users about the dependency updates: `The dependencies have been updated in the sources. To review and apply the changes, select here - <link>.` The UI message is shown in the example.\n\n\\[Omitted image \"bia-update-ui-message.png\"\\] Alt text: Snapshot UI message.\n\nThe snapshot records are used for record keeping purposes. The BCM application stores one active snapshot for each BIA at a time. Whenever the dependencies are updated, a snapshot is always created first. As the system processes all the records one by one, the snapshot records are auto-committed one by one in the system.\n\nThe snapshots that are in the **Completed** state and that have not been updated for a few months are removed from the application automatically.\n\nIf the BIA record does not have any changes in the dependencies, then a snapshot record is not created for that BIA record.\n\n## Roles associated with BIA dependency updates\n\nUsers with these roles check for the dependency updates in a BIA:\n\n-   The BCM program managers, BCM planners, and BCM managers can update the latest dependencies​.\n-   BCM administrators can configure the Impact analysis dependency update configuration module.\n\nA user who can update the dependency assessment can import the dependency updates for a BIA.\n\n## Data Relationships Framework\n\nWhen you perform a business impact analysis \\(BIA\\) on an asset, you must evaluate the dependencies of the BIA by performing a dependency assessment. If the dependencies in the CMDB are updated, importing them manually in a BIA can be a tedious activity. Beginning with the Australia release, the Data Relationships Framework application \\(com.sn\\_app\\_grc\\_relationship\\_config\\) supports the BCM application with the underlying framework to fetch the dependencies in the BIA. The Data Relationships Framework application is installed with the BCM application by default.\n\nFor more information on the Data Relationships Framework, see [Data Relationships Framework](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/data-relationship-framework.md).\n\n-   **[Update the BIA dependencies](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/imp-analysis-dep-update-config.md)**  \nUpdate the business impact analysis \\(BIA\\) dependencies manually from the snapshot if the scheduled job is not activated in the Impact analysis dependency update configuration module. You can update the dependencies in an active BIA.\n\n**Parent Topic:**[Structured workflows for BIAs](https://raw.githubusercontent.com/ServiceNow/ServiceNowDocs/australia/markdown/australia/governance-risk-compliance/bia-tasks-performed-by-bia-owner.md)\n\n"}}