Join / Log in
Learn how to increase the operational efficiency of the assets you manage, and improve overall equipment effectiveness by using IoT data and AI.
Reduce the operational costs of the facilities you manage, and create more engaging occupant experiences through the application of IoT data and AI.
Learn how IoT data and AI are being applied to transform the end-to-end engineering lifecycle.
I can create WOs using one of two methods:
Create new WO from Work Order Tracking
Or use a PM/JP/Route to generate parent and child WOs
With option 1, I can do the following successfully:
a) Use a crossover domain on classification to automatically populate fields in WOs.
b) Use job plan conditions to prevent parent WOs from getting tasks and assignments from the JP (more info here, here, and here).
c) Use automation scripts to auto-populate fields in tasks.
However, when I use option 2, a & c don't seem to work (the functionality doesn't seem to get triggered). And with b, the JP fails to get applied to any of the WOs - including child WOs - which is not what I want.
Does anyone else have similar issues? Is there a known design limitation in PMs that would explain this?
@Biplab Choudhury Do I remember that you experienced a similar issue with Job Plan conditions?
1) Create new WO from Work Order Tracking
2) Or use a PM/JP/Route to generate parent and child WOs
Does anyone else have these issues? Is there a known design limitation in Maximo that would explain this?