Investigations of Different Function Allocations in SA Systems Enabled by IEC 61850
Investigations of Different Function Allocations in SA Systems Enabled by IEC 61850
The authors are with ABB Switzerland Ltd., Baden: Figure 1 – Common structure and function allocation in SA systems
klaus-peter.brand@ch.abb.com, wolfgang.wimmer@ch.abb.com
500 2
II. THE FREE ALLOCATION ACCORDING TO IEC 61850 their functionality. The station level is consisting of an HMI
IEC 61850 provides not only interoperability, but supports with work place functionality only and of a gateway to the
also the free allocation of LNs to physical devices to be NCC. The IEDs can be physically clustered as optimal
open for different design and operation philosophies of the needed from reliability or maintenance point of view. Also
utilities world-wide. Important for the future is that this this solution is supported by the powerful communication
approach opens the door for an assessment of given SA standardized by IEC 61850 providing the independence of
solutions and to ask for the optimized solution proofing the the data model and communication services from
existing traditional ones or claiming for new ones based on implementation. Any single IED failure refers only to one
the well known functions needed by the utilities in SA atom of functionality. The influence of a function atom
systems. This new degree of freedom enabled by IEC 61850 failure on the functions must be minimized by an
may result also in developments extending the functionality appropriate design (see Figure 3).
of the substations and SA system for the benefit of the
overall power system. It should be noted that any packaging
Station
HMI
of functions has an impact on the SW implementation and, Level
Gateway
Interlocking
Interlocking
Archiving Sequences Archiving
Sequences
III. BASIC EXAMPLES OF FUNCTION ALLOCATIONS Bay Protection Control Monitoring Protection Control Monitoring
Level
One extreme example is the allocation of all functions BBP BBP
commands and trips via remote outputs (actuators) at Sensor Actuator Sensor Actuator Sensor Actuator Sensor Actuator
process level again. There are no bay level and no dedicated Process
Level Bay Bay
IEDs for protection, control, monitoring and other functions
Switchgear
anymore. Since the necessary computation power was in the
past available in big computers only, such solutions had
been proposed at the very early beginning of substation Figure 3 – Toward a totally decentralized SA system (schematic)
automation. They may now see a revival because of the The most SA systems today have populated all three levels
powerful communication services standardized by with functions in multifunctional IEDs. At station level, the
IEC 61850. There is no discussion that such a centralized computer is not only providing an HMI, but also functions
computer has to be duplicated to avoid a very dangerous for the complete substation like event and alarm lists, an
single point of failure (see Figure 2). The loss of sensors archive for historical data and e.g. functions like a
and/or actuators is a problem left for the adaptability of sequencer supporting the local or remote operator. At bay
functions facilitated by the comprehensive data image in level, dedicated IEDs for functions like protection, control,
these centralized computers. The bay level control has to be and monitoring exist. With the use of a serial link (“process
connected also to these central computers, making it more bus”) according to IEC 61850 between the bay and process
vulnerable against cable faults in the system. level, also at process level IEDs with sensor or actuator
functions may be found (see Figure 1). Multiple measures
are taken to overcome single point failures and to increase
Sequences
Archiving
reliability. Therefore, the common solution with process bus
Station
HMI
Interlocking Station
Gateway
looks like an intermediate one mixing benefits and
Level BBP Computer
Protection drawbacks of both extreme ones. The paper tries to answer
Control
Station
Monitoring
the question for the optimal solution regarding the
Bus
functionality requested in the substation, and all related
Process
Bus criteria.
Bay
Level IV. EVALUATION CRITERIA
(about 20) PB
QB2XSWI1 Pos Pos
CU Central LN processing 20 PB
(all – e.g. 400 - LNs) QB9XSWI1
PB
Tab. 1 – Relative IED costs QC1XSWI1 Pos
PB
In Figure 4 the communication in a process bus (PB) type protection (Prot1) to the station level (LN IHMI1, LN
network between the central combined protection and ITCI1). If applicable the fuse failure from the voltage
control unit and the sensors and actuators for one bay with 2 transformer (LN BB1_TVTR1) is also reported. The trip of
instrument transformers and 7 switching devices is shown. protection is sent by GOOSE message to the control in the
The resulting load per such a sub-network is 8090 kBit/s or same bay e.g. for autoreclosure start. The positions of the
8009 msgs/s. The throughput limit given by the actual switchgear are exchanged between bays represented here by
version of IEC 61850 is 100 Mbit/s per line. Switches Ctl1 and Ctl2 with GOOSE messages for interlocking. Same
having also ports with 1 GBit/s are available and mostly happens for the positions from Ctl1 to Prot1. If applicable
used for backbone links. To avoid collisions on the Ethernet the voltage of the busbar VT (BB1_TVTR1) is send as SV
and support priorities as requested by IEC 61850, managed message to the bay controller (e.g. Ctl1) for the
switches have to be used which have a throughput in the synchrocheck function.
order of 200’000 msgs/s. Therefore, the calculated load for The resulting load per bay in such a sub-network including
one typical bay means that such a solution with centralized the voltage samples is 4038 kBit/s or 4011 Msgs/s. The
functions can handle around 10 bays per sub-network or main load comes from the busbar VT since the calculation
network segment related to a 100 MBit/s link to the central without this VT results in 36 kBit/s or 9 msgs/s.
IEDs, and around 20 bays related to the switch message This means, that if the bay level samples can be hidden from
throughput. Due to the needed high amount of input the interbay bus (IBB), at least 1000 bays can be served by
processing capacity, especially for samples (SV messages), the sub-network without distributed synchrocheck or,
such a group of 10-20 bays may need a separate sample pre- generally, without broadcasting samples of current and/or
processing unit within the centralized function unit. voltage. In this case, the real bottle neck is the throughput
2) Loss of sensors and actuators into the station level IEDs. If this would be 1000 msgs/s,
Regarding the effort for sensors and actuators and the around 200 bays are possible. The synchrocheck adds
communication load, in most cases (except complete around 4 MBit/s, i.e. 1 Busbar VT corresponds to the load
separation of main1 from main2 in HV protection) these of 100 bays without sampled analogue values (SAV). If we
components will not be duplicated. Therefore, the most stay with 100 bays resulting in maximum to loads of about
important drawback of such a solution is the impact of the 4 MB/s, roughly 20 VTs could be handled in addition. This
loss of a sensor or an actuator or of the related then relates either to a maximum of 20 bays or 20 bus bar
communication link. The MTTF of sensors and actuator segments depending where the busbar VT values are created
may be assumed to be at least 200 years, SA proof switches and how communicated. This means that in the
as far as needed have currently around 50 years. The 'conventional' architecture with BB VT values onto the IBB
centralized common data base of the complete substation around 20 HV bays could be handled. Also 20 bus bar
offer the basis to compensate some losses, but innovative segments with totally up to 100 bays seem to be a
new algorithms are needed to handle this problem. reasonable size, without technical problems. If for medium
voltage (MV) the sampling rate may be lower, this figures
B. The extremely decentralized case: Benefits and could be even higher. The critical factor then becomes the
drawbacks input processing capacity of the IEDs.
The overall functionality of the totally decentralized There is also a direct interaction between the bays including
solution as indicated in Figure 3 consisting of many the exchange of current samples for busbar protection,
functions or function groups is implemented by which is not considered above; for MV systems it is seldom
communication between many decentralized IEDs at bay used, for HV systems it is normally a separate network.
level, each hosting one LN. .
IHMI1 GOOSE SAV Buffered Unbuffered
PC
1) Load and Performance IBB
The assumptions about the messages generated are the same ITCI1
as above but the results are different by the different PC
IBB
topology. What is shown in Figure 4 as CentralProt and Tripevents Tripevents Prot1 Trip
CentralCntl now becomes a single function processor, e.g. Prot
IBB
for instantaneous overcurrent protection (PIOC), for
BinState BinState Pos Ctl1 Pos
synchrocheck (RSYN) or for switch control (CSWI), and is Measurents Measurents BC
multiplied up to one IED per LN needed for the function IBB
considered. These LNs add a few GOOSE messages for Measurents Measurents Pos Ctl2
BinState BinState BC
communication in between them, and some reports for IBB
supervision and operation purpose to and commands from FuFail FuFail Volt Volt BB1TVTR1
PI
station level. If we assume typical the implementation of IBB
20 LN instances of different LN classes for bay
functionality, this adds around 40 msgs/s resp. 40 kBit/s. Figure 5 – One conventional bay exchanging Interbay data
Report messages from a bay unit both to the IHM and NCC and receiving samples from busbar VT
gateway may assumed to contribute with a message size
same as the GOOSE messages, and sent once per second.
Figure 5 illustrates the load between the bays and to station
level. Commands are sent from the HMI (LN IHMI1) and
NCC gateway (LN ITCI1) at station level to the bay control
(Ctl1). Reports are sent from the bay control (Ctl1) and bay
500 5
2) Loss of single functions or function groups IED) needs careful configuration of the communication
This decentralized solution is very sensitive to the loss of a system to limit the data flow. The demand for processing
single LN involved in multiple functions, caused either by power is more on the communication side than on the
the loss of the allocated IED or of relevant communication functionality side. Therefore, this solution is not very cost
links. The station level consists of the HMI only. Therefore, effective. If we apply the estimation of Tab. 1 to system
a certain redundancy of functions as already common at HV sizes of 5, 10 and 20 bays each with 20 Logical Nodes, the
level as main1 and main2 protection or as back-up system hardware costs relate as follows (sensors and
protection may be requested in general. It is mainly needed actuators neglected because they are the same in all cases).
for single LNs acting as interface to the process or for
functions being commonly used by more than one other
function like autoreclosure (represented by RREC)and the Cost/Case Distribute Conventiona Centralized
trip conditioning matrix (represented by PTRP). For d l
communications redundant or duplicated systems may be 5 bays 100 10 40
necessary and useful [3]. 10 bays 200 20 40
20 bays 400 40 40
C. Today’s allocation: an optimal solution?
Tab. 2 – Cost comparison of systems
• Case 1: Station and process bus physically separated
The most common SA architecture shown in Figure 1 is The today’s bay oriented solution shows a reasonable
based on the allocation of functions to some more or less function allocation (some functions per IED), is best
dedicated IEDs. All IEDs have an interface to the process adaptable to system size, and costs are never higher than the
data of this bay, and a second interface to the station bus centralized solution. It allows the maximum system size
communication to the station level and between the bays. with reasonable reliability and reasonable communication
• Case 2:Common bus for station and process system engineering effort (see Tab. 3). Similar
communication
improvements in reliability as in the central case against loss
The bay level functionality is allocated to bay level IEDs
of sensors with relatively low costs may be possible by
which exchange data by one interface and one switch both
for process bus data and interbay and station data as having a central IED per busbar section and function group
described in [3] as solution in Figure 7. (Control, Protection) instead of per complete system. The
1) Load and Performance data flow between busbar sections and system level is
Case 1 separates station bus traffic from process bus traffic minimized and the functional redundancy can be used to
by architecture. The critical point to be solved is how some some degree. To exploit this solution the development of
process data needed in other bays can be brought to the some new distributed algorithms is needed. The relative
station bus side (e.g. voltages for Synchrocheck). positioning regarding cost may be influenced by future
Case 2 has not this problem, but the separation must be advances in technology and could be even lower than for
handled by careful configuration of the switches e.g. by the conventional solution.
VLANs. This separation assures that the very high amount
of about 200 bays can be handled. Case Distributed Conventiona Centralized
2) Loss of components l
If we loose one protection IED (e.g. main 1), there is at least Maximal 100 - 200 200 10-20
on transmission level a second protection (main 2) available. number
It should be noted that main1 and main 2 have some other of bays
purpose beyond redundancy (diversity in fault detection
Reliability Only single Loss of one Compensate
characteristics). The MTTF of control IED is mostly
function bay tolerated loss of one
sufficiently high, and the loss of one bay regarding control
is in most cases acceptable, especially if there is an concerned sensor;
emergency device directly at the switchgear. bay HMI
The loss of sensors and actuators leads to loss of the part of vulnerable
the functions. Critical are the sensors both for current Switch High Low to Low
(TCTR) and voltage (TVTR), and the circuit breaker configura- (VLAN medium
interface XCBR. The loss of the circuit breaker can be tion effort config..) (VLAN
handled for protection purpose by the breaker failure config.)
protection. Tab. 3 – Comparison of system parameters