Overview - TMS vs Planning vs Both

Aptean recommends Aptean Routing and Execution plus Aptean TMS for full system functionality across the whole process set of an organisation.

Overview of Functionality

Aptean Routing & Scheduling and POD:

Aptean TMS Calidus Edition:

Single point of data, regardless of source or how it is executed.
Single process for order and trip lifecycles, regardless of source or how it is executed. In other words, when is planning, execution, middle mile, final mile, etc), automatically generating tasks for and importing tasks from other systems (such as Aptean Routing and Scheduling, Aptean POD, other third-party systems as required).
Order well - much more detailed. Extensible, down to items and contents.
Order generation – fixed schedules, milk runs, etc.
Locations - reusable locations for variety of purposes (e.g. Depot, customer locations), with configuration that affects how jobs are planned or executed at a location level. Not just an address against an order.
Order Integration - order well from many different inputs, in different formats
Fixed routes - Middle-mile planning to outbase/RDC/Delivering depot
Middle mile execution - scanning into and out of depots, palletisation, etc
Manual or Overflow planning - 3rd party carrier
Resource management - 1st/3rd party (known resources), 3rd party manual entry of resources.
3rd-party carrier process - tendering, acceptance, carrier invoicing, comparison, carrier restrictions.
Finance - order revenue, trip costs, invoicing
Operational documents (e.g. item labels, paper-based loading sheets, driver notes, manifests, etc)
Pushed export back to system source, can be multiple, segregated based on source system.
Single point of BI export regardless of source or how it was executed.