Hi Kevin,
Of the three options for routes, only the child work order will give you what you from.
The set-up:
- Create route with one or more stops.
- Mark it to generate child work order
- Save
- Create a PM referencing an active Job Plan and the route from step#1
- Complete other PM fields as needed
- Save
- Change status to Active
- Generate the work order using either the menu option or the cron task.
This will result in a master work order with the same number of child work orders as there are route stops. One for each child work order will be the job plan, but the job plan will also be on the parent work order and as such is incorrect. You are not doing the same tasks on the parent as the children and this is why the correct option should be to have on the route stops the job plan for the activities required to be performed at each stop.
You will also have to have the discipline to record the time and materials only on the tasks, though there is also time spent on the parent in managing the task, so some allowance is given here.
If you chose instead the task option you can still charge you time to each task or only to the work order, it just depends on where you overall want to accumulate the costs. However, in this scenario, the concept is that the job plan covers ALL the tasks materials and hours i.e. each asset will take 10 min to complete, but there are six, so that will be 60 minutes of work in total.
Either option works, it's a matter of how you want to work and accumulate the costs. Is there any advantage of one over the other? Simply put, do want you to spend your time looking at seven work orders (1 parent + 6 children) or just one work order?
BTW: The multi-option is still very similar to the task option, but costs for not get accumulated against each asset.
BTW: In Maximo for Transportation, they have asset lists that are very similar to routes, but there is no choice, as they will generate child work orders.
Finally, let's get back to the PM and forecasting. I've inferred that using the child option means only having to mention the JP once on the PM, whereas using the task option you'll either have to mention the JP for each stop or have the PM JP sum up all the costs for doing all the stops, then if you select the multi option the PM JP sum up all the costs for doing all the stops.
Helped or more confused?
------------------------------
Craig Kokay
Principal Consultant
COSOL
email:
craig.kokay@cosol.global#IBMChampion
------------------------------
Original Message:
Sent: 02-07-2024 15:49
From: Kevin Egolf
Subject: PM Forecasting
We are attempting to use PM forecasting to establish resource requirements and budget costs for the next year. I have been successful at generating the schedule but struggle to get accurate cost and resource information.
We use a lot of routes to address similar assets in a building (AC units, Pumps). When the forecast is run and the costs are calculated Maximo only shows the cost and resources for one iteration of the PM if you use the multi asset / location option or child work order option if you do not add a job plan to the route stops. This can be quite inaccurate for a building with 30 AC units in it. If you configure the route for child work orders and add the job plan to each route stop the costs are correct. However you can not use sequenced job plans since the job plan is on the route.
We have created a report that uses the forecasting table data and multiplies by the number of route stops, but it is a bit clunky. Has anyone come up with a cleaner solution?
#MaximoApplicationSuite
------------------------------
Kevin Egolf
TechOps
------------------------------