Business Requirements Specification - California ISO · Template Version: 4 Document Version: ... Clarification about how ISO uses state of charge ... Business Requirements Specification

Program Office

Copyright 2012 California ISO

Doc ID: GNFDMDEHU6BB-46-53 Page 1 of 21

Business Requirements Specification

Energy Storage and Distributed Energy Resources (ESDER)

Document Version: 1.0

Date Created: 5/5/2016

Program Office



Technology

Template Version: 4


Energy Storage and Distributed Energy Resources (ESDER) Business

Requirements Specification - Planning Date Created: 5/5/2016

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.

Program Office



Technology

Template Version: 4




Table of Contents

1. INTRODUCTION ........................................................................................................................................................................ 4

1.1 PURPOSE .................................................................................................................................................................................... 4

2. DETAILS OF BUSINESS NEED/PROBLEM .......................................................................................................................... 4

2.1 DESCRIPTION.............................................................................................................................................................................. 4

3. BUSINESS PROCESS IMPACTS .............................................................................................................................................. 6

3.1 HIGH LEVEL DESCRIPTION OF BUSINESS PROCESS .................................................................................................................... 6

3.2 VISUAL AIDES ........................................................................................................................................................................... 7

Definition of Terms ........................................................................................................................................................................ 8

3.3 JUSTIFICATION ........................................................................................................................................................................... 9

4. BUSINESS REQUIREMENTS ................................................................................................................................................... 9

4.1 BUSINESS PROCESS: < MANAGE ENTITY AND RESOURCE MAINTENANCE UPDATES (MASTER FILE) AND FULL NETWORK

MODEL (FNM)> .................................................................................................................................................................................. 9

4.1.1 Business Requirements .................................................................................................................................................... 9

4.2 BUSINESS PROCESS: < MANAGE DAY AHEAD MARKET AND REAL TIME MARKET > ............................................................... 11

4.2.1 Business Requirements .................................................................................................................................................. 11

4.3 BUSINESS PROCESS: < MANAGE DRS, DRRS, METERING, AND SETTLEMENT > ...................................................................... 15


4.4 BUSINESS PROCESS: MARKET MONITORING AND REPORTING ................................................................................................. 21


Program Office



Technology

Template Version: 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 projects and to all Business Process Modeling and System Requirements Specifications efforts.

Business requirements are what must be delivered to provide value for the Users and Business Stakeholders. Systems, software, and processes are the ways (how) to delivery, satisfy or meet the business requirements (what). The Initial BRS will provide sufficient information to determine the scope of the project and will provide the functional business requirements so that the Architecture Decision can be made. Following the Architecture Decision, the remaining non-functional business requirements, such as data, performance, web services, and security can be added to complete the Final BRS.

2. Details of Business Need/Problem

2.1 Description

Overview of Energy Storage and Distributed Energy Resource (ESDER)

Non-generator Resources (NGR) enhancements

Updated NGR documentation (multiple BPMs, add NGR detail rules and examples)

Clarification about how ISO uses state of charge (SOC) in the market optimization (BPM, market operations, clarify with examples on telemetry, timing, optimization with SOC limits)

Allow initial state of charge as a daily bid parameter in the day-ahead market (SIBR, DAM, daily bids, BPM Market Op)

Allow an option to not provide SOC energy limits or not have the ISO co-optimize an NGR based on state of charge (SIBR, DAM/RTM, BPM market op 7.8.2.5)

Proxy Demand Response and Reliability Demand Response Resource (PDR/RDRR) Enhancements (no system changes, Scheduling Coordinator Meter Entity (SCME) submits PDR meter data directly based on approved baseline method according to Tariff)

Support performance evaluation methodology based on NAESB meter generator output (MGO) concepts o Meter configuration A

SCME submit Net meter (N) of load representing load being offset by the behind meter generation, existing baseline type I performance apply with PDR N meter

Program Office



Technology

Template Version: 4




o Meter configuration B Option B1 –load reduction only (DRS/Settlement, existing functionality-hourly gen for submitting (N-G) interval meter, using sign convention that load is a positive quantity and the output of a generating device – or energy storage in discharging mode- is a negative quantity)

SCME calculate Baseline: Virtual Meter for the load is net meter (N)- generator meter (G) for baseline BN-G, baseline type I apply BN-G

SCME calculate/submit PDR performance interval meter BN-G(t)-(N(t)-G(t)) o Meter configuration B Option B2 –generation offset only(DRS/Settlement, existing functionality-hourly

gen for submitting G interval meter, BPM metering) SCME calculate Baseline: meter G(t), type I apply to baseline GLM, except Not apply A day-of

adjustment. SCME submit PDR performance = -(G(t)-GLM(t)), SCME apply Net export rule: N>0

o Meter configuration B Option B3 –load reduction and generation offset(DRS/Settlement, existing functionality-hourly gen for submitting , BPM metering)

SCME calculate baseline for load: BN-G(t) SCME calculate baseline for generator: GLM(t) SCME calculate/submit PDR performance= BN-G(t)-(N(t)-G(t))+ (-(G(t)-GLM(t)))= BN-G(t)-N(t)

+GLM(t) SCME apply Net export rule: N>0

Support NAESB Baseline type II: Develop additional detail regarding use of statistical sampling and document

that in the appropriate BPMs (written application, ISO approval, according to BPM metering, tariff)

o SC of PDR submit application for ISO approval (contract) o SC of PDR must follow the ISO sample size requirement and have interval meter (15 minute or 5

minute) from sampling underlying account, ISO have right to audit (customer side) o SC of PDR scale up the sampling data, submit the virtual meter data for the PDR resource for RTM

energy and AS (DRS existing functionality, BPM metering) o ISO apply 10-in-10 rules for the virtual meter data same way as type I interval meter data (DRS existing

functionality, BPM metering) o DAM cannot use type II for PDR, the underlying account must have the hourly meter.

Non-resource adequacy (non-RA) multiple use applications (no system changes)

Distribution system service provision and wholesale market participation o treat deviations from ISO dispatch instructions as uninstructed imbalance energy (UIE) o not address double payment

Services to end-use customers and wholesale market participation: o DERA as NGR: separate account for DERA, independent from load; or

Program Office



Technology

Template Version: 4




o PDR: Model as PDR with MGO baseline

Net movement of sub-resources at each pnode must be in same direction and aligned with distribution factors (DFs) when dispatched (DERA uses existing NGR functionality, DAM/RTM, BPM Market OP 7.8.2.5)

Metering and ISO settlement in all hours (DERA uses existing NGR functionality OMAR, Settlement, BPM) Support SC submit the SQMD for the PDR using MGO baseline method:

SCME shall subject to LRA rule if applicable

SCME shall follow the MGO methods approved by the ISO tariff and BPM

SCME shall submit a signed letter, acknowledge that SCME meets all the requirements in Tariff and BPM for using MGO Baseline and or other approved baseline methods.

Support ISO audit on PDR, DERA meter and monitor DERA GDF:

Leverage annual SCME self-audit, apply to SCME of PDR, DERA , o Annual process o report submitted by SCME o No data submitted from SCME o The rule of conduct for SCME is applicable

monitor DERA performance, GDF o Annual process, o ISO Produce report o Decide sample size to request o SCME submit requested DERA pnode meter for the whole year by 5 minute interval

ISO IT infrastructure must support SCME of DERA and PDR to submit data upon requests through secured site and store the data that can be retrieved.

Market application enhancement to support model multiple DERA and/or PDR at the same pnode without change the FNM (system changes in MF, IFM/RTM):

Apply functionality to combine individual schedules from multiple DER/PDR and load into a single nodal injection for NA power flow

Define resource ID for each NGR(DERA) and/or PDR for market bid and settlement, link to the same cnode

3. Business Process Impacts

3.1 High Level Description of Business Process

Manage Markets & Grid (MMG) (80005)

Manage Day ahead Market (MMG LII)

Manage Real Time Operations (MMG LII)

Manage Operations Support & Settlements (MOS) (80007)

SCME Self Audit Review (MOS LII)

Program Office



Technology

Template Version: 4




Manage Meter data submittals (MOS LIII)

3.2 Visual Aides

Support model multiple DERA and/or PDR at the same pnode

Program Office



Technology

Template Version: 4




Definition of Terms

Term Definition

BPM Business Practice Manuals

DAM Day-Ahead Market.

DERA Distributed Energy Resource Aggregation

DOT Dispatch Operating Target

DRP Demand Response Provider.

DRRS Demand Response Registration System

DRS Demand Response System

EMS Energy Management System

FNM Full Network Model

GDF Generation Distribution Factor

IFM Integrated Forward Market

LRA local regulatory authority

MF Master File

NGR Non-generator resource

PDR Proxy Demand Resource (PDR)

RTM Real-Time Market

SCME Scheduling Coordinator Meter Entity

SE State Estimator

SIBR Scheduling Infrastructure and Business Rules system

SOC State of Charge

SQMD Settlement Quality Meter Data

Program Office



Technology

Template Version: 4




3.3 Justification

Energy Storage and distributed energy resources connected to the distribution grid are growing and will represent an increasingly important part of the future resource mix. This initiative will make enhancements to NGR and to demand response performance measurement to facility distributed energy resource to participating market.

4. Business Requirements

The sections below describe the Business Processes and the associated Business Requirements involved in the project.

System impact includes:

Allow Bid in initial SOC value in DAM (SIBR)

Allow SOC constraint not be enforced: If No Energy limit submitted, MF will setup a flag that no SOC constraint will be enforced in DAM/RTM

Allow multiple PDR/NGR(DERA) logic resources link to the same network cnode/pnode (MF, DAM/RTM, EMS)

o Allow one network cnode/pnode connect more than one PDR/NGR(DERA) logic resources (MF) o Combine load resource and PDR/NGR(DERA) schedules from SCUC to form nodal injection at each

load cnode/pnode in network application (NA) for power flow solution (IFM/RTM) o Use PDR/NGR(DERA) previous DOT or SCADA telemetry if it is available as the initial condition in the

market. o Market optimally commit and schedule individual PDR/NGR(DERA) resources based on the their bids

and constraints.

4.1 Business Process: < Manage Entity and Resource Maintenance Updates (Master File) and Full Network Model (FNM)>

4.1.1 Business Requirements

Program Office



Technology

Template Version: 4




ID# Business Feature

Requirement Type

Potential Application(s)

Impacted

ESDER_BRQ010 Allow one Pnode connect more than one

PDR/NGR(DERA) resources

Define multiple PDR/NGR(DERA)

resource IDs, associate them with same

underlying FNM Pnode,

Ensure the PDR/NGR(DERA) resources

can be identified in the downstream

systems for power flow combined injection

and for PDR Settlement DLAP adjustment.

PDR/NGR (DERA) as single resource: The multiple PDR can be single resources defined at a Pnode.

PDR/NGR(DERA) as aggregated resource: The multiple PDR/NGR(DERA) can be aggregated resources defined at a Apnode, composed of one or more PNodes where the relevant individual units are connected. Define GDF for the aggregated resource.

PDR/NGR(DERA) resources can participate in energy and AS market.

Pass the resource and underlying pnode/apnode to downstream systems.

Core Master File

ESDER_BRQ011 Allow PDR/NGR(DERA) resources and load resources defined on the same FNM Pnode

Load resources and PDR/NGR(DERA) can be defined on the same Pnode

Generator and NGR connect to transmission network must have its own Pnode. PDR/NGR(DERA) cannot defined on the Pnode of (non- PDR/NGR(DERA)) generation resource.

Core Master File

Program Office



Technology

Template Version: 4





Requirement Type


Impacted

ESDER_BRQ020 No need to create Pnode and pseudo resource in FNM for each PDR, because the PDR will be defined on the load pnode.

Time of PDR to participating market will not be restricted by pre-defined PDR resources and FNM cycle.

Core FNM

ESDER_BRQ021 Business Process: Pre-defined resources will be created on demand in the Masterfile when requested through the GRDT process maintaining the current pre-defined resource ID Pnode and Pnode distribution factors currently in place for pre-defined resources by SubLap.

Core MF

ESDER_BRQ022 If No Energy limit defined for the resource, MF shall set SOC constraint flag as not enforced for the resource :

If scheduling coordinator of NGR not submit the energy limit, energy limit is “Null”, MF shall setup a flag for the resource SOC constraint not enforced in the Market using transfer script and pass to the market

Note This rule is not applicable for NGR-REM. NGR-REM resource always subject to SOC constraint.

Core

MF, Transfer Script

4.2 Business Process: < Manage Day Ahead Market and Real Time Market >


Program Office



Technology

Template Version: 4





Requirement Type


Impacted

ESDER_BRQ030 Bid in initial SOC value in DAM: Allow SC of NGR bid SOC initial value in DAM, through UI and API, apply initial SOC in the first hour of the DAM of NGR participation interval of the day. If SC not provide the initial value, system will use current existing logic, default to the SOC calculated from the prior day, or 0 if prior day SOC value not available.

Core

SIBR, DAM,

ESDER_BRQ031 If the SOC constraint flag of the resource set to not enforced, no SOC constraint will be enforced for the resource:

Market shall receive the SOC constraint flag for NGR resource from MF

If the flag set to not enforced, market and EMS shall not enforce SOC constraint for the NGR, and SOC data point is not required in telemetry.

Note This rule is not applicable for NGR-REM. NGR-REM always subject to SOC constraint.

Core

MF, DAM, RTM, EMS

Program Office



Technology

Template Version: 4





Requirement Type


Impacted

ESDER_BRQ041 Combine load resource and PDR/NGR(DERA) schedules from SCUC to form nodal injection at each load cnode in network application (NA) for power flow solution

Combine schedules: The load resource and PDR generation energy schedules or awards from SCUC shall be combined to form a net nodal power injection for the load cnode in the power flow solution.

Ex: at node2, PDR1=25, PDR2=20, NGR3=10, NGR4=-5, Load=100

Combined Load nodal injection (Load-Gen): Load-(PDR1+PDR2+NGR3+NGR4) =100-(25+20+10+(-5))= 50

Use combined nodal schedule to conduct power flow analysis: transfer the combined net nodal schedule to NA power flow for the power flow solution, contingency analysis, critical constraint determination, and loss penalty and shift factor calculation.

No Tracking: NA does not need to track segments of nodal inject for each PDR/NGR(DERA) or load resources.

EMS SE solution for the nodal injection: the Energy Management System (EMS) SE solution must be provided for nodal injection

Core

SIBR, DAM, RTM, EMS

Program Office



Technology

Template Version: 4





Requirement Type


Impacted

ESDER_BRQ050 Market shall optimally commit and schedule individual PDR/NGR(DERA) resources based on the their bids and constraints:

Commit and dispatch individual PDR/NGR(DERA): The market application shall optimally commit and schedule the each PDR/NGR(DERA) resource similar as regular resources based on its telemetry (State Estimator solution, ), three-part energy bid (SUC, MLC, and incremental energy bid) and the ancillary services bid, subject to its technical limits (ramp rate, minimum up and down times, etc.).

Core

DAM, RTM

ESDER_BRQ060 Set up PDR/NGR(DERA) initial condition of the interval in the market as previous DOT or telemetry if it is available:

If resource PDR/NGR(DERA) has no telemetry, set up initial condition to previous binding interval DOT

If resource PDR/NGR(DERA) has telemetry, use resource telemetry as starting point to calculate initial condition in the market.

Core

DAM, RTM,

EMS, SE

ESDER_BRQ070 The current market rules for PDR/NGR resources are applicable for the logic PDR/NGR(DERA) resources, including:

o Bidding o LMPM o Exceptional dispatch o Revenue Adequacy o Outages o Settlement o Publish

Core

Existing Functionalities

SIBR, DAM, RTM, OMS, Settlement, CMRI, OASIS. integration

Program Office



Technology

Template Version: 4




4.3 Business Process: < Manage DRS, DRRS, Metering, and Settlement >



Requirement Type


Impacted

ESDER_BRQ120 For PDR or RDRR with MGO baseline (Meter configuration A, B1, B2, B3), The SCME must meet the ISO tariff requirement to calculate the PDR or RDRR MGO baseline

SCME responsibility

submit PDR performance meter data through hourly gen function to DRS

ISO responsibility

ISO receive MGO meter through DRS hourly gen for PDR from SC

Existing PDR settlement rule apply for PDR,

Core

DRS, OMAR, Settlement

ESDER_BRQ121 For PDR elects gross load meter, SCME shall Calculate the baseline using configuration B1.

The Demand Response Energy Measurement shall be the quantity of Energy equal to the difference between (i) the Customer Load Baseline, which derives from the gross Load independent of offsetting Energy from behind-the-meter generation, for the Proxy Demand Resource or Reliability Demand Response Resource and (ii) the gross underlying Load, independent of offsetting Energy from the behind-the-meter generation.

SCME calculate Baseline: Virtual Meter for the load is net meter (N)- generator meter (G) for baseline BN-G, baseline type I (Tariff 4.13.4.1) apply BN-G

SCME calculate/submit PDR performance interval meter BN-G(t)-(N(t)-G(t))

Core

N/A

SCME will calculate PDR/RDRR baseline and performance

Program Office



Technology

Template Version: 4





Requirement Type


Impacted

ESDER_BRQ122 Settlement of Energy Transactions Using Metering Generator Output Methodology , with configuration B2

PDR/RDRR consisting of registered behind-the-meter Generating Units shall be the quantity of Energy equal to the difference between (i) the Energy output of the PRD/RDRR and (ii) the Generator Output Baseline for the behind-the-meter Generating Unit registered in the Proxy Demand Resource or Reliability Demand Response Resource, which derives from the Energy output of the behind-the-meter Generating Unit(s) only, independent of offsetting facility Load. In calculating the Energy output of such Generating Units, the net Meter Data must be set to zero in any Settlement Interval in which a Generating Unit is exporting Energy (i.e., where the behind-the-meter generation Energy output exceeds its facility Load). For such behind-the-meter Generating Units, the Generator Output Baseline will be calculated as set forth in Tariff Section 4.13.4.2.

SCME calculate Baseline: meter G(t), baseline GLM (Tariff 4.13.4.2)

SCME submit PDR performance = -(G(t)-GLM(t)),

SCME apply Net export rule: N>=0

Core

N/A


Program Office



Technology

Template Version: 4





Requirement Type


Impacted

ESDER_BRQ123 Settlement of ODR/RDRR Using Metering Generator Output Methodology and independent load reduction, with configuration B3

PDR/RDRR that include (i) separately metered, registered behind-the-meter generation Energy output Meter Data, exclusive of facility Load data pursuant to tariff Sections 4.13.4.2 and 11.6.2, and Proxy Demand Resources or Reliability Demand Response Resources that are (ii) Load reduction independent and separately metered from offsetting behind-the-meter generation pursuant to tariff Sections 4.13.4.1 and 11.6.1, shall be the sum of the Demand Response Energy Measurements for the Proxy Demand Resources or Reliability Demand Response Resources as if they were settled separately and independently pursuant to tariff Sections 11.6.1 and 11.6.2.

SCME calculate baseline for load: BN-

G(t)

SCME calculate baseline for generator: GLM(t)

SCME calculate/submit PDR performance= BN-G(t)-(N(t)-G(t))+ (-(G(t)-GLM(t)))= BN-G(t)-N(t) +GLM(t)

SCME apply Net export rule: N>=0

Core

N/A


Program Office



Technology

Template Version: 4





Requirement Type


Impacted

ESDER_BRQ125 Calculate the Meter Generator Output (MGO) Baseline GLM:

For behind-the-meter Generating Units registered in PDR/RDRR and settling Energy Transactions pursuant to tariff Section 11.6.2,

the Generator Output Baseline will be calculated in the similar manner as the customer load baseline uses 10-in-10 non-event day method,

Different from customer load

baseline, No A day-of adjustment multiplier apply to MGO Baseline GLM

The baseline amount of Energy provided by the behind-the-meter Generating Unit(s) will be calculated on the simple hourly average of the collected Meter Data

In calculating the Generator Output Baseline pursuant to tariff 4.13.4.2(a), the Meter Data must be set to zero in any Settlement Interval in which the behind-the-meter Generating Unit is charging, and in any Settlement Interval where the behind-the-meter Generating Unit is exporting Energy (i.e., where the behind-the-meter Generation Energy output exceeds its location Load)

Core

N/A


Program Office



Technology

Template Version: 4





Requirement Type


Impacted

ESDER_BRQ130 For PDR baseline Type II, statistic method

SCME responsibility:

PDR scale up the sampling data, submit the virtual load meter data (SQMD) for the PDR resource energy and AS (DRS, BPM metering)

ISO responsibility

Receive SCME submit the virtual load meter data (SQMD) for the total population of PDR underlying load.

Apply existing baseline rules for the virtual load meter data (BPM: Metering Section 12)

Core

DRS, OMAR, Settlement

ESDER_BRQ140 Support the submission of SQMD for the PDR using MGO performance method:

SCME shall subject to LRA rule if applicable

SCME shall follow the MGO methods approved by the ISO tariff and BPM

A DRP must submit a written request to the CAISO, [email protected], for approval of the use of the MGO performance methodology for the PDR/RDRR.

As specified in the Business Practice Manual, the CAISO and the Demand Response Provider will then engage in written discussion which will result in the CAISO either approving or denying the request.

Core

N/A

https://bpmcm.caiso.com/Pages/BPMDetails.aspx?BPM=Metering

https://bpmcm.caiso.com/Pages/BPMDetails.aspx?BPM=Metering

mailto:[email protected]

Program Office



Technology

Template Version: 4





Requirement Type


Impacted

ESDER_BRQ141 Support the submission of SQMD for the PDR/RDRR using the approved statistical sampling methodology:

A DRP must submit a written request to the CAISO, [email protected], for approval of the use of statistical sampling in the development of SQMD for the PDR/RDRR.

As specified in the Business Practice Manual, the CAISO and the Demand Response Provider will then engage in written discussion which will result in the CAISO either approving or denying the request.

Core

N/A

ESDER_BRQ150 Auditing by CAISO for Demand Response Providers

To ensure accuracy and compliance with the CAISO tariff, the CAISO will have the right to audit Meter Data submitted by Scheduling Coordinators to establish performance evaluation methodologies pursuant to tariff Section 4.13.4 or Demand Response Energy Measurements pursuant to tariff Section 11.6 Leverage annual SCME self-audit, apply to SCME of PDR, DERA ,

o Annual process o report submitted by SCME o No data submitted from SCME

The rule of conduct for SCME is applicable

Core

N/A

ESDER_BRQ151 The system will no longer require the tracking of the number of pre-defined resources available per SubLap. Pre-defined resources will be created on-demand when requested through the established PDR/RDRR resource management GRDT process.

Core

DRRS

mailto:[email protected]

Program Office



Technology

Template Version: 4





Requirement Type


Impacted

ESDER_BRQ152 Pre-defined resource ID selection will be maintained.

Current pre-defined resource IDs associated to a DRP will continue to be made available for their selection.

The system shall make available resource IDs that are associated with active and inactive resource IDs for selection by the DRP.

PDR resource ID is created by the PDR coordinator and provided to the DRP.

Naming convention should identify DRPID and SubLap using the following naming convention:

<sublap name>_<DRPid>_<PDRP/RDRRxxx>

Core

Existing functionality

DRRS

4.4 Business Process: Market Monitoring and Reporting


ID# Business Feature Requirement Type

Application(s)

Impacted

ESDER_BRQ170

Support ISO monitor DERA GDF:

monitor DERA performance, GDF o Annual process, o ISO Produce report o Decide sample size to request o SCME submit requested DERA

pnode meter for the whole year by 5 minute interval

ISO IT infrastructure must support SCME of DERA and PDR to submit data upon requests through secured site and store the data that can be retrieved.

Core N/A

Documents

Business Requirements Specification - California ISO · Template Version: 4 Document Version: ... Clarification about how ISO uses state of charge ... Business Requirements Specification