Topic/Matter Intersection

Topic:"Interpretation Of Legislation" in M03324

Matter: E-NERC-R-10 - North American Electric Reliability Corporation - Reliability Standards; and Northeast Power Coordinating Council, Inc. - Regional Reliability Criteria
15 passages 4 documents

Interpretation Of Legislation across all matters →

N-5Notice of Filing of the NERC Reliability Standard Processes Manual Incorporating Proposed Revisions to the Reliability Standards Development Process 6/29/2010 1 passage
Interpretations
Interpretations The interpretation process was revised to include a quality review, followed by a formal 45-day comment period conducted at the same time as the ballot . If an interpretation identifies the need to revise a standard for cla...

AI summary The interpretation process now includes a quality review and a 45-day comment period. Revisions to standards may require submitting a SAR if clarity issues or reliability gaps are identified. Interpretation teams may also decline to develop interpretations when necessary.

N-10Reliability Standards of the North American Electric Reliability Corporation 7/5/2010 8 passages
F. Associated Documents p. p. 117
F. Associated Documents 1. Appendix 2 – Interpretation of Requirement R1 (October 23, 2007).

AI summary The document references Appendix 2, which provides an interpretation of Requirement R1 dated October 23, 2007. This appendix is part of the regulatory proceeding's associated documents and pertains to clarifying specific compliance requirements.

Interpretation of Requirement 1 p. p. 117
Interpretation of Requirement 1 Request: Does the WECC Automatic Time Error Control Procedure (WATEC) violate Requirement 1 of BAL-001-0?

AI summary The document raises a question about whether the WECC Automatic Time Error Control Procedure (WATEC) violates Requirement 1 of BAL-001-0, a standard related to system reliability and time synchronization in the electricity sector.

F. Associated Documents p. p. 136
F. Associated Documents - 1. Appendix 1 Interpretation of Requirement R3 (October 23, 2007). - 2. Appendix 2 Interpretation of Requirements R2, R2.2, R5, and R5.1 (February 12, 2008).

AI summary The section lists two appendices providing interpretations of regulatory requirements dated October 2007 and February 2008. These documents outline clarifications for requirements R3, R2, R2.2, R5, and R5.1, though no specific claims or entities are mentioned in the text.

Interpretation of Requirement 3 p. p. 136
Interpretation of Requirement 3 Request: Does the WECC Automatic Time Error Control Procedure (WATEC) violate Requirement 3 of BAL-003-0?

AI summary The document asks whether the WECC Automatic Time Error Control Procedure (WATEC) violates Requirement 3 of BAL-003-0, focusing on regulatory compliance and system reliability standards.

Interpretation of Requirements R2, R2.2, R5, R5.1 p. p. 136
Interpretation of Requirements R2, R2.2, R5, R5.1 Request: ERCOT specifically requests clarification that a Balancing Authority is entitled to use a variable bias value as authorized by Requirement R2.2, even though Requirement 5 seems not...

AI summary ERCOT seeks clarification on whether a Balancing Authority can use variable bias values under R2.2, despite R5 not addressing variable bias settings, highlighting a potential conflict between regulatory requirements.

Request for Interpretation of TPL-002-0 and TPL-003-0 Requirement R1.3.12 Received from MISO on August 9, 2007: p. p. 171
Request for Interpretation of TPL-002-0 and TPL-003-0 Requirement R1.3.12 Received from MISO on August 9, 2007: MISO asks if the term "planned outages" means only already known/scheduled planned outages that may continue into the planning...

AI summary MISO requests clarification on whether 'planned outages' in TPL-002-0 and TPL-003-0 R1.3.12 include unscheduled potential outages or only known/scheduled ones. It also asks if system planning must account for Category C3 n-2 events even if the initial event is a planned base condition, and whether this aligns with NERC's original interpretation.

F. Associated Documents p. p. 171
F. Associated Documents 1. Appendix 1 – Interpretation of Requirements R1 and R2 (August 1, 2007).

AI summary The document references Appendix 1, which provides an interpretation of Requirements R1 and R2 dated August 1, 2007. No further details about the content or implications of these requirements are included in the excerpt.

Interpretation of Requirements R1 and R2 p. p. 171
Interpretation of Requirements R1 and R2

AI summary The document focuses on interpreting regulatory requirements R1 and R2, likely within the context of compliance with reliability standards or legal frameworks. Specific details are not provided in the text, but the heading suggests a discussion around clarifying obligations or definitions under these requirements.

06641Notice of Filing of Informational Filing of the North American Electric Reliability Corporation 3/23/2011 1 passage
G. Critical Infrastructure Protection p. p. 63
e standard drafting team to resolve any industry comments received during this markup process and support the CIPC in completing the guideline development and approval process. See item G.2.a. above. - 3. Need for Technical Feasibility Exc...

AI summary The text discusses the finalization of the Technical Feasibility Exception (TFE) procedure for NERC CIP standards, its approval by NERC and FERC, and the use of Compliance and Enforcement Notices (CAN) to address CIP compliance issues. It also suggests a hotline for CIP reliability standards questions, citing the CAN process as more efficient than formal interpretations.

07810Quarterly Application for Approval of Reliability Standards of the North American Electric Reliability Corporation - September 2, 2011 9/6/2011 5 passages
F. Associated Documents p. p. 192
F. Associated Documents 1 . Appendix 1 – Interpretation of Requirements R1.2 and R3

AI summary The document references Appendix 1, which provides an interpretation of Requirements R1.2 and R3. These requirements are part of regulatory standards governing reliability and operations in the electricity sector, though specific details of their interpretation are not elaborated in this excerpt.

Question 1 p. p. 192
Question 1 Does the phrase, "as specified" in Requirement R3 reference the documented data and information specification in IRO-010-1 Requirement R1, or is the data and information in Requirement R3 "any" data and information that the Reli...

AI summary The response clarifies that Requirement R3's data refers to the documented specification in IRO-010-1 Requirement R1, not arbitrary data requested by the Reliability Coordinator.

Version History p. p. 17
Version History Version Date Action Change Tracking 1a Board approved 11/05/2009 Interpretation of R2 and R8 Interpretation (Project 2009-15) Appendix 1

AI summary This document provides a version history of a regulatory proceeding, including the approval date and action taken by the Board on 11/05/2009, related to the interpretation of R2 and R8 under Project 2009-15.

F. Associated Documents p. p. 145
F. Associated Documents 1. Appendix 1 – Interpretation of Requirements R1 and R2 (August 1, 2007).

AI summary The document references Appendix 1, which provides an interpretation of Requirements R1 and R2 dated August 1, 2007. This appendix is part of the associated documents in the regulatory proceeding.

Interpretation of Requirements R1 and R2 p. p. 145
Interpretation of Requirements R1 and R2

AI summary The document addresses the interpretation of regulatory requirements R1 and R2, likely within the context of compliance with electric reliability standards or utility regulations in Nova Scotia. Key focus areas may include definitions, applicability, and enforcement mechanisms for these requirements.

Disclaimer: These summaries were generated by AI from the filings they describe. We take care to make them accurate, but errors are possible - and they aren't advice. Only the filings themselves are the record: if you're relying on something here, confirm it against the source documents or the Nova Scotia Energy Board's own record. Full disclaimer →