See Also
The What Occurred information with contingency analysis results provides details of the actions associated with each contingency and those that were applied or skipped. Additional information about the status of devices, i.e. line flows before a line is open or generation level changes, is also supplied. The What Occurred information can be accessed from several places.
- To view a list of what occurred for a single contingency, a tab is available next to the Contingency Violations Display tab when selecting a single contingency from the Contingency Records Display
- To view a list of what occurred for a single contingency, click on the What Occurred option from the local menu of the Contingency Records Display
- To view a list of what occurred for a single contingency, click on the What Occurred option from the local menu of the Contingency Violation List table found on the Contingency Results tab
- To view a list of what occurred for all contingencies, the Contingency Results tab contains the What Occurred table
Each row of the table represents a contingency element action with the details of what occurred. An example of the table format is shown below:
Field Descriptions
The fields that appear in either the text or table format of What Occurred have the following meaning:
Contingency
Name of the contingency to which this element belongs.
Applied or Skipped
Applied actions are those that are implemented during the contingency. Skipped actions result because the Model Criteria specified with the contingency is not met. Only actions that belong to the contingency itself will be reported as skipped. Remedial Actions, Global Actions, and Transient Actions will not be reported as skipped because there could be a large number of these defined that are routinely skipped.
Actions
Contingency element action as provided with the contingency element definition. The format of the actions can be changed by changing the Contingency Action Description in What Occurred found with the Miscellaneous options. This option must be set BEFORE the analysis is run for the changes to take effect.
Model Criteria
Contingency element Model Criteria as defined with the contingency element definition.
Status
Contingency element Status as defined with the contingency element definition.
Comment
Contingency element Comment as defined with the contingency element definition.
Brief What Occurred
This provides details of what happened when applying this contingency element action. This will show details such as how much flow was on a line when it was opened, how much generation changed, how much load changed, etc.
When using the Open Breakers or Close Breakers contingency actions for a device, this field will indicate which breakers operated to isolate or close a device. Additional action records will be added for each breaker that operated.
Origin of Action
Each contingency can be comprised of elements from the base contingency record, contingency blocks, global actions, remedial actions, and transient actions. This field provides details of where the element is defined. This is useful when tracking the implementation of special protection schemes (SPS) or remedial action schemes (RAS) that might be defined outside of the contingency definition.
The elements that are included within the implementation of a contingency can come from several sources:
ELEMENT - element is defined with the base contingency record
BLOCK - element is defined with a Contingency Block that is part of the base contingency record
GLOBAL - element is defined with the Global Actions
REMEDIAL - element is defined with the Remedial Actions
TRANSIENT - element is defined as one of the Transient Models that acted
Open Breakers and Close Breakers contingency actions will dynamically determine the breakers that need to operate. These actions will appear in the what occurred list as Open or Close actions on the actual breakers. To indicate that these actions were dynamically created and not defined explicitly with the contingency or remedial action, the keyword DYNAMIC will be appended to the source keyword for the action.
Remedial Action
Name of the remedial action to which the action belongs if the Origin of Action is REMEDIAL; otherwise, this field will be blank.
What Occurred
This is a repeat of the entirety of what occurred in the Text Format.
Time Delay
This is the time delay that was used when the action was applied. Time delays can come from several different sources as described in the treatment of time delays topic.
Group Order
This is an integer value that specifies the group in which the action was applied. The contingency process has different steps that are determined by the Status of an action, i.e. CHECK, TOPOLOGYCHECK, POSTCHECK, etc. These different steps of the process define a new group. Any Solve Power Flow contingency actions will also define a new group. This value helps determine the overall order in which actions were applied.
Group Status
Status that defines the step in the contingency process in which the action was applied, i.e. CHECK, TOPOLOGYCHECK, POSTCHECK, etc.
Subgroup Order
This is an integer value that specifies the order in which an action with applied within its Group. Sorting the what occurred results by Group Order and then Subgroup Order will give the overall order in which actions were applied.