Skip to main content

Load Shapes – Version control between eTRM & Cedars

Feature RequestImpact Profiles & Load Shapes2026

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.

Select the module in CEDARS
Select user type
Posted by cedars team ·
Status: Completed6 comments

Log in to comment and vote

Comments6

  • Derya Gumustel

    Team•

    Jul 30

    Work for this has been deployed, outdated draft measure package versions will no longer appear in the measure package selection drop down on the load shapes upload page.

  • Jennifer Scheuerell

    Team•

    Jul 17

    •

    Merged request

    •

    2 votes

    Improve Identification of Duplicate Draft Measure Packages

    We have learned that sometimes measure developers create multiple measure package drafts for one measure and those multiple drafts can have identical permutation data, which makes it impossible for cedars users to know which measure they should select in the interface.

    The measure developers would like us to include the eTRM version ID with the measure name in the drop down list for adding load shapes so they can distinguish the draft they want to upload load shapes.

    “The best date to use would be the "LastUpdatedDate" = Date when MP data, properties, or workflow status is updated. Not 100% ideal since the timestamp may also be updated by changes unrelated to the permutation data, but it is the best available option.

    If your system records the "LastUpdatedDate" timestamp when it detects changes to a measure's permutation data, that should be close to the timestamp when the permutation was rebuilt. PA and measure developer should then use the measure draft with the most recent timestamp.”

    • nfette

      •

      Jul 16

      We have been getting around this by looking at the preview of validation labels after selecting one option from the dropdown. So it is not impossible to proceed without this enhancement, but it could save a few minutes for each new set of uploads.

  • cedars team

    Team•

    Jul 1

    •

    Merged request

    •

    1 vote

    Improve Identification of Duplicate Measure Packages in Load Shape Uploads

    When draft measure packages are committed or discarded in eTRM, CEDARS may display multiple versions of what appears to be the same measure package in the Load Shape upload workflow.

    This occurs because CEDARS preserves any measure package that already has uploaded load shape data attached, while also syncing the updated version from eTRM. As a result, users can see duplicate measure packages in the selection list with no clear way to identify which version is the latest.

    Current Impact

    • Users may inadvertently select an outdated measure package.

    • There is no visible indication of which duplicate should be used.

    • Determining the correct version requires comparing underlying permutation data, which is not practical for users.

    • If a revised measure package is required, users must upload load shapes to the new version.

    Proposed Improvements

    • Display additional identifying information in the Measure Package selection list to help distinguish duplicate versions.

    • Display key values used by load shape processing, such as UECs, to make differences between versions more apparent.

  • cedars team

    Team•

    Jun 12

    It was discussed today in the eTRM Demo of Development Processes that it would be helpful to include the Version ID next to the measure package name in the Cedars dropdown. This change will make it easier for users to identify which measure package is being synced from eTRM.

  • spencer.lipp@futee.biz

    •

    Jun 10

    The eTRM uses a draft versioning system for quality control, revision history, and transferring ownership between different people. For example, after completing a round of data update, a developer will save the draft version and release their control when submitting the measure to CPUC review. The CPUC personnel then takes the assignment, locking out the developer, to conduct their review. Once CPUC completes their review, they release the assignment back to the measure developer, who then creates a new draft version to address the comments and implement more measure updates. This saving-draft/creating-new-draft process also occur when measure developer submit the measure to PA review, when the measure is transferred to a new measure developer, or when the measure developer needs to save their changes for version tracking.

    Currently, CEDARS does not support the draft versioning described above. The work around is to keep the draft measure package open until CPUC approval, which loses the version changes tracking ability and deviates from the current measure development workflow. CEDARS needs to be modified to support the existing eTRM versioning for draft measure packages.