Data setup for services or business services
Summarize
Summary of Data setup for services or business services
The data setup for services or business services within Operational Resilience enables managers to verify service data and monitor resilience metrics. This is achieved through the Service (CMDB) Main node for existing customers and the OpRes with CSDM header for new customers. The Services overview and Business services overview tabs can be customized based on organizational needs.
Show less
Key Features
- Service Configuration: Administrators can assign the itil user role to manage services and processes effectively. This role is essential for adding or removing services in the Operational Resilience Workspace.
- Operational Resilience Reporting: Services can be added to reporting via the Operational Resilience Workspace, allowing users to view various metrics, including resilience metrics and red flags.
- Service Form Tabs: The Overview and Details tabs display resilience metrics and key attributes, respectively. Additional related lists can show child services, dependencies, issues, and risks associated with a service.
- Dependency and 360-Degree View: Users can access a dependency view and a 360-degree view of services to understand their relationships and performance across multiple pillars, such as Process and Technology.
Key Outcomes
By effectively setting up data for services, organizations can enhance their operational resilience. This includes improved risk management through visibility of red flags and dependencies, streamlined service management through role assignments, and comprehensive performance monitoring via the 360-degree view. Ultimately, this leads to better decision-making and resource allocation in maintaining service continuity.
Operational Resilience managers typically verify that data is set up for services or business services and monitor their resilience metrics on the dashboard. The Service (CMDB) Main node configuration fetches service-related data, while the Opres with CSDM header Main node configuration sets up the business services-related data.
Services and business services overview on the dashboard
Assigning the itil user role to the Operational Resilience administrators or managers
To add or remove services and processes in the Operational Resilience Workspace, you must have the sn_oper_res.manager and itil role or the sn_oper_res.admin and itil roles. In the CMDB, granting the itil role allows users to add or remove services and processes from the backend. However, the Operational Resilience Workspace application prevents users with the sn_oper_res.user role from making these changes in the Operational Resilience Workspace.
Adding a service to reporting
Overview and Details tabs in the Service form
On the Overview tab in the Service form, you can view the resilience metrics for a service as shown in the following example.
The Red flags section displays the total number of red flags, red flags by type, and details of the assets that are impacted by the red flags.
Child services, processes, and dependencies of a service
Reporting data for an object without a business service as the parent entity
When you have a business service or service as the parent entity, any red flags or dependencies roll up to that business service or service. Even if an object like a service offering (SO) or business process (BP) does not have a business service or service as the parent entity, running the scheduled job still fetches its dependencies and integrates them with the red flags.
For example, if a service offering SO4 does not have a business service or service as the parent entity but has a dependency, running the scheduled job fetches its dependency into Operational Resilience and integrates them with the red flags for reporting, as shown in the following examples.
Other related lists in the Service form
| Tab | Description | New action | Add action | Remove action |
|---|---|---|---|---|
| Child services | List of the child services for a service. To associate an existing child service with a service, select Add. To create a child service for the current service, select New. |
Form where you can add a child service. On this form, you can create a relationship between the child service and the current service. |
Table view where you can select multiple services that you can add as the child services of the current service. |
Form where you can remove a child service from the service. |
| Business processes | List of business processes that are associated with a service. | Not applicable | Table view where you can select multiple processes that you can add as the child services of the current service. | Form where you can remove a process from the service. |
| Dependencies | List of the dependencies that are associated with a service. | Not applicable | Table view where you can select multiple assets (entities) that you can add as the downstream entities of the current service. | Form where you can remove an asset from the service. |
| Issues | List of the issues that are associated with a service. Starting with the Washington DC, you can select Add to associate an existing issue with a service as shown in the following example. |
Form where you can create an issue for a service. | Form where you can add an existing issue to a service. | Not applicable |
| High risks | List of the high-risk items or the risk assessments in the monitor state that are associated with the service. | Not applicable | Not applicable | Not applicable |
| Failed controls | List of the failed or common controls where the status of the control is non-compliant and the reliant entity is the service. | Not applicable | Not applicable | Not applicable |
| Change requests | List of the change requests that are associated with a service. | Change Request form. When you submit the Change Request form, the application creates a record in the Services table. | Not applicable | Not applicable |
| Tasks | List of the tasks that are associated with a service. | List of the task tables, from where you can select the type of the task that you want to create. When you submit the form, the application creates a record in the Services with the Tasks table. | Not applicable | Not applicable |
| Incidents | List of the incidents that are associated with a service. | Incident form. When you submit the Incident form, it creates a record in the Services table. | Not applicable | Not applicable |
| Outages | List of the open outages that are associated with a service. | Outage form. When you submit the form, the application creates a record in the Services table. | Not applicable | Not applicable |
| Business continuity plans | List of the Business continuity plans that are associated with a service. | Not applicable | Not applicable | Not applicable |
| Vulnerabilities | List of vulnerabilities that are associated with a service. | Vulnerabilities for a service. | Not applicable | Not applicable |
| Importance and impact assessment | List of the approved Importance and impact assessments. | Not applicable | Not applicable | Not applicable |
| Scenario analysis | List of the approved Scenario analyses. | Not applicable | Not applicable | Not applicable |
| Operational vulnerabilities | Operational vulnerabilities associated with a service. | Not applicable | Not applicable | Not applicable |
Service added as an entity of Services (OR) type
When you add a service to the Operational Resilience reporting, the service is added as an entity of the Services (OR) type, as shown in the following example.
Open dependency view and 360-degree view for a service
On the 360° view tab, the Operational Resilience managers can monitor the 360-degree view of a service and measure its performance.
- Parent and child services
- Dependencies that are related to a pillar, such as the Process, Technology, People, Supplier, and Facility pillars in your organization
- Operational Resilience metrics