Skip to main content

Create a flag to identify non-programs from programs

Feedback2026

Non-programs are program IDs that capture costs (e.g., portfolio support, GRC overhead, SW__PA programs) without implementing anything.

Select the module in CEDARS
Posted by cedars team ·
Status: No Fix Required3 comments

Log in to comment and vote

Comments3

  • Amy.reardon@cpuc.ca.gov

    Team•

    Sep 29

    I think we can close this ticket since we learned that “non-program” implementers is a suitable solution.

  • cedars team

    Team•

    Aug 26

    Discussion at the last dev demo was had on using the existing “program implementer” field (which already has a “non-program” option) rather than adding a new field.

    For PG&E, non-programs sit in the IOU core bucket, so no conflicts anticipated. Consensus leaning toward using the existing field; Jake suggested letting people sit with it and adding it as an agenda topic at the September PCG meeting for final feedback.

  • cedars team

    Team•

    Aug 19

    The program implementer field within the programs module contains "non-program" as an option. Would this be a suitable solution, or is that field intended for another purpose?

    Is that field used for any additional logic within CEDARS?

    Is “cost tracking” or “cost tracking only” more suitable than non-program.