Maximo Open Forum

Hi Cory,

The MORE community has a 'Resources' page you can visit. https://moremaximo.com/maximoresources - within this page there are helpful resources like training videos. You can always look there to see if there is a training video around storerooms.

Some things to note when going through a Parent/Child Relationship. The Parent must be in the same organization and site as the child. It will allow you to add items to multiple storerooms at once, or trigger reordering of parts from a single parent site.

IBM has some documentation around storerooms here: https://www.ibm.com/docs/en/masv-and-l/maximo-manage/cd?topic=module-storerooms.

Thank you,

Hello Cory,

Please refer to the Storeroom hierarchies section of the below link. This give good information on maintaining storeroom hierarchy. 

https://www.ibm.com/docs/fi/mam/7.6.1?topic=module-storerooms-application

Hi Cory,

There is lots of training available to assist in building up your knowledge and skills around Maximo.  As Allen has said, there are resources within the MORE Maximo community, the Maximo - IBM Community, and IBM Training - Maximo specific.  I've never needed to set up a storeroom hierarchy because if there was a central storeroom scenario, I've set up the preferred supplier on the remote storerooms to be the central storeroom.  If your business scenario is that the remotes get replenished from the centrail storeroom, the only additional thing is to set the storeroom to be used in PR/PO which is a setting in the storeroom.

I think parent/child hierarchy would be more useful if Maximo was able to logically see inventory counts in the parent and child as a single count for an item. That would make reorder point calculations easier. I think Parent/Child is useful if the child storerooms must stock the same items as the parent. Preferred Suppplier is better I think when a child storeroom only needs to pull a subset of items from the parent storeroom.

For me, Parent/Child may be useful since we have furniture we track as an Item and when it is returned, it may go to 1 of 4 storerooms so having an existing item with 0 quantity would make it eligible to return to any storeroom.

Hi Sum Kim

I see the use case you have outlined using the "Add Items to Multiple Storerooms" menu option in the Item Master application when you have set up a hierarchy of storerooms.  Again, not one I have needed to use, but now I know more.  This is an outlier case because most times the item is created only in the storerooms where it will be held, rather than the chance that it may be returned to any storeroom.  Nothing wrong with that, it just that you have increased the number of items to be stock counted.

You mentioned that it would be better for reordering to combine the parent/child count for the purposes of reordering.  Here's my view on that. The ROP should be specific to that store.

Storeroom A - ROP 0, current stock 1, EOQ = 1, preferred supplier = ABC

Storeroom B - ROP 0, current stock 0, EOQ = 1, preferred supplier = Storeroom A

So, when the reorder cron task runs (order of operation are important here):

• Storeroom B reorders from Storeroom A
• Storeroom A reorders from the supplier

As long as you run the satellite stores before the central store, this cascade works well.  Even if you don't, it will be caught up on the next round, but that could be a whole day later.  Not great.

Each store has specific requirements and behaviour specific to its operations.  What this means is that you may have to adjust the EOQ or the ROP on the central store if multiple satellite storerooms are being fulfilled, i.e. what is the minimum stock at the central storeroom required so that the satellite store has a minimum lag tag time in order to meet the demands placed on them.  In other words, "How much buffer stock do you need?"

It's an art and a balance as to storeroom/warehouse management, so that:

• You minimised stock
• Have sufficient quantities to meet expected demand without having them wait whilst more stock is received
• Keep stock turning over
• ....