Maximo Open Forum

I am trying to utilize the PM forecasting to project resource requirements for the next year. We utilize a large number of routes where some generate work orders as child work orders and some as multi asset /multi loc work orders. For routes with job plans associated with the route stops the cost forecasting appears to be accurate. For the routes using the multi asset generation the cost forecast only shows costs for one iteration of the job plan and not the total cost for the route. We may have something configured incorrectly but I have not found anything to address this. Has anyone determined a way to display this data correctly?
#Analytics
#Assets

------------------------------
Kevin Egolf
TechOps
------------------------------

Hello Kevin

Scheduler product introduced this functionality and it is a known limitation for routes that have multiple assets/locations or task level work orders as we do not have the multiple job plans needed to calculate the correct resource requirements for both costing and scheduling.  I checked and Scheduler product does not have an open RFE on this subject if you would like to add one.

------------------------------
Lori Pilgrim
IBM
------------------------------

Hi Kevin,

I have leveraged conditional expressions on the job plan labor record to select the row with the planned hours as a function of how many stops are on the route record.  The number of stops is populated in a user defined attribute in the PM object.  This is the value evaluated during wogen to select the labor that is scaled to the number route stops on the route.

If you  need more information on our out of the box configuration, let me know.



------------------------------
Bill Steudler
The Pennsylvania State University
------------------------------

Original Message:
Sent: 6/21/2021 10:18:00 AM
From: Bill Steudler
Subject: RE: PM forecasting

Hi Kevin,

I have leveraged conditional expressions on the job plan labor record to select the row with the planned hours as a function of how many stops are on the route record.  The number of stops is populated in a user defined attribute in the PM object.  This is the value evaluated during wogen to select the labor that is scaled to the number route stops on the route.

If you  need more information on our out of the box configuration, let me know.



------------------------------
Bill Steudler
The Pennsylvania State University
------------------------------

Kevin,

Per your request, below are the configuration details of our implementation and references to additional content already published and available.

1. Database Configurations Application - Create two(2) user defined attributes, one each in PM and WORKORDER objects.  The datatype is integer.  I tagged these as routestopcount but can be named whatever is meaningful or appropriate to the organization.
2. Domains Application - Create a Crossover Domain to populate the WORKORDER user defined attribute from the PM object attribute (https://www.ibm.com/support/pages/setting-crossover-functionality-maximo).
3. Application Designer - Modify PM application to include a field that is configured to the PM object attribute created in step 1.  An authorized user will be able to update this value to match the number of stops on the applied route on the PM record.  Exposing this value in the WOTRACK application is optional.
4. Conditional Expression Manager - Create condition expression that are evaluated when the work order is generated (https://www.ibm.com/docs/en/mam/7.6.0.5?topic=module-conditional-expression-manager-application).  Examples of conditional expression we have implemented include bundling the count into a group with a range or a distinct single value:
   • :psu_routestopcount >= '1' and :psu_routestopcount <= '8'
   • :psu_routestopcount = '8'
5. Job Plan Application - Create a conditional job plan where there is multiple labor requirements with different planned time representing the scale of the effort dictated by the route count (https://www.ibm.com/docs/en/maximo-eam-saas?topic=orders-job-plan-conditions).
6. Apply created conditional job plan on a proper configured PM record that includes a route.

------------------------------
Bill Steudler
The Pennsylvania State University
------------------------------

Original Message:
Sent: 06-21-2021 10:28
From: Kevin Egolf
Subject: PM forecasting

Bill,

 

That sounds like it would work for us as well. I would appreciate any details you can provide to help us establish a process for our community.

 

Kevin Egolf

kegolf@techopsolutions.net

-----------------------------------------

Director Asset Management Programs

TechOp Solutions International

Cell: 571-344-3221

 

Original Message:
Sent: 6/21/2021 10:18:00 AM
From: Bill Steudler
Subject: RE: PM forecasting

Hi Kevin,

I have leveraged conditional expressions on the job plan labor record to select the row with the planned hours as a function of how many stops are on the route record.  The number of stops is populated in a user defined attribute in the PM object.  This is the value evaluated during wogen to select the labor that is scaled to the number route stops on the route.

If you  need more information on our out of the box configuration, let me know.



------------------------------
Bill Steudler
The Pennsylvania State University
------------------------------

Original Message:
Sent: 6/28/2021 9:13:00 AM
From: Bill Steudler
Subject: RE: PM forecasting

Kevin,

Per your request, below are the configuration details of our implementation and references to additional content already published and available.

1. Database Configurations Application - Create two(2) user defined attributes, one each in PM and WORKORDER objects.  The datatype is integer.  I tagged these as routestopcount but can be named whatever is meaningful or appropriate to the organization.
2. Domains Application - Create a Crossover Domain to populate the WORKORDER user defined attribute from the PM object attribute (https://www.ibm.com/support/pages/setting-crossover-functionality-maximo).
3. Application Designer - Modify PM application to include a field that is configured to the PM object attribute created in step 1.  An authorized user will be able to update this value to match the number of stops on the applied route on the PM record.  Exposing this value in the WOTRACK application is optional.
4. Conditional Expression Manager - Create condition expression that are evaluated when the work order is generated (https://www.ibm.com/docs/en/mam/7.6.0.5?topic=module-conditional-expression-manager-application).  Examples of conditional expression we have implemented include bundling the count into a group with a range or a distinct single value:
   • :psu_routestopcount >= '1' and :psu_routestopcount <= '8'
   • :psu_routestopcount = '8'
5. Job Plan Application - Create a conditional job plan where there is multiple labor requirements with different planned time representing the scale of the effort dictated by the route count (https://www.ibm.com/docs/en/maximo-eam-saas?topic=orders-job-plan-conditions).
6. Apply created conditional job plan on a proper configured PM record that includes a route.

------------------------------
Bill Steudler
The Pennsylvania State University
------------------------------


Original Message:
Sent: 06-21-2021 10:28
From: Kevin Egolf
Subject: PM forecasting

Bill,

 

That sounds like it would work for us as well. I would appreciate any details you can provide to help us establish a process for our community.

 

Kevin Egolf

kegolf@techopsolutions.net

-----------------------------------------

Director Asset Management Programs

TechOp Solutions International

Cell: 571-344-3221