1 / 10

CIM Test Development Process

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

tarmon
Télécharger la présentation

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 Meeting3/29/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 Working on the wording for the dry run test participation Mark Ortiz furnished VPN client for Consumers server Windows 64 bit version available EPRI FTP site Windows 32 bit version also needed Mark Ortiz walked through the creation of the CIM Message and EndDeviceControl payload XSD

  4. CIM Common Message Structure

  5. UML for EndDeviceControls Messages

  6. Sample EndDeviceEventsMessage XSD <?xml version="1.0" encoding="utf-8"?> <xs:schema xmlns="http://www.iec.ch/TC57/2010/EndDeviceEventsMessage" xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns:msg="http://www.iec.ch/TC57/2010/schema/message" xmlns:obj="http://iec.ch/TC57/2010/EndDeviceEvents#" targetNamespace="http://www.iec.ch/TC57/2010/EndDeviceEventsMessage" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1.0.0"> <!-- Base Message Definitions --> <xs:import namespace="http://www.iec.ch/TC57/2010/schema/message" schemaLocation="Message.xsd"/> <!-- CIM Information Object Definition --> <xs:import namespace="http://iec.ch/TC57/2010/EndDeviceEvents#" schemaLocation="EndDeviceEvents.xsd"/> <!-- PayloadType Definition --> <xs:complexType name="EndDeviceEventsPayloadType"> <xs:sequence> <xs:element ref="obj:EndDeviceEvents"/> <xs:element name="OperationSet" type="msg:OperationSet" minOccurs="0"/> <xs:element name="Compressed" type="xs:string" minOccurs="0"> <xs:annotation> <xs:documentation>For compressed and/or binary, uuencoded payloads</xs:documentation> </xs:annotation> </xs:element> <xs:element name="Format" type="xs:string" minOccurs="0"> <xs:annotation> <xs:documentation>Hint as to format of payload, e.g. XML, RDF, SVF, BINARY, PDF, ...</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType>>

  7. <!-- Message Types --> <!-- RequestMessageType --> <xs:complexType name="EndDeviceEventMessageRequestMessageType"> <xs:sequence> <xs:element name="Header" type="msg:HeaderType"/> <xs:element name="Request" type="msg:RequestType" minOccurs="0"/> <xs:element name="Payload" type="EndDeviceEventMessagePayloadType" minOccurs="0"/> </xs:sequence> </xs:complexType> <!-- ResponseMessageType --> <xs:complexType name="EndDeviceEventMessageResponseMessageType"> <xs:sequence> <xs:element name="Header" type="msg:HeaderType"/> <xs:element name="Reply" type="msg:ReplyType"/> <xs:element name="Payload" type="EndDeviceEventMessagePayloadType" minOccurs="0"/> </xs:sequence> </xs:complexType> <!-- EventMessageType --> <xs:complexType name="EndDeviceEventMessageEventMessageType"> <xs:sequence> <xs:element name="Header" type="msg:HeaderType"/> <xs:element name="Payload" type="EndDeviceEventMessagePayloadType" minOccurs="0"/> </xs:sequence> </xs:complexType> <!-- FaultMessageType --> <xs:complexType name="EndDeviceEventMessageFaultMessageType"> <xs:sequence> <xs:element name="Reply" type="msg:ReplyType"/> </xs:sequence> </xs:complexType> <xs:element name="CreateEndDeviceEventMessage" type="EndDeviceEventMessageRequestMessageType"/> <xs:element name="ChangeEndDeviceEventMessage" type="EndDeviceEventMessageRequestMessageType"/> <xs:element name="CancelEndDeviceEventMessage" type="EndDeviceEventMessageRequestMessageType"/> <xs:element name="CloseEndDeviceEventMessage" type="EndDeviceEventMessageRequestMessageType"/> <xs:element name="DeleteEndDeviceEventMessage" type="EndDeviceEventMessageRequestMessageType"/> <xs:element name="CreatedEndDeviceEventMessage" type="EndDeviceEventMessageEventMessageType"/> <xs:element name="ChangedEndDeviceEventMessage" type="EndDeviceEventMessageEventMessageType"/> <xs:element name="CanceledEndDeviceEventMessage" type="EndDeviceEventMessageEventMessageType"/> <xs:element name="ClosedEndDeviceEventMessage" type="EndDeviceEventMessageEventMessageType"/> <xs:element name="DeletedEndDeviceEventMessage" type="EndDeviceEventMessageEventMessageType"/> <xs:element name="EndDeviceEventMessageResponseMessage" type="EndDeviceEventMessageResponseMessageType"/> <xs:element name="EndDeviceEventMessageFaultMessage" type="EndDeviceEventMessageFaultMessageType"/> </xs:schema> <!-- Message Types --> <!-- RequestMessageType --> <xs:complexType name="EndDeviceEventMessageRequestMessageType"> <xs:sequence> <xs:element name="Header" type="msg:HeaderType"/> <xs:element name="Request" type="msg:RequestType" minOccurs="0"/> <xs:element name="Payload" type="EndDeviceEventMessagePayloadType" minOccurs="0"/> </xs:sequence> </xs:complexType> <!-- ResponseMessageType --> <xs:complexType name="EndDeviceEventMessageResponseMessageType"> <xs:sequence> <xs:element name="Header" type="msg:HeaderType"/> <xs:element name="Reply" type="msg:ReplyType"/> <xs:element name="Payload" type="EndDeviceEventMessagePayloadType" minOccurs="0"/> </xs:sequence> </xs:complexType> <!-- EventMessageType --> <xs:complexType name="EndDeviceEventMessageEventMessageType"> <xs:sequence> <xs:element name="Header" type="msg:HeaderType"/> <xs:element name="Payload" type="EndDeviceEventMessagePayloadType" minOccurs="0"/> </xs:sequence> </xs:complexType> <!-- FaultMessageType --> <xs:complexType name="EndDeviceEventMessageFaultMessageType"> <xs:sequence> <xs:element name="Reply" type="msg:ReplyType"/> </xs:sequence> </xs:complexType> <xs:element name="CreateEndDeviceEventMessage" type="EndDeviceEventMessageRequestMessageType"/> <xs:element name="ChangeEndDeviceEventMessage" type="EndDeviceEventMessageRequestMessageType"/> <xs:element name="CancelEndDeviceEventMessage" type="EndDeviceEventMessageRequestMessageType"/> <xs:element name="CloseEndDeviceEventMessage" type="EndDeviceEventMessageRequestMessageType"/> <xs:element name="DeleteEndDeviceEventMessage" type="EndDeviceEventMessageRequestMessageType"/> <xs:element name="CreatedEndDeviceEventMessage" type="EndDeviceEventMessageEventMessageType"/> <xs:element name="ChangedEndDeviceEventMessage" type="EndDeviceEventMessageEventMessageType"/> <xs:element name="CanceledEndDeviceEventMessage" type="EndDeviceEventMessageEventMessageType"/> <xs:element name="ClosedEndDeviceEventMessage" type="EndDeviceEventMessageEventMessageType"/> <xs:element name="DeletedEndDeviceEventMessage" type="EndDeviceEventMessageEventMessageType"/> <xs:element name="EndDeviceEventMessageResponseMessage" type="EndDeviceEventMessageResponseMessageType"/> <xs:element name="EndDeviceEventMessageFaultMessage" type="EndDeviceEventMessageFaultMessageType"/> </xs:schema> Sample EndDeviceEventMessage XSD (cont) • <!-- Message Types --> • <!-- RequestMessageType --> • <xs:complexType name="EndDeviceEventMessageRequestMessageType"> • <xs:sequence> • <xs:element name="Header" type="msg:HeaderType"/> • <xs:element name="Request" type="msg:RequestType" minOccurs="0"/> • <xs:element name="Payload" type="EndDeviceEventMessagePayloadType" minOccurs="0"/> • </xs:sequence> • </xs:complexType> • <!-- ResponseMessageType --> • <xs:complexType name="EndDeviceEventMessageResponseMessageType"> • <xs:sequence> • <xs:element name="Header" type="msg:HeaderType"/> • <xs:element name="Reply" type="msg:ReplyType"/> • <xs:element name="Payload" type="EndDeviceEventMessagePayloadType" minOccurs="0"/> • </xs:sequence> • </xs:complexType> • <!-- EventMessageType --> • <xs:complexType name="EndDeviceEventMessageEventMessageType"> • <xs:sequence> • <xs:element name="Header" type="msg:HeaderType"/> • <xs:element name="Payload" type="EndDeviceEventMessagePayloadType" minOccurs="0"/> • </xs:sequence> • </xs:complexType> • <!-- FaultMessageType --> • <xs:complexType name="EndDeviceEventMessageFaultMessageType"> • <xs:sequence> • <xs:element name="Reply" type="msg:ReplyType"/> • </xs:sequence> • </xs:complexType> • <xs:element name="CreateEndDeviceEventMessage" type="EndDeviceEventMessageRequestMessageType"/> • <xs:element name="ChangeEndDeviceEventMessage" type="EndDeviceEventMessageRequestMessageType"/> • <xs:element name="CancelEndDeviceEventMessage" type="EndDeviceEventMessageRequestMessageType"/> • <xs:element name="CloseEndDeviceEventMessage" type="EndDeviceEventMessageRequestMessageType"/> • <xs:element name="DeleteEndDeviceEventMessage" type="EndDeviceEventMessageRequestMessageType"/> • <xs:element name="CreatedEndDeviceEventMessage" type="EndDeviceEventMessageEventMessageType"/> • <xs:element name="ChangedEndDeviceEventMessage" type="EndDeviceEventMessageEventMessageType"/> • <xs:element name="CanceledEndDeviceEventMessage" type="EndDeviceEventMessageEventMessageType"/> • <xs:element name="ClosedEndDeviceEventMessage" type="EndDeviceEventMessageEventMessageType"/> • <xs:element name="DeletedEndDeviceEventMessage" type="EndDeviceEventMessageEventMessageType"/> • <xs:element name="EndDeviceEventMessageResponseMessage" type="EndDeviceEventMessageResponseMessageType"/> • <xs:element name="EndDeviceEventMessageFaultMessage" type="EndDeviceEventMessageFaultMessageType"/> • </xs:schema>

  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 General Message available Sample of payload needed Process to connect multiple test sites needs to be dry run

  10. Together…Shaping the Future of Electricity

More Related