The CAPcargo TransportOrder reflects the order you receive from your customer about the shipment. Collection and delivery place information, timelines, agreed services or references. On the line level we store all relevant information about the material to be transported. The flexible unit structure let you define, what to track. Not important whether we ship pallets, boxes, bulk commodities or animals.
The transport order is priced based on our contract framework and invoiced to the customer.
The rapid order entry process for manually created orders or EDI import for electronic orders are just two options how to bring the orders into the system.
Hub and spoke model? Multi-hub-approach? Multimodal? Logistic is a mass business and the TransportManagementSystem has to comply with complex routing rules. No time for manual splitting logic. The CAPcargo routing engine takes over this job and creates transport legs taking condition-based configurations into account. Forward or backward scheduling logic makes sure that single or multi-order-consignments are arriving at the same time, departing as late as possible or arriving as early as possible.
The CAPcargo tour can reflect multiple scenarios. The work of a truck during a day? Yes. A cross-continent-journey? Yes. The journey of an oversea-container? Yes. Everything handled by a partner during a day? Yes.
Transport legs are dispatched into a tour and we define start and end point. We assign one or several resources (driver, truck, trailer, …) or subcontract to a vendor. The scheduling engine calculates ETA of every stop, taking activities into account.
From 0 trucks to thousands of resources. The CAPcargo tour bundles it together.
Increasing the fleet utilization and loading more into the existing fleet is probably the easiest way to improve margins. But how to achieve this? The challenge is how to find these potentials in the day to day planning, especially under time pressure multiple dispatchers set-ups. The CAPcargo GraphicalPlanningBoard is the key to this. A user friendly interface makes it possible that dispatchers can really do their planning job directly in the system. This is mandatory in order to have latest planning information in the system. The interactive multi-window and multi-monitor set-up are giving the opportunity to have a full overview over the fleet either on Gantt (time line) or map view. The system is intuitively showing ideal vehicles for a tour or whether there are issues with an ongoing trip. An experienced Scandinavian dispatcher said once: “Finally, after all these years, a system working for us and not we have to work for the system!”
One size fits all? Probably not.
Your fleet is unique. We capture, dimensions, capacities, equipment, costs, emission class, special purpose… just all technical details. And in order not to forget it, maintenance intervals can be scheduled.
In the mid-term-driver planning we can link driver and resources. Just until the next change comes up.
Do you have multi dimension pricing agreements with your customers? Probably nobody likes them, but they are fact and there are good reasons for them. We reflect the challenge in our contract framework. Three-dimension matrix, surcharges condition based and of course multi-currency handling. And since this is often not enough, collection orders help to group orders and calculate (and invoice) them together.
When it comes to invoicing, we follow the clear idea to have this covered in an automated process.
Not every truck can serve every address; not every driver can drive every truck; not every commodity can be loaded into every truck; not every commodity can be loaded next to certain commodities; not every driver can handle every commodity; … many conditions and difficult to keep an eye on all of them and impossible for to optimizer engine to respect them without having them nicely structured. The Qualification framework takes care of them. And since certain conditions have an expiration date, we have included also the certificates into to. Since not every shipment is just standard.