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
Amy would also like a reminder about this to be sent prior to the PAs submitting files.
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.
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.
Integration Method: The dashboard will likely be embedded in CEDARS using an iframe or a direct URL link. Public Access: The page will be publicly available without authentication, as the data is considered public information. Placement: The initial preference is to place the visual on the data tab within CEDARS. Testing Path: The integration will be tested in CEDARS 2 before moving to production.
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.
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.
Custom memo area, modeled similarly to ex-ante memos, to capture guidance for early opinions.
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.
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."
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.
Business Justification: New DEER Delivery Types have been introduced for Program Year 2026 and must be incorporated into existing CEDARS data validation rules and business logic. This enhancement will ensure accurate validation, processing, and reporting of 2026+ claims while maintaining compatibility with legacy delivery types used for pre-2026 program years. Request Update all applicable CEDARS data rules and validations (e.g., DATE rules and other delivery type-dependent validations) to incorporate the new DEER Delivery Types. Ensure the new delivery types are supported for Program Year 2026 and future years. Maintain compatibility with the legacy delivery types for pre-2026 program years to avoid impacts on historical data and reporting. Review all rules, calculations, and reporting logic that reference delivery type values and update them as needed.
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.
As a user of the Load Shapes Library, I want to export the library table to CSV or Excel, so that I can more easily search, filter, and review the full list of load shapes outside the application. Description Add an export function that lets users download the load shape library table (currently containing thousands of entries) as a CSV or Excel file, since searching/filtering within the current table interface is difficult at this volume.
Some eTRM records may reference a draft_measure_package_id that does not have a corresponding draft Measure Package record. When this occurs: Skip the affected Measure Package and continue syncing valid Measure Packages. Show the skipped Measure Package on the eTRM Sync History page being released as part of @Improve eTRM Sync Resilience for Invalid Measure Package Data. Include the reason it was skipped, for example: draft_measure_package_id referenced in impact_profiles_latestpermutation was not found in impact_profiles_draftmeasurepackage.
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.
As a Measure Developer, I want CEDARS to accommodate measures with equal base and measure UECs so that future load-shifting measures can represent changes in consumption timing even when there are no overall energy savings. Investigate support for load-shifting scenarios where base and measure UECs are equal. Current calculations can result in a 0/0 condition, and supporting this may require changes to Impact Profile generation, avoided cost, and TSB calculations. Eligibility requirements for deemed measures also need stakeholder discussion.
As a Program Administrator and someones reviewing claims data, I want Claim.ClaimType to only accept valid claim type values, so that claim data remains consistent and invalid values are prevented from being submitted. The Claim.ClaimType field is intended to only accept the values defined in the Claim Specification Value List: Deemed Custom Currently, no validation is applied to this field. As a result, Program Administrators have been able to submit unsupported values (for example, NMEC), leading to inconsistent data. Update validation so that Claim.ClaimType must match one of the values defined in the Claim Specification Value List. Field Claim.ClaimType Reference Value List: https://cedars.cpuc.ca.gov/claims/specification/values-list/claim-type/