Template:EPOD Glossary - Revision history

Anw: Minor correction

2019-03-13T17:46:18Z

Minor correction

← Older revision		Revision as of 19:46, 13 March 2019
Line 52:		Line 52:
	\|-		\|-
	\|Issue Life \|\|The time after which an item is no longer fit for purpose.		\|Issue Life \|\|The time after which an item is no longer fit for purpose.
	~~\|- bgcolor="silver"~~
	~~\|colspan="2"\|'''Product Related Definitions'''~~
	\|-		\|-
	\|Pack Size; Case Quantity \|\| A product may consist of a full quantity of items, inside a pack. The Pack Size (or Case Quantity) defines the amount of this product contained in a single pack. For example, if there are 85 items to deliver, with a pack size of 24, the number of full packs is determined to be 3 (24 * 3, or 72), with the remaining (13) being 'loose' quantity. This is displayed as "3/13" on the mobile application.		\|Pack Size; Case Quantity \|\| A product may consist of a full quantity of items, inside a pack. The Pack Size (or Case Quantity) defines the amount of this product contained in a single pack. For example, if there are 85 items to deliver, with a pack size of 24, the number of full packs is determined to be 3 (24 * 3, or 72), with the remaining (13) being 'loose' quantity. This is displayed as "3/13" on the mobile application.
Line 161:		Line 159:
	\|Geocode; Reverse Geocode\|\|Geocoding is the process of obtaining lat-longs from an address. Reverse Geocoding is the process obtaining an address from lat-longs.		\|Geocode; Reverse Geocode\|\|Geocoding is the process of obtaining lat-longs from an address. Reverse Geocoding is the process obtaining an address from lat-longs.
	\|-		\|-
	\|Geofence; Geofence Break\|\|A Geofence is a perimeter around a location. A Geofence Break occurs when a device passes through this perimeter on entry or ~~exist~~ from the location.		\|Geofence; Geofence Break\|\|A Geofence is a perimeter around a location. A Geofence Break occurs when a device passes through this perimeter on entry or exit from the location.
	\|}		\|}
	<!-- NEW PAGE -->		<!-- NEW PAGE -->

Anw: Minor formatting changes.

2019-03-13T10:57:59Z

Minor formatting changes.

← Older revision		Revision as of 12:57, 13 March 2019
Line 2:		Line 2:
	\|- bgcolor="silver"		\|- bgcolor="silver"
	!width="20%"\|Term or Acronym !! Meaning		!width="20%"\|Term or Acronym !! Meaning
	\|-		\|- bgcolor="silver"
	\|colspan="2"\|'''General Definitions'''		\|colspan="2"\|'''General Definitions'''
	\|-		\|-
Line 26:		Line 26:
	\|-		\|-
	\|Operator; Executor \|\|The Site (depot or carrier) that is executing the load or loads that are involved in the delivery of the items.		\|Operator; Executor \|\|The Site (depot or carrier) that is executing the load or loads that are involved in the delivery of the items.
	\|-		\|- bgcolor="silver"
	\|colspan="2"\|'''Item Related Definitions'''		\|colspan="2"\|'''Item Related Definitions'''
	\|-		\|-
Line 52:		Line 52:
	\|-		\|-
	\|Issue Life \|\|The time after which an item is no longer fit for purpose.		\|Issue Life \|\|The time after which an item is no longer fit for purpose.
	\|-		\|- bgcolor="silver"
	\|colspan="2"\|'''Product Related Definitions'''		\|colspan="2"\|'''Product Related Definitions'''
	\|-		\|-
Line 60:		Line 60:
	\|-		\|-
	\|Product Type \|\| A classification of the product being delivered. For example, a company may deliver 7 different mortar products and 80 different concrete slab products. The Product Types may be set to "MORTAR" and "SLABS". This may be used to attach additional configuration, changing the data required when collecting or delivering these product types.		\|Product Type \|\| A classification of the product being delivered. For example, a company may deliver 7 different mortar products and 80 different concrete slab products. The Product Types may be set to "MORTAR" and "SLABS". This may be used to attach additional configuration, changing the data required when collecting or delivering these product types.
	\|-		\|- bgcolor="silver"
	\|colspan="2"\|'''Status Definitions'''		\|colspan="2"\|'''Status Definitions'''
	\|-		\|-
Line 82:		Line 82:
	\|-		\|-
	\|Submitted \|\|An optional status that applies only to a 'Job' and which occurs after the 'Job' has been completed. This indicates that any time and expenses information recorded for the 'Job' has been submitted back to the server and can no longer be altered.		\|Submitted \|\|An optional status that applies only to a 'Job' and which occurs after the 'Job' has been completed. This indicates that any time and expenses information recorded for the 'Job' has been submitted back to the server and can no longer be altered.
	\|-		\|- bgcolor="silver"
	\|colspan="2"\|'''Action Definitions'''		\|colspan="2"\|'''Action Definitions'''
	\|-		\|-
Line 116:		Line 116:
	\|-		\|-
	\|Signature Capture \|\|Usually the final action of a job, where the customer's name and signature are entered.		\|Signature Capture \|\|Usually the final action of a job, where the customer's name and signature are entered.
	\|-		\|- bgcolor="silver"
	\|colspan="2"\|'''Other Definitions'''		\|colspan="2"\|'''Other Definitions'''
	\|-		\|-
Line 152:		Line 152:
	\|-		\|-
	\|Collection/Delivery Windows; Access Windows\|\|Periods of time between which it is acceptable to deliver or collect from that customer. This has limited use in the system, mostly for reporting purposes.		\|Collection/Delivery Windows; Access Windows\|\|Periods of time between which it is acceptable to deliver or collect from that customer. This has limited use in the system, mostly for reporting purposes.
	\|-		\|- bgcolor="silver"
	\|colspan="2"\|'''Location/Map Terms'''		\|colspan="2"\|'''Location/Map Terms'''
	\|-		\|-

Anw: Updated based on version 4.00.02.08

2019-03-13T10:32:56Z

Updated based on version 4.00.02.08

← Older revision		Revision as of 12:32, 13 March 2019
Line 52:		Line 52:
	\|-		\|-
	\|Issue Life \|\|The time after which an item is no longer fit for purpose.		\|Issue Life \|\|The time after which an item is no longer fit for purpose.
			\|-
			\|colspan="2"\|'''Product Related Definitions'''
			\|-
			\|Pack Size; Case Quantity \|\| A product may consist of a full quantity of items, inside a pack. The Pack Size (or Case Quantity) defines the amount of this product contained in a single pack. For example, if there are 85 items to deliver, with a pack size of 24, the number of full packs is determined to be 3 (24 * 3, or 72), with the remaining (13) being 'loose' quantity. This is displayed as "3/13" on the mobile application.
			\|-
			\|UOM; Item Type \|\| Unit of Measure; The major (case) UOM. This can optionally be displayed on the mobile device when changing product quantities.
			\|-
			\|Product Type \|\| A classification of the product being delivered. For example, a company may deliver 7 different mortar products and 80 different concrete slab products. The Product Types may be set to "MORTAR" and "SLABS". This may be used to attach additional configuration, changing the data required when collecting or delivering these product types.
	\|-		\|-
	\|colspan="2"\|'''Status Definitions'''		\|colspan="2"\|'''Status Definitions'''

Anw: Minor correction

2019-03-12T17:08:43Z

Minor correction

← Older revision		Revision as of 19:08, 12 March 2019
Line 153:		Line 153:
	\|Geocode; Reverse Geocode\|\|Geocoding is the process of obtaining lat-longs from an address. Reverse Geocoding is the process obtaining an address from lat-longs.		\|Geocode; Reverse Geocode\|\|Geocoding is the process of obtaining lat-longs from an address. Reverse Geocoding is the process obtaining an address from lat-longs.
	\|-		\|-
	\|Geofence; Geofence Break\|\|A Geofence is a perimeter around a location. A Geofence Break occurs when a device passes through this ~~perimiter~~ on entry or exist from the location.		\|Geofence; Geofence Break\|\|A Geofence is a perimeter around a location. A Geofence Break occurs when a device passes through this perimeter on entry or exist from the location.
	\|}		\|}
	<!-- NEW PAGE -->		<!-- NEW PAGE -->

Anw: Corrections to some Location/Map Terms

2019-03-12T17:05:33Z

Corrections to some Location/Map Terms

← Older revision		Revision as of 19:05, 12 March 2019
Line 147:		Line 147:
	\|colspan="2"\|'''Location/Map Terms'''		\|colspan="2"\|'''Location/Map Terms'''
	\|-		\|-
	\|Lat-Longs; GPS Co-ordinates\|\|Latitude and Longitude co-ordinates, specified together as a single entity, identifying the exact position of a location. There are multiple formats - ''CALIDUS'' ePOD uses decimal notation, for example "53.3490818,-2.8521498" identifies the OBS Logistics office building in Liverpool.		\|Lat-Longs; GPS Co-ordinates, GPS Position\|\|Latitude and Longitude co-ordinates, specified together as a single entity, identifying the exact position of a location. There are multiple formats - ''CALIDUS'' ePOD uses decimal notation, for example "53.3490818,-2.8521498" identifies the OBS Logistics office building in Liverpool.
	\|-		\|-
	\|GPS\|\|Global Positioning System; a satellite system ~~reporting lat-longs~~ to ~~help~~ with navigation and location positioning.		\|GPS\|\|Global Positioning System; the satellite system used to obtain a GPS position, for use with navigation and location positioning.
	\|-		\|-
	\|Geocode; Reverse Geocode\|\|Geocoding is the process of obtaining lat-longs from an address. Reverse Geocoding is the process obtaining an address from lat-longs.		\|Geocode; Reverse Geocode\|\|Geocoding is the process of obtaining lat-longs from an address. Reverse Geocoding is the process obtaining an address from lat-longs.

Anw: Updated for Geofence terminology

2019-03-12T17:02:34Z

Updated for Geofence terminology

← Older revision		Revision as of 19:02, 12 March 2019
Line 145:		Line 145:
	\|Collection/Delivery Windows; Access Windows\|\|Periods of time between which it is acceptable to deliver or collect from that customer. This has limited use in the system, mostly for reporting purposes.		\|Collection/Delivery Windows; Access Windows\|\|Periods of time between which it is acceptable to deliver or collect from that customer. This has limited use in the system, mostly for reporting purposes.
	\|-		\|-
	\|colspan="2"\|'''~~General~~ Terms'''		\|colspan="2"\|'''Location/Map Terms'''
	\|-		\|-
	\|Lat-Longs; GPS Co-ordinates\|\|Latitude and Longitude co-ordinates, specified together as a single entity, identifying the exact position of a location. There are multiple formats - ''CALIDUS'' ePOD uses decimal notation, for example "53.3490818,-2.8521498" identifies the OBS Logistics office building in Liverpool.		\|Lat-Longs; GPS Co-ordinates\|\|Latitude and Longitude co-ordinates, specified together as a single entity, identifying the exact position of a location. There are multiple formats - ''CALIDUS'' ePOD uses decimal notation, for example "53.3490818,-2.8521498" identifies the OBS Logistics office building in Liverpool.
Line 152:		Line 152:
	\|-		\|-
	\|Geocode; Reverse Geocode\|\|Geocoding is the process of obtaining lat-longs from an address. Reverse Geocoding is the process obtaining an address from lat-longs.		\|Geocode; Reverse Geocode\|\|Geocoding is the process of obtaining lat-longs from an address. Reverse Geocoding is the process obtaining an address from lat-longs.
			\|-
			\|Geofence; Geofence Break\|\|A Geofence is a perimeter around a location. A Geofence Break occurs when a device passes through this perimiter on entry or exist from the location.
	\|}		\|}
	<!-- NEW PAGE -->		<!-- NEW PAGE -->

Anw: Updated to latest version from OBS Hub

2019-01-08T09:40:23Z

Updated to latest version from OBS Hub

@@ Line 1: / Line 1: @@
-{| border="1"
+{| class="wikitable" border="1"
 |- bgcolor="silver"
 !width="20%"|Term or Acronym !! Meaning
@@ Line 134: / Line 134: @@
 |-
 |Unplanned Ad Hoc Collection ||A collection job that is created by the driver, usually after delivering to a customer.
 |-
 |Completion Report ||POD, POC, Service/Work Report.
 |}
 <!-- NEW PAGE -->

Anw: Updated Glossary

2017-11-29T08:50:13Z

Updated Glossary

← Older revision		Revision as of 10:50, 29 November 2017
Line 10:		Line 10:
	\|-		\|-
	\|Mobile Device; PDA \|\|The device used by the driver to perform the jobs. Typically an Android mobile device or tablet.		\|Mobile Device; PDA \|\|The device used by the driver to perform the jobs. Typically an Android mobile device or tablet.
			\|-
			\|Site \|\|The site usually defines the depot, business or the transport group (carrier). It can be set to any value required by the customer. All transactions data (for example, loads and jobs) and standing data (for example, vehicles and uses) belong to a site. An EPOD user, on a device or in the Admin screen, can only see data for one site at a time.
	\|-		\|-
	\|Load \|\|A single journey for the driver with a set of work attached. A load is identified by a unique load ID. This may also be referred to as a worklist or workload.		\|Load \|\|A single journey for the driver with a set of work attached. A load is identified by a unique load ID. This may also be referred to as a worklist or workload.
	\|-		\|-
	\|Job \|\|Also Consignment. A single task for the driver as a specific location. This could be the collection of goods or the delivery of goods. Jobs may also be Services (for example, servicing, installing or de-installing a boiler). A job is identified by a unique job ID but can also have other references held against the job (e.g. job code, SO number, customer reference and external reference).		\|Job \|\|Also Consignment. A single task for the driver as a specific location. This could be the collection of goods or the delivery of goods. Jobs may also be Services (for example, servicing, installing or de-installing a boiler). A job is identified by a unique job ID but can also have other references held against the job (e.g. job code, SO number, customer reference and external reference).
			\|-
			\|Job Group \|\|Jobs must be tagged with a Job Group. All jobs tagged with a single job group are processed in the same way. The job group has configuration associated to it to control such items as: POD/POC Report settings; Pre-Job actions (such as signing at a gatehouse); Post-Job actions (such as who signs for the item, are photos required); configurable fields required for entry for the jobs; Terms and Conditions displayed and; driver/user process (such as photos required for cancellation, comments/notes allowed). The job group can be used for any or all Sites, and the configuration against the job group can be different in each site. Job Groups can also be restricted from Admin and Remote users, so that certain users only see jobs for certain groups.
	\|-		\|-
	\|Container \|\|A generic term for any object that contains the items being collected or delivered. Examples of containers are: Pallet; Package; Carton; Item; Cage. A special container "Loose Products" - see Product below. A container is identified by a container ID which is unique to this physical container.		\|Container \|\|A generic term for any object that contains the items being collected or delivered. Examples of containers are: Pallet; Package; Carton; Item; Cage. A special container "Loose Products" - see Product below. A container is identified by a container ID which is unique to this physical container.
	\|-		\|-
	\|Product \|\|A product is any goods that are being collected or delivered where the product has a 'Product Code' which identifies what the product is but which does not uniquely identify each individual item. A product will also have a quantity associated with it to indicate how many items of this 'Product Code' are being collected or delivered. Products can either be processed within a 'Container' or as 'Loose Products' without a 'Container'.		\|Product \|\|A product is any goods that are being collected or delivered where the product has a 'Product Code' which identifies what the product is but which does not uniquely identify each individual item. A product will also have a quantity associated with it to indicate how many items of this 'Product Code' are being collected or delivered. Products can either be processed within a 'Container' or as 'Loose Products' without a 'Container'.
			\|-
			\|Owner \|\|The owner of the order that created the job. Typically this is the sales team that took the order and will be responsible for dealing with queries from the customer regarding the status.
			\|-
			\|Operator; Executor \|\|The Site (depot or carrier) that is executing the load or loads that are involved in the delivery of the items.
	\|-		\|-
	\|colspan="2"\|'''Item Related Definitions'''		\|colspan="2"\|'''Item Related Definitions'''
Line 129:		Line 137:
	\|Completion Report \|\|POD, POC, Service/Work Report.		\|Completion Report \|\|POD, POC, Service/Work Report.
	\|}		\|}
			<!-- NEW PAGE -->
	<noinclude>		<noinclude>
	[[Category:Templates\|{{PAGENAME}}]]		[[Category:Templates\|{{PAGENAME}}]]
	</noinclude>		</noinclude>

Anw: Fixed formatting issue.

2017-01-03T10:07:28Z

Fixed formatting issue.

← Older revision		Revision as of 12:07, 3 January 2017
Line 5:		Line 5:
	\|colspan="2"\|'''General Definitions'''		\|colspan="2"\|'''General Definitions'''
	\|-		\|-
	\|EPOD\|\|Electronic Proof of Delivery. The OBSL EPOD system is ''CALIDUS'' ~~EPOD~~. This also comprises the basis of the Service Completion system ''CALIDUS'' eServ.		\|EPOD\|\|Electronic Proof of Delivery. The OBSL EPOD system is ''CALIDUS'' ePOD. This also comprises the basis of the Service Completion system ''CALIDUS'' eServ.
	\|-		\|-
	Server: The portion of the ''CALIDUS'' ePOD/eServ systems that controls all the data and sends information to and receives updates from the mobile device.		\|Server \|\|The portion of the ''CALIDUS'' ePOD/eServ systems that controls all the data and sends information to and receives updates from the mobile device.
	\|-		\|-
	Mobile Device; PDA: The device used by the driver to perform the jobs. Typically an Android mobile device or tablet.		\|Mobile Device; PDA \|\|The device used by the driver to perform the jobs. Typically an Android mobile device or tablet.
	\|-		\|-
	\|Load \|\|A single journey for the driver with a set of work attached. A load is identified by a unique load ID. This may also be referred to as a worklist or workload.		\|Load \|\|A single journey for the driver with a set of work attached. A load is identified by a unique load ID. This may also be referred to as a worklist or workload.

Anw: Update for app version 3.3.2.X

2016-12-20T10:59:18Z

Update for app version 3.3.2.X

Show changes