We have PMs with Routes (Route Stops to be become Child WOs) associated with them, OOB Maximo does not seem to copy the Parent WO descriptions to Child WOs.

Is there perhaps a system property that would automatically copy Parent WO descriptions Child WOs?

Hi Tom,

Hmmm, no.  Let's understand what Maximo does when you add a child work order.  It does not have any description, so why would you expected anything else?

If your route stop does not mention a job plan, then the child work order description is the asset/location + its description.

If your route stop does mention a job plan, then the child work order description is that of the job plan, similiar if you don't fill in the work order description and add job plan.

There are a number of automation scripts out there that copy something from the parent to the child ref: A Scripting Solution to Set Child Work Order Values From the Parent

I have also created a script that performs a similar function, but based on the route and route stop.

My question is: why do you want the child to have the same as the parent?  Normally, the child is assigned to cover a different activity or Work Breakdown Structure (WBS).

Still, scripting is the answer.

We have PMs with Routes (Route Stops to be become Child WOs) associated with them, OOB Maximo does not seem to copy the Parent WO descriptions to Child WOs.

Is there perhaps a system property that would automatically copy Parent WO descriptions Child WOs?

Hi Tom,

Hmmm, no.  Let's understand what Maximo does when you add a child work order.  It does not have any description, so why would you expected anything else?

If your route stop does not mention a job plan, then the child work order description is the asset/location + its description.

If your route stop does mention a job plan, then the child work order description is that of the job plan, similiar if you don't fill in the work order description and add job plan.

There are a number of automation scripts out there that copy something from the parent to the child ref: A Scripting Solution to Set Child Work Order Values From the Parent

I have also created a script that performs a similar function, but based on the route and route stop.

My question is: why do you want the child to have the same as the parent?  Normally, the child is assigned to cover a different activity or Work Breakdown Structure (WBS).

Still, scripting is the answer.

We have PMs with Routes (Route Stops to be become Child WOs) associated with them, OOB Maximo does not seem to copy the Parent WO descriptions to Child WOs.

Is there perhaps a system property that would automatically copy Parent WO descriptions Child WOs?

Hi Craig,

This can be an issue if you have a single Job Pan attached to a PM where you have created a Route with multiple Locations or Assets. You may want to create separate child WO's using the same JP (craft, est hrs, task) executed at each one of the Locations/Assets due to the locations each having a different GL account. In that case you would select the route option for "Route Stops to become Child Work Orders". Since these become separate work orders rather than tasks or multiple entries on a single work order you would need for the WO descriptions to provide more than just the route location/asset. I know that adding the job plan to each route stop will bring in the description to each WO, but that prevents you from using that same route for other PMs where you want a job plan to be executed at each stop, perhaps by different resources depending on location (work zone).

For example, you may want to create a route for "All Nuclear Gauges" to list all scintillating counters within a site. But you might have other PM "tasks" that you want to perform on that same group of assets. It would seem that if you have selected the Route option to create child work orders for each stop, and you have not assigned a job plan to the individual stops, then the PM (parent) job plan description should carry to the work order description on all of the child work orders. Especially if these work orders may be assigned to different resources (internal or external) based on work zone assignments.

The main thing for me is the ability to reuse the same route when creating a new PM for that same group of locations or assets. If the route option is selected to create child work orders, then apply the PM job plan description to each child work order.

------------------------------
Jay Brackett

Original Message:
Sent: Thu April 17, 2025 01:42 AM
From: Craig Kokay
Subject: Parent WO Descriptions to Child WOs

Hi Tom,

Hmmm, no.  Let's understand what Maximo does when you add a child work order.  It does not have any description, so why would you expected anything else?

If your route stop does not mention a job plan, then the child work order description is the asset/location + its description.

If your route stop does mention a job plan, then the child work order description is that of the job plan, similiar if you don't fill in the work order description and add job plan.

There are a number of automation scripts out there that copy something from the parent to the child ref: A Scripting Solution to Set Child Work Order Values From the Parent

I have also created a script that performs a similar function, but based on the route and route stop.

My question is: why do you want the child to have the same as the parent?  Normally, the child is assigned to cover a different activity or Work Breakdown Structure (WBS).

Still, scripting is the answer.

------------------------------
Regards, Craig Kokay
Princpal Consultant, COSOL
https://cosol.global/

Ph: +61-411-682-040
email: craig.kokay@cosol.global
#IBMChampion

Original Message:
Sent: Wed April 16, 2025 08:06 PM
From: Tom M
Subject: Parent WO Descriptions to Child WOs

We have PMs with Routes (Route Stops to be become Child WOs) associated with them, OOB Maximo does not seem to copy the Parent WO descriptions to Child WOs.

Is there perhaps a system property that would automatically copy Parent WO descriptions Child WOs?

------------------------------
Tom M
------------------------------

Hi Jay,

I've conducted some testing.  I raised a route with five (5) stops.  For each route stop I:

1. Added a stop description + asset + no JP
2. Added a stop description + asset + JP.  The stop description was overridden by the JP description.
3. No stop description + Asset + no JP.
4. No stop description + asset + JP. The stop description was overridden by the JP description.
5. No stop description + asset + JP. The stop description was overridden by the JP description, but I then added the words "Special" to the stop description.

Then, I generated the route on a PM that also had a JP.  The results were:

1. Work order (parent) has the JP description.
2. Work order (child) description = route stop description
3. Work order (child) description = jp description, which has come from the route stop description
4. Work order (child) description = assetnum + asset description
5. Work order (child) description = jp description, which has come from the route stop description
6. Work order (child) description = jp description + "Special", which has come from the route stop description

I have avoided the scenario for this where you have a JP with no description, which should take on the PM description.

I'm not sure what you mean by "But you might have other PM "tasks" that you want to perform on that same group of assets" Can you please elaborate?

The takeaway is that you can override the route stop description to provide your own description per stop, otherwise you may need an automation script.

NB: All testing was done on MAS 9.0.10

Hi Craig,

This can be an issue if you have a single Job Pan attached to a PM where you have created a Route with multiple Locations or Assets. You may want to create separate child WO's using the same JP (craft, est hrs, task) executed at each one of the Locations/Assets due to the locations each having a different GL account. In that case you would select the route option for "Route Stops to become Child Work Orders". Since these become separate work orders rather than tasks or multiple entries on a single work order you would need for the WO descriptions to provide more than just the route location/asset. I know that adding the job plan to each route stop will bring in the description to each WO, but that prevents you from using that same route for other PMs where you want a job plan to be executed at each stop, perhaps by different resources depending on location (work zone).

For example, you may want to create a route for "All Nuclear Gauges" to list all scintillating counters within a site. But you might have other PM "tasks" that you want to perform on that same group of assets. It would seem that if you have selected the Route option to create child work orders for each stop, and you have not assigned a job plan to the individual stops, then the PM (parent) job plan description should carry to the work order description on all of the child work orders. Especially if these work orders may be assigned to different resources (internal or external) based on work zone assignments.

The main thing for me is the ability to reuse the same route when creating a new PM for that same group of locations or assets. If the route option is selected to create child work orders, then apply the PM job plan description to each child work order.

Hi Tom,

Hmmm, no.  Let's understand what Maximo does when you add a child work order.  It does not have any description, so why would you expected anything else?

If your route stop does not mention a job plan, then the child work order description is the asset/location + its description.

If your route stop does mention a job plan, then the child work order description is that of the job plan, similiar if you don't fill in the work order description and add job plan.

There are a number of automation scripts out there that copy something from the parent to the child ref: A Scripting Solution to Set Child Work Order Values From the Parent

I have also created a script that performs a similar function, but based on the route and route stop.

My question is: why do you want the child to have the same as the parent?  Normally, the child is assigned to cover a different activity or Work Breakdown Structure (WBS).

Still, scripting is the answer.

We have PMs with Routes (Route Stops to be become Child WOs) associated with them, OOB Maximo does not seem to copy the Parent WO descriptions to Child WOs.

Is there perhaps a system property that would automatically copy Parent WO descriptions Child WOs?

Hi Craig,

Thank you for your excellent analysis of the different ways that workorder descriptions are rendered when using routes. It clarifies how Maximo treats the different scenarios in setting up a route. I guess what I failed to describe fully is the desire to use the same route with several different PMs, each with a single job plan. In my case, it is not so much specific assets but actually departments located in as many as a hundred different physical locations in a large geographical area. Currently when you need to create a new PM for all of these locations, you would create a job plan and attach that same job plan to a hundred new PMs, each with the appropriate department location. This is because each would have a different GL account and may be assigned to different resources according to what work zone a location might fall in. Add the fact that when viewing a list of PM workorders you would need to see an activity-based description rather than just the asset or location.

In my opinion, the ideal scenario would be that when you create a PM with a Job Plan and reference a Route having the option selected to create child workorders, and no job plans are referenced on the route, then either the JP or PM description should appear as the child work order description. However, all of the methods to manage the WO description seemingly ties the Route to a single PM rather than being reusable for other PMs. I do not see a way to do this without scripting.

Thanks again for your response.

Hi Jay,

I've conducted some testing.  I raised a route with five (5) stops.  For each route stop I:

1. Added a stop description + asset + no JP
2. Added a stop description + asset + JP.  The stop description was overridden by the JP description.
3. No stop description + Asset + no JP.
4. No stop description + asset + JP. The stop description was overridden by the JP description.
5. No stop description + asset + JP. The stop description was overridden by the JP description, but I then added the words "Special" to the stop description.

Then, I generated the route on a PM that also had a JP.  The results were:

1. Work order (parent) has the JP description.
2. Work order (child) description = route stop description
3. Work order (child) description = jp description, which has come from the route stop description
4. Work order (child) description = assetnum + asset description
5. Work order (child) description = jp description, which has come from the route stop description
6. Work order (child) description = jp description + "Special", which has come from the route stop description

I have avoided the scenario for this where you have a JP with no description, which should take on the PM description.

I'm not sure what you mean by "But you might have other PM "tasks" that you want to perform on that same group of assets" Can you please elaborate?

The takeaway is that you can override the route stop description to provide your own description per stop, otherwise you may need an automation script.

NB: All testing was done on MAS 9.0.10

Hi Craig,

This can be an issue if you have a single Job Pan attached to a PM where you have created a Route with multiple Locations or Assets. You may want to create separate child WO's using the same JP (craft, est hrs, task) executed at each one of the Locations/Assets due to the locations each having a different GL account. In that case you would select the route option for "Route Stops to become Child Work Orders". Since these become separate work orders rather than tasks or multiple entries on a single work order you would need for the WO descriptions to provide more than just the route location/asset. I know that adding the job plan to each route stop will bring in the description to each WO, but that prevents you from using that same route for other PMs where you want a job plan to be executed at each stop, perhaps by different resources depending on location (work zone).

For example, you may want to create a route for "All Nuclear Gauges" to list all scintillating counters within a site. But you might have other PM "tasks" that you want to perform on that same group of assets. It would seem that if you have selected the Route option to create child work orders for each stop, and you have not assigned a job plan to the individual stops, then the PM (parent) job plan description should carry to the work order description on all of the child work orders. Especially if these work orders may be assigned to different resources (internal or external) based on work zone assignments.

The main thing for me is the ability to reuse the same route when creating a new PM for that same group of locations or assets. If the route option is selected to create child work orders, then apply the PM job plan description to each child work order.

Hi Tom,

Hmmm, no.  Let's understand what Maximo does when you add a child work order.  It does not have any description, so why would you expected anything else?

If your route stop does not mention a job plan, then the child work order description is the asset/location + its description.

If your route stop does mention a job plan, then the child work order description is that of the job plan, similiar if you don't fill in the work order description and add job plan.

There are a number of automation scripts out there that copy something from the parent to the child ref: A Scripting Solution to Set Child Work Order Values From the Parent

I have also created a script that performs a similar function, but based on the route and route stop.

My question is: why do you want the child to have the same as the parent?  Normally, the child is assigned to cover a different activity or Work Breakdown Structure (WBS).

Still, scripting is the answer.

We have PMs with Routes (Route Stops to be become Child WOs) associated with them, OOB Maximo does not seem to copy the Parent WO descriptions to Child WOs.

Is there perhaps a system property that would automatically copy Parent WO descriptions Child WOs?

Hi Jay

This diagram depicts a current scenario where the route is common to multiple PMs, and each PM references a different location.

You'll note that the GL account and the work group is different per PM as that is where the cost and the responsibility per PM reside.  The part seems to fit with what you have mentioned, but the description on the child WO still does not fit, so let's look at what I think is you're end goal.

Same outcome, but on each child WO, the description reflects that of the parent or rather the JP that is assigned.

My answer

My answer still has not changed from the original answer.  You will need to use an automation script to override the default behaviour of Maximo.

It's all about the triggering event.  If we think about what gets copied and what does not get copied when the child WO gets created, it brings an understanding of why the use of an automation script should be the answer.

When a PM with a route is attached and the route is nominated to create child WOs, then when the PM is triggered, the route gets applied to the WO, thus creating the child WOs.  Each child work order receives the JP from the route (if present on the stop and if not, then from the PM, again only if present).  Additionally, the route number and route stop are tagged on the child WO.  This means per child WO we know:

• If is a child WO
• If it comes from a route and which route stop
• What JP is being applied
• If there is a route stop description to use that; else use the Assetnum+asset desc or location+loc desc NB: No JP applied to the route stop

I have done this several times, where if the child WO (that's important here) has a JP and is from a route, then override the generated description with the JP description.  As this is an automation script, you could also derive the child WO from other information, such as the route description or PM description.

If I'm still wrong with my interpretation (always a chance there), can you please do a diagram.  It just makes it easier to interpret.  If not, there we're all good, and do you need help with the script?

------------------------------
Regards, Craig Kokay
Princpal Consultant, COSOL
https://cosol.global/

Ph: +61-411-682-040
email: craig.kokay@cosol.global
#IBMChampion

Original Message:
Sent: Fri July 11, 2025 08:34 AM
From: Jay Brackett
Subject: Parent WO Descriptions to Child WOs

Hi Craig,

Thank you for your excellent analysis of the different ways that workorder descriptions are rendered when using routes. It clarifies how Maximo treats the different scenarios in setting up a route. I guess what I failed to describe fully is the desire to use the same route with several different PMs, each with a single job plan. In my case, it is not so much specific assets but actually departments located in as many as a hundred different physical locations in a large geographical area. Currently when you need to create a new PM for all of these locations, you would create a job plan and attach that same job plan to a hundred new PMs, each with the appropriate department location. This is because each would have a different GL account and may be assigned to different resources according to what work zone a location might fall in. Add the fact that when viewing a list of PM workorders you would need to see an activity-based description rather than just the asset or location.

In my opinion, the ideal scenario would be that when you create a PM with a Job Plan and reference a Route having the option selected to create child workorders, and no job plans are referenced on the route, then either the JP or PM description should appear as the child work order description. However, all of the methods to manage the WO description seemingly ties the Route to a single PM rather than being reusable for other PMs. I do not see a way to do this without scripting.

Thanks again for your response.

------------------------------
Jay Brackett

Original Message:
Sent: Fri July 11, 2025 01:29 AM
From: Craig Kokay
Subject: Parent WO Descriptions to Child WOs

Hi Jay,

I've conducted some testing.  I raised a route with five (5) stops.  For each route stop I:

1. Added a stop description + asset + no JP
2. Added a stop description + asset + JP.  The stop description was overridden by the JP description.
3. No stop description + Asset + no JP.
4. No stop description + asset + JP. The stop description was overridden by the JP description.
5. No stop description + asset + JP. The stop description was overridden by the JP description, but I then added the words "Special" to the stop description.

Then, I generated the route on a PM that also had a JP.  The results were:

1. Work order (parent) has the JP description.
2. Work order (child) description = route stop description
3. Work order (child) description = jp description, which has come from the route stop description
4. Work order (child) description = assetnum + asset description
5. Work order (child) description = jp description, which has come from the route stop description
6. Work order (child) description = jp description + "Special", which has come from the route stop description

I have avoided the scenario for this where you have a JP with no description, which should take on the PM description.

I'm not sure what you mean by "But you might have other PM "tasks" that you want to perform on that same group of assets" Can you please elaborate?

The takeaway is that you can override the route stop description to provide your own description per stop, otherwise you may need an automation script.

NB: All testing was done on MAS 9.0.10

------------------------------
Regards, Craig Kokay
Princpal Consultant, COSOL
https://cosol.global/

Ph: +61-411-682-040
email: craig.kokay@cosol.global
#IBMChampion

Original Message:
Sent: Thu July 10, 2025 08:32 AM
From: Jay Brackett
Subject: Parent WO Descriptions to Child WOs

Hi Craig,

This can be an issue if you have a single Job Pan attached to a PM where you have created a Route with multiple Locations or Assets. You may want to create separate child WO's using the same JP (craft, est hrs, task) executed at each one of the Locations/Assets due to the locations each having a different GL account. In that case you would select the route option for "Route Stops to become Child Work Orders". Since these become separate work orders rather than tasks or multiple entries on a single work order you would need for the WO descriptions to provide more than just the route location/asset. I know that adding the job plan to each route stop will bring in the description to each WO, but that prevents you from using that same route for other PMs where you want a job plan to be executed at each stop, perhaps by different resources depending on location (work zone).

For example, you may want to create a route for "All Nuclear Gauges" to list all scintillating counters within a site. But you might have other PM "tasks" that you want to perform on that same group of assets. It would seem that if you have selected the Route option to create child work orders for each stop, and you have not assigned a job plan to the individual stops, then the PM (parent) job plan description should carry to the work order description on all of the child work orders. Especially if these work orders may be assigned to different resources (internal or external) based on work zone assignments.

The main thing for me is the ability to reuse the same route when creating a new PM for that same group of locations or assets. If the route option is selected to create child work orders, then apply the PM job plan description to each child work order.

------------------------------
Jay Brackett

Original Message:
Sent: Thu April 17, 2025 01:42 AM
From: Craig Kokay
Subject: Parent WO Descriptions to Child WOs

Hi Tom,

Hmmm, no.  Let's understand what Maximo does when you add a child work order.  It does not have any description, so why would you expected anything else?

If your route stop does not mention a job plan, then the child work order description is the asset/location + its description.

If your route stop does mention a job plan, then the child work order description is that of the job plan, similiar if you don't fill in the work order description and add job plan.

There are a number of automation scripts out there that copy something from the parent to the child ref: A Scripting Solution to Set Child Work Order Values From the Parent

I have also created a script that performs a similar function, but based on the route and route stop.

My question is: why do you want the child to have the same as the parent?  Normally, the child is assigned to cover a different activity or Work Breakdown Structure (WBS).

Still, scripting is the answer.

------------------------------
Regards, Craig Kokay
Princpal Consultant, COSOL
https://cosol.global/

Ph: +61-411-682-040
email: craig.kokay@cosol.global
#IBMChampion

Original Message:
Sent: Wed April 16, 2025 08:06 PM
From: Tom M
Subject: Parent WO Descriptions to Child WOs

We have PMs with Routes (Route Stops to be become Child WOs) associated with them, OOB Maximo does not seem to copy the Parent WO descriptions to Child WOs.

Is there perhaps a system property that would automatically copy Parent WO descriptions Child WOs?

------------------------------
Tom M
------------------------------