Planning on planboard
βNavigate to the Planning Tab-orders to plan: Go to the Planning tab and choose the "Orders" + to plan section. (You can also customise your planning view or plan a trip also see π customise planning view)
β
βApply Filters(if applicable): To narrow down your selection, use filters based on date, customer, or any related fields such as πplanning group. (also see π customise planning view)
β
βSelect the Order: Highlight the specific order you want to plan a trip.
Initiate Trip Planning: Click on the "Plan New Trip" button to start the trip planning process.
β
βDefine Resources and Save: Make selections for the resources associated with the trip and save your choices.
βNote: If a resource(combination) is already in use for the selected day, you will see the lined view with the locations as marked below.
βView Trip on Board: Once the trip is planned, it will be visible in the board view, providing an organised overview.
If there was a previously used trailer or container for the same resource set you made the planning for, you will get suggestions to add these in the trip once you have planned it. To assign the same trailer or container, simply click on the texts to have your trailer in your new trip:
β
β
If the resource has already been added in the planboard via "πalways on planboard toggle" or by adding via the resources page in πplanning, you can also drag the specific order to the line of the resource to plan a trip.
β
Planning a Time Window.
If the πtime window on the first stop in your order is enforced, the trip will be planned taking the enforced time into consideration. An 'βEnforced Time' icon (lock) can be found under the order start/end details, in planning:
If attempting to plan the trip outside of the enforced time, the trip will default to the planned time. βFor example: if you have an enforced time window in your order for collection, regardless of which hour you drop the order in the planning, it will automatically get transferred to the start time of the enforced time-window:
If the order has been planned , but does not match with the time window set for a stop activity, you will get a VIOLATION. This can occur when the FIRST stop conditions are satisfied (enforced or not), but a subsequent stop has an enforced time window that cannot be met; for instance if there are multiple stops, or if the delivery is the stop with the enforcement. The order can be planned outside of the enforced time window however the stop that is out of scope, will show a violation (RED/ORANGE) on the Planning Board.
Click on the stop to open, it will show the violation, along with the planned time outside of the window.
If the 1st stop is NOT enforced and planned AFTER a stop with an enforced time window, the trip will be planned outside of the enforced time window. The trip will show a VIOLATION in red for the affected stop.
You can adjust the arrival time and duration with the calendar icon located next to the estimated hours. The options to modify the time include:
Set the arrival time (manually set)
Calculate the arrival time
Enforce the time window
In addition to above, duration of the stops is also adjustable in the Planboard by simply dragging the route bar to left or right. If changing the stop duration creates an issue with an enforced time window on another stop, the stop will show the warning by turning Orange. The stop can be readjusted to bring the trip back into compliance.
Tip: Qargo uses the distance to calculate estimated times of the routes.
Planning by adding resources to the order
Planning a trip is also possible by simply adding resources to your order as below:
You can then view it afterwards in the planning by navigating to the planboard:
β
All your planned trips will then be visible also in a listed view under the "Trips" column where you can apply filters, πcustomise columns and πexport data.
β
For planning multiple orders in 1 trip(Groupage): πPlanning trips in bulk (groupage)
For planning Empty Trips πEmpty trips
Generating trip documents: πGenerating Trip Documents
Dispatching trip to the drivers: πDispatching the Trips
β
β