Model Parts and Assembly. Jay Britton Britton Consulting LLC

Transcription

1 Model Parts and Assembly Jay Britton Britton Consulting LLC

2 WG13 Ref Model for a Network Analysis Case Physical Network Model Parts Repository Full Model Parts Incremental Model Parts Model Part Types: EQ SC OP DY DL Physical Model Select / Edit Equipment (EQ) - Equipment - Containment - Connectivity - Controls - SIPS - Equipment Rating - Normal operations - Energy allocation Short Circuit (SC) Dynamics (DY) Diagram Layout (DL) Normal Operations (OP) CIM Standard Datasets in a Network Analysis Case Measurement Sources Other External Sources Outage Schedules Energy Forecasts & Schedules SSH Model Parts Repository Full Model Parts Incremental Model Parts Device Status Initialization/Edit Control Setting Initialization/Edit Monitoring Initialization/Edit Energy Injection Initialization/Edit Steady-State Hypothesis (SSH) - Status - Switch status - In Service - Branch end - Tap positions - Control settings - Voltage regulation - Flow regulation - SIPS - Monitoring - Operating limits - Other - Energy Injections - Bulk generation - Solar - Wind - Storage - Traditional Load - DR - etc, Topology & Network Solution Algorithm Topology (TP) - TopologyNodes - association to conducting equipment State Variables (SV) - Energized State - Island Topology - BusVoltage - Bus Injections - Terminal flows - Controls - Violations

3 The Goal: Many Cases from Common Parts Model parts are maintained once TSO A Unified Grid Model TSO B A B C D Study Type 1 O O O Formal specification of modeling responsibility. E F G H I J K L M N O P Formal specification of study assembly process. Study Type 2 O O O Q R S T TSO W U V W X Study Type n TSO X and used in many different study case assemblies.

4 A Model Part is a set of CIM data that can be composed with other model parts to create a complete model. There can be any number of instances (versions) of a given model part. Versions are often used to track the as-built state of the network as the network evolves over time. A model part has business metadata. This describes: Model part name Model part relationship to a framework part Model part data type i.e. information model Model authority who is responsible for the content?

5 A Framework is a set of Framework Parts that define how Model Parts fit together. Two main kinds of Framework Parts: Frames define the regions (like TSOs) that are the responsibility of one model authority. Boundaries define the set of objects that the model authorities of two adjacent frames agree to maintain in common.

6 Framework Boundary nodes A-B Boundary Frame A Frame B B-C Boundary A-C Boundary Frame C

7 Framework Model Part for A Model Part for C Model Part for B A-B Boundary Frame A Frame B B-C Boundary A-C Boundary Frame C

8 Model Part Business Metadata Name: Belgium As-Built Detail Frame: Belgium Model Authority: Belgium TSO Name: German As-Built Equiv Frame: Germany Model Authority: France TSO Name: France As-Built Detail Frame: France Model Authority: France TSO

9 Model Part Content Belgium-Germany Boundary France-Germany Boundary France-Belgium Boundary

10 Assembling Model Parts Dump selected model part bags onto the magic table i.e. a workspace. The dangling references resolve. Dump in selected incremental model parts. The dangling references resolve. When all dangling references resolve, you have a complete case.

11 Incremental Model Parts Similar to Model Parts They have a type They have both envelope and content data. Different from Model Parts They express a change to a model part: Creation of objects Deletion of objects Modification of objects External references point to the modified objects. Used to represent planned new construction projects, for example.

12 An Assembly is a collection of model parts that are composed as part of some process. In discussion, but not yet formally standardized A Procedure describes how to assemble a model. The ability to capture common processes as repeatable, parameter-driven procedures is an essential feature for NMM products. An Audit Trail describes the how a model was assembled. The ability to exchange a case with documentation of how it was produced will greatly reduce the engineering time that goes into checking validity of results.

13 An interconnection framework example: 9 TSO frame parts 12 boundary parts NW W-NW West W-C N-NW North N-C Central East W-SW S-C E-SE SW South SE S-SW S-SE E-C N-NE NE E-NE

14 Monolithic TSO Model Part boundary Energy In/Out Bulk Power Grid Sub-Transmission s boundary Energy In/Out

15 Decomposed TSO Model Part Adds Flexibility boundary Bulk Power Grid boundary boundary boundary boundary Sub-Trans boundary Sub-Trans boundary Sub-Trans boundary boundary Bulk Power Grid boundary boundary boundary boundary Edge Edge Edge

16 Decomposition can be continued down into the distribution system. Use as many levels as are appropriate, but three is a good starting idea: Bulk power level (e.g. 345 and up) Mid-level (e.g or any non-bulk that is networked) Distribution level (primarily radial lower voltages) Strategy for decomposition can be left to the individual top level authority, as long as there are no ties (boundaries) that need to be agreed on.

17 Unifying T and D models Decomposition to lower voltages is the path to unifying transmission and distribution models. When T and D models fit together Better load modeling for T can be derived directly from D. Better source modeling for D can be derived directly from T. Specialized T and D studies are straightforward to create.

18 North Study 1: What TSO Frames to include? NW North NE West Central

19 North Study 2: Add Boundaries for the required Frames. NW W-NW West N-NW W-C North N-C Central E-C N-NE NE E-NE W-SW S-C

20 North Study 3: Add Edge Parts to represent interchange with un-modeled parts. NW W-NW West N-NW W-C North N-C Central E-C N-NE E-C Edge NE E-NE E-NE Edge W-SW W-SW Edge S-C S-C Edge

21 North Study 4: Select detail for TSO Frames. NW W-NW N-NW W-C N-C Central Bulk Inj E-C N-NE E-C Edge NE North TSO Bulk Power Grid E-NE BndryE-NE Edge Bndry Mid Grid Bndry Mid Grid Bndry Bndry Mid Grid Bndry Edge W-SW W-SW Edge S-C S-C Edge Inj / Cons Inj / Cons Inj / Cons West Bulk Power Grid Part Bulk Inj Bndry Bndry Mid Edge o o o Mid Edge

22 IGM CGM Use Case Best Practice Approach

23 Broad Outline 1. An orchestrator defines the situation that is to be represented. 2. The control area participants build IGMs of the situation for their territory. 3. IGMs are sent to the orchestrator. 4. The orchestrator assembles the CGM from the IGMs. 5. The CGM is made available to all parties that will use it to conduct analysis.

24 Using control area specifications Operationally, control areas are very important Load forecasts and energy schedules are based on control areas. In power flow, study situations normally begin with assumptions about load forecasts and net interchange by control area. Using interchange control equations in the power flow is the best way to get a solution that matches the desired situation. CIM provides Control and TieFlow classes for defining control areas. TieFlow objects reference Terminals. TieFlow objects reference the Control that they define. Control areas are like boundaries in that each TieFlow location must be mutually agreed between the pair of control areas connected by the tie. No correspondence is required between frames and control areas, but in transmission, the entities that operate control areas are usually the same entities that are model authorities for the territory within the control area.

25 Recommended practice for control areas and boundaries NW Control NW Control North Control North Control TieFlow + TieFlow - TieFlow + TieFlow - TieFlow - TieFlow + TieFlow - TieFlow + TieFlow - TieFlow + TieFlow - TieFlow + TieFlow - t eq t 1 t eq t t t eq t 2 t eq t NW EQ t eq t 3 t eq t N-NW t eq t t eq t North EQ N-NE 5 t eq t t W-NW t N-C t The boundary is expanded to include all terminals referenced by TieFlow objects. Control area objects are better in separate model parts. If an area is not completely included in a case (so that its interchange control spec would be invalid), this avoids having unsatisfied references from a global control area model part.

26 Suppose we have an interconnection of 9 regions NW W-NW West W-C N-NW North N-C Central East W-SW S-C E-SE SW South SE S-SW S-SE E-C N-NE NE E-NE

27 Mutual agreement is made for both boundaries and control areas. This definition is re-usable across many scenarios. NW Control W-NW W Control N-NW W-C N-C E-NE W-SW S-C E-SE SW Control S-SW W-C N Control C Control S Control S-SE E-C E-C N-NE NE Control E Control SE Control

28 Use Case Step 1. Forecasted Energy and Interchange values are added by the Orchestrator Energy Forecast and Interchange Values NW Control W-NW W Control N-NW W-C N-C E-NE W-SW S-C E-SE SW Control S-SW W-C N Control C Control S Control S-SE E-C E-C N-NE NE Control E Control SE Control

29 Step 2. Submitter adds regional network modeling and prepares IGM using best guess of external Energy Forecast and Interchange Values NW W SW NW Control W-NW W Control N-NW W-C N SUBMITTER C Control W-SW S-C E-SE SW Control S-SW W-C S N Control N-C S Control S-SE E-C E-C N-NE NE E SE NE Control E-NE E Control SE Control

30 Step 3. Submitting an IGM Minimum requirements for submission: The submission shall include the control area s EQ and SSH model parts. The submission shall include TP and SV model parts covering the control area and its boundary. (This is sufficient to check whether the IGM conforms to the specified criteria and is solved.) Optional submission requirements: The IGM shall submit their complete solved power flow case, including all EQ, SSH, TP and SV, retaining all original model part identity. Submitting the complete case gives the orchestrator maximum insight as to how the result was built.

31 Step 4. Building the CGM Energy Forecast and Interchange Values NW W SW NW Control W-NW W Control N-NW N C W-SW S-C E-SE SW Control W-C S-SW W-C S N Control N-C C Control S Control S-SE E-C E-C N-NE NE E SE NE Control E-NE E Control SE Control

32 Step 5. Using the CGM (reduced with edge models) Energy Forecast and Interchange Values NW W NW Control W-NW W Control N-NW W-C N C N Control N-C C Control E-C N-NE NE E W-SW S-C SW S

33