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
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
Update includes: Rename forecast fields to "Annual Forecast" Correct tooltip typos and other formatting issues Refresh the data
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.
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!
Amy would also like a reminder about this to be sent prior to the PAs submitting files.
The PA 2026 YR submission is due 5/3; the PII handoff to the Guidehouse team is due 5/18.
The Q4 PA deadline is 3/1; the deadline to handoff the data to the Guidehouse team is 3/17.
Q3 PII submissions are due Dec 4; the handoff to the Guidehouse team is due Dec 18.
What's included in the Other Cost field in the CET Outputs file? See column DG below. What is the formula for this output?
Update from Amy that Jon has a new solution ready and will be sharing it.
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.
Right now the upload summary only shows the number or load shapes replaced. The upload results should match how impact profile results already work in QC summary, where new profiles and replaced profiles are displayed. After upload, the results list each load shape as New, Replaced, or Unchanged.
Write the PA submitted files into it.
I have a question about how the 2024 ACC Electric Model v1b feeds into the CET. When running the excel model, should the 8760 values for the Total Levelized Value sum up to the Total System Benefit for that specific scenario when run through the CET? How are the quarterly avoided costs derived from the 8760 hours of avoided cost? If there are more resources available on how the ACC informs the CET outputs, please let me know. Thank you!
Users need to have clear timestamps to know which data to grab. Use case: Yamini wasn’t aware that the 2026-7 MCAL data they used in the dashboards was out of date, and said that there was no way to ID the correct data version/no timestamp in the file.
Perhaps a way to help users know when data changes might be by having all data updates trigger automatic notifications. Recent use case: Yamini wasn’t aware of updates to the MCAL data and thus used an outdated data set in the dashboards. Could we discuss whether this is a good enhancement for 2027, or if it belongs in modernization?
Calculation traceability: Storing the exact eTRM MP/version and source permutation record(s), source snapshot, baseline and measure load-shape versions, and annual UECs actually used to generate each profile. Link these to the resulting Impact Profile ID, climate zone, baseline type, and generation timestamp/version. The original calculation inputs should remain recoverable if possible even after subsequent eTRM updates or load-shape uploads.