The common understanding of information is crucial for the understanding of the related functions that produce, consume, and exchange the information. Information is always "bound" to functions ... no function - no information.
Let's have a look at this function:
Supervision of a temperature value ... report an alarm to a well known entity when the temperature change rate reaches a value of xyz ... this is the FUNCTION. Now we model it with IEC 61850:
The temperature supervision is modeled in the logical node MySTMP1. We use the data objects Tmp (reported every x minutes), RteAlm (reported when the value of the RteAlmSet is reached, e.g., 0.5 K/s).
This "function" is described in an SCL document ... here the MySTMP1 is bound to a topology (SSD), e.g., room temperature in building so-and-so, the reports are sent to the SCADA system mySCADA-client, ... the factory acceptance test can more or less be automated based on the SCL document.
The IEC 61850 STMP logical node model follows the temperature supervision function!!
The function was there well before IEC 61850 was born!
IEC 61850 standardizes the information shared with a real function.
The following diagram shows the basic modelling approach in IEC 61850:
- IEC 61850-7-2 defines the foundation
- IEC 61850-7-3 defines the common data classes: MV for measurements, SPS for single point status, and ASG for analogue sessings.
- IEC 61850-7-4 defines the logical node and data object classes.
More details will follow ... stay tuned.
The real challenge with IEC 61850 is: You likely get the feeling when you start reading hundreds of pages: unable to see the wood for the trees.
