Create New Service Instance form

Use the Create New Service Instance form in Operational Resilience Workspace to set up an application service and configure its related lists.

Create New Service Instance form

For a description of the field values, see the following table.

Table 1. Create New Service Instance form

Field	Description
Details tab
Name	Name of the application service.
Approval group	Approval group that is responsible for the approval of the application service, for example, Analytics setting managers or Application Security group.
Model ID	Model ID for the application service, for example, AT&T SoundPoint IP 560.
Support group	Support group for the application service, for example, App Engine Admins.
Owned by	Owner of the application service.
Change group	Change group that is responsible for updating the application service, for example, Application Development.
Business criticality	Criticality of the application service. The available options are as follows: 1—most critical 2—somewhat critical 3—less critical 4—not critical
Managed by	User that manages the application service.
Version	Version of the application service.
SLA	Service level agreements (SLAs) associated with the application service, for example, Finance 99.99.
Used for	Usage category that the application service is used for. For example, Staging. The available options for the usage category are as follows: Production Staging QA Test Development Demonstration Training Disaster recovery
Location	Location and the physical address for the application service.
Operational status	Operational status of the application service. The available options are as follows: Operational Non-Operational Repair in Progress DR Standby Ready Retired Pipeline Catalog
Vendor	Vendor that is responsible for operating the application service, for example, Acer or Adobe Systems.
Service classification	Classification of the service. The available options are as follows: Application Service Business Service Technology Management Service
Comments	Comments section for the application service. Typically, the Operational Resilience administrators add comments about the application service.

Table 2. Related tabs that are associated with the application service

Related tab	Description
General
Overview tab	Displays the following red flags data: Total red flags Red flags by type Issues Failed controls Risks Outages Incidents Change requests Operational vulnerabilities Vulnerabilities Third party risk assessments Assets impacted by red flags
Details tab	Details of the selected application service record.
Services and dependencies
Child services	Child services that are associated with the application service. The tab displays the following sample information about the child services: Dependency Pillar Impacted objects Red flags count
Business processes	Processes that are associated with the application service. The tab displays the following sample information about the business processes: Dependency Pillar Impacted objects Red flags count
Dependencies	Dependencies that are associated with the application service. The tab displays the following sample information about the dependencies: Dependency Pillar Impacted objects Red flags count
Ongoing events
Incidents	Incidents that are associated with the application service. The tab displays the following sample information about the incidents: Incident Short description Owner Opened Caller Priority State Category Assignment group Assigned to Updated Updated by Dependency Pillar
Outages	Outages that are associated with the current application service. You can create an outage for the service. The tab displays the following sample information about the outages: Number Outage Type Begin End Dependency Pillar
Red flags
Issues	Issues that are associated with the application service. The tab displays the following sample information about the issues: Issue Priority Status Planned end date Dependency Pillar
High risks	High risks that are associated with the application service. The tab displays the following sample information about the high risks: Risk Risk assessment Risk statement Risk response Inherent rating Computed inherent rating Residual rating Computed residual rating Dependency Pillar
Failed controls	Failed controls that are associated with the application service. The tab displays the following sample information about the failed controls: Control Control objective Status Dependency Pillar
Change requests	Change requests that are associated with a business service. The tab displays the following sample information about the change requests: Change request Short description Type State Planned start date Planned end date Assigned to Dependency Pillar
Tasks	Tasks that are associated with the application service. The tab displays the following sample information about the tasks: Task Short description State Task type Priority Assigned to Dependency Pillar
Vulnerabilities	Vulnerabilities associated with the application service. The tab displays the following sample information about the vulnerabilities: Vulnerability Dependency Pillar
Operational vulnerabilities	Operational vulnerabilities associated with the application service. The tab displays the following sample information about the operational vulnerabilities: Number Case Related area Related area table Title Related area type Domain
Third party risk assessments	Third party risk assessments associated with the application service. The tab displays the following sample information about the Third party risk assessments: Third party risk assessment Dependency Pillar
Program activities
Business continuity plans	List of the Business continuity plans that are associated with the application service. The tab displays the following sample information about the plans: Plan Plan asset Activated plan Event Event asset Dependency Pillar Status RTO RPO BIA date RTO gap
Importance and impact assessment	Importance and impact assessment that is done for the application service. The tab displays the following sample information about the assessment: Impact tolerance (Duration) Impact tolerance assessment Justification for overriding impact tolerance (Duration) Justification for overriding impact tolerance (Customer impact) Justification for overriding impact tolerance (Financial impact) Justification for overriding impact tolerance (Transaction Volume) Overridden importance Impact tolerance (Customer impact) Impact tolerance (Financial impact) Impact tolerance (Transaction Volume) Importance
Scenario analysis	Scenario analysis that is associated with the application service. The tab displays the following sample information about the scenario analysis: Breach status Disruption duration Impact tolerance Deviation (%) Importance Scenario analysis Service Created by Created Domain