May 3, 2010OpenSG – SG Systems – Service Definitions1 Chair: Gerald Gray, CIMple Integrations Co-Chair: Shawn Hu, Xtensible Solutions SG Systems Service Definition Team

Introduction Why Service Definitions? –Best Practice CIM implementation –“The CIM is neat but…” The service definition process (high level view) IEC CIM alignment Future Plans May 3, 2010OpenSG - SG Systems - Service Definition2

Introduction May 3, 2010OpenSG - SG Systems - Service Definition3 You are here

Where We Fit August 12, 2009OpenSG - SG Systems - Service Definition4 Use Case Team SRS Team Service Definition Team Interoperability Team Security Team Open AMI-ENT OpenADEOpenADROpenHAN

May 3, 2010OpenSG - SG Systems - Service Definition5 The Process Use Cases Business Processes Integration Requirements Services WSDLs XSDs System Requirements Specification For more info: smartgridipedia.org: HOW-TO service definition document

May 3, 2010OpenSG - SG Systems - Service Definition6 The Process Logical model input & development Identification of integration requirements Pattern naming Information objects Artifact generation Posting Issue generation and resolution Versioning

May 3, 2010OpenSG - SG Systems - Service Definition7 Logical Model Input IEC and Multispeak are the primary model inputs Use case contributions from SCE, Consumers Energy AMI-ENT, OpenADE 1.0 Up Coming additions: OpenADE 2.0

SDO – User Group Relationship Iterative process Analogy – early browser development May 3, 2010OpenSG - SG Systems - Service Definition8 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. May 3, 2010OpenSG - SG Systems - Service Definition9. - Specification - Implementation Irrelevant. Consistent. Compliant. Conformant. Fully Conformant Adapted from TOGAF 9

May 3, 2010OpenSG - SG Systems - Service Definition10 Logical Model Development Standardized actors from AMI-ENT SRS Document business process in use cases and activity diagrams

May 3, 2010OpenSG - SG Systems - Service Definition11 Identify Integration Requirements Where a process flow crosses an actor boundary

May 3, 2010OpenSG - SG Systems - Service Definition12 Harmonize Integration Requirements Compare integration requirements and look for commonality: –Common actors –Common consumers –Common providers –Common information objects Eliminate duplicates, refine integration requirements

May 3, 2010OpenSG - SG Systems - Service Definition13 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

May 3, 2010OpenSG - SG Systems - Service Definition14 Notification Subscribe to the Listserv – Send listserv Issues with artifacts should be noted on the OpenSG Help Desk site – Implementation Projects: Service Definition Team Wiki – Projects/Home.aspxhttp://osgug.ucaiug.org/sgsystems/SDTeam/Implementation%20 Projects/Home.aspx

Plans - Feedback Current work was shared with IEC WG14 ( Use Cases, Requirements, Artifacts ) Continuing service definition work… May 3, 2010OpenSG - SG Systems - Service Definition15 OpenSG AMI- ENT ballot Oct ‘09Jan ‘10 IEC WG14Re-factor artifacts OpenADE 1.0 artifacts REST/SOAP May ‘10OpenADE 2.0, other…

Ta Da! Questions? August 12, 2009OpenSG - SG Systems - Service Definition16