Setting up pillars, entity types, entity filters, and entities

This section helps you configure the Operational Resilience application to organize and track your organization's operational data through a structured hierarchy of pillars, entity types, and entities.

Key concepts and definitions in Operational Resilience

It is essential to understand the core terminology and how different components relate to each other. This section defines the key concepts that form the foundation of the application's data structure. Knowledge of these terms enables informed decision-making during setup and confirms that the system is configured correctly for your organization's needs. The table provides definitions and practical examples for each concept.

Consider the example of organizing a filing cabinet where pillars are drawers, entity types are folders within each drawer, entity filters are the labels that determine what goes in each folder, and entities are the actual documents.

Understanding the data hierarchy

The Operational Resilience application organizes data in a multi-level hierarchy as shown in the example.

Key relationships between pillars, entity types, and entity filters

Understanding how different levels of the data hierarchy interact with each other is crucial for effective configuration and maintenance of the Operational Resilience application.

Note: The CMDB relationships flow into Operational Resilience in one direction only. Changes to Operational Resilience entities do not update the CMDB relationships automatically. If relationships change in the CMDB, new entity relationships are created, but old relationships aren’t automatically deleted—you may need to delete them manually.

Required roles, their capabilities, and checklist

Before beginning the setup process, verify that you have the required roles to perform the setup.

• Required roles for the setup

  sn_oper_res.admin, sn_oper_res.manager

• Role capabilities

  Role	Can activate pillars	Can create Entity types	Can delete Entity types	Can generate entities
  sn_oper_res.admin	Yes	Yes	Yes	Yes
  sn_oper_res.manager	Yes	Yes	No	Yes

• Checklist

  Complete the checklist before you begin the setup:

  1. Confirm that you have the required roles to perform the setup.
  2. Review the list of default pillars. The default pillars are: Services, Business Services, Business Processes, Technology, Facilities, People, Suppliers, Data, Application Services, and Service Offerings.
  3. Identify the pillars and entity types that you would need for your organization.
  4. Determine if you need custom entity types in addition to the default entity types.
  5. Understand your CMDB structure and relationships.
  6. Allocate sufficient time for the initial setup.

Note: Beginning with Operational Resilience, Release 21.x.x, all pillars are shipped in an "Inactive" state. You must activate the pillars before activating the entity types, as the entity types depend on the pillars. Entity types can be activated only after their parent pillars are active.

Using the Workspace UI or Admin setup

This section provides a high-level overview of the Workspace UI or the Admin setup from Core UI in the Operational Resilience.

Note: Use the Workspace UI to use latest features and enhancements. The Core UI is part of the classic interface. You can switch between them at any time.

Step-by-step overview

Setting up Operational Resilience follows a logical progression from foundational components to data generation. This overview helps you understand what each step accomplishes and why the sequence matters. Detailed procedures with screenshots and examples are available in the subsequent sections.