Topic:"Regulatory Compliance" in M03324

Section 2 — Composition of Board Based on Country Participation - a. The board shall consist of a number of trustees from the United States and from Canada. The number of trustees from Canada shall not be less than the percentage of the NE...

AI summary Section 2 establishes a board composition formula based on the net energy for load (NEL) percentages of Canada and the United States, ensuring Canadian representation proportional to their NEL share. It also outlines a future expansion to include Mexico if recognized as an electric reliability organization by Mexican regulatory authorities.

ARTICLE II Membership Section 1 — Members — Membership in the Corporation is voluntary and is open to any person or entity that has an interest in the reliable operation of the North American bulk power system and that registers with the C...

AI summary This section outlines the membership requirements for the Corporation, including voluntary registration, eligibility criteria, and procedures for maintaining and renewing membership. It also describes the responsibilities of the secretary in managing the member roster and handling removals for non-renewal.

Section 3 — Obligations and Conditions of Membership - a. Each member shall agree, in writing, to accept the responsibility to promote, support, and comply with the purposes and policies of the Corporation as set forth in its Certificate o...

AI summary Section 3 outlines membership obligations, requiring members to support the Corporation's policies and execute a liability waiver agreement, shielding the Corporation from damages caused by its agents, except in cases of gross negligence or intentional misconduct.

rm of Membership — Membership in the Corporation shall be retained as long as a member meets its respective qualifications, obligations, and conditions of membership as set forth in this Article II. Section 6 — Removal — In addition to ter...

AI summary The section outlines membership retention requirements and termination procedures. Membership is retained if qualifications are met, while the board may terminate membership for violations via a two-thirds vote, with an appeal right to the Commission or relevant Canadian/Mexican authority.

the areas of technical electric operations and reliability, legal, market, financial, and regulatory matters, and familiarity with regional system operation issues; and reflects geographic diversity.

AI summary The text outlines criteria for Board composition, emphasizing expertise in technical electric operations, reliability, legal, market, financial, and regulatory matters, along with regional system operation knowledge and geographic diversity.

the results shall be posted on the Corporation's Web site, within ten (10) days of the action vote, and all written responses of the members shall be filed with the minutes of proceedings of members. Section 5 ¾ Meetings of the Members to...

AI summary The Corporation must post meeting results online within 10 days of a vote and file member responses with meeting minutes. Meetings must be publicly accessible, with non-confidential materials posted within 24 hours, though closed sessions may occur for sensitive topics like personnel, litigation, or commercial data.

ARTICLE IX Reliability Standards Section 1 ¾ Development of Reliability Standards ¾ The Corporation shall develop, implement and, in all regions in which necessary governmental approvals have been obtained or authority has been provided, e...

AI summary The Corporation must develop and enforce reliability standards for North American bulk power systems, approved by the board and made publicly available. Standards must be created through transparent processes with public input. Violations trigger sanctions via procedures allowing hearings, with penalties proportional to severity and considering remediation efforts.

REDLINED VERSION OF NERC BYLAWS MARKED TO SHOW AMENDMENTS

AI summary This document presents a redlined version of NERC bylaws with amendments, highlighting changes to governance structures and compliance processes. Key entities involved include NERC, FERC, MRC, and BOTCC, with discussions centered on regulatory compliance, oversight, and rule-making under NERC's framework.

ARTICLE IX Reliability Standards Section 1 ¾ Development of Reliability Standards ¾ The Corporation shall develop, implement and, in all regions in which necessary governmental approvals have been obtained or authority has been provided, e...

AI summary The Corporation must develop and enforce reliability standards for North American bulk power systems, approved by the board and made publicly available. Standards must be created through transparent processes with public input. Violations trigger sanctions via procedures allowing hearings, with penalties proportional to severity and considering remediation efforts.

schedule. These combined activities have resulted in an approximate nine month extension to the project. The anticipated completion date of the project is now scheduled for the third quarter of 2012. 2008-02 Undervoltage Load Shedding. No...

AI summary The project timeline has been extended by nine months, with completion now in Q3 2012. The 2008-02 project timeline remains unchanged. The 2008-06 Cyber Security project, initiated under FERC Order 706, involves multiple phases of revising CIP Reliability Standards, with FERC approving Version 2 in September 2009 and directing further modifications.

I. INTRODUCTION The North American Electric Reliability Corporation ("NERC") respectfully provides notice of the following documents: - Revised pro forma Delegation Agreement with Regional Entities ( Attachment 1 to this filing) - Revised...

AI summary NERC notifies revisions to Delegation Agreements with Regional Entities and updates to NERC Rules of Procedure (ROP), including changes to multiple sections and appendices. The filings were submitted to FERC and Canadian authorities, with specific revisions detailed in attachments.

pro forma Delegation Agreement, and the remaining provisions were viewed to be no longer necessary, particularly in light of the agreement that all Regional Entities will adopt the NERC uniform CMEP. Section 7, Delegation-Related Activitie...

AI summary The document revises Section 7 of the Base Delegation Agreement, expanding the Regional Entity's statutory activities to include certification of Bulk-Power System entities, registration of owners/operators, and compliance monitoring. It emphasizes NERC's role in setting criteria for certification and registration, with Regional Entities adopting NERC's uniform CMEP.

b. Exhibit A to Delegation Agreement Exhibit A to the Delegation Agreements sets forth the Regional Entity's geographic boundaries and any additions to or exclusions from the geographic or electrical boundaries within which the Regional En...

AI summary Exhibit A to the Delegation Agreement defines the Regional Entity's geographic and electrical boundaries for delegated functions. A new instruction requires all exclusions or additions to these boundaries—whether geographic, electrical, or involving Registered Entities—to be explicitly described in Exhibit A, emphasizing specificity in scope definitions.

d. Exhibit C to Delegation Agreement In the revised pro forma Delegation Agreement, there is only one change to the 34 Common Attributes of an acceptable Regional Entity Reliability Standards Development Procedure ("RSDP") which the Region...

AI summary Exhibit C to the Delegation Agreement revises Common Attribute 34 by removing 'Violation Severity Levels' from the Regional Entity's RSDP, aligning with NERC's updated RSDP framework approved by FERC. This change shifts compliance elements like severity levels to separate development processes, no longer integrated into RSDP standards.

e. Exhibit D to the Delegation Agreement Section 1.0 of Exhibit D has been revised to state that the Regional Entity will implement the NERC CMEP, Appendix 4C to the NERC ROP. All Regional Entities have agreed to implement the NERC CMEP. 8...

AI summary Exhibit D's Section 1.0 was revised to require Regional Entities to implement NERC's CMEP and Appendix 4C to the NERC ROP. All Regional Entities agreed to adopt the NERC CMEP, except for one deviation in the WECC CMEP. The revision clarifies that NERC CMEP excludes uniform Hearing Procedures, which are addressed separately in Section 2.0. Section 3.0 remains unchanged, requiring identification of other compliance decision-making bodies.

f. Exhibit E to the Delegation Agreement Exhibit E, Funding, has been considerably expanded in the revised pro forma Delegation Agreement, and some provisions have been moved to Exhibit E from the body of the Delegation Agreement. In Secti...

AI summary Exhibit E to the Delegation Agreement has been expanded, detailing funded activities such as Event Analysis and Reliability Improvement, while removing Reliability Readiness Evaluation and Improvement. Budgeting provisions for the Regional Entity's business plan and reserve mechanisms are emphasized, with NERC ROP references omitted for budgeting purposes.

, along with the structure of the Hearing Body, fully supports the requirement that no two stakeholder sectors may control, and no single stakeholder sector may veto, a matter before the Hearing Body. The above-described provisions of §2.0...

AI summary The revised NPCC Delegation Agreement outlines stakeholder governance rules for the Hearing Body and details NPCC Compliance Staff's role in reviewing compliance submittals, issuing NOPVs/NOCVs, and aligning with NERC's CMEP. The process emphasizes non-veto power for any single sector and integration of uniform enforcement standards.

1. Amendments to Section 200 – Definitions The definition of "Confirmed Violation" has been amended to include a violation that the entity has admitted to in a settlement agreement. In addition, a reference to the "appeals process" has bee...

AI summary The definition of 'Confirmed Violation' now includes admissions via settlement agreements, and the 'appeals process' reference was updated to 'hearings and appeals process.' These changes align with amendments in Appendix 4C, §1.1.9.

2. Amendments to Section 400 – Compliance Enforcement Two recurring reasons for amendments in §400 are: (1) to adopt new or revised terminology adopted in amended Appendix 4C, such as the terms "possible violation," "alleged 12 Article XI,...

AI summary Amendments to Section 400 focus on aligning terminology with Appendix 4C (e.g., 'possible violation,' 'confirmed violation') and removing redundant text to avoid confusion. This follows NERC Bylaws requiring public comment on ROP amendments before approval by the NERC Board of Trustees.

3. Amendments to Section 500 – Organization Registration and Certification Throughout §500, references to Appendix 5, the NERC Organization Registration and Certification Manual , have been changed to Appendix 5A to reflect the renumbering...

AI summary Amendments to Section 500 renumber Appendix 5 to 5A, remove a list of Registered Entity types to avoid frequent updates, and require bulk power system owners to provide timely updates to NERC and regional entities. Section 501.1.2 now references the NERC Statement of Compliance Registry Criteria (Appendix 5B) instead of listing criteria directly, avoiding duplication.

4. Amendments to Section 800 – Reliability Assessment and Performance Analysis The amendments to §800 are in §807 and §808. Section 807, Analysis of Major Events, has been amended to add a new subsection (c) (with the subsequent subsection...

AI summary Amendments to Sections 807 and 808 of §800 clarify NERC's and regional entities' authority to request information from bulk power system stakeholders. This enables them to analyze major and off-normal events, assess vulnerabilities, and develop lessons learned.

eparing annual budgets for governmental approvals for 2007, 2008, 2009 and 2010, has found to be appropriate for, and desired by the governmental authorities to be provided in, the budget submissions: The NERC annual budget submittal to ER...

AI summary The text outlines requirements for NERC's annual budget submissions to ERO governmental authorities, including justification for program activities, alignment with statutory authorities, resource sufficiency, calculation methods, staffing details, and compliance with FERC and other regulatory bodies. Emphasis is placed on affordability, sustainability, efficiency, transparency, and accountability.

-delegated to another regional entity. Regional entities may share resources with one another so long as such arrangements do not result in cross-subsidization or in any sub-delegation of authorities. Section 1207, Regional Entity Audits....

AI summary Amendments to Section 1207 extend NERC audits of Regional Entities from every three to five years, aligning with five-year Delegation Agreements and reducing redundant audits. Audits must follow U.S. and international standards, avoiding duplication with existing compliance audits.

tion related to other jurisdictions. - Compliance staff from other Regional Entities may participate as observers, with consent of NERC and the compliance manager of the Regional Entity being audited. The requirements in current Appendix 4...

AI summary Amendments to Appendix 4A of NERC Rules of Procedure remove requirements for CCC and other Regional Entity compliance staff on audit teams, designate NERC staff as ATL, and introduce 60-day pre-audit notifications, 30-day questionnaires, and optional planning conferences for audit coordination.

D. Amendments to Appendix 4B to the NERC Rules of Procedure The amendments to Appendix 4B, Sanction Guidelines of the North American Electric Reliability Corporation , are largely for the purpose of consistency with other provisions of the...

AI summary Amendments to Appendix 4B of the NERC Rules of Procedure aim to align terminology and cross-references with other NERC documents, ensuring consistency without altering penalty determination methods. Key changes include updating terms like 'possible violation' and removing references to regional entity-specific procedures in favor of NERC's uniform CMEP.

ossible Violation (§1.1.19), Possible Violation (§1.1.21), and Preliminary Screen (§1.1.22): 15 Section numbers cited in this discussion are the section numbers in the amended Appendix 4C.

AI summary The text references Possible Violation sections (§1.1.19, §1.1.21) and a Preliminary Screen (§1.1.22), with a footnote indicating these sections are from the amended Appendix 4C. No further details about violations or screening criteria are provided in the excerpt.

2. Section 2.0 – Identification of Organizations Responsible for Complying with Reliability Standards The revisions to the first five paragraphs of §2.0 reflect the revised roles of NERC and the Regional Entities in registering entities an...

AI summary Revisions to Section 2.0 clarify NERC's expanded role in maintaining a consolidated Compliance Registry for the Bulk Power System, replacing regional registries. Regional Entities now provide data for registration decisions, and Registered Entities must notify NERC of changes. NERC will also list applicable Reliability Standards and report to FERC monthly.

deleted from this subsection and is addressed in the next subsection (§3.1.4.2). New §3.1.4.2, Period Covered, addresses the time period to be covered in a Compliance Audit, and specifies as follows: The Registered Entity's data and inform...

AI summary Section 3.1.4.2 defines the period for Compliance Audits, starting after the prior audit or June 18, 2007, and ending with the audit's stated end date. Exceptions apply if other compliance processes occur, and entities must demonstrate compliance despite document retention period limitations.

b. Section 3.2 – Self-Certification Section 3.2 has been revised, consistent with the new progression of steps in the compliance enforcement process in amended Appendix 4C, to specify that "If the Compliance Enforcement Authority concludes...

AI summary Section 3.2 was revised to align with updated compliance enforcement steps in Appendix 4C, requiring the Compliance Enforcement Authority to issue a Notice of Possible Violation after Preliminary Screens. A redundant provision about Regional Entities notifying NERC was deleted, as Section 8.0 already covers reporting requirements.

d. Section 3.4 – Compliance Investigations Revisions have been made throughout §3.4 to reflect that the name of this compliance monitoring process has been changed from "Compliance Violation Investigation" to "Compliance Investigation," as...

AI summary Section 3.4 on Compliance Investigations has been revised to rename the process from 'Compliance Violation Investigation' to 'Compliance Investigation,' clarify terminology like 'potential noncompliance,' and adjust procedural steps. Key changes include reordering steps to reflect typical on-site visits after data submission and expanding requirements for Registered Entities to provide sworn verification or testimony. FERC's 2007 order is cited for procedural alignment.

e. Section 3.5 – Self Reporting The final process step for Self-Reporting in §3.5.1 has been revised, consistent with the new progression of steps in the compliance enforcement process in amended Appendix 4C, to specify that "If the Compli...

AI summary Section 3.5's self-reporting process was revised to align with amended Appendix 4C, specifying that a Notice of Possible Violation must be issued after a Preliminary Screen. A redundant step requiring Regional Entities to notify NERC of Alleged Violations was removed, as §8.0 already covers reporting requirements.

f. Section 3.6 – Periodic Data Submittals The fifth process step for Periodic Data Submittals in §3.6.1 has been revised to state that if the Compliance Enforcement Authority's assessment, based on the Periodic Data Submittal, of the Regis...

AI summary Revisions to Section 3.6's Periodic Data Submittals process now allow Registered Entities to comment on assessments indicating Possible Violations before finalization. Steps notifying entities of assessment completion and redundant NERC notification requirements were deleted. Final steps align with amended Appendix 4C, specifying Notice of Possible Violation issuance after Preliminary Screens.

h. Section 3.8 Complaints The initial paragraph of §3.8 has been revised to state that a Complaint received by a Regional Entity will be reviewed to determine if the Complaint provides sufficient basis for initiating another Compliance Mon...

AI summary Revisions to Section 3.8 clarify that complaints trigger a Compliance Monitoring and Enforcement process, not a Compliance Violation Investigation. References to Section 3.4 were updated to Section 3.0, and terms like 'possible violation' were replaced to avoid confusion with defined terms.

5. Section 5.0 – Enforcement Actions 17 Section 5.0 has been extensively revised to present the revised, standardized progression of steps for processing evidence of a potential noncompliance discovered by the Compliance Enforcement Author...

AI summary Section 5.0 outlines revised standardized steps for processing potential noncompliance evidence by the Compliance Enforcement Authority (NERC or Regional Entities). The process includes a Preliminary Screen and issuing a Notice of Possible Violation, aiming to ensure consistent terminology and clear procedures for Registered Entities.

a. Section 6.1 – Requirement for Submission of Mitigation Plans Section 6.1 has been revised to specify that in addition to being required to submit a Mitigation Plan upon being found in violation of a Reliability Standard, a Registered En...

AI summary Section 6.1 has been revised to allow Registered Entities to submit Mitigation Plans at any time, including with a Self-Report or in response to a Notice of Possible Violation. Appendix 4C updates disclosure prohibitions and references to NERC's director of enforcement.

b. Section 6.2 – Contents of Mitigation Plans Section 6.2 has been revised to incorporate use of the terms "Possible Violation," "Alleged Violation," and "Confirmed Violation, and to use other defined terms. In addition, a provision has be...

AI summary Section 6.2 has been revised to define terms like 'Possible Violation,' 'Alleged Violation,' and 'Confirmed Violation,' and mandates that mitigation plans include action plans to address both the causes and the violations themselves.

c. Section 6.3 – Timetable for Completion of Mitigation Plans Section 6.3 has been revised to specify that a Mitigation Plan "should encompass actions necessary to prevent a recurring violation of the Reliability Standard requirements unde...

AI summary Section 6.3 was revised to require Mitigation Plans to address actions preventing recurring violations of Reliability Standards linked to Possible, Alleged, or Confirmed Violations, ensuring compliance with reliability requirements.

d. Section 6.4 – Submission of Mitigation Plans Section 6.4 has been revised to specify that a Registered Entity may submit a Mitigation Plan in response to a Notice of Possible Violation, without being deemed to have admitted the violatio...

AI summary Section 6.4 was revised to permit Registered Entities to submit Mitigation Plans in response to a Notice of Possible Violation (NOPV) without admitting the violation or penalty. The section was also updated to ensure proper use of defined terms.

f. Section 6.6 – Completion/Confirmation of Implementation of Mitigation Plans In the second paragraph of §6.6, a reference to the Compliance Enforcement Authority verifying that the Registered Entity has completed its Mitigation Plan and...

AI summary Section 6.6 was revised to clarify that the Compliance Enforcement Authority verifies completion of Mitigation Plans aligned with specific Reliability Standard requirements, not just general standards. Mitigation Plans address violations of particular Reliability Standard requirements.

g. Section 6.7 Recordkeeping Section 6.7 has been revised to use the new defined terms Notice of Possible Violation and Notice of Alleged Violation.

AI summary Section 6.7 has been updated to incorporate new terminology: 'Notice of Possible Violation' (NOPV) and 'Notice of Alleged Violation' (NOAV), reflecting changes in regulatory compliance procedures.

8. Section 8.0 – Reporting and Disclosure Section 8.0 has been revised to provide that Regional Entities shall report all Possible Violations, Alleged Violations and Confirmed Violations to NERC by promptly entering the item into the NERC...

AI summary Section 8.0 has been revised to require Regional Entities to report Possible, Alleged, and Confirmed Violations to NERC via the NERC compliance reporting system. This eliminates the prior requirement to separately submit copies of notices within specific timeframes, as electronic entry into the system fulfills reporting obligations.

AUDIT OF REGIONAL ENTITY COMPLIANCE PROGRAMS

AI summary The audit examines compliance programs of regional entities within the electric reliability framework, focusing on adherence to standards and regulations governed by organizations like NERC, FERC, and various reliability coordinators.

COMPLIANCE MONITORING AND ENFORCEMENT PROGRAM

AI summary The document outlines the Compliance Monitoring and Enforcement Program (CMEP), detailing its role in ensuring adherence to reliability standards by electric reliability organizations (EROs) and regulatory bodies. It references key entities involved in compliance oversight and enforcement mechanisms.

STATEMENT OF COMPLIANCE REGISTRY CRITERIA

AI summary The document outlines criteria for a compliance registry, likely related to regulatory standards and procedures. It may involve entities such as reliability organizations, regulatory bodies, and compliance monitoring programs, though specific content is not detailed in the provided text.

IV. APPENDIX 5A TO THE NERC RULES OF PROCEDURE In the June 21 Filing, NERC proposed to re-label current Appendix 5 to the ROP as Appendix 5A, with no other changes to its text. This re-labeling was proposed due to the proposed addition of...

AI summary NERC proposed relabeling Appendix 5 of the ROP as 5A, but FERC approved designating the Organization Registration and Organization Certification Manual as Appendix 5A instead. This made NERC's original proposal moot, with FERC's May 2010 approval of Texas Reliability, Inc. as the Regional Entity also referenced.

AMENDED SECTION 500 OF THE NERC RULES OF PROCEDURE

AI summary This document outlines amendments to Section 500 of the NERC Rules of Procedure, involving regulatory oversight by FERC and other entities, focusing on compliance and procedural updates.

al coordination between the compliance staff and drafting teams during the development of standards. - The description of the Compliance and Certification Committee's responsibilities was added to reflect the role of the committee in asses...

AI summary The document outlines procedural changes to enhance coordination in reliability standards development, including revised roles for compliance staff, drafting teams, and the Compliance and Certification Committee. It removes the SAR Drafting Team role to avoid unnecessary delays and clarifies that all drafting teams report to the Standards Committee. The NAESB's role in coordinating standards impacting both reliability and business practices is emphasized.

b. NERC Compliance and Certification Committee Hearing Procedures for Use in Appeals of Certification Matters The NERC Compliance and Certification Committee Hearing Procedures for Use in Appeals of Certification Matters describe procedure...

AI summary The NERC Compliance and Certification Committee Hearing Procedures outline processes for resolving certification disputes, governed by Section 504 and Appendix 5A of NERC's Rules of Procedure. These procedures emphasize fairness, fact-based decisions, and efficiency in appeals related to registration or certification activities.

c. NERC Compliance and Certification Committee Mediation Procedures The NERC Compliance and Certification Committee Mediation Procedures describe an informal, voluntary process in which a CCC mediation panel assists NERC and a Regional Ent...

AI summary The NERC Compliance and Certification Committee Mediation Procedures outline an informal, voluntary process where a mediation panel assists NERC and a Regional Entity in resolving disputes over compliance program audits. The process is confidential, and any agreement reached is binding, though parties are not obligated to settle. Alternative dispute resolution options remain available.

C. Proposed Amended Compliance and Certification Committee Charter The proposed amendments to the Compliance and Certification Committee Charter were primarily made to reflect changes to the Joint Registration Organization criteria and the...

AI summary Proposed amendments to the Compliance and Certification Committee (CCC) Charter align with updated Joint Registration Organization and Coordinated Functional Registration criteria, reflect revised NERC Rules of Procedure, and adjust titles to 'Director of Compliance Operations.' References to ERCOT are modified to specify Texas RE's role in appeals if affiliated with ERCOT.

Attachment 11 : Western Interconnection Regional Advisory Body proposed Business Plan and Budget for 2010 Attachment 12: Discussion of Comments Received During Development of NERC's 2010 Business Plan and Budget. Attachment 13: Calculation...

AI summary The text lists various attachments related to NERC's 2010 business plan, budget, and related reports, including financial statements, reliability assessments, and administrative cost metrics for the Western Interconnection Regional Advisory Body and other regional entities.

supports the statutory activities of development of reliability standards and achieving compliance with reliability standards, and includes NERC's metrics, benchmarking and event analysis activities. (5) The Situation Awareness and Infrast...

AI summary The text outlines NERC's 2010 Business Plan and Budget, emphasizing compliance with reliability standards, infrastructure security, and funding distribution. It highlights the Situation Awareness and Infrastructure Security Program's role in reliability enforcement and critical infrastructure protection (CIP), alongside the need for additional staffing and resources to improve operational efficiency and reliability initiatives.

IP standards that provide for TFEs, pending adoption of a permanent program to address TFEs. 38 Compliance Process #2009-006 provides for registered entities to submit TFEs to the applicable 37 The originally-posted proposed TFE Procedure,...

AI summary The text discusses the handling of Technical Feasibility Exceptions (TFEs) under Compliance Process #2009-006, emphasizing that Regional Entities, not NERC, are responsible for reviewing and processing TFE submittals. It references NERC's role in IP standards and provides links to related documents.

2. Compliance Monitoring and Enforcement and Organization Registration and Certification Program Under the Compliance Monitoring and Enforcement and Organization Registration and Certification Program, NERC monitors, audits, investigates a...

AI summary NERC oversees compliance with reliability standards through its Compliance Monitoring and Enforcement Program, including a registry of over 1,800 entities responsible for 4,500 functions affecting bulk power system reliability. Goals include processing violations efficiently and conducting audits of regional entities.

6. Administrative Services The Administrative Services departments support the other NERC programs. Administrative Services comprises the following functions: (i) Technical Committees and Members' Forums; (ii) General and Administrative; (...

AI summary Administrative Services supports NERC programs through functions like Technical Committees, Legal/Regulatory, and Finance. The 2010 budget for Technical Committees and Forums is $1.6M, fully funded by forum dues, with no impact on LSE assessments. This includes a $300K reimbursement from the Transmission Owners and Operators Forum to NERC.

e resource requirements for processing TFE become clearer during 2010, it is possible that WECC may need to submit a supplemental budget and funding request for additional resources for this activity. WECC is budgeting increases in direct...

AI summary WECC outlines 2010 budget adjustments, including increased FTEs for reliability programs, reduced consultant costs, and funding for new Reliability Coordination Centers. It seeks a $1M increase to meet its Working Capital Reserve target, while addressing resource needs from TFE processing.

n on compliance audits requested in the 2009 Budget Order in the December 19, 2008 Budget Revision Filing. FERC found this information to be acceptable in the July 16, 2009 Budget Compliance Order. 87 84 See, e.g., 2008 Budget Order at PP...

AI summary The text discusses FERC's approval of compliance audits in the 2009 Budget Order and NERC's development of metrics for Regional Entity operations, including administrative cost metrics. These metrics were included in filings following FERC's 2008 directive to improve budget transparency and cost analysis.

he Regional Entities, in alphabetical order. The audited financial statements provided for SPP are the audited financial statements for Southwest Power Pool, Inc., since the SPP Regional Entity is not budgets against actual expenditures, b...

AI summary The document outlines the reconciliation of 2008 budgets against actual expenses for NERC and Regional Entities, noting that audited financial statements were used for some entities while others relied on unaudited data. FERC directed NERC to include additional reconciliations in future filings based on audited statements.

VII. UPDATE ON STATUS OF PROCESSING ALLEGED VIOLATIONS OF RELIABILITY STANDARDS In the December 19, 2008 Budget Revision Filing , NERC and the Regional Entities provided a report on the status of alleged violations of reliability standards...

AI summary The document discusses NERC and Regional Entities' progress in processing alleged violations of reliability standards, FERC's concerns about backlog reduction, and the directive for a 2010 report on remaining unprocessed violations. Attachment 19 details initiatives to expedite processing.

sup> The following reliability enhancement programs and activities were described in the 2008 Reliability Enhancement Programs Filing : 100 2009 Budget Order at P 71 (footnote omitted). 101 Compliance Filing of the North American Electric...

AI summary The 2008 Reliability Enhancement Programs Filing outlines NERC's initiatives, including strategic planning, critical infrastructure protection, reliability metrics benchmarking, and development of reliability databases. NERC emphasized ongoing efforts to improve efficiency in standards development, compliance monitoring, and reliability assessments, with updates filed separately.

/sup> Order Certifying the North American Electric Reliability Corporation as the Electric Reliability Organization and Ordering Compliance Filing , 116 FERC ¶61,062 (2006) (ERO Certification Order). 2 Rules Concerning Certification of the...

AI summary NERC submits a three-year performance report to FERC, demonstrating compliance with ERO regulations (18 C.F.R. §39.3) and evaluating Regional Entities' effectiveness. The report highlights NERC's role in enforcing reliability standards and outlines planned improvements to enhance bulk power system reliability.

or to WECC, where the Reliability Management System agreement imposed, by contract, penalties for violation of a subset of reliability standards on those entities in WSCC that had signed the contract. the bulk power system. Prior to adopti...

AI summary The text discusses the adoption of mandatory reliability standards for bulk power systems, noting Ontario and New Brunswick's implementation of NERC-developed standards. It highlights the role of WECC's Reliability Management System, CFE's participation in the Western Interconnection, and Congress's endorsement of audited self-regulation via NERC. The approach emphasizes stakeholder collaboration and delegated regulatory authority.

ng, hard work, and most of all, a mind open to the nature of risk. As with all such difficult and persistent human problems, the question is whether we have the wisdom and will to change. 10 The fundamental question to be addressed by the...

AI summary The document evaluates NERC's performance as the ERO over three years, noting improvements in bulk power system reliability through enhanced systems and mitigation of over 1,000 violations. The Commission will review this assessment under 18 C.F.R. §39.3, with public comment, to determine if reliability has improved and if future plans will further enhance it.

Improvement to the Reliability of the Bulk Power System NERC and the industry have made significant progress toward accomplishing the goal of the U.S. Congress of having a comprehensive set of mandatory and enforceable reliability standard...

AI summary NERC and FERC have established mandatory reliability standards for the bulk power system, replacing voluntary compliance with enforceable requirements. The CIP standards (CIP-002 to CIP-009) aim to protect critical infrastructure, while regional entities like WECC develop additional standards. Ongoing revisions ensure evolving reliability needs are met.

ic Reliability Corporation 2009-2011 Standards Development Plan Pursuant to Section 310 of the ERO Rules of Procedure , filed February 23, 2009 in Docket Nos. RM05-17-000, RM05-25-000 and RM06-16-000. Each annual plan has included more sta...

AI summary The text discusses challenges with NERC's 2009–2011 Standards Development Plan, highlighting resource pressures from increasing standards projects and the need for a streamlined interpretation process. It affirms the effectiveness of the consensus-based reliability standards model under FERC approval, emphasizing compliance with statutory requirements for public comment and due process.

C. NERC and the Regional Entities Have Developed and Implemented a Comprehensive Organization Registration Program In order to begin monitoring and enforcing compliance with the mandatory reliability standards, it was necessary for NERC an...

AI summary NERC and Regional Entities established a program to register bulk power system entities for reliability compliance. Over 1,800 entities were registered, with 100 disputes arising, seven unresolved as of 2009. The process involved defining reliability functions, creating compliance criteria, and resolving disputes through regional and NERC-level appeals.

D. NERC and the Regional Entities Have Developed a Comprehensive and Effective Program for Monitoring and Enforcing Compliance with Reliability Standards Since becoming the ERO, NERC, working with the Regional Entities, has developed and i...

AI summary NERC, as the ERO, has established a comprehensive compliance program with Regional Entities through the CMEP, including eight processes like audits and self-reports. Regional Entities handle front-line tasks, while NERC provides oversight. This ensures adherence to reliability standards via procedures outlined in NERC's Rules of Procedure.

Issues Identified by Stakeholders Concerning the Compliance Program Despite how much has been accomplished in starting up the NERC and Regional Entity Compliance Monitoring and Enforcement Programs, it remains an incomplete effort. At one...

AI summary Stakeholders note the NERC and Regional Entity Compliance Monitoring and Enforcement Programs are incomplete, with limited public compliance actions and few decided cases. This lack of transparency creates uncertainty for registered entities, necessitating greater visibility of standards violations and penalties to foster a culture of compliance.

for certain segments of owners, operators, or users of the bulk power system to take to ensure the reliability of the bulk power system. Essential Actions require NERC board approval before issuance. These notifications currently are sent...

AI summary NERC's alert dissemination program notifies registered entities of reliability risks, requiring acknowledgment and progress reports for Level 2/3 notifications. Essential Actions need board approval, and the program enables NERC to monitor responses to reliability threats.

Improvement to the Reliability of the Bulk Power System The Event Analysis Program has been effective in helping to improve the reliability of the bulk power system by analyzing major events occurring on the bulk power system, uncovering i...

AI summary The Event Analysis Program enhances bulk power system reliability by identifying risks and sharing insights, though confidentiality and cross-border regulatory protocols hinder full information dissemination. NERC urges FERC and Canadian authorities to expedite protocols for improved reliability and plans to expand redacted post-event analysis sharing.

Issues Identified by Stakeholders Concerning Event Analysis Noting the backlog of system events being analyzed for which reports have not been published, stakeholders suggested a need for criteria to determine events to be analyzed (in ord...

AI summary Stakeholders highlighted a backlog of unanalyzed system events, urging criteria to prioritize analyses and interim reporting. They also emphasized improving cross-border information protocols and addressing tensions between Event Analysis and Compliance Programs. NERC's ongoing reliability assessments of the bulk power system, mandated by FPA and FERC, are detailed, with a focus on emerging reliability issues.

NERC responsible for the overall Situational Awareness Program and is a recognized CIP expert. Additionally, NERC has created and staffed the position of Manager of Critical Infrastructure Protection. NERC's CIP activities include facilita...

AI summary NERC leads critical infrastructure protection (CIP) through standard development, compliance oversight, and training. Eight CIP standards (CIP-002 to CIP-009) were approved by FERC in Order No. 706, requiring phased compliance by registered entities. Regional Entities conduct audits, and self-certification is mandated every six months starting 2008.

Issues Identified by Stakeholders Concerning Critical Infrastructure Protection Stakeholders identified a number of issues and recommendations concerning NERC's CIP activities, including the following: - Direction for implementation of CIP...

AI summary Stakeholders highlighted issues with NERC's CIP activities, including the need for centralized direction, timely guidance, a fast-track process for interpretation requests, and more targeted cybersecurity advisories. NERC's role in infrastructure security via ES-ISAC is noted, with detailed discussion in Attachment 2.

III. NERC CONTINUES TO MEET THE CERTIFICATION CRITERIA OF 18 C.F.R. §39.3(b) A. NERC Has the Ability to Develop and Enforce, Pursuant to 18 C.F.R. §39.7, Reliability Standards that Provide for an Adequate Level of Reliability of the Bulk P...

AI summary NERC, as the certified ERO, has developed 95 continent-wide reliability standards with FERC approval, using a stakeholder-driven process. Standards are created by industry experts, subject to public comment, ballot approval, and FERC endorsement. NERC continues prioritizing new and revised standards through its three-year development plans to ensure bulk power system reliability.

disputed Remedial Action Directive. Appeals from adverse decisions of the Regional Entity hearing body may be taken to NERC, to be heard and decided by the NERC Board of Trustees Compliance Committee. NERC has also established rules for th...

AI summary NERC has established rules for financial penalties related to reliability standard violations, managed through the CMEP. The process includes issuing violation notices, processing alleged violations, and reporting to FERC per ERO regulations. Appeals from adverse decisions by the Regional Entity hearing body are directed to NERC's Board of Trustees Compliance Committee.

iring consultation with the MRC in the preparation of the NERC budget as well as posting of the proposed budget for a 30-day period to allow for comment by the members and standing committees of NERC. thereby enabling NERC to monitor the R...

AI summary NERC and Regional Entities have established robust budgeting, financial reporting, and compliance processes, including MRC consultation, 30-day comment periods, audited statements, and FERC-compliant records retention. These systems ensure statutory funds are segregated from non-statutory expenses and have enhanced staffing since 2006.

C. NERC Has Developed an Effective Set of Rules of Procedure NERC's predecessor organization had rules of procedure in place covering a number of areas of its activities. For purposes of its ERO certification application, NERC organized th...

AI summary NERC's Rules of Procedure, developed and updated post-ERO certification, cover reliability standards, compliance monitoring, and administrative processes. All amendments were submitted to and approved by FERC, ensuring alignment with FPA and FERC regulations. The rules address areas like training, infrastructure security, and information handling.

D. NERC Has Negotiated and Modified Delegation Agreements with the Regional Entities Governing their Delegated Statutory Functions NERC has negotiated and has in place a set of delegation agreements with the eight Regional Entities pursuan...

AI summary NERC has established and modified delegation agreements with eight Regional Entities, granting them authority to perform statutory functions under FPA and FERC regulations. These agreements cover standards development, governance, compliance monitoring, and financial allocations, with NERC planning to eliminate Section 700 aligning with the termination of a 2009 program.

Criteria A8, Reliability Compliance Enforcement Program Approved, December 20, 2007 The NPCC Inc. Reliability Compliance and Enforcement Program (the Program) described in this document is to be used to assess and enforce compliance with N...

AI summary The NPCC Inc. Reliability Compliance and Enforcement Program (2007) establishes procedures to assess and enforce compliance with NPCC reliability criteria. Sanctions under the program do not absolve members of their obligation to comply with NPCC guidelines, and members must submit compliance plans. The program applies only to bulk power system elements classified in Document A-10.

1.0 Introduction NPCC has established a Reliability Assessment Program to bring together work done by NPCC, Transmission Planners and Planning Coordinators relevant to the assessment of bulk power system reliability . As part of the Reliab...

AI summary The NPCC's Reliability Assessment Program involves periodic reviews of bulk power system reliability by the Task Force on System Studies (TFSS) and annual assessments by Planning Coordinators. These efforts ensure compliance with NPCC and NERC standards, with NPCC overseeing inter-area issues and Planning Coordinators handling intra-area problems.

5.0 NPCC Full Member, More Stringent Criteria These Criteria are in addition, more stringent or more specific than the NERC or any Regional Reliability standard requirements

AI summary The NPCC Full Member criteria are additional, more stringent, and more specific than NERC or Regional Reliability standards. This establishes higher reliability requirements for NPCC members compared to general industry benchmarks.

7.0 Compliance Monitoring Adherence to requirements in this Directory must be reported in a manner and form designated by the Compliance Committee. Exceptions to the requirements stipulated herein are acceptable if the exceptions are compl...

AI summary The section outlines compliance reporting requirements, exception handling, revision processes involving the Task Force on System Protection and RCC, and updates aligned with NERC standards. Revisions require NPCC Open Process review, RCC approval, and Full Member Representative final approval for revised sections.

1.6.2.2.2 Facility Classification Upgraded to Bulk Power System . These criteria apply to all existing facilities which become classified as bulk power system . A mitigation plan shall be required to bring such a facility into compliance w...

AI summary Facilities upgraded to Bulk Power System must implement mitigation plans. If physical separation per Section 5.12 is unfeasible, owners must report reasons and assessments to TFSP using specified forms. Compliance procedures are outlined in Appendix A, Section 4.0.

b. SPS Re-classified to Type I or Type II These requirements apply to all existing SPSs which are reclassified as Type I or Type II due to system changes. A mitigation plan shall be required to bring such a SPS into compliance with these c...

AI summary This section outlines requirements for existing Special Protection Systems (SPS) reclassified as Type I or Type II due to system changes, mandating the development of a mitigation plan to ensure compliance with updated criteria.

ded, manual vs. automatic, etc. - . Reason for the installation - . Comments, explanations, such as "temporary until such time…" - . Company, owner - . SPS Number, drawn by NPCC staff - . Current Status, i.e. New, Changed or Removed - . Ty...

AI summary The document outlines procedures for installing, modifying, or retiring Special Protection Systems (SPS), emphasizing review by the Reliability Coordinating Committee (RCC) and Task Force on Coordination of Planning (TFCP). It details requirements for reporting SPS changes, determining system types, and updating NPCC databases.

h each key facility ; - perform the tests outlined in Table 1; - maintain records of the test results; and - provide the above upon request to the Reliability Coordinator and Transmission Operator. Note that the occurrence of an actual suc...

AI summary The text outlines requirements for testing key facilities, maintaining records, and reporting to reliability coordinators and transmission operators. It emphasizes that successful events can count as completed tests if they meet performance criteria. The NPCC Compliance Committee sets reporting obligations for transmission and generator owners regarding critical component failures.

Revision History Version Date Action Change Tracking (New, Errata or Revisions) 0 12/22/2008 New 1 07/07/2009 Included FAC-008 in Section 3.0 Errata Table of Content Title Page 1 Revision History 2 Table of Content 3 1.0 Introduction 4 2.0...

AI summary The document provides a revision history and table of contents for a technical standard related to reliability requirements set by NERC ERO and NPCC. It outlines sections covering terms, reliability standards, regional requirements, verification programs, and compliance monitoring.

ne and report the generator or generation facility real power seasonal auxiliary loads (including common station loads ) to the Transmission Operator. - 5.6.2 The Transmission Operator shall: - 5.6.2.1 Document any discrepancies between sy...

AI summary The document outlines the Transmission Operator's responsibilities to verify generator capabilities, report discrepancies to NPCC, and ensure compliance through annual validation and audits by NPCC's Task Force and Compliance Committee.

5.5 UFLS Program Assessment Requirements - 5.5.1 Studies shall be performed by the associated Transmission Operator to ensure satisfactory voltage and loading conditions after automatic load shedding . - 5.5.2 The Task Force on System Stud...

AI summary Section 5.5 outlines requirements for UFLS program assessments, including studies by Transmission Operators to ensure voltage/loading conditions post-load shedding and triennial coordination by the Task Force on System Studies with NPCC Balancing Authorities. Compliance monitoring is mandated, with revisions to the NPCC Directory requiring RCC and Full Member approval.

3.5 Com pliance with NERC Disturbance Control Standard (DCS) Areas within NPCC shall calculate and report compliance with the Disturbance Control Standard as stipulated in Document C-09, Monitoring Procedures for Operating Reserve Criteria...

AI summary NPCC areas must comply with NERC's Disturbance Control Standard (DCS) using a 15-minute recovery period, achieving 100% compliance for reportable disturbances. Non-compliance requires increasing ten-minute reserve requirements by the Contingency Reserve Adjustment Factor.

1.0 Introduction The purpose of the Northeast Power Coordinating Council Inc. is to promote the reliable and efficient operation of the interconnected bulk power systems in Northeastern North America through the establishment of criteria,...

AI summary The Northeast Power Coordinating Council Inc. (NPCC Inc.) aims to ensure reliable and efficient operation of bulk power systems through reliability criteria, planning coordination, and compliance enforcement. Its Reliability Compliance and Enforcement Program assigns compliance assessment responsibilities between NPCC Inc. and regional 'Areas,' emphasizing that the latter handles market participant reporting. The program applies to all full members and aligns with NPCC Inc. bylaws.

2.1 Development of Criteria The criteria utilized in assessing compliance have been developed by NPCC Inc. consistent with the North American Electric Reliability Council broad-based standards. NPCC Inc. has implemented its Open Process as...

AI summary The criteria for compliance were developed by NPCC Inc. in alignment with NERC standards, utilizing an Open Process to ensure non-discrimination and industry input in their establishment and modification.

2.2 Obligations of Members Appendix A of this document sets forth the compliance requirements to which each Member has agreed for the current enforcement year.

AI summary Appendix A outlines compliance requirements agreed to by Members for the current enforcement year, establishing obligations under the regulatory framework governing Nova Scotia's utility sector.

3.1 Area Reporting Each Area furnishes to CMAS via the NPCC Inc. web-based Compliance Application, as per the established schedule, a compliance submittal for each of the requirements described in the annual NPCC Inc. Compliance Program Sc...

AI summary Each Area must submit compliance reports to CMAS via NPCC Inc.'s web-based Compliance Application according to the annual schedule. NPCC Inc. enforces a lateness policy with sanctions outlined in Section 4.2 of A-8.

3.2 Area Disclosure When an alleged violation is suspected, the name of the Area (not the individual party) will be reported to NPCC Inc. CMAS will track alleged violations and report to the RCC. Upon confirmation and completion of the due...

AI summary The section outlines procedures for disclosing participants responsible for alleged violations. The Area reports the violation to NPCC Inc., CMAS tracks violations, and upon confirmation, the Area discloses the responsible participant's name to RCC if they are an NPCC member, or follows internal procedures otherwise.

4.0 Compliance Assessment and Enforcement Process The compliance assessment and enforcement process is described below in terms of the functional entities that will be responsible for the process. In addition, the Guidelines for the Implem...

AI summary The compliance assessment and enforcement process involves functional entities responsible for its implementation. The Guidelines for the Implementation of the NPCC Inc. Compliance Program (Document B-22) provides detailed processes and related information for the Program.

4.1 Compliance Monitoring and Assessment Subcommittee (CMAS) CMAS, as a standing subcommittee of the Reliability Coordinating Committee (RCC), has the responsibility to perform independent compliance monitoring and assessment functions and...

AI summary CMAS, a subcommittee of the RCC, oversees compliance monitoring and enforcement, managing programs, utilizing NPCC Inc. Task Forces for assessments, and employing self-certification forms. It submits reports to the RCC and recommends sanctions for violations, using documents like Document C-32 for verification.

4.2 Reliability Coordinating Committee (RCC ) The RCC, a standing committee of NPCC Inc., reviews the compliance report submittals received from CMAS. Prior to a final compliance determination, the RCC may remand the report back to CMAS fo...

AI summary The Reliability Coordinating Committee (RCC), a standing committee of NPCC Inc., reviews compliance reports and sanction recommendations from CMAS. It may remand reports for clarification before final compliance determinations and forwards disputes to the Enforcement Panel (EP).

5.1 Violations of Reliability Criteria Table 1 defines the sanctions for violations to the criteria as described in the Compliance Templates shown in Appendix A. Not all Compliance Templates require all four levels of non-compliance. Excep...

AI summary This section outlines the sanctions for violations of reliability criteria, referencing Compliance Templates in Appendix A. It clarifies that not all templates apply all four levels of non-compliance and that criteria take precedence over templates where there is an inconsistency.

Table 1 - NPCC Inc. Non-Compliance Sanctions Level of Non Compliance Sanctions 1 Letter to the relevant functional head (operations, planning) of the Area 2 Letter to the Chief Executive of the Area with copy to the relevant functional hea...

AI summary This table outlines the sanctions imposed by the Northeast Power Coordinating Council Inc. (NPCC Inc.) for different levels of non-compliance. It provides a structured approach to addressing non-compliance, ranging from letters to relevant individuals and groups to more severe actions involving regulatory authorities.

Sanctions shall be applied if a complete report is not received by CMAS after a grace period of ten calendar days has expired. CMAS shall assess the following level of non-compliance for lateness: Level 1 After 10 calendar day grace period...

AI summary The text outlines a sanctions framework applied by CMAS if reports are not submitted within specified grace periods. Non-compliance levels escalate based on the duration of lateness, with increasing severity from Level 1 to Level 4.

6.0 RCEP Data Retention Requirements For the purposes of NPCC Inc. RCEP, a minimum of three years of data shall be retained that fully supports certification towards an NPCC Inc. criteria document or compliance template. This requirement m...

AI summary NPCC Inc. mandates a minimum three-year data retention period for RCEP compliance, subject to override by other NPCC criteria. The Compliance Monitoring and Assessment Subcommittee leads this, with annual reviews by TFCP, TFCO, TFSP, TFSS, and TFIST. References include NPCC Inc. bylaws and compliance program documents.

APPENDIX A Compliance Templates and Monitoring

AI summary Appendix A of the regulatory proceeding document focuses on Compliance Templates and Monitoring. The section likely outlines standardized templates and procedures for ensuring adherence to regulatory requirements, though specific content details are not provided in the text.

Responsibilities Reporting Responsibility : Areas Frequency of Reporting: Annually Compliance Monitoring and Assessment Responsibility: NPCC Inc. Enforcement Responsibility: NPCC Inc.

AI summary The document outlines annual reporting responsibilities and assigns compliance monitoring, assessment, and enforcement duties to NPCC Inc. under the regulatory proceeding. These responsibilities emphasize ongoing oversight and adherence to standards.

Full (100%) Compliance An annual Area Transmission Review Report, including all supporting documentation in accordance with Document B-4 was submitted to TFSS and the Area's planned bulk power system meets the requirements of Document A-2....

AI summary The Area submitted an annual Area Transmission Review Report to TFSS, complying with Document B-4 and A-2 requirements. Reports for Interim/Intermediate Reviews must be submitted by year-end, while Comprehensive Reviews by April 1st of the following year.

Non-Compliance - Level 1: An Area Transmission Review was submitted, but was incomplete in meeting the requirements of Document B-4. - Level 2: An Area Transm ission Review was submitted. Ho wever, the Area 's planned bulk power system was...

AI summary The text outlines four levels of non-compliance related to the submission of an Area Transmission Review and the Bulk Power System's adherence to A-2 criteria. Levels 1-3 involve varying degrees of incomplete submissions or noncompliance, with corrective actions required. Level 4 refers to no submission and directs to the Policy on Lateness.

Responsibilities Reporting Responsibility : Areas Frequency of Reporting: Annually Compliance Monitoring and Assessment Responsibility: NPCC Inc. Enforcement Responsibility: NPCC Inc.

AI summary The document outlines annual reporting responsibilities and assigns compliance monitoring, assessment, and enforcement duties to NPCC Inc. under the regulatory proceeding. These responsibilities emphasize ongoing oversight and adherence to standards.

Full (100%) Compliance The Area load-shedding program fully complies with the requirements of the NPCC Inc. Emergency Operation Criteria (Document A-3), Section 4.6.

AI summary The Area load-shedding program is confirmed to fully comply with the NPCC Inc.'s Emergency Operation Criteria (Document A-3), Section 4.6, ensuring alignment with established emergency operational standards.

Non-Compliance Level 1: Deficiencies in Area load shedding capability were reported and a plan was submitted by the Area to correct the deficiencies. Deficiencies were corrected within five (5) months of the end of the current reporting pe...

AI summary The document outlines four levels of non-compliance related to Area load shedding capability, specifying correction timelines (5–12 months) and percentage thresholds (90–100% of required load shedding). It references Document A-8 from NPCC Inc. and Section 5.2 on lateness, highlighting deficiencies in Underfrequency Load Shedding (UFLS) programs and incomplete corrective plans.

Compliance Template A3-3

AI summary This document outlines Compliance Template A3-3 from a Nova Scotia regulatory proceeding, referencing various acronyms and topics related to energy regulation, compliance, and technical standards.

Responsibilities Reporting Responsibility : Areas Frequency of Reporting: Annually Compliance Monitoring and Assessment Responsibility: NPCC Inc. Enforcement Responsibility: NPCC Inc.

AI summary The document outlines annual reporting responsibilities and assigns compliance monitoring, assessment, and enforcement duties to NPCC Inc. under the regulatory proceeding. These responsibilities emphasize ongoing oversight and adherence to standards.

Full (100%) Compliance Each Area shall provide to NPCC Inc. , on a confidential basis, t heir current key facilities and critical components list annually . The list shall identify critical components associated with the following applicab...

AI summary The document mandates that each Area submit an annual, confidential list of key facilities and critical components to NPCC Inc., including blackstart generating stations, underground transmission cables, and control center facilities, to ensure full compliance with reliability standards.

Non-Compliance Level 1: None. Level 2: A key facility and critical component list was provided but NPCC Inc. Inter-Area Restoration Coordination Working Group (CO-11) found that it did not fully support the energization of the basic minimu...

AI summary The document outlines non-compliance levels related to maintaining a current list of key facilities and critical components. Level 2 notes that the provided list did not fully support energizing the basic minimum power system, as identified by NPCC Inc.'s CO-11 working group. Level 3 highlights the Area's failure to maintain an updated list.

A-4 Compliance

AI summary The document section titled 'A-4 Compliance' is identified, but no further details or discussions are provided in the text.

Bulk Power System Protection Minimum Maintenance Standard: Protection system owners shall im plement a protection sy stem maintenance and testing program that fulfills the requirements of the NPCC Maintenance Criteria for Bulk Power System...

AI summary Protection system owners must implement maintenance programs per NPCC's Document A-4, ensuring compliance with bulk power system protection standards.

Responsibilities Area shall enforce market participants' compliance to A-4 Criteria in accordance with the Area 's policy and procedure.

AI summary The document outlines the responsibility of the 'Area' to enforce compliance with A-4 Criteria among market participants, adhering to its established policies and procedures.

Full (100%) Compliance Exceptions to Docu ment A-4 requirements are acceptable if the exceptions are completely removed within five (5) months of the end of the current reporting period. Document A-8 NPCC Inc. Reliability Compliance And En...

AI summary The document allows exceptions to Document A-4 requirements if removed within five months. It references NPCC Inc.'s Reliability Compliance and Enforcement Program from December 2007.

Compliance Template A6-1

AI summary The document is a compliance template with a list of acronyms and existing topics related to regulatory proceedings in Nova Scotia, including energy, grid, and regulatory processes.

Non-Compliance - Level 1: Failure to meet the Ten-Minute Reserve requirement as described above once during the past twelve (12) months. - Level 2: Failure to meet the Ten-Minute Reserve requirements as described above twice during the pas...

AI summary The text outlines four levels of non-compliance based on the frequency of failing to meet the Ten-Minute Reserve requirement over a 12-month period, with escalating severity from one to four or more failures.

8.0 Maintenance And Testing Each TO, and GO shall establish a maintenance and testing program for DME (guidance for maintenance and testing is provided in Document B-26) that includes: - Maintenance and testing intervals and their basis. -...

AI summary The document outlines requirements for TOs and GOs to establish maintenance and testing programs for DME, referencing NERC, NPCC, and IEEE standards. It emphasizes procedures, intervals, and compliance with reliability guidelines, prepared by the Task Force on System Protection.

harged with developing mandatory and enforceable Reliability Standards, which are subject to FERC review and approval. & lt;sup>3 16 U.S.C. § 824o(f) (2006). & lt;sup>4 See Memorandum of Understanding between Nova Scotia Utility and Review...

AI summary The document discusses the implementation of NERC Reliability Standards and NPCC Regional Reliability Criteria in Nova Scotia, referencing memoranda of understanding between the Nova Scotia Utility and Review Board and NERC, as well as between Nova Scotia Power Incorporated and the Northeast Power Coordinating Council and NERC.

ty standard shall state one or more performance requirements, which if achieved by the applicable entities, will provide for a reliable bulk power system, consistent with good utility practice and 10 9 These functional classes of entities...

AI summary The benchmarks for an excellent reliability standard emphasize measurable performance requirements, technical engineering foundations, completeness, and clear language. Standards must avoid lowest-common-denominator compromises, ensure objective evaluation, and define consequences for noncompliance. These criteria align with NERC's reliability model and prioritize public interest through sound engineering practices.

Applicability: • Balancing Authorities On October 29, 2008, BAL-001-0.1a was approved by the NERC Board of Trustees. On May 13, 2009, BAL-001-0.1a was approved by the Federal Energy Regulatory Commission. Version BAL-001-0.1a resulted from...

AI summary The document outlines the approval history of the BAL-001-0.1a standard by NERC and FERC, and explains the purpose of the Disturbance Control Standard (BAL-002-0) to ensure Balancing Authorities maintain interconnection frequency during supply disruptions. It clarifies that the standard applies to loss of supply, not load.

Applicability: • Balancing Authorities On October 29, 2008, BAL-006-1.1 was approved by the NERC Board of Trustees. On May 13, 2009, BAL-006-1.1 was approved by the Federal Energy Regulatory Commission. Version BAL-006-1.1 resulted from er...

AI summary The text outlines the approval history of BAL-006-1.1 by NERC and FERC, noting its derivation from errata changes. It also introduces CIP-001-1, a standard requiring sabotage-related disturbances to be reported to relevant authorities.

Standard BAL-001-0.1a — Real Power Balancing Control Performance

AI summary This document outlines the regulatory standard BAL-001-0.1a, focusing on real power balancing control performance. It involves entities like NERC, NSUARB, and NSPI, addressing system reliability, performance standards, and compliance with regulatory frameworks.

D. Compliance

AI summary The section outlines compliance requirements under various regulatory standards and organizations, including NERC, FERC, and NSUARB, with detailed acronyms for standards like CIP-004-2 and EOP-001-0.

1. Compliance Monitoring Process 1.1. Compliance Monitoring Responsibility Regional Reliability Organization.

AI summary The compliance monitoring process assigns responsibility to the Regional Reliability Organization (RRO) for ensuring adherence to regulatory standards and reliability protocols within the electricity sector.

1.2. Compliance Monitoring Period and Reset Timeframe One calendar month.

AI summary The compliance monitoring period is set to one calendar month, establishing a timeframe for assessing adherence to regulatory requirements.

1.3. Data Retention The data that supports the calculation of CPS1 and CPS2 (Appendix 1-BAL-001-0) are to be retained in electronic form for at least a one-year period. If the CPS1 and CPS2 data for a Balancing Authority Area are undergoin...

AI summary Data supporting CPS1 and CPS2 calculations must be retained electronically for at least one year, with extended retention during reviews. Balancing Authorities must maintain rolling 12-month records of ACE, Frequency Error, and Frequency Bias values.

3. Levels of Non-Compliance – CPS2 - 3.1. Level 1: The Balancing Authority Area's value of CPS2 is less than 90% but greater than or equal to 85%. - 3.2. Level 2: The Balancing Authority Area's value of CPS2 is less than 85% but greater th...

AI summary The document outlines four levels of non-compliance for CPS2 (Control Performance Standard 2), defined by the Balancing Authority Area's CPS2 value thresholds: Level 1 (85–90%), Level 2 (80–85%), Level 3 (75–80%), and Level 4 (<75%). These thresholds determine the severity of non-compliance with control performance requirements.

4. Applicability: - 4.1. Balancing Authorities - 4.2. Reserve Sharing Groups (Balancing Authorities may meet the requirements of Standard 002 through participation in a Reserve Sharing Group.) - 4.3. Regional Reliability Organizations - 5....

AI summary Section 4 outlines applicability of standards to Balancing Authorities, Reserve Sharing Groups, and Regional Reliability Organizations. Section 5 sets the effective date as April 1, 2005, establishing compliance timelines for these entities.

D. Compliance

AI summary The section heading 'D. Compliance' indicates a regulatory proceeding discussion focused on compliance requirements, though no detailed content is provided in the text chunk. Further analysis would require additional context from the proceeding document.

1. Compliance Monitoring Process Compliance with the DCS shall be measured on a percentage basis as set forth in the measures above. Each Balancing Authority or Reserve Sharing Group shall submit one completed copy of DCS Form, "NERC Contr...

AI summary Compliance with the Disturbance Control Standard (DCS) is measured as a percentage. Balancing Authorities and Reserve Sharing Groups must submit DCS forms to their Resources Subcommittee by the 10th day of the month following each quarter. Regional Reliability Organizations report compliance to NERC by the 20th day of the subsequent month.

1.1. Compliance Monitoring Responsibility Regional Reliability Organization.

AI summary The section outlines the responsibility of the Regional Reliability Organization (RRO) in monitoring compliance with reliability standards, emphasizing its role in ensuring adherence to regulations set by entities like NERC, FERC, and NSUARB.

1.2. Compliance Monitoring Period and Reset Timeframe Compliance for DCS will be evaluated for each reporting period. Reset is one calendar quarter without a violation.

AI summary Compliance for the Disturbance Control Standard (DCS) is evaluated during each reporting period. A reset occurs if one full calendar quarter passes without any violations, indicating sustained compliance with the standard.

1.4. Additional Compliance Information Reportable Disturbances – Reportable Disturbances are contingencies that are greater than or equal to 80% of the most severe single Contingency. A Regional Reliability Organization, sub-Regional Relia...

AI summary The section defines reportable disturbances as contingencies exceeding 80% of the most severe single contingency, outlines handling of simultaneous contingencies, and specifies evaluation procedures for multiple contingencies during recovery periods. Compliance is managed by Balancing Authorities and Reserve Sharing Groups, with potential waiver requests for inadequacies in contingency reserves.

2. Levels of Non-Compliance Each Balancing Authority or Reserve Sharing Group not meeting the DCS during a given calendar quarter shall increase its Contingency Reserve obligation for the calendar quarter (offset by one month) following th...

AI summary Non-compliant Balancing Authorities and Reserve Sharing Groups must increase Contingency Reserve obligations proportionally to their DCS non-compliance, with adjustments applied for three months. Four levels of non-compliance are defined based on average percent recovery (95–100%, 90–95%, 85–90%, and below 85%). Written documentation verifying compliance adjustments is required.

B. Requirements - R1. Only a Reliability Coordinator shall be eligible to act as Interconnection Time Monitor. A single Reliability Coordinator in each Interconnection shall be designated by the NERC Operating Committee to serve as Interco...

AI summary The document outlines requirements for the Interconnection Time Monitor, specifying that only a Reliability Coordinator can act in this role. It details procedures for monitoring Time Error, corrective actions by Balancing Authorities, and termination authority for Reliability Coordinators, referencing the NAESB Time Error Correction Procedure.

4. Applicability: - 4.1. Balancing Authorities - 4.2. Generator Operators - 4.3. Transmission Operators - 4.4. Load Serving Entities - 5. Effective Date: May 13, 2009

AI summary Section 4 outlines the applicability of regulations to Balancing Authorities, Generator Operators, Transmission Operators, and Load Serving Entities, with an effective date of May 13, 2009. No specific claims or entities are detailed beyond these roles.

1.1. Compliance Monitoring Responsibility Balancing Authorities shall be prepared to supply data to NERC in the format defined below: - 1.1.1. Within one week upon request, Balancing Authorities shall provide NERC or the Regional Reliabili...

AI summary Balancing Authorities must provide NERC with specific data formats (CSV files) within one week, including ACE and Frequency Error metrics, as part of compliance monitoring responsibilities.

2. Levels of Non-Compliance Not specified.

AI summary The section on Levels of Non-Compliance is not specified in the provided text, indicating a lack of detailed information on compliance levels or associated violations.

D. Compliance

AI summary The document section titled 'Compliance' outlines regulatory requirements and standards relevant to Nova Scotia's utility sector, referencing various reliability, security, and operational protocols governed by entities like NERC, FERC, and NSUARB.

1. Compliance Monitoring Process - 1.1. Each Balancing Authority shall submit a monthly summary of Inadvertent Interchange. These summaries shall not include any after-the-fact changes that were not agreed to by the Source Balancing Author...

AI summary The Compliance Monitoring Process outlines requirements for Balancing Authorities to submit monthly Inadvertent Interchange summaries, including specific data points and deadlines. Regional Reliability Organizations must prepare and report monthly summaries to NERC, while Balancing Authorities must conduct AIE Surveys upon NERC's request to assess interchange errors.

2. Levels of Non Compliance A Balancing Authority that neither submits a report to the Regional Reliability Organization Survey Contact, nor supplies a reason for not submitting the required data, by the 20th calendar day of the following...

AI summary The text outlines that a Balancing Authority failing to submit required reports to the RRO by the deadline is deemed non-compliant, emphasizing regulatory compliance requirements.

4. Applicability - 4.1. Reliability Coordinators. - 4.2. Balancing Authorities. - 4.3. Transmission Operators. - 4.4. Generator Operators. - 4.5. Load Serving Entities. - 5. Effective Date: January 1, 2007

AI summary Section 4 outlines the applicability of regulatory requirements to entities including Reliability Coordinators, Balancing Authorities, Transmission Operators, Generator Operators, and Load Serving Entities, with an effective date of January 1, 2007.

C. Measures - M1. Each Reliability Coordinator, Balancing Authority, Transmission Operator, Generator Operator, and Load Serving Entity shall have and provide upon request a procedure (either electronic or hard copy) as defined in Requirem...

AI summary The document outlines three measures requiring Reliability Coordinators, Balancing Authorities, and other entities to establish procedures for compliance with reliability standards, including communication protocols with FBI/RCMP for sabotage events. These measures aim to ensure operational reliability and security in the electricity sector.

1. Compliance Monitoring Process

AI summary The section outlines the compliance monitoring process, likely detailing procedures for ensuring adherence to regulatory standards and protocols within the Nova Scotia utility sector. Specifics on monitoring mechanisms, responsibilities, and enforcement measures are expected in this section.

1.1. Compliance Monitoring Responsibility Regional Reliability Organizations shall be responsible for compliance monitoring.

AI summary The section assigns responsibility for compliance monitoring to Regional Reliability Organizations, emphasizing their role in ensuring adherence to regulatory standards within the electricity sector.

1.2. Compliance Monitoring and Reset Time Frame One or more of the following methods will be used to verify compliance: - Self-certification (Conducted annually with submission according to schedule.) - Spot Check Audits (Conducted anytime...

AI summary The document outlines compliance verification methods including self-certification, spot checks, periodic audits, and triggered investigations. The Performance-Reset Period is 12 months from the last noncompliance finding, allowing entities to address issues before re-evaluation.

1.3. Data Retention Each Reliability Coordinator, Transmission Operator, Generator Operator, Distribution Provider, and Load Serving Entity shall have current, in-force documents available as evidence of compliance as specified in each of...

AI summary The section outlines data retention requirements for entities involved in reliability and compliance. Non-compliant entities must retain records until compliance is achieved or for two years plus the current year. Investigation-related evidence must be kept for one year post-closure, and the Compliance Monitor retains audit reports and compliance records.

1.4. Additional Compliance Information Adopted by Board of Trustees: November 1, 2006 Page 2 of 3 Effective Date: January 1, 2007 None.

AI summary The section indicates no additional compliance information was provided, with adoption and effective dates noted (November 1, 2006 and January 1, 2007, respectively).

2. Levels of Non-Compliance: - 2.1. Level 1: There shall be a separate Level 1 non-compliance, for every one of the following requirements that is in violation: - 2.1.1 Does not have procedures for the recognition of and for making its ope...

AI summary The document outlines four levels of non-compliance, with Level 1 and Level 3 specifying violations related to procedures for recognizing sabotage events, communicating such events, establishing contacts, and providing response guidelines. Levels 2 and 4 are not applicable.

4. Applicability: - 4.1. Within the text of Standard CIP-002-2, "Responsible Entity" shall mean: - 4.1.1 Reliability Coordinator. - 4.1.2 Balancing Authority. - 4.1.3 Interchange Authority. - 4.1.4 Transmission Service Provider. - 4.1.5 Tr...

AI summary Section 4 defines 'Responsible Entity' under CIP-002-2, including roles like Reliability Coordinators, Balancing Authorities, and Transmission Owners. Exemptions apply to nuclear-regulated facilities and certain cyber assets. The standard's effective date depends on regulatory approvals or BOT adoption.

B. Requirements - R1. Critical Asset Identification Method The Responsible Entity shall identify and document a risk-based assessment methodology to use to identify its Critical Assets. - R1.1. The Responsible Entity shall maintain documen...

AI summary The document outlines requirements for identifying critical assets and cyber assets, including annual risk-based assessments, documentation of methodologies, and senior management approval. Critical assets include control centers, transmission substations, generation resources, and systems essential for system restoration and load shedding. Critical cyber assets are defined with specific communication and accessibility criteria.

1.1. Compliance Enforcement Authority - 1.1.1 Regional Entity for Responsible Entities that do not perform delegated tasks for their Regional Entity. - 1.1.2 ERO for Regional Entity. - 1.1.3 Third-party monitor without vested interest in t...

AI summary This section outlines compliance enforcement structures, specifying roles for Regional Entities, Electric Reliability Organizations (ERO), and third-party monitors under NERC. It defines accountability for entities not delegating tasks and emphasizes oversight mechanisms for reliability standards.

1.3. Compliance Monitoring and Enforcement Processes Compliance Audits Self-Certifications Spot Checking Compliance Violation Investigations Self-Reporting Complaints

AI summary The section outlines compliance monitoring and enforcement processes, including audits, self-certifications, spot checks, violation investigations, self-reporting, and handling complaints as part of regulatory oversight mechanisms.

1.4. Data Retention - 1.4.1 The Responsible Entity shall keep documentation required by Standard CIP-002- 2 from the previous full calendar year unless directed by its Compliance Enforcement Authority to retain specific evidence for a long...

AI summary The Responsible Entity must retain documentation from the previous calendar year as required by CIP-002-2, unless extended by the Compliance Enforcement Authority during investigations. Audit records must be maintained by the Compliance Enforcement Authority and the Registered Entity.

1.5. Additional Compliance Information - 1.5.1 None. - 2. Violation Severity Levels (To be developed later.)

AI summary The section indicates no additional compliance information is provided in 1.5.1. It also notes that the subsection on Violation Severity Levels (VSL) is to be developed later, suggesting ongoing work on compliance frameworks.

1.1. Compliance Enforcement Authority - 1.1.1 Regional Entity for Responsible Entities that do not perform delegated tasks for their Regional Entity. - 1.1.2 ERO for Regional Entity. - 1.1.3 Third-party monitor without vested interest in t...

AI summary This section outlines compliance enforcement structures, specifying roles for Regional Entities, Electric Reliability Organizations (ERO), and third-party monitors under NERC. It defines accountability for entities not delegating tasks and emphasizes oversight mechanisms for reliability standards.

1.3. Compliance Monitoring and Enforcement Processes Compliance Audits Self-Certifications Spot Checking Compliance Violation Investigations Self-Reporting Complaints

AI summary The section outlines compliance monitoring and enforcement processes, including audits, self-certifications, spot checks, violation investigations, self-reporting, and handling complaints as part of regulatory oversight mechanisms.

1.4. Data Retention - 1.4.1 The Responsible Entity shall keep all documentation and records from the previous full calendar year unless directed by its Compliance Enforcement Authority to retain specific evidence for a longer period of tim...

AI summary The Responsible Entity must retain documentation from the prior calendar year, with potential extensions by the Compliance Enforcement Authority during investigations. Audit records, including those from the last audit and subsequent submissions, must be jointly maintained by the Compliance Enforcement Authority and Registered Entity.

1.5. Additional Compliance Information

AI summary The section '1.5. Additional Compliance Information' introduces a regulatory proceeding context, though no specific content or details are provided in the text. It likely outlines compliance requirements or standards relevant to the proceeding.

Version History Version Date Action Change Tracking 2 Modifications to clarify the requirements and to bring the compliance elements into conformance with the latest guidelines for developing compliance elements of standards. Removal of re...

AI summary This document outlines the version history of a regulatory compliance standard, including modifications to align with the latest guidelines, removal of certain provisions, and updates to responsible entities and compliance monitoring roles. The document was adopted by the NERC Board of Trustees on 05/06/09.

1.2. Compliance Monitoring Period and Reset Time Frame Not Applicable.

AI summary The section on compliance monitoring period and reset time frame is marked as 'Not Applicable,' indicating no specific details or requirements are provided for this regulatory proceeding under the specified topic.

1.5. Additional Compliance Information 2. Violation Severity Levels (To be developed later.)

AI summary The document outlines the need to develop Violation Severity Levels (VSL) for regulatory compliance, though this section is marked as pending further development. It highlights the importance of defining VSL to ensure adherence to standards such as CIP-004-2 and CIP-005-2, which are critical for cybersecurity and infrastructure protection.

1.4. Data Retention - 1.4.1 The Responsible Entity shall keep logs for a minimum of ninety calendar days, unless: a) longer retention is required pursuant to Standard CIP-008-2, Requirement R2; b) directed by its Compliance Enforcement Aut...

AI summary The Responsible Entity must retain logs for 90 days, except when required by CIP-008-2 R2 or directed by the Compliance Enforcement Authority. Documents under CIP-005-2 from the prior year and audit records must also be retained, with the Compliance Enforcement Authority and Registered Entity jointly managing audit data.

1.5. Additional Compliance Information

AI summary The section '1.5. Additional Compliance Information' introduces a regulatory proceeding context, though no specific content or details are provided in the text. It likely outlines compliance requirements or standards relevant to the proceeding.

2. Violation Severity Levels (To be developed later.)

AI summary The section titled 'Violation Severity Levels' is identified as a placeholder to be developed later, indicating that specific criteria or frameworks for assessing the severity of violations have not yet been detailed in this document.

D. Compliance

AI summary The section heading 'D. Compliance' indicates a regulatory proceeding discussion focused on compliance requirements, though no detailed content is provided in the text chunk. Further analysis would require additional context from the proceeding document.

1. Compliance Monitoring Process

AI summary The section outlines the compliance monitoring process, likely involving regulatory oversight and adherence to standards such as CIP and FAC. It may discuss roles of entities like NSUARB and NSPI in ensuring compliance with reliability and operational protocols.

1.1. Compliance Enforcement Authority - 1.1.1 Regional Entity for Responsible Entities that do not perform delegated tasks for their Regional Entity. - 1.1.2 ERO for Regional Entities. - 1.1.3 Third-party monitor without vested interest in...

AI summary This section outlines compliance enforcement structures, including Regional Entities, ERO, and third-party monitors for NERC, defining roles in regulatory oversight.

1.3. Compliance Monitoring and Enforcement Processes Compliance Audits Self-Certifications Spot Checking Compliance Violation Investigations Self-Reporting Complaints

AI summary The section outlines compliance monitoring and enforcement processes, including audits, self-certifications, spot checks, violation investigations, self-reporting, and handling complaints as part of regulatory oversight mechanisms.

1.4. Data Retention - 1.4.1 The Responsible Entity shall keep documents other than those specified in Requirements R7 and R8.2 from the previous full calendar year unless directed by its Compliance Enforcement Authority to retain specific...

AI summary The Responsible Entity must retain documents from the previous calendar year unless directed otherwise by the Compliance Enforcement Authority. Audit records must be retained by both the Compliance Enforcement Authority and the Registered Entity.

1.5. Additional Compliance Information - 1.5.1 The Responsible Entity may not make exceptions in its cyber security policy to the creation, documentation, or maintenance of a physical security plan. - 1.5.2 For dial-up accessible Critical...

AI summary The Responsible Entity must adhere to strict cyber security policies without exceptions for physical security plans. However, dial-up accessible Critical Cyber Assets using non-routable protocols are exempt from CIP-006-2 compliance for that specific access point.

2. Violation Severity Levels (Under development by the CIP VSL Drafting Team)

AI summary The section outlines the development of Violation Severity Levels (VSL) by the CIP VSL Drafting Team, focusing on categorizing violations under regulatory standards. It is currently under development and has not been finalized.

D. Compliance Adopted by NERC Board of Trustees: November 5, 2009 4 Effective Date: April 1, 2010

AI summary The text states that a compliance standard was adopted by the NERC Board of Trustees on November 5, 2009, with an effective date of April 1, 2010. This is part of a regulatory proceeding related to compliance requirements.

1. Compliance Monitoring Process

AI summary The section outlines the compliance monitoring process, likely involving regulatory oversight and adherence to standards such as CIP and FAC. It may discuss roles of entities like NSUARB and NSPI in ensuring compliance with reliability and operational protocols.

2. Violation Severity Levels (To be developed later.)

AI summary The section titled 'Violation Severity Levels' is identified as a placeholder to be developed later, indicating that specific criteria or frameworks for assessing the severity of violations have not yet been detailed in this document.

3. Levels of Non-Compliance — NERCnet User Organization - 3.1. Level 1: Not applicable. - 3.2. Level 2: Not applicable. - 3.3. Level 3: Not applicable. - 3.4. Level 4: Did not adhere to the requirements in Attachment 1-COM-001, NERCnet Sec...

AI summary The document outlines non-compliance levels for NERCnet, with Level 4 indicating failure to adhere to the NERCnet Security Policy in Attachment 1-COM-001.

Responsibilities It is the responsibility of NERCnet User Organizations to: - Use NERCnet facilities for NERC-authorized business purposes only. - Comply with the NERCnet security policies, standards, and guidelines, as well as any procedu...

AI summary NERCnet User Organizations are responsible for using NERCnet facilities only for authorized purposes, complying with security policies, protecting data confidentiality, managing user access, and conducting self-assessments for compliance with NERC standards.

2. Levels of Non-Compliance for Transmission Operator and Balancing Authority: Adopted by Board of Trustees: November 1, 2006 Page2 of 3 Effective Date: January 1, 2007 - 2.1. Level 1: Not applicable. - 2.2. Level 2: Not applicable . - 2.3...

AI summary The document outlines non-compliance levels for a Transmission Operator and Balancing Authority, noting Levels 1–3 are not applicable, while Level 4 involves a failure in communication as specified in R1.1.

3. Levels of Non-Compliance for Generator Operator: - 3.1. Level 1: Not applicable. - 3.2. Level 2: Not applicable . - 3.3. Level 3: Not applicable. - 3.4. Level 4: Communication facilities are not provided to address a real-time emergency...

AI summary The document outlines non-compliance levels for a generator operator, with Level 4 specifically noting the absence of communication facilities to address real-time emergency conditions as required by R1. Lower levels (1-3) are marked as not applicable.

1.1. Compliance Monitoring Responsibility Regional Reliability Organization.

AI summary The section outlines the responsibility of the Regional Reliability Organization (RRO) in monitoring compliance with reliability standards, emphasizing its role in ensuring adherence to regulations set by entities like NERC, FERC, and NSUARB.

1.2. Compliance Monitoring Period and Reset Timeframes The Regional Reliability Organization shall review and evaluate emergency plans every three years to ensure that the plans consider the applicable elements of Attachment 1- EOP-001-0....

AI summary The Regional Reliability Organization must review emergency plans every three years, considering Attachment 1-EOP-001-0. Self-certification by the Transmission Operator and Balancing Authority may be requested in non-review years. The reset timeframe is one calendar year.

2. Levels of Non-Compliance 2.1. Level 1: One of the applicable elements of Attachment 1-EOP-001-0 has not been addressed in the emergency plans. Adopted by NERC Board of Trustees: February 8, 2005 2 of 4

AI summary Level 1 non-compliance involves unaddressed elements of Attachment 1-EOP-001-0 in emergency plans. The NERC Board of Trustees adopted this standard on February 8, 2005, highlighting its regulatory significance.

1.2. Compliance Monitoring and Reset Timeframe One or more of the following methods will be used to assess compliance: - Self-certification (Conducted annually with submission according to schedule.) - Spot Check Audits (Conducted anytime...

AI summary The section outlines compliance assessment methods including self-certification, spot checks, periodic audits, and triggered investigations, each with specific timelines and procedures. The Performance-Reset Period is defined as 12 months following the last noncompliance finding.

2. Levels of Non-Compliance for a Reliability Coordinator: - 2.1. Level 1: Did not submit the report to NERC as required in R9.2. - 2.2. Level 2: Not applicable. - 2.3. Level 3: Not applicable. - 2.4. Level 4: There shall be a separate Lev...

AI summary The document outlines four levels of non-compliance for a Reliability Coordinator, with Level 1 involving failure to report to NERC (R9.2) and Level 4 covering violations of emergency plans, alerts, and decision-making authority (R1-R8, R9.3-9.4). Levels 2 and 3 are not applicable.

3. Levels of Non-Compliance for a Balancing Authority: - 3.1. Level 1: Not applicable. - 3.2. Level 2: Did not provide evidence that it has the responsibility and clear decision-making authority in accordance with R1. - 3.3. Level 3: Not a...

AI summary The document outlines four levels of non-compliance for a Balancing Authority, detailing specific violations related to responsibility, communication during emergencies, and implementation of emergency plans. Adopted by the Board of Trustees in 2008 and effective May 2009, Level 4 violations include failure to communicate system conditions and improper execution of emergency protocols.

condition exists or as allowed by the Balancing Authority or Transmission Operator whose equipment is at risk. The following are minimum requirements that must be met before SOLs or IROLs are revised:

AI summary The text outlines conditions for revising System Operating Limits (SOLs) and Interconnection Reliability Operating Limits (IROLs), emphasizing that revisions require meeting minimum requirements set by the Balancing Authority or Transmission Operator whose equipment is at risk.

1.2. Compliance Monitoring and Reset Time Frame One or more of the following methods will be used to assess compliance: - Self-certification (Conducted annually with submission according to schedule.) - Spot Check Audits (Conducted anytime...

AI summary The section outlines compliance monitoring methods including self-certification, spot checks, periodic audits, and triggered investigations. Noncompliance resets occur 12 months after the last finding. Entities must prepare for investigations with 30-day notice, and extensions may be granted on a case-by-case basis.

1.4. Data Retention Each Balancing Authority and Transmission Operator shall have its current, inforce load shedding plans. If an entity is found non-compliant the entity shall keep information related to the noncompliance until found comp...

AI summary The section outlines data retention requirements for Balancing Authorities and Transmission Operators, mandating retention of non-compliance information until compliance is achieved or for two years plus the current year. Evidence from investigations must be retained for one year post-investigation closure, with the Compliance Monitor responsible for audit reports and compliance records.

2. Levels of Non-Compliance: - 2.1. Level 1: Not applicable. - 2.2. Level 2: Not applicable. - 2.3. Level 3: Not Applicable. - 2.4. Level 4: There shall be a separate Level 4 non-compliance, for every one of the following requirements that...

AI summary The document outlines four levels of non-compliance, with Levels 1-3 being non-applicable. Level 4 specifically addresses violations related to the absence of automatic (R2) and manual (R8) load shedding plans, which are critical for system reliability and regulatory compliance.

C. Measures - M1. The Regional Reliability Organization shall have and provide upon request as evidence, its current regional reporting procedure that is used to facilitate preparation of preliminary and final disturbance reports. (Require...

AI summary The measures outline requirements for regional reliability organizations and entities to maintain and provide evidence of procedures for preparing and submitting NERC-compliant disturbance reports within 24 hours of incidents, including documentation of verbal communications when immediate reporting is not feasible.

1.4. Additional Compliance Information See Attachments: - EOP-004 Disturbance Reporting Form - Table 1 EOP-004 - 2. Levels of Non-Compliance for a Regional Reliability Organization - 2.1. Level 1: Not applicable. - 2.2. Level 2: Not applic...

AI summary The document outlines non-compliance levels for entities under EOP-004, specifying that Level 4 non-compliance applies to Regional Reliability Organizations lacking procedures for preliminary and final disturbance reports. Other entities face Level 1 non-compliance for specific reporting failures.

Introduction These disturbance reporting requirements apply to all Reliability Coordinators, Balancing Authorities, Transmission Operators, Generator Operators, and Load Serving Entities, and provide a common basis for all NERC disturbance...

AI summary The document outlines NERC's disturbance reporting requirements for entities like Reliability Coordinators and Balancing Authorities. Reports must be submitted via specific forms to NERC and the U.S. Department of Energy, covering events such as bulk power transmission failures, system separations, and load shedding exceeding thresholds.

Introduction The U.S. Department of Energy (DOE), under its relevant authorities, has established mandatory reporting requirements for electric emergency incidents and disturbances in the United States. DOE collects this information from t...

AI summary The U.S. Department of Energy (DOE) mandates reporting of electric emergency incidents via Form OE-417 to support national security and Federal Response Plan (FRP) obligations. The Energy Information Administration (EIA) utilizes this data for monthly reporting and legislative recommendations. All Reliability Coordinators, Balancing Authorities, and similar entities must submit reports to the DOE Operations Center, with EIA requesting notification of joint or separate filings.

1.2. Compliance Monitoring Period and Reset Timeframe One calendar year.

AI summary The compliance monitoring period is set to one calendar year, establishing a timeframe for assessing adherence to regulatory standards.

1.3. Data Retention The Transmission Operator must have its plan to reestablish its electric system available for review by the Regional Reliability Organization at all times. The Compliance Monitor shall retain any audit data for three ye...

AI summary The Transmission Operator must maintain a plan to reestablish its electric system for perpetual review by the Regional Reliability Organization. The Compliance Monitor is required to retain audit data for three years, ensuring compliance with regulatory standards.

1.4. Additional Compliance Information Self-Certification: Each Transmission Operator shall annually self-certify to the Regional Reliability Organization that the following criteria have been met: - 1.4.1 The necessary operating instructi...

AI summary Transmission Operators must annually self-certify compliance with Regional Reliability Organization (RRO) criteria, including restoration plan procedures, training documentation, blackstart unit adequacy, and cranking path availability. Changes to restoration plans must be reported to the RRO.

1.2. Compliance Monitoring and Reset Time Frame One or more of the following methods will be used to assess compliance: - Self-certification (Conducted annually with submission according to schedule.) - Spot Check Audits (Conducted anytime...

AI summary Compliance will be assessed through self-certification, spot checks, periodic audits, and triggered investigations. The reset period for performance compliance is 12 months from the last non-compliance finding.

2. Levels of Non-Compliance: - 2.1. Level 1: Did not have one of the Transmission Operator restoration plans within the Reliability Coordinator's Area as specified in R1. - 2.2. Level 2: Not applicable. - 2.3. Level 3: There shall be a sep...

AI summary The document outlines four levels of non-compliance related to restoration plans and coordination requirements under the Reliability Coordinator's Area. Level 1-4 violations include missing plans, lack of coordination, and failure to monitor or execute restoration protocols as specified in R1-R6.

1.2. Compliance Monitoring Period and Reset Timeframe Periodic Review: Review and evaluate the plan for loss of primary control facility contingency as part of the three-year on-site audit process. The audit must include a demonstration of...

AI summary The regulatory proceeding outlines a three-year on-site audit process to review and evaluate the plan for loss of primary control facility contingency, requiring demonstration by the Reliability Coordinator, Transmission Operator, and Balancing Authority. The reset timeframe for compliance monitoring is set to one calendar year.

1.3. Data Retention The contingency plan for loss of primary control facility must be available for review at all times.

AI summary The contingency plan for loss of primary control facility must be available for review at all times, emphasizing the importance of data retention and accessibility in regulatory compliance.

2. Levels of Non-Compliance - 2.1. Level 1: NA - 2.2. Level 2: A contingency plan has been implemented and tested, but has not been tested in the past year or there are no records of shift operating personnel training. - 2.3. Level 3: A co...

AI summary The document outlines four levels of non-compliance related to contingency planning. Level 2 notes incomplete training records, Level 3 identifies missing plan elements (R1.1–R1.8), and Level 4 indicates no plan development. Each level reflects increasing severity in adherence to reliability and planning standards.

1.1. Compliance Monitoring Responsibility Compliance Monitor: Regional Reliability Organization.

AI summary The Regional Reliability Organization (RRO) is designated as the Compliance Monitor under the regulatory proceeding, tasked with overseeing adherence to reliability and operational standards in the electricity sector.

1.2. Compliance Monitoring Period and Reset Timeframe Current test results: to the Regional Reliability Organization and upon request to NERC (30 calendar days).

AI summary The compliance monitoring period requires submitting test results to the Regional Reliability Organization and NERC within 30 calendar days upon request. This timeframe outlines procedural requirements for reporting and adherence to reliability standards.

2. Levels of Non-Compliance - 2.1. Level 1: Startup and operation testing of each blackstart generating unit was performed, but the documentation was incomplete. - 2.2. Level 2: Not applicable. Adopted by NERC Board of Trustees: February 8...

AI summary The document outlines two levels of non-compliance. Level 1 notes incomplete documentation for blackstart generating unit testing, while Level 2 is not applicable. The standards were adopted by the NERC Board of Trustees in 2005.

1.3. Data Retention Evidence of the assessment of the reliability impacts of new facilities and their connections on the interconnected transmission systems: Three years.

AI summary The document specifies a three-year data retention period for evidence assessing the reliability impacts of new facilities and their connections on interconnected transmission systems.

5. Effective Dates: - 5.1. One calendar year from the date of adoption by the NERC Board of Trustees for Requirements 1 and 2. - 5.2. Sixty calendar days from the date of adoption by the NERC Board of Trustees for Requirements 3 and 4.

AI summary The effective dates for NERC requirements are set at one calendar year from adoption for Requirements 1 and 2, and sixty calendar days from adoption for Requirements 3 and 4, as determined by the NERC Board of Trustees.

- R3. The Transmission Owner shall report quarterly to its RRO, or the RRO's designee, sustained transmission line outages determined by the Transmission Owner to have been caused by vegetation. - R3.1. Multiple sustained outages on an ind...

AI summary The Transmission Owner must quarterly report sustained vegetation-caused transmission outages to the RRO, excluding those from natural disasters or human/animal activity. Reports must include outage details, categorization into 'grow-ins' or 'fall-ins', and countermeasures. Exceptions and required information are specified.

C. Measures - M1. The Transmission Owner has a documented TVMP, as identified in Requirement 1. - M1.1. The Transmission Owner has documentation that the Transmission Owner performed the vegetation inspections as identified in Requirement...

AI summary The document outlines compliance measures for vegetation management, documentation requirements, and reporting obligations under transmission and reliability standards. It specifies that the Transmission Owner must maintain documented processes for vegetation inspections, clearances, personnel qualifications, and outage reporting to the RRO and NERC.

1.2. Compliance Monitoring Period and Reset One calendar Year

AI summary The compliance monitoring period is defined as one calendar year, establishing a timeframe for assessing adherence to regulatory standards within the Nova Scotia Utility and Review Board proceedings.

2.1. Level 1: - 2.1.1. The TVMP was incomplete in one of the requirements specified in any subpart of Requirement 1, or; - 2.1.2. Documentation of the annual work plan, as specified in Requirement 2, was incomplete when presented to the Co...

AI summary Level 1 violations include incomplete TVMP requirements, incomplete annual work plan documentation during audits, and incomplete outage reports submitted by the RRO to NERC. These scenarios highlight gaps in compliance with specified regulatory standards.

2.2. Level 2: - 2.2.1. The TVMP was incomplete in two of the requirements specified in any subpart of Requirement 1, or; - 2.2.2. The Transmission Owner was unable to certify during its annual selfcertification that it fully implemented it...

AI summary The subsections outline scenarios where the Transmission Vegetation Management Plan (TVMP) or the Transmission Owner's compliance with annual requirements may be deficient, including incomplete plan requirements, failure to self-certify implementation, or reporting a Category 2 vegetation-related outage.

1.2. Compliance Monitoring Period and Reset Time Frame Each Transmission Owner and Generator Owner shall self-certify its compliance to the Compliance Monitor at least once every three years. New Transmission Owners and Generator Owners sh...

AI summary Transmission and Generator Owners must self-certify compliance every three years, with new entities undergoing on-site audits within their first year. The Compliance Monitor conducts audits every nine years and investigations on complaint. The Performance-Reset Period lasts 12 months after the last noncompliance finding.

1.2. Compliance Monitoring Period and Reset Time Frame Each Transmission Owner and Generator Owner shall self-certify its compliance to the Compliance Monitor annually. The Compliance Monitor may conduct a targeted audit once in each calen...

AI summary The Compliance Monitor requires annual self-certification from Transmission and Generator Owners, with annual targeted audits and complaint-driven investigations. The Performance-Reset Period lasts twelve months following the last noncompliance finding.

Standard FAC-010-2 — System Operating Limits Methodology for the Planning Horizon - M1. The Planning Authority's SOL Methodology shall address all of the items listed in Requirement 1 through Requirement 3. - M2. The Planning Authority sha...

AI summary The Planning Authority's System Operating Limits (SOL) Methodology must address specified requirements, provide evidence of methodology issuance, and respond to technical comments within 45 days. Compliance with these procedural mandates ensures adherence to regulatory standards for planning horizon SOL methodologies.

1. Compliance Monitoring Process

AI summary The section outlines the compliance monitoring process, likely involving regulatory oversight and adherence to standards such as CIP and FAC. It may discuss roles of entities like NSUARB and NSPI in ensuring compliance with reliability and operational protocols.

1.1. Compliance Monitoring Responsibility Regional Reliability Organization

AI summary This section outlines the responsibility for compliance monitoring, referencing the Regional Reliability Organization (RRO) as a key entity involved in ensuring adherence to regulatory standards.

1.2. Compliance Monitoring Period and Reset Time Frame Each Planning Authority shall self-certify its compliance to the Compliance Monitor at least once every three years. New Planning Authorities shall demonstrate compliance through an on...

AI summary Planning Authorities must self-certify compliance every three years, with new authorities undergoing on-site audits in their first year. The Compliance Monitor conducts audits every nine years and investigates complaints. The Performance-Reset Period lasts twelve months after the last non-compliance incident.

1.3. Data Retention The Planning Authority shall keep all superseded portions to its SOL Methodology for 12 months beyond the date of the change in that methodology and shall keep all documented comments on its SOL Methodology and associat...

AI summary The Planning Authority must retain superseded SOL Methodology portions for 12 months and documented comments for three years. Non-compliant entities must retain non-compliance information until compliance is achieved. The Compliance Monitor retains audit records.

1.4. Additional Compliance Information The Planning Authority shall make the following available for inspection during an onsite audit by the Compliance Monitor or within 15 business days of a request as part of an investigation upon compl...

AI summary The Planning Authority must provide access to SOL Methodology documents, including technical reviews, superseded portions from the past 12 months, and evidence of methodology distribution to required entities during audits or upon request within 15 business days.

2. Levels of Non-Compliance for Western Interconnection: (To be replaced with VSLs once developed and approved by WECC) - 2.1. Level 1: There shall be a level one non-compliance if either of the following conditions exists: - 2.1.1 The SOL...

AI summary Defines Level 1 non-compliance for Western Interconnection if SOL Methodology lacks a statement on not exceeding Facility Ratings, pending VSLs from WECC.

Standard FAC-010-2 — System Operating Limits Methodology for the Planning Horizon - 2.1.2 No evidence of responses to a recipient's comments on the SOL Methodology. - 2.2. Level 2: The SOL Methodology did not include a requirement to addre...

AI summary The document outlines non-compliance levels for the System Operating Limits (SOL) Methodology, including failure to address required elements, missing contingency evaluations, and incomplete distribution. Levels 2-4 detail specific deficiencies in the methodology's scope and implementation, adopted by the Board of Trustees in 2009.

3.Violation Severity Levels: ire Re t q m en u Lo er w M de te o ra ig H h Se ve re

AI summary The section outlines different levels of violation severity, categorizing them into lower, moderate, high, and severe. This classification is likely used for regulatory compliance and enforcement purposes.

2. Levels of Non-Compliance - 2.1. Level 1: Not applicable. - 2.2. Level 2: Not all requested Transfer Capabilities were provided in accordance with their respective schedules. - 2.3. Level 3: Transfer Capabilities were not developed consi...

AI summary The document outlines four levels of non-compliance related to Transfer Capabilities. Level 2 involves partial non-delivery on schedule, Level 3 refers to methodology inconsistencies, and Level 4 indicates complete failure to deliver. Level 1 is not applicable, emphasizing structured compliance tiers for transfer capability adherence.

2. Levels of Non-Compliance for Sink Balancing Authorities: - 2.1. Level 1: One instance of not submitting Arranged Interchange to the Interchange Authority as specified in R2.1 and R2.2. - 2.2. Level 2: Two instances of not submitting Arr...

AI summary The document outlines four levels of non-compliance for Sink Balancing Authorities based on the number of instances where Arranged Interchange was not submitted to the Interchange Authority as required by R2.1 and R2.2, ranging from one instance (Level 1) to four or more instances (Level 4).

3. Levels of Non-Compliance for Purchasing-Selling Entities that Serve Load: 3.1. Level 1: One instance of not submitting Arranged Interchange to the Interchange Authority as specified in R1.

AI summary This section outlines Level 1 non-compliance for purchasing-selling entities serving load, defined as a single instance of failing to submit Arranged Interchange to the Interchange Authority as required by R1.

Standard INT-001-3 — Interchange Information - 3.2. Level 2: Two instances of not submitting Arranged Interchange to the Interchange Authority as specified in R1. - 3.3. Level 3: Three instances of not submitting Arranged Interchange to th...

AI summary The document outlines non-compliance levels (Level 2-4) based on the number of instances where Arranged Interchange was not submitted to the Interchange Authority as required by R1, with increasing severity for four or more instances.

2. Levels of Non-Compliance for Balancing Authorities: - 2.1. Level 1: There shall be a separate Level 1 non-compliance, if either of the following conditions exists: - 2.1.1 One instance of entering a schedule into its ACE equation withou...

AI summary The document outlines four levels of non-compliance for Balancing Authorities, defined by the number of instances of specific violations: (1) entering schedules into ACE equations without confirmation, and (2) failing to coordinate Interchange Schedules with HVDC tie Transmission Operators. Levels escalate with increasing instance counts, adopted by the Board of Trustees in 2006.

E. Regional Differences - 1. MISO Scheduling Agent Waiver dated November 21, 2002. - 2. MISO Enhanced Scheduling Agent Waiver dated July 16, 2003. - 3. MISO Energy Flow Information Waiver dated July 16, 2003.

AI summary The section lists three MISO waivers related to scheduling and energy flow information, dated 2002 and 2003, indicating regional differences in regulatory compliance or operational procedures.

1.2. Compliance Monitoring Period and Reset Time Frame The Performance-Reset Period shall be twelve months from the last noncompliance to Requirement 1.

AI summary The Performance-Reset Period is defined as a 12-month duration beginning from the last instance of noncompliance with Requirement 1, establishing a timeframe for monitoring and addressing compliance issues.

1.4. Additional Compliance Information Each Interchange Authority shall demonstrate compliance to the Compliance Monitor within the first year that this standard becomes effective or the first year the entity commences operation by self-ce...

AI summary The section outlines compliance requirements for Interchange Authorities, including initial self-certification, periodic audits, spot checks, and complaint resolution processes. Compliance Monitor inspections may involve data reviews and investigations into specific complaints within 60 days of incidents.

2. Levels of Non-Compliance - 2.1. Level 1: One occurrence1 of not distributing information to all involved reliability entities as described in R1. - 2.2. Level 2: Two occurrences1 of not distributing information to all involved reliabili...

AI summary The document outlines four levels of non-compliance based on the number of occurrences of failing to distribute information to reliability entities as per R1. Levels escalate from one occurrence (Level 1) to four or more occurrences or lack of evidence (Level 4).

Version History Version Date Action Change Tracking 1 May 2, 2006 Approved by BOT New 1 This does not include instances of not distributing information due to extenuating circumstances approved by the Compliance Monitor.

AI summary The document's version history notes approval by the Board of Trustees (BOT) on May 2, 2006. A footnote clarifies that exceptions to information distribution requirements, approved by the Compliance Monitor, are excluded from tracking.

D. Compliance - 1. Compliance Monitoring Process - 1.1. Compliance Monitoring Responsibility Regional Reliability Organization. - 1.2. Compliance Monitoring Period and Reset Time Frame The Performance-Reset Period shall be twelve months fr...

AI summary The compliance monitoring process assigns responsibility to the Regional Reliability Organization. The Performance-Reset Period lasts 12 months from the last noncompliance to Requirement 1. Data retention requirements specify 90 days for Balancing Authority and Transmission Service Provider, and three years for the Compliance Monitor.

1.4. Additional Compliance Information The Balancing Authority and Transmission Service Provider shall demonstrate compliance to the Compliance Monitor within the first year that this standard becomes effective or the first year the entity...

AI summary The Balancing Authority and Transmission Service Provider must self-certify compliance with reliability standards initially, followed by audits and spot checks. Complaints must be addressed within 60 days, with data and logs provided for inspection. Compliance is verified through audits, spot checks, and complaint evaluations.

2. Levels of Non-Compliance - 2.1. Level 1: One occurrence1 of not responding to the Interchange Authority as described in R1. - 2.2. Level 2: Two occurrences1 of not responding to the Interchange Authority as described in R1. 1 This does...

AI summary This section defines two levels of non-compliance based on the number of occurrences (one or two) of failing to respond to the Interchange Authority as outlined in R1. Extenuating circumstances approved by the Compliance Monitor exclude such instances from non-compliance.

Standard INT-006-2 — Response to Interchange Authority - 2.3. Level 3: Three occurrences1 of not responding to the Interchange Authority as described in R1. - 2.4. Level 4: Four or more occurrences 1 of not responding to the Interchange Au...

AI summary The text outlines Level 3 and Level 4 violations under Standard INT-006-2, detailing non-response to the Interchange Authority. Level 3 involves three occurrences, while Level 4 includes four or more occurrences or lack of evidence, referencing R1.

A B C D If Actual Arranged Interchange (RFI) is Submitted IA Makes Initial Distribution of Arranged Interchange BA and TSP Conduct Reliability Assessments IA Verifies Reliability Data Complete IA Compiles and Distributes Status BA Prepares...

AI summary The document outlines timelines for interchange confirmation and reliability assessments in Nova Scotia's regulatory process. It specifies response time thresholds for entities like IA (Interchange Authority), BA (Balancing Authority), and TSP (Transmission Service Provider) to ensure reliability before implementing arranged interchange, referencing standard INT-007-1.

1.2. Compliance Monitoring Period and Reset Time Frame The Performance-Reset Period shall be twelve months from the last noncompliance to Requirement 1.

AI summary The Performance-Reset Period is defined as a 12-month duration starting from the last instance of noncompliance with Requirement 1, establishing a timeframe for monitoring and addressing regulatory adherence.

1.4. Additional Compliance Information Each Interchange Authority shall demonstrate compliance to the Compliance Monitor within the first year that this standard becomes effective or the first year the entity commences operation by self-ce...

AI summary This section outlines compliance requirements for Interchange Authorities, including self-certification, audit schedules (every three years, annual audits for noncompliant entities), spot checks, and complaint resolution processes. Compliance Monitor access to data logs and system records is mandated for verification.

Standard INT-008-2 — Interchange Authority Distributes Status - 2.2. Level 2: Two occurrences1 of not distributing final status and information as described in R1. - 2.3. Level 3: Three occurrences1 of not distributing final status and inf...

AI summary The text outlines non-compliance levels (Level 2 to Level 4) related to the Interchange Authority's failure to distribute final status and information as required by R1, with increasing severity based on the number of occurrences or lack of evidence.

1.3. Data Retention Each Regional Reliability Organization shall have its current, in-force document for Measure 1. Each Reliability Coordinator shall have its current, in-force documents or the latest copy of a record as evidence of compl...

AI summary The section outlines data retention requirements for entities in the electricity sector, specifying periods for retaining compliance documents and evidence. Regional Reliability Organizations, Reliability Coordinators, and others must keep records for varying durations, with non-compliance data retained longer. The Compliance Monitor retains audit reports and compliance records.

2. Levels of Non-Compliance: for a Regional Reliability Organization: - 2.1. Level 1: Not applicable - 2.2. Level 2: Not applicable - 2.3. Level 3: Not applicable - 2.4. Level 4: Does not have evidence it established one or more Reliabilit...

AI summary The document outlines non-compliance Level 4 for a Regional Reliability Organization, noting the absence of evidence that Reliability Coordinators were established to assess transmission reliability and coordinate emergency operations as required.

3. Levels of Non-Compliance for a Reliability Coordinator: - 3.1. Level 1: Not applicable. - 3.2. Level 2: Not applicable. - 3.3. Level 3: Not applicable . - 3.4. Level 4: There shall be a separate Level 4 non-compliance for every one of t...

AI summary The document outlines non-compliance levels for Reliability Coordinators and other entities, with Level 4 detailing specific violations such as lacking authority, formal agreements, and adherence to NERC standards. Similar structures apply to Transmission Operators and Balancing Authorities.

2. Levels of Non-Compliance for a Reliability Coordinator - 2.1. Level 1: Not applicable. - 2.2. Level 2: Did not confirm that the network used for data exchange to other Reliability Coordinators is secure as specified in R3. - 2.3. Level...

AI summary The document outlines four levels of non-compliance for a Reliability Coordinator, detailing violations related to data security, reliability coordination tasks, communication facilities, and monitoring procedures. Each level corresponds to specific regulatory requirements (e.g., R3, R7, R9).

2. Levels of Non-Compliance 2.1. Level 1: System studies were not conducted for one day in a calendar month and/or the action plans were not developed to maintain transmission loading within acceptable limits for potential interface and ot...

AI summary The document outlines four levels of non-compliance based on missed system studies and inadequate action plans to maintain transmission loading within acceptable limits for IROL violations. Levels escalate with increasing days of missed studies (1–4 days, 4–5 days, etc.).

3. Levels of Non-Compliance for a Reliability Coordinator: - 3.1. Level 1: Not applicable. - 3.2. Level 2: Did not make Interchange Transaction information available to all other Reliability Coordinators in the Interconnection. (Requiremen...

AI summary The document outlines non-compliance levels for Reliability Coordinators, detailing violations related to information sharing, coordination with Balancing Authorities, and adherence to standards like DCS, CPS, and SOL. Levels 2–4 escalate from minor to severe infractions, including failure to address GMD events, delay in emergency actions, and inadequate monitoring.

4. Levels of Non-Compliance for a Transmission Service Provider - 4.1. Level 1: Not applicable. - 4.2. Level 2: Not applicable. - 4.3. Level 3: Not applicable. - 4.4. Level 4: There shall be a separate Level 4 non-compliance, for every one...

AI summary Level 4 non-compliance applies to transmission service providers violating specific operational requirements, including failing to use the most limiting parameter when limits differ and not adhering to System Operating Limits (SOLs) or Interconnection Reliability Operating Limits (IROLs) as defined in filed tariffs and regional processes.

2. Violation Severity Levels - 2.1. Lower. There shall be a lower violation severity level if any of the following conditions exist: - 2.1.1 For each TLR in the Eastern Interconnection, the Reliability Coordinator violates one (1) requirem...

AI summary The document outlines four violation severity levels (Lower, Moderate, High, Severe) for reliability violations in the Eastern and Western Interconnections. Conditions include non-compliance with Interconnection-wide procedures, improper congestion management, and failure to follow mitigation protocols by Reliability Coordinators and Balancing Authorities.

to the initiating Reliability Coordinator. Causes of questionable IDC results may include: - Missing Interchange Transactions that are known to contribute to the Constraint. - Significant change in transmission system topology. - TDF matri...

AI summary The text outlines procedures for addressing questionable IDC results in TLR events, including curtailment exemptions and logging requirements. It details causes and impacts of such results and mandates coordination among Reliability Coordinators and NERC compliance.

B. Requirements - R1. The Reliability Coordinator shall have Operating Procedures, Processes, or Plans in place for activities that require notification, exchange of information or coordination of actions with one or more other Reliability...

AI summary The requirements outline procedures for Reliability Coordinators to ensure interconnection reliability through communication protocols, outage management, voltage control, and coordinated action plans. Procedures must be agreed upon, distributed, and periodically reviewed, with specific focus on addressing energy shortages, unplanned outages, and adverse reliability impacts.

C. Measures - M1. The Reliability Coordinator's System Operators shall have available for Real-time use, the latest approved version of Operating Procedures, Processes, or Plans that require notifications, information exchange or the coord...

AI summary The document outlines measures requiring Reliability Coordinators to maintain up-to-date operating procedures for real-time use, ensure agreement and distribution among coordinators, include version control, and conduct reviews within three years. These measures aim to standardize coordination, communication, and reliability management across systems.

D. Compliance

AI summary The section heading 'D. Compliance' indicates a regulatory proceeding discussion focused on compliance requirements, though no detailed content is provided in the text chunk. Further analysis would require additional context from the proceeding document.

1. Compliance Monitoring Process

AI summary The section outlines the compliance monitoring process, likely involving regulatory oversight and adherence to standards such as CIP and FAC. It may discuss roles of entities like NSUARB and NSPI in ensuring compliance with reliability and operational protocols.

1.1. Compliance Monitoring Responsibility Regional Reliability Organization

AI summary This section outlines the responsibility for compliance monitoring, referencing the Regional Reliability Organization (RRO) as a key entity involved in ensuring adherence to regulatory standards.

1.2. Compliance Monitoring Period and Reset Time Frame The Performance-Reset Period shall be one calendar year.

AI summary The regulatory proceeding establishes a one-year calendar period for the Performance-Reset Period, which governs compliance monitoring and reset timelines for regulatory obligations.

1.3. Data Retention The Reliability Coordinator shall keep documentation for the prior calendar year and the current calendar year. The Compliance Monitor shall keep compliance data for a minimum of three years or until the Reliability Coo...

AI summary The Reliability Coordinator must retain documentation for two calendar years, while the Compliance Monitor must keep compliance data for three years or until full compliance is achieved, whichever is longer.

1.4. Additional Compliance Information The Reliability Coordinator shall demonstrate compliance through self-certification submitted to its Compliance Monitor annually. The Compliance Monitor shall also use a scheduled on-site review at le...

AI summary The Reliability Coordinator must comply via annual self-certification and periodic on-site reviews by the Compliance Monitor. Investigations into complaints must occur within 30 days of discovery and conclude within 45 days. Documents related to interconnection reliability procedures and their distribution must be available for audit or inspection.

2. Levels of Non-Compliance - 2.1. Level 1: There shall be a level one non-compliance if either of the following conditions is present: - 2.1.1 The latest versions of Operating Procedures, Processes, or Plans (identified through self-certi...

AI summary The document outlines four levels of non-compliance related to reliability standards, specifying conditions for each level. Level 1 requires version control and distribution lists for operating procedures, while higher levels address distribution failures, unavailability, and omission of required topics, with Level 4 being non-applicable. Reliability Standard IRO-014 R1 is referenced as a critical benchmark.

1.3. Data Retention For the Regional Reliability Organization and Planning Authority: Current version of the documentation. For the Compliance Monitor: Three years of audit information.

AI summary The document outlines data retention requirements for the Regional Reliability Organization and Planning Authority (current documentation) and the Compliance Monitor (three years of audit information). These policies govern how long specific records must be maintained under regulatory oversight.

1.4. Additional Compliance Information The Regional Reliability Organization and Planning Authority shall each demonstrate compliance through self-certification or audit (periodic, as part of targeted monitoring or initiated by complaint o...

AI summary The Regional Reliability Organization and Planning Authority must demonstrate compliance through self-certification or audit, as determined by the Compliance Monitor. Methods include periodic audits, targeted monitoring, or audits triggered by complaints or events.

2. Levels of Non-Compliance - 2.1. Level 1: Documentation does not address completeness and double counting of customer data. - 2.2. Level 2: Documentation did not address one of the three types of data required in R1 (Demand data, Net Ene...

AI summary The document outlines four levels of non-compliance related to documentation requirements, focusing on incomplete or missing data types (Demand data, Net Energy for Load data, controllable DSM data) and distribution failures. Each level escalates in severity from documentation gaps to complete absence of required evidence.

2. Levels of Non-Compliance - 2.1. Level 1: Information for Reliability Standard MOD-018-0 item R1.1 or R1.2 was not provided. - 2.2. Level 2: Information for Reliability Standards MOD-018-0 items R1.1 and R1.2 was not provided. - 2.3. Lev...

AI summary The document outlines four levels of non-compliance related to Reliability Standard MOD-018-0. Levels 1 and 2 involve missing information for specific items (R1.1 and R1.2), while Levels 3 and 4 are not applicable. This categorization addresses gaps in reporting requirements under the standard.

Standard MOD-019-0.1 — Forecasts of Interruptible Demands and DCLM Data None specified. 1.4. Additional Compliance Information None.

AI summary The document indicates no specific information was provided regarding compliance with MOD-019-0.1, forecasts of interruptible demands, or DCLM data, with additional compliance details also unspecified.

Standard MOD-020-0 — Providing Interruptible Demands and DCLM Data - 2.3. Level 3: Not applicable. - 2.4. Level 4: Interruptible Demands and DCLM data were not provided to Reliability Coordinators, Balancing Authorities, and Transmission O...

AI summary The document outlines Standard MOD-020-0, which addresses the provision of Interruptible Demands and DCLM data. Level 3 is not applicable, while Level 4 indicates that such data were not provided to Reliability Coordinators, Balancing Authorities, and Transmission Operators, potentially impacting system reliability and compliance.

1.3. Compliance Monitoring and Enforcement Processes: Compliance Audits Self-Certifications Spot Checking Compliance Violation Investigations Self-Reporting Complaints

AI summary Section 1.3 outlines compliance monitoring and enforcement processes, including self-certifications, spot checks, audits, violation investigations, self-reporting, and complaint handling mechanisms within regulatory proceedings.

2. Violation Severity Levels - 2.1. Lower: Agreement(s) exist per this standard and NPIRs were identified and implemented, but documentation described in M1-M8 was not provided. - 2.2. Moderate: Agreement(s) exist per R2 and NPIRs were ide...

AI summary The document outlines four violation severity levels (Lower, Moderate, High, Severe) based on compliance with standards, documentation requirements (M1-M8), and implementation of Non-Physical Infrastructure Risks (NPIRs). Each level corresponds to different degrees of non-compliance with regulatory agreements and requirements.

E. Regional Differences The design basis for Canadian (CANDU) NPPs does not result in the same licensing requirements as U.S. NPPs. NRC design criteria specifies that in addition to emergency on-site electrical power, electrical power from...

AI summary The text highlights regional differences in nuclear power plant (NPP) licensing requirements between Canada and the U.S., noting that U.S. NRC regulations mandate grid power for safe shutdown during emergencies, while Canadian CANDU NPPs lack equivalent requirements for Station Blackout (SBO) or coping times. It defines NPLR as statutorily mandated safety requirements for nuclear plants during electrical disturbances.

Standard NUC-001-2 — Nuclear Plant Interface Coordination and footnote 1; modifications to bring compliance elements into conformance with the latest version of the ERO Rules of Procedure. 2 August 5, 2009 Adopted by Board of Trustees Revi...

AI summary This section introduces Standard NUC-001-2, which focuses on nuclear plant interface coordination. It outlines the adoption and revision history of the standard by the Board of Trustees and FERC, highlighting updates and compliance with the ERO Rules of Procedure.

A. Introduction 1. Title: Operating Personnel Training 2. Number: PER-002-0 3. Purpose: Each Transmission Operator and Balancing Authority must provide their personnel with a coordinated training program that will ensure reliable system op...

AI summary The PER-002-0 standard mandates that Transmission Operators and Balancing Authorities implement coordinated training programs to ensure reliable system operations. This requirement emphasizes the importance of personnel training in maintaining grid reliability and adherence to regulatory standards.

B. Requirements - R1. Each Transmission Operator and Balancing Authority shall be staffed with adequately trained operating personnel. - R2. Each Transmission Operator and Balancing Authority shall have a training program for all operating...

AI summary The requirements mandate that Transmission Operators and Balancing Authorities must staff trained personnel and implement training programs aligned with NERC and RRO standards, including simulations and drills for emergency scenarios.

C. Measures - M1. Each Transmission Operator, Balancing Authority, and Reliability Coordinator shall have NERC-certified operating personnel on shift in required positions at all times with the following exceptions: - M1.1 While in trainin...

AI summary The measures require NERC-certified personnel for Transmission Operators, Balancing Authorities, and Reliability Coordinators, with exceptions for trainees and real-time emergencies. Trainees must work under supervision, and emergency control transfers to backup centers are excluded from non-compliance calculations for up to four hours.

D. Compliance

AI summary The section heading 'D. Compliance' indicates a regulatory proceeding discussion focused on compliance requirements, though no detailed content is provided in the text chunk. Further analysis would require additional context from the proceeding document.

1. Compliance Monitoring Process Periodic Review: An on-site review will be conducted every three years. Staffing schedules and certification numbers will be compared to ensure that positions that require NERCcertified operating personnel...

AI summary The compliance monitoring process involves periodic on-site reviews every three years to ensure staffing and certification requirements are met, with violations reported to the Regional Reliability Organization and NERC.

1.1. Compliance Monitoring Responsibility Regional Reliability Organization. Adopted by NERC Board of Trustees: February 8, 2005 1 of 2

AI summary The section outlines compliance monitoring responsibility under the Regional Reliability Organization, adopted by NERC's Board of Trustees on February 8, 2005.

1.2. Compliance Monitoring Period and Reset Timeframe One calendar month without a violation.

AI summary The compliance monitoring period is defined as one calendar month without any violations, establishing a timeframe for assessing adherence to regulatory standards.

1.3. Data Retention Present calendar year plus previous calendar year staffing plan.

AI summary The document specifies the need to retain staffing plans for the current and previous calendar years, ensuring data availability for regulatory review and analysis.

2. Levels of Non-Compliance - 2.1. Level 1: The Transmission Operator, Balancing Authority, or Reliability Coordinator did not meet the requirement for a total time greater than 0 hours and up to 12 hours during a one calendar month period...

AI summary The document outlines four levels of non-compliance based on the number of hours that Transmission Operators, Balancing Authorities, and Reliability Coordinators fail to meet staffing plan requirements. Each level corresponds to increasing time thresholds (0-12, 12-36, etc.), indicating the severity of non-compliance over a one-month period.

2. Levels of Non-Compliance for a Reliability Coordinator - 2.1. Level 1: Not applicable. - 2.2. Level 2: Not applicable. - 2.3. Level 3: Not applicable. - 2.4. Level 4: There shall be a separate Level 4 non-compliance, for every one of th...

AI summary The document outlines Level 4 non-compliance criteria for Reliability Coordinators, requiring specific training, understanding of regional operations, and knowledge of Balancing Authorities and operators. These requirements were adopted by the Board of Trustees in 2006.

2. Levels of Non-Compliance for Generator Operators: - 2.1. Level 1: Not applicable. - 2.2. Level 2 : Not applicable. - 2.3. Level 3: Not applicable. - 2.4. Level 4: Failed to provide evidence of coordination when installing new protective...

AI summary The document outlines non-compliance levels for generator operators, with Level 4 specifically noting a failure to provide evidence of coordination during protective system installations and changes with the Transmission Operator and Host Balancing Authority as required by R3.1.

3. Levels of Non-Compliance for Transmission Operators: - 3.1. Level 1: Not applicable. - 3.2. Level 2 : Not applicable. - 3.3. Level 3: Not applicable. - 3.4. Level 4: There shall be a separate Level 4 non-compliance, for every one of the...

AI summary The document outlines non-compliance levels for transmission operators, with Level 4 specifically addressing failures to coordinate protective system installations with neighboring operators and Balancing Authorities, as well as inadequate monitoring of Special Protection Systems. These violations trigger Level 4 non-compliance under rules R3.2 and R6.

4. Levels of Non-Compliance for Balancing Authorities: - 4.1. Level 1: Not applicable. - 4.2. Level 2 : Not applicable. - 4.3. Level 3: Not applicable. - 4.4. Level 4: Did not monitor the status of each Special Protection System, or did no...

AI summary The document outlines non-compliance levels for Balancing Authorities, with Level 4 requiring monitoring of Special Protection Systems (SPS) and notifying Transmission Operators and Balancing Authorities of changes as per R6. Higher levels involve more severe non-compliance actions.

B. Requirements - R1. The Transmission Owner and any Distribution Provider that owns a transmission Protection System shall each analyze its transmission Protection System Misoperations and shall develop and implement a Corrective Action P...

AI summary The requirements mandate analysis of protection system misoperations and development of corrective action plans by transmission owners, distribution providers, and generator owners, in accordance with PRC-003 R1 procedures.

1.4. Additional Compliance Information The Transmission Owner, and any Distribution Provider that owns a transmission Protection System and the Generator Owner shall demonstrate compliance through selfcertification or audit (periodic, as p...

AI summary The Transmission Owner, Distribution Provider, and Generator Owner must demonstrate compliance through self-certification or audits, determined by the Compliance Monitor. Compliance methods include periodic audits, targeted monitoring, or responses to complaints/events.

2. Levels of Non-Compliance for Transmission Owners and Distribution Providers that own a Transmission Protection System: - 2.1. Level 1: Documentation of Misoperations is complete according to PRC-004 R1, but documentation of Corrective A...

AI summary The document outlines four levels of non-compliance for transmission owners and distribution providers regarding their transmission protection systems. Levels range from incomplete documentation of corrective actions (Level 1) to no documentation or analysis of misoperations (Level 4), with references to PRC-004 R1 and the Regional Reliability Organization's requirements.

3. Levels of Non-Compliance for Generator Owners - 3.1. Level 1: Documentation of Misoperations is complete according to PRC-004 R2, but documentation of Corrective Action Plans is incomplete. - 3.2. Level 2: Documentation of Misoperations...

AI summary The document outlines four levels of non-compliance for generator owners, focusing on documentation of misoperations and corrective action plans under PRC-004 R2 and R3. Levels escalate from incomplete documentation to no analysis or reporting, impacting system reliability and regulatory adherence.

B. Requirements - R1. The Transmission Owner and Distribution Provider with a UFLS program (as required by its Regional Reliability Organization) shall have a UFLS equipment maintenance and testing program in place. This UFLS equipment mai...

AI summary The requirements mandate that Transmission Owners and Distribution Providers with UFLS programs implement maintenance and testing protocols, including equipment identification, testing schedules, and reporting to the Regional Reliability Organization and NERC within 30 days. Compliance with these standards ensures system reliability and adherence to regional and federal regulations.

4. Applicability: - 4.1. Transmission Owner that owns an SPS - 4.2. Generator Owner that owns an SPS - 4.3. Distribution Provider that owns an SPS 5. Effective Date: April 1, 2005

AI summary The document outlines the applicability of regulations to entities owning a Special Protection System (SPS), including Transmission Owners, Generator Owners, and Distribution Providers, with an effective date of April 1, 2005.

Standard PRC-016-0.1 — Special Protection System Misoperations

AI summary This regulatory proceeding addresses Standard PRC-016-0.1, focusing on preventing misoperations of Special Protection Systems (SPS) to ensure grid reliability. Nova Scotia Utility and Review Board (NSUARB) and Nova Scotia Power Incorporated (NSPI) are key entities involved in enforcing compliance with protection reliability coordination standards.

4. Applicability - 4.1. Transmission Owner. - 4.2. Generator Owner. - 5. Effective Dates: Phased in over four years after BOT adoption: Requirements 1 and 2: - − 50% compliant two years after initial issuance of regional requirements per R...

AI summary The document outlines compliance requirements for Transmission and Generator Owners under PRC-002, phased over four years post-BOT adoption. Compliance milestones include 50% adherence after two years, 75% after three, and full compliance after four years for Requirements 1-2, with earlier deadlines for Requirements 3-6 tied to DME installation timelines.

Standard PRC-018-1 — Disturbance Monitoring Equipment Installation and Data Reporting - 2.3.2 Recorded Disturbance data that meets all Regional Reliability Organization's Disturbance data requirements (in accordance with R4) was provided f...

AI summary The document outlines non-compliance with Disturbance Monitoring Equipment (DME) installation and data reporting requirements under PRC-018-1. Key issues include incomplete documentation of maintenance programs, insufficient DME coverage (70-80% of locations), and failure to meet Regional Reliability Organization (RRO) standards for installation and data collection. Level 4 non-compliance is triggered by missing DMEs, incomplete data, or absent maintenance records.

2. Levels of Non-Compliance for a Balancing Authority: - 2.1. Level 1: Not applicable. - 2.2. Level 2: Not applicable. - 2.3. Level 3: Not applicable. - 2.4. Level 4: There shall be a separate Level 4 non-compliance, for every one of the f...

AI summary The document outlines non-compliance levels for a Balancing Authority, with Level 4 specifically addressing violations of reliability directives by Reliability Coordinators/Transmission Operators and failure to provide emergency assistance as required by R6.

3. Levels of Non-Compliance for a Transmission Operator - 3.1. Level 1: Not applicable. - 3.2. Level 2: Not applicable. - 3.3. Level 3: Not applicable. - 3.4. Level 4: There shall be a separate Level 4 non-compliance, for every one of the...

AI summary The document outlines Level 4 non-compliance for Transmission Operators, detailing specific violations such as lack of documented authority, failure to act during emergencies, non-compliance with reliability directives, and improper removal of Bulk Electric System facilities. These violations trigger formal non-compliance actions.

4. Levels of Non-Compliance for a Generator Operator: Effective Date: January 1, 2007 - 4.1. Level 1: Not applicable. - 4.2. Level 2: Not applicable. - 4.3. Level 3: Not applicable. - 4.4. Level 4: There shall be a separate Level 4 non-com...

AI summary The document outlines four levels of non-compliance for generator operators, with Level 4 detailing specific violations including failure to follow reliability directives, refusing emergency assistance, and improperly removing Bulk Electric System (BES) facilities from service. Effective January 1, 2007, these levels define consequences for non-adherence to reliability and operational standards.

5. Levels of Non-Compliance for a Distribution Provider or Load Serving Entity - 5.1. Level 1: Not applicable. - 5.2. Level 2: Not applicable. - 5.3. Level 3: Not applicable - 5.4. Level 4: Did not comply with a Transmission Operator's rel...

AI summary The document outlines four levels of non-compliance for distribution providers or load serving entities, with Level 4 specifically addressing failure to comply with transmission reliability directives or notify the Transmission Operator of inability to perform, as specified in R4.

3. Levels of Non-Compliance for Transmission Operators - 3.1. Level 1: Did not use uniform line identifiers when referring to transmission facilities of an interconnected network as specified in R18. - 3.2. Level 2: Not applicable. - 3.3....

AI summary The document outlines four levels of non-compliance for transmission operators, detailing specific violations such as failure to use uniform line identifiers, update studies, maintain current-day plans, and notify Balancing Authorities. These levels reference regulatory requirements (R1, R5, R6, R10, R11, R16) related to system reliability and operational standards.

4. Levels of Non-Compliance for Generator Operators: - 4.1. Level 1: Did not use uniform line identifiers when referring to transmission facilities of an interconnected network as specified in R18. - 4.2. Level 2: Not applicable. - 4.3. Le...

AI summary The document outlines four levels of non-compliance for generator operators, with Level 1 requiring uniform line identifiers for transmission facilities and Level 4 addressing violations in capability verification, notifications to authorities, and output forecasting. Levels 2 and 3 are not applicable.

5. Levels of Non-Compliance for Transmission Service Providers and Load-serving Entities: 5.1. Level 1: Did not use uniform line identifiers when referring to transmission facilities of an interconnected network as specified in R18. Adopte...

AI summary Level 1 non-compliance involves failure to use uniform line identifiers for transmission facilities as specified in R18. This standard was adopted by the Board of Trustees on February 10, 2009, and applies to transmission service providers and load-serving entities.

Response to Question #2 The requirement does not mandate a particular type of review or study. The review or study may be based on complex computer studies or a manual reasonability review of previously existing study results. The requirem...

AI summary The requirement allows flexibility in conducting reviews or studies, which may be computer-based or manual, to ensure the Transmission Operator remains sensitive to ongoing or emerging issues. No specific method is mandated.

Question #3 Does the term, "to determine SOLs" as used in the first sentence of Requirement R11 mean the "determination of system operating limits" or does it mean the "identification of potential SOL violations?"

AI summary The question seeks clarification on whether 'to determine SOLs' in Requirement R11 refers to establishing system operating limits or identifying potential violations. This hinges on interpreting the term 'determine' within the context of regulatory standards like FAC-014-2, which emphasizes establishing and communicating SOLs.

4. Applicability - 4.1. Generator Operators. - 4.2. Transmission Operators. - 4.3. Balancing Authorities. - 4.4. Reliability Coordinators. 5. Effective Date: April 1, 2005

AI summary Section 4 outlines the applicability of regulations to Generator Operators, Transmission Operators, Balancing Authorities, and Reliability Coordinators. The effective date is set for April 1, 2005, indicating when these requirements become enforceable.

D. Compliance

AI summary The section heading 'D. Compliance' indicates a regulatory proceeding discussion focused on compliance requirements, though no detailed content is provided in the text chunk. Further analysis would require additional context from the proceeding document.

1. Compliance Monitoring Process Each Regional Reliability Organization shall conduct a review every three years to ensure that each responsible entity has a process in place to provide planned generator and/or bulk transmission outage inf...

AI summary The document outlines a three-year compliance review process by Regional Reliability Organizations (RROs) to ensure entities provide outage information to Reliability Coordinators and neighboring operators. Investigations may be initiated by RROs or NERC upon complaints, with notifications required within 60 days. Investigation methods are determined by NERC/RRO.

1.1. Compliance Monitoring Responsibility A Reliability Coordinator makes a request for an outage to "not be taken" because of a reliability impact on the grid and the outage is still taken. The Reliability Coordinator must provide all its...

AI summary Reliability Coordinators must document and report outages with reliability impacts within three business days to the Regional Reliability Organization (RRO), which then reports compliance and violations to NERC via its Compliance Reporting process.

1.2. Compliance Monitoring Period and Reset Timeframe One calendar year without a violation from the time of the violation.

AI summary The compliance monitoring period is defined as one calendar year without any violations from the time of the violation, establishing a reset timeframe for regulatory compliance.

2. Levels of Non-Compliance - 2.1. Level 1: Each entity responsible for reporting information under Requirements R1 and R3 has a process in place to provide information to their Reliability Coordinator but does not have a process in place...

AI summary The document outlines four levels of non-compliance, with Level 1 highlighting missing processes for sharing information with neighboring Balancing Authorities and Transmission Operators, and Level 4 addressing failures in outage information exchange or adherence to Reliability Coordinator directives.

Standard TOP-004-2 — Transmission Operations - 2.4. Level 4: There shall be a separate Level 4 non-compliance, for every one of the following requirements that is in violation: - 2.4.1 Did not restore operations to respect proven reliable...

AI summary The text outlines Level 4 non-compliance under TOP-004-2 for two violations: failure to restore operations within 30 minutes as per R4 and absence of formal policies on three topics from R6.1 to R6.4. These requirements ensure adherence to reliable power system limits and proper procedural frameworks.

Version History Version Date Action Change Tracking 0 April 1, 2005 Effective Date New 0 August 8, 2005 Removed "Proposed" from Effective Date Errata 1 November 1, 2006 Added language from Missing Measures and Compliance Elements adopted b...

AI summary The document provides a version history of a regulatory proceeding, detailing changes and updates made over time, including the incorporation of new standards and errata.

Attachment 1 — TOP-005-1.1

AI summary Attachment 1 — TOP-005-1.1 relates to operational reliability information standards under the Nova Scotia Utility and Review Board (NSUARB) regulatory proceeding. It involves compliance with NERC and FERC standards, including CIP and TOP-005-1.1 requirements for reporting system operating limits and reliability data.

2. Levels of Non-Compliance for Reliability Coordinators: - 2.1. Level 1: Not applicable. - 2.2. Level 2: Not applicable. - 2.3. Level 3: Not applicable. - 2.4. Level 4: There shall be a separate Level 4 non-compliance, for every one of th...

AI summary The document outlines non-compliance levels for reliability coordinators, focusing on Level 4 violations. These include failing to monitor operational items, lacking specified information, not communicating deviations to operators, and not monitoring system frequency. The Board of Trustees adopted these standards in 2006 with an effective date of 2007.

3. Levels of Non-Compliance for Generator Operators: - 3.1. Level 1: Not applicable. - 3.2. Level 2: Not applicable. - 3.3. Level 3: Not applicable. - 3.4. Level 4: Did not inform its Host Balancing Authority and/or the Transmission Operat...

AI summary Section 3 outlines non-compliance levels for generator operators, with Level 4 specifically addressing failure to inform the Host Balancing Authority and Transmission Operator about available generation resources, citing reference R1.1.

4. Levels of Non-Compliance for Transmission Operators and Balancing Authorities: - 4.1. Level 1: Not applicable. - 4.2. Level 2: Not applicable. - 4.3. Level 3: Not applicable. - 4.4. Level 4: There shall be a separate Level 4 non-complia...

AI summary Level 4 non-compliance involves specific violations, including failure to inform Reliability Coordinators, monitor required items, track system frequency, and address operating deviations. These breaches require corrective actions and adherence to reliability standards.

Standard TOP-007-0 — Reporting SOL and IROL Violations

AI summary The document outlines the regulatory requirements for reporting violations of System Operating Limits (SOL) and Interconnection Reliability Operating Limits (IROL) under Standard TOP-007-0. It emphasizes the role of the Nova Scotia Utility and Review Board (NSUARB) and Nova Scotia Power Incorporated (NSPI) in ensuring compliance with reliability standards set by the North American Electric Reliability Corporation (NERC).

3. Purpose: This standard ensures SOL and IROL violations are being reported to the Reliability Coordinator so that the Reliability Coordinator may evaluate actions being taken and direct additional corrective actions as needed.

AI summary This standard mandates the reporting of System Operating Limit (SOL) and Interconnection Reliability Operating Limit (IROL) violations to the Reliability Coordinator, enabling evaluation of corrective actions and ensuring reliability in the electricity grid.

D. Compliance

AI summary The section heading 'D. Compliance' indicates a regulatory proceeding discussion focused on compliance requirements, though no detailed content is provided in the text chunk. Further analysis would require additional context from the proceeding document.

1. Compliance Monitoring Process

AI summary The section outlines the compliance monitoring process, likely involving regulatory oversight and adherence to standards such as CIP and FAC. It may discuss roles of entities like NSUARB and NSPI in ensuring compliance with reliability and operational protocols.

1.2. Compliance Monitoring Period and Reset Timeframe The reset period is monthly.

AI summary The compliance monitoring period's reset timeframe is established as monthly, indicating the frequency at which compliance status is reassessed.

2. Levels of Non-Compliance for Transmission Operator - 2.1. Level 1: Not applicable. - 2.2. Level 2: Disconnected an overloaded facility as specified in R3 but did not notify its Reliability Coordinator and all neighboring Transmission Op...

AI summary The document outlines four levels of non-compliance for a Transmission Operator, detailing specific violations related to handling overloaded facilities, notifying reliability coordinators, and mitigating system operating limit (SOL) and interconnection reliability operating limit (IROL) violations. Level 4 includes multiple violations, such as failing to use analysis tools to determine SOL causes or mitigate violations.

1.1. Compliance Monitoring Responsibility Compliance Monitor: Regional Reliability Organizations. Each Compliance Monitor shall report compliance and violations to NERC via the NERC Compliance Reporting Process.

AI summary The Regional Reliability Organizations (RROs) are designated as Compliance Monitors responsible for reporting compliance and violations to NERC through its official Compliance Reporting Process, ensuring adherence to reliability standards.

1.2. Compliance Monitoring Period and Reset Timeframe Annually.

AI summary The compliance monitoring period and reset timeframe for the proceeding is set annually, indicating a yearly cycle for assessing adherence to regulatory requirements.

Interpretation of TPL-002-0 Requirements R1.3.2 and R1.3.12 and TPL-003-0 Requirements R1.3.2 and R1.3.12 for Ameren and MISO NERC received two requests for interpretation of identical requirements (Requirements R1.3.2 and R1.3.12) in TPL-...

AI summary NERC received interpretation requests from Midwest ISO and Ameren regarding identical requirements (R1.3.2 and R1.3.12) in TPL-002-0 and TPL-003-0. These requirements pertain to transmission planning and reliability standards, with the requests seeking clarification on their application.

Request for Interpretation of TPL-002-0 and TPL-003-0 Requirement R1.3.2 Received from Ameren on July 25, 2007: Ameren specifically requests clarification on the phrase, 'critical system conditions' in R1.3.2. Ameren asks if compliance wit...

AI summary Ameren seeks clarification on the definition of 'critical system conditions' in TPL-002-0 and TPL-003-0 R1.3.2, specifically whether compliance requires modeling multiple contingent generating unit outages as part of generation dispatch scenarios.

Request for Interpretation of TPL-002-0 and TPL-003-0 Requirement R1.3.12 Received from Ameren on July 25, 2007: Ameren also asks how the inclusion of planned outages should be interpreted with respect to the contingency definitions specif...

AI summary Ameren seeks clarification on interpreting TPL-002-0 and TPL-003-0 Requirement R1.3.12, specifically whether planned outages must be considered in contingency definitions for Categories B and C. They ask if the system must be operated during planned outages with performance requirements from Table 1 plus any unidentified outage.

The following interpretation of TPL-002-0 and TPL-003-0 Requirement R1.3.12 was developed by the NERC Planning Committee on March 13, 2008: This provision was not previously interpreted by NERC since its approval by FERC and other regulato...

AI summary The NERC Planning Committee interpreted TPL-002-0 and TPL-003-0 Requirement R1.3.12 on March 13, 2008, clarifying that planned outages (including maintenance) of bulk electric equipment must be included in studies at demand levels requiring such outages. Planned outages are not considered 'contingencies' under NERC standards, necessitating system adjustments in compliance assessments.

1. Compliance Monitoring Process

AI summary The section outlines the compliance monitoring process, likely involving regulatory oversight and adherence to standards such as CIP and FAC. It may discuss roles of entities like NSUARB and NSPI in ensuring compliance with reliability and operational protocols.

1.1. Compliance Monitoring Responsibility Compliance Monitor: Regional Reliability Organizations.

AI summary The Compliance Monitor for regulatory proceedings is designated as the Regional Reliability Organizations (RROs), underscoring their role in overseeing compliance within the electricity sector's reliability frameworks.

1.2. Compliance Monitoring Period and Reset Timeframe Annually.

AI summary The compliance monitoring period and reset timeframe for the proceeding is set annually, indicating a yearly cycle for assessing adherence to regulatory requirements.

2. Levels of Non-Compliance - 2.1. Level 1: Not applicable. - 2.2. Level 2: A valid assessment and corrective plan for the longer-term planning horizon is not available. - 2.3. Level 3: Not applicable. - 2.4. Level 4: A valid assessment an...

AI summary The document outlines four levels of non-compliance, with Levels 1 and 3 deemed not applicable. Level 2 requires a valid assessment and corrective plan for long-term planning, while Level 4 pertains to near-term planning. No specific entities, programs, or legislation are discussed in this section.

The following interpretation of TPL-002-0 and TPL-003-0 Requirement R1.3.2 was developed by the NERC Planning Committee on March 13, 2008: The selection of a credible generation dispatch for the modeling of critical system conditions is wi...

AI summary The NERC Planning Committee interprets TPL-002-0 and TPL-003-0 R1.3.2, clarifying the Planning Coordinator's discretion in selecting critical system conditions and generator dispatch scenarios. It also updates the Compliance Monitor from RRO to RE per FERC Order 693, affecting how 'valid assessments' are evaluated.

C. Measures - M1. The Planning Authority and Transmission Planner shall have a valid assessment for its system responses as specified in Reliability Standard TPL-004-0_R1. - M2. The Planning Authority and Transmission Planner shall provide...

AI summary The Planning Authority and Transmission Planner must ensure valid system response assessments under TPL-004-0_R1 and provide documentation to their Compliance Monitor as required by the same reliability standard.

D. Compliance - 1. Compliance Monitoring Process - 1.1. Compliance Monitoring Responsibility Regional Reliability Organization. 1.2. Compliance Monitoring Period and Reset Time Frame One calendar year.

AI summary The compliance monitoring process is managed by the Regional Reliability Organization (RRO) with a one-year monitoring period. This section outlines the entity responsible for compliance and the timeframe for monitoring activities.

1. Compliance Monitoring Process

AI summary The section outlines the compliance monitoring process, likely involving regulatory oversight and adherence to standards such as CIP and FAC. It may discuss roles of entities like NSUARB and NSPI in ensuring compliance with reliability and operational protocols.

1.1. Compliance Monitoring Responsibility Regional Reliability Organization.

AI summary The section outlines the responsibility of the Regional Reliability Organization (RRO) in monitoring compliance with reliability standards, emphasizing its role in ensuring adherence to regulations set by entities like NERC, FERC, and NSUARB.

1.2. Compliance Monitoring Period and Reset Time Frame One calendar year.

AI summary The compliance monitoring period is established as one calendar year, with no additional details provided regarding reset time frames or specific compliance requirements.

1.3. Data Retention The Generator Operator shall maintain evidence needed for Measure 1 through Measure 5 and Measure 7 for the current and previous calendar years. The Generator Owner shall keep its latest version of documentation on its...

AI summary The Generator Operator must retain evidence for Measures 1-5 and 7 for current and prior calendar years. Generator Owners must keep documentation on transformers (Measure 6). Compliance Monitors must retain audit data for three years.

1.4. Additional Compliance Information The Generator Owner and Generator Operator shall each demonstrate compliance through self-certification or audit (periodic, as part of targeted monitoring or initiated by complaint or event), as deter...

AI summary Generator Owner and Generator Operator must demonstrate compliance through self-certification or audit, as determined by the Compliance Monitor. Methods include periodic audits, targeted monitoring, or audits triggered by complaints or events.

2. Levels of Non-Compliance for Generator Operator - 2.1. Level 1: There shall be a Level 1 non-compliance if any of the following conditions exist: - 2.1.1 One incident of failing to notify the Transmission Operator as identified in , R3....

AI summary The NSUARB defines four levels of non-compliance for generator operators based on incidents of failing to notify the Transmission Operator or maintain voltage/reactive power schedules. Levels escalate with increasing incident counts, ranging from one incident (Level 1) to ten or more incidents (Level 4), with specific thresholds outlined for each category.

3. Levels of Non-Compliance for Generator Owner: - 3.1.1 Level One: Not applicable. - 3.1.2 Level Two: Documentation of generator step-up transformers and auxiliary transformers with primary voltages equal to or greater than the generator...

AI summary The document outlines four levels of non-compliance for a generator owner, detailing missing documentation for transformers and failure to adjust transformer settings per Transmission Operator specifications. Levels Two and Three involve incomplete or absent records, while Level Four addresses non-compliance with transformer setting changes as required by the Transmission Operator.

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.

Request: Requirement R1 of Standard VAR-002-1 states that Generation Operators shall operate each generator connected to the interconnected transmission system in the automatic voltage control mode ( automatic voltage regulator in service...

AI summary The document requests a formal interpretation of NERC's VAR-002-1 standard regarding generator AVR operation modes. It highlights conflicting interpretations: some argue constant power factor/Mvar modes comply with R1/R2, while others insist only constant voltage mode meets requirements. Misinterpretation risks voltage instability and financial penalties.

Interpretation: 1. First, does AVR operation in the constant PF or constant Mvar modes comply with R1? Interpretation : No, only operation in constant voltage mode meets this requirement. This answer is predicated on the assumption that th...

AI summary The document interprets whether AVR operation in constant PF/Mvar modes complies with R1 (only constant voltage mode is allowed) and if R2 permits the Transmission Operator to direct non-constant voltage modes. The Board of Trustees adopted this interpretation on October 29, 2008, assuming the generator has necessary equipment and the Transmission Operator hasn't mandated otherwise.

1 See 18 CFR 37.6(b)(1) Continent-wide Term Acronym BOT Approved Date FERC Approved Date Definition Control Performance Standard [Archive] CPS 2/8/2005 3/16/2007 The reliability standard that sets the limits of a Balancing Authority's Area...

AI summary This document defines various terms related to electric system reliability and operations, including Control Performance Standards, Corrective Action Plans, Cranking Paths, Critical Assets, Critical Cyber Assets, and Curtailment. These definitions are part of a broader set of reliability standards and procedures.

Glossary of Terms Used in NERC Reliability Standards

AI summary A glossary defining terms from NERC Reliability Standards, including organizations (NERC, FERC), regulatory bodies (NSUARB), utilities (NSPI), and technical standards (CIP, FAC, EOP). Focuses on electric system reliability, cybersecurity, and operational protocols.

Implementation Schedule The following tables identify when Responsible Entities must Begin Work (BW) to become compliant with a requirement, Substantially Compliant (SC) with a requirement, Compliant (C) with a requirement, and Auditably C...

AI summary The document outlines an implementation schedule for Responsible Entities under NERC Functional Model standards, detailing compliance stages such as Begin Work, Substantially Compliant, Compliant, and Auditably Compliant. Different tables apply to various entity types, including Balancing Authorities, Transmission Operators, and Generating Plants.

Table 1 Compliance Schedule for Standards CIP-002-1 through CIP-009-1 Balancing Authorities and Transmission Operators Required to Self-certify to UA Standard 1200, and Reliability Coordinators End of 2nd Qtr 2007 End of 2nd Qtr 2008 End o...

AI summary The table outlines a compliance schedule for various standards (CIP-002-1 through CIP-009-1) related to cybersecurity and reliability in the electricity sector, specifying deadlines for Balancing Authorities, Transmission Operators, and Reliability Coordinators to self-certify to UA Standard 1200.

Implementation Plan for Newly Identified Critical Cyber Assets and Newly Registered Entities This Implementation Plan applies to Cyber Security Standards CIP-002-2 through CIP-009-2 and CIP-002-3 through CIP-009-3. The term "Compliant" in...

AI summary The document outlines an implementation plan for compliance with NERC CIP standards (CIP-002-2 to CIP-009-3) for new entities and critical cyber assets, defining compliance schedules and noting that CIP-002 has no new milestones due to prior compliance.

Implementation Plan for Newly Registered Entities A newly Registered Entity is one that has registered with NERC in April 2008 or thereafter and has not previously undergone the NERC CIP-002 Critical Asset Identification Process. As such,...

AI summary Defines newly registered entities under NERC, requiring compliance with CIP-002 to CIP-009 standards via a schedule in Table 3. Entities registered after April 2008 must follow the compliance milestones outlined for NERC Reliability Standards.

Implementation Milestone Categories The Implementation Plan milestones and schedule to achieve compliance with the NERC Reliability Standards CIP-002 through CIP-009 for newly identified Critical Cyber Assets and newly Registered Entities...

AI summary The document outlines implementation milestones for achieving compliance with NERC CIP-002 through CIP-009 standards for newly identified Critical Cyber Assets and Registered Entities. Milestones are categorized by identification scenarios, with definitions for terms like 'Auditably Compliant' (AC) and 'CIP compliance implementation program.'

Implementation Milestone Categories and Schedules Based on the Critical Cyber Asset identification scenarios identified above, the implementation milestone categories and schedules for those scenarios are defined and distinguished below fo...

AI summary The document outlines two implementation milestone categories for Critical Cyber Assets under NERC standards. Category 1 applies to entities newly identifying Critical Cyber Assets without prior CIP programs, while Category 2 involves entities expanding existing CIP programs to include newly identified assets. Compliance milestones are detailed in Table 2 for Category 1.

A Merger of Two or More Registered Entities where None of the Predecessor Registered Entities has Identified any Critical Cyber Asset In the case of a business merger or asset acquisition, because there are no identified Critical Cyber Ass...

AI summary When merging entities without Critical Cyber Assets, CIP-002 compliance requires implementing risk-based Critical Asset identification. The merged entity has one year to combine or maintain separate methodologies under a unified governance structure. Annual applications of the methodology must continue even during this period, with compliance required post-analysis. Newly identified Critical Cyber Assets trigger full implementation milestones regardless of merger timelines.

A Merger of Two or More Registered Entities where Two or More of the Predecessor Registered Entities has Identified at Least One Critical Cyber Asset This scenario is the most complicated of the three, since it applies to a merged Register...

AI summary The merger of entities with critical cyber assets requires harmonizing conflicting risk-based identification methodologies and CIP compliance programs. The merged entity must align these under a common governance structure within one year, with compliance reviewed under NERC CIP-002.

Table 35 Compliance Schedule for Standards CIP-002-2 through CIP-009-2 or CIP-002-3 through CIP-009-3 For Entities Registering in April 2008 and Thereafter Registration + 12 months Registration + 24 months All Facilities All Facilities CIP...

AI summary Table 35 outlines compliance schedules for CIP-002-2 through CIP-009-3 standards, showing most requirements as compliant except for CIP-003-2/3 where R2 is initially non-compliant. The note clarifies that 'Compliant' dates follow Version 1 Implementation Plan conventions, aligning with Table 4. Other compliance states from Version 1 are no longer used.

Timing Requirements for WECC A В С D If Arranged Interchange (RFI) 3 is Submitted IA Assigned Time Classification IA Makes Initial Distribution of Arranged Interchange BA and TSP Conduct Reliability Assessments IA Compiles and Distributes...

AI summary The document outlines timing requirements for WECC (Western Electricity Coordinating Council) related to arranged interchange (RFI) submissions, including IA distribution timelines, reliability assessments, and confirmed interchange implementation based on submission times relative to the ramp start.

C. Measures M1. The Balancing Authority and Transmission Service Provider shall each provide evidence that it responded, relative to transitioning an Arranged Interchange to a Confirmed Interchange, to each On–time Request for Interchange...

AI summary Measure M1 mandates the Balancing Authority and Transmission Service Provider to provide evidence of responding to On-time, Emergency, and Reliability Adjustment RFIs within the reliability assessment period defined in the Timing Table, Column B, excluding other requests.

D. Compliance - 1. Compliance Monitoring Process - 1.1. Compliance Monitoring Responsibility Regional Reliability Organization.

AI summary The compliance monitoring process is outlined, with the Regional Reliability Organization designated as responsible for compliance monitoring responsibilities.

Example of Timing Requirements for WECC

AI summary The document provides an example of timing requirements related to the Western Electricity Coordinating Council (WECC), likely illustrating compliance deadlines or procedural timelines. The content includes a reference to a figure (_page_54_Figure_2.jpeg) that may depict these requirements visually.

1.4. Compliance Monitoring and Enforcement Processes: The following processes may be used: - Compliance Audits - Self-Certifications - Spot Checking - Compliance Violation Investigations - Self-Reporting - Complaints

AI summary Section 1.4 outlines compliance monitoring and enforcement processes including audits, self-certifications, spot checks, violation investigations, self-reporting, and complaints. These mechanisms ensure adherence to regulatory standards and address non-compliance through structured procedures.

2.Violation Severity Levels R # Lo V S L w er M de V S L te o ra H ig h V S L Se V S L ve re R 1. / N A / N A / N A T he Tr iss ion O d i d to an sm p er a r lec f he i f ie d t s t o t no e ne o s p ec ho do log ies fo h A T C t m e r e a...

AI summary The document outlines violation severity levels, with a focus on high and severe violation levels. It includes details about transmission operations and performance issues, indicating potential regulatory concerns related to compliance and operational standards.

1.1. Compliance Enforcement Authority (CEA) Regional Entity.

AI summary This section introduces the Compliance Enforcement Authority (CEA) as a regional entity under the Nova Scotia Utility and Review Board (NSUARB), responsible for enforcing compliance with regulatory standards in the electricity sector.

Violation Severity Levels R # S Lo V L er w S M de te V L o ra ig S H h V L Se S V L ve re

AI summary The text outlines a table titled 'Violation Severity Levels' with columns indicating different severity levels of violations, though the content within the table is not provided in the chunk. The table appears to be related to regulatory compliance and reliability standards in the electricity sector.

1.4. Compliance Monitoring and Enforcement Processes Any of the following may be used: - Compliance Audits - Self-Certifications - Spot Checking - Compliance Violation Investigations - Self-Reporting - Complaints

AI summary Section 1.4 outlines compliance monitoring and enforcement processes, including audits, self-certifications, spot checks, investigations, self-reporting, and complaints. These mechanisms ensure adherence to regulatory standards and address violations systematically.

1.4. Compliance Monitoring and Enforcement Processes:

AI summary Section 1.4 outlines processes for monitoring and enforcing compliance with regulatory standards in Nova Scotia's energy sector, involving entities like NSUARB and NSPI. It references key acronyms related to reliability, security, and operational standards.

Standard MOD-030-02 — Flowgate Methodology The following processes may be used: - - Compliance Audits - - Self-Certifications - - Spot Checking - - Compliance Violation Investigations - - Self-Reporting - - Complaints

AI summary Standard MOD-030-02 outlines compliance processes including audits, self-certifications, and investigations to ensure adherence to flowgate methodology regulations.

Matrix of Violation Risk Factors for Approval Standard Number Requirement Text of Requirement Violation

AI summary The document presents a matrix outlining violation risk factors for approval, focusing on regulatory standards and requirements. It includes columns for standard number, requirement, text of requirement, and violation, though no specific entries are provided in the table.

Matrix of Violation Severity Levels for Approval Standard Number Requirement Number Text of Requirement Lower VSL Moderate VSL High VSL Severe VSL BAL-005-0.1b R12.1. Balancing Authorities that share a tie shall ensure Tie Line MW metering...

AI summary The document presents a matrix outlining violation severity levels for approval, focusing on a specific requirement related to Tie Line MW metering by Balancing Authorities. It specifies that a severe violation occurs when metering is not properly telemetered to both control centers from a common source.

Compliance Acconntability 10 Nova Scotia NSPI, as a Registered Entity, will be subject to NERC's Compliance Monitoring and Enforcement Program ("CMEP") as implemented by NPCC. NPCC in its determination of a NSPI violation may identify the...

AI summary NSPI is subject to NERC's Compliance Monitoring and Enforcement Program via NPCC, which assesses violations, determines reliability risks, and proposes non-monetary penalties to the NSUARB. The NSUARB will oversee enforcement proceedings to determine violations and appropriate remedial actions.

Reporting Requirements NSPI will provide NPCC all information respecting reporting requirements contained in the CMEP for both NERC Reliability Standards and NPCC Regional Reliability Criteria. NSPI will be responsible for providing infonn...

AI summary NSPI is required to report to NPCC under the CMEP framework, covering NERC Reliability Standards and NPCC Regional Reliability Criteria, including routine and event-based reporting obligations.

NERC Compliance Audits NSPI will be subject to compliance audits performed by NPCC related to NERC Reliability Standards and NPCC Regional Reliability aiteria.

AI summary NSPI will undergo compliance audits by NPCC concerning NERC Reliability Standards and NPCC Regional Reliability aiteria, highlighting regulatory oversight of reliability criteria in the electricity sector.

NPCC Regional Reliability Criteria Compliance Audit NSPI will be subject to NPCC Regional Reliability Criteria compliance audits. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 .-. 31 32 33 34 35 36 37 38...

AI summary NSPI will undergo NPCC Regional Reliability Criteria compliance audits. Points of contact for NERC, NPCC, and NSPI are provided, including names, titles, addresses, and contact information.

Background This matter has arisen as a result of the DARB having signed a Memorandum of Understanding with NERC dated December 22, 2006 wherein the UARB and NERC committed to a process for making NERC Reliability Standards mandatory, and a...

AI summary The document outlines Memoranda of Understanding (MOUs) between DARB, UARB, NERC, NSPI, and NPCC regarding NERC Reliability Standards. NSPI asserts compliance with these standards through audits and maintains its bulk power system infrastructure.

Regulatory Implications in Nova Scotia As part of the interconnected North American bulk power system, NSPI is currently required to comply with NERC Reliability Standards and NPCC Reliability Criteria. NSPI has brought forward capital wor...

AI summary NSPI must comply with NERC and NPCC standards, which have been used to justify capital projects and items in the 2010 ACE Plan. Compliance with these standards is a key factor in regulatory decisions.

Recommendation NSPI recommends that the UARB approve the NERC Reliability Standards as requested in its application of June 30, 2010 and the NPCC Reliability Criteria as requested in its application of June 29, 2010. NERC has also requeste...

AI summary NSPI recommends the UARB approve NERC and NPCC reliability standards but opposes approval of VRFs and VSLs, arguing the UARB can independently assess compliance impacts without formal approval. NSPI emphasizes the UARB's discretion in evaluating reliability violations.

Compliance The parties understand that, once the Board approves a reliability :standard I compliance with the reliability ~tandard will be mandatory in Nova Scotia. The Board may enforce approved reliability standards directly. The palties...

AI summary The Board enforces reliability standards in Nova Scotia, with NERC providing compliance information. Parties collaborate on reliability risk assessments, and NERC will report on audits, evaluations, and disturbances. The Board retains authority over penalty determination.

3. Compliance Aspects

AI summary The section outlines compliance aspects relevant to the regulatory proceeding, though no specific details are provided in the excerpt.

Compliance Accountability in Nova Scotia NSPI, as a Registered Entity, will be subject to NERC's Compliance Monitoring and Enforcement Program ("CMEP") as implemented by NPCC. NPCC in its determination of a NSPI violation may identify the...

AI summary NSPI must comply with NERC's CMEP via NPCC, which assesses violations and proposes penalties to the UARB. The UARB oversees enforcement proceedings to determine violations and appropriate remedies. NSPI may submit mitigation plans or responses to the Board.

NERC Compliance Audits NSPI will be subject to compliance audits performed by NPCC related to NERC Reliability Standards and NPCC Regional Reliability Criteria.

AI summary Nova Scotia Power Inc. (NSPI) will undergo compliance audits by the Northeast Power Coordinating Council (NPCC) to ensure adherence to NERC Reliability Standards and NPCC Regional Reliability Criteria.

NERC Reliability Standards and NPCC Regional Reliability Criteria (NSUARB NERC-R-10) NSPI Responses to UARB Information Requests

AI summary The document outlines Nova Scotia Power Inc.'s (NSPI) responses to the Utility and Review Board (UARB) information requests regarding compliance with NERC Reliability Standards and NPCC Regional Reliability Criteria under NSUARB NERC-R-10. It focuses on regulatory compliance and reliability criteria adherence.

es ofthe Alberta Commission and the Market Surveillance Administrator (MSA). Specified penalties for violations ofReliability Standards were adopted by the Alberta Commission, effective November 2010. The AESO established the AESO Reliabil...

AI summary Alberta's regulatory framework for reliability standards includes penalties enforced by the Alberta Commission, the AESO Reliability Committee (ARC), and a compliance monitoring program. Reliability Standards are reviewed and approved by the Alberta Commission, with 69 NERC standards either approved or rejected. The AESO revised its Work Plan in 2010 to adopt a risk-based prioritization approach. Alberta entities are excluded from the NERC Compliance Registry but maintain participation through negotiated agreements.

icture_0.jpeg) On November 25,2010, BCUC approved its Implementation Plan for purposes ofthe monitoring of compliance with adopted British Columbia Reliability Standards. BC does not have a Memorandum ofUnderstanding (MOU) with NERC, nor i...

AI summary BCUC approved a 2010 Implementation Plan for monitoring compliance with British Columbia Reliability Standards. British Columbia does not have an MOU with NERC, prioritizing WECC membership instead. BC Hydro is a member of both WECC and NERC, with BCUC maintaining close relationships with both organizations.

on date unless otherwise directed by the EUB. The EUB has authority under the Electricity Act to revoke the adoption of a Reliability Standard and remand it back to the NBSO for further consideration. NERC has MOUs with New Brunswick (Prov...

AI summary New Brunswick's regulatory framework for NERC Reliability Standards involves the EUB's authority to revoke standards, NBSO's accountability to NERC, and NPCC's monitoring role. NBSO enforces compliance with penalties, while EUB imposes administrative penalties under the Electricity Act. NERC and NPCC may recommend sanctions to EUB, with public disclosure limited to confirmed violations.

_0.jpeg) Reliability Standards by it or by market participants and is subject to NERC's Reliability Standards CMEP processes up to but not including financial penalties. The provincial government recognized NERC as the ERa on November 28,...

AI summary The text outlines Ontario's regulatory framework for electricity reliability, including NERC's role as the Electric Reliability Organization (ERa), the Memorandum of Understanding (MOD) between the IESO, NPCC, and NERC, and amendments to the Electricity Act, 1998. It emphasizes the Board's oversight of NERC and the IESO's compliance with reliability standards, alongside the Green Energy Act's impact on reliability rules.

Response to IR-6: (a) NERC Alerts apply to users, owners, or operators of the bulk power system. When NERC determines it is necessary to place the industry or segments of the industry on formal notice of its findings, analyses, and recomme...

AI summary NERC Alerts apply to bulk power system users and operators, providing non-enforceable guidance to NERC-registered entities. NERC notifies FERC and others but not NSUARB, stating Alerts align with approved reliability standards and do not require NSUARB approval.

Compliance Accountability in Nova Scotia NSPI, as a Registered Entity, will be subject to NERC's Compliance Monitoring and Enforcement Program ("CMEP") as implemented by NPCC. NPCC in its determination of a NSPI violation may identify the...

AI summary NSPI, as a Registered Entity, is subject to NERC's Compliance Monitoring and Enforcement Program (CMEP) via NPCC. NPCC may identify NERC Reliability Standard violations and propose mitigation plans or non-monetary penalties to the Nova Scotia Utility and Review Board (UARB). The UARB retains authority to determine violations and enforce remedial measures, per a 2006 Memorandum of Understanding with NERC. NERC and NPCC's roles in enforcement are outlined in a 2010 MoU.

5 Response to IR-IO: 4 6 7 NERC does not anticipate having a direct role in an NSPI capital application proceeding. NERC 8 may provide information as requested. North American Electric Reliability Corporation (NERC) Responds to Nova Scotia...

AI summary NERC clarifies it has no direct role in NSPI's capital application proceeding but may provide information if requested. The response addresses NERC's position on compliance obligations if Nova Scotia applies less stringent interpretations of reliability standards compared to the U.S.

Alberta: The Alberta Transmission Regulation (Reg 288/2009 as amended) outlines the framework for Reliability Standards in Alberta. The North American Electric Reliability Corporation (NERC) Reliability Standards apply in Alberta to the ex...

AI summary Alberta's reliability standards are governed by the Alberta Transmission Regulation, with NERC standards adopted by AESO and reviewed by the Alberta Commission. The 2009 Electricity Statutes Amendment Act formalized enforcement by the Alberta Commission and MSA, with penalties for violations. A 2007 Ministerial Order recognized NERC as the ERO.

cture_0.jpeg) On November 25,2010, BCUC approved its Implementation Plan for purposes ofthe monitoring of compliance with adopted British Columbia Reliability Standards. BC does not have a Memorandum of Understanding (MOU) with NERC, nor i...

AI summary BCUC approved a compliance monitoring plan for British Columbia's reliability standards in 2010. British Columbia does not have an MOU with NERC and prioritizes WECC membership for reliability. BC Hydro is part of both WECC and NERC, with BCUC maintaining close relationships with both organizations.

Manitoba: Manitoba Hydro is currently required to comply with NERC Reliability Standards through its membership in the Midwest Reliability Organization (MRO) and its membership in NERC, subject to exceptions based on provincial law. Pursua...

AI summary Manitoba Hydro must comply with NERC Reliability Standards via its Midwest Reliability Organization (MRO) membership, subject to provincial law exceptions. The 2004 Order in Council approved this compliance, with the 2009 Manitoba Hydro Act establishing enforceable reliability standards and PUB authority for sanctions. Regulations to implement the Act are pending, expected in 2011.

s point, however, as the program is extended to entities within Saskatchewan the potential use of methods of enforcement will be considered. The Saskatchewan oversight authority has been established, with very specific authorities within a...

AI summary The Saskatchewan oversight authority is tasked with enforcing compliance and managing mitigation plans, utilizing resources like MRO and NERC. It will determine applicable Reliability Standards and review unimplemented ones, with NERC and MRO conducting compliance audits in Saskatchewan.

Response to Nova Scotia Utility and Review Board Date ofResponse: February 10,2011 1 Request IR-1 : 2 3 Please reference Nova Scotia Power Inc's ("NSPI") letter to the Utility and Review Board dated 4 December 17,2010. 5 6 Please provide a...

AI summary Nova Scotia Power Inc. (NSPI) submitted a letter to the Utility and Review Board on December 17, 2010, regarding Violation Risk Factors and Violations Security Levels. The NPCC responded that it is encouraged by NSPI's endorsement of Regional Reliability Criteria and will defer to NERC on matters related to NERC's Severity Levels and Violation Risk Factors, as they pertain to Reliability Standards filings.

Compliance Audit Report Public Version Nova Scotia Power Inc. NERC ID# NCR07178 Confidential Information (including Privileged and Critical Energy Infrastructure Information) Has Been Removed Date of Audit: October 5-8, 2010

AI summary This is the public version of a compliance audit report conducted by Nova Scotia Power Inc. in October 2010. The report includes confidential information that has been removed, and it is associated with the North American Electric Reliability Corporation (NERC).

Audit Process The compliance audit process steps are detailed in the NPCC CMEP. The NPCC CMEP generally conforms to the United States Government Accountability Office Government Auditing Standards and other generally accepted audit practic...

AI summary The audit process follows the NPCC CMEP, aligning with U.S. GAO standards and accepted audit practices. The process replaces the Regional Entity Self-Certification method with a structured compliance audit framework.

Objectives All Registered Entities are subject to an audit for compliance with all reliability standards applicable to the functions for which the Registered Entity is registered. 2 The audit objectives are to: - Review compliance with the...

AI summary The audit objectives focus on reviewing NSP's compliance with NERC and NPCC reliability standards, validating self-reported violations, assessing compliance programs, and evaluating mitigation plans. The process ensures adherence to actively monitored reliability standards and regional requirements.

Methodology The audit team reviewed the information, data, and evidence submitted by NSP and assessed compliance with requirements ofthe applicable CIP standards. Submittal ofinformation and data was sent to NPCC as requested on or before...

AI summary The audit team reviewed NSP's compliance with CIP standards, assessed submitted data, and ensured adherence to NERC and CIP requirements. Information was submitted to NPCC, and evidence was validated, cross-checked, and stored securely. Findings were based on audit team consensus and NPCC AVP input.

Compliance Culture Nova Scotia Power Inc.'s compliance culture was reviewed by the audit team. During all contact, NSP staff was professional in their approach to compliance and understood the importance ofthe compliance and its role in ma...

AI summary Nova Scotia Power Inc.'s compliance culture was assessed as professional and committed to reliability and security. The audit found staff understood compliance's role in maintaining system integrity, with additional details in the Internal Compliance Survey.

Response to Nova Scotia Power, Inc. Date of Response: February 10, 2011 - Request IR-3: - Please describe the standard approval process for new Regional Reliability Criteria in each - of the provinces in Canada which have adopted Regional...

AI summary Nova Scotia Power, Inc. requested information on the approval process for Regional Reliability Criteria in Canadian provinces. NPCC responded that approval occurs via its Full Membership and filing with provinces, with automatic adoption in some cases. NPCC is currently focused on Nova Scotia, with Ontario and New Brunswick having adopted the criteria. The response also references ongoing activities in Quebec and mentions enforcement proceedings before the UARB.

ability Standards; and Northeast Power Coordinating Council, Inc. – Regional Reliability Criteria NERC-R-10/Matter No. M03324 Response to Nova Scotia Power, Inc. Date of Response: February 10, 2011 - Request IR-7 - Please advise as to what...

AI summary NPCC explains its role in enforcement proceedings involves providing compliance assessment results and recommending sanctions, while NERC's role is deferred. NPCC also states it would not directly participate in NSPI capital application proceedings but may provide information if requested.

ability Standards; and Northeast Power Coordinating Council, Inc. – Regional Reliability Criteria NERC-R-10/Matter No. M03324 Response to Nova Scotia Power, Inc. Date of Response: February 10, 2011 - Request IR-9: - If a less stringent int...

AI summary NPCC asserts that compliance with NERC standards and regional reliability criteria must be uniformly applied across regions, rejecting differential interpretations. It also states no inter-provincial coordination is required for Canadian provinces regarding these standards.

IT IS HEREBY ORDERED that: - 1. The Criteria filed by the NPCC are approved. - 2. The Standards and associated Glossary of Terms filed by NERC are approved. - 3. The Standards and the Criteria are mandatory and enforceable for users, owner...

AI summary The Board approves NPCC's Criteria and NERC's Standards and Glossary, making them mandatory for bulk power system participants in Nova Scotia. VRFs and VSLs are accepted for future compliance reviews but not enforceable.

II BACKGROUND [10] The Board exercises general supervision over NSPI pursuant to the Public Utilities Act, R.S.N.S. 1989, c. 380, as amended (the "Acf'). Under the Act, NSPI is required to provide reasonably safe and adequate service and f...

AI summary The Nova Scotia Utility and Review Board oversees NSPI under the Public Utilities Act. NSPI, NERC, and NPCC established MOUs to enforce reliability standards. NSPI claims existing compliance with standards and recommends rejecting VRFs/VSLs. The Board identifies four key issues: standard approval, amendment procedures, VRF/VSL approval, and compliance monitoring.

1. Standards and Criteria [20] In response to Board IR-2, NERC provided its report entitled "A Summary of Canadian Provincial Adoption of Reliability Standards Framework". A review of the report indicates widespread acceptance and adoption...

AI summary The Board approved reliability standards after NERC confirmed Canadian provinces' adoption, NPCC outlined regional criteria compliance by members, and NSPI's compliance was verified via audit. No objections were raised to the approval.

4. Compliance Monitoring and Enforcement [34] The May 9,2010 MOU provides the following: NSPI, as a Registered Entity, will be subject to NERC's Compliance Monitoring and Enforcement Program ("CMEpl ) as implemented by NPCC. NPCC in its de...

AI summary NSPI must comply with NERC standards via NPCC's CME program, with NPCC proposing non-monetary penalties to the UARB. The Board oversees enforcement but does not impose penalties, only directing remedial actions if non-compliance is found.

IV SUMMARY OF FINDINGS AND DIRECTIVES [36] The Criteria filed by the NPCC are approved. [37] The Standards and associated Glossary of Terms filed by NERC are approved. [38] The Standards and the Criteria are mandatory and enforceable for u...

AI summary The Board approves NPCC's Criteria and NERC's Standards/Glossary, mandating their enforcement for Nova Scotia's bulk power system. VRFs and VSLs are accepted for future compliance reviews. An order will be issued.

AUC) to accept or reject them. The AUC must follow the recommendation of the AESO unless an intervenor convinces the AUC that the recommendation is technically deficient or not in the public interest. The AESO is managing a project to brin...

AI summary The Alberta Utilities Commission (AUC) must accept or reject recommendations from the Alberta Electric System Operator (AESO) on NERC and WECC standards, unless intervenors demonstrate technical deficiencies or public interest concerns. The AESO is evaluating 35 adopted (with or without modifications) and 40 non-applicable standards, prioritizing alignment with NERC while adapting to Alberta's grid and market needs. Cost considerations are not a primary focus for AESO but may be raised by affected entities.

October 15,2010 Nancy McNeil Regulatory Affairs Officer/Clerk Nova Scotia Utility and Review Board 1601 Lower Water Street, 3rd Floor Halifax, NS B3J 3P6 Dear Ms. McNeil: Re: North American Electric Reliability Corporation - Reliability St...

AI summary Nova Scotia Power Inc. (NSPI) is conducting a NERC compliance audit and will propose a timeline for approving NERC and NPCC standards by Q4 2010. The audit, completed in two stages, will inform NSPI's recommendation to the Utility and Review Board (UARB), ensuring alignment with audit results.

NERC Reliability Standards and NPCC Regional Reliability Criteria (NSUARB NERC-R-10) NSPI Information Requests to NERC

AI summary The document outlines information requests by NSPI (Nova Scotia Power Inc.) to NERC (North American Electric Reliability Corporation) regarding compliance with NERC Reliability Standards and NPCC Regional Reliability Criteria under the NSUARB NERC-R-10 proceeding. It focuses on regulatory oversight of grid reliability.

Date Filed: January 20, 2011 NSPI (NERC) Page 1 of 6 1 Request IR-5: 2 3 From time to time NERC issues Compliance Notices which purport to direct certain action 4 to be taken by Registered Entities. These notices contain the following prov...

AI summary The document outlines questions regarding the applicability and enforcement of NERC Compliance Notices in Nova Scotia, including whether they require UARB approval and how conflicts with UARB-approved standards should be resolved.

Request IR-14: What process does NERC propose for adoption of future Reliability Standards in Nova Scotia? Request IR-15: What process does NERC propose for amendments to Reliability Standards in Nova Scotia? Request IR-16: At Section VI....

AI summary NERC proposes processes for adopting and amending future Reliability Standards in Nova Scotia and requests feedback from the Province. NSPI clarifies that references to the Province in NERC's application likely refer to the UARB, an independent regulatory body.

NOVA SCOTIA UTILITY AND REVIEW BOARD IN THE MATTER OF: THE PUBLIC UTILITIES ACT - and- IN THE MATTER OF: Filings by North American Electric Reliability Corporation ("NERC") and Northeast Power Coordinating Council Inc. ("NPCC") for approva...

AI summary The Nova Scotia Utility and Review Board requests comments on Nova Scotia Power Inc.'s letter regarding violation risk factors and compliance audit findings, while seeking approval for reliability standards submitted by NERC and NPCC. The Board also requests the final report of the 2010 NSPI compliance audit.

Index to NERC Responses to Directives and Other Actions from September 16, 2010 FERC Order on Three-Year ERO Performance Assessment P No. Directive Page 183 Directs NERC to develop a plan to address capacity and energy in its reliability a...

AI summary The document outlines Directive 183 from the September 16, 2010 FERC Order, which requires NERC to develop a plan to address capacity and energy in its reliability assessment methodology, along with a timeline for execution, to be submitted as part of the 2011 Long-Term Reliability Assessment.

2. Progress in Implementing Specific NERC Actions Identified in the Assessment Related to Each Area of Discussion Attachment 2 of the Assessment included summaries of stakeholder and Regional Entity comments and recommendations that were r...

AI summary NERC and Regional Entities collaborated to revise agreements and rules following stakeholder feedback, filing revised Delegation Agreements in 2010. Progress on implementing NERC actions across areas like reliability standards, compliance, and event analysis is detailed in Appendix A. NERC filed an informational report with FERC in 2011 and notified Canadian authorities.

00903.pdf) "If the Standards Committee finds that any of the documents do not meet the specified criteria, the Standards Committee shall remand the documents to the drafting team for additional work. "If the standard is outside the scope o...

AI summary The text outlines NERC's standards development process, including the Standards Committee's authority to remand non-compliant documents, requirements for aligning standards with SAR scope, and NERC staff responsibilities for ensuring clarity and enforceability. It emphasizes stakeholder ballot reporting, quality reviews for interpretations, and the role of the Standard Processes Manual in governance.

2. Compliance Monitoring and Enforcement In its September 16, 2010 Order, P 113, FERC expressed its general support for NERC's suggestions for program enhancements the Regional Entities should make to improve their processing of alleged vi...

AI summary FERC's 2010 Order P 113 endorsed NERC's proposals to enhance compliance monitoring and enforcement, including audit practices, penalty determinations, delegation agreements, and no-action letters. The order addresses improvements to processing violations and mitigation plans by Regional Entities.

standard for violations that occur prior to FERC providing differing direction through an order approving a revision of or an interpretation to the standard, or providing guidance on its application. The CAN process is not a consensus buil...

AI summary The CAN process ensures compliance consistency across NERC and regions by providing a short comment period for stakeholders, including FERC and industry, to address pre-FERC-order violations. It emphasizes transparency and expedited resolution of compliance issues without consensus-building.

ii. Focus Audits on Actual Performance In its September 16, 2010 Order, P 121, FERC stated: "The Commission agrees that the Reliability Standard Audit Worksheets should serve as no more than guidance to the auditor and the audited entity a...

AI summary FERC's 2010 Order P 121 emphasizes that Reliability Standard Audit Worksheets (RSAWs) should guide audits without prescribing rigid compliance methods. NERC is tasked with continuously improving RSAWs through input from Regional Entities and alignment with FERC guidance. Additional compliance tools like CANs and Compliance Bulletins aid entities in understanding standards.

iii. Participation in Regional Entity Compliance Audits by NERC Staff and FERC Staff In its September 16, 2010 Order, P 126, FERC stated: "The Commission commends NERC staff's participation in, and observation of, Regional Entity audits. I...

AI summary FERC commends NERC's participation in audits, stressing the need for technically proficient staff to ensure rigorous audits. Active involvement is crucial for NERC's oversight, and failure to meet standards could hinder its mission.

RC that FERC staff observers are present to assess the performance of the Regional Entity in performing the compliance audit of the registered entity and the performance of NERC in its oversight role. FERC staff participates in compliance...

AI summary FERC staff observers participate in NERC compliance audits to assess audit processes and technical rigor, ensuring equal access to evidence without influencing compliance determinations. They review audit methods but do not make compliance decisions.

b. Penalty Determinations In its September 16, 2010 Order, P 133, FERC stated: "We agree with NERC that there always will be some tension between the transparency of specific NERC Sanction Guidelines and flexibility to negotiate penalties...

AI summary FERC emphasizes balancing transparency and flexibility in penalty determinations under NERC Sanction Guidelines, supports self-reporting incentives, and acknowledges NERC's efforts to streamline enforcement through new NOP templates like the disposition document. NERC aims to improve clarity in penalty factors and review Sanction Guidelines for consistency.

NERC Responses to FERC's Other Action – P 138 The revised Delegation Agreements that were filed on June 21, 2011 establish processes for the collaborative development by NERC and the Regional Entities of performance goals, measures and oth...

AI summary NERC's revised Delegation Agreements (2011) establish collaborative processes with Regional Entities to develop performance metrics aligned with ERO goals, ensuring consistent implementation of the Compliance Monitoring and Enforcement Program (CMEP) and enhancing bulk power system reliability. Metrics focus on transparency, consistency, and organizational performance across program areas.

e. Administrative Citation Process In the September 16, 2010 Order, P 218, FERC stated: "One method that NERC and Regional Entities advocate to process enforcement matters more efficiently is to streamline procedures for handling less seri...

AI summary FERC encourages streamlining enforcement processes for minor violations through 'parking ticket' approaches and bundled settlements, while rejecting 'warning tickets' due to concerns about inadequate recognition of compliance history. The focus is on aligning penalty procedures with violation severity and ensuring auditable compliance.

NERC Response to FERC's Other Action – PP 218-219 Since Spring 2010, NERC has been working to implement a program that establishes categories of NOPs and streamlines those NOPs in which risk to the bulk power system is minimal or moderate....

AI summary NERC has streamlined NOPs since 2010, increasing efficiency by handling more violations monthly. The administrative citation process, introduced by Mr. Cauley, allows NERC to address multiple low-risk violations via a single NOP, reducing procedural steps and documentation required under the CMEP.

ain the essential knowledge and skills to conduct cyber security audits, NERC should consider the worthiness of an ongoing "accreditation" of qualified auditor candidates through continued education." NERC understands the importance of dev...

AI summary NERC emphasizes the need for ongoing auditor training to enhance CIP reliability standard compliance. FERC expresses concerns about potential inconsistencies in 'fast track' CIP interpretations, urging NERC to seek Commission review for such proposals. NERC has conducted and plans to expand auditor workshops to improve expertise.

4. Compliance Registry In its September 16, 2010 Order, P 162, FERC stated: "While NERC indicates that it will consider whether to raise the thresholds set forth in the Registry Criteria, NERC also observes that the registration process is...

AI summary FERC's 2010 Order emphasizes that NERC must justify threshold changes to the Compliance Registry from a reliability perspective. NERC acknowledges the current process works well but is refining registration requirements in alignment with Bulk Electric System definitions and the Ad Hoc Generator Owner/Transmission Owner Report. Revisions to Section 500 and Appendix 5A of the Rules of Procedure were approved by FERC.

a. Situation Awareness In its September 16, 2010 Order, P 166, FERC stated: "While stakeholders expressed concerns to NERC about the SAFNR project, we have no specific information to support their arguments against the project, and thus fi...

AI summary NERC is finalizing the SAFNR Version 2 system, selected via RFP, to enhance situational awareness as required by FERC. Despite budget overruns, NERC seeks funding solutions with FERC. The project timeline has been adjusted due to contract negotiations and data support from Reliability Coordinators.

NERC Response to FERC's Directive – P 169 NERC has established criteria for prioritizing events by risk and significance for the purpose of reporting and determining the level of analysis needed for each category. The threshold criteria ar...

AI summary NERC has established event categorization criteria based on risk and significance, with five categories. A field trial from October 2010 to January 2011 led to process improvements, with plans for a second revision by April 2011 and updates to Rules of Procedure for the NERC Board of Trustees in November 2011.

In P 170, FERC stated: "In addition, the Commission's staff needs timely access to detailed event information. Absent such information, the Commission's identification of any needed improvements in the Reliability Standards could be delaye...

AI summary FERC emphasizes the need for timely access to detailed event information by its staff to identify improvements in Reliability Standards. It directs NERC to collaborate with Regional Entities to provide such information upon request, including event sequences and diagrams, and mandates NERC to report implementation steps in an informational report.

In P 171, FERC stated: "The Commission also directs NERC to develop communication protocols between NERC, the Commission and the Regional Entities for use during events. These protocols will help avoid possible delays and miscommunications...

AI summary FERC directs NERC to develop standardized communication protocols with the Commission and Regional Entities during events to prevent delays and miscommunications. Protocols must include contact details, hierarchy, information requirements, and timelines. NERC must submit a written protocol and report progress every six months.

ii. Timing of and Interaction between Event Analysis and Compliance Violation Investigations In its September 16, 2010 Order, P 174, FERC stated: "To address the stakeholders' concerns, the Commission offers the following guidance to NERC....

AI summary FERC's 2010 Order P 174 mandates concurrent execution of event analysis and compliance violation investigations (CVIs) to conserve resources and ensure data integrity. Immediate data retention is emphasized to prevent loss during these processes.

Further, in P 175, FERC stated: "While the facts and circumstances in both an event analysis and a CVI often are the same, the focus of each inquiry is different. A CVI addresses whether Reliability Standards have been violated, while an e...

AI summary FERC distinguishes between Compliance and Violation Investigations (CVIs) and event analyses, emphasizing that CVIs assess reliability standard violations, while event analyses focus on preventing recurrence. Industry participants cannot influence CVIs, and ERO/Regional Entities must maintain direct involvement in event analyses to ensure objectivity.

In P 176, FERC stated: "In order to create more efficiency in the event analysis and CVI processes, all event analysis materials obtained by the event analysis team, including requests for information and responses, should be sent, at the...

AI summary FERC aims to improve efficiency in event analysis and CVI processes by requiring simultaneous sharing of materials with compliance staff and NERC. This ensures CVI teams access necessary data without duplicative requests, while maintaining confidentiality by keeping event analysis personnel unaware of ongoing CVI activities.

In P 177, FERC stated: "Further, any communication between an event analysis team and a corresponding CVI team generally should be one-way only: from the event analysis team to the CVI team. This one-way information sharing will avoid the...

AI summary FERC mandates one-way communication from event analysis teams to CVI teams to prevent disclosure of confidential compliance information. It also directs NERC to clarify event analysis-compliance interfaces, report on staff reorganization impacts, and address staffing adequacy for expanded duties. NERC must detail procedures for information exchange and budget adjustments if needed.

NERC Response to FERC's Directive – P 178 Draft revisions to the events analysis process currently under consideration contemplate both Regional Entities and registered entities taking a more direct role in analysis of lower significance e...

AI summary NERC outlines revised event analysis processes involving Regional and registered entities for lower significance events, shifting NERC's focus to higher significance events and quality reviews. A Phase 2 field trial (March 2011) will assess capabilities, with results informing 2012 business plans. NERC has developed a four-stage event analysis process, including compliance evaluation and enforcement, alongside a cause analysis methodology training program.

i. Assessment Reports In its September 16, 2010 Order, P 180, FERC stated: "Scenario Assessments are a critical tool for addressing reliability considerations arising from various emerging issues, including faster renewable resource integr...

AI summary FERC's September 16, 2010 Order P180 emphasizes the importance of scenario assessments for reliability, directing NERC to update protocols for annual scenario analysis to address emerging issues like renewable integration. This ensures timely development of reliability standards.

NERC Response to FERC's Directive – P 183 NERC strives to provide continuous improvement of reliability assessments and welcomes FERC's suggestions for further improvement. With respect to FERC's specific directive, NERC will implement pro...

AI summary NERC responds to FERC's directive by implementing probabilistic assessments in the Long-Term Reliability Assessment (LTRA), with a voluntary trial phase in 2011 and full implementation in 2012. The Generation and Transmission Reliability Planning Models Task Force (GTRPMTF) developed methods to supplement traditional reliability metrics with probabilistic indices, enhancing energy-based assessments.

NERC Response to FERC's Directive – P 185 In 2009 NERC began a review of its internal data collection and validation processes to fortify its current data analysis system and to improve data validation. NERC agrees with FERC's directive of...

AI summary NERC is enhancing its data collection and validation processes per FERC's directive, including establishing permanent databases for reliability assessments, evaluating transmission and generation data, and developing a web application for data management.

6. Business Planning and Budgeting, Accounting and Financial Reporting and Assessment Processes In its September 16, 2010 Order, P 194, FERC stated: "Noting that NERC already engages in strategic planning out to five years, the Commission...

AI summary FERC's 2010 Order P 194 encourages joint strategic planning between NERC and Regional Entities under ERO oversight to improve reliability operations and reduce budget process tensions, emphasizing the value of multi-year budgets for stakeholder transparency.

Further, in P 195, FERC stated: "A joint strategic planning initiative also would address another major Commission concern, which is adequate monitoring of the Regional Entities' expenditures. The Commission notes that in NERC's compliance...

AI summary FERC emphasizes the need for NERC to improve oversight of Regional Entities' budgets, citing past reliance on internal estimates and the requirement for ERO to review expenditures. A joint strategic planning initiative with multi-year budgets is proposed to ensure adequate funding for Regional Entities' delegated functions.

a. Issues Concerning all Regional Entities In its September 16, 2010 Order, P 217, FERC stated: "We also agree that development of reasonable metrics for assessment of the Regional Entities' performance of their compliance functions will i...

AI summary FERC's September 2010 Order P 217 mandates NERC and Regional Entities to develop a non-public compliance data hub to improve enforcement efficiency, provide performance metrics, and coordinate public disclosure of compliance information. The hub aims to streamline processes and enhance transparency in compliance monitoring.

NERC Response to FERC's Directive – P 217 NERC initiated a multi-phase project in 2008 to design and build a system for the collection, management, and exchange of compliance-related information between NERC and the Regional Compliance Enf...

AI summary NERC initiated a multi-phase project in 2008 to develop the Compliance Reporting, Analysis, and Tracking System (CRATS) for managing compliance data with Regional Compliance Enforcement Authorities. CRATS, a modular system, includes modules like Registration, Standards, and Compliance Violations, with ongoing development of Mitigation Plans and Enforcement modules. The system replaces spreadsheet-based methods and continues evolving.

NERC Response to FERC's Directive – P 220 NERC and the Regional Entities will continue to audit reliability coordinators, balancing authorities and transmission operators on three year cycles and all other registered entities on six year c...

AI summary NERC outlines a risk-based audit strategy for reliability coordinators and registered entities, focusing on three-year cycles for critical roles and six-year cycles for others. Audits prioritize entities needing oversight while maintaining visibility across all registered entities, guided by the CMEP Implementation Plan and monitored standards.

APPENDIX A Progress in Implementing Specific NERC Actions from the Three-Year ERO Performance Assessment

AI summary This appendix outlines progress in implementing specific North American Electric Reliability Corporation (NERC) actions as part of a three-year Electric Reliability Organization (ERO) performance assessment, focusing on compliance and regulatory oversight.

Progress in Implementing Specific NERC Actions from the Three-Year ERO Performance Assessment March 16, 2011

AI summary The document outlines progress in implementing specific North American Electric Reliability Corporation (NERC) actions following a three-year Electric Reliability Organization (ERO) performance assessment conducted on March 16, 2011. Key entities involved include NERC, ERO, and the Federal Energy Regulatory Commission (FERC).

work plan and recommendations for adjusting the timing of individual projects; and - identification of potential future projects for addressing changes in or development of new reliability standards. In addition, as part of the annual proj...

AI summary The document outlines NERC's process for revising reliability standards, including project timing adjustments, stakeholder input, administrative changes tracking, and converting existing standards to performance-based metrics. Annual revisions involve leadership input, webinars, and integration with project management programs.

Appendix 3A — Reliability Standards Development Procedure may be necessary or desirable.] As the result of amendments submitted and approved since the 3-Year ERO Performance Assessment Report was filed with the Commission, the current NERC...

AI summary The NERC Standard Processes Manual outlines procedures for gathering stakeholder feedback during reliability standards development, including mandatory 30-day informal comment periods and public summary responses. This follows amendments approved by the Commission in 2010, emphasizing transparency in the drafting process.

c. Requirements i. Reinforce with the standards drafting teams the need to fully address regulatory directives during development activities such that subsequent modifications to the standards are not necessary, thereby reducing future wor...

AI summary The text emphasizes reinforcing standards drafting teams to address regulatory directives during development to avoid future modifications, reducing workload. NERC has incorporated this into training for standard drafting teams as an ongoing initiative.

d. Ballots i. Permit multiple initial ballots without the need for multiple 30-day pre-ballot review periods. Permit modification to the balloted reliability standard between these multiple initial ballot periods if the ballot results and...

AI summary The text discusses modifying the ballot process for reliability standards to allow multiple initial ballots without separate 30-day reviews, enabling modifications based on feedback. It references the NERC Standard Processes Manual and the Commission's approval of the manual in 2010, which outlines procedures for successive ballots and recirculation.

etter Order issued February 5, 2010 in Docket No. RR10‐04‐000. [Changes to Section 300 of the NERC ROP and/or Appendix 3A — Reliability Standards Development Procedure may be necessary or desirable.] This action has not been comprehensivel...

AI summary The text discusses NERC's revisions to reliability standards development procedures, including the expedited process under the Standard Processes Manual. It references ANSI standard development practices and Commission approvals of revised procedures in June 2010 and September 2010.

f. Training and Support i. Conduct a detailed pre-kickoff session between NERC staff, standard drafting team chairs and vice-chairs, subject matter experts, and regulatory authority staff (if regulatory directives for improvement are invol...

AI summary The text outlines NERC's training and support initiatives for standard drafting teams, including pre-kickoff sessions, enhanced coordinator training, and resource allocation for complex drafting tasks. These measures aim to clarify technical expectations, improve team collaboration, and ensure effective standard development.

6. Provide clear measures for each standard requirement. a. Work with the compliance program to ensure that measures (1) directly correspond to each requirement of each standard describing what an entity has to do to comply, (2) include ex...

AI summary The text emphasizes aligning compliance measures with reliability standards, specifying evidence requirements, and ensuring stakeholder communication through tools like RSAWs. It references NERC's Standard Processes Manual, highlighting feedback during standard development and field testing. Compliance programs must collaborate with standards staff to ensure practical implementation.

B. Organization Registration and Certification 1. Raise threshold criteria for requiring entities to be registered. a. Review existing registration criteria with NERC technical staff for possible changes. This is an ongoing effort. The reg...

AI summary The text discusses revising registration criteria for entities under NERC's Rules of Procedure, influenced by the Commission's order on BES definition. It emphasizes simplification through a bright-line test, exemption procedures, and stakeholder coordination. The project involves NERC technical staff, committees, and industry stakeholders, with a one-year completion deadline.

C. Compliance Monitoring and Enforcement - 1. Put more emphasis on training, education, and assistance regarding what it takes to comply with, and to demonstrate compliance with, reliability standards. - a. Develop a proposed process or pr...

AI summary The section emphasizes enhancing training and education for compliance with reliability standards. NERC considered a no-action letter process but opted for Compliance Application Notices, Reports, and Case Notes instead. The need for registered entities to be aware of existing compliance guidance is highlighted.

10. Basis for penalty determinations needs to be more transparent. a. Conduct a policy-level review of the Sanction Guidelines and address improvements in the penalty determination process. In 2011, NERC is working with the Regional Entiti...

AI summary The document highlights the need for greater transparency in penalty determinations by recommending a policy review of Sanction Guidelines and enabling Regional Entities to seek early NERC involvement in developing Notices of Alleged Violation and Proposed Penalty or Sanction. NERC and Regional Entities have informally implemented the latter measure.

11. Improve system for submitting compliance information. a. Complete the development and implementation of the new database entry and query system. See item C.2.g above and the response to P 217 of the Commission's September 16, 2010 Orde...

AI summary The document outlines actions to improve compliance information systems, including developing a new database, implementing common report forms, and revising delegation agreements. It addresses conflicts between data retention requirements in reliability standards and CMEP, and emphasizes secure handling of critical energy infrastructure information. NERC and Regional Entities are tasked with updating procedures and communicating revised compliance guidelines.

E. Reliability Assessment - 1. Assessment reports need to avoid taking policy advocacy positions and include more support from well-researched information. - a. Investigate and validate assumptions, data, and conclusions in future reliabil...

AI summary NERC is enhancing reliability assessments by avoiding policy advocacy, validating data with Regional Entities, improving metric definitions, and expanding stakeholder feedback processes. Reorganization of LTRAs and peer review refinements aim to increase transparency and technical accuracy in reliability evaluations.

technical committees. - a. NERC CIP and standards staff is taking aggressive efforts and providing specialized support to the Project 2008-06 Cyber Security Order 706 standard drafting team. This is 18 http://www.nerc.com/docs/pc/rmwg/RMWG...

AI summary NERC is revising CIP-002 through CIP-009 reliability standards in response to FERC Order 706, with Phase I revisions adopted in 2009 and Phase II focusing on NIST framework integration. The Critical Asset Identification Guideline was finalized in 2009 for CIP standards Version 1-3.

ng and Education Group. One expected activity of this group is to establish meaningful educational topics that will most benefit the industry. The first meeting of the group is planned for early 2011. - 4. Requirements for training program...

AI summary The Training, Education, and Personnel Certification Group plans its first meeting in 2011 to develop industry-beneficial educational topics. NERC released a white paper in late 2009 on accreditation criteria for training programs, receiving positive feedback but noting the need for incentives to encourage participation in compliance audits. NERC will further evaluate this proposal in 2011.

10. NERC and the Regional Entities should update annually their rolling three-year goals. a. Discuss the proposal with the REBG to identify whether it is generally supported and what steps would be required to implement it. NERC is working...

AI summary NERC and Regional Entities are proposed to annually update their rolling three-year goals. NERC is collaborating with REBG to assess implementation steps, with Strategic Goals for 2012-2014 tied to business planning. The proposal references a Commission order from September 16, 2010.

13. Standardize language and expectations on components of indirect costs. a. In conjunction with the Regional Entities, complete development of a common definition of, and procedures for recording and budgeting, indirect costs. Standard d...

AI summary The document outlines the standardization of indirect cost definitions and procedures, adopted since 2009 and refined in 2011 through amended Regional Delegation Agreements. These agreements, specifically Sections 9(a), (d), (g), (j), and Exhibit E Sections 2 and 5, ensure consistency in business planning and budgeting across Regional Entities. No further changes to the agreements are required.

16. NERC and Regional Entities should use generally accepted accounting principles. a. Continue implementation in the 2010 and future year budgets and in the 2009 and future year reporting of actual costs Generally Accepted Accounting Prin...

AI summary NERC and Regional Entities are required to apply Generally Accepted Accounting Principles (GAAP) in their annual budgets and cost reports, ensuring consistent financial practices for reliability and compliance.

K. Stakeholder Communications and Public Relations - 1. NERC Website functionality and ease of use. - a. NERC will continue to conduct regular surveys of the users of the NERC Website and develop tools to track and measure usability of its...

AI summary NERC is enhancing its website's usability through surveys and implementing improvements, including adding an 'Approvals' box with board and FERC approval dates, and improving access to information on mandatory standards' effective dates. The website coordinator role is being filled to drive these changes.

A Summary of Canadian Provincial Adoption of Reliability Standards Framework

AI summary This document summarizes the adoption of reliability standards by Canadian provinces, focusing on frameworks and compliance mechanisms involving organizations like NERC and FERC.

A Summary of Canadian Provincial Adoption of Reliability Standards Framework This document was prepared by the North American Electric Reliability Corporation (NERC) in consultation with the various Canadian and Provincial jurisdictions ba...

AI summary This document, prepared by NERC, summarizes Canadian provinces' adoption of reliability standards frameworks. It outlines NERC's collaboration with provincial jurisdictions and serves as an informational resource. Contact Ric Cameron for corrections.

Revision History Doc Number Description Created by Revised by Issued Date LEG-CA-GOV v1 Conformed 12-22-2010 Ric Cameron Davis Smith 02-10-2011 working version of document to NERC Template and issued document internally

AI summary The LEG-CA-GOV v1 document, issued on 02-10-2011, reflects a revision history involving Ric Cameron (creator) and Davis Smith (revisor). It describes a working version conforming to NERC standards, using a template and internally issued. The document's purpose is regulatory alignment with NERC requirements.

Alberta: The Alberta Transmission Regulation (Reg 288/2009 as amended) outlines the framework for Reliability Standards in Alberta. The North American Electric Reliability Corporation (NERC) Reliability Standards apply in Alberta to the ex...

AI summary Alberta's Transmission Regulation (2009) integrates NERC Reliability Standards through AESO consultation and Alberta Commission oversight. The Minister of Energy recognized NERC as the ERO in 2007, and the 2009 Electricity Statutes Amendment Act formalized enforcement by the Alberta Commission and MSA, with penalties for non-compliance.

British Columbia: The 2007 provincial Energy Plan committed British Columbia (BC) to "ensure that the province remains consistent with North American transmission reliability standards." With the implementation of the Utilities Commission...

AI summary British Columbia's 2007 Energy Plan aligned with North American reliability standards. The 2009 Utilities Commission Amendment Act granted the BC Utilities Commission (BCUC) exclusive authority to enforce reliability standards, recognizing NERC and WECC as standard-making bodies. The BC Transmission Corporation (BCTC) must review reliability standards' impacts, with BCUC ensuring public access to reports and stakeholder feedback.

Manitoba: Manitoba Hydro is currently required to comply with NERC Reliability Standards through its membership in the Midwest Reliability Organization (MRO) and its membership in NERC, subject to exceptions based on provincial law. Pursua...

AI summary Manitoba Hydro complies with NERC Reliability Standards via membership in MRO, subject to provincial exceptions. The Manitoba Hydro Act (2004) and subsequent legislative amendments establish a framework for enforceable reliability standards, with PUB authorized to enforce compliance. A 2008 agreement with NERC/MRO outlines joint responsibilities, pending new provincial legislation and regulations expected in 2011.

National Energy Board: The National Energy Board (NEB) has statutory responsibility for authorizing the construction and operation of international power lines (IPL) and designated interprovincial power lines and approving electric exports...

AI summary The National Energy Board (NEB) oversees international power lines (IPLs) and interprovincial power lines, enforcing permit conditions without financial penalties. It lacks authority to approve or remand NERC Reliability Standards but collaborates with NERC via a 2006 MOU. The NEB seeks to implement mandatory reliability standards on IPLs through regulation-making.

New Brunswick: The Electricity Act in New Brunswick established the New Brunswick System Operator (NBSO) on October 1, 2004. NBSO is responsible to direct the operation of the transmission grid, to maintain the adequacy and reliability of...

AI summary New Brunswick's Electricity Act established the New Brunswick System Operator (NBSO) in 2004 to manage the transmission grid and ensure system reliability. NERC Reliability Standards are enforced via market rules, with compliance required for licenses. The Public Utilities Board was replaced by the Energy and Utilities Board (EUB) as the regulatory authority.

Ontario: The Electricity Act, 1998 (Ontario) established the Independent Electricity System Operator (IESO). The IESO is responsible for managing Ontario's bulk electric system and operating the wholesale electricity market. A 2004 amendme...

AI summary Ontario's Electricity Act established the IESO and Ontario Power Authority. NERC Reliability Standards are enforced via IESO market rules, with compliance tied to licenses from the Ontario Energy Board. Bill 44 (2008) allows the Board to review NERC standards post-May 2008, limiting applicability to standards approved by the NERC Board of Trustees.

Québec: On December 13, 2006, the Québec Government adopted legislation "An Act Respecting the Implementation of the Québec Energy Strategy and Amending Various Legislative Provisions" (Bill 52) which gave the Régie de l'énergie du Québec...

AI summary Québec adopted Bill 52 in 2006, granting the Régie de l'énergie du Québec authority over reliability standards. The Régie partnered with NERC and NPCC in 2009 to implement compliance programs, including the QCMEP. A 2009 consultation on QROP and QCMEP documents led to revisions by 2010 to ensure consistent enforcement across North America.

Saskatchewan: Prior to 2004, SaskPower generally followed accepted industry practice. In 2004, following the 2003 eastern seaboard blackout, SaskPower committed itself formally to adopt NERC Reliability Standards. SaskPower joined MRO, and...

AI summary SaskPower adopted NERC reliability standards post-2003 blackout, joined MRO, and established a reliability oversight authority under the Power Corporation Act. A 2009 MOU with MRO and NERC outlines their roles as EROs, with Saskatchewan retaining enforcement authority. No penalties are currently envisioned, but future enforcement methods may be considered.

Event Categories and Levels of Analysis The purpose of this document is to identify events that may require further analysis. Each event is categorized to help the Regional Entities (REs) and registered entity(s) impacted determine the app...

AI summary This document outlines a framework for categorizing events requiring analysis, aiding Regional Entities (REs) and impacted registered entities in determining appropriate levels of review or analysis.

Chapter 9 – Scenario Assessment of the NERC Reliability Assessment Guidebook

AI summary This chapter evaluates the NERC Reliability Assessment Guidebook's scenario assessment methods, focusing on ensuring bulk electric system reliability through compliance with mandatory reliability standards and regulatory frameworks.

Dear Ms. McNeil: In accordance with the timeline established in connection with the application of the Northeast Power Coordinating Council, Inc. ("NPCC") for approval of the Regional Reliability Criteria in Nova Scotia, NPCC hereby provid...

AI summary NPCC submits its Final Submission for approval of Regional Reliability Criteria in Nova Scotia, emphasizing enhanced system reliability and alignment with NERC standards. NSPI supports the criteria, noting existing compliance. NPCC recommends quarterly reviews of new reliability standards by NSUARB.

II BACKGROUND [10] The Board exercises general supervision over NSPI pursuant to the Public Utilities Act, R.S.N.S. 1989, c. 380, as amended (the "Acf'). Under the Act, NSPI is required to provide reasonably safe and adequate service and f...

AI summary The Nova Scotia Utility and Review Board (NSUARB) oversees NSPI under the Public Utilities Act. NSPI, NERC, and NPCC established MOUs to enforce reliability standards. NSPI claimed compliance with these standards and recommended their approval, while opposing VRFs and VSLs. The Board must address four issues: standard approval, amendment procedures, VRF/VSL approval, and compliance monitoring.

4. Compliance Monitoring and Enforcement [34] The May 9,2010 MOU provides the following: NSPI, as a Registered Entity, will be subject to NERC's Compliance Monitoring and Enforcement Program ("CMEpl ) as implemented by NPCC. NPCC in its de...

AI summary The May 9, 2010 MOU outlines NSPI's compliance with NERC standards via NPCC's CME program. NPCC may propose non-monetary penalties to the NSUARB for NSPI violations, which the Board would then assess for enforcement. The Board retains authority to determine violations and mitigation but not to impose penalties directly.

IV SUMMARY OF FINDINGS AND DIRECTIVES [36] The Criteria filed by the NPCC are approved. [37] The Standards and associated Glossary of Terms filed by NERC are approved. [38] The Standards and the Criteria are mandatory and enforceable for u...

AI summary The Nova Scotia Utility and Review Board approves NPCC's Criteria and NERC's Standards, mandating their enforcement for bulk power system operators. VRFs and VSLs are accepted for future compliance reviews. An Order will be issued to formalize these directives.

D. Compliance

AI summary The section heading 'D. Compliance' indicates a focus on regulatory compliance requirements, but no substantive content or analysis is provided in the chunk for further elaboration.

1. Compliance Monitoring Process Compliance with the DCS shall be measured on a percentage basis as set forth in the measures above. Each Balancing Authority or Reserve Sharing Group shall submit one completed copy of DCS Form, "NERC Contr...

AI summary Compliance with the Disturbance Control Standard (DCS) is measured as a percentage. Balancing Authorities and Reserve Sharing Groups must submit DCS forms to their Resources Subcommittee by the 10th day of the month following each quarter. Regional Entities must report DCS compliance to NERC by the 20th day of the following month.

1.1. Compliance Enforcement Authority Regional Entity.

AI summary The section titled 'Compliance Enforcement Authority' briefly references a 'Regional Entity' without providing further details or context about its role, responsibilities, or specific regulatory actions.

1.2. Compliance Monitoring Period and Reset Timeframe Compliance for DCS will be evaluated for each reporting period. Reset is one calendar quarter without a violation.

AI summary Compliance for the Disturbance Control Standard (DCS) is evaluated during each reporting period. A reset occurs if there is one consecutive calendar quarter without any violations, indicating successful compliance.

1.3. Compliance Monitoring and Enforcement Processes: Compliance Audits Self-Certifications Spot Checking Compliance Violation Investigations Self-Reporting Complaints

AI summary The section outlines compliance monitoring and enforcement processes, including audits, self-certifications, spot checks, investigations, self-reporting, and handling complaints. These mechanisms ensure adherence to regulatory standards and address violations systematically.

Version History Version Date Action Change Tracking 0 April 1, 2005 Effective Date New 0 August 8, 2005 Removed "Proposed" from Effective Date Errata 0 February 14, 2006 Revised graph on page 3, "10 min." to "Recovery time." Removed fourth...

AI summary The document outlines the version history of a regulatory proceeding, detailing changes and revisions over time, including effective dates, errata, and modifications in response to regulatory orders.

D. Compliance

AI summary The document section titled 'Compliance' is introduced but no specific content or details about compliance requirements, standards, or related proceedings are provided in the text chunk.

1. Compliance Monitoring Process - 1.1. Each Balancing Authority shall submit a monthly summary of Inadvertent Interchange. These summaries shall not include any after-the-fact changes that were not agreed to by the Source Balancing Author...

AI summary The Compliance Monitoring Process outlines requirements for Balancing Authorities to submit monthly Inadvertent Interchange summaries, including accumulation data for On-Peak and Off-Peak periods, deadlines for submission, and obligations for Regional Reliability Organizations to report to NERC. It also mandates AIE Surveys to assess interchange errors.

2. Violation Severity Levels R# Lower VSL Moderate VSL High VSL Severe VSL R1. N/A N/A N/A Each Balancing Authority failed to calculate and record hourly Inadvertent Interchange. R2. N/A N/A The Balancing Authority failed to include all AC...

AI summary This section outlines different levels of violation severity related to balancing authority responsibilities, including failures to calculate inadvertent interchange, include AC tie lines, and ensure proper metering at interconnection points.

C. Measures - M1. Each Reliability Coordinator, Balancing Authority, Transmission Operator, Generator Operator, and Load Serving Entity shall have and provide upon request a procedure (either electronic or hard copy) as defined in Requirem...

AI summary The measures require Reliability Coordinators, Balancing Authorities, Transmission Operators, Generator Operators, and Load Serving Entities to establish and provide procedures for compliance with reliability requirements (M1, M2) and evidence of communication protocols with local law enforcement for sabotage events (M3).

1.1. Compliance Monitoring Responsibility Regional Reliability Organizations shall be responsible for compliance monitoring.

AI summary This section assigns the responsibility for compliance monitoring to Regional Reliability Organizations, emphasizing their role in ensuring adherence to reliability standards within the electricity sector. It underscores the regulatory framework's focus on maintaining system reliability through designated oversight entities.

1.2. Compliance Monitoring and Reset Time Frame One or more of the following methods will be used to verify compliance: - Self-certification (Conducted annually with submission according to schedule.) - Spot Check Audits (Conducted anytime...

AI summary The document outlines compliance verification methods, including self-certification, spot checks, periodic audits, and triggered investigations, with preparation timelines and extension possibilities. The Performance-Reset Period is set to 12 months following the last noncompliance finding, establishing a framework for ongoing regulatory oversight.

1.3. Data Retention Each Reliability Coordinator, Transmission Operator, Generator Operator, Distribution Provider, and Load Serving Entity shall have current, in-force documents available as evidence of compliance as specified in each of...

AI summary The section outlines data retention requirements for entities in the electricity sector, mandating document retention for compliance evidence. Non-compliant entities must retain records until compliance is achieved or for two years plus the current year. Investigation-related evidence is kept for one year post-closure, with the Compliance Monitor retaining audit reports and compliance records.

2. Levels of Non-Compliance: - 2.1. Level 1: There shall be a separate Level 1 non-compliance, for every one of the following requirements that is in violation: - 2.1.1 Does not have procedures for the recognition of and for making its ope...

AI summary The document outlines four levels of non-compliance, with Levels 1 and 3 specifying violations related to procedures for recognizing sabotage events, communicating sabotage information, establishing communication contacts, and providing sabotage response guidelines. Levels 2 and 4 are not applicable.

B. Requirements - R1. Critical Asset Identification Method The Responsible Entity shall identify and document a risk-based assessment methodology to use to identify its Critical Assets. - R1.1. The Responsible Entity shall maintain documen...

AI summary The document outlines requirements for identifying critical assets and cyber assets in the Bulk Electric System. It mandates risk-based assessment methodologies, annual updates to critical asset lists, and senior management approval. Key assets include control centers, transmission substations, generation resources, and systems critical to system restoration and load shedding.

C. Measures - M1. The Responsible Entity shall make available its current risk-based assessment methodology documentation as specified in Requirement R1. - M2. The Responsible Entity shall make available its list of Critical Assets as spec...

AI summary The Responsible Entity must provide documentation on risk-based assessment methodologies, lists of critical and cyber assets, and annual approval records as specified in Requirements R1 through R4.

1.1. Compliance Enforcement Authority - 1.1.1 Regional Entity for Responsible Entities that do not perform delegated tasks for their Regional Entity. - 1.1.2 ERO for Regional Entity. - 1.1.3 Third-party monitor without vested interest in t...

AI summary Section 1.1 outlines compliance enforcement authority, specifying roles for Regional Entities, Electric Reliability Organizations (ERO), and third-party monitors. It emphasizes oversight mechanisms for NERC, including delegated tasks and monitoring by unaffiliated third parties.

1.3. Compliance Monitoring and Enforcement Processes Compliance Audits Self-Certifications Spot Checking Compliance Violation Investigations Self-Reporting Complaints

AI summary The section outlines compliance monitoring and enforcement processes, including audits, self-certifications, spot checks, violation investigations, self-reporting, and complaint handling mechanisms. These processes aim to ensure adherence to regulatory standards and address non-compliance through systematic oversight.

1.4. Data Retention - 1.4.1 The Responsible Entity shall keep documentation required by Standard CIP-002- 3 from the previous full calendar year unless directed by its Compliance Enforcement Authority to retain specific evidence for a long...

AI summary The Responsible Entity must retain documentation from the previous year under CIP-002-3 unless directed otherwise by the Compliance Enforcement Authority, which also retains audit records with the Registered Entity.

4. Applicability: - 4.1. Within the text of Standard CIP-003-3, "Responsible Entity" shall mean: - 4.1.1 Reliability Coordinator. - 4.1.2 Balancing Authority. - 4.1.3 Interchange Authority. - 4.1.4 Transmission Service Provider. - 4.1.5 Tr...

AI summary Defines 'Responsible Entity' under CIP-003-3, lists exemptions for nuclear facilities and certain cyber assets, and sets the effective date based on regulatory approvals.

horizing logical or physical access to protected information. - R5.1.1. Personnel shall be identified by name, title, and the information for which they are responsible for authorizing access. - R5.1.2. The list of personnel responsible fo...

AI summary The text outlines requirements for access control and change management of Critical Cyber Assets. It mandates annual verification of personnel authorizing access, annual review of access privileges, process assessments, and documented change control procedures for hardware/software modifications to Critical Cyber Assets.

1.1. Compliance Enforcement Authority - 1.1.1 Regional Entity for Responsible Entities that do not perform delegated tasks for their Regional Entity. - 1.1.2 ERO for Regional Entity. - 1.1.3 Third-party monitor without vested interest in t...

AI summary Section 1.1 outlines compliance enforcement authority, specifying roles for Regional Entities, Electric Reliability Organizations (ERO), and third-party monitors. It emphasizes oversight mechanisms for NERC, including delegated tasks and monitoring by unaffiliated third parties.

1.3. Compliance Monitoring and Enforcement Processes Compliance Audits Self-Certifications Spot Checking Compliance Violation Investigations Self-Reporting Complaints

AI summary The section outlines compliance monitoring and enforcement processes, including audits, self-certifications, spot checks, violation investigations, self-reporting, and complaint handling mechanisms. These processes aim to ensure adherence to regulatory standards and address non-compliance through systematic oversight.

1.4. Data Retention - 1.4.1 The Responsible Entity shall keep all documentation and records from the previous full calendar year unless directed by its Compliance Enforcement Authority to retain specific evidence for a longer period of tim...

AI summary The Responsible Entity must retain documentation from the previous calendar year, with potential extensions by the Compliance Enforcement Authority during investigations. Audit records, including those from the Registered Entity, must be maintained indefinitely.

1.5. Additional Compliance Information

AI summary The section '1.5. Additional Compliance Information' is a heading in a regulatory proceeding document, indicating the presence of supplementary compliance details, though no specific content is provided in the excerpt.

1.1. Compliance Enforcement Authority - 1.1.1 Regional Entity for Responsible Entities that do not perform delegated tasks for their Regional Entity. - 1.1.2 ERO for Regional Entity. - 1.1.3 Third-party monitor without vested interest in t...

AI summary Section 1.1 outlines compliance enforcement authority, specifying roles for Regional Entities, Electric Reliability Organizations (ERO), and third-party monitors. It emphasizes oversight mechanisms for NERC, including delegated tasks and monitoring by unaffiliated third parties.

1.3. Compliance Monitoring and Enforcement Processes Compliance Audits Self-Certifications Spot Checking Compliance Violation Investigations Self-Reporting Complaints

AI summary The section outlines compliance monitoring and enforcement processes, including audits, self-certifications, spot checks, violation investigations, self-reporting, and complaint handling mechanisms. These processes aim to ensure adherence to regulatory standards and address non-compliance through systematic oversight.

1.4. Data Retention - 1.4.1 The Responsible Entity shall keep personnel risk assessment documents in accordance with federal, state, provincial, and local laws. - 1.4.2 The Responsible Entity shall keep all other documentation required by...

AI summary The Responsible Entity must retain personnel risk assessment documents per applicable laws and CIP-004-3 requirements, retaining records from the prior calendar year unless extended by the Compliance Enforcement Authority. Audit records must be jointly maintained with the Compliance Enforcement Authority.

1.5. Additional Compliance Information

AI summary The section '1.5. Additional Compliance Information' is a heading in a regulatory proceeding document, indicating the presence of supplementary compliance details, though no specific content is provided in the excerpt.

- R1.3. Communication links connecting discrete Electronic Security Perimeters shall not be considered part of the Electronic Security Perimeter. However, end points of these communication links within the Electronic Security Perimeter(s)...

AI summary The text outlines requirements for managing Electronic Security Perimeters and Cyber Assets, emphasizing protection under CIP standards, documentation, and access control policies. It specifies that communication links are not part of the perimeter but endpoints are access points, non-critical assets must be protected under CIP-005-3, and access control must follow deny-by-default models.

D. Compliance

AI summary The 'Compliance' section is a placeholder heading with no substantive content provided in the chunk. It likely refers to regulatory compliance requirements but lacks specific details, arguments, or citations in the current text.

1.3. Compliance Monitoring and Enforcement Processes Compliance Audits Self-Certifications Spot Checking Compliance Violation Investigations Self-Reporting Complaints

AI summary The section outlines compliance monitoring and enforcement processes, including audits, self-certifications, spot checks, violation investigations, self-reporting, and complaint handling mechanisms. These processes aim to ensure adherence to regulatory standards and address non-compliance through systematic oversight.

1.4. Data Retention - 1.4.1 The Responsible Entity shall keep logs for a minimum of ninety calendar days, unless: a) longer retention is required pursuant to Standard CIP-008-3, Requirement R2; b) directed by its Compliance Enforcement Aut...

AI summary The Responsible Entity must retain logs for 90 days, with exceptions under CIP-008-3 R2 or compliance investigations. Documents under CIP-005-3 from the prior year must be kept, and audit records must be retained by the Compliance Enforcement Authority and Registered Entity.

1.1. Compliance Enforcement Authority - 1.1.1 Regional Entity for Responsible Entities that do not perform delegated tasks for their Regional Entity. - 1.1.2 ERO for Regional Entities. - 1.1.3 Third-party monitor without vested interest in...

AI summary The section outlines compliance enforcement mechanisms, including the role of the Electric Reliability Organization (ERO) for Regional Entities and the use of third-party monitors for the North American Electric Reliability Corporation (NERC).

1.3. Compliance Monitoring and Enforcement Processes Compliance Audits Self-Certifications Spot Checking Compliance Violation Investigations Self-Reporting Complaints

AI summary The section outlines compliance monitoring and enforcement processes, including audits, self-certifications, spot checks, violation investigations, self-reporting, and complaint handling mechanisms. These processes aim to ensure adherence to regulatory standards and address non-compliance through systematic oversight.

Interpretation: Dial-up assets are Critical Cyber Assets, assuming they meet the criteria in CIP-002-1, and they must reside within an Electronic Security Perimeter. However, physical security control over a critical cyber asset is not req...

AI summary Dial-up assets are classified as Critical Cyber Assets under CIP-002-1, requiring placement within an Electronic Security Perimeter. However, non-routable protocol dial-up devices (e.g., RTUs) are exempt from Physical Security Perimeter requirements per CIP-006-1. The standard drafting team clarified that such assets do not need full 'six-wall' enclosures if they use non-routable protocols.

D. Compliance 1. Compliance Monitoring Process

AI summary The section outlines the Compliance Monitoring Process but does not provide specific details or discussions about compliance mechanisms, entities involved, or regulatory actions. Further content is required for analysis.

C. Measures - M1. The Responsible Entity shall make available its recovery plan(s) as specified in Requirement R1. - M2. The Responsible Entity shall make available its records documenting required exercises as specified in Requirement R2....

AI summary The Responsible Entity is required to provide documentation related to recovery plans, required exercises, changes to plans, communications, backup storage, and testing of backup media as specified in Requirements R1 through R5. These measures emphasize transparency and compliance with regulatory standards for information management and system reliability.

Version History Version Date Action Change Tracking 2 Modifications to clarify the requirements and to bring the compliance elements into conformance with the latest guidelines for developing compliance elements of standards. Removal of re...

AI summary This document outlines the version history of a regulatory compliance standard, including modifications to clarify requirements, updates to version numbers, and changes in responsible entities and communication timelines. Version 3 was approved by the NERC Board of Trustees on December 16, 2009.

4. Applicability - 4.1. Balancing Authorities. - 4.2. Transmission Operators. - 5. Proposed Effective Date: Twenty-four months after the first day of the first calendar quarter following applicable regulatory approval. In those jurisdictio...

AI summary The section outlines the applicability of requirements to Balancing Authorities and Transmission Operators, with an effective date 24 months after regulatory approval or Board of Trustees adoption if no approval is required.

C. Measures - M1. The Transmission Operator and Balancing Authority shall have its emergency plans available for review by the Regional Reliability Organization at all times. - M2. The Transmission Operator and Balancing Authority shall ha...

AI summary The measures require the Transmission Operator and Balancing Authority to maintain accessible emergency plans and annual self-assessments for review by the Regional Reliability Organization, ensuring compliance with reliability standards.

1.1. Compliance Monitoring Responsibility Regional Reliability Organization.

AI summary The section outlines the responsibility for compliance monitoring, referencing the Regional Reliability Organization. It emphasizes the role of reliability organizations in ensuring adherence to regulatory standards.

1.2. Compliance Monitoring Period and Reset Time Frame The Regional Reliability Organization shall review and evaluate emergency plans every three years to ensure that the plans consider the applicable elements of Attachment 1- EOP-001-0....

AI summary The Regional Reliability Organization must review emergency plans every three years, with potential self-certification by the Transmission Operator and Balancing Authority in non-review years. The reset time frame for compliance monitoring is one calendar year.

B. Energy Emergency Alert Levels

AI summary The section outlines energy emergency alert levels, critical for managing grid reliability and response during crises. It references regulatory frameworks and standards like NERC, FERC, and NSUARB, emphasizing preparedness and operational protocols for energy emergencies.

be terminated. - 4.1. Notification. The Reliability Coordinator shall notify all other Reliability Coordinators via the RCIS of the termination. The Reliability Coordinator shall also notify the affected Balancing Authorities and Transmiss...

AI summary The Reliability Coordinator must notify other Reliability Coordinators, Balancing Authorities, and Transmission Operators of termination via RCIS. Alert 0 must also be posted on the NERC website if originally posted, ensuring transparency in reliability coordination procedures.

D. Compliance - 1. Compliance Monitoring Process - 1.1. Compliance Enforcement Authority Regional Entity. 1.2. Compliance Monitoring Period and Reset Time Frame Not applicable. 1.3. Compliance Monitoring and Enforcement Processes: Complian...

AI summary The compliance section outlines enforcement processes, including audits, self-certifications, and investigations. The Compliance Enforcement Authority is designated as a 'Regional Entity,' and no monitoring period is specified. Methods include spot checks, self-reporting, and handling complaints.

Standard EOP-005-2 — System Restoration from Blackstart Resources o Records of participation in all requested Reliability Coordinator restoration drills, exercises, or simulations since its last compliance audit for Requirement R18, Measur...

AI summary The document outlines requirements for Generation Operators to maintain records of participation in Reliability Coordinator restoration drills and exercises under EOP-005-2. Non-compliance necessitates retaining information until compliance is achieved, with the Compliance Enforcement Authority responsible for audit records.

2.Violation Severity Levels # R L V S L ow er M de V S L te o ra H ig h V S L Se V S L ve re

AI summary This section outlines different levels of violation severity within the regulatory framework, though the content is incomplete and lacks detailed explanations or context regarding the implications of each severity level.

1.2. Compliance Monitoring Period and Reset Time Frame Not applicable.

AI summary The compliance monitoring period and reset time frame are not applicable in this context, indicating no specific requirements or timelines are enforced for compliance tracking.

1.3. Compliance Monitoring and Enforcement Processes: Compliance Audits Self-Certifications Spot Checking Compliance Violation Investigations Self-Reporting Complaints

AI summary Section 1.3 outlines compliance monitoring and enforcement processes including audits, self-certifications, spot checks, violation investigations, self-reporting, and complaint handling mechanisms within the regulatory framework.

1.2. Compliance Monitoring and Enforcement Processes: Compliance Audits Self-Certifications Spot Checking Compliance Violation Investigations Self-Reporting Complaints

AI summary The section outlines compliance monitoring and enforcement processes, including audits, self-certifications, spot checks, violation investigations, self-reporting, and complaint handling mechanisms within regulatory frameworks.

1.2. Compliance Monitoring and Reset Time Frame One or more of the following methods will be used to assess compliance: - Self-certification (Conducted annually with submission according to schedule.) - Spot Check Audits (Conducted anytime...

AI summary The section outlines compliance assessment methods including self-certification, spot checks, periodic audits, and triggered investigations. It specifies a 12-month Performance-Reset Period following the last noncompliance finding, with preparation timelines and extension possibilities for investigations.

1.3. Data Retention Each Balancing Authority shall keep 90 days of historical data (evidence). If an entity is found non-compliant the entity shall keep information related to the noncompliance until found compliant or for two years plus t...

AI summary The data retention requirements mandate Balancing Authorities to retain 90 days of historical data. Non-compliant entities must retain noncompliance-related information until compliance is achieved or for two years plus the current year. Investigated entities must retain evidence for one year post-investigation closure, while the Compliance Monitor retains audit reports and compliance records.

2. Violation Severity Levels: R# Lower VSL Moderate VSL High VSL Severe VSL R1.1.1 The Balancing Authority experienced one instance of entering a schedule into its ACE equation without confirming the schedule as specified in R1, R1.1, R1.1...

AI summary The document outlines violation severity levels (VSL) related to the Balancing Authority's adherence to scheduling procedures within the ACE equation, specifying the number of instances for each severity level.

1.4. Additional Compliance Information Each Interchange Authority shall demonstrate compliance to the Compliance Monitor within the first year that this standard becomes effective or the first year the entity commences operation by self-ce...

AI summary Interchange Authorities must self-certify compliance initially, followed by periodic audits, spot checks, and complaint-driven verification. Compliance data and logs must be available for inspection, with specific requirements for audit periods and complaint-related data.

2. Levels of Non-Compliance - 2.1. Level 1: One occurrence[1](#page-132-0) of not distributing information to all involved reliability entities as described in R1. - 2.2. Level 2: Two occurrences 1 of not distributing information to all in...

AI summary The document outlines four levels of non-compliance based on the number of occurrences of failing to distribute information to reliability entities as required by R1, with Level 4 also including cases where no evidence is provided.

1.4. Additional Compliance Information The Balancing Authority and Transmission Service Provider shall demonstrate compliance to the Compliance Monitor within the first year that this standard becomes effective or the first year the entity...

AI summary The Balancing Authority and Transmission Service Provider must self-certify compliance initially, followed by audits and spot checks. Complaints must be addressed within 60 days, and relevant data must be available for inspection.

Example of Timing Requirements for WECC

AI summary The document presents an example of timing requirements related to the Western Electricity Coordinating Council (WECC), likely illustrating compliance deadlines or procedural timelines for regulatory or operational standards. No explicit content beyond the figure reference is provided in the text.

2. Violation Severity Levels: Requirement Lower Moderate High Severe

AI summary This section outlines the different levels of violation severity, categorizing them into Lower, Moderate, High, and Severe. It appears to be part of a regulatory framework that defines the severity of violations related to reliability and compliance in the electricity sector.

1. Compliance Monitoring Process Entities will be selected for an on-site audit at least every three years. For a selected 30-day period in the previous three calendar months prior to the on site audit, Reliability Coordinators will be ask...

AI summary The compliance monitoring process requires entities to undergo on-site audits every three years. Reliability Coordinators must provide documentation for a 30-day period showing next-day reliability analyses were conducted to ensure bulk power system operability under normal and contingency conditions, including identification of transmission and voltage limits.

D. Compliance - 1. Compliance Monitoring Process - 1.1. Compliance Monitoring Responsibility Regional Reliability Organizations shall be responsible for compliance monitoring. - 1.2. Compliance Monitoring and Reset Time Frame One or more o...

AI summary The compliance monitoring process assigns responsibility to Regional Reliability Organizations. Methods include self-certification, spot checks, periodic audits, and triggered investigations. Noncompliance resets performance metrics after 12 months from the last finding.

1.3. Data Retention For Measures 1 and 11, each Reliability Coordinator shall have its current in-force documents as evidence. For Measures 2–10 and Measure 13, and Measures 15 through 16, the Reliability Coordinator shall keep 90 days of...

AI summary The section outlines data retention requirements for various reliability and transmission entities. Reliability Coordinators, Transmission Operators, Balancing Authorities, and Transmission Service Providers must retain historical data for 90 days. Non-compliance requires retaining records until compliance is achieved or two years plus the current year. Compliance Monitors retain audit reports and compliance records.

1.4. Additional Compliance Information None. - 2. Levels of Non-Compliance for a Transmission Operator, Balancing Authority, Generator Operator, Load-serving Entity, Purchasing-selling Entity and Transmission Service Provider - 2.1. Level...

AI summary Section 2 outlines non-compliance levels for entities like Transmission Operators and Balancing Authorities. Only Level 4 is applicable, requiring adherence to Reliability Coordinator directives (R8 Part 2) and operating within the most limiting parameter (R13 Part 2). Other levels (1–3) are not applicable.

3. Levels of Non-Compliance for a Reliability Coordinator: - 3.1. Level 1: Not applicable. - 3.2. Level 2: Did not make Interchange Transaction information available to all other Reliability Coordinators in the Interconnection. (Requiremen...

AI summary The document outlines non-compliance levels for Reliability Coordinators, detailing violations related to information sharing, GMD response, IROL violations, and system monitoring. Each level (2-4) specifies requirements under NERC standards, emphasizing coordination with Balancing Authorities, Transmission Operators, and Generator Operators to maintain reliability.

4. Levels of Non-Compliance for a Transmission Service Provider - 4.1. Level 1: Not applicable. - 4.2. Level 2: Not applicable. - 4.3. Level 3: Not applicable. - 4.4. Level 4: There shall be a separate Level 4 non-compliance, for every one...

AI summary The document outlines Level 4 non-compliance for a Transmission Service Provider (TSP) when specific requirements are violated, including failure to operate within the most limiting parameter and non-adherence to System Operating Limits (SOLs) or Interconnection Reliability Operating Limits (IROLs) as per filed tariffs.

Violation Severity Levels R # Lower VSL Moderate VSL High VSL Severe VSL R1 The responsible entity received a request to curtail an Interchange Transaction crossing an Interconnection boundary pursuant to an Interconnection-wide transmissi...

AI summary The document outlines violation severity levels (VSL) for different scenarios involving non-compliance with reliability procedures. It specifically highlights a high VSL scenario where an entity fails to comply with a curtailment request from a reliability entity without providing a valid reason.

G. Version History Version Date Action Change Tracking 0 April 1, 2005 Effective Date New 0 August 8, 2005 Removed "Proposed" from Effective Date Errata 1 August 8, 2005 Revised Attachment 1 Revision 3 February 26, 2007 Revised Purpose and...

AI summary This section outlines the version history of a regulatory standard, detailing key revisions and approvals over time, including changes related to NERC/NAESB split and FERC orders.

C. Measures - M1. Each Reliability Coordinator shall provide evidence (such as dated logs, voice recordings, or other information in electronic or hard-copy format) that when acting or instructing others to act to mitigate the magnitude an...

AI summary The document outlines four measures requiring Reliability Coordinators to provide evidence of actions taken during the Eastern Interconnection TLR procedure. These include initiating mitigation steps, identifying TLR levels, notifying other coordinators, and complying with congestion management requests. Each measure specifies documentation requirements and procedural timelines.

D. Compliance - 1. Compliance Monitoring Process - 1.1. Compliance Enforcement Authority Regional Entity. 1.2. Compliance Monitoring and Enforcement Processes: The following processes may be used: - Compliance Audits - Self-Certifications...

AI summary The compliance section outlines processes for monitoring and enforcing compliance, including audits, self-certifications, spot checks, investigations, self-reporting, and complaints. It identifies 'Regional Entity' as the authority responsible for compliance enforcement.

1.3. Data Retention The Reliability Coordinator shall keep data or evidence to show compliance as identified below unless directed by its Compliance Enforcement Authority to retain specific evidence for a longer period of time as part of a...

AI summary The Reliability Coordinator must retain compliance data for 12 months plus the current month, extending retention if non-compliant. The Compliance Enforcement Authority retains audit records. These requirements ensure ongoing compliance verification and investigation readiness.

1.4. Data Retention The Reliability Coordinator shall keep data or evidence to show compliance as identified below unless directed by its Compliance Enforcement Authority to retain specific evidence for a longer period of time as part of a...

AI summary The Reliability Coordinator must retain compliance evidence for specific requirements (R1, R2, R3) and measures (M1, M2, M3) for 30 days to three months, unless the Compliance Enforcement Authority extends retention during investigations. Audit records must also be maintained.

1.1.Compliance Enforcement Authority For Reliability Coordinators and other functional entities that work for the Regional Entity, the ERO shall serve as the Compliance Enforcement Authority. For entities that do not work for the Regional...

AI summary The Compliance Enforcement Authority (CEA) for entities affiliated with the Regional Entity is the Electric Reliability Organization (ERO). For non-affiliated entities, the Regional Entity itself acts as the CEA, establishing a dual-tier enforcement framework based on organizational affiliation.

1.3. Compliance Monitoring and Enforcement Processes Compliance Audits Self-Certifications Spot Checking Compliance Violation Investigations Self-Reporting Complaints

AI summary Section 1.3 outlines compliance monitoring and enforcement processes, including audits, self-certifications, spot checks, violation investigations, self-reporting, and complaint handling mechanisms. These processes ensure adherence to regulatory standards and address non-compliance through structured procedures.

1.4.Data Retention The Balancing Authority, Generator Owner, Generator Operator, Load-Serving Entity, Reliability Coordinator, Transmission Operator and Transmission Owner, shall each keep data or evidence to show compliance as identified...

AI summary The section outlines data retention obligations for entities like Balancing Authorities, Reliability Coordinators, and Transmission Operators, requiring them to maintain compliance evidence for specific periods. The Compliance Enforcement Authority retains audit records, while entities must keep data related to requirements R1, R2, R3 for 90 days.

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.

Interpretation of Requirements R1.2 and R3 Text of Requirements R1.2 and R3 - R1. The Reliability Coordinator shall have a documented specification for data and information to build and maintain models to support Real-time monitoring, Oper...

AI summary The document outlines R1.2 and R3, requiring Reliability Coordinators to document data specifications for real-time monitoring and operational planning, and mandating data provision by entities like Balancing Authorities and Transmission Operators to ensure reliability. Key aspects include mutually agreeable formats, data provision processes, and compliance with reliability standards.

Question 2 Is the intent of Requirement R3 to have each responsible entity provide its own data and information to its Reliability Coordinator, or is the intent to have responsible entities provide aggregated data (collected and compiled f...

AI summary The intent of Requirement R3 is for each responsible entity to ensure its own data is provided to the Reliability Coordinator, even if another entity acts on its behalf. Aggregation of data from other entities is neither intended nor required.

B. Requirements - R1. Each Transmission Operator shall select one of the methodologies[1](#page-17-0) listed below for calculating Available Transfer Capability (ATC) or Available Flowgate Capability (AFC) for each ATC Path per time period...

AI summary The requirements outline methodologies for calculating Available Transfer Capability (ATC) and Available Flowgate Capability (AFC) by Transmission Operators and Service Providers, specifying time periods for calculations and the need for an ATCID document detailing implementation details and counterflow accounting.

C. Measures - M1. The Transmission Operator shall provide evidence (such as a calculation, inclusion of the information in the ATCID, or other written documentation) that it has selected one of the specified methodologies per time period i...

AI summary The measures outline requirements for the Transmission Operator and Service Provider to demonstrate compliance with methodologies for calculating transfer capabilities, maintain ATCID documentation, notify stakeholders, and ensure accessibility. Specific evidence, timeframes, and data submission protocols are mandated under R1-R5.

1.1. Compliance Enforcement Authority Regional Entity.

AI summary The section identifies the Regional Entity as the authority responsible for compliance enforcement under the regulatory framework.

1.4. Compliance Monitoring and Enforcement Processes: The following processes may be used: - Compliance Audits - Self-Certifications - Spot Checking - Compliance Violation Investigations - Self-Reporting - Complaints

AI summary Section 1.4 outlines compliance monitoring and enforcement processes including audits, self-certifications, spot checks, violation investigations, self-reporting, and complaints. These mechanisms ensure adherence to regulatory standards and address non-compliance.

2. Violation Severity Levels R # Lower VSL Moderate VSL High VSL Severe VSL R9 N/A The Transmission Service Provider made the requested data items specified in R9 available to the requesting entities specified within the requirement, per t...

AI summary The document outlines violation severity levels related to the Transmission Service Provider's compliance with data availability requirements under R9. It categorizes the severity based on the number of days the data was made available after a request was received.

Question #1 Is the "advisory ATC" used under the NYISO tariff subject to the ATC calculation and recalculation requirements in MOD-001-1 Requirements R2 and R8? If not, is it necessary to document the frequency of "advisory" calculations i...

AI summary The question examines whether 'advisory ATC' under NYISO's tariff must comply with MOD-001-1 Requirements R2 and R8 for ATC calculations and recalculation. It also asks if documentation of advisory calculation frequency is required in the Responsible Entity's Available Transfer Capability Implementation Document.

D. Compliance

AI summary The Compliance section outlines regulatory requirements and standards for ensuring adherence to reliability, security, and operational protocols within the Nova Scotia electricity sector, referencing key entities and compliance frameworks.

1.1. Compliance Enforcement Authority (CEA) Regional Entity.

AI summary The Compliance Enforcement Authority (CEA) is designated as a Regional Entity within the regulatory framework, indicating its role in overseeing compliance within a specific geographic or operational region.

1.4. Compliance Monitoring and Enforcement Processes: The following processes may be used: - - Compliance Audits - - Self-Certifications - - Spot Checking - - Compliance Violation Investigations - - Self-Reporting - - Complaints - 1.5. Add...

AI summary Section 1.4 outlines compliance monitoring and enforcement processes including audits, self-certifications, spot checks, violation investigations, self-reporting, and complaints. No additional compliance information is provided in section 1.5.

Violation Severity Levels R # S Lo V L er w S M de te V L o ra ig S H h V L Se S V L ve re de i be d in R 5. 2. sc r hs io de i be d in t p a o r r eg ns a s sc r R 5. 2

AI summary The text outlines violation severity levels, referencing various standards and requirements, including R5.2 and other regulatory frameworks, but lacks detailed explanation or context for the classifications provided.

1.1. Compliance Enforcement Authority Regional Entity.

AI summary The section identifies the Regional Entity as the authority responsible for compliance enforcement under the regulatory framework.

1.4. Compliance Monitoring and Enforcement Processes Any of the following may be used: - Compliance Audits - Self-Certifications - Spot Checking - Compliance Violation Investigations - Self-Reporting - Complaints

AI summary The section outlines compliance monitoring and enforcement tools including audits, self-certifications, spot checks, investigations, self-reporting, and complaints. These mechanisms ensure adherence to regulatory standards and address non-compliance.

1.2. Compliance Monitoring Period and Reset Timeframe On request (within 30 calendar days).

AI summary The compliance monitoring period and reset timeframe are established as 30 calendar days upon request, indicating a procedural framework for addressing compliance issues within a defined temporal window.

1.3. Compliance Monitoring and Enforcement Processes: Compliance Audits Self-Certifications Spot Checking Compliance Violation Investigations Self-Reporting Complaints

AI summary The section outlines compliance monitoring and enforcement processes, including audits, self-certifications, spot checks, investigations, self-reporting, and handling complaints. These mechanisms ensure adherence to regulatory standards and address violations systematically.

1.1. Compliance Enforcement Authority Regional Entity.

AI summary The section identifies the Regional Entity as the authority responsible for compliance enforcement under the regulatory framework.

1.3. Data Retention The Transmission Operator and Transmission Service Provider shall keep data or evidence to show compliance as identified below unless directed by its Compliance Enforcement Authority to retain specific evidence for a lo...

AI summary The Transmission Operator and Transmission Service Provider must retain specific compliance data for defined periods, including ATCID versions, TTC models, and evidence for requirements R1-R11. Non-compliance data must be retained until resolution, and audit records are kept by the Compliance Enforcement Authority.

1.4. Compliance Monitoring and Enforcement Processes: The following processes may be used: - - Compliance Audits - - Self-Certifications - - Spot Checking - - Compliance Violation Investigations - - Self-Reporting

AI summary The section outlines compliance monitoring and enforcement processes, including compliance audits, self-certifications, spot checking, compliance violation investigations, and self-reporting.

1.3. Data Retention - The Transmission Operator and Transmission Service Provider shall keep data or evidence to show compliance as identified below unless directed by its Compliance Enforcement Authority to retain specific evidence for a...

AI summary The Transmission Operator and Transmission Service Provider must retain specific data and evidence to demonstrate compliance with regulatory requirements, including models, ATCID versions, TTC study reports, and historical records. Non-compliance information must be retained until resolved, and the Compliance Enforcement Authority retains audit records.

1.4. Compliance Monitoring and Enforcement Processes: The following processes may be used: - - Compliance Audits - - Self-Certifications - - Spot Checking - - Compliance Violation Investigations - - Self-Reporting - - Complaints

AI summary Section 1.4 outlines compliance monitoring and enforcement processes including audits, self-certifications, spot checks, violation investigations, self-reporting, and complaints. These mechanisms ensure adherence to regulatory standards and address non-compliance.

Standard MOD-030-02 — Flowgate Methodology The following processes may be used: - - Compliance Audits - - Self-Certifications - - Spot Checking - - Compliance Violation Investigations - - Self-Reporting - - Complaints

AI summary The document outlines compliance processes under the Flowgate Methodology, including audits, self-certifications, spot checks, violation investigations, self-reporting, and complaints. These mechanisms ensure adherence to regulatory standards in transmission planning and grid management.

1.1. Compliance Monitoring Responsibility Regional Reliability Organizations shall be responsible for compliance monitoring.

AI summary The text assigns responsibility for compliance monitoring to Regional Reliability Organizations (RROs) within the regulatory framework. This outlines a key procedural requirement for ensuring adherence to reliability standards in the electricity sector.

1.2. Compliance Monitoring and Reset Time Frame One or more of the following methods will be used to assess compliance: - Self-certification (Conducted annually with submission according to schedule.) - Spot Check Audits (Conducted anytime...

AI summary The section outlines compliance assessment methods, including self-certification, spot checks, periodic audits, and triggered investigations, with preparation timelines and extension requests. The Performance-Reset Period is defined as 12 months following the last noncompliance finding.

1.3. Data Retention Each Reliability Coordinator shall keep evidence of compliance for the previous two calendar years plus the current year. If an entity is found non-compliant the entity shall keep information related to the noncomplianc...

AI summary The section outlines data retention requirements for Reliability Coordinators, non-compliant entities, and the Compliance Monitor. Entities must retain compliance evidence for two years plus the current year, while investigations require one year of record-keeping post-closure. The Compliance Monitor retains audit reports and compliance records.

2. Levels of Non-Compliance for a Reliability Coordinator (Replaced with VSLs) 2.1.

AI summary The document outlines the replacement of non-compliance levels for a Reliability Coordinator with Violation Severity Levels (VSLs). It introduces a framework for categorizing compliance issues based on severity, though specific criteria or implementation details are not provided in the excerpt.

1. Title: System Personnel Training 2. Number: PER-005-1 3. Purpose: To ensure that System Operators performing real-time, reliability-related tasks on the North American Bulk Electric System (BES) are competent to perform those reliabilit...

AI summary This document outlines the purpose of PER-005-1, which is to ensure that System Operators on the North American Bulk Electric System are competent in performing real-time, reliability-related tasks, as their competency is critical to system reliability.

1.1. Compliance Enforcement Authority For Reliability Coordinators and other functional entities that work for their Regional Entity, the ERO shall serve as the Compliance Enforcement Authority. For entities that do not work for the Region...

AI summary The ERO serves as the Compliance Enforcement Authority for entities affiliated with the Regional Entity, while the Regional Entity itself acts as the authority for non-affiliated entities.

1.3. Compliance Monitoring and Enforcement Processes: Compliance Audits Self-Certifications Spot Checking Compliance Violation Investigations Self-Reporting Complaints

AI summary Section 1.3 outlines compliance monitoring and enforcement processes, including audits, self-certifications, spot checks, violation investigations, self-reporting, and complaint handling mechanisms. These processes ensure adherence to regulatory standards and address non-compliance through structured procedures.

1.4. Data Retention Each Reliability Coordinator, Balancing Authority and Transmission Operator shall keep data or evidence to show compliance for three years or since its last compliance audit, whichever time frame is the greatest, unless...

AI summary The section outlines data retention requirements for Reliability Coordinators, Balancing Authorities, and Transmission Operators, mandating retention for three years or post-last audit, whichever is longer. Non-compliance records must be kept until resolution, and Compliance Enforcement Authorities retain audit records.

1.3. Compliance Monitoring and Enforcement Processes: Compliance Audits Self-Certifications Spot Checking Compliance Violation Investigations Self-Reporting Complaints

AI summary The section outlines compliance monitoring and enforcement processes, including audits, self-certifications, spot checks, investigations, self-reporting, and handling complaints. These mechanisms ensure adherence to regulatory standards and address violations systematically.

1.5. Additional Compliance Information The Transmission Owner, and any Distribution Provider that owns a transmission Protection System and the Generator Owner shall demonstrate compliance through selfcertification or audit (periodic, as p...

AI summary The Transmission Owner, Distribution Provider, and Generator Owner must demonstrate compliance via self-certification or audit, as determined by the Compliance Monitor through periodic checks, targeted monitoring, or complaints/events.

5. Effective Dates 1 : - 5.1. Requirement 1, Requirement 2: - 5.1.1 For circuits described in 4.1.1 and 4.1.3 above (except for switch-on-to-fault schemes) —the beginning of the first calendar quarter following applicable regulatory approv...

AI summary The section outlines effective dates for compliance requirements, with timelines varying by circuit type and regulatory approvals. Temporary exceptions approved by NERC's Planning Committee prior to standard approval avoid noncompliance if mitigation plans are implemented.

r tt nc e se g s ly it h c ite ia in R 1. 1 co mp w r r ho h 1. 1 3 e ist bu i de is t t e ug x s, v nc e inc let inc fo ct om p e o r or re r o ne or f t he br ire nt mo re o su eq u me s. lay in do ly it h Re tt t c se g s no om p w f t...

AI summary The text discusses violation severity levels, referencing standards and requirements related to transmission and generation protection system misoperations within the Bulk Electric System. It mentions PRC-004-2, NERC, IEEE, and specific requirements such as R1, R2, and R3.

D. Compliance

AI summary The Compliance section outlines regulatory requirements and standards for ensuring adherence to reliability, security, and operational protocols within the Nova Scotia electricity sector, referencing key entities and compliance frameworks.

1. Compliance Monitoring Process Each Regional Reliability Organization shall conduct a review every three years to ensure that each responsible entity has a process in place to provide planned generator and/or bulk transmission outage inf...

AI summary The Compliance Monitoring Process mandates that Regional Reliability Organizations (RROs) conduct triennial reviews to ensure responsible entities provide outage information to Reliability Coordinators and neighboring operators. Investigations may be initiated by RROs or NERC upon complaints of non-compliance, with notifications required within 60 days.

1.1. Compliance Monitoring Responsibility A Reliability Coordinator makes a request for an outage to "not be taken" because of a reliability impact on the grid and the outage is still taken. The Reliability Coordinator must provide all its...

AI summary The Reliability Coordinator must document outages within three business days and report compliance and violations to NERC via the NERC Compliance Reporting process.

1.2. Compliance Monitoring Period and Reset Timeframe One calendar year without a violation from the time of the violation.

AI summary The compliance monitoring period is defined as one calendar year without any violations occurring from the time of the violation, establishing a reset timeframe for regulatory adherence.

1.2. Compliance Monitoring Period and Reset Time Frame Periodic Review: Entities will be selected for operational reviews at least every three years. One calendar year without a violation from the time of the violation.

AI summary Entities will undergo operational reviews at least every three years. A one-year period without violations is required for reset time frames following a violation.

2. Levels of Non-Compliance - 2.1. Level 1: Each entity responsible for reporting information under Requirements R1 to R4 is providing the requesting entities with the data required, in specified time intervals and format, but there are pr...

AI summary The document outlines four levels of non-compliance related to data reporting under Requirements R1 to R4. Level 1 identifies consistency issues due to equipment malfunctions or scaling errors, while Level 4 indicates failure to provide required data in terms of content, timeliness, or format. Levels 2 and 3 are not applicable.

Background Information for Interpretation The TOP-005-1 standard focuses on two key obligations. The first key obligation (Requirement R1) is a "responsibility mandate." Requirement R1 establishes who is responsible for the obligation to p...

AI summary The text outlines obligations under TOP-005-1 and IRO standards, emphasizing data sharing responsibilities (R1, R3) and monitoring system conditions (R1, R3, R5). Reliability Coordinators must provide data upon request and maintain communication processes for reliability.

C. Measures M1. Evidence that the Balancing Authority, Transmission Operator, and Purchasing-Selling Entity is providing the information required, within the time intervals specified, and in a format agreed upon by the requesting entities.

AI summary Measure M1 requires the Balancing Authority, Transmission Operator, and Purchasing-Selling Entity to provide required information within agreed time intervals and formats. This ensures transparency and coordination in operational reporting for regulatory oversight.

1.1. Compliance Monitoring Responsibility Self-Certification: Entities shall annually self-certify compliance to the measures as required by its Regional Reliability Organization. Exception Reporting: Each Region shall report compliance an...

AI summary Entities must annually self-certify compliance with reliability measures to their Regional Reliability Organization (RRO), while regions report compliance and violations to NERC through its formal reporting process.

1.2. Compliance Monitoring Period and Reset Time Frame Periodic Review: Entities will be selected for operational reviews at least every three years. One calendar year without a violation from the time of the violation.

AI summary Entities will undergo operational reviews at least every three years. A one-year period without violations is required for reset time frames following a violation.

Background Information for Interpretation The TOP-005-1 standard focuses on two key obligations. The first key obligation (Requirement R1) is a "responsibility mandate." Requirement R1 establishes who is responsible for the obligation to p...

AI summary The TOP-005-1 standard outlines two obligations: R1 (responsibility mandate) for data provision to Reliability Coordinators, and R3 (performance mandate) for data sharing with other reliability entities. The attachment serves as a guideline, not an enforceable requirement. The current version (TOP-005-2a) redefines this as R2.

1.1. Compliance Monitoring Responsibility Regional Reliability Organizations shall be responsible for compliance monitoring.

AI summary This section assigns the responsibility for compliance monitoring to Regional Reliability Organizations, emphasizing their role in ensuring adherence to reliability standards within the electricity sector. It underscores the regulatory framework's focus on maintaining system reliability through designated oversight entities.

1.2. Compliance Monitoring and Reset Time Frame One or more of the following methods will be used to assess compliance: - Self-certification (Conducted annually with submission according to schedule.) - Spot Check Audits (Conducted anytime...

AI summary The section outlines compliance monitoring methods including self-certification, spot checks, periodic audits, and triggered investigations, with specific timelines and procedures. The Performance-Reset Period is defined as 12 months following the last noncompliance finding.

1.3. Data Retention Each Generator Operator shall keep 90 days of historical data (evidence) for Measure 1. Each Transmission Operator and Balancing Authority shall keep 90 days of historical data (evidence) for Measure 2. Each Reliability...

AI summary The data retention requirements specify that Generator Operators, Transmission Operators, and Balancing Authorities must retain historical data for 90 days or longer for specific compliance measures. Non-compliant entities must retain noncompliance information for two years plus the current year. The Compliance Monitor retains audit reports and compliance data.

2. Violation Severity Levels: R# Lower Moderate High Severe R4 N/A N/A The responsible entity has either weather forecasts or past load patterns, available to predict the system's near-term load pattern, but not both. The responsible entit...

AI summary This section outlines violation severity levels for different regulatory rules (R4, R5, R6) related to load prediction, monitoring equipment use, and metering adequacy. Each rule defines the conditions under which violations are categorized as high or severe based on the lack of resources or actions taken by the responsible entity.

4. Applicability: - 4.1. Transmission Operators. - 4.2. Purchasing-Selling Entities. - 4.3. Load Serving Entities. - 5. (Proposed) Effective Date: The first day of the first calendar quarter six months after applicable regulatory approval;...

AI summary Section 4 outlines the applicability of standards to Transmission Operators, Purchasing-Selling Entities, and Load Serving Entities. Section 5 sets the effective date as six months post-regulatory approval or Board of Trustees' adoption, depending on jurisdictional requirements.

D. Compliance 1. Compliance Monitoring Process

AI summary The section outlines the Compliance Monitoring Process but does not provide specific details or discussions about compliance mechanisms, entities involved, or regulatory actions. Further content is required for analysis.

1.1. Compliance Enforcement Authority Regional Entity.

AI summary The section titled 'Compliance Enforcement Authority' briefly references a 'Regional Entity' without providing further details or context about its role, responsibilities, or specific regulatory actions.

1.2. Compliance Monitoring Period and Reset Time Frame One calendar year.

AI summary The compliance monitoring period for the Nova Scotia Utility and Review Board (NSUARB) proceeding is set to one calendar year, establishing a timeframe for assessing adherence to regulatory requirements.

1.3. Compliance Monitoring and Enforcement Processes: Compliance Audits Self-Certifications Spot Checking Compliance Violation Investigations Self-Reporting Complaints

AI summary The section outlines compliance monitoring and enforcement processes, including audits, self-certifications, spot checks, investigations, self-reporting, and handling complaints. These mechanisms ensure adherence to regulatory standards and address violations systematically.

1.4. Data Retention The Transmission Operator shall retain evidence for Measures 1 through 4 for 12 months. The Compliance Monitor shall retain any audit data for three years.

AI summary The Transmission Operator must retain evidence for Measures 1-4 for 12 months, while the Compliance Monitor must retain audit data for three years under data retention requirements.

1.5. Additional Compliance Information The Transmission Operator shall demonstrate compliance through self-certification or audit (periodic, as part of targeted monitoring or initiated by complaint or event), as determined by the Complianc...

AI summary The Transmission Operator must demonstrate compliance via self-certification or audit, as determined by the Compliance Monitor. Methods include periodic audits, targeted monitoring, or complaint/event-triggered reviews.

2. Levels of Non-Compliance for Generator Operator - 2.1. Level 1: There shall be a Level 1 non-compliance if any of the following conditions exist: - 2.1.1 One incident of failing to notify the Transmission Operator as identified in , R3....

AI summary The document defines four levels of non-compliance for generator operators, based on the frequency of incidents related to notifying the Transmission Operator and maintaining voltage/reactive power schedules, with specific thresholds for each level (e.g., Level 1: 1 incident; Level 4: 10+ incidents).

3. Levels of Non-Compliance for Generator Owner: - 3.1.1 Level One: Not applicable. - 3.1.2 Level Two: Documentation of generator step-up transformers and auxiliary transformers with primary voltages equal to or greater than the generator...

AI summary The document outlines four levels of non-compliance for a generator owner, detailing missing documentation for transformer specifications (R4.1.1-R4.1.4) and failure to adjust transformer settings per Transmission Operator guidelines (R5). Levels escalate from documentation gaps to operational non-compliance.

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.

Interpretation: 1. First, does AVR operation in the constant PF or constant Mvar modes comply with R1? Interpretation : No, only operation in constant voltage mode meets this requirement. This answer is predicated on the assumption that th...

AI summary The document interprets regulatory requirements (R1 and R2) for Automatic Voltage Regulator (AVR) operations. It clarifies that constant voltage mode is required for R1 compliance, while R2 allows Transmission Operators to direct non-constant voltage modes if explicitly specified. The Board of Trustees adopted this interpretation on February 10, 2009.

Implementation Milestone Categories The Implementation Plan milestones and schedule to achieve compliance with the NERC Reliability Standards CIP-002 through CIP-009 for newly identified Critical Cyber Assets and newly Registered Entities...

AI summary The document outlines milestones for achieving compliance with NERC CIP-002 through CIP-009 standards for Critical Cyber Assets and newly registered entities. It defines 'CIP compliance implementation program' and 'Auditably Compliant' (AC), emphasizing auditable records for compliance. The plan omits 'Auditably Compliant' dates as they follow 'Compliant' dates by one year.

Implementation Milestone Categories and Schedules Based on the Critical Cyber Asset identification scenarios identified above, the implementation milestone categories and schedules for those scenarios are defined and distinguished below fo...

AI summary The document outlines two implementation scenarios for Critical Cyber Assets under NERC CIP standards. Category 1 applies to Responsible Entities newly identifying Critical Cyber Assets without prior CIP compliance programs, while Category 2 addresses entities adding new Cyber Assets to existing compliance programs. Milestones for Category 1 are detailed in Table 2.

A Merger of Two or More Registered Entities where None of the Predecessor Registered Entities has Identified any Critical Cyber Asset In the case of a business merger or asset acquisition, because there are no identified Critical Cyber Ass...

AI summary In a merger without critical cyber assets, CIP-002 risk-based asset identification must be implemented. The merged entity has one year to combine or maintain separate methodologies under common governance. Annual compliance with CIP-002 R2 is required, with potential expansion to CIP-002 R3 if critical cyber assets are later identified.

tered Entity specific circumstances may dictate or allow the two programs to continue separately. These decisions may be subject to review as part of compliance with NERC Reliability Standard CIP-002. Registered Entities are encouraged whe...

AI summary The document outlines requirements for merging registered entities with critical cyber assets, emphasizing compliance with NERC CIP-002 standards. It mandates maintaining separate CIP programs initially, ensuring combined methodologies retain all predecessor critical assets, and merging under a common governance structure within one year.

Compliance with Standards Once these standards become effective, the Responsible Entities identified in the Applicability section of the standard must comply with the requirements. These Responsible Entities include: - Reliability Coordina...

AI summary The document outlines that once standards take effect, specified Responsible Entities—including Reliability Coordinators, Balancing Authorities, and NERC—must comply with requirements. These entities encompass roles in grid operations, generation, and transmission, emphasizing adherence to regulatory frameworks.

Proposed Effective Date The Responsible Entities shall be compliant with all requirements on the Effective Date specified in each standard.

AI summary The Responsible Entities must comply with all standard requirements on the specified Effective Date, as outlined in regulatory proceedings.

Implementation Plan for Newly Identified Critical Cyber Assets and Newly Registered Entities Concurrently submitted with Version 3 of Cyber Security Standards CIP-002-3 through CIP-009-3 is a separate Implementation Plan document that woul...

AI summary The document introduces an Implementation Plan to address compliance gaps for newly identified Critical Cyber Assets under NERC CIP-002-3 to CIP-009-3. It provides a phased schedule for Responsible Entities to achieve compliance, rectifying the unrealistic requirement in Version 1 to immediately attain 'Auditably Compliant' status. The plan also covers compliance for merged entities and new NERC registry registrants.

Prior Version Implementation Plan Retirement By December 31, 2009, CIP Version 1's Table 1, 2, and 3 Registered Entities that registered prior to December 31, 2007 will have reached the "Compliant" milestone for all CIP Version 1 Requireme...

AI summary The document outlines the retirement of CIP Version 1's Implementation Plan by December 31, 2010, when Table 3 Registered Entities achieve Auditably Compliant status. Compliance milestones for new entities are covered under CIP Version 2, effective April 1, 2010, with Version 3 milestones pending FERC approval.

Implementation of CIP Version 2 and 3 Standards for U.S Nuclear Power Plant Owners and Operators On September 15, 2009, NERC filed for FERC approval an implementation plan for the CIP Version 1 standards (CIP-002-1 through CIP-009-1) for o...

AI summary The document outlines the timeline for implementing NERC CIP Version 2 and 3 standards for U.S. nuclear power plants, aligning compliance with Version 1's schedule. FERC approved Version 2 in 2009, and Version 3 was filed in late 2009. Compliance dates depend on FERC approval and refueling outages, with hypothetical examples provided.

B A L- 0 0 1- 0. 1a R 1. Ea h Ba la in A ho i ha l l o h ha l l in 1 2- h ba is he t ty te t t, t t c nc g u r s p er a s uc on a ro g m on s , f f Co he lo k- in he Ba la in A ho i 's A l t te t t ty tro av er ag e o c c m u a ve ra g es...

AI summary The text discusses a matrix of violation risk factors related to information, including compliance with standards and regulations such as NERC, CIP, and others. It references various entities, acronyms, and potential violations related to reliability and compliance in the energy sector.