FS 371933 6287 EBB CTL Operational Documents

From Calidus HUB
Revision as of 11:45, 5 May 2020 by Anw (talk | contribs) (v1.0 - Issue of formal specification)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)






Aptean Logo.png







EBB Paper

Operational Documents

Functional Specification

17th April 2020 - 1.0
Reference: FS 371933 6287















FUNCTIONAL OVERVIEW

Client Requirement

SCR 3 in the SDD. See here:

http://172.198.45.54/calidus-assist/OBS/index.php/SDD_366558_EBB_Paper_CTL_Solution_Design#Execution

The customer requires their existing reports to be produced out of CTL, consisting of:

  • Driver Manifest.
  • Delivery Notes.

This specification includes the definition of TFS work item 6288 - Driver manifest to include run sequence (SDD v1.0 SCR 4).


SCR 4 in the SDD. See here:

http://172.198.45.54/calidus-assist/OBS/index.php/SDD_366558_EBB_Paper_CTL_Solution_Design#Loading

When the driver manifest report is run, stamp a run sequence against the trip/stop/order (used to be called SCH_HAULAGE_ACTIVITY). This can be related/generated from the date/time. Only stamp records when it has not already been stamped before.

This will be displayed on the Driver Manifest operational report.


Solution Overview

The two operational reports will be created in CTL-TMS.

  • EBB Delivery Note.
  • EBB Driver Manifest.
  • EBB Driver Manifest + Delivery Notes.


Further to the basic requirements of the formatting, data and layout of the existing report, the driver manifest will be modified to include a Run Sequence and date/time. Every time the reports are run, any orders that have already been included on the print will have been stamped with the run sequence, date and time - this will be displayed against the orders. Any new orders will not have a run sequence, date and time against them, so that the users can clearly see that these are newly-planned orders.


These reports will be set to be the default reports run by the system whenever the Driver Manifest or Delivery Note reports are run from the planning screen.


The Planning screen will be modified to allow the reports to be run from the More menu against a trip. When selected, these reports will be run to the screen as a PDF, ready for printing.


The reports will also be available to run from the standard reports screen when created.


Scope

This change will be applied to system version 1.00 on test database EBBCTST) and once approved EPPCPRD.


Impact

This development is dependent on the following TFS work items being completed first:

  • 6222 - Operational Reports (base).
  • 6178 - Schedule Proposal.
  • 6281 - Bespoke Import Interface.


CONFIGURATION SET-UP

Pre-requisites

Menu Structure

Data

Own Fleet Depot (RDC) Locations must be configured with an Alternate Name.


System parameters should be created and configured to set the variant of the following reports:

  • Delivery Note - drop-down list of report names, defaulting to the standard Delivery Note format. Ensure that EBB Delivery Note is added to this list.
  • Driver Manifest - drop-down list of report names, defaulting to the standard Driver Manifest format. Ensure that EBB Driver Manifest is added to this list.
  • Loading sheet - drop-down list of report names, defaulting to the standard Delivery Note format.

This will identify which report to run from the Planning screen when the report option is selected.


Implementation Advice

FUNCTIONAL DESCRIPTION

The two operational reports will be created in CTL-TMS.

  • EBB Delivery Note.
  • EBB Driver Manifest.
  • EBB Driver Manifest + Delivery Notes.


The customer has chosen to match the existing formats. These use pro-forma paper stock, as follows:

FS 371933 ProForma.png


The driver manifest format is as follows:

FS 371933 Driver Manifest.png


The delivery note format is as follows:

FS 371933 Delivery Note.png


Further to the basic requirements of the formatting, data and layout of the existing report, the driver manifest will be modified to include a Run Sequence and date/time. Every time the reports are run, any orders that have already been included on the print will have been stamped with the run sequence, date and time - this will be displayed against the orders. Any new orders will not have a run sequence, date and time against them, so that the users can clearly see that these are newly-planned orders.

These reports will be set to be the default reports run by the system whenever the Driver Manifest or Delivery Note reports are run from the planning screen.


The Planning screen will be modified to allow the reports to be run from the More menu against a trip. When selected, these reports will be run to the screen as a PDF, ready for printing.


The reports will also be available to run from the standard reports screen when created.

The reports will request the following parameters:

  • Owning Depot - defaulting value to the user's owning depot parameter. This will be a drop-down list of all own-fleet depot locations (RDCs) within the system. This is required entry.
  • Schedule - This will allow text entry of a schedule or allow a lookup of any schedules that are created in the system. The schedule will default to the closest automatically created schedule to today's date. This schedule lookup will be the same as the standard schedule lookup being developed as part of TSF work item 6178 - Schedule Proposal. This is optional entry.
  • Date/Time range - this will default to the dates and times calculated from the schedule selected above. This will allow date and time lookups. This is required entry and the total range should never exceed 7 days.
  • Carrier Group - This will allow text entry of a carrier group, or allow a lookup of carrier groups. This is optional entry.
  • Carrier - This will allow text entry of a carrier ID, or allow a lookup of carriers. Only carriers within the group selected (if any) may be entered. The lookup will provide a list of carriers limited to this group, if provided. This is an optional parameter.
  • Trip - This will allow text entry of a trip ID, or allow a lookup of trips. This is optional entry. Only trips in the date/time range above will be shown on the lookup.


TECHNICAL NOTES

Database Changes

Table TRP_TRIP_HEADER:

A new field TTH_MANIFEST_PRINT_SEQ should be added. This should be an integer and defaulted to 0.


Table TRP_STOP_ACTIVITY

A new field TSA_MANIFEST_PRINT_CODE should be added. This should be a string, defaulting to blank.


General Reports

Re: TFS stream 6337 - Reporting.

There are a number of standard operational reports that will available in the system, such as:

  • Traffic Sheet
  • Outstanding Debrief Report
  • Exceptions Failures and Reasons Report
  • Summary by Depot Report
  • Operational Reports (base)

The last one (TFS item 6222) specifies the following:

Specifically a process by which they can be:

  • run with parameters
  • exported to PDF
  • emailed
  • downloaded
  • created with configurable formats

Specific reports required:

  • Delivery Note
  • Driver Manifest
  • Driver Manifest plus Delivery notes
  • Loading sheet

Therefore there must be a mechanism whereby these reports can be selected and run, entering parameters.

This new report will be added to the same report selection screen, labelled as "EBB Driver Manifest + Delivery notes".

The Driver Manifest and Delivery Note reports should be developed as two separate reports.

Each report should be added as an option to the Reports menu:

  • EBB Delivery Note
  • EBB Driver Manifest
  • EBB Driver Manifest + Delivery Notes


All reports will prompt for the following parameters:

  • Owning Depot - defaulting value to the user's owning depot parameter. This should be a drop-down list of all own-fleet depot locations (RDCs) within the system. This is required entry.
  • Schedule - This should allow text entry of a schedule or allow a lookup of any schedules that are created in the system. The schedule should default to the closest automatically created schedule to today's date. This schedule lookup should be the same as the standard schedule lookup being developed as part of TSF work item 6178 - Schedule Proposal. This is optional.
  • Date/Time range - this should default to the dates and times calculated from the schedule selected above. This should allow date and time lookups. This is required and the total range should never exceed 7 days.
  • Carrier Group - This should allow text entry of a carrier group, or allow a lookup of carrier groups. This is optional.
  • Carrier - This should allow text entry of a carrier ID, or allow a lookup of carriers. Validation of this field is necessary - only carriers within the group selected (if any) may be entered. The lookup should provide a list of carriers limited to this group, if provided. This is an optional parameter.
  • Trip - This should allow text entry of a trip ID, or allow a lookup of trips. This is as optional parameter. Only trips in the date/time range above should be shown on the lookup.

When run, the report should be produced as PDF and downloaded.

Note Note: For the "EBB Driver Manifest + Delivery Note" option, the two reports should be concatenated into a single PDF output.


This PDF should then be actioned as per the standard processing (i.e. PDF download, email, print, etc).


Planning Screen

A Reports should be added to the central More button against a trip selected in the Planning screen.

When selected, a list of the trip based reports should be shown. Initially, this should consist of:

  • Driver Manifest.
  • Delivery Note.
  • Driver Manifest + Delivery Note.
  • Loading/Unloading Sheet.

When the report is selected, the system should check the system parameters to see which report format to run.

The reports will be passed the parameters required, all sourced from the trip selected - importantly:

  • Owning Depot.
  • Trip ID.


No other information should be required to run the report selected and the report should be generated out as PDF to the browser in a separate tab.

Note Note: When the process is run to print the report *but before it has been generated*, the print sequence against the trip and all trip stop activity must be set.

  • The trip run sequence (TRP_TRIP_HEADER.TSA_MANIFEST_PRINT_SEQ) should be incremented by 1. For example, on the first print of this trip, the trip sequence should be incremented from 0 to 1, on the second print, from 1 to 2, etc.
  • Any orders on this trip stop without a defined run sequence should be stamped with the trip run sequence and the print time e.g. "3-1648". Any that already have a value in this field should *not* be updated. This is on table TRP_STOP_ACTIVITY, field TSA_MANIFEST_PRINT_CODE.


Driver Manifest Report

Per trip in the selection criteria. Page numbering should reset per trip.

Criteria provided will be from the following:

  • Owning Depot - required. Select only trips for this owning depot.
  • Date/Time range - required. Select only trips that pass through this date/time range, based on planned date/time of the stops.
  • Carrier Group - optional. If provided, select only trips assigned to carriers in this carrier group.
  • Carrier - optional. If provided, select only trips assigned to this carrier. The previous selection may then be ignored.
  • Trip ID - optional. If provided, select the trip by the trip ID - no other criteria is necessary.


Header

Note Note: Includes printing the labels in the correct positions as well.

  • "MANIFEST" - fixed text
  • Printed At - Time of printing
  • Printed By - CTMS user
  • "**Reprint**" - only if the trip has been printed before. Can be derived from TTH_MANIFEST_PRINT_SEQ being blank.
  • Run Sequence - new field below "Printed By" - displaying the trip run sequence TTH_MANIFEST_PRINT_SEQ
  • Additional Instructions - Trip instructions TTH_COMMENT.
  • Vehicle - Assigned vehicle of Trip - TRP_TRIP_HEADER.TTH_VEHICLE_CODE.
  • Driver - Assigned Driver of trip - RES_PERSON.RSP_CODE + " - " + RES_PERSON.RSP_FORENAME concatenated with RSP_SURNAME, delimited with " ".
  • Trailer - Assigned Trailer of the trip stop TRP_LOAD_STOP.TLS_TRAILER_CODE. Note: this is subject to change of trailer swap planing, under change 371746 6616 - Plan Trailer Swaps (SDD v1.0 SCR 2).
  • Collated By/Time - label only - for driver to fill in
  • Checked By Driver - label only - for driver to fill in
  • Checked By W/H - label only - for driver to fill in
  • Loaded By - label only - for driver to fill in
  • No. Pallets/Jobs - label only - for driver to fill in
  • Date - Planned manifest date - TRP_TRIP_HEADER.TTH_COLLECT_DATETIME_FROM
  • Branch - Starting Depot - the SU location of the trip on the first trip stop, TRP_STOP.TRS_LOCATION_CODE
  • Delivery Date - Start Date - TRP_STOP.TRS_PLANNED_ARRIVE_DATETIME
  • Start Time - Start time of trip - TRP_STOP.TRS_PLANNED_ARRIVE_DATETIME of the first stop.
  • Load Number - Trip ID TRP_TRIP_HEADER.TTH_TRIP_REF


Details

One line per Stop/Order (TRP_STOP_ACTIVITY record)

  • First line: Cust Reference of order + from location alternate name + from location name plus COMMENT_ID
    • ORD_ORDER_HEADER.OOH_CUSTOMER_REF
    • GEO_LOCATION.GLO_ALTERNATE_NAME
    • GEO_LOCATION.GLO_NAME
    • order parameter "ORD_COMMID"
  • Second line: Order parameter "Route"
  • Third line: Quantity + TU + description + fixed text "Signed:___"
    • ORD_ORDER_LINE.OOL_QUANTITY
    • ORD_ORDER_LINE.OOL_DESCRIPTION
  • Fourth line: Run Sequence + description 2 (BinBay + NS Flag) + fixed text "Print:___"
    • TRP_STOP_ACTIVITY.TSA_MANIFEST_PRINT_CODE
    • ORD_ORDER_LINE.OOL_DESCRIPTION2

Note:

  • Run Sequence This displays the trip run sequence code from the trip stop activity record for that order, for example "2-1648" from TSA_MANIFEST_PRINT_CODE.


Footer

Note: Including labels.

  • T&Cs - fixed text.
  • Total Wgt: calculated from ORD_ORDER_HEADER.OOH_WEIGHT.
  • Page X of Y - calculated by the report.


Delivery Note

Per delivered order on the selected trips. All orders on the trip should be produced in a single document, with page numbering as expected. Page numbering should reset per trip.

Criteria provided will be from the following:

  • Owning Depot - required. Select only trips for this owning depot.
  • Date/Time range - required. Select only trips that pass through this date/time range, based on planned date/time of the stops.
  • Carrier Group - optional. If provided, select only trips assigned to carriers in this carrier group.
  • Carrier - optional. If provided, select only trips assigned to this carrier. The previous selection may then be ignored.
  • Trip ID - optional. If provided, select the trip by the trip ID - no other criteria is necessary.


Header

Note: Includes printing the labels in the correct positions as well.

  • "Delivery Note"
  • Invoice To - Customer address, from the customer of the order, from GEO_LOCATION.
  • Delivery To - Location to address, from GEO_LOCATION.
  • Delivery Instructions - order special instructions ORD_ORDER_HEADER.OOH_SPECIAL_INSTRUCTIONS
  • DATE - Order creation date ORD_ORDER_HEADER.OOH_ORDER_PLACED_DATE.
  • BRANCH - From location of the order, ORD_ORDER_HEADER.OOH_COLLECT_LOCATION_CODE
  • DEL DATE - Planned delivery date. TRP_STOP.TRS_PLANNED_ARRIVE_DATETIME of the stop for that order.
  • DELIVERY TIME - ORD_ORDER_HEADER.OOH_COLLECT_DATETIME_FROM
  • S TIME - TRP_STOP.TRS_PLANNED_ARRIVE_DATETIME of the stop for that order.
  • E TIME - TRP_STOP.TRS_PLANNED_DEPART_DATETIME of the stop for that order.
  • DEL NOTE NO - ORD_ORDER_HEADER.OOH_CUSTOMER_REF


Details

Sourced from order lines

Note: Including labels.

  • ORDER NO - new field against order line OOL_CUST_ORD_REF.
  • QTY - ORD_ORDER_LINE.OOL_QUANTITY
  • UNITS - RES_TRANSPORT_UNIT.RTU_DESCRIPTION linked from ORD_ORDER_LINE.OOL_TRANSPORT_UNIT_CODE
  • QUALITY & DESCRIPTION - Order line description plus description 2 on the line following.
    • ORD_ORDER_LINE.OOL_DESCRIPTION
    • PRD_PRODUCT_TYPE.PPT_DESCRIPTION2
  • PACKS - quantity divided by new field "quantity pack" ORD_ORDER_LINE.OOL_PACK_QUANTITY
  • KGS - ORD_ORDER_LINE.OOL_WEIGHT.


Footer

Note: Including labels.

  • "04" - Order parameter "Route"
  • T&Cs - fixed text.
  • Total Wgt - ORD_ORDER_HEADER.OOH_WEIGH
  • Page X of Y - calculated by the report.
  • Barcode - CODE_39 barcode, containing the Cust Ref ORD_ORDER_HEADER.OOH_CUSTOMER_REF.


APPENDIX A: DOCUMENT HISTORY

References

Ref NoDocument Title & IDVersionDate
1   


Glossary

Term Definition
Transport Terms
Audit Log A log of events that have happened in the C-TL system. It could include information, error, debug or audit messages. Users are able to search for messages of a certain type, on a certain day and from a certain area of the system.
Activity The activity at a stop. Usually loading or unloading.
Asset A traceable DU; the item that is tracked during delivery and collection. This Asset has a type (e.g. Cage, Tet, etc).
Backloads Orders that are placed on a pre-existing trip at the end of the trip before returning to the depot. They may be for customers other than the customer that is paying for the full trip and may result in a rebate to the customer, and a charge to the backload order’s customer.
Booking A quantity of a single Product Type on a single DU Type to be delivered from one location to another on particular date but not at a particular time. These records are usually created by the Auto Summary process. These records are displayed in the main view on the Bookings form.
BUE Base Unit Equivalent. Also RPE (Regular Pallet Equivalent). A means of comparing transport unit type size. For example, a Standard Pallet may equate to 1 BUE, a Large Board may equate to 2 BUEs, a carton may equate to 0.02 BUE. This is used to estimate volume and therefore capacity of vehicles within CTL-TMS. Typically this is based on a standard 1 cubic metre pallet.
C-ePOD CALIDUS EPOD, OBS Logistics' app-enabled trip execution system.
C-Portal CALIDUS Portal, OBS Logistics' web-enabled external access system. Also, any electronic internet-based system designed to access functionality for a particular purpose (for example, customer enquiries, supplier activity, track and trace, etc.).
Carrier The carrier completing the trip. Can comprise any carrier configured in the system, but normally Home Fleet (usually a carrier per depot), 3rd-party carriers, supplier-/customer-own transport, own collection, etc.
Case A Case of individual packets of a product e.g. a case of Cornflake packets.
Consolidating Centre A depot that takes delivery of goods from several origins and consolidates them for trunking to out-bases (q.v.) or final delivery to destinations. See also Consolidation.
Consolidation In execution terms, this is the act of taking several jobs and combining them into a single execution job. This can be by several criteria but is broadly defined as: Same Location consolidation, where the delivery/collection points are identical; Linked Location, where the deliver/collection points have been configured to be seen as the same point within CTL-TMS and; Manual (Ad Hoc) Consolidation, where the driver decides that two jobs should be delivered/collected at the same time.
Containerisation The action of taking items and placing them inside another item for tracking purposes. See also Asset.
Cost The cost to the operation of running the trip. The cost is generated from the carrier's rate card. Cost is generated from the trip.
Cross-Dock Also a specific location at which product is exchanged.
CTL-TMS CALIDUS Total Logistics TMS, OBS Logistics' Transport Management System.
CTM This refers to the Carrier Trip Management module within C-TL.
Customer In 3PL terms, the customer on behalf of which the transport is being operated.
Debrief Comprises multiple parts: Stop debrief, where actual arrival and departure times against a trip are entered; Order debrief, where actual product and item quantities are entered; Driver/Trip debrief, where additional information is captured from the driver relating to the trip.
Demurrage; Detention Any time spent loading, unloading or waiting that is outside contractual obligation in execution of a trip. This usually incurs additional charges.
Depot Any location that schedules and controls transport.
Despatch In transport terms, the process of loading and despatching items out of a depot. The process of loading and despatching may be controlled by C-MCS (q.v.). See also Loading.
DMS Document Management Systems: Systems than manage the storage and viewing of (predominantly) scanned documents. Usually these systems also include some automation and indexing routines.
DOT Delivery On Time - see OTIF.
Driver Comprising drivers and crew assigned to a trip.
DU Despatch Unit type e.g. Standard Roll Pallet.
Drivers Day A schedule of work that a driver would undertake in a day including any rest periods and breaks.
EDI Electronic Data Interchange - a mechanism by which 2 systems can communicate normally without user intervention.
ERP Enterprise Resource Planning.
Fixed Route Template A template in CTL-TMS that provides a series of timed slots into which orders will fit. This can be used to create fixed routes (q.v.) and also as a template for cross-docking and grouping similar orders together.
Fixed Route In transport terms, a fixed route is a trip comprised of a series of fixed stops that are typically always visited. A CTL-TMS fixed route template (q.v.) can be used to create these.
Fuel Surcharge An additional charge that may be applied to a Transport charge to reflect the increasing price of fuel.
Item A single (usually unique) item for delivery/collection. A general terms, distinct from the TU of the deliverable item e.g. Pallet, Package, etc.
Load CTL-TMS: A trip that encompasses just a vehicle-full of items, or one journey out and back to a depot.
Loading In transport terms, the process of loading and despatching items out of a depot. The process of loading and despatching may be controlled by C-MCS (q.v.). See also Despatch.
Location In CTL-TMS terms, a trip comprises visits or drops to many locations. A location can be of many different types.
Location Types Usually one of: Depot, Customer, Delivery/Collection Location, Store, etc.
Location Zone Also Zone; A grouping of included or excluded postal regions, zones or post codes. These are used in fixed route templates to determine whether orders from or to locations should be included in any trips created from them.
MCS Mobile Control System
MSMQ Microsoft Message Queue – a method of interfacing with another system using Microsoft based technology.
OBD On-Board Diagnostics - an automotive term referring to a vehicle's self-diagnostic and reporting capabilities. Also CANbus.
ODBC Open Database Connectivity – A method of communicating with an external database from a program outside of the database environment.
Optimisation Route Building and Optimisation.
Order An instruction to deliver specific quantities of one or more Product Types on particular DU types from one location to another at a particular time; a transport movement.
Order Item An individual, usually unique item for collection or deliver.
Order Line An order can be made up of different order lines (i.e. an order from one location to another can contain many lines such as 20 ambient pallets and 20 chilled pallets).
Order Status The lifecycle of an order. Typically: Unscheduled; Scheduled (or Sheduled for Collection for cross-docked orders); Completed; Cancelled.
Order Type This defines the category of the order, and is intrinsically linked to revenue and cost tariffs.
Organization A part of an organization to which costs may be charged for accounting purposes. For CTL-TMS, this is used for accounting purposes, and also to generally configure the system.
OTIF On Time In Full - Success metrics to measure successful completion of an order.
Out-base A regional depot for collection and delivery in this local area. See also: RDC; ROC.
Payment Monies paid by a cost centre to a third party such as a carrier.
Plan A term used to describe the result from scheduling Orders onto Trips. The first set of Trips may be referred to as 'Plan A', with a subsequent, more accurate plan later in the day being referred to as 'Plan B'.
Post Schedule The period after Orders have been scheduled in the Scheduling Program and then returned to C-TL. Any subsequent manipulation of these Orders would be Post Schedule manipulation.
Pre Schedule The period before Orders have been scheduled in the Scheduling Program and then returned to C-TL. Any manipulation of these Orders would be Pre Schedule manipulation.
Product Item Another term for a case or SKU.
Product Quantity A quantity of a single Product Item or SKU to be delivered from one location to another on particular date but not at a particular time. These records are created by the inbound Bookings interface process. These records are displayed in the View Detail screen on the Bookings form.
Product Summary Another term for Booking.
Product Type The category that a Product Item, Case or SKU falls in to, usually associated with temperature e.g. FROZEN, PERISHABLE, AMBIENT.
Rate Card See Tariffs.
Reason Codes Of many types, defining exceptions: Adjustment, Non-conformance, Order.
Recalculate Distance and Times A C-TL function that is applied to a trip. The function checks the properties of the trip to ensure that it meets the defined rules for a trip in respect of drive times and driver’s breaks.
RDC; ROC Regional Distributions Centre and Regional Operating Centre. For transport operations with multiple depots, these depots are used for the final delivery.
Region Geographical Region. Also, Postal Region.
Receipt In transport terms, the process of receiving and uploading items into a depot. The process of receipt and unloading may be controlled by C-MCS (q.v.). See also Unloading.
Resource General term grouping the executors of a trip. Carriers, Drivers, Crew, Tractors, Vehicles, Trailers.
Revenue Monies received by an organisation from a third party such as a customer. Revenue is generated from an order, based on the customer's rate card.
Route A route is a fixed route that is repeated. A Trip is a unique trip, which may be created from a route.
Schedule The period to which a set of Orders and Trips will be assigned and scheduled. Usually, but not necessarily, a single day of the week so referred to as a Schedule Date that runs from 22:00 – 22:00 e.g. Schedule Date 11th July 2002 runs from 22:00 10-July-16 to 22:00 11-July-16.
Scheduled Order An Order that has been scheduled onto a Trip by the scheduling process.
Service Levels; Service Types Typically used to determine additional services for an order, or a quicker transport service.
Shunt A trunk (q.v.) movement between depots using the trunk network, typically of a much shorter length than a trunk movement.
SKU Stock Keeping Unit – another term for a Case.
Stop See Trip Stop.
Stop Type Along with the activity (q.v.), defines the stop use. Usually: SU - Start-up; PK - Pick-up; DL - Delivery; CL - Close-down.
Supplier A supplier brings goods to your transport operation for delivery through the transport network. This is used when transport customers have relationships with suppliers for delivery, but the transport operation has a relationship with the customer.
Surcharges Any changes applied to an invoice at invoice stage, rather than generated from the order or trip itself. Examples are: Fuel Surcharge/Rebate, Demurrage.
Tariffs Rate Cards, forming the basis of generating trip/carrier costs and order revenue.
TI Transport Instruction – another term for an Order.
TLM Transport Logistics Manager.
TMS Ref A unique transport movement ID, referring to a single transport movement request.
Tractor The driver cab, pulling the trailer.
Trailer The trailer carrying the goods. Can be several types.
Trans-Ship The process of receiving, cross-docking and despatching items within a depot, usually within a single transaction. In this implementation, this is the process at the RDC (q.v.).
Transport Any portion of an operation that deals with the execution of trips; the transport management office.
Trip A routed Truck Load of goods. For example, a trip that begins at Depot 1 where an Order is loaded, then travels to Store 1 where the Order is unloaded. Typically the trip would then return to Depot 1 to terminate the trip.
Trip Manipulation The manipulation of Scheduled Trips, whether it be to add a Carrier or to completely recalculate times on the Trip.
Trip Status The lifecycle of a trip. Typically: Planned; Tendered; Accepted; En-Route; Completed.
Trip Stop Stops within a trip at which specific activities would take place such as the loading or unloading of goods.
Trunk A route between depots, transporting goods usually to be delivered from the destination depot, but any transfer of goods from the original receiving or originating depot in the network to the final delivery depot (the out-base).
TU Transport Unit - box, tray, cage, tet, etc.; Also Asset, Asset Type.
TTM CALIDUS Portal TTM; Track and Trace Module; OBS Logistics' application dedicated to tracking and tracing order events with inputs from several external systems.
Unloading The process of receiving and uploading items into a depot. The process of receipt and unloading may be controlled by C-MCS (q.v.). See also Receiving.
Unscheduled Order An Order that is yet to be scheduled onto a Trip by the scheduling process.
Vehicle A generic term for a tractor (q.v.). This term may also be used to specifically identify a fixed tractor/trailer combination, for example a van, luton, etc.
Warehouse This is a depot in CTL-TMS that is seen to be a warehouse, or origin and storage point for product for delivery.
Application Usage Terms
Check box A box that when checked indicates that the item to the left is enabled. If unchecked, this is disabled or not in use.
DDL; Drop-down List A series of pre-designated answers to a particular question on a device, rather than requiring the user to key the answer in in full.
Field A single point of data entry on a screen, for example, a text box, drop-down list, check box, etc.
Look-up A pop-up window specifically designed to allow searching for and selected pre-configured data.
Pop-up A window (q.v.) that appears over the top of the open window.
Screen The functional area, for example, "the Debrief screen". All functionality for this functional area is contained within this screen.
Window The area of the browser used to display the screen and all contained entities.


Authorised By


Matt Tipping
OBS Project Manager
_____________________________

Paul Griffiths
Customer Representative
_____________________________
Retrieved from ‘https://calidusassist.adcservices.apteancloud.com/calidus-assist/OBS/index.php?title=FS_371933_6287_EBB_CTL_Operational_Documents&oldid=8809’