Create Tasks

You can create tasks in NEXUS IC in several ways, depending on how the work is identified and planned.

Tasks can be created in the following ways:

  • Manually, from the Tasks tab on the PLANNING or WORKPACKS screen (see Create Tasks Manually).

  • By importing, using the Import function on the Tasks tab of the PLANNING or WORKPACKS screen (see Import).

  • Automatically, when a planning template is applied (see Planning Templates).

  • From an anomaly action, where a task is created to carry out remediation or follow up work.

    For example, a previous inspection may have identified a fault by recording an event and logging a finding, or NEXUS IC may have logged a finding when a data value was outside acceptable limits. An anomaly can then be raised to track the issue, followed by an anomaly action that defines the intended response. A task can be created and linked to that anomaly action so that the remediation work is carried out as part of a specific workpack.

  • As a continuation of an existing task, when work cannot be completed in a single session, for example due to time constraints or weather conditions. In this case, a continuation task can be created to capture the remaining work.

Prerequisites

Before creating a task, ensure that:

Create Tasks Manually

  1. On the PLANNING or WORKPACKS screen, go to the Tasks tab and choose Add.

  2. In the Add Task dialog, select the asset to which you want to assign the task and specify other parameters as required. Assigning a workpack and an event type is mandatory. For information about how to fill the fields in the dialog, see Add/Edit Task Dialog.

  3. Click OK to save the task.

    Result

    The task is created and displayed in the list of tasks on the Tasks tab.

Create Ad Hoc Tasks

You can create ad hoc tasks when you create or edit a regular task and select the Adhoc Task checkbox in the Add Task or Edit Task dialog (see Add/Edit Task Dialog). When you change a regular task to an ad hoc task, the available fields and screen options change.

In IC-Inspector, when an inspector selects an ad hoc task and fills out the form, the task will not vanish from their list — it will be available for them to complete again and again. You only need to create one ad hoc task of each type, as a single ad hoc task will be available on all assets. You should create that task on the highest-level relevant asset that has that event type available. Ad hoc tasks are suitable for events like “Damage”, where you want inspectors to be able to note any damage they see, even if it’s not part of the explicitly-tasked scope.