Field service route planning
Field service route planning assigns service visits to technicians and vans and orders the stops so that travel, time on site and customer appointment windows fit the working day. Flowtlas's planning engine models visit duration, appointment windows and technician skills together and reports work it could not assign, so coordinators can act on it before dispatch. Generation availability and integrations are confirmed for your workspace.
The operational problem
Use this model when visits have different durations, only some teams can perform specialist work, or customers provide limited access windows. Typical examples include appliance repair, telecom visits, facilities maintenance and equipment servicing.
Product capability
For each visit, supply a location, a realistic service duration and any appointment window. Add the required skills and allowed resources. For each tour, specify its vehicle, people, starting point, work windows and applicable breaks or limits.
Place each visit inside the customer's access window.
Reserve realistic time on site, from a 30-minute check to a long repair.
Keep specialist work on tours whose people carry the required skill.
Practical workflow
Supply locations, service durations, visit windows and resource requirements.
Specify vehicles, assigned people, start locations and dated working periods.
Include consistent capacity units, eligibility and stop order where needed.
When generation is enabled, inspect assignments and estimates, including any work left unassigned.
Operational benefits
In practice
A coordinator has two service vans available from 08:00 to 17:00. One customer allows access only between 09:00 and 11:00. Another repair needs a specialist skill and 90 minutes on site. A third visit is a 30-minute check with a wider access window.
The model must reserve time for the work and travel, place the appointment within its allowed window, and keep the specialist repair on an eligible tour. If an optional visit cannot fit, a partial result can make that remaining work visible for review.
The example illustrates input requirements; it does not assert that these visits form a feasible solved route without addresses, travel estimates and the complete request.
Questions
When generation is enabled for your workspace, the engine assigns visits to eligible tours using location, travel estimates, duration, time windows and skills, then orders the stops. Work that cannot fit is reported with reasons for review.
Yes. Stops can have supplied time windows, and tours have dated work windows. Include service duration and travel requirements as well so the model reflects the time the work actually needs.
Yes. Service duration is supplied for each task stop. A short inspection and a longer repair can therefore consume different amounts of the available working period.
Yes. Tasks and places can restrict eligibility, and resources can carry supplied skills. The engine uses those requirements when determining eligible tours. It does not independently verify professional qualifications or equipment records.
The request supports breaks in tour work windows and unavailable periods for resources. These are explicit planning inputs. They should not be described as a complete legal working-time or employee-roster compliance system.
Work with operational context
