Skip to main content

CET v25.1 database Available for Download from CEDARS doesn't include logic for old eTRM measure packages (MeasDetailID instead of FuelID)

Feedback

SDGE is seeing CE output misalignment between CEDARS CET Tool and the Database Download.

More specifically, the CET outputs for fuel sub measures identified with only a pre-2026 fuel sub MeasImpactType and no FuelID produce different results between the CEDARS CET module and the CET v25.1 database downloaded from CEDARS.

Attached is example of this misalignment for 2026 FuelSub measures.

Please confirm that the most current 25.1 database is posted to CEDARS for use by IOU internal systems as this is crucial for building out our portfolio budgets.

2026 forecast fuel sub summary.xlsx

12.8 KB• Spreadsheet

Posted by ggreen ·
Status: Completed6 comments

Log in to comment and vote

Comments6

  • Jennifer Scheuerell

    Team•

    Sep 4, 2025

    Good morning @ggreen

    I was able to move the fuelsub logic into the CET and will email over a database download to you and Eric C. for you to confirm it works on your end. If it looks good to you two I’ll update the posted documentation on Cedars tonight.

    • ggreen

      •

      Sep 4, 2025

      Morning Jenn,

      We were able to successfully download the new database with fuelsub logic. One question Eric noticed in this version and the previous version made available on 8/20 is that in the stored procedures that create CE, cost, emissions, and savings all the data in the “Saved” tables is deleted during every CET run. Curious if CEDARS is saving this data somewhere else?

      • Jennifer Scheuerell

        Team•

        Sep 4, 2025

        Yes, all data inputs and outputs are stored in the CEDARS database. CEDARS treats the CET as a calculation tool only.

  • Jennifer Scheuerell

    Team•

    Sep 3, 2025

    Hi @ggreen

    I can confirm that the CET database posted is the correct v25.1 database. In the interest of time, the code update to look to MeasDetailID if FuelID is empty was done upstream of the CET before the CET run is invoked, which is why you don’t see it inside the CET database. It didn’t occur to me before seeing this note that you all would want the CET to have that flexibility coded internally. I’ll take a look to see if I can move that logic into the CET database.

    • ggreen

      •

      Sep 3, 2025

      Thanks Jenn, and welcome back!

    • ggreen

      •

      Sep 24, 2025

      This ticket can be closed, thanks!