Skip to content
Release: Australia · Updated: 2026-03-12 · Official documentation · View source

Create Scenario analysis form

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

Create Scenario analysis form

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

FieldDescription
Scenario analysis panel
NumberNumber 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.
NameName of the scenario analysis.
DescriptionDescription for the scenario analysis.
GoalSpecific 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 dateDate 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
OwnerOwner of the scenario analysis.
Plan approverApprover of the scenario analysis plan.
Analysis approverApprover of the scenario analysis.
Compose panel
Work notesWork 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 sectionList 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
DependenciesAssets 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
ResponsesResponse 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
IssuesIssues 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 servicesNumber of services that are associated with the scenario analysis.
Actual start dateActual start date of the scenario analysis.
Actual end dateActual end date of the scenario analysis. This field is auto-filled.
Actual durationActual duration of the scenario analysis. This field is auto-filled.
Number of services under impact toleranceNumber of services that are associated with the scenario analysis that are under the impact tolerance.
Number of services above impact toleranceNumber of services that are associated with the scenario analysis that are above the impact tolerance.
Number of scenariosNumber of scenarios that are associated with the analysis.
Number of scenarios completedNumber of completed scenarios that are associated with the analysis.
Number of eventsNumber of events that are associated with the analysis.
Number of events completedNumber of completed events that are associated with the analysis.
Disruption durationTime duration between the end time of the last event and the start time of the first event.
Duration of events with overlapsSummation of all event durations including the overlapping events and pauses.
Duration of events without overlapsSummation of all event durations without the overlapping events and pauses.
ApproversApprovers that are associated with the scenario analysis.