2026-03-24 Executive Report - GREF

Scope, High-Level Milestones, LoE Document Completion

The v2.0 (final version) of the Atria – GREF Migration and Application Development document was completed following review and discussions, and has been uploaded to the Milvian OneDrive. It includes comprehensive details on scope, high-level milestones, functional and non-functional requirements, and a combined Level of Effort (LoE) for both GREF and Milvian. The document was also reviewed by Nikhil. It will be used as the basis for SoW creation, using the LoE specific to Milvian. A separate document has already been created for Milvian-only efforts.

v2.0 Document Reference: GREF - Atria Migration

Live Installation Support & Provisioning Issue Resolution

Jessica Hattig was provided live support during device configuration and installation verification while working/training with the India team. This included provisioning a MultiTech gateway and a Milesight sensor. Nikhil was involved to help resolve a few issues, including gateway certificate file naming inconsistencies, the sensor not checking in initially, and Milvian verified the correct device profile configuration (IN865 frequency). These were addressed, leading to a successful installation/configuration.

Potential Future Automation - GREF Device Provisioning

Currently, the Milvian team uploads device metadata documents to GREF Box, which triggers automated notifications to Nikhil’s mailbox upon upload. However, the subsequent steps - retrieving the files and executing provisioning via GREF APIs - are still manual. This gap can sometimes lead to delays and require follow-ups. Future work will focus on exploring Box automation capabilities and engaging with the Box support team to streamline and automate this end-to-end provisioning process.

Addressing Team Questions & Next Steps

Questions from multiple Milvian team members were addressed, and next steps were aligned. These include enabling the GREF Installs app (Atria) to support Asionic meters in India, creating a GREF Installs guide to help train the India team, and planning automation for retrieving device metadata files from Box and triggering downstream GREF APIs. These requests were raised by Jessica, Mac, and Garrett. This would help increase team productivity.

GREF Workspace Setup Initiated

Initial work has begun to set up Amazon Builder Tools and the Kiro IDE within the Amazon Windows Workspace, which will be used for the upcoming GREF–Atria Migration and Application Development initiative. Some permission-related issues were identified and communicated to Nikhil, who will work with the GREF team to resolve them. If issues persist, a separate Amazon laptop may be required. This early setup will help save time and provide a head start ahead of development post-SoW.

Lowlights

No major lowlights were identified this week. The documentation creation and review process was smooth and timely, and the SoW process is expected to begin shortly.

Overall

This week focused on completing and aligning on the scope and planning for the GREF–Atria Migration and Application Development initiative. The final v2.0 and LoE document was completed, reviewed, and shared, laying the foundation for SoW creation. In parallel, live support was provided for live installations and provisioning, helping unblock immediate needs. Early steps were also taken toward future automation opportunities and setting up the required Amazon development environment. Questions were addressed in a timely manner. Overall, progress was steady across planning and support activities, with no major blockers identified.