Establishing relationships between different objects

To illustrate the relationships between different CSDM objects, consider the following example of a business service (BS1).

BP2 has a dependency on PS Apache02. AS1 has a dependency on AS2 and AS2 has a dependency on PS Apache03.

The Applies to field in a business impact analysis (BIA) shows the object that has the dependency. The example shows that the business process (BP1) has Acer as a dependency.

The dependency is also brought from the Parent field into Operational Resilience for the service offerings and application services. For example, the parent for service offering (SO3) is business service (BS1). Therefore, when the scheduled job is executed, it fetches SO3 as a configured relationship for business service (BS1).

All the CMDB relationships, as shown in the example, are maintained in the CI relationships [cmdb_rel_ci] table.

To bring these relationships into Operational Resilience, you must use the Main node configurations. For more information, see Configure the Main node configurations.

You can establish the following relationships between objects such as business services, service offerings, and business processes.

The same relationship can be applied and used on multiple forms. For example, the business process relationship can be used on both Business service and Service offering forms.

For information on the Main node configurations, see Main node configurations: A component of the Data Relationships Framework.