You apply conditions to job plans to specify that work can begin only when certain conditions are satisfied.
Job plan conditions automate the creation of new work items on a work order and improve the flow of work in your organization. Conditions can be applied to job plan components and to any corresponding resources. The job plan component can be a task, labor, materials, services, or tools.
You can require that conditions are met for the job plan component and also for the resources that are linked to it. When the conditions that you specify for job plans are met, the component of the job plan is copied to the designated work order.
The conditions that you create for job plans can be designed to suit the needs of your site or organization. You create conditions in the Conditional Expression Manager application.
Job plan conditions that are not met can have an impact on process flow control. You must define predecessor relationships correctly to avoid a break in the process flow.
Predecessor relationships ensure that the sequential flow of a work order is not disrupted when job plan conditions are not met. If predecessor relationships are defined, but they control a task that is not copied to the work order, a break in the process flow can occur. If a condition is not met, the job plan task cannot be copied to the designated work order. As a result, any tasks that reference the job plan task as a predecessor are also affected.
Job plan task | Predecessor task and relationship | Condition | Work order task | Predecessor task and relationship | Condition |
---|---|---|---|---|---|
10 | Null value | Null value | 10 | Null value | Null value |
20 | 10; Finish-to-start | Null value | 20 | 10; Finish-to-start | Null value |
30 | 20; Start-to-start | Condition is defined: Can be true or false. | Null value | Null value | Null value |
40 | 30; Finish-to-start | Null value | 40 | Null value | Null value |
Because the job plan condition that was defined for task 30 proved false, the sequence of tasks is broken. As a result, task 40 is lacking a predecessor relationship, so the status is set to In Progress (INPRG) at the same time as task 10.
Job plan task | Predecessor task and relationship | Condition | Work order task | Predecessor task and relationship | Condition |
---|---|---|---|---|---|
10 | Null value | Null value | 10 | Null value | Null value |
20 | 10; Finish-to-start | Null value | 20 | 10; Finish-to-start | Null value |
30 | 20; Start-to-start | Condition is defined: Can be true or false. | Null value | Null value | Null value |
40 | 20; Start-to-start*; 30; Finish-to-start | Null value | 40 | 20; Start-to-start | Null value |
The condition that was defined for task 30 proved false, so the task and the predecessor value were not copied to the work order. However, by defining task 20 as an alternative predecessor to task 40, the sequential flow of the job plan scenario is uninterrupted.