Change Log

Permutations Update: PY2026 CET Correction

Affected User: Reporting, program designers, program implementers

Features: Overwrote the existing published PY2026 permutations in response to the CET's Electric Avoided Cost correction deployed on June 26, 2026. The 2026 CET correction resolved a day-shifting error in the electric avoided cost calculation, which updated the electric benefits and all dependent fields. To ensure consistency with the corrected CET, eTRM has rerun the 2026 CET and the related Restricted Permutation Flag calculation.

Please reach out to Cal TF staff if you would like to review the analysis of the data changes.

Notes:

• This update only affects measures that are active in 2026 (i.e., End Date is blank or End Date ≥ 1/1/2026).

• This update only overwrites the 10 cost-effectiveness fields and the Restricted Permutations Flag Field; No other permutation fields are modified.
  Electric Benefits (ElecBen)
  Gas Benefits (GasBen)
  TRC Cost - No Administrative Cost (TRCCostNoAdmin)
  PAC Cost - No Administrative Cost (PACCostNoAdmin)
  TRC Ratio - No Administrative Cost (TRCRatioNoAdmin)
  PAC Ratio - No Administrative Cost (PACRatioNoAdmin)
  Total System Benefit (TotalSystemBenefit)
  Water Energy Benefits (WaterEnergyBen)
  Other Benefits (OtherBen)
  Other Costs (OtherCost)

  Restricted Permutation (RestrictedPerm)

Permutations Update: PY2026 Annual CET Update

Affected User: Reporting, program designers, program implementers

Features: Overwrote the values for 10 cost effectiveness output data in the permutation table to ensure they reflect the correct CET avoided cost version (2026), CET version (v25.1), and net present value (2026Q3) for the new program year 2026. This is part of the eTRM annual update process to keep eTRM CET results aligned with the best available data for program planning and payment. Please reach out to Cal TF staff if you would like to review the analysis of the data changes.
Notes:

• This update only affects measures that are active in 2026 (i.e., End Date is blank or End Date ≥ 1/1/2026).

• This update only overwrites the 10 cost effectiveness fields; No other permutation fields are modified.
  Electric Benefits (ElecBen)
  Gas Benefits (GasBen)
  TRC Cost - No Administrative Cost (TRCCostNoAdmin)
  PAC Cost - No Administrative Cost (PACCostNoAdmin)
  TRC Ratio - No Administrative Cost (TRCRatioNoAdmin)
  PAC Ratio - No Administrative Cost (PACRatioNoAdmin)
  Total System Benefit (TotalSystemBenefit)
  Water Energy Benefits (WaterEnergyBen)
  Other Benefits (OtherBen)
  Other Costs (OtherCost)

Resolved various AWS security vulnerabilities

Affected users: None

Features: Resolved various AWS container vulnerabilities identified by the monitoring software to maintain security compliance and SLA.

Permutation Updates: Populated the Fuel ID field

The eTRM software team executed a backend script to populate the "Fuel ID" field for measure permutations active in 2026 (i.e, EndDate is blank or EndDate >= 1/1/2026). The "Last Updated Date" for these measures was also updated to "6/13/2025".

The Fuel ID values were validated in coordination with Cal TF staff, PA leads, and the CPUC.

Affected Users:

• To any users that download eTRM permutation data, you can now view and extract the Fuel ID labels from the permutation table of the individual measure, from the All Measure Permutations Report, and via eTRM API.

• To any users that download eTRM permutation data via the public PostgreSQL database, the eTRM Development Team will begin the database sync today at 5:30 p.m. PST to sync the permutation update. This sync will take a couple of hours and you may experience restricted access during this time. Once the database sync is completed, you can view and extract the Fuel ID labels.

• To measure developers, please note that this eTRM update only writes in the Fuel ID label for the published permutation file. When you start a new measure update draft, you will need to follow the process to map the Fuel ID field and populate the label in the permutations. Please see the instructions in the Measure Developer Resources SharePoint.