1 / 10

CIM Test Development Process

CIM Test Development Process. John Simmins Weekly Status and Planning Meeting 4/12/2011. Agenda. Progress since last meeting Issues, opportunities and risks arising during the previous week Verify progress against stakeholder expectations General issues discussion

leehicks
Download Presentation

CIM Test Development Process

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. CIM Test Development Process John Simmins Weekly Status and Planning Meeting4/12/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

  3. Progress Since Last Call 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

  4. Progress Since Last Call Sample / Instance example Outage message created Issues noted Shawn Hu from eXtensible created outage message Discuss later in briefing

  5. Instance Sample Outage Message Header —Shawn Hu <?xml version="1.0" encoding="UTF-8"?> <CreatedEndDeviceEvents xsi:schemaLocation="http://www.iec.ch/TC57/2010/EndDeviceEventsMessage EndDeviceEventsMessage.xsd" xmlns="http://www.iec.ch/TC57/2010/EndDeviceEventsMessage" xmlns:obj="http://iec.ch/TC57/2010/EndDeviceEvents#" xmlns:msg="http://www.iec.ch/TC57/2010/schema/message" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <Header> <msg:Verb>created</msg:Verb> <msg:Noun>EndDeviceEvents</msg:Noun> <msg:Context>TESTING</msg:Context> <msg:Timestamp>2011-04-12T10:00:00Z</msg:Timestamp> <msg:Source>HE-001</msg:Source> <msg:ReplyAddress>Not Applied</msg:ReplyAddress> <msg:AckRequired>true</msg:AckRequired> <msg:MessageID>ABC-123</msg:MessageID> <msg:CorrelationID></msg:CorrelationID> <msg:Comment>created end device events for testing</msg:Comment> </Header>

  6. Instance Sample Outage Message Payload —Shawn Hu <Payload> <obj:EndDeviceEvents> <obj:EndDeviceEvent> <obj:createdDateTime>2011-04-12T09:30:30Z</obj:createdDateTime> <obj:reason>Electric Meter Power Out</obj:reason> <obj:Assets> <obj:mRID>3dc53ee5-777e-50b4-8699-a1c224f45f3d</obj:mRID> <obj:Names> <obj:name>Meter23253</obj:name> </obj:Names> </obj:Assets> <obj:EndDeviceEventType ref="3.26.0.85"></obj:EndDeviceEventType> <obj:status> <obj:dateTime>2011-04-12T08:35:47Z</obj:dateTime> <obj:value>Electric meter power out</obj:value> </obj:status> </obj:EndDeviceEvent> </obj:EndDeviceEvents> </Payload>

  7. Outage Message Plan to move forward • 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

  8. Open Action Items

  9. 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

  10. Together…Shaping the Future of Electricity

More Related