Business Requirements Specification

Transcription

1 Business s Specification Peak Reliability Coordinator Funding Page 1 of 8

2 Disclaimer All information contained in this draft Business s 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. Page 2 of 8

3 Table of Contents 1. INTRODUCTION PURPOSE DETAILS OF BUSINESS NEED/PROBLEM DESCRIPTION JUSTIFICATION BUSINESS PROCESS IMPACTS HIGH LEVEL DESCRIPTION OF BUSINESS PROCESS BUSINESS REQUIREMENTS BUSINESS PROCESS: MANAGE MARKET BILLING & SETTLEMENTS Business s BUSINESS PROCESS: MANAGE MRI-SETTLEMENT Business s BUSINESS PROCESS: MANAGE MARKET CLEARING Business s BUSINESS PROCESS: MANAGE DISPUTE ANALYSIS & RESOLUTION Business s BUSINESS PROCESS: MANAGE CREDIT & COLLATERAL Business s... 7 Page 3 of 8

4 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 s 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 s 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. 2. Details of Business Need/Problem 2.1 Description Due to the recent bifurcation of the Western Electricity Coordinating Council (WECC), a separate independent company, Peak Reliability, was formed to perform the reliability coordinator services previously performed by WECC. Because of this change, the ISO expects to start receiving an annual direct bill from Peak for reliability coordinator services beginning in November Objective: Passing on the annual direct bill for reliability coordinator service from Peak to SCs. Include an adjustment for the SCs amount of the RC Charges in calculation of collateral requirements and other credit requirements. Change settlement and payment process to issue an initial and recalculation statement of reliability coordinator service charges or default payment to SCs. Revise Tariff section to give the ISO authority to bill and collect for reliability coordinator charges. 2.2 Justification The ISO believes that it is more likely that the alternative funding agreement will be completed and executed in time to fund Page 4 of 8

5 3. Business Process Impacts 3.1 High Level Description of Business Process Manage Operations Support & Settlements Level II - Manage Market Billing & Settlements o Invoice SCs to collect Peak RC charges. Manage Market & Reliability Data & Modeling Level II - Manage Credit & Collateral (Logical Group) o Adjust financial security amounts. 4. Business s The sections below describe the Business Processes and the associated Business s 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. 4.1 Business Process: Manage Market Billing & Settlements Business s BRQ010 System shall calculate the RC charge rate to SCs. RC charge rate = Total RC Charges invoiced to the CAISO / (Total NERC/WECC metered demand). eterra BRQ020 System shall calculate the allocation of RC charges to each SC as follows: eterra RC charges to one SC = RC charge rate * (NERC/WECC Metered Demand for that SC). BRQ030 System shall calculate the Peak Initial statement within 5 Business Days from CAISO receiving the invoice for RC charges. eterra Page 5 of 8

6 BRQ031 Within 5 Business Days after CAISO receives the invoice for Reliability Coordinator Charges, Settlements shall issue a market notice setting forth the RC charge rate for the relevant assessment year. N/A BRQ040 Within 10 Business Days after CAISO receives the invoice for RC charges, Settlements shall publish the Peak Invoice containing the RC charges for each SC. Settlements BRQ050 If CAISO determines that an invoice contains a typographical or other ministerial error, and the resolution of the dispute makes correction necessary, the CAISO shall issue a corrected statement within 15 Business Days of the date the initial Peak statement was published. Settlements BRQ060 The ISO shall include the RC charges in the next available Peak invoice to collect the unpaid RC charge defaults. Settlements Note: This is discretionary to avoid billing for a nominal amout of unpaid charges. BRQ070 If the ISO decides to issue an invoice to collect the unpaid RC charge defaults, the ISO shall pro-rata allocate unpaid payment defaults to scheduling coordinators with NERC/WECC metered demand, excluding the defaulting scheduling coordinator. Settlements 4.2 Business Process: Manage MRI-Settlement Business s Page 6 of 8

7 BRQ090 MRI-S system shall provide data to SCs who receive RC charges. MRI-S Data includes, but not limited to: SCs billable Metered Data. SCs total amount of RC charges. SCs default amount. 4.3 Business Process: Manage Market Clearing Business s BRQ100 Market clearing system shall add an invoice type, Peak. Market Clearing 4.4 Business Process: Manage Dispute Analysis & Resolution Business s BRQ110 CIDI shall add a charge code, Peak. CIDI 4.5 Business Process: Manage Credit & Collateral Business s Page 7 of 8

8 BRQ120 EAL Components shall have a new component for Peak RC charges. EAL calculation Note: EAL Component #4 Extrapolated shall not include Peak RC charges. BRQ130 Parent-Child EAL Report in CAISO Credit Portal which is located in the Credit Management section of the CAISO s Market Participant Portal (MPP) shall include the EAL Component for Peak RC charges. CAISO Credit Portal BRQ140 Detailed Charge Code Data in CAISO Credit Portal which is located in the Credit Management section of the CAISO s Market Participant Portal (MPP) shall include the Charge Code and EAL Component for Peak RC charges. CAISO Credit Portal Page 8 of 8