cost effective multi vendor iec 61850 systems - phoenix … scada europe 2013 - dnv... ·...

Bas MulderMarch 22, 2013

Cost effective multi vendor IEC 61850 systemsChallenges and best practices

Cost effictive multi vendor IEC 61850 systems

March 22, 2013

Introduction Who ?

Previous Life? - In 1999/2000 System Admin for TebeCAI/UPC (IoCATV)- In 2000/2001 ATM/STM Network Admin at a local college

And then?- Back to University, graduated in 2006 in the field of Computer

Science & Telecommunication

KEMA? - Since 2005 working for (DNV) KEMA in the field of Substation

Automation (61850) and Telecommunication

Anything else?- Contributor to the IEC 61850-90-4 LAN Engineering guidelines- Member of the brand new TF -90-12 for WAN Engineering

25 March 2013

2


March 22, 2013

The world is changing from ….

3

‘1985 - ’200? - De-central sys-tem, Hierarchical communication


March 22, 2013

Back into time Traditional substation automation systems

- Did not communicate in any direction- Were developed and delivered by one technology provider- Were not connected to any public network- Lasted a life-time

Various systems still in operation- Master/Slave systems : L&G, Siemens, BBC, AEG (1970-now)

- 1st gen digital systems : Masterpiece (1980-1990)

- 2nd gen digital systems : SAT 1703, ABB MicroScada, Siemens Sicam, Sprecon IEC 60870-5-103 (1990-now)

4


March 22, 2013

….. To

5

Reforming

Gas

Electricity

Bi-directional power and information flows

Some challenges: less predictable generation, less predictable load, network overload

risk, …

New services can be offered: real time

pricing, local energy storage, smart charging, …

Grids should be ‘smarter’ to enable integration of distributed (sustainable) generation


March 22, 2013

Introducing new substation automation systems Next generation based upon IEC 61850

- ABB Relion, Siprotec 4, Sprecon EP

61850 edition 2 is ready for use

The biggest smart grid challenge for a utility and system integrator is to support, maintain and extend legacy and current systems

An interoperable future proof approach is needed to ensure full time operation without downtime

6

Picture provided by Enexis


March 22, 2013

How technology drives the smart grid

7


March 22, 2013

Obsolete applications replaced by new (digital) technologies

8

These are obvious and prevalent …. This is increasing in application ….


March 22, 2013

Usage of new technologies requires interoperability

9

Smart Grid standards:

IEC 60870-5 / DNP3

IEC 61850

IEC 60870-6 (Tase.2/ICCP and Elcom-90)

IEC 61400-25 (wind power)

IEC 61970 / 61968 (CIM)

Smart Meter standards:

DLMS

IDIS

M-Bus

PRIME

SML

OSGP

Telecom Technologies:

SDH/PDH

MPLS

WCDMA/LTE

RF Meshed

PLC


March 22, 2013

But what does interoperability mean? Interoperability means “Being able to seamless integrate different types of devices

from different technology providers, interconnected by different types of local and wide area networks to ensure an always-on electrical grid”.

March 25, 201310

Technology provider 1



Interoperable Smart Grid

Compliant


March 22, 2013

The IEC 61850 approach

March 25, 201311

Good basis fora standard!

No basis fora standard!

„(Abstract) Application objects“

Methods, languages, interfacesfor description and access to application objects

System lifecycle

Innovation of base technologies


March 22, 2013

IEC 61850 Core

March 25, 201312

Application Object Models

Abstract Communication Services

Mapping to Technology

Conformance Testing

.

Substation Configuration

Language (SCL)


March 22, 2013

How to achieve interoperability (1)Set-up IEC 61850 vendor independent requirements

Data modelling

Communication

Engineering

13

– Define typical bays (feeder, transformer,…)

– Define automation functions (logical nodes) per typical bay

– Exactly specify the data exchange

Utility specific data-model

– Require conformance tested and certified devices

– Define standard gateway functionality to SCADA or use 61850

Utility specific PID

– Use vendor independent substation engineering tools

– Verify interoperability between engineering tools


March 22, 2013

How to achieve interoperability (2)Set-up IEC 61850 vendor independent requirements

Replacement

Testing

No utility/vendor specific specials!

Standardize per bay or per station

14

– Standardized connector(s) to process to prevent hard wiretesting on site

– Automation System shall be fully tested in the factory byusing advanced protocol simulators (reduce on-site tests)

– Require advanced simulators during factory testing


March 22, 2013

Engineering challenges In a modern multi technology provider environment you will have

- Legacy systems based upon conventional technology, IEC 60870-5-10x- Diversity of vendors and their different views and approaches- Diversity of communication and configuration protocols- Many firmware updates and bug fixes, changes to configurations- Microsoft Windows systems

Integration is key in a modern substation environment- Protection systems- Control systems - Sometimes Protection and Control systems- Telecommunication- Automation & telecontrol- Local and Wide Area networks- Remote Access to systems

15

Internet connectivity

towards smart grids and smart

meters

Standardized data models

utilities

Increased security attention

Asset management


March 22, 2013

How to handle these challenges? Standardized engineering process is key

- Engineering specification- Engineering & Documentation tools- Functional test and full functional FAT

Try to keep up - Equipment will be changed every 3 year- Support windows are small (3-5 yrs)- Technology providers will come and go- Software is out dated before the launch- Define interoperability on a functional level- Manage spare parts and software updates- Develop new management procedures

16


March 22, 2013

Optimal work flow for a multi vendor system

17

Picture provided by Joulz


March 22, 2013

Total system engineering Transition from device oriented engineering to

- bay oriented engineering - Substation oriented engineering

Object oriented programming- Storage of software and configuration data

Results of this transition- More difficult to evaluate impact of changes- Extensive and thorough testing is required- The need for higher qualified employees- Educate engineers to think in systems not in bays- Difficult to maintain older systems after years of operation

18


March 22, 2013

SCL Engineering

19

Manufacturer

*.ICD

*.ICD

*.ICD

1

IED Configurator

Substation Configurator

*.SSD

*.SCD

*.ICD

*.ICD

*.ICD

3

Substation Specification tool

*.SSD2

*.CID

*.CID

*.CID

2 Single Line DiagramDescription of primary installation, station lay-out and basic functions

1 Description of IED capabilitiesDefined by the manufacturer or tool

3 Combine SSD and ICD filesSCD includes the network, GOOSE, reporting and dataset configuration

4 Subset of the SCD with the relevant configuration data for the IED isloaded back into the IED4


March 22, 2013

SCL Engineering Challenges Generic tools for 100% independent system integration are not available

- Independent third party SCL Engineering is available and works pretty well- Vendor specific configuration tools are still needed- Continues tool training is mandatory- Challenge to keep track of all outputs and merging of SCL files

Sometimes difficult to start using the vendor specific tools

SCL engineering is function oriented including primary and secondary equipment, real-life is still signal oriented

Vendor selection based upon functions is key

20


March 22, 2013

Next Steps Define strict functional specifications for data-model and communication

Select best technology providers to do the job

Standardization of primary equipment

Develop project templates to minimize project specials

Develop and maintain IEC 61850 knowledge

Define a complete overall test strategy (FAT, SAT)

Define and deploy a secure communication infrastructure

Introduction of software and configuration management process (ITIL)

Develop a training platform together with independent knowledge providers and thought leaders

21


March 22, 2013

How to overcome these challenges?

Define utility specific functional specifications

Create a Protocol Implementation Document or IEC 61850 profile

Select best technology providers to support in the core tasks

Standardize primary and secondary equipment

Develop project templates to minimize project specials

Develop and maintain IEC 61850 knowledge

Define a complete overall test strategy (FAT, SAT)

Define and deploy a secure communication infrastructure

Introduction of software and configuration management process (ITIL)

22

Picture provided by ELIA


March 22, 2013

Conclusions IEC 61850 is still under development and construction

- Regular maintenance upgrades- Edition 2 is ready for use- Edition 2.1 is about to be released- Deal with backwards compatibility

Technology providers keep updating their devices- Improved stability - Difficult to maintain compatibility

Engineering and configuration tool limitations- Naming restrictions- Different interpretations by technology providers- GOOSE signal exchange between technology providers requires additional attention- Workarounds need special care- Backwards compatibility with older versions- Introduction of software and configuration change processes (ITIL)

23


March 22, 2013

Final thoughts Together with ENTSO-E work is done to establish a common specification defining

within the IEC61850 standard a global transmission profile in order to guarantee a robust interoperability level

Third party tool manufacturers are cordially invited to develop full independent configuration- and engineering tools that will make IEC61850 system engineering efficient and effective in a full multivendor- environment

24


March 22, 2013

Questions?

25

Picture provided by ELIA


March 22, 2013

For more information http://www.linkedin.com/in/mulderbas

[email protected]

+31 6 4671 3606

cost effective multi vendor iec 61850 systems - phoenix … scada europe 2013 - dnv... ·...

Documents