Update CMPA Validation Errors to Warnings
What: Per Amy’s approval during December 19, 2024 meeting with staff, DNV, CEDARS Team, and PG&E in attendance, change the validation errors regarding CMPA ApplicationID and MeasureCode fields to warnings.
When: By mid-January 2024 to allow time for UAT and Q4 statewide claims submission due February 15, 2025.
Why: The data flow/mapping between CMPA and CEDARS may not be fully functional. As a result, several custom projects are failing CEDARS CMPA validation rules including the non-savings claims, even though the projects are already approved in CMPA.
Other:
CEDARS Team will work on the back-end data flow to process custom projects submitted to CMPA, pre and post Otter database deployment in February 2023.
Regarding PG&E claims, CEDARS Team will update the mapping for the projects included in 12/19 email RE: PG&E CMPA bimonthly list.
Featurebase tickets will be created for quarterly claims warnings moving forward so that CEDARS Team can research these claims.
- Select the module in CEDARS
- Select user type
Log in to comment and vote
Comments19
cedars team
Jan 7, 2025
This is the rules that should be changed to a warning:
Claim.CMPA_ApplicationID is empty or is in the ApplicationID valuelist.Claim.CMPA_MeasureCode is empty or is in the MeasureCode valuelist.cedars team
Jan 9, 2025
Here is a mockup of the required UI changes to the upload history and upload summary pages to add the warning validation. Any feedback is appreciated:
https://www.figma.com/proto/Ox1mKANJh2lCC4h4rhVytA/Claims---Warnings?page-id=0%3A1&node-id=1-719&viewport=161%2C344%2C0.25&t=Ec5HZC6KmRMvnyuZ-1&scaling=scale-down&content-scaling=fixed
jvrz@pge.com
Jan 9, 2025
Look as expected to me.
RoopaReddy_PGE
Jan 10, 2025
Looks good to me. Thanks.
RoopaReddy_PGE
Jan 14, 2025
@cedars team Extending the implementation date to end of January is fine with PG&E.
I will send the list of missing CMPA codes for PG&E’s Q4 claims via email.
RoopaReddy_PGE
Jan 14, 2025
Please refer to email with subject line “Missing PG&E CMPA codes - 1/13”.
Filename is Missing_PG&E CMPA Codes_2024 Claims_1.13.2025.xlsx.
Jennifer Scheuerell
Jan 17, 2025
@RoopaReddy_PGE This work is up on testing/3 for review:
https://cedars-3.cpuc.ca.gov/claims/specification/data-rules-claim/
Please let us know any feedback.
RoopaReddy_PGE
Jan 17, 2025
@cedars team Will do. Thank you.
cedars team
Jan 14, 2025
The development has flagged that finishing this by the end of Sprint 1 (21st January) may not happen. Is having this in production by the end of January acceptable? Craig has completed the work of bringing PGE legacy projects into Otter.
RoopaReddy_PGE
Jan 18, 2025
@cedars team
I tested Custom (core and meter-based) claims for the following use cases:
Test results were as expected. Please refer to the upload details and QC feedback here: https://cedars-3.cpuc.ca.gov/claims/upload-summary/359/
Custom claims with null CMPA Application ID and Measure Code – records failed with Application ID errors, but no Measure code errors (since the rule does not specify that the measure code is required)
Custom claims with invalid CMPA Application ID and Measure Code – records successfully loaded but with Application ID and Measure Code warnings
Custom claims with valid CMPA Application ID and Measure Code – records successfully loaded with no errors or warnings
FYI
CEDARS revised rules
Thank you
RoopaReddy_PGE
Jan 21, 2025
@cedars team
I tested the CMPA revised rules with SW upload and the test results were slightly different from PA upload in regard to Upload history status and test records #1,4 errors.
I used the same test data as the PA upload except I updated the Claim, Site, Contact, and Program IDs with SW IDs.
Compare SW Upload https://cedars-3.cpuc.ca.gov/claims/statewide/upload-summary/45/ vs PA Upload https://cedars-3.cpuc.ca.gov/claims/upload-summary/359/ in cedars-3.
SW Upload
Upload History status is “passed with warnings”, while PA upload status is “record_ errors”.
I was expecting ClaimIDs SW-2024-test5 and SW-2024-test8 to fail with CMPA_ApplicationID is empty error, but there were no errors.
Please advise.
RoopaReddy_PGE
Jan 22, 2025
I emailed the test upload batches to CEDARS team on 1/21/2025 since cedars-3 got refreshed and test data/results got wiped out.
cedars team
Jan 22, 2025
@RoopaReddy_PGE The development team has created a new ticket for the issue where the validation is inconsistent between local and statewide claims because it appears to be a bug also present in production.
https://cpuccedars.featurebase.app/p/inconsistent-validation-between-statewide-and-local-claim
I received some feedback from the development team that I want to ensure aligns with your expectations of the rules:
"Claim.CMPA_ApplicationID is empty or is in the ApplicationID valuelist.
As best I can tell, the CMPA_ApplicationID field is empty for the records with claim IDs SW-2024-test5 and SW-2024-test8. This satisfies the rule, and so it looks to me like the fact that no errors are generated there is the correct behaviour."
RoopaReddy_PGE
Jan 22, 2025
@cedars team Please refer to the last column in the image below for my interpretation of the revised rules regarding SW upload test batch:
CMPA_ApplicationID field is empty for the records with claim IDs SW-2024-test5 and SW-2024-test8 and do not satisfy the rule “Claim.CMPA_ApplicationID is required when Claim.ClaimID does not end with one of ('Audit', 'Placeholder') and Claim.ClaimType equals 'Custom' and Measure.MeasImpactType does not start with 'Cust-NMEC-Pop' and Program.ProgramCategory does not equal 'Energy Savings Assistance' and Program.ProgramSegment is populated and Program.ProgramSegment does not equal 'Codes and Standards'.“
Please advise if I understood the rules incorrectly.
cedars team
Jan 23, 2025
We believe that this rule is functioning as intended. Claim IDs SW-2024-test5 and SW-2024-test8 will be exempt from the rule, as we assume their Program.ProgramSegment will be empty due to being statewide.
Claim.CMPA_ApplicationID is required when Claim.ClaimID does not end with one of (‘Audit’, ‘Placeholder’) and Claim.ClaimType equals ‘Custom’ and Measure.MeasImpactType does not start with ‘Cust-NMEC-Pop’ and Program.ProgramCategory does not equal ‘Energy Savings Assistance’ and Program.ProgramSegment is populated and Program.ProgramSegment does not equal ‘Codes and Standards’.
We have tested this in both the testing and staging environments, and everything appears ready for deployment.
If the rule is not working as expected and SW should not be excluded from the validation, we can bring this ticket
https://cpuccedars.featurebase.app/p/inconsistent-validation-between-statewide-and-local-claim into an upcoming sprint. Otherwise, if the statewide exemption is expected, I can close that one.
RoopaReddy_PGE
Jan 23, 2025
@cedars team
Thanks for the explanation regarding my comments on the SW upload test batch. Makes sense to me.
Regarding the question if the validation should apply to SW claims or not - in my opinion, the rule must apply to “all” custom claims including SW. Please get feedback from the other stakeholders before finalizing the path forward.
Program Segment mapping for SW programs is straight forward since Program.ProgramSegment is already mapped for the corresponding PA specific SW Program IDs.
RoopaReddy_PGE
Jan 23, 2025
@cedars team
I agree that the revised rules are ready for deployment.
Depending on stakeholder input regarding SW should be exempt or not, the status of the following ticket can be determined for the upcoming sprint: https://cpuccedars.featurebase.app/p/inconsistent-validation-between-statewide-and-local-claim