Tasks

Tasks are work to be done. Often (but not always) this is inspection work. Typically you will specify an asset that the task is to be done on, and an event type specifying the type of work to be done. For example if the task is to carry out a GVI of the asset, you would specify event type ‘GVI’. Tasks can be created by using the Add button, or by importing, or can be raised as a result of an anomaly action: in a previous inspection you might have noted some fault by logging an event and logging a finding on that event, or NEXUS might have noticed that a data value was outside acceptable bounds and log a finding for you. You might then create an anomaly to track that problem, then create an anomaly action as your intended solution to the problem, and on that anomaly action you might then create a task, so that the remediation gets carried out as part of a particular workpack. Tasks can also created as a continuation of an existing task: if you get partway through a task and are then forced to stop (by end of day, by weather, etc.), you may log a continuation task for the remainder of the work.

Properties of a Task

1. Asset - where the task is to be completed.
2. Start KP/EL / End KP/EL - defines the starting and ending kilometre point or elevation of a task (if required).
3. Workpack / Schedule - You must specify either a workpack or a schedule to contain your task. If a Workpack is chosen, the Schedule option will disappear, and vice versa.
4. Event Type - the type of Event which is to occur to complete this task (can be null).
5. Category - You may optionally create task categories to further group your tasks (tasks that require rope access, tasks that should only be undertaken on days ending in a ‘y’, etc).
6. Assigned To - you may optionally assign particular tasks to particular personnel.
7. Requires Shutdown - In plant inspection, some work requires the asset to be shut down — for example, inspecting the interior of a vessel. Check this box for such tasks.
8. Order - Order in which the task is to be completed (for information purposes only). For example, if an asset should be cleaned and then GVI’ed, give the Cleaning task a lower order number than the GVI task. Repeated numbers are OK.
9. Approx Timing - This will be used to estimate the overall duration (and optionally, cost) of workpacks.
10. Instructions - any descriptive text relating to this task which may assist the inspector. If you find you are using the same instruction for every event of this type, you should instead put those instructions on the Event Type. (It is similarly possible to put instructions on a planning template.)
11. Task Origin - 150 characters.
12. Anomaly Action - If this task was created from an anomaly action, it is shown here.
13. Planning Template - If this task was created from a planning template, it is shown here.
14. Event - If an event has been used to complete this task, it is shown here.
15. Task Status - You may optionally create task statuses to classify your tasks.
16. Is Completed - True if an event has been used to complete this task.
17. Retasked - True if another task references this task (i.e. is linked to this task).
18. Is Deferred - True if Is Completed is true and Is Retasked is true.

If the task has instructions (from any of event type instructions, planning template instructions or instructions on the specific task), those instructions will be shown in a pane on the right.

Tasks Toolbar

• Add

  Add a task.

• Edit

  Edit the selected task(s).

• Delete

  Delete the selected task(s).

• Import

  See Import for full description of the Import menu item.

• Export

  See Export for full description of the Export menu item.

• Customise

  See Customise for full description of the Customise menu item.

• Connections

  See Connections for information about the Connections toolbar option.

• Task Instructions

  Show/hide the Task Instructions pane. Task instructions can come from the task’s Event Type, and/or from its planning template, and/or from the task itself.