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.
I've encountered a couple of dryers (as in laundry washer & dryer) that are sold as a stacked unit. So there are two dryers, an upper and a lower. They share a serial number. But they can be separated into individual units. You can also buy "the same dryer" as an individual unit, but the model number changes.
So it seems to me there would be 2 Item numbers here; one for the stacked dryers and one for the single dryers.
I want/need to track each one of these as Assets, so I need to make them Rotating, right? Of course that's right.
I also need to track that stacked unit individually; as in, once deployed, that stacked unit goes into BuildingX as Dryer 1 and Dryer 2. I want to be able to track the repairs for Dryer 1 separately from those for Dryer 2. Then, for example, someday down the road, Dryer 1 breaks, gets replaced by one of those single units. This seems like the answer is to make this a Kit. . .
A rotating item cannot be a kitted item. How would you go about solving this?
A preliminary test leads me to believe that the only way this "might" work is to buy the Stacked Dryer item for a storeroom. Then a PO will let you have a conversion factor other than "1." But I can't see us doing that; we'd buy it for a work order, and on the PO that automatically makes the conversion factor 1.
Travis Herron
I have been ~lucky~ enough to have Maximo and laundry machine experience. In this case Maximo was used in a consolidated call center for university housing and the actual maintenance was done by a laundry vendor. This allowed for each machine, stacked or otherwise, to be tracked on its own by its Customer Service Number as attached by the laundry service vendor.
However for your scenario would having each machine in the stack as a child asset to the stack? Yes, this creates an additional asset for the parent stack but would allow for the unit to be treated and moved as one, except when it is needed to be broken down or have one part replaced.
The most fun is the washer on the bottom and dryer on the top stacks!
Happy washing and drying,
Andy
Are you always deploying these in a stacked configuration? If so, then my approach would be this.
1) Create a location for stacked dryers.
2) Create an asset for the stacked model.
3) Create two spares, one for each half of the stacked configuration.
If the entire stacked config needs to be replaced, you do that by reordering the stacked model. If half of it breaks, you pull out part of the asset and swap in the spare. No kits.
-C