In Maximo 7.6.1.2:

I have a PM that uses a Job Plan (with tasks) and a Route (child WOs option) to generate a parent WO and child WOs.

• The PM generates child WOs with the tasks from the JP, which is good.
• However, when the PM generates the parent WO, the tasks also get applied to that parent WO. This is not what I want (the parent WO should not have tasks).

Is there a way to generate parent & child WOs from a PM/JP/Route without creating the JP tasks in the parent WO?

Thanks.
#Maximo
#AssetandFacilitiesManagement

If you have the JP on the PM and on none of the Route Stops, then all will use the JP i.e. parent + children.

If you have the JP on the PM and on the Route Stops, then you still have the same situation, but they maybe different JP's.  i.e. PM uses JP01, and the Route Stops uses JP02.

If you have no JP on the PM and instead on the Route Stops, then the parent has not tasks, only the child WO's do.  However, if you miss assigning on a Route Stop, then that subsequent Child WO will not have any tasks either.

So it's not a matter of preventing, more a case of understanding.

I hope that this helps.

------------------------------
Craig Kokay,
Lead Senior Maximo/IoT Consultant
ISW
Sydney, NSW, Australia
Ph: 0411-682-040
------------------------------

Hi

Having the Job Plan on the PM causes the tasks to be on the Parent Work Order. If the PM only has one Job Plan applied - remove the Job Plan from the PM and add it to each item in the route - tasks will then appear only on the Child Work Orders and not on the Parent Work Order. 

The problem I have is when there is a PM with sequenced Job Plans and a Route generating Child Work Orders. Tasks will appear on the Child and Parent Work Orders as the Job Plans have to be on the PM. If anyone has a solution to that it would be appreciated.

Thanks

------------------------------
Sonja Mangan
------------------------------

There is no easy solution to using a PM sequence and no JP on the top-level WO. So instead of fighting it, embrace it.  Simply have a JP that contains....nothing. If you don't put on any tasks or resources, then there will be...well, none.  Leaving all the work on the Route Stops that contain the real JP's.

There are advanced ways when using the like of Maximo for Transportation or ACM where you can enable/disable PM i.e. alternate between two.

------------------------------
===============================
Craig Kokay,
Lead Senior Maximo/IoT Consultant
ISW
Sydney, NSW, Australia
Ph: 0411-682-040
=================================
------------------------------

Original Message:
Sent: Mon November 16, 2020 07:12 PM
From: Sonja Mangan
Subject: Prevent parent WO from getting tasks? (PM/JP/Route)

Hi

Having the Job Plan on the PM causes the tasks to be on the Parent Work Order. If the PM only has one Job Plan applied - remove the Job Plan from the PM and add it to each item in the route - tasks will then appear only on the Child Work Orders and not on the Parent Work Order. 

The problem I have is when there is a PM with sequenced Job Plans and a Route generating Child Work Orders. Tasks will appear on the Child and Parent Work Orders as the Job Plans have to be on the PM. If anyone has a solution to that it would be appreciated.

Thanks

------------------------------
Sonja Mangan
------------------------------

Thanks Craig. That helps.

I'm planning to use routes for civil assets. For example, our mid-sized City has 10 zones.
So, for a type of asset (example: sewer connections), each zone will have a route. Each route will have up to 5,000 route stops for each asset in the zone. Multiplied by 10 zones.

If I were to apply a Job Plan to all 5,000 route stops in the route, I think I'd need a way to batch-apply the Job Plan to the route stops.
Any ideas for batch-applying a Job Plan to all route stops in a route?

Thanks.

Original Message:
Sent: Tue November 17, 2020 03:55 PM
From: Craig Kokay
Subject: Prevent parent WO from getting tasks? (PM/JP/Route)

There is no easy solution to using a PM sequence and no JP on the top-level WO. So instead of fighting it, embrace it.  Simply have a JP that contains....nothing. If you don't put on any tasks or resources, then there will be...well, none.  Leaving all the work on the Route Stops that contain the real JP's.

There are advanced ways when using the like of Maximo for Transportation or ACM where you can enable/disable PM i.e. alternate between two.

------------------------------
===============================
Craig Kokay,
Lead Senior Maximo/IoT Consultant
ISW
Sydney, NSW, Australia
Ph: 0411-682-040
=================================
------------------------------


Original Message:
Sent: Mon November 16, 2020 07:12 PM
From: Sonja Mangan
Subject: Prevent parent WO from getting tasks? (PM/JP/Route)

Hi

Having the Job Plan on the PM causes the tasks to be on the Parent Work Order. If the PM only has one Job Plan applied - remove the Job Plan from the PM and add it to each item in the route - tasks will then appear only on the Child Work Orders and not on the Parent Work Order. 

The problem I have is when there is a PM with sequenced Job Plans and a Route generating Child Work Orders. Tasks will appear on the Child and Parent Work Orders as the Job Plans have to be on the PM. If anyone has a solution to that it would be appreciated.

Thanks

------------------------------
Sonja Mangan

I wonder if I could add a custom JP field to the routes table, and use a crossover domain to populate the JP field on the route stops from the custom route field.

Might work?
Original Message:
Sent: Tue November 17, 2020 03:55 PM
From: Craig Kokay
Subject: Prevent parent WO from getting tasks? (PM/JP/Route)

There is no easy solution to using a PM sequence and no JP on the top-level WO. So instead of fighting it, embrace it.  Simply have a JP that contains....nothing. If you don't put on any tasks or resources, then there will be...well, none.  Leaving all the work on the Route Stops that contain the real JP's.

There are advanced ways when using the like of Maximo for Transportation or ACM where you can enable/disable PM i.e. alternate between two.

------------------------------
===============================
Craig Kokay,
Lead Senior Maximo/IoT Consultant
ISW
Sydney, NSW, Australia
Ph: 0411-682-040
=================================
------------------------------


Original Message:
Sent: Mon November 16, 2020 07:12 PM
From: Sonja Mangan
Subject: Prevent parent WO from getting tasks? (PM/JP/Route)

Hi

Having the Job Plan on the PM causes the tasks to be on the Parent Work Order. If the PM only has one Job Plan applied - remove the Job Plan from the PM and add it to each item in the route - tasks will then appear only on the Child Work Orders and not on the Parent Work Order. 

The problem I have is when there is a PM with sequenced Job Plans and a Route generating Child Work Orders. Tasks will appear on the Child and Parent Work Orders as the Job Plans have to be on the PM. If anyone has a solution to that it would be appreciated.

Thanks

------------------------------
Sonja Mangan

That should work for route stops that you add to the route after setting the value on the route. You could avoid an outage by using "Default Table Data" controls - i.e. a textbox with Input Mode = Default. But if you go with adding an attribute to Route, you might want to put an autoscript on the attribute or use some other launch mechanism to copy that attribute's value down to all the stops.

------------------------------
Blessings,
Jason Uppenborn
Sr. Technical Maximo Consultant
Ontracks Consulting
------------------------------

Original Message:
Sent: Mon November 23, 2020 08:35 PM
From: User1971
Subject: Prevent parent WO from getting tasks? (PM/JP/Route)

I wonder if I could add a custom JP field to the routes table, and use a crossover domain to populate the JP field on the route stops from the custom route field.

Might work?

Original Message:
Sent: Tue November 17, 2020 03:55 PM
From: Craig Kokay
Subject: Prevent parent WO from getting tasks? (PM/JP/Route)

There is no easy solution to using a PM sequence and no JP on the top-level WO. So instead of fighting it, embrace it.  Simply have a JP that contains....nothing. If you don't put on any tasks or resources, then there will be...well, none.  Leaving all the work on the Route Stops that contain the real JP's.

There are advanced ways when using the like of Maximo for Transportation or ACM where you can enable/disable PM i.e. alternate between two.

------------------------------
===============================
Craig Kokay,
Lead Senior Maximo/IoT Consultant
ISW
Sydney, NSW, Australia
Ph: 0411-682-040
=================================


Original Message:
Sent: Mon November 16, 2020 07:12 PM
From: Sonja Mangan
Subject: Prevent parent WO from getting tasks? (PM/JP/Route)

Hi

Having the Job Plan on the PM causes the tasks to be on the Parent Work Order. If the PM only has one Job Plan applied - remove the Job Plan from the PM and add it to each item in the route - tasks will then appear only on the Child Work Orders and not on the Parent Work Order. 

The problem I have is when there is a PM with sequenced Job Plans and a Route generating Child Work Orders. Tasks will appear on the Child and Parent Work Orders as the Job Plans have to be on the PM. If anyone has a solution to that it would be appreciated.

Thanks

------------------------------
Sonja Mangan

Hi, 

You can use the condition field  on the JOBTASK , You can set a condition that is evaluated when a task is copied to a work order. If the condition is met, the task and its corresponding resources are copied to the work order. If the condition is not met, none of the components of the job plan are copied to the work order.
You enable conditions for job plans in the Organizations application. 

In the condition you can put "parent is not null .." or any other specific condition, you can even use automation script if you need to evaluate the condition base on non-persistent field

Regards 
Abdelmonem Boughdiri

------------------------------
Abdelmonem Boughdiri
------------------------------

Hi, 

You can use the condition field  on the JOBTASK , You can set a condition that is evaluated when a task is copied to a work order. If the condition is met, the task and its corresponding resources are copied to the work order. If the condition is not met, none of the components of the job plan are copied to the work order.
You enable conditions for job plans in the Organizations application. 

In the condition you can put "parent is not null .." or any other specific condition, you can even use automation script if you need to evaluate the condition base on non-persistent field

Regards 
Abdelmonem Boughdiri

------------------------------
Abdelmonem Boughdiri
------------------------------

Thanks!

Regarding: "You enable conditions for job plans in the Organizations application"
I'm having trouble finding the Job Plans section in the Organizations application.

Are you referring to the PM Options window as shown below?

 

Original Message:
Sent: Tue November 24, 2020 07:03 AM
From: Abdelmonem Boughdiri
Subject: Prevent parent WO from getting tasks? (PM/JP/Route)

Hi, 

You can use the condition field  on the JOBTASK , You can set a condition that is evaluated when a task is copied to a work order. If the condition is met, the task and its corresponding resources are copied to the work order. If the condition is not met, none of the components of the job plan are copied to the work order.
You enable conditions for job plans in the Organizations application. 

In the condition you can put "parent is not null .." or any other specific condition, you can even use automation script if you need to evaluate the condition base on non-persistent field

Regards 
Abdelmonem Boughdiri

------------------------------
Abdelmonem Boughdiri
------------------------------

Original Message:
Sent: 11/25/2020 3:17:00 PM
From: User1971
Subject: RE: Prevent parent WO from getting tasks? (PM/JP/Route)

Thanks!

Regarding: "You enable conditions for job plans in the Organizations application"
I'm having trouble finding the Job Plans section in the Organizations application.

Are you referring to the PM Options window as shown below?

Thanks again.

 

More info here:

https://www.ibm.com/support/pages/job-plan-conditions

https://www.ibm.com/support/knowledgecenter/SSBLW8/com.ibm.mbs.doc/jobplan/t_set_jobplan_conditions.html
Original Message:
Sent: Wed November 25, 2020 03:16 PM
From: User1971
Subject: Prevent parent WO from getting tasks? (PM/JP/Route)

Thanks!

Regarding: "You enable conditions for job plans in the Organizations application"
I'm having trouble finding the Job Plans section in the Organizations application.

Are you referring to the PM Options window as shown below?

Thanks again.

 

Original Message:
Sent: Tue November 24, 2020 07:03 AM
From: Abdelmonem Boughdiri
Subject: Prevent parent WO from getting tasks? (PM/JP/Route)

Hi, 

You can use the condition field  on the JOBTASK , You can set a condition that is evaluated when a task is copied to a work order. If the condition is met, the task and its corresponding resources are copied to the work order. If the condition is not met, none of the components of the job plan are copied to the work order.
You enable conditions for job plans in the Organizations application. 

In the condition you can put "parent is not null .." or any other specific condition, you can even use automation script if you need to evaluate the condition base on non-persistent field

Regards 
Abdelmonem Boughdiri

------------------------------
Abdelmonem Boughdiri

A related question here:

WOs from PM/JP/Route: Multiple issues with auto-populating data

(including Job Plan conditions)

#Maximo
#AssetandFacilitiesManagement