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

15
October 19, 2009 OpenSG - AMI-ENTERPRISE 1 The Framework, Standards, and Plans AMI-Enterprise Service Definition Team
  • date post

    21-Dec-2015
  • Category

    Documents

  • view

    213
  • download

    0

Transcript of October 19, 2009OpenSG - AMI-ENTERPRISE1 The Framework, Standards, and Plans AMI-Enterprise Service...

October 19, 2009 OpenSG - AMI-ENTERPRISE 1

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, 2009 OpenSG - AMI-ENTERPRISE 2

October 19, 2009 OpenSG - AMI-ENTERPRISE 3

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, 2009 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

October 19, 2009 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

SDO – User Group Relationship

• Iterative process• Analogy – early browser

development

October 19, 2009 OpenSG - AMI-ENTERPRISE 6

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, 2009 OpenSG - AMI-ENTERPRISE 7

.

- Specification

- Implementation

Irrelevant

. Consistent

. Compliant

.Conformant

. Fully Conformant

Adapted from TOGAF 9

October 19, 2009 OpenSG - AMI-ENTERPRISE 8

Logical Model Development

• Standardized actors from AMI-ENT SRS

• Document business process in use cases and activity diagrams

October 19, 2009 OpenSG - AMI-ENTERPRISE 9

Identify Integration Requirements

• Simply where a process flow crosses an actor boundary

October 19, 2009 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

October 19, 2009 OpenSG - AMI-ENTERPRISE 11

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 61968

• Verb examples: – Create, Created– Send, Reply

• Information Object examples:– EndDeviceAsset– MeterSystemEvent– MeterReading

<IEC Verb><Information Object> e.g. CreatedMeterReading

October 19, 2009 OpenSG - AMI-ENTERPRISE 12

Artifacts & Versioning

Information objects are modeled in UML using Sparx EA. 1. IEC CIM is used as a Reference Model2. Classes and attributes are selected and transformed into

Semantic Model3. 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="http://www.smartgridipedia.org/2009/03/MeterReading.wsdl"

xmlns:typeOrig="http://www.smartgridipedia.org/2009/03/MeterReading"

October 19, 2009 OpenSG - AMI-ENTERPRISE 13

Notification

• Subscribe to the Listserv– http://listserv.enernex.com/cgi/wa.exe

• Send listserv e-mail– [email protected]

• 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

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, 2009 OpenSG - AMI-ENTERPRISE 14

OpenSG ballot

October ‘09 January ‘10

IEC WG14

On-going service definition work

October 19, 2009 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