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

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?