Glossary - Revision history

Anw: Minor correction

2020-01-08T13:57:44Z

Minor correction

← Older revision		Revision as of 15:57, 8 January 2020
Line 15:		Line 15:
	\|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.		\|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 \|\|Also RPE (Regular Pallet Equivalent). A means of comparing ~~DU Type~~ size~~, for~~ example, a Standard ~~Roll~~ Pallet may equate to 1 BUE, a Large Board may equate to 2 BUEs. This is used to estimate volume and therefore capacity of vehicles within CTL-TMS.		\|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-ePOD \|\| ''CALIDUS'' EPOD, OBS Logistics' app-enabled trip execution system.

Anw: Minor correction

2020-01-06T08:21:37Z

Minor correction

← Older revision		Revision as of 10:21, 6 January 2020
Line 14:		Line 14:
	\|-		\|-
	\|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.		\|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 \|\|Also RPE (Regular Pallet Equivalent). A means of comparing DU Type size, for example, a Standard Roll Pallet may equate to 1 BUE, a Large Board may equate to 2 BUEs. This is used to estimate volume and therefore capacity of vehicles within CTL-TMS.
	\|-		\|-
	\|C-ePOD \|\| ''CALIDUS'' EPOD, OBS Logistics' app-enabled trip execution system.		\|C-ePOD \|\| ''CALIDUS'' EPOD, OBS Logistics' app-enabled trip execution system.
Line 138:		Line 140:
	\|-		\|-
	\|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.
	\|-
	\|RPE \|\|Regular Pallet Equivalent. A means of comparing DU Type size, for example, a Standard Roll Pallet may equate to 1 RPE, a Large Board may equate to 2 RPE’s. This is used to estimate volume and therefore capacity of vehicles within CTL-TMS.
	\|-		\|-
	\|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.		\|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.

Anw: Minor correction

2019-11-18T16:07:02Z

Minor correction

← Older revision		Revision as of 18:07, 18 November 2019
Line 150:		Line 150:
	\|-		\|-
	\|SKU \|\|Stock Keeping Unit – another term for a Case.		\|SKU \|\|Stock Keeping Unit – another term for a Case.
	\|-
	~~\|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 \|\|See Trip Stop.		\|Stop \|\|See Trip Stop.

Anw: Minor correction

2019-11-18T16:05:29Z

Minor correction

← Older revision		Revision as of 18:05, 18 November 2019
Line 45:		Line 45:
	\|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. The process of loading and despatching may be ~~predominantly~~ controlled by C-MCS (q.v.). See also Loading.		\|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.		\|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 131:		Line 131:
	\|Region \|\| Geographical Region. Also, Postal Region.		\|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.		\|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.		\|Resource \|\| General term grouping the executors of a trip. Carriers, Drivers, Crew, Tractors, Vehicles, Trailers.
Line 191:		Line 191:
	\|TTM \|\| ''CALIDUS'' Portal TTM; Track and Trace Module; OBS Logistics' application dedicated to tracking and tracing order events with inputs from several external systems.		\|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. ~~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. 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.		\|Unscheduled Order \|\|An Order that is yet to be scheduled onto a Trip by the scheduling process.

Anw: Updated CTL-TMS Glossary

2019-11-12T14:51:06Z

Updated CTL-TMS Glossary

Show changes

Anw: Minor formatting changes.

2019-10-22T10:44:35Z

Minor formatting changes.

← Older revision		Revision as of 12:44, 22 October 2019
Line 1:		Line 1:
	{\|		{\| class="wikitable" border="1"
			\|- bgcolor="silver"
			! Term !! Definition
			\|-
	\|Audit Log		\|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.		\|A log of events that have happened in the [[Overview\|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.
	\|-		\|-
	\|Booking		\|Booking
Line 10:		Line 13:
	\|-		\|-
	\|CTM		\|CTM
	\|This refers to the Carrier Trip ~~Managment~~ module within [[C-TL]].		\|This refers to the Carrier Trip Management module within [[Overview\|C-TL]].
	\|-		\|-
	\|DU		\|DU
Line 25:		Line 28:
	\|-		\|-
	\|ODBC		\|ODBC
	\|Open Database Connectivity – A method of communicating with an external database from a program outside of the database environment		\|Open Database Connectivity – A method of communicating with an external database from a program outside of the database environment.
	\|-		\|-
	\|Order		\|Order
Line 31:		Line 34:
	\|-		\|-
	\|Order Line		\|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)		\|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).
	\|-		\|-
	\|Payment		\|Payment
Line 37:		Line 40:
	\|-		\|-
	\|Plan		\|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’~~.		\|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		\|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.		\|The period after Orders have been scheduled in the Scheduling Program and then returned to [[Overview\|C-TL]]. Any subsequent manipulation of these Orders would be Post Schedule manipulation.
	\|-		\|-
	\|Pre Schedule		\|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.		\|The period before Orders have been scheduled in the Scheduling Program and then returned to [[Overview\|C-TL]]. Any manipulation of these Orders would be Pre Schedule manipulation.
	\|-		\|-
	\|Product Item		\|Product Item
	\|Another term for a case or SKU		\|Another term for a case or SKU.
	\|-		\|-
	\|Product Quantity		\|Product Quantity
Line 52:		Line 55:
	\|-		\|-
	\|Product Summary		\|Product Summary
	\|Another term for Booking		\|Another term for Booking.
	\|-		\|-
	\|Product Type		\|Product Type
	\|The category that a Product Item, Case or SKU falls in to, usually associated with temperature e.g. FROZEN, PERISHABLE, AMBIENT		\|The category that a Product Item, Case or SKU falls in to, usually associated with temperature e.g. FROZEN, PERISHABLE, AMBIENT.
	\|-		\|-
	\|Recalculate Distance and Times		\|Recalculate Distance and Times
	\|An [[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.		\|A [[Overview\|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.
	\|-		\|-
	\|Revenue		\|Revenue
Line 76:		Line 79:
	\|-		\|-
	\|SKU		\|SKU
	\|Stock Keeping Unit – another term for a Case		\|Stock Keeping Unit – another term for a Case.
	\|-		\|-
	\|Sourcing Unit		\|Sourcing Unit
Line 91:		Line 94:
	\|-		\|-
	\|Trip Stop		\|Trip Stop
	\|Stops within a trip at which specific activities would take place such as the loading or unloading of goods		\|Stops within a trip at which specific activities would take place such as the loading or unloading of goods.
	\|-		\|-
	\|Unscheduled Order		\|Unscheduled Order
Line 97:		Line 100:
	\|-		\|-
	\|Visual Basic		\|Visual Basic
	\|A fourth generation (4GL) programming language		\|A fourth generation (4GL) programming language.
	\|}		\|}

Dmurphy: update

2018-03-23T14:03:47Z

update

← Older revision		Revision as of 16:03, 23 March 2018
Line 8:		Line 8:
	\|Case		\|Case
	\|A Case of individual packets of a product e.g. a case of Cornflake packets.		\|A Case of individual packets of a product e.g. a case of Cornflake packets.
	\|-
	~~\|Crossdock~~
	~~\|Delivery from one location to another via another third location. This third location is known as the ‘Crossdock’ location.~~
	\|-		\|-
	\|CTM		\|CTM

Dmurphy at 10:29, 22 February 2017

2017-02-22T10:29:35Z

← Older revision		Revision as of 12:29, 22 February 2017
Line 9:		Line 9:
	\|A Case of individual packets of a product e.g. a case of Cornflake packets.		\|A Case of individual packets of a product e.g. a case of Cornflake packets.
	\|-		\|-
	\|[[Crossdock]]		\|Crossdock
	\|Delivery from one location to another via another third location. This third location is known as the ‘Crossdock’ location.		\|Delivery from one location to another via another third location. This third location is known as the ‘Crossdock’ location.
	\|-		\|-

Dmurphy at 09:17, 22 February 2017

2017-02-22T09:17:18Z

← Older revision		Revision as of 11:17, 22 February 2017
Line 1:		Line 1:
	{\|		{\|
	\|Audit Log		\|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.		\|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.
	\|-		\|-
	\|Booking		\|Booking
Line 11:		Line 11:
	\|[[Crossdock]]		\|[[Crossdock]]
	\|Delivery from one location to another via another third location. This third location is known as the ‘Crossdock’ location.		\|Delivery from one location to another via another third location. This third location is known as the ‘Crossdock’ location.
	\|-
	~~\|CSB~~
	~~\|This refers to Carrier Self Billing, the process that [[C-TMS]] uses to produce and send invoices to carriers.~~
	\|-		\|-
	\|CTM		\|CTM
	\|This refers to the Carrier Trip Managment module within [[C-~~TMS~~]].		\|This refers to the Carrier Trip Managment module within [[C-TL]].
	\|-		\|-
	\|DU		\|DU
Line 26:		Line 23:
	\|Fuel Surcharge		\|Fuel Surcharge
	\|An additional charge that may be applied to a Transport charge to reflect the increasing price of fuel.		\|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).
	\|-		\|-
	\|MSMQ		\|MSMQ
Line 49:		Line 43:
	\|-		\|-
	\|Post Schedule		\|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.		\|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		\|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.		\|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		\|Product Item
Line 67:		Line 61:
	\|-		\|-
	\|Recalculate Distance and Times		\|Recalculate Distance and Times
	\|An [[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.		\|An [[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.
	\|-		\|-
	\|Revenue		\|Revenue
Line 79:		Line 73:
	\|-		\|-
	\|Schedule		\|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-02 to 22:00 11-July-02.		\|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		\|Scheduled Order

Dmurphy: Created page with "{| |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..."

2017-02-22T09:06:31Z

Created page with "{| |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..."

New page

{|
|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.
|-
|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.
|-
|Case
|A Case of individual packets of a product e.g. a case of Cornflake packets.
|-
|[[Crossdock]]
|Delivery from one location to another via another third location. This third location is known as the ‘Crossdock’ location.
|-
|CSB
|This refers to Carrier Self Billing, the process that [[C-TMS]] uses to produce and send invoices to carriers.
|-
|CTM
|This refers to the Carrier Trip Managment module within [[C-TMS]].
|-
|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.
|-
|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).
|-
|MSMQ
|Microsoft Message Queue – a method of interfacing with another system using Microsoft based technology.
|-
|ODBC
|Open Database Connectivity – A method of communicating with an external database from a program outside of the database environment
|-
|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.
|-
|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)
|-
|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
|-
|Recalculate Distance and Times
|An [[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.
|-
|Revenue
|Monies received by a cost centre from a third party such as a customer.
|-
|RDC
|Regional Distribution Centre.
|-
|RPE
|Regular Pallet Equivalent. A means of comparing DU Type size, for example, a Standard Roll Pallet may equate to 1 RPE, a Large Board may equate to 2 RPE’s.
|-
|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-02 to 22:00 11-July-02.
|-
|Scheduled Order
|An Order that has been scheduled onto a Trip by the scheduling process.
|-
|SKU
|Stock Keeping Unit – another term for a Case
|-
|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.
|-
|TI
|Transport Instruction – another term for an Order.
|-
|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 Stop
|Stops within a trip at which specific activities would take place such as the loading or unloading of goods
|-
|Unscheduled Order
|An Order that is yet to be scheduled onto a Trip by the scheduling process.
|-
|Visual Basic
|A fourth generation (4GL) programming language
|}