cim for enterprise integration for the cim university, cim users group in san francisco, ca october...

CIM for Enterprise Integration for the

CIM University, CIM Users Groupin San Francisco, CA

October 11, 2010

For further information, contact:

Greg Robinson ([email protected]),

Convener of IEC TC57 WG14

Co-Chair of SG-Systems WG (of OpenSG of UCA Users Group)

ZigBee & HomePlug SEA – Smart Energy Profile 2.0 Leadership Team

NIST SGIP – Smart Grid Architecture Committee Member

CIM Users Group: CIM for Enterprise Integration

Slide 2

Agenda

• CIM for enterprise integration (IEC 61968) – Overall Scope, Approach– Messaging– Highlights for Using CIM

• AMI, DMS, OMS, GIS, CIS • Asset management, work management

– Supporting the smart grid


Slide 3

This is Not a Good Practice For Wires Integration;

It’s Not Good For Data Integration Either!

Wires Integration Anarchy!


Slide 4

Goal: Interface Standards Should Be Based on Common Semantics(e.g., CIM) to Avoid Adding to ‘Integration Anarchy’

Integration anarchy is a chaos of:(1) duplicated logic, (2) duplicated data, (3) duplicated effort,(4) newly acquired integration difficulties,(5) lack of ability to easily create new application functionality from services, and(6) lack of ability to support business processes with applications

Integration anarchy will result in higher costs and an inflexible, brittle Smart Grid System of Systems

Integration Infrastructure

OMS CISGIS

AMRDMSWMS

Without Common

Semantics, Point-to-Point

Integration Will Continue at the

Data Level

Data Integration Anarchy!


Slide 5

The IEC 61968-1 Interface Reference Model (IRM) Provides The Framework For Identifying Information Exchange Requirements Among Utility Business Functions

IEC 61968 Sequence Diagrams are organized by the IRM

Application Integration InfrastructureApplication Integration Infrastructure

Network OperationsNetwork Operations(NO) – IEC 61968-3(NO) – IEC 61968-3

Network OperationsNetwork OperationsMonitoring (NMON)Monitoring (NMON)

Network ControlNetwork Control(CTL)(CTL)

Fault ManagementFault Management(FLT)(FLT)

Operational FeedbackOperational FeedbackAnalysis (OFA)Analysis (OFA)

Operation StatisticsOperation Statistics& Reporting (OST)& Reporting (OST)

Network CalculationsNetwork Calculations- Real Time (CLC)- Real Time (CLC)

Records & AssetRecords & AssetManagement Management

(AM) – IEC 61968-4(AM) – IEC 61968-4

Substation & NetworkSubstation & NetworkInventory (EINV)Inventory (EINV)

GeographicalGeographicalInventory (GINV)Inventory (GINV)

Asset InvestmentAsset InvestmentPlanning (AIP)Planning (AIP)

Operational PlanningOperational Planning& Optimization & Optimization

(OP) – IEC 61968-5(OP) – IEC 61968-5

Network OperationNetwork OperationSimulation (SIM)Simulation (SIM)

Switch ActionSwitch ActionScheduling (SSC)Scheduling (SSC)

Power Import Sched.Power Import Sched.& Optimization (IMP)& Optimization (IMP)

Maintenance andMaintenance andConstructionConstruction

(MC) – IEC 61968-6(MC) – IEC 61968-6

Maintenance &Maintenance &Inspection (MAI)Inspection (MAI)

Construction WMS Construction WMS (CON)(CON)

Design &Design &Estimate (DGN)Estimate (DGN)

SchedulingScheduling& Dispatch (SCH)& Dispatch (SCH)

FieldFieldRecording (FRD)Recording (FRD)

Network ExtensionNetwork ExtensionPlanning Planning

(NE) – IEC 61968-7(NE) – IEC 61968-7

NetworkNetworkCalculations (NCLC)Calculations (NCLC)

Project DefinitionProject Definition(PRJ)(PRJ)

ConstructionConstructionSupervision (CSP)Supervision (CSP)

ComplianceComplianceManagement (CMPL)Management (CMPL)

CustomerCustomerSupport Support

(CS) – IEC 61968-8(CS) – IEC 61968-8

Customer ServiceCustomer Service(CSRV)(CSRV)

Trouble CallTrouble CallManagement (TCM)Management (TCM)

Meter Reading & ControlMeter Reading & Control(MR) – IEC 61968-9(MR) – IEC 61968-9

Meter ReadingMeter Reading(RMR)(RMR)

External to DMSExternal to DMS(EXT)(EXT)

Energy TradingEnergy Trading (ET)(ET)

RetailRetail(RET)(RET)

SalesSales(SAL)(SAL)

Customer Account Customer Account Management (ACT)Management (ACT)

FinancialFinancial(FIN)(FIN)

Business Planning & Business Planning & Reporting (BPR)Reporting (BPR)

Dispatcher Training Dispatcher Training (TRN)(TRN)

General inventory General inventory management (GIM)management (GIM)

Load ControlLoad Control(LDC)(LDC)

Meter Maintenance Meter Maintenance (MM)(MM)

Meter Data (MD)Meter Data (MD)Stakeholder Planning & Stakeholder Planning &

Management (SPM)Management (SPM)

Supply Chain & Supply Chain & Logistics (SC)Logistics (SC)

PremisesPremises(PRM)(PRM)

Human ResourcesHuman Resources(HR)(HR)

Point Of SalePoint Of Sale(POS)(POS)

Meter OperationsMeter Operations(MOP)(MOP)

Advanced Metering Advanced Metering Infrastructure (AMI)Infrastructure (AMI)

Meter Data Meter Data Management IMDM)Management IMDM)

Metering SystemMetering System(MS)(MS)

Demand ResponseDemand Response(DR)(DR)


Slide 6

Key Concept: Incremental Integration - in Step With Business Needs

Semantically Consistent ESB

OMSCIS

GIS

AMR

DMS

WMS

TT

OR

IEC 61968 IRM Interface

CIS OMS DMS

TT

OR

Trouble Ticket

Outage Record

Information Flow Design


Slide 7

Key Concept: Replace Large Monolithic Applications ‘a Chunk at a Time’

WMSM

aint

enan

ce &

Insp

ectio

n

Con

stru

ctio

n

Wor

kS

ched

ulin

g

Des

ign

Fie

ldR

ecor

ding

Other AppsOther Apps

Other AppsCIM Message Types


Slide 8

Agenda





Slide 9

IEC 61968 Basic Message Structure

• A verb to identify the type of action being taken

• A noun, to identify the type of the payload

• The payload, which contains the data relevant to the information exchange as defined using a profile

[source: IEC 61968-1]


Slide 10

Field Description

Verb This enumerated list of verbs can be used to form message types in compliance with the IEC 61968 standard

Noun The Noun identifies the main subject of the message type, typically a real world object defined as a profile using the CIM.

Revision Revision level of the message type.

Context Intended context for information usage such as production, testing and etc.

Timestamp Application level relevant time and date for when this instance of the message type was produced. This is not intended to be used by middleware for message management.

Source Source person or system that publishes the message

AsyncReplyFlag Indicates whether or not reply should be asynchronous

ReplyAddress Address to be used for asynchronous replies

AckRequired Indicates whether or not an acknowledgement is required

User User information of the sender

MessageID Unique message ID to be used for tracking messages

CorrelationID ID to be used by applications for correlating replies

Comment Optional comment

Property Message properties can be used to identify information needed for extended routing and filtering capabilities.

Message Header



Slide 11

Message Types Are Created By Combining IEC 61968 Verbs With Information Exchange Topics, Referred To As Nouns

Verbs Meaning Message BodyCREATE The CREATE verb is used to publish a request to

the master system to create a new document.All sections (datarequired to create thedocument)

CHANGE The CHANGE verb is used to publish a request tothe master system to make a change in thedocument based on the information in themessage.

All sections (key(s) +data to be changed)

CANCEL The CANCEL verb is used to publish a request tothe master system to cancel the document. TheCANCEL verb is used when the business contentof the document is no longer valid due to error(s).

Header information +message content key(s)

CLOSE The CLOSE verb is used to publish a request tothe master system to close the document. TheCLOSE verb is used when the business documentreaches the end of its life cycle due to successfulcompletion of a business process.


DELETE The DELETE verb is used to publish a request tothe master system to delete the document. TheDELETE verb is used when the businessdocument should no longer be kept in theintegrated systems either due to error(s) or due toarchiving needs.


GET The GET verb is used to publish a request to themaster system to get the current data for a givendocument reference code or a set of documents.

One or more documentreference codes +Key(s)



Slide 12

Verbs Meaning Message BodyCREATED The CREATED verb is used to publish the

creation of a document as a result of either anexternal request or an internal action within themaster system of that document.

All sections

CHANGED The CHANGED verb is used to publish thechange of a document as a result of either anexternal request or an internal action within themaster system of that document.

All sections (key(s) +changed content)

CLOSED The CLOSED verb is used to publish the normalclosure of a document as a result of either anexternal request or an internal action within themaster system of that document.


CANCELED The CANCELED verb is used to publish thecancellation of a document as a result of either anexternal request or an internal action within themaster system of that document.


SHOW The SHOW verb is used to publish the mostcurrent content of a document as a result of eitheran external GET request or an internal actionwithin the master system of that document.

All sections

REPLY The REPLY verb is used to publish the processingresult of an external request to the master systemto create, change, delete, cancel, or close adocument. The REPLY message type couldcontain specific confirmation information as towhether the request is processed successfully ornot and provide alternatives if applicable.

Header information +message content key(s)+ confirmationinformation +alternatives (optional)

SUBSCRIBE The SUBSCRIBE verb is used to publish therequest to ask the master system of a documentto publish a CHANGED document whenever thereis a change to the document.


UNSUBSCRIBE

The UNSUBSCRIBE verb is used to publish therequest to ask the master system of a documentto stop publishing a CHANGED documentwhenever there is a change to the document.


(IEC 61968 Verbs - continued)



Slide 13

Example of a “message type” payload



Slide 14

class part9: MeterReadings message type

IdentifiedObject

Metering::MeterReading

Agreement

Customers::CustomerAgreement

ActivityRecord

Metering::EndDeviceEvent

Metering::IntervalBlock

EndDeviceAsset

Metering::MeterAsset

MeasurementValue

Metering::Reading

IdentifiedObject

Metering::ServiceDeliveryPoint

+MeterReadings

0..*

+CustomerAgreement

0..1

+MeterReading

0..1

+EndDeviceEvents

0..*

+MeterReadings

0..*

+ServiceDeliveryPoint

0..1

+IntervalBlocks

0..*

+MeterReading

0..1

+MeterAsset

0..1

+MeterReadings

0..*

+Readings

0..*

+MeterReadings

0..*

Example of how message elements are derived from the CIM



Slide 15

Navigating associations in CIM (UML notation)

class part9: MeterReadings message type

IdentifiedObject

Metering::MeterReading

IdentifiedObject

Metering::ReadingType

Metering::IntervalBlock

MeasurementValue

Metering::IntervalReading

Metering::Pending

Metering::ReadingQuality

+IntervalBlocks

0..*

+MeterReading

0..1

+IntervalBlocks 0..*

+ReadingType

1

+IntervalBlocks

0..*

+IntervalReadings

0..*

+IntervalBlocks0..*

+Pending

0..1

+Pending 0..1

+ReadingType

1

+ReadingQualities0..*

+IntervalReading

1


Slide 16

Navigating associations in message type schemas


Slide 17

Agenda





Slide 18

Service Provider Responsibilities:

• Construction & maintenance project management

• Materials sourcing & inventory management

• System engineering & design• Bargaining unit negotiations• Workforce scheduling &

deployment• Work practice design &

development• Asset data input and collection• Workforce training• Marketing & sales of services• Competitor analysis

Asset Owner Responsibilities:

• Asset valuation• Investment analysis & strategy• Contract negotiation/structuring• Regulatory oversight• Market & economic analysis• Portfolio management• Capital allocation• Asset financial & operating

performance analysis• Asset planning• Asset acquisition &

monetization

Asset Manager• Asset Optimization• Asset yield contribution

understanding• Financial structuring• Business development• Asset specifications &

standards• Full lifecycle asset

management• Asset data management• Workload management• Asset financial and

operating performance analysis

• Asset strategy & plan development

• Asset full lifecycle financial & operational data analysis

• Regulatory strategy & negotiation

• Contract management• Risk management• Asset data requirements

definition• Asset opportunity

development & analysis• Industry Best Practices

Case Study: LIPA Asset Management and Organization (source: IEEE 2009)


Slide 19

Case Study: LIPA Asset Management Concept (source: IEEE 2009)

MSAMSA

CustomerSatisfaction

Financial

TechnicalPerformance

Regulatory

CriticalityDynamicFMEA

VisualizationKRIs/Risk Indicators

Assets & Processes (O&M&Planning) aspects

Data and Process Integration – CIM/IB/SOA

Assess E

ffectiveness

RiskManagement

Risk AssessmentRisk Assessment

RiskStatus

RiskDrivers

RiskTolerance

LIPA Goals

LIPA Goals

Asset ManagementAsset ManagementAsset ManagementAsset Owner Asset Manager

Service Provider

Execute

Implement

PlanStrategy

KPIs


Slide 20

Some Foundational Relationships of the IEC CIM for Asset Management

Power System ResourceElectrical Network Role Used For

Planning, Operations, etc.

AssetPhysical Plant Filling A Role

Such As A Transformer, Pole, etc.

LocationA Street Address, Coordinates

For a Geographic or Schematic reference system, etc.

OrganisationEntities Performing One or More

Roles Such As Customer, Supplier,Manufacturer, Service Provider, etc.

Erp PersonA Person Performing Roles SuchDispatcher, Field Operator, etc.

DocumentInformation Containers Such As

Asset Catalogues, Trouble Tickets, Work Orders, etc.

Activity RecordUsed to Record Each State

change of CIM objects

Type AssetCompatible Unit For

Design & Procurement

Asset ModelParticular Model and Version

of a Vendor's Product


Slide 21

IEC 61968-4: Records and Asset Management(Note: Maintenance Update in Process)

• Network Data Set– Contains data for any part of a distribution network:

• Typically selected for operational or extension planning studies• Used in numerous implementations for GIS to DMS integration• Can be part of a feeder, a single feeder or more than one feeder • Can be either the ‘As built’ network or a proposed network selected for analysis• It is a superset of IEC 61968-13 CDPSM (i.e., Distribution’s CPSM)

– Contains references to other static data such as:• Elements of a TypeAssetCatalogue• Elements of a AssetCatalogue• Assets performing the roles of the associated types of PowerSystemResources• Other “leaf node” elements such as Organisations, Locations, and

Measurements

• Change Set– Contains updates required in a transaction for an existing

NetworkDataSet– Each step in the ChangeSet is described through a separate ChangeItem.

• A change item identifies the change type (add, delete, modify)• Sequence number for a particular change within a set of changes of a

ChangeSet. – Only the identifiers of the relevant NetworkDataSet messages are to be

included in a ChageSet message. • The actual contents are provided in accompanying NetworkDataSets

messages.


Slide 22

PowerSystemResource(from Core)

OrgAssetRole(from AssetBasics)

DocAssetRole(from AssetBasics)

OrgPsrRole(from AssetBasics)

DocPsrRole(from AssetBasics)

AssetPsrRole(f rom AssetBasics)

TypeAsset(from TypeAsset)

AssetModel(from AssetBasics)

Organisation(from TopLevel)

ErpInventory(from ERP_Support)

FinancialProperties(from AssetBasics)

Asset(from AssetBasics)

Document(from DocumentInheritance)

0..10..n 0..10..n

0..n

0..n

0..n

0..n

0..1

0..1

1..n

0..n

1..n

0..n0..1

0..1

0..1

0..10..1

0..1

0..n

0..n

0..n

0..n0..n

0..n

+Documents

0..n

0..n

0..n

0..n

0..n

0..n

From the logical view to the physical asset view of the same object.


Slide 23


• Presentation:– Can contain location information for most any element

represented in the CIM, particularly elements of the distribution network.

– Provides location information of individual assets or power system resources

– Provides a set of location information as a companion to the NetworkDataSet.

• Asset List:– Can contain various amounts of data for any set of utility assets– Contains references to static reference data such as:

• Elements of an AssetCatalogue• Elements of a TypeAssetCatlogue• PowerSystemResources that specify the role in which the Asset is

being used– If it has been installed rather than sitting in inventory

• Other “leaf node” elements such as Organisations, Locations, and Measurements


Slide 24

Case Study: Asset Management System Used to Initialize System Control Center System (source: DistribuTECH2002)

System Control Center

Asset Management

Adapter

Adapter

Integration Bus

Asset data sent in XML

Transformation into CIM Objects

Publish AMS data in CIM format

Subscribe to Asset data

[presented at DistribuTECH 2001]


Slide 25

Case Study: Operations Model Capabilities (source: DistribuTECH2002)

AMS

DMS


Slide 26

DocAssetRole(from AssetBasics)

AssetListRole(from AssetBasics)

DocPsrRole(from AssetBasics)

AssetCatalogue(from AssetBasics)

TypeAssetCatalogue(from AssetBasics)

AssetCatalogueItem(f rom AssetBasics)


AssetModel(from AssetBasics)

Specification(f rom AssetBasics)

AssetLis t(f rom AssetBasics)

Collection(from Collections)


Asset(from AssetBasics)

Document(from DocumentInheritance)

10..1

0..n

1

0..n

0..n

0..n

0..1

0..n

0..1

0..1

0..n

0..1

0..n 0..10..n

0..n

0..n

0..n

0..n

0..n

0..n

0..n

0..n

0..n

0..n

0..n

0..n

0..n 0..n0..n 0..n


Slide 27


• Asset Catalogue:– A collection of information regarding available types of

products and materials that are used to build or install an Asset(s), to maintain an Asset(s) or to operate an Asset(s).

– Each catagoue item is for a specific product available from a specific supplier.

– Contains references to static reference data such as:• Elements of a TypeAssetCatalogue• Specifications• Other “leaf node” elements such as Organisations

• Type Asset Catalogue – Contains data for a set of utility asset types– It is a collection of information regarding generic types of

assets that may be used for design purposes, analysis, and so on

– A TypeAsset is not associated with a particular manufacturer– Contains references to other Documents containing static

reference data such as:• Elements of an AssetCatalogue• Other “leaf node” elements such as Organisation


Slide 28

IEC 61968-6: Maintenance & Construction(Note: CD in development – paper being presented at Grid InterOp)

Business Functions Performed

• Maintain and Plan PM Programs• Manage Inspection and Maintenance “Triggers”• Link Inspection orders to follow-up repair orders• Gather “failure” data

• Initiate and Plan work orders• Manage material, equipment, and permit

requests• Manage and Track Work (Workflow)• Close Work and Support Performance Analysis

• Gather actual costs and support cost reconciliation

• Monitor work progress• support financial closing with accounting systems

• Work Design and Cost Estimation• Compatible Unit based Graphical design• Generate Bill of Materials

• Assign crew based on work type and skills• Determine Schedule Date• Perform constraint-based “auto-scheduling”

Maintenance andMaintenance andConstructionConstruction

(MC) – IEC 61968-6(MC) – IEC 61968-6

Maintenance &Maintenance &Inspection (MAI)Inspection (MAI)

Construction Construction WMS (CON)WMS (CON)

Design &Design &Estimate (DGN)Estimate (DGN)

SchedulingScheduling& Dispatch (SCH)& Dispatch (SCH)

FieldFieldRecording (FRD)Recording (FRD)


Slide 29

IEC 61968-6: Maintenance & Construction

• Work is created any time a person is required to perform an activity related to company assets. Examples of work include – Construction work (e.g. service installations, line

extensions, and system betterment projects)– Service work (e.g meter replacements, Turn-on, Turn-

off, etc.)– Maintenance work (e.g. routine oil changes, painting,

etc.) – Inspection work (e.g. pole inspections, vault

inspections, Substation inspections) – Trouble work (e.g. Power outage, voltage quality

problem, etc.)


Slide 30

IEC 61968-6: Construction & Maintenance

• Current Message Types:– Compatible Units– Construction Work– Crew– Design– Inspect & Test– Labor– One Call Request– Procedure– Service Work– Trouble Work– Work Cost Detail– Work Scheduling– Work Status– Work Task


Slide 31

Generic “TypeAssets” are used for Design

TypeMaterial(f rom WorkStandards)

CUGroup(f rom WorkStandards)

CULaborItem(f rom WorkStandards)

CUContractorItem(f rom WorkStandards)

Procedure(f rom WorkInspectionMaintenance)

CUMaterialItem(f rom WorkStandards)

CompatibleUnit(from WorkDesign)

CUAsset(from WorkStandards)


CUEquipmentItem(from WorkStandards)

0..1

0..n0..n0..n0..n0..1

0..n

0..n

0..n

0..n

0..1

0..n

0..n

0..n0..n

0..1

0..n

0..n

0..n

0..n

0..n

0..n0..n

0..n0..n

0..n

0..n

0..n0..n 0..n

0..n0..n

0..n

0..1

0..10..1

0..1

0..1

0..n

0..n

0..n

0..1

0..1

0..1

CostType(f rom WorkClosing)

0..1

0..n

0..1

0..n

0..1

0..n

0..1


Slide 32

IEC 61968-3: Network Operations(Note: Maintenance Update in Process)• Current Message Types:

– Measurement list;– Operational restrictions;– Outage records;– Safety documents;– Switching schedules.

• Regarding “Note”, currently being updated through a use case-driven and incremental maintenance cycle, with first iteration being in support of outage management.


Slide 33

OrgErpPersonR ole(from TopLevel)

DocOrgRole(from TopLevel)

OperationalRestriction(from Operational)

Equipment(from Core)

ClearanceTag(from Outage)

ConductingEquipment(from Core)

0..n

1

0..n

1

SafetyDocument(from Operational)

PSRType(from Core)

ErpPerson(from ERP_Support)


0..n

0..1

0..n

0..1

Organisation(from TopLevel)

0..n

0..n

0..n

0..n

ActivityRecord(from ActivityRecords)

Docum ent(from DocumentInheritance)

0..n0..n

0..n0..n

0..n

0..n

0..n

0..n

0..n

0..n

0..n

0..n

0..n

0..n

0..n

0..n

An Example: Safety Document Classes


Slide 34

Safety Document Message Type


Slide 35

IEC 61968-8: Customer Support(Note: Update to second CD in Process)

• Current Message Types:– Trouble Ticket– Failure Event– Planned Outage Notification– Call Back– Compliance Event– Outage History– Service Extension Request– ServiceRequest– CustomerServiceAgreement– Customer Billing– Construction Billing


Slide 36

Aspects of Customer Accounts

Agreement(from TopLevel) ConductingEquipment

(f rom Core)

ErpPerson(f rom ERP_Support)

Organisation(f rom TopLev el)

CustomerData(from Consumers)

CustomerAccount(from Consumers)

Equipment(f rom Core)

T ariff(from Consumers)

CustomerAgreement(from Consumers)

ServiceKind(f rom Consumers)

ServiceLocation(from Locations)

PricingStructure(f rom Consumers)

SDPLocation(from Locations)

PowerQualityPricing(f rom Consumers)

EnergyConsum er(f rom Wires)

ServiceDeliveryPoint(from Metering)0..n

0..n

0..n

0..n

0..n

0..1

0..1

0..n

0..10..10..1

0..1

1

1..n

1

1..n 1 0..n

0..n

0..n

1

0..n 0..n0..n

0..n

0..n

0..n

0..n

1

0..n

1

1

0..n

0..n

0..n

0..1

0..n0..n 0..n

0..n

0..n

0..n0..n0..n

1

1

0..n

0..1

0..n

0..n

0..n

1

0..n

0..n

1

0..n0..n

0..n

0..n0..n

0..n

0..n

1

0..n


Slide 37

A Customer Account Message Type for AMI (IEC 61968-9)

IEC 61968-9ReferenceModel

Refer to

Margaret’s presentation


Slide 39

Agenda





Slide 40

NIST Conceptual Model

[Source: NIST Interim Roadmap]


Slide 42

http://www.ucaiug.org/

User groups are a good source of help

Board of Directors

Testing

Technical Publications

Technical Oversight Committee

ExecutiveCommittee

Harmonization

Marketing

Advisors

AuditCommittee

OperatingOfficers

Membership

Liaison

CIM

61850

OpenSG

Help Desk


Slide 43


Slide 44

Key Collaboration Concept for the SG-Systems Working Group

• Standard building blocks are defined by standards development organizations (SDOs)

• Requirements (use cases) are gathered from helpful sources– Utilities– Industry initiatives

• The SG-Systems WG articulates Industry Best Practices (see next slide) that satisfy requirements through the use of standard building blocks.– Recommended extensions and changes to standard building

blocks are provided back to appropriate standards bodies.

OpenSG Focus: Finding/Developing Best Practices & Making Them into Vetted “Industry Best Practices”

• Local Utility Projects

• Consortiums & User Groups like OpenSG (business requirements) & CIMug (optimization & implementation support)

• Standards Development Organizations (SDOs) like IEC TC57 Working Group 14 for the IEC 61968 series of standards, NAESB, IEEE, et al.

Utility’sProjects

- Design &Implementations

---------------

Utility’sArchitecture

-----------------------Industry Best PracticesInteroperability Testing

---------------------------------

Industry Best Practices------------------------------------------

Standards Conformance & Interoperability Testing

-----------------------------------------------------Industry Standards


Slide 46

•The scope of AMI-ENT is the systems and/or applications within and around the utility enterprise and the inter-systems related business functions and stops at the boundaries of applications and the edge of utility enterprise.

•The focus is on how these systems are to be integrated and composed to support AMI related business processes and functions. •Edge applications are those applications that communicate with networks and devices in the field, as well as those that communicate with other businesses or enterprises (generally defined as third parties).

(of UCAIug/OpenSG/SG-Systems WG)


Slide 47

Case Study: Consumers Energy and AMI-Ent TF

AMIAMI--ENTENT

Enterprise Bus + Common Model & Service

Outage Outage ManagementManagement

CustomerCustomerInfo. & BillingInfo. & Billing

Revenue Revenue ProtectionProtection

DistributionDistributionManagementManagement

AMI ServiceAMI ServiceManagerManager

HANHANManagementManagement

Third PartyThird PartyPortalPortal

CustomerCustomerPortalPortal

MeterMeterDataData

ManagementManagement

DemandDemandResponseResponse


Meter AssetMeter AssetManagementManagement

AMI NetworkAMI NetworkAssetAsset


Representative of AMI-ENT components, not all inclusive.


Slide 48

Case Study: AMI-Ent Service Identification


Slide 49

Case Study: AMI-Ent Inventory of CIM-Based Services Supporting Use Cases for AMI-Enterprise

Use Case & Scenario

Integration Requirement

Functional Description of the Service

Operation Pattern

Service Name Service Operation Service Consumer(Outbound)

Service Provider(Inbound - WS)

Information Object(normalized)

B1-S1 REQ-B1004 MDUS receives the meter reading results on scheduled basis.

Created MeterReading CreatedMeterReading Head End MDUS MeterReading

B1-S12 REQ-B1011 MDUS receives meter reads

Created MeterReading CreatedMeterReading Field Tool MDUS MeterReading

B1-S15 REQ-B1012 MDUS notifies meters with reading problems

Created MeterSystemEvent CreatedMeterSystemEvent MDUS? MDUS MeterSystemEvent

B1-S15 REQ-B1013 AMI Head End operator receives meter service orders

Created MeterServiceOrder CreatedMeterServiceOrder MDUS Head End MeterServiceOrder

B1-S17 REQ-B1014 Request billing determinant Create BillingDeterminantRequest CreateBillingDeterminant CIS MDUS BillingDeterminant

B1-S17 REQ-B1014 Request billing determinant Created BillingDeterminant CreatedBillingDeterminant MDUS CIS BillingDeterminant

B1-S2 REQ-B1001 Head End receives the request for a meter reading on demand

Create MeterReading CreateMeterReading TBD Head End MeterReading

B1-S2 REQ-B1002 MDUS receives a meter reading on demand

Created MeterReading CreatedMeterReading Head End MDUS MeterReading

B1-S2 REQ-B1003 A user or system receives a meter reading on demand

Created MeterReading CreatedMeterReading MDUS TBD MeterReading

B1-S3 REQ-B1006 CIS receives meter event Created MeterSystemEvent CreatedMeterSystemEvent Head End/MDUS

CIS MeterSystemEvent

B1-S7 REQ-B1009 MDUS receives the request for meter readings

Create MeterReading CreateMeterReading Third Party Portal

MDUS MeterReading

B1-S7 REQ-B1010 Third party receives the meter readings

Created MeterReading CreatedMeterReading MDUS Third Party Portal MeterReading

B1-S8 REQ-B1009 MDUS receives the request for meter readings

Create MeterReading CreateMeterReading Third Party Portal

MDUS MeterReading

B1-S8 REQ-B1010 Third party receives the meter readings

Created MeterReading CreatedMeterReading MDUS Third Party Portal MeterReading

B2-S1 REQ-B2001 Send scheduled shut off notification

Created ScheduledEvent CreatedScheduledEvent CIS Head End ScheduledEvent

B2-S1 REQ-B2002 Send scheduled shut off command

Created ConnectDisconnect CreatedConnectDisconnect CIS Head End ConnectDisconnect

B2-S1 REQ-B2003 Send scheduled shut off command confirmation

Created CommonConfirmation CreatedCommonConfirmation Head End CIS CommonConfirmation

B2-S1 REQ-B2004 Send meter read (final) Created MeterReading CreatedMeterReading Head End MDUS MeterReading

B2-S2 REQ-B2005 Request AMI Meter status Create MeterStatusRequest CreateMeterStatus CIS Head End MeterStatus


Slide 50

Application View

Services Provided/Consumed by “Customer Information Management”

Customer Information ManagementCustomer Information Management

Meter Data ManagementMeter Data Management

AMI Head EndAMI Head End

Meter Data ManagementMeter Data Management

AMI Head EndAMI Head End

Create

Created

Created

CreatedCommonConfirmation

MeterStatus

HanAsset

BillingDeterminant

MeterStatus

MeterSystemEvent

Service Consumers Service Providers

ScheduledEvent

ConnectDisconnect

CommonConfirmation

MeterStatusCreated

Created HANAsset

BillingDeterminant

MeterStatus

MeterSystemEvent

ScheduledEvent

ConnectDisconnect

CreateMeterStatusRequest MeterStatusRequest

CreateLoadControlCommandRequest LoadControlCommandRequest

CreatedServiceToken ServiceToken

CreateHANAsset HANAsset

CreateBillingDeterminant BillingDeterminant

ChangeMeterAssetRequest MeterAssetRequest

CreateMeterServiceOrderRequest MeterServiceOrderRequest

Service Providers / Consumers

Service Operation

Created

Created

Service Operation

Changed


Slide 51

Technical View (Patterns)

Application A Transparent ESB

ANativeAPI or Service

T S/C

Application B

BNativeAPI or Service

TS/PS/P S/C

SendMeterReading

CreatedMeterReading

ChangedMeterReading

CanceledMeterReading

SendMeterReading

CreatedMeterReading

ChangedMeterReading


OrchestrationOrchestration

ServiceService

OperationsOperations

Other interested parties……Guaranteed delivery within ESB, plus internal routing……

ReceiveMeterReading

CreatedMeterReading

ChangedMeterReading


ReceiveMeterReading

CreatedMeterReading

ChangedMeterReading



Slide 52

Common Concerns About The CIM for Integration

– Concern 1: the CIM is too large• For the common systems language, the CIM can be thought of as the

unabridged dictionary. It is important to note that projects only use the portion of the dictionary relevant to their implementation

• But as the dictionary is is much richer, there will be consistency and congruity for other areas that the implementation must interface with.

– Concern 2: the CIM inhibits innovation• Because people don’t have to waste time re-inventing things that have

been well vetted in the community, they can leverage the existing dictionary while focusing more energy on their innovative concept.

• Not only is this more efficient for the innovator, but it is also much more efficient for the people the innovators wants to share his ideas with. The community is already educated on how to use the well vetted language.

– Concern 3: the CIM is too slow • This is like saying the English language is slow; it is based on the

speakers command of the language and the choice of media used.• When a person communicates with someone, they must:

1. Articulate the information for the receiver to comprehend it2. As a person may then provide this information through the US Postal

Service, through email, through phone calls, etc., the system may provide this information over many types of middleware (messaging, file transfers, data base, etc.)

[source: IEEE T&D Optimization Panel 2010]


Slide 53

Common Concerns About The CIM for Integration (continued)

– Concern 4: The CIM is too abstract• This quality enables the CIM to continue to be relevant and valid even as

technology continuously changes. The ability to properly convey unambiguous information primarily boils down to one’s skills in applying the common systems language.

– Concern 5: The CIM is not a best practice data model • For any individual purpose, one can always invent a model that is

superior to any other existing model.• The CIM has not been developed for only one functional area, but rather

by a wide range of domain experts for integrating disparate applications. So for inter-application integration purposes, a superior model does not exist and would be difficult to achieve.

– Concern 6: The CIM is too hard to implement• Specialized models are often biased for a particular implementation and

used with the a specific implementation technology. If the implementation never had to interface with other systems, this would be easier.

• As the CIM is an information model that is technology neutral, using the CIM does require following a process that restricts the general information model for particular contexts and then generates the appropriate design artifacts. The CIM Community has been doing this for some time and many tools are available for automating the process.

[source: IEEE T&D Optimization Panel 2010]


Slide 54

Thank you for your time!

• Good news: The CIM is being used extensively – so learning about it is time well spent.

• Bad news: The CIM continues to need a lot of work and therefore users must be prepared for revision management

• Fun news: The CIM is a key NIST standard – so we have many exciting adventures (HAN, DER, PEV, ADE, DR, etc.) to look forward too!

cim for enterprise integration for the cim university, cim users group in san francisco, ca october...

Documents

enterprise integration

pointtopoint integration

integration difficulties

cim users group

enterprise integration

wires integration anarchy

cim ami

cim university