CIM Testing Procedure Development

CIM Testing Procedure Development

EPRI Project 071103

CIM Testing Procedure Development

Minutes of the CIM Test Procedures Teleconference

Held on 12 April 2011 (2:00-3:00EST)

Meeting Summary

Weekly meeting of the EPRICIM Testing Procedure Development. Representatives from EPRI, Consumers, IBM, Guiding Principle, Xtensible, and EnerNex attended.

Good discussion today on the technical details including pmessage XML contents. Shawn Hu from eXtensible discussed the Outage message formats including the header and payload. Marilza Maia from IBM discussed some of the implementation details from the Paris IOP.

Agenda

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

Participants

The following people participated in the Teleconference:

Name / Company
Mark Ortiz / Consumers
Marilza Maia / IBM
Gerald Gray / Guiding Principle
Kay Stefferud / EnerNex
John Simmins / EPRI
Bruce Muschlitz / EnerNex
Shaun Hu / Xtensible

Progress since last meeting

•Sample vender package for outage test procedure

–Single file with all data needed

–Designed for venders to participate in dry run

–Specific test steps for each system under test

•OMS

•MDMS

•Head End

–Still needed

•Vetted sample outage message

•Instructions to create outage

•Test system login Sample / Instance example Outage message created

–Issues noted

–Shawn Hu from eXtensible created outage message

  • Briefing posted at

Issues arising during the previous week

Discussion centered on details of the sample messages, IOP use of header data in the recent Paris IOP, need to validate the message pattern and sequence diagrams and the need to review message content with the relevant vendors.

It was noted that some header fields in the IOP had vendor-specific content. Most (all) responders copy the incoming {MessageID} field into the outgoing CorrelationID field.

Some responder vendors also put “special stuff” into the {MessageID} field (because the listener should treat that as a don’t-care field).

Plan to move forward with the Sample Outage Message

Verify progress against stakeholder expectations

No change from last week.

Expected Work Output During the Next Week

•Meeting with Consumers (Mark) and EnerNex (Kay)

–Consumer server login process

•Continue Sample Messages

–Sample message from IOP would be helpful

•Process to connect multiple test sites needs to be dry run

Plan to move forward with the Outage Message

•Start with Instance/Sample message

•Describe content/format as required

•Include in vender package

•Review and vet message with venders as required

–OMS

–MDMS

–Head End

–Meter

•Shawn to provide multiple meter outage message sample (action completed same day as the meeting)

Open Action Items for Individuals

Assignee / Action / Status
John Simmins / Work with internal resources to separate lab network completely from the EPRI operational network. / COMPLETED
Mark Ortiz / Provide written procedures on access to Consumer’s DMZ network and server / COMPLETE
Kay Stefferud / Contract Mark Ortiz to request written procedures to access the Consumers server. / COMPLETE
Margaret Goodrich / Review sample abstract test case. / In process
Mark Ortiz / Send Kay excel spreadsheet with test set-up information. / COMPLETE

Action items for individualsnew and from previous weeks

AI # / Assignee / Action / Status
1 / John Simmins / Talk to Elster, Telvent, InterGraph, MillSoft. / Complete
2 / Mark Ortiz / Have Shawn Hu send ADR/ADE info links. / Complete
3 / Kay Stefferud / Update Abstract Use Case with features from the Ft. Lauderdale abstract use case / Complete
4 / Clint Powell / Find SCE representative for this group / Complete
5 / Bruce Muschlitz / Add , , to meeting minutes. / Complete
6 / Bruce Muschlitz / Provide reference to X291 companion specs to be added to abstract test cases. / Complete
7 / Kay Stefferud / Request CIM IOP IPR restrictions from IOP team. List, monitor and address set of network issues arising from connecting external vender servers to the Consumers and EPRI servers. Add SOW task references to schedule presented next week. / Complete
8 / Mark Ortiz / Send Kay excel spreadsheet with test Point of Contact (POV) information. / Complete
9 / Kay Stefferud / Update concrete test procedures to include these four changes:
1. Add test data sets
2. Recording of data during test
3.Show both IEC functions and utility systems in sequence diagrams.
4. Change log title to Test Procedure / Complete
10 / Brad Singletary / Send Site Guide to Frank at AEP. / Complete
11 / Kay Stefferud/ John Simmins / Schedule PMO meeting with John Simmins, Robert Sarfi, Kay Stefferud and Bruce Muschlitz / Complete
12 / Bruce Muschlitz / ADR/ADE link to group, part of these notes. / Complete
13 / John Simmins / Work with internal resources to separate lab network completely from the EPRI operational network. / Complete
14 / Mark Ortiz / Set up EPRI server at EPRI. / Complete
15 / Mark Ortiz / Provide written procedures on access to Consumer’s DMZ network and server / Complete
16 / Kay Stefferud / Contract Mark Ortiz to request written procedures to access the Consumers server. / Complete
17 / Margaret Goodrich / Review sample abstract test case. / In process
18 / Mark Ortiz / Send Kay excel spreadsheet with test set-up information. / Complete
19 / Kay Stefferud / Vet set of Part-9 interoperability requirements with Consumers and SCE. / In process
20 / Kay Stefferud / Provide recommendation on which version of the Part 9 to use as a baseline for the EPRI CIM testing. / Complete
21 / Kay Stefferud, Bruce Muschlitz / Review the services used in the test procedures and verify that the services referenced are correct / Complete

20110412CIM Testing Meeting Notes.docPage 1 of 4