Business Requirements Specification

Transcription

1 and Data Transparency Improvements Project Business Requirements Specification - Planning Business Requirements Specification and Data Transparency Improvements Project Doc ID: GNFDMDEHU6BB Page 1 of 20

2 and Data Transparency Improvements Project Business Requirements Specification - Planning Date Version Description Author 08/04/ Created the document Tarak Thaker 09/08/ Updated BRQ020 from 7 days to 1 day Lindsey Larson Doc ID: GNFDMDEHU6BB Page 2 of 20

3 and Data Transparency Improvements Project Business Requirements Specification - Planning Disclaimer All information contained in this draft Business Requirements Specification (BRS) as provided by the California Independent System Operator Corporation (ISO) is prepared for discussion and information purposes only. The draft BRS is provided as is without representation or warranty of any kind, including, without limitation, a representation or warranty as to accuracy, completeness, or appropriateness for any particular purpose. The draft BRS shall be revised as the development and review of the business requirements progresses. The ISO assumes no responsibility for the consequences of any errors or omissions. The ISO may revise or withdraw all or part of this information at any time at its discretion without notice. Doc ID: GNFDMDEHU6BB Page 3 of 20

4 and Data Transparency Improvements Project Business Requirements Specification - Planning Table of Contents 1. INTRODUCTION PURPOSE DETAILS OF BUSINESS NEED/PROBLEM DESCRIPTION BUSINESS PROCESS IMPACTS HIGH LEVEL BUSINESS PROCESS Description Pros RISKS AND MITIGATION JUSTIFICATION BUSINESS REQUIREMENTS CURRENT SYSTEM DIAGRAM TO-BE (FUTURE) SYSTEM DIAGRAM BUSINESS PROCESS: MANAGE PIRP DECOMISSIONING Business Requirements BUSINESS PROCESS: MANAGE DATA INTEGRATION FOR PIRP DECOMISSIONING Business Requirements BUSINESS PROCESS: MANAGE INTEGRATION FOR VER FORECAST DATA Business Requirements BUSINESS PROCESS: MANAGE DATA TRANSPARENCY FOR MARKET CLEARING AND EPI Business Requirements BUSINESS PROCESS: MANAGE VER FORECAST DATA ARCHIVAL Business Requirements BUSINESS PROCESS: MANAGE WECC VER FORECAST DATA ARCHIVAL Business Requirements BUSINESS PROCESS: MANAGE ALFS SYSTEM UPGRADE Business Requirements...20 Doc ID: GNFDMDEHU6BB Page 4 of 20

5 and Data Transparency Improvements Project Business Requirements Specification - Planning 1. Introduction 1.1 Purpose The purpose of this document is to capture and record a description of what the Users and Business Stakeholders of the project wish to obtain by providing high-level business requirements. This document establishes the basis for the agreement between the initiators and implementers of the project. The information in this document serves as input to determining the scope of Information Systems projects and to all Business Process Modeling and System Requirements Specifications efforts. These requirements will serve as the initial set of business unit requirements for the appropriate software application/systems development effort. It is understood that additional requirements and systems analysis may produce To Be Business Process Models, System Requirements Specifications, and Use Cases to serve as the set of requirements documents used by the development teams to buy, modify, or build the necessary software and hardware systems. The Business Unit(s) involved in the project will have an opportunity to review and approve all requirements documentation produced. Doc ID: GNFDMDEHU6BB Page 5 of 20

6 and Data Transparency Improvements Project Business Requirements Specification - Planning 2. Details of Business Need/Problem 2.1 Description The PIRP system is being decommissioned and its forecasting data collection and reporting functions must be implemented in another system. Additionally, Variable Energy Resource (VER) telemetry and performance data collection shall be streamlined to eliminate a cumbersome and time intensive manual process. The ALFS system must consume the dispatch operating target (DOT) from EMS/PISOA. Finally, the VER forecast data needs to be archived for the Department of Market Monitoring (DMM) analysis and reporting functions. 3. Business Process Impacts 3.1 High Level Business Process Description This project is highly involved in the following CAISO level 1 process areas: Manage Markets & Grid The description below outlines the high-level scope items for Load Improvements: 1. Decommission PIRP a. Retire PIRP system i. This includes retiring system references to PIRP on website & portal and remedy/incident management systems b. Retire PIRP processes and reports that are no longer relevant i. Two reports are deemed no longer required c. Assign required PIRP functionality to appropriate systems i. PIRP Reporting will be performed by CMRI (Forecast by resource) ii. Manage Exception Group Mapping that PIRP performed (in AIM) iii. ALFS will send Hourly forecast info to ETerraSettlements 2. Systems newly performing remaining PIRP functionality will consume data needed to provide that functionality a. This includes data pulls from OMAR, WebOMS, PISOA, others 3. Streamline labor intensive and error prone VER data input process among source systems (EMS, Master File) to destination systems PISOA, ALFS, Service Provider (currently AWS Truepower). Doc ID: GNFDMDEHU6BB Page 6 of 20

7 and Data Transparency Improvements Project Business Requirements Specification - Planning 4. Consume Dispatch Operating Target data into ALFS from EMS via PISOA to perform some functions in ALFS. 5. Persist VER Forecast Data in an archival system for DMM analysis and reporting. 6. Persist WECC Forecast Data Archival 7. Perform Data Transparency Reporting for Wind and Solar Resources Pros Since PIRP as a system is no longer architecturally well aligned with new system integrations and functionality migration into other systems, PIRP system decommissioning will help to reduce the number of system that need to be managed and maintained. Some of PIRP s required reporting and data collection functionality can be implemented in other systems that are better aligned with their system purpose. Streamlining the VER data collection process will eliminate a manual, error prone, and timeintensive process. 3.2 Risks and Mitigation There is a risk/dependency that the VER Resource infrastructure described in this BRS is in place before large VER penetration occurs as part of future model builds. 3.3 Justification This project is required to align system architecture with the purpose of each application. Doc ID: GNFDMDEHU6BB Page 7 of 20

8 and Data Transparency Improvements Project Business Requirements Specification - Planning 4. Business Requirements The sections below describe the Business Processes and the associated Business Requirements involved in the project. These may represent high level functional, non-functional, reporting and/or infrastructure requirements. These business requirements directly relate to the high level scope items determined for the project. Doc ID: GNFDMDEHU6BB Page 8 of 20

9 and Data Transparency Improvements Project Business Requirements Specification - Planning As the Load improvements project requires the decommissioning of PIRP, there are major integration changes required. 4.1 Current System Diagram OMAR RED arrows = SOA Integration OMS EMS/PI MET / MW Gen PISOA Meter Data, DB to DB MW Availability PI to ALFS Script MET / MW Gen Eterra Settlements HA VERs PIRP DA & HA VER ALFS DA and Real-Time 5 min VER Forecast Service Provider HA & DA Renewable Forecast for VER Meter Data, MW Availablity 5 Minute VER Forecast OASIS DA VER IFM/RTN Doc ID: GNFDMDEHU6BB Page 9 of 20

10 and Data Transparency Improvements Project Business Requirements Specification - Planning 4.2 To-Be (Future) System Diagram Red = Existing SOA Integration, Purple = New SOA Integration Master File MV EMS/PI Resource MW Gen, MET data, Windspeed, other Static resource data MET / MW Gen, DOT RED arrows = SOA Integration PISOA Purple = Pending 5 minute tags, 15-min Tags, MW Gen, (up to 800 tags), DOT MET / MW Gen, Resource-level data Including Resource Name, DOT Meter Data (Pull) OMAR Eterra Settlements HA VER, Latest Forecast ALFS DA and Real-Time 5 min VER Forecast Service Provider MW Availability (Pull) CMRI (resource-level reporting) DA, HA VER Per resource DA, HA VER Per resource OASIS (Aggregates resource-level to APIs region) DOT Day-Ahead, 5 Minute VER Forecast IFM/RTN External MPs 5-min VER Forecast EDR Submitted VER Forecast WebOMS SIBR Doc ID: GNFDMDEHU6BB Page 10 of 20

11 4.3 Business Process: Manage PIRP Decomissioning Business Requirements ID# Business Feature Requirement Type Business Unit(s) Affected BRQ005 BRQ010 The PIRP Participation Report shall be decommissioned. Load The PIRP Data Quality Report shall be decommissioned. Load BRQ015 The PIRP Rolling Hour-Ahead Forecast shall be decommissioned. This report shall be refreshed at T-105 minutes before the hour. It shall be reimplemented in CMRI. Load BRQ017 The PIRP Hour-Ahead Locked Report shall be decommissioned. It shall be re-implemented in CMRI. This report shall be refreshed at T-105 minutes before the hour. Load Note: this is the forecast report that is settled upon. BRQ020 The PIRP Day-Ahead Forecast Report shall be decommissioned. It shall be re-implemented in CMRI as a Variable Energy Resource (VER) forecast. This report will provide a rolling forecast for and including the next 1 day. This report shall be published and refreshed at 5:30am. Short Term Note: This requirement serves a business request by the IOUs. BRQ021 OASIS shall consume the Hour Ahead (HA) and Day-Ahead (DA) Renewable Variable Energy Resource data Short Term Note: PIRP currently supplies OASIS this payload. ALFS adapter shall provide this to OASIS. Doc ID: GNFDMDEHU6BB Page 11 of 20

12 and Data Transparency Improvements Project Business Requirements Specification - Planning ID# Business Feature Requirement Type Business Unit(s) Affected BRQ022 E-Terra shall consume the Hour Ahead (HA) Renewable Variable Energy Resource data Short Term Note: PIRP currently supplies Eterra this payload. ALFS adapter shall provide this to E Terra. BRQ023 PIRP as a system shall be decommissioned. This includes removal from CAISO website, taking back database and application storage, etc. Short Term Note: Likely to be implemented at a later time from the PIRp UI being turned off. BRQ025 A user must be able to request access for a given resource in the three aforementioned reports. Short Term Note: This requirement will be managed as part of the AIM Improvements project. BRQ027 AIM shall manage Exception Group Mapping (Entities) for CMRI to handle the three aforementioned CMRI reports (PIRP Hour-Ahead Locked Report, PIRP Day-Ahead Forecast Report, and Rolling Hour Ahead Report). This applies to the ClearedMW CMRI Reports, EPI Reports as part of the Data Transparency section. This functionality will allow for resource to role mappings and view restrictions. Short Term BRQ028 AIM shall manage User Role Mapping for CMRI to handle the three aforementioned CMRI reports (PIRP Hour-Ahead Locked Report, PIRP Day-Ahead Forecast Report, and Rolling Hour Ahead Report). This applies to the ClearedMW Report, EPI CMRI Reports as part of the Data Transparency section. This functionality will allow for user to role mappings and view restrictions. Short Term 4.4 Business Process: Manage Data Integration for PIRP Decomissioning Business Requirements Doc ID: GNFDMDEHU6BB Page 12 of 20

13 and Data Transparency Improvements Project Business Requirements Specification - Planning ID# Business Feature Requirement Type Business Unit(s) Affected BRQ100 CMRI shall consume Day-Ahead, Hour-Ahead VER Forecast Data from ALFS adapter. CMRI will use this data to support new the Hourly and Day-Ahead Forecast Reports (see BRQ020, BRQ015, BRQ017). ITPD BRQ103 CMRI shall make the Hourly and Day-Ahead Forecast Reports (see BRQ020, BRQ015, BRQ017) available to market participants in a UI format. ITPD BRQ105 CMRI shall make the Hourly and Day-Ahead Forecast Reports (see BRQ020, BRQ015, BRQ017) available to market participants in an automated manner (APIs). ITPD BRQ110 The Forecast Service Provider (AWST) shall consume Meter Data from the Meter Data management system. ITPD Note: Meter Data is currently being consumed by PIRP and is indirectly being made available to The Forecast Service Provider (AWST). BRQ115 ALFS shall consume VER MW Availability from the outage management system. ITPD Note: MW Availability data is currently being consumed by PIRP and is indirectly being made available to ALFS. BRQ116 The Forecast Service Provider (AWST) shall consume MW Availability from the outage management system. ITPD BRQ135 Note: MW Availability data is currently being consumed by PIRP and is indirectly being made available to The Forecast Service Provider (AWST). CSDS / AIM shall update profiles to manage exception group mappings. Corporate Systems BRQ140 BRQ145 Potential Requirement: WebOMS may require new roles to be implemented for the forecast provider (AWST) to pull data from WebOMS Potential Requirement: OMAR may require new roles to be implemented for the forecast provider (AWST) to pull data from OMAR. ITPD, Load ITPD, Load Doc ID: GNFDMDEHU6BB Page 13 of 20

14 and Data Transparency Improvements Project Business Requirements Specification - Planning ID# Business Feature Requirement Type Business Unit(s) Affected BRQ150 References to PIRP on the CAISO market portal shall be removed. ITPD BRQ155 PIRP shall be removed as an option for case management from CIDI / Remedy Force / AARF. ITPD, Help Desk BRQ160 AWS shall consume the Dispatch Operating Target (DOT) from RTN PSTO BRQ165 ALFS shall receive and consume the Market Participant submitted VER Forecast from the AI. Short-Term, PSTO 4.5 Business Process: Manage Integration for VER Forecast Data Business Requirements Doc ID: GNFDMDEHU6BB Page 14 of 20

15 and Data Transparency Improvements Project Business Requirements Specification - Planning ID# Business Feature Requirement Type Business Unit(s) Affected BRQ120 PISOA shall consume the Resource ID and Fuel type information for mapping PI tag data. ITPD, MCI Note: This may require an XSD update in order to consume this data. BRQ121 NEW VER Resource Procedure: 1. A resource is flagged as wind/solar (VER) as part of the NRI process 2. Generate PI Tags for all new Production resource IDs (especially for project, VER resource IDs). Rules / process outlined below: PSTO, Short Term Consume EMS point name, SO Analog table Create proper spacing between the end of the tag and the period (.) Concetenate the market resource ID suffix to the beginning of the PI tag. Concetenate.AQ (quality) and.av (value),.cv (calculated value, only for ALFS) to the end of the PI tag Formulate measurement type label based on the PI Tag Name. Include Designated Turbines and specific attrubites (windspeed, wind direction) into the PI Tag creation process o Backfill DT turbine wind speed and wind direction that are currently unavailable in PISOA. Output newly created tags into consuming system (PISOA) 2. The new PI Tag shall be validated to determine if it already exists. 3. If a PI tag must be created, create the PI tag based on Fuel Type. Include MF fuel type, measurement type, and tag value. 4. If an issue exists, then remediate manually and log and notify the issue. User must be able to view PI tags associated with the VER payload. A role shall allow for PI tag mapping edits (extra spaces, etc.). 5. Add the tag to the VER payload. BRQ122 The VER data payload shall be sent to ALFS and AWS via standard SOA. Short Term Doc ID: GNFDMDEHU6BB Page 15 of 20

16 and Data Transparency Improvements Project Business Requirements Specification - Planning ID# Business Feature Requirement Type Business Unit(s) Affected BRQ123 The VER data payload shall include Resource ID, PI Tag, Measurement Type, Fuel Type, Value. Short Term BRQ124 ALFS shall detect new VER resources and create associated forecasting models. Short Term BRQ125 ALFS shall consume several data elements Dispatch Operating Target (DOT) from IFM/RTN via a data payload. ITPD, Short Term Doc ID: GNFDMDEHU6BB Page 16 of 20

17 and Data Transparency Improvements Project Business Requirements Specification - Planning 4.6 Business Process: Manage Data Transparency for Market Clearing and EPI Business Requirements ID# Business Feature Requirement Type Business Unit(s) Affected BRQ200 CMRI s shall consume the ClearedMW quantity from all markets (DA, Hour-Ahead, FMM, RTD) for binding and advisory intervals. N/A BRQ210 CMRI shall make the Cleared MW quantity available to Market participants for all markets (DA, Hour-Ahead, FMM, RTD) for binding and advisory intervals. N/A BRQ220 CMRI shall receive and consume the Electricity Price Index (EPI) from RLC/ECIC for the Day-Ahead and Real-Time Markets. N/A BRQ230 CMRI shall make available the EPI to the Scheduling Coordinators (SCs) for owned resources. This applies for the Day-Ahead and Real-Time Markets for ISO resources and EIM Participating resources only. N/A Doc ID: GNFDMDEHU6BB Page 17 of 20

18 and Data Transparency Improvements Project Business Requirements Specification - Planning 4.7 Business Process: Manage VER Forecast Data Archival Business Requirements ALFS consumes the VER Forecast from DNVGL (Pacificorp) and AWST (CAISO). 5 minute forecasting, rolling 8 hours out. Uses the 5 minute forecast for the binding interval 10 minutes out. Day-Ahead Forecast (Hourly). ID# Business Feature Requirement Type Business Unit(s) Affected BRQ400 Every 5 minutes, the VER Forecast shall be recorded and archived for the binding interval in EDR. The binding interval is 24 five-minute values (2 hours, 12 5-minute intervals each). 288 x 24 values 6912 values per day. This shall be archived for 6 years. This will be about 631k rows of data, where each row contains the 24 5-minute interval values. PSTO, Short- Term 60 days worth of data shall be immediately available in ALFS. The rest (6 years) worth may be archived in EDR. Payloads: Submit5minVER (From AWS), Broadcast5MinVER (From ALFS) BRQ402 Daily, the Day-Ahead VER Forecast shall be recorded and archived for the binding interval in EDR. 24 hourly values per day (one hour interval). This shall be archived for 6 years. 30 to 60 days worth of data shall be immediately available in ALFS. The rest (6 years) worth may be archived in EDR PSTO, Short- Term, PSTD Payloads: SubmitDailyVER (From AWS), BroadcastDayAheadVER (From ALFS) (to be created) BRQ410 Every Market Participant Submitted VER Forecast shall be captured. 60 days worth of data shall be immediately available in ALFS. The rest (6 years) worth may be archived in EDR. Payload: XYZ5MinVER (name to be determined in SRS) PSTO, Short- Term, PSTD Doc ID: GNFDMDEHU6BB Page 18 of 20

19 and Data Transparency Improvements Project Business Requirements Specification - Planning 4.8 Business Process: Manage WECC VER Forecast Data Archival Business Requirements ID# Business Feature Requirement Type Business Unit(s) Affected BRQ500 EDR shall collect the WECC CSV file via FTP. This pull shall occur daily between 12:13pm and 2:00pm. 6 years worth of WECC data shall be stored with 60 days available online and the rest archived. PSTO, Short- Term, PSTD Doc ID: GNFDMDEHU6BB Page 19 of 20

20 and Data Transparency Improvements Project Business Requirements Specification - Planning 4.9 Business Process: Manage ALFS System Upgrade Business Requirements ID# Business Feature Requirement Type Business Unit(s) Affected BRQ600 The ALFS system shall be upgraded to the latest version, namely Current version is Integration Note: Broadcast / Receive should not change in structure. No regression test required on payload New Version Benefits:Should allow for easier MF integration. Automated MF data load. UI monitor is still manual. Allows for VER and DR model integration. PSTO, Short- Term, PSTD, ITRON See additional project plan notes here. BRQ605 The ALFS 764 (VER) schema shall be merged into the base Load Forecast schema. Note: The VER forecast model was create in a separate schema as part of the FERC 764 effort. At this time the VER schema shall be merged into the base model. PSTO, Short- Term, PSTD, ITRON Doc ID: GNFDMDEHU6BB Page 20 of 20