PRR for Protocol 8
May 14, 2003
2002 Generation Outages
Reasons
 for Protocol Revision
•	Contingency analysis studies based on inaccurate data noted at PUC Workshop

•	Numerous cases where a Resource Outage was moved and Transmission Outage had to be re-scheduled

•	Reliability window needed for ERCOT analysis

•	RMR & Black Start guidelines needed

Reasons 
for Protocol Revision
•	Cost savings expected as a result of changes
–	Resource scheduled off in Outage Scheduler that is on in the Resource Plan
–	Resources that are unavailable in Resource Plan and are not scheduled in Outage Scheduler
–	Real-time correction changes as a result of inaccurate scheduling
Applicability of Parts of Section 8
•	8.1 Transmission and Resource
•	8.2 Transmission and Resource
•	8.3 Transmission
•	8.4 Resource (other than Reliability Resources)
•	8.5 Reliability Resources
•	8.6 All Resources
•	8.7 Resource Adequacy
•	8.8 Topology
Changes to Protocol 8
•	Moved sections pertaining to Transmission together
•	Made minor changes to Transmission
–	Editorial in nature and did not change meaning
•	Defined “Reliability Resource” as a general name for RMR, Black Start, Sync Condenser units
•	Specifics of Reliability Resource added
Reliability Resources
All Resources other than Reliability Units
Changes to Protocol 8
•	ERCOT Requirements
–	Approval Rules
–	Rejection Rules
–	Withdrawal Rules
•	Unplanned Outages Defined
–	Forced
–	Level 1
Protocol 8 Outline
•	8.1.3 Rolling 12 Month Outage Planning
–	Transmission and Resources separated
–	Statement added stating Outages entered <30 days before start date required approval
Protocol 8 Outline
•	8.2 Communications
–	Single Point of Contact defined
•	8.2.2 Outages must be submitted via Outage Scheduler
•	8.2.4 Reporting of Resource Outages (duplicate of Transmission statement
Protocol 8 Outline
•	8.3.3 Timeline for approval of Transmission Outage
–	Change to accommodate 06:00 posting requirement and reflect actual practice
Posting Correction
Protocol 8 Outline
•	8.4 Approval Resource Outages
–	Requests entered <30 days before start date require approval
–	Outage cannot be rejected if reliability standards are met (duplicate of Transmission statement)
Protocol 8 Outline
•	8.4.1 Information to be included on Request Form
–	2 items added
•	Primary and Alternate Phone Numbers
•	Nature of work being performed
Protocol 8 Outline
•	8.4.3 Changes to Resource Plan
–	Resource Outages will be accepted without comment for all changes with >30 days notice before start of the Outage
–	Resource Entities must obtain ERCOT approval for changes made <30 days before the start of the Outage
Protocol 8 Outline
•	8.4.4 Timelines for ERCOT Response
–	Outages received between 3 & 8 days before start date
•	ERCOT will approve/reject 2 days before start date
–	Outages received between 9 & 30 days before start date
•	ERCOT will approve/reject 4 days before start date

Protocol 8 Outline
•	8.4.5 Delay
–	Approval may be delayed if insufficient data is submitted
Protocol 8 Outline
•	8.5 Approval of Reliability Resources
–	ERCOT approval guidelines statement
Protocol 8 Outline
•	8.5.1 Timelines for response by ERCOT (12-Month Outage Programs)
–	Greater than 45 days before start date of Outage
•	Approve/reject 30 days before start date
–	Received no less than 30 days before start date of Outage
•	Approve/Reject 15 days before start date
Protocol 8 Outline
•	Other repairs that are needed
–	Received between 3 & 8 days before start date of Outage
•	Approve/reject 2 days before start date
–	Received between 9 & 30 days before start date of Outage
•	Approve/reject 4 days before start date
Protocol 8 Outline
•	8.5.2 Changes to an Approved Reliability Resource Program
–	A Change Request Form must be submitted 30 days before start date of Outage
–	Approve/reject 15 days after receipt
Protocol 8 Outline
•	8.6 Management of all Resource Outages
–	8.6.1 Rejection of proposed Resource Outages
•	ERCOT requirements for rejecting Outages
–	8.6.2 Withdrawal of Outage approvals
•	ERCOT requirements for withdrawing approvals
Protocol 8 Outline
•	8.6 Management of all Resource Outages
–	8.6.3 Deratings
•	Deratings that extend for more than 24 hours must be entered in Outage Scheduler
–	8.6.4 Management of Resource Unplanned Outages
•	Forced Outage Defined
•	Level 1 Outage Defined
–	Removal of unit must be coordinated with ERCOT