Chair: Gerald Gray, CIMple Integrations

1
SG SystemsService Definition Team

• Chair Gerald Gray, CIMple Integrations
• gerald.gray_at_cim-ple.com
• Co-Chair Shawn Hu, Xtensible Solutions
• shu_at_xtensible.com

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

3
Introduction
You are here
4
Where We Fit
Open AMI-ENT
OpenADE
OpenADR
OpenHAN
Use Case Team
SRS Team
Service Definition Team
Interoperability Team
Security Team
5
The Process
Use Cases Business Processes
Integration Requirements

• Services
• WSDLs
• XSDs

For more info smartgridipedia.org HOW-TO
service definition document
6
The Process

• Logical model input development
• Identification of integration requirements
• Pattern naming
• Information objects
• Artifact generation
• Posting
• Issue generation and resolution
• Versioning

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

8
SDO User Group Relationship

• Iterative process
• Analogy early browser development

Feedback

• OpenSG example
• First pass IEC CIM draft XSD as informative
• Now XSD as normative

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
10
Logical Model Development

• Standardized actors from AMI-ENT SRS
• Document business process in use cases and
  activity diagrams

11
Identify Integration Requirements

• Where a process flow crosses an actor boundary

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

13
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

ltIEC VerbgtltInformation Objectgt e.g.
CreatedMeterReading
14
Notification

• Subscribe to the Listserv
• http//listserv.enernex.com/cgi/wa.exe
• Send listserv e-mail
• OPENSG-SGSYS-SD_at_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/Implement
  ation20Projects/Home.aspx

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
16
Ta Da!

• Questions?