1.

Antitrust Admonition

Calhoun

9:30 am

2.

ROS Meeting Report

Calhoun

3.

OWG meeting minutes approval:  July meeting minutes review and approval.

All

4.

NOGRRs for review and language changes:

• 100NOGRR Extending Manual Time Error Correction Threshold.  This Nodal Operating Guide Revision Request (NOGRR) extends the manual time error correction threshold from +/- 3 seconds to +/- 30 seconds. The increased threshold of +/- 30 seconds will provide a larger window for self-correction of the accumulated time errors. [ERCOT] Impact Analysis Review
• 101NOGRR Market Transparency for DC Tie Outage Information.  This Nodal Operating Guide Revision Request (NOGRR) provides that ERCOT shall produce a detailed report regarding any outage of a Direct Current Tie (DC Tie) in a timely manner.  Outages of interconnection points between the ERCOT and non-ERCOT Control Areas have market implications on both the ERCOT market and the interconnected market.  Detailed information regarding such outages is necessary for Market Participants on both sides of the interconnection point to be able to manage risk associated with such outages. [Tenaska]  Language Review  *Calpine Comments
• 102NOGRR Synchronization with NPRR454, Removal of Unfunded Project List Language.  This Nodal Operating Guide Revision Request (NOGRR) aligns the Nodal Operating Guides with Nodal Protocol Revision Request (NPRR) 454 (approved by the ERCOT Board on July 17, 2012) which removed language regarding the Unfunded Project List. 
• This NOGRR also aligns the Nodal Operating Guides with the Protocols by requiring ERCOT’s opinion in the TAC Report for any NOGRR requiring an ERCOT project for implementation; and includes administrative alignment changes. [ERCOT] Language Review

All

5.

Operations Report

• Monthly Operations Report Summary/Questions

ERCOT

6.

Nodal Protocol and Guides Resolution Task Force Report

• NPGRTF to review the concerns related to voltage profile set points and SCADA accuracy and return finds of whether or not OWG needs to address this issue to OWG in July.

Owens

7.

Operations Task Force Report

Morris/Blackmer

8.

Texas RE Update Report

Penny/Henry

9.

System Operations Report

• Operating Procedure changes that impact market participants.

ERCOT

10.

Other

Questions to OWG from Curtis Crews.  He would like to hear OWG’s opinions.

1. Please review the definition of an OCN and clarify (a) if emergency condition should be capitalized and if the (b) Protocol reference regarding details is correct.  Compared to the other possible levels of communication, OCN appears to be inconsistent.  
2. The Protocol definition of Emergency Notice indicates that it is issued in anticipation of a possible Emergency Condition which seems to conflict with Operating Guide 4.2.4 (3) which states (in part)  When an Emergency Notice is issued, ERCOT is operating in an emergency operating condition.  (a) Is an emergency operating condition different than Emergency Condition? (b) If not, there is no anticipation is there?  (c) If there is a difference, what is it?
3. (a) Section 6.5.9.3 (3) has a similar reference that does not appear to be correct.  Section 6.5.9.3.4 has a few caveats of note starting with 6.5.9.3.4 (2) and what text should be considered below (b) (is it formatting and all four items are sub-bullets??) (c) And which of those items may put ERCOT in an unreliable condition?
4. Additionally, the one or both reference in 6.5.9.3.4 (2)(f) appears to be incorrect as there are more than two measures listed in 6.5.9.2 (3).
5. In 6.5.9.1 (3) the phrase emergency limit should probably be Emergency Rating as referenced in Operating Guide 2.2.2 (2) (b).  Technically a generator is a Transmission Element and does have emergency limits specified by the owners but the inference appears to be Transmission related.

All

11.

Future Meeting Date:

Calhoun

Adjourn

Calhoun

3:00 pm