SCR #760 · Revision Request
SCR760 Recommended Changes Needed for Information Model Manager and Topology Processor for Planning Models
ReasonERCOT decided that system modeling information feeding downstream applications, market apps, operations systems, and planning models would reside in one database, which is the Information Model Manager. The Topology Processor is a piece of software that takes the Information Model Manager database (a breaker/switch model) and modifies the data into a planning model (a bus/branch model). This model will then be input into the Model On Demand (MOD) software which will be used to create future planning cases. Since 2009, the SSWG began a detailed review of the Topology Processor output and has noted a number of deficiencies in the Information Model Manager and/or Topology Processor. These deficiencies have to be corrected to produce usable cases for planning analyses; therefore, rather than make these corrections on the back end of the process through MOD each time a case is created, we strongly urge the adoption of the changes suggested in this SCR. The deficiencies with the current output of the Topology Processor are listed in a ranked order of importance to the SSWG. Potential resolutions have been offered; however, further discussion with ERCOT and its vendors will be needed before finalizing.
Created2010-11-11
Approved2011-03-22
Sections Affected
Changes to the Information Model Manager and Topology Processor
Summary
This System Change Request (SCR) proposes changes to the Information Model Manager and Topology Processor to fix a number of deficiencies with the proposed Annual Planning Model creation process.
Timeline
-
Nov 4 '10
PRSFiled by Wesley Woitt on behalf of the SSWG
-
Nov 11 '10
ROS ROS MeetingROSRecommended for Approval Urgent status Recommended for approval“Voted to grant Urgent status to SCR760 and to recommend approval of SCR760 as submitted.” — Passed
-
Nov 18 '10
PRS PRS MeetingPRSRecommended for Approval Priority Recommended for approval Forwarded → TAC“To recommend a priority of Critical and to endorse and forward the 11/11/10 ROS Report for SCR760 to TAC” — Passed→ TAC Consideration
-
Dec 6 '10
TAC TAC MeetingTACDeferred/Tabled Tabled“To table SCR760 for one month” — Passed→ TAC Consideration
- Dec 15 '10
-
Jan 6 '11
TAC TAC MeetingTACDeferred/Tabled Tabled“To table SCR760 for one month.” — Passed→ TAC Consideration
- Jan 13 '11
-
Feb 3 '11
TAC TAC MeetingTACDeferred/Tabled Tabled Amended by the Jan 24 '11 ROS comments“To table SCR760 and to direct ERCOT to complete an impact assessment based on the 1/24/11 ROS comments” — Passed→ TAC Consideration
-
Mar 3 '11
TAC TAC MeetingTACRecommended for Approval Recommended for approval Amended by the Jan 24 '11 ROS comments Priority“To recommend approval of SCR760 as amended by the 1/24/11 ROS comments with a priority of Critical and a rank of 3.5” — Passed→ ERCOT Board Consideration
-
Mar 22 '11
BOARDEmail Vote / Unlisted MeetingBOARDApproved Approved“To approve SCR760 as recommended by TAC in the 3/3/11 TAC Report” — Passed
- Apr 11 '11
-
Apr 19 '11
Listed without action at 20 meetings (Apr 19 '11 – May 8 '13)
- NDSWG Meeting
- ROS Meeting
- ROS Meeting
- ROS Meeting
- ROS Meeting
- ROS Meeting
- ROS Meeting
- Reliability and Operations Subcommittee (ROS) Meeting
- Reliability and Operations Subcommittee (ROS) Meeting
- Steady State Working Group (SSWG) Bi-Weekly Meeting by WebEx Only
- Reliability and Operations Subcommittee (ROS) Meeting
- Steady State Working Group (SSWG) Bi-Weekly Meeting by WebEx Only
- Steady State Working Group (SSWG) Bi-Weekly Meeting by WebEx Only
- Reliability and Operations Subcommittee (ROS) Meeting
- Steady State Working Group (SSWG) Bi-Weekly Meeting by WebEx Only
- Reliability and Operations Subcommittee (ROS) Meeting
- Steady State Working Group (SSWG) Meeting
- Steady State Working Group (SSWG) Bi-Weekly Meeting by WebEx Only
- Steady State Working Group (SSWG) Meeting by WebEx only
- Steady State Working Group (SSWG) Meeting by WebEx only