This chapter introduces three main sections required for SIE to implement the switching actions
The items listed above will be discussed in detail in the later sections of this chapter, but before the setup
of the SIE is discussed in the following section.
Edit Mode
Load flow Mode
Switching Sequence Mode
This feature does not have a study case editor and only requires setup of the interlock page of any or all of
the following AC switching devices:
LVCB
HVCB
Recloser
Single Switch
Double Switch
Ground Switch
Contactor
The following syntax statements can be used into the SIE interlock page:
Boolean: AND, OR
Precedence: ( )
Inputs are the switching device status (open / close) and the multi-meter MW, MVAR, AMPS, VOLTS,
FREQ and Power Factor (PF).
This section gives examples on setting up the Pre-Switching and Post-Switching of the switching devices.
A high voltage circuit breaker (HVCB) switching device is used as an example.
Example 1
Logic: To Open circuit breaker “CB32” if circuit breakers CB3 has open status and LVCB1 has closed
status. The following image shows how the interlock logic is added into the interlock page of circuit
breaker “CB32”.
Example 2
Open circuit breaker “CB32” if Multi-Meter “MM32” reads a frequency which is not exactly the same as
60 Hz.
Example 3
Syntax Error example. There is a built-in syntax logic checker. If the proper syntax is not used when
entering the switching logic a message is displayed in the logic description window.
Example 4
Example of post action execution without post action requirements.
Logic: If circuit breaker “CB32” is successfully switched, then automatically trip “CB2”
Example 5
Post action execution with post action requirement.
Logic: If circuit breaker “CB32” is successfully closed (which it should since pre-switching action is only
dedicated to the Open function), then automatically trip “CB2” if and only if “CB4” is open.
If a conflict is detected, then the Switching Interlock View (SIV) window is launched with a list of all the
conflicts.
Each conflict must be settled. For example by changing the status of breakers or by de-activating the
interlock condition before dismissing the conflict alert.
If the conflicts are not resolved, then the SIE is turned off and interlock logic enforcement does not take
place.
In the example below, “CB29-9” is interlocked with “CB29-3” in a way such that “CB29-9” can only be
closed if “CB29-3” is open. However, “CB29-2” is closed.
Once the SIE is activated, the following alert view window appears
At this point, the only available options for the user are:
Double click on any field in the CB29-9 row under the Action column to launch the Interlock
page of the CB29-9 and revise the logic.
Click OK to deactivate SIE, revise the switching status of either CB29-3 or CB29-9, and then
reactivate SIE.
Click OK to deactivate SIE and Continue working on the project file without enforcement of the
Interlock logic
It is important to note that SIE will not continue to be active if there are any outstanding conflicts that are
not yet resolved.
When the user changes the status of the switching device, SIE will check to see if the interlock logic in
any Interlock page does not conflict with the switching status of another switching device in the system or
a meter reading (Interlocking with meter readings are only available in Load Flow mode).
Under this mode, simultaneous switching of status of multiple switching devices is not available to user.
The user will only be able to switch one switching device at a time either through the switching device
editors or through selecting the element and changing the Switching Device status through the Right
Click menu.
If a conflict is detected, then SIE will prevent the user’s switching action from taking place and the
Switching Interlock View (SIV) will launch instead informing the user of the issue.
As an example, in the image below, CB2 can only be opened if CB1 is opened. The current status of CB1
is closed.
As soon as the user tries to switch the status of CB2 to open, then the following interlock conflict appears
with the SIE feature already active.
If OK is selected, the SIE will turn off and the user has the option to modify the switching device status
or the Interlock logic.
If Cancel is selected, then the user’s action (Opening CB2) is ignored and SIE will remain active.
It is extremely important to note that the Interlock logic of CB2 will alert the user that CB2 cannot be
opened since CB1 is closed. However, the Interlock logic of CB2 will not give an alert to the user if the
user changes the switching status of CB1. Basically, CB1 must have its own interlock logic as well.
For example, using the previous example of CB1 and CB2, the user was able to successfully open CB2
since CB1 was open.
However, if the user violates the logic given in CB2 by closing CB1, as in the image below, then no alert
will given. In this case, the user is responsible to enter equivalent logic in the interlock page of CB1 to
prevent the user from unintentionally opening CB1.
Note: if the user deactivates then reactivates SIE, then the SIE will perform initial conflict check and the
error will be detected.
Note that in SSM mode, SIE will be disabled if either of the SSM Builder or Sequence view windows are
launched.
If a Post-switching action is triggered due to the last successful action, then a SIE alert window is
launched displaying for the user the available post switching actions with a checkbox next to them.
In the example below, CB2 can only be opened if CB1 is opened. However, Once CB2 is successfully
opened, then CB1 needs to be closed as well.
Once the action takes place, the following confirmation alert appears. If the check boxes are ticked, then
those actions will be executed; otherwise, the post action is disregarded.
If the subsequent post actions are generated due to the previous post actions, then the SIE alert window
will repeat launching continuously until the chain of post actions are all executed or until the user cancels
execution of post actions.
If the user cancels execution of post actions, then the subsequent post-switching actions are disregarded
and the previous post actions on the OLV have been reversed including the original action that caused the
chain of action triggers.
The following alert appears when initial system conflicts (Refer to Initial Conflict Check section) have
been detected.
1. Action-ID: The ID of the switching device (SD) that is the subject of the Pre-Switching conflict
2. Action-Type: Lists the type of the SD that is the subject of the Pre-Switching Alert.
3. Action-Bus: Lists the “From” bus that the switching device is connected to.
4. Action-Status/New Status: Lists the configuration status of the SD that is in conflict due to
another switching device or meter reading.
6. Conflict-Type: lists the type of the switching device SD that conflicts with Action-ID.
7. Conflict-Bus: Lists the “From” bus that the conflicting switching device is connected to.
8. Conflict-Status: lists the existing configuration status of the interlocking SD which conflicts with
the pre-interlock logic of Action-ID. The user will have to double click on the row to open the
interlock page of Action-ID for further investigation.
The following alert appears when pre-switching conflict (refer to Pre-Switching Conflict Check section)
has been detected.
1. Action-ID: The ID of the switching device (SD) that is the subject of the Pre-Switching conflict
2. Action-Type: Lists the type of the SD that is the subject of the Pre-Switching Alert.
3. Action-Bus: Lists the “From” bus that the switching device is connected to.
4. Action-/New Status: Lists the configuration status of the SD that is in conflict due to another
switching device or meter reading.
6. Conflict-Type: lists the type of the switching device SD that conflicts with Action-ID.
7. Conflict-Bus: Lists the “From” bus that the conflicting switching device is connected to.
Conflict-Status: lists the existing configuration status of the interlocking SD which conflicts with the pre-
interlock logic of Action-ID. The user will have to double click on the row to open the interlock page
The following alert appears when post-switching action (refer to Post Switching Conflict Check and
Execution section) is awaiting confirmation for execution.
1. Current Action-ID: The ID of the switching device (SD) that is triggering the post action.
2. Current Action-Type: Lists the type of the SD that is triggering the post action.
3. Current Action-Bus: Lists the “From” bus that is triggering the post action.
4. Current Action- Status: Lists the configuration status of the SD that is triggering the post action.
5. Post Action-ID: lists the ID of the SD that is being triggered by the post action.
6. Post Action -Type: lists the type of the switching device SD that is being triggered by the post
action.
7. Post Action -Bus: Lists the “From” bus that is being triggered by the post action.
8. Post Action –Current Status: lists the existing configuration status of the interlocking SD that is
being triggered by the post action.
9. Post Action –New Status: lists the existing configuration status of the interlocking SD that is
being triggered by the post action.
10. Post Action –Execute?: When checked, this is a confirmation by the user, that the post action can
take place and therefore will modify the system configuration and possibly the study (e.g. Load
Flow) results.
LVCB, HVCB, Recloser, Single Switch, Double Switch, Contactor, Ground Switch
Action
Device Type (Switching or Metering)
ID/Tag
Logic Operator (=, !=, AND, OR, (, ) )
Multi-Meter
Connected Current Transformer ratio
Connected Potential Transformer ratio
Voltmeter
Connected Potential Transformer ratio
Ammeter
Connected Current Transformer ratio
A switching sequence can be created and modified from the Switching Sequence Editor. This interface
allows the user to build a sequence of actions using devices and/or instructional procedures. The sequence
can be set in any order and organized into different groups. During the simulations, the automatic
interlock built-in among the switching devices will also be simulated.
The Switching Sequence Toolbar will appear on the screen when the user is in the Switching Sequence
Study Mode.
After running a switching sequence, the user can click on this button to open the Alert View, which lists
all equipment with Load Flow critical and marginal violations based on the settings in the Study Case.
simulations. To view any of the listed Output Reports, click on the “Output Report Name”, and then click
on the “View Output Report” button.
As a part of the multi-dimensional database concept of ETAP, Study Cases can be used for any
combination of the three major system toolbar components, i.e., for any configuration status, one-line
diagram presentation, and Base/Revision data.
When the user is in SSM Mode, they can access the Switching Sequence Study Case Editor by clicking
on the “Study Case” button from the SSM Study Case Toolbar. The user can also access this editor from
the System Manager by clicking on the “Switching Sequence Study Case” folder.
There are two ways the user can create a new Study Case. They can click on the “New Study Case”
button in the Study Case Toolbar, as shown above. It will open the Duplicate Study Case dialog box for
them to specify names of an existing Study Case and the new Study Case they want to create.
The user can also create a new Study Case from the System Manager, by right-clicking on the “Switching
Sequence Study Case” folder and selecting “Create New”, as shown below. ETAP will then create a new
Study Case, which is a copy of the default Study Case, and adds it to the Switching Sequence Study Case
folder.
To get started with the builder, click the Edit Switching Sequence button (the left button in the picture
above) and the switching Sequence Editor – Builder mode will be launched.
Switch Sequence
Sequence ID
From this edit field, the user can enter or modify the ID of the sequence.
Action #
The “Action Number” field is display only and the number is automatically assigned. The number will be
reassigned whenever there is a change in the sequence order or in Delay Time, including,
Clicking on one of the following buttons: Up, Down, Split Group, Insert, Add, and Delete.
Change of group number by editing the field.
Change of Delay Time for an action.
Note that when the Action Number is reassigned after one of the changed listed above; the sequence list
will not be resorted automatically and must be manually sorted by clicking on the column header.
Group #
This is an editable field indicating the group number of the actions. During simulation, all actions in the
same group will be processed together in parallel.
Active
If the checkbox is checked, the action is considered active. Only active actions will be included in the
Sequence View window to be simulated.
Device Type
This is a list of device types. Options include:
Protective Device: LV CB, HV CB, Switch, DT Switch, Contactor, Recloser, and Ground Switch.
Procedure: This is a plain text entry added by the user. A new one can be added to the System
Manager window by browsing for it under the Switching branch under the configuration branch.
Device ID
Depending on the selection in the “Type” field, this field lists the device IDs, or procedure IDs.
Delay T (HH:MM:SS)
The delay time for a device is entered in the format of Hour:Minutes:Second:Millisecond. This is an
intentional time spent between sending command to take an action and the actual execution of an action.
This, for instance, can represent the actual time taken by a crew to safely rack a breaker once the work
order has been received.
Action
This is a list for action types. For Double Throw Switch, the options include “Pos. A” and “Pos. B”, for
the Ground Switch, the options include “Ground” and “Open”, and for all other protective devices, the
options include “Open” and “Close”.
Crew
This is a text field of up to 25 characters which can represent the crew that is performing the switching
action.
Remarks
This is a text field of up to 25 characters which can serve as reminders of why this action was taken.
Cost
This is a currency field displayed in the column in U.S ($) dollars. Note that the project’s local currency
can be entered without the need to convert to dollars.
Name
This field logs the name of the ETAP user who last modified this action line. The field is display only.
Date
The “Date” field is display only. It displays the date the action line was modified.
Time
The modification time for an action line is in the format of Hour:Minutes:Second. This is the time the
action line is modified and the field is display only.
Edit
Up
Clicking on this button will move the currently highlighted action up by a row. If the action is the highest
ranking order in a group, then the Up button will move the action to the bottom of the higher ranking
group.
Down
Clicking on this button will move the currently highlighted action down by a row. If the action is the
lowest ranking order in a group, then the Down button will move the action to the top of the lower
ranking group.
Split Group
Clicking on this button will make the currently highlighted action to solely take over the group number.
The rest of the actions will form their own group with a lower ranking number.
Insert
Clicking on this button will insert a new action before the currently selected action. If the action is
surrounded by other actions in a group, then this action will be inserted before the currently selected
action and below the higher ranking action.
Add
Clicking on this button will add a new action to the bottom of the list with a new group number.
Delete
Clicking on this button will delete the selected action from the list. Note that if this action was the only
action number in the group, the action along with the group number will be deleted. The group number
can be manually re-entered by modifying an existing or a newly assigned group number.
Logic Editor
Clicking on this button opens up the Interlock page associated with the device type selected in the Type
column. The user can add/modify the Interlock logic from the launched editor. This button is enabled
only when the highlighted action line is associated with a Switching device and will not highlight when a
procedure is selected.
For more information about the Interlock feature, read the Interlock sections associated with the devices
that include an Interlock page in Chapter 11.
Zone
Enable device filtering in the Sequence for the “ID” field of the elements that are connected to terminal
busses belonging to a selected zone in the One Line View.
Zone Number
The user can type or select the Zone number. When a number for a Zone is displayed, if the Zone has
been defined in the project, the name of Zone will be displayed in the field next to the number. If the
Zone has not been defined, the field will show as blank.
Zone Name
The user can select a Zone from the “Name” field. The list will contain all Zones defined in the project.
When the name for a Zone is selected, the “Number” field shall display the number for the Zone.
Area
Enable device filtering in the Sequence for the “ID” field of the elements that are connected to terminal
busses belonging to a selected Area in the One Line View.
Area Number
The user can type or select the Area number. When a number for an Area is displayed, if the Area has
been defined in the project, the name of Area will be displayed in the field next to the number. If the Area
has not been defined, the field will show as blank.
Area Name
The user can select an Area from the “Name” field. The list will contain all Areas defined in the project.
When the name for an Area is selected, the “Number” field shall display the number for the Area.
Region
Enable device filtering in the Sequence for the “ID” field of the elements that are connected to terminal
busses belonging to a selected Region in the One Line View.
Region Number
The user can type or select the Region number. When a number for a Region is displayed, if the Region
has been defined in the project, the name of Region will be displayed in the field next to the number. If
the Region has not been defined, the field will show as blank.
Region Name
The user can select a Region from the “Name” field. The list will contain all Regions defined in the
project. When the name for a Region is selected, the “Number” field will display the number for the
Region.
A user can add switching device actions to the switching sequence by either adding them using the
buttons (e.g. Add, insert, etc.) in the builder or by clicking on them on the One Line View while the
Builder editor is open.
If the user chooses to add the switching actions from the One Line View, then the following two options
are available to the user.
Execute / UnExecute
This button, when clicked on an unexecuted action, will execute (change the switching device status) all
the unexecuted action from the top of the list to the selected unexecuted action. When clicked on an
executed action, it will un-execute all executed actions form the bottom of the list to the selected executed
action.
In addition to adding a switching action from the Switching Sequence Editor - Builder Editor, an action
can also be added from one-line diagram through a two way interaction between the One Line View and
the Auto-Builder Editor as described in the previous section.
Left mouse-click and control-click can be used to specify actions as the actions are simulated on the
ETAP One Line View.
The Switching Device status on the One Line View will mimic the status before the Builder editor was
launched. Once the builder is launched, a temporary configuration will be used for the Builder and it will
return to the selected configuration once the Builder editor is closed.
Green annotations on the One Line View will also appear next to the Switching Devices representing
future switching action to be taken.
Magenta annotations will appear next to the Switching Devices representing switching actions.
When in the Builder Mode, the user may change the settings of a unexecuted action but not the executed
ones.
The next sections describe the methods of adding and executing actions using the mouse buttons on the
One Line View while the Builder editor is open.
Left-Click on a PD
When a PD is left clicked, a switching action is inserted on its behalf in the Builder editor. ETAP then
executes this action by changing the PD status on the One Line View as well as the Builder editor.
If there are no executed actions, the newly inserted action will take the group number of the first group
and take an action number that is dependent on the delay times of the other actions in the same group.
Sequence Selection
When ETAP is switched to SSM mode, the default or previously selected Sequence is available. There
could be multiple previously created sequences and the user can choose any of them for simulation
purposes.
Configuration Selection
When ETAP is switched to SSM Mode, the user can change the configuration the same way as in any
other mode.
When the “Run Switching Sequence” button is clicked on, the Sequence View window opens up and
ETAP creates a temporary configuration and uses it for simulation. During simulation, it displays the
results within the temporary configuration. When in the Run Mode, any changes in the permanent
configuration One Line View is disabled.
When the Sequence Simulation View is closed, the presentation returns to the selected configuration.
Action #
The “Action Number” field is automatically assigned and the Action # is carried over from the Sequence
Builder Editor.
Group #
The “Group Number” field is automatically assigned and the Group # is carried over from the Sequence
Builder Editor.
Command Time
This column displays the starting time of each action. The starting time for an action is the end time of
last action (group) plus the delay time of this action. Note that the first action starts at 0:0:0.00 plus the
initial action’s delay open/closing delay time. For example, if the switching device is a 5 Cycle HVCB on
a 50 Hz system, then the command time will be incremented by 0.1 seconds such as 0:0:0.100.
Action Status
The Action status shows the status of each action. The possible status includes Completed, skipped, Not
Required, and Next. The future actions will have the field shown as blank.
ID
Depending on the selection in the “Type” field, this field is a list of device IDs, or procedure IDs.
Type
This is a list of device types such as LVCB, HVCB, Switch, DT Switch, Contactor, Recloser, and Ground
Switching Procedures can also be added.
Original Status
This field displays the original status of the device as in the selected configuration before a switching
action takes place.
Action
This field displays the switching action type. This field is carried over from the Sequence
Editor/Sequence Builder Mode.
Current Status
This field displays the current switching status of the device, which changes as the simulation progresses.
Duration
Duration is the time used to execute an action. It is the difference between the End Time and the
Command Time.
End Time
This column displays the ending time of each action. For simulation, it is the command time plus the PD
operation time.
Crew
This field is the same as the corresponding field in the Sequence Builder/Editor.
Remarks
This field is the same as the corresponding field in the Sequence Builder/Editor.
Cost
This field is the same as the corresponding field in the Sequence Builder/Editor.
Execution Control
Auto Start
Clicking on this button will simulate the whole sequence. Once the Auto-Simulation is started, the button
changes to “Auto Exec”.
Once the simulation starts, different colors will apply on different actions to indicate status of actions
according to the display options.
Also note that if a Critical Alert is raised, such as when exposing the system to a grounded switch or any
other alert, simulation will halt and will not advance to the next action, just like the figure below.
If the “Skip Alert Evaulation (Load Flow)” check box is checked, the sequence will be automatically
executed without regard to the load flow alerts raised.
For the “Overide Pre-Switching Condition Logic” and “Override Pre-switching Operational Logic” check
boxes, the sequence will be automatically executed without regard to the Pre-Switching Interlock logic
defined in the switching device’s interlock page.
Run an initial Load Flow based on the initial system’s Switching Device configuration . System
Load Flow Alerts should be displayed at the bottom of the window.
Check Pre-Logic Conditions for Next Action – by checking all pre-logic conditions for the next
action to see if all the interlocking conditions are satisfied. If not, an alert will be posted for any
failed conditions and the action will be skipped.
Implement the first Action– by executing the switching actions on the One Line View and inside
the editors. Interlock Logic alerts can be seen at the bottom of the window.
Run Load Flow – If the Skip Operating Evaluation checkbox is not checked, it will run Load
Flow for each switching in this action. It will check the Load Flow alerts according to the
selected study case options. If there are any abnormal conditions, an alert will be raised.
Determine Post Actions – It will determine post actions based on the logic defined in the
Interlock Logic Editor for switching devices. All post actions generated will be inserted in the
sequence list.
Note that if an action causes a ground switch to be directly grounding a live portion of the system,
simulation will halt and will not advance to the next action, and an alert will be raised as shown in the
figure below.
Also note that during step-simulation, the “Auto-Exec” button will be enabled, allowing the user to switch
to auto-simulation at any stage.
Restart
Clicking on this button will abort the current simulation. The Sequence List and the Alert List will appear
as if it is just opened.
When this box is checked, at the end of the simulation, ETAP will save the temporary configuration with
the final switching sequence using the name selected.
Alert
Action #
This field displays the action number shown in the Sequence Editor. Notice that blank actions are related
to initial Load Flow simulation before the first switching sequence was executed.
Command Time
This field displays the action Command Time shown in the Sequence List section at the top of the
Sequence View window.
ID
This field is the same as the corresponding field in the Sequence List section of the Sequence View.
Type
This field is the same as the corresponding field in the Sequence List section of the Sequence View.
Status
This field is the same as the corresponding field in the Sequence List section of the Sequence View.
Action
This field is the same as the corresponding field in the Sequence List section of the Sequence View.
Alert Type
This field displays one of four types: Invalid Action/Initial State, Logic, Critical, and Marginal.
Alert Condition
Alert conditions include Over Loading, Over Voltage, Under-Voltage, Over-Excitation, Under-Excitation,
Existing Status, Interlock Logic, and Invalid Action.
Over/Under Voltage: SSM Load Flow detected and Over Voltage condition at the listed bus.
Over/Under Excited: SSM Load Flow detected an excitation issue with the listed generator.
Existing Status: SSM detected that the action specified for switching action is redundant due to the action
already having the same switching status (e.g. Opening an already open breaker).
Interlock Logic: SSM detected that the action specified for switching action cannot taken due to its Pre-
switching Logic not meeting the stated requirement.
Invalid Action: SSM detected that the action that was about to be taken will cause a live portion of the
system to be connected directly to ground.
Device ID
This field is the same as the corresponding field in the Sequence List section of the Sequence View.
Device Type
This field is the same as the corresponding field in the Sequence List section of the Sequence View.
Required
This field shows the required condition, including device status, voltage values, and loading values.
Actual
This field shows the actual values related to the required condition.
Device Type
Device ID
Delay Time
Action
Active status
Group # that the device belongs to
Action# based on the sequence needed
Bus Data
Required data for SSM Load Flow calculations for buses includes:
Nominal kV
%V and Angle (when Initial Condition is set to Bus Initial Voltages)
Load Diversity Factor (when the Loading option is set to use load diversity factor)
Branch Data
Branch data is entered into the Branch Editors, i.e., Transformer, Transmission Line, Cable, Reactor, and
Impedance Editors. Required data for Load Flow calculations for branches includes:
Note: The Mvar limits (Qmax and Qmin) can also be calculated from the capability curve. The required
additional data for this calculation includes
Inverter Data
Required data for SSM Load Flow calculations for inverters includes:
Inverter ID
DC and AC rating data
AC output voltage regulating data
Static Load ID
Rated kVA/MVA and kV
Power factor
% Loading for desired Loading Category
Equipment cable data
Capacitor Data
Required data for SSM Load Flow calculations for capacitors includes:
Capacitor ID
Rated kV, kvar/bank, and number of banks
% Loading for desired Loading Category
Equipment cable data
Conventional
Load ID
Rated kV, kVA/MVA, power factor, and % motor load
% Loading for desired Loading Category
Unbalanced
Load ID
Rated kV, kVA/MVA, power factor, % motor load, and % static load
% Loading for desired Loading Category
Exponential
Load ID
Rated kV, P0, Q0, a, and b
% Loading for desired Loading Category
Polynomial
Load ID
Rated kV, P0, Q0, p1, p2, q1, and q2
% Loading for desired Loading Category
Comprehensive
Load ID
Rated kV, P0, Q0, a1, a2, b1, b2, p1, p2, p3, p4, q1, q2, q3, and q4
% Loading for desired Loading Category
HV DC Link Data
Required data for SSM Load Flow calculations for HV DC links includes:
Element ID
All data on the Rating page is required for Load Flow calculations
Inverter current margin (Im)
SVC Data
Required data for SSM Load Flow calculations for SVC’s includes:
Element ID
Rated kV
Inductive Rating (Either QL, IL, or BL)
Capacitive Rating (Either QC, IC, or BC)
Max Inductive Rating (Either QL(Max), or IL(Max))
Max Capacitive Rating (Either QC(Min), or IC(Min))
Other Data
There are some SSM Study Case related data, which must also be provided. This includes:
Max Iteration
Precision
Loading Category
Initial Voltage Condition
Report Format
The SSM Mode offers the user an Output Report as a complete document in MS Excel format.
General
Builder
Sequence
Alerts
General
The General page is the title page which displays all the basic information about the report.
Builder
The Builder page corresponds to the SSM Sequence Editor/Builder window.
Sequence
The Sequence page corresponds to the Sequence List section at the top of the Sequence View window.
Alert
The Alert page is equivalent to the Alert section at the bottom of the Sequence window with the “Show
All Alerts” checkbox enabled.
Contingency Analysis
Contingency analysis represents an important tool to study the effect of elements outages in power system
security during operation and planning. It investigates, evaluates, filters and prioritizes the impacts on an
electric power system whenever typically unplanned problems or outages occur.
The ETAP Contingency Analysis module allows users to evaluate the impact of N-1 and N-2
contingencies, determine system performance indices, and compare results against safe operating limits
for each element in the power system based on user-defined component outage and failure scenarios. For
accurate results, AC load flow is run for each contingency. The ETAP user friendly interface allows
running base and contingency load flows to see the outage effects on OLV.