IEC61850: Application Migration, Conformance and Interoperability Testing. International Conference IEC March 30, 2005 FURNAS Rio de Janeiro

Transcription

1 IEC61850: Application Migration, Conformance and Interoperability Testing International Conference IEC March 30, 2005 FURNAS Rio de Janeiro Ralph Mackiewicz SISCO, Inc. Agenda Migration to IEC61850 The need for migration Legacy Protocols to IEC61850 SCADA Migration UCA2.0 to IEC61850 Testing Interoperability & Conformance Testing Certification and quality control Test Cases Role of the UCA International Users Group 1

2 Why is Migration Important? IEC61850 delivers significant benefits: Drastically reduced setup/configuration Standardized naming and configuration More standardized functions (less custom) Higher performance Without migration, benefits are only available for new systems. Missed opportunity for cost and performance improvements Replace Existing Equipment New construction System replacements What about system expansions or upgrades? Some new equipment but still need to leverage existing equipment while preserving benefits of IEC

3 Migration Strategy Data Concentrators/Gateways Preserve existing equipment Wrap the legacy protocol with IEC61850 to hide the primitive protocols. Isolates the limitations of the legacy systems to enable the benefits of IEC61850 IEC61850 is designed specifically to support these concepts. Logical Device Structure IEC61850 Clients WAN to Control Center IEC61850 Server Physical Device Logical Device 1 to N Logical Devices Logical Device Logical Node Logical Node Logical Node Logical Node Data Data Data Data Data Data Data Data 9-2 Process Bus Field Signals Communications Driver Legacy Device(s) 3

4 Example Project Current Phone Network Control Center Existing automation for existing feeders RTU IED Modem IED I/O Example Project New WAN New automation for expansion Station Bus Router/ Firewall Control Center Process Bus 4

5 Example Project Migrated WAN Control Center New automation for expansion Station Bus Router/ Firewall LD Existing automation for existing feeders RTU IED Process Bus LD LD IED I/O Data Concentrator Example Project Integrated WAN New automation for expansion Station Bus Router/ Firewall Logical Device Control Center Existing automation for existing feeders IED Process Bus Logical Device Logical Device IED I/O Data Concentrator Eliminates maintenance and configuration of separate RTUs 5

6 Example Project Equip. Replacement WAN Control Center New automation for expansion Station Bus Router/ Firewall Existing automation for existing feeders Process Bus Logical Device Logical Device IED I/O Equipment Replacement Has Minimal Impact on Existing Systems Object Mapping Legacy data objects must be mapped to IEC61850 objects LD MMXU1 XCBR1 PIOC1 IEC61850 Device MX.A.PhsA.cVal.mag.f MX.A.PhsB.cVal.mag.f MX.A.PhsC.cVal.mag.f ST.Loc.stVal ST.Pos.stVal ST.BlkOpn.stVal ST.Op.phsA ST.Op.phsB ST.Op.phsC Legacy Device R R R R R R R R R R R40004A R40004B 6

7 Benefits of Migration Eliminates legacy IED and protocol dependencies from applications reducing configuration and maintenance cost. Common network infrastructure for both Legacy equipment can be replaced with minimal application impact. Manual configuration (mapping) of points only needed for legacy systems. Why Migrate SCADA? IEC61850 is a substation automation standard but it is useful for SCADA 7

8 SCADA Migration Current Phone Network Control Center Existing automation for existing feeders RTU IED Modem IED I/O SCADA Migration Future? WAN Control Center Existing automation for existing feeders LD IED Firewall/ Router LD LD IED I/O Data Concentrator 8

9 Legacy View of SCADA Data Flat set of tags Client Access by tag name SCADA Using Flat tags for SCADA It is in Register 4023 and 4024 That s intuitive? I need the Phase A voltage for the 345KV primary feeder #1 9

10 Object Models: IEC61850 PhV Functional Constraints MX MX Logical Nodes A MMXU1 MMXU2 Logical Device (e.g. Relay1) Physical Device (network address) MMXU2$MX$A = Feeder #2 Current Measurements IEC61850 View of Devices Brand X IOC Relay Brand Y Diff Relay PIOC Measurements MMXU1 PDIF Measurements MMXU1 SG CO A PhV SG CO A PhV MMXU1$MX$PhV$phsA$cVal$mag$f 10

11 Why Migrate SCADA Which is more intuitive? R4023 MMXU1$MX$PhV$phsA$cVal$mag$f Even user defined tag conventions are proprietary. Use of IEC61850 and IEC61970 (CIM) structures and names is possible in existing systems. Why waste power system engineers as data base configuration clerks? UCA2.0 to IEC61850 Migration 11

12 UCA2 IEC61850 Migration UCA2.0 is mostly a subset of IEC Some additional services and objects. Changes in object structures. IEC61850 uses SNTP for networked time synchronization. IEC61850 clients can be compatible with both UCA2 and IEC UCA2 vs Object Models Data Object Model Data Set Model Association Model Server Model Unbuffered Reporting Model Security Model Time Model Direct and SBO Control GSSE (called GOOSE in UCA2) Data Object Model Data Set Model Association Server Unbuffered and Buffered Reporting Separate Security Standard Time Direct, SBO, enhanced Control GOOSE, GSSE, and GSE Management 12

13 Un-buffered Report Control Block UCA 2.0 IEC61850 Fixed Length vs. Variable Length Variable Length allows for expansion, yet is backward compatible. Client Report Subscriptions UCA2 Clients see only those report control blocks available to them and enable them as needed (some IEC61850 devices may do this also). IEC61850 Clients may see: All available URCBs and use the resv bit to reserve a specific URCB for their use. If a client enables a URCB without reserving it, the reservation is made implicitly. 13

14 61850 Buffered Reporting Un-buffered Buffered EntryID is used by Client to resynch to an offset in a buffer containing changes. Object Name Changes Some Logical Nodes, like MMXU, contain additional Data Attributes. The structure of objects has changed. Objects are still self-described by devices so clients can auto-detect object structure at run-time 14

15 UCA2.0 v.s. IEC61850 MMXU UCA2 IEC61850 Migration Impact on Clients Clients will see a different object structure and will need to select IEC61850 objects. Client report subscriptions may be impacted depending on device. Clients not using new services and do not hard code object names are not affected. Several IED vendors plan to support both. 15

16 IEC61850 Testing Conformance, Interoperability, and Certification The Ultimate Goal of Testing: Everything works as expected when systems are deployed in the field PROJECT SUCCESS 16

17 Vendor Commitment Committed to supporting standards Committed to working with others Committed to make products work What happens with disagreements? User Commitment Committed to understanding the standard Specification of products and systems Justification to realize benefits Appropriate application/realistic expectations Committed to using the standard How do users cooperate? 17

18 Interoperability Testing Verifies that devices and applications can communicate with each other. Fundamental expectation of all users. Does not verify conformance Both products could implement the same error Conformance Testing Verifies that a given device conforms to the standard. Conformance will result in increased likelihood of interoperability in the field. What happens if 2 conformant devices don t interoperate? 18

19 Certification A statement that tests have been run: Who ran the tests What tests have been run How the results were determined Certification must provide a quality assurance process to improve the testing and increase field interoperability What is More Important? PROJECT SUCCESS Commitment Conformance Interoperability Certification Quality Assurance Foundation 19

20 Testing Process IEC TC57 Working Groups Test Cases Standards Product Development Products Standards Committees Vendors Test Labs Users Test System Development Test Systems Test Laboratories Tested Products Projects Successful Systems What is the Foundation? UCA International Users Group Advancing Interoperability for the Utility Enterprise A non-profit users group 20

21 UCA International Users Group Certification of test procedures and systems Educational seminars and conferences Help desk for user assistance Gathering input for standards work Promotional activities UCA IUG Organization Advisors Board of Directors Operating Officers Executive Committee Technical Committee Marketing Liaison Membership IEC Working Groups & Task Force OpenDR Sub Committee OpenAMI Task Force Technical Publications Testing Help Desk 21

22 UCA IUG Quality Assurance Process Difficult to Coordinate Vendor Manufacturer System Integrator All Parties Need Feedback IEC TC57 Working Groups QAP Projects (Users) Test System Developers Realistic Coordination Test Laboratories IEC61850 Part 10 Conformance Testing Introduction Conformance Testing Definitions Quality Assurance Process Conformance Testing Procedures Test Cases for Servers Performance Testing Methodology Criteria 22

23 Some Definitions PICS: Protocol Implementation Conformance Statement Specifies what parts of the standard are implemented (e.g. ACSI services, etc.) MICS: Model Implementation Conformance Statement Specifies what portion of the model that are implemented (e.g. LNs, Data, attributes, etc.) PIXIT: Protocol Implementation extra Information for Testing Specifies information needed for testing that is outside the scope of IEC61850 (e.g. addresses, supported values, etc.) IEC Test Process Start Static Conformance Requirements PICS MICS Static Conformance Review Dynamic Conformance Requirements PIXIT Test Selection and Setup Conformance Test Suite/Cases Dynamic Tests Communication Testing Anomaly & Capability Testing Behavior Testing Review of Results Final Conformance Review Conclusion (Customer Sign-Off) Test Report Production Information Testing Interaction End Control Flow Data Flow 23

24 Test Architecture Communications Simulator Ethernet Hub Device Under Test Analyzer Time Master Equipment Simulator IEC Test Cases Test Cases Exist for: Server, Logical Device, Data, and Attribute models Data Set Model Setting Group Model Log Control Model Generic Object Oriented System Wide Events Control Model Substitution Model Transmission of Sample Values Time and Time Synchronization File Transfer Negative and Positive test cases 24

25 Sample Test Cases From IEC Sample Test Cases From IEC

26 Sample Test Cases From IEC Performance Testing Latency Measurements Time for device to transmit a process value Time for network to deliver the message Time required to deliver received message to device process logic Test Cases (for both input and output) GOOSE GSSE Sampled values Reports Controls 26

27 Acceptance Criteria Pass DUT behaves as specified by IEC61850 and PIXIT Fail DUT does not behave per IEC61850 and PIXIT Inconclusive Action need to resolve DUT must remain operational throughout tests Who Determines Pass/Fail? A Certification Body 27

28 UCA IUG Testing Committee Advisors Board of Directors Operating Officers Executive Committee Technical Committee Marketing Liaison Membership IEC Working Groups & Task Force OpenDR Sub Committee OpenAMI Task Force Technical Publications Testing Help Desk Inconclusive? Ambiguities in the DUT responses to test cases Ambiguities in the standard? A process for resolving Technical Issues (TISSUES) is needed. 28

29 TISSUE Process A TISSUE resolution process is in place to feed back user experience to improve the standard. TISSUE Membership UCA IUG Technical Committee Each part of the standard has a responsible GoE member identified Group Of Experts IEC TC57 WG10 29

30 TISSUE comment sheets Worksheets for open TISSUE under clarification only Comment Worksheets , 7-2, 7-3, Comment resolution sheets for clarified, accepted and voted TISSUES Comment sheets for preliminary proposal TISSUES UCAIug Comment resolution; , 7-2, 7-3, Preliminary proposals; , 7-2, 7-3, Only the green and yellow pages shall be available on the UCA website. One separate website section shall be established for each category. TISSUE Process Initiator s Could be a short term fix TISSUES 1st Proposal Final Proposal 100% approval Selected and distributed to the responsible member of GoE Resp. GoE member will create 1st proposal and distribute to all of GoE. After discussion a final proposal is distributed to TISSUES group for vote. green TISSUES yellow TISSUES IEC TC57 WG10 30

31 TISSUE Clarification Schedule Selecting 1st Proposal Final Proposal Voting Voted Veto 2 days 2 weeks 2 weeks 4 weeks Why Join? Support rigorous testing that will lower your cost of ownership. Participate in the standards process without the cost of attending IEC meetings. Vote on key technical issues important to your organization. Learn from others through participation. 31

32 Member Benefits Include Access to Working Documents Meeting Minutes Training Courses Demo Participation Help Desk Discussion Forum Voting Procedures 2005 Membership Fees Revenues $1 Billion $100 Million $10 Million $1 Million Membership Fees $5,000 $4,000 $3,000 $2,000 $1,000 Individual $250 32

33 Consider Joining Contribute to a community effort to improve implementation of IEC61850 Provide feedback into and learn about standards activities w/o joining IEC Who Needs to Join? Every small utility using IEC61850 should have at least one individual member for access to information. Every large utility should be a corporate member to participate in and influence the standard and user group processes. 33

34 Questions - Discussion WHAT? WHY? HOW? Thank You Ralph Mackiewicz SISCO, Inc ½ Mile Road Sterling Heights, MI USA Tel: x103 Fax: ralph@sisconet.com 34