Scheduling, asset, and crew systems re-platformed to the cloud, with a mobile experience designed for the places the network does not reach.
The challenge
A utility’s field systems ran on servers that had become a single point of failure for every crew in the province. Migration was overdue, but field teams worked in locations with no connectivity, and the previous mobile application had quietly been abandoned in favour of paper.
Our approach
We migrated the back-office systems service by service, rebuilt the mobile tools to work offline by default and synchronize when a connection was available, and ran both paths in parallel through a storm season before decommissioning the original servers.
What we built
- A landing zone with security controls and cost allocation from the outset
- Service-by-service migration with rehearsed rollbacks
- An offline-first mobile application for crews, tested in the field
- A telemetry pipeline for asset data, with alerting
- Runbooks and on-call design for a small operations team
What changed
- No single server can take every crew offline
- Field teams retired paper because the application works where they do
- Costs are visible by system and owned by a named individual
This engagement is representative of the work Loonwise undertakes; client names and specifics are shared in conversation.
Contact
From ambition to working software.
Whether you are accelerating AI adoption, modernizing a critical system, or building the capabilities to innovate faster, we bring the consultants who scope the work and the engineers who build it—the same people, from the first conversation. A senior engineer responds within one business day.
Get in touch