MIS LOG IN

NPRR132

Summary

Title: Outage Clarification
Next Group:
Next Step:
Status: Approved on 08/19/2008
Effective Dates:
12/01/2010

or per the Nodal Protocol Transition Plan http://www.ercot.com/mktrules/protocols (09/01/08 Nodal Protocols Library)

Action

Date Gov Body Action Taken Next Steps
07/17/2008 PRS Recommended for Approval Consideration of NPRR132 by TAC.
08/07/2008 TAC Recommended for Approval Consideration of NPRR132 by the ERCOT Board
06/19/2008 PRS Recommended for Approval Review of Impact Analysis
08/19/2008 BOARD Approved
05/22/2008 TPTF Recommended for Approval PRS consideration

Voting Record

Date Gov Body Motion Result
07/17/2008 PRS To endorse the Impact Analysis and Recommendation Report for NPRR132 and forward the documents to TAC. Passed
08/07/2008 TAC To recommend approval of NPRR132 as recommended by PRS with the caveat that documentation of "outage" versus "Outage" will be developed subsequently by ERCOT Staff. Passed
06/19/2008 PRS To recommend approval as submitted. Passed
08/19/2008 BOARD To approve NPRR132 as recommended by TAC. Passed
05/22/2008 TPTF To endorse NPRR132 as submitted. Passed

Vote tallies here reflect individual votes, not the weight of the votes by market segment. Affirmative votes are not recorded in these vote tallies. For additional details on the voting record, please consult the Recommendation or Action Report, or the official vote tally if available, as posted in the key documents.

Background

Status: Approved
Date Posted: May 16, 2008
Sponsor: ERCOT Staff
Urgent: No
Sections: 4.2.3, Posting Forecasted ERCOT System Conditions
Description: This Nodal Protocol Revision Request (NPRR) changes the use of the defined term "Outage" to generic "outage" to clarify that the Protocol language regarding outages in the CIM model includes known normal operating status outages, not Outages as defined in Section 2.1, Definitions. .This NPRR also proposes non-substantive edits.
Reason: Using the defined term "Outage" for the purpose of the Network Operations Model is technically not feasible because this information is not available in the Common Information Model (CIM) Standard.

Key Documents

Related Content