Skip to main content

Development Plan 2026

The development tasks agreed to by the CPUC data reporting project coordination group. All tickets tagged 2026

On Hold

Under consideration

No On Hold issues

Modernization

31

Under consideration

Feature Request

Budget filings: Update specification to new claim-style pages

To have the new data specification pages including metadata descriptions for each field in the new easy to view format currently used in claims. Identified and requested by PG&E.

cedars team
Feature Request

Monthly reports: Allow Excel spreadsheets to be uploaded

As a program administrator, I want to upload Excel spreadsheets (like we do in the claims module) for monthly reports to streamline data submissions. As a CEDARS user, I want to upload Excel spreadsheets to the CET so that there is less of a data preparation hurdle to run my data. Adding Excel for CET and Budget Filings carved off into their own ticket.

Jennifer Scheuerell
Feature Request

Program fund shifts: Expand functionality

Enable fund shifting between statewide programs As a Statewide Program Administrator, I want to enable fund shifting between statewide programs in CEDARS so that I can efficiently manage budget adjustments similar to how it's done in local monthly reports. PAs are allowed to move funds between programs; CEDARS has functionality to manage fund shifts in the PA local monthly reports module. Fund shift dollars are expected to sum to zero for each PA and are added to or subtracted from to the forecast filing budget to produce the revised operating budget for each program for each year. No equivalent functionality exists for statewide programs. If statewide programs need to report fund shifts to CEDARS we need to build functionality to allow them to do so. Allow Fund Shifts Between Programs in Different Program Years As a PA, I would like the to have the flexibility to fund shift between programs in different program years. For example, β€’ Move funds from one year to a future year. β€’ Move funds from a future year to the current year. Right now, the ability to fund shift within CEDARS is only currently available between programs in the current active program year. Having this functionality in CEDARS would support more transparency between the IOUs when conducting these activities. This enhancement would affect Reporting, more significantly the Annual Report template. Improve presentation of program revised operating budgets As a PA, I want to see dashboards updated in real time when funds shift between programs.

ggreen
Feature Request

Statewide Module Implemented With CET

As a PA I want to have the statewide module implemented with the CET user interface so that PA's can track TSP Goals. Identified and requested by PG&E. Per the 10/3 ADP meeting, additional notes about this request: When PGE gets the CET forecast for state line programs and when they’re doing their internal forecast to assess if they will make their goal, they have to manually allocate that to just the PGE portion. They’re wanting to get allocated outputs from the CET for the statewide programs.

Amyreardon
Feature Request

Cost Effectiveness Module - Dashboard For Results

As a PA I want to have a dashboard within the Cost Effectiveness Module to run results and various scenarios So that I dont have to download a file and manipulate the data from the file and outside of CEDARS. Identified and requested by SDGE Additional context for this request per the discussion at the 10/3 ADP meeting: Idea is that a user could do various scenarios and runs without having to keep re uploading the same file over and over again

cedars team
Feature Request

Create Central Repository For All Templates

As a PA, I want all templates in a central repository so that they are easy to access from one location.’ Identified and requested by Marin Clean Energy and SoCal REN (LA County)

Amyreardon
Feature Request

Allow users to reference load shapes in their CET input data instead of impact profiles

This would eliminate the need to pre-calculate impact profiles for every possible combination of load shapes in advance. This would also allow dual baseline measures to use the correct impact profile for the early retirement phase and the above standard phase of their measure, instead of having to use one impact profile for both baselines as the CET works currently.

cedars team
Feedback

CET Simplification

Goals Eliminate renaming fields within CET calculations Simplify the CET code Improve version control Improve code availability Stop doing the same calculation multiple times Make the code more accessible to users Reduce the time it takes to calculate cost effectiveness Improve our ability to run multiple data inputs at the same time Ensure future code updates can be made efficiently Requirements Updated code will produce the same outputs as the current CET (v25.1) Updated code will be publicly available in a GitHub repository Ensure that all required inputs are clearly identified … Approach The CET has four primary scripts that calculate outputs: Savings Costs Cost effectiveness Emissions We propose to simplify the savings equations (the CalcSavings stored procedure in the current CET) first. Questions Do we want to continue to group equations like the current CET does, i.e. Savings, Costs, CE, and Emissions? …

cedars team
Feature Request

Remove the review step "Approve 2024 Budget Filing" button

Remove the "Approve 2024 Budget Filing" button. Once the budget data passes quality checks and is marked as complete, it should automatically be considered accepted and "Approved," eliminating the need for Amy to approve each filing manually.

cedars team
Feature Request

Data tab: Improve Accessibility of Large Record-Level Files

As a user, I want to be able to access the files easily on my device without running into performance issues or file size limitations,so that I can efficiently review a PA’s entire portfolio and analyze all necessary records without technical interruptions. Acceptance Criteria File Accessibility Large files, such as the SDG&E record-level file, are broken down or optimized to a size that can be opened on common user devices. A recommended file size limit is set (e.g., 1GB for Excel compatibility), though this may vary based on testing and device specifications. Consistent Record Availability Files are structured in a way that maintains ease of searching and comprehensive access to a PA’s portfolio within a manageable number of files. Clear Communication on File Structure Documentation or guidance is provided to inform users of any new file structures, including rationale for split files, compression, or access methods.

Amyreardon

Backlog

36

Under consideration

Feature Request

CEDARS Email: Confirm Report Upload/CEDARS To Send Email Reminders

As a PA I want an email from CEDARS confirming when a document is uploaded So that I have a record of the document upload and I do not have to take a screenshot of the downloaded zip file with the date as my record. Identified and requested by SCE. Additional context for the ask per 10/3 ADP meeting: Current state: PA has to go into the document, look when it was uploaded, screen shot the date as proof of upload. This effort would be a regulatory solve.

cedars team
Feature Request

Data tab: Make pre-2016 and evaluation data available for download

As a PA, I want to review data from before CEDARS was online and also evaluation data. These data could be available for download at the measure level in the data tab.

cedars team
Feature Request

Remove NormUnit from load shape 8760 upload specification

Per request to align with the energy plus post processing script

Jennifer Scheuerell
Feedback

Budget Filing Dashboards – Add Toggle to Exclude ESA Savings from Segment, Sector, and Program Summaries

Add an β€œExclude Energy Savings Assistance (ESA)” toggle to the Budget Filing Dashboard tables, similar to the existing ESA toggle in the Claims module. Timeline / Priority: Ideally implemented before 2028–2031 Budget Filings. Applicable to 2026 and 2027 filings for verification and consistency. Problem it solves: β€œFor 2026 and 2027, the TSB, Net kWh, Net kW, Net Therm, Gross kWh, Gross kW, and Gross Therm values include ESA program data at the segment, sector and program levels which should not be part of this filing.”

ggreen
Feature Request

Email notifications: Deactivate User Accounts When Email is Returned

User Story: Deactivate User Accounts When Email is Returned As a system administrator, I want to automatically deactivate user accounts when emails sent to their registered email addresses are returned as undeliverable, So that I can maintain the email sending reputation of our system and manage accounts that are no longer active.

Jennifer Scheuerell
Feedback

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 team
Feedback

Review Requirement for Site ID in the Participant Table

During Claims 2026 UAT, stakeholders provided feedback on the new Site ID field in the Participant table. The feedback was that participant counts are generally managed and analysed at the program level, rather than the individual site level. Requiring a Site ID introduces additional complexity to the submission process and may provide more granularity than is needed for the intended reporting outcomes. The reporting objective should be reviewed with Energy Division staff to confirm whether participant reporting is intended to occur at the site level or whether a program-level approach would better meet the business need. Questions for Energy Division What reporting or analytical use case requires participant records to be associated with a Site ID? Are participant counts expected to be reported at the site level or only at the program level? Would program-level participant reporting satisfy the reporting requirements? If Site ID is retained, how will participant records be used differently from the existing Site table?

cedars team
Feature Request

Support Baseline Tech Group and Tech Type in Load Shape Uploads

As a Measure Developer, I want CEDARS to recognise baseline technology information separately from measure technology information so that I can upload baseline load shapes using their correct Tech Group and Tech Type values. Background CEDARS currently only synchronise the measure case Tech Group and Tech Type from eTRM permutations. As a result, both measure and baseline load shapes are expected to use the measure case values during upload. For example: Measure: SWWH031-07 Measure Tech Type: HP_COP Baseline Tech Type: Stor_UEF Although the Tech ID correctly identifies the baseline technology, uploads currently fail unless the baseline load shape is generated using HP_COP. This behaviour has caused user confusion and ongoing troubleshooting effort.

cedars team
Feature Request

Add AnalysisMethodology to Claim table

Data Type: Text Value list: Top‑down Bottom‑up Mixed Analysis Description Indicates the primary evaluation approach used to estimate SEM savings for the claim, based on whether savings are derived using whole‑facility modeling, measure‑level calculations, or a combination of both. The reported methodology must be consistent with the savings documentation and calculation approach used for the claim. Rules Required for all SEM‑related claims Must be a value from the value list

cedars team
Feature Request

Make program segment non-editable once used in budget filing

As ED staff, I want to make sure that PAs cannot edit their program segments after they have included the program in a budget filing.

Jennifer Scheuerell

PCG Top Priority

2

Committed and queued

Fixed Development

2

Committed and queued

Planned

8

Committed and queued

Feature Request

CEDARS & CET calculations: Add documentation

As a PA, I want the documentation for formulas utilized throughout the CEDARS site and CET to be updated and published to CEDARS So that users have the most up to date formula information available. Identified and requested by SDGE Per 10/3 ADP meeting - It’s putting in clearer language for all the formulas and what calculates all the different fields in CEDARS so that you can trace back and somebody who doesn't have a mathematics background can figure out what the calculation is. Also to include a formalized CET reference document that is up to date and again, includes the calculations, etc.

cedars team
Feature Request

CET: Provide metadata for outputs

As a user, I want CEDARS to provide metadata and descriptions for CET output fields so that I can easily understand and utilize the data without confusion. Description: CEDARS currently only provides metadata to describe data PAs submit; the CET output fields are not similarly described for users. Multiple users (PAs and others) have requested Cedars offer a data dictionary/metadata field description for the CET output fields. Program administrators and other users need clear definitions and context for CET output fields to interpret the data accurately and efficiently. Currently, this information is lacking, which can lead to misunderstandings and misinterpretations.

Jennifer Scheuerell
Feature Request

Allow measure packages to share load shapes

Lake Casco
Feature Request

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
Feedback

Claims TCR-Res-002: Multifamily Program CEDARS Corrections

Corrections were originally scheduled for this week (February 23rd) to fix an accounting error in the TCR-Res-002: Multifamily program. Our team has discussed with Amy and Jennifer and they are good with the planned reschedule. Corrections will still occur in Q1 2026 and the website tool tip does not need to be updated.

[Deleted User]
Feature Request

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.

cedars team
Feedback

Updates/next steps on PCE 2023-2024 claims revisions

PCE would like an update or discussion of next steps on getting 2023-2024 claims updated per previous conversations/data provided.

PCE_TEC
Feedback

Review "Other" program categories: Recommendations for Program Attribute Choices

A quick look at the fields brought up at the PCG, If we could add the following attribute choices. Field Add Primary Sector: Non-Program Sector Non-Program Program Category Incentive Program Measured Savings Non-Program

GGolden42

In Sprint

5

Committed and queued

Feedback

CET User Guide - Improvements to Fuel Sub guidance

https://cedars.cpuc.ca.gov/cet_ui/cet-user-guide/

cedars team
Bug Reports

CET validation fails for SWWH025 impact profiles found in the ACC list, run 123326

Lake Casco reports that CET runs using impact profiles for measure SWWH025 fail validation. CEDARS says the values aren’t allowed for AvoidedCostCombo, but the same impact profile appears in the ACC list. Reference run: CEDARS run 123326. Sample error from the CEDARS error log: Table Record Message Type Message Code measure SWWH025-12-draft-BD-AR-DI-Res-DMo-Ex-Any-CZ01-FuelSubst-Default-Def-GSIA-Any-Any ERROR _VALUES_1_DMO Message: Values = ('1', 'DMo*Ex*rDXGF*RE-WaterHtg_eq-HP_UEF-40g-LO-2.75UEF-120V*RG-WaterHtg_eq-Stor_UEF-30g-MD-0.61UEF', 'Res', 'PGE') are not allowed for AvoidedCostCombo.

Sonja Loader-Jurac
Feedback

Process 2026 Q3 PII submissions

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

Jennifer Scheuerell
Feature Request

Select 2028 Avoided Cost for new Impact Profiles

Once the 2028 avoided costs are in Cedars we want to include it as an option on the dropdown for First Avoided Cost Version

Sonja Loader-Jurac
Bug Reports

As a CPUC admin, I want reopen approvals to work, so that filings reopen as expected.

Amy approved a reopen request on a budget filing, but the approval hung and the filing didn’t reopen. The filing went back to the PA admin instead, as if they had never asked to reopen it. We fixed the reopening manually. We still need to find and fix the cause so this doesn’t happen again.

Sonja Loader-Jurac

In Progress

2

Actively being built

In Testing

8

Actively being built

Feedback

Schedule CEDARS Budget Filing Correction for AVA (EBCE)

This item has been discussed with Amy Reardon and Pam Rittelmeyer. AVA’s program is closing out in May 2026 and to meet future reporting requirements and to align with a past program budget change, 2023-2025 total budget amounts will need to be updated. We are preparing new files to upload the data and will need to schedule time to make the updates, preferably before the upcoming Annual Report (4/15) deadline. It is also important to note AVA was previously called EBCE in 2023.

KlarsonMCE
Feature Request

Update CEDARS Data Validation Rules to Support New DEER Delivery Types (PY2026+)

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.

Roopa Reddy
Feature Request

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.

cedars team
Feature Request

New review team file download

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.

sepidehs
Feedback

RRN Budget Filing Correction for 2025

In preparation of the 2025 Annual Report, an error in RRN 2025 budget values was identified. Unfortunately, the entered RA portfolio budget ($6,174) and CS Portfolio budget ($131,806) should be switched. The total 2025 budget remains the same. Would it be possible to switch these values in CEDARS? Also, for Annual Report submittal, is there anything additional we should note? We will report the correction within the workbook and narrative.

KlarsonMCE
Feature Request

Custom resources tab

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

cedars team
Feedback

PCE ETA budgets for 2026-2027

Resolution E-5442 approved PCE to Elect to Administer for a total of $2,974,494 from August 1, 2025 through July 31, 2028. These budgets are not currently reflected in CEDARS but PCE is reporting expenditures via CEDARS. PCE would like the budgets reflected in CEDARS to avoid the appearance of overspend.

PCE_TEC
Feedback

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.

Jennifer Scheuerell

Done

155

Recently shipped

Feature Request

Deemed Measure Load Shape Repository

As a consultant to the CPUC, DNV is leading the effort to create a library of deemed measure load shapes on CEDARS. This is needed to enable the measure package developers and PAs to upload 2-3 load shapes for each deemed measure permutation in the eTRM for PY2028. These load shapes will be used to determine the quarterly avoided costs for each deemed measure claim as an input to the CET. It will be important to leverage the viewing/calculation capabilities that were developed for the impact profile library. We think there will also be a need to have a second sandbox library that would enable measure package developers to upload load shapes pertinent to a given measure package in preparation for their CET runs. This will need to be ready for use by measure package developers by mid-late spring 2026. This effort is intended to enable the replacement of the legacy DEER load shapes--many of which may no longer accurately represent the hourly distribution of savings--to improve the accuracy of the TSB and TRC of deemed measure.

rachel.murray@dnv.com
Feature Request

Add ParticipantID to claim table

For SEM in particular, to allow linking between multi-year claims for a single participant. Also include complete SEM Reporting Guidance, including the requirement to file a no-savings claim in the year there is no activity. Table: Claim Field Name: ParticipantID Description: Identifier used by PAs to track all SEM activities and claims for a participant across the full program engagement, including core cycles and any graduate cycle. This ID is needed in tracking data to consistently link related SEM records over time.(e.g., FPCx.00 or 7999.P0) Data Type: Text (up to 255 characters) Required: N Rules: Required for SEM Claims

Jennifer Scheuerell
Feature Request

Claims IDSM field removal

Claims IDSM fields removal As a user, I would like the IDSM fields introduced in the 2024 Claim Specification update to be removed from Claims reporting, as there is currently insufficient guidance on how to populate them and limited value in collecting them in their current form. Fields for removal: Claim.IDSM_DR Claim.IDSM_DER Background: Definitions and intended reporting requirements for these fields remain unclear. It is unclear which values should be entered and whether they pertain to incentives, costs, benefits, or other metrics. Current reporting pathways do not adequately support meaningful or consistent use of these fields. Proposed outcome: Remove both fields from the Claims Specification. Consider alternative IDSM reporting, such as annual narrative reporting.

Amyreardon
Feature Request

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
Feedback

Claim.HTR_Flag if true other flags are required to be true

Draft valid combinations of Claim.HTR_Flag = true based on HTR CEDARS.docx Option A: CA_Flag path Claim.HTR_Flag = true + Claim.CA_Flag = true Option B: Geographic path Claim.HTR_Flag = true + (Claim.OMBCSA_Flag OR Claim.CalEPA_Flag) = true + 1 other remaining flag = true Non-Res (Claim.DEER_Sector = Com, Ind, Ag) remaining flags: Claim.Lang_Flag, Claim.NRSize_Flag, Claim.NRLease_Flag, Claim.LG_Flag Res (Claim.DEER_Sector = Res) remaining flags: Claim.Lang_Flag, Claim.ResLI_Flag, Claim.ResMFMH_Flag Option C: Any 3 of the remaining flags = true Non-Res (Claim.DEER_Sector = Com, Ind, Ag) remaining flags: Claim.Lang_Flag, Claim.NRSize_Flag, Claim.NRLease_Flag, Res (Claim.DEER_Sector = Res) remaining flags: Claim.Lang_Flag, Claim.ResLI_Flag, Claim.ResMFMH_Flag Design mockup: https://www.figma.com/proto/djSwjUOnQmtJGgHy5wcHbk/Claim-Specification-Update-2026?node-id=6611-2898&viewport=-1119%2C479%2C0.13&t=8RsCmH7VPF8ekkHP-1&scaling=min-zoom&content-scaling=fixed&starting-point-node-id=6827%3A2341&desktop-link-click-timestamp=1778106748421&desktop-ul-exp-bucket=V&page-id=6601%3A2827 Flag Descriptions Field descriptions and location Move all relevant HTR fields together in Claim Spec and update descriptions. Listed in order: HTR_Flag As is: Hard to Reach. Flag to identify the measure was installed in a hard to reach location. To be: Indicates the claims is being reported as Hard to Reach. The claim must satisfy one of the valid Hard to Reach qualification pathways. Hard to Reach participant counts are included in the Participant table. CA_Flag As is: Flag to identify Cultural Accessibility - HTR (Hard to reach). To. be: Flag to identify Cultural Accessibility. It identifies California Native American Tribes as hard to reach. Tribal customers qualify independently under Commission policy and do not need to meet additional Hard-to-Reach (HTR) criteria. Lang_Flag As is: Language. Meets language barrier for hard to reach. To be: Flag to identify customers where the primary language spoken is other than English. Contributes to Hard-to-Reach (HTR) eligibility. OMBCSA_Flag As is: United States Office of Management and Budget. Flag to identify measures installed in a zip code outside of defined US Office of Management & Budget statistical areas for hard to reach. To be: Flag to identify measures installed at customer premises located outside the United States Office of Management and Budget (OMB) Combined Statistical Areas of the San Francisco Bay Area, Greater Los Angeles Area, and Greater Sacramento Area, a

Amyreardon
Feedback

Add new table and fields to track participant type and number of participants

Reporting at the program level is preferred over Claims as it’s less complex. Unique Pop NMEC could also be reported. Will be reported as a CSV zipped with the record-level downloads on the data tab Inline guidance and user guide will need to be updated. Design mockup - Draft Table name: Participant Primary Key Primary key: Participant.PrgID + Participant.PrgYear + Participant.ParticipantType + Participant.SiteID Table validation check e.g. That the primary key is unique regardless of the letter case. Relationship validation Participant.PrgID must match a ProgramCost.PrgID Participant.SiteID, when populated, must match a Site.SiteID Fields PrgID Data type: Text (up to 255 characters) Required: Y Description: The unique program identifier; joins to the ProgramCost table. PrgYear Data type: Integer Required: Y ParticipantType Data type: Text Required: Y Valuelist ParticipantCount Data type: Number (Up to 15 decimal places) Required: Y SiteID Data type: Text EquityTargeted Data type: Number (Up to 15 decimal places) Required: Y DAC Data type: Number (Up to 15 decimal places) Required: Y HTR Data type: Number (Up to 15 decimal places) Required: Y Underserved Data type: Number (Up to 15 decimal places) Required: Y Comments Data type: Text Required: N

Jennifer Scheuerell
Feature Request

Add TCR confirmed claim info button

Add infobutton on the TCR confirmed dashboard that says: β€œAn accounting error in the TCR-Res-002: Multifamily program that impacts the program cost will be corrected in Q1 2026. This will result in a discrepancy in TCR's 2023 and 2024 annual report until the correction is made.”

[Deleted User]
Bug Reports

Duplicate Hour in Impact Profile Exports

Load shapes Impact Profile export 8759 unique hours instead of 8760 β€” one hour appears twice while another is missing entirely, resulting in the output still containing 8,760 rows but with a duplicated hour timestamp rather than a duplicated impact value. Specifically, hour 1587 is missing and hour 1588 appears twice. Likely related to daylight saving time handling.

cedars team
Feedback

Allow users to replace previously uploaded load shapes, impact profiles, and avoided costs

Currently load shapes are overwritten when re-uploaded. The generated impact profiles should be replaced. Background Measure Developers may need to update previously submitted load shapes due to: Corrections to uploaded data Changes to eTRM permutations or assumptions Re-running simulations with updated modeling inputs QC findings identified after initial upload Currently, CEDARS allows users to re-upload load shape files, which replaces the underlying load shape data. However, any previously generated Impact Profiles remain locked and cannot be recalculated. This can result in inconsistencies between the latest load shape data and the Impact Profiles and avoided cost combinations being used downstream. In addition, users currently receive an error when attempting to regenerate Impact Profiles that have already been generated: β€œImpact profiles have already been generated for the load shapes in this upload. Existing impact profiles cannot be recalculated.” This limitation prevents Measure Developers from correcting or updating previously submitted data. Proposed Enhancement Allow users to replace previously uploaded load shapes and regenerate associated Impact Profiles and avoided cost combinations so that CEDARS reflects the latest approved data. The enhancement should: Permit replacement of existing load shapes for a draft measure package. Allow existing Impact Profiles to be removed and regenerated from the updated load shapes. Provide transparency and safeguards to prevent unintended overwrites.

Jennifer Scheuerell
Feature Request

Load Shape User Guide

As a Measure Developer or Program Administrator, I want clear documentation explaining how to use the Load Shape Library tool, so that I can correctly prepare, upload, load shapes.

cedars team