Transcript Changing SCADA Package

Enhancing the SCADA Package
With calculation and data exchange
Gerard Hoogenraad
Data management
[email protected]
CIM User Group, 13. May 2011
1
Agenda
1. Why enhance
2. Data exchange
3. Calculation
Gerard Hoogenraad, Enhancing SCADA Package 2011, CIM User Group
2
Why enhance the SCADA package
• Only receiving data and control is configurable
• Not possible to configure the main usage of a SCADA
system.
• Calculation of data points
• Sending a data point to one or more other partners (e.g.
neighbour RTOs/TSOs)
• Communication link parameters with protocol specifics
Gerard Hoogenraad, Enhancing SCADA Package 2011, CIM User Group
3
Main considerations
• As less changes to the existing SCADA package as
possible
• As less new classes as possible.
Gerard Hoogenraad, Enhancing SCADA Package 2011, CIM User Group
4
Interpretation change of RemotePoint
• Description now :
• For a RTU remote points correspond to telemetered values or
control outputs. Other units (e.g. control centers) usually also
contain calculated values.
• Description new :
• A remote point is a data point on a specific communication link
on the far side seen from the SCADA system. For a RTU remote
points correspond to telemetered values or control outputs. For
a partner connection it correspond to a value offered by or
offered to this partner.
Gerard Hoogenraad, Enhancing SCADA Package 2011, CIM User Group
5
New main classes for data exchange
• OfferedValue as subclass of RemotePoint :
• A MeasuredValue can be send to an other site. The
MeasuredValue can be send to multiple sites (partners) under
different names using different protocols.
• RemotePointAddress as subclass of IdentifiedObject :
• RemotePointAddress is a superclass for the detailed addressing
issues for all protocols and contains the link to the RemotePoint.
Also specific multiplication and/or offset parameters of a
protocol, e.g. an analog protocol, to convert the transmitted
value to a meaningful value.
Gerard Hoogenraad, Enhancing SCADA Package 2011, CIM User Group
6
New class overview for data exchange
Gerard Hoogenraad, Enhancing SCADA Package 2011, CIM User Group
7
Protocol specific settings / addressing
• For a protocol 3 subclasses have to be defined for :
• CommunicationLink
• settings to make the link work
• RemoteUnit (RTU / Client / Server)
• settings specific to a RTU / Gateway
• RemotePointAddress
• specific addressing in this protocol
• protocol conversion parameter like offset and multiplier
Gerard Hoogenraad, Enhancing SCADA Package 2011, CIM User Group
8
IEC 60870-6 Tase.2 example
Gerard Hoogenraad, Enhancing SCADA Package 2011, CIM User Group
9
What are we able to do now?
• For a SCADA system we are now able to define
following use case :
• receive a data point from a RTU using a IEC 101 protocol
• use it in the grid network model
• send this to the other grid operator using the IEC 104 protocol
• and send it also to my TSO using the TASE.2 protocol
Gerard Hoogenraad, Enhancing SCADA Package 2011, CIM User Group
10
Why put it in the standard
• If I give my model to my neighbour TSO/RSO he/she
not only becomes the network but also the addresses
under which he/she can receive the MeasurementValue
and configure the system(s) accordingly.
• Mapping of Equipment to MeasurementValue is there
and the receiver of the CIM Model does not have to
understand your network
• No more sending Scada pictures with addresses
written on them
Gerard Hoogenraad, Enhancing SCADA Package 2011, CIM User Group
11
Calculation
• In many cases we have to make calculations in order
to be able to use a MeasurementValue within a SCADA
system, e.g.
• inverse
• Multiplying with/out offset
• copy
• group alarming
• summation
• low voltage side measuring  high voltage side
• substitute value (rule in formula)
Gerard Hoogenraad, Enhancing SCADA Package 2011, CIM User Group
12
How to model calculation
• We need 3 new classes :
• CalculatedValue (subclass of MeasurementValue)
• this is where the result will go into
• and holds the formula
• CalculationInputValue (subclass of IdentifiedObject)
• matches variable names to MeasurementValues
• FixedMeasurementValue (subclass of MeasurementValue)
• fixed value, e.g. this way the same formula can be used multiple
times with different multipliers or offsets by connecting it using
CalculationInputValue
Gerard Hoogenraad, Enhancing SCADA Package 2011, CIM User Group
13
How to model calculation
Gerard Hoogenraad, Enhancing SCADA Package 2011, CIM User Group
14
How to model calculation
• To be able to map this to Measurement properly we
need to make 3 extra subclass of CalculatedValue and
FixedMeasurementValue subclasses :
• …AccumulatorValue
• …AnalogValue
• …DiscreteValue
• This in order to make a proper connection to
Measurement
Gerard Hoogenraad, Enhancing SCADA Package 2011, CIM User Group
15
How to model calculation
• Extra aggregations for :
• CalculatedValue to IdentifiedObject:
• Associate a CalculatedValue to a group e.g. a EnergyArea,
LoadGroup, GeographicalArea, SubGeographicalArea,
PowerCutZone, BranchGroup, ControlArea, SubControlArea,
ReportingGroup or ReportingSuperGroup.
Because there is no superclass like Area or Group for these, the
class the IdentifiedObject class is used.
• FixedMeasurementValue to PowerSystemResource :
• link a fixed value to equipment in the network
Gerard Hoogenraad, Enhancing SCADA Package 2011, CIM User Group
16
Use cases
• Group / Area calculations can be checked for
completeness in the formula
• All Measurements on a TieFlow must be linked to
CalculationInputValue of a specific CalculatedValue
• Check if Metering System uses the same summation as the
real-time system
• Usage of a MeasurementValue inside one or more
CalculatedValues can be monitored before deleting this
value.
• Substation automation can see if they can remove a datapoint
safely or have to find replacement (calculated?)
Gerard Hoogenraad, Enhancing SCADA Package 2011, CIM User Group
17
Enhancing the SCADA Package
• Thank you for your attention
• Any questions / remarks ?
• Please contact me at [email protected]
This document is the property of swissgrid ltd. and has been produced solely for information purposes. swissgrid ltd. reserves all rights. This document may only be copied or any
elements contained herein reproduced (in their entirety or in the form of extracts) with the prior written consent of swissgrid ltd.
swissgrid ltd. assumes no liability for errors in this document. swissgrid ltd. reserves the right to amend this document at any time without further notice. swissgrid ltd. shall not be
liable for the usage of this document for any purpose other than that for which it is intended.
The content of this document is correct at the time of publication.
Gerard Hoogenraad, Enhancing SCADA Package 2011, CIM User Group
18