2026-03-10 Executive Report - GREF

Atria Migration & GREF Applet Development

Initiated planning discussions with the GREF team for the upcoming GREF-specific Atria migration initiative. The initiative involves migrating the Atria platform to the GREF AWS account, porting and adapting the system to operate within GREF’s AWS infrastructure, Git repositories, CI/CD pipelines, tooling, and engineering standards.

Held a detailed discussion with Nikhil to review the current Atria code structure and architecture. This knowledge-sharing session provides the necessary context for the GREF team to assess migration complexity and plan the architectural transition, helping ensure the migration path is well understood across both teams.

Post-migration, a new applet - tentatively titled “GREF Device & Site Health Report” - will be deployed to this Atria instance to deliver site and device telemetry from GREF APIs to installers on-site. This SoW-based engagement provides the first direct revenue opportunity for Atria and opens the door for future work within Amazon/GREF environments.

Required Documentation & Estimated Timeline Discussion

Aligned with the GREF team on the documentation required before the project can formally begin. This includes a high-level milestone document and Level of Effort (LoE) estimate from the GREF side for the migration effort. Once available, Milvian will create a corresponding LoE will be prepared for the GREF Site & Device Health Report applet development, followed by the Statement of Work (SoW) needed to initiate the project.

Preliminary discussions indicate the Atria migration and app development effort may take approximately 1.5 months, with efforts planned to run in parallel. Development of the GREF Site & Device Health Report applet is estimated at 4–5 weeks, plus a one-week buffer. These timelines remain preliminary and will be refined as scope details are finalized.

Infrastructure Preparation

Initial infrastructure preparation has been started by Nikhil within the GREF environment. The GREF team has started setting up the required permissions, package access, AWS account configuration, and CI/CD pipeline readiness needed to support the migration and subsequent development work.

India ModBus Decoder Sync

Organized a call with Faris Jamil, Matt Burns and Nikhil(GREF) regarding handling GREF India sites where existing energy meters communicate only via Modbus RTU. The team is exploring the use of a Modbus-to-LoRaWAN converter to retrieve data from these meters without replacing the hardware.

Nikhil will work on implementing the required decoder and testing the Modbus-to-LoRaWAN workflow with Matt. The tests will determine whether device-specific changes to the decoder are needed for different meter types or if the integration can be applied broadly across similar deployments at GREF India sites.

Lowlights

Awaiting Documentation from GREF

Progress toward project initiation is currently dependent on receiving the milestones and LoE documentation from the GREF team. Nikhil, who is responsible for providing these documents, has been out sick since Monday and responses to follow-ups are pending. Since Milvian’s LoE document and Statement of Work (SoW) depends on these documents, the start of development activities may be delayed until they are finalized.

Overall

In the past week, the GREF initiative progressed from early discussions to structured planning. Architectural alignment has begun, documentation requirements and preliminary timelines have been clarified, and infrastructure preparation has started within the GREF AWS environment. Once the remaining documentation is finalized, the project will be positioned to move into active execution.