1 / 15

OpenSG-AMI-ENTERPRISE Service Definition and Standards Framework

Learn about the high-level service definition process, IEC CIM alignment, future plans, system requirements specification, logical model input, integration needs, and more in the AMI-ENTERPRISE framework. Utilize pattern naming, artifact generation, versioning, and feedback mechanisms.

josephhanson
Download Presentation

OpenSG-AMI-ENTERPRISE Service Definition and Standards Framework

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. AMI-Enterprise Service Definition Team The Framework, Standards, and Plans OpenSG - AMI-ENTERPRISE

  2. Introduction • The service definition process (high level view) • IEC CIM alignment • Future Plans OpenSG - AMI-ENTERPRISE

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

  4. The Process • Logical model input & development • Identification of integration requirements • Pattern naming • Information objects • Artifact generation • Posting • Issue generation and resolution • Versioning OpenSG - AMI-ENTERPRISE

  5. Logical Model Input • IEC 61989-9 and Multispeak are the primary model inputs • Use case contributions from SCE, Consumers Energy • Up Coming additions: PHEV, OpenADE, OpenADR OpenSG - AMI-ENTERPRISE

  6. 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 - AMI-ENTERPRISE

  7. 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 - AMI-ENTERPRISE

  8. Logical Model Development • Standardized actors from AMI-ENT SRS • Document business process in use cases and activity diagrams OpenSG - AMI-ENTERPRISE

  9. Identify Integration Requirements • Simply where a process flow crosses an actor boundary OpenSG - AMI-ENTERPRISE

  10. 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 - AMI-ENTERPRISE

  11. 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 - AMI-ENTERPRISE

  12. Artifacts & Versioning • Information objects are modeled in UML using Sparx EA. • IEC CIM is used as a Reference Model • Classes and attributes are selected and transformed into Semantic Model • Each context folder contains an entity class diagram that lists all entities that are used to describe an information object. • 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="http://www.smartgridipedia.org/2009/03/MeterReading.wsdl" • xmlns:typeOrig="http://www.smartgridipedia.org/2009/03/MeterReading" OpenSG - AMI-ENTERPRISE

  13. Notification • Subscribe to the Listserv • http://listserv.enernex.com/cgi/wa.exe • Send listserv e-mail • AMI-ENTERPRISE@LISTSERV.ENERNEX.COM • When new artifacts are generated notices are sent via the listserv • Issues with artifacts should be noted on the OpenSG collaboration site • http://osgug.ucaiug.org/default.aspx OpenSG - AMI-ENTERPRISE

  14. 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 OpenSG ballot IEC WG14 October ‘09 January ‘10 On-going service definition work OpenSG - AMI-ENTERPRISE

  15. For More Information • See detailed information in: “AMI-ENT: Step-by-Step Modeling and Artifacts Generation Guidelines” http://www.smartgridipedia.org/images/a/af/AMI_ENT_Step-By-Step_Modeling_and_Artifacts_Generation_Guidelines.doc OpenSG - AMI-ENTERPRISE

More Related