Template:CTMS Glossary - Revision history

Anw: Minor correction

2025-04-28T12:09:17Z

Minor correction

← Older revision		Revision as of 14:09, 28 April 2025
Line 35:		Line 35:
	\|C-TMS \|\| ''CALIDUS'' TMS, Aptean's Transport Management System.		\|C-TMS \|\| ''CALIDUS'' TMS, Aptean's Transport Management System.
	\|-		\|-
	\|CSB \|\|This refers to Carrier Self Billing, the process that [[C-TMS]] uses to produce and send invoices to carriers.		\|CSB \|\|This refers to Carrier Self Billing, the process that C-TMS uses to produce and send invoices to carriers.
	\|-		\|-
	\|Customer \|\| In 3PL terms, the customer on behalf of which the transport is being operated.		\|Customer \|\| In 3PL terms, the customer on behalf of which the transport is being operated.
Line 111:		Line 111:
	\|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’.		\|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-TMS]]. Any subsequent manipulation of these Orders would be Post Schedule manipulation.		\|Post Schedule \|\|The period after Orders have been scheduled in the Scheduling Program and then returned to C-TMS. 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-TMS]]. Any manipulation of these Orders would be Pre Schedule manipulation.		\|Pre Schedule \|\|The period before Orders have been scheduled in the Scheduling Program and then returned to C-TMS. Any manipulation of these Orders would be Pre Schedule manipulation.
	\|-		\|-
	\|Product Item \|\|Another term for a case or SKU		\|Product Item \|\|Another term for a case or SKU

Anw: Minor correction

2025-04-28T12:08:36Z

Minor correction

Anw: Updated to latest version

2024-08-21T15:06:57Z

Updated to latest version

← Older revision		Revision as of 17:06, 21 August 2024
Line 1:		Line 1:
	{\| class="wikitable" border="1"		{\| class="wikitable apt-searchable" border="1"
	\|- bgcolor="silver"		\|- bgcolor="silver"
	!width="20%"\|Term or Acronym !! Meaning		!width="20%"\|Term or Acronym !! Meaning
Line 8:		Line 8:
	\|-		\|-
	\|Asset \|\| A traceable DU; the item that is tracked during delivery and collection. This Asset has a type (e.g. Cage, Tet, etc).		\|Asset \|\| A traceable DU; the item that is tracked during delivery and collection. This Asset has a type (e.g. Cage, Tet, etc).
			\|-
			\|Audit Log \|\|A log of events that have happened in the [[C-TMS]] 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.
	\|-		\|-
	\|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.		\|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.
	\|-		\|-
	\|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.		\|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 outbases (q.v.) or final delivery to destinations. See also Consolidation.		\|Consolidating Centre \|\| A depot that takes delivery of goods from several origins and consolidates them for trunking to outbases (q.v.) or final delivery to destinations. See also Consolidation.
Line 28:		Line 34:
	\|-		\|-
	\|C-TMS \|\| ''CALIDUS'' TMS, OBS Logistics' Transport Management System.		\|C-TMS \|\| ''CALIDUS'' TMS, OBS Logistics' Transport Management System.
			\|-
			\|CSB \|\|This refers to Carrier Self Billing, the process that [[C-TMS]] uses to produce and send invoices to carriers.
	\|-		\|-
	\|Customer \|\| In 3PL terms, the customer on behalf of which the transport is being operated.		\|Customer \|\| In 3PL terms, the customer on behalf of which the transport is being operated.
Line 48:		Line 56:
	\|-		\|-
	\|Driver \|\| Comprising drivers and crew assigned to a trip.		\|Driver \|\| Comprising drivers and crew assigned to a trip.
			\|-
			\|Drivers Day \|\|A schedule of work that a driver would undertake in a day including any rest periods and breaks.
	\|-		\|-
	\|Drop \|\| A stop on a trip.		\|Drop \|\| A stop on a trip.
	\|-		\|-
	\|DU \|\| Distribution/Deliverable Unit - box, tray, cage, tet, etc.; Also Asset, Asset Type.		\|DU \|\| Distribution/Despatch/Deliverable Unit - box, tray, cage, tet, etc.; Also Asset, Asset Type.
	\|-		\|-
	\|EDI \|\| Electronic Data Interchange - a mechanism by which 2 systems can communicate normally without user intervention.		\|EDI \|\| Electronic Data Interchange - a mechanism by which 2 systems can communicate normally without user intervention.
Line 62:		Line 72:
	\|-		\|-
	\|Fixed Schedule \|\| An order that occurs at a fixed time. Differing from the above, the order will be created in the schedule; Also Milk Run.		\|Fixed Schedule \|\| An order that occurs at a fixed time. Differing from the above, the order will be created in the schedule; Also Milk Run.
			\|-
			\|Fuel Surcharge \|\|An additional charge that may be applied to a Transport charge to reflect the increasing price of fuel.
			\|-
			\|Isotrak \|\|A third party software package that allows users to be informed of the whereabouts of their vehicles using GPS technology. Interfaces with C-TMS in order to provide ‘actuals’ information for trips (i.e. the time a trip arrived at a stop and the amount of pallets that were delivered).
	\|-		\|-
	\|Item \|\| A single item for delivery/collection.		\|Item \|\| A single item for delivery/collection.
Line 84:		Line 98:
	\|-		\|-
	\|Order \|\| Equiv: OMS Ref; a transport movement.		\|Order \|\| Equiv: OMS Ref; a transport movement.
			\|-
			\|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, usually UNSCHEDULED->SCHED-COLL->SCHEDULED->DELIVERED/FAILED/CANCELLED.		\|Order Status \|\| The lifecycle of an order, usually UNSCHEDULED->SCHED-COLL->SCHEDULED->DELIVERED/FAILED/CANCELLED.
Line 91:		Line 107:
	\|Outbase \|\| A depot whose purpose is to deliver to final delivery destination within a geographically-restricted subsection of the whole catchment area; also ROC, RDC.		\|Outbase \|\| A depot whose purpose is to deliver to final delivery destination within a geographically-restricted subsection of the whole catchment area; also ROC, RDC.
	\|-		\|-
			\|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-TMS]]. 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-TMS]]. 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
			\|-
	\|Reason Codes \|\| Of many types: Adjustment, Non-conformance, Order.		\|Reason Codes \|\| Of many types: Adjustment, Non-conformance, Order.
			\|-
			\|Recalculate Distance and Times \|\|A C-TMS 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.
	\|-		\|-
	\|Receipt \|\| In transport terms, the process of receiving and uploading items into a depot. In this implementation, the process of receipt and unloading is predominantly controlled by C-MCS (q.v.). See also Unloading.		\|Receipt \|\| In transport terms, the process of receiving and uploading items into a depot. In this implementation, the process of receipt and unloading is predominantly controlled by C-MCS (q.v.). See also Unloading.
Line 98:		Line 132:
	\|-		\|-
	\|Resources \|\| Drivers, Crew, Tractors, Vehicles, Trailers		\|Resources \|\| Drivers, Crew, Tractors, Vehicles, Trailers
			\|-
			\|Revenue
			\|Monies received by a cost centre from a third party such as a customer.
	\|-		\|-
	\|Route \|\| A route is a fixed route that is repeated. A Trip is a unique trip, which may be created from a route.		\|Route \|\| A route is a fixed route that is repeated. A Trip is a unique trip, which may be created from a route.
Line 105:		Line 142:
	\|RDC \|\|Regional Distribution Centre.		\|RDC \|\|Regional Distribution Centre.
	\|-		\|-
	\|RPE \|\| ~~Roll-pallet Equivalent;~~ Regular Pallet Equivalent - This is used to estimate volume and therefore capacity of vehicles within C-TMS.		\|RPE \|\| Regular Pallet Equivalent - This is used to estimate volume and therefore capacity of vehicles within C-TMS.
	\|-		\|-
	\|Schedule \|\| A day's plan, usually consisting of 24 hours, not necessarily from midnight to midnight.		\|Schedule \|\| A day's plan, usually consisting of 24 hours, not necessarily from midnight to midnight.
Line 113:		Line 150:
	\|Shunt \|\|A trunk (q.v.) movement between depots using the trunk network, typically of a much shorter length than a trunk movement.		\|Shunt \|\|A trunk (q.v.) movement between depots using the trunk network, typically of a much shorter length than a trunk movement.
	\|-		\|-
	\|Stop \|\|A stop on a trip. In this solution, Drop is the pre-assigned fixed route drop number, whereas Stop is the generated CTMS stop ID.		\|Sourcing Unit \|\|A second entity that can be applied to a Lane, and all charges relating to that Lane will then be applied to the Sourcing Unit and not the Customer.
			\|-
			\|Stop \|\|Also Trip Stop. A stop on a trip. In this solution, Drop is the pre-assigned fixed route drop number, whereas Stop is the generated CTMS stop ID.
	\|-		\|-
	\|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.		\|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.		\|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		\|TLM \|\| Transport Logistics Manager
Line 128:		Line 169:
	\|-		\|-
	\|Trip \|\| C-TMS: A selection of work to be completed, specifically a workload that lasts for an entire shift for a driver.		\|Trip \|\| C-TMS: A selection of work to be completed, specifically a workload that lasts for an entire shift for a driver.
			\|-
			\|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		\|Trip Status \|\| The lifecycle of a trip

Anw: Extended TMS Glossary

2024-05-03T13:17:44Z

Extended TMS Glossary

← Older revision		Revision as of 15:17, 3 May 2024
Line 48:		Line 48:
	\|-		\|-
	\|Driver \|\| Comprising drivers and crew assigned to a trip.		\|Driver \|\| Comprising drivers and crew assigned to a trip.
			\|-
			\|Drop \|\| A stop on a trip.
	\|-		\|-
	\|DU \|\| Distribution/Deliverable Unit - box, tray, cage, tet, etc.; Also Asset, Asset Type.		\|DU \|\| Distribution/Deliverable Unit - box, tray, cage, tet, etc.; Also Asset, Asset Type.
Line 55:		Line 57:
	\|ERP \|\| Enterprise Resource Planning		\|ERP \|\| Enterprise Resource Planning
	\|-		\|-
	\|Fixed Route \|\| ~~Provides~~ a series of timed slots into which orders will fit.		\|Fixed Route Template \|\|A template in C-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 C-TMS fixed route template (q.v.) can be used to create these.
	\|-		\|-
	\|Fixed Schedule \|\| An order that occurs at a fixed time. Differing from the above, the order will be created in the schedule; Also Milk Run.		\|Fixed Schedule \|\| An order that occurs at a fixed time. Differing from the above, the order will be created in the schedule; Also Milk Run.
Line 62:		Line 66:
	\|-		\|-
	\|Load \|\| C-TMS: A trip that encompasses just a vehicle-full of items, or one journey out and back to a depot.		\|Load \|\| C-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. In this implementation, the process of loading and despatching is predominantly controlled by C-MCS (q.v.). See also Despatch.
	\|-		\|-
	\|Location \|\| In C-TMS terms, a trip comprises visits or drops to many locations. A location can be of many different types.		\|Location \|\| In C-TMS terms, a trip comprises visits or drops to many locations. A location can be of many different types.
Line 99:		Line 105:
	\|RDC \|\|Regional Distribution Centre.		\|RDC \|\|Regional Distribution Centre.
	\|-		\|-
	\|RPE \|\| Roll-pallet Equivalent - This is used to estimate volume and therefore capacity of vehicles within C-TMS.		\|RPE \|\| Roll-pallet Equivalent; Regular Pallet Equivalent - This is used to estimate volume and therefore capacity of vehicles within C-TMS.
	\|-		\|-
	\|Schedule \|\| A day's plan, usually consisting of 24 hours, not necessarily from midnight to midnight.		\|Schedule \|\| A day's plan, usually consisting of 24 hours, not necessarily from midnight to midnight.
	\|-		\|-
	\|Service Levels; Service Types \|\| Typically used to determine additional services for an order, or a quicker transport service. This defines the order windows i.e. the collection and delivery windows and offsets relating to the service level, through schedule rules.		\|Service Levels; Service Types \|\| Typically used to determine additional services for an order, or a quicker transport service. This defines the order windows i.e. the collection and delivery windows and offsets relating to the service level, through schedule rules.
			\|-
			\|Shunt \|\|A trunk (q.v.) movement between depots using the trunk network, typically of a much shorter length than a trunk movement.
			\|-
			\|Stop \|\|A stop on a trip. In this solution, Drop is the pre-assigned fixed route drop number, whereas Stop is the generated CTMS stop ID.
	\|-		\|-
	\|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.		\|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.
Line 120:		Line 130:
	\|-		\|-
	\|Trip Status \|\| The lifecycle of a trip		\|Trip Status \|\| The lifecycle of a trip
			\|-
			\|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).
	\|-		\|-
	\|TTM \|\| ''CALIDUS'' TTM; Track and Trace Module; OBS Logistics' application dedicated to tracking and tracing order events with inputs from several external systems.		\|TTM \|\| ''CALIDUS'' 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. In this implementation, the process of receipt and unloading is predominantly controlled by C-MCS (q.v.). See also Receiving.
	\|-		\|-
	\|WCS \|\| Warehouse Control System		\|WCS \|\| Warehouse Control System

Anw: Expanded

2023-08-11T08:03:57Z

Expanded

← Older revision		Revision as of 10:03, 11 August 2023
Line 12:		Line 12:
	\|-		\|-
	\|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.		\|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.
			\|-
			\|Consolidating Centre \|\| A depot that takes delivery of goods from several origins and consolidates them for trunking to outbases (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 C-TMS and; Manual (Ad Hoc) Consolidation, where the driver decides that two jobs should be delivered/collected at the same time.		\|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 C-TMS and; Manual (Ad Hoc) Consolidation, where the driver decides that two jobs should be delivered/collected at the same time.
Line 31:		Line 33:
	\|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.		\|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.
	\|-		\|-
	\|Debrief \|\| Comprises 2 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.		\|Debrief \|\| Comprises 3 parts: Trip debrief, where general trip notes and vehicle information is captured; 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.
	\|-		\|-
	\|Delivery Types \|\| This defines the category of the order, and is intrinsically linked to revenue and cost tariffs.		\|Delivery Types \|\| This defines the category of the order, and is intrinsically linked to revenue and cost tariffs.
Line 38:		Line 40:
	\|-		\|-
	\|Depot \|\| Any location that schedules and controls transport.		\|Depot \|\| Any location that schedules and controls transport.
			\|-
			\|Despatch \|\| In transport terms, the process of loading and despatching items out of a depot. In this implementation, the process of loading and despatching is predominantly 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.		\|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.
Line 75:		Line 79:
	\|Order \|\| Equiv: OMS Ref; a transport movement.		\|Order \|\| Equiv: OMS Ref; a transport movement.
	\|-		\|-
	\|Order Status \|\| The lifecycle of an order		\|Order Status \|\| The lifecycle of an order, usually UNSCHEDULED->SCHED-COLL->SCHEDULED->DELIVERED/FAILED/CANCELLED.
	\|-		\|-
	\|OTIF \|\| On Time In Full - Metrics to measure successful collection or delivery.		\|OTIF \|\| On Time In Full - Metrics to measure successful collection or delivery.
			\|-
			\|Outbase \|\| A depot whose purpose is to deliver to final delivery destination within a geographically-restricted subsection of the whole catchment area; also ROC, RDC.
	\|-		\|-
	\|Reason Codes \|\| Of many types: Adjustment, Non-conformance, Order.		\|Reason Codes \|\| Of many types: Adjustment, Non-conformance, Order.
	\|-		\|-
	\|Region \|\| Geographical Region. Also, Postal Region.		\|Receipt \|\| In transport terms, the process of receiving and uploading items into a depot. In this implementation, the process of receipt and unloading is predominantly controlled by C-MCS (q.v.). See also Unloading.
			\|-
			\|Region \|\| Geographical Region. Also, Postal Region. Regions are allocated to Depots and are used to determine ownership of a particular Order.
	\|-		\|-
	\|Resources \|\| Drivers, Crew, Tractors, Vehicles, Trailers		\|Resources \|\| Drivers, Crew, Tractors, Vehicles, Trailers
	\|-		\|-
	\|Route \|\| A route is a fixed route that is repeated. A Trip is a unique trip, which may be created from a route.		\|Route \|\| A route is a fixed route that is repeated. A Trip is a unique trip, which may be created from a route.
			\|-
			\|ROC \|\|Regional Operating Centre; a depot whose purpose is to deliver to final delivery destination within a geographically-restricted subsection of the whole catchment area; also Outbase.
			\|-
			\|RDC \|\|Regional Distribution Centre.
	\|-		\|-
	\|RPE \|\| Roll-pallet Equivalent - This is used to estimate volume and therefore capacity of vehicles within C-TMS.		\|RPE \|\| Roll-pallet Equivalent - This is used to estimate volume and therefore capacity of vehicles within C-TMS.
Line 91:		Line 103:
	\|Schedule \|\| A day's plan, usually consisting of 24 hours, not necessarily from midnight to midnight.		\|Schedule \|\| A day's plan, usually consisting of 24 hours, not necessarily from midnight to midnight.
	\|-		\|-
	\|Service Levels; Service Types \|\| Typically used to determine additional services for an order, or a quicker transport service.		\|Service Levels; Service Types \|\| Typically used to determine additional services for an order, or a quicker transport service. This defines the order windows i.e. the collection and delivery windows and offsets relating to the service level, through schedule rules.
	\|-		\|-
	\|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.		\|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.

Anw: Minor correction

2020-07-13T12:04:59Z

Minor correction

← Older revision		Revision as of 14:04, 13 July 2020
Line 22:		Line 22:
	\|-		\|-
	\|Cross-Dock \|\| Also a specific location at which product is exchanged.		\|Cross-Dock \|\| Also a specific location at which product is exchanged.
			\|-
			\|C-ePOD; EPOD\|\|Electronic Proof of Delivery. The OBSL EPOD system is ''CALIDUS'' ePOD.
	\|-		\|-
	\|C-TMS \|\| ''CALIDUS'' TMS, OBS Logistics' Transport Management System.		\|C-TMS \|\| ''CALIDUS'' TMS, OBS Logistics' Transport Management System.

Anw: Categorisation of document pages

2020-07-02T09:10:46Z

Categorisation of document pages

← Older revision		Revision as of 11:10, 2 July 2020
Line 116:		Line 116:
	<noinclude>		<noinclude>
	[[Category:Templates\|{{PAGENAME}}]]		[[Category:Templates\|{{PAGENAME}}]]
			[[Category:Glossaries\|{{PAGENAME}}]]
	</noinclude>		</noinclude>

Anw: Minor formatting changes.

2019-09-04T08:00:52Z

Minor formatting changes.

← Older revision		Revision as of 10:00, 4 September 2019
Line 39:		Line 39:
	\|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.		\|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.		\|DOT \|\| Delivery On Time - see OTIF.
	\|-		\|-
	\|Driver \|\| Comprising drivers and crew assigned to a trip.		\|Driver \|\| Comprising drivers and crew assigned to a trip.
Line 45:		Line 45:
	\|DU \|\| Distribution/Deliverable Unit - box, tray, cage, tet, etc.; Also Asset, Asset Type.		\|DU \|\| Distribution/Deliverable Unit - box, tray, cage, tet, etc.; Also Asset, Asset Type.
	\|-		\|-
	\|EDI \|\| Electronic Data Interchange – a mechanism by which 2 systems can communicate normally without user intervention.		\|EDI \|\| Electronic Data Interchange - a mechanism by which 2 systems can communicate normally without user intervention.
	\|-		\|-
	\|ERP \|\| Enterprise Resource Planning		\|ERP \|\| Enterprise Resource Planning

Anw: Minor correction

2019-07-01T10:13:29Z

Minor correction

← Older revision		Revision as of 12:13, 1 July 2019
Line 101:		Line 101:
	\|Trailer \|\| The trailer carrying the goods. Can be several types.		\|Trailer \|\| The trailer carrying the goods. Can be several types.
	\|-		\|-
	\|Transport \|\| ~~Moran Logistics Transport~~		\|Transport \|\| The transport management office.
	\|-		\|-
	\|Trip \|\| C-TMS: A selection of work to be completed, specifically a workload that lasts for an entire shift for a driver.		\|Trip \|\| C-TMS: A selection of work to be completed, specifically a workload that lasts for an entire shift for a driver.

Anw: Initial creation

2019-07-01T09:40:17Z

Initial creation

New page

{| class="wikitable" border="1"
|- bgcolor="silver"
!width="20%"|Term or Acronym !! Meaning
|-
|Ad Hoc Collection || Ad Hoc Collections are collections at a consignee or other point, where the actual items to be collected have not been defined, allowing for a free-form scanning of items.
|-
|AI || In barcode terms, an Application Identifier; some pre-defined characters in a barcode that define the data content rather than the format.
|-
|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.
|-
|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.
|-
|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 C-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 Centre || A part of an organization to which costs may be charged for accounting purposes. For C-TMS, this is used for accounting purposes, and also to generally configure the 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.)
|-
|Cross-Dock || Also a specific location at which product is exchanged.
|-
|C-TMS || ''CALIDUS'' TMS, OBS Logistics' Transport Management System.
|-
|Customer || In 3PL terms, the customer on behalf of which the transport is being operated.
|-
|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.
|-
|Debrief || Comprises 2 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.
|-
|Delivery Types || This defines the category of the order, and is intrinsically linked to revenue and cost tariffs.
|-
|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.
|-
|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 || Distribution/Deliverable Unit - box, tray, cage, tet, etc.; Also Asset, Asset Type.
|-
|EDI || Electronic Data Interchange – a mechanism by which 2 systems can communicate normally without user intervention.
|-
|ERP || Enterprise Resource Planning
|-
|Fixed Route || Provides a series of timed slots into which orders will fit.
|-
|Fixed Schedule || An order that occurs at a fixed time. Differing from the above, the order will be created in the schedule; Also Milk Run.
|-
|Item || A single item for delivery/collection.
|-
|Load || C-TMS: A trip that encompasses just a vehicle-full of items, or one journey out and back to a depot.
|-
|Location || In C-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.
|-
|MCS || Mobile Control System
|-
|OBD || On-Board Diagnostics - an automotive term referring to a vehicle's self-diagnostic and reporting capabilities. Also CANbus.
|-
|OMS Ref || A unique transport movement ID, referring to a single transport movement request.
|-
|OPS13 || Vehicle Checks; Defect Reporting
|-
|Optimisation || Route Building and Optimisation
|-
|Order || Equiv: OMS Ref; a transport movement.
|-
|Order Status || The lifecycle of an order
|-
|OTIF || On Time In Full - Metrics to measure successful collection or delivery.
|-
|Reason Codes || Of many types: Adjustment, Non-conformance, Order.
|-
|Region || Geographical Region. Also, Postal Region.
|-
|Resources || Drivers, Crew, Tractors, Vehicles, Trailers
|-
|Route || A route is a fixed route that is repeated. A Trip is a unique trip, which may be created from a route.
|-
|RPE || Roll-pallet Equivalent - This is used to estimate volume and therefore capacity of vehicles within C-TMS.
|-
|Schedule || A day's plan, usually consisting of 24 hours, not necessarily from midnight to midnight.
|-
|Service Levels; Service Types || Typically used to determine additional services for an order, or a quicker transport service.
|-
|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.
|-
|TLM || Transport Logistics Manager
|-
|Tractor || The driver cab, pulling the trailer.
|-
|Trailer || The trailer carrying the goods. Can be several types.
|-
|Transport || Moran Logistics Transport
|-
|Trip || C-TMS: A selection of work to be completed, specifically a workload that lasts for an entire shift for a driver.
|-
|Trip Status || The lifecycle of a trip
|-
|TTM || ''CALIDUS'' TTM; Track and Trace Module; OBS Logistics' application dedicated to tracking and tracing order events with inputs from several external systems.
|-
|WCS || Warehouse Control System
|-
|WMS || Warehouse Management System
|}

<noinclude>
[[Category:Templates|{{PAGENAME}}]]
</noinclude>

← Older revision		Revision as of 14:08, 28 April 2025
Line 9:		Line 9:
	\|Asset \|\| A traceable DU; the item that is tracked during delivery and collection. This Asset has a type (e.g. Cage, Tet, etc).		\|Asset \|\| A traceable DU; the item that is tracked during delivery and collection. This Asset has a type (e.g. Cage, Tet, etc).
	\|-		\|-
	\|Audit Log \|\|A log of events that have happened in the [[C-TMS]] 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.		\|Audit Log \|\|A log of events that have happened in the C-TMS 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.
	\|-		\|-
	\|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.		\|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.
Line 27:		Line 27:
	\|Cost Centre \|\| A part of an organization to which costs may be charged for accounting purposes. For C-TMS, this is used for accounting purposes, and also to generally configure the system.		\|Cost Centre \|\| A part of an organization to which costs may be charged for accounting purposes. For C-TMS, this is used for accounting purposes, and also to generally configure the 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.)		\|C-Portal \|\| ''CALIDUS'' Portal, Aptean's web-enabled external access system to the Calidus systems. Also, any electronic internet-based system designed to access functionality for a particular purpose (for example, customer enquiries, supplier activity, track and trace, etc.)
	\|-		\|-
	\|Cross-Dock \|\| Also a specific location at which product is exchanged.		\|Cross-Dock \|\| Also a specific location at which product is exchanged.
	\|-		\|-
	\|C-ePOD; EPOD\|\|Electronic Proof of Delivery. The ~~OBSL~~ EPOD system is ''CALIDUS'' ePOD.		\|C-ePOD; EPOD, APOD\|\|Electronic Proof of Delivery. The Aptean EPOD system is ''CALIDUS'' ePOD or Aptean POD.
	\|-		\|-
	\|C-TMS \|\| ''CALIDUS'' TMS, ~~OBS Logistics~~' Transport Management System.		\|C-TMS \|\| ''CALIDUS'' TMS, Aptean's Transport Management System.
	\|-		\|-
	\|CSB \|\|This refers to Carrier Self Billing, the process that [[C-TMS]] uses to produce and send invoices to carriers.		\|CSB \|\|This refers to Carrier Self Billing, the process that [[C-TMS]] uses to produce and send invoices to carriers.
Line 176:		Line 176:
	\|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).		\|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).
	\|-		\|-
	\|TTM \|\| ''CALIDUS'' TTM; Track and Trace Module; ~~OBS Logistics~~' application dedicated to tracking and tracing order events with inputs from several external systems.		\|TTM \|\| ''CALIDUS'' TTM; Track and Trace Module; Aptean's 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. In this implementation, the process of receipt and unloading is predominantly controlled by C-MCS (q.v.). See also Receiving.		\|Unloading \|\|The process of receiving and uploading items into a depot. In this implementation, the process of receipt and unloading is predominantly controlled by C-MCS (q.v.). See also Receiving.