Maximo Open Forum

The concept is great, build an Inspection form, associate it with any number of assets by using a route.  You can then associate the route with a PM for scheduled inspections or associate the route directly with a work order for ad-hoc inspections.

Data gathered in the work center inspection carries over to the asset's meter(s) and condition monitoring points.

Use case examples:

• •      Using a route to report operating hours for mobile equipment meter based PMs
• •      Entering readings (gauge, characteristic meters) for condition monitoring point data

Trouble is, I'm not able to successfully configure an end-to-end pilot where a PM fires the Route and I can initiate collection of the inspection results in WO Tracking.

I've been testing in both MaS 8 and 7.6.1.2. Some features work in 7.6 and some in 8.6. Main issue is Inspection results are not generated for the Route Stops.

Is there a minimum version/patch level that others have found success with routes and inspection forms, Steven?

The issue you're seeing is related to the system property mxe.app.workorder.StatusToCreateInspection that was added. Previously we created the inspection result as soon as it was applied to a WO. Now we make it a configurable setting of which statuses (a comma separated list) you want the inspection result to be generated in. Unfortunately, out of the box it's set to WAPPR and a PM is set to generate WO in typically WSCH or APPR so it causes it to not generate the inspection result. You need to update this system property to have all the statuses you want it to generate in and then it will for new records. Existing records you need to go back to a previous status and change it again to get it to generate. 

Another useful system property that is not directly relevant to this but important to call out is mxe.app.inspection.UpdatePendingResults. With PMs this is especially important because you may generate PMs month in advance. In the past if you then had revised the inspection form after WOs were generated, all those existing WOs were stuck with the old inspection form revision. Now as long as it's still in a PENDING status (users haven't worked the inspection) it will automatically use the latest revision instead when this is enabled.

The concept is great, build an Inspection form, associate it with any number of assets by using a route.  You can then associate the route with a PM for scheduled inspections or associate the route directly with a work order for ad-hoc inspections.

Data gathered in the work center inspection carries over to the asset's meter(s) and condition monitoring points.

Use case examples:

• •      Using a route to report operating hours for mobile equipment meter based PMs
• •      Entering readings (gauge, characteristic meters) for condition monitoring point data

Trouble is, I'm not able to successfully configure an end-to-end pilot where a PM fires the Route and I can initiate collection of the inspection results in WO Tracking.

I've been testing in both MaS 8 and 7.6.1.2. Some features work in 7.6 and some in 8.6. Main issue is Inspection results are not generated for the Route Stops.

Is there a minimum version/patch level that others have found success with routes and inspection forms, Steven?

Thank you Steven - in further testing, I found another system property that needed to be updated from its default to achieve my desired outcome of batch inspections for the route - mxe.app.workorder.InspectionBatchRecord.

I really like what I'm seeing with this functionality, looking forward to see how it plays on mobile devices. 

The issue you're seeing is related to the system property mxe.app.workorder.StatusToCreateInspection that was added. Previously we created the inspection result as soon as it was applied to a WO. Now we make it a configurable setting of which statuses (a comma separated list) you want the inspection result to be generated in. Unfortunately, out of the box it's set to WAPPR and a PM is set to generate WO in typically WSCH or APPR so it causes it to not generate the inspection result. You need to update this system property to have all the statuses you want it to generate in and then it will for new records. Existing records you need to go back to a previous status and change it again to get it to generate. 

Another useful system property that is not directly relevant to this but important to call out is mxe.app.inspection.UpdatePendingResults. With PMs this is especially important because you may generate PMs month in advance. In the past if you then had revised the inspection form after WOs were generated, all those existing WOs were stuck with the old inspection form revision. Now as long as it's still in a PENDING status (users haven't worked the inspection) it will automatically use the latest revision instead when this is enabled.

The concept is great, build an Inspection form, associate it with any number of assets by using a route.  You can then associate the route with a PM for scheduled inspections or associate the route directly with a work order for ad-hoc inspections.

Data gathered in the work center inspection carries over to the asset's meter(s) and condition monitoring points.

Use case examples:

• •      Using a route to report operating hours for mobile equipment meter based PMs
• •      Entering readings (gauge, characteristic meters) for condition monitoring point data

Trouble is, I'm not able to successfully configure an end-to-end pilot where a PM fires the Route and I can initiate collection of the inspection results in WO Tracking.

I've been testing in both MaS 8 and 7.6.1.2. Some features work in 7.6 and some in 8.6. Main issue is Inspection results are not generated for the Route Stops.

Is there a minimum version/patch level that others have found success with routes and inspection forms, Steven?

Thank you Steven - in further testing, I found another system property that needed to be updated from its default to achieve my desired outcome of batch inspections for the route - mxe.app.workorder.InspectionBatchRecord.

I really like what I'm seeing with this functionality, looking forward to see how it plays on mobile devices. 

------------------------------
Mack Parrott
Projetech Inc.

Original Message:
Sent: 08-29-2023 11:01
From: Steven Shull
Subject: Using Routes and Inspection forms

The issue you're seeing is related to the system property mxe.app.workorder.StatusToCreateInspection that was added. Previously we created the inspection result as soon as it was applied to a WO. Now we make it a configurable setting of which statuses (a comma separated list) you want the inspection result to be generated in. Unfortunately, out of the box it's set to WAPPR and a PM is set to generate WO in typically WSCH or APPR so it causes it to not generate the inspection result. You need to update this system property to have all the statuses you want it to generate in and then it will for new records. Existing records you need to go back to a previous status and change it again to get it to generate. 

Another useful system property that is not directly relevant to this but important to call out is mxe.app.inspection.UpdatePendingResults. With PMs this is especially important because you may generate PMs month in advance. In the past if you then had revised the inspection form after WOs were generated, all those existing WOs were stuck with the old inspection form revision. Now as long as it's still in a PENDING status (users haven't worked the inspection) it will automatically use the latest revision instead when this is enabled.

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

Original Message:
Sent: 08-28-2023 17:07
From: Mack Parrott
Subject: Using Routes and Inspection forms

The concept is great, build an Inspection form, associate it with any number of assets by using a route.  You can then associate the route with a PM for scheduled inspections or associate the route directly with a work order for ad-hoc inspections.

Data gathered in the work center inspection carries over to the asset's meter(s) and condition monitoring points.

Use case examples:

• •      Using a route to report operating hours for mobile equipment meter based PMs
• •      Entering readings (gauge, characteristic meters) for condition monitoring point data

Trouble is, I'm not able to successfully configure an end-to-end pilot where a PM fires the Route and I can initiate collection of the inspection results in WO Tracking.

I've been testing in both MaS 8 and 7.6.1.2. Some features work in 7.6 and some in 8.6. Main issue is Inspection results are not generated for the Route Stops.

Is there a minimum version/patch level that others have found success with routes and inspection forms, Steven?

#WorkCenters

------------------------------
Mack Parrott
Projetech Inc.
------------------------------

The issue you're seeing is related to the system property mxe.app.workorder.StatusToCreateInspection that was added. Previously we created the inspection result as soon as it was applied to a WO. Now we make it a configurable setting of which statuses (a comma separated list) you want the inspection result to be generated in. Unfortunately, out of the box it's set to WAPPR and a PM is set to generate WO in typically WSCH or APPR so it causes it to not generate the inspection result. You need to update this system property to have all the statuses you want it to generate in and then it will for new records. Existing records you need to go back to a previous status and change it again to get it to generate. 

Another useful system property that is not directly relevant to this but important to call out is mxe.app.inspection.UpdatePendingResults. With PMs this is especially important because you may generate PMs month in advance. In the past if you then had revised the inspection form after WOs were generated, all those existing WOs were stuck with the old inspection form revision. Now as long as it's still in a PENDING status (users haven't worked the inspection) it will automatically use the latest revision instead when this is enabled.

The concept is great, build an Inspection form, associate it with any number of assets by using a route.  You can then associate the route with a PM for scheduled inspections or associate the route directly with a work order for ad-hoc inspections.

Data gathered in the work center inspection carries over to the asset's meter(s) and condition monitoring points.

Use case examples:

• •      Using a route to report operating hours for mobile equipment meter based PMs
• •      Entering readings (gauge, characteristic meters) for condition monitoring point data

Trouble is, I'm not able to successfully configure an end-to-end pilot where a PM fires the Route and I can initiate collection of the inspection results in WO Tracking.

I've been testing in both MaS 8 and 7.6.1.2. Some features work in 7.6 and some in 8.6. Main issue is Inspection results are not generated for the Route Stops.

Is there a minimum version/patch level that others have found success with routes and inspection forms, Steven?

The concept is great, build an Inspection form, associate it with any number of assets by using a route.  You can then associate the route with a PM for scheduled inspections or associate the route directly with a work order for ad-hoc inspections.

Data gathered in the work center inspection carries over to the asset's meter(s) and condition monitoring points.

Use case examples:

• •      Using a route to report operating hours for mobile equipment meter based PMs
• •      Entering readings (gauge, characteristic meters) for condition monitoring point data

Trouble is, I'm not able to successfully configure an end-to-end pilot where a PM fires the Route and I can initiate collection of the inspection results in WO Tracking.

I've been testing in both MaS 8 and 7.6.1.2. Some features work in 7.6 and some in 8.6. Main issue is Inspection results are not generated for the Route Stops.

Is there a minimum version/patch level that others have found success with routes and inspection forms, Steven?

Hi Mark, 

In our current Maximo implementation we are using the same method as you described. On paper it works great until we deployed to production where with large amounts of data has become very very slow and almost unusable. Have you seen any issues with perforamce when trying this set up? we are currently on 7.6.1.2 . Or if anyone else has seen performance issues around Routes, Inspection Forms, and Workorders? 

------------------------------
David Nielsen
------------------------------

The concept is great, build an Inspection form, associate it with any number of assets by using a route.  You can then associate the route with a PM for scheduled inspections or associate the route directly with a work order for ad-hoc inspections.

Data gathered in the work center inspection carries over to the asset's meter(s) and condition monitoring points.

Use case examples:

• •      Using a route to report operating hours for mobile equipment meter based PMs
• •      Entering readings (gauge, characteristic meters) for condition monitoring point data

Trouble is, I'm not able to successfully configure an end-to-end pilot where a PM fires the Route and I can initiate collection of the inspection results in WO Tracking.

I've been testing in both MaS 8 and 7.6.1.2. Some features work in 7.6 and some in 8.6. Main issue is Inspection results are not generated for the Route Stops.

Is there a minimum version/patch level that others have found success with routes and inspection forms, Steven?

Hi Mark, 

In our current Maximo implementation we are using the same method as you described. On paper it works great until we deployed to production where with large amounts of data has become very very slow and almost unusable. Have you seen any issues with perforamce when trying this set up? we are currently on 7.6.1.2 . Or if anyone else has seen performance issues around Routes, Inspection Forms, and Workorders? 

------------------------------
David Nielsen
------------------------------

The concept is great, build an Inspection form, associate it with any number of assets by using a route.  You can then associate the route with a PM for scheduled inspections or associate the route directly with a work order for ad-hoc inspections.

Data gathered in the work center inspection carries over to the asset's meter(s) and condition monitoring points.

Use case examples:

• •      Using a route to report operating hours for mobile equipment meter based PMs
• •      Entering readings (gauge, characteristic meters) for condition monitoring point data

Trouble is, I'm not able to successfully configure an end-to-end pilot where a PM fires the Route and I can initiate collection of the inspection results in WO Tracking.

I've been testing in both MaS 8 and 7.6.1.2. Some features work in 7.6 and some in 8.6. Main issue is Inspection results are not generated for the Route Stops.

Is there a minimum version/patch level that others have found success with routes and inspection forms, Steven?