Outage Coordination External Workshop. Jason Ausmus Manager, Operations Planning

Size: px
Start display at page:

Download "Outage Coordination External Workshop. Jason Ausmus Manager, Operations Planning"

Transcription

1 Outage Coordination External Workshop Jason Ausmus Manager, Operations Planning

2 Outage Coordination Course 8 total CEHs for this course To get the CEHs, you will need to: o Be present for the entire class no partial credit o Sign the sign-in sheet o Take, pass, and turn in the learning assessment o Complete and turn in the course evaluation 2

3 Learning Objectives 3 Summarize Peak s Approach and Strategy In Creating the Outage Coordination (OC) Process Review the IRO NERC Standard High Level Process Overview Explaining Differences Between Current OPA Process and new OC Process Describe All 26 Outage States and Focus on Those Applicable to BAs and TOPs Describe All 7 Outage Types and Explain How Their Use in OC

4 Learning Objectives 4 Deeper Dive on Urgent, Opportunity and One-at- Time (OAT) Outages Review the Study and Assessment Requirements Describe Operating Plans and Their Submission Requirements Explanation and Demo on How To Properly Submit an In-Scope OC Outage in the Appropriate Outage State Review the RC Study Windows and Submission Timelines

5 Learning Objectives 5 Explain the Switching Point Submission Requirement Review the Priority Date and Significant Change Concepts Build into COS Review the COS Data Dictionary and How it Relates to the OC Process Demo of How to Subscribe to an Outage Notification and the Reports In COS Review the Implementation Plans for Mar 21 st and Apr 1 st

6 Outage Coordination Project Review 6 Peak s first IRO stakeholder kick-off webinar took place on Sept 21, 2015 Small Team formed in Oct 2015 On November 19, 2015, FERC issued Order 817, approving the revised NERC TOP/IRO standards which included NERC Standard IRO o April 1 st, 2017 effective date established for IRO

7 Outage Coordination Project Review 7 Stakeholder Outreach Webinars o Sept 2015 Oct 2016 Small Team held 4 face-to-face meetings o Jan Vancouver o Feb Phoenix o Mar 29 Apr 1 Folsom o May Vancouver First Posting June 17 th o First round industry comments Second Posting Aug 17 th o Second round industry comments Final Posting Oct 3 rd

8 Guiding Principles Benchmark industry processes learn from what others have developed and experienced Close collaboration with industry key to successful implementation o Regular stakeholder outreach, comment periods, etc. Small team formed to collaboratively develop the process o APS, BPA, CAISO, CSU, PAC, PRPA, PSE, SCE, TEP, USACE, USBR, XCEL 8

9 Background Outage Coordination No centralized outage coordination process Wide ranging technology and process implementations IRO-017 major cultural shift 9

10 Vision Ultimate goal highly advanced and automated process: For Peak to have an automated continuous real-time hourly process that assesses expected system conditions (including approved planned outages) for each hour of the upcoming X hour period For Peak to assesses applicable BES outages against every hour for a Y day window and against the peak hour for each day for a Z month window 10

11 Strategy Initially develop an achievable outage coordination process for Apr 1 st Enhance process over time using phased approach 11

12 Outage Coordination Comments Future version of the Outage Coordination process is likely (no timetable) Any future revision will be coordinated in a similar manner to v1.0 Any concerns or clarifications should be sent to IRO-017project@peakrc.com Peak to consider future SharePoint site for entities to provide comments/suggestions on any future revision 12

13

14 IRO Purpose: To ensure that outages are properly coordinated in the Operations Planning time horizon and Near Term Transmission Planning Horizon. Applicability: 14 o Reliability Coordinator o Transmission Operator o Balancing Authority o Planning Coordinator o Transmission Planner

15 IRO Requirements Review R1. Each Reliability Coordinator shall develop, implement, and maintain an outage coordination process for generation and Transmission outages within its Reliability Coordinator Area. The outage coordination process shall: [Violation Risk Factor: Medium] [Time Horizon: Operations Planning] 1.1. Identify applicable roles and reporting responsibilities including: Development and communication of outage schedules Assignment of coordination responsibilities for outage schedules between Transmission Operator(s) and Balancing Authority(s). 15

16 IRO Requirements Review 1.2. Specify outage submission timing requirements Define the process to evaluate the impact of Transmission and generation outages within its Wide Area Define the process to coordinate the resolution of identified outage conflicts with its Transmission Operators and Balancing Authorities, and other Reliability Coordinators. 16

17 IRO Requirements Review R2. Each Transmission Operator and Balancing Authority shall perform the functions specified in its Reliability Coordinator s outage coordination process. [Violation Risk Factor: Medium] [Time Horizon: Operations Planning] R3 & R4 contain requirements for Planning Coordinators and Transmission Planners 17

18 IRO Requirements Review R3. Each Planning Coordinator and Transmission Planner shall provide its Planning Assessment to impacted Reliability Coordinators. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning] R4. Each Planning Coordinator and Transmission Planner shall jointly develop solutions with its respective Reliability Coordinator(s) for identified issues or conflicts with planned outages in its Planning Assessment for the Near-Term Transmission Planning Horizon. [Violation Risk Factor: Medium] [Time Horizon: Long-term Planning] 18

19 Peak Reliability Outage Coordination Process Overview Process was finalized and posted on peakrc.com October 3, 2016 OC Process is applicable only to: 19 o BA o TOP OC Process to address both generation and Transmission outages Process to become effective Apr 1 st 2017 o Optional early start of Mar 21 st

20 Present and Future Process Comparison 20

21

22 Outage Coordination Outage States Outage States (26) 22 o Necessary for RC to follow the outage lifecycle Four states each for BA and TOP o Preliminary, Proposed, Confirmed, Cancelled o (8) total outage states although entities are expected to use just two most of the time Two states covering Implemented (in-progress) and Completed outages o Two variations with unverified and verified timestamps (future tool to track/log actual dates and times) o (4) total outage states

23 Outage Coordination Outage States Three main states occurring in the lifecycle of the outage for the RC Study Windows 23 o Confirmed, Conflicts Identified, Denied o (13) total outage states covering RC study windows (Long-Range, Short-Range, OPA D+2, OPA D+1, RCSO) (1) outage state for Expired o Move stale outages out of COS o Proposed Outages -> start of Short- Range Study Window

24 BA and TOP Outage States Preliminary, Proposed and Confirmed outage states o Preliminary (optional) Create awareness for coordination purposes. No study/assessment required. o Proposed (optional) Studies/assessments may be underway. Neighboring outages considered when submitting outages in this state. o Confirmed Studies/assessments are complete. Neighboring outages considered, coordination (if required) occurred and operating plans (if required) developed. 24

25 BA and TOP Outage States What are the differences between 25 Proposed and Confirmed outages? o Both establish priority, i.e. Priority Date Confirmed outage must account for the following: o Study has been performed o Outage has been coordinated, if applicable o Operating Plan has been developed, if applicable

26 BA and TOP Outage States Only Confirmed outages will be included in the RC Study Windows (LR, SR, OPA) TOP Confirmed o All in-scope transmission outages BA and TOP Confirmed o All in-scope generation outages o If BA and TOP are different entities, then outage will move from BA Confirmed -> BA and TOP Confirmed o Requires coordination between BA and the TOP they are interconnected with 26

27 Screenshot Outage States in COS Default Outage States Listed at Bottom of Form 27

28 TOP Confirmed OC Process Definition TOP Confirmed TOP studies completed and no conflicts or reliability concerns were identified. Expectation for BA and TOP studies/assessments to include neighboring outages that are in this state (encouraged to also include proposed) and to ensure coordination with the impacted entities is resolved prior to changing the outage to this state. Outages in this state will be included in the RC Long-Range, RC Short-Range and RC OPA studies. If required, an Operating Plan must be attached to the outage when setting the outage to this state. The TOP is responsible for setting this outage state. 28

29 BA Confirmed OC Process Definition BA Confirmed BA assessments completed and no conflicts or reliability concerns were identified. Expectation for BA and TOP studies/assessments to include neighboring outages that are in this state (encouraged to also include proposed). Outages in this state will be included in the RC Long-Range, RC Short-Range and RC OPA studies. If required, an Operating Plan must be attached to the outage when setting the outage to this state. The BA is responsible for setting this outage state. 29

30 BA and TOP Confirmed OC Process Definition BA and TOP Confirmed Outages in this state will reflect generation outages submitted by the BA in the BA Confirmed state and later confirmed by the TOP. Or, in cases where the BA and the TOP functions are performed within the same work environment, the generation outage can be directly submitted as BA and TOP Confirmed without having to sequentially submit the outage as BA Confirmed and then change it to TOP Confirmed. It reflects that all studies/assessments were completed and no conflicts or reliability concerns were identified. Expectation for studies/assessments include neighboring outages that are in this state (encouraged to also include proposed) and that any coordination needs with the impacted entities are resolved prior to changing the outage to this state. Outages in this state will be included in the RC Long-Range, RC Short-Range and RC OPA studies. If required, an Operating Plan must be attached to the outage when setting the outage to this state. The TOP is responsible for setting this outage state. 30

31 Demo BA & TOP Confirmed Outage Entry 31

32 Demo BA & TOP Confirmed Outage Entry For generators, must have a TOP identified for every unit, even if the TOP is the same as the BA 32

33 Demo BA & TOP Confirmed Outage Entry 33

34 Demo BA & TOP Confirmed Outage Entry The TOP who has permission, what they should see when they input enter the outage # for the BA Confirmed Outage 34

35 Demo BA & TOP Confirmed Outage Entry The TOP has confirmed outage by selecting BA and TOP Confirmed 35

36

37 Outage Coordination Outage Types Outage Types (7) Listed in order of priority 37 o Forced Automatic o Forced Emergency o Urgent o Operational Transmission o Planned o Opportunity o Informational

38 Forced Emergency vs. Automatic Forced Automatic Outage Facility/equipment removed from service via automatic action. Forced Emergency Outage Facility/equipment that is removed from service via operator action due to imminent equipment risks, safety concerns, environmental regulations or increased risk to grid reliability and/or security. 38

39 Outage Coordination Outage Types Urgent Outage Facility/equipment that is known to be operable, yet carries an increased risk of a Forced Emergency or Forced Automatic outage occurring. Facility/equipment remains in service until personnel, equipment and system conditions allow the outage to occur. Operational Transmission Outage Transmission Facility/equipment that is removed from service in the normal course of maintaining optimal or reliable system conditions but remains available if needed upon short notice. 39

40 Planned Outages Planned Outage Non-automatic Facility/equipment outage with advance notice, for the purpose of maintenance, construction (including energizing and testing new Facilities), inspection, testing or other planned activities. 40 o Continuous A Facility/equipment outage that will remain out of service for the duration of the specified start date/time and end date/time o Non-Continuous A Facility/equipment outage that will not be out of service for the duration of the specified start date/time and end date/time.

41 Demo of Continuous vs. Non-Continuous and Outage Profiles 41

42 Demo of Continuous vs. Non-Continuous and Outage Profiles 42

43 Demo of Continuous vs. Non-Continuous and Outage Profiles 43

44 Demo of Continuous vs. Non-Continuous and Outage Profiles 44

45 Demo of Continuous vs. Non-Continuous and Outage Profiles 45

46 Outage Coordination Outage Types Opportunity Outage (OC definition) 46 o A short-duration Facility/equipment outage that can be taken due to a change in system conditions or availability of field personnel Opportunity Outages are those that could not have been planned for Acceptable uses of an Opportunity Outage o Unforeseen weather changes that provide a window of opportunity for work to be done o Field crews unexpectedly finish early and are available for other work, e.g. breaker maintenance in a substation

47 Opportunity Outages Implementation in Outage Coordination Opportunity Outages: 47 o May only last one business day Weekend Opportunity provides for longer duration o That cause reliability issues or conflict with Confirmed outages of a higher priority cannot be implemented o May not require implementation of an outagespecific Operating Plan or mitigation efforts to achieve acceptable pre- and post-contingency system performance during the outage

48 How to Submit Opportunity Outages Opportunity outage get approved one business at a time. Opportunity outage record can be submitted for multiple days o E.g. An entity can submit a 5-day Opportunity outage However, outage will need to be approved each business day 48

49

50

51

52 Opportunity Outage Example (discussion) A TOP learns that two days from now an unexpected favorable weather condition allows a TOP to take a one-day outage on a transformer. The Opportunity outage requirements are met, and the TOP submits the outage to COS prior to the OPA lock-down time. An unexpected favorable weather condition creates an opportunity to take a three-day transformer outage. The TOP may submit this outage as an Opportunity outage; however, the outage will need to be submitted as three separate one-day outages (can also use Outage Profile), any of which may be denied for reliability reasons if OPA studies indicate conflicts. The TOP will need to determine if the outage can proceed as three separate one-day Opportunity outages, or if the outage needs to be rescheduled to re-enter into the Short-Range process. An unexpected transmission or generation outage results in an opportunity to take an outage on a related transmission or generation facility. An unanticipated change causes an outage to be returned to service earlier than expected, allowing subsequent outages to proceed earlier than originally planned. Crew/Parts/Tools availability and resources become available due to scheduling openings. A radial transmission line to a generation plant is out of service due to Forced Automatic, Forced Emergency or Urgent reasons. The generators at the plant may be taken as Opportunity outages for the duration of the transmission line outage upon BA and TOP confirmation. 52

53 One-at-a-Time (OAT) Outages OAT outages are a subset of Planned outages that are available for use by the TOP/BA. OAT outages allow the TOP/BA to perform work on numerous elements of the same Facility/equipment type at a single station without maintaining the outage records. 53 o Minimum duration of OAT sequence is 30 min o Any individual element outage 30 min or more required separate COS record

54

55 Study and Assessment Requirements For Outage Coordination Similar principles as stated in new TOP/IRO Reliability Standards (4/1/17) and reflects revised OPA definition (1/1/17) TOP performs a study for an outage (TOP R1) 2. RC performs a study for an outage (IRO R1) 3. TOP develops an outage-specific Operating Plan to address the SOL exceedance (TOP R2) 4. TOP communicates the outage-specific Operating Plan to the RC (TOP R3) Confirmed outages must have 1, 3 and 4 completed prior to submission in that state

56 What will the RC do if they see an issue in any of their studies? Move the Confirmed outage to the Conflicts Identified state Send out an (potential phone follow-up) Verify Operating Plan, if provided one, to determine if it resolves the issue Change state: o Confirmed if issue resolved o Denied if issue not resolved and outage is not cancelled or rescheduled by entity 56

57 Study Result Communication s After internal validation, s are sent for various study concerns in the OPA: o Unsolved, branch, voltage, islanding conditions is meant to ensure consistency amongst Peak s study engineers Have determined a baseline of information to provide all entities for the initial outreach on the various issues 57

58 Study Result Communication - Branch Exceedance Example Hello, We are seeing the following result(s) in Peak RC 1-Day Ahead analysis for 8/12/2015 (Peak Time Studied - 5:00:00 PM Mountain Time Zone) - TOP Name: TOPA, TOPB Type: Branch Exceedance Topology (Outage - Element being taken out of service): Line A B #2 500kV line (8/12/ :00:00 AM - 8/18/2015 4:00:00 PM) [COS# 1-XXXX; TOP A Outage #YYYYYY] Monitored Element: TOP A Line C-D #1 500kV (50 MVA, 124 MVA, 124%, 100 MVA) CTG Element: TOP B Line E F #1 230 kv 58

59 Communication cont We need to verify with TOP A and TOP B if they are seeing the above results in their Operational Planning Analysis (OPA). If yes, please provide us with the following information What is the pre-mitigation plan? (If applicable) What is the post-mitigation plan? (If applicable) Please verify the maximum line rating. Provide us with the temporary line rating if any. If applicable, please refer to the operating procedure which sufficiently addresses the reliability concerns. You can reach me at (970) or by replying to this mail (please reply to all the recipients in the mail) during office hours. If you are not able to contact me, please be sure to follow up with a response to the Peak Real Time Operations Engineer (ROE) at ops.engineering@peakrc.com or (360)

60 Operating Plans Submission required per TOP for both BA and TOP As stated in Peak Reliability Data Request Specification (IRO-010-2) 60 o NERC Standard TOP R7 requires each Balancing Authority to provide its Operating Plan for next-day operations identified in TOP R4 to its Reliability Coordinator. Given the 4 requirements TOP R4 needs to address, those same requirements are being fulfilled in this data request by items, 3.5 and 3.7 (R4.1), 2.2 and 2.3 (R4.2), 3.3 (R4.3) and 2.8 (R4.4).

61 Operating Plans TOP required to submit Operating Plans to address potential SOL Exceedance(s). Operating Plans must identify mitigating action(s) necessary to resolve potential SOL Exceedance(s). Two different types of Operating Plans per OC: 61 o Outage Specific: Operating Plans due to a specific outage. Must be submitted with outage record to COS. Can either be an attachment or entered in the free form COS comment box. o Next-Day Operations: Operating Plans not due to a specific outage, but to a variety of system conditions, e.g. system loading, high system flows, etc. Must be submitted along with TOP s OPA to PeakRC.org.

62 Operating Plan Uploading Outage Specific 62

63 Operating Plan Uploading Outage Specific For any large procedure, outage submitting entity must indicate the page number and section in the comments box. 63

64 Operating Plan Uploading Next-Day Operations 64

65 Operating Plan Uploading Next-Day Operations 65

66 Operating Plan Uploading Next-Day Operations 66

67

68 In-Scope Outages For Outage Coordination BES transmission/generation Facilities o Includes buses, circuit breakers, generating units, reactive compensation (dynamic, series, shunt), transformers, transmission lines Non-BES transmission/generation Facilities identified by the RC, TOP or BA as having an impact on the reliability of the BES 68

69 In-Scope Outages For Outage Coordination BES Remedial Action Scheme (RAS), non-ras automatic schemes, or protection systems when functionality is affected (i.e., when normal fault clearing zones are impacted) or Contingency definitions are impacted Clearing when breaker protection removed from tap at Station B (A C) Normal Clearing (A-B) Normal Clearing (B-C) Station A Station C 69 Breaker protection Removed at Station B Tap Station B

70 Other Data Per Data Request Specification Out of Scope, but needed for RC study accuracy COS entry needed for: 70 o Generator Derates o AVR/PSS Outages o TTC Reduction Submissions Above entries follow Short-Range submission timelines (needed for study accuracy), but Out of Scope for OC purposes

71 General Outage Submission Requirements Outages are expected to have a continuous duration of 30 minutes or more require submission to COS 71 o OAT exceptions stated in process document Outages expected to have a continuous duration of less than 30 minutes are not required to be submitted to COS unless the outage requires an Operating Plan to facilitate the outage

72 General Outage Submission Permissions Ability to submit/revise outages based on permissions listed in COS Must be listed as either (by element): o Operator (up to 5 different entities in COS) o Submitter (up to 2 different entities in COS) Will also be able to list company permissions by NERC Registered Function o E.g. BA, GOP, TOP 72

73

74 General Outage Submission Permissions The default responsible entities for outage submission are BA (generator) and TOP (transmission) Can I as a BA or TOP delegate my outage submitting responsibilities? 74 o Yes, provided the decision is mutual, documented and provided to Peak. This type of arranged does not absolve BAs and TOPs of other OC related obligations (e.g. studies, coordination)

75 Outage Submission Backup What is COS becomes unavailable during the OC Process? Per OC Process: Should COS become unavailable at any time during the Outage Coordination Process, Peak will communicate information regarding an alternate means of submitting outage data. 75 o For example, submitting outage data via may be required in this scenario

76 RC Study Windows Peak Reliability Study Windows o Long-Range (3-4 months) Optional o Short-Range (1-2 weeks) Required o OPA Window(2 business days) Required OPA D+2, OPA D+1 Peak Ops Planning will be performing system studies for study windows noted above A planned outage may be assessed by Peak up to 4 times prior to being implemented o E.g. LR -> SR -> OPA (D+2 & D+1) 76

77 RC Long-Range Study Window Submission timeline Planned outages must be in either the BA and TOP Confirmed or TOP Confirmed state prior to the first day of the month, three months in advance of the month in which the outage is scheduled to start. Criteria Outage duration of five consecutive days or longer, continuous or non-continuous. 77

78 RC Long-Range Study Window Ex. Apr start date submitted prior to Jan 1 st 78

79

80

81 RC Short-Range Study Window Submission timeline Planned outages whose start dates occur between Monday and Sunday are to be submitted on a rolling weekly basis by the Monday prior at 6 a.m. Mountain Prevailing Time (MPT). 81 o Short-Range submission adjusts for holidays Criteria Same as the General Outage Submission Requirements

82 RC Short-Range Study Window Short-Range Timeline divided into two weeks: 82 o Outage Submission Week o Study Week RC requires 5 business days during the Outage Submission Week to perform Short- Range studies Holidays only accounted for when occurring during Outage Submission Week

83 RC Short-Range Study Window Short-Range Timeline Mon Submission 83

84 RC Short-Range Study Window Short-Range Timeline Monday Holiday 84

85 RC Short-Range Study Window Short-Range Timeline Thurs & Fri Holiday 85

86 Short-Range Window Planned Outages Planned outages are required to be submitted in Confirmed state prior to entering Short-Range Study Window o Validation rule in COS to enforce this concept What options are available then? o Urgent o Opportunity Specific criteria for each outage type 86

87

88

89 RC OPA D+2 and D+1 Study Window Submission timeline Only Opportunity, Urgent, Forced Emergency, and Forced Automatic are only new types allowed. Timeline is from Short-Range up to real-time. Planned outages are only allowed prior start Short-Range Study Window Criteria Same as the General Outage Submission Requirements 89

90 RC OPA D+2 and D+1 Study Window Two OPA studies are being performed by RC o OPA D+2 studies occurring 2 business days prior to date o OPA D+1 studies occurring 1 business day prior to date 90

91

92 Long-Range to OPA "Clean" Example (discussion): TOP wants to take an important two-week duration 230kV transmission line outage. Because the TOP wants the outage to have a high priority, the TOP enters the Planned outage into COS as TOP Proposed, as studies have not yet been completed. The TOP studies the outage consistent with the expectations in the Outage Coordination Process and TOP studies show no reliability conflicts. The TOP submits the Planned outage to COS prior to the Long-Range study window in the TOP Confirmed state in time for it to be studied by the RC as part of the Long-Range study window process. The RC studies the outage as part of the Long-Range study window process consistent with the expectations in the Outage Coordination Process, and the RC studies show no reliability conflicts. The RC changes the state of the outage to RC Long-Range Confirmed. A few months later the same outage comes to within two weeks of the Short-Range study window process. The TOP includes this outage in its studies when evaluating other outages. Some other outages cannot be scheduled to overlap with the important two-week outage, so the TOP makes adjustments to the other outage schedules accordingly. The important two-week outage then rolls into the short-range process. The TOP studies that have occurred show no conflicts with the outage as of the Short-Range submission deadline. No status change by the TOP is needed. The status of the outage remains as RC Long-Range Confirmed. The RC studies the outage as part of the Short-Range process consistent with the expectations in the Outage Coordination Process, and no conflicts are identified. The RC changes the state of the outage to RC Short- Range Confirmed. The two-week outage rolls into the OPA study window. The TOP and the RC include this outage in their OPAs. The RC changes the state of the outage to RC OPA Confirmed. 92

93

94 Outage Submission and Switching Points Per COS Manual, the submission of Switching Points as modeled in the Peak WSM, is required for the following equipment types: o Buses o Generating Units o Reactive Compensation Devices (Dynamic, Series, Shunt) o Transformers o Transmission Line Segment or Protection Zone 94

95 Outage Submission and Switching Points A Switching Point is defined as either a circuit breaker, circuit switcher or disconnect switch used to switch elements in- and out-of-service. Switching Points can also be located outside of the station where the outage is being taken. While there may be many switching points associated with the equipment, not all will have to be submitted. o Circuit breakers are preferred, but disconnect switches may also be submitted where appropriate. 95

96 Outage End State Outage End State is defined as the state immediately following switching when work is ready to begin on the element being outaged. Switching Points being submitted to COS are those that reflect the Outage End State and not the switching sequence typically used to energize and de-energize equipment. 96

97 Switching Point Outage Submission Examples 97

98 Switching Point Outage Submission Examples 98

99 Why Switching Point Outage Submission? Why is Peak requiring the submission of Switching Points? o Peak WSM is a node-breaker model o More accurate representation of the outage o More accurate contingency analysis Knowing what Switching Point to use to isolate an element matters! 99

100 10 0 Switching Point Outage Submission 3 parallel line example Outage End State scenario 1, using CBs Line 1 P => Line 2 P => Line 3 P = 0 MW

101 10 1 Switching Point Outage Submission 3 parallel line example Outage End State scenario 2, using DSWs Line 1 P => Line 2 P => Line 3 P = 0 MW

102 10 2 Switching Point Outage Submission 3 parallel line example Outage End State scenario 1, Post-CTG Line 1 P = 0 MW Line 2 P = 0 MW Line 3 P = 0 MW

103 10 3 Switching Point Outage Submission 3 parallel line example Outage End State scenario 2, Post-CTG Line 1 P = 0 MW Line 2 P => Line 3 P = 0 MW

104 Switching Point Submission in COS

105

106 10 6 In-Scope OC Outage Entry Requirement - Review In order for an outage to be included in the various RC study windows (Long-Range, Short-Range, OPA), it will need to be in one of the following outage state: o TOP Confirmed: Transmission outages that are in-scope for the Outage Coordination Process. o BA and TOP Confirmed: Generation outages that are in-scope for the Outage Coordination Process.

107 Outage Entry Demo 10 7

108 10 8 Outage Entry Demo Please note the buttons at the bottom of the page o Transmission Outage Example o Ultimately have to be in TOP Confirmed outage state for RC study window inclusion

109 Outage Entry Demo 10 9

110 11 0 Very Important!!! For In-Scope OC outages, please do not use the Submit Request button Button is for Out-of-Scope Items only: o Generator Derates o AVR/PSS Outages o Telemetering and Control o TTC Reduction Submissions

111 Incorrect In-Scope Outage Entry Submitted states not included in RC study 111

112

113 11 3 Same Day and Real-Time Outage Requests With exception of Forced Automatic and some Forced Emergency outages, the rest of the outage types will also need to be Confirmed by RC prior to Implementation. COS will flag outages where the end-day was extended, after the outage starts. This will be call an Unprocessed Outage Extension o A checkbox is visible in COS WebUI

114

115 11 5 Same-Day and Real-Time Outage Update Requirements Outage submitting entities are expected to keep COS up to date For T+3 hours and less, the scheduled start and end times are expected to be accurate within a +/- one hour deadband.

116 Same-Day and Real-Time Outage Update Requirements Examples (Discussion) 11 6 Examples regarding the +/- one hour threshold (listed in OC Process doc) o o o o o Example It is now 7 a.m. An outage is scheduled to start at 9:30 a.m. The outage is not expected to start until 10:15 a.m. There is no need to update the scheduled start time. Example It is now 7 a.m. An outage is scheduled to start at 9:30 a.m. The outage is expected to start at 8:45 a.m., assuming studies/assessments show no conflicts. There is no need to update the scheduled start time. Example It is now 7 a.m. An outage is scheduled to start at 9 a.m. The outage is not expected to start until 10 a.m. The scheduled start time should be revised to reflect a 10 a.m. start time. Example An outage is scheduled to end at 5 p.m. At 2 p.m. the System Operator learns that the outage will end at 4 p.m. The scheduled end time should be updated to reflect the 4 p.m. scheduled end time. Example An outage is scheduled to end at 3 p.m. At 1 p.m. the System Operator learns that the outage will end at 3:45 p.m. There is no need to update the scheduled end time.

117 Priority Date and Significant Changes Priority Date for an outage record is considered the point in time in which an outage establishes its queue position or priority Outage states that initialize the Priority Date: 11 7 o BA Proposed o BA Confirmed o BA and TOP Confirmed o TOP Proposed o TOP Confirmed

118 Priority Date and Significant Changes Significant Change is the way to define 11 8 high impact changes to a COS outage record. What are Significant Changes? o Moving the Start Date Up o Moving the End Date Out (prior to the outage beginning) o Adding more equipment to the outage record

119 11 9 Priority Date and Significant Changes A Significant Change will result in a Priority Date Change Priority Date will be reset to the current date/time if it is currently set and a Significant Change is made to the outage request

120 12 0 What are not Significant Changes? Examples include: o Adding/editing Switching Points o Adding/editing the comments o Changing the Constraint Type from OOS to anything else o Removing equipment from the record o Shortening the duration of the outage, i.e. moving the start date out or moving the end date up, within the original outage window

121 12 1 Demo Significant Change Error Outage currently in RC Short- Range Confirmed State Note: Priority Date Timestamp 1/30/ :35

122 12 2 Demo Significant Change Error BA has changed the date by moving the start date up, Tues -> Mon

123 12 3 Demo Significant Change Error BA pushes Save Changes, but save not allowed due to being within the SR Study Window.

124 12 4 Demo Significant Change Error If making a Significant Change within SR Study Window, outage will need to be reconfirmed by BA or TOP. E.g. BA pushed BA Confirmed button which was successful Note: Priority Date Timestamp 1/30/ :35 -> 1/30/ :40

125

126 12 6 COS Data Dictionary COS Data Dictionary is Peak WSM centric o All BES equipment in the WSM will have a matching element in COS COS Data Dictionary has been designed to support a one-to-one mapping of equipment in the WSM Accuracy of COS Data Dictionary extremely important for successful Outage Coordination Implementation

127 12 7 COS Data Dictionary COS enhanced to support on-demand COS Data Dictionary additions Not-In-Model (NIM) was designed to provide for the necessary flexibility to enter outages on equipment not currently in COS NIM should only be used when adding small numbers of equipment to the COS Data Dictionary o Bulk changes need to continue be requested at cos.support@peakrc.com

128 COS Data Dictionary NIM Example 12 8

129 COS Data Dictionary NIM Example 12 9

130 COS Data Dictionary NIM Example 13 0

131 13 1 COS Data Dictionary - Reporting COS also supports the reporting of changes by company for each entity s data dictionary Every COS user will have the ability to subscribe to a weekly report Reporting period is on a weekly basis (Mon Mon) with reports first being sent out at 3:30A MPT on Mondays

132 13 2 COS Data Dictionary - Reporting In COS WebUI, click on Reports

133

134 13 4 Subscribing to COS Outage Notifications COS provides automated Notifications where a user can be notified by for entries or changes in COS by the following categories: o Station / Equipment o Submission by Company o Equipment Type o Outage States Example of TOP subscribing to BA generator outage needing their confirmation

135

136

137

138 13 8 Implementation Plans Two Implementation Dates: o Mar 21 st (changed from Feb 7 th ) Optional o Apr 1 st (effective date of IRO-017) Mandatory Both implementation plans are centered around submission of outages by type Purpose of the optional implementation is to give their processes a dry run in harmony with the RC Outage Coordination Process

139 13 9 Mar 21 st Implementation Plan Optional Version Outage Types (not including Planned) effective Mar 21 st :00 MPT o Forced Automatic o Forced Emergency o Urgent o Operational Transmission o Opportunity o Information (please note these outage types are not required)

140 14 0 Mar 21 st Implementation Plan Optional Version Planned Outage Type outage submitting details listed below by study window o Long-Range Window (optional): Planned outages with start dates occurring in July need to be submitted in the TOP Confirmed or BA and TOP Confirmed states prior to Apr 1, 2017 o Short-Range Window (required): Planned outages with start dates occurring Apr 3 rd Apr 9 th ) will need to be submitted by Mar 27 th 6A MPT

141 14 1 Apr 1 st Implementation Plan IRO-017 Effective Date (mandatory) Outage Types (not including Planned) effective Apr 1 st :00 MPT o Forced Automatic o Forced Emergency o Urgent o Operational Transmission o Opportunity o Information (please note these outage types are not required)

142 14 2 Apr 1 st Implementation Plan IRO-017 Effective Date (mandatory) Planned Outage Type outage submitting details listed below by study window o Long-Range Window (optional): Planned outages with start dates occurring in Aug need to be submitted in the TOP Confirmed or BA and TOP Confirmed states prior to May 1, 2017 o Short-Range Window (required): Planned outages with start dates occurring Apr 10 th Apr 16 th ) will need to be submitted by Apr 3 rd 6A MPT

143 Transition from Current OPA to OC Process Current outages will be copied over 14 3 from the current system to the new production In-scope outages in the Submitted state will need to be updated to the Confirmed state to be included in the RC studies o Per the Apr 1 st Implementation Plan timelines

144 14 4 Future Training Opportunities Peak will work on putting together COS Outage Data entry examples on PeakRC.org Will be the equivalent of a YouTube like video library By request and as time allows one-on-ones o Via phone or WebEx

145 14 5 Summary Review Outage Coordination Process o Outage States/Types, RC Study Windows, Study Requirements, Operating Plans Demos on how to properly submit outages Switching Point Requirement Review COS Data Dictionary Report and Notification Subscriptions Implementation Plan Review

146

Peak Reliability IRO Project Overview Oct 25, 2016

Peak Reliability IRO Project Overview Oct 25, 2016 Peak Reliability IRO-017-1 Project Overview Oct 25, 2016 Vic Howell Manager, Operations Engineering Support Jason Ausmus Manager, Operations Planning Objectives Overview of new IRO-017-1 Peak s Approach

More information

Peak Reliability. Reliability Coordinator Data Request and Specifications for Data Provision

Peak Reliability. Reliability Coordinator Data Request and Specifications for Data Provision Table of Contents I. Purpose... 2 II. Introduction... 2 III. Peak Roles and Responsibilities... 2 IV. Applicability and Obligations... 3 V. Questions and Comments... 6 VI. Data Request Spreadsheet... 6

More information

Reliability Coordinator Procedure

Reliability Coordinator Procedure No. Table of Contents Purpose... 1 1. Responsibilities... 2 2. Scope/ Applicability... 2 2.1. Background... 2 2.2. Scope... 2 2.3. Applicability... 3 3. Detail... 3 3.1. Format and Security Protocols...

More information

TOP/IRO Standards. RC Users Group January 21, Vic Howell Manager, Operations Engineering Support

TOP/IRO Standards. RC Users Group January 21, Vic Howell Manager, Operations Engineering Support TOP/IRO Standards RC Users Group January 21, 2016 Vic Howell Manager, Operations Engineering Support Saad Malik Manager, Real-Time Operations Engineering New/Revised TOP & IRO Standards November 19, 2015,

More information

TOP-010-1(i) Real-time Reliability Monitoring and Analysis Capabilities

TOP-010-1(i) Real-time Reliability Monitoring and Analysis Capabilities A. Introduction 1. Title: Real-time Reliability Monitoring and Analysis Capabilities 2. Number: TOP-010-1(i) 3. Purpose: Establish requirements for Real-time monitoring and analysis capabilities to support

More information

Guidelines for Submitting NERC Reliability Standards Required Documents to the SPP Reliability Coordinator and the SPP Balancing Authority Version 1

Guidelines for Submitting NERC Reliability Standards Required Documents to the SPP Reliability Coordinator and the SPP Balancing Authority Version 1 Guidelines for Submitting NERC Reliability Standards Required Documents to the SPP Reliability Coordinator and the SPP Balancing Authority Version 1 Revision History Version Effective Date Summary of Revisions

More information

November 9, Revisions to the Violation Risk Factors for Reliability Standards IRO and TOP

November 9, Revisions to the Violation Risk Factors for Reliability Standards IRO and TOP !! November 9, 2016 VIA ELECTRONIC FILING Jim Crone Director, Energy Division Manitoba Innovation, Energy and Mines 1200-155 Carlton Street Winnipeg MB R3C 3H8 RE: Revisions to the Violation Risk Factors

More information

Standard TOP Transmission Operations

Standard TOP Transmission Operations A. Introduction 1. Title: Transmission Operations 2. Number: TOP-001-34 3. Purpose: To prevent instability, uncontrolled separation, or Cascading outages that adversely impact the reliability of the Interconnection

More information

Standard Development Timeline

Standard Development Timeline Standard Development Timeline This section is maintained by the drafting team during the development of the standard and will be removed when the standard becomes effective. Description of Current Draft

More information

Bulk Electric System Definition Changes and Reporting

Bulk Electric System Definition Changes and Reporting Bulk Electric System Definition Changes and Reporting June 12, 2014 Greg Sorenson, PE Senior Compliance Engineer gsorenson.re@spp.org 501.688.1713 Overview BES Definition Change BES Definition Reference

More information

Reliability Standard Audit Worksheet 1

Reliability Standard Audit Worksheet 1 Reliability Standard Audit Worksheet 1 CIP-002-5.1 Cyber Security BES Cyber System Categorization This section to be completed by the Compliance Enforcement Authority. Audit ID: Registered Entity: NCR

More information

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

This section is maintained by the drafting team during the development of the standard and will be removed when the standard becomes effective. Standard Development Timeline This section is maintained by the drafting team during the development of the standard and will be removed when the standard becomes effective. Development Steps Completed

More information

primary Control Center, for the exchange of Real-time data with its Balancing

primary Control Center, for the exchange of Real-time data with its Balancing A. Introduction 1. Title: Reliability Coordination Monitoring and Analysis 2. Number: IRO-002-5 3. Purpose: To provide System Operators with the capabilities necessary to monitor and analyze data needed

More information

Project Consideration of Commission Directives in Order No. 693

Project Consideration of Commission Directives in Order No. 693 Project 2009-02 Consideration of Commission Directives in Order Order P 905-906 Further, consistent with the NOPR, the Commission directs the ERO to modify IRO-002-1 to require a minimum set of tools that

More information

Compliance Enforcement Initiative

Compliance Enforcement Initiative Compliance Enforcement Initiative Filing and Status Update November 2, 2011 Rebecca Michael Status of the Filings NERC filed several components of the Compliance Enforcement Initiative on September 30,

More information

Physical Security Reliability Standard Implementation

Physical Security Reliability Standard Implementation Physical Security Reliability Standard Implementation Attachment 4b Action Information Background On March 7, 2014, the Commission issued an order directing NERC to submit for approval, within 90 days,

More information

Standard CIP Cyber Security Critical Cyber As s et Identification

Standard CIP Cyber Security Critical Cyber As s et Identification A. Introduction 1. Title: Cyber Security Critical Cyber Asset Identification 2. Number: CIP-002-4 3. Purpose: NERC Standards CIP-002-4 through CIP-009-4 provide a cyber security framework for the identification

More information

PRC Coordination of Protection Systems for Performance During Faults

PRC Coordination of Protection Systems for Performance During Faults PRC-027-1 Coordination of Protection Systems for Performance During Faults A. Introduction 1. Title: Coordination of Protection Systems for Performance During Faults 2. Number: PRC-027-1 3. Purpose: To

More information

Project Posting 8 Frequently Asked Questions Guide

Project Posting 8 Frequently Asked Questions Guide Project 2007-02 Posting 8 Frequently Asked Questions Guide General Questions 1. What were the inputs that drove the development of posting 8 of Project 2007-02? The NERC Board of Trustees November 7 th,

More information

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

This section is maintained by the drafting team during the development of the standard and will be removed when the standard becomes effective. Standard Development Timeline This section is maintained by the drafting team during the development of the standard and will be removed when the standard becomes effective. Development Steps Completed

More information

Standard Development Timeline

Standard Development Timeline Standard Development Timeline This section is maintained by the drafting team during the development of the standard and will be removed when the standard becomes effective. Description of Current Draft

More information

Peak Reliability Coordination Services in the West March 30, 2018

Peak Reliability Coordination Services in the West March 30, 2018 Peak Reliability Coordination Services in the West March 30, 2018 Peak Reliability, 2018. 1 Peak Reliability Coordination Services in the West Peak s fundamental mission is to enhance and promote the reliability

More information

Standard INT Dynamic Transfers

Standard INT Dynamic Transfers Standard INT-004-3.1 Dynamic Transfers A. Introduction 1. Title: Dynamic Transfers 2. Number: INT-004-3.1 3. Purpose: To ensure Dynamic Schedules and Pseudo-Ties are communicated and accounted for appropriately

More information

DRAFT. Cyber Security Communications between Control Centers. March May Technical Rationale and Justification for Reliability Standard CIP-012-1

DRAFT. Cyber Security Communications between Control Centers. March May Technical Rationale and Justification for Reliability Standard CIP-012-1 DRAFT Cyber Security Communications between Control Centers Technical Rationale and Justification for Reliability Standard CIP-012-1 March May 2018 NERC Report Title Report Date I Table of Contents Preface...

More information

NERC Relay Loadability Standard Reliability Standards Webinar November 23, 2010

NERC Relay Loadability Standard Reliability Standards Webinar November 23, 2010 Transmission Relay Loadability FERC Order 733 Project 2010-1313 NERC Relay Loadability Standard Reliability Standards Webinar November 23, 2010 Project Overview 2 Standards Involved PRC-023-2 Transmission

More information

SMUD Model Data Requirements & Reporting Procedures MOD VERSION 1.2

SMUD Model Data Requirements & Reporting Procedures MOD VERSION 1.2 SMUD Model Data Requirements & Reporting Procedures MOD-032-1 VERSION 1.2 NOVEMBER 10, 2015 1 TABLE OF CONTENTS INTRODUCTION... 2 1.1 Purpose... 2 1.2 Audience... 3 1.3 Process Overview... 3 Figure 1-1:

More information

Disclaimer Executive Summary Introduction Overall Application of Attachment Generation Transmission...

Disclaimer Executive Summary Introduction Overall Application of Attachment Generation Transmission... CIP-002-4 Cyber Security Critical Cyber Asset Identification Rationale and Implementation Reference Document September, 2010 Table of Contents TABLE OF CONTENts Disclaimer... 3 Executive Summary... 4 Introduction...

More information

Requirements for Data for Power System Modeling and Analysis (MOD-032-1) Arizona Public Service Company

Requirements for Data for Power System Modeling and Analysis (MOD-032-1) Arizona Public Service Company Requirements for Data for Power System Modeling and Analysis (MOD-032-1) Arizona Public Service Company December 29, 2016 APS Requirements for Data for Power System Modeling and Analysis Table of Contents

More information

Standard Development Timeline

Standard Development Timeline CIP-002-6 Cyber Security BES Cyber System Categorization Standard Development Timeline This section is maintained by the drafting team during the development of the standard and will be removed when the

More information

WECC Criterion MOD-(11 and 13)-WECC-CRT-1.1

WECC Criterion MOD-(11 and 13)-WECC-CRT-1.1 WECC Criterion MOD-(11 and 13)-WECC-CRT-1.1 A. Introduction 1. Title: Steady State and Dynamic Data Requirements 2. Number: MOD-(11 and 13)-WECC-CRT-1.1 3. Purpose: To establish the consistent data requirements

More information

Generation, Transmission, and End User Facilities

Generation, Transmission, and End User Facilities Procedures for Interconnection of Generation, Transmission, and End User To the Grand River Dam Authority Transmission System Table of Contents GRDA/SPP Interaction... 3 Standards... 3 Generation... 3

More information

Table of Contents. TOP TOP BA Data Request and Specification Guidelines. Operating Procedure

Table of Contents. TOP TOP BA Data Request and Specification Guidelines. Operating Procedure No. 3140 Table of Contents Purpose... 2 Responsibilities... 2 2. Scope/Applicability... 4 2.1 Background... 4 2.2 Scope / Applicability... 4 3. Detail... 5 3.1... 5 Introduction... 5 3.2 Data Specification

More information

Standard CIP Cyber Security Critical Cyber As s et Identification

Standard CIP Cyber Security Critical Cyber As s et Identification A. Introduction 1. Title: Cyber Security Critical Cyber Asset Identification 2. Number: CIP-002-4 3. Purpose: NERC Standards CIP-002-4 through CIP-009-4 provide a cyber security framework for the identification

More information

Impacts and Implementation: NERC Reliability Standards, Compliance Initiatives, and Regulatory Activities

Impacts and Implementation: NERC Reliability Standards, Compliance Initiatives, and Regulatory Activities Impacts and Implementation: NERC Reliability Standards, Compliance Initiatives, and Regulatory Activities NRECA TechAdvantage March 2014 Patti Metro Manager, Transmission & Reliability Standards NRECA

More information

Standard INT Dynamic Transfers

Standard INT Dynamic Transfers A. Introduction 1. Title: Dynamic Transfers 2. Number: INT-004-3 3. Purpose: To ensure Dynamic Schedules and Pseudo-Ties are communicated and accounted for appropriately in congestion management procedures.

More information

5. Effective Date: The first day of the first calendar quarter after applicable regulatory approval.

5. Effective Date: The first day of the first calendar quarter after applicable regulatory approval. Introduction 1. Title: IROL and SOL Mitigation in the ERCOT Region 2. Number: IRO-006-TRE-1 3. Purpose: To provide and execute transmission loading relief procedures that can be used to mitigate SOL or

More information

Standard EOP Disturbance Reporting

Standard EOP Disturbance Reporting A. Introduction 1. Title: Disturbance Reporting 2. Number: EOP-004-1 3. Purpose: Disturbances or unusual occurrences that jeopardize the operation of the Bulk Electric System, or result in system equipment

More information

NERC Event Analysis Update Webinar. Hassan Hamdar Chair, Event Analysis Subcommittee October 20, 2016

NERC Event Analysis Update Webinar. Hassan Hamdar Chair, Event Analysis Subcommittee October 20, 2016 NERC Event Analysis Update Webinar Hassan Hamdar Chair, Event Analysis Subcommittee October 20, 2016 Webinar Agenda ERO Event Analysis Process Update Lesson Learned Presentation from Entity ERO Lessons

More information

Cyber Security Reliability Standards CIP V5 Transition Guidance:

Cyber Security Reliability Standards CIP V5 Transition Guidance: Cyber Security Reliability Standards CIP V5 Transition Guidance: ERO Compliance and Enforcement Activities during the Transition to the CIP Version 5 Reliability Standards To: Regional Entities and Responsible

More information

Standards Authorization Request Form

Standards Authorization Request Form Standards Authorization Request Form When completed, email this form to: sarcomm@nerc.com NERC welcomes suggestions to improve the reliability of the bulk power system through improved reliability standards.

More information

Reliability Coordinator Procedure PURPOSE... 1

Reliability Coordinator Procedure PURPOSE... 1 No. RC0550 Restriction: Table of Contents PURPOSE... 1 1. RESPONSIBILITIES... 2 1.1.1. CAISO RC... 2 1.1.2. RC Working Groups... 2 1.1.3. Operationally Affected Parties... 2 1.1.4. RC Oversight Committee...

More information

151 FERC 61,066 UNITED STATES OF AMERICA FEDERAL ENERGY REGULATORY COMMISSION ORDER DENYING REHEARING. (Issued April 23, 2015)

151 FERC 61,066 UNITED STATES OF AMERICA FEDERAL ENERGY REGULATORY COMMISSION ORDER DENYING REHEARING. (Issued April 23, 2015) 151 FERC 61,066 UNITED STATES OF AMERICA FEDERAL ENERGY REGULATORY COMMISSION Before Commissioners: Norman C. Bay, Chairman; Philip D. Moeller, Cheryl A. LaFleur, Tony Clark, and Colette D. Honorable.

More information

Standard Development Timeline

Standard Development Timeline Standard Development Timeline This section is maintained by the drafting team during the development of the standard and will be removed when the standard is adopted by the NERC Board of Trustees (Board).

More information

Standard Development Timeline

Standard Development Timeline CIP-002-6 Cyber Security BES Cyber System Categorization Standard Development Timeline This section is maintained by the drafting team during the development of the standard and will be removed when the

More information

Southwest Power Pool Independent Coordinator of Transmission RELIABILITY PLAN for Entergy in the Southeastern Electric Reliability Council September

Southwest Power Pool Independent Coordinator of Transmission RELIABILITY PLAN for Entergy in the Southeastern Electric Reliability Council September Southwest Power Pool Independent Coordinator of Transmission RELIABILITY PLAN for Entergy in the Southeastern Electric Reliability Council September 23, 2009 TABLE OF CONTENTS INTRODUCTION A. RESPONSIBILITIES

More information

Introduction to Generation Availability Data System (GADS) Wind Reporting

Introduction to Generation Availability Data System (GADS) Wind Reporting Introduction to Generation Availability Data System (GADS) Wind Reporting Registration and Reporting Fundamentals Donna Pratt, Performance Analysis Manager-Data Analytics NERC Webinar April 26, 2017 Topics

More information

REAL-TIME MONITORING DATA SPECIFICATION

REAL-TIME MONITORING DATA SPECIFICATION REAL-TIME MONITORING DATA SPECIFICATION Version 1 December 9, 2016 Revision History Version Date Reviewer Revisions 1 11/1/16 Mansion Hudson Initial document 1 Contents 1. DOCUMENT REVIEW... 3 2. DEFINITIONS...

More information

Draft CIP Standards Version 5

Draft CIP Standards Version 5 Draft CIP Standards Version 5 Technical Webinar Part 1 Project 2008-06 Cyber Security Order 706 Standards Drafting Team November 15, 2011 Agenda Opening Remarks John Lim, Consolidated Edison, Chair V5

More information

Memorandum. This memorandum requires Board action. EXECUTIVE SUMMARY

Memorandum. This memorandum requires Board action. EXECUTIVE SUMMARY California Independent System Operator Corporation Memorandum To: ISO Board of Governors From: Keith Casey, Vice President, Market & Infrastructure Development Date: May 21, 2014 Re: Decision on interconnection

More information

Critical Infrastructure Protection (CIP) Version 5 Revisions. Standard Drafting Team Update Industry Webinar September 19, 2014

Critical Infrastructure Protection (CIP) Version 5 Revisions. Standard Drafting Team Update Industry Webinar September 19, 2014 Critical Infrastructure Protection (CIP) Version 5 Revisions Standard Drafting Team Update Industry Webinar September 19, 2014 Administrative Items NERC Antitrust Guidelines It is NERC s policy and practice

More information

Wide-Area Reliability Monitoring and Visualization Tools

Wide-Area Reliability Monitoring and Visualization Tools OE Visualization and Controls Peer Review Wide-Area Reliability Monitoring and Visualization Tools Carlos Martinez CERTS - Electric Power Group 21 October 2008 Washington, D.C. Presentation Outline Research

More information

ERO Enterprise Registration Practice Guide: Distribution Provider directly connected Determinations Version 2: July 5, 2018

ERO Enterprise Registration Practice Guide: Distribution Provider directly connected Determinations Version 2: July 5, 2018 ERO Enterprise Registration Practice Guide: Distribution Provider directly connected Determinations Version 2: July 5, 2018 Purpose The purpose of this Practice Guide is provide a reference to be used

More information

4.1.1 Generator Owner Transmission Owner that owns synchronous condenser(s)

4.1.1 Generator Owner Transmission Owner that owns synchronous condenser(s) A. Introduction 1. Title: Verification and Data Reporting of Generator Real and Reactive Power Capability and Synchronous Condenser Reactive Power Capability 2. Number: MOD-025-2 3. Purpose: To ensure

More information

Standard Development Timeline

Standard Development Timeline Standard Development Timeline This section is maintained by the drafting team during the development of the standard and will be removed when the standard is adopted by the NERC Board of Trustees (Board).

More information

4.1.1 Generator Owner Transmission Owner that owns synchronous condenser(s)

4.1.1 Generator Owner Transmission Owner that owns synchronous condenser(s) A. Introduction 1. Title: Verification and Data Reporting of Generator Real and Reactive Power Capability and Synchronous Condenser Reactive Power Capability 2. Number: MOD-025-2 3. Purpose: To ensure

More information

CIP Cyber Security Recovery Plans for BES Cyber Systems

CIP Cyber Security Recovery Plans for BES Cyber Systems Standard Development Timeline This section is maintained by the drafting team during the development of the standard and will be removed when the standard becomes effective. Development Steps Completed

More information

Requests for Clarifications And Responses Order No. 754 Data Request The Study of Single Point of Failure

Requests for Clarifications And Responses Order No. 754 Data Request The Study of Single Point of Failure Requests for Clarifications And Responses Order No. 754 Data Request The Study of Single Point of Failure Revised: July 12, 2013 Introduction The following information includes requests for clarification

More information

Studies Overview and Data Requirements. Robert Pan

Studies Overview and Data Requirements. Robert Pan Studies Overview and Data Requirements Robert Pan Outline 1. Introduction 2. BC Transmission System 3. BCTC Studies for Clean Power Call 4. Data Requirements for Interconnection Studies 5. Application

More information

Feasibility Study on Load Flow and Short Circuit Project

Feasibility Study on Load Flow and Short Circuit Project Feasibility Study on Load Flow and Short Circuit Project 101813-01 Prepared by: Transmission Planning Department Cleco Corporation, Inc. 2180 St. Landry Hwy P.O. Box 70 St. Landry, LA 71367 Final November

More information

Title. Critical Infrastructure Protection Getting Low with a Touch of Medium. CanWEA Operations and Maintenance Summit 2018.

Title. Critical Infrastructure Protection Getting Low with a Touch of Medium. CanWEA Operations and Maintenance Summit 2018. Critical Infrastructure Protection Getting Low with a Touch of Medium Title CanWEA Operations and Maintenance Summit 2018 January 30, 2018 George E. Brown Compliance Manager Acciona Wind Energy Canada

More information

TOP-001 v3 and v4 Monitoring Non-BES and Data Exchange Requirements. FRCC Spring RE Workshop April 17-18, 2018

TOP-001 v3 and v4 Monitoring Non-BES and Data Exchange Requirements. FRCC Spring RE Workshop April 17-18, 2018 TOP-001 v3 and v4 Monitoring Non-BES and Data Exchange Requirements FRCC Spring RE Workshop April 17-18, 2018 Objectives Background Reference Documents TOP-001-3 to TOP-001-4 Changes o R10 (TOP) Monitoring

More information

Unofficial Comment Form Project Operating Personnel Communications Protocols COM Operating Personnel Communications Protocols

Unofficial Comment Form Project Operating Personnel Communications Protocols COM Operating Personnel Communications Protocols Project 2007-02 Operating Personnel Communications Protocols COM-002-4 Operating Personnel Communications Protocols Please DO NOT use this form. Please use the electronic comment form to submit comments

More information

TOP for Transmission Operators

TOP for Transmission Operators Meeting Title Date TOP-001-4 for Transmission Operators Compliance Team Lead, Keith Smith Background Effective July 1, 2018 Replaces currently effective TOP-001-3 Modified to address reliability concerns

More information

Standards Authorization Request Form

Standards Authorization Request Form Standards Authorization Request Form When completed, email this form to: sarcomm@nerc.com NERC welcomes suggestions to improve the reliability of the bulk power system through improved reliability standards.

More information

CIP Cyber Security Recovery Plans for BES Cyber Systems

CIP Cyber Security Recovery Plans for BES Cyber Systems A. Introduction 1. Title: Cyber Security Recovery Plans for BES Cyber Systems 2. Number: CIP-009-6 3. Purpose: To recover reliability functions performed by BES Cyber Systems by specifying recovery plan

More information

Agreements and Queue Management

Agreements and Queue Management Agreements and Queue Management Infrastructure Contracts and Management Joanne Bradley, Queue Management Shoukat Ansari, Contract Negotiation PJ Topping, Regulatory Contracts February 27, 2019 Interconnection

More information

Interconnection and Transmission

Interconnection and Transmission Interconnection and Transmission Gary L. Brown, P.E. Director of Energy Development Gary@ZGlobal.biz 916-985-9461 Kevin Coffee Energy Management Committee Meeting Irvine, California August 26, 2015 Interconnection

More information

CROW Outage Scheduler Web GUI Tutorial

CROW Outage Scheduler Web GUI Tutorial CROW Outage Scheduler Web GUI Tutorial 9/14/2011 SPP Operations Engineering Revision History Date or Version Number Author Change Description Comments 06/22/2011 Derek Hawkins Initial Draft Draft for review

More information

Reliability Standard Audit Worksheet 1

Reliability Standard Audit Worksheet 1 Reliability Standard Audit Worksheet 1 FAC-003-4 Transmission Vegetation Management. Registered Entity Name: Applicable Function(s): Applicable only for TO and GO Compliance Monitoring Method: RSAW Version:

More information

requirements in a NERC or Regional Reliability Standard.

requirements in a NERC or Regional Reliability Standard. CIP 002 5.1 Cyber Security BES Cyber System Categorization A. Introduction 1. Title: Cyber Security BES Cyber System Categorization 2. Number: CIP 002 5.1 3. Purpose: To identify and categorize BES Cyber

More information

CIP Cyber Security Recovery Plans for BES Cyber Systems

CIP Cyber Security Recovery Plans for BES Cyber Systems A. Introduction 1. Title: Cyber Security Recovery Plans for BES Cyber Systems 2. Number: CIP-009-5 3. Purpose: To recover reliability functions performed by BES Cyber Systems by specifying recovery plan

More information

EEI Fall 2008 Legal Conference Boston, Massachusetts Stephen M. Spina November 1,

EEI Fall 2008 Legal Conference Boston, Massachusetts Stephen M. Spina November 1, EEI Fall 2008 Legal Conference Boston, Massachusetts Stephen M. Spina November 1, 2008 www.morganlewis.com Overview Reliability Standards Enforcement Framework Critical Infrastructure Protection (CIP)

More information

CIP Cyber Security Critical Cyber Asset Identification. Rationale and Implementation Reference Document

CIP Cyber Security Critical Cyber Asset Identification. Rationale and Implementation Reference Document CIP-002-4 Cyber Security Critical Cyber Asset Identification Rationale and Implementation Reference Document NERC Cyber Security Standards Drafting Team for Order 706 December 2010 This document provides

More information

Agenda Event Analysis Subcommittee Conference Call

Agenda Event Analysis Subcommittee Conference Call Agenda Event Analysis Subcommittee Conference Call August 14, 2013 11:00 a.m. 1:00 p.m. Eastern Ready Talk Conference Call and Web Meeting Information: Dial-In: 1-866-740-1260 Access Code: 6517175 Security

More information

Enhanced Curtailment Calculator Update

Enhanced Curtailment Calculator Update Enhanced Curtailment Calculator Update December 13, 2017 Member Advisory Committee Meeting Brett Wangen Chief Engineering and Technology Officer Jeremy West Manager, Interconnection Reliability Initiatives

More information

CIP Cyber Security Configuration Change Management and Vulnerability Assessments

CIP Cyber Security Configuration Change Management and Vulnerability Assessments Standard Development Timeline This section is maintained by the drafting team during the development of the standard and will be removed when the standard becomes effective. Development Steps Completed

More information

CIP Cyber Security Personnel & Training

CIP Cyber Security Personnel & Training A. Introduction 1. Title: Cyber Security Personnel & Training 2. Number: CIP-004-6 3. Purpose: To minimize the risk against compromise that could lead to misoperation or instability in the Bulk Electric

More information

RELIABILITY OF THE BULK POWER SYSTEM

RELIABILITY OF THE BULK POWER SYSTEM RELIABILITY OF THE BULK POWER SYSTEM Jim Burley, VP of Compliance, Mitigation and Standards October 26, 2011 Promoting RELIABILITY and Mitigating RISKS to the Bulk Power System Context In the Beginning-2003

More information

British Columbia Utilities Commission Reliability Standards with Effective Dates adopted in British Columbia

British Columbia Utilities Commission Reliability Standards with Effective Dates adopted in British Columbia Page 1 of 15 British Columbia Utilities Reliability Standards with s adopted in British Columbia BAL-001-2 Standard Real Power Balancing Control Performance R-14-16 July 1, 2016 BAL-002-1 1 Disturbance

More information

New Brunswick 2018 Annual Implementation Plan Version 1

New Brunswick 2018 Annual Implementation Plan Version 1 New Brunswick Energy and Utilities Board Reliability Standards, Compliance and Enforcement Program New Brunswick 2018 Annual Implementation Plan Version 1 December 28, 2017 Table of Contents Version History...

More information

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

This section is maintained by the drafting team during the development of the standard and will be removed when the standard becomes effective. Standard Development Timeline This section is maintained by the drafting team during the development of the standard and will be removed when the standard becomes effective. Description of Current Draft

More information

This draft standard is being posted for an initial comment and ballot. The draft includes modifications to meet the directives of FERC Order No. 791.

This draft standard is being posted for an initial comment and ballot. The draft includes modifications to meet the directives of FERC Order No. 791. Standard Development Timeline This section is maintained by the drafting team during the development of the standard and will be removed when the standard becomes effective. Development Steps Completed

More information

ERO Enterprise IT Projects Update

ERO Enterprise IT Projects Update ERO Enterprise IT Projects Update Stan Hoptroff, Vice President, Chief Technology Officer and Director of Information Technology Technology and Security Committee Meeting November 6, 2018 Agenda ERO IT

More information

Québec Reliability Standards Compliance Monitoring and Enforcement Program Implementation Plan Annual Implementation Plan

Québec Reliability Standards Compliance Monitoring and Enforcement Program Implementation Plan Annual Implementation Plan Québec Reliability Standards Compliance Monitoring and Enforcement Program Implementation Plan 2017 Annual Implementation Plan Effective Date: January 1, 2017 Approved by the Régie: December 1, 2016 Table

More information

Resource Adequacy Pre-Market Simulation Training Workshop

Resource Adequacy Pre-Market Simulation Training Workshop Resource Adequacy Pre-Market Simulation Training Workshop Focusing on the following initiatives: Reliability Services Initiative (RSI) Capacity Procurement Mechanism (CPM) Replacement October 21, 2015

More information

Reliability Standard Audit Worksheet 1

Reliability Standard Audit Worksheet 1 Reliability Standard Audit Worksheet 1 CIP-012-1 Cyber Security Communications between Control Centers This section to be completed by the Compliance Enforcement Authority. Audit ID: Registered Entity:

More information

Standards Authorization Request Justification

Standards Authorization Request Justification Standards Authorization Request Justification Project 2009-02 Real-time Monitoring and Analysis Capabilities NERC Report Title Report Date 1 of 30 3353 Peachtree Road NE Suite 600, North Tower Atlanta,

More information

A. Introduction. B. Requirements and Measures

A. Introduction. B. Requirements and Measures A. Introduction 1. Title: Communications 2. Number: COM-001-3 3. Purpose: To establish Communication capabilities necessary to maintain reliability. 4. Applicability: 4.1. Functional Entities: 4.1.1. Transmission

More information

Modifications to TOP and IRO Standards

Modifications to TOP and IRO Standards Modifications to TOP and IRO Standards Jason Smith, Mgr Reliability Standards Development SPP RTO Compliance Forum September 21-22, 2016 Project 2016-01 Background FERC issued Order No. 817 in November

More information

CIP Cyber Security Personnel & Training

CIP Cyber Security Personnel & Training A. Introduction 1. Title: Cyber Security Personnel & Training 2. Number: CIP-004-5.1 3. Purpose: To minimize the risk against compromise that could lead to misoperation or instability in the BES from individuals

More information

edart Quick Reference Guide

edart Quick Reference Guide edart Quick Reference Guide Revision: 05 Effective Date: 08/16/2017 PJM 2017 Prepared by edart Project Team Table of Contents Table of Contents... 2 Revision History... 6 About the Quick Reference Guide...

More information

PG&E Transmission Interconnection Handbook

PG&E Transmission Interconnection Handbook Table of Contents TABLE OF CONTENTS... 1 UPDATE HISTORY... UP-1 INTRODUCTION... IN-1 I-1. PURPOSE... IN-1 I-2. INTRODUCTORY DEFINITIONS... IN-1 I-3. HANDBOOK APPLICABILITY... IN-2 I-3.1. New Load, New

More information

Unofficial Comment Form 1st Draft of PRC-005-3: Protection System and Automatic Reclosing Maintenance (Project )

Unofficial Comment Form 1st Draft of PRC-005-3: Protection System and Automatic Reclosing Maintenance (Project ) Unofficial Comment Form 1st Draft of PRC-005-3: Protection System and Automatic Reclosing Maintenance (Project 2007-17.2) Please DO NOT use this form for submitting comments. Please use the electronic

More information

CIP Cyber Security Standards. Development Update

CIP Cyber Security Standards. Development Update CIP Cyber Security Standards Development Update John Lim Consolidated Edison Co. of New York Rob Antonishen Ontario Power Generation September 21-22, 2010 1 Disclaimer This NPCC TFIST workshop provides

More information

A. Introduction 1. Title: 2. Number: 3. Purpose: 4. Applicability: 4.1. Functional Entities: Balancing Authority Distribution Provider

A. Introduction 1. Title: 2. Number: 3. Purpose: 4. Applicability: 4.1. Functional Entities: Balancing Authority Distribution Provider The Background, VRF/VSLs, and Guidelines and Technical Basis Sections have been removed for this informal posting. The Project 2016-02 is seeking comments around the concept of the Requirement/Measure

More information

Reliability Standard Audit Worksheet 1

Reliability Standard Audit Worksheet 1 Reliability Standard Audit Worksheet 1 CIP-006-6 Cyber Security Physical Security of BES Cyber Systems This section to be completed by the Compliance Enforcement Authority. Audit ID: Registered Entity:

More information

CIP Cyber Security Systems Security Management

CIP Cyber Security Systems Security Management A. Introduction 1. Title: Cyber Security System Security Management 2. Number: CIP-007-5 3. Purpose: To manage system security by specifying select technical, operational, and procedural requirements in

More information

Project , COM Operating Personnel Communications Protocols Rationale and Technical Justification

Project , COM Operating Personnel Communications Protocols Rationale and Technical Justification Project 2007-02, COM-002-4 Operating Personnel Communications Protocols Rationale and Technical Justification Posting 8: Background and Justification for COM-002-4 Requirements The purpose of the proposed

More information

CIP V5 Implementation Study SMUD s Experience

CIP V5 Implementation Study SMUD s Experience CIP V5 Implementation Study SMUD s Experience Tim Kelley October 16, 2014 Powering forward. Together. SMUD Fast Facts General Information SMUD employs approximately 2,000 individuals Service area of 900

More information

State of Reliability Report 2013

State of Reliability Report 2013 State of Reliability Report 2013 Jessica Bian, Director of Performance Analysis Reliability Assessment and Performance Analysis (RAPA), NERC Risk Issues Steering Committee Meeting, July 11-12, 2013 State

More information