Skip to main content

Welcome to the CEDARS feedback portal

Using our feedback portal, you can:

  • Share feedback to help us improve CEDARS and the CET

  • Request new features

  • Submit bug reports

  • Ask questions not covered in the user guide

In Progress

Stakeholder code review for generating avoided cost data from impact profiles

Jake R asked to review the code that generates avoided cost data from impact profiles. We produced and shared the attached document. Generating quarterly avoided costs for the CET.pdf

cedars team1 hour ago

CET avoided cost version update: 2028 version gas cost tables

Use the gas avoided cost calculator to produce the 2028 gas avoided costs for the CET. Provide the data for PA review ahead of the CET release.

12026CET

How should NRLease_Flag be populated on residential MFMH claims? Practice differs across PAs

I'm a researcher using the 2025 record-level claims data, and I've noticed that PAs populate NRLease_Flag differently on residential multifamily/mobile-home claims. Among the 2025 claims with ResMFMH_Flag = True, NRLease_Flag is True on every claim from SCE's non-statewide programs (e.g. SCE_3P_2024R_MF_001, SCE-13-SW-001G), SoCalREN (SCR-RES-A1, A5) and almost every claim from Tri-County REN (TCR-Res-002). It is False on every MFMH claim from SoCalGas, SDG&E, PG&E, BayREN and MCE, and on all statewide program claims. The data rules describe NRLease_Flag as identifying measures "installed at locations that are leased or rented", and it appears only in the nonresidential HTR pathways. ResMFMH_Flag already identifies MF/MH dwellings "where tenants rent or lease the dwelling". Could you clarify: 1. Is NRLease_Flag meant to be populated only for nonresidential claims, or also for residential claims where the dwelling is rented? 2. For optional flags such as NRLease_Flag, HTR_Flag and ResMFMH_Flag, does a False value in the record-level download mean "not applicable / not verified" or "verified not applicable"? 3. Is there any PA-level documentation of how these eligibility flags are populated? Thank you!

Vivek Narayan3 days ago
Planned

Provide a download of PDA and PSR data

(plus attachments and comments)

Nov 132026

Process 2026 YR PII submissions

The PA 2026 YR submission is due 5/3; the PII handoff to the Guidehouse team is due 5/18.

Process 2026 Q4 PII submissions

The Q4 PA deadline is 3/1; the deadline to handoff the data to the Guidehouse team is 3/17.

Planned

Process 2026 Q3 PII submissions

Q3 PII submissions are due Dec 4; the handoff to the Guidehouse team is due Dec 18.

Dec 182026

Other Cost Output & Formula

What's included in the Other Cost field in the CET Outputs file? See column DG below. What is the formula for this output?

Klarson_AVA13 days ago
On Hold

Plan for PDA and PSR future

Update from Amy that Jon has a new solution ready and will be sharing it.

Planned

Update the IQP dashboard on the Data tab

The IQP team has a new PBI dashboard ready to be deployed to CEDARS. Their requested production deadline is the week of Nov 9th, with review and approval on cedars-2 beforehand.

cedars team14 days ago
1

Exclude From Budget/CE Flagged Programs Record Level Data

CEDARS should not remove calculated values for programs with exclude from budget or exclude from CE in the record level downloads - the full data should be available and PAs apply the flags appropriately when filtering for specific values. Zeroing them out removes transparency in what was being excluded.

Retention policy and managing obsolete Load Shapes/Impact Profiles

When a measure package's TechIDs change after load shapes/impact profiles have already been uploaded, the original ("obsolete") upload data remains in Cedars even though it will never be used. We need a documented best practice for whether these obsolete uploads should be deleted or retained. Background/Example For SWCR018, load shapes were initially uploaded (Upload 447) using the original TechIDs for a non-modeled measure package, but with values borrowed from a modeled measure package (SWCR015). Following further discussion, it was decided that the TechIDs from the modeled measure package should be used instead, resulting in a new upload (Upload 453). As a result: Upload 453 will be the load shapes/impact profiles actually used going forward. Upload 447 is now obsolete and will never be used. Problem There is currently no defined process for handling obsolete uploads. Leaving unused, obsolete load shapes and impact profiles in the system risks: Duplication of records Confusion between correct and incorrect/outdated load shapes Potential for the wrong upload to be referenced downstream Questions for Discussion Should obsolete uploads be deleted outright, or is there a preferred archiving/flagging mechanism instead? Is there a technical or audit-trail reason to retain obsolete uploads? If deletion is the agreed approach, who is responsible for performing it β€” the original uploader or anyone on their team?

cedars team2 months ago
52026Impact Profiles & Load Shapes

Add 2023–2025 Statewide Claims "Record-level Measure Input and Cost Effectiveness Output" files to Data tab

The Statewide Claims "Record-level Measure Input and Cost Effectiveness Output" file was added for 2026 to the record-level data page. Equivalent files already exist for 2023–2025 on the Statewide confirmed dashboard, but they are not yet surfaced on the record-level Data tab for those years.

cedars team2 months ago
Design UpgradeClaim SpecData Tab

SW Budget Filing Inputs Download

Other IOUs should be able to download the SW budget filing input zip files for the programs they don’t lead from CEDARS. Currently we can only download files uploaded by our own PA. There is no PII in budget filings, this would allow us to easily get the inputs from the other leads.

2026Budget Filings

Impact Profile download – Field should be "Published Date"

To be more inclusive of DEER and Load shape derived impact profiles. https://cedars.cpuc.ca.gov/impact-profiles/

cedars team3 months ago
Design UpgradeImpact Profiles & Load Shapes

How long do we want CEDARS to hold onto CET output files?

Question for the data reporting PCG: The CET module was added to CEDARS in 2018 and to date more than 120K CET runs have been done in production. We currently keep CET input/output files from runs indefinitely. It would help us plan for future disk size updates to know if we want to continue to keep all files and make them available to the person who uploaded them indefinitely, or if we want to set a window where files uploaded more than X years ago are deleted.

cedars team3 months ago
1