MAM 7.6.1.2:

I can create WOs using one of two methods:

1. Create new WO from Work Order Tracking

2. 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.

Question:

Does anyone else have similar issues? Is there a known design limitation in PMs that would explain this?

#AssetandFacilitiesManagement
#Maximo

@Biplab Choudhury Do I remember that you experienced a similar issue with Job Plan conditions?

Hi User1971,

I have not seen the issue you have mentoned. 
Not sure for action b but action #a and #c should definitely work.

Can you please give more details on what kind of crossover domain or script you were trying and didnt get triggered?

Thanks,
Biplab​​

------------------------------
Biplab Choudhury
Maximo Consultant
Tata Consultancy Services
Melbourne
------------------------------

Original Message:
Sent: Tue December 29, 2020 09:12 AM
From: User1971
Subject: WOs from PM/JP/Route: Multiple issues with auto-populating data

@Biplab Choudhury Do I remember that you experienced a similar issue with Job Plan conditions?