Add/Edit Planning Task Dialog
The Add Planning Task and Edit Planning Task dialogs allow you to define the properties of a planning task and manage its related data.
See below for the description of fields in the Add Planning Task/Edit Planning Task dialogs.
Field/Checkbox Name |
Description |
|---|---|
Planning Template |
Specifies the planning template that contains this planning task. |
Asset |
Specifies the asset on which the task is to be performed. Select an asset from the hierarchy. You must specify either an asset or an asset type. |
Asset Type |
Use this option if the task applies to a group of assets of a specific type rather than to a single asset. Click the ellipsis button to select an asset type. |
Ad Hoc Task |
If selected, tasks generated from this planning task are flagged as ad hoc tasks. |
Start KP/EL / End KP/EL |
Defines the start and end kilometre point (KP) or elevation location where the task is to be performed. These fields are optional. |
Event Type |
Specifies the type of event or sensor reading to be scheduled. You may select from any preconfigured event types (see Configure Event Types) or sensor types (see Configure Sensors). The selected type determines which specific event form or sensor data form must be launched to complete the resulting task. This field is mandatory. |
Schedule Type |
Optional field used for grouping or categorising planning tasks. |
Category |
Optional task category used to further group tasks (for example, tasks that require rope access, tasks that should only be undertaken on days ending in a ‘y’, etc.). |
Reference Number |
Company-specific reference number for the planning task. When the planning template is applied and a task is created, this reference number is inherited by the task. |
Requires Shutdown (Manual) |
Indicates whether the asset requires shutdown before the task can be completed. |
Requires Shutdown (Lookup) |
Select a Yes / No AIG field that provides the shutdown requirement for this task. |
Approx Timing (Manual) |
Estimated time required to complete the task. This value is used to estimate the overall duration and, optionally, the cost of workpacks. |
Approx Timing (Lookup) |
Select a Numeric AIG field that contains the estimated time to complete this task. |
Order Number |
Specifies the order in which tasks are intended to be completed (for information purposes only). For example, if an asset must be cleaned before GVI, assign the Cleaning task a lower order number than the GVI task. Repeated values are allowed. The Order Number also determines the order in which tasks appear in the inspector’s list in IC-Inspector (see Tasks Screen). |
Instructions (Manual) |
Enter task-specific instructions. These instructions can be included in workpack reports to guide inspection engineers. |
Instructions (Lookup) |
Select the AIG field that contains instructions for this task. |
Start (Manual) |
Specifies the first occurrence (or workpack) at which the task is created. This can be a numeric value representing the first occurrence, or a date value (such as “last inspected date”). If a date value is used, the Update/Apply process calculates the corresponding occurrence based on that date. |
Repeat (Manual) |
Enter a value that defines the frequency that the task is to be created. This can be either a numeric value (which will be considered a frequency), or a date value (such as “next inspection date”). For example, if you enter 3 in this field, a task will be created at every third occurrence. If a date is used, the Update/Apply process will calculate the occurrence based on the date. |
Start (Lookup) |
Choose the AIG field that defines the first occurrence (or workpack) to create this task. This can either be a numeric value that specifies the first occurrence, or a date value (such as “last inspected date”). If a date-type field is used, it automatically populates the Due Date field for planning tasks generated by this template. |
Repeat (Lookup) |
Select the AIG field that defines how often the task is created. This can be a numeric field representing a frequency or a date-type field (such as “next inspection date”). The Update/Apply process calculates the occurrence based on the date. |
Create Action |
Determines when exactly a task is created. Choose from the following options:
|
Anomaly Action |
If this planning task is related to a specific anomaly action, click the ellipsis button and choose the relevant anomaly action from the list. |
Details |
Reference or source information for the planning task, for example a risk-based assessment or a company procedure number. |
See Checking History.
See also