Have something to say?
CET Measures.csv export scrambled
I am working through Heat Pump Water Heater, Commercial, Fuel Substitution (SWWH027-07-5) and am trying to get an export of the CET to run through the CEDARS CET tool. I am consistently getting errors as the file is not in the correct format. Am I missing something?
Additional TSB and TRC fields
At the October PCG meeting, Felix Monterroso requested TSB and TRC values for each quarter to be in the permutation table. Currently, he has to run CET multiple times to understand how different installation times impact TSB and TRC for his programs.
Manual downloads of permutation files do not need the newly added row
For users who manually download permutation files, and who therefore know what they downloaded and from where, the newly added row at the top of the permutation file that states “Exported from …” is absolutely unnecessary. It also causes downstream data processing issues for some. One of the following options would be much appreciated: (1) not adding the extra row at the top of the permutation file for manual downloads OR (2) an “opt out of the additional row” button side-by-side with the current “download csv” OR (3) adding the extra row at the bottom of the permutation file for manual downloads Thanks for your consideration.
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.
Add collapsible toggle for Cover Sheet "Change to Attributes" section
Description: The Cover Sheet Change to Attributes section can generate extremely long cells when recording additions and removals of permutation data spec fields. For example, PY2028 measures that add thousands of new TechID-based impact shape IDs. The lengthy entry occupies a significant portion of the page, making it difficult to read and navigate. Add a collapsible/expandable toggle (e.g., Show More / Show Less) for cells containing a lengthy change list, with the shortened preview as the default, so the Cover Sheet remains compact while allowing users to view the full details on demand. Business rationale: Improve the readability and usability of the Measure Cover Sheet by implementing a collapsible/expandable UI for the Cover Sheet “Change to Attributes” section.
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.
Invalid Calculation
Issue: Calculations using the “BasisValue” column of the shared Effective Useful Life and Remaining Useful Life value table result in validity error. However, the equation is still evaluated correctly in the permutation. Business Impact: Unknown or potentially false validity error, creating confusion and low confidence with the calculation. Reporter: Nicholas Fette (Solaris Technical)
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.
Allow measure developer to edit parameter labels
Description: When measure developers need to update parameter labels, they would need to delete the label, add new labels, and set up all the value tables again (setting up value tables is a multi-step process of reselecting the parameter and permuting the rows). Allowing measure developers to edit labels would reduce setup time and costs for measure development. Business Requirement: Reduce measure development time and effort by simplifying the process to update parameter and parameter labels. By: Lake Casco
Integrate OpenBCA Tool within eTRM
Integrate the newly released, open-source OpenBCA tool into eTRM for what-if scenario analysis of cost-effectiveness beyond what is currently possible within the CET. Per the OpenBCA site: “OpenBCA can assess individual technologies—including energy efficiency, demand response, distributed generation, distributed storage, electric vehicles (e.g. managed charging), and building electrification—as well as integrated DER portfolios at the project, program, and portfolio levels. OpenBCA can also support non-wires solutions (NWS), non-pipes solutions (NPS), and location-specific analyses when avoided or deferred infrastructure costs can be represented through appropriate valuation inputs.” See OpenBCA Tool | NASEO for details on options for integrating the tool, licensing, and other IT considerations. Note that incorporating additional benefit-cost and cost-effectiveness calculation capabilities beyond CET alone is consistent with Cal TF’s mission “To support the growth and success of energy efficiency and IDSM” and the vision for the eTRM Roadmap topic of Data Analytics.
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
AI Bot to create initial set of Measure Property Data
Description Develop an AI-powered assistant to automate the initial creation of Measure Property Data during measure development, using data from the permutation table, Measure Characterization, existing measure MPDs, predefined set of common data collection requirements. The generated output should populate the values or suggestions for all the fields of the eTRM MPD templates (e.g., names, description, applicable eTRM permutations, data types, default values, validation rules) Measure developers would be able to review, edit, accept, or reject the AI-generated suggestions before they are saved. Business Rationale Reducing manual effort, improving consistency across measures, accelerating the measure development and management process, and simplifying future updates while maintaining human oversight over the final data.
Software Business/Functional Requirements Management
Transition from SpecHub as a software requirements management tool to in-house alternative.
SSO for Featurebase
Implement single sign-on (SSO) for Featurebase users who already have eTRM login credentials to avoid eTRM users having to create a separate set of login credentials for Featurebase, unless they decide to do so for personal reasons.
Allow measure developer to download unrounded data for QC
eTRM permutation data is rounded at the display and permutation download - some due to regulatory reasons (e.g., savings are reported at 3 sigfigs). This makes it hard for a user to reproduce the calculation or QC. For example, the QC rule UES = UECBase - UECMeas is very difficult to QC with the current data availability since the rounding introduces precision errors (can be huge for large savings that are rounded to 3 sigfigs); the measure developers must self-verify whether the difference is actual data inconsistency or rounding error. Measure developers with an active open draft can download the individual value tables and get the unrounded numbers. Users can also get the unrounded numbers from the JSON file, but this process is not user-friendly, well-known, or intuitive. Allow measure developers and measure reviewers to download/access unrounded permutation values to perform their QC. Business rationale/requirement: Improve the traceability and effectiveness of measure quality control by providing measure contributors measure-by-measure access to unrounded permutation data through downloads and other approved data-access methods.
Ability to sort value tables and permutations
Allow a contributor to sort Value Tables based upon any column (parameter or value) and embed that sorted table to a characterization field. eTRM sorts by the parameters alphabetically. As a result, the offering ID table is typically out of order by the offering ID, which can be slightly confusing. Might be easier to let a base user sort when viewing the table rather than rely on the developer to sort. Allow for a stacking sort similar to how it currently works (alphabetically by row).
Ability to add and remove measure roles for multiple measures at once
Ability for admin users (PA Admin, CPUC Admin, and System Admin) to add and remove measure contributor roles to multiple measures at once. Admin users typically add (or remove) the same user(s) to multiple measures. Currently, admin users would have to do this one measure at a time, which can become quite time-consuming.
Enable measures to link to one another to ensure information consistency
Ability for measures to link to one another. For example, linking deemed measure to fuel sub, low income, and/or custom measure counterpart Business rationale/requirement: Help promote data consistency and synchronization during measure updates.
Embed parameters in Characterization
Ability to embed parameters or link to the parameter (shared or measure specific) in the characterization to dynamically list eligibility and measure scope, instead of recreating static tables. Example use cases: “Eligible Building Types” and “Eligible Building Location” subsections of “Program Requirement” “Modeled ” subsections of “Electric Savings” of modeled measures. It would be useful to just import or insert a link to the tables instead of recreating them.