CIM Modeling For Market Management Systems
CIM Modeling For Market Management Systems
I
n a practical Market Management System, there are many
services that are available to all other Business
important software components and they are interfaced
Service Components (BSC), e.g., Common Logging
with almost all the other systems of a RTO/ISO. A good
design for system integration should provide enough Service, etc.
flexibility for future expansion while satisfying the business • Orchestrator provides overall process control and
functional requirements. coordination over the ESB.
• EMS. State Estimation (SE) and Real-Time
In recent years, the IEC Common Information Model (CIM) Contingency Analysis (RTCA) provide market
and the Service Oriented Architecture (SOA) have become the systems with real-time network topology, generation
industrial trend for control center system integration. In fact, and load MW values, and real-time transmission
CIGRE D2.24 working group has been developing a CIM and security constraints. On the other hand, Automatic
SOA based standard for Very Large Power Grid Operators Generation Control (AGC) takes the real-time SCED
(VLPGO) around the world. Figure 1 shows a high level solution as the unit base points for generation
example of SOA based RTO system integration. control.
• DA/AS/RT/FTR. Common market functional
components for a RTO/ISO: Day Ahead Market,
Ancillary Services Market, Real-Time Market, and
Financial Transmission Rights (FTR) Market.
• MUI. Market User Interface is for participants to
submit bids and offers and for RTO to publish
market clearing results.
• Data Warehouse is capable to store all market
clearing related historical data for multiple years.
• Market Monitoring is the post market analysis to
detect potential market power. It often requires the
same core market clearing engines that are used to
clear the markets and other statistical tools. Market
monitoring system can access all historical market
data stored in the data warehouse for play back,
Figure 1 – SOA based MMS System Integration market simulation and scenario analysis.
CIM is the Common Information Model, an IEC standard, that The AC2 objectives for PJM MMS systems include:
was created and extended under the sponsorship of EPRI. The
most mature part of CIM in use today is the power system • Importing CIM Network Model into MMS
model that is used by ISOs, RTOs, and TRANCOs, for • Building CIM compliant messages for ESB data
exchanging power system equipment and network connection transfers to replace the messy point-to-point DB links
data. between business components within MMS and
between MMS and other PJM systems.
CME means CIM Market Extensions and it is a phased • Enhancement on system security
implementation of information model components used to • Inter-site coordination
represent wholesale energy market operations. CME is the
result of FERC’s request of EPRI to extend CIM to model
B. Import CIM network model into MMS
SMD (Standard Market Design) functions and facilitate the
integration of CIM into market applications. CME is often
written as a couplet acronym with CIM as CIM/CME. To ensure system operational reliability during markets
operation, MMS requires a detailed transmission network
The chief goal of CME is to standardize the information model which is based on the one used in EMS. In the case of
model and data format for the North American wholesale PJM, the network model is produced by its EMS modeler. In
electricity markets. The key players in this arena include: the past, the network model exchange between EMS and
• ISOs/RTOs MMS has been a time consuming process because it involves
• Generator & Demand Service Response Organizations. many manual steps and thus very difficult to operate and
• Load (industrial and retail demand customers). maintain. One of the main goals of the AC2 project is to
streamline this modeling process utilizing the CIM standards.
• Energy Marketers
The following figure illustrates the main workflow of the new
The CME information model is a common language that
AC2 CIM network model importing process.
describes the data and entity types, the semantics, and the
entities involved in market operations. In addition, NERC has PJM Sonic Environment
mandated that the XML data formatting language be used for Claim
AOA ORG TNA C&S
all CIM/CME data exchanges. Check
ESB
The existing CME structure is very generic and it has to be Network CTGS Pnodes
Contingency
Powerflow NETVALID
Validation
The first (and the most important) step towards a true SOA AS Area
enterprise architecture is to build a common master data model Control
Zone 1
Contro
l Zone
using a UML (Unified Modeling Language) tool. This master
UML model will be used to produce message definitions Control
Area: PJM
(XSDs and WSDLs) that are used to build the data transfers Dispatc
between different Business Services Components (BSC). The h Zone Contro
l Zone
Contr
ol
AS Area
+ areaControlMode: AreaControlMode
+ freqSetPoint: Frequency
calendar), ControlArea
IdentifiedObject
+controlArea
+
+
+
controlArea: Reference
internalArea: Boolean = FALSE
internalAre aDay: Date
•
+ hostControlAre a: Reference* + operatingReserve Req: Reference*
0..* 0..*
following steps:
IdentifiedObject
+ bidVirtual: Enume ratedType = NoBid
Reserv eZone + resourceGroup : Reference*
+ caseInjection: Boolean = FALSE
+ sequenceNumber: int
at different time.
0. .1 + sequenceNumber: int
For example, PJM has the following areas and zones as shown +
+
+
ownerParticipan t: Reference* 0..*
pnode: Reference
reserveZone: Reference
1 +
+
+
genEmergencyCondition: EnumeratedType = Normal
gpmEnabled: B oolean = FALSE
resources: Reference*
gy
Pro
• Create Business Process • Gather Interface Inventory
Flows • Determine Interface Scope
olo
c
ess
hn
• Interface Discovery and
• BSP Discovery
c
Documentation
es
Te
• Create Relational Model and Map to
• BSP Requirements CIM
• Generate UML Model
• Message Generation