The framework enables configuration of main object types (main nodes) and their relationships with child nodes, allowing BCM users to efficiently track and update dependencies across different sources. A scheduled job regularly scans and retrieves updated dependencies to maintain accurate relationship data.

Key Features

• Unified API: Offers a single API to fetch dependencies from multiple configured sources (BIA, BCP, CMDB).
• Main Node Configuration: Allows BCM administrators to define main nodes including their source, table name, and filters to control how and what dependency data is retrieved.
• Node Relationship Configuration: Supports defining how main nodes relate to child nodes such as assets, risks, or other objects to build comprehensive dependency maps.
• Scheduled Dependency Updates: Automatically detects changes and fetches updated dependency data to ensure plans and events reflect current relationships.
• Role-Based Access: Includes roles for administrators to configure relationships and readers who can view relationship data; all BCM users have reader access by default.
• Configuration Tables: Utilizes new tables for main node and node relationship configurations and existing relationship registries to store and manage dependency data systematically.
• Performance Control: Enables selection of data sources and filtering conditions to optimize data retrieval and system performance.

Practical Use and Configuration

BCM administrators can configure dependency sources via modules such as Main Node Configuration and Relationship Registries within the Data Relationships Framework. These configurations define where and how dependency data is pulled, including impact analysis, planning, and event dependency updates. Conditions set within configurations help limit retrieved data to necessary information only.

For example, the framework can map incidents as main nodes to affected assets and associated risks as child nodes, creating a clear, multi-level dependency graph that supports BCM decision-making.

Limitations

• Fetched dependency data is specific to its configured use and cannot be repurposed for other contexts.
• Only the predefined sources within the framework can be used for fetching dependency updates; custom sources cannot be added.

Next Steps for Customers

• Create Main Node Configuration Records: Define sources and filtering criteria to specify how dependencies are fetched for your BCM objects.
• Update Node Relationship Configurations: Specify relationships between main nodes and child nodes to accurately represent dependencies.
• Create Relationship Registry Records: Set up how different object types relate to each other within the BCM context.
• Configure Framework Properties: Adjust settings to fine-tune framework behavior according to organizational needs.

By leveraging the Data Relationships Framework, ServiceNow BCM customers can achieve streamlined, automated dependency management across BIAs, plans, and events, enhancing the accuracy and responsiveness of continuity planning and response activities.