UG CALIDUS Transport Systems Cross-Functional Flows

From Calidus HUB
Revision as of 17:26, 11 September 2025 by Anw (talk | contribs) (Initial Creation)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)





Aptean Logo.png







Aptean

CALIDUS Transport Systems Cross-Functional Flows

CALIDUS Transport Systems

11th September 2025 - 1.0
Reference: UG PROD-UG











































Process Flows

The intention of this guide is to show the types of movements that may be entered into within any transport operation, and how the different CALIDUS systems may be used to interact and execute those transport movements.

Any implementation may use any CALIDUS system (although it is assumed that CTMS is required at a basic level). These guides assume processes using the following systems:

  • Depot Scanning - CALIDUS MCS or CALIDUS WCS
  • Driver Execution - APOD or CALIDUS ePOD
  • Transport Management - CALIDUS TMS

The described transport solution below makes use of the following resources:

  • Own Fleet - road transport for all aspects of transport (initial collection, middle mile, final destination).
  • Agent - road transport, trusted 3rd party carriers using CALIDUS systems (e.g. APOD/EPOD). Used as Own Fleet.
  • 3PC - road transport to final destination, external 3rd party carriers.
  • Air/Airlines - Air transport, middle mile.
  • Line Haulage - road transport middle mile through 3PC.

The intention is that the individual cross-functional flows may be combined in order to provide a cohesive description of full transport movement execution for any movements within any network.

Component Trips

When an order is received, it will be planned from its source to its destination through a series of trips:


Direct Deliveries (completed by all carriers and depots):

  • Source-Destination
    • Direct delivery, completed in one trip.


Not Pick/Pack via Own Fleet depot (RDC) or agent depot (AD):

  • Source-Depot-Destination
    • Collect into network, deliver direct from same depot.
  • Source-Depot-RDC-Destination
    • Collect into network, use the network to move between regional depots (road haulage), deliver to destination from regional depot.
  • Source-Depot-Airport1-Airport2-RDC-Destination
    • Collect into network, move to airport, use a line haulier to move between airports, collect from airport into regional depot, deliver to customer.
  • Source-Depot-Airport1-Airport2-AD-Destination
    • Collect into network, move to airport, use a line haulier to move between airports, collect from airport into agent depot, deliver to customer.
  • Source-Depot-Airport1-Airport2-Destination
    • Collect into network, move to airport, use a line haulier to move between airports, collect from airport and deliver to customer in one trip.
  • Source-Depot-3rd-party Carrier Depot-Destination
    • Collect into network, label and pass onto 3rd-party carrier.
  • Source-Depot-Airport1-Airport2-Depot-3rd-party Carrier Depot-Destination
    • Collect into network, move to airport, use a line haulier to move between airports, collect from airport into regional depot, label and pass onto 3rd-party carrier.
  • Source-Depot-Airport1-Airport2-3rd-party Carrier-Destination
    • Collect into network, label and move to airport, use a line haulier to move between airports, 3rd-party carrier collects from airport and delivers.


Pick/Pack at Own Fleet depot (also any ad-hoc orders that turn up at a Depot):

  • RDC-Destination
    • Picked/Packed at depot, delivered to customer.
  • RDC-RDC-Destination
    • Picked/Packed at depot, use the network to move between regional depots (road haulage), deliver to destination from regional depot.
  • RDC-Airport1-Airport2-RDC-Destination
    • Picked/Packed at depot, move to airport, use a line haulier to move between airports, collect from airport into regional depot, deliver to customer.
  • RDC-Airport1-Airport2-AD-Destination
    • Picked/Packed at depot, move to airport, use a line haulier to move between airports, collect from airport into agent depot, deliver to customer.
  • RDC-Airport1-Airport2-Destination
    • Picked/Packed at depot, move to airport, use a line haulier to move between airports, collect from airport and deliver to customer in one trip.
  • RDC-3rd-party Carrier Depot-Destination
    • Picked/Packed at depot, label and pass onto 3rd-party carrier.
  • RDC-Airport1-Airport2-Depot-3rd-party Carrier Depot-Destination
    • Picked/Packed at depot, move to airport, use a line haulier to move between airports, collect from airport into regional depot, label and pass onto 3rd-party carrier.
  • RDC-Airport1-Airport2-3rd-party Carrier-Destination
    • Picked/Packed at depot, label and move to airport, use a line haulier to move between airports, 3rd-party carrier collects from airport and delivers.


The following is a list of the individual trips required to action the order routing above, showing the potential executing agent:

  1. Source-Destination
    1. Can be completed by Own Fleet Driver, Agent or 3rd-party Haulier
  2. Source-Depot
    1. Can be completed by Supplier, Own Fleet Driver, Agent or 3rd-party Haulier
  3. Depot-Destination
    1. Can be completed by Own Fleet Driver, Agent or 3rd-party Carrier
  4. Depot-RDC
    1. Can be completed by Own Fleet Driver or Agent.
  5. RDC-Destination
    1. Always completed by Own Fleet Driver – this is the same as Depot-Destination.
  6. Depot-Airport1
    1. Can be completed by Own Fleet Driver or Agent.
  7. Airport1-Airport2
    1. Always completed by Line Hauler (Airline)
  8. Airport2-RDC
    1. Always completed by Own Fleet Driver.
  9. Airport2-AD
    1. Only if the agent uses a Depot. Completed by Agent.
  10. AD-Destination
    1. Only if the agent uses a Depot. Completed by Agent.
  11. Airport2-Destination
    1. Only if the agent has no depot. Completed by Agent.
  12. Depot-3rd-party Carrier
    1. Can be completed by 3rd-party Carrier, Own Fleet Driver or Agent. If executed by an Own Fleet Driver or Agent, the process is identical to Depot-Destination.
  13. RDC-RDC
    1. As Depot-RDC, always completed by Own Fleet Driver. See that process flow for details.
  14. RDC-Airport1
    1. As Depot-Airport1, always completed by Own Fleet Driver. See that process flow for details.
  15. Airport2-3rd-party Carrier
    1. Always completed by 3rd-party Carrier.
  16. 3rd-party Carrier-Destination
    1. Always completed by 3rd-party Carrier.


Each Component Trip is shown in detail below, with proposed processes, responsibilities and notes.

Cross-Functional Flows

Source-Destination

XFUNC-S-D-Own-Fleet.png

XFUNC-S-D-3PC.png

Source-Depot

XFUNC-S-Depot-Own-Fleet.png

XFUNC-S-Depot-3PC.png

Depot-Destination

XFUNC-DEPOT-D-Own-Fleet.png

XFUNC-DEPOT-D-3PC.png

Notes:

  • This process includes a transit job to come to the depot to collect the order, if required.
  • The process Agent Depot-Destination is identical to this process.
  • The process Depot-3rd-party Carrier depot is identical to this process, if executed by an Own Fleet Driver or Agent.

Depot-RDC

XFUNC-DEPOT-RDC-Own-Fleet.png

Depot-Airport1

XFUNC-DEPOT-AIR-OWN-FLEET.png

XFUNC-DEPOT-AIR-AGENT.png

Airport1-Airport2

XFUNC-AIR-AIR.png

Notes:

  • No process is necessary for these tasks, as debrief and en-route is essentially meaningless without accurate data returned by the line haulier. However, this process could be followed if desired.
  • Although present in this flow, the AWB will have been presented to the airline in advance to this trip being initiated, during the Depot-Airport process. It is during that process that this trip may be marked as En Route, if required.

Airport2-RDC

XFUNC-AIR-RDC.png

Airport2-AD

XFUNC-AIR-AD.png

Notes:

  • This process assumes that the Agent is using a depot for inbound movements, and that the agent driver wishes to use EPOD for scanning off the vehicle at an item level. If the agent depot wishes to use WCS scanning, see process Air-RDC.
  • If the agent depot requires loading or scanning off pallets rather than packages, this requires further development to EPOD.
  • Scanning through EPOD does not allow identifying additional packages, just ones that were planned. If this is required, WCS scanning is required - see process Air-RDC.

AD-Destination

XFUNC-S-D-AD-D.png

Notes:

  • The process that should be used for these moves is as outlined in the Depot-Destination process.
  • It should be noted that the agent depots may want to follow a more rigidly-planned process, in which case EPOD may be used to load the items at the depot rather than WCS. The system may be configured in this way and this is the process outlined here.
  • If EPOD is used to load, no additional items may be processed, only the planned items.

Airport2-Destination

XFUNC-AIR-D.png

Notes:

  • This process assumes the agent is not using a depot for inbound movements, just routing them straight to final destination.
  • In this case, EPOD is used to load the items without scanning, and then used to deliver directly to final destination - this is the process that is documented here.
  • If the agent requires loading at the airport using scanning of packages, the EPOD system can be configured for this.
  • If the agent requires loading at the airport using scanning of pallets rather than packages, this requires further development to EPOD.
  • In this process, there is no way to identify additional items.

Depot-3rd-party Carrier

XFUNC-DEP-3PC-OWN FLEET.png

Notes:

  • This is a process covering trips being on-forwarded through a 3rd-party carrier depot, where the items are delivered to the 3rd-party depot by an Own Fleet or Agent driver.


XFUNC-DEP-3PC-3PC.png

Notes:

  • It is considered unlikely that the 3rd-party carrier will confirm to Own Fleet when the move to the depot is complete, so the Admin users may update the trip as complete once departed (as shown here) or update this trip to complete once POD confirmation of the final delivery is received - see the 3rd-party Carrier-Destination process.

Airport2-3rd-party Carrier

XFUNC-AIR-3PC.png

Notes:

  • Packages must have been labelled with 3rd-party labels priori to departure from original depot, during the Depot-Air processes.
  • 3rd-party must also be informed before departing depot.
  • This process has been documented for the Own Fleet contract as being always completed by the 3rd-party carrier themselves. However, this could also be completed by Own Fleet or Agent drivers - a process will be written for this if required.
  • It is considered unlikely that the 3rd-party courier will confirm this trip specifically, just the destination delivery - see process 3rd-party Carrier-Destination for details.

3rd-party Carrier-Destination

XFUNC-3PC-D.png

Retrieved from ‘https://calidusassist.adcservices.apteancloud.com/calidus-assist/OBS/index.php?title=UG_CALIDUS_Transport_Systems_Cross-Functional_Flows&oldid=14710’