- Home
- Grid Information
- Transmission
- Production Load Schedule
Production Load 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 (NOM) through the submission of model and outage data.
The table at the bottom represents a schedule of planned updates to the ERCOT 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 Production Load. This calendar is applicable to all network topology, registered Resource parameter, QSE-to-Resource relationship and telemetry changes submitted by Transmission Service Providers (TSPs), Resource Entities (REs), and Qualified Scheduling Entities (QSEs). Refer to the 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).
Interim Updates Restriction List
Items removed from interim update consideration (submittal deadline of Protocol 3.10.1 timeline applies): *
- New topological changes for field transitions requiring Existing/Future modeling in the same CIM model where Contingencies need to be created and managed in ERCOT’s model(s) for the time of field transition
- New substations with Line-Breakers (or substation Breaker/Line reconfiguration)
- New physical Lines
- New Transformers
- TSP equipment for new Generation with coordinated model-ready date
- Synchronous Condenser
- Items requiring Resource Node additions/modifications
Interim items considered for processing, if meeting the 65 Calendar Days prior to Production Load submittal deadline: *
- New Tap Station (No Line controlling Breakers)
- New Shunt Compensator
- New SVCs
Interim items considered for processing, if meeting the 20 Calendar Days prior to Production Load submittal deadline: *
- Field vs Model Cleanup (Only Deletes)
- New Loads (with controlling Breaker if applicable)
* Exceptions
- If needed to avoid a reliability risk in the ERCOT grid, and if in a timeframe that is less than the submittal deadline listed above, the MP shall provide, as an attachment to the change request (NOMCR, CAMR, or ICR), 1) the TSP Interim Update Request Form or the RE Interim Update Request Form and 2) supporting information of a reliability risk for consideration, involving these change items, that demonstrates the change relieves a reliability concern.
- In an ERCOT declared Emergency, Interim Update restrictions may be temporarily waived.
Downstream Production Changes
For an applicable model change that is considered a Downstream Production Change (DPC) per the Modeling Expectations, the MP shall provide as an attachment to the change request the TSP DPC Request Form and RE DPC Request Form.
Telemetry Points Updates
ERCOT Protocols consider telemetry point additions and changes submitted 20 days prior to the Production Load as non-interim updates. Protocols allow ERCOT five days to process NOMCR requests. ICCP data must be in compliance with the ERCOT Nodal ICCP Communication Handbook in accordance with Nodal Operating Guide Section 7.2, ERCOT ICCP Interface and Section 7.3, Telemetry.
QSE NDCRC Submittals
The Net Dependable Capability and Reactive Capability (NDCRC) application allows 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, as well as other test data. Such revisions must also be submitted through a Resource Asset Registration Form (RARF) by the RE in order to be uploaded into the NOM. When submitting RARF with updated unit test data, the RE is to note this on Service Request.