Maximo List Archive - Rogue Asset in Work Orders

This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.

Rogue Asset in Work Orders

From: Ian Turner (2017-08-08 10:48)

Hi All,

I feel I should know this but we have a rogue asset number that appears in
work orders (in the asset number field) that are set up as multi-asset or
child work orders from a planned maintenance. I have set up routes and set
these (now) to multi-asset but what we have done, to aid other lookups, is
to also add a location in the PM. Could having both route and location in
the PM cause this?

From: therron (2017-08-11 13:21)

I just ran a test of that on the Maximo 7.6 Preview Site. There was a PM in there that had a Route and a Location.

Jumping to the Location, there were 4 Assets in the Location.

Jumping to the Route, there were 7 Assets on the Route, configured to be in the Multi-Loc-CI table.

Generated a work order from the PM. Then went to Work Order Tracking to look at the work order. The Location was right, the Multi-Loc-CI was right, but it populated the Assetnum field with the alphabetically-first Asset at that location. However, that Asset happens to be the Parent Asset of the other 3 Assets in the Location, so that may be the good-old "if there's one Asset at the Location, and you make a Work Order for that Location, Maximo automatically assumes you are working on that Asset/fills in the Assetnum."

So I made a 2nd Asset at that Location, and generated another Work Order from the PM. This time it did not populate the Assetnum field. This is normal Maximo behavior. Adding a Location and a Route to your PM should still function correctly.

SO: Does the Location you put on the PM have one-and-only-one (parent-level) Asset in it, and is that Asset the "rogue" that is showing up?

Otherwise, start looking at the rogue asset, and see how it is connected to the other Assets. What do they have in common?

Also, look in the database itself to see if the table(s) (I'm thinking mostly the ROUTE_STOP table) have the same data that you are seeing in the UI.

Travis Herron