Create New Scenario analysis form

Use the Create New Scenario analysis form in Operational Resilience Workspace to add the details about the scenario analysis, milestones, assignees, and so on.

Create New Scenario analysis form

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

Table 1. Create New Scenario analysis form

Field	Description
Scenario analysis panel
Number	Number of the scenario analysis. When you create a scenario analysis, the application creates a scenario analysis and assigns it with a unique identification number. This field is auto-filled.
Name	Name of the scenario analysis.
Description	Description for the scenario analysis.
Goal	Specific goal that you want to achieve by performing the scenario analysis. For example, your goal might be to analyze the critical services for your business.
Milestones panel
Analysis start date	Date to start the scenario analysis. The owner of the analysis fills in the Analysis start date. A notification is sent to the participants to start their analysis on this date.
Assignees panel
Owner	Owner of the scenario analysis.
Plan approver	Approver of the scenario analysis plan.
Analysis approver	Approver of the scenario analysis.
Compose panel
Work notes	Work notes for the activities that are related to the record.
Additional comments (Customer visible)	More comments that can be shared with the customer.
Activity panel
Activity section	List of activities with the dates and times that are related to the scenario analysis.
Tabs associated with the scenario analysis
Scenario Events	Note: You must add at least one service, one scenario event, and one participant before proceeding with the scenario analysis. Scenario events that an analysis owner can associate with the analysis. As an owner, select Add to associate a scenario event with the analysis. When you add a scenario event to the analysis, the following details about the event are displayed on the form: Name. For example, Facility outage. Event group. For example, Infrastructure Events. Scenario. For example, Flooding Situation. Pillars. For example, Facilities, People, Suppliers, or Technology. Potential start date time. For example, the date and time when a user starts working on the event. Potential end date time. For example, the date and time when a user finishes working on the event. Duration. For example, the calculated duration of the event. Observations. For example, the observations about the scenario event. Gaps. For example, the gaps or missing information about the scenario event. Recommendations. For example, the recommendations about the scenario event. Status of the scenario event.
Services	Services that an analysis owner can associate with the analysis. As an owner, select Add to associate a service with the analysis. When you associate a service with the analysis, the following details about the service are displayed on the form: Name Owned by Importance Impact tolerance Disruption duration Breach status Deviation (%)
Participants	Participants that an analysis owner can add to the analysis. To add a new participant, you can select New on the form. When you add a participant to the analysis, the following details about the participant are displayed on the form: Name Role Instruction
Dependencies	Assets that are added to a scenario analysis. When you add an asset to the analysis, the following details about the asset are displayed on the form: Name of the asset Associated analysis scenario event
Responses	Response task that is associated with the scenario event. The following details are displayed on the Responses form: Number Participant State Short description Observation Gap Recommendation
Issues	Issues that are associated with the scenario analysis. The following details are displayed on the Issues form: Issue Number State Priority Assigned to Issue manager Scenario event
Summary
Number of services	Number of services that are associated with the scenario analysis.
Actual start date	Actual start date of the scenario analysis.
Actual end date	Actual end date of the scenario analysis. This field is auto-filled.
Actual duration	Actual duration of the scenario analysis. This field is auto-filled.
Number of services under impact tolerance	Number of services that are associated with the scenario analysis that are under the impact tolerance.
Number of services above impact tolerance	Number of services that are associated with the scenario analysis that are above the impact tolerance.
Number of scenarios	Number of scenarios that are associated with the analysis.
Number of scenarios completed	Number of completed scenarios that are associated with the analysis.
Number of events	Number of events that are associated with the analysis.
Number of events completed	Number of completed events that are associated with the analysis.
Disruption duration	Time duration between the end time of the last event and the start time of the first event.
Duration of events with overlaps	Summation of all event durations including the overlapping events and pauses.
Duration of events without overlaps	Summation of all event durations without the overlapping events and pauses.
Approvers	Approvers that are associated with the scenario analysis.