Highlights: Achievements and Impact

This week, several initiatives and tickets were successfully completed, resulting in measurable improvements in operational efficiency, data quality, system reliability, and user experience for both sustainability reporting and device health monitoring:

Installer and Device Queue User Experience Improvements:

·      Impact: Lower installation errors and reduced need for rework, leading to improved data integrity and increased installer productivity. These changes have a positive effect on risk management, cost reduction, and organizational reputation.

·      Actions Taken: Safeguards and workflow fixes were implemented, including image retention across navigation, warnings for existing devices in the queue, prevention of duplicate EUIs, and enhanced persistence during reloads or new JSON uploads.

Reporting Enhancements for Site Report and Device List:

·      Impact: Enables more informed operational decisions and reduces unnecessary noise in reporting, benefiting business, sustainability efforts, and risk management.

·      Actions Taken: Invisible filters were introduced to exclude legacy devices, warehouses were added to the Site Report, header behavior was improved, gateway context and sensor value visibility were enhanced, and install date visibility was supported.

Troubleshooting Enablement via CSV Exports and Documentation:

·      Impact: Accelerates issue resolution for meter and vendor investigations, leading to a decreased support burden and improved risk and cost management.

·      Actions Taken: Documentation for CSV exports was delivered, and the export of sensor readings was enabled to support troubleshooting such as Subeca meter investigations.

Reliability and Access Improvements:

·      Impact: Minimizes downtime and support escalations, thereby increasing user trust and reducing risk and reputational concerns.

·      Actions Taken: Resolved double login issues, fixed DeviceList access errors (404/400), improved password reset for migrated users (including verified emails and confirmed states), and removed self-signup in favor of admin-managed access controls.

GREF Enablement Assets (Process and Training Materials):

·      Impact: Facilitates faster and more consistent installations, enhancing cross-team preparedness and reducing business and risk concerns.

·      Actions Taken: Developed provisioning, configuration, and installation flowcharts; produced an installation and JSON creation app video.

Data Model and Backend Enhancements:

·      Impact: Delivers more accurate reporting and simplifies long-term data querying while reducing technical debt for the business and risk areas.

·      Actions Taken: ProvisioningTime is now saved for sensors and gateways, Gateway Health was added to DynamoDB, decoder/lambda handling for pulse base DevEUIs was updated, and precision for Site Health Report display was increased to three digits for kW values.

Lowlights: Challenges Encountered

This week, several key issues were identified and addressed through fixes or mitigation efforts:

PDF Site Report Generation Mismatch/Failure:

Description: The PDF version of the site report was malfunctioning and did not align with the on-screen report.

Impact/Risk: Risk to reporting reliability and customer trust for formal deliverables.

Mitigation/Next Steps: Fixes to PDF generation and alignment were implemented. Continued monitoring is recommended, using a regression suite with representative sites.

Site Report Performance Slowness:

Description: The site report experienced performance issues, impacting installers and end users.

Impact/Risk: Productivity loss and increased risk of installation delays.

Mitigation/Next Steps: Root causes were investigated and improvements were made. It is recommended to track load times and set up alerts for performance regressions.

Legacy/Duplicate Device Noise in Atria:

Description: Historical and legacy devices, as well as pulse base DevEUIs, generated confusion and unnecessary noise in the UI and email communications.

Impact/Risk: Operational noise, increased support burden, and risk to reputation if data appears inconsistent.

Mitigation/Next Steps: Filtering and visibility controls were implemented, and base DevEUIs were excluded when appropriate. A proposal was completed to formalize a long-term strategy for addressing these issues.