Operational planning examples
A delivery job can involve more than a single destination. Flowtlas's planning engine models an ordered chain of stops as one task, so a collection and its delivery stay together while vehicle load changes along the route. Contact us to confirm generation availability and integrations for your workspace.
The operational problem
Supply the pickup and delivery locations in order, the duration of work at each stop, and any visit windows. Record how much load is added or removed, the vehicle's capacity and any load already on board. Include restrictions when only certain resources can handle the task.
Product capability
Some jobs include an explicitly supplied reload, disposal or intermediate service stop. The task model can express an ordered chain, but a stop label does not automatically choose the best facility, manage inventory or add industry-specific rules.
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 vehicle with capacity for four pallets starts empty. The job adds two pallets at a depot and removes those two pallets at the customer site.
This ledger explains capacity arithmetic for one fictional job. It is not a calculated plan. When other jobs share the route, their load changes and visit windows also affect the plan. For multiple capacity dimensions, each relevant quantity needs consistent units and limits.
Stop: Start; Load change: 0; On-board pallets after this stop: 0
Stop: Pickup; Load change: +2; On-board pallets after this stop: 2
Stop: Delivery; Load change: -2; On-board pallets after this stop: 0
Questions
Yes. A task can contain ordered stops, keeping its pickup and delivery within one task on the same tour. Supply the locations, durations, visit windows and load changes for each stop.
Yes. Positive and negative stop changes describe load being added or removed. Supply the starting load and capacity consistently so every point along the route can be evaluated.
The engine supports named capacity dimensions, so a request can describe several quantities. Use consistent names, units and integer values across capacity and load fields. This is a capacity model, not a physical packing or automatic unit-conversion system.
An explicitly supplied task chain can include these stop actions. The caller must provide the locations, sequence, durations and load effects. The action name alone does not select a facility or enforce industry-specific operating rules.
Work with operational context
