Member Impacting Project Overview Data Push

Transcription

1 Member Impacting Project Overview Data Push Page 1

2 Table of Contents Table of Contents... 2 Executive Summary... 4 Business Impact... 4 Technical Impact... 5 Technical Implementation... 6 Cutover/Back-out Plan... 7 Summary of Timeline... 7 Communication... 7 Next Steps... 7 FAQS... 8 Version Control Version Date Author Change Description 1.0 5/12/2009 J. Erwin Initial Template 1.1 5/3/2010 D. Giessmann First draft of Data Push document 1.2 5/14/2010 D. Giessmann Revisions from SPS/Xcel Energy s request and updates to proposed timeline based on CWG feedback 1.3 5/25/2010 D. Giessmann Add link to as-is xml file structure and other supporting documentation /4/2010 D. Giessmann Add protocol information to Technical Impact; update proposed timeline based on additional feedback; update documentation index 1.5 6/11/2010 D. Giessmann Update list of projects closed because their requirements are included in this project to include PR RTO_SS Schedule Data Availability; add more detail to Technical Impact section 1.6 7/21/10 D. Giessmann Update file names in documentation index 1.7 7/30/10 D. Giessmann Update file names in Business Impact section and documentation index. Flowgate Name has been added to Curtailment section /1/10 D. Giessmann Under Other Information table on page 4, add reference to document Example and Configuration.pdf (this document was posted 6/28/10 to provide information about how to configure server settings to increase HTTP uploads in IIS6.0). Updated version number for Data Details for Schedule Pushes v04.pdf Added LOSS SUM information to the Technical Page 2

3 Version Date Author Change Description PR Data Push Implementation section. Added FAQS section at end of document. Corrected IP address information table to reflect that the IP address for ITE using SPPNET will change. Page 3

4 Executive Summary The Data Push system will provide subscription-based data feeds similar to those provided by the current WebData Schedule push but with improved error handling and error logging, more reliable delivery of data, and the ability to re-push data not received. In addition, it will allow for the addition of future data packages (via separate future releases). The data to be provided in the first release has been selected based on prioritization information obtained from the PRR 131 Subcommittee. Member testing and transition to the new system is required, as detailed in remaining sections of this document. The original project to develop a Settlements Data API stemmed from members need to effectively shadow settle losses and to see outage schedules for reserve share events. The existing WebData pushes had a number of issues that needed to be addressed, including being difficult to support and troubleshoot because of a lack of internal error logging and handling. In order to address member and SPP needs most expediently, the Data Push effort has now been separated from the Data API effort. The first release of the Data Push system will provide enhanced near real-time and COS data pushes as well as a new data push that will supply a portion of the data required for shadow settlements. Business Impact The first release of the Data Push system will include changes to the two existing data pushes (Near Real Time data and COS data) and an additional push: Loss Sum by Loss Location. Specific data included in these pushes is detailed below. Sample files, XSD documentation and a Data Dictionary are available on the CWG site and are indexed in the Technical Impact section below. As with the current WebData Schedule Push, the Data Push system will be subscription-based. Current subscriptions will be transitioned to the system, which will require member system changes, coordination, and testing with each subscriber. See the Technical Impact, Technical Implementation, and Testing sections below. The following data will be provided in the first release: Near Real-Time Schedule Data for Control Area and Transmission Customer, which will include curtailment data (See Schedule_Integrated_Schedules_v03.xml and Schedule_NonIntegrated_Schedules_v03.xml) Daily Settlement Summary for Transmission Customer which will include additional loss information and will be delivered OD + 1. (See Combined_Energy_Schedules_v03.xml) Sum of Loss MW by Location (See sample file Loss_Location_Data_v03.xml) Report listing SPP pushes sent in a given time period will be posted on reports.spp.org A manual re-push of this data can be requested via SPP s standard service request process. Page 4

5 The following PRPC Projects have been terminated and included in the scope of this project since the requirements overlap: PR Add Two New Views to the RTOSS COS Subscription Service PR Schedule Push: Loss Locations PR Increase RTOSS Schedule Availability to WebData Transfer PR RTO_SS Schedule Data Availability Users and Business Functions Impacted All parties currently subscribed to the WebData Schedule push and any additional parties wishing to subscribe. Technical Impact The Data Push system will follow an updated XML specification which incorporates updated XML standards. Each subscriber will be required to update their systems to allow them to correctly receive and utilize the data pushes. The XML specification documents (XSD) were provided to the CWG on May 7, The sample files for the new data push are posted on the CWG site under Project Information for Data Push. To access the link to supporting documentation, click here. NOTE: The current WebData Subscription Service document cannot be posted to the website but can be provided upon request. Sample XML files Combined_Energy_Schedules_v03.xml Sample of what the new COS file will contain Loss_Location_Data_v03.xml Sample of what the Sum of Loss MW by Location file will contain Schedule_Integrated_Schedules_v03.xml Sample of what the Near Real Time with Integrated MW file will contain Schedule_NonIntegrated_Schedules_v03.xml Sample of what the Near Real Time with Non-Integrated MW file will contain old_xml_example.xml Sample of the old xml; the as-is that was not originally provided when the new xml was originally distributed XSD files Combined_Energy_Schedules_v03.xsd Loss_Location_Data_v03.xsd Schedule_Integrated_Schedules_v03.xsd Schedule_NonIntegrated_Schedules_v03.xsd The XML Schema document for the COS file The XML Schema document for the Sum of Loss MW by Location file The XML Schema document for the Near Real Time with Integrated MW file The XML Schema document for the Near Real Time with Non-Integrated MW file Excel Spreadsheet Data Details for Schedule Pushes v04.pdf Data Dictionary; provides details and data definitions for the XML files listed above Other Information PR New Settlement Data Push Information This documents information presented to the Settlements User Group about the COS data push. Page 5

6 Other Information Changes to XML.pdf Example and Configuration.pdf This document highlights the differences between the old and new XML file for the near- real time data push. This applies for both the integrated and non-integrated push. The PayLoadType would be Schedule_NonIntegrated_Schedules for the non-integrated push. This documents how to configure server settings (increase from 4MB default in IIS6.0) for HTTP uploads Data transmission will be sent in a secure manner. The following describes the version and transport method for sending data to clients. Hypertext Transfer Protocol Secure (HTTPS), utilizing the Hypertext Transfer Protocol version 1.1 (HTTP 1.1). Data Transmission for the Schedule Event-driven Notification Deliver System (SENDS) Phase 1: Data transmission sent to customers will use HTTPS. The customer s web server will need a valid Server Certificate that can be verified up the chain to a Trusted Root Certificate Authority. The customer will provide Southwest Power Pool access to the Trusted Root Certificate Authority and Intermediate Certification Authorities so that it can be stored in the SENDS local machines certificate cache. This will enable data transmission without the need for a client certificate but ensure that the transmission is encrypted. HTTP uploads are limited by default in IIS 6.0 to 4MB. Configuration server settings will have to be increased. NOTE: Amount of increase to be provided during testing. The table below indicates which IP addresses will change for this new process. Environment SPPNet Internet DR No YES PRD No YES ITE YES No Technical Implementation Subscribers will need to make changes to their systems in order to support the receipt of data pushes from the Data Push system, prior to the testing period. NOTE: MPs will be set up in ITE to receive the pushes they are currently receiving in production. For example, if you receive the Near Real-Time Non-Integrated push and the COS Schedule push in production, you will be set up to receive those in ITE. To add the new Loss Sum push, it must be requested through Customer Relations. To receive any push not currently sent in production, the MP must request it through Customer Relations. The four pushes are: Near Real-Time Non-Integrated push Near Real-Time Integrated push COS Schedule push Loss Sum push (new to all MPS; please contact your CRR if you wish to subscribe) Page 6

7 Testing SPP will support testing of the data pushes in the ITE with each subscriber on a scheduled basis, during the proposed testing period of September 1 October 22, SPP will contact project liaisons to set up scheduled, interactive testing with curtailment data. Training SPP does not anticipate any training needs for this project. Cutover/Back-out Plan Pending successful testing, cutover to the production Data Push system will occur October 26, While it is expected that the CWG-negotiated timelines will be met by all subscribers, in the event that all subscribers are not able to successfully complete their system changes and testing, the cutover will be delayed and new timelines will be negotiated with the CWG. Summary of Timeline NOTE: All of these dates are dependent upon approval by the CWG. XSD delivered to CWG May 7, 2010 Member Development Present August 31, 2010 Member Testing September 1 October 22, 2010 Implementation October 26, 2010 Communication All project communication and information will be posted to the SPP Change Working Group Project Documentation folder. Please submit all project-related correspondence through your respective SPP Customer Relations Representative. The CWG is requested to identify and communicate a project liaison for this effort to Project Manager Dena Giessmann. Next Steps Action Assignee Status & Due Date Distribute XML Specs and Member Impact Project Overview Document to CWG CWG Teleconference to discuss specs and potential timeline for development PM 5/7/10 CWG Week of 5/10/10 Page 7

8 Action Assignee Status & Due Date changes Member Development CWG Present August 31, 2010 Member Testing CWG/SPP September 1 October 22, 2010 Implementation SPP October 26, 2010 FAQS What is the difference between an integrated and non-integrated schedule? Integrated Schedule Includes the sum of the MW value for an hour of the schedule. Non-Integrated Schedule Includes a MW value every time the schedule changes within an hour. What are the detailed definitions of the COS and Loss MW pushes? ETS Energy Energy Combined Schedule Daily Summary of all energy schedules submitted to the Settlement system. Sum Loss MW by Location - The Sum of Loss_MW grouped by hour ending for the Settlement Location holding the losses. How do we determine which pushes an entity receives in ITE? Each company is automatically set up in ITE like it is in production. However, if a company wants to see one of the pushes not currently being received, it can be requested from the Customer Relations Representative. Page 8