Have something to say?
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.
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.
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.
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). However, one measure data QC rule is that the UES = UECBase - UECMeas. This rule is ambiguous 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) that require the measure developers to self-verify whether the difference is actual data inconsistency or rounding error. Allow measure developers and measure reviewers to download/access unrounded permutation values to perform their QC. Business rationale/requirement: Improve the accuracy and efficiency of measure quality control by providing measure contributors measure-by-measure access to unrounded permutation data through downloads and other approved data-access methods.
Automatically classify QA comments by type and severity
When a measure package is being reviewed, use AI to automatically classify comments into severity levels (High/Medium/Low) and comment category. This will enable quicker reviews by helping prioritize and respond to QA comments. Example categories: CriticalityBroad CategorySpecific Category High Criticality Savings Savings: methods, assumptions, base/measure, or data High Criticality Savings Savings: general/issue with results High Criticality Costs Costs: methods/assumptions/data High Criticality Costs Costs: general/issue with results High Criticality Permutation edit Permutation edit: add Tech ID High Criticality Permutation edit Permutation edit: MAT High Criticality NTG Update NTG Medium Criticality Methodology description Methodology description: incomplete/unclear/missing/erroneous Medium Criticality Clarification needed Clarification needed: technical/code/program Medium Criticality Analysis reference Analysis reference: incomplete/unclear/missing Medium Criticality Future comment Future comment: will be high criticality in the future Low Criticality Language update grammar, spelling, and suggested clarity Low Criticality Comment out of scope Comment out of scope: comment on wrong version Low Criticality Comment out of scope Comment out of scope: general comment to PA Low Criticality Comment out of scope Comment out of scope: reporting and EM&V processes outside the eTRM Low Criticality Code information Code information: date, cycle number, and/or reference Low Criticality Reference Edit Reference edit Low Criticality Delivery
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.
Show unrounded data for value tables in the MP download
The value table CSV files that are a part of the Measure Package download should show the full precision, unrounded values. eTRM displays rounded values but uses the full precision data for calculations. However, it’s hard for a user (without having an open draft of the measure version) to reproduce the numbers and/or trace the rounding error because the downloaded data is rounded. 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.
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.
Improve calculation transparency and traceability
Add an "evaluate" function to show step-by-step calculation processes. Currently, evaluating calculations in the eTRM can be tedious. You need to rerun permutations every single time you make one change to the calculations. Having an evaluate/look in function, similar to the one in Excel that allows you to see every step along the way, would be helpful so that you do not need to check/run permutations every time. The user can have options on what CZ, BT, MAT, and other parameters they want to run the evaluate/look in function for.This can also be helpful in the MC, displaying how a calculation is evaluated for a set of parameters would be very helpful for base users. Solutions may include: Evaluate each calculation to a value table and the ability to export that result Above + even when the draft is committed or published (for users)
Expose relevant eTRM data in a mobile-optimized format
Exposing relevant eTRM data (such as current program eligible measure permutations/offerings/MPDs) to practitioners in the field such as program implementers and project developers in a format optimized for mobile use or use in third-party applications could facilitate uptake of deemed measures.
Allow MP submission without PA sponsor
Currently, measure must have a PA sponsor in order to be considered for the deemed measures library. This is an obstacle for new measures. Add a "Cal TF" option for the PA Lead field to allow Cal TF to develop and submit measures without a PA sponsor. An alternative is to make “PA Lead” field optional (i.e., new measure without PA lead). To ensure high quality standards are maintained, prevent measure developers from changing the status to "Submitted to CPUC" without going through "Cal TF Staff Review" and "Cal TF Affirmation" if measure does not have a PA Lead designation.
Unsync and remove "Load Shapes, Electric/Gas" CPUC Support Tables
Unsync and remove "Load Shapes, Electric/Gas" CPUC Support Tables
AI for Hybrid Measures
Use AI to generate simple, interactive calculators for measures with relatively simple formulas and algorithms and limited site-specific inputs (i.e., "hybrid"or "custom-lite"measures). Example: fuel substitution calculator for space heating retrofits (gas heating to heat pump) when baseline gas use is known from metered data.