GUIDE 10 Outage Scheduler User's Guide September 2016
Version: 3.0 Revision Date: 09/13/2016 This document was prepared by: Scheduling, Energy Market Operations New York Independent System Operator 10 Krey Blvd Rensselaer, NY 12144 (518) 356-6060 www.nyiso.com Disclaimer The information contained within this guide, along with the other NYISO documents, is intended to be used for informational purposes and is subject to change. The NYISO is not responsible for the user s reliance on these publications or for any erroneous or misleading material. Copyright 1999-2016 New York Independent System Operator
Table of Contents Table of Figures... v Revision History... vii 1. Introduction... 1-1 1.1 Definition of an Outage Request... 1-1 1.2 Description of the Outage Scheduler (itoa) System... 1-1 1.3 Outage Scheduler (itoa) System Users... 1-1 1.4 Obtaining Help and Handling Error Messages... 1-1 2. User Requirements... 2-1 2.1 Computer Hardware and Software... 2-1 2.2 Digital Certificates and MIS Privileges... 2-1 2.3 Logging in to the Outage Scheduler (itoa) System... 2-1 3. New Outage Request... 3-1 3.1 New Outage Request (Generation)... 3-1 3.1.1 Generation Outage Request Entry Process... 3-1 3.1.2 Required Information for a Generation Outage Request... 3-1 3.1.3 Steps to Create a Generation Outage Request... 3-1 3.2 New Outage Request (Transmission)... 3-6 3.2.1 Transmission Outage Request Entry Process... 3-6 3.2.2 Required Information for a Transmission Outage Request... 3-6 3.2.3 Steps to Create a Transmission Outage Request... 3-7 4. Outage Request Status Conditions... 4-1 4.1 Request States... 4-1 5. Actions... 5-1 5.1 Actions... 5-1 6. Process Flow... 6-3 6.1 Outage Request Process Flow (GO User)... 6-3 6.2 Outage Request Process Flow (TO User)... 6-5 7. Outage Request List... 7-1 8. Pending Request List... 8-1 9. Uploading Outage Requests... 9-1 9.1 Generation Upload Introduction... 9-1 9.1.1 Overview of the Upload Templates... 9-5 9.1.1.1 Template Header... 9-5 9.1.1.2 Template Body (Generation)... 9-5 9.1.2 Addition Upload Rules and Requirements... 9-8 9.1.2.1 Submitting a new GO Outage Request... 9-8 9.1.2.2 Modifying a GO Outage Request... 9-8 9.1.2.3 Cancelling a GO Outage Request... 9-8 9.1.2.4 Completing a GO Outage Request... 9-9 9.1.3 Upload Process... 9-9 9.1.4 CSV Validation... 9-9 9.1.4.1 Format Validation... 9-10 9.1.4.2 Syntax Validation... 9-12 9.1.4.3 Business Rules Validation... 9-13 9.1.5 Upload Examples and Validation Messaging... 9-15 Operations Products, Market Structures iii
9.2 Transmission Upload Introduction... 9-19 9.2.1 Overview of the Upload Templates... 9-21 9.2.1.1 Authentication Requirement... 9-21 9.2.1.2 Template Header... 9-21 9.2.1.3 Template Payload... 9-22 9.2.2 Additional Upload Rules and Requirements... 9-25 9.2.2.1 Submitting a new TO Outage Request... 9-25 9.2.2.2 Modifying a TO Outage Request... 9-25 9.2.2.3 Cancelling a TO Outage Request... 9-27 9.2.2.4 Approving a TO Outage Request... 9-27 9.2.2.5 Denying a TO Outage Request... 9-27 9.2.3 XML Validation... 9-27 9.2.3.1 Outage Request Re-Submission Detection... 9-29 9.2.4 Additional TO Upload Information... 9-30 Appendix A. Acronyms... A iv Scheduling, Energy Market Operations
Table of Figures Figure 2-1 NYISO Home Page...2-2 Figure 2-2 Expanded NYISO Markets & Operations Header Highlighting Market Access Login Link...2-3 Figure 2-3 Market Access Login Web Page Highlighting User Login Link for the Outage Scheduler (itoa) System...2-4 Figure 2-4 NYISO Outage Scheduler (itoa) Login Page...2-5 Figure 2-5 NYISO Outage Scheduler (itoa) Main Menu (TO)...2-6 Figure 2-6 NYISO Outage Scheduler (itoa) Main Menu (GO)...2-6 Figure 3-1 NYISO GO Outage Request Entry Form...3-2 Figure 3-2 NYISO GO Outage Request Entry Form...3-2 Figure 3-3 NYISO GO Outage Request Entry Form - General Tab...3-3 Figure 3-4 NYISO GO Outage Request Entry Form - Schedule Tab...3-4 Figure 3-5 NYISO GO Outage Request Entry Form - Contact Tab...3-4 Figure 3-6 NYISO GO Outage Request Entry Form - History Tab...3-5 Figure 3-7 NYISO GO Outage Request Entry Form - Audit Trail Tab...3-5 Figure 3-8 NYISO GO Outage Request Entry Form - Remarks Tab...3-6 Figure 3-9 NYISO TO Outage Request Entry Form...3-8 Figure 3-10 NYISO TO Outage Request Entry Form...3-9 Figure 3-11 NYISO TO Outage Request Entry Form - General Tab... 3-10 Figure 3-12 NYISO TO Outage Request Entry Form - Schedule Tab... 3-11 Figure 3-13 NYISO TO Outage Request Entry Form - Contact Tab... 3-11 Figure 3-14 NYISO TO Outage Request Entry Form - History Tab... 3-12 Figure 3-15 NYISO TO Outage Request Entry Form - Audit Trail Tab... 3-13 Figure 3-16 NYISO TO Outage Request Entry Form - Remarks Tab... 3-13 Figure 6-1 GO Outage Request Process Flow Diagram - 1 of 2...6-3 Figure 6-2 GO Outage Request Process Flow Diagram - 2 of 2...6-4 Figure 6-3 TO Outage Request Process Flow Diagram - 1 of 2...6-5 Figure 6-4 TO Outage Request Process Flow Diagram - 2 of 2...6-6 Figure 7-1 NYISO Outage Scheduler (itoa): TO Outage Request List...7-1 Figure 7-2 NYISO Outage Scheduler (itoa): GO Outage Request List...7-2 Figure 8-1 NYISO Outage Scheduler: Generation Pending Request List...8-1 Figure 8-2 NYISO Outage Scheduler: Transmission Pending Request List...8-2 Figure 9-1 Generation Upload and Validation Flowchart 1 of 3...9-2 Figure 9-2 Generation Upload and Validation Flowchart 2 of 3...9-3 Figure 9-3 Generation Upload and Validation Flowchart 3 of 3...9-4 Figure 9-4 NYISO Outage Schedule (itoa)-go Upload...9-9 Figure 9-5 Outage Request 427.CSV... 9-10 Figure 9-6 Generation Upload Error Email... 9-11 Figure 9-7 Generation Upload Error Pop-up Message... 9-11 Figure 9-8 Outage Request 1254 to 1255.csv... 9-15 Figure 9-9 Outage Request 478.CSV... 9-16 Figure 9-10 Three Outage Requests.CSV... 9-17 Figure 9-11 Generation Upload Error Email Multiple Requests... 9-17 Figure 9-12 Generation Upload Pop-up Error Message Multiple Requests... 9-18 Figure 9-13 Generation Upload Acceptance Email... 9-19 Figure 9-14 Transmission Upload Flowchart... 9-20 Scheduling, Energy Market Operations v
Table of Tables Table 9-1 General Information Record...9-6 Table 9-2 Equipment Information Record...9-7 Table 9-3 Format Validation Errors... 9-12 Table 9-4 Syntax Validation Errors... 9-13 Table 9-5 Business Rules Validation Errors... 9-15 Table 9-6 Upload Request Data Structure... 9-21 Table 9-7 Template Header - Header Component... 9-22 Table 9-8 Template Payload Outage Record Component... 9-24 Table 9-9 Template Payload Outage Schedule Component... 9-25 Table 9-10 Template Payload Local Generation Impacted Component... 9-25 Table 9-11 List of Error Information... 9-29 vi Scheduling, Energy Market Operations
Revision History Version Date Revisions 3.0 09/13/2016 Complete rewrite for transition to itoa. 2.0 10/10/2013 Table of Tables Added tables Section 1 Removed the word Generator from Section 8 Added Section 9 Section 1.4 Replaced Customer Service with Stakeholder Services Section 2.2 Replaced Customer Service with Stakeholder Services Section 2.3 Updated Figure 2-3 Section 3.1.3 Updated all Generation screens to include the Complete Status in the Status Bar Section 4.1 Added Completed to Request States Section 5.1 Added Figure 5-2 Added the Complete Button to the list of Action Buttons Section 6.1 Updated Figure 6-2 with Complete State Section 9.1 Added captions to figures Section 9.1.1.2 Added captions to tables Updated Table 9-1 with Complete Status Section 9.1.2.4 New Added Completing a GO Outage Request Section 9.1.4.1 Added captions to figures and tables Section 9.1.4.2 Added caption to table Updated Table 9-4 with Complete Status Section 9.1.4.3 Added caption to table Updated Table 9-5 with Complete Status Section 9.1.5 Added captions to figures Scheduling, Energy Market Operations vii
Section 9.2 New - Added TO Upload information Appendix A Added Acronyms 1.2 05/06/2011 Section 1.2 Removed note stating application was not available to TOs yet. Section 2.2 Added TO roles Section 2.3 Added TO Main Menu Section 3 Replaced all Generation screens with updated screens Added TO User Interface section 3.2 Section 4 Added TO and NYISO Approved Status Conditions Section 5 Added TO and NYISO Approved Action Buttons Section 6 Added TO Outage Request Process Flow Section 7 Added TO Outage Request List Section 8 Added TO Pending Request List Section 9 New - Added Uploading Outage Requests 1.1 01/14/2010 Section 2.2 Updated link for accessing the NYISO Market Participant User's Guide secondary to NYISO Web site redesign. Section 2.3 Revised instructions and screenshots related to accessing the Outage Scheduler (itoa) System secondary to NYISO Web site redesign. Added new screenshot as Figure 2-2 to illustrate new means of accessing the Outage Scheduler (itoa) System secondary to NYISO Web site redesign, resulting in re-numbering of all subsequent figures within section 2. Section 3.3 Within the description of the Contact tab, clarified the source of default contact information (name, email, phone). 1.0 10/15/2009 Initial Release viii Scheduling, Energy Market Operations
1. INTRODUCTION This user guide is intended for Market Participants (MPs) and Transmission Owners (TOs) who are users of the NYISO Outage Scheduler (itoa) System. This user guide has been organized in the following fashion: Section 1 serves as a general introduction. Section 2 describes the hardware and software requirements to access the Outage Scheduler (itoa) System. Section 3 describes how to create an outage request using the Outage Scheduler (itoa) System. Section 4 describes the outage request status condition for the lifespan of an outage request. Section 5 describes the actions available throughout the lifespan of an outage request. Section 6 describes the process flow for an outage request lifespan. Section 7 describes the Outage Request List report. Section 8 describes the Pending Request List report. Section 9 describes the Uploading Outage Request process. 1.1 Definition of an Outage Request A generator outage request is a request by a Generation Owner (GO) to remove equipment from service that impacts a generating unit, causing a unit outage or a derate. A transmission outage request is a request by a Transmission Owner (TO) to remove a transmission facility from service for maintenance. 1.2 Description of the Outage Scheduler (itoa) System The Outage Scheduler (itoa) System is a user-friendly, secure, Web-based application. The Outage Scheduler (itoa) System includes features that support the requirements to schedule an outage request. 1.3 Outage Scheduler (itoa) System Users The community of users for the Outage Scheduler (itoa) System are NYISO Schedulers and Market Participants. 1.4 Obtaining Help and Handling Error Messages When help is required while using the Outage Scheduler (itoa) System software, please contact your Stakeholder Services Representative. Scheduling, Energy Market Operations 1-1
Error messages may appear occasionally while using this software. These messages will be displayed in a pop-up window with information about the error. After reading the message, close the window and proceed. If additional help or information is needed, please contact your Stakeholder Services Representative. 1-2 Scheduling, Energy Market Operations
2. USER REQUIREMENTS The computer requirements for the user to run the Outage Scheduler (itoa) System are described in this section. 2.1 Computer Hardware and Software The following are required to run the Outage Scheduler (itoa) System: Microsoft Internet Explorer (version 10.0 +) OR recent versions of Mozilla Firefox with Java Script enabled Minimum 1024x768 screen resolution Internet connection with a recommended connection speed of at least 56 kbps Adobe Acrobat Reader The following software is suggested: Microsoft Office 2002 (or later) 2.2 Digital Certificates and MIS Privileges All users must have a valid digital certificate installed on their respective computers and specific to their respective browsers in order to access the NYISO Outage Scheduler (itoa) System. For more information on digital certificates (including applying, exporting, obtaining installing, and validating), please see the NYISO Market Participant User's Guide, available from the NYISO Web site at the following URL: http://www.nyiso.com/public/markets_operations/documents/manuals_guides/index.jsp Existing MIS accounts need to be set-up with itoa privileges. At the organization level, this must be done by the NYISO. Once the organization is set up with the necessary privileges, the organization's MIS Administrator may then assign itoa privileges at the user level. If the MIS does not reflect the itoa GO OBSERVER, itoa GO SCHEDULER, itoa TO OBSERVER, or itoa TO SCHEDULER privileges in the Privileges area of the Organization Details display for your organization, contact the NYISO Stakeholder Services group as outlined in the section of the NYISO Market Participant User's Guide on Changing Privileges/Authorizations, Contact Information, and Classifications. 2.3 Logging in to the Outage Scheduler (itoa) System Some screenshots in this user's guide were captured after resizing the application s window. This may have caused the application to wrap within the window and appear slightly different as compared to viewing in a fully-sized browser window. Some screenshots were cropped for ease of presentation. Scheduling, Energy Market Operations 2-1
When opening a report your internet software may cause a new tab to open within the browser. In this case, the user may close the tab and will still remain logged in to the system. To log in to the Outage Scheduler (itoa) System MPs Note: In order to access the Outage Scheduler (itoa) System, the user must have itoa privileges. 1. Point your browser to the NYISO Home page at www.nyiso.com (see Figure 2-1). Figure 2-1 NYISO Home Page 2-2 Scheduling, Energy Market Operations
2. On the NYISO Home page, position your mouse over the Markets & Operations header. The header expands to list related categories of information (see Figure 2-2). Step 2 Step 3 Figure 2-2 Expanded NYISO Markets & Operations Header Highlighting Market Access Login Link 3. Under the Market & Operational Data category in the displayed list, activate the Market Access Login link (see Figure 2-2). The Market Access Login Web page is displayed (see Figure 2-3). Scheduling, Energy Market Operations 2-3
Figure 2-3 Market Access Login Web Page Highlighting User Login Link for the Outage Scheduler (itoa) System 4. Under the Outage Schedule (itoa) heading, choose User Login. The Outage Scheduler Login page is displayed (as shown in Figure 2-4, following). 2-4 Scheduling, Energy Market Operations
Figure 2-4 NYISO Outage Scheduler (itoa) Login Page 5. In the corresponding fields, type your MIS Username and Password. Note: The password is case sensitive. 6. Activate the Login button. By default following login, the Outage Scheduler Main Menu is displayed (as shown in Figure 2-5 and Figure 2-6, following). Depending on the role(s) assigned to your Username you will be presented with either a Generation Main Menu or a Transmission Main Menu. Scheduling, Energy Market Operations 2-5
Name Click dropdown arrow to change roles. Figure 2-5 NYISO Outage Scheduler (itoa) Main Menu (TO) Click dropdown arrow to change roles. Figure 2-6 NYISO Outage Scheduler (itoa) Main Menu (GO) From this menu you can access the Web forms to create a new outage request, produce a list of all outage requests, produce a list of requests having the status of Submitted or Evaluating, and upload outage requests. 2-6 Scheduling, Energy Market Operations
3. NEW OUTAGE REQUEST There are substantial differences between the Outage Request Entry pages for a generation outage request and a transmission outage request. For these reasons the requests are discussed separately. The Generation Outage Request Entry is covered in Section 3.1 and the Transmission Outage Request Entry pages are covered in Section 3.2. 3.1 New Outage Request (Generation) 3.1.1 Generation Outage Request Entry Process After accessing the New Outage Request Entry page from the Outage Scheduler Main Menu (refer to Figure 2-6, on page 2-6), the user enters information on the General tab. Next, the user can select from the following options: Save saves the outage request data. Print to File creates a PDF displaying the Generation Outage Report for that current outage request. Return closes the form and returns to the Outage Request List. Save and Return saves the outage request data for the General tab and returns to a display for further data entry including a schedule on the Schedule tab, alternate contact information can be entered on the Contact tab, and additional remarks on the Remarks tab. 3.1.2 Required Information for a Generation Outage Request The following information is required when creating a generation outage request: General Tab Request Type Chosen from a drop-down list Schedule Type Continuous, Daily (No Weekends), or Daily Description of Work 50-character alpha-numeric PTID Chosen from a list of authorized generator PTIDs Outage Type Chosen from a drop-down list Schedule Tab Start date of outage request entered as MM/DD/YYYY HH:MM, or use calendar application to choose the desired date. 3.1.3 Steps to Create a Generation Outage Request To create a generation outage request 1. Log in to the Outage Scheduler (itoa) System as outlined in Section 2.3. Scheduling, Energy Market Operations 3-1
2. Choose the New Outage Request Entry option (refer to Figure 2-6Figure 2-5, on page 2-6). The page illustrated in Figure 3-1, following, is displayed: Figure 3-1 NYISO GO Outage Request Entry Form 3. Once the general information has been completed select Save and Return (refer to Figure 3-1). The page illustrated in Figure 3-2, following, is displayed: 2 3 1 Figure 3-2 NYISO GO Outage Request Entry Form The GO Outage Request Entry pages can be accessed through the tabs in number 3 of Figure 3-2. The General tab is the What page that gathers the outage request reason, the type of outage request, the schedule type, and the equipment involved. The Schedule tab is the When page that gathers the start and end dates for each 3-2 Scheduling, Energy Market Operations
piece of equipment on the outage request. The Contact tab defines "Who" from the requesting entity needs to know when the outage request status changes or who evaluators should contact for additional information or clarification. The History tab provides a record of who, what, and when changes were made to the outage request. The Audit Trail tab provides a detailed list of each change to the request. The Remarks tab is a place to add other notes related to the job. Note: There are features that are consistent throughout the NYISO Outage Scheduler (itoa) application such as the Status Indicator (see number 1 in Figure 3-1) and the Function Bar (number 2 in Figure 3-1), which lists all of the common functions that a user should require. The state of the request may influence the functions that are allowed. 4. On each of the displayed tabs, provide and/or review all required information, using the following as a reference in doing so: Figure 3-3 NYISO GO Outage Request Entry Form - General Tab General Tab (see Figure 3-3) This form is used to enter summary information for an outage request. The user will enter information that includes request type, schedule type, emergency restoration time, description of work, comments, and each generator ID (PTID) that pertains to the outage. For each PTID selected enter the outage type, along with maximum unit output, test type, and AVR unit # (where applicable). Scheduling, Energy Market Operations 3-3
Figure 3-4 NYISO GO Outage Request Entry Form - Schedule Tab Schedule Tab (see Figure 3-4) This form is used to enter schedule information for each PTID in the outage including a start and end date for the outage request. The start of the outage request is the earliest start time for any individual component of the outage request, and the end of the request is the latest return time for any individual component of the outage request. Via the corresponding buttons, users can also Select Equipment and Apply the start and end date to each piece of equipment selected. Users can also update the start and end date by individual PTID. The start and stop times can be different between the devices. Figure 3-5 NYISO GO Outage Request Entry Form - Contact Tab Contact Tab (see Figure 3-5) This form is used to enter contact information (name, email, and phone) for notification of changes in the outage request. The primary contact is automatically displayed, based on the username of the user creating the outage request. 3-4 Scheduling, Energy Market Operations
Note: The default contact information is the contact information from the MIS User Contact, which is listed on the MIS User Details page. This form allows for the entry of alternate contact information (name, email, and phone) for the outage request. The contact information entered here will apply to only this particular outage and will not be a permanent change to contact information in MIS. More than one email address can be entered in the email box by separating each address with a comma. The email address(es) on this page will receive an email notification any time the state of the request changes. Figure 3-6 NYISO GO Outage Request Entry Form - History Tab History Tab (see Figure 3-6) This form is used to display the history of the outage request. All status changes that take place will be displayed on this form. This display lists the status changes associated with this outage request along with when and who made the change. If an outage request is modified, denied, or cancelled, the provided reason for the status will be displayed in the Detail column. Additionally, if a request is denied, the outage evaluator is required to propose an alternate start and end date for the outage request (see Section 4-1). The alternate start and end dates are displayed in the Alternate Dates columns. Note: The History page is for display purposes only. The user is not allowed to enter data on this page. Figure 3-7 NYISO GO Outage Request Entry Form - Audit Trail Tab Audit Trail (see Figure 3-7) This form is used to display a detailed list of changes to the outage request. Scheduling, Energy Market Operations 3-5
Figure 3-8 NYISO GO Outage Request Entry Form - Remarks Tab Remarks (see Figure 3-8) This form is used to include other notes pertaining to the outage request. 3.2 New Outage Request (Transmission) 3.2.1 Transmission Outage Request Entry Process After accessing the New Outage Request Entry page from the Outage Scheduler Main Menu (refer to Figure 2-5 and Figure 2-6, on page 2-6), the user enters information on the General tab and Schedule tab. Additionally, alternate contact information can be entered on the Contact tab. Next, the user can choose among the following options on the Function bar at the bottom of the screens: Save saves the outage request data. Print to File creates a PDF displaying the Transmission Outage Report for that current outage request. Return closes the form and returns to the Outage Request List. Save and Return saves the outage request data for the General tab and returns to a display for further data entry including a schedule on the Schedule tab, alternate contact information can be entered on the Contact tab, and additional remarks on the Remarks tab. 3.2.2 Required Information for a Transmission Outage Request The following information is required when creating a transmission outage request: General Tab Request Type Chosen from a drop-down list Schedule Type Continuous, Daily (No Weekends), or Daily Posted Reason Chosen from a drop-down list Description of Work 50-character alpha-numeric TO ID Chosen from a list of the TOs equipment Outage Type Chosen from a drop-down list Local Generation Impacted Yes or No (requires further information about the impacted generator(s)) 3-6 Scheduling, Energy Market Operations
Schedule Tab Start date of outage request entered as MM/DD/YYYY HH:MM, or use calendar application to choose the desired date. 3.2.3 Steps to Create a Transmission Outage Request To create an transmission outage request 1. Log in to the Outage Scheduler System as outlined in Section 2.3. 2. Choose the New Outage Request Entry option (refer to Figure 2-5 and Figure 2-6, on page 2-6). The page illustrated in Figure 3-9, following, is displayed: Scheduling, Energy Market Operations 3-7
Figure 3-9 NYISO TO Outage Request Entry Form 3. Once the general information has been completed select Save and Return (refer to Figure 3-10). The page illustrated in Figure 3-10, following, is displayed: 3-8 Scheduling, Energy Market Operations
2 3 1 Figure 3-10 NYISO TO Outage Request Entry Form The TO Outage Request Entry pages can be accessed through the tabs in number 3 of Figure 3-10. The General tab is the What page that gathers the outage request reason, the type of outage request, the schedule type, and the equipment involved. The Schedule tab is the When page that gathers the start and end dates for each piece of equipment on the outage request. The Contact tab defines "Who" from the requesting entity needs to know when the outage request status changes or who evaluators should contact for additional information or clarification. The History tab provides a record of who, what, and when changes were made to the outage request. The Audit Trail tab provides a detailed list of each change to the request. The Remarks tab is a place to add other notes related to the job. Note: There are features that are consistent throughout the NYISO Outage Scheduler (itoa) application such as the Status Indicator (see number 1 in Figure 3-10) and the Function Bar (number 2 in Figure 3-10), which lists all of the common functions that a user should require. The state of the request may influence the functions that are allowed. 4. On each of the displayed tabs, provide and/or review all required information, using the following as a reference in doing so: Scheduling, Energy Market Operations 3-9
Figure 3-11 NYISO TO Outage Request Entry Form - General Tab General Tab (see Figure 3-11) This form is used to enter summary information for an outage request. The user will enter information that includes request type, schedule type, emergency restoration time, description of work, comments, each TO ID or PTID that pertains to the outage and for each TO ID selected, and the outage type. For TOs that do not use identifier numbers (TO ID), this field will be populated with the associated NYISO PTID in its place. 3-10 Scheduling, Energy Market Operations
Figure 3-12 NYISO TO Outage Request Entry Form - Schedule Tab Schedule Tab (see Figure 3-12Error! Reference source not found.) This form is used to enter schedule information for each piece of equipment ID (TO ID or PTID) in the outage including a start and end date for the outage request. The start of the outage request is the earliest start time for any individual component of the outage request, and the end of the request is the latest return time for any individual component of the outage request. Via the corresponding buttons, users can also Select Equipment and Apply the start and end date to each piece of equipment selected. Users can also update the start and end date by individual ID. The start and stop times can be different between devices. Figure 3-13 NYISO TO Outage Request Entry Form - Contact Tab Scheduling, Energy Market Operations 3-11
Contact Tab (see Figure 3-13) This form is used to enter contact information (name, email, and phone) for notification of changes in outage request. The primary contact is automatically displayed, based on the username of the user creating the outage request. Note: The default contact information is the contact information from the MIS User Contact, which is listed on the MIS User Details page. This form allows for the entry of alternate contact information (name, email, and phone) for the outage request. The contact information entered here will apply to only this particular outage and will not be a permanent change to contact information in MIS. More than one email address can be entered in the email box by separating each address with a comma. The email address(es) on this page will receive an email notification any time the request state changes. Figure 3-14 NYISO TO Outage Request Entry Form - History Tab History Tab (see Figure 3-14) This form is used to display the history of the outage request. All status changes that take place will be displayed on this form. This display lists the status changes associated with this outage request along with when and who made the change. If an outage request is modified, denied, or cancelled, the reason for the status will be displayed in the Detail column. Additionally, if a request is denied, the outage evaluator is required to propose an alternate start and end date for the outage request (see Section 4.1). The alternate start and end dates are displayed in the Alternate Dates columns. The exception column is checked if the user is requesting an outage that is not within the normal notification lead-time for that device. Note: The History page is for display purposes only. The user is not allowed to enter data on this page. 3-12 Scheduling, Energy Market Operations
Figure 3-15 NYISO TO Outage Request Entry Form - Audit Trail Tab Audit Trail (see Figure 3-15) This form is used to display a detailed list of changes to the outage request Figure 3-16 NYISO TO Outage Request Entry Form - Remarks Tab Remarks (see Figure 3-16) This form is used to include other notes pertaining to the outage request. Scheduling, Energy Market Operations 3-13
This page intentionally blank. 3-14 Scheduling, Energy Market Operations
4. OUTAGE REQUEST STATUS CONDITIONS 4.1 Request States Nine different states may be associated with an outage request throughout its lifespan, as outlined below: TO or GO Created Request information as entered has been saved and stored in the Outage Scheduler (itoa) database(s). The outage request has not been sent to the NYISO and TO evaluators. Submitted to NYISO The request has been submitted to NYISO/TO for evaluation, but the evaluators (NYISO/TO) have not yet started the evaluation process. Evaluating The NYISO/TO evaluators have begun evaluating the outage request. TO Approved The TO evaluators have reviewed the outage request and agreed that the request can occur on the date/time specified for the outage request. In the case of a generation request, the TO is the local TO where the generator is located. In the case of a transmission request, the TO would be a switching authority. NYISO Approved The NYISO evaluators have reviewed the outage request and agreed that the request can occur on the date/time specified for the outage request. Approved Both the NYISO and the TO evaluators have reviewed the outage request and have agreed that the request can occur on the date/time specified for the outage request. Denied The NYISO/TO evaluators have reviewed the outage request and have determined that it cannot reliably occur. The evaluator will provide a reason for the denial and alternate dates when the outage can be accommodated. The history page will detail who denied the request. Modified A request that was previously evaluated, either approved or denied, is being edited. The user who is modifying the request is required to enter a reason for the modification. Scheduling, Energy Market Operations 4-1
Cancelled The submitter has decided to withdraw the outage request anytime after the outage was submitted for evaluation. To have the request for cancellation recognized, the user who cancels the request is required to enter a reason for the cancellation. The outage request information remains in the Outage Scheduler (itoa) database(s) and can be displayed. Note: A cancellation is non-reversible. Completed This status is only available for generation outage requests. For a currently ongoing and approved request, the user can accurately reflect the early completion of the outage request. The user who is completing the request is required to enter the time and date of job completion. The history page will detail the job completion information. Note: A completion is non-reversible. 4-2 Scheduling, Energy Market Operations
5. ACTIONS 5.1 Actions Action button is used to move an outage request between the various states. Allowable actions depend on the current state of the outage request and the role of the user. If the user is associated with a TO, they will have the ability to Delete, Submit, Modify, Cancel, TO Approve and TO Deny. If the user is associated with a GO, they will have the ability to Delete, Submit, Modify, Cancel, and Complete. Delete Button The Delete action button is used by a user to remove all information associated with a particular outage request. Note: The Delete action is allowed only until the outage request has been submitted for evaluation. THIS ACTION CANNOT BE REVERSED. Submit Button The Submit action button changes the outage request state from Created to Submitted. This action is used when the author of the outage request is satisfied with the outage request and wants the outage request to be evaluated by the NYISO and/or TO. Modify Button The Modify action button is used to edit an outage request that is in the Approved or Denied state. The user is required to enter a reason for the modification before being allowed to save the outage request changes. TO Approve Button The TO Approve action button is used by a Transmission Owner to approve a generator outage request for a generator that is located within the TO's service territory. It is also used by a TO to approve a transmission outage request for which the TO is the owner or the switching authority. A GO user will not see this button. TO Deny Button The TO Deny action button is used by a Transmission Owner to deny a generator outage request for a generator that is located within the TO's service territory. It is also used by a TO to deny a transmission outage request for which the TO is the owner or switching authority. A GO user will not see this button. Scheduling, Energy Market Operations 5-1
Cancel Button The Cancel action button can be used by a user to cancel an outage request anytime after the outage request is in a Submitted state. The user is required to enter a reason for the cancellation before being allowed to save the cancellation. Note: The information for a cancelled outage request remains in the Outage Scheduler (itoa) database(s) and can be displayed. THIS ACTION CANNOT BE REVERSED. Complete Button The Complete action button is used by a Generation Owner to complete an outage request which has completion date earlier than its originally Scheduled End Date. This can only be done in the Approved state of an ongoing outage request. The user is required to enter the Job Completion Date and Time before being allowed to save the completion. There is also an Auto Complete function for Generation requests. This is an automatic job completion function which runs daily, at a pre-determined time, and marks all Generation requests with an Approved status and a Scheduled End Date in the past to a status of Complete. Please note that Complete Status emails will not be sent for outage requests that have been set to Complete via this automatic process. Note: The information for a completed outage request remains in the Outage Scheduler (itoa) database(s) and can be displayed. THIS ACTION CANNOT BE REVERSED. Below is a table of the Available actions for a TO: Request Status Conditions Available Action TO/GO Created if requestor is Owner or SA Submit Delete Submitted if requestor is Owner or SA Cancel Modfied by TO if requestor is Owner or SA Submit Modfied by ISO if requestor is Owner or SA Cancel if requestor is Owner or SA and Evaluating request not yet approved by TO Cancel Deny Approve Evaluating if requestor is Owner or SA Cancel Deny Evaluating if requestor is not Owner or SA Cancel Evaluating if not requestor but is Owner or SA and not yet approved by TO Deny Approve Evaluating if requestor is Owner or SA Deny Approved by ISO if requester is Owner or SA Cancel Modify Deny Approved by ISO If not requestor but is Owner or SA Deny Approved by ISO Y but (nor owner nor SA) Cancel Modify Denied by ISO if requestor is a SA Cancel Modify 5-2 Scheduling, Energy Market Operations
6. PROCESS FLOW 6.1 Outage Request Process Flow (GO User) Figure 6-1 shows the first half of the process flow diagram, illustrating the actions required to move an outage request from No Status to Created to Submitted to Evaluating. Figure 6-2 shows the second half of the outage request lifecycle, illustrating the movement of an outage request from Evaluating to Approved or Denied or Modified or Canceled or Completed. Outage Request Process Flow Created, Submitted & Evaluated No Status CREATED SUBMITTED EVALUATING GO enters the minimum required information for an outage request Save the request? N GO selects the RETURN button or DELETE Action GO selects the SAVE button Y N Application executes the following actions: - saves the info - assign outage ID - records Created By and Date Created - chg status to CREATED Request ready for NYISO/TO evaluation? GO selects the SUBMIT button Y Application executes the following actions: - chg status to SUBMITTED -send email to interested parties NYISO Scheduler begins evaluation of GO request TO Scheduler begins evaluation of GO request TO provides feedback to NYISO Scheduling Staff - APPROVES - DENY w/ reason and alternate date Application executes the following actions: - chg status to EVALUATING - send email to interested parties APPROVES request Y A Application deletes the information entered GO Edits or Deletes request R DELETED N GO CANCELS request D C Figure 6-1 GO Outage Request Process Flow Diagram - 1 of 2 Scheduling, Energy Market Operations 6-3
Figure 6-2 GO Outage Request Process Flow Diagram - 2 of 2 6-4 Scheduling, Energy Market Operations
6.2 Outage Request Process Flow (TO User) Figure 6-3 shows the first half of the process flow diagram, illustrating the actions required to move an outage request from No Status to Created to Submitted to Evaluating. Figure 6-4 shows the second half of the outage request lifecycle, illustrating the movement of an outage request from Evaluating to Approved or Denied or Modified or Canceled. Outage Request Process Flow Created, Submitted & Evaluated No Status CREATED SUBMITTED EVALUATING TO enters the minimum required information for an outage request Save the request? N TO selects the RETURN button or DELETE Action TO selects the SAVE button Y N Application executes the following actions: - saves the info - assign outage ID - records Created By and Date Created - chg status to CREATED Request ready for NYISO/SA evaluation? TO selects the SUBMIT button Y Application executes the following actions: - chg status to SUBMITTED -send email to interested parties NYISO Scheduler begins evaluation of TO request SA Scheduler begins evaluation of TO request SA provides feedback to NYISO Scheduling Staff - APPROVES - DENY w/ reason and alternate date Application executes the following actions: - chg status to EVALUATING - send email to interested parties APPROVES request Y A Application deletes the information entered TO Edits or Deletes request R DELETED N TO CANCELS request D C Figure 6-3 TO Outage Request Process Flow Diagram - 1 of 2 Scheduling, Energy Market Operations 6-5
Outage Request Process Flow Approved, Denied, Canceled States Previous page APPROVED DENIED CANCELED A NYISO Scheduler selects the APPROVE action Application executed the following actions: - Chg status to APPROVED - Email notification sent to interested parties D APPROVED NYISO Scheduler selects the DENY action, includes a reason and alternate date. Application executed the following actions: - Chg status to DENIED - Email notification sent to interested parties DENIED R (On pg 1) If the proposed alt date is acceptable to the TO, the TO modifies the request and resubmits CANCELED C TO CANCELS request TO CANCELS request TO selects the CANCEL action, includes a reason. Application executed the following actions: - Chg status to CANCELED - Email notification sent to interested parties Figure 6-4 TO Outage Request Process Flow Diagram - 2 of 2 6-6 Scheduling, Energy Market Operations
7. OUTAGE REQUEST LIST The Outage Request List Main Menu option (refer to Figure 2-5 and Figure 2-6 on page 2-6) provides the user with a list of all outage requests the user is allowed to view. In the case of a TO user, the TO Outage Request List will look like Figure 7-1, following. Figure 7-1 NYISO Outage Scheduler (itoa): TO Outage Request List Scheduling, Energy Market Operations 7-1
In the case of a GO user the GO Outage Request List will look like Figure 7-2, following: Clear Filter Filter Figure 7-2 NYISO Outage Scheduler (itoa): GO Outage Request List The Reference ID is automatically assigned to the outage request when the request is first saved. The Revision Number is automatically incremented anytime the outage is put into Modified status. The remainder of the information in this report is either information that was entered by the user or the state of each outage request. The buttons listed below are used to manipulate the individual rows on this display. Purposes of these buttons are as follows: View To view a request either click on the Ref. ID or double click on the row desired. 7-2 Scheduling, Energy Market Operations
Clear Filters Erases any previous queries and returns the display to the original state. Filter Allows the user to enter information that will be used to search the Outage Scheduler (itoa) database(s) for entries. Filter is available for all fields. User may also select options from the area shown above the Outage Request List in Figure 7-1 and Figure 7-2. Export Exports the data from the list into either a PDF or CSV file. New Request Takes the user to the Outage Request Entry page. Scheduling, Energy Market Operations 7-3
This page intentionally blank. 7-4 Scheduling, Energy Market Operations
8. PENDING REQUEST LIST The Pending Request List Main Menu option (refer to Figure 2-5 and Figure 2-6 on page 2-6) displays the outage request information for equipment authorized for the user and having a status of Submitted or Evaluating only (see Figure 8-1, following). Figure 8-1 NYISO Outage Scheduler: Generation Pending Request List Note: The buttons displayed on this form have the same functionality as discussed in Section 7. Scheduling, Energy Market Operations 8-1
The Transmission Pending Request List Main Menu option (refer to Figure 2-6 on page 2-6) displays the outage request information for equipment authorized for the user and having a status of Submitted or Evaluating (see Figure 8-2, following). This screen is available to TO users only. Figure 8-2 NYISO Outage Scheduler: Transmission Pending Request List 8-2 Scheduling, Energy Market Operations
9. UPLOADING OUTAGE REQUESTS This section handles uploading a generation outage request via a CSV file and uploading a transmission outage request via a XML file. The generation outage upload process is covered in section 9.1 and the transmission outage upload process is covered in section 9.2. 9.1 Generation Upload Introduction Section 9 describes an interactive method for entering data into the NYISO itoa Outage Scheduler. The method is based on interactive Web Browser technology. This section describes the equivalent functionality using an application user interface developed by the Generator Owner. This method requires that all information is prepackaged into files which are then sent to the NYISO Outage Scheduler. This interface is provided for quick and efficient transfer of large amounts of data between Generator Owners and NYISO. The NYISO Outage Scheduling application (itoa) has a facility for the uploading of generation outage requests as a comma separated values (.CSV) file. At the present time this facility is not available for transmission outages. The upload process is initiated via an "Upload Generator Outage Requests" selection on the GO Main Menu. The.CSV file may contain just a single outage request, or multiple outage requests. CSV File The data that is prepared by the Market Participant is a text file consisting of multiple records, each one with one or more comma separated value fields. This type of file is known as common separated value, or CSV. Templates Each type of data is described as a template. Data submission and the corresponding responses are described. Responses to uploads are automatic. The Market Participant does not have to query the Outage Scheduler to get information as to the status of a data upload. The following flowcharts describe the upload process and the three levels of validation that are performed on the uploaded file. The upload and validation process is very similar to the existing generator bid upload process. Scheduling, Energy Market Operations 9-1
GO creates a csv file of Outage Requests (saved to the GO users local drive or network drive). GO logs onto the TOA Application and selects Upload Generator Outage Requests from TOA Main Menu. GO selects csv file from local or network drive and presses Upload to NYISO button. CSV file will be uploaded to TOA Application Server in a pre-determined folder. Format Validation Process Error YES GO will receive FILE REJECTED email with Summary Report. Mailbox Store NO NO EOF YES A Figure 9-1 Generation Upload and Validation Flowchart 1 of 3 9-2 Scheduling, Energy Market Operations
A Syntax Validation Process Error YES Record Syntax Error NO EOF YES Syntax Errors Found YES GO will receive FILE REJECTED email with Summary Report. Mailbox Store NO NO B Figure 9-2 Generation Upload and Validation Flowchart 2 of 3 Scheduling, Energy Market Operations 9-3
B Business Validation Process Error YES NO Re-Submitted Outage Request YES NO Outage Request will be inserted into the appropriate TOA tables and submitted. TOA Record Disregard Message GO will receive FILE REJECTED email with Summary Report. Mailbox Store EOF YES GO will receive FILE ACCEPTED email with Summary Report. Mailbox Store NO Figure 9-3 Generation Upload and Validation Flowchart 3 of 3 9-4 Scheduling, Energy Market Operations
9.1.1 Overview of the Upload Templates The upload request templates have a header and body. 9.1.1.1 Template Header The header of the upload request is delimited by ampersands (&) that separate the various records of the header. All upload requests require a four-record header as follows: 1. SUBMISSION_TYPE Indicates the type of outage request that is being supplied 2. USER ID To log on to MIS and itoa 3. PASSWORD To log on to MIS and itoa 4. DATA ROWS The number of records that follow Valid SUBMISSION_TYPE values are: GENERATION Submit Generator Outage Request TRANSMISSION Submit Transmission Outage Request (not valid at this time) A value for USER ID and PASSWORD are not required if the user is logged in to the itoa application and has selected the "Upload Outage Request" on the Generation Owner Main Menu. If no USER ID and PASSWORD are entered then an '&' needs to be in those fields. If the user is logged in to the itoa application and the USER ID and PASSWORD are also provided on the header record, then they must match. If they do not, the file will be rejected. A USER ID and PASSWORD will be required for other applications outside of the NYISO itoa Outage Scheduler submitting Outage Requests. Sample Header Record: 9.1.1.2 Template Body (Generation) The Body of a Generation Outage Request can contain up to two components for each outage request. To identify the two components of an outage request, the upload.csv file will contain a record type indicator to identify the component. The two components are: General Information Record The General record has an 'Action' data field (Submit, Modify, Cancel, and Complete) to describe the purpose of the record. Scheduling, Energy Market Operations 9-5
Table 9-1 General Information Record 9-6 Scheduling, Energy Market Operations
Equipment Information Record The Equipment record describes what individual pieces of equipment are being affected by the outage request and how. Note: Items in Bold are required. Note: Request Type, Schedule Type, Emergency Restoration Time Label, Equipment Outage Type, and Test Type values are presented with drop-down menu values in itoa. These text values have an associated numeric lookup_code_id assigned in itoa. The descriptions above provide the numeric lookup_code_id and the associated text value. The GO Upload..CSV file will require the use of the numeric lookup_code_id. Table 9-2 Equipment Information Record Scheduling, Energy Market Operations 9-7
9.1.2 Addition Upload Rules and Requirements The GO Upload.CSV file can contain multiple Outage Requests. Each new request will contain a General record and an Equipment record. itoa will identify a new request when a General record type is encountered in the file. 9.1.2.1 Submitting a new GO Outage Request The submission of a new Outage Request will require the following record types: one General record with an Outage Action = Submit, and a blank itoa Outage Id, a minimum of one or more Equipment records(s) 9.1.2.2 Modifying a GO Outage Request The modification to an Outage Request must contain either the itoa Outage Id or the GO Outage Id. The GO Outage Id field will need to be populated on the previously submitted Outage Request either by submitting it on the initial GO Upload.CSV file or entering it later via the itoa web based screen. If the itoa Outage Id is supplied it will be used to locate the correct Outage Request. Otherwise, the correct Outage Request record will be selected using the GO Outage Id. `The required components for a Modify are: One General record with an Outage Action = MODIFY and either the GO Outage Id or itoa Outage Id, Schedule Type and Reason fields populated. In addition, all of the Equipment records in the Outage Request will be required. These equipment record(s) can consist of existing equipment record(s) that are not being modified, equipment record(s) that are being modified, or equipment record(s) that are being added. All of the Equipment records are required because; a MODIFY request will trigger the itoa application to delete all existing pieces of equipment in the referenced outage request from the itoa database, and add all the Equipment record(s) on the MODIFY.CSV file. Any Outage Requests that previously had been part of an upload that contained multiple requests that do not have any changes do not have to be included as a modification upload. Only Outage Requests that are being modified have to be included. 9.1.2.3 Cancelling a GO Outage Request The cancellation of an Outage Request will require the following records: A General record with an Outage Action = Cancel, either the GO Outage Id or itoa Outage Id and Reason fields populated. If the itoa Outage Id is supplied it will be used to locate the correct outage request. If the itoa Outage Id is not supplied, the correct record will be selected using the GO Outage Id. 9-8 Scheduling, Energy Market Operations
9.1.2.4 Completing a GO Outage Request The completion of an Outage Request will require the following records: A general record with an Outage Action = Complete, either the GO Outage Id or itoa Outage Id and the new Actual End Date fields populated. If the itoa Outage Id is supplied it will be used to locate the correct Outage Request. If the itoa Outage Id is not supplied, the correct record will be selected using the GO Outage Id. The list of all Outage Requests will first be filtered so that only Outage Requests that the submitting User has access to will be searched for the matching GO Outage Id. This pre-filtering mitigates the possibility of a GO Organization accessing another GO Organization s identical GO Outage Id. The Outage Request must be in the Approved state in order for a Complete action to be performed. 9.1.3 Upload Process Using the Upload batch interface requires selecting "Upload Generator Outage Requests" from the GO Main Menu (see Figure 2-5). Figure 9-4 NYISO Outage Schedule (itoa)-go Upload The user then selects a file from their local disk by typing a file name or using the (file) Browse button available with Netscape 7.x and MS Explorer 6.x, or equivalent. When the user clicks on the "Upload to NYISO" button, the input file is sent to the Web Server, where it is received by the itoa Outage Scheduler application. The itoa application processes the.csv file and provides on-screen validation results and also emails these same results to the logged-in user's email address. 9.1.4 CSV Validation As described in the flowchart in Section 9.1, there are three levels of validation of the.csv file. The three levels of validation are Format, Syntax, and Business Rules. Scheduling, Energy Market Operations 9-9
9.1.4.1 Format Validation The Format Validation pass initially checks for errors or missing information in the header records. If an error is detected, the file is rejected and an email is sent to the address of the submitter as determined by the UserID that the submitter logged into itoa under. The email Subject line will contain the file name of the.csv file and whether the file was accepted or rejected. The body of the message will describe the error that was encountered. The information in the email body will also be displayed in a pop-up message on the GO Upload Outage Request screen if the upload is being performed using the "Upload Generator Outage Requests" button on the GO Main Menu. If the header Submission Type and the number of data rows are correct, the Format Validation checking can continue to verify that the data rows contain valid record types (General and Equipment) and that the following relationships exist: A General record must be the first record in an Outage Request. The General record must be followed by one or more Equipment records. In Figure 9.2, Outage Request 427.CSV will be rejected by the Format Validation pass as the header record says that there are six data rows and there are actually only five rows. Figure 9-5 Outage Request 427.CSV The following is an example of the email message that is generated and sent to the requester of Outage Request 427.CSV (Figure 9-2) upon detecting the error in the Format Validation process. The file header says that there are six data rows when in fact there are only five. 9-10 Scheduling, Energy Market Operations
Figure 9-6 Generation Upload Error Email Below is the pop-up message that will be displayed back to the user if they remain logged in the itoa application. Figure 9-7 Generation Upload Error Pop-up Message Scheduling, Energy Market Operations 9-11
The following table lists all of the Format Validation errors. Format Validation Errors Invalid Submission Type in Header. Submission Type must be GENERATION or TRANSMISSION Invalid Submission Type for Requesters Role. UserID logged on to itoa does NOT match USERID and PASSWORD on Header record. Invalid Number of Rows in File Invalid Record Type. Values include GENERAL and EQUIPMENT. Invalid Outage Request Invalid SUBMIT Request If data value submitted on.csv file is not GENERATION or TRANSMISSON file is in error. NOTE: TRANSMISSION choice is not yet available. If the Requester is logged in as a Generator Owner they cannot submit a Transmission Outage and vice-versa. If user is logged on the itoa application and the data value submitted on the Header Record for USERID and PASSWORD does not match to the logged in userid and password file is in error. If number of rows submitted in.csv file is not equal to value submitted on Header Record file is in error. If Record Type submitted on.csv file is not GENERAL or EQUIPMENT field is in error. If the.csv file contains an Equipment record and does not contain a General record the file is in error. If the.csv file contains a General record with an Outage Action = Submit and does not have at least one Equipment record the file is in error. Table 9-3 Format Validation Errors 9.1.4.2 Syntax Validation The second validation performed is a syntax check. This will encompass validating that the correct component records are present for each individual outage request in the CSV file. Additionally, data item values that will be used as a lookup code on an itoa table will be validated. If a Syntax validation error(s) is encountered, the entire upload.csv file will be rejected after the entire file is processed. An email will be sent by itoa describing all errors. The Syntax errors will also be displayed on the itoa screen if the upload is being performed using the "Upload Generator Outage Requests" button on the GO Main Menu. Syntax Validation Errors Invalid Format - field name must be a numeric value. Invalid field name. Value can not be greater than 999. Missing Required Data data field name If data value submitted on.csv file is not numeric field is in error. If data format definition is NUMBER (03), and data value submitted on. CSV file is >999 field is in error. If any of the data items do not have a value submitted on the. CSV file the file is in error. These are required fields. Outage Action Request Type Schedule Type Description of Work PTID Outage Type 9-12 Scheduling, Energy Market Operations
Syntax Validation Errors Required GO or itoa Outage Id is missing. Invalid itoa Outage Id. Invalid itoa Outage Id for User. Invalid Outage Action. Values include SUBMIT, MODIFY, CANCEL, COMPLETE. Invalid Outage Request Type. Invalid Schedule Type. Invalid Equipment Outage Type. Invalid Test Type. Invalid Emergency Restoration Time Label. Invalid field name. Text must be enclosed in. Invalid Format for date. Correct format is mm/dd/yyyy hh:mm. Invalid Month: value Invalid Day: value. Invalid Hour: value. Invalid Minute: value. Schedule Start Date If Outage Action = MODIFY, CANCEL or COMPLETE, either the GO Outage Id or the itoa Outage ID is required. If Outage Action = SUBMIT and itoa Outage Id is populated file is in error. If user submitting an Outage Action = MODIFY, CANCEL, or COMPLETE is not authorized to access the referenced itoa Outage Id - file is in error. If Outage Action submitted on.csv file is not SUBMIT, MODIFY, CANCEL, or COMPLETE field is in error. Outage Request Type submitted on.csv file is not found in itoa tables. Schedule Type submitted on.csv file is not found in itoa tables. Equipment Outage Type submitted on.csv file is not found in itoa tables. Test Type submitted on.csv file is not found on itoa tables. Data value submitted on.csv file is not found in itoa tables. Data value submitted on.csv file for Description of Work, Reason or Comments is not enclosed in. Data value is not submitted in correct format field is in error. Data value submitted on.csv file is in error. Data value submitted on.csv file is in error. Data value submitted on.csv file is in error. Data value submitted on.csv file is in error. Table 9-4 Syntax Validation Errors 9.1.4.3 Business Rules Validation The final validation performed is on applicable business rules. In the Business validation process, each record within the entire outage request (General record and all Equipment records) must pass the validation rules for the outage request to be submitted. If a Business validation error is encountered, the remainder of the CSV file will be rejected and email will be sent by itoa describing the error. If one or more earlier occurring outage requests in the file have processed successfully, these will result in a successfully submitted outage request(s). If a subsequent error is encountered, processing will stop and the remainder of the CSV file will be rejected. Any outage requests that were successfully processed before the error was encountered remain in the SUBMIT state. Business Rules Validation Errors Invalid PTID value. User is not authorized to schedule the referenced PTID. If user is not authorized to schedule against the referenced PTID submitted on the Outage Request field is in error. Scheduling, Energy Market Operations 9-13
Business Rules Validation Errors WARNING: Invalid Max Unit Output. Max Unit Output cannot be greater than DMNC value value MW. Invalid AVR unit value for Request Type. Invalid Date Range. Scheduled End Date/Time must be equal to or later than Scheduled Start Date/Time. Invalid Date Range. For COMPLETE the End Date/Time must be equal to or later than Scheduled Start Date/Time. WARNING: Overlapping Outage Request with itoa Outage Id XX-XXXX (toa_app_data.app_num) MODIFY Action failed. itoa was unable to find a match on GO Outage Id or the itoa Outage Id CANCEL Action failed. itoa was unable to find a match on GO Outage Id or the itoa Outage Id COMPLETE Action failed. TOA was unable to find a match on GO Outage Id or the itoa Outage Id A Reason is required for a MODIFY or a CANCEL Outage Action A Schedule End Date is required for a COMPLETE Outage Action Invalid Date Range. For COMPLETE the Schedule End Date/Time must be less than or equal to current Date/Time. A duplicate of the Outage Request (itoa Outage Id) was found, but re-submission disregarded. A duplicate of the Outage Request (itoa Outage Id) was found, but the record was not available for MODIFY action. The COMPLETE Outage Action has been rejected. The Outage Request is not in an Approved state. Outage Request (itoa Outage Id) was previously cancelled or completed. Outage Request (itoa Outage Id) has been successfully submitted. Outage Request (itoa Outage Id) has been successfully modified. Outage Request (itoa Outage Id) has been successfully canceled. If data value submitted on.csv file is greater than the DMNC value in the itoa table GEN_DMNC field is in error. This error will trigger a warning message in the email reply, but the file will still process. If data value submitted on.csv file is greater than zero, and Request Type NOT = Forced AVR/VSS Outage OR Scheduled AVR/VSS Outage field is in error. If Scheduled End Date is less than Scheduled Start Date field is in error. If End Date is less than Scheduled Start Date field is in error. Overlapping outages are defined as two or more outages that have the same PTID and the Schedule Start/End Dates overlap with each other. This error will trigger a warning message in the email reply, but the file will continue processing. The.CSV file contains a General record with an Outage Action = MODIFY and a record cannot be found that matches GO Outage Id or the itoa Outage Id The.CSV file contains a General record with an Outage Action = CANCEL and a record cannot be found that matches GO Outage Id or the itoa Outage Id If the.csv file contains a General record with an Outage Action = COMPLETE and a record is not found that matches GO Outage Id or the itoa Outage Id If the Outage Action is either a MODIFY or a CANCEL, then the Reason field must be filled in and enclosed in quotes. If the Outage Action is COMPLETE, then the Schedule End Date field must be filled in with a valid date. If Schedule End Date is greater than current date/time field is in error. If a duplicate Outage Request is found, the original is retained, and the re-submission is disregarded. A MODIFY action is encountered, but the target Outage Request of the modification is not in either the APPROVE or DENY state, so the MODIFY is disregarded. If a COMPLETE action is encountered, but the target Outage Request is not in the APPROVE state, the COMPLETE is disregarded. A CANCEL action is encountered, but the target Outage Request is already in a cancelled state, so the CANCEL is disregarded. A SUBMIT action Outage Request is error free and processed to completion. The record is written to the itoa database with a state of Submitted A MODIFY action Outage Request is error free and processed to completion. The record is written to the itoa database with a state of Modified A CANCEL action Outage Request is error free and processed to completion. The record is written to the itoa database with a state of Cancelled 9-14 Scheduling, Energy Market Operations
Business Rules Validation Errors Outage Request (itoa Outage Id) has been successfully completed. If a COMPLETE action on Outage Request is error free and processed to completion, it is written to the itoa database with a state of Complete Table 9-5 Business Rules Validation Errors 9.1.5 Upload Examples and Validation Messaging Once a.csv file is uploaded it can be immediately processed and validated. Each Outage Request record in the.csv file can be sequentially processed and submitted. Examples of the process are given below using the following upload.csv files as examples of submitted input. Figure 9-8 Outage Request 1254 to 1255.csv This file, Outage Requests 1254 to 1255.CSV has two separate Outage Requests. The first is for a single generator outage, but has three errors in the file. The first error, in the General record, is the lack of a Schedule Type, which is a required field. This error should be caught in the syntax validation check. The second error is the Equipment record has the Equipment Outage Type as a text Out of Service rather than the required numeric code of 843. The third error is that the schedule end date of the outage occurs before the schedule start date. This error would be caught in the Business Rules validation pass. The second Outage Request in this.csv file (rows 3 to 5) is for generator testing on two separate units. Since both units will be performing the same test, they can share a General record. Each unit has its own Equipment record. There are no errors in this request. Scheduling, Energy Market Operations 9-15
Figure 9-9 Outage Request 478.CSV In this example, Outage Request 478.CSV has a generator that will be performing NOX Testing (Code 878) on three consecutive days but for different time periods each day. The Outage Request has one general record, and three equipment records. The equipment records are all for the same PTID, but each is for a different day. There are no errors in the request. In this example, a.csv file is submitted that contains three outage requests, but there are Business Rule errors in the second and third requests, but the first outage request in the file will be successfully submitted. The Business Rule error in the second outage request is a warning message only, so processing will continue. Processing will stop when the Business Rule error is encountered in the third outage request. In the example below, the second outage request has a Max Unit Output value of 1000 that is well above the units DMNC value. The third Outage Request has an error in a PTID (13758, instead of 23758) resulting in a PTID that the requester is not authorized to schedule against. 9-16 Scheduling, Energy Market Operations