Multi-site Network Model Management

Power Transmission &
Distribution, Inc.
Kurt Hunter
27 June 2007

Multi-site Network Model Management

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

Background on Model Management

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.

Energy Management & Automation Division
Page 3

April 06

© 2006 Siemens Power Transmissions & Distribution, Inc. All rights reserved

Background on Model Management 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. Energy Management & Automation Division Page 4 April 06 © 2006 Siemens Power Transmissions & Distribution. All rights reserved . Inc.

Background on Model Management Neighbor B Network Neighbor A Network External Model My Network Neighbor C Network Internal Model Neighbor D Network Energy Management & Automation Division Page 5 April 06 © 2006 Siemens Power Transmissions & Distribution. Inc. All rights reserved .

All rights reserved .Background on Model Management 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 Energy Management & Automation Division Page 6 April 06 © 2006 Siemens Power Transmissions & Distribution. Inc.

Inc.Background on Model Management 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) Energy Management & Automation Division Page 7 April 06 © 2006 Siemens Power Transmissions & Distribution. All rights reserved .

All rights reserved .Background on Model Management Model Exchange and Merge My Network Model Network Model Merge Neighbor A Neighbor B PSS/E File IEEE File Neighbor C Proprietary Format File Energy Management & Automation Division Page 8 April 06 © 2006 Siemens Power Transmissions & Distribution. Inc.

if neighbor used the same EMS vendor ƒ Semi-automated process at best Energy Management & Automation Division Page 9 April 06 © 2006 Siemens Power Transmissions & Distribution. PSLF or IEEE) ƒ Occasionally received as node/breaker.Background on Model Management Model Exchange and Merge ƒ Data received from multiple sources in multiple formats with multiple unique issues ƒ Usually received as bus/branch (PSS/E. Inc. All rights reserved .

Background on Model Management Model Exchange and Merge ƒ Labor intensive effort ƒ Difficult to automate ƒ Expensive ƒ Performed infrequently Energy Management & Automation Division Page 10 April 06 © 2006 Siemens Power Transmissions & Distribution. All rights reserved . Inc.

All rights reserved . Inc.Background on Model Management Model Exchange and Merge Energy Management & Automation Division Page 11 April 06 © 2006 Siemens Power Transmissions & Distribution.

Inc. ƒ No longer just peer to peer ƒ Member models not necessarily synchronized ƒ Model Exchange from Coordinator to members to improve synchronization Energy Management & Automation Division Page 12 April 06 © 2006 Siemens Power Transmissions & Distribution.Background on Model Management Multi-site Management and Merge ƒ Introduction of ISOs and RTOs made it necessary to construct large scale detailed network models. All rights reserved .

All rights reserved . Inc.Background on Model Management 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 Energy Management & Automation Division Page 13 April 06 © 2006 Siemens Power Transmissions & Distribution.

CIM XML Based Model Exchange The reality is CIM will not solve all your problems. Energy Management & Automation Division Page 14 April 06 © 2006 Siemens Power Transmissions & Distribution. All rights reserved . Inc.

including incremental changes (IEC 61970-552-4) Energy Management & Automation Division Page 15 April 06 © 2006 Siemens Power Transmissions & Distribution. Inc. All rights reserved .CIM XML Based Model Exchange CIM XML Based Model Exchange ƒ 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.

Inc.CIM XML Based Model Exchange CIM XML Based Model Exchange . 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) Energy Management & Automation Division Page 16 April 06 © 2006 Siemens Power Transmissions & Distribution. All rights reserved .Principals ƒ Each modeled object identified by a globally unique.

0010609418</cim:Conductor.r> <cim:Conductor.80864</cim:Conductor.x> </cim:ACLineSegment> Energy Management & Automation Division Page 17 April 06 © 2006 Siemens Power Transmissions & Distribution. Inc.x>13. All rights reserved .bch>0.bch> <cim:Conductor.CIM XML Based Model Exchange CIM XML Based Model Exchange – Sample XML <cim:ACLineSegment rdf:ID="_1c0789232f24da7a7c8751ccccf2b38"> <cim:IdentifiedObject.r>0.MemberOf_EquipmentContainer rdf:resource="#_e55503e162de464b9d17dfe57f936574"/> <cim:ConductingEquipment.8624</cim:Conductor.name> <cim:Equipment.BaseVoltage rdf:resource="#_216f3106be824bca99dd83a9af6681b6"/> <cim:Conductor.name>N12-N260</cim:IdentifiedObject.

Inc.History Nine Interoperability Tests have been executed ƒ Verified completeness of data exchanged ƒ Verified common understanding of data exchanged ƒ Verified exchange of incremental changes Energy Management & Automation Division Page 18 April 06 © 2006 Siemens Power Transmissions & Distribution.CIM XML Based Model Exchange CIM XML Based Model Exchange . All rights reserved .

CIM XML Based Model Exchange CIM XML Based Model Exchange . Inc. All rights reserved .History Interoperability Tests have not: ƒ Verified persistence of master resource IDs (MRIDs) ƒ Verified global uniqueness of MRIDs ƒ Tested data ownership or model merge Energy Management & Automation Division Page 19 April 06 © 2006 Siemens Power Transmissions & Distribution.

But we won’t all get there at the same time. All rights reserved . Inc.Model Management Implementation 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. Energy Management & Automation Division Page 20 April 06 © 2006 Siemens Power Transmissions & Distribution.

Not everyone is generating globally unique IDs 4. and in Texas) 2. All rights reserved . Inc. Security is necessary around data ownership Energy Management & Automation Division Page 21 April 06 © 2006 Siemens Power Transmissions & Distribution.Model Management Implementation Network Model Management Implementation Issues 1. Not everyone is generating persistent IDs 3. Not everyone has CIM XML capability (particularly outside the U. Agreements need to be reached on persistent IDs for boundary objects 5.S.

S. All rights reserved . Energy Management & Automation Division Page 22 April 06 © 2006 Siemens Power Transmissions & Distribution. Inc. and in Texas) CIM XML is gaining support in Europe and Asia. but is not as widely used as other data exchange formats.Model Management Implementation 1) Not everyone has CIM XML capability (particularly outside the U.

S. All rights reserved .Model Management Implementation 1) Not everyone has CIM XML capability (particularly outside the U. Inc. and in Texas) Resolution – Allow remote editing of coordinator’s combined network model by members ƒ Members without CIM XML capability piggyback on capabilities of the coordinator’s system ƒ Also requires implementation of security based on data ownership Energy Management & Automation Division Page 23 April 06 © 2006 Siemens Power Transmissions & Distribution.

Inc. All rights reserved . ƒ Persistence has not been tested in interoperability tests ƒ Persistent MRIDs are required for real world model management Energy Management & Automation Division Page 24 April 06 © 2006 Siemens Power Transmissions & Distribution.Model Management Implementation 2) Not everyone is generating persistent IDs Example – Internal index based MRIDs such as “Substation_174” may change when equipment is added or deleted.

Equipment Name. Inc. ƒ 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. locally unique ID. All rights reserved .) Energy Management & Automation Division Page 25 April 06 © 2006 Siemens Power Transmissions & Distribution. etc. Equipment Type.Model Management Implementation 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.

Globally unique IDs can’t be tied to data owner.Subatstion_17845. Energy Management & Automation Division Page 26 April 06 © 2006 Siemens Power Transmissions & Distribution.Model Management Implementation 3) Not everyone is generating globally unique IDs Example – Both Company A and Company B may have a substation identified as “Substation_17845”. Inc. Problem arises when Company A buys Company B. First impulse to add company name for uniqueness such as Company_A. All rights reserved .Substation_17845 and Company_B.

Coordinator system generates and assigns a truly globally unique and persistent ID and maps it to the member maintained persistent. locally unique ID. All rights reserved . Energy Management & Automation Division Page 27 April 06 © 2006 Siemens Power Transmissions & Distribution. Inc.Model Management Implementation 3) Not everyone is generating globally unique IDs Resolution .

Inc. names used by different applications.) Unique ID Mapping ƒ Maps a globally unique identifier to the locally unique identifier of the current data owner Energy Management & Automation Division Page 28 April 06 © 2006 Siemens Power Transmissions & Distribution. All rights reserved . etc.Model Management Implementation 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.

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. All rights reserved .Model Management Implementation 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. Inc. Energy Management & Automation Division Page 29 April 06 © 2006 Siemens Power Transmissions & Distribution. For example.

Model Management Implementation 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 Energy Management & Automation Division Page 30 April 06 © 2006 Siemens Power Transmissions & Distribution. Inc. All rights reserved .

Energy Management & Automation Division Page 31 April 06 © 2006 Siemens Power Transmissions & Distribution. must be restricted to only the responsible Modeling Authority.Model Management Implementation 5) Security is necessary around data ownership ƒ Any single object in the coordinator’s combined network model can have only one entity (Modeling Authority) responsible for that data. Inc. All rights reserved . either by direct editing or through import of incremental change files. ƒ Changes to that data.

Inc. All rights reserved . Energy Management & Automation Division Page 32 April 06 © 2006 Siemens Power Transmissions & Distribution.Model Management Implementation 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.

All rights reserved .Multi-site Network Model Management Questions? Energy Management & Automation Division Page 33 April 06 © 2006 Siemens Power Transmissions & Distribution. Inc.