Every scenario on this page is an example engagement, not a client: an invented fleet with round numbers, built to show how a rollout runs. Each follows Survey, Connect, Tune and Run, and each starts from a different problem.
Example: a 60‑machine civil contractor
Example engagement. A site-work and storm drain contractor runs 60 machines from five manufacturers on jobs from Rio Rancho to Mesa del Sol. Hour meters are read by hand once a month, so services slip: two excavators passed 1,000 hours without a swing drive oil change.
Survey the yard
The onboarding lead lists 60 machines, 14 attachments and nine trailers, and scans the shop’s service binder.
Connect the machines
Thirty-eight machines join through manufacturer feeds. A crew fits A1 gateways to the other 22 on one Saturday.
Tune the service plans
The shop lead approves 250 to 2,000-hour plans per model, with swing drive oil as its own 1,000-hour task.
Run the first week
Work orders open 50 hours ahead. By Friday the shop board shows six services due within two weeks.
Example: a Permian water‑hauling fleet
Example engagement. An oilfield service company out of Carlsbad runs 140 units on leases across Eddy and Lea counties: water trucks, roustabout backhoes and skid steers, light towers and generators. A third of the leases have no cell coverage, and towers sit forgotten on finished pads.
Map the leases
Every unit is listed by lease, dead zones marked. The team agrees what a 2 a.m. generator alert triggers.
Fit for no signal
A1S satellite gateways on 15 dead-zone machines, A1s on the rest, B1 trackers on 50 towers and generators.
Tune lease alerts
Each pad gets a geofence and a three-day idle flag. Drivers move to phone DVIRs, in English or Spanish.
Run with dispatch
The dispatcher gets a daily list of idle towers on finished pads, matched to trucks already driving past.
Example: a 300 MW solar build
Example engagement. A solar builder putting up a 300 MW plant near Deming peaks at 90 machines, a third of them rented: pile drivers, skid steers, telehandlers, trenchers and water trucks. Rentals stay on rent after their block is finished, and nobody can say which ones.
List owned and rented
Sixty owned and 30 rented machines share one list, each rental with its day rate and off-rent date.
Connect both fleets
Owned machines get A1 gateways. Rentals connect through their manufacturer feed or carry a B1 tracker for the term.
Zone the array
Geofences follow the array blocks. Seven days before each off-rent date, the site manager gets a call-off reminder.
Run the Monday list
Monday’s report lists rentals idle three days or more. Two skid steers go back before the next billing cycle.
Example: a county road department
Example engagement. A county road department runs 48 units from three district yards in the Four Corners: motor graders, plow trucks, loaders, a sweeper and a water truck. Commissioners want cost per unit before they approve replacements, and the records live in three spreadsheets.
Merge three spreadsheets
Purchase dates, hour meters and two years of repair costs for all 48 units come together in one list.
Connect and inspect
A1 gateways go on graders, loaders and trucks. Operators start phone inspections in English or Spanish.
Set costs and seasons
Plow prep becomes an October calendar task. Fuel and repair records set each unit’s cost per hour.
Run the unit report
The road superintendent gets a weekly unit report. The 30-day review lists the lowest-hour units for the budget talk.
Sketch your own first month
Send your machine count, your jobs and the problem that costs you most. A person replies within one business day and walks through a plan built on your own fleet list.