Transcript CIM Fundamentals

EMS User’s Group
CIM Extended to Power System
Planning at ERCOT
Presented By
Margaret Goodrich
Project Consultants, LLC
[email protected]
Presented to
EMS User’s Group
Austin, TX September 25, 2007
Topics
• ERCOT Requirement
• ERCOT CIM Extensions
– New Packages
– New Classes
– New Attributes
• Topology Processor Customization
• EPRI CIM for Planning Project
– Objectives
– Key Steps
– Use Cases
– Additional Extensions
© 2007 Project Consultants, LLC All rights reserved.
EMS User’s Group – September 25,2007 – Austin, TX
2
ERCOT Requirements and Needs
•
•
•
•
•
ERCOT has been mandated by Nodal Protocols to use CIM standards
for model exchange and posting
Annual Planning Models are required by protocols to be posted in
CIM/XML format
ERCOT needs an agreed upon framework to:
– Map a planning model to the CIM
– Provide incremental Planning files in CIM/XML
– Convert a solved model in Network Operations to a solved model in
planning
Improve consistency between the Planning model and the Operations
model.
Obtain naming consistency between Operations and Planning models
© 2007 Project Consultants, LLC All rights reserved.
EMS User’s Group – September 25,2007 – Austin, TX
3
ERCOT CIM Extensions
• The Network Modeling Group has extended the
CIM for all ERCOT needs including EMS and/or
Planning
• For Planning, we have identified:
–
–
–
–
–
–
In-Service/Out-of-Services Flags
Ownership & Operatorship
Ratings (Static & Dynamic)
Latitude & Longitude
Location/County
Bus Number
© 2007 Project Consultants, LLC All rights reserved.
EMS User’s Group – September 25,2007 – Austin, TX
4
ERCOT CIM Extensions
• In-Service/Out-of-Services Flags - an Attribute of a PSR
(Boolean)
• Ownership - This contains one or more names of the
owners and the percentage of ownership. Every Device in
the model will inherit from this.
• Operatorship - This contains one or more names of the
operators and companies that operate the Transmission
Element.
© 2007 Project Consultants, LLC All rights reserved.
EMS User’s Group – September 25,2007 – Austin, TX
5
ERCOT CIM Extensions
• Ratings (Static & Dynamic) - This class needs to model both
Static and Dynamic ratings (or we can add an additional
class for Dynamic ratings). There must be three types of
Ratings: Normal, 2 Hour, and Emergency (15 minutes for
operations and conductor for planning).
• Latitude & Longitude - is a decimal number that is an
attribute of a Substation
© 2007 Project Consultants, LLC All rights reserved.
EMS User’s Group – September 25,2007 – Austin, TX
6
ERCOT CIM Extensions
• Location/County – is a string that is an attribute of a
Substation
• Bus Number – is an integer that is an attribute of a
Topological Node
© 2007 Project Consultants, LLC All rights reserved.
EMS User’s Group – September 25,2007 – Austin, TX
7
CIM Extension - New Packages
• New Packages include:
– ETXContingency
– ETX
– ETXLoadModel
– ETXMonitoring
– ETXNetwork
– ETXPlanning
– ETXRASE
– ETXRating
– ETXRegulation
– ETXSCADA
© 2007 Project Consultants, LLC All rights reserved.
EMS User’s Group – September 25,2007 – Austin, TX
8
New Classes
• Some of the classes include:
– BranchGroup
– MonitoredGroup
– ConnectivityNodeGroup
– PlanningArea
– PlanningZone
– ProtectiveAction
– RemedialActionScheme
© 2007 Project Consultants, LLC All rights reserved.
EMS User’s Group – September 25,2007 – Austin, TX
9
New Attributes
• Some of the attributes include:
– minimumEnergencyMW
– MWMax
– PSSEBusNumber
– maximumActivePower
– minimumReactivePower
– isRAS
– isRAP
– Generationloss
– Loadloss
© 2007 Project Consultants, LLC All rights reserved.
EMS User’s Group – September 25,2007 – Austin, TX
10
Updated Topology Processor
• ERCOT has procured a new Topology Processor that provides
options to handle the differences between the operations and
planning model:
– Option to Collapse the three 2-winding transformers that
represent a three winding transformer to one 3-winding
– Option to convert Distributed Generators to Negative Loads
– Option to select a containment schema - Zone or Area
population has a containment of Load, Owner and Weather
– Option to provide an updated contingency list based on
topology processed file
– Option to specify a temperature to be used as the basis for
the rating of dynamically rated lines
© 2007 Project Consultants, LLC All rights reserved.
EMS User’s Group – September 25,2007 – Austin, TX
11
EPRI CIM Planning Project Objectives
• Develop a common 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
• To build transparency between the operation models and
planning models, thus allowing both sides to share critical
common information (e.g. ratings, impedance etc). This effort
will also evaluate the CIM readiness from two vendors (one for
EMS and one for Planning).
• To evaluate the adequacy of CIM database as a single data
source for a power system model repository for PLANNING.
© 2007 Project Consultants, LLC All rights reserved.
EMS User’s Group – September 25,2007 – Austin, TX
12
EPRI CIM for Planning Project - Key Steps
1.Define and analyze use cases to identify priority business processes and
requirements that need to be supported in the CIM and when exchanging
models
– Identify processing requirements for transformation/translation
– Identify data exchange requirements that need to be supported in the CIM
2.Identify and resolve differences between operational and planning models.
3.Identify and document planning extensions for the CIM
– Develop extensions to UML diagrams – add to existing and/or create new
class diagrams for planning models
– Define new planning profile(s) sufficient to support model types.
4.CIM Mapping Spreadsheets
– Develop agreements to map proprietary data representations to CIMbased representations
© 2007 Project Consultants, LLC All rights reserved.
EMS User’s Group – September 25,2007 – Austin, TX
13
EPRI CIM for Planning Project - Key Steps
(cont’d)
5. Define the XML/RDF schemas needed to support the priority information
exchange requirements between planning and operations
6. Conduct interoperability tests to prove the feasibility of model resolutions,
CIM extensions, planning profiles defined, and XML/RDF schema
definitions.
7. Prepare technical report to document recommendations and issues
8. Conduct industry workshops
9. Submit documents produced to the appropriate standards committees to
incorporate the planning extensions into the CIM and related standards.
© 2007 Project Consultants, LLC All rights reserved.
EMS User’s Group – September 25,2007 – Austin, TX
14
Mapping Spreadsheets
Generic Data
Requirement
CIM Class and Property
CIM
Extension
Area Identifier
InterchangeArea.mRID
Yes
Area Name
InterchangeArea.name
Yes
Swing Bus Identifier
TopologicalNode.type=area
swing bus
Yes
Scheduled Net Interchange InterchangeArea.pNetChange
Yes
Interchange Tolerance
InterchangeArea.pTolerance
Yes
Area Description
InterchangeArea.aliasName or Yes
InterchangeArea.description
© 2007 Project Consultants, LLC All rights reserved.
EMS User’s Group – September 25,2007 – Austin, TX
15
EPRI CIM for Planning - Use Cases
• Operation to Planning -- Allow planning to import CIM
compliant power flow model from EMS. Planning then can
compare critical common information used in both Operation
and planning models.
• Planning to Operation -- Allow planning to send new
equipment parameters in CIM format back to EMS.
• Planning to Planning -- Be able to generate base cases
efficiently, consistently and reliably and exchange these with
other planning applications.
© 2007 Project Consultants, LLC All rights reserved.
EMS User’s Group – September 25,2007 – Austin, TX
16
More Information
• Email: [email protected]
• Cell: (903) 477-7176
• CIM User’s Group Web Site:
http://sharepoint.ucausergroup.org/CIM/
© 2007 Project Consultants, LLC All rights reserved.
EMS User’s Group – September 25,2007 – Austin, TX
17