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 by Jason and Neil. 6/28/2011 Version 1.1 6/30/2011 Version 1.2 7/22/2011 Version 1.3 9/14/2011 Version 1.4 Derek Hawkins Updates based on initial reviews by the project team. For review and post to members. Derek Hawkins Screenshot updates Updates correspond to CROW ver. 5.3.0.117 Derek Hawkins Additions: Outage Statuses Outage Flags User Role Setup Jason Smith Clarification of tables reference from Appendix 12. Clarification on Planned End Time of Forced outages. Corrected max lead time for forced generation outages to match Appendix 12. Updated screenshots to reflect button move in GUI. Requests from members during the ITE testing phase. CROW Outage Scheduler Web GUI Tutorial 2
Table of Contents Revision History...2 Introduction to CROW...4 Outage Coordination Methodology Tables...4 Outage Priorities... 4 Outage Request Types... 5 Outage Causes... 6 Outage Statuses... 7 Outage Flags... 8 Facility Naming Conventions...9 Fundamental Model Characteristics... 9 Naming Conventions... 9 User Role Setup...11 OPS1 versus CROW...12 CROW Web Interface...13 Login... 13 Navigation... 13 Useful Navigation Hints... 17 Outage Submissions...18 New Request (Forced)...18 New Request (Un-forced)...23 Changing an Existing Request (Forced)...27 Changing an Existing Request (Un-forced)...29 CROW Outage Scheduler Web GUI Tutorial 3
Introduction to CROW Southwest Power Pool s CROW outage scheduler will be used by members of SPP to submit and coordinate transmission and generation outages. The SPP CROW application replaces the GEN_S and TRAN_S applications that have resided in SPP s OPS1 portal. CROW allows greater flexibility in order to meet each individual company s business needs related to outage coordination. Access to the transmission and/or generation information of each entity in the SPP CROW system is fully configurable based on each individual user account. Outage Coordination Methodology Tables All of the following tables are referenced from SPP Criteria Appendix 12: Outage Coordination Methodology. Outage Priorities Transmission Outage Priorities Priority Definition Minimum Lead Time Planned Equipment is known to be operable with little risk of leading to a forced outage. As required for preventive maintenance, troubleshooting, repairs that are not viewed as urgent, system improvements such as capacity upgrades, the installation of additional facilities, or the replacement of equipment due to obsolescence. Discretionary Equipment is known to be operable with little risk of leading to a forced outage; however the timeline for submission of Planned outage priority has passed. Discretionary outages are required to be submitted at least 2 calendar days in advance. Due to the shorter lead time, this outage priority has increased risk of being denied based upon higher priority outage requests. Opportunity Lead time may be very short or zero. An outage that can be taken None due to changed system conditions (i.e. Generator suddenly offline for forced outage allows transmission work to be done). Operational Equipment is removed from service for operational reasons such None as voltage control, constraint mitigation as identified in an operating procedure, etc. Urgent Equipment is known to be operable, yet carries an increased risk of a forced outage or equipment loss. The equipment remains in service until maintenance crews are ready to perform the work. Emergency Equipment is to be removed from service by operator as soon as None possible because of safety concerns or increased risk to grid security. 7 Days None Maximum Lead Time 2 Days 7 Days 7 Days None 2 Hours 48 Hours 2 Hours Forced Equipment is out of service at the time of the request. None 1 Hour Figure 1: Transmission Outage Priorities CROW Outage Scheduler Web GUI Tutorial 4
Generation Outage/Derate Priorities Priority Definition Minimum Lead Time Maximum Lead Time Planned Equipment is known to be operable with little risk of leading 2 Days None to a forced outage. As required for preventive maintenance, troubleshooting, repairs that are not viewed as urgent, system improvements such as capacity upgrades, the installation of additional facilities, or the replacement of equipment due to obsolescence. Urgent Equipment is known to be operable, yet carries an increased 24 Hours 7 Days risk of a forced outage or equipment loss. The equipment remains in service until maintenance crews are ready to perform the work. Emergency Equipment is to be removed from service by operator as None 24 Hours soon as possible because of safety concerns or increased risk to grid security. Forced Equipment is out of service at the time of the request. None None Figure 2: Generation Outage Priorities Outage Request Types Transmission Outage Types Outage Request Type Out of Service (OOS) Normally Open (NO) Informational (INF) Hot Line Work (HLW) General System Protection (GSP) Definition Equipment is out of service. Equipment is normally out of service and is identified as normally open in the SPP regional models. Normally Open request type is used to close (place in service) a normally open facility. Used for outage events that are not covered by one of the other Outage Equipment Request Types. Not an out of service event. Work is being performed on live or energized equipment. Work is being performed on protection systems. Requestor shall specifically identify protection systems out of service and any modification to operation or behavior of system contingencies. Figure 3: Transmission Outage Types Modeling Assumptions SDX = Open EMS = Open SDX = Closed EMS = Closed None Informational Only None Informational Only None Informational Only Generation Outage/Derate Types Request Type Out of Service Derate Definition Modeling Assumption Generator or Resource is out of service. SDX = offline EMS = offline Generator or Resource maximum capability is lowered from SDX = online, with new lower normal operation. A new maximum capability is required PMAX to be submitted with each Outage Request Type of Derate. EMS = online, with new lower PMAX Figure 4: Generation Outage/Derate Types CROW Outage Scheduler Web GUI Tutorial 5
Outage Causes Transmission Outage Causes Reason Definition Maintenance & Construction Outages to facilitate repair, maintain, or upgrade of facility related equipment. This includes clearances to perform vegetation management. Does not include outages to support Maintenance & Construction of other facilities. Those should be submitted as Voltage or SOL Mitigation. Third Party Request Non-transmission facility related requests for clearance or work such as highway construction. Voltage Mitigation Operation of facilities to preserve or correct Bulk Electric System voltage. SOL Mitigation (Thermal) Operation of facilities to preserve or correct Bulk Electric System thermal loading issues. Weather/Environmental/Fire Outages caused by wind, ice, snow, fire, flood, etc. All weather or (excluding Lightning) environmental causes excluding lightning strikes. Lightning Outages caused by direct or indirect Lightning strikes. Foreign Interference (including Outages caused by blown debris, bird droppings, kites, falling conductors, contamination) airplanes, etc. Vandalism/Terrorism/Malicious Outages resulting from known or suspected vandalism, terrorism, or other Acts malicious acts. Equipment Failure Outages resulting from failure of facility related equipment. Imminent Equipment Failure Operation of facilities due to expected imminent facility rated equipment failure. Protection System Failure Operation of facilities due to failure or undesired operation of the facility including Undesired Operations protection systems. Vegetation Outages resulting from contact with vegetation. This does not include outages due to clearances required to perform vegetation management which should be submitted as Maintenance & Construction. This does not include vegetation blown into rights of way or into contact with facilities which should be submitted as Foreign Interference. BES Condition (Stability, Outages resulting from Bulk Electric System conditions such as islanding, Loading) cascading outages, sudden thermal loading due to other contingencies, transient stability conditions, etc. Unknown Operation of facilities due to an unknown reason. Most forced outages will be submitted with an initial reason of Unknown. Once the actual reason for the operation is known, the outage requestor should update the outage request. SPP Staff will follow up after some time to determine the actual outage reason for any outages which still have a reason of Unknown submitted. Other Operation of facilities due to a reason not listed here. Figure 5: Transmission Outage Reasons CROW Outage Scheduler Web GUI Tutorial 6
Generation Outage/Derate Causes Reason Equipment Failure Imminent Equipment Failure BES Reliability Loss of Interconnection BES Stability Fuel Supply Regulatory/Safety/En vironmental Unknown Routine Generator Maintenance Supporting Transmission Outage BES Reliability Excess Capacity/Economic Outage Statuses Status Proposed Submitted Study Definition Failure in station generation, prime mover, or other equipment has occurred. Does not include failure of GSU transformers or interconnection facilities. Does include equipment related to fuel delivery considered a part of the resource (such as a coal mill). Expected failure in station generation, prime mover, or other equipment. Does not include failure of GSU transformers or interconnection facilities. Does include equipment related to fuel delivery considered a part of the resource (such as a coal mill). Removal from service or limitation to preserve or correct Bulk Electric System reliability issues either through action of a Special Protection System, runback scheme, or as mitigation of another reliability event. Failure in interconnection equipment such as GSU transformers or other interconnection facilities. Does not include loss of synchronization due to stability or islanding type events. Removal from service or limitation due to Bulk Electric System stability issues. Includes loss of synchronization due to transient stability and/or islanding issues. Removal from service or limitation due to fuel supply interruption. Does not include local equipment failures related to fuel supply. Includes loss of gas pressure due to offsite issue, coal supply exhaustion, lack of headwater issues for hydro, etc. Removal from service or limitation due to Regulatory/Safety/Environmental restrictions such as emission limits, OSHA, NRC, or other regulatory body limitations. Includes damage caused by weather including but not limited to lightning, flood, earthquake, etc. This may also include limitations to hydro due to low dissolved oxygen in tail water or to control downstream flooding. The default Forced Outage/Derate reason will be pre-populated with Unknown at the time of submittal. Either during the initial outage submittal or at a later time, the Unknown reason must be changed to reflect the actual experienced issue. Removal from service or limitation in order to perform repair or inspection of generation equipment. Removal from service or limitation in order to support a scheduled transmission outage. Removal from service or limitation to preserve or correct a Bulk Electric System reliability issue. Removal from service or limitation due to seasonal or system capacity need. This includes peaker units not expected to be used during winter months. Figure 6: Generation Outage/Derate Reasons Definition The outage request has been saved in the outage scheduler system and remains under the full revision control until the outage is entered into a Submitted state by the requestor. If the requestor does not move a proposed request to the submitted status within 30 days of the planned start date, the outage is automatically Withdrawn. Proposed outage request status dates DO NOT qualify for outage queuing in conflict resolution. Proposed outage requests are not provided to external systems such as NERC SDX/IDC or SPP s EMS. The outage request has been submitted into the outage scheduler system and is ready for review by SPP. The outage requestor does not possess revision control of the outage in this status. A revision request may be submitted to SPP regarding an outage in Submitted status. Outage requests in this state are provided to external systems such as NERC SDX/IDC or SPP s EMS. SPP will change the status type to Study once the active study process begins. Outage CROW Outage Scheduler Web GUI Tutorial 7
Preliminary Approved Approved Implemented Completed requests in this state are provided to external systems such as NERC SDX/IDC or SPP s EMS. Outage requests with Preliminary Approved status have been approved based on long lead studies and may need additional analysis closer to the planned start date or finalization of an Operating Guide. Once the restudy is complete or final opguide posted, the outage status is changed to Approved. Outage requests in this state are provided to external systems such as NERC SDX/IDC or SPP s EMS. Approved state indicates SPP has completed the study process and the outage request is ready for implementation. Outage requests in this state are provided to external systems such as NERC SDX/IDC or SPP s EMS. Once the outage request actual start time has been entered, signifying that the outage has begun, the outage status is changed to Implemented. Outage requests in this state are provided to external systems such as NERC SDX/IDC or SPP s EMS. Once the outage request actual end time has been entered, signifying that the outage has ended, the outage status is changed to Completed. Outage requests in this state are NO LONGER provided to external systems such as NERC SDX/IDC or SPP s EMS. Outage Flags Transmission Outage Flags Flag Perm. FG Element MTE Op Guide JOA Tie Line Definition This flag will be set when the equipment is determined to be an element of a permanent flowgate. Major Transmission Element This flag is set for the following equipment: All transmission facilities rated at 230kV or above. All tie lines, 60kV and above. All facilities, monitored and contingent elements, associated with flowgates Other facilities specified by the Transmission Operator or the Reliability Coordinator as having a major impact on the Bulk Electric System or that affect the capability and reliability of generating facilities (backup station power, etc). If the request has an operating guide associated with the outage then this flag will be set. Joint Operating Agreement This flag will be set for equipment identified as those that outages must be coordinated with MISO/TVA per our Joint Operating Agreements with those entities. This flag is set when the To and From stations are operated by different companies. Generation Outage Flags Flag Black Start JOU Definition This flag will be set for units that have been designated as black start units. Joint Owned Unit This flag is set for units that are owned by multiple companies. CROW Outage Scheduler Web GUI Tutorial 8
Facility Naming Conventions Fundamental Model Characteristics All bulk electric system equipment in the model in SPP CROW will be associated with a Station. For purposes of the SPP CROW project, a Station will be defined as all the bulk electric system equipment located at a geographic location. For the initial implementation of SPP CROW, the types of bulk electric system equipment that will be included in the model will be Units, Lines, and Transformers. Other types of bulk electric system equipment may be included in later upgrades to the SPP CROW system. Units and Transformers will be associated with (attached to) a Station in the CROW model. A Line will connect two Stations in the model. Each Line will be listed in CROW as equipment under both stations it connects to. Naming Conventions Stations Each Station will be given a single common name. This common name will be the name most often used collectively by transmission owners, transmission operators, and reliability coordinators when referring to a station. Station names should be spelled out completely. If station names contain a direction to distinguish between two stations, the direction will follow the actual station name. Directions can be used as an integral part of the station name. If two stations within the SPP Reliability Coordination area have the same name, the station operator s abbreviated name with be added. Station Name Examples NW Texarkana Northwest Texarkana (Preferred) East Fayetteville, South Fayetteville Fayetteville East, Fayetteville South (Preferred) Hugo WFEC Hugo AEP From these common names, a 12 character limited station name abbreviation will also be determined. If the full station name is 12 characters or less, the full name and abbreviated name will be the same. An appropriate abbreviation of this common name will be critical as station abbreviations are used frequently in CROW in place of the full station name. CROW Outage Scheduler Web GUI Tutorial 9
Equipment The SPP CROW system allows for three discreet names for each individual piece of bulk electric system equipment; Lines, Transformers, and Units. These are an SPP EMS NAME, COMMON NAME, and an ALTERNATE NAME. SPP will determine the SPP EMS NAME for each piece of equipment by its associated EMS equipment. The equipment Owner/Operator and SPP will collaborate to determine the most appropriate COMMON NAME. ALTERNATE NAMES can be set by the equipment Owner/Operator. Lines Each transmission line s Common Name will be the combination of a From Station name and a To Station name along with the voltage level. Circuit ID numbers will only be used in cases of double circuits or uncommon equipment configurations. The From and To stations will be placed in alphabetical order to form the line names. Line Common Name Examples Northwest Texarkana Lydia 345kV Lydia Northwest Texarkana 345kV (Preferred) Transformers Each transformer common name will be the common name of the station at which it is located along with the high and low side voltage levels. Circuit ID numbers will only be used in cases of double circuits or uncommon equipment configurations. Directions can be used in place of circuit ID numbers to distinguish transformers of the same high and low side voltage level at the same station. Transformer Common Name Examples Northwest Texarkana North 345/138kV Northwest Texarkana South 345/138kV CROW Outage Scheduler Web GUI Tutorial 10
User Role Setup The CROW system allows the flexibility to meet each individual company s business needs related to the access of transmission and/or generation information of each entity. The system is fully configurable based on each individual user account. SPP will work with each user to determine the appropriate access and review authority to preserve code of conduct integrity. The graphic below outlines the user role model that SPP will follow. Transmission and Reliability roles have the capability to view or submit outages for all types of equipment within its company. Generation and Marketing roles are only able to view or submit outages for Units within its company. Please note that individual users can be set up with read-only access or full outage submittal privileges. Southwest Power Pool Balancing Authority A TOP A GOP A IPP C Balancing Authority B TOP B GOP B TOP D Company A Trans. Reliability Role Company A Generation Marketing Role Company C Generation Marketing Role Company B Trans. Reliability Role Company B Generation Marketing Role Company D Trans. Reliability Role TOP A Lines TOP A XFMRs GOP A Units IPP C Units TOP B Lines TOP B XFMRs GOP B Units TOP D Lines TOP D XFMRs CROW Equipment CROW Outage Scheduler Web GUI Tutorial 11
OPS1 versus CROW SPP is replacing the Transmission and Generation Outage Scheduler applications on OPS1 with a new application by Equinox Software called the CROW Outage Scheduler. CROW will allow varying levels of granularity within companies and NERC registered entities. Individual Generator Operators (GOP s) within a BA or TOP may also be configured to provide outage requests independent of other entities within the larger entity. SPP will work with each user to determine the appropriate access and review authority to preserve code of conduct integrity. CROW simply replaces the TRANS and GENS outage submission functionality in OPS1. All other valid applications on OPS1 such as CPS, Hourly Load, Load Forecast, Load and Capability, Reports, etc. are not impacted nor replaced by the CROW Outage Scheduler. Important Differences between OPS1 and CROW The historical limitations in OPS1 did not allow much granularity in separation of different entities data, so submission on a Balancing Authority level was required. The CROW system allows the flexibility to meet each individual company s business needs related to the access of transmission and/or generation information of each entity. The system is fully configurable based on each individual user account. Currently in OPS1, station names are listed in an abbreviated form. With CROW s flexibility, SPP will use complete names to reduce opportunities for confusion. SPP has attempted to collaborate with the members in order to compile an agreed upon list of common station names. Generation derates will be handled differently in CROW from what is currently in OPS1. Generation derates in CROW will become the unit s new Pmax. An OPS1 generation derate was the amount that the unit was derated by. Example Unit 1 derated from a Pmax of 600 MW to 400 MW: CROW derate = 400 MW OPS1 derate = 200 MW Required Fields: OPS1 1. Start Time 2. End Time 3. Outage Priority (Maintenance or Forced) CROW 1. Start Time 2. End Time 3. Outage Priority 4. Outage Type 5. Outage Cause 6. Recall Time (or Unrecallable) CROW Outage Scheduler Web GUI Tutorial 12
CROW Web Interface The following section will address logging in to the SPP CROW Web application as well as basic navigation procedures and settings configurations. Login Upon accessing the PROD CROW URL (https://portal.spp.org/crow/) the user will be asked to select the certificate that was provided for member access. Once selected, the Outage Request Index screen will be displayed. Note that only a small set of equipment will be available in ITE CROW for beta testing purposes. Figure 7: Select certificate provided for access. Navigation Upon logging in to CROW Web the user will notice three tabs for navigation. The primary tabs that are common to all screens are Operations Reports, Outage Requests, and Options. Navigating between the primary tabs will populate secondary tabs specific to the current screen. Figure 8: Primary tabs common to all screens. CROW Outage Scheduler Web GUI Tutorial 13
1. Operations Reports a. CROW has the ability to allow users to define custom reports. These reports can be set up to view one time online or emailed to the user. It also allows for users to subscribe to reports and receive those reports via email on a user specified time basis. Figure 9: Operations Reports Tab CROW Outage Scheduler Web GUI Tutorial 14
2. Outage Requests Home a. This is the default Home screen that shows the Outage Request Index. b. The index only shows equipment that the user profile has been configured to have access to. c. This index can also be filtered using the Date/Time fields or the available drop down lists. To apply the filters, the user must click. d. New outage requests will be submitted here using the button. e. Outage request summaries can be viewed for previously submitted outages by double-clicking the request in the index. f. CROW allows the user to. This will open an Excel window containing all of the outage requests that are being displayed in the Outage Request Index. Figure 10: Outage Requests Tab displaying the Outage Request Index CROW Outage Scheduler Web GUI Tutorial 15
3. Options a. The Options tab allows users to configure the SPP CROW Web application to meet their specific business needs. b. Users can change time zones, naming conventions, and request outage approval/denial notifications via email. Figure 11: CROW Administrative Options Screen CROW Outage Scheduler Web GUI Tutorial 16
Useful Navigation Hints Buttons: Figure 12: Navigation buttons available from the Request Summary, Request Details/Approval, and Attachments screens. Back Returns to the previous screen. Export Opens a Word document containing the outage request details. Duplicate Displays a new Request Summary screen with the fields completed using the same data from the outage request that was selected to duplicate. Home Returns the user to the Outage Request Index screen. CROW Outage Scheduler Web GUI Tutorial 17
Outage Submissions The primary focus of SPP members will be outage submission. The following sections will detail new outage submissions as well as modifications to previously submitted outage request. The outage submission process will differ depending on the priority selected. For this guide, two types of priorities will be considered: forced and un-forced. All priorities excluding forced have a similar submission process; therefore, this tutorial will only cover that process once. New Request (Forced) 1. The first step in submitting a new outage is to click the New Outage Request button from the Outage Request Index screen. CROW Outage Scheduler Web GUI Tutorial 18
2. Step one creates a new screen under the Outage Request primary tab that displays the Request Summary tab. This is the screen where equipment will be added and outage request criteria will be completed. The first step from this screen will be to click Add in order to select the equipment that is being submitted. Select Add CROW Outage Scheduler Web GUI Tutorial 19
3. After selecting Add, the Select Circuits/Equipment window appears. This window allows the user to select the equipment using the drop down lists. Once the equipment is highlighted, click OK to return to the Request Summary screen noting that the equipment has been added to the Equip. Requested table. CROW Outage Scheduler Web GUI Tutorial 20
4. For this example we have chosen a Forced outage with the outage cause Unknown. (If upon further investigation the cause is discovered, then CROW allows for the outage request to be modified with the updated information. This is addressed in the next section.) We can now Implement the outage request. It is important to note that since this is a Forced outage, the only option is to Implement the outage since it should have already started. The default Planned End Time for a Forced Priority Outage is approximately 24 hours in the future. The Planned End Time can be updated later as more information about the Forced outage is known. 5. Since this is a Forced outage, a new window is displayed that allows the user to log the actual outage start time before completing the implementation. CROW Outage Scheduler Web GUI Tutorial 21
6. Upon successful implementation, the application returns to the Request Summary with a notification in green that the outage submission was completed successfully. When the outage is in this state, the user has the option to Request Change to the outage, Save any changes made to the outage, or Complete the outage by entering the time when equipment was returned to service. The outage request will also appear in the Outage Request Index. CROW Outage Scheduler Web GUI Tutorial 22
7. If the outage request conflicts with an existing outage request, the user will receive the following error indicating the existing outage request. 8. Users should utilize the Request Change button to update the Planned End time or Outage Cause for submitted outages. New Request (Un forced) 1. This example will consider a Planned outage to demonstrate the process for submitting unforced outages. Begin by clicking New Outage Request from the Outage Request Index page. CROW Outage Scheduler Web GUI Tutorial 23
2. Step one creates a new screen under the Outage Request primary tab that displays the Request Summary tab. From here equipment will be added and outage request criteria will be completed. The first step from this screen will be to click Add in order to select the equipment that is being submitted. Select Add 3. After selecting Add, the Select Circuits/Equipment window appears allowing the user to select the equipment using the drop down lists. Once the equipment is highlighted, click OK to return to the Request Summary screen noting that the equipment has been added to the Equip. Requested table. CROW Outage Scheduler Web GUI Tutorial 24
CROW Outage Scheduler Web GUI Tutorial 25
4. Once the equipment has been added to the request, the Outage Priority should be selected. This example specifies a Planned outage priority that will be Continuously out of service for the time span indicated. Also, a Min. Recall Time of 2 hours has been selected signifying that it would take at least 2 hours to return this equipment to service if directed to do so. After selecting Maintenance and Construction for the Outage Cause, notice that Planned outage requests offer the ability to Save Proposed outage request or Submit the outage request. Clicking Submit sends the outage request to SPP for analysis. Save Proposed requests are not visible to SPP and do not have a secured queue date. 5. Upon submittal, a green notification will be displayed at the top of the Outage Request Index page if the outage request was completed successfully. CROW Outage Scheduler Web GUI Tutorial 26
Changing an Existing Request (Forced) 1. To modify an existing outage request, or to notify SPP that the outage has ended by updating the Planned End Time, start by locating the outage in the Outage Request Index and doubleclicking the request. Notice that when the Request Summary screen is displayed that the fields are grayed-out indicating that they cannot be changed from this page. 2. Click Request Change to display a new Request Summary that will allow the fields to be changed. For this example, the outage cause will be updated from Unknown to Equipment Failure. CROW Outage Scheduler Web GUI Tutorial 27
3. Next, Submit the change insuring that a green notification is received. 4. The change request can be viewed in the Change Requests tab. 5. This outage request can no longer be modified until SPP staff has updated the approval status of the change request. CROW Outage Scheduler Web GUI Tutorial 28
Changing an Existing Request (Un forced) 1. To modify an existing outage request, start by locating the outage in the Outage Request Index and double-clicking the request. For this example, the outage request has been Preapproved by SPP. The CROW Web indicates a change in outage request status by highlighting the request in the Outage Request Index. 2. Notice that when the Request Summary screen is displayed that the fields are grayed-out indicating that they cannot be changed from this page. The Outage Status field is also red indicating that this field has been modified. CROW Outage Scheduler Web GUI Tutorial 29
3. There are two options with a Planned request that is in the Pre-Approved status: Request Change or Request Cancel. Click Request Change to display a new Request Summary that allows the fields to be modified. Note that change requests can only be submitted prior to the outage request reaching the implemented status. The Planned end date will be changed for this example. CROW Outage Scheduler Web GUI Tutorial 30
4. Next, Submit the change insuring that a green notification is received. This request has now been sent to SPP for analysis. CROW Outage Scheduler Web GUI Tutorial 31
5. CROW also allows the user to export the revision history of the outage request into an Excel spreadsheet by clicking. The following window would be displayed. CROW Outage Scheduler Web GUI Tutorial 32