1 / 24

CIM for Planning and CIM for Dynamic Models - Project Report

CIM for Planning and CIM for Dynamic Models - Project Report. Terry Saxton Xtensible Solutions tsaxton@xtensible.net. CIM User Group Vasteras, Sweden June 13, 2008. EPRI CIM Planning Project. EPRI initiated project in October 2006 Funded by ten utilities and multiple vendors Objectives

misha
Télécharger la présentation

CIM for Planning and CIM for Dynamic Models - Project Report

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CIM for Planning andCIM for Dynamic Models- Project Report Terry Saxton Xtensible Solutions tsaxton@xtensible.net CIM User GroupVasteras, Sweden June 13, 2008

  2. EPRI CIM Planning Project • EPRI initiated project in October 2006 • Funded by ten utilities and multiple vendors • Objectives • Develop a common power system network model that both operations and planning groups can use as a basis for information exchange • Provide the possibility of entering network model data once for both planning and operations applications

  3. Needs Addressed • Improve reliability of transmission grid • Strengthen planning efforts based on actual network contingencies and base conditions • Enable planning studies to be based on actual physical network with all current field changes incorporated • How? • Enable the management and maintenance of a single, common network model for use by both planning and operations • Enable the sharing of steady state, short circuit, and dynamic models • Technical Approach • Extend the IEC 61968/70 Common Information Model (CIM) Standard • Started with defining high priority use cases

  4. Use Cases: P-P • Export a static network model from one planning software program to another to transfer a planning base case for additional study by another party • Steady State model (completed) • Short Circuit model (partially completed) • Dynamic data models (preliminary investigation begun) • Cases may be transferred either within one organization, or between two separate organizations (i.e. RTO – utility) Planning Planning

  5. Use Cases: O-P Planning Planning Operations

  6. Use Cases – Operations to Planning • Import a state estimator or load flow case from the Energy Management System into the planning environment • To establish a planning base case for additional study or for developing a current planning model • Export Contingency Specifications from the EMS or another application for use by the planning application(s) • This would allow coordination between the contingencies used by operations and transmission planning as well as generation planning • Convert the contingency low side load rollover used in the EMS application(s) to the contingency load rollover used in the planning application(s) • Allows coordination between the contingencies used by operations and transmission planning as well as generation planning • Export Load Forecast data from the EMS or another application for use by the planning application(s) • This will provide correct conversion between the models used by operations and transmission planning as well as generation planning

  7. Use Cases: P-O • Export detailed dynamic model data to EMS (e.g., voltage stability analysis) for real-time dynamic assessment analysis Planning Planning Operations

  8. Profiles and Interfaces Planning Planning NMMR Historian • NMMR • Project Repository • As-build Network Model • Historical Data Operations

  9. Accomplishments and Benefits • Brought key suppliers of planning applications and EMS together with utilities to achieve stated objectives • Two workshops conducted • Task Forces prepared use cases for the information exchange between planning and operations and a central network model manager • Achieved agreements on CIM representation of steady state and short circuit models for exchange • Most reuse of existing CIM classes with some new extensions • Conducted multiple conference calls to resolve issues identified by project members • Collaborated closely with current RTO/ISO/utility projects with similar goals

  10. Accomplishments and Benefits • Extended CIM to support the new integration frameworks that incorporate a centralized network model repository and manager • Makes possible single entry of network model changes for use in both planning and operations environments • Enables sharing of models between planning and operations • Enables standard interfaces based on CIM/XML/RDF • Directly supports current ERCOT efforts and stated goals of other RTO/ISOs and member utilities • Defined new profiles for CIM Planning information exchange • Interoperability tests are planned • Proposed CIM extensions and issue resolutions submitted to IEC

  11. CIM Extensions – New Classes • Contains 10 new Classes in the newPlanning Package: • BranchGroup • BranchGroupTerminal • CorrectionValue • Loss Factor • Mutual Coupling • Ownership • Planning Area • PlanningZone • PlanningZoneGroup • WindingImpedanceCorrection

  12. CIM Extensions – New Classes (Cont’d) • Contains 1 new Class in the Topology Package: • ConnectivityNodeGroup • Contains 1 new Planning Class in the Wires Package: • SwitchedShunt • Contains 1 New Planning Class in the Meas Package: • EquipmentRating

  13. New Attributes • Each new class from the Planning Package contains one or more attributes • Added new attributes to Existing Classes: • ShuntCompensator • EnergyConsumer • PowerSystemResource • GeneratingUnit • TransformerWinding • SynchronousMachine

  14. CIM for Dynamic Models • New EPRI project – started March 2008 • Project Objectives • Develop a common model and set of interface profiles based on the CIM that supports the exchange of dynamic models and data between • different planning applications and equipment suppliers • planning applications and operations

  15. Business Needs • Conduct dynamic assessment studies • Contingency analysis • Evaluation of conditions leading up to a catastrophic event • Determine where network upgrades are needed • Studies involve simulations which require dynamic models of generators, loads, other network devices • Models far more detailed than those used for load flow studies • Dynamic models becoming more complex with multiple variations

  16. Business Needs (cont’d) • New plant commissioning • Operating utility must round up various dynamic models in various formats (e.g., PSLF or PSSE) • New equipment requires new models from supplier • May entail research from equipment manuals • Followed by manual tweaking for custom changes • Multiple sources of data from different systems needed for dynamic models • Ex: Transformer test reports stored in Asset Management system

  17. Types of Dynamic Model Exchanges • Standard models • Several approved lists (IEEE, WECC, RFC) • Include multiple models for following categories: • Generators (including wind turbines) • Motors • Excitation systems, limiters, and compensators • Turbine/govenor models • Stabilizers • Loads • Transmission devices • Relay and protection devices • HVDC • User-Defined models • Decomposed blocks for user-written models with parameters

  18. Project Teams Created • Three project teams were created to accomplish the majority of the work on the project • Standard Model Team: Lead - Bill Price • User-Defined Model Team: Lead - Chuck Dubose • CIM Modeling Team: Lead – Kendall Demaree • Other project members not in attendance are invited to join a team

  19. Project Work Accomplished • First cut made at requirements for dynamic model exchange • Will lead to compilation of data elements for exchange profile • Draw heavily on existing PSSE and PSLF file formats currently in use • New project participant DigSilent has additional file format to consider • New inputs from UCTE and Eurostag • Next step is mapping to CIM

  20. Requirements for Standard Models • Name of model • Associated bus number and unit ID in static network model (bus name and kV optional) • MVA base (or MW capability) value • System parameter values. For example for generators: • D-axis transient rotor time constant • Q-axis transient rotor time constant • Inertia constant, sec • Damping factor, pu • D-axis synchronous reactance • Q-axis synchronous reactance • D-axis transient reactance • Q-axis transient reactance • Stator leakage reactance, pu • Saturation factor at 1 pu flux • Saturation factor at 1.2 pu flux • Stator resistance, pu • Compounding resistance for voltage control, pu • Compounding reactance for voltage control, pu

  21. CNG DynamicModels SynchronousMachine f PSS V, θ Generator Ireal, Iimag GeneratingUnit Exciter Associating Dynamic Models to Static Load Flow Model • UML modeling requirements captured

  22. PowerSystemResource Control Block 1 1 * * Block Input Block Output 1 0..1 * Signal 0..1 * 0..1 Measurement Connectivity Modeling Between Control Blocks • Proposal for CIM modeling approach

  23. Key Artifacts to be Produced • Proposed extensions to CIM UML information model • Proposed modeling approach to handle dynamic models • New exchange profiles for the various exchanges between planning applications, operations advanced applications, asset management, and equipment manufacturers • Standard definition for base cases from operations • Template for equipment suppliers to provide dynamic models

  24. Questions?

More Related