Changelog

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

2026 Fixed Development

Add Fuel Sub Infrastructure Cost Fields to Claim Specification

Background: CPUC introduced fuel sub‑infrastructure cost reporting requirements in PY2023 for Kiteworks submission. Although PAs have been submitting these costs to Kiteworks along with the PII Site and Contact data, these requirements have not been incorporated into the claim specification in CEDARS. Ask: Add the fuel sub‑infrastructure cost reporting requirements outlined in the attached CPUC excel template to the claim specification. https://cedars.cpuc.ca.gov/claims/specification/

Roopa Reddy about 9 hours ago

1
📨

Feedback

In Progress

Load Shapes – Investigate Server Error on Cedars-2 After Successful eTRM Validation

Henry reported a server error occurring after the system successfully completes the eTRM validation step on cedars-2. This issue is preventing Henry from being able to prepare documentation for a training session later in the week. FYI, I tried it a few times and watching it closely it made a server error after successfully validating the eTRM portion. The upload progresses through eTRM validation without issue, but then fails with a server error. Draft Measure Package: Medium or Low-Temperature Display Case With Doors https://cedars-2.cpuc.ca.gov/impact-profiles/deemed-load-shapes/upload/6/qc-summary/ https://cedars-2.cpuc.ca.gov/impact-profiles/deemed-load-shapes/upload/5/qc-summary/ https://cedars-2.cpuc.ca.gov/impact-profiles/deemed-load-shapes/upload/4/qc-summary/

cedars team 1 day ago

🐛

Bug Reports

Completed

CET Output File Processing Only

Hi, I am pretty sure you are aware but in case you are not; since yesterday several of my CET runs have completed QC Feedback and Validation but CET Output is stuck at Processing. Not sure if this is related to ongoing updates in CEDARS but just wanted to check with you and see if this will be resolved soon. Thanks for all the work put on the updates and optimization of the environment.

fmonterroso 5 days ago

3
🐛

Bug Reports

In Progress

CET avoided cost data correction

DNV identified an issue in the date shifting methodology used to produce the 2026 avoided cost data and produced a corrected set of DEER load shape based avoided cost data. The development team ran some quick early look comparisons for ED staff. IOUs have rerun their 2026-27 budget filings and provided summaries. CCA/RENs are rerunning their 26-27 budget filings now; the dev team will produce comparison summaries for ED staff

cedars team 5 days ago

2
📨

Feedback

To Be Considered

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.

cedars team 7 days ago

💡

Feature Request

Load Shapes – On-Demand eTRM Sync

Currently, eTRM measure package data is synchronized to CEDARS through an overnight process. When a measure developer updates load shape-related variables in eTRM, they must wait until the next day before those changes are available in CEDARS. This delay can significantly slow Load Shape development, particularly when developers are iterating on measure package configurations and need to re-upload Load Shapes multiple times. The goal of this enhancement is to reduce the time between measure package updates in eTRM and their availability within CEDARS, improving measure development efficiency and reducing workflow interruptions.

cedars team 7 days ago

💡

Feature Request

Documents & Reports - Redesign for Improved Usability

As a CEDARS user, I want a clearer and more intuitive Documents & Reports page so that I can easily find, download, and upload documents without needing to navigate multiple sections or understand the underlying document structure. The current Documents page serves several important functions but has become difficult to navigate as the number of document types and user needs have grown. The goal is to reduce user effort, improve clarity around document ownership and purpose, and create a more maintainable structure as additional document types are added over time.

cedars team 8 days ago

💡

Feature Request

Completed

Reopening SCG 2025YR Monthly Report

Due to the filing extension, SCG needs to reopen its previously submitted 2025YR report in order to upload updated final 2025YR data. The current CEDARS workflow does not support rolling back multiple reporting periods entirely through the UI. Because both the March 2026 and April 2026 monthly reports have already been submitted, development support is required to roll back the reporting sequence.

cedars team 8 days ago

📨

Feedback

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.

cedars team 8 days ago

💡

Feature Request

Planned

Load Shapes – Improve Traceability and Visibility of Load Shape, TechID, and eTRM Synced Data

As a user reviewing Load Shape and Impact Profile data, I want clearer visibility into the relationship between TechIDs, measure packages, uploaded 8760 load shapes, and synced eTRM data so that I can more efficiently validate, troubleshoot, and trace generated outputs within CEDARS. Background Current Load Shape workflows require users to cross-reference TechIDs externally in eTRM in order to determine: Which measure a TechID belongs to Which uploaded 8760 data relates to a specific measure How generated Impact Profiles and outputs were derived While the information is technically available, the current workflow introduces multiple manual lookup steps and creates friction during validation and troubleshooting. Additional stakeholder feedback also requested greater transparency into: UEC data synced from eTRM into CEDARS Permutation data synced from eTRM into CEDARS Relationships between uploaded Load Shapes, TechIDs, Measure Packages, and generated outputs

cedars team 14 days ago

💡

Feature Request

Planned

Load Shape – Increase Upload Limits and Improve Large File Processing Performance

As a user uploading large load shape datasets, I want CEDARS to support larger upload sizes and improved processing performance so that I can submit load shape data without excessive file splitting, upload failures, or unreasonable processing times. Background Analysis of the 2026 measure package for SWHC013 indicates that a real-world production submission could contain approximately 80 million rows of data. Estimated file sizing: Single upload: approximately 500 MB Split upload approach: approximately 22 files at ~25 MB each Current upload limits and processing approaches may not be sufficient to support this scale of data submission efficiently.

cedars team 14 days ago

💡

Feature Request

Completed

Reopening SDGE, SCE, RRN 2025YR Monthly Reports

Due to the filing extension, some IOUs need to reopen previously submitted reports in order to upload updated final 2025YR data. The current CEDARS workflow does not support this process entirely through the UI when multiple report periods need to be rolled back in sequence. In these scenarios, development support is currently required. 2025YR will be re-opened so PAs can upload and submit, additionally because of the roll back they will need to resubmit 202603.

cedars team 14 days ago

1
📨

Feedback