October 19, 2009OpenSG - AMI-ENTERPRISE1 The Framework, Standards, and Plans AMI-Enterprise Service Definition Team

Introduction The service definition process (high level view) IEC CIM alignment Future Plans October 19, 2009OpenSG - AMI-ENTERPRISE2

October 19, 2009OpenSG - AMI-ENTERPRISE3 The Process Use Cases Business Processes Integration Requirements Services WSDLs XSDs System Requirements Specification For more info: smartgridipedia.org: HOW-TO service definition document 30,000 ft Level

October 19, 2009OpenSG - AMI-ENTERPRISE4 The Process Logical model input & development Identification of integration requirements Pattern naming Information objects Artifact generation Posting Issue generation and resolution Versioning

October 19, 2009OpenSG - AMI-ENTERPRISE5 Logical Model Input IEC and Multispeak are the primary model inputs Use case contributions from SCE, Consumers Energy Up Coming additions: PHEV, OpenADE, OpenADR

SDO – User Group Relationship Iterative process Analogy – early browser development October 19, 2009OpenSG - AMI-ENTERPRISE6 SDO User Community Thou shalt... Yes and... OpenSG example First pass – IEC CIM draft XSD as informative Now – XSD as normative Feedback

IEC CIM Alignment Consistent –some features of the spec, and in accordance, but also some additional features Compliant – some of spec not implemented, but what is implemented is in accordance Conformant – All features of spec implemented, but some additional features that are not conformant Fully Conformant – full correspondence between the spec and implementation. October 19, 2009OpenSG - AMI-ENTERPRISE7. - Specification - Implementation Irrelevant. Consistent. Compliant. Conformant. Fully Conformant Adapted from TOGAF 9

October 19, 2009OpenSG - AMI-ENTERPRISE8 Logical Model Development Standardized actors from AMI-ENT SRS Document business process in use cases and activity diagrams

October 19, 2009OpenSG - AMI-ENTERPRISE9 Identify Integration Requirements Simply where a process flow crosses an actor boundary

October 19, 2009OpenSG - AMI-ENTERPRISE10 Harmonize Integration Requirements Compare integration requirements and look for commonality: –Common actors –Common consumers –Common providers –Common information objects Eliminate duplicates, refine integration requirements

October 19, 2009OpenSG - AMI-ENTERPRISE11 Patterns – Using CIM Verbs Pattern naming allows for both ESB and non-ESB (point-to- point) architectural assumptions Verbs and Information objects are based IEC Verb examples: –Create, Created –Send, Reply Information Object examples: –EndDeviceAsset –MeterSystemEvent –MeterReading e.g. CreatedMeterReading

October 19, 2009OpenSG - AMI-ENTERPRISE12 Artifacts & Versioning Information objects are modeled in UML using Sparx EA. 1.IEC CIM is used as a Reference Model 2.Classes and attributes are selected and transformed into Semantic Model 3.Each context folder contains an entity class diagram that lists all entities that are used to describe an information object. 4.A model driven application tool is used to automatically generate XSDs (implementation). WSDL version control An XSD is imported in a WSDL for data type definition. Two namespaces (XSD & WSDL) exist in a WSDL definition as shown below: targetNamespace=" xmlns:typeOrig="

October 19, 2009OpenSG - AMI-ENTERPRISE13 Notification Subscribe to the Listserv – Send listserv When new artifacts are generated notices are sent via the listserv Issues with artifacts should be noted on the OpenSG collaboration site –

Plans - Feedback Current work (if approved), is shared with IEC WG14 ( Use Cases, Requirements, Artifacts ) Begin service definition work on other approved efforts e.g. OpenADE, OpenADR October 19, 2009OpenSG - AMI-ENTERPRISE14 OpenSG ballot October ‘09January ‘10 IEC WG14 On-going service definition work

October 19, 2009OpenSG - AMI-ENTERPRISE15 For More Information See detailed information in: “AMI-ENT: Step-by-Step Modeling and Artifacts Generation Guidelines”