1 / 16

SG Systems Service Definition Team

This document provides an introduction to OpenSG's service definitions, outlining the importance and best practices for CIM implementation. The structure includes a high-level view of the service definition process, alignment with IEC CIM standards, and future plans. Key topics include use cases, business processes, integration requirements, and artifact generation. The collaborative effort between teams aims to streamline interoperability while addressing integration challenges. For further details, resources such as the smartgridipedia.org site are referenced.

brick
Télécharger la présentation

SG Systems Service Definition Team

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. SG SystemsService Definition Team Chair: Gerald Gray, CIMple Integrations gerald.gray@cim-ple.com Co-Chair: Shawn Hu, Xtensible Solutions shu@xtensible.com OpenSG – SG Systems – Service Definitions

  2. 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 OpenSG - SG Systems - Service Definition

  3. Introduction You are here OpenSG - SG Systems - Service Definition

  4. Where We Fit Open AMI-ENT OpenADE OpenADR OpenHAN Use Case Team SRS Team Service Definition Team Interoperability Team Security Team OpenSG - SG Systems - Service Definition

  5. System Requirements Specification The Process Use Cases Business Processes Integration Requirements • Services • WSDLs • XSDs For more info: smartgridipedia.org: HOW-TO service definition document OpenSG - SG Systems - Service Definition

  6. The Process • Logical model input & development • Identification of integration requirements • Pattern naming • Information objects • Artifact generation • Posting • Issue generation and resolution • Versioning OpenSG - SG Systems - Service Definition

  7. Logical Model Input • IEC 61989-9 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 OpenSG - SG Systems - Service Definition

  8. SDO – User Group Relationship • Iterative process • Analogy – early browser development SDO Yes and... Thou shalt... User Community Feedback • OpenSG example • First pass – IEC CIM draft XSD as informative • Now – XSD as normative OpenSG - SG Systems - Service Definition

  9. IEC CIM Alignment - Specification • 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. Adapted from TOGAF 9 - Implementation . Irrelevant . Consistent . Compliant . Conformant . Fully Conformant OpenSG - SG Systems - Service Definition

  10. Logical Model Development • Standardized actors from AMI-ENT SRS • Document business process in use cases and activity diagrams OpenSG - SG Systems - Service Definition

  11. Identify Integration Requirements • Where a process flow crosses an actor boundary OpenSG - SG Systems - Service Definition

  12. Harmonize Integration Requirements • Compare integration requirements and look for commonality: • Common actors • Common consumers • Common providers • Common information objects • Eliminate duplicates, refine integration requirements OpenSG - SG Systems - Service Definition

  13. Pattern naming allows for both ESB and non-ESB (point-to-point) architectural assumptions Verbs and Information objects are based IEC 61968 Verb examples: Create, Created Send, Reply Information Object examples: EndDeviceAsset MeterSystemEvent MeterReading Patterns – Using CIM Verbs <IEC Verb><Information Object> e.g. CreatedMeterReading OpenSG - SG Systems - Service Definition

  14. Notification • Subscribe to the Listserv • http://listserv.enernex.com/cgi/wa.exe • Send listserv e-mail • OPENSG-SGSYS-SD@SMARTGRIDLISTSERV.ORG • Issues with artifacts should be noted on the OpenSG Help Desk site • http://osgug.ucaiug.org/HelpDesk/default.aspx • Implementation Projects: Service Definition Team Wiki • http://osgug.ucaiug.org/sgsystems/SDTeam/Implementation%20Projects/Home.aspx OpenSG - SG Systems - Service Definition

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

  16. Ta Da! • Questions? OpenSG - SG Systems - Service Definition

More Related