Field note 03 · Heavy civil operations · CMMS, ERP & field data
Weekly meter-hour updates from 4 hours to 20 minutes
Several weekly fleet tasks had predictable inputs but were done by hand. Power Automate flows (cloud and desktop) now do the work.
Built by RootN’s founder as an engineer inside a Western Canadian heavy-civil contractor’s equipment operation. The employer and its systems are not named.
- 4 h → 20 min
- weekly meter-hour update
- ≈190 h
- of admin time a year back (3 h 40 min × 52 weeks)
- 4 flows
- meter hours, approvals, locations, purchase orders
- No API?
- Desktop flows bridge the gap
The situation
An admin spent about 4 hours a week moving equipment meter readings from Excel into the fleet system. Timecard approvals in the construction ERP had to be clicked through one record at a time, and equipment location changes and placeholder purchase orders were entered by hand.
What was built
A Power Automate flow runs the meter update from a prepared Excel file. Where the ERP had no API for a task, desktop flows perform the clicks for bulk timecard approvals, location changes and placeholder purchase orders. These are an interim step, with a defined path to API integration.
The result
The weekly meter update takes about 20 minutes instead of about 4 hours, roughly 190 hours of admin time a year. Approvals, location changes and placeholder POs no longer need record-by-record entry.
What’s still manual
Preparing the meter-reading file. UI automation also needs watching when ERP screens change, which is why API integration is the long-term route.
What this means for you
Where the same pattern applies
Any task with a predictable input and a fixed set of clicks is a candidate, especially the ones done every week.