Scenarios

A scenario is a specific set of problems that occur in the simulation. The trainee is expected to go through the tools offered by the simulation to diagnose the problem, communicate the issues and their intentions to other involved professionals, and then fix the problem in a way that mitigates the issue safely and effectively.

Training scenarios are defined by a small collection of important fields, and a large collection of child objects that define how different actions are processed and scored for that specific scenario.

Flags

These are miscellaneous extra variables that can be set to change small details of how the training scenario functions. These are dependent on which simulator is being used.

Transmission Simulator flags

• ConsiderShedTime: Integer. After this many minutes pass in the training scenario, the trainee is expected to consider shedding load and may be directed to when communicating with others.
• Solution Targets: The generators the trainee is primarily expected to take actions on. This is an arbitrary distinction—any generator can be a solution target. If the trainee is expected to increase power in the north and not the south, for example, then the northern generators should be solution targets.

Child Objects

• Accomplishments: Milestones the trainee can reach by performing certain actions, which can affect how other objects are processed.
• Violations: Specifications of incorrect actions the trainee can perform.
• Questions: Training material presented in the After-Action Report based on violations triggered by the trainee.
• Communications: Message-response pairs the trainee sends to contacts who co-manage the grid. Can change as the scenario progresses.
• Coaching Steps: Sets of small hints given to the trainee upon request, based on how far they are through the scenario.
• Checks: Triggers that watch for when specific numerical values enter specific ranges.