Job List Sequence: Difference between revisions

From EPOD
m (Non-numeric values are not sequenced jobs)
m (Categorisation)
 
(One intermediate revision by the same user not shown)
Line 1: Line 1:
For collection and delivery jobs:
Collection and delivery jobs will be ordered by the ''CALIDUS'' ePOD mobile device application in site/load/planned start date and time sequence by default.  
Jobs will be ordered by the CALIDUS ePOD device in Site/Load/Planned Start Date and Time order by default.  


However, if sequences are passed through on jobs, these are used in preference i.e. Site/Load/Sequence/Planned Start Date and Time.
However, if sequences are present on jobs, these are used in preference i.e. site/load/sequence/planned start date and time.


The following rules apply:
The following rules apply to this process:
* Jobs with sequence 0, blank or non-numeric values are seen as un-sequenced jobs and will always appear in the list after sequenced jobs.
* Jobs with sequence 0, blank or non-numeric values are seen as un-sequenced jobs and will always appear in the list after sequenced jobs. The driver can complete these un-sequenced jobs at any time, regardless of any configuration or sequencing of other jobs in the job list.
* If re-sequence checks are turned on in C-ePOD, only jobs with a sequence (i.e. not null or 0) are checked. So, if a load consists of the following jobs:
* If re-sequence checks are turned on in C-ePOD, only jobs with a sequence (i.e. not null or 0) are checked. So, if a load consists of the following jobs:
** Job 1, no sequence, time 1200
** Job 1, no sequence, time 1200
Line 23: Line 22:
** Job 4, no sequence, time 1200
** Job 4, no sequence, time 1200
* When the user attempts to start a job out of sequence, and re-sequence checks are enabled, this will work as follows:
* When the user attempts to start a job out of sequence, and re-sequence checks are enabled, this will work as follows:
** Jobs 2, 5 and 6 cannot be completed before job 3.
** The driver can't complete jobs 2, 5 and 6 before job 3.
** Jobs 5 and 6 cannot be completed before job 2.
** The driver can't complete jobs 5 and 6 before job 2.
** When jobs 2 and 3 are complete, Jobs 5 and 6 may be completed in any order.
** When the driver completes jobs 2 and 3, they can complete jobs 5 and 6 in any order.
** Jobs 1, 4 and 7 are "wild cards", and may be completed at any time, before or after any other job is completed.
** Jobs 1, 4 and 7 are "wild cards", and the driver may complete these at any time, before or after any other job is completed.




[[Category:UG 291097 EPOD Advanced Guide|260]]
[[Category:UG 291097 EPOD Advanced Guide|260]]
[[Category:FAQ]]

Latest revision as of 12:07, 20 June 2025

Collection and delivery jobs will be ordered by the CALIDUS ePOD mobile device application in site/load/planned start date and time sequence by default.

However, if sequences are present on jobs, these are used in preference i.e. site/load/sequence/planned start date and time.

The following rules apply to this process:

  • Jobs with sequence 0, blank or non-numeric values are seen as un-sequenced jobs and will always appear in the list after sequenced jobs. The driver can complete these un-sequenced jobs at any time, regardless of any configuration or sequencing of other jobs in the job list.
  • If re-sequence checks are turned on in C-ePOD, only jobs with a sequence (i.e. not null or 0) are checked. So, if a load consists of the following jobs:
    • Job 1, no sequence, time 1200
    • Job 2, sequence 2, time 1100
    • Job 3, sequence 1, time 0900
    • Job 4, no sequence, time 1200
    • Job 5, sequence 3, time 1200
    • Job 6, sequence 3, time 0900
    • Job 7, no sequence, time 0900
  • They will be ordered on the list as follows:
    • Job 3, sequence 1, time 0900
    • Job 2, sequence 2, time 1100
    • Job 6, sequence 3, time 0900
    • Job 5, sequence 3, time 1200
    • Job 7, no sequence, time 0900
    • Job 1, no sequence, time 1200
    • Job 4, no sequence, time 1200
  • When the user attempts to start a job out of sequence, and re-sequence checks are enabled, this will work as follows:
    • The driver can't complete jobs 2, 5 and 6 before job 3.
    • The driver can't complete jobs 5 and 6 before job 2.
    • When the driver completes jobs 2 and 3, they can complete jobs 5 and 6 in any order.
    • Jobs 1, 4 and 7 are "wild cards", and the driver may complete these at any time, before or after any other job is completed.