Network Operations Model Change Schedule

ERCOT Protocols broadly delineate modeling requirements for different segments of the ERCOT market.  The information on this page is intended to more clearly define the expectations ERCOT has for market participants as they help to maintain the accuracy of the ERCOT Network Operations Model through the submission of model and outage data.

The table below represents a schedule of planned updates to the ERCOT Network Operations Model (NOM) through the Network Model Management System (NMMS) in accordance with Nodal Protocol Section 3.10.  Each row of dates is in support of a planned CIM database load (column labeled “Nodal DB Load”).  This calendar is applicable to all network topology, registered resource parameter, and telemetry changes submitted by transmission service providers (TSP), resource entities (RE), and qualified scheduling entities (QSE).  Refer to Modeling Expectations document for additional information on NOM update process.

Interim Updates:  Network Operations Model Change Requests (NOMCRs) that are submitted outside of the normal timelines are classified as Interim Updates and included in the Network Model if they are needed to correct unintentional modeling inconsistencies, are required for system restoration after a storm, or are a correction to previously submitted impedances or ratings.  Interim Updates will be reported to the Public Utility Commission of Texas (PUCT) Staff and the Independent Market Monitor (IMM).

NOM Update Schedule Definitions

[A] Deadline for Model Change:  This date is the 90-day cut-off for submittal of network topology and resource parameter changes that will not be considered as Interim Update. ERCOT request that registration of a NEW Generation Resource, required to be represented in the NOM, be submitted beginning 120 days prior to the first operating day of the interconnection. Refer to New Generations Resources -- Steps to Register page for further details. 

[B] Interim Update Period 1 Ends:  Submissions that miss the normal deadline by ten days or less.  ERCOT is processing the NOMCRs for the Target Month and has not completed the models that will be used in production.   Class 1-4 updates may generally be accepted as Interim Updates.

[C] Market Validation Start Date:  Operational Models undergo Initial Validation and are posted.  Information for CRR models is exported.

[D] Interim Update Period 2 Ends:  Immediately follows Period 1 and ends on the tenth of the month prior to the Target Month.  Class 2-4 updates may generally be accepted as Interim Updates.

[E] Market Validation End Date:  Final market validation is to be completed.  CRR Models are validated and posted.

[F] Interim Update Period 3 Ends:  Final production models have been completed and are being validated for use in production.  Period 3 will vary in length depending on when the affected model goes into production.  Class 3-4 updates may generally be accepted as Interim Updates.

[G] Nodal DB Load:  Date production ready NOM is loaded and used for Day-Ahead Market and Real-Time Operations.  

[H] Interim Update Period 4 Ends: Period 4 begins two days before the affected model is scheduled to be loaded into production and ends before last load.  Interim Updates allowed during Period 4 will require an Emergency Data Base load and for Class 4 only.

Telemetry Points Updates:  ERCOT protocol considers telemetry point additions and changes submitted by the 15^th of the month prior to the NOM update Target Month as non-interim updates.  ICCP Change Requests submitted after the 15^th will be considered as Interim Update and considered for approval based on classification of update (Class 1-4).

The resource entity (RE) and associated qualified scheduling entity (QSE) are encouraged to coordinate changes in relationships according to the posted schedule.  A change in the operations system is required to establish the operational relationship between QSE and generation resource in ERCOT's EMS.  The RE and QSE are asked to consider the Network Operations Model Change Schedule below when establishing an effective date when NEW resource interconnection is first energized, new QSE representing resources, and Resource changing QSE.  For NEW resources allow 7 days from EMS Database Load date and date the interconnection is approved to energize.

Market Participants setting up a new QSE representing resources need to plan across two NOM database load dates to accommodate the new QSE (or subordinate QSE).  The first database load is used to set up the new QSE in EMS and the second database load is used to map resource(s) and telemetry in the EMS.

QSE NDCRC Submittals: The Net Dependable Capability and Reactive Capability (NDCRC) application allows Qualified Scheduling Entities (QSEs) with Generation Resources to submit the ERCOT required seasonal High Sustained Limit (HSL), biennial unit reactive tests and results of the unannounced tests online and other test data.  Such revisions must also be submitted through resource asset registration (RARF) by the RE in order to be uploaded into the NOM.

Interim Update Classification

Class 1 Interim Update requests will have no impact to market or reliability after implementation.

Class 2 Interim Update requests will have an impact to market or reliability that can be mitigated in real-time with changes to data in downstream systems that can be managed by ERCOT.  In some cases ERCOT may request assistance from the Interim Update requestor in mitigating the effects of the change.

Class 3 Interim Update requests will have an impact to market or reliability that cannot be mitigated in real-time with changes to data in downstream systems. 

Class 4 Interim Update requests are those that if not incorporated in the model at the requested time will have a severe impact to either the market or reliability.  Class 4 updates should always be a result of circumstances that could not be reasonably anticipated.