iec 61850: from paper to operation - cepelceb5.cepel.br/arquivos/grupos_trabalho/wgb5.11... · b24...

IEC 61850:From Paper to Operation

Dr. Alexander ApostolovAREVA T&D Automation

XVIII SNPTEECuritiba, Brazil, 19 October 2005

IEC 61850: From Paper to Operation2 2

Introduction

IEC 61850 is now an approved international standard

It allows the development of a new generation of substation automation systems and applications

Devices conforming with the new communications standard are available from multiple vendors


Introduction


Introduction

IEC 6185014 Parts

>1000 pages (English only !)10 years of development

REAL SUBSTATIONDifferent vendorsInteroperability

Easy specification

Is it really that simple ?


Introduction

IEC 61850 is not just a new communications protocol

Its successful implementation requires: Good understanding of the principles of the standard (No Ignorance!)

Teamwork

Ambition


Introduction


IEC 61850 Standard - Organization


IEC 61850 Key Benefits

Speed: 100 Mbps instead of few 10 kbpsMore data for a better operation & maintenance

Peer-to-peer: No extra hardwareDesign of innovative automation schemes, late tuning

Conditional report instead of pollingOptimal performances

IP (Internet Protocol) routing: Ubiquitous data accessCapability to extend the system outside of the substation

Client-server: Instead of master-slaveFlexible designs easy to upgrade

Pre-defined names: Single vocabulary between usersEasier engineering between teams

XML references: Formal interfacesConsistency between engineering tools

A true step forward


IEC 61850: Basic applications and possible extensions

Telecontrol of substations “sTCA”in discussion, IEC TC57 / Ad Hoc Working Group 07

Addendum Power Quality, Monitoringunder way, IEC 57/624/NP

Product standard for switchgear equipmentunder way, IEC 62271-003

Control and monitoring of wind power plantsunder way, IEC 61400-25

Control and monitoring of distributed power stationsunder way, IEC 57/660/NP

Control and monitoring of hydroelectric power plantsunder way, IEC 57/661/NP

Metering (EPRI, IEEE), Gas, Waterin discussion

Several other WG within:IEEE PSRC H5: Setting, etc.UCA International: Testing, etc.CIGRE B5.11: Use of IEC 61850 in substation, etc.DKE/VDN (Germany): Recommendations


Substation Automation Project

Make sure you’ve got every ingredient before you start


Inside the IEC 61850Communication 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 reference simulator (Part 10)

Some non communication aspectsEnvironmental conditions (Part 3)Engineering requirements (Part 4)System lifecycle (Part 4)Informal function description (Part 5)Connectivity between primary devices (Part 6)

IEC 6185014 Parts

>1000 pages (English only !)10 years of development


Inside the IEC 61850


Logical architecture: Data flow

IEC 61850 POTENTIAL IMPACT

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


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 !


Functional specification (1)

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 definedExample: distance algorithm is specific to each manufacturer

The function shall be described by the project specification

Example: tripping time, number of zones, etc.

So what’s new ?


Functional specification (2)

No change for functions contained in a single IEDExample: distance protection function

Distributed functions shall be definedExample: Station Wide Interlocking

Some distributed functions are easy to identifyInterlocking, Inter-tripping, Load Shedding, Protection Acceleration, etc.

Some distributed functions require more attentionRedundancy 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 functionswhen mixing suppliers


IED ContentIEC 61850 enable to freely allocate the Logical Nodes into the IEDs

A way to foster creativity

A given IED will map a subset of all possible LN

Hardware and software resources

A project has to make compromisesImposed IEDs: qualification, installed, coupled with remote ones, etc.IED & Client Availability (suppliers)

A project shall check a priori compatibility between devices

PICS: Protocol Implementation Conformance StatementMICS: Model Implementation Conformance StatementICD: IED Capability DescriptionCapability to realize a complete function between distributed devices, including logic configuration capabilities

Client/Subscriber

Server/Publisher

Value/Comments

Client-Server roles

B11 Server side (of TWO-PARTY-APPLICATION-ASSOCIATION)

⎯ Y

B12 Client side of (TWO-PARTY-APPLICATION-ASSOCIATION)

Y ⎯

SCSMs supported

B21 SCSM: IEC 6185-8-1 used A-Profile cli-ent/serverT-ProfileTCP/IPA-ProfileGSE/GOOSET-profileGSE/GOOSE

A-Profile cli-ent/serverT-ProfileTCP/IPA-ProfileGSE/GOOSET-profileGSE/GOOSE

B22 SCSM: IEC 6185-9-1 used N N

B23 SCSM: IEC 6185-9-2 used N N

B24 SCSM: other N N

Generic substation event model (GSE)

B31 Publisher side ⎯ Y

B32 Subscriber side Y ⎯

Transmission of sampled value model (SVC)

B41 Publisher side ⎯ N

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


System architectureNothing is defined by the IEC 61850

Will to enable innovation

Logical architecture shall be definedNominal Data flow: clients/servers and peer-to-peer, short and medium term sizingNon Nominal Data Flow: missing device, invalid data, performance during avalanchesRedundancy management: client and server sides, cold/hot Performance management: multi-cast filtering, VLAN, ClustersSecurity: how to protect from external threats

Physical architecture shall be definedElectrical/opticalSingle/redundantLoop/StarEthernet Switches

System architect is required as per any Information System


The system architectA (“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 termGuarantee 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


System Architecture vs. System Integration

System IntegrationSystem 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

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

IED paper inter-operability analysis and validation

Performances simulations

SSD

Medium/long term evolution

Security policy

Standard packages (bay, schemes, etc.)

Project technical supervision


Migration strategy

“Greenfields” happen but are (very) rareNeed to define the general migration from present situation to the future

Several strategies – need to define the applicable onePer function, for example: change protection firstPer electro-technical entity, for example: bay or voltage levelKey criteria: aging device, qualified device, outage minimization, etc.

“Proxy concept”Gateway from past protocol to IEC 61850IED, RTU or even GUI

Network visionTelecontrol: protocol, configuration exchangesAsset managementDistributed automation

Part of the big picture


Non communication configuration (1)System configuration aims first at sharing the same data reference (addresses) between distributed devices

Single data entry and (implied) consistency

Need is increasing with the new technology

More data are likely to be transmittedMore than client-server schemes

System configuration goes beyond the pure communication

AutomationGraphicPhysical I/Os

Wiring

Automation

Communications

HMI

A growing requirement


Non communication configuration (2)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 transformers, etc.

Substation Configuration Language (SCL) is focused on communication

Sharing data between clients and servers, publisher and subscriber

<20% of the system configuration

Need for extensions

Communication & IEDscapabilities description:

IEC 61850-6

Graphical description:SVG

Automation description:IEC 1131-3/1499

CAD tools SCADA

Testing tools


Configuration managementConfiguration management

Capability to distribute configuration databases to the various devices and insure that their versions are consistent 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 to a supplier or a user

Solution: manual process or central software client

Fixing bugs

Addingfeatures

Evolving SubstationRequirements(size, functions, etc.)


Setting managementSetting management

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

100 Mbps/sEthernet

IEC 61850

Independent Engineering

Encapsulated Protocols

Web-services, email


Inter-operability tests (1)

IEC 61850-10 is defining purely conformance tests objectivesCommunication centric in front of a reference simulatorDetailed testing scenario are being defined by UCA International(not in part 10)A way to get confidence in the implementationNo way to test the application data modeling consistency (since function oriented)

Test MasterTest Monitor

Load SimulatorTime Sync

HMIMonitor

DUT 1Station Bus

Binary,AnalogOutputs

Binary,AnalogInputs



Test level Example

End-to-end tests, exact distributed functions,

Ethernet infrastructureProject tests

Typical distributed functions(nominal/degraded/performance)

Mapping sampleIEDs inter-operability tests

IED Conformance test IEC 61850 communications

FunctionalEnvironmentalIED Test

Need for tools and methodology



Communication is only a mean to perform a functiondistributed between communicating devices

Define the level of functional integrationthen make the right system tests

Functional level Non Trivial Test Example1. Supervision 1. Consistent time tagging2. Control 2. Sequence of tests with SBO3. Disturbance record retrieval 3. Keep real time values retrieval3. Remote setting 4. Transparent mode


Project phases

A project is much more than a demoMore data will be exchanged with the new technology thus methodology importance is increasingNeed to structure the work to converge quickly

RequirementsSystem specificationSystem ArchitectureDatabase & platform buildingInter-operability testsProject tests

Need to clarify the rolesEnd userSystem architectSystem integratorProduct suppliers


Conclusion: A long term investment

Benefits

Investmentphase

TraditionalTechnology

QUICKHITS

GOOSEStandard Clients

DEEPCHANGES

New applications(local, network)

Network data integration

COPY

Learning curve

Scalable systems


No pain, no gain!


The secret to successful blackout analysis

iec 61850: from paper to operation - cepelceb5.cepel.br/arquivos/grupos_trabalho/wgb5.11... · b24...

Documents