FS 371746 6616 EBB CTL Plan Trailer Swaps
EBB Paper
Plan Trailer Swaps
Functional Specification
19th May 2020 - 1.1
Reference: FS 371746 6616
Contents
FUNCTIONAL OVERVIEW
Client Requirement
This change is with reference to SCR 2 in the solution design document.
The operation will plan trailer or vehicle swaps by applying a trailer or vehicle to a trip as normal. The operation can then plan a trailer or vehicle swap at any location on the trip by entering a new trailer or vehicle against that stop.
Solution Overview
This change affects the Planning screen.
The planning screen will be modified to allow the users to select a stop on a trip and choose to change vehicle. This will allow the user to select a new vehicle ID.
The EPOD device will be informed of the changed vehicle which will display on the device.
Scope
This change will be applied to system version 1.00 on test database EBBCTST) and once approved EPPCPRD.
Impact
None.
CONFIGURATION SET-UP
Pre-requisites
Menu Structure
Data
Implementation Advice
FUNCTIONAL DESCRIPTION
There will be a facility against a planned trip stop to change the trailer type and ID. This applies only to collection/loading activity stops (or Both activity stops), but only against the collection activities at that stop.
When resourcing a trip initially, a trailer type, vehicle or trailer may be assigned to the trip.
If a trailer ID is assigned to the trip, the trailer type will default to that trailer's type.
When a vehicle ID, trailer type or trailer ID is assigned to the trip, it will be inherited against all stops (or stop activity) against the trip.
There will be a facility against any collection or both stop to allow the trailer type and/or trailer ID to be modified. This will be through a button against the collection/loading or Both-type stops.
When pressed, the screen should display a section below the stop allowing the vehicle ID, trailer type and/or trailer to be resourced from the resource list.
Note: The system will not stop a vehicle or trailer being changed, even if there are jobs travelling on from this location that were loaded at a prior location. In this case, the order is assumed to have been unloaded from vehicle or trailer one and loaded to vehicle or trailer 2.
The vehicle ID will be interfaced to C-ePOD, in order to view the trailer on the stops so that the driver can reveive instructions to change trailer.
TECHNICAL NOTES
Database/DAL Changes
File TRP_STOP
Column Name | Use |
---|---|
TRS_TRIP_REF | --- |
TRS_STOP_NO | --- |
TRS_STOP_TYPE | --- |
TRS_SEQUENCE | --- |
TRS_LOCATION_CODE | --- |
TRS_PLANNED_ARRIVE_DATETIME | --- |
TRS_PLANNED_DEPART_DATETIME | --- |
TRS_ACTUAL_ARRIVE_DATETIME | --- |
TRS_ACTUAL_DEPART_DATETIME | --- |
TRS_ACTIVE_IND | --- |
TRS_CREATED_BY | --- |
TRS_CREATED_DATE | --- |
TRS_LAST_UPDATED_BY | --- |
TRS_LAST_UPDATED_DATE | --- |
TRS_LAST_ACTIVE_CHANGE_BY | --- |
TRS_LAST_ACTIVE_CHANGE_DATE | --- |
TRS_LAST_PROCESS_ID | --- |
TRS_UPDATE_COUNTER | --- |
OR
File TRP_STOP_ACTIVITY
Column Name | Use |
---|---|
TSA_TRIP_REF | --- |
TSA_STOP_NO | --- |
TSA_SEQUENCE | --- |
TSA_ORDER_TMS_REF | --- |
TSA_ACTIVITY | --- |
TSA_ACTIVE_IND | --- |
TSA_CREATED_BY | --- |
TSA_CREATED_DATE | --- |
TSA_LAST_UPDATED_BY | --- |
TSA_LAST_UPDATED_DATE | --- |
TSA_LAST_ACTIVE_CHANGE_BY | --- |
TSA_LAST_ACTIVE_CHANGE_DATE | --- |
TSA_LAST_PROCESS_ID | --- |
TSA_UPDATE_COUNTER | --- |
Must add a new field to specify vehicle ID, trailer type and trailer ID against the stop or stop activity.
Planning Screen
Facility against a planned trip stop to change the trailer type and ID. This applies only to collection/loading activity stops (or Both activity stops), but only against the collection activities at that stop.
When resourcing a trip initially, a trailer type, vehicle or trailer may be assigned to the trip.
If a trailer ID is assigned to the trip, the trailer type should default to that trailer's type.
When a vehicle ID, trailer type or trailer ID is assigned to the trip, it should be inherited against all stops (or stop activity) against the trip.
If a vehicle ID, trailer type or trailer ID has been assigned to the trip, then there should be a facility against any collection or both stop to allow the trailer type and/or trailer ID to be modified.
This should be through a button against the collection/loading or Both-type stops.
When pressed, the screen should display a section below the stop allowing the vehicle ID, trailer type and/or trailer to be resourced from the resource list.
If a trailer is selected against the stop, then the trailer type of this stop will be defaulted to this trailer's type.
When a vehicle ID, trailer type or trailer ID is assigned to a stop, it should be set against this stop and inherited against all stops (or stop activity) following this stop on the trip.
Note: For Both type stops, the new vehicle and trailer IDs should be inherited against only the Collection/Loading activities at this stop.
Note: The system will not stop a vehicle or trailer being changed, even if there are jobs travelling on from this location that were loaded at a prior location. In this case, the order is assumed to have been unloaded from vehicle or trailer one and loaded to vehicle or trailer 2.
CTL-EPOD Interface
The trailer ID set against a trip should be sent to C-ePOD in EPOD_LOAD.EPL_TRAILER_ID.
The trailer ID set against a trip stop should be sent to C-ePOD in EPOD_JOB.EPL_TRAILER_ID.
For stops of type Both, the delivery jobs at this stop should still retain the previous stop's trailer ID. Note that if the trailer type and ID is stored against the stop activity, then this will not require any development. If it is stored against the stop itself, then the process will have to be modified to "remember" the prior stop's trailer ID and type.
When orders have a different vehicle type or trailer type to a previous stop, the job information sent to EPOD must contain the text "Vehicle/Trailer changed to XXX". The field is EPOD_JOB.EPL_JOB_INFORMATION.
APPENDIX A: DOCUMENT HISTORY
References
Ref No | Document Title & ID | Version | Date |
1 | SDD 366558 EBB Paper CTL Solution Design | 3.0 | 29/04/2020 |
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 | _____________________________ |