Skip to main content

Retention policy and managing obsolete Load Shapes/Impact Profiles

Feedback2026Impact Profiles & Load Shapes

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

  1. Should obsolete uploads be deleted outright, or is there a preferred archiving/flagging mechanism instead?

  2. Is there a technical or audit-trail reason to retain obsolete uploads?

  3. If deletion is the agreed approach, who is responsible for performing it — the original uploader or anyone on their team?

Select the module in CEDARS
Posted by cedars team ·
5 comments

Log in to comment and vote

Comments5

  • spencer.lipp@futee.biz

    •

    Oct 20

    •

    Merged request

    •

    1 vote

    Draft Measure Package Load Shapes Retention policy

    A retention policy for draft measure package load shapes was discussed in the 6/23 call. FutEE has checked with MP Developers and they do not have a concern with the retention policy.

    The policy is as follows:

    1. All draft load shapes will be retained in CEDARS during development and review.

    2. When CPUC approves the MP, the load shapes are also approved. The approved version of the MP/Load shapes are now available for claims/filings.

    3. All draft version load shapes are deleted from CEDARS after 30 days as a retention policy.

    • Jennifer Scheuerell

      Team•

      Jun 30

      Hi @spencer.lipp@futee.biz,

      I don’t understand the third point you included in the policy:

      “All draft version load shapes are deleted from CEDARS after 30 days as a retention policy.”

      Are you saying that we are supposed to delete every draft load shape 30 days after it is created unless the measure package they belong to has been approved? That would contradict the first point of the policy as you wrote it, if I am understanding correctly. Perhaps you mean that draft load shapes are to be deleted after their measure package is rejected? If so, why not delete the load shapes immediately when the CPUC has decided officially rejected the measure package?

      Can you also help us understand what the third point of the policy is looking to accomplish? Some context would be helpful for us in deciding the implementation details.

      • spencer.lipp@futee.biz

        •

        Jun 30

        What I meant is that the draft load shapes are deleted 30 days after approval. This is in case someone wanted to go back for some reason. My guess is this aspect is a “nice to have” and not a “need to have”. So, if that is an issue, let me know and we can rework it.

        • Jennifer Scheuerell

          Team•

          Jul 1

          Thank you @spencer.lipp@futee.biz, I think I understand the confusion.

          I believe in eTRM you all make copies of the data when status changes (i.e. from draft to production). That is unconventional and is not how data work in CEDARS. In CEDARS when the draft load shapes/impact profiles/avoided cost data are approved the data will not be duplicated, they will simply change status. So there will be no draft data to delete after 30 days.

          If we need to address the theoretical case that “someone wanted to go back for some reason” after the measure package is approved by CPUC, wouldn’t that need to involve CPUC staff, eTRM version change, etc? Perhaps we want to consider that possible path with the larger group and separate it from this ticket?

          I think what is missing here now is what is intended to happen when CPUC does not approve a draft measure package. Do you have any insight there?

          • spencer.lipp@futee.biz

            •

            Jul 7

            Yes, I was misinterpreting.

            If the CPUC does not approve the Measure Package, the load shapes would be retained for 30 days.