Maximo Open Forum

HI All,
I have a need to be able to add tasks from multiple Job Plans to a Work Order Plan Task Lines.  I know how the Nested Job Plan function works, but that creates a separate work order for each Job Plan.  In this scenario the client has many Job Plans pre configured for all types work.  They want to use these Job Plans to feed the Work Order Plan tasks.  Using Job Plans saves many hours of repetitive line entry.  These are not coming from PM's, it's general assigned work.  

My original thought is to add a button on the Work Order Plan tab, that will execute an Automation Script for them to select  or enter Job Plans and the script will enter the task lines to the Work Order as if they were manually entered in.  Unless someone out there has a better idea?  Perhaps a way to make the Job Plan field NOT read Only after adding a Job Plan??

Thanks
#WorkManagement

------------------------------
Brian Swanson
Herman Miller
------------------------------

I like nested job plans but I can understand why they don't want to see child work orders for them. I'm assuming these generic tasks need to be completed before any of the actual work is started? For example, to review the hazards/precautions, verify they're qualified to perform the work, that the necessary permits exist, etc. Is there anything from the generic job plan we'd use beside the tasks? I am also assuming these generic job plans would not have resource requirements (materials, labor, tools, etc.) defined on the job plan nor would those resources need to be captured on execution of the work so I'm thinking the use case might just be tasks. 

If you write something custom to bring these in as work order tasks and want to use traditional job plans as well, you're going to have to write the logic to handle taskid to avoid conflicts. For example, let's say they have 10 tasks for generic job plan 1 and the actual job plan 2 starts with a taskid of 10. Even if the generic job plan incremented the taskid by 1 instead of 10 you would have a conflict on task 10. Because you can't apply a job plan when tasks exist, you'd have to apply the functional job plan first and then add in your tasks after & renumber where needed. It's technically doable, but if you're not needing capabilities like tracking resources on them it seems counter-productive to me. And potentially adds a lot of data to the WORKORDER table to store it. 

I've seen customers use a variety of mechanisms for tracking this sort of stuff. For example, some customers are using Inspections for tracking a checklist before a user can start the work. Others have built custom objects for having the user sign off on before starting work. It really all depends on their use case what makes the most sense.

------------------------------
Steven Shull
IBM
------------------------------

HI Steven,
You are correct.  When they built the job plans they took the task ID into count, so first Job Plan 1 initial setup and eval are steps incremented by 5 starting at 1000, then job plan 2 work perform is like 2000 series and completion job plan 3 is 4000 series, but I do need to build in something to ensure that they do not conflict.   Thanks for the info..

------------------------------
Brian Swanson
Herman Miller
------------------------------

Original Message:
Sent: 11-11-2022 08:54
From: Steven Shull
Subject: Add tasks from multiple Job Plans to a Work Order Plan tasks

I like nested job plans but I can understand why they don't want to see child work orders for them. I'm assuming these generic tasks need to be completed before any of the actual work is started? For example, to review the hazards/precautions, verify they're qualified to perform the work, that the necessary permits exist, etc. Is there anything from the generic job plan we'd use beside the tasks? I am also assuming these generic job plans would not have resource requirements (materials, labor, tools, etc.) defined on the job plan nor would those resources need to be captured on execution of the work so I'm thinking the use case might just be tasks. 

If you write something custom to bring these in as work order tasks and want to use traditional job plans as well, you're going to have to write the logic to handle taskid to avoid conflicts. For example, let's say they have 10 tasks for generic job plan 1 and the actual job plan 2 starts with a taskid of 10. Even if the generic job plan incremented the taskid by 1 instead of 10 you would have a conflict on task 10. Because you can't apply a job plan when tasks exist, you'd have to apply the functional job plan first and then add in your tasks after & renumber where needed. It's technically doable, but if you're not needing capabilities like tracking resources on them it seems counter-productive to me. And potentially adds a lot of data to the WORKORDER table to store it. 

I've seen customers use a variety of mechanisms for tracking this sort of stuff. For example, some customers are using Inspections for tracking a checklist before a user can start the work. Others have built custom objects for having the user sign off on before starting work. It really all depends on their use case what makes the most sense.

------------------------------
Steven Shull
IBM
------------------------------