IBM Support

Job plan conditions

News


Abstract

New Job plan conditions functionality in Maximo 7.5

Content

Applying 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.

Example

A maintenance staff member identifies a leaking pump and creates a work order to fix the leak. The staff member specifies the details of the planned work order and applies a job plan. The job plan components have conditions that dictate how the work is to be carried out:

The correct type of seal must be used to fix the leak.


The condition specifies that the seal must be suitable for outdoor use. The job plan identifies two seals in planned material that have specific conditions about their suitability for outdoor or indoor use. The job plan condition requires that if the broken pump is located inside, seal A must be used. If the broken pump is located outside, seal B must be used.

The correct set of tools must be used.


The condition specifies that a specific set of tools must be used to perform the work task. The job plan identifies two sets of tools that can be used to repair pumps. The job plan condition dictates that if the broken pump is model number 123, tool set A must be used. If the pump is model number 456, tool set B must be used.

An additional safety check must be performed.


The condition specifies that an additional safety check task is performed when the job is complete. The job plan condition dictates that if the equipment is in circulation for more than two years, the pump requires an additional safety check.
The conditions are designed to create rules around the work that is performed. If any of the conditions are not met, the job plan component that the condition applies to is not copied to the work order. Only when the conditions are met for the job plan components, can the work be completed.

Job plan conditions and process flow control

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.


Example

A job plan scenario that does not have predecessor relationships correctly defined can cause a gap in the process flow.


In the following job plan scenario, the condition that is defined for task 30 might prove false. If the condition proves false, task 30 is not copied to the work order and task 40 no longer refers to task 30 as a predecessor. This outcome is not wanted for the job plan.



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.

A job plan scenario that has predecessor relationships correctly defined can bridge potential gaps in the process flow.


In the following job plan scenario, the condition that is defined for task 30 can still prove false. However, tasks 20 and 30 are defined as predecessors for task 40, so the potential gap in the process flow can be bridged.


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.

[{"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Component":"Job Plans","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF010","label":"HP-UX"},{"code":"PF016","label":"Linux"},{"code":"PF027","label":"Solaris"},{"code":"PF033","label":"Windows"}],"Version":"7.5","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Document Information

Modified date:
17 June 2018

UID

swg21622579