Overview - Debrief: Difference between revisions

From CTMS
(Added DEBRIEF)
(ER047-005 - 528318 - Added LogiNext information)
 
Line 30: Line 30:
* Microlise SmartPOD
* Microlise SmartPOD
* WEBFLEET
* WEBFLEET
* LogiNext 4PL


The interfaces support updating the following information:
The interfaces support updating the following information:
Line 40: Line 41:
** Trip Status COMPLETED
** Trip Status COMPLETED
* Aptean POD Calidus Edition
* Aptean POD Calidus Edition
** Trip automatically marked as EN-ROUTE
** Item quantity delivered
** Item quantity delivered
** Item non-conformance reason codes
** Item non-conformance reason codes
Line 63: Line 65:
** Trip ODO start/end
** Trip ODO start/end
** Start/End Latitude/Longitude
** Start/End Latitude/Longitude
** Trip Stop Departure/Arrival Times
** Trip Status COMPLETED
* LogiNext 4PL
** Trip automatically marked as EN-ROUTE
** Item quantity delivered
** Item non-conformance reason codes
** POD/POC flag set
** Order Status DELIVERED/FAILED
** Trip Stop Departure/Arrival Times
** Trip Stop Departure/Arrival Times
** Trip Status COMPLETED
** Trip Status COMPLETED

Latest revision as of 14:08, 8 July 2025

Manual Debrief

The Aptean TMS Calidus Edition Debrief process has the capability to capture the following debrief information:

  • Trip level
    • General comments
    • Fuel Drawn
    • ODO start/end
    • Comments – general/rejection/errors
  • Stop level
    • Arrive/Depart times
  • Order level
    • Actual quantities/weights
    • POC/POD complete
    • Additional Coll/Del debrief information, such as weighbridge/weight
    • Additional order references
    • Order level non-conformity/information/late codes
  • Order Items
    • Actual quantities/weights
  • Additional finance payments
  • Additional trip services (for generation of trip cost)
  • Additional Order Services (for capture of additional services per order, generating order revenue)
  • Trip Tasks/Trip Stop Tasks - additional extensible task information

Order and trip statuses can be set to identify the status of the order, and rebooking of incomplete or partially incomplete orders is supported.


Automatic Debrief

Aptean TMS Calidus edition supports automatic debrief from a number of electronic POD applications, including Aptean POD and Aptean POD Calidus Edition.

Also supported are:

  • Microlise SmartPOD
  • WEBFLEET
  • LogiNext 4PL

The interfaces support updating the following information:

  • Aptean POD
    • Item quantity delivered
    • Item non-conformance reason codes
    • POD/POC flag set
    • Order Status DELIVERED/FAILED
    • Trip Stop Departure/Arrival Times
    • Trip Status COMPLETED
  • Aptean POD Calidus Edition
    • Trip automatically marked as EN-ROUTE
    • Item quantity delivered
    • Item non-conformance reason codes
    • POD/POC flag set
    • Order Status DELIVERED/FAILED
    • Order HELD/RTB reason codes
    • Trip Stop Departure/Arrival Times
    • Trip Status COMPLETED
  • Microlise SmartPOD
    • Item quantity delivered
    • Item non-conformance reason codes
    • POD/POC flag set
    • Order Status DELIVERED/FAILED
    • Order HELD/RTB reason codes
    • Automatic Rebook
    • Trip Stop Departure/Arrival Times
    • Trip Stop Tasks
    • Trip Tasks
    • Trip Status COMPLETED
  • WEBFLEET
    • Order Events Audit
    • Trip Stop ETAs
    • Trip ODO start/end
    • Start/End Latitude/Longitude
    • Trip Stop Departure/Arrival Times
    • Trip Status COMPLETED
  • LogiNext 4PL
    • Trip automatically marked as EN-ROUTE
    • Item quantity delivered
    • Item non-conformance reason codes
    • POD/POC flag set
    • Order Status DELIVERED/FAILED
    • Trip Stop Departure/Arrival Times
    • Trip Status COMPLETED


3rd-Party Debrief

3rd-party carrier/haulier trips can be debriefed by invoice of the entire manifest.

Once the invoice is received and entered into the system, the invoice payments can then be shared between the different orders on the trip/manifest, or the pre-defined payments modified at that time to match the invoice received.

Aptean TMS Calidus edition also supports a carrier POD message to achieve this.

3rd-party carriers/hauliers can interface into Aptean TMS Calidus Edition through an existing message. This supports:

  • update through tracking reference (order number),
  • setting the line quantity to that captured
  • updating POD/POC against the order.
  • updating non-conformity reason codes against the lines.
  • updating arrival and departure dates/times.
  • updating signatory.
  • automatically updating order and trip status.


Aptean TMS Calidus edition also supports a Import format for basic debrief information. It can be configured as to how field are extracted from a CSV and then uploaded into the system. This supports:

  • adding or updating signature information (signatory, date and time).
  • setting the quantity delivered against the items.
  • setting the order to POD confirmed.
  • Validating the order as delivered.
  • auditing with a reason of CD (complete delivery).
  • setting the delivery trip stop with the arrival time.