¶ Crossdocking/splitting
Redetermine plan group when splitting
- If Yes, the plan group of plan lines will be redetermined by the plan group determination after splitting
- If No, the plan group of the split lines will remain the same as the order leg
Update plan group when splitting
Updates the plan date after splitting
Update plan date when undoing splitting
Updates the plan date after unsplitting
¶ Planning
Check constraints when planning resource
Checks when planning a resource on a trip whether there are constraints (features of e.g. an address that does not match the planned resource on a trip).
Check constraints when planning shipment
Checks when planning a shipment on a trip whether there are constraints (features of e.g. an address that does not match the planned resource on a trip).
Check route calculation with flags
If this is set to yes, a trip cannot be flagged if the route calculation of the resource combinations in the trip are not all set to Ok. This can be found under the costs tab:
Check loading date/places/postcodes/regions
Checks when planning whether this information has been entered in the order, otherwise the order cannot be planned
Request disconnection date
If this is set to yes, Transpas asks for the disconnection date.
Otherwise, the date of the departure date/time of the selected trip activity is selected.
Request coupling date
If this is set to yes, Transpas will ask for the coupling date.
Otherwise, the date of the arrival date/time of the selected trip activity will be selected.
No confirmation when descheduling
If this is set to no, Transpas will not ask for confirmation when a shipment is descheduled.
Warning limit when changing date/time
If the date of a trip activity is changed, Transpas can issue a notification:
You can enter the number of days from here.
For example, if this is set to 2, Transpas will issue a notification if the date of a trip activity is moved forward or back 2 days, but not if it is moved back 1 day.
Request for loading vehicle
When planning a shipment on a journey with multiple loading vehicles (e.g. LZV or combi), you can be asked in which loading vehicle the shipment should be planned.
Planning order
This setting ensures that multiple unplanned orders are placed on the journey in a certain way. You can choose from:
- Loading order: The selected orders are placed on the journey in the selected loading order
- Unloading order: The selected orders are placed on the journey in the selected unloading order
- Loading > Unloading: The selected orders are placed on the journey as loading, unloading, loading, unloading
Connect loading actions
This setting ensures that the loading activity is placed in the correct position within the series of the same loading address.
Connect unloading actions
This setting ensures that the unloading activity is placed in the correct position within the series of the same unloading address.
Update loading order
This setting ensures that when an unloading activity is moved within the trip, the associated loading activity is moved in the opposite direction.
Update unloading order
This setting ensures that when a loading activity is moved within the trip, the associated unloading activity is moved in the opposite direction.
Using the SHIFT key, the behavior can be reversed for both settings. So when the setting is on, it is done by default, but with the SHIFT key it is not done. When the setting is off, it is not done by default, but with the SHIFT key pressed it is.
Smooth undo-uncoupling
Allow uncoupling of cargo vehicle
Check resource agenda
Agenda check offset
Always start trip at location
Always end trip at location
If this is set to yes, the location address is filled in for coupling / uncoupling.
The location address can be entered in:
- Vehicle / Vehicle / Location address
- Plan group / General / Location address
- Company screen / Planning / Planning / Other / Location address
The search is from top to bottom, i.e. the location address of the vehicle has priority over the location address of the planning group.
Always start trip at location can also be set per resource type (this has priority over the setting on the Extra parameters tab). See resource type settings.
¶ Time calculation
Stop duration group
The stop duration group that is used on trips in this planning group. In a stop duration group you can record how long a certain activity lasts.
Default start time trip
When a trip is created, the start time can be set automatically.
Calculate times
Setting that ensures that the time calculation takes place in the trip. For this it is important to set a correct start time of the trip or to enter it for each new trip.
Time calculation preference
With this settings you can influence how the plandate of a shipment is chosen.
This is explained in the article Planning better: routecalculation and following vehicles
Start time day
End time day
The times calculation in this planning group takes into account start and end times where no planning is done. If unloading is later than the end time of a day, unloading is postponed by one day.
Use realized times
With this setting you can indicate whether the times fed back by the on-board computer should also overwrite the planning times. Important for an ETA calculation.
Continue calculation in flagged trips
If you set this to Yes, Transpas can still recalculate flagged trips. If you set this to No, a trip will no longer be recalculated after it has been flagged.
Fix flagged trips
If you set this to Yes, Transpas will no longer update the times and kilometers of a trip. On-board computer messages that come in after a trip has been flagged can be seen in the On-board computer messages tab, but nothing is done with them anymore.
Update execution order
Sometimes the driver carries out the activities in a different order than the planner has specified. With this setting you can ensure that the feedback from the driver via the on-board computer in the order in which he carries it out also automatically adjusts the trip in that order.
¶ Automatically finish trips
Trips autom. finish after # days
The planning group can be used to set all trips in that planning group to be automatically flagged after x number of days.
See also Flagging trips
Check truck
A trip without a truck is not automatically finished.
¶ Standard screen filters
¶ Reports
Print goods lines on reports
In the standard charter faxes (reports 21 and 22) this setting is used to print or not print goods data.
¶ Communication
Stop method
A stop method makes it possible to group on-board computer tasks into one stop.
This simplifies the driver's work: suppose the planning is set up in such a way that 10+ shipments are often loaded at the same address. It is then useful to group the loading activities, so that the driver can register this task with one push of a button, instead of having to do this for each shipment separately.
There are 5 possible stop methods:
| Do not group | Tasks are not grouped |
| Group only loading activities | Only the loading tasks are grouped into one stop |
| Group only unloading activities | Only the unloading tasks are grouped into one stop |
| Group loading and unloading activities | Loading tasks and unloading tasks are both grouped. When unloading and loading at one location, these become two tasks. |
| Group loading and unloading together | Loading and unloading tasks are grouped together into one stop. |
Status update within radius of # kms
With these settings, the on-board computer can influence the overwriting of the pre-planned date/time. Within the radius, a date/time can be adjusted by the driver from the on-board computer, outside the radius Transpas does not do this.
An example: the driver starts loading. He forgets to fill in an end of loading and reports "end of loading" at the next stop, 10 kilometers further.
If "8" is filled in for status update within radius of # kms, this is not adjusted in the trip because the status update was done at a distance of more than 8 kilometers, namely 10 km.
This applies to all tasks, so start of trip, loading, unloading, cleaning, etc.
Status update within time of # hours
This setting is used more often than the Status update within radius of # kms.
If a date/time is entered from the on-board computer for a trip activity, and these differ more than the number of hours entered here, Transpas will not adjust the planned date/time.
If the planning is quite tight, you will enter a low number here. If the pre-planned times in a trip can deviate considerably from the actual trip times, enter a high number here.
An example: a driver forgets to report unloading. He does this the next day, 10 hours after the planned unloading time. If 8 hours is entered for Status update within time of # hours, the unloading time will no longer be adjusted, because this is 8 hours after the planned time.
Back to