Integrate automated QA/QC tools directly within the eTRM
Integrate automated QA/QC tools directly within eTRM to reduce burden on stakeholders to perform manual checks or develop their own external tools. These QA/QC tools can include (1) checking for alignment/consistency between ex ante tables, (2) using measure property data to support claim validation and field data verification/QC, and (3) implementing measure permutation streamlining algorithms to recommend optimized permutations for new measures and major version updates.
Log in to comment and vote
Comments9
CA eTRM
Jun 15
Load Shape Verification, possibility
TechID is unique to UEC
Electric Impact Profile ID is a valid Avoided Cost Combo (may need some intergration with CEDARS to get the list of uploaded avoided cost combo)
UES = UECBase - UECMeas
CA eTRM
May 12
Quality check to ensure that Measure Detail ID is unique
CA eTRM
May 11
•Merged request
•1 vote
Make the "data spec non-conformance" error message more visible and informative
Make the "This permutation configuration does not conform to the CalTF’s standardized data spec" error message visible to all measure contributor roles and even when there isn’t an open draft. Currently, this error message is only visible to a measure developer when they have the draft open.
Should not be able to move forward with MP if there is this issue.
Also, in the error message list the fields that are not mapped correctly OR highlight those fields in the configuration panel.
CA eTRM
May 11
•Merged request
•1 vote
Automatically sort measure parameters and value tables into a preset order.
Cal TF staff has convention for the ordering of parameters and value tables. This enhancement automatically sorts the measure parameters and value tables to the preset order, ensuring compliance with QC guidelines and lessen the burden on measure developers. Measure developers can reorder the list if desired.
Alternative: QA/QC guidelines notify measure developers if the objects are out of order and suggest the ordering.
CA eTRM
May 11
•Merged request
•1 vote
Color-code unmapped fields in the permutation configuration panel
In the configure permutation fields panel, fields that are not mapped will be color- coded so that they are easier to see and correct. (ie, "unmapped" fields will appear in red).
An Anonymous User
May 10
•Merged request
•1 vote
Prevent inputs into certain fields based on the selected MeasAppType
Please consider preventing inputs into:
PreDesc, PreTechGroup, PreTechType, and PreTechID fields when MeasAppType is either the NR or NC.
StdDesc, StdTechGroup, StdTechType, and StdTechID fields when MeasAppType is either AOE, BW, BRO-Beh, BRO-RCx, or BRO-Op.
An Anonymous User
May 10
•Merged request
•1 vote
Advance the OfferingID only when the OfferingDesc has a meaningful update
Only advancing the OfferingID when OfferingDesc has a meaningful update. As I understand it, the current practice is to advance the OfferingID whenever the MeasDescription text changes from one measure package version to the next.
For PY026 measure package, updates to MeasImpactType and DelivType fields should not result in new OfferingIDs for offerings that are otherwise the same.
An Anonymous User
May 10
An Anonymous User
May 10