Maximo Open Forum

Hello all, I'm new to Maximo at this level. I'm the deep end with a half inflated life jacket. Our Maximo main user has recently left the business. We are finding out what they were dealing with in the background.

I am seeking the advice of the community on how to stop our maintenance PM's generating a work order for each task line on the embedded JP. 

We have PM's set up with Route stops for servicing multiple assets and each asset has a JP attached. The JP has several task lines.

Therefore we get (as an example) the PM is creating a "Parent Work Order", one Work Order for each asset that is being serviced and 14 Work Orders for each Asset with a task line assigned.  Therefore we get (1, + 12, +168) generated "Work Orders", needless generation of Work Orders and system space usage. 

We only require a Work Order for each asset. The service tech works off an Attached service sheet.  

Thank you in advance for any help.

Greg

------------------------------
Greg Dyer
Port Nelson Ltd
------------------------------

Hi @Greg Dyer!

The maintenance plan has an assigned route. Go to the routes application, search for it and you will see that it has configured how it should behave with each point on the route. This is where you define whether they will be tasks in WO or child work orders (each point a child WO). 

Regards!

------------------------------
Martin Fabra
ARSAT S.A. - Actively seeking employment
------------------------------

Hi Greg,

I'd like to elaborate a little on what Martin has said.

Your goal is to have one work order.  But you have also said "...for each asset".  That is conflicting as the current set-up fulfils the requirements.

There are two alternatives from the route perspective:

1. Have one work order + have each asset listed on the route as tasks.
2. Have one work order + have each asset listed on the route in the multiassetlocci table.

In both cases, they are not able to have a JP, instead, the PM contains the generic JP that must be executed for each asset.

However, you can have inspection forms.  If you've enabled the batching of these via the system properties, you still can have individual Q&A or/and meter collections.  Of course, once again this then expands the number of records, which you have indicated you don't want.

The least impactful, yet still able to be marked with complete (for tracking) is the multilocassetci.

------------------------------
Craig Kokay
Principal Consultant
COSOL

email: craig.kokay@cosol.global
#IBMChampion
------------------------------