Docstoc

WECC-0055 RAS Criterion - Clean as of 3-25-2010

Document Sample
WECC-0055 RAS Criterion - Clean as of 3-25-2010 Powered By Docstoc
					         WECC-0055 RAS / PRC-012 through 014-WECC-CRT-1

                          Criterion Development Roadmap

This section is maintained by the drafting team during the development of the criterion
and will be removed when the criterion becomes effective.

Development Steps Completed:
Completed Actions                                                  Completion Date
 Complete the first draft                                         April 1, 2010
 Post the first draft for 45-day comment                          April 5, 2010
 Meet to answer to comments, address impact statement,            May 27, 2010
  draft responses
 Post responses to 45-day comment on to the WECC Web              June 10, 2010
  site
 Post the second draft for 30-day comment                         June 24, 2010
 Meet to answer comments, address impact statement, draft         July 29, 2010
  responses
 Post responses to 30-day comment on the WECC Web site            August 12, 2010
 (Repeat posting and comments as necessary)
 (Hold tutorial workshops as necessary)
 Final draft with Implementation Plan
 Vote to forward final draft to the Standing Committee
 Standing Committee meets to vote                                 October 2010
 Target to forward approved document to the Board                 October 2010
 Proposed effective date                                          April 2011

Description of Current Draft:

The current draft is designed to document compliance with the “Fill-in-the-Blank”
requirements of NERC Standards PRC-012-0 and PRC-013-0. This criterion
establishes: 1) a review procedure for WECC Remedial Action Schemes (RAS), 2) the
Remedial Action Scheme Reliability Subcommittee as the entity to review and approve
RASs, 3) a mandate to provide data, and 4) the type of data that must be provided.

Parenthetical references to the NERC PRC-012-0 and PRC-013-0 are added to show
why the WECC requirement has been created. At this stage they are not intended to
remain as part of the final criterion though there is nothing prohibiting retention.


Implementation Plan

[Once the criterion is drafted the team needs to devise an implementation plan.]
         WECC-0055 RAS / PRC-012 through 014-WECC-CRT-1

Definitions of Terms Used in Criterion

This section includes all newly defined or revised terms used in the proposed criterion.
Terms already defined in the Reliability Standards Glossary of Terms are not repeated
here. New or revised definitions listed below become approved when the proposed
criterion is approved. When the criterion becomes effective, these definitions will be
removed from the criterion and added to the WECC Glossary.

WECC Type 1 (Wide Area RAS) – RAS that mitigates system conditions resulting from
credible Category B and C contingencies (Planning Event contingencies P1– P7 in new
TPL-001), and whose misoperation or failure to operate would have a significant
adverse impact outside of the local area. Requires WECC review and approval per
PRC-012 and PRC-014. Included in WECC RAS database per PRC-013.

WECC Type 2 (Safety Net) -- RAS that mitigates system conditions resulting from
Category D contingencies (Extreme Event contingencies in new TPL-001), and whose
misoperation or failure to operate could have a significant adverse impact inside or
outside of the local area. Subject to WECC review. Included in WECC RAS database.

WECC Type 3 (Local Area RAS) -- RAS that mitigates system conditions resulting
from Category B and C contingencies (Planning Event contingencies P1– P7 in new
TPL-001), and whose misoperation or failure to operate would have no significant
adverse impact outside of the local area. Does not require WECC review. Not(?)
included in WECC database.

Significant Adverse Impact – One or more of the following post-contingency system
conditions that occur in the affected BES shall be deemed as significant adverse
impact:

     Any angular or voltage instability that cannot be demonstrably contained to a
      well-defined local area
     System dynamic (oscillatory) response that is not demonstrated to be clearly
      positively damped within 30 seconds of the initiating event
     Voltage levels in violation of applicable emergency limits
     Facility loadings in violation of applicable emergency limits

Local Area – The portion of BES in electrical proximity to the contingency location,
typically contained within the footprint of a Transmission Operator or a Balancing
Authority.


Misoperation - Accidental or unintended RAS operation that does not meet the expected
performance, or a RAS failure to operate that causes voltage collapse or cascading outages.
(A regional definition is required by PRC-012-0, R1.6.)
        WECC-0055 RAS / PRC-012 through 014-WECC-CRT-1

Security-Based Misoperation: A Misoperation caused by the incorrect operation
of a Protection System or RAS. Security is a component of reliability and is the
measure of a device’s certainty not to operate falsely.

Dependability-Based Misoperation: Is the absence of a Protection System or
RAS operation when intended. Dependability is a component of reliability and is the
measure of a device’s certainty to operate when required.
     WECC-0055 RAS / PRC-012 through 014-WECC-CRT-1

A. Introduction


    1.    Title:         Remedial Action Scheme Regional Review Procedure

    2.    Number:         WECC-0055/ PRC-012-0 through PRC-013-0-WECC-1-CR

    3.    Purpose:       To develop a regional criterion review procedure to ensure
                         that each Remedial Action Scheme (RAS) within WECC
                         complies with WECC and NERC requirements.

                         This regional criterion was developed pursuant to North
                         American Electric Reliability Corporation (NERC) Reliability
                         Standards PRC-012-0 (Special Protection System Review
                         Procedure) and PRC-013-0 (Special Protection System
                         Database). As such, violation of this regional criterion may
                         lead to penalties or sanctions imposed by NERC for violation
                         of the associated Reliability Standards.

    4. Applicability:

         (This criterion is applicable to each of the following Responsible Entities that
         either uses or is proposing the use of a Remedial Action Scheme within
         WECC.)

         4.1   Transmission Owner
         4.2   Generator Owner
         4.3   Distribution Provider
         4.4   Reliability Assurer (WECC)

    5. Effective Date: On the first day of the first quarter, at least 45 days after
       approval by the WECC Board of Directors (Board).

B. Requirements:

   WR1. The Reliability Assurer (WECC) shall designate the Remedial Action
        Scheme Reliability Subcommittee (RASRS) as the entity responsible for
        the development, and maintenance of the procedures to review and
        approve both the proposed and the existing Remedial Action Schemes
        (RASs) within the Western Interconnection. (PRC-012-0, R.1.8)

   WR2. The Reliability Assurer (WECC) shall approve or deny a RAS for use
        within the Western Interconnection, upon consideration of the Remedial
        Action Scheme Reliability Subcommittee (RASRS) recommendation.
        (PRC-012-0, R.1.8)
  WECC-0055 RAS / PRC-012 through 014-WECC-CRT-1

WR3. The Reliability Assurer (WECC) shall approve a RAS for use within the
     Western Interconnection only if that RASRS confirms the RAS examined
     meets all of the following minimum conditions:

      WR3.1 The RASRS confirms the RAS is designed so that a single RAS
            component failure, when the RAS is intended to operate, does not
            prevent any portion of the interconnected transmission system
            within WECC from meeting the performance requirements defined
            in Reliability Standards TPL-001-0, TPL-002-0, and TPL-003-0.
            (PRC-012-0, R1.3)

      WR3.2 The RASRS confirms that inadvertent operation of the RAS meets
            the same performance requirement (TPL-001-0, TPL-002-0, and
            TPL-003-0) as that required of the contingency for which it was
            designed, and not exceed TPL-003-0. (PRC-012-0, R1.4)

      WR3.3. The RASRS confirms the proposed RAS will coordinate with
             other protection and control systems and applicable WECC
             emergency procedures. (PRC-012-0, R1.5)

WR4. Each Transmission Owner, Generation Owner, or Distribution Provider
     that is a party to a proposed or existing RAS shall complete and forward
     the Attached A to the Reliability Assurer (WECC) no later than January 1
     of the calendar year following the implementation date of this criterion.
     (PRC-012-0, R1.1.)

WR5. The Reliability Assurer (WECC) shall use the data collected from WR4 of
     this criterion to create and maintain a WECC RAS database of RAS
     schemes recommended for or proposed for approval by the RASRS for
     use within the Western Interconnection. Details contained in the database
     shall include, but not be limited to, the following information:

      WR5.1. Specification of the design objectives, contingencies and system
             conditions for which the RAS was designed

      WR5.2. Specification of how the scheme is intended to operate to include
             the actions taken by the RAS in response to Disturbance
             conditions, (and)

      WR5.3. A model of the scheme to include information on detection logic or
             relay settings that control operation of the RAS. (PRC-013, R1.
             Singh recommendation)

WR6. Each Transmission Owner, Generation Owner, or Distribution Provider
     that is a party to an existing WECC RAS shall review the WECC RAS
     database for accuracy no later than July 1 of each calendar year and
  WECC-0055 RAS / PRC-012 through 014-WECC-CRT-1

      report any changes, modifications, retirements or expansions of its RAS to
      the Reliability Assurer no later than August 1 of that year. (If there are no
      changes to the reviewed RAS, the Transmission Owner, Generator
      Owner, or Distribution Provider is required to take no further action.)
      (PRC-012-0, R1.2)

WR7. Each Transmission Owner, Generation Owner, or Distribution Provider
     that is a party to an existing WECC RAS shall submit for approval to the
     Reliability Assurer (WECC) and the RASRS any changes, modifications,
     retirements or expansions of its RAS prior to placing the RAS in service.

WR8. The Reliability Assurer (WECC) shall make available to the RASRS all
     data collected pursuant this criterion, prior to RASRS review and approval
     of a RAS.

WR9. Each Transmission Owner, Generation Owner, or Distribution Provider
     that is an owner of a RAS shall assess those RASs for operation,
     coordination and effectiveness at least once each five years. (PRC-014-
     0, R1)

WR10. Each Transmission Owner, Generation Owner, or Distribution Provider
      that is an owner of a RAS shall report the conclusions of its WR9
      assessment to the Reliability Assurer no later than December 31, of each
      year.
          WECC-0055 RAS / PRC-012 through 014-WECC-CRT-1

    C. Measures

       (Draft your measures after the Requirements have been vetted with the
      industry and are fairly well finalized.)

        WM1. Each [Applicable Entity] shall have evidence proving [this is a mirror
            image of the above Requirement]. (The evidence must prove the
            Applicable Entity performed the Requirement above. It can be as detailed
            as the drafting team wants. Each Requirement and sub-requirement
            above must have a corresponding Measure.)
           WM1.2 [See above.]

       WM2. Each [Applicable Entity] shall produce evidence that [match the
           corresponding Requirement above.]

       WM3. Each [Applicable Entity] shall produce evidence that [match the
           corresponding Requirement above.]

       WM4. Each [Applicable Entity] shall produce evidence that [match the
           corresponding Requirement above.]

       WM5. Each [Applicable Entity] shall produce evidence that [match the
           corresponding Requirement above.]


    D. Version Control

           Version Control shows approval history and summary of changes.
Version     Date             Action                             Change
                                                                Highlights
1                            Version X Posted
2
3
4
         WECC-0055 RAS / PRC-012 through 014-WECC-CRT-1

                                     Attachment A

                 WECC Remedial Action Scheme Information Sheet

This Attachment A is to be completed in accordance with this criterion by all parties to a
proposed or approved Remedial Action Scheme. Please forward to the Director of
Operations for the Western Electricity Coordinating Council and copy the chair of the
Remedial Access Scheme Reliability Subcommittee.


(GOAL: Tailor Attachment A to meet needs of WR4.)

RAS SCHEME PURPOSE AND OVERVIEW (PRC-012-0, R1.2)

Name of the RAS:
Corporate/Utility Owner:
Individual within the owner’s organization who is responsible for the
operation and maintenance of the RAS:
Purpose for the RAS:
Actual or Desired “In-Service” Date:

Provide a description of the RAS to give an overall understanding of the
contingencies and system conditions for which the RAS was designed:
(PRC-013-0, R1.1.)

Provide a map showing the location of the RAS:

Identify other protection and control systems requiring coordination with
the RAS.

Provide a single line drawing(s) showing all sites involved. (The
drawings should provide sufficient information to allow RASRS members
to assess design reliability, and should include information such as the
bus arrangement, circuit breakers, the associated switches, etc. For
each site, indicate whether detection, logic, action, or a combination of
these is present.)

Indicate the type of system reliability studies that were performed and
submit a list of those that are in progress.

Provide a discussion of the impact to the WECC power grid, including
other protection and control systems that result from the actions taken
by the RAS and from its failure to operate as expected.
         WECC-0055 RAS / PRC-012 through 014-WECC-CRT-1


RAS DESIGN (PRC-012-0, R1.2)


Describe the design philosophy (e.g. failure is to be a non-credible
event).

Describe the design criteria (e.g. failure of a single component, element
or system will not jeopardize the successful operation of the RAS).
(PRC-012-0, R1.3?)

Describe the actions taken by the RAS in response to Disturbance
conditions (PRC-013-0, R1.2)

RAS LOGIC (PRC-013-0, R1.3)

Provide a description of the RAS detection Logic in the form of written
text, flow charts, matrix logic tables, timing tables, etc. as appropriate
and identify the inputs and outputs. (Provide appropriate diagrams and
schematics.)

RAS LOGIC HARDWARE (PRC-013-0, R1.3)

Provide a description of the logic hardware (relays, relay settings that
control the operation of the RAS, digital computer, etc.) and describe
how the RAS logic function is achieved. (PRC-013-0, R1.3.)

REDUNDANCY

Provide a discussion of the redundancy configuration and if appropriate,
state why redundancy is not provided. Include discussion of redundant:
a) Detection, b) Power, supplies, batteries and chargers, c)
Telecommunications, d) Logic controllers (if applicable) and e) RAS trip
circuits.

ARMING

Describe how the RAS is armed (i.e. remotely via SCADA, locally,
automatic, etc.).

DETECTION

Define all inputs to the RAS for the scheme to perform its required
purpose. (Examples: a) Devices needed to determine line-end-status
         WECC-0055 RAS / PRC-012 through 014-WECC-CRT-1

such as circuit breaker contacts) and disconnect status, b) Protective
relay inputs, c) Transducer and IED (intelligent electronic device) inputs
(watts, vars, voltage, current), d) Rate-of-change detectors (angle,
power, current, voltage), e) All other inputs (e.g. set points, time from a
GPS clock and wide area measurements such as voltage angle between
two stations), f) Provide details of other remote data gathering or control
equipment.

COORDINATION WITH PROTECTION AND CONTROL SYSTEM (PRC-012-0, R1.5)

Describe all protection and control systems interactions with the RAS, in
addition to the RAS inputs described above.

System configuration changes due to RAS operation do not adversely
affect protective relay functions such as distance relay overcurrent
supervision, breaker failure pickup, switching of potential sources,
overexcitation protection activation, or other functions pertinent to the
specific relays or protection scheme.

If system studies indicate that transient or sustained low voltages are
expected in conjunction with elevated line flows during or after RAS
operation, confirm that any protection settings on affected lines will not
cause cascading outages related to the low system voltages

Potential adverse interactions with any other protection or control
systems.

MULTIFUNCTION DEVICES

A multifunction device is a single device that is used to perform the
function of a RAS in addition to protective relaying and/or SCADA
simultaneously. It is important that other applications in the multifunction
device do not compromise the functionality of the RAS when the device
is in-service or when is being maintained.

Describe how each multifunction device is applied in the RAS.

Show the general arrangement and describe how the multi-function
device is labeled in the design and application, so as to identify the RAS
and other device functions.

Describe the procedures used to isolate the RAS function from other
functions in the device.

Describe the procedures used when each multifunction device is
removed from service and whether any coordination with other
         WECC-0055 RAS / PRC-012 through 014-WECC-CRT-1

protection is required.

Describe how each multifunction device is tested, both for
commissioning and during periodic maintenance testing, with regard to
each function of the device.

Describe how the overall periodic RAS functional and throughput tests
are performed if multifunction devices are used for both local protection
and RAS.

Describe how upgrades to the multifunction device, such as firmware
upgrades, are accomplished. How is the RAS function taken into
consideration?


TELECOMMUNICATIONS

Provide a graphical display or diagram for each telecom path used in the
proposed RAS scheme, including, extent of redundancy employed. See
references. Indicate ownership of the circuits, paths, and segments.
Indicate responsibility for maintenance. If a telecom circuit utilizes a
public network, describe monitoring and maintenance agreements
including repair response, details of availability, and how possible
change of ownership is addressed. Describe maintenance agreements
and response commitments when the RAS communication utilizes
multiple private systems.

Describe and list telecommunications media and electronic equipment
(e.g.., microwave radio, fiber optic cable, multiplex node, power line
carrier, wire pair, etc.) including redundancy employed in each telecom
path. For each of the paths and segments of the RAS, identify the type
of telecom equipment employed. For example, whether analog or digital
licensed microwave radio, unlicensed spread spectrum radio, fiber optic
SONET node, etc. are applied.

Provide a description of common facilities used for each RAS telecom
path and segment that are not specifically excluded from redundancy by
the WECC critical communication circuit design guideline (e.g. towers,
generators, batteries). Identify paths or segments routed through
common equipment chassis such as Digital Cross-connect System,
SONET node, or router. Identify physical media carried or supported by
the same structure, such as a transmission line tower, pole structure, or
duct bank. Discuss outside plant and inside plant routing diversity. See
references.

Provide a discussion of communications system performance including,
         WECC-0055 RAS / PRC-012 through 014-WECC-CRT-1

circuit or path quality in terms of availability. Provide details of reliability
(e.g., availability of 99.95%), and other supporting reliability information
such as equipment age, history, maintenance, etc. Telecommunication
reliability information is the average overall percentage, and not point-to-
point information. See references.

Provide a discussion about performance of any non-deterministic
communication systems used (such as Ethernet). If RAS performance is
dependent upon successful operation through a non-deterministic
communications system or path, then describe how timing and latency
issues will be addressed and verified. Include timing and latency
planning or management and verification for initial commissioning and in
the event of network modifications or additions. Identify which industry
standard is applied. Acknowledge provision of appropriate high voltage
entrance protection if wire pairs are used.

Transfer Trip Equipment - Identify the manufacturer and type (FSK audio
tone, FS carrier, digital, etc.), and provide the logic configuration (dual
channel, pilot tone, etc.). Identify whether internal device medium is
used; e.g. “Relay-to-Relay” communication.

Remedial Actions Initiated - Provide a functional description of the
action(s) produced by the scheme and include a simplified one-line
diagram of the RAS output to the end-device operated by the scheme.


MONITORING

Provide details of RAS monitoring equipment and time resolution,
including station alarms, SCADA monitoring, and Sequence of Events
Recorders.

Provide details of facilities monitored including: a) Equipment self
diagnostics and annunciation, b) Initiation locations, c) Logic facilities, d)
Telecommunications, e) Transfer trip equipment, f) RAS actions

RAS OPERATING PROCEDURES FOR ABNORMAL SYSTEM CONDITIONS

Provide a summary of the operating procedures or the relevant Dispatch
Instructions pertaining to this RAS during abnormal system conditions.
Specifically, address the operating procedures for the following
situations:
a) The RAS operates incorrectly (failure to operate or false operation).
b) One part of a redundant RAS system is unavailable so that complete
redundancy is no longer assured.
c) When unscheduled, or unplanned and not coordinated, unavailability
         WECC-0055 RAS / PRC-012 through 014-WECC-CRT-1

of the subject RAS (complete loss of RAS) impacts operation.
d) When a partial or total loss of input data required for arming
decisions.
e) The actions taken by the RAS in response to Disturbance conditions.
(PRC-013-0, R1.1.2)


COMMISSIONING, MAINTENANCE AND TESTING (PRC-012-0, R1.9)

Describe the RAS commissioning and overall functional test
procedure(s).
Describe the maintenance and test procedures including:
a) The provision of test switches and test facilities
b) Preventative maintenance; both electrical and telecommunication
c) Functional testing, including system end-to-end checks
d) The maintenance and test intervals
e) A copy of the Maintenance and Test Procedure(s).
f) A discussion of power system curtailment during maintenance and test
activities


PERFORMANCE AND OPERATIONAL HISTORY

Provide assurances that the overall performance and operating time of
the RAS will meet the requirements identified in system studies.

When using the existing equipment and components, such as the EMS,
RAS controllers, and arming devices, address the following items as
they pertain to the operational history of such equipment and
procedures.

a) How long has the RAS been in operation and how many times has it
operated?

b) How many times has the RAS failed to operate when it should have?
Provide details of causes and impacts.

c) How many times has it operated unnecessarily? Provide details of
causes and impacts.

d) What modifications, if any, are planned as a result of b and c above?

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:3
posted:12/4/2011
language:English
pages:13