IBM Support

Conditional Job Plans

Question & Answer


Question

Is it possible to enable conditional Job Plans?

Answer

Steps:
1. Go to the Organizations application.
2. Bring up an organization.
3. Go to the Select Action menu and select System Settings.
4. Select "Enable Job Plan Conditions check-box.


5. Attach a condition to a job task on a job plan:



NOTE:
– The conditions are only evaluated if the feature is turned on.
– When a job plan is applied to a work order each condition is evaluated:

• If the condition is true, it copies.
• If the condition is false, it does not copy.
– If a task is not copied to a Work Order, none of the Resources (Labor,Material, Tools and Services) for that task will copy to the Work Order either, even if their Condition is null or executes and returns true.
• If the task won’t be on the Work Order, the resources for it should not be there either.
– Resources for a Task can also have their own Conditions defined – A Task might copy to the Work Order, but that does not mean all of its resources must copy. Only the ones whose conditions are null or return true will be copied.
– Task #s will not change or act in any dynamic way. If there is a Task 10, 20 and 30, and Task 20 does not copy, you will end up with Task 10 and 30. (30 would not somehow change to 20).

Nested Job Plans will function as the used to
• If the Task that has the nested Job Plan does not copy, then that nested Job Plan will not copy.
– Duplicating and Creating Follow-Up work orders will not come into play as in both cases, job plans are not ‘re-applied’, so the conditions are not re-evaluated.
– Once the job plan is copied to a work order and its conditions have
been evaluated, no further evaluation of those conditions will occur.
– For instance:
• A job plan has a conditional task that only copies over to work orders of WORKTYPE=’EM’. You insert a work order and do not yet enter a Work Type. You apply the job plan. Because it is not an EM type work order, the task does not copy to the work order. If you change the worktype to EM now, NO CHANGES will be made to the work plan on that work order. That job plan task will NOT be copied over after the fact.

Conditional Job Plans with Flow Control
– Using Job Plan Conditions AND Flow Control at the same time on a
Job Plan can present ambiguous scenarios and ‘gaps’ in the flow
defined in the flow control. If Predecessor relationships are defined, but point to a Task that did not get copied to the work order a ‘gap in the flow’ might be created. It will be the responsibility of the person creating the Job Plan to make sure they design it in a way that any of those potential ‘gaps’ would be bridged.
– When a Task is NOT copied to a Work Order because of a Condition, it must be removed from any other tasks that are referencing it as a Predecessor (as well as the predecessor relationship – FF,FS, SF, SS).

[{"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":"PF033","label":"Windows"}],"Version":"7.5","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]

Historical Number

TPAEWORK;conditional job plan

Document Information

Modified date:
17 June 2018

UID

swg21644788