
|

 |

Standards:
Reliability Standards
|
All standards on this page have been approved by the NERC Board of Trustees.
All comments should be forwarded to sarcomm@nerc.net. Questions? E-mail Herb Schrayshuen or call 609-452-8060.
Resource and Demand Balancing (BAL) |
| Number |
Title/Summary |
Date |
|
| BAL-001-0.1a |
Real Power Balancing Control Performance
To maintain Interconnection steady-state frequency within defined limits by balancing real power demand and supply in real-time. [Archive] |
10.29.2008 |
pdf |
| BAL-002-0 |
Disturbance Control Performance
The purpose of the Disturbance Control Standard (DCS) is to ensure the Balancing Authority is able to utilize its Contingency Reserve to balance resources and demand and return interconnection frequency within defined limits following a Reportable Disturbance. Because generator failures are far more common than significant losses of load and because Contingency Reserve activation does not typically apply to the loss of load, the application of DCS is limited to the loss of supply and does not apply to the loss of load. [Archive] |
02.02.2005 |
pdf |
| BAL-002-WECC-1 |
Contingency Reserve (WECC)
Contingency Reserve is required for the reliable operation of the interconnected power system. Adequate generating capacity must be available at all times to maintain scheduled frequency, and avoid loss of firm load following transmission or generation contingencies. This generating capacity is necessary to replace generating capacity and energy lost due to forced outages of generation or transmission equipment. [Archive] |
10.29.2008 |
pdf |
| BAL-003-0.1b |
Frequency Response and Bias
This standard provides a consistent method for calculating the Frequency Bias component of ACE. [Archive] |
10.29.2008 |
pdf |
| BAL-004-0 |
Time Error Correction
The purpose of this standard is to ensure that Time Error Corrections are conducted in a manner that does not adversely affect the reliability of the Interconnection. [Archive] |
02.02.2005 |
pdf |
| BAL-004-1 |
Time Error Correction
The purpose of this standard is to ensure that Time Error Corrections are conducted in a manner that does not adversely affect the reliability of the Interconnection. [Archive] |
03.26.2008 |
pdf |
| BAL-004-WECC-1 |
Automatic Time Error Correction (WECC)
To maintain Interconnection frequency within a predefined frequency profile under all conditions (i.e. normal and abnormal), and to ensure that Time Error Corrections are effectively conducted in a manner that does not adversely affect the reliability of the Interconnection. [Archive] |
01.01.1990 |
pdf |
| BAL-005-0.1b |
Automatic Generation Control
This standard establishes requirements for Balancing Authority Automatic Generation Control (AGC) necessary to calculate Area Control Error (ACE) and to routinely deploy the Regulating Reserve. The standard also ensures that all facilities and load electrically synchronized to the Interconnection are included within the metered boundary of a Balancing Area so that balancing of resources and demand can be achieved. [Archive] |
10.29.2008 |
pdf |
| BAL-006-1 |
Inadvertent Interchange
This standard defines a process for monitoring Balancing Authorities to ensure that, over the long term, Balancing Authority Areas do not excessively depend on other Balancing Authority Areas in the Interconnection for meeting their demand or Interchange obligations. [Archive] |
05.02.2006 |
pdf |
| BAL-006-1.1 |
Inadvertent Interchange
This standard defines a process for monitoring Balancing Authorities to ensure that, over the long term, Balancing Authority Areas do not excessively depend on other Balancing Authority Areas in the Interconnection for meeting their demand or Interchange obligations. [Archive] |
10.29.2008 |
pdf |
| BAL-502-RFC-02 |
Planned Resource Adequacy Assessment (RFC)
To establish common criteria, based on “one day in ten year” loss of Load expectation principles, for the analysis, assessment and documentation of Resource Adequacy for Load in the ReliabilityFirst Corporation (RFC) region. [Archive] |
08.05.2009 |
pdf |
| BAL-STD-002-0 |
Operating Reserves (WECC)
Regional Reliability Standard to address the Operating Reserve requirements of the Western Interconnection. [Archive] |
03.12.2007 |
pdf |
|
Communications (COM) |
| Number |
Title/Summary |
Date |
|
| COM-001-1.1 |
Telecommunications
Each Reliability Coordinator, Transmission Operator and Balancing Authority needs adequate and reliable telecommunications facilities internally and with others for the exchange of Interconnection and operating information necessary to maintain reliability. [Archive] |
10.29.2008 |
pdf |
| COM-002-2 |
Communications and Coordination
To ensure Balancing Authorities, Transmission Operators, and Generator Operators have adequate communications and that these communications capabilities are staffed and available for addressing a real-time emergency condition. To ensure communications by operating personnel are effective. [Archive] |
11.01.2006 |
pdf |
|
Critical Infrastructure Protection (CIP) |
| Number |
Title/Summary |
Date |
|
| CIP-001-1 |
Sabotage Reporting
Disturbances or unusual occurrences, suspected or determined to be caused by sabotage, shall be reported to the appropriate systems, governmental agencies, and regulatory bodies. [Archive] |
11.01.2006 |
pdf |
| CIP-001-1a |
Sabotage Reporting
Disturbances or unusual occurrences, suspected or determined to be caused by sabotage, shall be reported to the appropriate systems, governmental agencies, and regulatory bodies. [Archive] |
02.16.2010 |
pdf |
| CIP-002-1 |
Critical Cyber Asset Identification
NERC Standards CIP-002 through CIP-009 provides a cyber security framework for the identification and protection of Critical Cyber Assets to support reliable operation of the Bulk Electric System.
These standards recognize the differing roles of each entity in the operation of the Bulk Electric System, the criticality and vulnerability of the assets needed to manage Bulk Electric System reliability, and the risks to which they are exposed. Responsible Entities should interpret and apply Standards CIP-002 through CIP-009 using reasonable business judgment.
Business and operational demands for managing and maintaining a reliable Bulk Electric System increasingly rely on Cyber Assets supporting critical reliability functions and processes to communicate with each other, across functions and organizations, for services and data. This results in increased risks to these Cyber Assets.
Standard CIP-002 requires the identification and documentation of the Critical Cyber Assets associated with the Critical Assets that support the reliable operation of the Bulk Electric System. These Critical Assets are to be identified through the application of a risk-based assessment.
Phased-in Implementation: Please see Implementation Plan for complete list of dates for compliance with the requirements. [Archive] [Reference: FAQs] [Reference: Identifying Critical Assets] |
05.02.2006 |
pdf |
| CIP-002-2 |
Cyber Security - Critical Cyber Asset Identification
NERC Standards CIP-002-2 through CIP-009-2 provide a cyber security framework for the identification and protection of Critical Cyber Assets to support reliable operation of the Bulk Electric System. These standards recognize the differing roles of each entity in the operation of the Bulk Electric System, the criticality and vulnerability of the assets needed to manage Bulk Electric System reliability, and the risks to which they are exposed.
Business and operational demands for managing and maintaining a reliable Bulk Electric System increasingly rely on Cyber Assets supporting critical reliability functions and processes to communicate with each other, across functions and organizations, for services and data. This results in increased risks to these Cyber Assets.
Standard CIP-002-2 requires the identification and documentation of the Critical Cyber Assets associated with the Critical Assets that support the reliable operation of the Bulk Electric System. These Critical Assets are to be identified through the application of a risk-based assessment. [Archive] [Reference: Identifying Critical Assets] [Implementation Plan] |
05.06.2009 |
pdf |
| CIP-002-3 |
Cyber Security - Critical Cyber Asset Identification
NERC Standards CIP-002-3 through CIP-009-3 provide a cyber security framework for the identification and protection of Critical Cyber Assets to support reliable operation of the Bulk Electric System. These standards recognize the differing roles of each entity in the operation of the Bulk Electric System, the criticality and vulnerability of the assets needed to manage Bulk Electric System reliability, and the risks to which they are exposed.
Business and operational demands for managing and maintaining a reliable Bulk Electric System increasingly rely on Cyber Assets supporting critical reliability functions and processes to communicate with each other, across functions and organizations, for services and data. This results in increased risks to these Cyber Assets.
Standard CIP-002-3 requires the identification and documentation of the Critical Cyber Assets associated with the Critical Assets that support the reliable operation of the Bulk Electric System. These Critical Assets are to be identified through the application of a risk-based assessment. [Archive] [Reference: Identifying Critical Assets] [Implementation Plan] [Compliance Application Notice] |
12.16.2009 |
pdf |
| CIP-003-1 |
Security Management Controls
Standard CIP-003 requires that Responsible Entities have minimum security management controls in place to protect Critical Cyber Assets. Standard CIP-003 should be read as part of a group of standards numbered Standards CIP-002 through CIP-009. Responsible Entities should interpret and apply Standards CIP-002 through CIP-009 using reasonable business judgment.
Phased-in Implementation: Please see Implementation Plan for complete list of dates for compliance with the requirements. [Archive] [Reference] |
05.02.2006 |
pdf |
| CIP-003-2 |
Cyber Security - Security Management Controls
Standard CIP-003-2 requires that Responsible Entities have minimum security management controls in place to protect Critical Cyber Assets. Standard CIP-003-2 should be read as part of a group of standards numbered Standards CIP-002-2 through CIP-009-2. [Archive] [Implementation Plan] |
05.06.2009 |
pdf |
| CIP-003-3 |
Cyber Security - Security Management Controls
Standard CIP-003-3 requires that Responsible Entities have minimum security management controls in place to protect Critical Cyber Assets. Standard CIP-003-3 should be read as part of a group of standards numbered Standards CIP-002-3 through CIP-009-3. [Archive] [Implementation Plan] |
12.16.2009 |
pdf |
| CIP-004-1 |
Personnel & Training
Standard CIP-004 requires that personnel having authorized cyber or authorized unescorted physical access to Critical Cyber Assets, including contractors and service vendors, have an appropriate level of personnel risk assessment, training, and security awareness. Standard CIP-004 should be read as part of a group of standards numbered Standards CIP-002 through CIP-009. Responsible Entities should interpret and apply Standards CIP-002 through CIP-009 using reasonable business judgment.
Phased-in Implementation: Please see Implementation Plan for complete list of dates for compliance with the requirements. [Archive] [Reference] |
05.02.2006 |
pdf |
| CIP-004-2 |
Cyber Security - Personnel & Training
Standard CIP-004-2 requires that personnel having authorized cyber or authorized unescorted physical access to Critical Cyber Assets, including contractors and service vendors, have an appropriate level of personnel risk assessment, training, and security awareness. Standard CIP-004-2 should be read as part of a group of standards numbered Standards CIP-002-2 through CIP-009-2. [Archive] [Implementation Plan] |
05.06.2009 |
pdf |
| CIP-004-3 |
Cyber Security - Personnel & Training
Standard CIP-004-3 requires that personnel having authorized cyber or authorized unescorted physical access to Critical Cyber Assets, including contractors and service vendors, have an appropriate level of personnel risk assessment, training, and security awareness. Standard CIP-004-3 should be read as part of a group of standards numbered Standards CIP-002-3 through CIP-009-3. [Archive] [Implementation Plan] |
12.16.2009 |
pdf |
| CIP-005-1 |
Electronic Security Perimeter(s)
Standard CIP-005 requires the identification and protection of the Electronic Security Perimeter(s) inside which all Critical Cyber Assets reside, as well as all access points on the perimeter. Standard CIP-005 should be read as part of a group of standards numbered Standards CIP-002 through CIP-009. Responsible Entities should interpret and apply Standards CIP-002 through CIP-009 using reasonable business judgment.
Phased-in Implementation: Please see Implementation Plan for complete list of dates for compliance with the requirements. [Archive] [Reference] |
05.02.2006 |
pdf |
| CIP-005-1a |
Cyber Security - Electronic Security Perimeter(s)
Standard CIP-005 requires the identification and protection of the Electronic Security Perimeter(s) inside which all Critical Cyber Assets reside, as well as all access points on the perimeter. Standard CIP-005 should be read as part of a group of standards numbered Standards CIP-002 through CIP-009. Responsible Entities should interpret and apply Standards CIP-002 through CIP-009 using reasonable business judgment. [Archive] |
02.16.2010 |
pdf |
| CIP-005-2 |
Cyber Security - Electronic Security Perimeter(s)
Standard CIP-005-2 requires the identification and protection of the Electronic Security Perimeter(s) inside which all Critical Cyber Assets reside, as well as all access points on the perimeter. Standard CIP-005-2 should be read as part of a group of standards numbered Standards CIP-002-2 through CIP-009-2. [Archive] [Implementation Plan] |
05.06.2009 |
pdf |
| CIP-005-2a |
Cyber Security - Electronic Security Perimeter(s)
Standard CIP-005-2 requires the identification and protection of the Electronic Security Perimeter(s) inside which all Critical Cyber Assets reside, as well as all access points on the perimeter. Standard CIP-005-2 should be read as part of a group of standards numbered Standards CIP-002-2 through CIP-009-2. [Archive] [Implementation Plan] |
02.16.2010 |
pdf |
| CIP-005-3 |
Cyber Security - Electronic Security Perimeter(s)
Standard CIP-005-3 requires the identification and protection of the Electronic Security Perimeter(s) inside which all Critical Cyber Assets reside, as well as all access points on the perimeter. Standard CIP-005-3 should be read as part of a group of standards numbered Standards CIP-002-3 through CIP-009-3. [Archive] [Implementation Plan] |
12.16.2009 |
pdf |
| CIP-006-1 |
Physical Security of Critical Cyber Assets
Standard CIP-006 is intended to ensure the implementation of a physical security program for the protection of Critical Cyber Assets. Standard CIP-006 should be read as part of a group of standards numbered Standards CIP-002 through CIP-009. Responsible Entities should apply Standards CIP-002 through CIP-009 using reasonable business judgment.
Phased-in Implementation: Please see Implementation Plan for complete list of dates for compliance with the requirements. [Archive] [Reference] |
05.02.2006 |
pdf |
| CIP-006-1a |
Physical Security of Critical Cyber Assets
Standard CIP-006 is intended to ensure the implementation of a physical security program for the protection of Critical Cyber Assets. Standard CIP-006 should be read as part of a group of standards numbered Standards CIP-002 through CIP-009. Responsible Entities should apply Standards CIP-002 through CIP-009 using reasonable business judgment. [Archive] |
02.12.2008 |
pdf |
| CIP-006-1b |
Physical Security of Critical Cyber Assets
Standard CIP-006 is intended to ensure the implementation of a physical security program for the protection of Critical Cyber Assets. Standard CIP-006 should be read as part of a group of standards numbered Standards CIP-002 through CIP-009. Responsible Entities should apply Standards CIP-002 through CIP-009 using reasonable business judgment. [Interpretation A Archive Interpretation B Archive] |
08.05.2009 |
pdf |
| CIP-006-1c |
Cyber Security - Physical Security of Critical Cyber Assets
Standard CIP-006 is intended to ensure the implementation of a physical security program for the protection of Critical Cyber Assets. Standard CIP-006 should be read as part of a group of standards numbered Standards CIP-002 through CIP-009. Responsible Entities should apply Standards CIP-002 through CIP-009 using reasonable business judgment. [Archive] |
02.16.2010 |
pdf |
| CIP-006-2 |
Cyber Security - Physical Security of Critical Cyber Assets
Standard CIP-006-2 is intended to ensure the implementation of a physical security program for the protection of Critical Cyber Assets. Standard CIP-006-2 should be read as part of a group of standards numbered Standards CIP-002-2 through CIP-009-2. [Archive] [Implementation Plan] |
05.06.2009 |
pdf |
| CIP-006-2c |
Cyber Security - Physical Security of Critical Cyber Assets
Standard CIP-006-2 is intended to ensure the implementation of a physical security program for the protection of Critical Cyber Assets. Standard CIP-006-2 should be read as part of a group of standards numbered Standards CIP-002-2 through CIP-009-2. [Archive] [Implementation Plan] |
02.16.2010 |
pdf |
| CIP-006-3 |
Cyber Security - Physical Security of Critical Cyber Assets
Standard CIP-006-3 is intended to ensure the implementation of a physical security program for the protection of Critical Cyber Assets. Standard CIP-006-3 should be read as part of a group of standards numbered Standards CIP-002-3 through CIP-009-3. [Archive] [Implementation Plan] |
12.16.2009 |
pdf |
| CIP-007-1 |
Systems Security Management
Standard CIP-007 requires Responsible Entities to define methods, processes, and procedures for securing those systems determined to be Critical Cyber Assets, as well as the non-critical Cyber Assets within the Electronic Security Perimeter(s). Standard CIP-007 should be read as part of a group of standards numbered Standards CIP-002 through CIP-009. Responsible Entities should interpret and apply Standards CIP-002 through CIP-009 using reasonable business judgment.
Phased-in Implementation: Please see Implementation Plan for complete list of dates for compliance with the requirements. [Archive] [Reference] |
05.02.2006 |
pdf |
| CIP-007-2a |
Cyber Security - Systems Security Management
Standard CIP-007-2 requires Responsible Entities to define methods, processes, and procedures for securing those systems determined to be Critical Cyber Assets, as well as the other (non-critical) Cyber Assets within the Electronic Security Perimeter(s). Standard CIP-007-2 should be read as part of a group of standards numbered Standards CIP-002-2 through CIP-009-2. [Archive] [Implementation Plan] |
11.05.2009 |
pdf |
| CIP-007-3 |
Cyber Security - Systems Security Management
Standard CIP-007-3 requires Responsible Entities to define methods, processes, and procedures for securing those systems determined to be Critical Cyber Assets, as well as the other (non-critical) Cyber Assets within the Electronic Security Perimeter(s). Standard CIP-007-3 should be read as part of a group of standards numbered Standards CIP-002-3 through CIP-009-3. [Archive] [Implementation Plan] |
12.16.2009 |
pdf |
| CIP-008-1 |
Incident Reporting and Response Planning
Standard CIP-008 ensures the identification, classification, response, and reporting of Cyber Security Incidents related to Critical Cyber Assets. Standard CIP-008 should be read as part of a group of standards numbered Standards CIP-002 through CIP-009. Responsible Entities should apply Standards CIP-002 through CIP-009 using reasonable business judgment.
Phased-in Implementation: Please see Implementation Plan for complete list of dates for compliance with the requirements. [Archive] [Reference] |
05.02.2006 |
pdf |
| CIP-008-2 |
Cyber Security - Incident Reporting and Response Planning
Standard CIP-008-2 ensures the identification, classification, response, and reporting of Cyber Security Incidents related to Critical Cyber Assets. Standard CIP-008-2 should be read as part of a group of standards numbered Standards CIP-002-2 through CIP-009-2. [Archive] [Implemenation Plan] |
05.06.2009 |
pdf |
| CIP-008-3 |
Cyber Security - Incident Reporting and Response Planning
Standard CIP-008-3 ensures the identification, classification, response, and reporting of Cyber Security Incidents related to Critical Cyber Assets. Standard CIP-008-23 should be read as part of a group of standards numbered Standards CIP-002-3 through CIP-009-3. [Archive] [Implementation Plan] |
12.16.2009 |
pdf |
| CIP-009-1 |
Recovery Plans for Critical Cyber Assets
Standard CIP-009 ensures that recovery plan(s) are put in place for Critical Cyber Assets and that these plans follow established business continuity and disaster recovery techniques and practices. Standard CIP-009 should be read as part of a group of standards numbered Standards CIP-002 through CIP-009. Responsible Entities should apply Standards CIP-002 through CIP-009 using reasonable business judgment.
Phased-in Implementation: Please see Implementation Plan for complete list of dates for compliance with the requirements. [Archive] [Reference] |
05.02.2006 |
pdf |
| CIP-009-2 |
Cyber Security - Recovery Plans for Critical Cyber Assets
Standard CIP-009-2 ensures that recovery plan(s) are put in place for Critical Cyber Assets and that these plans follow established business continuity and disaster recovery techniques and practices. Standard CIP-009-2 should be read as part of a group of standards numbered Standards CIP-002-2 through CIP-009-2. [Archive] [Implementation Plan] |
05.06.2009 |
pdf |
| CIP-009-3 |
Cyber Security - Recovery Plans for Critical Cyber Assets
Standard CIP-009-3 ensures that recovery plan(s) are put in place for Critical Cyber Assets and that these plans follow established business continuity and disaster recovery techniques and practices. Standard CIP-009-3 should be read as part of a group of standards numbered Standards CIP-002-3 through CIP-009-3. [Archive] [Implementation Plan] |
12.16.2009 |
pdf |
|
Emergency Preparedness and Operations (EOP) |
| Number |
Title/Summary |
Date |
|
| EOP-001-0 |
Emergency Operations Planning
Each Transmission Operator and Balancing Authority needs to develop, maintain, and implement a set of plans to mitigate operating emergencies. These plans need to be coordinated with other Transmission Operators and Balancing Authorities, and the Reliability Coordinator. [Archive] |
02.02.2005 |
pdf |
| EOP-001-1 |
Emergency Operations Planning
Each Transmission Operator and Balancing Authority needs to develop, maintain, and implement a set of plans to mitigate operating emergencies. These plans need to be coordinated with other Transmission Operators and Balancing Authorities, and the Reliability Coordinator. [Archive] |
10.17.2008 |
pdf |
| EOP-001-2 |
Emergency Operations Planning
Each Transmission Operator and Balancing Authority needs to develop, maintain, and implement a set of plans to mitigate operating emergencies. These plans need to be coordinated with other Transmission Operators and Balancing Authorities, and the Reliability Coordinator. [Archive] |
08.05.2009 |
pdf |
| EOP-002-2.1 |
Capacity and Energy Emergencies
To ensure Reliability Coordinators and Balancing Authorities are prepared for capacity and energy emergencies. [Archive] |
10.29.2008 |
pdf |
| EOP-003-1 |
Load Shedding Plans
A Balancing Authority and Transmission Operator operating with insufficient generation or transmission capacity must have the capability and authority to shed load rather than risk an uncontrolled failure of the Interconnection. [Archive] |
11.01.2006 |
pdf |
| EOP-004-1 |
Disturbance Reporting
Disturbances or unusual occurrences that jeopardize the operation of the Bulk Electric System, or result in system equipment damage or customer interruptions, need to be studied and understood to minimize the likelihood of similar events in the future. [Archive]
IROL and Preliminary Disturbance Reporting Form [Word Form] |
11.01.2006 |
pdf |
| EOP-005-1 |
System Restoration Plans
To ensure plans, procedures, and resources are available to restore the electric system to a normal condition in the event of a partial or total shut down of the system. [Archive] |
05.02.2006 |
pdf |
| EOP-005-2 |
System Restoration from Blackstart Resources
Ensure plans, Facilities, and personnel are prepared to enable System restoration from Blackstart Resources to assure reliability is maintained during restoration and priority is placed on restoring the Interconnection. [Archive] |
08.05.2009 |
pdf |
| EOP-006-1 |
Reliability Coordination - System Restoration
The Reliability Coordinator must have a coordinating role in system restoration to ensure reliability is maintained during restoration and priority is placed on restoring the Interconnection. [Archive] |
11.01.2006 |
pdf |
| EOP-006-2 |
System Restoration Coordination
Ensure plans are established and personnel are prepared to enable effective coordination of the System restoration process to ensure reliability is maintained during restoration and priority is placed on restoring the Interconnection. [Archive] |
08.05.2009 |
pdf |
| EOP-007-0 |
Establish, Maintain, and Document a Regional Blackstart Capability Plan
A system Blackstart Capability Plan (BCP) is necessary to ensure that the quantity and location of system blackstart generators are sufficient and that they can perform their expected functions as specified in overall coordinated Regional System Restoration Plans (SRP). [Archive] |
02.02.2005 |
pdf |
| EOP-008-0 |
Plans for Loss of Control Center Functionality
Each reliability entity must have a plan to continue reliability operations in the event its control center becomes inoperable. [Archive] |
02.02.2005 |
pdf |
| EOP-009-0 |
Documentation of Blackstart Generating Unit Test Results
A system Blackstart Capability Plan (BCP) is necessary to ensure that the quantity and location of system blackstart generators are sufficient and that they can perform their expected functions as specified in overall coordinated Regional System Restoration Plans. [Archive] |
02.02.2005 |
pdf |
|
Interconnection Reliability Operations and Coordination (IRO) |
| Number |
Title/Summary |
Date |
|
| IRO-001-1.1 |
Reliability Coordination - Responsibilities and Authorities
Reliability Coordinators must have the authority, plans, and agreements in place to immediately direct reliability entities within their Reliability Coordinator Areas to re-dispatch generation, reconfigure transmission, or reduce load to mitigate critical conditions to return the system to a reliable state. If a Reliability Coordinator delegates tasks to others, the Reliability Coordinator retains its responsibilities for complying with NERC and regional standards. Standards of conduct are necessary to ensure the Reliability Coordinator does not act in a manner that favors one market participant over another. [Archive] |
10.29.2008 |
pdf |
| IRO-002-1 |
Reliability Coordination - Facilities
Reliability Coordinators need information, tools and other capabilities to perform their responsibilities. [Archive] |
11.01.2006 |
pdf |
| IRO-002-2 |
Reliability Coordination - Facilities
Reliability Coordinators need information, tools and other capabilities to perform their responsibilities. [Archive] |
10.17.2008 |
pdf |
| IRO-003-2 |
Reliability Coordination - Wide-Area View
The Reliability Coordinator must have a wide-area view of its own Reliability Coordinator Area and that of neighboring Reliability Coordinators. [Archive] |
11.01.2006 |
pdf |
| IRO-004-1 |
Reliability Coordination - Operations Planning
Each Reliability Coordinator must conduct next-day reliability analyses for its Reliability Coordinator Area to ensure the Bulk Electric System can be operated reliably in anticipated normal and Contingency conditions. System studies must be conducted to highlight potential interface and other operating limits, including overloaded transmission lines and transformers, voltage and stability limits, etc. Plans must be developed to alleviate System Operating Limit (SOL) and Interconnection Reliability Operating Limit (IROL) violations. [Archive] [Compliance Application Notice] |
02.07.2006 |
pdf |
| IRO-004-2 |
Reliability Coordination - Operations Planning
Each Reliability Coordinator must conduct next-day reliability analyses for its Reliability Coordinator Area to ensure the Bulk Electric System can be operated reliably in anticipated normal and Contingency conditions. System studies must be conducted to highlight potential interface and other operating limits, including overloaded transmission lines and transformers, voltage and stability limits, etc. Plans must be developed to alleviate System Operating Limit (SOL) and Interconnection Reliability Operating Limit (IROL) violations. [Archive] |
10.17.2008 |
pdf |
| IRO-005-2 |
Reliability Coordination - Current-Day Operations
The Reliability Coordinator must be continuously aware of conditions within its Reliability Coordinator Area and include this information in its reliability assessments. The Reliability Coordinator must monitor Bulk Electric System parameters that may have significant impacts upon the Reliability Coordinator Area and neighboring Reliability Coordinator Areas. [Archive] |
11.01.2006 |
pdf |
| IRO-005-2a |
Reliability Coordination - Current Day Operations
The Reliability Coordinator must be continuously aware of conditions within its Reliability Coordinator Area and include this information in its reliability assessments. The Reliability Coordinator must monitor Bulk Electric System parameters that may have significant impacts upon the Reliability Coordinator Area and neighboring Reliability Coordinator Areas. [Archive] |
11.05.2009 |
pdf |
| IRO-005-3 |
Reliability Coordination - Current Day Operations
The Reliability Coordinator must be continuously aware of conditions within its Reliability Coordinator Area and include this information in its reliability assessments. The Reliability Coordinator must monitor Bulk Electric System parameters that may have significant impacts upon the Reliability Coordinator Area and neighboring Reliability Coordinator Areas. [Archive] |
10.17.2008 |
pdf |
| IRO-006-3 |
Reliability Coordination - Transmission Loading Relief
Regardless of the process it uses, the Reliability Coordinator must direct its Balancing Authorities and Transmission Operators to return the transmission system to within its Interconnection Reliability Operating Limits as soon as possible, but no longer than 30 minutes. The Reliability Coordinator needs to direct Balancing Authorities and Transmission Operators to execute actions such as reconfiguration, redispatch, or load shedding until relief requested by the TLR process is achieved. [Archive] |
08.02.2006 |
pdf |
| IRO-006-4.1 |
Reliability Coordination - Transmission Loading Relief (TLR)
The purpose of this standard is to provide Interconnection-wide transmission loading relief procedures that can be used to prevent or manage potential or actual SOL and IROL violations to maintain reliability of the Bulk Electric System. [Archive] [Compliance Application Notice] |
04.15.2009 |
pdf |
| IRO-006-WECC-1 |
Qualified Transfer Path Unscheduled Flow Relief (WECC)
Mitigation of transmission overloads due to unscheduled flow on Qualified Transfer Paths. [Archive] |
02.10.2009 |
pdf |
| IRO-008-1 |
Reliability Coordinator Operational Analyses and Real-time Assessments
To prevent instability, uncontrolled separation, or cascading outages that adversely impact the reliability of the interconnection by ensuring that the Bulk Electric System is assessed during the operations horizon. [Archive] |
10.17.2008 |
pdf |
| IRO-009-1 |
Reliability Coordinator Actions to Operate Within IROLs
To prevent instability, uncontrolled separation, or cascading outages that adversely impact the reliability of the interconnection by ensuring prompt action to prevent or mitigate instances of exceeding Interconnection Reliability Operating Limits (IROLs). [Archive] |
10.17.2008 |
pdf |
| IRO-010-1 |
Reliability Coordinator Data Specification and Collection
To prevent instability, uncontrolled separation, or cascading outages that adversely impact the reliability of the interconnection by ensuring the Reliability Coordinator has the data it needs to monitor and assess the operation of its Reliability Coordinator Area. [Archive] |
10.17.2008 |
pdf |
| IRO-010-1a |
Reliability Coordinator Data Specification and Collection
To prevent instability, uncontrolled separation, or cascading outages that adversely impact the reliability of the interconnection by ensuring the Reliability Coordinator has the data it needs to monitor and assess the operation of its Reliability Coordinator Area. [Archive] |
08.05.2009 |
pdf |
| IRO-014-1 |
Procedures, Processes, or Plans to Support Coordination Between Reliability Coordinators
To ensure that each Reliability Coordinator’s operations are coordinated such that they will not have an Adverse Reliability Impact on other Reliability Coordinator Areas and to preserve the reliability benefits of interconnected operations. [Archive] |
02.07.2006 |
pdf |
| IRO-015-1 |
Notifications and Information Exchange Between Reliability Coordinators
To ensure that each Reliability Coordinator’s operations are coordinated such that they will not have an Adverse Reliability Impact on other Reliability Coordinator Areas and to preserve the reliability benefits of interconnected operations. [Archive] |
02.07.2006 |
pdf |
| IRO-016-1 |
Coordination of Real-time Activities Between Reliability Coordinators
To ensure that each Reliability Coordinator’s operations are coordinated such that they will not have an Adverse Reliability Impact on other Reliability Coordinator Areas and to preserve the reliability benefits of interconnected operations. [Archive] |
02.07.2006 |
pdf |
| IRO-STD-006-0 |
Qualified Path Unscheduled Flow Relief (WECC)
Mitigation of transmission overloads due to unscheduled line flow on Qualified Paths. [Archive] |
03.12.2007 |
pdf |
|
Modeling, Data, and Analysis (MOD) |
| Number |
Title/Summary |
Date |
|
| MOD-001-1 |
Available Transmission System Capability
To ensure that calculations are performed by Transmission Service Providers to maintain awareness of available transmission system capability and future flows on their own systems as well as those of their neighbors. [Archive] |
08.26.2008 |
pdf |
| MOD-004-1 |
Capacity Benefit Margin
To promote the consistent and reliable calculation, verification, preservation, and use of Capacity Benefit Margin (CBM) to support analysis and system operations. [Archive] |
11.13.2008 |
pdf |
| MOD-006-0.1 |
Procedures for the Use of Capacity Benefit Margin Values
To promote the consistent and uniform use of transmission Transfer Capability margins calculations among transmission system users. [Archive] |
10.29.2008 |
pdf |
| MOD-007-0 |
Documentation of the Use of Capacity Benefit Margin
To promote the consistent and uniform application of Transfer Capability margin calculations among transmission system users by developing methodologies for calculating Capacity Benefit Margin (CBM). This methodology shall comply with NERC definitions for CBM, the NERC Reliability Standards, and applicable Regional criteria. [Archive] |
02.02.2005 |
pdf |
| MOD-008-1 |
Transmission Reliability Margin Calculation Methodology
To promote the consistent and reliable calculation, verification, preservation, and use of Transmission Reliability Margin (TRM) to support analysis and system operations. [Archive] |
08.26.2008 |
pdf |
| MOD-010-0 |
Steady-State Data for Modeling and Simulation of the Interconnected Transmission System
To establish consistent data requirements, reporting procedures, and system models to be used in the analysis of the reliability of the Interconnected Transmission Systems. [Archive] |
02.02.2005 |
pdf |
| MOD-011-0 |
Maintenance and Distribution of Steady-State Data Requirements and Reporting Procedures
To establish consistent data requirements, reporting procedures, and system models to be used in the analysis of the reliability of the interconnected transmission systems. [Archive] |
02.02.2005 |
pdf |
| MOD-012-0 |
Dynamics Data for Modeling and Simulation of the Interconnected Transmission System
To establish consistent data requirements, reporting procedures, and system models to be used in the analysis of the reliability of the interconnected transmission systems. [Archive] |
02.02.2005 |
pdf |
| MOD-013-1 |
Maintenance and Distribution of Dynamics Data Requirements and Reporting Procedures
To establish consistent data requirements, reporting procedures, and system models to be used in the analysis of the reliability of the interconnected transmission systems. [Archive] |
05.02.2006 |
pdf |
| MOD-014-0 |
Development of Steady-State System Models
To establish consistent data requirements, reporting procedures, and system models to be used in the analysis of the reliability of the interconnected transmission systems. [Archive] |
02.02.2005 |
pdf |
| MOD-015-0 |
Development of Dynamics System Models
To establish consistent data requirements, reporting procedures, and system models to be used in the analysis of the reliability of the interconnected transmission systems. [Archive] |
02.02.2005 |
pdf |
| MOD-015-0.1 |
Development of Dynamics System Models
To establish consistent data requirements, reporting procedures, and system models to be used in the analysis of the reliability of the interconnected transmission systems. [Archive] |
10.29.2008 |
pdf |
| MOD-016-1.1 |
Documentation of Data Reporting Requirements for Actual and Forecast Demands
Net Energy for Load, and Controllable Demand-Side Management Ensure that accurate, actual Demand data is available to support assessments and validation of past events and databases. Forecast Demand data is needed to perform future system assessments to identify the need for system reinforcements for continued reliability. In addition, to assist in proper real-time operating, Load information related to controllable Demand-Side Management (DSM) programs is needed. [Archive] |
10.29.2008 |
pdf |
| MOD-017-0.1 |
Aggregated Actual and Forecast Demands and Net Energy for Load
To ensure that assessments and validation of past events and databases can be performed, reporting of actual Demand data is needed. Forecast demand data is needed to perform future system assessment to identify the need for system reinforcement for continued reliability. In addition to assist in proper real-time operating, load information related to controllable Demand-Side Management programs is needed. [Archive] |
10.29.2008 |
pdf |
| MOD-018-0 |
Treatment of Nonmember Demand Data and How Uncertainties are Addressed in the Forecasts of Demand and Net Energy for Load
To ensure that Assessments and validation of past events and databases can be performed, reporting of actual demand data is needed. Forecast demand data is needed to perform future system assessments to identify the need for system reinforcement for continued reliability. In addition, to assist in proper real-time operating, load information related to controllable Demand-Side Management programs is needed. [Archive] |
02.02.2005 |
pdf |
| MOD-019-0.1 |
Reporting of Interruptible Demands and Direct Control Load Management
To ensure that assessments and validation of past events and databases can be performed, reporting of actual demand data is needed. Forecast demand data is needed to perform future system assessments to identify the need for system reinforcement for continued reliability. In addition, to assist in proper real-time operating, load information related to controllable Demand-Side Management programs is needed. [Archive] |
10.29.2008 |
pdf |
| MOD-020-0 |
Providing Interruptible Demands and Direct Control Load Management Data to System Operators and Reliability Coordinators
To ensure that assessments and validation of past events and databases can be performed, reporting of actual demand data is needed. Forecast demand data is needed to perform future system assessments to identify the need for system reinforcement for continued reliability. In addition to assist in proper real-time operating, load information related to controllable Demand-Side Management programs is needed. [Archive] |
02.02.2005 |
pdf |
| MOD-021-0.1 |
Documentation of the Accounting Methodology for the Effects of Controllable DSM in Demand and Energy Forecasts
To ensure that assessments and validation of past events and databases can be performed, reporting of actual Demand data is needed. Forecast demand data is needed to perform future system assessments to identify the need for system reinforcement for continued reliability. In addition, to assist in proper real-time operating, load information related to controllable Demand-Side Management (DSM) programs is needed. [Archive] |
04.15.2009 |
pdf |
| MOD-024-1 |
Verification of Generator Gross and Net Real Power Capability
To ensure accurate information on generator gross and net Real Power capability is available for steady-state models used to assess Bulk Electric System reliability. [Archive] |
02.07.2006 |
pdf |
| MOD-025-1 |
Verification of Generator Gross and Net Reactive Power Capability
To ensure accurate information on generator gross and net Reactive Power capability is available for steady-state models used to assess Bulk Electric System reliability. [Archive] |
02.07.2006 |
pdf |
| MOD-028-1 |
Area Interchange Methodology
To increase consistency and reliability in the development and documentation of Transfer Capability calculations for short-term use performed by entities using the Area Interchange Methodology to support analysis and system operations. [Archive] |
08.26.2008 |
pdf |
| MOD-029-1 |
Rated System Path Methodology
To increase consistency and reliability in the development and documentation of transfer capability calculations for short-term use performed by entities using the Rated System Path Methodology to support analysis and system operations. [Archive] |
08.26.2008 |
pdf |
| MOD-030-2 |
Flowgate Methodology
To increase consistency and reliability in the development and documentation of transfer capability calculations for short-term use performed by entities using the Flowgate Methodology to support analysis and system operations. [Archive] |
02.10.2009 |
pdf |
|
Protection and Control (PRC) |
| Number |
Title/Summary |
Date |
|
| PRC-001-1 |
System Protection Coordination
To ensure system protection is coordinated among operating entities. [Archive] |
11.01.2006 |
pdf |
| PRC-002-1 |
Define Regional Disturbance Monitoring and Reporting Requirements
Ensure that Regional Reliability Organizations establish requirements for installation of Disturbance Monitoring Equipment (DME) and reporting of Disturbance data to facilitate analyses of events and verify system models. [Archive] |
08.02.2006 |
pdf |
| PRC-003-1 |
Regional Procedure for Analysis of Misoperations of Transmission and Generation Protection Systems
To ensure all transmission and generation Protection System Misoperations affecting the reliability of the Bulk Electric System (BES) are analyzed and mitigated. [Archive] |
02.07.2006 |
pdf |
| PRC-004-1 |
Analysis and Mitigation of Transmission and Generation Protection System Misoperations
Ensure all transmission and generation Protection System Misoperations affecting the reliability of the Bulk Electric System (BES) are analyzed and mitigated. [Archive] |
02.07.2006 |
pdf |
| PRC-004-WECC-1 |
Protection System and Remedial Action Scheme Misoperation (WECC)
Regional Reliability Standard to ensure all transmission and generation Protection System and Remedial Action Scheme (RAS) Misoperations on Transmission Paths and RAS defined in section 4 are analyzed and/or mitigated. [Archive] |
10.29.2008 |
pdf |
| PRC-005-1 |
Transmission and Generation Protection System Maintenance and Testing
To ensure all transmission and generation Protection Systems affecting the reliability of the Bulk Electric System (BES) are maintained and tested. [Archive] |
02.07.2006 |
pdf |
| PRC-006-0 |
Development and Documentation of Regional UFLS Programs
Provide last resort system preservation measures by implementing an Under Frequency Load Shedding (UFLS) program. [Archive] |
02.02.2005 |
pdf |
| PRC-007-0 |
Assuring Consistency of Entity Underfrequency Load Shedding Programs
Provide last resort System preservation measures by implementing an Under Frequency Load Shedding (UFLS) program. [Archive] |
02.02.2005 |
pdf |
| PRC-008-0 |
Implementation and Documentation of Underfrequency Load Shedding Equipment Maintenance Program
Provide last resort system preservation measures by implementing an Under Frequency Load Shedding (UFLS) program. [Archive] |
02.02.2005 |
pdf |
| PRC-009-0 |
Analysis and Documentation of Underfrequency Load Shedding Performance Following an Underfrequency Event
Provide last resort System preservation measures by implementing an Under Frequency Load Shedding (UFLS) program. [Archive] |
02.02.2005 |
pdf |
| PRC-010-0 |
Technical Assessment of the Design and Effectiveness of Undervoltage Load Shedding Program
Provide System preservation measures in an attempt to prevent system voltage collapse or voltage instability by implementing an Undervoltage Load Shedding (UVLS) program. [Archive] |
02.02.2005 |
pdf |
| PRC-011-0 |
Undervoltage Load Shedding System Maintenance and Testing
Provide system preservation measures in an attempt to prevent system voltage collapse or voltage instability by implementing an Undervoltage Load Shedding (UVLS) program. [Archive] |
02.02.2005 |
pdf |
| PRC-012-0 |
Special Protection System Review Procedure
To ensure that all Special Protection Systems (SPS) are properly designed, meet performance requirements, and are coordinated with other protection systems. To ensure that maintenance and testing programs are developed and misoperations are analyzed and corrected. [Archive] |
02.02.2005 |
pdf |
| PRC-013-0 |
Special Protection System Database
To ensure that all Special Protection Systems (SPSs) are properly designed, meet performance requirements, and are coordinated with other protection systems. [Archive] |
02.02.2005 |
pdf |
| PRC-014-0 |
Special Protection System Assessment
To ensure that all Special Protection Systems (SPS) are properly designed, meet performance requirements, and are coordinated with other protection systems. To ensure that maintenance and testing programs are developed and misoperations are analyzed and corrected. [Archive] |
02.02.2005 |
pdf |
| PRC-015-0 |
Special Protection System Data and Documentation
To ensure that all Special Protection Systems (SPS) are properly designed, meet performance requirements, and are coordinated with other protection systems. To ensure that maintenance and testing programs are developed and misoperations are analyzed and corrected. [Archive] |
02.02.2005 |
pdf |
| PRC-016-0.1 |
Special Protection System Misoperations
To ensure that all Special Protection Systems (SPS) are properly designed, meet performance requirements, and are coordinated with other protection systems. To ensure that maintenance and testing programs are developed and misoperations are analyzed and corrected. [Archive] |
10.29.2008 |
pdf |
| PRC-017-0 |
Special Protection System Maintenance and Testing
To ensure that all Special Protection Systems (SPS) are properly designed, meet performance requirements, and are coordinated with other protection systems. To ensure that maintenance and testing programs are developed and misoperations are analyzed and corrected. [Archive] |
02.02.2005 |
pdf |
| PRC-018-1 |
Disturbance Monitoring Equipment Installation and Data Reporting
Ensure that Disturbance Monitoring Equipment (DME) is installed and that Disturbance data is reported in accordance with regional requirements to facilitate analyses of events. [Archive] |
08.02.2006 |
pdf |
| PRC-020-1 |
Under-Voltage Load Shedding Program Database
Ensure that a regional database is maintained for Under-Voltage Load Shedding (UVLS) programs implemented by entities within the Region to mitigate the risk of voltage collapse or voltage instability in the Bulk Electric System (BES). Ensure the UVLS database is available for Regional studies and for dynamic studies and simulations of the BES. [Archive] |
02.07.2006 |
pdf |
| PRC-021-1 |
Under-Voltage Load Shedding Program Data
Ensure data is provided to support the Regional database maintained for Under-Voltage Load Shedding (UVLS) programs that were implemented to mitigate the risk of voltage collapse or voltage instability in the Bulk Electric System (BES). [Archive] |
02.07.2006 |
pdf |
| PRC-022-1 |
Under-Voltage Load Shedding Program Performance
Ensure that Under Voltage Load Shedding (UVLS) programs perform as intended to mitigate the risk of voltage collapse or voltage instability in the Bulk Electric System (BES). [Archive] |
02.07.2006 |
pdf |
| PRC-023-1 |
Transmission Relay Loadability
Protective relay settings shall not limit transmission loadability; not interfere with system operators’ ability to take remedial action to protect system reliability and; be set to reliably detect all fault conditions and protect the electrical network from these faults. [Archive] [Reference] |
02.12.2008 |
pdf |
| PRC-STD-001-1 |
Certification of Protective Relay Applications and Settings (WECC)
Regional Reliability Standard to certify all protective relay applications for the Bulk Power Transmission Paths of the Western Interconnection. [Archive] |
03.12.2007 |
pdf |
| PRC-STD-003-1 |
Protective Relay and Remedial Action Scheme Misoperation (WECC)
Regional Reliability Standard to ensure all transmission and generation Protection System Misoperations affecting the reliability of the Bulk Electric System (BES) are analyzed and mitigated. PRC-STD-003-1 is a Regional Reliability Standard that meets Requirement 1 of the NERC Standard PRC-003-1. [Archive] |
03.12.2007 |
pdf |
| PRC-STD-005-1 |
Transmission Maintenance (WECC)
Regional Reliability Standard to ensure the Transmission Operator or Owner of a transmission path identified in Attachment A perform maintenance and inspection on identified paths as described by its transmission maintenance plan. [Archive] |
03.12.2007 |
pdf |
|
Transmission Operations (TOP) |
| Number |
Title/Summary |
Date |
|
| TOP-001-1 |
Reliability Responsibilities and Authorities
To ensure reliability entities have clear decision-making authority and capabilities to take appropriate actions or direct the actions of others to return the transmission system to normal conditions during an emergency. [Archive] |
11.01.2006 |
pdf |
| TOP-002-2 |
Normal Operations Planning
Current operations plans and procedures are essential to being prepared for reliable operations, including response for unplanned events. [Archive] |
11.01.2006 |
pdf |
| TOP-002-2a |
Normal Operations Planning
Current operations plans and procedures are essential to being prepared for reliable operations, including response for unplanned events. [Archive] [Interpretation] |
02.10.2009 |
pdf |
| TOP-003-0 |
Planned Outage Coordination
Scheduled generator and transmission outages that may affect the reliability of interconnected operations must be planned and coordinated among Balancing Authorities, Transmission Operators, and Reliability Coordinators. [Archive] [Compliance Application Notice] |
02.02.2005 |
pdf |
| TOP-003-1 |
Planned Outage Coordination
Scheduled generator and transmission outages that may affect the reliability of interconnected operations must be planned and coordinated among Balancing Authorities, Transmission Operators, and Reliability Coordinators. [Archive] |
10.17.2008 |
pdf |
| TOP-004-2 |
Transmission Operations
To ensure that the transmission system is operated so that instability, uncontrolled separation, or cascading outages will not occur as a result of the most severe single Contingency and specified multiple Contingencies. [Archive A and Archive B]
TOP-004-0 was revised by the Missing Measures and Compliance Elements Drafting Team and by the Facility Ratings Standard Drafting Team. The Missing Measures and Compliance Elements Drafting Team added measures and compliance elements but did not change the requirement; the Facility Ratings Standard Drafting Team made changes to the requirements but did not modify the measures or compliance elements. Following BOT adoption of both versions of TOP-004-1 on November 1, 2006, a "conformed" version of the standard was developed to merge the two versions of TOP-004-1 into TOP-004-2.
|
11.01.2006 |
pdf |
| TOP-005-1.1 |
Operational Reliability Information
To ensure reliability entities have the operating data needed to monitor system conditions within their areas. [Archive] |
10.29.2008 |
pdf |
| TOP-005-1.1a |
Operational Reliability Information
To ensure reliability entities have the operating data needed to monitor system conditions within their areas. [Archive] |
11.05.2009 |
pdf |
| TOP-005-2 |
Operational Reliability Information
To ensure reliability entities have the operating data needed to monitor system conditions within their areas. [Archive] |
10.17.2008 |
pdf |
| TOP-006-1 |
Monitoring System Conditions
To ensure critical reliability parameters are monitored in real-time. [Archive] |
11.01.2006 |
pdf |
| TOP-006-2 |
Monitoring System Conditions
To ensure critical reliability parameters are monitored in real-time. [Archive] |
10.17.2008 |
pdf |
| TOP-007-0 |
Reporting System Operating Limit (SOL) and Interconnection Reliability Operating Limit (IROL) Violations
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. [Archive] |
02.02.2005 |
pdf |
| TOP-007-WECC-1 |
System Operating Limits (WECC)
When actual flows on Major WECC Transfer Paths exceed System Operating Limits (SOL), their associated schedules and actual flows are not exceeded for longer than a specified time. [Archive] |
10.29.2008 |
pdf |
| TOP-008-1 |
Response to Transmission Limit Violations
To ensure Transmission Operators take actions to mitigate SOL and IROL violations. [Archive] |
11.01.2006 |
pdf |
| TOP-STD-007-0 |
Operating Transfer Capability (WECC)
Regional Reliability Standard to ensure the Operating Transfer Capability limits requirements of the Western Interconnection are not exceeded. [Archive] |
03.12.2007 |
pdf |
|
Transmission Planning (TPL) |
| Number |
Title/Summary |
Date |
|
| TPL-001-0.1 |
System Performance Under Normal (No Contingency) Conditions (Category A)
System simulations and associated assessments are needed periodically to ensure that reliable systems are developed that meet specified performance requirements with sufficient lead time, and continue to be modified or upgraded as necessary to meet present and future system needs. [Archive] |
10.29.2008 |
pdf |
| TPL-002-0a |
System Performance Following Loss of a Single Bulk Electric System Element (Category B)
System simulations and associated assessments are needed periodically to ensure that reliable systems are developed that meet specified performance requirements with sufficient lead time, and continue to be modified or upgraded as necessary to meet present and future system needs. [Archive] |
07.30.2008 |
pdf |
| TPL-002-0b |
System Performance Following Loss of a Single Bulk Electric System Element (Category B)
System simulations and associated assessments are needed periodically to ensure that reliable systems are developed that meet specified performance requirements with sufficient lead time, and continue to be modified or upgraded as necessary to meet present and future system needs. [Archive] |
11.05.2009 |
pdf |
| TPL-003-0a |
System Performance Following Loss of Two or More Bulk Electric System Elements (Category C)
System simulations and associated assessments are needed periodically to ensure that reliable systems are developed that meet specified performance requirements, with sufficient lead time and continue to be modified or upgraded as necessary to meet present and future System needs. [Archive] |
07.30.2008 |
pdf |
| TPL-004-0 |
System Performance Following Extreme Events Resulting in the Loss of Two or More Bulk Electric System Elements (Category D)
System simulations and associated assessments are needed periodically to ensure that reliable systems are developed that meet specified performance requirements, with sufficient lead time and continue to be modified or upgraded as necessary to meet present and future System needs. [Archive] |
02.02.2005 |
pdf |
| TPL-005-0 |
Regional and Interregional Self-Assessment Reliability Reports
To ensure that each Regional Reliability Organization complies with planning criteria, for assessing the overall reliability (Adequacy and Security) of the interconnected Bulk Electric Systems, both existing and as planned. [Archive] |
02.02.2005 |
pdf |
| TPL-006-0 |
Data From the Regional Reliability Organization Needed to Assess Reliability
To ensure that each Regional Reliability Organization complies with planning criteria, for assessing the overall reliability (Adequacy and Security) of the interconnected Bulk Electric Systems, both existing and as planned. [Archive] |
02.02.2005 |
pdf |
| TPL-006-0.1 |
Data From the Regional Reliability Organization Needed to Assess Reliability
To ensure that each Regional Reliability Organization complies with planning criteria, for assessing the overall reliability (Adequacy and Security) of the interconnected Bulk Electric Systems, both existing and as planned. [Archive] |
04.15.2009 |
pdf |
|
Voltage and Reactive (VAR) |
| Number |
Title/Summary |
Date |
|
| VAR-001-1 |
Voltage and Reactive Control
To ensure that voltage levels, reactive flows, and reactive resources are monitored, controlled, and maintained within limits in real time to protect equipment and the reliable operation of the Interconnection. [Implementation Plan] [Archive] |
08.02.2006 |
pdf |
| VAR-002-1 |
Generator Operations for Maintaining Network Voltage Schedules
To ensure generators provide reactive and voltage control necessary to ensure voltage levels, reactive flows, and reactive resources are maintained within applicable Facility Ratings to protect equipment and the reliable operation of the Interconnection. [Implementation Plan] [Archive] |
08.02.2006 |
pdf |
| VAR-002-1.1a |
Generator Operation for Maintaining Network Voltage Schedules
To ensure generators provide reactive and voltage control necessary to ensure voltage levels, reactive flows, and reactive resources are maintained within applicable Facility Ratings to protect equipment and the reliable operation of the Interconnection. [Archive] |
10.29.2008 |
pdf |
| VAR-002-1.1b |
Generator Operation for Maintaining Network Voltage Schedules
To ensure generators provide reactive and voltage control necessary to ensure voltage levels, reactive flows, and reactive resources are maintained within applicable Facility Ratings to protect equipment and the reliable operation of the Interconnection. [Archive] |
02.10.2009 |
pdf |
| VAR-002-WECC-1 |
Automatic Voltage Regulators (AVR) (WECC)
To ensure that Automatic Voltage Regulators on synchronous generators and condensers shall be kept in service and controlling voltage. [Archive] |
10.29.2008 |
pdf |
| VAR-501-WECC-1 |
Power System Stabilizer (PSS) (WECC)
To ensure that Power System Stabilizers (PSS) on synchronous generators shall be kept in service. [Archive] |
10.29.2008 |
pdf |
| VAR-STD-002a-1 |
Automatic Voltage Regulators (WECC)
Regional Reliability Standard to ensure that automatic voltage control equipment on synchronous generators shall be kept in service at all times, unless one of the exemptions listed in Section C (Measures) applies, with outages coordinated to minimize the number out of service at any one time. All synchronous generators with automatic voltage control equipment shall normally be operated in voltage control mode and set to respond effectively to voltage deviations. (Source: WECC Criterion) [Archive] |
03.12.2007 |
pdf |
| VAR-STD-002b-1 |
Power System Stabilizer (WECC)
Regional Reliability Standard to ensure that Power System Stabilizers on generators shall be kept in service at all times, unless one of the exemptions listed in Section C (Measures) applies, and shall be properly tuned in accordance with WECC requirements. (Source: WECC Criterion) [Archive] |
03.12.2007 |
pdf |
|
|
|

|
 |