Road freight management system with driver workspace
Dispatcher passes the driver the tasks of the trip and sees their progress. The delay can be discussed with the customer in time, and delivery documents can be handed over to the settlement.
The customer's modified cargo, stop or term information is rewritten and does not always replace an already planned order. Dispatcher, driver and customer can rely on different execution conditions.
How the solution works
- The order is assigned to an executable sequence of journeys with proper transport and driver.
- Driver facts and movement data show the execution and required dispatcher reaction.
- The result of the delivery and the documents are checked until the responsible completion of the order.
Key challenges
- Orders are manually moved to TMS
- Fleet and driver capacity information is fragmented
- Return loads planned too late
- Arrival time not reliable enough
- The journey documents are collected and checked manually
Solution capabilities
Ordering and the sequence of voyages
Cargo, stops and time windows are associated with proper transport, driver availability and further obligations.
Validation of the principal
The own driver or partner receives a topical task. A significant change has an acceptance response.
Driver workspace
Stop instruction, delivered quantity, wait and recipient's notes are provided with evidence linked to the particular trip.
Arrival information
The shipment is associated with real transport and remaining stops. The forecast is provided with upgrade times and known uncertainty.
Delays and document deficiencies
Dispatcher receives the affected order and follow-up action. Delivery confirmation, missing document and additional work payment are completed separately.
Business context
- Orders are manually moved to TMS
- The customer's modified cargo, stop or term information is rewritten and does not always replace an already planned order. Dispatcher, driver and customer can rely on different execution conditions.
- Fleet and driver capacity information is fragmented
- Transport occupancy, cargo fitness, driver availability and partner acceptance are checked unconnected. By promising a capacity that cannot be used at a specific time or conditions.
- Return loads planned too late
- The possibility of return cargo is assessed by close location and price, without checking the continuous sequence of works and other commitment. Additional cargo can reduce one empty section but create a longer wait or violation of a subsequent order.
- Arrival time not reliable enough
- The arrival forecast uses a transport location but lacks data for the remaining stops, driver's work and rest and loading end. The customer is given an excessively accurate time, and the dispatcher notices the delay too late.
- The journey documents are collected and checked manually
- The documents, notes and additional waiting facts received by the driver return not to be linked to a specific version of the order and required confirmation. After delivery, it is necessary to collect additional evidence and to find out if the documents are sufficient for settlement.
- The carrier can reasonably inform and serve the customer
- The customer of the cargo plans loading, reception and other work according to arrival. Driver facts and documents allow for a more accurate explanation of the journey and deal with delays. Reliable execution and timely delivery evidence are important for reshipment orders.
Core features
- Ordering and the sequence of voyages
- Validation of the principal
- Driver workspace
- Arrival information
- Delays and document deficiencies
Key integrations
- Customer order channels
- Cargo and service requirements, change and order acceptance response.
- Fleet, working time and maintenance data sources
- Genuine asset fitness, unavailability and required driver planning restrictions.
- Carrier Channels
- Terms of a specific order, acceptance by the partner and facts of execution.
- Driver tasks and document workflow
- Valid instruction, its reception, delivery and document readiness.
- Parcel Visibility Function
- Relevant forecast and risk; a confirmed change to the plan is returned.
- Accounting and profitability analysis
- Agreed prices, the basis for execution costs and the connections required for settlement.
- Telematics and sources of partner events
- Movement or stop, its time and information about missing data are recorded.
- Source of work and recreation planning
- Restrictions are required and permitted for a specific voyage estimate.
- Traffic and route data
- Road and traffic estimates are significant for the journey when available.
- Dispatcher and Client Channels
- The forecast, its relevance, the decision of the responsible employee and the communication allowed.
- Electronic Waybills or Document Tool
- Document origin, version, endorsements and allowed access.
- Telematics and cargo monitoring sources
- Proof of time, location or specific cargo conditions is provided as needed.
- Commercial and billing process
- Document readiness response and a separate solution for additional service or non-compliance.
Potential impact (%)
The ranges indicate an illustrative relative change in the metric under the stated assumptions. Results depend on the starting position and actual use of the solution. Percentages for different metrics must not be added together.
Re-order data correction
12–36%Decreasing
This illustrative scenario assumes that 30-60% of manual data entry and handover work can be addressed. That share is assumed to fall by 40-60%. Company data is needed to verify both the addressable workload and the resulting change.
A repair work is measured, the reason for which was a rewrite or an untransmitted change.
Arrival forecast error
3–16%Decreasing
This illustrative scenario assumes that 15-40% of forecast error is attributable to the data and model used. That share is assumed to fall by 20-40%. Company data is needed to verify both the addressable share and the resulting change.
A comparison is made of the error in the arrival forecast in minutes when the forecast is made the same time before the arrival. Indicates which part of the journeys the data is available for.
Time to the right set of documents
6–25%Decreasing
This illustrative scenario assumes that 20-50% of waiting caused by missing information or unclear responsibility can be addressed. That share is assumed to fall by 30-50%. Company data is needed to verify both the addressable share and the resulting change.
The time from delivery to the approved set is measured, separating the document work from the dispute handling.
Parts of negative feedback on transportation
4–15%Decreasing
Indicative assumption: 15-30% of negative reviews relate to delayed trip forecast and delivery information. The solution could reduce this share by 25-50%. This is a scenario of potential; assumptions need to be verified by feedback collected by the company.
When a company starts collecting feedback, negative feedback about transportation is counted from all the assessments received on the subject. The same method of assessment is applied before and after installation and similar customer groups are compared. Without initial data, the actual change is not determined.
Conditional calculation scenarios. The assumptions have not been validated against client measurements.
When this solution is relevant
- The customer's modified stop condition is visible in the order, but the driver continues to follow the previous instruction.
- The return cargo is selected without checking whether the transport will be able to keep up with another already confirmed order.
- The arrival time provided to the customer does not change after an additional stop or a change of principal.
- Dispatchers ignore warnings because they do not indistinguish real delay from outdated data.
- The voyage has been delivered, but the bill preparation is awaiting an explanation of an unnamed document or a recipient's note.
- Additional waiting is recorded only after the voyage, when reliable proof is difficult to restore.
Implementation requirements
For voyage management, order, stop and driver task identifiers are matched. The transport management system used evaluates the return of changes, delivery clauses and documents and identifies missing connections between the dispatcher, driver and customer.