Development Workplan 2026

New Measure Module

Create a new measure proposal form in the eTRM that allows vendors to submit a new measure proposal and can then be converted/transfered to an eTRM measure package. May incorporate QA/QC automation for missing information, pre-process inputs, data suggestion (e.g., permutation streamlining, strategies for improving cost-effectiveness metrics, etc.) With this integration, incorporate Measure Screening tracking to Measure Development Report to view the entire lifecycle of MP.

Reference Request/Approval Form

Set up an input form for references so that users could request references directly in the eTRM, apply checks to references to ensure good quality. Be able to extract the list of the references that are uploaded into the eTRM for system admins (maybe base users, we will need to discuss). System admin can just approve (add the reference to the library with a new number), approve but modify the citation/file, or reject as new but update an existing reference insted, reject Features: Input fields to be converted to citation (bibme.org) Multiple choice selection + adding new labels to ensure consistency (U.S. v. US) AI integration to reformat the citation AI integration to find if there are duplicate citation (i.e., semantic search, file search) AI integration to find if the reference update will affect other measures, in which case a new reference may be warranted

Next up

Committed and queued

Integrate automated QA/QC tools directly within the eTRM

QA/QC tools integrated within the eTRM measure development workflow platform that support these potential features: Measure Data Validation. Check measure package permutation data for completeness, accuracy, compliance, and alignment Characterization Review. Check characterization content for completeness, accuracy, compliance, and alignment with applicable permutation data and requirements Permutation Optimization: Apply streamlining algorithms to recommend optimized permutations for new measures and version updates. Claim and Field Data QC: Use measure property data to support claim validation and field data verification. Business rationale: Improve measure package data quality, reduce manual effort, and fast-track the measure development/review process through automated data QC tools.

In Progress

Actively being built

Integrate a dedicated customer support platform ("Featurebase") for the eTRM

Integrate a "Help Desk" feature, such as Featurebase or Zendesk, in the eTRM as the new "Contact Us" page for System Admin / Cal TF Staff to intake and manage all eTRM communication, such as enhancement requests, road map, bugs report.

Done

Recently shipped

Advanced filtering for data tables and reports

Currently, eTRM only allows very limited filtering from the web application (e.g., single choice selection, only some tables allow filtering on parameters only). This enhancement adds more advanced filtering functionality to improve data searchability, usability, and overall user efficiency across the platform. Proposed filter widgets: Multiple choices Number range selection Date range selection Keywords search Additional filtering abilities: Ability to filter all table columns, not just parameter fields Persistent filters: Ability for users to save the filtered view for future access. For example, PA users may only need to see their measures. Ability to export the filtered table so the user does not have to reapply filters. The export csv should indicate the filters that were applied Tables targeted for the advanced filtering UI: Supporting Value Vables in Measure CPUC Support Tables Shared Value Tables Permutations Table/Custom Permutation Report Measure Development Report

Buggy UI when saving filters in Custom Permutation Report

Issue: The Custom Permutation Report filtering widget has buggy UI issues when configuring and saving filters. An unsupported icon/image is displayed at the top of the filtering panel and the individual filter widget. Additionally, when applying a filter, the filtering widget just freezes and does not do anything. However, if you ignore the unresponsive “apply” button and save the report, you do see that the filters were applied successfully and correctly. Business impacts: The bug creates confusion and uncertainty when configuring Custom Permutation Reports, increasing the risk of incorrect report configurations and requiring additional time to verify results. The unsupported icon took up most of the page.

eTRM Public Database Isn't Syncing - Published Tables

Issue: The eTRM system alarm detected discrepancies between the public database and the main eTRM database, identifying a sync failure with the public sync since the last manual sync on 7/28. This only affects the published tables of the database; the data tables sent to CEDARS for the load shape process were not affected. Business impact: Outdated or incomplete measure data was sent to downstream users and applications, which may have affected business analysis. Four published measures and their permutations were missing. Their previously published PY2026 versions were missing EndDate, added after the approval of the published versions.

Deleting Custom Permutation Report redirect you to Dashboard

Issue: When deleting a custom permutation report, the application redirects you all the way back to the Home Dashboard page, instead of just the “Permutations” tab of the measure you were looking at. Steps to reproduce: Navigate to a measure Click on the Permutations tab Create and save a custom permutation report if there is none Click on the custom permutation report again and delete the report eTRM brings you all the way back to Home page Business impact: Users are likely to continue managing the custom permutation report of the measure they were viewing. By redirecting the user all the way back to the dashboard, it’s quite inconvenient and time-consuming to go back to the measure.

eTRM Public Postgres Database Isn't Syncing

Issue: The eTRM public Postgres database has not synced since 7/21/2026 ~9 am UTC (~2 AM PST). This is the day we ran the 2026 CET correction update. The database data showed the last updated date was 7/21/2026. Measure activities (e.g., new drafts and new permutations) beyond that date are not reflected in the database after the scheduled sync time. Business Impact: The public PostgreSQL database contains outdated data, preventing users and downstream systems (especially the CEDARS Load Shape Library) from accessing the latest production updates. This resulted in inaccurate reporting and data discrepancies between the public database and the production eTRM system.

Strip Leading and Trailing Blank Space in eTRM Fields

Background eTRM currently accepts and stores leading and trailing whitespace entered into text fields (e.g., “Technology ID” value table). While editing a value, the whitespace is visible. However, after saving, the UI trims the whitespace for display in both the Value Table and the Permutation Table, making it appear as though the value has been cleaned. The whitespace is still present in the underlying data and is returned in downloads, the API, and the database. This inconsistent behavior makes the issue difficult to detect during quality control. In our case, the hidden whitespace caused a downstream validation error in the CEDARS Load Shape Tool (the Tool did not generate the avoided cost for the measure), but the root cause was not immediately apparent because the UI displayed the value without the whitespace. Solution: eTRM does the automatic stripping across the board (not just in the display) Steps to reproduce: Navigate to a measure Create or click on an existing value table Edit the value table column that is of text data type Save the edit Map the field to the per

Unsync and remove "Load Shapes, Electric/Gas" CPUC Support Tables

"Measure Development Report" Improvement

Update the existing Measure Development Report to: tracks more granular timeline during measure development and review process Update so “resubmitted to CPUC” does not overwrite "Submitted to CPUC" date provide more data users may be interested in (e.g., measure dev firm, current status, etc, target dates) allow more rows and columns customization for users to select the fields they are interested in enable data extraction for customized report and visualization

Add "text concatenation" calculation function

Allow users to create an equation that concatenates various parameters/value table fields. One immediate use case is for measure developers to generate their own load shape ID/E3MeasElecEndUseShape ID.

Raname "PA" to "IOU_AC_Territory" in the CET Input File

Raname "PA" to "IOUACTerritory" in the CET Input File