Timestamp Record Level Data Download Files

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.

When Claims/data filings are updated, trigger notifications to all users

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?

CEDARS Sitemap

Will you please provide a machine-readable sitemap? We may even consider a sitemap as part of normal documentation (just wondering aloud.) Thank you! Amy

Storing and retaining every permutation and input used to generate each impact profile

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.

Allow users to upload load shapes to measure packages with some passing permutations

It seems like currently when CEDARS syncs with the eTRM database, if any of a measure package's permutations have a sync error, the measure package gets marked as removed, blocking users from upload load shapes, even if the measure package did have some valid permutations. This problem needs further investigation and a fix so that measure developers expecting to upload to measure package SWHC059-06 are unblocked.

Publish data deadline map on CEDARS

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.

Update the custom measure load shape document in the user guide

DNV provided an update PDF for the documentation posted to the impact profile user guide called: Custom Measure Load Shape Tools Documentation. We now want to update the document hosted on CEDARS to the new version.

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.

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.

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.

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

I was asked to provide plain 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 resources tab

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).

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.

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

Hide the inactive PAs on the claim dashboard

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.

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.

Non-DEER Impact profiles download issue

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