CIM For Enterprise Integration: CIM University, CIM Users Group

CIM for Enterprise Integration
for the
CIM University, CIM Users Group
in Charlotte, NC
November 10, 2009
For further information, contact:

Greg Robinson (grobinson@xtensible.net),
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
Agenda
• CIM for enterprise integration (IEC 61968)

– Overall Scope, Approach
– Model Evolution
– Messaging
– Highlights for Using CIM
• AMI, DMS, OMS, GIS, CIS
• Asset management, work management
– Supporting the smart grid
Slide 2
CIM Users Group: CIM for Enterprise Integration
Key Premise: The Common Language Should Provide
Relevant Information To A User Regardless of Source
Materials
Management Construction
Engineering Concerns
Concerns Concerns
Operations Protection Maintenance

Concerns Concerns Concerns
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’
OMS GIS CIS
Integration Infrastructure
WMS DMS AMR

Data Integration Anarchy!
Integration anarchy is a chaos of: Without
(1) duplicated logic, Common
(2) duplicated data, Semantics,
Point-to-Point
(3) duplicated effort, Integration Will
(4) newly acquired integration difficulties, Continue at the
(5) lack of ability to easily create new application functionality from Data Level
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 CIM Users Group: CIM for Enterprise Integration
Slide 5
The IEC 61968-1 Interface Reference Model (IRM) Provides The Framework For
Identifying Information Exchange Requirements Among Utility Business Functions
All IEC 61968 Activity Diagrams and Sequence Diagrams are organized by the IRM
Business Functions
Distribution Management
External To Distribution
Business Functions
Management
(AM) (OP) (MC) (EMS) (SC)
(NO)
Records & Operational Maintenance Energy (RET) Supply
Network
Asset Planning & & Management & Retail Chain and
Operation
Management Optimization Construction Energy Trading Logistics
Interface Interface Interface Interface Interface Interface Interface

Standard: Part 3 Standard: Part 4 Standard: Part 5 Standard: Part 6 Standard: Part 10 Standard: Part 10 Standard: Part 10
IEC 61968 Compliant Middleware Services
Interface Interface Interface Interface Interface Interface Interface

Standard: Part 7 Standard: Part 8 Standard: Part 9 Standard: Part 10 Standard: Part 10 Standard: Part 10 Standard: Part 10
(NE) (MR) (ACT)

(CS) (HR)
Network Meter Customer (FIN) (PRM)
Customer Human
Extension Reading & Account Financial Premises
Support Resources
Planning Control Management
Electric Distribution Network Generation and Transmission Management,

Planning, Constructing, Enterprise Resource Planning, Supply Chain, and
Maintaining, and Operating General Corporate Services
Slide 6
Key Concept: Incremental Integration
- in Step With Business Needs
GIS
OMS
OR CIS
TT
IEC 61968
IRM Interface
Semantically Consistent ESB
WMS AMR
DMS Information Flow Design

CIS OMS DMS
Trouble Ticket TT
OR
Outage Record
Slide 7
Key Concept:
Replace Large Monolithic Applications ‘a Chunk at a Time’
Other Apps
MDI/CIM Messages Other Apps
Other Apps
Maintenance &
Construction
Scheduling
Recording
Inspection
Design
Work
Field
WMS
Slide 8
Agenda

– Model Evolution
– Messaging
Slide 9
IEC 61968-11: CIM Extension for Distribution
IEC61968CIMVersion
+ date: AbsoluteDateTime [0..1] = 2009- 04- 01

+ version: String [0..1] = IEC61968CIM10v23
Transitioning from
Rational Rose
Common
To Enterprise Architect
(Depending the state of a
Package, some diagrams in
this presentation are in Rose
Assets AssetModels and others are in EA)
Part 4
Work
Part 6
Customers
Part 8
Metering LoadControl PaymentMetering

Part 9
Slide 10
Priorities:
WG14 Roadmap priorities by NC
NC Averag
CAN CH DE FR UK US ZA Positio e comment
ns Priority
61968-9 3 3 3 3 3 3 6 3.0 Metering
61968-11 3 3 3 3 3 3 6 3.0 DCIM
61968-3 2 3 3 3 3 3 3 7 2.9 Operations (DMS/OMS)
61968-4 2 3 3 3 3 3 3 7 2.9 Asset & record mgmt.
61968-1 3 3 3 3 3 2 6 2.8 Reference architecture
61968-13 3 3 3 3 2 3 6 2.8 CDPSM
Security 1 3 3 2 3 5 2.4
61968-1-2 3 1 3 2 1 3 6 2.2 Naming/Design rules
61968-6 2 1 1 2 3 3 3 7 2.1 Work mgmt.
61968-10 2 1 2.0 n/a
61968-14-1 3 1 1 1 2 3 6 1.8 MultiSpeak
61968-14-2 3 1 1 1 2 3 6 1.8 MultiSpeak
61968-2 3 2 2 1 1 5 1.8 Glossary
61968-5 2 2 2 2 1 5 1.8 Operations Planning
61968-7 2 2 2 2 1 5 1.8 Extensions Planning
DER 1 2 1 2 3 5 1.8
61968-1-1 3 1 1 2 1 2 6 1.7 Integration profile
PHEV/PEV 1 2 2 1 2 5 1.6
Customers (mgmt,
61968-8 2 1 1 1 1 2 3 7 1.6
billing)
HAN 1 1 1 1 3 5 1.4
current pending postponed non-modelling

[source: Tanja Kostic]
Slide 11
Priorities:
Current modelling priorities
• Driven by interoperability (IOP) tests

– 2009: Metering (Part 9) + balanced and unbalanced CDPSM (Part
13 Ed.2)
– 2010: NetworkDataSet (Part 4 Ed.2) for CDPSM needs (GIS-
DMS/OMS exchange)
• Those common classes that support the above
• Overall CIM modelling principles, naming rules, network model
for T&D, coordination with CMM
• Part 4 maintenance cycle
• Part 3 maintenance cycle (some useful for Part 5)
• Metering-related packages (Part 9 Ed. 2)
• (continuous: clean-up for consistency/correctness,
simplification, diagrams, documentation)
Slide 12
CIM model and Part 11 evolution:
Normative vs. informative
• Introduced in January 2009
• WG14 package split to normative and informative (unstable, work-in-
progress)
– WG13 also started applying this approach to their obsolete packages 
• Condition for “normativity”
– Be used in messages of Part 9 Ed.1 and Part 13 Ed.2
– Be used in messages of Ed.2 of Parts 4, 3, 5 (priority by the WG14 roadmap)
• WG14 uses Informative package as a sandbox, with expiration date for
elements
– Move (potentially refactored) classes to normative packages – these are
maintained by WG14
• After expiry date, delete informative classes/relationships from the
model
– WG14 SharePoint has the archive of all model releases where deleted
elements can be found
– CIM users can take over and evolve deleted elements and potentially submit
through standard CIM issues form the request for inclusion into standard
CIM – modelling team decides whether the extension is considered as
globally useful and thus provided as standard CIM (and not custom for a
product/project/customer/vendor)
Slide 13
CIM model and Part 11 evolution
Model releases and IOPs
• WG14 follows the same timing as WG13
• IOPs take place in Q4 of a year
– WG13 does not have IOP this year, but in April 2010, for CIM14
• Given model version (used for IOPs) is frozen 2-3 months
before IOPs
– Base CIM end July (14v12), DCIM mid September (10v27)
• Modelling team evolves new versions of the model with
changes in informative parts only
• Issues identified in IOPs are addressed and resolutions
included in official DCIM release (Q1 of next year) used for Part
11 FDIS
– WG13 has the same approach for IEC61970-301
• After January meeting, we branch the model
– Version 14vXX-10vYY (developed during 2009) is for Part 11/301
FDIS
– IEC61968 package is merged by CMM into the combined 15vYY
– Copy of it is saved as 15vYY-11v01 and evolved for IOPs in 2010
Slide 14
Schedule until 2010-Q2
• Models for 2009 IOPs:

– CPSM IOP based on CIM14 (14v12)
• frozen end July 2009
– Metering and CDPSM IOPs based on DCIM10 (10v27)
• frozen mid September 2009
• no changes that would impact Part 9 FDIS messages
Model usable for all IOPs 2009
• Part 11 CDV comments:
– Arrived end August 2009
– We’ll address them in October 20 conference call
• CIM and DCIM FDIS:
• FDIS of 61970-301 Ed.4 and FDIS of 61968-11 Ed.1 planned
after January 2010 meetings
• Will include fixes, provided as high priority IOP issues
• To be submitted not later than end Q1-2010
Slide 15
Agenda

– Model Evolution
– Messaging
Slide 16
IEC 61968 Basic Message Structure
Slide 17
Message Header
Slide 18
Message Types Are Created By Combining IEC 61968 Verbs With
Information Exchange Topics, Referred To As Nouns
Verbs Meaning Message Body

CREATE The CREATE verb is used to publish a request to All sections (data
the master system to create a new document. required to create the
document)
CHANGE The CHANGE verb is used to publish a request to All sections (key(s) +
the master system to make a change in the data to be changed)
document based on the information in the
message.
CANCEL The CANCEL verb is used to publish a request to Header information +
the master system to cancel the document. The message content key(s)
CANCEL verb is used when the business content
of the document is no longer valid due to error(s).
CLOSE The CLOSE verb is used to publish a request to Header information +
the master system to close the document. The message content key(s)
CLOSE verb is used when the business document
reaches the end of its life cycle due to successful
completion of a business process.
DELETE The DELETE verb is used to publish a request to Header information +
the master system to delete the document. The message content key(s)
DELETE verb is used when the business
document should no longer be kept in the
integrated systems either due to error(s) or due to
archiving needs.
GET The GET verb is used to publish a request to the One or more document
master system to get the current data for a given reference codes +
document reference code or a set of documents. Key(s)
Slide 19
Verbs Meaning Message Body
CREATED The CREATED verb is used to publish the All sections
creation of a document as a result of either an
external request or an internal action within the
master system of that document.
CHANGED The CHANGED verb is used to publish the All sections (key(s) +
change of a document as a result of either an changed content)
CLOSED The CLOSED verb is used to publish the normal Header information +
closure of a document as a result of either an message content key(s)
CANCELED The CANCELED verb is used to publish the
cancellation of a document as a result of either an
Header information +
message content key(s)
(IEC 61968
Verbs - continued)
SHOW The SHOW verb is used to publish the most All sections
current content of a document as a result of either
an external GET request or an internal action
within the master system of that document.
REPLY The REPLY verb is used to publish the processing Header information +
result of an external request to the master system message content key(s)
to create, change, delete, cancel, or close a + confirmation
document. The REPLY message type could information +
contain specific confirmation information as to alternatives (optional)
whether the request is processed successfully or
not and provide alternatives if applicable.
SUBSCRIBE The SUBSCRIBE verb is used to publish the Header information +
request to ask the master system of a document message content key(s)
to publish a CHANGED document whenever there
is a change to the document.
UNSUBSCRIB The UNSUBSCRIBE verb is used to publish the Header information +
E request to ask the master system of a document message content key(s)
to stop publishing a CHANGED document
whenever there is a change to the document.
Slide 20
Message Payload of “End Device Control” of IEC 61968-9
XSD Tag Names Are

From Relevant Data
Elements in the CIM
Slide 21
“End Device Control” Sample XML
<?xml version="1.0" encoding="UTF-8"?>

<m:EndDeviceControls xsi:schemaLocation="http://iec.ch/TC57/2009/EndDeviceControls#
EndDeviceControls.xsd" xmlns:m="http://iec.ch/TC57/2009/EndDeviceControls#"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<m:EndDeviceControl>
<m:mRID>53185955_D0AB</m:mRID>
<m:drProgramLevel>3</m:drProgramLevel>
<m:drProgramMandatory>true</m:drProgramMandatory>
<m:priceSignal>0.2</m:priceSignal>
<m:type>PRICE</m:type>
<m:DemandResponseProgram>
<m:type>RTP</m:type>
</m:DemandResponseProgram>
<m:scheduledInterval>
<m:end>2001-12-17T10:30:47Z</m:end>
<m:start>2001-12-17T09:30:47Z</m:start>
</m:scheduledInterval>
</m:EndDeviceControl>
</m:EndDeviceControls>
Agenda

– Model Evolution
– Messaging
Slide 23
IEC 61968-4: Records and Asset Management
• 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 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 24
ChangeSet The NetworkDataSet is organized by logical
(from DataSets) Role (vs. physical asset) and may represent
0..n various views, such as as-built, nominal,
... operational, study, etc.
NetworkDataSet
(from DataSets) ChangeItem
0..n (from DataSets)
0..1 0..n
0..n 0..1
0..n
0..n
0..n
PowerSystemResource 0..n
0..1
(f rom Core)
LoadDataSet LandBase
(f rom DataSets)
0..1
(f rom DataSets)
1..n
0..n 0..n Asset
0..n (f rom AssetBasics)
0..n
0..n
Circuit 0..n CircuitSection
(f rom DataSets) (f rom DataSets)
1..n 0..n
Everything from the IEC 61970 Wires

Package may be included. Connectivity
Is based on IEC 61970 Topology
Slide 25
From the logical view to the physical asset view of the same object.
PowerSystemResource 0..n
Organisation
(from Core) (from TopLevel)
0..n
OrgPsrRole
0..n 0..n (from AssetBasics)
1..n
DocPsrRole OrgAssetRole
(from AssetBasics) (from AssetBasics)
AssetPsrRole
(f rom AssetBasics)
ErpInventory
(from ERP_Support)
0..1
+Documents DocAssetRole 0..n 0..n

0..n (from AssetBasics) 0..1
0..n
Document 0..n Asset
(from DocumentInheritance) (from AssetBasics)
0..1
0..1
AssetModel 0..n 0..1 TypeAsset FinancialProperties
(from AssetBasics) (from TypeAsset) (from AssetBasics)
Slide 26
• 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 27
Graphical Rendering
• GML has been designed to uphold the principle

of separating content from presentation
• GML provides mechanisms for the encoding of
geographic feature data without regard to how
the data may be presented to a human reader
• Since GML is an XML application, it can be
readily styled into a variety of presentation
formats including vector and raster graphics, text,
sound and voice
• GML is standardized through ISO
• ISO 19136 - Geographic information - Geography Markup
Language (GML)
Slide 28
Presentation of Real World Objects – Key Classes
GmlPointGeometry
Location GmlDiagramObject (f rom GML_Support)
(from Locations) (from GML_Support)
GmlLineGeometry
1 0..10..1
0..1 (f rom GML_Support)
0..1
0..n 0..n 0..1
Diagram GmlPosition GmlPolygonGeometry

(f rom GML_Support)
(from Presentation) (from GML_Support)
0..n 0..n
0..n
1 0..1 1..n
Map
GmlTextSymbol
(f rom Presentation) GmlCoordinateSystem (f rom GML_Support)
(from GML_Support)
0..n 0..n
0..n 0..n
GmlRasterSymbol GmlPointSymbol GmlLineSymbol GmlPolygonSymbol
(f rom GML_Support) (f rom GML_Support) (f rom GML_Support) (f rom GML_Support)
Slide 29
Case Study: Asset Management System Used to Initialize System Control
Center System (source: DistribuTECH2002)
Asset
Management
Asset data sent in XML

Adapter Transformation into CIM Objects
Publish AMS data in CIM format
Integration Bus
Adapter Subscribe to Asset data
System
Control Center
[presented at DistribuTECH 2001]
Slide 30
Case Study: Operations Model Capabilities (source: DistribuTECH2002)
AMS
DMS
Slide 31
Case Study: LIPA Asset Management and Organization (source: IEEE 2009)
Asset Owner Asset Manager

Responsibilities: • Asset Optimization
• Asset valuation • Asset yield contribution
• Investment analysis & strategy understanding
• Contract negotiation/structuring • Financial structuring
• Regulatory oversight • Business development
• Market & economic analysis • Asset specifications &
• Portfolio management standards
• Capital allocation • Full lifecycle asset
• Asset financial & operating management
performance analysis • Asset data management
• Asset planning • Workload management
• Asset acquisition & • Asset financial and
monetization operating performance
analysis
• Asset strategy & plan
Service Provider
development
Responsibilities: • Asset full lifecycle
• Construction & maintenance financial & operational
project management data analysis
• Materials sourcing & inventory • Regulatory strategy &
management negotiation
• System engineering & design • Contract management
• Bargaining unit negotiations • Risk management
• Workforce scheduling & • Asset data requirements
deployment definition
• Work practice design & • Asset opportunity
development development & analysis
• Asset data input and collection • Industry Best Practices
• Workforce training
• Marketing & sales of services
• Competitor analysis
Slide 32
Case Study: LIPA Asset Management Concept (source: IEEE 2009)
MSA
Asset
AssetManagement
Management
Management
Asset Service
Owner Asset Manager Provider
LIPA
LIPA Risk
Management Impl Exe
Goals Strategy Plan
Assess Effectiveness
Goals ement cute
Customer
Satisfaction Data and Process Integration – CIM/IB/SOA
Financial Risk
RiskAssessment
Assessment
Technical Risk Risk Risk
Performance Status Drivers Tolerance
Regulatory
Assets & Processes (O&M&Planning) aspects
KRIs/Risk
KPIs Visualization Dynamic Criticality
FMEA Indicators
Slide 33
Some Foundational Relationships
of the IEC CIM for Asset Management
Document Organisation
Information Containers Such As Entities Performing One or More
Asset Catalogues, Trouble Tickets, Roles Such As Customer, Supplier,
Work Orders, etc. Manufacturer, Service Provider, etc.
Location
A Street Address, Coordinates Erp Person
For a Geographic or Schematic A Person Performing Roles Such
reference system, etc. Dispatcher, Field Operator, etc.
Power System Resource Activity Record

Electrical Network Role Used For
Used to Record Each State
Planning, Operations, etc.
change of CIM objects
Type Asset Asset Model Asset

Compatible Unit For Particular Model and Version Physical Plant Filling A Role
Design & Procurement of a Vendor's Product Such As A Transformer, Pole, etc.
Slide 34
PowerSystemResource
(from Core)
0..n
DocPsrRole
(from AssetBasics)
DocAssetRole
(from AssetBasics)
0..n
AssetListRole
Document 0..n 0..n Asset (from AssetBasics)
(from DocumentInheritance) (from AssetBasics)
0..n 0..n
Collecti on 0..n AssetList

Specification
(f rom AssetBasics) 0..n (from Collections) (f rom AssetBasics)
TypeAssetCatalogue AssetCatalogue
(from AssetBasics) (from AssetBasics)
0..1 1
0..n
AssetModel 0..n 0..1 TypeAsset

(from AssetBasics) (from TypeAsset)
0..n
0..1
AssetCatalogueItem
0..n (f rom AssetBasics)
Slide 35
• 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 36
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 37
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 38
Generic “TypeAssets” are used for Design
CostType 0..1
CUGroup
(f rom WorkClosing)
(f rom WorkStandards)
0..1 0..n
0..n 0..1
0..n
0..n
CompatibleUnit 0..n CUContractorItem
(from WorkDesign) (f rom WorkStandards)
0..n
0..n
0..n 0..n 0..n
0..n 0..n
Procedure
(f rom WorkInspectionMaintenance)
0..n 0..n
0..n 0..n
CUMaterialItem CULaborItem
(f rom WorkStandards)
CUAsset CUEquipmentItem (f rom WorkStandards)
(from WorkStandards) (from WorkStandards)
0..n
0..1
0..1
0..1
0..1
0..1
TypeMaterial
(f rom WorkStandards) TypeAsset
(from TypeAsset)
Slide 39
IEC 61968-3: Network Operations

– Measurement list;
– Operational restrictions;
– Outage records;
– Safety documents;
– Switching schedules.
• More to be added during maintenance
cycles
Slide 40
An Example: Safety Document Classes
Organisation
(from TopLevel) OrgErpPersonRole
DocOrgRole
(from TopLevel)
(from TopLevel)
0..n
0..n
0..n
0..n
SafetyDocument Document ErpPerson
(from DocumentInheritance) (from ERP_Support)
(from Operational)
0..n
0..n 0..n
0..n
ActivityRecord
OperationalRestriction 0..n (from ActivityRecords)
(from Operational)
0..n
PowerSystemResource
(from Core)
0..n
0..1
ClearanceTag 1 ConductingEquipment Equipment PSRType
(from Outage)
(from Core) (from Core) (from Core)
0..n
Slide 41
Safety Document Message Type
Slide 42
IEC 61968-8: Customer Support

– Trouble Ticket
– Failure Event
– Planned Outage Notification
– Call Back
– Compliance Event
– Outage History
– Service Extension Request
– ServiceRequest
– CustomerServiceAgreement
– Customer Billing
– Construction Billing
Slide 43
Aspects of Customer Accounts
Agreement
CustomerAccount (from TopLevel) Equipment ConductingEquipment
(from Consumers) (f rom Core) (f rom Core)
1..n 1 0..n
1 0..n 0..n
CustomerData CustomerAgreement 0..n ServiceLocation EnergyConsumer

(from Consumers) (f rom Wires)
(from Consumers) (from Locations)
0..n
1
0..1 0..1 0..n 0..n 0..1
1 0..n 0..n
0..1 0..n
Organisation ErpPerson ServiceKind SDPLocation 0..n ServiceDeliveryPoint
0..n (f rom Consumers) (from Locations)
(f rom TopLev el) (f rom ERP_Support) (from Metering)
0..n 0..n
1 0..n
0..n 0..n
0..n
Tariff PricingStructure 1 PowerQualityPricing
(from Consumers) (f rom Consumers) (f rom Consumers)
0..n 0..n 0..n
Slide 44
A Customer Account Message Type for AMI (IEC 61968-9)
Slide 45
IEC 61968-9
Reference
Model
IEC 61968-9: Automated Meter Reading and Control
• Current Message Types

– CustomerMeterDataSet
– MeterAsset
– MeterAssetReading
– EndDeviceControls
– EndDeviceEvents
– MeterReadings
– MeterReadSchedule
– MeterServiceRequest
– MeterSystemEvents
– EndDeviceFirmware
Slide 47
Metering Inheritance Package
Slide 48
Customer Overview – from a 61968-9 perspective
Slide 49
Document
Pricing structure model Customers::
PricingStructure
+ PricingStructures 0..*
•TariffProfile determines the cycle of + Tariffs 0..*
Document
operation for the tariff, such as hourly,
Customers::
daily, weekly, monthly, etc, at the end Tariff
of which it resets to start at the

+ Tariffs 0..*
beginning of the process again.
•TimeTariffInterval determines the + TariffProfiles 0..*
starting time for a particular interval + TariffProfiles

Document
+ TariffProfiles
TariffProfile
and several instances of 0..*
+ tariffCycle: String [0..1] 0..*
TimeTariffInterval may be used to
construct a series of time intervals to + TimeTariffIntervals
+ ConsumptionTariffIntervals
realise a time of use tariff for example. 0..* 0..*
•ConsumptionTariff Interval TimeTariffInterval ConsumptionTariffInterval
determines the starting value of a + sequenceNumber: Integer [0..1] + sequenceNumber: Integer [0..1]
+ startDateTime: AbsoluteDateTime [0..1] + startValue: RealEnergy [0..1]
consumption interval and several
0..* 0..*
instances of + TimeTariffIntervals + ConsumptionTariffIntervals
ConsumptionTimeInterval may be
used to construct a series of I dent ifiedObject
Charge + Charges
consumption intervals to realise a + Charges
block tariff or a step tariff for example. 0..* + kind: ChargeKind [0..1] 0..*
+ fixedPortion: AccountingUnit [0..1]
+ variablePortion: PerCent [0..1]
+ ParentCharge
+ ChildCharges
0..1
0..*
Slide 50
Auxiliary agreements
• Receipting payments for

‘other items’ such as debt,
rates, taxes, municipal fines,
TV licences, garbage
collection charges, etc.
• The collection of such
revenue may be integrated
with token sales and
customer account payments
by means of auxiliary
agreements and auxiliary
accounts.
• AuxiliaryAccount captures the
dynamic information about
the charges and payments
made against the account.
Slide 51
Slide 52
Slide 53
Example of Meter Reading Schedules and Readings
Slide 54
Meter Reading Options
• Meter Readings may be requested using a

variety of parameters:
– Specific meter, using the MeterAsset mRID
– Specific meter, using a meter name as known
to the Metering System
– EndDeviceGroups, where a EndDeviceGroup
identifies a group address used within the
Metering System
– As specified using a TimeSchedule
– Reading types can be specified to identify the
desired reading types
Slide 55
Slide 57
Meter Readings Type
• Key to the reporting of a value from a meter is

the reading type. The ReadingType class allows
the capture of the following information:
– mRID (to uniquely identify a reading type)
– channel number
– default quality
– default value data type
– dynamic configuration
– forward chronology
– interval length (in seconds)
– measurement type category
– unit of measure
– register digits
• Refer to IEC 61968-9 Annex for details
Slide 58
Device Control
Example type controls:

•Load control signal
•Price signal or schedule
•Remote disconnect
•Remote reconnect
•Demand reset
•Demand reduction signal
End Device Updates
Slide 60
Meter System Events (page 1)
Slide 61
Meter System Events (page 2)
Slide 62
Meter
Service
Requests
Example Meter Relationship from IEC 61968-9
Description of Item Value CIM Location Type
This communication MCM-ID EndDeviceAsset.DeviceFunction.ComFunction.amrAddress name/mRID

module
is servicing this end End-device ID MeterAsset.name name/mRID

device
(which is let’s say an End-device type ServiceDeliveryPoint.serviceType Attribute

electricity
meter)
using this connection Port Number EndDeviceAsset.DeviceFunction.ComPort Attribute
Upstream CommAsset EndDeviceAsset.DeviceFunction. name/mRID
at this location ServiceDeliveryPoint ServiceDeliveryPoint.name name/mRID
for this account Account ID CustomerAccount.name name/mRID
and this customer Customer ID CustomerAccount.Customer.name name/mRID
In this utility Business Unit
Commencing at this Installation date ActivityRecord.statusDateTime Attribute

date
Because “In-Service” ActivityRecord.status Attribute
Slide 64
Agenda

– Model Evolution
– Messaging
Slide 65
GWAC Stack – Levels of Interoperability
[Source: GridWise Architectural Council Interoperability Context Setting Framework]

Slide 66
NIST Conceptual Model

[Source: NIST InterimSlide
Roadmap]
67
Interoperability Layers
Slide 69
(of UCAIug/OpenSG/SG-Systems WG)
•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
Slide 70
communicate with other businesses or enterprises (generally defined as third parties).
Case Study: Consumers Energy and AMI-Ent TF
Customer Distribution
Info. & Billing Management
HAN
Management
Outage
Revenue AMI Service
Management
Protection Manager
Enterprise Bus + Common Model & Service
AMI-
AMI-ENT
Demand
Customer
Response
Portal AMI Network
Management
Asset
Management
Third Party Meter
Meter Asset
Portal Data
Management
Management
Representative of AMI-ENT components, not all inclusive.
Slide 71
Case Study: AMI-Ent Use Cases
Slide 72
Case Study: AMI-Ent Service Identification
Slide 73
Case Study: AMI-Ent Inventory of 142 CIM-Based Services
Supporting Use Cases for AMI-Enterprise
Use Case & Integration Functional Description of Operation Service Name Service Operation Service Service Provider Information Object
Scenario Requirement the Service Pattern Consumer (Inbound - WS) (normalized)
(Outbound)
B1-S1 REQ-B1004 MDUS receives the meter Created MeterReading CreatedMeterReading Head End MDUS MeterReading
reading results on
B1-S12 REQ-B1011 scheduled basis.meter
MDUS receives Created MeterReading CreatedMeterReading Field Tool MDUS MeterReading
reads
B1-S15 REQ-B1012 MDUS notifies meters with Created MeterSystemEvent CreatedMeterSystemEvent MDUS? MDUS MeterSystemEvent
reading problems
B1-S15 REQ-B1013 AMI Head End operator Created MeterServiceOrder CreatedMeterServiceOrder MDUS Head End MeterServiceOrder
receives meter service
orders
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 Create MeterReading CreateMeterReading TBD Head End MeterReading
request for a meter reading
B1-S2 REQ-B1002 on demand
MDUS receives a meter Created MeterReading CreatedMeterReading Head End MDUS MeterReading
reading on demand
B1-S2 REQ-B1003 A user or system receives Created MeterReading CreatedMeterReading MDUS TBD MeterReading
a meter reading on
demand
B1-S3 REQ-B1006 CIS receives meter event Created MeterSystemEvent CreatedMeterSystemEvent Head CIS MeterSystemEvent
End/MDUS
B1-S7 REQ-B1009 MDUS receives the request Create MeterReading CreateMeterReading Third Party MDUS MeterReading
for meter readings Portal
B1-S7 REQ-B1010 Third party receives the Created MeterReading CreatedMeterReading MDUS Third Party Portal MeterReading
meter readings
B1-S8 REQ-B1009 MDUS receives the request Create MeterReading CreateMeterReading Third Party MDUS MeterReading
for meter readings Portal
B1-S8 REQ-B1010 Third party receives the Created MeterReading CreatedMeterReading MDUS Third Party Portal MeterReading
meter readings
B2-S1 REQ-B2001 Send scheduled shut off Created ScheduledEvent CreatedScheduledEvent CIS Head End ScheduledEvent
notification
B2-S1 REQ-B2002 Send scheduled shut off Created ConnectDisconnect CreatedConnectDisconnect CIS Head End ConnectDisconnect
command
B2-S1 REQ-B2003 Send scheduled shut off Created CommonConfirmation CreatedCommonConfirmation Head End CIS CommonConfirmation
command confirmation
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 74
Status/Plans:
1) Verified applicable XSDs are
compliant with IEC 61968-9
2) Submitted to CIM
InterOperability Testing; TBD
for when it will be included
(Margaret)
3) Proposed requirements and
extensions being submitted
to WG14 for consideration.
http://osgug.ucaiug.org/sgsystems/Pages/Voting%20Ballots.aspx
Slide 75
OpenHAN - Home Area Network – Collaboration between UCA, ZigBee,
and IEC
SEP 2.0 is being developed by ZigBee/
OpenHAN SRS given to ZigBee HomePlug SEA, is intended to be CIM-based
and was used for SEP 1.0 which is being coordinated with IEC
(and NIST, et al.)
Ot
h
s Ga er Pr
tion Ce (In tewa emis
plica rtif
ied
ter
ne y
e
Ap DG t)
tive Ce
rac
rtif
e ied
Int Hy Plu
ility bri g-In
t d
erU Ad
um van P Ce
ns ce Uti rem rtifie (e. HA
Co dI
HD lity ise
A E
d g.,
Se Cont
n Ga pplic MS t T rol
atio
Lo op ler
ad tew ati
Co unic ay on Sm Bo
x)
ntr m art
ol om Ap
PC red C nel Ho
plia
nc
T cu han me e
Se C
tility Ca Healt
U R re h
No eve Lig
n-e nu htin s
lec e G
tion
gC
tric ra on
Re Me de Ho tro plica
ve
Ele nu
ter me l
r Ap
ctr e
ic M Gra
Se me
ete de
cu
rity nsu
r ns Co
licatio
Uti p
lity AM Ap
Ow I G lity
ne atew
da Uti
nd ay
Op t
era as
ted adc gnal)
o i
Br e s
AM blic ric
IB
y Pu .g,., p
ac lit e
kh
au Uti nel (
lN
etw h an
ork C
Slide 76
Distributed Energy Resources - Collaboration between NIST,
UCA, ZigBee, and IEC
Discrete Metering,
Incentive Programs, and
Demand Response for
PEVs
© Copyright 2008, Southern California

Edison
Enable Net Metering,

Discrete metering and
Integrated Energy Home Energy Storage
Management w/Solar Creates Opportunities
Panel for Increased
Renewables
[source: Jose A. Salazar, SCE]

Slide 77
Future State- PHEV Connection (120VAC) &
Communication Scenario B

Slide 78
Future State- Battery EV w/ PLC Connection & Communication
Scenario A

Slide 79
OpenSG’s OpenADE - Automated Data Exchange –
Collaboration among NIST, UCA and IEC
Third Parties
Energy
Energy
Usage
Management
AMI
AMI&&
Internet
Internet
Utilities
Consumers
Energy
Delivery and Management
The Changing Dynamics of Energy Services
Slide 80
OpenADE Scope
• Authorization
• Publication
• 1.0 –
Interval
consumption,
after “VEE”
• 2.0 – (TBD)
Near-realtime
(from HAN)
Pricing / billing
information
October 19, 2009 OpenSG - OpenADE 81

Slide 81
OpenSG’s OpenADR – Automated Demand Response –
Collaboration among NAESB, NIST, UCA, OASIS, ZigBee, and IEC
OpenADR OpenADR
Message Message
LOAD EMCS LOADS

Utility/ISO Utility/ISO
Facility Facility
Direct Load Control,

(not OpenADR
Messages)
Facility
Proprietary OpenADR
OpenADR Communications Message
Message
Facility
Utility/ISO
Utility/ISO Intermediary Third Party
Service Provider
Facility
Slide 82
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 must 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 to!
Slide 83

CIM For Enterprise Integration: CIM University, CIM Users Group

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

CIM For Enterprise Integration: CIM University, CIM Users Group

Загружено:

Авторское право:

Доступные форматы

CIM for Enterprise Integration

For further information, contact:

• CIM for enterprise integration (IEC 61968)

Operations Protection Maintenance

Wires Integration Anarchy!

OMS GIS CIS

WMS DMS AMR

Interface Interface Interface Interface Interface Interface Interface

IEC 61968 Compliant Middleware Services

Interface Interface Interface Interface Interface Interface Interface

(NE) (MR) (ACT)

Electric Distribution Network Generation and Transmission Management,

Semantically Consistent ESB

DMS Information Flow Design

• CIM for enterprise integration (IEC 61968)

+ date: AbsoluteDateTime [0..1] = 2009- 04- 01

Metering LoadControl PaymentMetering

current pending postponed non-modelling

• Driven by interoperability (IOP) tests

[source: Tanja Kostic]

• Models for 2009 IOPs:

[source: Tanja Kostic]

• CIM for enterprise integration (IEC 61968)

Verbs Meaning Message Body

XSD Tag Names Are

• CIM for enterprise integration (IEC 61968)

• Network Data Set

Everything from the IEC 61970 Wires

+Documents DocAssetRole 0..n 0..n

• GML has been designed to uphold the principle

Diagram GmlPosition GmlPolygonGeometry

Asset data sent in XML

Adapter Subscribe to Asset data

Asset Owner Asset Manager

Power System Resource Activity Record

Type Asset Asset Model Asset

Collecti on 0..n AssetList

AssetModel 0..n 0..1 TypeAsset

• Work is created any time a person is required to

• Current Message Types:

• Current Message Types:

• Current Message Types:

CustomerData CustomerAgreement 0..n ServiceLocation EnergyConsumer

• Current Message Types

•TariffProfile determines the cycle of + Tariffs 0..*

of which it resets to start at the

starting time for a particular interval + TariffProfiles

•ConsumptionTariff Interval TimeTariffInterval ConsumptionTariffInterval

• Receipting payments for

• Meter Readings may be requested using a

• Key to the reporting of a value from a meter is

Example type controls:

Description of Item Value CIM Location Type

This communication MCM-ID EndDeviceAsset.DeviceFunction.ComFunction.amrAddress name/mRID

is servicing this end End-device ID MeterAsset.name name/mRID

(which is let’s say an End-device type ServiceDeliveryPoint.serviceType Attribute

using this connection Port Number EndDeviceAsset.DeviceFunction.ComPort Attribute

Upstream CommAsset EndDeviceAsset.DeviceFunction. name/mRID

at this location ServiceDeliveryPoint ServiceDeliveryPoint.name name/mRID

for this account Account ID CustomerAccount.name name/mRID

and this customer Customer ID CustomerAccount.Customer.name name/mRID

In this utility Business Unit

Commencing at this Installation date ActivityRecord.statusDateTime Attribute