Validation Results

5b1ff0b9bcb5bf000400000c

http://www.ercot.com/mktrules/issues/csv/NOGRR/All

Sorry, your CSV did not pass validation. Please review the errors and warnings below:

Total Rows Processed = 182

Download Standardised CSV
16Errors 3Warnings 1Messages
Structure 15 0 1
Schema 0 0 0
Context 1 2 0

16 Errors, 3 Warnings

Context problem: Incorrect content type

Your CSV file is being delivered with an incorrect Content-Type of text/html.
We recommend that you configure your server to deliver CSV files with a Content-Type header of text/csv; charset=utf-8

Structural problem: Stray quote on row 37

NOGRR036,Synchronization with PRR821 and PRR804,"This Nodal Operating Guide Revision Request (NOGRR) synchronizes the Nodal Operating Guides with PRR821, Update of Section 21, Process for Protocol Revision, and PRR804, Revisions to Section 21 Appeal Process.  Specifically, this NOGRR revises Section 1.3 to more effectively align with the current stakeholder process and to provide that if a motion to approve a request fails, the revision request shall be deemed rejected by the body considering it and subject to appeal, unless at the same meeting that body later votes to recommend approval, remand, or refer the revision request.  
 Changes were made to bring consistency between the NOGRR process, where applicable; remove arbitrary or conflicting timelines; clarify commenting process; expand on a revision request being deemed rejected to include email voting for the Reliability and Operations Subcommittee (ROS) and Technical Advisory Committee (TAC); and include formatting and administrative changes.",03/19/2010,ERCOT,No,1.3,Approved,08/01/2010,""

One or more values in the row have been incorrectly quoted. E.g. a comma has not been escaped, or a quoted field has not been properly escaped
Check the values in the column and ensure that quoting has been correctly applied.

Structural problem: Stray quote on row 40

NOGRR039,Synchronization of Section 1 with Nodal Protocols,"This Nodal Operating Guide Revision Request (NOGRR) aligns the Nodal Operating Guides with the Nodal Protocols by adding additional detail to Nodal Operating Guide sections that are referenced in the Nodal Protocols as well as eliminating conflicts and redundancies between the Nodal Operating Guides and Nodal Protocols.  
 This NOGRR also proposes non-substantive administrative changes, such as correcting acronym and defined term usage.  These are shown below with the author ""ERCOT Market Rules.""",05/10/2010,NOGRRTF,No,"1.1, 1.2, 1.4, 1.5.1, 1.5.3",Approved,10/01/2010,""

One or more values in the row have been incorrectly quoted. E.g. a comma has not been escaped, or a quoted field has not been properly escaped
Check the values in the column and ensure that quoting has been correctly applied.

Structural problem: Stray quote on row 42

NOGRR041,Synchronization of Section 2 with Nodal Protocols,"This Nodal Operating Guide Revision Request (NOGRR) aligns the Nodal Operating Guides with the Nodal Protocols by adding additional detail to Nodal Operating Guide sections that are referenced in the Nodal Protocols as well as eliminating conflicts and redundancies between the Nodal Operating Guides and Nodal Protocols.  
 This NOGRR also proposes non-substantive administrative changes, such as correcting acronym and defined term usage.  These are shown below with the author ""ERCOT Market Rules.""",05/27/2010,NOGRRTF,No,"2.1, 2.2.1, 2.2.2, 2.2.3, 2.2.4, 2.2.5, 2.2.7, 2.2.8, 2.3, 2.3.1, 2.3.1.1, 2.3.1.2, 2.3.2, 2.3.2.1, 2.3.3, 2.5, 2.5.1, 2.6.2, 2.7.1, 2.7.2, 2.7.3, 2.7.4.1, 2.7.4.3, 2.8, 2.8.1",Approved,11/01/2010,""

One or more values in the row have been incorrectly quoted. E.g. a comma has not been escaped, or a quoted field has not been properly escaped
Check the values in the column and ensure that quoting has been correctly applied.

Structural problem: Stray quote on row 43

NOGRR042,Synchronization of Section 3 with Nodal Protocols,"This Nodal Operating Guide Revision Request (NOGRR) aligns the Nodal Operating Guides with the Nodal Protocols by adding additional detail to Nodal Operating Guide sections that are referenced in the Nodal Protocols as well as eliminating conflicts and redundancies between the Nodal Operating Guides and Nodal Protocols.  
 This NOGRR also proposes non-substantive administrative changes, such as correcting acronym and defined term usage.  These are shown below with the author ""ERCOT Market Rules.""",05/27/2010,NOGRRTF,No,"3.2, 3.2.1, 3.2.2, 3.2.4, 3.3.1, 3.3.2.2, 3.3.2.3, 3.4, 3.5, 3.6, 3.7, 3.8, 3.9, 3.9.1, 3.9.2, 3.9.3, 3.9.4, 9.3.6",Approved,11/01/2010,""

One or more values in the row have been incorrectly quoted. E.g. a comma has not been escaped, or a quoted field has not been properly escaped
Check the values in the column and ensure that quoting has been correctly applied.

Structural problem: Stray quote on row 44

NOGRR043,"Synchronization with OGRR208,Voltage Ride-Through (VRT) Requirement","This Nodal Operating Guide Revision Request (NOGRR) relocates generator voltage requirements from Section 6, Disturbance Monitoring and System Protection, to Section 2, System Operation and Control Requirements, and establishes Voltage Ride-Through (VRT) requirements for Wind Generation Resources (WGRs) to synchronize with the zonal Operating Guides. 
 Clarifications to Resource Entity responsibilities regarding reactive capability and communication of changes have also been made.",06/04/2010,Warren Lasher,No,"2.9, Voltage Ride-Through Requirements (new) 2.9.1, Additional Voltage Ride-Through Requirements for Wind Generation Resources (new) 3.3, Resource Entities 6.2.5.3.6, Automatic Under-Voltage Load Shedding (UVLS) Protection Systems",Approved,11/01/2010,""

One or more values in the row have been incorrectly quoted. E.g. a comma has not been escaped, or a quoted field has not been properly escaped
Check the values in the column and ensure that quoting has been correctly applied.

Structural problem: Stray quote on row 47

NOGRR046,Synchronization of Sections 4 and 5 with Nodal Protocols,"This Nodal Operating Guide Revision Request (NOGRR) aligns the Nodal Operating Guides with the Nodal Protocols by adding additional detail to Nodal Operating Guide sections that are referenced in the Nodal Protocols as well as eliminating conflicts and redundancies between the Nodal Operating Guides and Nodal Protocols.
This NOGRR also proposes non-substantive administrative changes, such as correcting acronym and defined term usage.  These are shown with the author ""ERCOT Market Rules.""",06/11/2010,NOGRRTF,No,"4.1, 4.2, 4.2.3, 4.2.4, 4.3, 4.3.1, 4.5.1, 4.5.3, 4.5.3.2, 4.5.3.3, 4.5.3.4, 5.1.1, 5.1.2, 5.1.3, 5.2, 5.5, 5.5, 5.5.1",Approved,11/01/2010,""

One or more values in the row have been incorrectly quoted. E.g. a comma has not been escaped, or a quoted field has not been properly escaped
Check the values in the column and ensure that quoting has been correctly applied.

Structural problem: Stray quote on row 77

NOGRR076,Synchronization with NPRR298 and New Format for Black Start Plans,"This Nodal Operating Guide Revision Request (NOGRR):
 ·        Synchronizes the Nodal Operating Guides with Nodal Protocol Revision Request (NPRR) 298, New Definitions Related to Black Start and Clarification to the Hourly Standby Fee Payments for Black Start Resources (formerly ""New Definitions Related to Black Start""), which introduced new black start terminology and corrected the acronym related to the Hourly Standby Fee Payment.  NPRR298 was approved by the ERCOT Board on April 19, 2011.
·        Introduces new black start terminology to the Nodal Operating Guides; 
·        Creates a requirement for all Transmission Operators (TOs) to submit their Black Start Plans to ERCOT by November 1 of each year; andIntroduces a template for Black Start Plans to the Nodal Operating Guides.",07/05/2011,Black Start Working Group (BSWG),No,"1.4, 1.5.1, 2.3, 4.3, 4.5.2, 4.6, 4.6.1, 4.6.2, 4.6.3, 4.6.4, 4.6.5, 8A, 8E (new)",Approved,12/14/2011,""

One or more values in the row have been incorrectly quoted. E.g. a comma has not been escaped, or a quoted field has not been properly escaped
Check the values in the column and ensure that quoting has been correctly applied.

Structural problem: Stray quote on row 103

NOGRR102,"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.",07/31/2012,ERCOT,No,"1.3.1, 1.3.4.5, 1.3.4.8, 1.3.4.10, and 1.3.4.11",Approved,12/01/2012,""

One or more values in the row have been incorrectly quoted. E.g. a comma has not been escaped, or a quoted field has not been properly escaped
Check the values in the column and ensure that quoting has been correctly applied.

Structural problem: Stray quote on row 111

NOGRR110,"Synchronization with NPRR529, Congestion Management Plan","This Nodal Operating Guide Revision Request (NOGRR) synchronizes the Nodal Operating Guide with revisions proposed by NPRR529, Congestion Management Plan and also:
·        Moves language related to Special Protection Systems (SPSs) and Remedial Action Plans (RAPs) to new Section 11.
·        Formalizes two existing Congestion Management Plans (CMPs), Transmission Outage Action Plans (TOAPs) and Pre-Contingency Action Plans (PCAPs).
·        Eliminates the distinction between Type I and Type II SPSs.·       Institutes a stakeholder comment process for RAPs that are proposed by Market Participants to provide for input from other Market Participants into ERCOT’s approval process for these Market Participant-proposed RAPs.",03/06/2013,ERCOT,No,"2.5.1, 3.7.2, 4.3.1, 4.3.2, 6.2.2, 11 (new section)",Approved,02/01/2014,""

One or more values in the row have been incorrectly quoted. E.g. a comma has not been escaped, or a quoted field has not been properly escaped
Check the values in the column and ensure that quoting has been correctly applied.

Structural problem: Stray quote on row 136

NOGRR135,Constraint Management During Energy Emergency Alert,"This Nodal Operating Guide Revision Request (NOGRR) seeks to improve management of congestion during an Energy Emergency Alert (EEA) by proposing: 
1. Language that provides a mechanism for ERCOT Operations to manage constraints in EEA 2 or 3 to higher Facility ratings when applicable for those constraints identified as limiting generation output; and
2. Language that reconsiders use of double-circuit contingencies during emergency operations based on Grid conditions",07/23/2014,ERCOT,No,"4.2.3, 4.5.2, 4.5.3, 4.5.3.1",Approved,05/01/2015,""

One or more values in the row have been incorrectly quoted. E.g. a comma has not been escaped, or a quoted field has not been properly escaped
Check the values in the column and ensure that quoting has been correctly applied.

Structural problem: Stray quote on row 139

NOGRR138,Delete Grey Box for Reporting of Back-up Control Plan Submittal,"This Nodal Operating Guide Revision Request (NOGRR) proposes the discontinuation of the posting requirement for Discontinue Backup Control Plan Submittal Results, ERCOT Market Information List (EMIL) ID, NP8-510M and Backup Control Plan Test Dates and Results Summary Reports, EMIL ID NP8-922-M.  
 
This NOGRR is part of a series of revision requests submitted by the Market Information System User Group (MISUG) in support of the TAC June 2013 recommendation that all manually developed ERCOT market reports be reviewed for market interest and the amount of labor involved to produce the reports.  This NOGRR is the result of a collaborative effort between the MISUG and ERCOT to review the reports that are manually produced by ERCOT.",09/24/2014,MIS User Group,No,9.3.6,Approved,09/25/2015,""

One or more values in the row have been incorrectly quoted. E.g. a comma has not been escaped, or a quoted field has not been properly escaped
Check the values in the column and ensure that quoting has been correctly applied.

Structural problem: Stray quote on row 155

NOGRR153,Maintenance of Duplicate EEA Language via Alignment NOGRR Process,"This Nodal Operating Guide Revision Request (NOGRR) creates a new process for maintaining alignment of the Energy Emergency Alert (EEA) language between the Protocols and Nodal Operating Guides via ���Alignment NOGRRs���.

This NOGRR is in response to the 5/28/15 Technical Advisory Committee (TAC) decision that EEA language be maintained in both the Protocols and Nodal Operating Guides; and that a process be developed to ensure consistency.",01/27/2016,ERCOT,No,1.3.1 and 1.3.6,Approved,05/01/2016,""

One or more values in the row have been incorrectly quoted. E.g. a comma has not been escaped, or a quoted field has not been properly escaped
Check the values in the column and ensure that quoting has been correctly applied.

Structural problem: Stray quote on row 161

NOGRR159,"Alignment with NPRR779, Clarifies References to Texas Reliability Entity and Independent Market Monitor","This Nodal Operating Guide Revision Request (NOGRR) clarifies references to the Texas Reliability Entity (Texas RE) and the Independent Market Monitor (IMM).  The Nodal Operating Guide currently refers to the Texas RE in both its capacity as the North American Electric Reliability Corporation (NERC) Regional Entity and the Public Utility Commission of Texas (PUCT) Reliability Monitor, a new term recently added to P.U.C. SUBST. R. �� 25.503, Oversight of Wholesale Market Participants.

This NOGRR modifies uses of the term ���Texas Reliability Entity��� to more accurately reflect distinct references to the NERC Regional Entity and the PUCT Reliability Monitor, and clarifies that the IMM is an included party in several provisions related to the ERCOT stakeholder process.",05/27/2016,ERCOT,No,"1.3.1, 1.3.2, 1.3.3, 1.3.4.3, 1.3.4.4, 1.3.4.12, 1.5.4, 2.7.4.1, 6.2.3, Section 8, Attachment A, 9.1.8, 9.3.1, 11.2.1",Approved,11/01/2016,""

One or more values in the row have been incorrectly quoted. E.g. a comma has not been escaped, or a quoted field has not been properly escaped
Check the values in the column and ensure that quoting has been correctly applied.

Structural problem: Stray quote on row 170

NOGRR168,Nodal Operating Guide Revision Request Process,"This Nodal Operating Guide Revision Request (NOGRR) refines the process for revising the Nodal Operating Guide so that NOGRRs are originally considered at the voting Subcommittee level and expands the list of NOGRRs requiring ERCOT Board approval.

These process changes were discussed at the 8/25/16 TAC/TAC Subcommittee Structural and Procedural Review, the 9/29/16 TAC meeting, and the 10/10/16 HR & Governance Committee meeting.",01/30/2017,ERCOT,No,"1.3.1, 1.3.3, 1.3.4, 1.3.4.1, 1.3.4.2, 1.3.4.3, 1.3.4.4, 1.3.4.5, 1.3.4.6, 1.3.4.7, 1.3.4.8, 1.3.4.9, 1.3.4.10, 1.3.4.11, 1.3.4.12, 1.3.5, and 1.3.6",Approved,06/01/2017,""

One or more values in the row have been incorrectly quoted. E.g. a comma has not been escaped, or a quoted field has not been properly escaped
Check the values in the column and ensure that quoting has been correctly applied.

Structural problem: Stray quote on row 172

NOGRR170,"Alignment with NPRR824, Alignment of EEA Level 3 with NERC Reliability Standards EOP-011-1 and BAL-001-2","This Nodal Operating Guide Revision Request (NOGRR) revises the Nodal Operating Guide (NOG) to be consistent with NPRR824 language relating to North American Reliability Corporation (NERC) Reliability Standards EOP-011-1, Emergency Operations, and BAL-001-2, Real Power Balancing Control Performance.  
Pursuant to paragraph (5) of Section 1.3.1, Introduction, this NOGRR does not modify Section 4.5.3.3, EEA Levels.  An Alignment NOGRR will be posted upon ERCOT Board approval of NPRR824 to maintain alignment of Protocol Section 6.5.9.4.2, EEA Levels, with NOG Section 4.5.3.3.",03/29/2017,ERCOT,No,4.5.3 and 4.5.3.1,Approved,07/01/2017,""

One or more values in the row have been incorrectly quoted. E.g. a comma has not been escaped, or a quoted field has not been properly escaped
Check the values in the column and ensure that quoting has been correctly applied.

Dialect: Non standard dialect

Although your CSV validates, to make it as easy as possible for your data to be reused, we recommend using commas as delimiters, double quotes to enclose fields, and autodetecting line endings.

Context problem: No encoding

The encoding of your CSV file is not being declared in the HTTP response.
We recommend that you configure your server to deliver CSV files with a Content-Type header of text/csv; charset=utf-8
If you are using a different encoding, then use an appropriate value for the charset parameter.

Context problem: Incorrect Encoding

Your CSV appears to be encoded in ASCII-8BIT. We recommend you use UTF-8.

Structural problem: Non-standard Line Breaks on row 1

Your CSV appears to use LF line-breaks. While this will be fine in most cases, RFC 4180 specifies that CSV files should use CR-LF (a carriage-return and line-feed pair, e.g. \r\n). This may be labelled as "Windows line endings" on some systems.

Next Steps

Publish and transform your data using DataGraft, either as enhanced CSV or Linked Data.