Due Tasks

Due tasks provides a view of the tasks that are forecast and when these are ready to be scheduled, a list will be displayed.

There are fields on the regular asset task that check whether all the required fields have been filled in. These checks performed on the regular asset task confirms that the task is configured correctly and consequently, that the regular asset task is ready for scheduling. If so, then a list of due tasks will appear. Once you see a task in the due tasks list, it means that the task is due and it doesn't have any failures.

The due tasks list is just a view for the user to see which tasks are due and when they are due. You cannot perform any actions on due tasks. However, you can add more data to the grid on the dashboard via the Properties Panel and the Query Builder.

Due tasks allows you to see a year plan of when all maintenance tasks are due so that planning can be done around this, such as ordering the appropriate spares and ensure there's enough resources available.

Due tasks are a list of tasks that are not yet on a proposed work order. So, if no due tasks are displayed, then you cannot generate a proposed work order.

System Options

The Due Tasks Future Range (Days) setting in the system options governs how far in the future you can see due tasks. You can specify the duration into the future that tasks will be predicted, which will be the value you define plus 30 days. By default, due tasks will be predicted for one year into the future plus 30 days.

If this value is updated, the changes will take some time to reflect in the due tasks list as all due tasks will need to be recalculated. However, when an update is made on a regular asset task which affects scheduling, then the change on the due task will be seen almost immediately because its a single task being changed and not the whole database.

Refer to Proposed Work Orders in the system options for more information.

Due Task Validity

A due task is created for a regular asset task, based on the Due Tasks Future Range (Days) setting in the system options and when Ready For Scheduling is set to true on the regular asset task.

There are specific conditions that cause reruns of due tasks to occur. When due tasks are rerun, all due tasks are removed and generated again. The following changes in the asset register trigger due tasks to be rerun:

  • when a user manually changes the Last Scheduled Date and Last Scheduled Reading on a regular asset task with a Scheduling Method of "Last Scheduled"
    • However, when these values are updated by the system, then a rerun of due tasks is not triggered.
  • when the Last Done Date and Last Done Reading changes on a regular asset task with a Scheduling Method of "Last Done"
    • This will always trigger a rerun of due tasks, irrespective of whether the values were updated manually or by the system.
  • when the meter changes
  • when the predictive meter reading changes
  • when the actual interval changes
  • when the Scheduling Method changes
  • when the asset calendar changes
  • when the asset calendar's working days or non-working days changes.

A due task that is "locked" because there is an open work order or proposed work order against it will not be deleted when a rerun is triggered.

Other conditions that trigger a rerun of due tasks are:

  • when the asset task suppression set-up changes
  • when a task changes from single scheduling to dual scheduling
  • when Ready For Scheduling changes to true.

When due tasks are run, the Estimated Next Due Date is updated on the regular asset task.