Automatic mode: Change plan by changing priority

According to the scheduling methodology being described in the The Automatic Scheduling Mode chapter, the two key parameters for changing the plan in the automatic mode are priority and capacity. 

So, if you need to change your plan, you should always try to do so by either changing the priority  (sequence number) of the job or by changing the capacity. Changing the priority should always be your first choice when it comes to optimizing your schedule.

Priority: Crucial role for the schedule

The priority of a task, specified by the sequence number, plays a crucial role in just plan it since it determines the order in which the jobs are worked off. The lower the sequence number, the higher the job's priority and the earlier this job gets the required resources, meaning that when e.g. Job 1 and Job 2 compete for the same resources, Job1 will get assigned these resources earlier because Job 1 has a higher priority. In our terms, Job 1 has a lower “sequence number” than Job 2.

Changing priority by changing the sequence number

Jobs that will be finished past their due date are indicated by a red exclamation mark in the left hand table, a red due date symbol and red task bars (of those tasks that finish past the job's due date).

The appropriate reaction would be to change the sequence number and give the late job a higher priority so that it gets resources assigned earlier. To do so, click the job number Job_No_6.png next to the job name in the Job view to open the "Set Sequence number dialog":


Since changing the priority will directly affect the operations of lower priority you can click Highlight_Changed_Tasks_Icon.png  in the "Essentials" tab of the menu ribbon to highlight the tasks affected by plan modifications in order to understand which orders had been pushed out to have the other job finished earlier.

Decision support via critical sequence number

The "Set Sequence Number" dialog offers a decision support functionality: The "Critical sequence number" provides decision support being aligned with the decision alert mentioned above.  

This decision support will be helpful in two cases

  • For late jobs: Efficiently increase priority to (just) finish in time
  • For ontime jobs: Efficiently decrease priority to (still just) finish in time

In the illustration above, job 6 has sequence number 6. The decision support in the form of the "critical sequence number" =  9, tells you that this is the highest possible sequence number (i.e. the lowest possible priority) at which the job will not be late. 

Changing priority by changing the job status

If you change the job status you have to be aware of the fact that in doing so you will also change the sequence number. Changing the status from quoted to released or ordered, will give a lower sequence number = higher priority to the job, changing, e.g., the job status from released to ordered or quoted will cause the sequence number to be increased, meaning the job gets a lower priority. The re-categorized orders will get the highest sequence number = lowest priority in their new category.

Tutorial video