FS 372499 6233 CTL Planning Screen Improvements
OBS Logistics Ltd
CTL Planning Screen Improvements
Functional Specification
28th May 2020 - 1.2
Reference: FS 372499 6233
Contents
FUNCTIONAL OVERVIEW
Client Requirement
Planning/Resourcing screen improvements:
- needs to be more information on trips themselves (e.g. cost, distance, owner, carrier, etc). Possibly just on the full-window view?
- Automatic filtering of trips by ownership.
- Reduction of filtering by carrier - can't see the trips for a depot if carried by multiple carriers. At least an "All" option when planning.
- Change trip status: PLANNED/ACCEPTED/EN-ROUTE.
- Need to be able to operate the screen in EITHER planning OR resourcing OR viewing mode. In other words, allow the two side panels to be hidden.
- Better search criteria or orders and trips.
- More (and configurable) details shown for orders.
- Search for trunk or radial trips.
Solution Overview
The planning screen will be modified for this change.
The screen will allow a full "control tower" view to see all trips for all depots.
The trip cards will include more information, such as the owning depot code and carrier.
The search criteria for trips will be extended to allow more specific searching.
The filter criteria for trips that have been found will be extended to allow more specific searching.
The screen will more obviously display when a filter has been applied, and will sort the matching trips to the first tabs, to more easily find and see the matching trips. This trip filter will be easily cleared.
The search criteria for unassigned orders will be extended to allow more specific searching.
The filter criteria for unassigned orders that have been found will be extended to allow more specific searching.
The screen will more obviously display when a filter has been applied. This trip filter will be easily cleared.
Scope
This change will be applied to system version 1.X on CTLDEV and once approved CTLTST and customer QA systems.
The following elements already specify changes in this area:
- needs to be more information on trips themselves (e.g. cost, distance, owner, carrier, etc). Possibly just on the full-window view?
- 6055 - Need to be able to assign internal carriers to trip.
- Automatic filtering of trips by ownership.
- 372329 5955 - Allocation of legs
- Change trip status: PLANNED/ACCEPTED/EN-ROUTE.
- 372305 5934 - Allow change of trip status
- Need to be able to operate the screen in EITHER planning OR resourcing OR viewing mode. In other words, allow the two side panels to be hidden.
- 372254 6267 - Planning Screen Enhancements
The screen already does the following
- More (and configurable) details shown for orders.
- The screen allows many fields to be shown and hidden for the unavailable orders list.
- Also 5846 - Need to be able to change the sequence of the columns in the order well. The sequence should persist between sessions.
- needs to be more information on trips themselves (e.g. cost, distance, owner, carrier, etc). Possibly just on the full-window view?
- The screen already displays cost, revenue and distance through a pop-out panel.
Note also that Trip Searching will be modified by the proposed implementation of Schedule into the system.
- 372263 6178 - Schedule Proposal
Impact
None
CONFIGURATION SET-UP
Pre-requisites
371767 6283 - Bespoke Scheduling Engine Process
When a order runs through the scheduling engine, the process should mark that the order has been through, whether it is successful or not. That is then used as a filter for the scheduling engine to not process that order again. It is also referenced below in the Auto-processed order filter.
If the change above is not completed before this change, then the order filter for Auto-processed orders must be completed as part of of task 6283, or in a new task after that is completed.
Note: This is dependent on this functionality being added to the system as part of these changes - currently, this has NOT been applied as part of these changes and will be subject to a new work item to implement.
Menu Structure
N/A
Data
N/A
Implementation Advice
The existing debrief documentation within CALIDUS Assist must be updated to reflect the new way to use the screen.
FUNCTIONAL DESCRIPTION
Planning Screen
The planning screen will be modified for this change.
Owning Depot
The list of owning depots defaults to the Owning Depot parameter of the user group.
If no owning depot parameter is found, all depots should be shown without errors. The user should also have an option to select "All Depots". This is only available when the user has no owning depot parameter, and is the default.
When in this mode, the screen will be in read-only mode - the user will not be able to affect changes to trips.
Trip Information
The following is proposed under TFS work item 6055:
- Display the carrier against a trip card.
The screen will be changed as part of this task as follows:
If the user has selected "All Depots", the trip cards must prominently display the Owning Depot code. That must be displayed in the trip card in both minimal and full-screen view.
Trip Search
This currently allows the following criteria:
- Trip Date Range
- Status
This will be modified by other TFS tasks to allow selection of Schedule.
Trip Filtering
Trip Filtering filters the list of trips, making trips less opacity if they do not match the filter.
This should change as follows:
- Change filter criteria.
- Re-order the matching trips so that they are on the first tabs.
The filter criteria currently allows:
- Trip Reference
- Trip Name
- Location Name
- Driver Name
- Vehicle
- Trailer
The filter criteria will be modified as follows:
- Trip Reference - "LIKE" matching on the trip ID
- Trip Name - free-text entry, also with a look-up of all routes in the system, with a facility to show only those for your owning depot through a check-box (the default option, checked).
- Location Name - "LIKE" matching on any location on any stop on the trips.
- Driver Name - "LIKE" matching on the driver name.
- Vehicle - "LIKE" matching on the vehicle.
- Trailer - "LIKE" matching on the trailer.
- Carrier - a look-up of accessible carriers only, or all carriers.
- Route Code - a look-up of all routes in the system, with a facility to show only those for your owning depot through a check-box (the default option, checked).
- Owning Depot - only available if the user has selected "All Depots" from the header. This should be a drop-down list of all depots in the network, with a default option of "Select a depot".
- Trunk/Radial - a drop-down list of "All" (the default), "Trunk Only" or "Radial Only".
- Customer Ref - "LIKE" matching on any trips with orders that have a matching customer ref.
- Order Ref - "LIKE" matching on any trips with orders that have a matching order ref.
- Booking Ref - "LIKE" matching on any trips with orders that have a matching booking ref.
- Customer - "LIKE" matching on any trips with orders that have a matching customer name. A lookup of customers should be provided.
- Order Group - "LIKE" matching on any trips with orders that have a matching order group. A lookup of customers should be provided.
The trip filter should have another button in the title to "Clear All" (red button). This button should be shown dynamically when any filter is populated. Clicking this button should clear all filters applied, or reset them to their default values.
When any trip filter is applied, the trip Filter button should be green, so the user can clearly see that a filter is applied.
When a trip filter is applied, all trips not matching the filter are made transparent.
This should also re-order the trips on the tabs, so that the matching trips are shown on the first tabs. The first tab should be shown.
When removing filters or clearing all filters, the trips should be re-paginated back to their original sort sequence.
Order Search
Order Search currently allows the following criteria:
- Order Date Range
- Customer Group
- Status
- Service Level
This will be modified by other TFS tasks to allow selection of Schedule.
This will be modified as part of this change to add a facility to optionally enter a zone.
This will provide a lookup of zones available in the system.
Order Filtering
Order Filtering filters the list of orders, removing orders that do not match the filter.
The filter criteria currently allows:
- Order Number
- Location name
- Postal Code
- Weight - greater than/equal to/less than
- Volume - greater than/equal to/less than
The filter criteria will be modified as follows:
- Order Number - "LIKE" match to the TMS order reference
- Customer Ref - "LIKE" matching on orders that have a matching customer ref.
- Order Group - "LIKE" matching on orders that have a matching order group. A lookup of order groups should be provided.
- Customer Name - "LIKE" matching on orders that have a matching customer name. A lookup of customers should be provided.
- Location name - "LIKE" match a location on the order, or the current planned location of the order. Provide a lookup of locations.
- Postal Code - "LIKE" match a postcode on any location on the order, or the current planned location.
- Weight - greater than/equal to/less than
- Volume - greater than/equal to/less than
- Auto-processed - whether the order has been through the scheduling engine.
The order filter should have another button in the title to "Clear All" (red button). This button should be shown dynamically when any filter is populated. Clicking this button should clear all filters applied, or reset them to their default values.
When any order filter is applied, the order Filter button should be green, so the user can clearly see that a filter is applied.
TECHNICAL NOTES
Owning Depot
The list of owning depots defaults to the Owning Depot parameter of the user group.
If no owning depot parameter is found, all depots should be shown without errors. The user should also have an option to select "All Depots". This is only available when the user has no owning depot parameter, and is the default.
When in this mode, the screen will be in read-only mode - the user will not be able to affect changes to trips.
Trip Information
If the user has selected "All Depots", the trip cards must prominently display the Owning Depot code. That must be displayed in the trip card in both minimal and full-screen view.
Trip Filtering
The filter criteria will be modified as follows:
- Trip Reference - "LIKE" matching on the trip ID
- Trip Name - free-text entry, also with a look-up of all routes in the system, with a facility to show only those for your owning depot through a check-box (the default option, checked).
- Location Name - "LIKE" matching on any location on any stop on the trips.
- Driver Name - "LIKE" matching on the driver name.
- Vehicle - "LIKE" matching on the vehicle.
- Trailer - "LIKE" matching on the trailer.
- Carrier - a look-up of accessible carriers only, or all carriers.
- Route Code - a look-up of all routes in the system, with a facility to show only those for your owning depot through a check-box (the default option, checked).
- Owning Depot - only available if the user has selected "All Depots" from the header. This should be a drop-down list of all depots in the network, with a default option of "Select a depot".
- Trunk/Radial - a drop-down list of "All" (the default), "Trunk Only" or "Radial Only".
- Customer Ref - "LIKE" matching on any trips with orders that have a matching customer ref.
- Order Ref - "LIKE" matching on any trips with orders that have a matching order ref.
- Booking Ref - "LIKE" matching on any trips with orders that have a matching booking ref.
- Customer - "LIKE" matching on any trips with orders that have a matching customer name. A lookup of customers should be provided.
- Order Group - "LIKE" matching on any trips with orders that have a matching order group. A lookup of customers should be provided.
The trip filter should have another button in the title to "Clear All" (red button). This button should be shown dynamically when any filter is populated. Clicking this button should clear all filters applied, or reset them to their default values.
When any trip filter is applied, the trip Filter button should be green, so the user can clearly see that a filter is applied.
When a trip filter is applied, all trips not matching the filter are made transparent.
This should also re-order the trips on the tabs, so that the matching trips are shown on the first tabs. The first tab should be shown.
When removing filters or clearing all filters, the trips should be re-paginated back to their original sort sequence.
Order Search
Order Search currently allows the following criteria:
- Order Date Range
- Customer Group
- Status
- Service Level
This will be modified by other TFS tasks to allow selection of Schedule.
This will be modified as part of this change to add a facility to optionally enter a zone.
This will provide a lookup of zones available in the system.
When submitted, this will be used to find orders where the postcode is within the ranges included in the zone selected or not within the range of postcodes excluded from the zone selected, and also within any zones included in that zone or sub-zones.
For example:
- Zone B-ZONE1 includes all postcode B1-B2 and B4-B4.
- Cone B-ZONE2 includes all postcodes from B11-B99
- Zone B-ZONE3 includes all postcodes from B1-B99 and excludes zones B-ZONE1 and B-ZONE2
- Zone B includes EITHER all postcodes from B1-B99, or could instead be defined as including zones B-ZONE1, B-ZONE2 and B-ZONE3.
- Zone MIDLANDS includes zone B (and other zones).
- Zone UK includes MIDLANDS (and other zones).
Entering criteria for B would bring find orders where the postcode is in B1-B99, whereas searching for B-ZONE1 will only find orders where the postcode is in B1-B2 or B4.
Note: The zone should match against any location on the order, namely:
- The order is from any location in that zone.
- To order is to any location in that zone.
- The order has been planned up to any location in that zone.
Order Filtering
The filter criteria will be modified as follows:
- Order Number - "LIKE" match to the TMS order reference
- Customer Ref - "LIKE" matching on orders that have a matching customer ref.
- Order Group - "LIKE" matching on orders that have a matching order group. A lookup of order groups should be provided.
- Customer Name - "LIKE" matching on orders that have a matching customer name. A lookup of customers should be provided.
- Location name - "LIKE" match a location on the order, or the current planned location of the order. Provide a lookup of locations.
- Postal Code - "LIKE" match a postcode on any location on the order, or the current planned location.
- Weight - greater than/equal to/less than
- Volume - greater than/equal to/less than
- Auto-processed - whether the order has been through the scheduling engine.
The order filter should have another button in the title to "Clear All" (red button). This button should be shown dynamically when any filter is populated. Clicking this button should clear all filters applied, or reset them to their default values.
When any order filter is applied, the order Filter button should be green, so the user can clearly see that a filter is applied.
TEST PLAN
| Test Script / Scenario Reference | CTL Planning Screen Improvements | Call Number(s): 372499 6233 |
| Test Script / Scenario Description | Planning Screen Improvements | PASS / ISSUES / FAIL |
| Menu Access | Trip Planning | |
| Pre-requisites | Multiple trips and orders. | Tested By: |
| Test Objective | To test that: All depots can be selected; trip search works as expected; trip filtering works as expected; filtered trips are resequenced; order search works as expected; order filtering works as expected;can be saved without confirming all changes; trips can be reopened; unsaved data changes are warned. | Date: |
| Step | Action | Result | Remarks | P/F |
| 1 | Trip Planning | |||
| 1.01 | Select Owning Depot "All Depots" | Trips for all depots are displayed. Trips may not be modified. Owning depot is displayed in the trip card. | ||
| 1.02 | Test new search criteria for trips | Trips are displayed matching the criteria entered | ||
| 1.03 | Search for all trips. Filter trips using the new criteria. | Trips are filtered matching the criteria entered. Non-matching are obscured. Matching are moved to the first tabs. The first tab is shown. Clear all button is present and clears all filters. When filters are applied, the button clearly displays this. | ||
| 1.04 | Test new search criteria for order (specifically zones) | Trips are displayed matching the criteria entered. Zone matching works as expected. | ||
| 1.05 | Search for all orders. Filter orders using the new criteria. | Orders are filtered matching the criteria entered. Non-matching are not displayed. Clear all button is present and clears all filters. When filters are applied, the button clearly displays this. |
APPENDIX A: DOCUMENT HISTORY
References
| Ref No | Document Title & ID | Version | Date |
| 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
Neil Appadu | OBS Development Manager | _____________________________ |
Dave Meir | Product Manager | _____________________________ |
