Master/Local Control Center Procedure No. 13 (M/LCC 13) Communications Between the ISO and Local Control Centers

Transcription

1 Master/LCC Procedure No Communications Master/Local Control Center Procedure No. 13 (M/LCC 13) Communications 1. References Background Responsibilities Procedure Basic Protocol for All Operational Communications ISO and LCC Communications Involving Normal Operations ISO and LCC Emergency Communications Determine NERC Event Analysis Reporting Requirements Revision History Attachments This document is controlled when viewed on the ISO New England Internet web site. When downloaded and printed, this document becomes UNCONTROLLED, and users should check the Internet web site to ensure that they have the latest version. In addition, a Controlled Copy is available in the Master Control Room procedure binders at the ISO. Rev. 13 Page 1 of 12

2 1. References NERC Reliability Standard COM Telecommunications NERC Reliability Standard COM Communications and Coordination NPCC Directory #7 Special Protection Systems ISO New England Operating Procedure No. 4 - Action During a Capacity Deficiency (OP-4) ISO New England Operating Procedure No. 7 - Action in an Emergency (OP-7) ISO New England Operating Procedure No Emergency Incident and Disturbance Notifications (OP-10) ISO New England Operating Procedure No Analysis of Power System Incidents (OP-20) Master/Local Control Center Procedure No.1 - Nuclear Plant Transmission Operations (M/LCC 1) Master Local Control Center Procedure No. 2 - Abnormal Conditions Alert (M/LCC 2) Master/Local Control Center Procedure No. 4 - Emergency Load Reduction Plans for Mitigating IROL Violations (M/LCC 4) Master/Local Control Center Procedure No Verification of New England System Restoration Plan (M/LCC 11) Master/Local Control Center Procedure No Coordination of Responsibilities to Comply With NERC Standards for Transmission Operations (M/LCC 12) SOP-RTMKTS Implement Operations During Abnormal Conditions SOP-RTMKTS Implement Capacity Remedial Action SOP-RTMKTS Communicate With Internal and External Parties CROP.50001, Reporting Procedure Rev. 13 Page 2 of 12

3 2. Background The intent of Master/Local Control Center No Communications Between ISO and the Local Control Centers (M/LCC 13) is to establish common protocols for communication between ISO New England (ISO) and each Local Control Center (LCC) for effective communications by operating personnel. NERC Reliability Standard COM Telecommunications and NERC Reliability Standard COM Communications and Coordination set requirements for effective communications. ISO and each LCC have internal communication procedures already established (e.g., for ISO, SOP-RTMKTS Communicate With Internal and External Parties), however M/LCC 13 is intended to supplement those procedures and provide specific guidance for communications between the ISO and each LCC System Operators. 3. Responsibilities 1. ISO and each LCC are responsible for precise, accurate, and professional communications involving the collaborative efforts to meet Transmission Operator requirements as set forth in Master/Local Control Center Procedure No Coordination of Responsibilities to Comply With NERC Standards for Transmission Operations (M/LCC 12). 2. ISO and each LCC are responsible for gathering and providing complete and accurate information during operational communications. NOTE Although not required, it is considered a best practice to use three part communication when issuing an instruction or when its use will enhance communication. 3. ISO and each LCC are responsible for performing three part communications to further the goal of maintaining operating directives that are performed accurately and efficiently. Rev. 13 Page 3 of 12

4 4. Procedure 4.1 Basic Protocol for All Operational Communications NOTE NERC Reliability Standard COM Telecommunications requires that English be spoken for all communications unless agreed to otherwise. The Basic Protocols referred to in this section apply to communications between ISO, each LCC and each external recipient of a directive for system operations. The initial communication each shift between ISO and each LCC requires stating names and locations. Subsequent communication during the shift between ISO and each LCC, it is acceptable to state names only. 1. Verbal communication is extremely important and the primary method by which the ISO and LCC System Operators provide and receive information. ISO and LCC System Operators verbal communications make use of the following standard practices: A. When communicating, identify yourself, including your name and location. B. Separate the conversational portion of a discussion from the portion when a decision, directive or instruction is being delivered. C. Communications should always be precise, accurate, and professional. D. Be proactive rather than reactive in communications. Doing so provides up to date information for both the LCC and ISO. E. Whenever possible, limit all unnecessary distractions that could hamper good communications. F. Communication must be free of ambiguity. Avoid the use of slang terms and words that have a similar sound. Use correct nomenclature for any devices mentioned. G. Be direct. Use simple, straightforward language. Avoid technical terms and acronyms. Be aware that technical terms, jargon, and acronyms may be confusing and meaningless to people with backgrounds and experience different from your own. H. Make every effort to provide clear communications and intentions that are understood completely. Listen to cues from the other party to gauge their interest in your comments. If they sound confused or distracted, stop speaking and make sure the conversation is on track. If there is a concern of misunderstanding or confusion, stop the evolution and resolve the concerns. I. Communications with team members should be concise and prioritized such that the meaning of urgent or high consequence data is conveyed with minimum distraction and delay. Rev. 13 Page 4 of 12

5 J. If a request for information is received, obtain the information and promptly communicate it back to the party or provide them with a knowledgeable contact. 2. After an exchange of general operational information, the discussion should be summarized and acknowledged by the recipient by repeating back enough information in summary so that the sender knows his message was received correctly. 3. When issuing instructions which require a discrete action of the receiving party, ISO and LCC System Operators should practice the use of three-part communications, described as: A. Issue instructions in a clear, concise, and definitive manner. B. Verify the recipient of the instruction repeats the information back correctly. C. Acknowledge the response as correct or repeat the original instruction to resolve any misunderstandings. NOTE During contingency situations, communications between the ISO Control Room and the LCCs should be performed under the guidance set forth in Attachment A - Contingency Actions and Communications Protocol. 4. Three part communication is required for all directives issued. Directives are defined to include (and only include) the following types of instructions issued or communications: A. Request made for implementation or termination of Simultaneous Activation of Ten- Minute Reserve (SAR) assistance or Mutual Reserve Assistance (MRA). B. Transmission equipment change of state or status to mitigate a transmission limit exceedance. C. Generator dispatch order to mitigate a transmission limit exceedance. D. Implementation or cancellation of any Action of ISO New England Operating Procedure No. 4 - Action During a Capacity Deficiency (OP-4). E. Interruption or restoration of actual firm load as an action of either ISO New England Operating Procedure No. 7 Action in an Emergency (OP-7) or Master/Control Center Procedure No. 4 - Emergency Load Reduction Plans for Mitigating IROL Violations (M/LCC 4). 5. The recipient of a directive reports back to the entity issuing the directive when the directed actions have been implemented. Rev. 13 Page 5 of 12

6 4.2 ISO and LCC Communications Involving Normal Operations NOTE Each routine Generator/DARD dispatch by ISO is not communicated to the applicable LCC verbally and does not require any special communications protocols. 1. For each of the following conditions, the ISO Generation Operator or ISO Loader Operator immediately makes the specified notification(s) : If a Generator greater than 400 MW trips, notify each LCC If a Generator greater than 100 MW trips and is in close proximity to a neighboring LCC, notify each applicable LCC If significant tie line changes occur, notify each affected LCC If a significant Generator/DARD Redeclaration occurs, notify each affected LCC If a Generator Automatic Voltage Regulator (AVR) or Power System Stabilizer (PSS) or governor device is inoperable, notify the applicable LCC 2. The ISO Senior System Operator communicates Time Error Correction (TEC) to each LCC. 3. The ISO Security System Operator communicates system security issues that suddenly emerge to each affected LCC. 4. When an LCC becomes aware of a system security issue, transmission outage, or voltage/reactive control problem, the LCC communicates that condition to the ISO System Operators. 5. When exceeding an operating limit, the ISO Security Operator and each affected LCC discuss the actions needed to resolve the exceedance as follows: A. Operating Limits: o Normal rating, precontingent; RTNET/SCADA (thermal or voltage) o Contingency Analysis reporting an STE exceedance o Contingency Analysis reporting a voltage exceedance o Interface limit B. Actions to be performed: (1) Confirm the contingency and limiting element Rev. 13 Page 6 of 12

7 (2) Compare results i. If results are different, determine reason for difference of results (3) Implement no cost options: i. Adjust Phase Shifting Transformers ii. Use of weather sensitive ratings iii. Evaluate reactive flows for potential adjustments to alleviate exceedance (4) Activate constraint and dispatch generation 6. The ISO Security System Operator maintains close communication with each LCC during any tight operating reserve situation. 7. If ISO is operating close to any security operating limit or if there is any security doubt or concern, the Security Operator notifies each applicable LCC of any status changes in a Generator/DARD that may affect the security operating limit in question. NOTE Attachment B - Accepted SPS Terminology, is a listing of terms that are expected to be used when communicating the state of an Special Protection System (SPS). 8. The ISO System Operator provides agreement to the applicable LCC prior to changing the state of a Type I or Type II SPS. 9. Each LCC notifies and obtains agreement from the ISO System Operator prior to changing the state of a Type I or Type II SPS. 10. Each LCC notifies the ISO System Operator when the state of a Type III SPS or Automatic Control Scheme (ACS) is changed. 11. When providing instructions to change a Generator voltage schedule, the LCC or ISO System Operator communicates the revised voltage setpoint to the Generator Operator and informs the Generator Operator to maintain their Automatic Voltage Regulator (AVR) in automatic voltage control Mode For example: Increase your voltage schedule to kv and maintain AVR in automatic voltage control mode. 12. When ISO is notified by an entity other than the LCC of a failure or test failure of a Key Facility Critical Component (KFCC) listed on the Master/Local Control Center Procedure No Verification of New England System Restoration Plan (M/LCC 11) Attachment D - Restoration Plan Resources List, the ISO System Operator notifies the LCC System Operator of the KFCC status change. Rev. 13 Page 7 of 12

8 13. When an LCC is aware of an unplanned outage due to failure during testing or operation of either a KFCC listed on M/LCC 11 Attachment D - Restoration Plan Resources List, or a non-identified piece of equipment considered a Critical Component to System Restoration, the LCC System Operator communicates that outage to ISO by performing the following actions: A. Create an Information Outage in the ISO Outage Scheduling software as follows: (1) Search and enter the affected station in the 1-Line Designation field (2) Select the affected Station (3) From the Constraints/Commitment drop-down menu select KF Impact (4) In the Reason/Priority section, record the details that identify the exact piece of equipment B. Contact and notify the ISO Security Operator of the submitted Informational Outage Application and discuss the outage pertinent details. C. When the facility is returned to service, the LCC Operator notifies the ISO Security Operator. 14. When an LCC loses the ability to shed load, the applicable LCC notifies ISO. Rev. 13 Page 8 of 12

9 4.3 ISO and LCC Emergency Communications NOTE OP-4 provides the specific messages that are to be used when communicating OP-4 Steps. OP-7 provides the specific messages to be used when communicating OP-7 Steps. M/LCC 4 provides specific messages to be used when communicating verbal instructions for load shed to alleviate an IROL contingency to the LCC. 1. If ISO or any LCC evacuates to their Backup Control Center (BCC), ISO notifies each LCC and each adjoining Reliability Coordinator / Balancing Authority (RC/BA) of the situation. 2. When ISO declares M/LCC 2, ISO immediately performs M/LCC 2 notifications to each LCC as directed in SOP-RTMKTS Implement Operations During Abnormal Conditions. 3. When ISO declares OP-4, ISO immediately performs OP-4 notifications to each LCC as directed in SOP-RTMKTS Implement Capacity Remedial Action. 4. When ISO implements OP-7 action(s), ISO immediately notifies each LCC. 5. If load shedding is required due to an IROL exceedance referenced in M/LCC 4, ISO immediately notifies each LCC. 6. If ISO and any LCC are both not able to monitor system reliability (i.e., ISO EMS and the LCC EMS systems are not operable at the same time), the ISO Senior System Operator notifies each affected nuclear power Generator Operator to take all of the appropriate required action(s). 7. When any LCC declares M/LCC 2 or OP-4, ISO immediately notifies each remaining LCC. 8. When ISO and/or any LCC are required to perform emergency reporting / communications, ISO and/or the LCC refers to ISO New England Operating Procedure No Emergency Incident and Disturbance Notifications (OP-10) and ISO New England Operating Procedure No Analysis of Power System Incidents (OP-20). 9. When ISO and/or LCC emergency reporting / communications are required: A. ISO performs the applicable actions of SOP-RTMKTS Communicate with Internal and External Parties and/or CROP Reporting Procedure. B. Each LCC performs actions prescribed in the LCC internal procedure(s) for emergency reporting / communications. Rev. 13 Page 9 of 12

10 4.4 Determine NERC Event Analysis Reporting Requirements 1. When a transmission system event requires ISO and/or LCC NERC Event Analysis Reporting, the ISO Shift Supervisor performs the following actions: A. Refers to CROP.50001, Reporting Procedure to determine if the event meets the NERC Event Analysis Categories and to determine the required event analysis reporting actions. B. Contacts the applicable LCC, discusses the event and based on the severity of the event: (1) Determines which organization perform the event analysis reporting (2) Verifies one of the following applicable actions is performed: ISO performs the applicable actions of CROP.50001, Reporting Procedure. The LCC performs the actions prescribed in the LCC internal procedure(s) for reporting. Rev. 13 Page 10 of 12

11 5. Revision History Rev. No. Date Reason 0 09/14/07 Original Procedure 1 01/15/09 Added NOTE prior to Step 4.2; Added new Attachment A 2 03/12/09 Biennial review completed; Header Review Due Date: changed from calendar date to 24 months from the Effective Date:; Added NERC Reliability Standard COM-001 Telecommunication to References Section, Background Section and Section 4.1 NOTE; minor grammar changes were made in Step 4.1.D Global used Generator/DARD in place of Resource, LCC in place of Local Control Center, ISO in place of the ISO. Moved NOTE from the end to the beginning of Step 4.3; Editorial and grammatical changes to steps 4.3.2, 4.3.3, 4.3.4, 4.3.6, 4.3.7, 4.3.8, & 4.3.9; 3 12/04/09 Global: minor editorial and grammatical changes Section st Added M/LCC 1 to References section; NOTE, Step F & I, Step 4.1.3, Section final NOTE, Step & bullet, Section 2 & 3 provided full title for referenced procedures, defined ISO as acronym; After step added 2 new steps (4.2.6 & 4.2.7) Grammar changes to: former Step 4.2.6, Step 4.3.1, Step 4.3.2, 3, 4, 5, 6 Replaced as soon as possible with immediately in Steps 4.3.2, 3, 4, 5 & 6; Step 4.3 modified former NOTES items and added new NOTES items for M/LCC 1 and M/LCC 4; Reversed the order of & Grammar & format changes (sub-steps) to Step , & /15/10 Minor editorial changes, changed text fonts to Arial, re-formatted NOTE boxes; Added NOTE prior Section 4.2.6; Section replaced Control with Reliability Coordinator ; Added Attachment B to Attachments Section 5 07/28/11 Changed Procedure Contact to Manager, Control Room Operations, updated copyright date, changed pagination to X of Y format; Added Note to Section 3; Added new Section to define criteria requiring 3 part communication 6 11/17/11 Biennial review by procedure owner; New Section 4.4 step and sub-steps to establish communications protocol and provide the applicable actions for recognizing the classification of NERC events and determining ISO & LCC responsibilities for NERC event analysis reporting. 7 04/19/12 Header, Updated copyright date; Global, changed subject/object/tense to singular where applicable; A, Moved the old step I. to be the new A.; B, Added new step and re-numbered remaining steps.; H, Minor wording change; 4.1.3, Modified wording; 4.1.5, Added wording for confirmation of directive implementation; A(1), 8 11/01/12 Biennial review by procedure owner; Updated for CROP and CROW software change for KFCC reporting: Section 1 added CROP and M/LCC 11; Section 4.2, added new step and & sub-steps; Section 4.3, added and/or CROP Section 4.4, replaced SOP-RTMKTS in step A.(1) & the 1 st bullet sub-step; Rev. 13 Page 11 of 12

12 Rev. No. Date Reason 9 05/06/13 Added new step and an example; Modified step A, added new sub-step (1) and modified sub-step (2); Added new step C 10 09/01/13 Added MRA to list of directives in step A; Modified step C; Added new step /11/13 Modified NOTE prior to section 4.1.1; Globally updated referred to documents and or their acronyms to be consistent with current practices and management expectations; Relocated step 9 to step 4 in section 4.2; Added step and sub-steps; Added guidance for communicating transmission issues between ISO and LCC 12 09/30/14 Biennial review by procedure owner; Globally replaced shall and ensure per ROC directive and corrected the resulting applicable grammar, minor editorial changes consistent with current practices and management expectations; Section last bullet, added or governor /28/15 Process minor revision to correct Review Due Date in Header 13 03/23/15 Added NPCC Directory #7 to References; Added step : require LCC notification to ISO for Type III SPS or ACS change of state, renumbered remaining steps in section; Section 4.3: first Note, deleted M/LCC1 and Attachments as they no longer contain emergency instructions 6. Attachments Attachment A - Contingency Actions and Communications Protocol Attachment B - Accepted SPS Terminology Rev. 13 Page 12 of 12