Skip to main content

Value List Validations / 2026 Claim Spec

Feature Request20262026 Claim Spec Update Queue

This popped in my head and want to capture it here.

With prior year measure package versions being allowed based on the savings date field, CEDARS needs to allow prior year value list values in these cases. To me the cleanest way is if, for deemed measures, the SavingsDate field is used to compare against the value list, but open to other solutions.

Select the module in CEDARS
Select user type
Posted by Jake Richardson (PG&E) ·
Status: Completed1 comment

Log in to comment and vote

Comments1

  • cedars team

    Team•

    Apr 29

    We propose rather than introducing SavingsDate driven conditional validation at this stage, a simpler near-term approach may be to align with the Budget Filing handling and remove end dates from impacted value lists so historical measure packages pass validation.

    Suggested values list to allow past prior end dates for:

    • EUL

    • RUL

    • TechType

    • DeliveryType

    • MeasImpactType


    This would reduce risk for 2026 Claim Spec timing. More advanced SavingsDate aware validation could be a future enhancement.