K E M A , I N C .

Substation Integration and Automation –

Approaches and Best Practices

Modern Energy Management Systems

Georgia Tech
Atlanta, Georgia
Wednesday, November 12, 2003

John McDonald, P.E.

KEMA, Inc.
K E M A,I N C .

Overview – Approaches and Best

Practices
n System Architecture
v Substation Integration and Automation Levels
v Primary and Secondary Substations

v Architecture Functional Data Paths

v New Versus Existing Substations

n Communication Protocols
v IED Standalone Capabilities
v IED Integration Capabilities

n Utility Case Study

v Functional Architecture
v Vendor Installed Architecture
2
v Equipment Photographs
K E M A,I N C .

Intelligent Electronic Device (IED)

n Any device incorporating one or more processors with
the capability to receive or send data/control from or
to an external source (e.g., electronic multifunction
meters, digital relays, controllers)

3
K E M A,I N C .

Substation Integration and Automation

Levels
Utility Enterprise
Substation Automation Applications

IED Integration
IED Implementation
Power System Equipment
(Transformers, Breakers)
4
K E M A,I N C .

Substation Integration
n Integration of protection, control and data acquisition
functions into a minimal number of platforms to
reduce capital and operating costs, reduce panel and
control room space, and eliminate redundant
equipment and databases

Utility Enterprise
Substation Automation
IED Integration

5
K E M A,I N C .

Substation Automation
n Deployment of substation and feeder operating
functions and applications ranging from SCADA and
alarm processing to integrated volt/VAR control in
order to optimize the management of capital assets
and enhance operation and maintenance (O&M)
efficiencies with minimal human intervention

Utility Enterprise
Substation Automation
IED Integration

6
K E M A,I N C .

User Applications

Corporate

Example of EMS
Corporate WAN Data
Repository

“Primary” Dial-Up Link

(modem)
Bridge/Router/ Gateway/
Comms Processor

Local UI &

Substation SCADA
Substation
Integration
System
Applications

(direct link) Local/Remote

and
RTU Individual IEDs
Primary
“Secondary” IM
Local Substation LAN
Substation
Substation IM IM IM IM

Comms

IED
(RP-3599
IED Time Sync IED IED
compliant)
(legacy) Source

IM = Interface Module Communications Link

(radio, dedicated line, etc)
= Other possible configurations (migration and future)
= Station environment

Comms

Local/Remote location, eg, on feeders, DAC

or at Remote Customer Substations Server
Secondary
IM IM
Substation
IED
(RP-3599
IED IED compliant)
(legacy)

7
K E M A,I N C .

Primary Substation Automation System

8
K E M A,I N C .

Secondary Substation Automation System

9
K E M A,I N C .

Architecture Functional Data Paths

Utility Enterprise Connection

SCADA Data to MCC Historical Data to Data Remote Dial-In to IED

Warehouse
Substation Automation Applications
IED Integration Via Data Concentrator/Substation Host Processor
IED Implementation
Power System Equipment (Transformers, Breakers)

10
K E M A,I N C . Web pages with Applet
and Servlet (Java)
software for updates
Web Browser Web server
Web Pages with:
oReal
Real--time values
Real- time
Real- oRelay settings
SCADA
oFault records
Fault records, summaries
DNP3.0 ORACLE RdB and waveform data from
relays (and settings)
Frame relay 4-wire lease line

Real-time SCADA
Real-
LAN/WAN TelCo System
data and controls DFR records
All WAN
(any IED’s data) communications are
Router via secure TCP/IP
MB+

Relays

RTU
Fault/Oscillography Real- time
Real-
data files data & controls
Custom files
11
K E M A,I N C .

New Versus Existing Substations

n New Substations
v IEDsWith Digital Communications
v PLCs for Direct I/O
v No Conventional RTUs

n Existing Substations
v May Integrate IEDs With Existing RTUs (Not
Support Non-Operational and Remote Access
Data Paths)
v Integrate Existing RTU as IED or Eliminate
Existing RTU and Use IEDs and PLCs for RTU
I/O
12
K E M A,I N C .

Protocol Fundamentals
n Communication Protocol
v Allows Two Devices to Talk to Each Other
v Each Device Must Have the Same Protocol
Implemented, and the Same Version of the
Protocol
n Both Devices From Same Supplier, and Protocol
n Both Devices From Same Supplier, with Industry
Standard Protocol
n Devices From Different Suppliers, with Industry
Standard Protocol
13
K E M A,I N C .

Protocol Considerations
n North American Electric Utilities Specify the
IEDs to be Used in a Substation
v Chosen Based on IED’s Standalone
Capabilities (Relay for Protection of Power
System) and Not IED’s Integration Capabilities
v IEDs From Various Vendors (Will Not Accept
Turnkey Approach From One Vendor With All
IEDs From that Vendor)

14
K E M A,I N C .

Protocol Considerations…(continued)
n Once IEDs Specified by Utility Based on
Standalone Capabilities, Then Consider Each
IED’s Integration Capabilities
v IED Protocol Support
• Modbus, Modbus Plus, DNP3
• UCA2 MMS
• May Lose Some IED Functionality When Choose Other
Than IED’s Native Protocol
v IED Networking Support
• RS-232 and RS-485 (Serial)
• Ethernet
15
K E M A,I N C .

IEC TC57 Harmonization with UCA2

x-y GOMSFE
Device Models
Device Models
7-4 Compatible data objects Device Models

Common Class Definitions

7-3 Data Templates for Substations
Standard Data Types and
Common Components
Abstract Communication
7-2 Service Interface (ACSI)

Common Application
8-1 Mapping to MMS Service Model (CASM)

61850-x-y
UCA2

16
K E M A,I N C .

North American Projects

• Omaha Public Power District (OPPD) – Two
Substations and One Training Simulator
• MidAmerican Energy Company (Iowa) – Two
Substations and One Training Simulator
• Los Angeles Department of Water and Power – 179
Substations, Two Development Systems, One
Training Simulator Over Five Years
• EPCOR Utilities (Edmonton) – Two Substations
• Minnesota Power – Strategic Plan
• Potomac Electric Power Company (PEPCO) – all
4kV, 13kV, 69kV and 230kV Substations
• Frankfort Electric and Water Plant Board (Kentucky)
– Sixteen Substations and One SCADA System With
17 Two Dispatch Centers
K E M A,I N C .

Omaha Public Power District (OPPD)

• EPRI Tailored Collaboration (TC) Project
• Two Substations, One Training Simulator
• Require all IEDs with UCA Capability to be
Integrated Using UCA2 MMS Protocol and Ethernet
Networking
• Discovered that IEDs Thought to Have UCA
Capability Did Not (Beckwith M2002B LTC Control)
• Discovered that IEDs Achieve UCA Capability By
Adding a Separate Box (Rather Than Integrating Into
IED) (RFL 9745 Teleprotection)
• Integrators Not Need SEL 2030 Communication
Processor – Integrate SEL Relays Directly
• One Substation System and Training Simulator
18 System Being Installed
K E M A,I N C .

OPPD Simplified SA Functional Sketch

19
K E M A,I N C .

Simplified OPPD SA System

20