Route planning capabilities
Plans can change after work begins. The Flowtlas engine accepts an earlier route plan and recorded vehicle state so that another solve can take account of current positions, loads and the commitment policy supplied by the caller. Contact us to confirm generation availability and integrations for your workspace.
The operational problem
Provide the previous plan, identify committed stops, and send current vehicle positions and loads. Record the time associated with state updates. Old or incomplete state can make the new plan unsuitable even when the planning engine follows the request correctly.
Product capability
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 dispatcher receives another service request while vehicles are already working. One visit is committed and should remain protected by the request policy. The dispatcher supplies the earlier plan and the latest recorded vehicle state before evaluating remaining work again.
Review the resulting assignments and any unassigned tasks before communicating changes. This example does not imply automatic dispatch, automatic customer notifications or a continuous telematics feed.
Questions
Yes, the engine accepts an earlier plan and a commitment policy, as well as recorded vehicle position and load. The application must send accurate state and the correct previous-plan data; availability of a fully connected workflow must be verified.
Do not assume that. The engine can accept recorded vehicle positions and loads, but a data source must provide them. Current road estimates should not be presented as predictive traffic or proof that continuous GPS tracking is connected.
A configured planning agent can supply bounded advice at supported checkpoints, such as assignment preferences or a request to reconsider a limited set of work. The planning engine retains the hard constraints. The default setup does not establish an active external agent.
Work with operational context
