The use of Job Plans for Inspections requires the creation of a WO for each Asset or Location being inspected. This has always been a significant drawback of doing inspections in Maximo. The creation of a WO for activities that may only take a few minutes and are not going to be scheduled or charged individually adds a huge burden to the system.
The Routes application was introduced a long time ago to support Inspections. It allowed a single PM to be used to generate a number of inspections by associating a Route with a PM rather than creating and maintaining a separate PM for each Asset or Location to be inspected. However, it still required the creation of a Child or Task WO for every Route Stop and it is was necessary to capture readings, measurements, and/or observations at each Route Stop, then a Child WO needed to be created for each Route Stop with a Job Plan to generate Tasks for each reading, measurement, and/or observation.
The MultiAssetLocCI object was added more recently and partially addressed the problem by allowing Route Stops to become MultiAssetLocCI record rather than a Child or Task WO and generating only a single WO for the entire PM and Route. However, this functionality only allowed tracking the completion of the inspection at each Route Stop with no ability to enter readings, measurements, and/or observations from each inspection. This severely limited its usefulness as it only worked well for simple inspections where the same activity was being performed on each Route Stop and/or there was not need to capture results for each Asset or Location unless a problem was found, in which case a Follow-Up WO could be generated for each Route Stop with a problem.
With the addition of the Inspections functionality, Inspection Forms can now be referenced on Route Stops in the Routes application allowing a MultiAssetLocCI to be generated for each Route Stop and still be able to capture results of the inspection for the Asset or Location on each Route Stop. The Inspections functionality is a huge improvement to Maximo and has been improving with each release since it was initially introduced.
Of course, if the inspection of a single Asset or Location is going to take a significant amount of time or resources, a separate WO should be created for it so it can be properly planned, scheduled, and charged. However, it would still be preferable to reference an Inspection From on the WO to use for capturing results rather than using a Job Plan to generate a Task for each reading, measurement, or observation that may need to be captured.
Thank you.
#Maximo#AssetandFacilitiesManagement