Route planning capabilities
Some operations cover more locations than one shift allows. A Flowtlas tour can contain several dated work windows, allowing the engine to plan work across a supplied multi-day horizon with one vehicle and its assigned people. Contact us to confirm generation availability and integrations for your workspace.
The operational problem
The horizon defines the overall period being considered. Work windows define when each tour can operate within it. Supply the dates and time zone explicitly, together with any breaks, limits or resource downtime.
Product capability
If the operation needs a nightly depot visit, a hotel stop or a particular handover, model the required visits and validate that scenario. The engine does not automatically book hotels, choose accommodation or guarantee compliance with long-haul driving regulations.
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
An inspection team has a vehicle and work windows on Monday, Tuesday and Wednesday, each from 08:00 to 17:00. Sites have different service durations and some have limited access. The tour starts at a depot and must finish at a specified service base on Wednesday.
The request expresses the work periods and final endpoint. The engine accounts for travel and service within the modeled constraints. The final endpoint does not tell it to return to the depot every evening.
Questions
Yes. A tour can have several dated work windows within the planning horizon. This can model multi-day service or inspection work with one vehicle and its assigned people.
Not automatically. A specified endpoint closes the overall tour; it does not create a nightly return after every work window. Daily return requirements need to be modeled and verified.
No automatic hotel selection or booking is established by the current implementation. Supply required stops explicitly and handle accommodation decisions in the operational workflow.
The planning engine plans supplied tasks. Generating future visits from a recurrence or service-frequency rule is a separate responsibility. Confirm the app or integration that creates those dated tasks before promising an automatic recurring-visit workflow.
Work with operational context
