Features
Each technician's day, in the order that makes sense.
Eight visits in a day, each in a different corner of town. The order they are done in decides whether the technician finishes at four in the afternoon or seven at night. Atus route planning works that order out over real roads, respects the stops you need to pin, and shows — before the technician leaves — how much of the day will be driving and how much will be work.
- One route per technician per day
- Distances and times over the real road network
- Optimized order, with pinned stops when needed
- Start point, departure time and return to base
- Map, stop list and day summary
- Jobs with no address flagged, without blocking the route
A technician, a day and the jobs to visit
Planning starts with the technician and the date. You set the starting point, the departure time and whether they return to base at the end of the day, and pick the open work orders that go on the route.
The system returns the visit order, a map of the path, the stop list with expected times and a summary with the number of stops, distance, travel time and time in the field.
Indicadores · Planta Joinville
Últimos 30 dias
MTBF
212h
MTTR
3,9h
OEE
84,2%
Backlog
11 OS
Evolução do backlog (semanas)
Over roads, not as the crow flies
The cost between stops comes from the road network — real distance and driving time, one-way streets and detours included — not the straight-line distance on a map.
Over that matrix, the optimizer builds a first path by nearest neighbour and then refines it by swapping segments until no improvement is left. At the scale of a technician's day, that lands within a few percent of the ideal path in a fraction of a second.
Pinned stops for what cannot move
Some visits have a set time: the customer only opens at eight, the plant-room key is handed over late in the afternoon. Those stops can be pinned to a position on the route, and the optimizer arranges the rest around them.
The route can also be reordered by hand and re-optimized while it is still a plan. Work orders already in progress are not moved — their position is a record, not a plan.
Addresses become coordinates
Customer addresses are converted into coordinates, and each customer can have several sites registered with their own location.
If a work order cannot go on the route — no address, no coordinates, already on another active route or already finished — it is flagged with the reason, and the other fourteen are routed as usual. One missing address never blocks the day's plan.
One job, one active route
Every route has a status — accepted, in progress, completed or cancelled. A work order can sit on only one active route at a time, which stops two technicians being sent to the same job. Cancelling or completing a route returns its pending work orders to planning.
A routed day in practice
The technician has nine jobs tomorrow, spread across town, and one customer who only opens at eight. The manager picks the technician and the date, sets departure from base at half past seven, pins the eight o'clock customer as the first stop and asks for the optimization.
The route comes back with the order of the other eight visits, the path on the map and the day summary: distance, travel time and time in the field, worked out from each job's estimated hours. One of the jobs had no coordinates; it shows up separately, with the reason, so someone can fix the address.
Frequently asked questions
What every maintenance manager asks before buying.
Keep exploring
Create, prioritize and track work orders with checklists, photos, parts, signatures and an audit trail. Four types, seven statuses, branded PDF reports.
Preventive plans that open their own work orders: nine frequencies, end by date or count, inherited checklists and a month, week and day schedule.
An Android and iOS app where technicians run work orders with no signal: checklists, photos, parts and signatures stay on the phone and sync on reconnect.
Per-work-order or fixed-fee contracts with billing periods, validity and auto-renewal, percentage or manual price adjustments and covered assets.
Ready to put control, audit and AI in one ecosystem?
See Atus running against your own scenario in a 30-minute demo.