On-condition task definitions
To handle tasks that are necessary only under certain conditions, you can create a task definition and select the on-condition attribute. On-condition definitions are initialized manually, or if they have a task dependency and the dependency is fulfilled, they are initialized automatically.
Here's an example of an on-condition definition that's automatically initialized because of a task dependency with another definition: after a repair is completed, an on-condition, FOLLOW class requirement definition for an inspection is automatically initialized. The pre-requisite requirement definition for the repair has a Create New dependency to the following on-condition requirement definition.
The on-condition option can be selected for these types of task definitions: non-recurring blocks, requirements, and reference documents.
- Work that is optional or opportunistic; if there is time to perform additional work during a maintenance visit, the task definition can be initialized for the inventory undergoing maintenance.
- Work that becomes necessary only when specific events occur; for example, an inspection task that is necessary following a hard landing.
- Work that can or must be performed when a new inventory item is added to your Maintenix system. In an on-condition task definition, you select the Review on Receipt check box to indicate that the task definition should be reviewed whenever new inventory—to which the task definition relates —is added to your Maintenix system. Users can see the list of all review on receipt on-condition task definitions, assess whether any of them should be initialized for the new inventory item, and initialize those that are deemed necessary, on the Edit Inventory page, Step 4 - Edit task list for inventory.
If you cancel an active, one-time, non-recurring block task that was created from an on-condition block definition, the block's sub-tasks are also canceled.