View
217
Download
3
Category
Preview:
Citation preview
CIM Use at CenterPoint Energy CIM Use at CenterPoint Energy CIM Use at CenterPoint Energy
September 2010September 2010
Kevin Ding, Valentine EmesihKevin Ding, Valentine EmesihControl Systems, CenterPoint EnergyControl Systems, CenterPoint Energy
“Confidential & Proprietary Information – CEII”
–Company Introduction
–CIM Modeling
–Auto‐Generated One‐lines
– Future Plan
2
Outlines
“Confidential & Proprietary Information – CEII”
3
Company Introduction
“Confidential & Proprietary Information – CEII”
4
Company Introduction
“Confidential & Proprietary Information – CEII”
CenterPoint Energy (CNP) Houston Electric
• About 25% of ERCOT load;
• 5,000 square‐mile electric
service territory serving 2+
million customers;
• Own and maintain the
power lines and electric
distribution system;
• Installing 2+ million smart
meters.
Main reasons to use Common Information Modeling (CIM) at CenterPoint Energy:
1.
Texas Nodal protocol requirement
2.
Model exchangeable with ERCOT entities,
3.
Model exchangeable between internal
applications;
4.
To Standardize a way exchanging messages.
5
CIM Modeling
“Confidential & Proprietary Information – CEII”
Timeline:
6
CIM Modeling
“Confidential & Proprietary Information – CEII”
2005 Initial efforts to convert CNP EMS model to CIM/XML.
2006 ERCOT initiated its NMMS project in 2006.
2007 Contracted to purchase a Common Modeling
Management (CMM) System.
1/2009 CNP CMM system in production.
9/2009 ERCOT implemented Single Entry Modeling in NMMS
Present Incremental Model files are exchangeable between
ERCOT and CenterPoint Energy.
CenterPoint Energy CMM systemProduction System: Redundant setup
Development System: Single server setup
Currently we are using CMM to1.
Exchange incremental model files with ERCOT
Nodal Model Management System
2.
Update CNP Network Applications Model
3.
Generate Common models for other applications,
potentially DMS
4.
Test auto‐layout substation one‐lines
7
CIM Modeling
“Confidential & Proprietary Information – CEII”
System and Processes:
Positives– One Common Model (ERCOT and CNP)
– Fewer application interfaces (e.g., substation model for
DMS)
– Graphic user interface to edit model changes
– Easy access to ERCOT models
– Time‐based model changes
Challenges– Heavy dependency on ERCOT defined schema
– Managing attributes in different namespaces
– Ever‐changing model schema initiated by ERCOT
– Restrictive rules from downstream applications
8
CIM Modeling
“Confidential & Proprietary Information – CEII”
• No text‐file
editing anymore
LINE 2 5 2 0.0001 0.0005 1000 1200 …
Model changes will be done in CMM.
9
CIM Modeling
“Confidential & Proprietary Information – CEII”
Model update example
Dynamic external modeling
10
CIM Modeling
“Confidential & Proprietary Information – CEII”
11
Auto‐Generated One‐lines
“Confidential & Proprietary Information – CEII”
Use XML model file to automatically generate One‐lines
12
Auto‐Generated One‐lines
“Confidential & Proprietary Information – CEII”
13
Future Plan
“Confidential & Proprietary Information – CEII”
CIM/XML models are used in our Network Applications
CNP Network Applications =
Time‐based CIM/XML models + Time‐based auto‐generated one‐lines + Time‐base PI Historian data + Applications
14
Future Plan
“Confidential & Proprietary Information – CEII”
CMM
As-built CIM model
Project CIM model 1 (with NOMCR 1 …i)
Project CIM model k (with NOMCR j …m)
As-built NA database
Project NA database 1
Project NA database k
NA Database Server
15
Future Plan
“Confidential & Proprietary Information – CEII”
As-built NA database
Project NA database 1
Project NA database k
Real-time SCADA data
Historical data
NA functions
User Consoles
Real-time Operations
R-T Operations Planning
Foren
sic
Inve
stiga
tion
Recommended