1. CIM Test Development Process
John Simmins
Weekly Status and Planning Meeting 3/01/2011

2. Agenda Progress since last meeting
Issues, opportunities and risks arising during the previous week
Verify progress against stakeholder expectations
General issues discussion
Action items for individuals
Expected work output during next week
Standing agenda 2

3. Testing Project Plan

4. Progress Since Last Call
Organized briefings for OpenSG
SOW task to coordinate with Enterprise and Edge Conformity groups
Multiple briefings scheduled
Intro to CIM EPRI test effort, approximately 30 minutes at SG Conformity initial session, Tuesday 10:30 -12:00. Bruce leading.
Detailed CIM EPRI briefing, 2 hours at SG Systems OpenAMI-Ent session, Tuesday 1:00 -3:00. Kay leading.
Application of EPRI CIM test methodology to OpenADR/OpenADE, tdb minutes at Enterprise/Edge Conformity, Tuesday 3:30 – 5:30. Mark leading.
Working session: Applying EPRI CIM test methodology to OpenADR, 1.5 hours Thursday at 10:30 – 12:00. Albert Chiu and Bruce leading.
Preparing briefing for Spring 2011 CIM Users Group
SOW task to coordinate with CIM User’s Group Interoperability group
Submitting topic under call for presentations
10-13 May 2011, Prague, Czech Republic . John will present
Summary of recent activities and of the test procedures 4

5. Progress Since Last Call (continued)
Talking to venders about participating in dry runs
Actions needed:
Provide instructions for a test using EPRI/Consumers servers
Setup virtual services on Amazon
Provide test harness capable of sending Part-9 message set
EndDeviceEvent, EndDeviceControl, MeterReadSchedule, MeterServiceRequest, MeterReadings
Consider weekly meeting for
Venders with implemented CIM messages
Telvent, Oracle, Siemens, GE Energy
Issue invite to all interested venders
Send each vender a test package
Quick start instruction set (XSDs, WSDLs, sample messages)
Reference material (use cases, requirements, etc.)
Summary of recent activities and of the test procedures 5

6. Progress Since Last Call (continued)
Minor modifications to test procedures for consistency
Format and wording changes
Task 3 Spreadsheet Mapping
Business Proc To Test Mapping (first tab)
Business services
Test Procedures
Service Operations
Messages
XSDs
Requirements Cross Reference (second tab)
Requirements to Test Procedures mapping
Summary of recent activities and of the test procedures 6

7. Task 3 Mapping Spreadsheet
Sample showing 4 test procedures
Business Process
Use Case
Test Procedures
Schedule Meter Reads
SCE B1 - Multiple Clients Read Demand and Energy Data Automatically from Customer Premises
2.01 Scheduled Meter Read Nominal Interoperability Scheduled Meter Read System Errors
Query Meter On-Demand
2.03 On Demand Meter Read Nominal Interoperability On Demand Meter Read System Errors

8. Task 3 Mapping Spreadsheet (cont)
Sample showing 4 test procedures
Test Procedures
Service Operations
Message
Payload XSD
2.01 Scheduled Meter Read Nominal Interoperability Scheduled Meter Read System Errors
Create Reply Created
MeterReadSchedule MeterReadSchedule MeterReadings
MeterReadSchedule (Message) MeterReadings
2.03 On Demand Meter Read Nominal Interoperability On Demand Meter Read System Errors
Get? Create? Reply? Created?
MeterReadings MeterReadings
GetMeterReading? ReplyMeterReading?

9. Requirements Mapping (selected sample)
Test Procedure
Requirements
ECITP 2.01
CIM v1.0 - The MeterReadSchedule message shall contain a valid subset of information data items specified in IEC part9: MeterReadSchedule message type.
CIM v1.0 - The MeterReadSchedule message shall be formatted in accordance with the standard MeterReadings XSD.
SCE Use Case B1 vers REQ The Meter Data Unification System shall record the source of all meter data. See
SCE Use Case B1 vers REQ Meter Data Unification System shall be able to remotely manage work load and priority of ad hoc and routine requests for usage data to provide reasonable system response time.
AMI ENT Requirement REQ-B1004-Send a scheduled meter reading

10. Issues Recommended Resolution
Recommended CIM versions to use as baseline
Enterprise Architect (EA) Universal Model Language (UML) models
Model Manager responsible for posting official version
1 January 2011 version
XML Schema Definitions (XSDs) use Part-9 and newer as available
Web Service Definitions (WSDLs) use OpenSG version
Separate Part 9 UML/XML tests from Part 1 tests
Using WSDLs to execute tests
Not validating WSDL format
Issues to discuss 10

11. Opportunities arising during the Previous Week
XSDs version identification
Message XSD version is 1.0.0
Both Part 1 and Part 9 undergoing revisions
Part 9 payload XSD’s have no version id
Recommend
Increment because fielded systems implemented earlier XSDs
Add version ID for Part 9 XSDs
CIM Part 1 and Part 9 loose coupling
Specification incorporate loose coupling of service patterns and UML/XML
EPRI CIM tests follow decoupled approach per IEC 61986/61970
Separate tests for meter Part 1 (web services) and Part 9 (meter reading)

12. On-Demand Meter Read Messages Names Needs Clarification
Should these be Get/Reply
messages/operations?
Figure 25 – Example on-request meter read exchange Source: 2009 published version of IEC Part-9

13. Part 1 Message Structure

14. Part 1 Message Structure (continued)

15. Open Action Items Assignee Action Status John Simmins
Work with internal resources to separate lab network completely from the EPRI operational network.
In process
Mark Ortiz
Set up EPRI server at EPRI.
Provide written procedures on access to Consumer’s DMZ network and server
Kay Stefferud
Contract Mark Ortiz to request written procedures to access the Consumers server.
Margaret Goodrich
Review sample abstract test case.
Send Kay excel spreadsheet with test set-up information.
Vet set of Part-9 interoperability requirements with Consumers and SCE.
Provide recommendation on which version of the Part 9 to use as a baseline for the EPRI CIM testing.
Presented today.
Kay Stefferud,
Bruce Muschlitz
Review the services used in the test procedures and verify that the services referenced are correct
Status of action items generated from each weekly meeting. We can discuss status now or else please send an to the group with the completed action item information. 15

16. Expected Work Output During the Next Week
Contact venders per plan
Test packages for venders
Prepare briefings for OpenSG meeting next week 16

17. Together…Shaping the Future of Electricity