INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
TC 57
CIM Model Manager Report (WG13, WG14,
WG16 & WG21)
CIM Users Group, Atlanta, Georgia
November 17, 2016
CMM Responsibilities/Activities
Chair modelling meetings
Manage UML
Keep track of issues
TC57 CIM coordination between WG13,
WG14 and WG16
P 2
Current Model Managers
WG13 Report – Kendall Demaree, WG13
Model Manager
WG14 Report – Margaret Goodrich, WG14
Model Manager
WG16 & WG21 Report – Becky Iverson,
WG16 & 21 Model Manger – Presented by
Margaret Godorich
P 3
Modeling Meetings
Regular web conferences for all three Groups
Weekly 1-1.5 hour meetings 9:30 US Central, 16:30 EU
Central
Typically 8 to 12 people attending each call
Topics
New requirements and issues
Resolving issues
Shrink backlog, close dead issues
Prioritize and combine
Priority on common issues
Check new issues to be solvable
Develop IEC 61970, 61968 and 62325 documents
P 4
Model Management, WG Models
P 5
One UML package per WG
61970 support the other
61968 depend on 61970
62325 depend on the other
Model synchronization
WG13619706196862325
WG14619706196862325
WG16619706196862325
Model Management, UML Files
Zip archive including
complete EA file UML
WG13, WG14, WG16 and combined issues spread sheets
Summary documents describing the CIM versions
Xmi files for import in other UML tools
iec61970cim17v19_iec61968cim13v09_iec62325cim03v14
61970 CIM17 version 19
61968 CIM13 version 9
62325 CIM3 version 14
P 6
CIM 16 Status
UML frozen
iec61970cim16v33_iec61968cim12v08_iec62325cim03v01a
The basis for ENTSO-E CGMES 2.4.15
Corresponding IEC Specification being created
IEC 61970-301 Ed6
IEC 61970-452 Ed3 – CGMES EQ
IEC 61970-456 Ed2 – CGMES SSH, TP and SV
IEC 61970-552 Ed2
61970 CIM 16 Summary
HVDC
Dynamics
Steady State Hypothesis (SSH) power flow input
Grounding models
Nonlinear shunt compensators
Short circuit calculation based on IEC 60909
Phase shifter model updates
Profiles supporting both transmission and
distribution
Issues found by ENTSO-E resolved
Enumeration harmonizationP 8
61970 CIM 17 Status
Achievements
Change modelling
ICCP configuration model
Datatype changes for WG16
Issues actively worked on
50 - almost all from ENTSO-E
10 Big ones
P 9
Meta Data in 61970-552 Header
class Pa r t552
Sta tements Ful lModelDif fer enceModel
Model
+ created: DateTime
+ scenarioTime: DateTime
+ description: String
+ modelingAuthoritySet: URI [0..1]
+ profile: URI [1..*]
+ version: Integer
«Primitive»
URI
{root}
+Depending 0..*
+DependentOn 0..*
+reverseDifferences
0..1
+forwardDifferences
0..1
+SupersededBy 0..*
+Supersedes
0..*
Why New Meta Data Model?
The 61970-552 UML just documentation, not validated
by tools as regular CIM data
61970-552 is a serialization format extended with meta
data about content
Profile
Model version
Source of model
Time for scenario and creation
Dependencies
Changes
Treat meta data the same way as any other CIM data
Meta Data in 61970-301
cla ss Gener icDa taSet
Cor e::Ident if iedObject
Da taSetMember
InstanceSet
+ version: Integer
+ minorVersion: Integer
ObjectCr ea t ionObjectDelet ionObjectModif ica t ion
ChangeSetMemberChangeSet
ObjectRev er seModif ica t ion
Da taSet
InstanceSetMember
P r of i le
+ObjectReverseModification
0..1
+ObjectModification
0..1
+TargetingCIMDataObject
0..*
+TargetObject
1
+Profileset
0..*
+Profile 1..*
+ObjectChange
0..*+Changeset
0..1
+AlternateCIMDataObject
0..*
+Dataset
1
+PropertiesCIMDataObject
0..1
+PropertiesObject
0..1Change Model –>
Frames for the rest
yet to finalize
ICCP Configuration Data
Goal to automate ICCP configuration
Providers describe the data they make
available
61970-452/ICCPExchange
61970-452/EQExchange
TO1
ICCPProvidedPoint A
RTO
ICCPProviderICCPProvider& Client
TO2
ICCPClient
MeasValX
SourceRTU
MeasO
ICCPProvidedPoint B
Colors- Turquoise; Data owned and exported by TO/RTO- Red; Data imported by TO/RTO
MeasValX
SourceICCP
MeasO
MeasValX2
SourceICCP
MeasO
MeasValX
ICCPProvidedPoint C
EQ
EQ
Generic Bilateral Exchange
class Gener icB i la ter a lExchange
IdentifiedObject
B i la ter a lExchangeAgr eement
IdentifiedObject
B i la ter a lExchangeActor
IdentifiedObject
P r ov idedBi la ter a lPoint
Meas::Measur ementVa lue Meas::Contr ol
IdentifiedObject
Meas::Measur ementVa lueSour ce
IdentifiedObject
Meas::IOPoint
PowerSystemResource
SCADA::
Communica t ionLink
+CommunicationLink
0..n
+BilateralExchangeActor
0..1
+MeasurementValueSource 1
+MeasurementValues 0..*
+ProvidedBilateralIOPoint0..*
+BilateralExchangeActor
1
+ConsumerBilateralExchange
0..*
+Consumer
0..1
+IOPoint0..1
+BilateralToIOPoint0..*
+Provider
1
+ProviderBilateralExchange
0..*
ICCP Configuration
cla ss ICCP
TASE2Bi la ter a lTable
+ bilateralTableID: String
+ tase2version: String
+ bilateralTableVersion: String
IPAccessPoint
+ address: String
+ addressType: IPAddressKind
+ gateway: String [0..1]
+ subnet: String [0..1]
ICCPP r ov idedPoint
+ scope: ICCPScope
+ pointType: ICCPPointKind
+ pointQuality: ICCPQualityKind
+ accessPriviledge: ICCPAccessPrivilegeKind
TCPAccessPoint
+ keepAliveTime: Integer [0..1]
+ port: Integer [0..1]
ISOUpper Lay er
+ osiPsel: String
+ osiSsel: String
+ apTitle: String [0..1]
+ osiTsel: String
+ apInvoke: int [0..1]
+ aeInvoke: int [0..1]
+ aeQual: int [0..1]
IdentifiedObject
ICCP Infor mat ionMessage
+ localReference: String [0..1]
+ scope: ICCPScope [0..1]
IdentifiedObject
B i la ter a lExchangeAgr eement
IdentifiedObject
P r ov idedBi la ter a lPoint
«enumeration»
ICCPScope
VCC
ICC
«enumeration»
IPAddr essK ind
IPv4
IPv6
PowerSystemResource
SCADA::
Communica t ionLink
«enumeration»
ICCPPointK ind
discrete
real
state
stateSupplemental
singleProtectionEvent
packedProtectionEvent
«enumeration»
ICCPQua l i ty K ind
none
qualityOnly
qualityAndTime
extended
extendedwithQualityTime
«enumeration»
ICCPAccessP r iv i legeK ind
readOnly
readWrite
IdentifiedObject
B i la ter a lExchangeActor
ICCPV ir tua lContr olCenter
+ clientAndServer: Boolean
+ minimumUpdateInterval: int
+ calling: Boolean
+ TransportSecurityRequirement: Boolean
+ applicationSecurityRequirement: IEC62351-6ApplicationSecurityKind
+ nameOfLocalICC: String
+ supportForBlock1: Boolean
+ supportForBlock2: Boolean
+ supportForBlock3: Boolean
+ supportForBlock4: Boolean
+ supportForBlock5: Boolean
+ supportForDepriciatedBlock8: Boolean
«enumeration»
IEC62351-
6Appl ica t ionSecur ity K ind
noSecurity
applicationLevel
end-to-end
Publ icX509Cer t i f ica te
+ issuerName: String
+ serialNumber: String
IdentifiedObject
Meas::IOPoint
+ConsumerBilateralExchange
0..*
+Consumer
0..1
+PublicX509Certificate0..*
+TCPAccessPoint 0..1
+Provider
1
+ProviderBilateralExchange
0..*
+ProvidedBilateralIOPoint
0..*
+BilateralExchangeActor
1
+IOPoint 0..1
+BilateralToIOPoint 0..*
+ICCPInformationMessage
0..*+TASE2BilateralTable
0..*
+PublicX509Certificate0..*
+ISOUpperLayer
0..1
+CommunicationLink0..n
+BilateralExchangeActor
0..1
61970 CIM 17 Work In Progress
Frames for meta data
Goal move away from 61970-552 header
Network model projects
Manage future or passed network model
changes
Smart grid and DER behavior
Distribution networks no longer only loads
Availability/Outage plans
Network studies with market data
Mapping of schedules and forecasts on network
modelP 16
Case Building
Time
Data
EQ
Equipment
And
Parameters
Power
System
Projects
And
Audit trails
OutagesEquipment
Outages
Operational
Data
- Forecasts
- Schedules
- Patterns
- Recordings
- Measurements
SSH
Consumption
Production
Interchange
Limits, ratings
Voltage
Tap positions
Switch positions
Scenarios
ΔΔ
ΔΔ
ΔΔ
Δ
Δ
Δ
Study future
models
Study future
power flow
Now
61970 CIM 17 Work In Progress
System Integrity Protection Schemes – SIPS
Needed in Security Assessment
Remedial actions
Reactions to events
Operational limits, dynamic ratings
Weather and topology dependent
Alternate models
Models not always the same but similar
Feeder model
ENTSO-E Smaller issues
CGMES conformity testing generate issues
P 18
61970 CIM Non-modeling issues
61850 - CIM exchange and harmonization
Standardization of profile creation
CIM for Enterprise Canonical Data Model
Interoperability 61970-552/CIMXML – XML
Schema
P 19
Conclusions
ENTSO-E adoption of CIM -> CIM used in EU
A huge increase in use
Evolution of 61970 CIM and CGMES is rapid
ENTSO-E working on CGMES 2.5 based on CIM 17
Tough for WG13 to keep up
CGMES improved CIM interoperability a lot
WG14: System Interfaces for
Distribution Management
Mission, Scope:
Develop Standards for Distribution system
interfaces
Back-office applications such as OMS, CIS, WMS
Planning and DMS Operations
Package IEC61968 within TC57 CIM UML Model
P 21
Model Status Summary
IEC61968-11 Edition 2 released on IEC61968
CIM11v13 packaged with IEC61970 CIM15v01
IEC61968 CIM13 started in 2015 and packaged with
IEC61970 CIM17v08
IEC61968 CIM13v09 is the version of UML that was
used to generate IEC61968-11 Edition 3
Current model is posted on IEC WG14 Part 11
SharePoint Site and to the Current CIM Model
Drafts folders on the CIMug Site
Reviewed the Edition 3 CDV with the modelling
team on 11-8-2016
Submitted Edition 3 CDV to the IEC on 11-10-2016
P 22
Edition 3 Changes
Wire-Assembly change to support WG13
CDPSM
Outage model changes from Part 3 team & ODI
TF
Customer model changes proposed by Part 8
team
Asset Health to the Asset model from the Asset
Health Focus Community
DER changes from the Part 5 team
Work model changes from issues supplied by
EPRI
P 23
Wire-Assembly Change
P 24
Outage Model Changes
P 25
The Outage Data Initiative (ODI)
“New industry-led effort to provide consumers and first-responders with information about power outages:Today, a number of electric utilities and technology companies agreed to the development and use of a voluntary open standard for the publishing of power outage and restoration information. The commitment of utilities to publish their already public outage information as a structured data in an easy-to-use and common format, in a consistent location, will make it easier for a wide set of interested parties—including first responders, public health officials, utility operations and mutual assistance efforts, and the public at large—to make use of and act upon this important information, especially during times of natural disaster or crisis.”
(White House Press Release 05/28/2014)
Outage Model Changes
P 26
class ODI Ov er v iew
Oper a t ions::Outage
+ cause: String [0..1]
+ isPlanned: Boolean [0..1]
+ estimatedPeriod: DateTimeInterval [0..1]
+ actualPeriod: DateTimeInterval [0..1]
+ cancelledDateTime: DateTime [0..1]
+ summary: ServicePointOutageSummary [0..1]
«ODI Extension»
ODI_Outage
+ causeKind: OutageCauseKind
+ communityDescriptor: String
+ customersRestored: Integer
+ customersServed: Integer
+ metersAffected: Integer [0..1]
+ originalMetersAffected: Integer [0..1]
+ outageKind: OutageStatusKind
+ startTime: DateTime [0..1]
+ statusKind: CrewStatusKind
+ utilityDisclaimer: String [0..1]
Cor e::Ident if iedObject
+ aliasName: String [0..1]
+ description: String [0..1]
+ mRID: String [0..1]
+ name: String [0..1]
Common::Document
+ type: String [0..1]
+ authorName: String [0..1]
+ createdDateTime: DateTime [0..1]
+ lastModifiedDateTime: DateTime [0..1]
+ revisionNumber: String [0..1]
+ electronicAddress: ElectronicAddress [0..1]
+ subject: String [0..1]
+ title: String [0..1]
+ docStatus: Status [0..1]
+ status: Status [0..1]
+ comment: String [0..1]
Common::Loca t ion
+ type: String [0..1]
+ mainAddress: StreetAddress [0..1]
+ secondaryAddress: StreetAddress [0..1]
+ phone1: TelephoneNumber [0..1]
+ phone2: TelephoneNumber [0..1]
+ electronicAddress: ElectronicAddress [0..1]
+ geoInfoReference: String [0..1]
+ direction: String [0..1]
+ status: Status [0..1]
«enumeration»
OutageCauseK ind
planned
unplanned
animal
«enumeration»
Cr ewSta tusK ind
assigned
dispatched
arrived
fieldComplete
«enumeration»
OutageSta tusK ind
verified
estimated
«ODI Extension»
ERT
+ confidenceKind: ERTConfidenceKind
+ ert: DateTime [0..1]
+ ertSource: String
«enumeration»
ERTConf idenceK ind
high
low
Oper a t ions::
Incident
+ cause: String [0..1]
«ODI Extension»
OutageAr ea
+ earliestReportedTime: DateTime
+ metersServed: Integer
+ outageAreaKind: AreaKind
«enumeration»
Ar eaK ind
borough
county
parish
serviceArea
state
township
ward
zipcode
+Outage
0..*
+ERT 1
+Incident 0..1
+Location 0..1
+Incident 0..1
+ERT 1
+Incident
0..1
+Outage 0..1
Customer Model Changes
P 27
Asset Health Changes
P 28
class AssetHea lthOv er v iew
IdentifiedObject
Asset
AssetConta iner
IdentifiedObject
Asset Info
OrganisationRole
Manufactur er
IdentifiedObject
P r oductAssetModel
Document
P r ocedur eDataSet
Document
P r ocedur e
OrganisationRole
AssetOr ganisa t ionRole
AssetOwner
IdentifiedObject
AssetDeploy ment
IdentifiedObject
Cor e::Power Sy stemResour ce
IdentifiedObject
Common::Act iv ity Recor d
IdentifiedObject
Meas::Measur ementVa lueIdentifiedObject
Ana ly t icScor e
IdentifiedObject
Meas::Measur ement
IdentifiedObject
Ca ta logAssetTy pe
+ estimatedUnitCost: Money [0..1]
+ quantity: StringQuantity [0..1]
+ kind: AssetKind [0..1]
+ stockItem: Boolean [0..1]
+ type: String [0..1]
+Asset
0..1+AssetDeployment
0..1
+ProductAssetModel0..1
+AssetInfo 0..1
+ProcedureDataSet 0..*
+Asset0..1
+Procedures0..*
+Assets 0..*
+Assets
0..*+PowerSystemResources
0..*
+ProductAssetModels
0..*
+Manufacturer 0..1
+Procedure 0..1
+ProcedureDataSets0..*
+Assets
0..*+OrganisationRoles
0..*
+Asset
0..1
+Measurements0..*
+ProductAssetModel
0..*+CatalogAssetType
0..1
+Asset 0..*
+ProductAssetModel 0..1
+ProcedureDataSet
0..*
+MeasurementValue 0..*
+Assets
0..*
+ActivityRecords
0..*
+Assets 0..*
+AssetInfo 0..1
+Assets
0..*
+AssetContainer
0..1
+AnalyticScore 0..*
+Asset0..1
+AssetInfo0..1
+CatalogAssetType0..1
Asset Health Changes
P 29
class AssetMeasur ement
IdentifiedObject
Asset
+ kind: AssetKind [0..1]
+ type: String [0..1]
+ utcNumber: String [0..1]
+ serialNumber: String [0..1]
+ lotNumber: String [0..1]
+ purchasePrice: Money [0..1]
+ critical: Boolean [0..1]
+ position: String [0..1]
+ electronicAddress: ElectronicAddress [0..1]
+ lifecycleState: AssetLifecycleStateKind [0..1]
+ lifecycleDate: LifecycleDate [0..1]
+ inUseState: InUseStateKind [0..1]
+ inUseDate: InUseDate [0..1]
+ acceptanceTest: AcceptanceTest [0..1]
+ baselineCondition: String [0..1]
+ baselineLossOfLife: PerCent [0..1]
+ status: Status [0..1]
+ retiredReason: RetiredReasonKind [0..1]
AssetConta iner
P r ocedur eDataSet
+ completedDateTime: DateTime [0..1]
P r ocedur e
+ kind: ProcedureKind [0..1]
+ sequenceNumber: String [0..1]
+ instruction: String [0..1]
IdentifiedObject
Common::Document
+ type: String [0..1]
+ authorName: String [0..1]
+ createdDateTime: DateTime [0..1]
+ lastModifiedDateTime: DateTime [0..1]
+ revisionNumber: String [0..1]
+ electronicAddress: ElectronicAddress [0..1]
+ subject: String [0..1]
+ title: String [0..1]
+ docStatus: Status [0..1]
+ status: Status [0..1]
+ comment: String [0..1]
IdentifiedObject
Meas::Measur ementVa lue
+ timeStamp: DateTime [0..1]
+ sensorAccuracy: PerCent [0..1]
«enumeration»
Pr ocedur eK ind
inspection
diagnosis
maintenance
test
other
ExtendedMeas::
AssetStr ingMeasur ement
+ kind: AssetStringKind [0..1]
ExtendedMeas::AssetAna log
+ precision: Float [0..1]
+ reportingTemperature: Temperature [0..1]
+ detectionLimit: Float [0..1]
ExtendedMeas::AssetDiscr ete
Meas::Ana log
+ maxValue: Float [0..1]
+ minValue: Float [0..1]
+ normalValue: Float [0..1]
+ positiveFlowIn: Boolean [0..1]
Meas::Discr ete
+ maxValue: Integer [0..1]
+ minValue: Integer [0..1]
+ normalValue: Integer [0..1]
Meas::
Str ingMeasur ement
ExtendedMeas::
ExtendedAna log
ExtendedMeas::
ExtendedStr ingMeasur ement
ExtendedMeas::
ExtendedDiscr ete
IdentifiedObject
Meas::Measur ement
+ measurementType: String [0..1]
+ phases: PhaseCode [0..1]
+ unitMultiplier: UnitMultiplier [0..1]
+ unitSymbol: UnitSymbol [0..1]
+ProcedureDataSet0..*
+MeasurementValue 0..*
+Assets 0..*
+AssetContainer 0..1
+ProcedureDataSet 0..*
+Asset
0..1
+Asset
0..1+Measurements
0..*
+Procedures 0..*
+Measurements 0..*
+Procedures
0..*
+Assets
0..*
+Procedure 0..1
+ProcedureDataSets0..*
Asset Health Changes
P 30
cla ss AssetAna ly t ics
IdentifiedObject
Ana ly t icScor e
+ value: Float [0..1]
+ calculationDateTime: DateTime [0..1]
+ effectiveDateTime: DateTime [0..1]
Aggr ega teScor e
Ana ly t ic
+ kind: AnalyticKind
+ bestValue: float [0..1]
+ worstValue: float [0..1]
+ scaleKind: ScaleKind [0..1]
IdentifiedObject
Asset
+ kind: AssetKind [0..1]
+ type: String [0..1]
+ utcNumber: String [0..1]
+ serialNumber: String [0..1]
+ lotNumber: String [0..1]
+ purchasePrice: Money [0..1]
+ critical: Boolean [0..1]
+ position: String [0..1]
+ electronicAddress: ElectronicAddress [0..1]
+ lifecycleState: AssetLifecycleStateKind [0..1]
+ lifecycleDate: LifecycleDate [0..1]
+ inUseState: InUseStateKind [0..1]
+ inUseDate: InUseDate [0..1]
+ acceptanceTest: AcceptanceTest [0..1]
+ baselineCondition: String [0..1]
+ baselineLossOfLife: PerCent [0..1]
+ status: Status [0..1]
+ retiredReason: RetiredReasonKind [0..1]
RiskScor e
+ kind: RiskScoreKind [0..1]
Hea lthScor e
AssetConta iner
«enumeration»
RiskScor eK ind
customerRisk
financialRisk
safetyRisk
«enumeration»
Sca leK ind
linear
exponential
AssetGr oup
+ kind: AssetGroupKind
AssetHea lthEv ent
+ actionRecommendation: String [0..1]
+ actionTimeline: Duration [0..1]
+ effectiveDateTime: DateTime [0..1]
IdentifiedObject
Common::Act iv ity Recor d
+ createdDateTime: DateTime [0..1]
+ type: String [0..1]
+ severity: String [0..1]
+ reason: String [0..1]
+ status: Status [0..1]
«enumeration»
Ana ly t icK ind
riskAnalytic
faultAnalytic
agingAnalytic
healthAnalytic
replacementAnalytic
other
«enumeration»
AssetGr oupK ind
analysisGroup
inventoryGroup
complianceGroup
functionalGroup
other
IdentifiedObject
Common::Document
+ type: String [0..1]
+ authorName: String [0..1]
+ createdDateTime: DateTime [0..1]
+ lastModifiedDateTime: DateTime [0..1]
+ revisionNumber: String [0..1]
+ electronicAddress: ElectronicAddress [0..1]
+ subject: String [0..1]
+ title: String [0..1]
+ docStatus: Status [0..1]
+ status: Status [0..1]
+ comment: String [0..1]
+AssetGroup0..*
+Asset 0..*
+Analytic
0..*
+AssetGroup 0..*
+AnalyticScore0..*
+Asset0..1
+Analytic 0..*
+Asset
0..*
+AssetGroup 0..1
+AnalyticScore
0..*
+Analytic0..1
+AnalyticScore
0..*
+AssetHealthScore 0..*
+AssetRiskScore 0..1
+Analytic 1
+AssetHealthEvent 0..*
+Assets 0..*
+AssetContainer 0..1
+AssetAggregateScore0..1
+AnalyticScore1..*
+Assets
0..*
+ActivityRecords
0..*
Asset Health Changes
P 31
class AssetLifecy cle
IdentifiedObject
Asset
+ kind: AssetKind [0..1]
+ type: String [0..1]
+ utcNumber: String [0..1]
+ serialNumber: String [0..1]
+ lotNumber: String [0..1]
+ purchasePrice: Money [0..1]
+ critical: Boolean [0..1]
+ position: String [0..1]
+ electronicAddress: ElectronicAddress [0..1]
+ lifecycleState: AssetLifecycleStateKind [0..1]
+ lifecycleDate: LifecycleDate [0..1]
+ inUseState: InUseStateKind [0..1]
+ inUseDate: InUseDate [0..1]
+ acceptanceTest: AcceptanceTest [0..1]
+ baselineCondition: String [0..1]
+ baselineLossOfLife: PerCent [0..1]
+ status: Status [0..1]
+ retiredReason: RetiredReasonKind [0..1]
AssetConta iner
«Compound»
Lifecy cleDa te
«enum»
+ manufacturedDate: Date [0..1]
+ purchaseDate: Date [0..1]
+ receivedDate: Date [0..1]
+ installationDate: Date [0..1]
+ removalDate: Date [0..1]
+ retiredDate: Date [0..1]
«enumeration»
AssetLifecy cleSta teK ind
manufactured
purchased
received
retired
disposedOf
«enumeration»
Ret ir edReasonK ind
environmental
excessiveMaintenance
facilitiesUpgrade
failed
obsolescence
other
sold
«enumeration»
InUseSta teK ind
inUse
readyForUse
notReadyForUse
«Compound»
InUseDa te
+ inUseDate: Date [0..1]
+ readyForUseDate: Date [0..1]
+ notReadyForUseDate: Date [0..1]
IdentifiedObject
AssetDeploy ment
+ deploymentState: DeploymentStateKind [0..1]
+ deploymentDate: DeploymentDate [0..1]
+ breakerApplication: BreakerApplicationKind [0..1]
+ transformerApplication: TransformerApplicationKind [0..1]
+ likelihoodOfFailure: Integer [0..1]
+ facilityKind: FacilityKind [0..1]
«Compound»
Deploy mentDa te
+ notYetInstalledDate: DateTime [0..1]
+ installedDate: DateTime [0..1]
+ inServiceDate: DateTime [0..1]
+ outOfServiceDate: DateTime [0..1]
+ removedDate: DateTime [0..1]
«enumeration»
Deploy mentSta teK ind
notYetInstalled
installed
inService
outOfService
removed
+Asset0..1
+AssetDeployment0..1
+Assets 0..*
+AssetContainer 0..1
DER Changes
P 32
cla ss DER-EndDev iceOv er v iew
«Compound»
Common::Sta tus
+ value: String [0..1]
+ dateTime: DateTime [0..1]
+ remark: String [0..1]
+ reason: String [0..1]
AssetContainer
Meter ing::EndDev ice
+ isVirtual: Boolean [0..1]
+ isPan: Boolean [0..1]
+ installCode: String [0..1]
+ amrSystem: String [0..1]
+ timeZoneOffset: Minutes [0..1]
+ isSmartInverter: Boolean [0..1]
Meter ing::
EndDev iceGr oup
+ type: String [0..1]
+ status: Status [0..1]
+ version: Version [0..1]
Cor e::Ident if iedObject
+ aliasName: String [0..1]
+ description: String [0..1]
+ mRID: String [0..1]
+ name: String [0..1]
DERGr oupFor ecast
+ capabilityKind: CapabilityKind [0..1]
+ predictionCreationDate: DateTime [0..1]
+ predictionIntervalKind: PredictionalIntervalKind [0..1]
+ predictionStartDate: DateTime [0..1]
Dispa tchablePower Capabil i ty
+ currentActivePower: ActivePower [0..1]
+ currentApparentPower: ApparentPower [0..1]
+ currentReactivePower: ReactivePower [0..1]
+ maxActivePower: ActivePower [0..1]
+ maxApparentPower: ApparentPower [0..1]
+ maxReactivePower: ReactivePower [0..1]
+ minActivePower: ActivePower [0..1]
+ minApparentPower: ApparentPower [0..1]
+ minReactivePower: ReactivePower [0..1]
«Compound»
Common::Ver sion
+ date: DateTime [0..1]
+ major: Integer
+ minor: Integer [0..1]
+ revision: Integer [0..1]
Other Capabil i ty
+ capabilitySubType: String [0..1]
+ capabilityType: String [0..1]
+ capabiityUnits: String [0..1]
+ capabilityValue: String [0..1]
+EndDeviceGroups0..* +EndDevices
0..*
+EndDevice 0..1
+OtherCapability0..*
+EndDeviceGroup
0..1
+DispatchablePowerCapability
0..1
+EndDeviceGroup0..1
+OtherCapability
0..*
+DERGroupForecast1..*
+EndDeviceGroup
1..*
+EndDevice 0..1
+DispatchablePowerCapability 0..*
DER Changes
P 33
cla ss DEROv er v iew
DERGr oupFor ecast
+ capabilityKind: CapabilityKind [0..1]
+ predictionCreationDate: DateTime [0..1]
+ predictionIntervalKind: PredictionalIntervalKind [0..1]
+ predictionStartDate: DateTime [0..1]
DERGr oupFor ecasts
DERGr oupFor ecastRequest
+ capabilityKind: CapabilityKind [0..1]
+ forecastBeginDate: DateTime [0..1]
+ forecastInterval: PredictionIntervalKind [0..1]
+ forecastIntervalQty: Integer [0..1]
Cor e::Ident if iedObject
+ aliasName: String [0..1]
+ description: String [0..1]
+ mRID: String [0..1]
+ name: String [0..1]
P r edict ions
+ confidence: PerCent [0..1]
+ maxActivePower: ActivePower [0..1]
+ maxApparentPower: ApparentPower [0..1]
+ maxReactivePower: ReactivePower [0..1]
+ minActivePower: ActivePower [0..1]
+ minApparentPower: ApparentPower [0..1]
+ minReactivePower: ReactivePower [0..1]
+ sequence: Integer [0..1]
+ predictionInterval: DateTimeInterval [0..1]
It is required that the
forecast return
values based on the
units asked for, e.g.,
if the request was in
ActivePower, the
response must be
expressed in
ActivePower.
«enumeration»
Capabil i ty K ind
apparentPower
activePower
reactivePower
Other Capabil i ty
+ capabilitySubType: String [0..1]
+ capabilityType: String [0..1]
+ capabiityUnits: String [0..1]
+ capabilityValue: String [0..1]
«enumeration»
P r edict ionInter v a lK ind
Y
M
D
h
m
s
«CIMDatatype»
Doma in::Act iv ePower
+ value: Float [0..1]
+ unit: UnitSymbol [0..1] = W {readOnly}
+ multiplier: UnitMultiplier [0..1]
«CIMDatatype»
Doma in::Appa r entPower
+ value: Float [0..1]
+ unit: UnitSymbol [0..1] = VA {readOnly}
+ multiplier: UnitMultiplier [0..1]
«CIMDatatype»
Doma in::React iv ePower
+ value: Float [0..1]
+ unit: UnitSymbol [0..1] = VAr {readOnly}
+ multiplier: UnitMultiplier [0..1]
+DERGroupForecasts
1..*
+DERGroupForecast
1..*
+DERGroupForecast 1..*
+OtherCapability 0..*
+DERGroupForecast1..*
+Predictions 1..*
Work Model Changes
P 34
class AssetWor k
IdentifiedObject
Assets::Asset
+ kind: AssetKind [0..1]
+ type: String [0..1]
+ utcNumber: String [0..1]
+ serialNumber: String [0..1]
+ lotNumber: String [0..1]
+ purchasePrice: Money [0..1]
+ critical: Boolean [0..1]
+ position: String [0..1]
+ electronicAddress: ElectronicAddress [0..1]
+ lifecycleState: AssetLifecycleStateKind [0..1]
+ lifecycleDate: LifecycleDate [0..1]
+ inUseState: InUseStateKind [0..1]
+ inUseDate: InUseDate [0..1]
+ acceptanceTest: AcceptanceTest [0..1]
+ baselineCondition: String [0..1]
+ baselineLossOfLife: PerCent [0..1]
+ status: Status [0..1]
+ retiredReason: RetiredReasonKind [0..1]
Assets::AssetConta iner
IdentifiedObject
Common::Document
+ type: String [0..1]
+ authorName: String [0..1]
+ createdDateTime: DateTime [0..1]
+ lastModifiedDateTime: DateTime [0..1]
+ revisionNumber: String [0..1]
+ electronicAddress: ElectronicAddress [0..1]
+ subject: String [0..1]
+ title: String [0..1]
+ docStatus: Status [0..1]
+ status: Status [0..1]
+ comment: String [0..1]
BaseWor k
+ kind: WorkKind [0..1]
+ priority: Priority [0..1]
+ statusKind: WorkStatusKind [0..1]
Wor k
+ workOrderNumber: String [0..1]
+ requestDateTime: DateTime [0..1]
Wor kTask
+ taskKind: WorkTaskKind [0..1]
+ instruction: String [0..1]
+ schedOverride: String [0..1]
+ crewETA: DateTime [0..1]
+ startedDateTime: DateTime [0..1]
+ completedDateTime: DateTime [0..1]
+ laborHours: Hours [0..1]
+ contractorCost: Money [0..1]
+ laborCost: Money [0..1]
+ materiallCost: Money [0..1]
+ toolCost: Money [0..1]
«enumeration»
Wor kTaskK ind
install
remove
exchange
investigate
«enumeration»
Wor kK ind
construction
inspection
maintenance
repair
test
service
disconnect
connect
other
refurbishment
«enum, deprecated»
reconnect
«enumeration»
Wor kSta tusK ind
waitingOnApproval
approved
cancelled
waitingToBeScheduled
scheduled
waitingOnMaterial
inProgress
completed
closed
dispatched
enroute
onSite
«Compound»
Common::P r ior ity
+ rank: Integer [0..1]
+ type: String [0..1]
+ justification: String [0..1]
«enumeration»
Br eaker Repa ir I temKind
airCompressor
auxiliarySwitchAndLinkage
busConnection
checkValve
closeCoil
contactor
controlCircuit
corrosion
gasDensitySupervision
heaterOrThermostat
hydraulicFluidLeak
interrupterAssembly
positionIndicator
pressureSwitch
pumpOrMotor
relay
SF6GasLeak
storedEnergySystem
tripCoil
tripControlValve
wiring
other
Ma intenanceWor kTask
+ breakerMaintenanceKind: BreakerMaintenanceKind [0..1]
+ transformerMaintenanceKind: TransformerMaintenanceKind [0..1]
IdentifiedObject
Mater ia l I tem
+ quantity: IntegerQuantity [0..1]
«enumeration»
Tr ansfor mer Repa ir I temKind
Repa ir Wor kTask
+ emergency: Boolean [0..1]
«enumeration»
Br eaker Ma intenanceK ind
externalOutOfService
internalOutOfService
interrupterOverhaul
«enumeration»
Tr ansfor mer Ma intenanceK ind
Repa ir I tem
+ breakerRepairItem: BreakerRepairItemKind [0..1]
+ transformerRepairItem: TransformerRepairItemKind [0..1]
+ReplacementWorkTasks
0..*
+OldAsset 0..1
+Assets 0..*
+AssetContainer 0..1
+BreakerRepairItem 0..*
+RepairWorkTask 0..*
+WorkTasks0..*
+Assets0..*
+Work
1 +WorkTasks
0..*+WorkTask
0..1
+MaterialItems0..*
WG14 Profile Work
Profile Work Started for:
Part 3
Part 4
Part 5
Part 6
Part 8
Part 9
May have additional changes go into
model as a result of the above profile
work.P 35
WG16: Deregulated Market
Communications
Mission, Scope:
Develop Standards for Electricity Market
Communications
Market Participants to Market Operator
Intra Market Operator
Package IEC62325 within TC57 CIM UML Model
P 36
WG16: Two Subteams
Two Styles of Markets throughout world
“European Style” Markets:
Day Ahead Markets: Bilateral, Exchanges
Intra-day Markets
Balancing by TSOs
Collaboration with ENTSO-e
“US Style” Market
Bilateral Markets, Exchanges
Day Ahead Markets with SCUC
Hour Ahead Markets
Real Time Markets with SCED
Collaboration with IRC, and ISO projects
Beneficiaries will include Market Participants, Market
Operators, Vendors
P 37
“European Style” Markets
Data Exchanges to support Energy Markets
Derived from ETSO Electronic Data Interchange (EDI)
ENTSO-E Scheduling System – ESS
ENTSO-E Settlement Process – ESP
ENTSO-E Reserve Resource Process – ERRP
ENTSO-E Capacity Allocation and Nomination – ECAN
Mapping of existing data exchanges to CIM-based data exchanges
IEC WG-16 working in formal liaison with ENTSO-E
Standardization as IEC 62325, package MarketManagement
P 38
“North American Style” Markets
Data Exchanges to support
Day Ahead MarketsReal Time MarketsFinancial Transmission Rights (CRR)Settlement
IEC WG-16 picked up results of EPRI CME project (CIM Extensions to Support Market Operations)
Working with ISO/RTO Council
Individual ISO/RTO projects contributed extension to the CIM
to support Energy Markets.
Standardization as IEC 62325, package MarketOperations
P 39
Model Status Summary
IEC62325-301 Edition 1 released on
IEC62325 CIM02v09
Packaged with IEC61970 CIM16v01 and IEC61968
CIM12v01
IEC62325-301 Edition 2 submitted to IEC as
CDV in October 2016
Edition 2 built on IEC 62325 CIM03v16
Packaged with IEC61970CIM17v16 and
IEC61968CIM13v09
P 40
Model Status Summary
Current IEC62325 version
IEC62325CIM03v16 posted on WG16
SharePoint
P 41
Focus Items Incorporated in Edition 2
European Regulation; Network Codes
Demand Response for Markets Extensions
Harmonization with OpenADR Extensions
North American Day Ahead Market Profiles
Model Updates
CIM for Environmental Data (Weather)
P 42
Demand Response for Markets
Model submitted to WG16 from SGIP PAP19 (supported
by IRC and NIST)
Formed Demand Response for Markets sub-team to
harmonize with IEC62325
Worked through Use Cases and validated against
existing IEC62325 model
As designed, extensions support market based demand
response in North America
Resulting model as a basis for OpenADR Harmonization
task force
P 44
Demand Response for Markets
Communication Model Layers
P 45
Demand Response for Markets Model
Extensions
P 46
North American Day Ahead Profiles
Developing Use Cases
Modifications required to support use cases are
included in IEC62325CIM03v10
NA Sub-team has weekly web conferences
Reuse of IEC61970-452 for network model
Defining profiles for supplemental market data
Registered Resources
Pricing Nodes
Aggregate Nodes
P 47
CIM for Environmental Data
Model extensions included as of IEC62325CIM03v10;
definitions for
• Alerts & Events
• Observations & Forecasts
• EnvironmentalValueSets
• Phenomena
Weekly web meetings, participation has included:
WG16 members (Jim, Becky, Margaret, Fedder)
Ex-Southern Cal Edison (Jim Horstman, Henry Dotson)
EPRI (Pat Brown)
Folks with knowledge of Ecologic use of model (Chris Kardos)
P 48
AlertsObservations Forecasts
Phenomenon Phenomenon ValueSets
Analogs CodedValues
High Level Data Organization
ValueSets
Analogs CodedValues
CIM for Environmental Data
Assumed Deployment Architecture
CIM for Environmental Data
Load Forecastapplication
Utility Environmental
Data Service
WX
XM
CIM
External weather data
providers
Utility-owned weather stations
External weather data
providers
External weather data
providers
Integration Framework
Outage Management
System
Transmission Contingency
Analysis
Work Management
System
Renewables Dispatch
CIM
CIM
CIM
CIM
CIM
Etc.
CIM
Next steps:
Select use cases for profile building
Definition of Message Profiles
Write NWIP (New Work in Progress) for
Profiles
CIM for Environmental Data
WG21 Scope
WG21: Interfaces and protocol profiles
relevant to systems connected to the
electrical grid
Mission, Scope:
Interface from aggregator, (utility, QSE, SC) to end
customer
Includes, commercial, industrial, home
Includes retail markets, real time pricing
Includes traditional non-market load management
P 55
56
Modeling Team Structure
Initial kickoff – October 5, 2016
Tracking WG21 modeling issues
WG21-CIM-Issues
Located on WG21 SharePoint in Modeling-Team-Workspace
WG Combined Issues list
WG13, WG14, WG16 combined issues
Maintained by WG Modeling Managers
Located on WG19 SharePoint in Combined_CIM_Issues
Jean-Luc Sanson
Tadayoshi Kosaka
Yasuro Shobatake
Dong Liu
Margaret Goodrich
Peter Ferstl
Scott Neumann
Becky Iverson
Modeling Team Members
57
Recent Focus Items
Reviewing use cases to identify priority
Use cases from SGIP PAP19 Demand Response for Markets (WG16)
Use Cases from SGTEC/IEEJ (Smart Grid Technologies for Electricity Customers/Institute of Electrical Engineering of Japan) (WG21)
Use cases from OpenADR Harmonization Task Force (WG21)
58
Harmonization with OpenADR
Goal: Develop a mapping between the IEC CIM
and OpenADR2.0 to facilitate future
interoperability
Use case driven
UML extensions Support
Communication with Market Demand-Side
Resources
Communication of Market Pricing
P 59
CIM for Demand-Side Resources
IEC CIM based profile schemas defined
ResourceDeployment
CommodityPrices
CommodityDefinitions
IEC CIM Profile schemas can support the
communication involved in Demand Response
for Markets
Model extensions included as of
IEC62325CIM03v10
P 60
CIM Market Demand-Side Resource
ResourceDeployment
P 61
EVENT
DISPATCH INTERVAL
SETPOINT
CIM Market Pricing
Commodity Definition
P 62
LOCATION IF ZONAL
REGION
UNIT OF MEASURE
CURRENCY; EUR/USD
LOCATION IF NODAL
STOCK SYMBOL EQUIVALENT
CIM Market Pricing
Commodity Price
P 63
LINK TO COMMODITY DEFINITION
VALID TIMEFRAME
DAY AHEAD / REAL TIME
PRICE
LMP / ALL-IN RETAIL
Modeling Team Next Steps
Use case selection
Discuss profile mapping to CIM classes to identify gaps
Once gaps are identified, the proper modeling location will be decided by the team
64
Model Summary
Start with current IEC62325 version
IEC62325CIM03v16 posted on WG16
SharePoint
P 65
INTERNATIONAL
ELECTROTECHNICAL
COMMISSION
Questions?