IEC 61850 data modelling
The main idea of IEC 61850 is to breakdown a physical device in to logical devices each of which will
be further broken down into logical nodes, data objects and data attributes [1].
The Logical Device hosts communication access point of IEDs and related communication services
and is hosted by a single IED. However, there’s no rule on how to arrange Logical Devices into a
physical device which brings a great flexibility to the user.
Logical Nodes are the smallest entities which are derived from the application functions. Logical
nodes are the building blocks of the standard since they represents the smallest functions of the device.
The scope of this project is about microgrids control and asset management which is very different
from the scope of substation automation systems; therefore, many new functions must be modelled.
The next clause will describe how to model a new function as IEC 61850 Logical Nodes.
Figure 3.3 – IEC 61850 data modelling, copied from [1]
Figure 3.3 illustrates the principle of IEC 61850 data modelling. In this case, a physical device IEDx is
composed of a logical device LDx in which there are two different logical nodes XCBR and MMXU.
XCBR1 and MMXU1 are the two instances of the logical node class XCBR and MMXU which
represent the circuit breaker and the measurement unit respectively. 30 Each logical node is composed
of many data object. In this example, logical node XCBR1 contains the data object Pos which
represents the position of the circuit breaker. This data object consists of many data attribute among
which are StVal attribute for setting the position of the breaker to open or close, q attribute stands for
quality of the data and t stands for time of operating the function.
3.2.1 Extension rule for logical nodes
The rule for extension or definition of new logical nodes is defined in IEC 61850 part 7-1 [3]
Figure 3.4 – Basic extension rules diagram, copied from [3]
The rules modelled in Figure 3.4 can be briefly summarized as follow [3]:
If there is any Logical Nodes Class which fits the function to be modelled, an instance of this
logical node shall be used with all its mandatory data (M).
31
If there are dedicated versions of this function with the same basic data different instances of this
Logical Node Class shall be used.
If there are no Logical Nodes Classes which fit to the function to be modelled, a new logical node
shall be created according to the rules for new Logical Nodes.