Service Definitions

A Framework For Standard Interface Development

Abstract to Detail

• Standards Bodies• Business Case• Conceptual Architecture• Use Cases• Integration Requirements• Sequence Diagram• Patterns• Services• WSDL

Leveraging the Overlap

CIMug

UtilityAMIAMI Enterprise WG

Standard Services

Key Collaboration Concept

• Standard building blocks are defined by CIMug – i.e., IEC working groups and other relevant industry

groups such as Open Architecture Group (OAG), MultiSpeak

• Common industry practices are defined by the user community; the AMI Enterprise TF– by specifying how standard building blocks are used

for popular scenarios with the resulting artifacts:• Use cases specify required services• Service definitions (WSDLs) contain the building

blocks• Artifacts are placed on smartgridipedia.org

– Anyone may use a common industry practice or artifact.

Moving to a Standard

Requirements Traceability

Business Benefits

Business Processes

Functional Requirements

IntegrationRequirements

Services Portfolio

Interface Reference Model

Application Portfolio

Resulting from an activity in a Use Case Scenario

Resulting from an flow in a Use Case

Scenario

Includes application services and

common services.

Services Gap Analysis

Map system actors to IEC

61968 systems/IRM

Map system actors to IEC

61968 systems/IRM

Identify integration requirements

Identify integration requirements

Create common services per integration

requirements

Create common services per integration

requirements

Model service sequence diagram

that includes vendor and legacy

services

Model service sequence diagram

that includes vendor and legacy

services

Create services mapping and gap

analysis!

Create services mapping and gap

analysis!

Review CIM and MultiSpeak

services/schemas

Review CIM and MultiSpeak

services/schemas

Identify Application services/schemas

Identify Application services/schemas

Gap analysis Documents

Scope

Conceptual Architecture

Enterprise SystemsHead End Systems

Head-End 1

Head End n

Data, pq, informational events

Technical VEEdata

Commands

Ent

erpr

ise

Ser

vice

Bus

Commands

sync

Events

Real-time events

Real-time events

Commands

Outage Management

ERP

Asset Management

MDUS/MDM

Meter Data Repository

High Speed Data Handler

Event& Command

Handler

Master Data Sycnhronization

The Process

Use Cases

Business Processes

Integration Requirements

Services

•WSDLs

•XSDs

Business Process B1.3

Integration Requirements

Service Naming

Based on IEC CIM Information ObjectsExamples:

• EndDeviceEvent• MeterAsset• MeteringReading• MeterSystemEvent

<Information Object> e.g. MeterReading

Operation Naming Patterns

Utilizing IEC 61968-9 verb :

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

CREATECREATED CHANGECHANGED CANCELCLOSEDELETEGET

CLOSEDCANCELEDDELETEDSHOWREPLYSUBSCRIBEUNSUBSCRIBE

Sequence Diagram

Recommended Services

From AMI-ENT Service Inventory smartgridipedia.org

Utility Benefits

• As utilities pull in the same direction, de facto standards are created; economies of scale should yield: – Improved vendor response & support– Reduced product procurement costs– Reduced effort for requirements analysis and

design– Reduced risk of overlooking requirements

• That are expensive to retrofit later

– Reduced life-cycle costs

Artifacts - Resources

• Smartgridipedia.org - wiki– Business processes– WSDLs/XSDs– Information Objects

• AMI-ENT Task Force - Sharepoint– Issue Tracking– Discussion– Calendar

Future Service Definitions Work

• Sources of information for future service definitions work– PHEV use cases– OpenADR– OpenADE

• Business process map• Integration requirements identification• Rationalization/Harmonization• New services documented