Load Shapes & Impact Profiles
Tickets tagged with “Impact Profiles & Load Shapes”
Modernization
2Under consideration
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.
PA Measure Developer registration flow
Currently the development team can change user types to measure developers. This ticket would allow users to self-register. As a user involved in measure development, I want to register for a PA Measure Developer account and have my access request approved, so that I can upload load shapes and generate impact profiles
Backlog
33Under consideration
Remove NormUnit from load shape 8760 upload specification
Per request to align with the energy plus post processing script
Load Shape - Downloadable validation report
As a measure developer, I want to download the validation report in a portable format (CSV, Excel, text, or PDF), so that I can document issues, share errors with stakeholders, and track corrections across multiple upload attempts. Acceptance Criteria: A download button is available on the validation results page Supported formats include at least one of: CSV, Excel (.xlsx) The downloaded file includes all validation errors shown on screen The filename reflects the upload session The download is available immediately after validation completes and does not require re-running the validation
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?
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.
Quarterly Avoided Cost graph is wonky while generating
Jake (PGE) noted that “When generating, the graph gets wonky (turns super long). Reloading - or changing the drop down - fixes it but maybe something that can be done later to make it look like that from the start (or force reload at the end). This should be low priority.”
Non-DEER Impact profiles download issue
Several non-DEER impact profile CSV files include missing data that require review.
Export Load Shape Library Table
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.
eTRM Sync – Skip Measure Packages with Missing Draft References
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.
Support Load Shifting Where Base and Measure UECs Are Equal
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.
Display UEC proportion values when selecting draft measure package
As a Measure Developer, I want to see proportion UEC values when selecting a Measure Package so that I can confirm I am uploading load shapes against the correct eTRM version. Description Multiple versions of the same Measure Package can appear in CEDARS following draft commits or discards in eTRM. The current Measure Package Values table does not display UEC proportion values, making it difficult to determine which version should be used. Selecting the wrong version may result in Impact Profiles and Avoided Cost Combinations being generated using outdated savings assumptions.
Next up
1Committed and queued
In Progress
1Actively being built
In Testing
1Actively being built
Done
34Recently shipped
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.
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.
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.
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.
Load shape performance
I’m logging the issue that was discussed in the email thread initiated by Henry Liu (PG&E) on 6/30 regarding load shape processing performance. The load shapes uploaded on 6/30 remain in the processing queue as of 7/8. This delay is also impacting the ex-ante measure package review schedule and the CPUC/ex-ante team’s ability to determine next steps. The processing time was initially estimated at approximately 30 hours, with an additional 25 hours later identified. However, the actual processing duration has significantly exceeded those estimates. Notably, this issue pertains to only a single measure package, while several additional packages must be processed to support the DEER 2028 update. Please prioritize the resolution of this issue as soon as possible. Thank you.
Add email notification when load shape derived impact profile generation completes
It takes hours sometimes and we don’t want users to have to keep coming back to cedars to check if the job has completed.
Load Shape - Add a new user type for PA staff to upload load shapes
In the March 5 PCG meeting it came up that we may benefit from adding a new user type in CEDARS for users to upload load shapes but not have access to the other PA data reporting tools. New CEDARS user type: PA_MeasureDeveloper Granted community user privileges plus upload load shapes. Page permissions Load shape library: Public access View load shape graphs: Public access Add a new load shape: Any PA user Load shape upload history: Any PA user (Can only see own PA’s uploads) Permission Matrix Feature Access Load Shape Library Authenticated Users View Load Shape Details & Graphs Authenticated Users Add New Load Shape PA Admin, PA Ordinary, PA Measure Developer View Load Shape Upload History PA Admin, PA Ordinary, PA Measure Developer (Assigned PA only) Generate Load Shape Derived Impact Profiles PA Admin, PA Ordinary, PA Measure Developer Add Custom Impact Profiles PA Admin, PA Ordinary Edit Custom Impact Profiles PA Admin, PA Ordinary
SWWH014-09: Workaround for NR and NC permutations sharing the same load shape
As a Measure Developer, I want a supported way to use the same modeled load shape data across Existing and New vintages, so that CET can successfully run impact profiles where the modeled energy results are intentionally the same across vintages. Sophiya reported an issue with SWWH014-09 Heat Pump Water Heater, Residential. The CET run failed because an Impact Profile ID was not available for the New vintage for some measures. Following further clarification, the issue is not that the base and measure case use the same load shape. For SWWH014-09: Normal Replacement (NR / Existing) and New Construction (NC / New) have the same modeled savings and load shapes. eTRM permutations include both Existing (Ex) and New (New) vintages, resulting in expected Load Shape / Impact Profile IDs for both. The underlying modeling was only run for the NR / Existing building configuration. The NR energy results were then also used for the NC permutations in eTRM because the water heating measure was not expected to be affected by differences between the building vintages. As a result, the generated 8760 files only contain Load Shape IDs associated with the Existing (Ex) vintage. The corresponding New (New) vintage Load Shape IDs are therefore not included in the uploaded load shape files. CET fails when processing the NC permutations because the expected New vintage Impact Profiles cannot be generated from the uploaded data. Note we have a ticket in the backlog to @Allow measure packages to share load shapes
Load Shape – Impact profile generation can become Stuck After Errors
Impact Profile generation may enter an invalid state when processing encounters an error. Users may be unable to retry generation, with uploads remaining marked as processing, or incorrectly report that Impact Profiles have already been generated. Generation fails due to missing or invalid required data. Upload may remain in a “busy” state indefinitely. Users cannot re-run Impact Profile generation after correcting the issue. The system may incorrectly report that Impact Profiles already exist when the generation did not complete successfully. Expected Behavior Failed generation attempts should be rolled back cleanly. Users should be able to retry generation once the underlying issue is resolved. Existing Impact Profiles should be detected only when the generation completes successfully. Investigation Review generation error handling and rollback logic. Verify that the processing status is correctly updated after failures. Verify that the generated profile checks do not treat failed attempts as successful. Review queue handling when multiple uploads and generation requests are processed concurrently. For the production uploads already affected, we need to identify them, reset them, allow regeneration, and notify users.
Improve eTRM Sync Resilience for Invalid Measure Package Data
CEDARS synchronizes draft Measure Package data from eTRM to support Load Shapes uploads. We have encountered Measure Packages containing data that does not meet the assumptions required for processing within CEDARS. Examples include unexpected data formats, and invalid baseline data used for load shape calculations. Because CEDARS does not control the quality or completeness of data maintained in eTRM, additional handling is needed to ensure that a single problematic Measure Package does not prevent the synchronization of all other valid Measure Packages. Problem Currently, when invalid or unexpected data is encountered during synchronization, the entire sync process can fail. This creates several issues: Valid Measure Packages may not be synchronized into CEDARS. Users have limited visibility into which Measure Packages caused the failure. Troubleshooting requires investigation by development teams rather than providing actionable information to users and measure developers. Proposed Solution Enhance the synchronization process to be more resilient when invalid Measure Package data is encountered. When a Measure Package cannot be processed: The sync should continue processing all remaining Measure Packages. The problematic Measure Package should be excluded from synchronization. The user should be informed which Measure Packages were excluded. A clear reason for the exclusion should be provided where possible. The system should support a broad range of validation failures and unexpected data conditions, rather than only handling known examples.