CIGRE 2005 - B5 - Cepel · CIGRE 2005 - B5 IEC 61850: ... ¿ EN TE C P141 MiC O TRIP ... Managing the flows: Examples Structured system design stage Design Level Technology IED

CIGRE 2005 - B5IEC 61850:

Impact on System Architecture and Tools

FURNAS, Rio de Janeiro, March 29th

Luc Hossenlopp

CIGRE 2005: Rio de Janerio, March 29th, 20053 3

What is an architecture ?

� Not defined in the IEC 61850 Glossary (part 2) !

A vast subject - different ways to approach it

� “ A system architecture is the science and art of selecting and interconnecting components to create a system that meet functional, performance and costgoals”, derived from On Computer Architecture, 2004

� “An architecture is the fundamental organization of a system embodied in its components, their relationshipswith each other, and to the environment, and its principles guiding its design and evolution”, IEEE 1471 (2001)


Architecture Analysis: Key Parameters

Scope, Functions & Evolutions

Process/Function distribution Performances Dependability

Physical integration

4 analysis layers for defining a complete solution

Imposedcomponents

New componentscapabilities

DetailedInterfaces


Architecture design: Key stepsLOGICAL

ARCHITECTUREExample

ProxyServerMaster

ControlServer

ProtectionServer

Mimic displayClient

Line protectionSlave

Line protectionSlave

ControlServer

Data modeling &data flow between

logical nodes

PHYSICALARCHITECTURE

Example

GUI

EthernetSwitch

��C

P141

��

MiCOMTRIPALARM

OUT OF SERVICE

HEALTH Y

C = CLEAR��= READ↵↵↵↵= ENTER

��C

P141

��

MiCOMTRIPALARM

OUT OF SERVICE

HEALTH Y


IEDs

Legacy IEDs(parallel wiring, T103, DNP3, Modbus)

Real devices andcommunication technology

mapping


Logical architecture: ScopeTRADITIONNAL (> 80%)

SAS

DispatchingMaintenance

Center

Primarydevices

Other substations

Substation centricPretty Monolithic

SAS

IEC 61850 POTENTIAL IMPACT

Other substations

Dispatching MaintenanceCenter

Primarydevices

Scalable & adaptable: from process bus to network automation

Other substations

Bay

Station

Process

WAN

WANWAN

Processbus

IEC 61850: Think out of the box !


Logical architecture: Data flow


Server Server Server

Client Client

IP Routable

Simple and standard clients

Fast Peer-to-Peer

Non trivial design forinnovative schemes

(performances, side effects)

ClientT104,

http, etc.

TRADITIONNAL (> 80%)

Slave

Slave

Master

Central pointDistributed functions limited

by performances

HMIGateway

Station Computer

Protection

Bay computer


Logical Architecture: Data Integration


Formal system configurationCapability to secure large

application interconnections

XML - SCL - CIM - (and more to come)

TRADITIONNAL (> 80%)

Hand made system configurationsubject to human interpretation:

Limited application interconnections

IED Data list HMI Data list


A long term investment

Scalable systems

Benefits

Investmentphase

TraditionalTechnology

QUICKHITS

GOOSEStandard Clients

DEEPCHANGES

New applications(local, network)

Network data integration

COPY

Learning curve


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


Distributed function exampleInterlocking

No miracle - Function detailed description is (still) needed !Need to insure that each IED logic is compatible withthe system specification - and check inter-operability

IED IED IEDIED

1. Lock

2. Block ifno lock inprogress



Insuring a unique control at

a timefor system

interlocking function


Increased data flows

� Frame overhead

� Use of MMS/TCP/IP requires higher overheads than traditional T103/DNP3/Modbus links, this is the price to pay for a better flexibility

� Data integration

� Use of XML files permits to formally and automatically create logical links between applications using the same data thus more data will be exchanged for operation or maintenance purpose

� Function distribution

� Use of client-server and Goose mechanisms drive new functional distribution for better flexibility and generate additional data flow

� New applications

� New substation and grid-wide applications are likely to be developed using ubiquitous information availability

� Dependability

� Increased inter-relations between devices make requires additional redundancy management for critical components

Truly manage the data flows


Look at the server communication constraints


Client Client

Fast Peer-to-Peer

ClientT104,

http, etc.

� Report to several clients:

� One change within the server may request to build several reports and send them

� Send, Receive and Process GOOSE

� One GOOSE is continuously repeated for security and automation initiation

� Reception of a GOOSE normally request some automation processing

� Process non IEC 61850 traffic

� Remote Setting, Disturbance record retrieval

One server device shall “simultaneously”


Managing the flows: Examples

Structured system design stage

Design Level Technology

IED

Ethernet Switches

System physical architecture

System logical architecture

Hardware multi-cast filtering

VLAN

Proxy

Clustered (standard) schemes


Redundancy management

� A way to improve system availability and reliability

� Behavior is not defined in IEC 61850

�Typical example where the architect needs to define what shall be done… and first check on paper that it can be supported by the IEDs

� May be applied to:

�Communication infrastructure: tolerate the loss of an optical fiber or/and the loss of a central switch

�Clients: capability for a client to continue the tasks initiated by a first client (example: Graphical user interface)

�Servers: capability for a client to switch to a redundant server if the first one is not operational (example: CT/VT sensor)

� 99.99% availability requests the 3 types of redundancy


Redundancy management: Communication infrastructure examples

STARAdd a redundant central switch

Make sure that all devices can have two Ethernet links

RINGNative redundancy

TechnologyStandard IP Routing (Spanning Tree): Typ. 30 s

Standard Fast Spanning Tree implementation: Typ. 300 msBest in class: <<1 ms


Redundancy management: Client redundancy GUI example

Constraints = f(performances)

Hot redundancyTwo GUI directly accessing each server

Both display and archive dataOne only is active in control

Once the first has failed the second continueswithout context re-initialisation

No data loss even for “long” failure detection

Warm/cold redundancyOne GUI is accessing each server

The second GUI get data from the first oneBoth display and possibly archive data

One only is active in controlOnce the first has failed the second re-initialize

the communications with the serversPossible data loss during switch-over

NominalLink

NominalLink

NominalLink

NominalLink

Back-upLink


Managing Complexity:Version management examples

Methodologies & Tools importance is increasing

Fixing bugs

Addingfeatures

� Each IED life is made of different versions

� Making sure that a new version does not bring regression at system level is non trivial

� Each IED configuration database shall insure data consistency with other IEDs or software for distributed functions

� Identification of which IED database shall be changed during a system evolution is nottrivial


Client Client

Client

Server


System Methodologies & Tools

� System configuration

�Create consistentdatabases and manages versions of them


Client Client

Client

Server

Communication & IEDscapabilities description:

IEC 61850-6

Graphical description:SVG

Automation description:IEC 1131-3/1499

CAD tools SCADA

Testing tools

� System management

�Download databases to run insure a consistent system and activate devices accordingly


System Methodologies & Tools

� Device simulator

�Re-create missing devices in a system to assess the correct configuration and performances

Test plan

Testobjectives

Testscenario

Test managem

ent

Test methodology


Client Client

Client

Simulator

� Test management

�Test plan, detailed test sheet and simulator scenario for inter-operability, functional validations and performances


Architecture Example - 1

Bay level - new and legacy devices

��C

P141

��

MiCOMTRIPALARM

OUT OF SERVICE

HEALTH Y


��C

P141

��

MiCOMTRIPALARM

OUT OF SERVICE

HEALTH Y


��C

P141

��

MiCOMTRIPALARM

OUT OF SERVICE

HEALTH Y


��C

P141

��

MiCOMTRIPALARM

OUT OF SERVICE

HEALTH Y


Single deviceMV Schemes

Mix of new and legacy

technologiesHV Schemes

Pure new technologiesHV Schemes

P1

P2

P+C C C

P1

P2

IEC 61850

T103DNP3

Modbus

��C

P141

��

MiCOMTRIPALARM

OUT OF SERVICE

HEALTH Y


��C

P141

��

MiCOMTRIPALARM

OUT OF SERVICE

HEALTH Y


Pure new technologiesHV Schemeswith process

bus

C

P1

P2

��C

P141

��

MiCOMTRIPALARM

OUT OF SERVICE

HEALTH YC = CLEAR��= READ↵↵↵↵= ENTER

��C

P141

��

MiCOMTRIPALARM

OUT OF SERVICE

HEALTH YC = CLEAR��= READ↵↵↵↵= ENTER

S1 S2



Typical distributed scheme - could be a star or mix

GUI Gateway

BayBay

Bay



Large schemes/Network automation

GUI

Proxy

BayBay

Bay

Proxy

BayBay

Bay

Gateway


Conclusion

� Key evolution potential with IEC 61850

� Gradual move is recommended

� Re-use of validated/standard schemes within scalable systems

� Architect job, Methodology and Tools are key

Documents

CIGRE 2005 - B5 - Cepel · CIGRE 2005 - B5 IEC 61850: ... ¿ EN TE C P141 MiC O TRIP ... Managing the flows: Examples Structured system design stage Design Level Technology IED