1. Systems Integration Specialists Company, Inc. The Standards Based Integration Company © Copyright 2009 SISCO, Inc. IOP Status Report CIMug Meeting Margaret Goodrich, SISCO Inc Charlotte, NC November 11, 2009

2. © Copyright 2009 SISCO, Inc. 2 General Topics l Dynamics Project IOP l CDPSM IOP l Part 9 IOP

3. © Copyright 2009 SISCO, Inc. 3 Dynamics Project IOP l Project Introduction l Test Participants l Test Contents l Use of Profiles l Test Witnesses and Logistics

4. © Copyright 2009 SISCO, Inc. 4 Dynamics Project Introduction l EPRI Sponsored Project l Terry Saxton and Margaret Goodrich are Co- Directors of the Project l Project participants include Vendors and Utilities l Goal is to define and validate extensions to CIM for Dynamic Model Exchange and Dynamic Studies. l The Dynamics and Static model Profiles must contain sufficient information to allow Dynamic Study Analysis to be performed.

5. © Copyright 2009 SISCO, Inc. 5 Dynamics Project Introduction l Project includes:  Definition of new UML modeling methods  Definition of the CIM Extensions for Standard Dynamic Models  Definition of User Defined Dynamic Models  Planning and Execution of an IOP test to Validate the extensions

6. © Copyright 2009 SISCO, Inc. 6 Dynamics IOP Test Participants (Products) l DigSilent (PowerFactory) l GE Energy (PSLF) l RTE/Tractebel (Eurostag) l Siemens PTI (PSS/E)

7. © Copyright 2009 SISCO, Inc. 7 Dynamics IOP Test Contents l Full Model Exchange of Static Model (import and export) l Power Flow Solutions l Interoperation of full test models between two or more vendors l Exchange of Solution Files l Exchange of Dynamic Profiles l Dynamics Studies

8. © Copyright 2009 SISCO, Inc. 8 Dynamics IOP Test Contents – Model Exchange

9. © Copyright 2009 SISCO, Inc. 9 Dynamics IOP Test Contents – Solution Exchange

10. © Copyright 2009 SISCO, Inc. 10 Dynamics IOP – Use of Profiles l IOP will use 4 Profiles  Equipment  Topology  State Variables  Dynamics for both Standard and User Defined Models l Equipment, Topology and State Variables Profiles will be the same as was used in the UCTE IOP last March.

11. © Copyright 2009 SISCO, Inc. 11 Dynamics IOP – UCTE Profiles

12. © Copyright 2009 SISCO, Inc. 12 Dynamics IOP – Test Witnesses and Logistics l Test Witnesses  David Bogen, Oncor  Pamela McClean, AESO  Chavdar Ivanov, ENTSO-E  Margaret Goodrich, SISCO l Logistics  Location – EPRI Offices, Dallas, TX  Dates – Nov. 16 through Nov. 19

13. © Copyright 2009 SISCO, Inc. 13 Part 13 CDPSM IOP l Participants l Profiles Used l Tests Contents l Test Witnesses l Logistics

14. © Copyright 2009 SISCO, Inc. 14 CDPSM IOP Test Participants l EDF l GE l EPRI (OpenDSS) by Tom McDermott l Current Group (by Rod Frowd) l SISCO

15. © Copyright 2009 SISCO, Inc. 15 CDPSM IOP Profiles l Three Profiles – All Full Model Single Profile Documents  CDPSM for Balanced Network Model  CDPSM for Unbalanced Network Model  GIS Connectivity Network Model

16. © Copyright 2009 SISCO, Inc. 16 CDPSM IOP Test Contents l Tests Include:  Full Model Exchange between two DMS systems  Full Model Exchange from a GIS System to a DMS  Interoperation of full test models between two or more vendors  Incremental Model Exchange between two DMS systems  Incremental Model Exchange between a GIS and a DMS  Power Flow Solution for Balanced and Unbalanced Network Models.

17. © Copyright 2009 SISCO, Inc. 17 CDPSM IOP Test Contents Data Exchange Test Cases – GIS Focus 61968-13 – CDPSM exchange, GIS focus in 2009

18. © Copyright 2009 SISCO, Inc. 18 CDPSM IOP Test Contents Data Exchange Test Cases – DMS Model Exchange Focus Exchange of CDPSM * (similar to today’s CPSM inter-op tests) *Common Distribution Power System Model (CDPSM) – IEC 61968-13 standard

19. © Copyright 2009 SISCO, Inc. 19 CDPSM IOP Test Witnesses & Logistics l Test Witnesses  David Bogen, Oncor  Margaret Goodrich, SISCO l Logistics  Location – Oncor, Dallas, TX  Dates – Nov. 30 through Dec. 3rd

20. © Copyright 2009 SISCO, Inc. 20 Part 9 IOP l Introduction l Testing Infrastructure Overview l Test Participants l Test Contents l Test Issues  Controls and Events  Metering Systems  Asynchronous Replies l Enumerations l Test Witness GUI Slides l Test Schedule

21. © Copyright 2009 SISCO, Inc. 21 Introduction l Test is Sponsored by EPRI l Scott Neumann and Margaret Goodrich are Co- Directors l First IOP for WG14 l First Messaging Test l First Test using ESB l First Test Remotely

22. © Copyright 2009 SISCO, Inc. 22 Testing Infrastructure Overview l UISOL test bus is based upon EPRI TR 1018795 and IEC 61968-1 l Participant products remotely connect to bus using internet as clients, servers and/or listeners l Test witnesses monitor tests using web browser Slide Courtesy of UISOL

23. © Copyright 2009 SISCO, Inc. 23 Test Participants l Ecologic l EDF l Elster l GE l Grid Net l Itron l L&G l Telvent

24. © Copyright 2009 SISCO, Inc. 24 Test Contents - Messages l MeterReading l EndDeviceEvents l EndDeviceControls l EndDeviceAssets l CustomerMeterDataSet l MeterReadSchedule

25. © Copyright 2009 SISCO, Inc. 25 Test Contents RequestsEvents getcreate upda te delet e canc el clos ecreated upd ate d delet ed cancele dclosed MeterReadings X - X - X - X - X - X X - X - X - X - X X - X - X - X - X - X EndDeviceEventsX - XX - X - X - XXXX X - X - X - X - X - X EndDeviceControlsXX - X - XXX X - X EndDeviceAssetsXX X - X CustomerMeterDataSetX - XX X MeterReadScheduleX - X - X - X XX X - X - X X - X Green = ElsterRed = L&GBlue = EcologicMauve - GEOrange - ItronBrown - Grid NetBlack - EDF

26. © Copyright 2009 SISCO, Inc. 26 Controls and Events Slide Courtesy of UISOL

27. © Copyright 2009 SISCO, Inc. 27 Controls and Events 1. Client process issues request to MS as ‘create EndDeviceControls’, where each EndDeviceControl has a unique mRID (using a GUID) 2. MS replies to client synchronous, as ‘reply EndDeviceControls’ 3. Event published ‘created EndDeviceControls’ to notify potentially interested clients that a control has been requested or scheduled 4. MS processes control request issuing messages to end devices as needed (the messaging and processing sequences here are outside the scope of 61968-9) 5. Consequences of controls may be reported to metering system from end devices 6. Events published ‘created EndDeviceEvents’ to notify potentially interested clients, where if possible, the mRID for each EndDeviceEvent should use the mRID from the corresponding EndDeviceControl Slide Courtesy of UISOL

28. © Copyright 2009 SISCO, Inc. 28 Metering Systems Slide Courtesy of UISOL

29. © Copyright 2009 SISCO, Inc. 29 Metering Systems 1. Meter readings are collected by metering system 2. Metering system publishes messages using ‘created MeterReadings’ to potentially interested clients 3. Some of the information collected from meters may be events, or may cause events to be inferenced and reported using ‘created EndDeviceEvents’ Slide Courtesy of UISOL

30. © Copyright 2009 SISCO, Inc. 30 Asynchronous Replies Slide Courtesy of UISOL

31. © Copyright 2009 SISCO, Inc. 31 Asynchronous Replies 1. Client (e.g. MDM) may request meter readings from metering system using ‘get MeterReadings’ 2. Metering system replies to client synchronously using ‘reply MeterReadings’ with whatever data is available that is relevant to the request if it chooses 3. Meters may later return the desired data to metering system 4. Metering system replies asynchronously to client using ‘reply MeterReadings’ to specified reply topic/queue and correlation ID used on initial request 5. Metering system may also publish data using ‘created MeterReadings’ to any potentially interested client Slide Courtesy of UISOL

32. © Copyright 2009 SISCO, Inc. 32 More on Asynchronous Replies l Client responsibilities:  CorrelationID in header must be used to allow client to correlate multiple replies to an initial request  AsyncReplyFlag in header should be set to true  ReplyAddress should identify topic/queue to be used for asynchronous replies l Server responsibilities:  Server (e.g. metering system) must be will to dedicate a thread or process to process the request asynchronously  Server must send replies to the designated destination with the appropriate correlationID as initially supplied by the client  All but last reply should use ‘PARTIAL’ for the ReplyCode  Last reply should use ‘OK’ for the ReplyCode Slide Courtesy of UISOL

33. © Copyright 2009 SISCO, Inc. 33 Reading Types l 61968-9 Annex C l Needed for MeterReadings message l Populated as the value for the ‘ref’ attribute in ReadingType structure l Population of the ReadingTypes list in the MeterReadings structure is optional mRIDDescription 2.6.7.1.0.12.0.0.0.3.7215-minute Incremental IntervalData Forward Energy (kWh) 4.6.4.0.2.8.0.0.0.0.11124-hour Incremental DeltaData IEEE1366MomentaryInterruption (Count) 7.6.7.1.0.12.0.0.0.3.7260-minute Incremental IntervalData Forward Energy (kWh) 0.0.0.0.0.011.0.0.0.0.109Energization status 0.0.6.0.0.54.0.0.0.0.29Indicating Voltage (V) 0.0.1.1.0.12.0.0.0.3.72BulkQuantity Forward Energy (kWh) Slide Courtesy of UISOL

34. © Copyright 2009 SISCO, Inc. 34 Quality Codes l 61968-9 Annex D l Used to populate ‘quality’ element in ReadingQualities structure l Readings are assumed to be valid unless reading quality is specified mRIDDescription NullAssumed valid 1.0.0Data valid 1.4.5Test data 2.3.4Reverse rotation 1.5.257Error code 1.4.4Skipped interval Slide Courtesy of UISOL

35. © Copyright 2009 SISCO, Inc. 35 Event Types l 61968-9 Annex E l Used to populate ‘category’ of EndDeviceEvent structure l Important not to confuse event codes with reply codes CategoryDescription 3.26.9.185 Power off alarm 3.26.9.216 Power on 6.38.1.150 Low voltage 6.38.9.150 Low voltage cleared 6.38.1.93High voltage 6.38.9.93High voltage cleared 7.1.1.2Unauthorized Access attempt 3.33.1.257 Tamper detection 2.2.1.17 Battery failed 3.8.6.61Demand reset 3.31.6.11Armed for closure 3.31.6.68Disconnected 3.31.6.42Reconnected Slide Courtesy of UISOL

36. © Copyright 2009 SISCO, Inc. 36 Control Types l 61968-9 Annex F l Used to populate ‘type’ in EndDeviceControl structure TypeDescription 3.8.6.61 Demand reset 3.15.6.242.0 Load control started 3.15.6.243.1 Load control stopped 3.31.6.42Close remote connect/disconnect switch 3.31.6.66 Disable RCD Switch 3.31.6.68Open remote connect/disconnect switch 3.31.6.76Enable RCD switch 3.34.6.201Price signal Slide Courtesy of UISOL

37. © Copyright 2009 SISCO, Inc. 37 Test Witness GUI Slides 37 Slide Courtesy of UISOL

38. © Copyright 2009 SISCO, Inc. 38 Test Witness GUI Slides 38 Slide Courtesy of UISOL

39. © Copyright 2009 SISCO, Inc. 39 Test Witness GUI Slides Slide Courtesy of UISOL

40. © Copyright 2009 SISCO, Inc. 40 Test Schedule l All Connectivity testing between Vendor and ESB by November l Dry Run Test – Dec. 15-16, 2009 l Actual Test – Jan 5-6, 2010

41. © Copyright 2009 SISCO, Inc. 41 Questions ??????