Member Impacting Overview Page 1 of 7
Table of Contents PR20090027 - Outage Scheduler Table of Contents... 2 Version Control... 2 Document Purpose... 2 Executive Summary... 3 Business Impact... 3 Technical Impact... 3 Member Requirements... 3 Implementation/Back-out Plan... 4 Summary of Timeline... 5 Assumptions... 5 Risks... 6 Additional Documentation... 6 Communication Plan... 6 Next Steps... 6 FAQs... 7 Version Control Version Date Author Change Description 1.0 6/7/2011 Gina Pierson Initial Draft 1.1 6/15/2011 Gina Pierson Updated Testing and Timeline sections to reflect revised approach/dates for connectivity testing and user login setup 1.2 6/21/2011 Ramy-Claude James Document Purpose Updated based on feedback and action items gathered during MIPO Deep Dive This template should be used to provide initial and ongoing communication of member impacting projects to the CWG and membership. The Manager should provide the MIPO with an initial review period. The CWG Representative should review the MIPO and provide feedback and response, including request for a MIPO review meeting, during the comment period. All MIPO updates will be red-lined, and that version will be saved as MIPO_<PR#_NAME_V#.R#> where V# is the version number associated with the touch point, and R# is the release within that touchpoint. The latest version will have accepted redline from the previous version, and any new changes redlined. The CWG and/or project liaison will be notified of any MIPO change. Page 2 of 7
Executive Summary PR20090027 - Outage Scheduler The Outage Scheduler System will replace the OPS1 Gen, GenOutage, Tran, and TransOutage applications as the system that members interface with to submit and modify outages. In addition, SPP staff will also use the Outage Scheduler System to coordinate, approve, and distribute outage information. The new system will allow for the necessary compliance reporting and functionality improvements necessary to process the outages for SPP's expanding footprint. The Outage Scheduler System is currently in out-of-the-box configuration. A Beta Testing period will be utilized in order to allow members to comment on functionality. Should system gaps or needed changes be identified during the Beta Testing period, SPP will work with members to revise the release schedule for adjustments as needed. Business Impact Users Impacted OPS1 Gen, GenOutage, Tran, and TransOutage application users. Users who submit, modify, or view outages. Business Functions Impacted All outage related business functions, including submission, modification, and viewing of outages. Technical Impact SPP Systems/Processes Impacted The Outage Scheduler System will replace the OPS1 Gen, GenOutage, Tran, and TransOutage applications and the corresponding Generator and Transmission Outage FTP data submissions as the system that SPP staff uses to coordinate, approve, and distribute outage information. Anticipated Member Systems/Processes Impacted The Outage Scheduler System will replace the OPS1 Gen, GenOutage, Tran, and TransOutage applications via a new GUI as the system that members interface with to submit and modify outages.. A new API for outage submission and modification will be available for development post-cutover. All functionality will remain available in the GUI, and use of the API is not mandatory. Member Requirements In production, members will be required to utilize a digital certificate to access the web-based GUI. The web-based GUI will be available within a secured environment; the URL will be visible only to users of the SPP Outage Scheduler System. API development support will be available post-cutover.. Page 3 of 7
Testing Member testing will include beta testing, structured CROW GUI testing, unstructured CROW GUI testing, API testing, connectivity testing, and parallel operations: Beta testing will consist of a subset of members performing unstructured testing of the CROW GUI in order to identify any gaps or defects. Beta testing is tentatively scheduled from June 20, 2011 through July 8, 2011. SPP staff will contact those members designated as beta testers. Structured CROW GUI testing will allow members to test the CROW GUI using scripts provided by SPP detailing the required actions and the parameters of the test. Structured CROW GUI testing is tentatively scheduled from July 11, 2011 through July 29, 2011. Test Scripts will be provided to members prior to July 11, and a Member Testing Kick-Off will be conducted on July 7, 2011. o Starting on July 5, SPP staff requests that members provide their user access form to CROWtesting@spp.org, which will initiate user access setup. Members will be notified via email when user access setup is complete. For any access related questions, please contact Derek Hawkins (dhawkins@spp.org, 501-688-1662) or Neil Robertson (nrobertson@spp.org, 501-614-3322). Member testing of the API has been postponed until post-cutover, a detailed timeline will be provided at a later date. As an initial step leading into parallel operations in the production environment, connectivity testing will be performed to validate that members can access CROW within the secured environment. SPP Staff will coordinate connectivity testing with the members. Connectivity testing is tentatively scheduled for August 25, 2011 through August 29, 2011. Parallel operations is designed to mimic production, with the continuous submittal/updates of realistic outage data. Parallel operations is tentatively scheduled from August 30, 2011 through September 12, 2011. To allow time for updating the tool and/or database in the Integration Test Environment (ITE), each Tuesday will be set aside as scheduled downtime during which no member testing will occur. Please note that additional details around testing will be provided in the Member Test Plan and during the Member Testing Kickoff Meeting. Training Member training will be required. Live training demonstrations will be provided to both the ORWG and CWG. A recorded demonstration will be made available to all members. SPP staff will provide members with training materials for the CROW GUI by July 1, 2011. Implementation/Back-out Plan <To be Developed> Page 4 of 7
Summary of Timeline Date Responsible Party Action June July 2011 Team Development of SPP interfaces and CROW application enhancements June 7, 2011 Team Publish Member Impacting Overview (MIPO) June 17, 2011 Conduct MIPO Deep Dive June 20 July 8, 2011 Member Beta Testing; SPP staff will contact those members designated as beta testers June 24, 2011 Team Provide members with test scripts for structured CROW GUI testing July 1, 2011 Team Provide members with training materials for CROW GUI. July 5 July 8, 2011 July 7, 2011 User Login Setup for structured CROW GUI testing Member Testing Kick-Off July 11 July 29, 2011 Member Structured CROW GUI Testing August 1 August 15, 2011 Member Optional Unstructured CROW GUI Testing August 16 August 29, 2011 August 25 August 29, 2011 August 30 September 12, 2011 Prepare for Parallel Operations Perform Connectivity Test Parallel Operations September 13, 2011 Team Production Cutover TBD Team Provide members with sample application that leverages CROW API TBD CROW API Deep Dive TBD Member May begin development using CROW API specification TBD Member API Testing TBD API Production Cutover Assumptions All members will participate in CROW GUI Testing. Page 5 of 7
Any CROW Enhancements required by Appendix 12 will be developed/tested in parallel with SPP interface development/testing. Risks None identified. Additional Documentation <This section should include links to any supporting documentation. Supporting documentation should be posted to the project documentation folder as well.> For members who would like to begin development of applications using the API, please make use of the Control Room Operations Window (CROW) API Reference, version 5.2, which is available in the Outage Scheduler CWG project folder. Please refer to the Outage Scheduler project documentation folder for the following pieces of additional documentation: CROW GUI Tutorial Test Plan Test scripts for structured CROW GUI testing MIPO Deep Dive Meeting Minutes Communication Plan All project communication and information will be posted to the SPP Change Working Group Documentation folder. This MIPO will be updated upon change or with any new information, a redline version posted to the project documentation folder, and the CWG notified. Members can contact Derek Hawkins (dhawkins@spp.org, 501-688-1662) with any questions for the project team. Neil Robertson (nrobertson@spp.org, 501-614-3322) will be the secondary project team contact. Each Member will identify a Business Contact and a Technical Contact who will serve as member liaisons to the Team in their respective areas. The Team requests that members provide the CWG Staff Secretary with contact information for their Business Contact and Technical contact no later than June 17, 2011. Next Steps Action Assignee Status & Due Date Provide: Company Name Business Contact: Name, Phone Number, Email Address, & Primary Method of Contact Technical Contact Name: Name, Phone Number, Email Address, & Primary Method of Contact Participate in Structured CROW GUI Testing Member CWG Representative Member Testing Liaison June 17, 2011 In Progress thru July 29, 2011 Page 6 of 7
FAQs PR20090027 - Outage Scheduler Frequently asked questions will be added to the document as identified or necessary. Page 7 of 7