ERCOT Guideline for Interim Updates to the Network Operations Model Excerpted from the “Modeling Expectations” whitepaper D.W. Rickerson

When implementing Transmission Element changes, ERCOT shall correct errors uncovered during testing that are due to submission of inaccurate information. Each TSP shall provide reasonably accurate information at the time of the original submission. ERCOT may update the model on an interim basis, outside of the timeline described in Section , Time Line for Network Operations Model Change Requests, for the correction of temporary configuration changes in a system restoration situation, such as after a storm, or correction of impedances and ratings. Interim updates to the Network Operations Model caused by unintentional inconsistencies of the model with the physical transmission grid may be made. If an interim update is implemented, ERCOT shall report changes to the Public Utility Commission of Texas (PUCT) Staff and the Independent Market Monitor (IMM). ERCOT shall provide Notice via electronic means to all Market Participants and post the Notice on the MIS Secure Area detailing the changed model information and the reason for the interim update within two Business Days following the report to PUCT Staff and the IMM. Interim Updates – Nodal Protocols (5)

Month Target Month Month 15 Model for Week 1 Model for Week 2 Model for Week 3 Model for Week 4 Model for Week 1 Model for Week 2 Model for Week 3 Model for Week 4 Week 1 Week 2 Week 3 Week 4 Initial ValidationMarket ValidationFinal Validation NOMCR Process ing for Target Month Produ ction 10 Period 3Period 2Period 1Period 4 NMG finalizes Model Content for 45-day Posting NMG finalizes Model Content for Production Pre-ProductionProduction Period 1 requests would be submissions that miss the normal deadline by ten days or less. At this point in the validation process ERCOT is still processing the NOMCRs for the Target Month and has not completed the models that will be used in production. Period 2 immediately follows Period 1 and ends on the tenth of the month prior to the Target Month. During Period 2, the Operational Models undergo Initial Validation and are posted. In addition, the information needed to build the CRR models is exported. Period 3 immediately follows Period 2 and ends when the affected model goes into production. At this point in the validation process the 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. Period 4 immediately follows Period 3, beginning two days prior to the time the affected model is scheduled to be loaded into production. Interim Updates allowed during Period 4 will require an Emergency Data Base load.

Interim Update Classes 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.

NOMCR R submitted after 3.10 deadline Class 1Class 2Class 3Class 4Class 1Class 2Class 3Class 4Class 1Class 2Class 3Class 4 Class 1Class 2Class 3Class 4 Included in Model, not an Interim Update Period 1 Period 2 Period 3 Period 4 update Not Included in Model, as an Interim Update Included in Model as an Interim Update Included in Model as an Interim Update requiring an Emergency Database Load yes No ImpactMitigatedNo MitigationSevere