Multi-Site Network Model Management: Power Transmission & Distribution, Inc

Multi-site Network Model Management
Power Transmission &

Distribution, Inc.
Kurt Hunter
27 June 2007
Topics
Background on Model Management

CIM XML Based Model Exchange
Model Management Implementation
Energy Management & Automation Division

Page 2
April 06
2006 Siemens Power Transmissions & Distribution, Inc. All rights reserved
What is Network Model Management?

Maintenance of an equipment and topology model
to support network applications such as power
flow, state estimation and contingency analysis.

Page 3
April 06
Network Model Management requires:

On-going maintenance of the node/breaker model
of the portion of the electrical network that your
organization operates or oversees as well as
neighboring areas that affect operation of your
network.

Page 4
April 06
Neighbor B
Network
Neighbor A
Network
External Model
My Network
Neighbor C
Network
Internal Model
Neighbor D
Network

Page 5
April 06
Internal Model
Updated frequently
Verified by State Estimator solution
Highly accurate
External Model
Infrequently updated
Requires input from external organizations
Accuracy depends on frequency of update

Page 6
April 06
External Model Update
Requires exchanging network model data with closest

neighbors
Usually done as a wholesale replace of all data within

your network model for a given company
Usually requires conversion between data formats

Requires stitching the new data into the existing data
(primarily updating connectivity references for tie lines)

Page 7
April 06
Model Exchange
and Merge
My Network
Model
Network Model Merge
Neighbor A
Neighbor B
PSS/E File
IEEE File
Neighbor C
Proprietary Format
File

Page 8
April 06
Model Exchange and Merge

Data received from multiple sources in multiple formats with
multiple unique issues
Usually received as bus/branch (PSS/E, PSLF or IEEE)

Occasionally received as node/breaker, if neighbor used the same
EMS vendor
Semi-automated process at best

Page 9
April 06

Labor intensive effort
Difficult to automate
Expensive
Performed infrequently

Page 10
April 06

Page 11
April 06
Multi-site Management and Merge

Introduction of ISOs and RTOs made it necessary to construct
large scale detailed network models.
No longer just peer to peer

Member models not necessarily synchronized
Model Exchange from Coordinator to members to improve
synchronization

Page 12
April 06
Multi-site Management and Merge
Combined Model
el
Member B Model
od
M
be
rA
ed
bin
m
l
de
Mo
M
em
Co
rC
be
Member A
m
Me
Co
M
mb
od
ine
el
dM
od
el
Cordinator
(ISO/RTO)
Member C
Member B

Page 13
April 06
The reality is
CIM will not solve

all your problems.

Page 14
April 06
Based on Common Information Model (IEC 61970-301)

Standardizing a profile for node/breaker model exchange
for network applications (IEC 61970-452)
Standardizing an XML based method for data exchange,

including incremental changes (IEC 61970-552-4)

Page 15
April 06

CIM XML Based Model Exchange - Principals
Each modeled object identified by a globally unique, persistent master

resource ID (MRID)
Identification independent of naming

Model exchanged in greatest detail available (and reduced or
equivalenced as necessary by the consumer)
Unique identification independent of data owner (Modeling Authority)

(Unique ID remains constant even if data owner changes)

Page 16
April 06

CIM XML Based Model Exchange Sample XML
<cim:ACLineSegment rdf:ID="_1c0789232f24da7a7c8751ccccf2b38">
<cim:IdentifiedObject.name>N12-N260</cim:IdentifiedObject.name>
<cim:Equipment.MemberOf_EquipmentContainer
rdf:resource="#_e55503e162de464b9d17dfe57f936574"/>
<cim:ConductingEquipment.BaseVoltage
rdf:resource="#_216f3106be824bca99dd83a9af6681b6"/>
<cim:Conductor.bch>0.0010609418</cim:Conductor.bch>
<cim:Conductor.r>0.80864</cim:Conductor.r>
<cim:Conductor.x>13.8624</cim:Conductor.x>
</cim:ACLineSegment>

Page 17
April 06
CIM XML Based Model Exchange - History

Nine Interoperability Tests have been executed
Verified completeness of data exchanged

Verified common understanding of data exchanged
Verified exchange of incremental changes

Page 18
April 06
CIM XML Based Model Exchange - History

Interoperability Tests have not:
Verified persistence of master resource IDs (MRIDs)

Verified global uniqueness of MRIDs
Tested data ownership or model merge

Page 19
April 06
Network Model Management Implementation

CIM Model has been expanded to support:
Identification of data ownership

Ease of model merge
A clear methodology has been defined,
But we wont all get there at the same time.

Page 20
April 06
Network Model Management Implementation Issues

1. Not everyone has CIM XML capability (particularly outside the
U.S. and in Texas)
2. Not everyone is generating persistent IDs

3. Not everyone is generating globally unique IDs
4. Agreements need to be reached on persistent IDs for boundary
objects
5. Security is necessary around data ownership

Page 21
April 06
1) Not everyone has CIM XML capability (particularly outside

the U.S. and in Texas)
CIM XML is gaining support in Europe and Asia, but is not as widely
used as other data exchange formats.

Page 22
April 06
1) Not everyone has CIM XML capability (particularly outside

the U.S. and in Texas)
Resolution Allow remote editing of coordinators combined network
model by members
Members without CIM XML capability piggyback on capabilities of the

coordinators system
Also requires implementation of security based on data ownership

Page 23
April 06
2) Not everyone is generating persistent IDs

Example Internal index based MRIDs such as Substation_174 may
change when equipment is added or deleted.
Persistence has not been tested in interoperability tests

Persistent MRIDs are required for real world model management

Page 24
April 06
2) Not everyone is generating persistent IDs

Resolution Coordinator system generates and assigns a truly globally
unique and persistent ID and maps it to the member maintained
persistent, locally unique ID.
Usually locally unique identification tied to naming, so naming must be

persistent or renaming must be handled as a special case
Usually unique naming is a combination of parameters (Substation

Name, Equipment Name, Equipment Type, etc.)

Page 25
April 06
3) Not everyone is generating globally unique IDs

Example Both Company A and Company B may have a substation
identified as Substation_17845.
First impulse to add company name for uniqueness such as
Company_A.Substation_17845 and Company_B.Subatstion_17845.
Problem arises when Company A buys Company B.
Globally unique IDs cant be tied to data owner.

Page 26
April 06

3) Not everyone is generating globally unique IDs
Resolution - Coordinator system generates and assigns a truly globally

unique and persistent ID and maps it to the member maintained
persistent, locally unique ID.

Page 27
April 06
Name Registry versus Unique ID Mapping

Name Registry
Maps a single globally unique identifier to multiple names used in
different contexts (names used by different companies, names used
by different applications, etc.)
Unique ID Mapping
Maps a globally unique identifier to the locally unique identifier of
the current data owner

Page 28
April 06
4) Agreements need to be reached on persistent IDs for

boundary objects
Agreement must be reached on the globally unique identification of
any object referenced in more than one model.
For example, the connectivity node in Company A where a tie line
from Company B connects must have an ID that does not change
without agreement from both Company A and Company B.

Page 29
April 06
4) Agreements need to be reached on persistent IDs for

boundary objects
Resolution Requires interested parties to:
Agree on common modeling of shared objects

Agree on a primary owner of all shared objects
Agree on globally unique and persistent IDs for shared objects

Page 30
April 06
5) Security is necessary around data ownership

Any single object in the coordinators combined network model can have
only one entity (Modeling Authority) responsible for that data.
Changes to that data, either by direct editing or through import of

incremental change files, must be restricted to only the responsible
Modeling Authority.

Page 31
April 06
5) Security is necessary around data ownership

Resolution Software tools for Model Management must support the
capability to control who can edit and in some cases view individual
data objects.

Page 32
April 06
Questions?

Page 33
April 06

Multi-Site Network Model Management: Power Transmission & Distribution, Inc

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Multi-Site Network Model Management: Power Transmission & Distribution, Inc

Uploaded by

Copyright:

Available Formats

Multi-site Network Model Management

Power Transmission &

Multi-site Network Model Management

Background on Model Management

Energy Management & Automation Division

Background on Model Management

What is Network Model Management?

Energy Management & Automation Division

Background on Model Management

Network Model Management requires:

Energy Management & Automation Division

Background on Model Management

Energy Management & Automation Division

Background on Model Management

Energy Management & Automation Division

Background on Model Management

External Model Update

Requires exchanging network model data with closest

Usually done as a wholesale replace of all data within

Usually requires conversion between data formats

Energy Management & Automation Division

Background on Model Management

Network Model Merge

Energy Management & Automation Division

Background on Model Management

Model Exchange and Merge

Usually received as bus/branch (PSS/E, PSLF or IEEE)

Semi-automated process at best

Energy Management & Automation Division

Background on Model Management

Model Exchange and Merge

Energy Management & Automation Division

Background on Model Management

Model Exchange and Merge

Energy Management & Automation Division

Background on Model Management

Multi-site Management and Merge

No longer just peer to peer

Energy Management & Automation Division

Background on Model Management

Multi-site Management and Merge

Energy Management & Automation Division

CIM XML Based Model Exchange

CIM will not solve

Energy Management & Automation Division

CIM XML Based Model Exchange

CIM XML Based Model Exchange

Based on Common Information Model (IEC 61970-301)

Standardizing an XML based method for data exchange,

Energy Management & Automation Division

CIM XML Based Model Exchange

Each modeled object identified by a globally unique, persistent master

Identification independent of naming

Unique identification independent of data owner (Modeling Authority)

Energy Management & Automation Division

CIM XML Based Model Exchange

Energy Management & Automation Division

CIM XML Based Model Exchange

CIM XML Based Model Exchange - History

Verified completeness of data exchanged

Energy Management & Automation Division

CIM XML Based Model Exchange

CIM XML Based Model Exchange - History