Substation Automation

Systems – Architecture and

Functions

Dr. Alexander Apostolov

Los Angeles, CA

K02 03 20060309

© OMICRON
 Introduction
• IEC 61850 is an approved international
standard
• Hundreds of substations in service
• Different levels of implementation
• Mostly single vendor systems
• Requires answers to many questions

© OMICRON
Why integration?

© OMICRON
The Integration Process

© OMICRON
The Secret to Success

© OMICRON
 Substation Automation
Substation
Computer

Merging Distance LAN Merging Distance

Unit Protection Switch Unit Protection

Merging Merging
Unit Unit

T1 X-er T2 X-er
Protect. Protect.

DR/PQ DR/PQ DR/PQ DR/PQ

Monitor Monitor Monitor Monitor

Feeder Feeder Feeder Feeder

Protect. Protect. Protect. Protect.

© OMICRON
 What is SAS?
• Substation automation can mean
different things to different electric
utilities.
• Adding a supervisory control and data
acquisition (SCADA) sys-tem for
remote monitoring and control to a
traditional substation with mimic
panels and an annunciator.
• Replacing the mimic panel and
annunciator with a station human
machine interface (HMI).

© OMICRON
 What is SAS?
• Replacing all interlocks, cutouts and
other controls so that all station
control is performed and monitored
using a combination of
microprocessor based relays,
substation controllers and HMIs.
• Actual station automation, including
such items as automatic voltage
control, power fail actions, intelligent
load transferring between stations,
load tap changer control and other
automated routines.

© OMICRON
 Questions
• Do we have a problem?
• What do we need?
• What do we want?
• What is our practice?
• What technology is available?
• What is the site?
• How can we do it?
• Who should do what?
• How should we make sure that it
works?

© OMICRON
Communication in Substations
SUBSTATION COMMUNICATION

Physical link Protocol

RS232 - copper Courier

RS485 - copper SPA

Ethernet - copper Profibus . . .

Proprietary
Ethernet – optic MODBUS

DNP3

IEC 60870 Open

© OMICRON
 Existing Protocol Limitations
• High engineering costs
• Each protocol had its own structure of
representing data (approx. US $ 28 billion spent
on application integration in 1998 – Forrester
1999.)
• Many protocols
• Inter-operability was an issue.
• Different levels of functionalities
• Use of proprietary protocol
• limited use of multi-user products
• Each protocol supported
Different standards followed in Europe and North
America

© OMICRON
 Market Requirements

• Global Market
• Needs a global standard
• Means a broad range of philosophies
• Mixing of devices, at least with copper
cables
• Cost reduction by
• Competition
• Intelligence (functions)

“IEC61850 tutorial, CIGRE Sept 2003.” – Klaus Peter Brand

© OMICRON
 Market Requirements

• Cost reduction in
• Investment
• Operation
• Maintenance
• Open standard, especially for the future
safe guard of investments

“IEC61850 tutorial, CIGRE Sept 2003.” – Klaus Peter Brand

© OMICRON
European historical perspective

• TC57 - Power systems management and

associated information exchange

• IEC 60870-6 TASE 1 - ELCOM90

TASE 2 - ICCP

• IEC 60870-5 101 telecontrol

102 metering
103 protection and control
104 telecontrol over TCP

© OMICRON
European historical perspective

• 1994 AHWG created 2 New Work Item

Proposals:
• Short term solution
• 103 = VDEW + Courier
• Longer term solution
• IEC 61850

© OMICRON
American historical perspective

• ANSI Market
• MODBUS
• MODBUS plus
• DNP 3.0 level 2

• EPRI UCA 1.0 - TASE.2 (ICCP)

2.0 - Substation Initiative

© OMICRON
Substation Automation Project

• Utility functional requirements

• Individual solutions

• Complete solution
• New substations

• Existing substation

• Power System Integration

© OMICRON
Substation Automation Project

© OMICRON
SAS Functional Requirements

• Operations
• real time measurements and status indication
• short-term load forecasting
• fault location information
• power quality monitoring
• Planning
• load flow studies
• system stability studies
• trend recording

© OMICRON
SAS Functional Requirements

• Protection
• relay settings
• relay operations analysis
• Revenue metering
• Analysis
• disturbance recording
• waveform recording
• maintenance analysis
• two-ended fault locator

© OMICRON
IEC 61850 Standard Design

© OMICRON
☺
© OMICRON
Conventional Substations

© OMICRON
Distance Protection Example

Distance Protection
Relay
Waveform Outputs
Recording Module

Analog V, I, Distance
Inputs V0, I0, Protection
I Module
Module Data V2, I2
Bus

Opto Distance
Inputs Protection
Module Scheme

© OMICRON
Conventional Solutions
Process

Analog Sensor Function Outputs Process

Sensor Module Module Module Control

Process
Status Input Multifunctional
Sensor Module IED

Process

Event Start Event End

tSM tFM tOM tPC

tEVT

© OMICRON
 IEC 61850 Systems
• Not just integrated devices
• Functions
• Communications architecture
• Tools

© OMICRON
 IEC 61850 Systems Devices
• Merging Units
• Binary Interface Units
• Integrated Field Units
• Intelligent Multifunction Devices
• Communication Devices
• Computers for Substation Integration
• Real Time Computers

© OMICRON
 IEC 61850 Systems
• Existing substations
• New hybrid substations
• Complete IEC 61850 based substations

© OMICRON
 Substation Automation System
Functions
• Protection
• Automation
• Control
• Measurements
• Metering
• Recording
• Condition monitoring
• Analysis

© OMICRON
 IEC 61850 System Tools
• Engineering
• Configuration
• Integration
• Analysis
• Condition monitoring
• Testing
• Time synchronization

© OMICRON
The IEC 61850 Difference

Boxes versus
Functions

© OMICRON
Communication in Substations
• Centralized monitoring and control
• With numerical relays (IDs) substation
automation has become more popular and
easy to install
• Reduced hardwiring – saving time and
effort on commissioning and maintenance

© OMICRON
Communication in Substations
SCADA Protocol
To IMS/SCADA

HMI,s

Substation
Controller (s)

Communications Architecture

ISD ISD ISD ISD

© OMICRON
 IEC 61850 Based Protection

Process
Merging Unit Protection IED

Analog Sensor Interface LAN Interface Protection Outputs

Sensor Module Module Switch Module Module Module

Process
Status Input Interface Control
Sensor Module Module

Control Interface Unit Process

Process

Event Start Event End

tSM tIM1 tLAN tIM2 tPM tOM tPC

tEVT

© OMICRON
Communication in Substations
SCADA Protocol
To IMS/SCADA
HMI,s

Substation
Controller (s)

Communications Architecture

ISD ISD ISD ISD

IOU IOU IOU IOU

© OMICRON
 IEC 61850 Based Protection
Process
Merging Unit Protection IED

Analog Sensor Interface LAN Interface Protection

Sensor Module Module Switch Module Module

Status Input Interface

Sensor Module Module

Outputs
Module Control Interface
Process
Unit

Process
Control
Event Start Event End

tSM tIM1 tLAN1 tIM2 tPM tIM3 tLAN2 tIM4 tOM tPC

tEVT

© OMICRON
 System Architecture
Station Bus Mappings (8-1)
Layered Mapping (TCP/IP)
GOOSE/GSSE (Link)
Substation Computer Time Sync (SNTP)

Station Bus

IED IED IED IED

Process Bus

CT VT CT VT Process Bus Mappings (9-1,9-2)

Sampled Values (Link)
GOOSE/GSSE (Link)
Time Sync (SNTP)

© OMICRON
Substation Automation Project

Make sure you’ve got every ingredient before you start

© OMICRON
 Inside the IEC 61850
• Communication first
• Services: How to transfer data ?
(Parts 7, 8 and 9)
• Objects: How to address data ?
(Parts 7, 8 and 9)
• Configuration: How to share
common references between
applications ? (Part 6)
• Conformance test objectives: How
to test a server in front of a IEC 61850
reference simulator (Part 10) 14 Parts
>1000 pages (English only !)
10 years of development

© OMICRON
 Inside the IEC 61850

• Some non communication

aspects
• Environmental conditions (Part 3)
• Engineering requirements (Part 4)
• System lifecycle (Part 4)
• Informal function description (Part
5)
• Connectivity between primary IEC 61850
devices (Part 6)
14 Parts
>1000 pages (English only !)
10 years of development

© OMICRON
 Logical architecture: Data flow
TRADITIONNAL (> 80%) IEC 61850 POTENTIAL IMPACT

Master
HMI
Simple and Client
standard clients T104,
Gateway
http, etc.
Station Computer
Client Client

Slave
IP Routable
Protection

Server Server Server

Slave
Bay Fast Peer-to-Peer
computer

Central point Non trivial design for

Distributed functions limited innovative schemes
by performances (performances, side effects)

© OMICRON
Outside the IEC 61850

• Functional specification
• IED content
• System architecture
• Migration strategy
• Non communication
configuration
• Configuration & setting
management
• Inter-operability tests
• Project phases

What you need to add for a real project !

© OMICRON
 Functional specification
• IEC 61850 is defining a series of function
names
• “Logical Nodes”
• Example: “PDIS” = Distance Protection
• Each logical node is associated to a data
structure
• Example: “Str” = Start (for a protection)
• The content of the data structure can be
remotely accessed
• Example: Report “Str” when there is a change

• But the function itself is not defined

• Example: distance algorithm is specific to each manufacturer
• The function shall be described by the project specification
• Example: tripping time, number of zones, etc.

© OMICRON
 Functional specification

• No change for functions contained in a single

IED
• Example: distance protection function
• Distributed functions shall be defined
• Example: Station Wide Interlocking

• Some distributed functions are easy to identify

• Interlocking, Inter-tripping, Load Shedding, Protection
Acceleration, etc.

Accurately specify distributed functions

when mixing suppliers

© OMICRON
 Functional specification
• Some distributed functions require more
attention
• Redundancy management, alarm management, time
synchronization server, etc.

• Just replicating old schemes is likely to restrict

the technology benefits
• Need to think “out of the box” to build cost effective
solutions: standard clients, standard bays, new
automation

Accurately specify distributed functions

when mixing suppliers

© OMICRON
 IED Content
• IEC 61850 enable to freely allocate Client/
Subscriber
Server/
Publisher
Value/Commen
ts

the Logical Nodes into the IEDs Client-Server roles

B11 Server side (of TWO-PARTY- ⎯ Y

• A way to foster creativity B12

APPLICATION-ASSOCIATION)
Client side of (TW O-PARTY- Y ⎯
APPLICATION-ASSOCIATION)

SCSMs supported

• A given IED will map a subset of all B21 SCSM: IEC 6185-8-1 used A-Profile cli-
ent/server
A-Profile cli-
ent/server

possible LN T-Profile
TCP/IP
T-Profile
TCP/IP

• Hardware and software resources

A-Profile A-Profile
GSE/GOOSE GSE/GOOSE
T-profile T-profile
GSE/GOOSE GSE/GOOSE
B22 SCSM: IEC 6185-9-1 used N N
B23 SCSM: IEC 6185-9-2 used N N

• A project has to make B24 SCSM: other N N

compromises Generic substation event model (GSE)

• Imposed IEDs: qualification, B31

B32
Publisher side
Subscriber side
⎯
Y ⎯
Y

installed, coupled with remote

ones, etc. Transmission of sampled value model (SVC)

B41 Publisher side ⎯ N

• IED & Client Availability (suppliers) B42 Subcriber side N

c1 – shall be ‘M’ if support for LOGICAL-DEVICE model has been declared.
⎯

• A project shall check a priori compatibility between devices

• PICS: Protocol Implementation Conformance Statement
• MICS: Model Implementation Conformance Statement
• ICD: IED Capability Device
• Capability to realize a complete function between distributed devices,
including logic configuration capabilities

© OMICRON
 System architecture
• Nothing is defined by the IEC 61850
• Will to enable innovation
• Logical architecture shall be defined
• Nominal Data flow: clients/servers and peer-to-peer, short and
medium term sizing
• Non Nominal Data Flow: missing device, invalid data,
performance during avalanches
• Redundancy management: client and server sides, cold/hot
• Performance management: multi-cast filtering, VLAN, Clusters
• Security: how to protect from external threats
• Physical architecture shall be defined
• Electrical/optical
• Single/redundant
• Loop/Star
• Ethernet Switches
System architect is required as per any Information System

© OMICRON
 The system architect
• A (“new”) job essential for innovative
design and/or mix of different suppliers
matching evolving business processes

• Both long term view (defining guidelines)

and short term perspective (real projects)

• Short term
• Guarantee the functional consistency of the various devices
working together and the system performances
• Make sure that distributed functions are fully defined and have
acceptable side effects in case of degraded situations
• Mix legacy devices with new technology and define migration
paths
• Manage the increasing system complexity: version, security, etc.
• Design with system tests & costs in mind: interoperability,
functional validation, performances
• Design and regularly improve internal generic standard

© OMICRON
 System Architecture vs. System
Integration
System Architect
• Distributed functions detailed
specifications (LN mapping, LN detailed
logic, report parameters, etc.)
• Migration strategy
• Communication architecture
• PICS and MICS of the IEDs to be used
• IED preliminary choice and supplier
participation negotiation
• IED paper inter-operability analysis and
validation
• Performances simulations
• SSD
• Medium/long term evolution
• Security policy
• Standard packages (bay, schemes, etc.)
• Project technical supervision
System Integration
• Overall specification
• Distributed function specification
adjustment
• Overall configuration databases
and setting
• Plate-form components purchasing
and assembly
• Test plan/sheet/results for
nominal/degraded/performance
scenario
• IED fault reports/Change report
emission and supplier negotiations
within the agreed frame
• Architect fault report
• Version management for
HW/SW/Database per IED
• FAT/SAT/Maintenance
© OMICRON
 Non communication configuration
• System configuration aims first at
sharing the same data reference
(addresses) between distributed
devices Communications
• Single data entry and (implied)
consistency
• Need is increasing with the new Wiring HMI
technology
• More data are likely to be transmitted
• More than client-server schemes
Automation
• System configuration goes beyond
the pure communication
• Automation
• Graphic
• Physical I/Os
A growing requirement

© OMICRON
 Non communication configuration
• Most real time value are
shared between the source
(IED) and GUI or Gateway
• Electrical topology is typically
shared between devices and
used for interlocking, voltage
regulation of parallel Graphical description:
transformers, etc. SVG

Automation description: Testing Tools

• Substation Configuration IEC 1131-3/1499

Language (SCL) is focused

on communication Communications &
Capabilities
• Sharing data between clients IEC
and servers, publisher and
subscriber
• <20% of the system
configuration CAD tools SCADA

• Need for extensions

© OMICRON
 Non communication configuration
• Most real time value are shared
between the source (IED) and
GUI or Gateway
Graphical description:
• Electrical topology is typically SVG
shared between devices and used
Automation description:
for interlocking, voltage regulation IEC 1131-3/1499
Testing tools

of parallel transformers, etc.

Communication & IEDs
capabilities description:
• Substation Configuration IEC 61850-6

Language (SCL) is focused on CAD tools SCADA

communication
• Sharing data between clients and
servers, publisher and subscriber
• <20% of the system configuration
• Need for extensions

© OMICRON
 Configuration management
• Configuration management
• Capability to distribute
Evolving Substation
configuration databases to the
Requirements various devices and insure that
(size, functions, etc.) their versions are consistent
Fixing bugs between them
• But a also that they are
consistent with evolving
hardware and software versions
• Inconsistent databases might
lead to security issues (example:
control the wrong circuit
breaker)
• Not defined by IEC, i.e. specific
Adding
to a supplier or a user
features
• Solution: manual process or
central software client

© OMICRON
 Setting management
• Setting management
IEC 61850
Independent Engineering
100 Mbps/s
Encapsulated Protocols
Ethernet
Web-services, email
• Capability to adjust a device
setting, i.e. local data only
• IEC is defining a change of
setting group (similar to IEC
60870-5-103) but not the change
of individual parameter
• IEC is defining a subset of the
setting of a real device
(common subset between
suppliers) and is not defining
how to do it (file transfer,
individual setting change,
device reboot, etc)
• Solution: encapsulation of the
traditional setting messages
over TCP/IP, in parallel to pure
IEC 61850 exchanges
© OMICRON
 Project phases
• A project is much more than a demo
• More data will be exchanged with the new technology thus
methodology importance is increasing
• Need to structure the work to converge quickly
• Requirements
• System specification
• System Architecture
• Database & platform building
• Inter-operability tests
• Project tests
• Need to clarify the roles
• End user
• System architect
• System integrator
• Product suppliers

© OMICRON
 Conclusion: A long term
investment
Benefits
GOOSE New applications
Standard Clients (local, network)
Network data integration
Traditional
Technology

Learning
curve

Investment
COPY QUICK DEEP phase
HITS CHANGES

Scalable systems

© OMICRON