FS 356513 Assigning Jobs to Users

From Calidus HUB
Revision as of 13:03, 9 May 2019 by Anw (talk | contribs) (Minor formatting changes.)





Aptean Logo.png







Rory J Holbrook

Assigning Jobs to Users

Functional Specification

8th May 2019 - 0.2
Reference: FS 356513















FUNCTIONAL OVERVIEW

Client Requirement

Requirements were gathered from Ben at RJ Holbrooks on 20th March 2019.

The customer requirements break down into the following areas:

  1. Being able to auto-create loads by assigning to drivers as jobs are created.
  2. In the case of creating bulk jobs, he doesn't usually want to assign them en masse to a single driver but split them across multiple drivers, in this instance.
  3. For job de-assignment, he wants to be able to quickly remove (de-assign) a job from a specific driver so that it is available to assign to another driver, in the same way above.
  4. Sequencing should work for him using the same (Job) screen.


Solution Overview

The Bulk Jobs creation process will be modified to show a list of all jobs created, with the facility to assign a driver to each job (through a drop-down list of users). If that driver does not have a load on that date, the load will be automatically created by the system. The user will be able to identify whether to assign the jobs in pairs or in bulk The process will automatically sequence the jobs on the load.


The system will be modified to identify loads by driver (user) and date, in the sequencing and assignment screens. So, the user will not have to select a load and drill-down from the loads screen, but instead will be able to use the sequencing and assignment screens directly from the menu (or on another tab in the browser).

When the screen is used like this, the user can select a date and select a driver from a drop-down list of users. The screen will then display any load found (as long as it is not completed). If one is not found, the screen will create a new one.

In this way, the user can quickly create loads and assign jobs without having to create them first. Sequencing will also be quicker.

Both screens will also be made available as links from the jobs screen, to aid in quickly accessing the processing.

The user will be able to quickly transfer jobs between users, by using the existing assignment screen, finding the first driver and date, selecting the jobs and de-assigning them, then finding the new driver's load and assigning them again.


Scope

The changes will be made in the latest versions of CALIDUS ePOD. The changes will be available only to v4.5 customers.

All screenshots in this document are intended to be representative of the final development. However, some changes may occur during development.


Impact

Existing customers will not be adversely affected by these changes, as it is intended that this functionality will be configurable in the system.


CONFIGURATION SET-UP

Pre-requisites

None.


Menu Structure

New menu options will be added to the Tasks menu in CALIDUS ePOD Admin console:

  • Job Assignment
  • Job Sequencing

Border

Figure 1: Main Menu


Data

In order to operate as described for Rory J Holbrook, the following new flags must be checked against the site:

  • Assignment After Creation.
  • Keep Linked Jobs Together.

Border

Figure 2: Site - Admin Tab


Implementation Advice

None.


FUNCTIONAL DESCRIPTION

The administrative user will adopt the following procedures. The system will be changed to allow the users to achieve this as described below.


Creating and Assigning Jobs to Drivers

The process for creating and assigning jobs will be:

  • The user will be in the existing Jobs screen.
  • They will click the Bulk Entry button.
  • They will enter the details of the jobs as they do now, and as described in FS 355304 RJH EPOD Bulk Job Entry.
  • When they click Save to create the jobs, the system will display a new Bulk Assign by User screen which will show a list of all jobs created, with the facility to:
    • Assign all jobs to one user.
    • Assign each job/pair of jobs to a user.
    • Assign any number of jobs/pairs of jobs to a user.
    • Re-assign jobs to another user.
  • The top bar of the new screen displays the following items:
    • A Back button for exiting the screen.
    • The date for the jobs created.
    • A drop-down list for selection of a driver to assign jobs to.
    • A drop-down list of loads for that driver.
    • An Assign button.
    • An Assign All button.
  • The user will select a user from the top bar, to indicate to whom they will be assigning jobs.
  • The screen displays jobs from the first (not yet complete) load matching that driver and date.
    • If there is a pending load, the screen will display this load.
    • If there is no pending load but there is an in-progress load, the screen will display this load.
    • If there are no incomplete loads, the screen will display "New Load".
    • Regardless, all loads for that day will be shown in a drop-down list, including "New Load", so that the user can see all loads for that user on that day, if there are many.
  • The user will select the load from the list for that user.
  • They will select jobs to assign to the user by clicking on the jobs in the table.
  • If jobs are linked by Job Code, when the user clicks a job, the linked job will also be selected. In other words, when selecting to assign jobs, both the collection and the delivery job will be automatically selected.
  • If for some reason, the user only wants one of the linked jobs assigned, clicking one of the selected linked jobs again will de-select only that job.
    • Any unassigned jobs that the user selects will be displayed in blue.
    • Any jobs already assigned jobs that the user selects will be displayed in red.
  • When the user has selected all jobs to assign to a load, they will confirm this with the Assign button.
  • The system will save the jobs onto the selected loads. If required, the system will create new loads for the drivers on that day. Any jobs that were already assigned to a load will be moved to the new driver's load.
  • The jobs that are assigned will display the user and load ID against them, and will be displayed in green.
  • To quickly assign all jobs to a single driver, the user can select the driver in the top bar, select the load, then click the Assign All button.
  • When the user has finished assigning jobs to drivers, they can return to the jobs screen using the Back button. The jobs are shown on the Jobs screen.


Border

Figure 3: New Bulk Assign by User screen, showing jobs created, having assigned 6 jobs, then selected 2 more (including 2 already assigned) to assign to another user on a new load.


Assigning Jobs to Drivers (after creation)

The user will assign jobs to drivers during the Bulk job creation process, as described above.

However, it may be required to change jobs assigned to drivers after creation.

The process for quickly assigning jobs to drivers will be:

  • The user will be in the existing Jobs screen.
  • They will click the Job Assignment button on the top of the screen, or run the screen from the Job Assignment option from the menu. The Job Assignment screen could also be open in another tab within the browser.
  • Because the user has not come to the Job Assignment screen from the Load screen, this will now allow the user to select which load is being worked on, through a series of parameters.
    • If not automatically creating loads, the screen will allow the user to select which load is being worked on through a drop-down list of load IDs.
    • If automatically creating loads (which is how the system will be set up for Rory J Holbrook), the screen will allow the user to select the driver (through a drop-down list) and select the date, which will default to the current date.
  • The user will select the driver and date and click Search.
  • The screen displays jobs from the first (not yet complete) load matching that driver and date.
    • If there is a pending load, the screen will display this load.
    • If there is no pending load but there is an in-progress load, the screen will display this load.
    • If there are no incomplete loads, the screen will display "New Load".
    • Regardless, all loads for that day will be shown in a drop-down list, including "New Load", so that the user can see all loads for that user on that day, if there are many.
  • The user then uses the screen to select and assign jobs to the load. This is described in FS 340547 PROD-75 Admin Job Assignment Improvements.
  • If jobs are linked by Job Code, when the user clicks a job to assign to a load, the linked job will also be selected. In other words, when selecting to assign jobs, both the collection and the delivery job will be automatically selected.
  • If for some reason, the user only wants one of the linked jobs assigned to the load, clicking one of the selected linked jobs again will de-select only that job.
  • When the user has selected all jobs to assign to a load, they will confirm this with the Save button.
  • If the user has selected to create a new load, the screen will create the load for the user. If a pre-existing load is selected, the jobs will be assigned to that load.
  • The user will be returned to the jobs screen.


Border

Figure 4: "Find Loads" panel, showing criteria and loads found. 2 jobs are selected to assign, and 2 to de-assign.


De-assigning Jobs from Drivers (error correction)

Again, in unexpected circumstances (driver illness, for example), jobs may need to be de-assigned from a driver.

The process for quickly de-assigning jobs will be:

  • The user will be in the existing Jobs screen.
  • They will click the Job Assignment button on the top of the screen, or run the screen from the Job Assignment option from the menu. The Job Assignment screen could also be open in another tab within the browser.
  • Because the user has not come to the Job Assignment screen from the Load screen, this will now allow the user to select which load is being worked on, through a series of parameters.
    • If not automatically creating loads, the screen will allow the user to select which load is being worked on through a drop-down list of load IDs.
    • If automatically creating loads (which is how the system will be set up for Rory J Holbrook), the screen will allow the user to select the driver (through a drop-down list) and select the date, which will default to the current date.
  • The user will select the driver and date and click Search.
  • The screen displays jobs from the first (not yet complete) load matching that driver and date.
    • If there is a pending load, the screen will display this load.
    • If there is no pending load but there is an in-progress load, the screen will display this load.
    • If there are no incomplete loads, the screen will display "New Load". Note Note: In this case, there will not be any jobs to de-assign, as there is not yet a load for that driver.
    • Regardless, all loads for that day will be shown in a drop-down list, so that the user can see all loads for that user on that day, if there are many.
  • The user then uses the screen to select and de-assign jobs from the load. This is described in FS 340547 PROD-75 Admin Job Assignment Improvements.
  • If jobs are linked by Job Code, when the user clicks a job to de-assign from a load, the linked job will also be selected. In other words, when selecting to de-assign jobs, both the collection and the delivery job will be automatically selected.
  • If for some reason, the user only wants one of the linked jobs de-assigned to the load, clicking one of the selected linked jobs again will de-select only that job.
  • When the user has selected all jobs to de-assign from the load, they will confirm this with the Save button.
  • The jobs will be de-assigned from that load.
  • The user will be returned to the jobs screen.


Transferring Jobs between Drivers

A more common error correction in the above case would be to transfer jobs from one driver's load to another driver.

The process for re-assigning jobs will be:

  • The user will be in the existing Jobs screen.
  • They will click the Job Assignment button on the top of the screen, or run the screen from the Job Assignment option from the menu. The Job Assignment screen could also be open in another tab within the browser.
  • Because the user has not come to the Job Assignment screen from the Load screen, this will now allow the user to select which load is being worked on, through a series of parameters.
    • If not automatically creating loads, the screen will allow the user to select which load is being worked on through a drop-down list of load IDs.
    • If automatically creating loads (which is how the system will be set up for Rory J Holbrook), the screen will allow the user to select the driver (through a drop-down list) and select the date, which will default to the current date.
  • The user will select the driver and date and click Search.
  • The screen displays jobs from the first (not yet complete) load matching that driver and date, or "New Load" if there are none, as described earlier.
  • The user then uses the screen to select and de-assign jobs from the load, as shown above.
  • When the user has selected all jobs to de-assign from the load, they will confirm this with the Save button.
  • The jobs will be de-assigned from that load.
  • The user will click Find Loads, select the new driver and date and click Search.
  • The screen displays jobs from the first (not yet complete) load matching that driver and date, or New Load if there are none, as described earlier.
  • The user then uses the screen to select and assign jobs to the load, as shown above.
  • When the user has selected all jobs to assign to a load, they will confirm this with the Save button.
  • If the user has selected to create a new load, the screen will create the load for the user. If a pre-existing load is selected, the jobs will be assigned to that load.
  • The user will be returned to the jobs screen.


Re-sequencing Jobs (after creation)

Part of the Bulk Job entry process will be to identify the jobs that are assigned to the same driver and sequence them automatically on the driver's load on that day. The system will be configured to do this in the most appropriate way for the operation.

For Rory J Holbrook, the process will sequence the jobs in pairs.

So, if there are 2 pairs of linked collection and delivery jobs created and assigned to the same user, they will have the same collection times and delivery times.

Normally, that would result in the jobs being sequenced as follows:

  • Collection of job 1.
  • Collection of job 2.
  • Delivery of job 1.
  • Delivery of job 2.

The system will be configured to sequence the jobs as follows:

  • Collection of job 1.
  • Delivery of job 1.
  • Collection of job 2.
  • Delivery of job 2.

Jobs will be sequenced by the earliest collection time, and the delivery job will be added directly after this job.


If the user needs to change the order of the jobs from this automatic sequence, they will use the existing Job Sequencing screen. However, to ease use of this screen, the jobs screen will have the Job Sequencing button added to the top of the screen. This will also be available from the main menu, and can be opened in a new browser tab.


The process for re-sequencing jobs will be:

  • The user will be in the existing Jobs screen.
  • They will click the Job Sequencing button on the top of the screen, or run the screen from the Job Sequencing option from the menu. The Job Sequencing screen could also be open in another tab within the browser.
  • Because the user has not come to the Job Sequencing screen from the Load screen, this will now allow the user to select which load is being worked on, through a series of parameters.
    • If not automatically creating loads, the screen will allow the user to select which load is being worked on through a drop-down list of load IDs.
    • If automatically creating loads (which is how the system will be set up for Rory J Holbrook), the screen will allow the user to select the driver (through a drop-down list) and select the date, which will default to the current date.
  • The user will select the driver and date and clicks Search.
  • The screen displays jobs from the first (not yet complete) load matching that driver and date.
    • If there is a pending load, the screen will display this load.
    • If there is no pending load but there is an in-progress load, the screen will display this load.
    • If there are no incomplete loads, the screen will display "No Load Found".
    • If some are found, all loads for that day will be shown in a drop-down list, so that the user can see all loads for that user on that day, if there are many.
  • The user then uses the screen to sequence or consolidate jobs on the load. This is described in FS 340547 PROD-75 Admin Job Assignment Improvements.
  • When the user has sequenced jobs on the load, they will confirm this with the Save button.
  • The user can to the jobs screen with the Back button.

Border

Figure 5: Job Sequencing screen with 3 pairs of jobs, in the sequence as created, with new load selection criteria.


TECHNICAL NOTES

Modules Changed

Module Name Module Type Notes
EPOD_JOB.cs C# file Site DAL object
{Date}_{Time}-4.5.0.7-356513_JobAssignChanges.sql Database Script Database and Data modification script.
Screens/JobAssign MVC Form Job Assignment screen.
Screens/JobSequencing MVC Form Job Sequencing screen.
job_details.aspx Web Form Job Details screen.


Table Updates

The following fields will be added to table EPOD_SITE:

Name Type Nullable Default Storage Comments
EPL_BULK_ASSIGN_IND smallint N 1    
EPL_BULK_LINKED_SEQ_IND smallint N 1    

Note Note:

  • A database modification script will be required to add the new fields.
  • Modifications will be required to the EPOD_SITE DAL object to use these new fields.
  • These fields will be added to all stored procedures in the database that require them.
  • These fields are not required on the device - the XML export will not include them.
  • These fields are not required to be contained within the Export.
  • These fields are not required to be used when filtering data for selection.


Developer Notes

Summary:

  • New configuration flags against the Site.
  • Change existing Job screen to work differently if automatically creating loads.
  • Add Assignment process to Bulk Job Entry.
  • Add ability to call Job Assignment and Job Sequencing screens from Jobs.
  • Add ability to select Load or (user + date) from Job Assignment screen.
  • Add ability to select Load or (user + date) from Job Sequencing screen.
  • Select pairs if jobs linked by job code. Deselect assigned jobs in pairs. Deselect jobs just selected is one by one.

Detail:

  • Change existing Job screen to work differently if automatically creating loads.
    • Filter just on User ID.
    • Assigning Load is now by selecting User. Screen checks user and planned start date (which must be entered). The job is then assigned to the load found on that date or the load is created.
    • Changing planned start date on job moves to new load/creates new load as required
  • Add Assignment process to Bulk Job Entry
    • Pop-up new panel after creating jobs.
    • Several checkboxes (defaulting) and drop-down lists as described.
  • Add ability to call Job Assignment and Job Sequencing screens from Jobs
    • Added to top tool bar
  • Job Assignment Screen changes:
    • Add ability to select Load or (user + date).
    • If jobs linked by job code, select pairs if jobs linked by job code.
    • If jobs linked by job code, deselect assigned jobs in pairs.
    • Deselect jobs just selected for assignment is always one by one.
    • Add Transfer button, to request driver to transfer to.
  • Job Sequencing Screen changes:
    • Add ability to select Load or (user + date).


Development

  • Additional configuration: 1.0d
  • Overall load assignment changes: 2.0d
  • Jobs screen - 2.0d
  • Job Assignment screen - 2.0d
  • Bulk Jobs assignment process - 3.5d

Total: 10.5d Ballpark: 22.0d


Admin Modifications

Menu

A data modification script will be required to add the following screens to the default menu under the Task (TSK) sub-menu, on any already-created menus. The screens will be sequenced to appear under jobs, with all existing Tasks menu items under that having their sequence incremented.

On table EPOD_ADM_MENU_OPTION:

AMO_MENU_TEXT AMO_CALLED_PROG AMO_OPTION_HELP
Job Assignment Screens/JobAssign/Index Find loads and assign jobs.
Job Sequencing Screens/JobSequencing/Index Find loads and sequence jobs.

On table EPOD_ADM_PROGRAM:

APR_DESCRIPTION APR_NAME APR_PROGRAM_TYPE
Job Assignment Screens/JobAssign/Index MVC
Job Sequencing Screens/JobSequencing/Index MVC

The icons used on the menu should match the prototype screens (and referenced in APR_IMAGE_FILENAME against the specific screen in EPOD_ADM_PROGRAM). For information, the following FontAwesome icons were used in the prototype:

  • Job assignment - fa-asterisk.
  • Job sequencing - fa-sort-numeric-asc.


Jobs

Job Assignment

Job Sequencing

Warning Warning: Bug Fixes:


TEST PLAN

Test Script / Scenario ReferenceAssigning Jobs to UsersCall Number(s): 356513
Test Script / Scenario DescriptionTesting ...PASS / ISSUES / FAIL
Menu AccessTasks/Jobs, Job Sequencing & Job Assignment 
Pre-requisites Tested By:
 
Test ObjectiveTo test that: ...Date:
 


Step Action Result Remarks P/F
1        
         
1.01    
1.02    
1.03    


APPENDIX A: QUOTE & DOCUMENT HISTORY

Cost Details
Activity Estimate
No. of Days		 No. of Days Rate per Day (£) Cost (£ Exc. VAT)
Requirements 0.00 0.00 850 £0.00
Change Request Evaluation 0.50 0.50 850 £425.00
Functional Specification 3.25 3.25 850 £2,762.50
Technical Specification 0.00 0.00 850 £0.00
Development 14.00 14.00 850 £11,900.00
Testing and Release 3.25 3.25 850 £2,762.50
Implementation 0.00 0.00 850 £0.00
Project Management 1.00 1.00 850 £850.00
 
TOTAL 22.00 22.00   £18,700.00
Estimate excludes training, release to live and go live support.

References

Ref NoDocument Title & IDVersionDate
1FS 355526 Rory Holbrook POD Notes0.205/03/2019
2FS 355304 RJH EPOD Bulk Job Entry1.030/01/2019
3FS 356080 Add Parameters for Additional Data0.407/03/2019
4FS 340547 PROD-75 Admin Job Assignment Improvements0.224/01/2017


Glossary

Term or Acronym Meaning
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.
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.
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.
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.
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.
Item Related Definitions
Job Code A reference associated with a job or job(s). This reference is common to connected jobs, for example this would be the same on both the collection of goods and the associated delivery of the same goods. Typically this would be the transport unique reference.
SO Number A reference associated with a job which indicates the "Sales Order Number" this job is associated with.
Customer Reference A reference associated with a job which has been provided by and will be recognised by the customer.
External Reference A reference associated with a job which does not match any of the existing references, usually because it has been provided by an external system.
Pallet An alternative for 'Container'. The term pallet is used when the operation only uses portable platforms as the container for goods.
Package An alternative for 'Container'. The term package is used when the operation only uses boxes or wrapping as containers for goods.
Package Code A code representing the type of 'Container'.
Package Desc A description of the type of 'Container'.
Product Code A code which identifies what a product is.
Item A generic term for any individual item that can be collected or delivered. An item can represent a 'Container' or a 'Product'. This can also be used as an alternative for 'Container' when the operation only treats the goods as individual items, i.e. not as identifiable products.
Service Item An item which will be serviced by a service job. See action 'Service'.
Issue Life The time after which an item is no longer fit for purpose.
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.
Status Definitions
Status An indicator of how far through the processing a 'Job', 'Container' or 'Product' has progressed.
Pending A status indicating that the processing has not yet started, but is required to be completed.
In Progress A status indicating that processing has started but not yet finished.
Complete A status indicating that the 'Job', 'Container' or 'Product' has been collected or delivered.
Complete (Amended) A status indicating that the 'Job', 'Container' or 'Product' has been collected or delivered but that some changes or amendments have been made. This means that not everything that was planned to be collected or delivered was collected or delivered, some items may have been cancelled or some products may only have had some of the planned quantities collected or delivered.
Complete (Claused) A status indicating that the processing has been finished but that a 'Clause' condition has been recorded for this item.
Claused See 'Complete (Claused)' and action 'Clause'.
Cancelled A status indicating that the processing of this item or job is no longer required.
Cancelled at Collection A status indicating that the delivery of a container or product is no longer required because the associated collection of this container or product was cancelled.
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.
Action Definitions
Start An action associated with a 'Job' meaning the driver is about to start the processing of this job or jobs. This action will mark the job(s) with a status of 'In Progress'.
Arrive A conditional action associated with a 'Job' meaning the driver has arrived at the location the goods should be collected from or delivered to.
Continue An action associated with a 'Job' meaning the driver has previously performed the 'Start' and/or 'Arrive' action and has exited the processing screen but is now going to continue the processing.
Collect An action associated with a specific 'Container' or a 'Product' meaning the driver has collected the 'Container' or 'Product'. This action will mark the 'Container' or 'Product' with a status of 'Complete' or 'Complete (Amended)'.
Collect Claused An action associated with a specific 'Container' or a 'Product' meaning the driver has collected the 'Container' or 'Product' but with a condition under which the collection was accepted. This action will accept the clause condition and then mark the 'Container' or 'Product' with a status of 'Complete (Claused)'.
Deliver An action associated with a specific 'Container' or a 'Product' meaning the driver has delivered the 'Container' or 'Product'. This action will mark the 'Container' or 'Product' with a status of 'Complete' or 'Complete (Amended)'.
Deliver Claused An action associated with a specific 'Container' or a 'Product' meaning the driver has delivered the 'Container' or 'Product' but with a condition under which the delivery was accepted. This action will accept the clause condition and then mark the 'Container' or 'Product' with a status of 'Complete (Claused)'.
Clause An action associated with a specific 'Container' or a 'Product' that has already been collected or delivered meaning the collection or delivery has been accepted with a condition. This action will accept the clause condition and then mark the 'Container' or 'Product' with a status of 'Complete (Claused)'.
Cancel An action associated with a 'Job', 'Container' or 'Product' meaning the collection or delivery will not be performed for this 'Job', 'Container' or 'Product'.
Submit An optional action which can conditionally be carried out after a 'Job' has been collection or delivered meaning that any/all required expense or time recording for this 'Job' has been completed and can be submitted back to the server.
Service A service of a service item or items. Typically, Installation, Deinstallation or Service. The process of a service usually encompasses Pre- and Port-work checks, information gathering and diagnosis and resolution notes. Additional references (MC Refs) may also be captured.
Actioned A general term describing completing a job. So, 'Actioned' may be used instead of 'Collected', 'Serviced', 'Delivered'.
Consolidate The action of taking several jobs and linking them together, so they are actioned at the same time with one start, arrive and signature.
Deconsolidate The action of taking a consolidation of jobs and breaking them down into the component jobs again.
Job Swap The action of selecting an existing load not assigned to the user, and picking jobs to transfer onto the user's load.
Signature Capture Usually the final action of a job, where the customer's name and signature are entered.
Other Definitions
Reason Code A code which represents the reason that a job was cancelled or an item was cancelled or claused.
Vehicle The vehicle used for transporting the goods.
Vehicle Checks Also Defect Checks. A series of questions representing the results of checks intended to ensure the vehicle is in an acceptable condition.
Metrics Entry A series of questions to capture information either at the start or end of a 'Load'.
Driver The person performing the collections or deliveries; the user of the device/application.
Engineer The person performing the services; the user of the device/application.
Customer The person/company the goods are being collected from or delivered to.
Signatory The name of the person providing a signature.
T&Cs Terms and Conditions. The T&Cs are shown when signatures are prompted for. The text of the T&Cs are defined in the system itself.
Transfer Load A load select from which to swap jobs to the user's load.
Base E.g. 'Return to Base'. Typically the depot from which the driver departed.
Unplanned Ad Hoc Collection A collection job that is created by the driver, usually after delivering to a customer.
Ad Hoc Container Entry/Scanning The process of adding containers (items) to a job that have not been pre-advised on the job.
Completion Report POD, POC, Service/Work Report.
Load Assignment The action of assigning a vehicle and/or a driver to a load.
Job Assignment The action of putting jobs onto a load.
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.
Location/Map Terms
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; 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.
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.


Authorised By


Murray Middleton
OBS Project Manager
_____________________________

Ben Williams
Rory J Holbrook Transport Manager
_____________________________
Retrieved from ‘https://calidusassist.adcservices.apteancloud.com/calidus-assist/OBS/index.php?title=FS_356513_Assigning_Jobs_to_Users&oldid=7360’