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

Fix user interface for profile drop-down

When selecting your profile, the background color on the drop-down options (Manage Profile, Notifications, and Log Out) are the same as the text color. Users can currently only see the text when hovering over.

Fix Impact Profile Library table header colors

Fix the color on the table headers for E3 Mea Elec End Use Shape and Upload PA on the Impact Profile Library page.

Design UpgradeImpact Profiles & Load Shapes
Planned

Add TOU impact profiles to the CEDARS library

As a CET user, I want TOU impact profiles included in the CEDARS library so the TOU avoided costs can be generated using the same code pipeline as the DEER, Custom, and load-shape-derived impact profiles. The TOU impact profiles will be used to correct the CET TOU avoided costs for the 2026 version and to create TOU avoided costs for the 2028 version. For clarity, we also want to add “Time of Use” as a source impact type and ensure that all TOU impact profiles are marked accordingly.

Planned

CET avoided cost version update: 2028 version utility rate tables

Required CET data update alongside the 2028 version avoided cost data. Each PA provides the data for their organization and the CEDARS team compiles them into the CET database rate schedule tables.

Oct 29

CET: Discounting is being handled inconsistently in RIM bill reduction and bill increase calcuations

I was asked to provide plan language explanations of the four bill reduction and bill increase calculations done in the CET for the RIM test and while reviewing that code, saw two ways the discounting rate is being applied. Discounting is inconsistent between the first baseline and the rest. The first baseline divides by Raf^(Qy−Yr1), which discounts back to the first year. Every other slice divides by Raf^Qy, which discounts back to the 2024 base year (Yr1 is the claim year minus 2024). It appears to be a bug that the first-baseline slice is on a different time basis. I believe all of the code time blocks should discount back to the first year.

Custom memo area

Custom memo area, modeled similarly to ex-ante memos, to capture guidance for early opinions.

MCE EE Portfolio Dashboard Feedback

In the Cost Effectiveness tab the Forecasted values for Commercial on CEDARS2 shows 1.06 but CEDARS shows 1.14, Cross Cutting 0.35 v 0.41. Some values in the budget and expenditures tab are off by 1 (most likely some rounding issue).

3Data Tab

RRN CEDARS-2 EE Portfolio and Metrics Dashboard Testing

The TSB in the data dashboard is correct, but for the metrics, they are all different than what we reported in 2025. There also is not 2026 data.

6Data Tab

IREN EE Portfolio and Metrics Dashboard Testing

For IREN Portfolio Dashboard, in the Budget and Expenditures tab, the cross-cutting total expenditures on CEDARS2 is $1,481,296 and on CEDARS it's $2,043,688. For the Metrics Dashboard, there is no 2026 data showing but it was reported.

2Data Tab
Planned

Unprocessed Q1-Q2 Claims for MCE

During the Quantum Feedback for Q1-Q2 Claims, there was a note that some of the claims were unable to be processed due to an error with the CET. Looking to finding out why there was not CET output for these claims

Missing Measure Detail ID

The following Measure Detail ID is missing from the CEDARS Value List: SWHC046-06-BN-NR-Down-Com-OfS-Ex-cDXHP-CZ12-FuelSubst-Default-Def-GSIA-Any-Any

In Progress

Add page for DEER 2028

Per request from Sepi and Peter.

In Testing

Publish updated EE portfolio metrics 🔥

Including 2026 Q2 claims and budget refiling. First draft live on cedars-2 by Tuesday Oct 6 for review ahead of the Oct 7 dev demo. Second draft shared Friday Oct 16, up on cedars-2 for review and sign off.

Planned

Metrics and Indicators Part 2 - 2026 Claim

As a Cedars user, I want the remaining metrics and indicators available with clear names, sector and quarter, so that I can filter and compare results without needing to interpret raw field names. Part two of the metrics and indicators work. Part one delivered the initial set of metrics; this ticket covers the remaining metrics that can be derived from data already held within Cedars, and adds friendly names, sector and quarter so they're easier to find, read and compare.

Jan 29

Non-DEER Impact profiles download issue

Several non-DEER impact profile CSV files include missing data that require review.

12026Impact Profiles & Load Shapes

As a CEDARS claims reviewer, I want Measure.FuelID to be required in the 2027 claims spec, so that fuel substitution claims always go through fuel substitution validation

During 2026 Q1–Q2 QC, Corina found that many PY2026 fuel substitution measures are missing a Fuel ID and still pass CEDARS validation. Fuel substitution is no longer flagged in Delivery Type, so these claims now skip the fuel substitution logic whenever neither Fuel ID nor Measure Impact Type flags them. Roopa confirmed that validation uses Fuel ID when it is filled in and falls back to Measure Impact Type when it isn't. This ticket tightens Fuel ID validation for the 2027 claims spec and accounts for legacy measure packages that were built without a Fuel ID. "In the Q1-2 QC, we notice that, since Fuel Sub is no longer specified in the Delivery Type, many Fuel Sub measures are lacking FuelIDs and getting through the CEDARS validation process when we think they should have been errored."

Claim Spec20272027 Claim Spec Update Queue

SoCalREN 2025 data correction

SoCalREN discovered that some expenditures from 2025 were miscategorized and would like CEDARS to reflect the correct categorization. The total amounts are correct and do not need to be changed.

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.