CIM for UCTE Jay Britton jay brittonarevatd com

CIM for UCTE Jay Britton jay. britton@areva-td. com

Issues u Business Process (Use Cases) w How does the UCTE DACF compare with CIM model exchange processes? u Format Compatibility w UCTE DEF is a power flow format. w CIM/XML (452/552) is an EMS model exchange format. 3 3

UCTE Day-Ahead Congestion Forecast 4 4

UCTE Day-Ahead Congestion Forecast II 5 5

UCTE Day-Ahead Congestion Forecast III 6 6

The initial CIM model exchange standard focused on transfer of complete models: CIM Exchange (full, partial, incremental update) CIM import / export System B Import Model System A Import Model Proprietary / Home grown Extract / Merge Tools System A Local Vendor Model A Internal Model A’s model of B System A EMS 7 a Proprietary / Home grown Extract / Merge Tools System B Local Vendor Model b B’s Model of A B Internal Model System B EMS 7

Basic 2 -Region Process Example Site A makes a change: 1. A changes its Model. Authority. Set using its CIM modeller. 2. A imports the change into its EMS. 3. A exports the change to B. 4. B receives the change (full or incremental), updating A’s Model. Authority. Set within its CIM modeller. 5. B renames any new elements and repeats any reduction of A’s Model. Authority. Set. 6. B imports the new model into its EMS. 8 8

Hierarchical Process Definition for an Interconnection u Bottom level. w No significant differences. l l Export changes as the model authority. Import externals from the full interconnection model. u Upper level: w Manages boundary sets. w Creates the full interconnection model. l l Model quality evaluation. Study state estimation. w Derives operational model in the same manner as lower levels. l Different reduction criteria. u Design extends to any number of hierarchical levels. 9 9

The CIM Model Exchange Business Process 10 10

Format Issue: Bus-Branch Models u UCTE (and other power flow formats) are “bus-branch” w Substations have one “bus” for each normally connected set of bus sections. w Switches and circuit breakers are normally not modeled. w Bus numbers or names are often the key tool for engineers in navigating the model and comparing results. u CIM EMS modeling is “node-breaker” w Substation switches and breakers are normally modeled so that real-time configurations can be evaluated. w Nodes represent bus sections and other electrical junctions. w Buses are calculated as a result of “topology processing”. 11 11

Format Issue: Bus-Branch Models u Problem has been discussed extensively in the 2007 “CIM for Planning”. u Solution: w Models that only require bus-branch detail simply use one CIM Connectivity. Node per Bus. w When a CIM model is converted to bus-branch form, l l 12 The output of the topology processor is used to form buses. Markers may be added to the CIM modelling to allow consistent buses to be named consistently. 12

Format Issue: Dynamic Data u UCTE and CIM are not “information equivalent” u UCTE (and other power flow formats) represent one point in time w Load and generation at a bus w Desired voltage w Cap bank input u CIM EMS models describe network parameters over time. w Time Schedules w Load Distribution Patterns w Generation and Interchange 13 13

Converting CIM Dynamic Data to UCTE u EMS products have been converting EMS formats to various power flow formats, including EMS, for some time. u Solution: w Scheduling functions calculate values at time T. w Same procedures are used as occurs within an EMS to set up a power flow. w Power flow formats are produced from power flow scheduling functions, not from the raw modeling data. 14 14

Converting UCTE Dynamic Data to CIM u Has been done when power flow cases are used to create external models for EMS. u Solution One – No Changes to CIM: w Power flow values for load, desired voltage, etc. are used to reverse engineer dummy schedules. w Load distribution works pretty well, but other schedules are not usually very good and need amendment. w This approach is most appropriate as a partial initialization procedure for externals. u Solution Two – CIM extensions required: w Single time point, power flow input variables are added to the CIM model. w A new CIM “Scheduled Output Interface” is defined between scheduling and network analysis. w UCTE data uses the new interface rather than the 452 model exchange interface. w This is probably the more appropriate solution for most real business situations. 15 15