Development Plan 2026

Remove the review step "Approve 2024 Budget Filing" button

Remove the "Approve 2024 Budget Filing" button. Once the budget data passes quality checks and is marked as complete, it should automatically be considered accepted and "Approved," eliminating the need for Amy to approve each filing manually.

Budget filings: Update specification to new claim-style pages

To have the new data specification pages including metadata descriptions for each field in the new easy to view format currently used in claims. Identified and requested by PG&E.

CEDARS & CET calculations: Add documentation

As a PA, I want the documentation for formulas utilized throughout the CEDARS site and CET to be updated and published to CEDARS So that users have the most up to date formula information available. Identified and requested by SDGE Per 10/3 ADP meeting - It’s putting in clearer language for all the formulas and what calculates all the different fields in CEDARS so that you can trace back and somebody who doesn't have a mathematics background can figure out what the calculation is. Also to include a formalized CET reference document that is up to date and again, includes the calculations, etc.

CEDARS Email: Confirm Report Upload/CEDARS To Send Email Reminders

As a PA I want an email from CEDARS confirming when a document is uploaded So that I have a record of the document upload and I do not have to take a screenshot of the downloaded zip file with the date as my record. Identified and requested by SCE. Additional context for the ask per 10/3 ADP meeting: Current state: PA has to go into the document, look when it was uploaded, screen shot the date as proof of upload. This effort would be a regulatory solve.

Statewide Module Implemented With CET

As a PA I want to have the statewide module implemented with the CET user interface so that PA's can track TSP Goals. Identified and requested by PG&E. Per the 10/3 ADP meeting, additional notes about this request: When PGE gets the CET forecast for state line programs and when they’re doing their internal forecast to assess if they will make their goal, they have to manually allocate that to just the PGE portion. They’re wanting to get allocated outputs from the CET for the statewide programs.

Data tab: Make pre-2016 and evaluation data available for download

As a PA, I want to review data from before CEDARS was online and also evaluation data. These data could be available for download at the measure level in the data tab.

Allow users to reference load shapes in their CET input data instead of impact profiles

This would eliminate the need to pre-calculate impact profiles for every possible combination of load shapes in advance. This would also allow dual baseline measures to use the correct impact profile for the early retirement phase and the above standard phase of their measure, instead of having to use one impact profile for both baselines as the CET works currently.

Remove NormUnit from load shape 8760 upload specification

Per request to align with the energy plus post processing script

Budget Filing Dashboards – Add Toggle to Exclude ESA Savings from Segment, Sector, and Program Summaries

Add an “Exclude Energy Savings Assistance (ESA)” toggle to the Budget Filing Dashboard tables, similar to the existing ESA toggle in the Claims module. Timeline / Priority: Ideally implemented before 2028–2031 Budget Filings. Applicable to 2026 and 2027 filings for verification and consistency. Problem it solves: “For 2026 and 2027, the TSB, Net kWh, Net kW, Net Therm, Gross kWh, Gross kW, and Gross Therm values include ESA program data at the segment, sector and program levels which should not be part of this filing.”

CET Simplification

Goals Eliminate renaming fields within CET calculations Simplify the CET code Improve version control Improve code availability Stop doing the same calculation multiple times Make the code more accessible to users Reduce the time it takes to calculate cost effectiveness Improve our ability to run multiple data inputs at the same time Ensure future code updates can be made efficiently Requirements Updated code will produce the same outputs as the current CET (v25.1) Updated code will be publicly available in a GitHub repository Ensure that all required inputs are clearly identified … Approach The CET has four primary scripts that calculate outputs: Savings Costs Cost effectiveness Emissions We propose to simplify the savings equations (the CalcSavings stored procedure in the current CET) first. Questions Do we want to continue to group equations like the current CET does, i.e. Savings, Costs, CE, and Emissions? …

Data tab: Improve Accessibility of Large Record-Level Files

As a user, I want to be able to access the files easily on my device without running into performance issues or file size limitations,so that I can efficiently review a PA’s entire portfolio and analyze all necessary records without technical interruptions. Acceptance Criteria File Accessibility Large files, such as the SDG&E record-level file, are broken down or optimized to a size that can be opened on common user devices. A recommended file size limit is set (e.g., 1GB for Excel compatibility), though this may vary based on testing and device specifications. Consistent Record Availability Files are structured in a way that maintains ease of searching and comprehensive access to a PA’s portfolio within a manageable number of files. Clear Communication on File Structure Documentation or guidance is provided to inform users of any new file structures, including rationale for split files, compression, or access methods.

Update Error Messages - Improve Error Communication

As a PA I want all error messages to identify the error and also provide the solution for fixing the error so that I dont have to guess at the solution or inadvertently create additional errors in their re-submission. Identified and requested by Frontier Energy, Marin Clean Energy, Peninsula Clean Energy, Sonoma Clean Power, SoCal Re (LA County), Bay Area Metro and Redwood Clean Energy. Per our 10-3-24 ADP meeting: Create a file of the different error messages that CEDARS has and then focus group it with these users and edit per discussion with users. Need to review the validation errors and warnings messaging

Program fund shifts: Expand functionality

Enable fund shifting between statewide programs As a Statewide Program Administrator, I want to enable fund shifting between statewide programs in CEDARS so that I can efficiently manage budget adjustments similar to how it's done in local monthly reports. PAs are allowed to move funds between programs; CEDARS has functionality to manage fund shifts in the PA local monthly reports module. Fund shift dollars are expected to sum to zero for each PA and are added to or subtracted from to the forecast filing budget to produce the revised operating budget for each program for each year. No equivalent functionality exists for statewide programs. If statewide programs need to report fund shifts to CEDARS we need to build functionality to allow them to do so. Allow Fund Shifts Between Programs in Different Program Years As a PA, I would like the to have the flexibility to fund shift between programs in different program years. For example, • Move funds from one year to a future year. • Move funds from a future year to the current year. Right now, the ability to fund shift within CEDARS is only currently available between programs in the current active program year. Having this functionality in CEDARS would support more transparency between the IOUs when conducting these activities. This enhancement would affect Reporting, more significantly the Annual Report template. Improve presentation of program revised operating budgets As a PA, I want to see dashboards updated in real time when funds shift between programs.

Monthly reports: Allow Excel spreadsheets to be uploaded

As a program administrator, I want to upload Excel spreadsheets (like we do in the claims module) for monthly reports to streamline data submissions. As a CEDARS user, I want to upload Excel spreadsheets to the CET so that there is less of a data preparation hurdle to run my data. Adding Excel for CET and Budget Filings carved off into their own ticket.

Cost Effectiveness Module - Dashboard For Results

As a PA I want to have a dashboard within the Cost Effectiveness Module to run results and various scenarios So that I dont have to download a file and manipulate the data from the file and outside of CEDARS. Identified and requested by SDGE Additional context for this request per the discussion at the 10/3 ADP meeting: Idea is that a user could do various scenarios and runs without having to keep re uploading the same file over and over again

Create Central Repository For All Templates

As a PA, I want all templates in a central repository so that they are easy to access from one location.’ Identified and requested by Marin Clean Energy and SoCal REN (LA County)

Data Tables/dashboards in CEDARS

There are ways in Java to enhance the tables in CEDARS to make them easier to use: DataTables | Javascript table library I would like several of these interaction controls deployed on the site tables.

ACC Definitions And Values - Interpreting The Values For Users

As a PA I want to see the Avoided Cost Combinations and their values and what fields feed the calculator so that when I get an error, I can determine what combination was wrong and is creating an error message. Requested by Frontier Energy and Peninsula Clean Energy

Improve CET run speeds

Reduce the amount of time users are waiting for CET results for the claim, budget filing, and CET modules.

Automate end of year reconciliation of monthly report and claim cost and savings

Reconciliation is done manually currently. The checks could be automated and integrated into the end-of-year data submissions to eliminate the need for PA re-openings and re-submissions after the May 1 YR deadline. As a program administrator, I want the end-of-year reconciliation of monthly report and claim cost and savings to be automated, so that the process is more efficient and reduces the need for manual re-openings and re-submissions after YR deadline.

Improve claim data processing speeds

CMPA for SEM: Must change the workflow for when the system issues Application_IDs for SEM Projects

The SEM team wants to change the logic surrounding when SEM projects receive the Application_ID. Currently, when projects are released (wither because review was waived, or because review was completed for selected projects) they receive the ID, but we want to have the system provide an ID up-front. Sometimes SEM projects get stuck in a review cycle that prohibits CEDARS from accepting them without an App_ID. So, we need App IDs, and we no longer need the requirement where projects selected for review must wait until afterwards to have an ID assigned. I hope this makes sense; if not, please reach out, as we probably need this for 2025.

2026 Avoided Cost Calculator Update

The CET will require ACC table updates when the ACC updates are finalized in Q4.2026. There will undoubtedly be subtasks; this ticket is essentially a placeholder.

Add the PCT test to the CET

Needed 1/1/2027 per draft VEA

CET: Provide metadata for outputs

As a user, I want CEDARS to provide metadata and descriptions for CET output fields so that I can easily understand and utilize the data without confusion. Description: CEDARS currently only provides metadata to describe data PAs submit; the CET output fields are not similarly described for users. Multiple users (PAs and others) have requested Cedars offer a data dictionary/metadata field description for the CET output fields. Program administrators and other users need clear definitions and context for CET output fields to interpret the data accurately and efficiently. Currently, this information is lacking, which can lead to misunderstandings and misinterpretations.

Load Shape User Guide

As a Measure Developer or Program Administrator, I want clear documentation explaining how to use the Load Shape Library tool, so that I can correctly prepare, upload, load shapes.

Participant Table - Statewide Participant Reporting

During discussion of the new Participant table, a potential limitation was identified by Gary Golden for statewide program reporting. Unlike IOU-administered programs, statewide programs may serve participants across multiple utility territories. In these cases, the Program ID alone is not sufficient to determine which utility should receive credit for a participant in statewide reporting. The current Participant table structure does not fully support scenarios where a participant may need to be associated with one or more utility service territories for statewide reporting purposes. As a result, certain statewide metrics and reporting queries may not be able to accurately attribute participants to the appropriate IOUs.

Export Hourly Data for a Specific Load Shape

It would be useful to add two separate functions to the load shape library for current/future users, particularly if the functionality of the load shape process allows for load shapes to be used between measure package (as is planned). First, it would be good to be able to export the library table itself as a csv or excel file. We have thousands of load shapes now, and searching/filtering in the current table can be challenging. Being able to export to excel and review there would be helpful. Second, being able to export the actual hourly data for a specific load shape in the library. This would be important for users who want to adopt load shapes between measure packages, or use them for other purposes, such as billing impact or other hourly analysis.

Allow measure packages to share load shapes

Schedule CEDARS Budget Filing Correction for AVA (EBCE)

This item has been discussed with Amy Reardon and Pam Rittelmeyer. AVA’s program is closing out in May 2026 and to meet future reporting requirements and to align with a past program budget change, 2023-2025 total budget amounts will need to be updated. We are preparing new files to upload the data and will need to schedule time to make the updates, preferably before the upcoming Annual Report (4/15) deadline. It is also important to note AVA was previously called EBCE in 2023.

CET User Guide - Improvements to Fuel Sub guidance

https://cedars.cpuc.ca.gov/cet_ui/cet-user-guide/

When is the best time for IQP testing on CEDARS-2?

We are expecting to receive a replacement dashboard soon for review and is requested to be available on cedars-2 for several weeks.

RRN Budget Filing Correction for 2025

In preparation of the 2025 Annual Report, an error in RRN 2025 budget values was identified. Unfortunately, the entered RA portfolio budget ($6,174) and CS Portfolio budget ($131,806) should be switched. The total 2025 budget remains the same. Would it be possible to switch these values in CEDARS? Also, for Annual Report submittal, is there anything additional we should note? We will report the correction within the workbook and narrative.

New review team file download

Request from Peter B’s team. New impact profile file for download that includes: a.  Impact Profile ID / E3MeaElecEndUseShape b.  PA / IOU c.  E3TargetSector d.  E3ClimateZone e.  avoided-cost version f.   avoided-cost combination ID / AC Elec Key g.  BldgType h.  BldgVint i.   BldgHVAC j.   Measure TechID k.  Baseline TechID l.   TechGroup and TechType, where applicable m. first-baseline vs second-baseline indicator, if applicable n.  source year/calendar used, e.g. 2009 non-leap Thursday-start o.  baseline load-shape ID used p.  measure load-shape ID used q.  baseline annual UEC used r.   measure annual UEC used s.  denominator/savings used in the impact formula t.   validation status/results u.  generation timestamp v. eTRM measure package ID w. eTRM permutation ID x. eTRM source snapshot/extract timestamp And also provides additional files containing: 1. baseline load-shape 8760 csv 2. measure load-shape 8760 csv Please give files descriptive names that include the Impact Profile ID or AC Elec Key.

Duplicate Hour in Impact Profile Exports

Load shapes Impact Profile export 8759 unique hours instead of 8760 — one hour appears twice while another is missing entirely, resulting in the output still containing 8,760 rows but with a duplicated hour timestamp rather than a duplicated impact value. Specifically, hour 1587 is missing and hour 1588 appears twice. Likely related to daylight saving time handling.

Latest CET database snapshot file appears invalid

I downloaded the latest CET database file from CEDARS, “2025 CET Database Version 25.1 - 26 June 2026 release,” and it won’t run when loaded into our internal CET SQL Server instance. The database structure contains references to an E3AvoidedCostElecCO2Seq2027 table but that table does not exist. I did see there was a new 2026corrected table and I tried adjusting and using that instead, but it didn’t work. Am I missing something or could there be an issue with the database snapshot currently on CEDARS? Is it possible to get an updated snapshot/export?

Understand how FuelID affects CET outputs

On behalf of BayREN, I’d like clarity on how populating the Measure table FuelID field affects CET outputs for fuel sub measures. In claims reporting, my team is considering using this field to identify all fuel sub claims because some fuel sub measure packages don’t use the fuel sub measure impact type values by default. With the Q1-Q2 claims we’ve filed, including/removing the fuel sub FuelID for only one fuel sub claim (using measure SWHC044-07) affected CET outputs (TRC, PAC, RIM, SCT, ElecBens). We don’t understand why this is the case and whether we should expect similar results for other fuel sub claims. For reference, I’ve attached our analysis comparing FuelID vs. no FuelID, along with a copy of the claims file with FuelID populated for BAYREN02 (the program in the Q2 submission containing fuel sub claims).

Participant Output issue with SW programs

Not sure if this was brought up before while I was out. When downloading the SW claims output from the SW Confirmed Dashboard, the Participant Output only includes the SCG programs which were the last group to upload. I think the overriding of the previous Participant Table uploads needs to be PA specific for SW

Access to prior CET versions

As an evaluator for the CPUC, I need to run evaluation data updates through the CET. However, this requires that the CET for that year be available with the correct specification and other database requirements. Alternatively, we need an efficient way to run CETs for prior versions. It needn’t be in production; at this stage we need the most straightforward pathway. If CET access needs to be limited in scope, then we can provide you with the year(s) for which we need access to an old CET version. Please contact me, Corina Jump, and Rachel Harcharik to discuss. Thank you!

Metrics and Indicators subset - 2026 Claim Q1/Q2

For the initial release, allow users to download a .csv file for each PA similar to the Excel spreadsheet used for 2025 with the metric and indicators listed by index.

Deemed Measure Load Shape Repository

As a consultant to the CPUC, DNV is leading the effort to create a library of deemed measure load shapes on CEDARS. This is needed to enable the measure package developers and PAs to upload 2-3 load shapes for each deemed measure permutation in the eTRM for PY2028. These load shapes will be used to determine the quarterly avoided costs for each deemed measure claim as an input to the CET. It will be important to leverage the viewing/calculation capabilities that were developed for the impact profile library. We think there will also be a need to have a second sandbox library that would enable measure package developers to upload load shapes pertinent to a given measure package in preparation for their CET runs. This will need to be ready for use by measure package developers by mid-late spring 2026. This effort is intended to enable the replacement of the legacy DEER load shapes--many of which may no longer accurately represent the hourly distribution of savings--to improve the accuracy of the TSB and TRC of deemed measure.

Add ParticipantID to claim table

For SEM in particular, to allow linking between multi-year claims for a single participant. Also include complete SEM Reporting Guidance, including the requirement to file a no-savings claim in the year there is no activity. Table: Claim Field Name: ParticipantID Description: Identifier used by PAs to track all SEM activities and claims for a participant across the full program engagement, including core cycles and any graduate cycle. This ID is needed in tracking data to consistently link related SEM records over time.(e.g., FPCx.00 or 7999.P0) Data Type: Text (up to 255 characters) Required: N Rules: Required for SEM Claims

Claims IDSM field removal

Claims IDSM fields removal As a user, I would like the IDSM fields introduced in the 2024 Claim Specification update to be removed from Claims reporting, as there is currently insufficient guidance on how to populate them and limited value in collecting them in their current form. Fields for removal: Claim.IDSM_DR Claim.IDSM_DER Background: Definitions and intended reporting requirements for these fields remain unclear. It is unclear which values should be entered and whether they pertain to incentives, costs, benefits, or other metrics. Current reporting pathways do not adequately support meaningful or consistent use of these fields. Proposed outcome: Remove both fields from the Claims Specification. Consider alternative IDSM reporting, such as annual narrative reporting.

Load Shapes – Version control between eTRM & Cedars

As a Measure Package Developer, I want CEDARS and eTRM to consistently handle revisions to draft measure packages that affect load shape identifying fields, so that I can update measure package permutations during review without creating duplicate, orphaned, or incorrectly associated load shapes. Description Measure developers regularly update draft measure packages throughout the ex-ante review process. These updates may change fields that are currently used by CEDARS to identify, match, and reuse load shapes. Example: A measure developer updates one or more load shape-related permutation fields in eTRM (e.g. TechID, Building Type, Building Vintage, HVAC Type, Climate Zone). The updated measure package may no longer match the previously uploaded load shape records. The current MVP supports re-uploading load shapes when a measure is re-modeled and assumes replacement based on load shape identifying fields. However, the long-term versioning strategy between eTRM measure package revisions and CEDARS load shape records has not been defined.

Claim.HTR_Flag if true other flags are required to be true

Draft valid combinations of Claim.HTR_Flag = true based on HTR CEDARS.docx Option A: CA_Flag path Claim.HTR_Flag = true + Claim.CA_Flag = true Option B: Geographic path Claim.HTR_Flag = true + (Claim.OMBCSA_Flag OR Claim.CalEPA_Flag) = true + 1 other remaining flag = true Non-Res (Claim.DEER_Sector = Com, Ind, Ag) remaining flags: Claim.Lang_Flag, Claim.NRSize_Flag, Claim.NRLease_Flag, Claim.LG_Flag Res (Claim.DEER_Sector = Res) remaining flags: Claim.Lang_Flag, Claim.ResLI_Flag, Claim.ResMFMH_Flag Option C: Any 3 of the remaining flags = true Non-Res (Claim.DEER_Sector = Com, Ind, Ag) remaining flags: Claim.Lang_Flag, Claim.NRSize_Flag, Claim.NRLease_Flag, Res (Claim.DEER_Sector = Res) remaining flags: Claim.Lang_Flag, Claim.ResLI_Flag, Claim.ResMFMH_Flag Design mockup: https://www.figma.com/proto/djSwjUOnQmtJGgHy5wcHbk/Claim-Specification-Update-2026?node-id=6611-2898&viewport=-1119%2C479%2C0.13&t=8RsCmH7VPF8ekkHP-1&scaling=min-zoom&content-scaling=fixed&starting-point-node-id=6827%3A2341&desktop-link-click-timestamp=1778106748421&desktop-ul-exp-bucket=V&page-id=6601%3A2827 Flag Descriptions Field descriptions and location Move all relevant HTR fields together in Claim Spec and update descriptions. Listed in order: HTR_Flag As is: Hard to Reach. Flag to identify the measure was installed in a hard to reach location. To be: Indicates the claims is being reported as Hard to Reach. The claim must satisfy one of the valid Hard to Reach qualification pathways. Hard to Reach participant counts are included in the Participant table. CA_Flag As is: Flag to identify Cultural Accessibility - HTR (Hard to reach). To. be: Flag to identify Cultural Accessibility. It identifies California Native American Tribes as hard to reach. Tribal customers qualify independently under Commission policy and do not need to meet additional Hard-to-Reach (HTR) criteria. Lang_Flag As is: Language. Meets language barrier for hard to reach. To be: Flag to identify customers where the primary language spoken is other than English. Contributes to Hard-to-Reach (HTR) eligibility. OMBCSA_Flag As is: United States Office of Management and Budget. Flag to identify measures installed in a zip code outside of defined US Office of Management & Budget statistical areas for hard to reach. To be: Flag to identify measures installed at customer premises located outside the United States Office of Management and Budget (OMB) Combined Statistical Areas of the San Francisco Bay Area, Greater Los Angeles Area, and Greater Sacramento Area, a

Add new table and fields to track participant type and number of participants

Reporting at the program level is preferred over Claims as it’s less complex. Unique Pop NMEC could also be reported. Will be reported as a CSV zipped with the record-level downloads on the data tab Inline guidance and user guide will need to be updated. Design mockup - Draft Table name: Participant Primary Key Primary key: Participant.PrgID + Participant.PrgYear + Participant.ParticipantType + Participant.SiteID Table validation check e.g. That the primary key is unique regardless of the letter case. Relationship validation Participant.PrgID must match a ProgramCost.PrgID Participant.SiteID, when populated, must match a Site.SiteID Fields PrgID Data type: Text (up to 255 characters) Required: Y Description: The unique program identifier; joins to the ProgramCost table. PrgYear Data type: Integer Required: Y ParticipantType Data type: Text Required: Y Valuelist ParticipantCount Data type: Number (Up to 15 decimal places) Required: Y SiteID Data type: Text EquityTargeted Data type: Number (Up to 15 decimal places) Required: Y DAC Data type: Number (Up to 15 decimal places) Required: Y HTR Data type: Number (Up to 15 decimal places) Required: Y Underserved Data type: Number (Up to 15 decimal places) Required: Y Comments Data type: Text Required: N

Add TCR confirmed claim info button

Add infobutton on the TCR confirmed dashboard that says: “An accounting error in the TCR-Res-002: Multifamily program that impacts the program cost will be corrected in Q1 2026. This will result in a discrepancy in TCR's 2023 and 2024 annual report until the correction is made.”

Business Name in PII Site Table

Add “Company Name” or something similar to the PII Site Table. This would help in the data collection for evaluators and eliminate a separate data request. Sometimes, the Service Account owner isn’t the related to the Business Name (Could be a Trust, Franchise Owner, etc.) and the business name helps the evaluators find the actual business better for contacting. Context: Difficult in Midstream programs to get the right info. —- Field Name: Business Name Description: Actual name of the business where the intervention happened. This is what Google Maps might show for the site address, and is often different than Account Name. Data Type: Text Required: N Rules: Not required for residential. Provide info if known, with the understanding that the rule is being introduced halfway through 2026 so it can’t be expected to be know for all commercial sites.

Add Census Tract to PII Site table

Guidehouse has requested the ability to develop geospatial visualisations of claims data to better understand where Program Administrators (PAs) are active and the relative impact of programs across regions. Intended use cases include assessing market support and equity outcomes. These dashboards would be restricted to CPUC internal use only and would not be public-facing. To enable this capability, a new PII Site table field would be required. A new location-related field would be added to Claims submissions, such as Census Tract. This would represent a new data-collection requirement and require explicit agreement and governance approval. New Field Table: Site PII table Field name: Census Tract Required: Y Data type: 11 characters Description: The census-defined geographic area of the site. Used by CPUC internally to support geospatial analysis of claims data. (Draft) Key Considerations PII and Data Governance PA Data Availability. PG&E has indicated they can provide customer-level location data. RENs and CCAs have indicated they do not currently have this information. Some programs (e.g., PopNMEC, Home Energy Reports, RCTs) submit aggregated claims and cannot be meaningfully associated with customer-level locations.

Data tab and Claims dashboard - Claims Record-level download to include 2026 input and outputs

Add any new input fields from the 2026 claims spec update and the new set of CET v25.1 cost effectiveness outputs to the data tab record-level download for Claims so that the data is accessible for CPUC analysis. Fields to include are: Fuel ID Unit Tax Credits Water Energy Benefits Water Energy Benefits Gross Water Energy Cost Water Energy Cost Gross Electric Bill Reduction Electric Bill Increase Gas Bill Reduction Gas Bill Increase Electric Benefits Gross SCB Electric Benefits Gross SCH Electric Benefits SCB Electric Benefits SCH Electric Supply Cost Gross SCB Electric Supply Cost Gross SCH Electric Supply Cost SCB Electric Supply Cost SCH Gas Benefits Gross SCB Gas Benefits Gross SCH Gas Benefits SCB Gas Benefits SCH Gas Supply Cost Gross SCB Gas Supply Cost Gross SCH Gas Supply Cost SCB Gas Supply Cost SCH RIM Cost No Admin SCB Cost SCB Cost Gross SCB Ratio No Admin SCH Cost SCH Cost Gross SCH Cost No Admin SCH Ratio No Admin Tax Credits Tax Credits Gross Water Energy Benefits Gross SCB Water Energy Benefits Gross SCH Water Energy Benefits SCB Water Energy Benefits SCH Water Energy Cost Gross SCB Water Energy Cost Gross SCH Water Energy Cost SCB Water Energy Cost SCH