Situational Awareness UPDEA - Workshop

1
Situational Awareness UPDEA - Workshop
2
Awareness of the Situation

• 25,623 Alarms in 8 Hours
• 53 Alarms / min (average)
• 80 Are consequential

• Things to keep in mind during a disturbance -
• Analog data is not reported in time with the
  state data
• Controls are issued but the feedback is very slow
• Control staff are no longer aware of the
  situation.
• Communications protocol (IEC60870-5-101)
• SCADA data base design

3
State Alarming to Process Alarming

• Items to keep in mind that will cause a blackout
• The trip limit is 50 above the 90 degree limit.
• Dont have predictive analysis tools
• No Rate-of-change alarm processing.
• No consequential analysis warning
• No warnings of when it could trip.

27 / 160022
ARNOT SIMPL2 MVA HIGH 450 440
ALARM
4
Alarm Questions

• How much knowledge do Control Staff have of the
  situation?
• Address of a state change there is no context.
• No information - only data!
• Why 2 separate messages?Why not 1 message with
  all the event Information e.g.

27 / 153000 ARNOT_SIMPL1 - Trip - ARC - Trip,
- Main 1, Zone 1, White phase,
- Impedance Earth Fault - 35 km from
Arnot - Tripped 3 phase - Locked out
Permanent Fault - 320 MVA Loss at 402 kV -
DR indicates lightning strike on White phase
5
Electricity Production
Electricity production is a continuous process
but we do not monitor it as such.
6
SCADA Master data base
7
Monitoring Problems
Processes are never static - they are always
changing
Result We do not predict the future but we can
8
Hands up who recognise this.
9
Adding Situational Awareness
Monitor the Rate-of-Change of the Process
Variables.

1. Temperature
2. Megawatts
3. Megavars
4. Kilo Volts

• Add Consequential Analysis - (New)
• Combine PAS tool outputs
• Add predictive warnings to SCADA

10
Designing for a Disturbance (1)

• SCADA Master Philosophy
• Front Ends use the bay and station state to
  filter the alarms
• Messages are automatically suppressed based on
  bay state
• Event data from both ends of a line is combined

• Substation Philosophy
• Bays report their state to the station bay
  following a change
• The station state is a function of the bay and
  busbar states
• The station bay decides what is sent to the SCADA
  Master
• Update messages are sent to all bays on the same
  busbar
• A Dead Bus automatically sets the alarm
  suppression flag.
• 1 message is sent to the control staff for dead
  busses
• Include the protection, analog data and what
  happened

11
Summary

• Change the
• Substation data base to Object Oriented structure
• Master station data base to support Object
  Orientation
• Communications protocol to allow for
  containerisation
• Allow
• Ad hoc messages from RTU
• Dynamic alarm suppression at Master based on bay
  state
• Provide
• Situations Awareness identification areas using
  colour
• Consequential Analysis tool to SCADA tool box

12
Designing for a Disturbance (2)

• SCADA Substation philosophy
• Each status and analog values is reported
  individually to the SCADA master
• The physical bay structure is modelled in SCADA

13
SCADA Bay model

• Master Station Philosophy
• Each physical Bay is modelled in SCADA including
  the substation and region bays.
• All tele-metered state changes are defined as log
  only.
• No messages are sent directly to the control
  staff from the station.
• All incoming status and analog value are used to
  update the bay state only.
• The station state is a function of the bays and
  busbar states.
• The bays send messages to update the Station bay
  state.
• The station object updates the bay states based
  on the overall station state.

14
Designing for a Disturbance (3)

• Alarming
• The station bay sets flags that decides what
  alarm data is sent to the control staff by the
  bays. See example on next slide.
• The station bay generates and sends messages that
  are common to the station.
• For local bay events the bay generates and sends
  bay related messages
• For line events the alarm data is combined from
  both bays to create a single line alarm message
• A Dead Bus automatically sets the alarm
  suppression flag.
• All alarm messages include the protection, analog
  data and explain what happened

15
Primary versus Consequential
80 of alarms are consequential
Battery Charger
Alarm Log 13H14 Bay 1 DC Fail Alarm 13H14 Bay 2
DC Fail Alarm 13H14 Bay 3 DC Fail Alarm
Alarm Log 13h14 Battery DC output fail alarm
Bay 1
Bay 2
System Activity Log 13H14 Bay 1 DC Fail Alarm
13H14 Bay 2 DC Fail Alarm 13H14 Bay 3 DC Fail
Alarm
Bay 3
16
Summary

• Change the
• Substation data base to Object Oriented structure
• Master station data base to support Object
  Orientation
• Containerisation is performed at the Master
  Station
• Allow
• Bays to generate alarm messages
• All alarms are defined as log only at Master
• Provide
• Situations Awareness identification areas using
  colour
• Consequential Analysis tool to SCADA tool box

17
Situational Awareness
Problem identification Highlight problem areas in colour on the display
Sequential Analysis Indicate the cause and effect and number of possible incidents in a possible event
Rate of change Identify time to Trip
Contingency Analysis Identify consequences of Trfr 2 trip and reasons for tripping.
VSAT Identify local voltage changes and risks
Consequential Analysis Identify Time to Trip (Trfr 4) Identify size of Load loss and number of customers affected
18
Situational Awareness
Adding Situational Awareness

• Scenario
• Trfr 2 has reported an oil temperature high alarm
  note red line.
• Since we measure the actual temperature and can
  predict, based on the current, when the
  transformer will trip, i.e. how much time we
  have before it will trip.
• Contingency Analysis calculated how much load
  will be carried by transformer 4 if trfr 2 trips.
• Contingency Analysis also predicts that trfr4
  will also trip on overload.
• We can also predict how long it will take before
  trfr 4 trip based on the new load,
• With VSAT we can estimate the resulting voltage
  collapse risk if both transformers trip.
• We can also calculate the total load loss and the
  number of customers that will be affected.

19
2) Indicate the cause and effect and number of
possible incidents in a possible event
20
Questions