GER-3976

Inter and Intra Substation Communications:

Requirements and Solutions
 Inter and Intra Substation Communications:
Requirements and Solutions
by
Mark Adamiak Ron Patterson Jerry Melcher

GE Protection & Control EPRI

Malvern, PA Palo Alto, CA

Abstract rates, have more data to communicate, and are capable of

As the substation communication world searches for the performing some programmable logic functions.
“Promised LAN”, it would be helpful to have a roadmap
to give direction to the search. Many are the expectations In view of future capabilities and a continuing
of a LAN flowing with data and able to connect with any proliferation of IED’s in the substation, a cry has come
Intelligent Electronic Device (IED) that was ever made. from the utility community to create a framework for not
Such expectations must be tempered with the cost and only common communication but an architecture that will
complexity of achieving them. This paper presents an provide for interoperation. Interoperation implies the
outline of the communication requirements of the myriad ability to “plug and play” and also to be able to “share”
of IED’s in existence in the substation today as well as the data and functions. As an example, a protective relay
expectations of what second generation microprocessor may be required to provide a “check synchronism”
based devices might be able to do. Requirements will function which requires the magnitude and phase angle
focus on language issues, system capabilities, comparison of two voltages. The relay performing the
performance requirements, external interfaces, function may have intrinsic access to only one voltage.
environmental, and quality issues. Some attention will The other voltage may be available from another device in
also be given to the architecture of a solution and some the substation . An interoperable system could then
guidelines as to how this structure might be built. negotiate for access to the other voltage and as such,
avoid all the overhead involved in direct wiring.
Introduction
From the introduction of processor based devices, we have Integration Benefits
had the ability to communicate with these devices. The As substation integration becomes a reality, there are
ability to communicate gives added value to the IED and numerous benefits that can be realized. With data
as such, has hastened their implementation. As time has sharing, wiring between devices can now be minimized.
gone on, we have watched communities of these devices Distributed data acquisition now becomes the foundation
sprout up in the substation - typically with no concerted of substation integration. Traditional hardware devices
attempt to inter-communicate much less interoperate. As such as the Remote Terminal Unit and the Digital Fault
a result, a veritable “Tower of Babble” has arisen inside Recorder now become primarily functional entities that
the substation. Attempts to date to achieve some draw on other IED’s for their data. Interoperation
semblance of common communication have focused permits distributed functionality, that is, the data and/or
around “Rosetta Stone” solutions whereby a translation the decisions needed for a particular function may reside
module of software is located between the IED and host among multiple IEDs.
computer. Although this technique achieves today’s
goals, translation hardware is usually required and Such changes in the substation design paradigm can be
creation of the translation module can be costly and time measured both quantitatively as well as qualitatively.
consuming. Another aspect is that revisions and Quantitatively speaking, substation integration has the
generations of new IED’s have become a frequent potential for the following savings [1]:
occurrence demanding constant “stone cutting” and • Elimination of the station fault recorder & wiring
“chipping” of translation communication software. • Elimination of the station Sequence of Events
Newer IED designs implement faster communication recorder & wiring
• Minimization of RTU wiring
• Minimization of Breaker Wiring and verbs in the same language and can turn to a
dictionary to describe the words we do not understand.
Qualitatively, the integrated system brings with it:
• Reduced O&M through “Real Time” condition The requirements definition process mandated some
monitoring technique whereby the various information items and
• 100% redundancy in fault recording functions of the IED’s could be described and where that
• Rapid fault location description could be shared by all. A device description
• Integrated Protection & Control technique known as Object Oriented Methodology
(OOM) has been adopted as a fundamental requirement
and many others. in the overall design process. OOM provides a tool
whereby the “nouns” and “verbs” that describe an IED
Requirements Document Creation and its functions can be created or “abstracted”. The
Through the funding of EPRI and in conjunction with “nouns” or the information contained within the IED are
numerous IEEE Working Groups and the MMS Forum, known as the “attributes” of the object and the “verbs” or
work has begun on a top down design to define the what the IED can do to the data are known as the
requirements for an integrated Protection, Control, and “methods”. For example, a relay will make
Data Acquisition communication system. The measurements of voltage and current and compute watts
requirements document (open to the public for review and and vars. The attributes for this one aspect of a relay
comment) is intended to be the foundation of an open would be: Volts, Amps, Watts, and Vars. Subsequently,
protocol definition that will focus on peer to peer one of the methods would then be “Compute”.
communication in the substation and is expected to have
extensions to other areas of power system communication. In establishing the groundwork for abstracting the
numerous attributes and methods of the substation
The software architecture is based on the International IED’s, a model of the model or a “meta” model was
Standards Organization (ISO) seven layer Open System created. This “meta” model defines data that would be
Interconnect (OSI) model for communication protocols present in any type of IED. There is a standard diagram
[2]. This model breaks a protocol down into 7 that is used to construct the object model which is
independent functional entities that can be linked together illustrated in Figure 2 via the “meta” model for an IED.
(depending on the functional requirements) to create a
protocol definition. In the substation environment, there
are three layers that are applicable and only the bottom
one is of interest to the utility. Figure 1 illustrates this APPLICATION
shortened stack of protocol agreements. The bottom layer
is know as the “Physical” layer and defines how one
LAYER
connects into the system. For example, do I connect a
fiber optic cable or a pair of copper wires. The middle
(MMS, OOM)
layer in this Substation stack is the Data Link Layer
which defines how the data is packaged. DATA LINK
The top layer of this model is known as the Application
LAYER
layer. It is at this level at which the user or user’s
program interfaces with the communication protocol and
(FIELD BUS, HDLC)
ultimately other IED’s. It is also at this level where the
greatest challenge lies as the development of a common PHYSICAL
language is required here in order to interoperate among
the various IED’s. The challenge here can be equated to
LAYER
communication through the spoken language. As a (COPPER, FIBER, etc)
simple model, the basic building blocks of most
languages are nouns and verbs. Combinations of these
nouns and verbs express requests, issue commands, and Figure 1
exchange information. The reason we can communicate 3 Layer Protocol Stack
together is because we have all learned the same nouns
The top line is the name of the object being described is useful for re-triggering multiple IED’s when one IED
which in this case is a Virtual Device object. The is triggered for a data capture. Broadcast transfers can
middle section is the “attribute” list and the bottom reduce the total traffic loading on the communication
section is the “methods” list. Clearly, there are more system, however, broadcast messages cannot be
attributes and methods needed to describe, for example, acknowledged and thus cannot be used when
a relay object. The beauty of the object modeling confirmation of a message is required.
approach, however, is that various attributes can be
grouped in classes and then linked back to the base Multicast - a variation of Broadcast whereby multiple
model. This technique allows the addition of new addresses can be specified to receive a message.
attributes without having to re-do the definitions and
assignments of the previously defined attributes. Directory Services - automatically creates and
maintains a map of all network resources. This function
Work is now in progress in the MMS Forum and the is critical for automatically configuring the network.
IEEE Power System Relay and Substation Committees to
define standard or public object definitions. Common Negotiation - the ability to query the availability of
items such as Voltage, Current, Watts, Vars, etc. can required system data elements and methods. For
very readily be agreed upon as far as a standard example, the IED doing check synchronism may need to
definition goes. It is inevitable, however, that each negotiate for the availability of the voltages on the
manufacturer’s IED will have attributes that are new or network.
unique to that IED. These “vendor specific” attributes,
being otherwise unknown to anything else in the system, File Access, Transfer, and Management - the
need a mechanism to define what they are. transparent transfer of data files between IED’s as part
of the data management function of the various IED. As
As such, the concept of “self defining data” was included processor power increases, the number and size of these
in the requirements document. In response to the data files will increase in kind.
standard query “who are you?”, an IED would be
required to download its object definition, complete with
a data dictionary, to define any “vendor specific”
attributes. In this manner, an RTU function could
automatically query all IED’s in the substation and
Virtual Device
compile a standard list of the information it is required
to obtain. Devide_ID
Device_Type
Device_Description
System Requirements
Device_Make_Model
System functionality was based on application Device_Communication_Address
requirements of existing relaying schemes such as Circuit_Identifier
breaker failure, reclosing, fault recording, metering, and Circuit_Voltage
Circuit_CT_Ratio
sequence of events recording. In so basing the thinking,
Local_Remote_State
system capabilities, performance requirements, facility, Tag_Type_Permitted
environmental, and external interfaces were specified to Active_Tag_Array
meet these application requirements. The various Load
Device_Rating
elements fall out as follows:

System Capabilities Set_Attribute

Get_Attribute
Test
Addressing - each data source and receiver need to be
Reset
identified by and respond to a unique address. One issue
to be resolved is whether all IED are assigned a unique
address in the universe similar to the addressing done on
Ethernet boards.
Figure 2
Standard Object Model
Broadcast - the ability of a pre-specified group of
receivers to respond to a common address. This feature
Network Access - this is how an IED obtains its ability System Quality Requirements
to respond to a query or to offer and unsolicited message. The following elements deal with the question of “how
There are two primary access methods for consideration: well” the system performs its tasks not only today but
also tomorrow.
Peer to Peer - wherein any IED in the substation
can communicate with any other IED. Peer to Scalability - the protocol profile chosen should be robust
peer can take place either through controlled enough for operation today and should have a clear
access (such as a token-passing scheme) or via migration path to increased performance in the future.
random access (such as the listen before you talk
access of Ethernet). A variation of either of these Reliability - the system shall provide error free data
access methods is the ability to permit “priority transmission, shall possess “fail soft” recovery from link
access”, that is, the ability to interrupt a message congestion, and shall provide support for link and/or
transfer with a higher priority message. equipment redundancy.

Master / Slave - wherein IED’s in the system Transportability - the system software shall be
only responds to requests from a master device. A migratable to multiple hardware, software , and network
variation of this occurs where there are multiple operating environments and support the object
masters - each capable of peer to peer management structure chosen as well as its expansion.
communication.
Flexibility and Expandability - the system shall have
Network Management - this shall provide the network adequate address space for today and moving into the
manager up to the minute information on the network future. It shall easily detect and add on new devices
size, operating conditions, alarms, system loading, and hooked into the LAN. It shall support on-line network
error statistics. This function shall also be used to add and IED system upgrades.
new devices to the network.
Security and Integrity - provisions shall be available to
System Performance Requirements prevent unauthorized access, provide management of
To implement the various functions that are envisioned user authorization, support for encryption, and
for implementation on a substation LAN, the following automated virus detection.
performance requirements have been defined:

Time Synchronization - Two levels of time The Number of the Beast

synchronization have been identified in the substation. As the requirements lead to a proposed solution, one of
For general purpose synchronizing, a time accuracy of the questions that arises is “how big” or “how fast” is the
1ms ±0.1ms was selected. For higher accuracy data, size of the animal that is being defined? Taking a stab at
such as phasor measurement and data sharing, an some numbers for two different system requirements, the
accuracy of 1µsec ±0.5µsec has been chosen. results roll up as follows:

Timing Constraints - data transfers intervals were

divided into three categories, namely, “High Speed” for For a “Medium Speed” system that is addressing 32
data transfer requirements less than 10ms, “Medium IED’s once every second and transferring up to 256 bytes
Speed” for transfer requirements greater than 10ms and each second, an aggregate throughput of about 65kbps
less than 1sec, and “Low Speed” involving data transfer would be required.
rates greater that 1 sec. Note: At this time, the
requirement for the exchange of High Speed sample data
was not a priority and as such was not addressed by this For a “High Speed” system also addressing 32 IEDs on a
document. Token Passing network but with a smaller data packet of
64 bytes and a response time of 4ms (including any turn-
Delivery Times - the time allowed to transfer any around time), an aggregate system throughput of about
routinely updated data element from a sending to a 4Mbps would be required. The benefit of “Priority
receiving IED must be less than the average update Access” can be seen here in that similar response time
interval. can be achieved with a lower data rate.
Implementation utility industry. Several other approaches are emerging
The current institutional efforts to define structure for the which include:
new digital universe must be accompanied by the rapid • Combinations of the Software supplier and the
development of implementation vehicles if the industry is Integrator
to advantage, rather than succumb to the new technology. • The IED supplier with the Software supplier
If the current standards work is to have more than • The integration Equipment supplier with the
historical value it must be accelerated to synchronize with Integrator
the pace of technological change, be viewed as a real time and so on. In the absence of at least an appropriate de
consensus definition of best practice, and be connected to facto standard embraced by all the often competing
an implementation path embraced by the utility industry. elements, the solutions will continue to be somewhat
cumbersome, inflexible and costly.
Utilities are driven by the need for increased productivity
in the emerging competitive environment, while at the The two essential aspects of realizing the benefits of the
same time are undergoing personnel reductions which application of digital technology to substation and power
weaken their ability to define and implement integrated system automation are: First; a fast track commitment by
automation systems to improve productivity. Functionally the utilities to sponsor and support the definition of open
fragmented institutional structures are evolving to support standards for integration; and Second; the development
these integrated system goals, but the trauma of such and utilization of Integrators who effectively implement
major changes further inhibits internal solutions. these emerging standards.

Figure 3 illustrates the principal elements of substation One example of the possible ways in which this could be
integration and automation systems. The integration accomplished would be the utilization of existing utility
function has, in today's environment, typically moved organizations such as EPRI to establish system
outside of the utility box. The Integrator's challenge is to integrators which, because of their utility sponsorship,
define best fit / best value solutions tailored to the specific would implement the preferred standards, represent the
utility's goals. In this consulting role the Integrator is utilities, and strongly influence the support of the related
expected to develop specifications for open systems with hardware and software suppliers. Various other proactive
maximum flexibility for growth. His role can be utility initiatives would appear to be worth considering.
expanded to identify the supplier of products and services, The screens for such initiatives might include:
layout the program, manage the program, or take turnkey
responsibility, as well as providing ongoing support and • support by a significant number of utilities
services. • a possible equity position by the sponsoring utilities
• a strong linkage with the continuing "standards"
The IED suppliers provide protection or monitoring based activity
intelligent digital devices which are performance / cost • a strategy that allows customizing for individual
optimized in a rapidly changing competitive market. The utilities
IED's also provide the data acquisition and control • operational control at the Integrator with an advisory
interface with the power system at the substation. board representing the sponsoring utilities
• the assignment of key utility personnel to the
The Software suppliers provide custom software Integrator during a project.
interfacing, drivers and control functions to integrate the
IED's and provide the required system functions. The The alternative of waiting to see what becomes available
Integration Equipment includes the substation control does not look very attractive for the utility.
and interfacing equipment such as Programmable Logic
Controllers (PLC's) Personal Computers (PC's), Remote Conclusions
Terminal Units (RTU's), and associated communication The search for a common communication platform in
equipment. the utility industry is becoming acute being driven by the
proliferation of communicating Intelligent Electronic
The value to the utility of being able to implement open Devices. A “top down” approach to solving the
systems which meet current and future requirements with communication problem has been sponsored by EPRI.
interoperable elements is obvious. The alternative of a This effort has resulted in the creation of a requirements
single supplier providing all elements integrated into a document that is open to the public for review. A
closed system has generally not been acceptable to the summary of the basic requirements is presented. The
heart of the requirements document is the use of Object
Oriented Methodology as the tool to create a common
IED communication language. This effort will only be
effective if there is a concerted effort between the various
industry players to quickly bring this technology to
practice.

References
1. “The Integration of Protection, Control, and
Monitoring is a High Voltage Substation”, M.
Adamiak, E. Weintraub, J. Schnegg, J. Burger,
Proceedings of the 46th Annual Texas A&M Conference
for Protective Relay Engineers, April 12-14, 1993.

2. ISO 7498 - OSI Basic Reference Model