ERCOT / NERC Compliance Update October 9, 2003

1

ERCOT / NERC Compliance

UpdateOctober 9, 2003

2

NERC Compliance Reporting

• 64 Planning Standards• 17 Operating Standards

• Types of Assessments– Periodic Reports– Self-Certifications– Investigations– Audits

3

NERC Compliance Reporting

Measure P2T2 – Operating Security Limit (OSL) Violations

• Return Transmission System to within Operating Security Limits within 30 minutes

• Violations reported to the NERC Compliance Director within 72 hours

• Regional Reliability Organization (RRO) selects critical elements to be monitored

4

NERC Compliance Reporting

OSL Violations

• 2002 – 103 Violations reported to NERC– Based on Double Circuit Contingency Criteria

• 2003 – 2 Violations reported to NERC so far– Based on W-N and S-N CSCs Criteria

• If 2003 criteria would have been used in 2002, there would have been approximately 6 Violations reported in 2002.

5

NERC Compliance Reporting

OSL Violations

• ERCOT has not changed what is monitored and analyzed, only the criteria used to determine what is reported to NERC

6

ERCOT Protocol Compliance

Types of Assessments

• Day-to-Day Monitoring– Fail to follow Valid Dispatch Instructions

• Data Gathering and Reporting– Unit Net Dependable Capability Testing

• Audit/Self-Certification

• Investigation– EECP

7

ERCOT Protocol Compliance

Who will be assessed?• Transmission Operators• Qualified Scheduling Entities• Power Generating Companies

When will enforcement begin?• Enforcement of some has already begun (Day-Ahead

and Real-Time Operations related Protocols)• Enforcement of remaining Reliability-Based Protocols

to be phased in beginning January 1, 2004

8

ERCOT Protocol Compliance

Reporting

• Assessment (Reporting) Period for the different Protocols will vary, i.e., continuous, monthly, seasonal, annual, biennial.

• Report Card – Information related to which MPs pass and fail each assessed Reliability-Based Protocol will be posted on the ERCOT Web Site