FS 374034 49195 CTL KPI Summary by Depot

From Calidus HUB






Aptean Logo.png







OBS Logistics Ltd

CTL KPI Summary by Depot Report

Functional Specification

17th June 2020 - 0.2
Reference: FS 374034 49195















FUNCTIONAL OVERVIEW

Client Requirement

KPI Summary by Depot - drivers, vehicles, miles, revenue, cost, vehicle utilisation fill, empty running, weighted average, total units, total weight, total volume, total PEF, driver hours, deliveries/ collections /returns. This summary must provide an overview of the business performance for a day, week and month.


Solution Overview

1 report will be written.

This will be run by the user and will be generated as a PDF report.


Scope

This change will be applied to system version 1.X on CTLDEV and once approved CTLTST and customer QA systems.


Impact

None


CONFIGURATION SET-UP

Pre-requisites

DevOps item 47341 - Operational Reports (base).


Menu Structure

N/A


Data

N/A


Implementation Advice

None

FUNCTIONAL DESCRIPTION

This is an operational report (not extract) and will be generated to a PDF report, strongly formatted.

The reports shall be named:

  • KPI Summary by Depot report.


Selection Criteria

  • Depot - Required. Default to accessible depot. Lookup of accessible depots.
  • Date Range or Schedule. Required. Defaulted from the existing selected or default schedule.
  • Period - a drop-down list of values:
    • Day
    • Week
    • Month


Report Format

Title

Set to "KPI SUMMARY BY DEPOT REPORT".

A sub-title will show the depot and period being reported on this page: 

Depot X - NAME. Period: [PERIOD]

The period is formatted by the following criteria:

  • Day - system date format e.g. "DD/MM/YYYY"
  • Week - week format "YYYY, week WW"
  • Month - month format "YYYY-Mmm"


Data Selection

Compared to a traditional report (which reports details in "header/detail/footer" style, this report is summarising several queries into one page per depot. Each section will select its own data from different data sources.

However, basic selection criteria will be required based on the parameters entered.

  • If no depot is selected, all depots will be reported on.
  • Trips will be selected based on the owning depot and the date range selected.
  • Orders will be selected based on the owning depot and the date range selected.
  • Trip data range selection should be based on the actual start date, or the planned date if not started.
  • Order data range selection should be based on the actual collection and delivery dates, or the planned dates if not completed.
  • Deleted trips should be excluded.
  • Cancelled orders should be excluded.
  • Drivers should be selected based on the carriers associated to that depot.
  • Vehicles should be selected based on the carriers associated to that depot.


Reporting Sections

Each page of data contains the following sections:

  • Drivers
  • Vehicles
  • Orders
  • Trips


1 page per depot per period reported. So:

  • if by date and a week range is selected, 7 pages will be produced, one for each day.
  • if by week and a 10 day range is selected, 2 pages will be produced, one for each week, with all data applicable to the weeks defined by the date range selected.
  • if by month and a single day is selected, 1 page will be produced, one for the month, with all data applicable to the month defined by the date range selected.


Drivers

One row per driver type, summed.

Columns:

  • "Type"
  • "Qty"
  • "Hours Available"
  • "Hours Worked"
  • "%Util"

Data:

  • "Type" - the person type
  • "Qty" - the count of people of this type.
  • "Hours Available" - the total hours available, taking into account system, organisation and carrier non-working days, the driver's assigned shift hours, calendar exceptions and country non-working days, summed.
  • "Hours Worked" - the total hours worked i.e. spent on trips. Note Note: If there are trips without debrief information (i.e. actuals), use the planned timea instead.
  • "%Util" - a percentage utilisation of resources of this type, based on the above two calculations.


Vehicles

Vehicles (based at carrier associated to this depot) by type.

Columns:

  • "Type"
  • "Qty"
  • "Trips"
  • "Distance (UOM)" - the distance unit of measure should be displayed here as an abbreviation i.e. "M" or "KM".
  • "Empty Running (UOM)" - the distance unit of measure should be displayed here as an abbreviation i.e. "M" or "KM".
  • "Hours Available"
  • "Hours Worked"
  • "%Util"


Data:

  • "Type" - the vehicle type.
  • "Qty" - the count of people of this type.
  • "Distance" - the number of trips assigned to vehicles of this type. If a trip is only assigned to a vehicle type, not an actual vehicle, do not count it.
  • "Distance (UOM)" - the summed actual miles of all of these trips for vehicles of this type. If actual information is not available for the trip, use the planned distance instead.
  • "Empty Running (UOM)" - where a vehicle has no BUE carried between stops, this distance between stops should be summed here for the trips selected above.
  • "Hours Available" - the total hours available, taking into account system, organisation and carrier non-working days, calendar exceptions and country non-working days, summed.
  • "Hours Worked" - the total hours worked i.e. spent on trips. Note Note: If there are trips without debrief information (i.e. actuals), use the planned timea instead.
  • "%Util" - a percentage utilisation of resources of this type, based on the above two calculations.


Orders

Orders Owned by this depot by Service Level

Columns:

  • "Service Level"
  • "Qty"
  • "Total units"
  • "Total weight (UOM)" - the weight unit of measure should be displayed here as an abbreviation e.g. "Kg" or "T".
  • "Total volume (UOM)" - the volume unit of measure should be displayed here as an abbreviation i.e. "m3" or "cu.f".
  • "Total BUE"
  • "Total Revenue (CURRENCY)" - the short currency code of the organisation should be displayed here e.g. "GBP".
  • "Total cost (CURRENCY)" - the short currency code of the organisation should be displayed here e.g. "GBP".


Data:

  • "Service Level" - service level name.
  • "Qty" - the count of orders of this service level.
  • "Total units" - the total quantity of all of the orders of this type, summed.
  • "Total weight (UOM)" - the total weight of all of the orders of this type, summed.
  • "Total volume (UOM)" - the total volume of all of the orders of this type, summed.
  • "Total BUE" - the total quantity of all of the orders of this type, summed.
  • "Total Revenue (CURRENCY)" - the total revenue of the orders selected, summed.
  • "Total cost (CURRENCY)" - the total apportioned transport costs of the orders selected, summed.


Trips

Trips by Type (Trunk/Radial) owned by this depot

Columns:

  • "Type"
  • "Qty"
  • "Avg Departure vehicle fill (BUE)"
  • "Avg Weighted average fill (BUE)"
  • "Empty Running (UOM)" - the distance unit of measure should be displayed here as an abbreviation i.e. "M" or "KM".
  • "Total units"
  • "Total weight (UOM)" - the weight unit of measure should be displayed here as an abbreviation e.g. "Kg" or "T".
  • "Total volume (UOM)" - the volume unit of measure should be displayed here as an abbreviation i.e. "m3" or "cu.f".
  • "Total BUE"
  • "Total cost (CURRENCY)" - the short currency code of the organisation should be displayed here e.g. "GBP".


Data:

  • "Type" - "Trunk" if a trunk trip else "Radial"
  • "Qty" - the count of trips of this type.
  • "Avg Departure vehicle fill (BUE)" - the first loading stop BUE for all trips of this type, summed.
  • "Avg Weighted average fill (BUE)" - the average BUE at departure of each stop for all trips of this type, summed.
  • "Empty Running (UOM)" - where a trip has no BUE carried between stops, this distance between stops should be summed here for the trips selected above.
  • "Total units" - the total quantity collected or loaded onto trips of this trip, summed.
  • "Total weight (UOM)" - the total weight collected or loaded onto trips of this type, summed.
  • "Total volume (UOM)" - the total volume collected or loaded onto trips of this type, summed.
  • "Total BUE" - the total quantity collected or loaded onto trips of this type, summed.
  • "Total cost (CURRENCY)" - the total transport costs of the trips selected, summed.


TEST PLAN

Test Script / Scenario ReferenceCTL KPI Summary by Depot ReportCall Number(s): 374034 49195
Test Script / Scenario DescriptionOutstanding Debrief ReportPASS / ISSUES / FAIL
Menu AccessReports 
Pre-requisitesMultiple trips and orders, resourced, planned, some accepted, some en-route, some debriefed (completed), some trip debriefed (confirmed), some partially debriefed, some with no debrief information.Tested By:
 
Test ObjectiveTo test that the Outstanding debrief report works.Date:
 


Step Action Result Remarks P/F
1 Reports      
         
1.01 Run the Oustanding Debrief report with a date range or schedule. Only trips within the date range calculated are displayed. Only trips from the depot selected are displayed. Only trips, stops, orders, lines and products missing debrief information are displayed.    


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


Neil Appadu
OBS Development Manager
_____________________________

Dave Meir
Product Manager
_____________________________
Retrieved from ‘https://calidusassist.adcservices.apteancloud.com/calidus-assist/OBS/index.php?title=FS_374034_49195_CTL_KPI_Summary_by_Depot&oldid=8914’