The following is a guidline for work being done by the sustainability backend team. In addition to the roadmap below we are also driving the discussions with current and potential customers in Amazon GREF and WWOps (EU Water, US Water, etc.), and meeting their needs for monitoring and maintenence of the LoRaWAN Platform (aka “BMS”).

Projects and Ownership

There are several projects worked on by the Sustainability engineering team. Atria and Gref work is currently in development, and the LoRaWAN Platform and Wirefree Quicksight Dashboards are considered under maintenance, with tasks and adjustments made to support our relationship with Amazon and their business needs.

The following are the product owners associations to each given project, who expect direct reports regarding updates to the given project.

Atria - Kristie Lanum (Milvian)

LoRaWAN Platform (BMS) - Francesca Stobbione (EU Amzn) / Nicholas Harrison (NA Amzn)

Wirefree Quicksight Dashboards - Francesca Stobbione (EU Amzn) / Nicholas Harrison (NA Amzn) / Leo Liu (Amzn)

GREF - Nathan Wesselius (Amzn)

Atria/WWOps/BMS

Q1 Carry-Over / Wrap-Up

These items are either in-flight from Q1 or have remaining scope that didn't close out.

1. Site Survey Application — Final Close-Out

• Status: Development complete; QA pending from hardware team

• Key Tasks:

  • Hardware team QA pass and sign-off

  • Resolve any QA-reported bugs

  • Final deployment and project close-out

2. Notifications — Full Implementation

• Status: Basic layout completed in Q1

• Key Tasks:

  • Complete notification subscription management (Chimes in-app)

  • Email notification architecture (Outlook integration design and implementation)

  • Integration with Data Verification stack (battery check, device down alerts)

  • End-to-end testing of notification delivery

New Q2 Priorities

4. Site Report Dashboard (Dashboards Applet) : Data Security

• Status: Water and KPI dashboards completed; Site Report dashboard pending

• Key Tasks:

  • Build Site Report dashboard within the Dashboards Applet

  • Tagging system for user-based access control (ties into Data Security below)

  • QA and deployment
    Subeca T & Q Values — Flow and Usage Enhancements

• Objective: Surface additional Subeca telemetry (Temperature & Flow Quality values, usage) and enable flow-related notifications

• Key Tasks:

  • Add T & Q values and flow/usage data to relevant views

  • Excel sheet export support

  • Flow notification alerts (no flow, pulse count not incrementing)

  • Integration with Notifications stack

5. PEM Electricity Dashboard

• Objective: New dashboard within the Dashboards Applet for PEM electricity monitoring

• Key Tasks:

  • Requirements gathering with stakeholders

  • Dashboard design and implementation

  • Deploy within Dashboards Applet

6. Door Open/Close Stats Dashboard

• Objective: Display door open/close statistics for operational visibility; extend to US dock door data

• Key Tasks:

  • Define metrics and visualization requirements

  • Build dashboard (shared data model for both use cases)

  • Deploy and validate with stakeholders

7. Site Decommissioning Workflow

• Objective: Establish a best-practice workflow for decommissioning sites

• Key Tasks:

  • Document decommissioning process and requirements

  • Implement workflow tooling in Atria (device removal, data archival, status updates)

  • QA and stakeholder review

8. Feature Request Form

• Objective: Provide product owners with a structured way to submit feature requests

• Key Tasks:

  • Design and build feature request submission form

  • Routing/notification to engineering team

  • Deploy

Backlog / New Work (Target: Mid-to-Late Q2+)

These are larger initiatives that will be scoped and scheduled as bandwidth allows and business priorities dictate.

9. Aqueduct Atria — Fork and Refactor

• Goal: Replicate and tailor Atria for Milvian Aqueduct / BMS environments

• Key Tasks:

  • Identify shared assets and define fork architecture

  • Establish pattern for Atria forks (shared core, environment-specific modules)

  • CDK infrastructure for rapid deployment

  • Initial implementation

10. LoRaWAN Platform — CloudGate Support (Egypt Project)

• Goal: Enable deployment in Egypt via CloudGate devices (no LoRaWAN licensing required)

• Key Tasks:

  • Finalize implementation document (scope, architecture, integration)

  • Confirm schedule once Egypt project dates are set

  • Execute development and rollout

11. QR Code & Ticket Printer System

• Goal: Eliminate manual EUI entry for installers

• Key Tasks:

  • QR code generation for device EUIs

  • Ticket printer integration

  • Installer-facing QR scanning workflow

  • Backend validation and provisioning

Ongoing

• Platform Enhancements: Pulse Rate Installation Modal/Calculator, Installation Summary legacy device import improvements, UX enhancements, ticketed bug
  fixes . Dashboard improvements(Water)

• Maintenance: LoRaWAN Platform (BMS), Wirefree Quicksight Dashboards, GREF — pivot to support requests from respective owners (Francesca, Nicholas, Leo,
  Nathan) as needed

• Customer Engagement: Continue discussions with Amazon GREF and WWOps stakeholders

• Hardware Team Support: Available as needed

GREF

Objective:
Deploy a GREF-specific version of the Atria application in the GREF AWS account, leveraging their AWS infrastructure, Git repository, CI/CD processes, tooling, and engineering standards.

Post-migration, a new applet - tentatively called “GREF Device & Site Health Report” - will be developed and deployed within that Atria instance. The applet will consume data from GREF-provided APIs and provide site/device health and telemetry information to installers and other team members, enabling them to verify installation and device configuration status and confirm successful site/device setup.

This will be executed as a SoW-based engagement, creating a direct revenue opportunity for Atria and enabling possibility of future development/related work within Amazon/GREF environments.

Note:
Currently in the initial phase. Work is expected to begin soon - before the end of Q1 - and continue into early Q2.

Key Phases:

Work Across All Phases:

• Resolve issues with GREF CI/CD pipeline, AWS environment, scanning tools, testing etc.

• Bug fixes and unforeseen issues.

Expected Outcomes:

• Address GREF security and governance requirements

• Replace the existing email-bot workflow with a more efficient application-based solution

• Enable installers and other members to perform real-time installation/device config verification

• Provide a robust and scalable solution that directly consumes data from GREF APIs, removing SES-related roadblocks