Hi jeff. We had a doubt regarding this topic. As you show, we can have an asset for example a tank, where it have assets down like a pump, an agitator, an motor... So when creating task order, if you want to do a job in the tank but also in the pump you are using the asset "Tank". How can you make the spare part (Fexample the mechanic seal of the pump) also in the tank, so if you are doing the task and you detect the mechanic seal leaking you can look to it directly on the task and don't need to go to the asset of the pump a look there for the correct seal.
Hi Jorge - It can be difficult to answer these sort of questions because there are so many factors, really you need to see your data, and discuss face to face neither of which is possible. My first reaction was why is the tank an asset and not an operating location? The pump, agitator and motor can be assets of the tank, and these are referenced by the work order or task, they would naturally add the tank as the location. If you always inspect the components of the tank at the same time then they can be linked together using a Route and the PM references the Tank location and the Route. The Spare Parts are on the assets that they are spare parts of, the pump, agitator, and motor in your example. If you also have spare parts of the tank itself then create an asset for the tank at the operating location of the tank and put the spare parts on the tank asset. You do not need an asset hierarchy unless the assets truly belong as a subasssembly. Think of this more as if you disassembled the parent would you take the subassemblies with it? There are other factors to consider. Are there continuous meters? If so is the delta reading applied to multiple of the tank's assets? Do you record downtime? In which case on which asset would you record downtime? These are the sort of questions you would ask in a more rigorous analysis of your situation. What I have suggested above may not be the right answer, but it is the best I can give based on the information you gave. Good luck. PS. Put three seasoned Maximo consultants in a room with this sort of problem and they would not come up with the same answer, but they would conclude they needed to ask a lot more questions when they did their workshop.
Thanks Achanta - The next two areas are Maintenance Planning (Job Plans, PMs, Routes that sort of thing), then Service Management (SR's). On Maximo Secrets if you look at the Podcast there are the first forty transcripts, of which the first 8 in Asset Management now have the podcast audio. After Service Management will be Work Management, then Inventory, Contracts, Procurement and lastly Finance - I have planned about 90 episodes, but this will take me 18 months to do the videos, but I may try and get all the articles/podcasts done by next July.
Very Useful Jeff. Thanks for your good work.
Thanks Sankar, pleased you enjoyed them.
Really Great Videos ❤️
Thank you 🙌
Hi jeff. We had a doubt regarding this topic. As you show, we can have an asset for example a tank, where it have assets down like a pump, an agitator, an motor... So when creating task order, if you want to do a job in the tank but also in the pump you are using the asset "Tank". How can you make the spare part (Fexample the mechanic seal of the pump) also in the tank, so if you are doing the task and you detect the mechanic seal leaking you can look to it directly on the task and don't need to go to the asset of the pump a look there for the correct seal.
Hi Jorge - It can be difficult to answer these sort of questions because there are so many factors, really you need to see your data, and discuss face to face neither of which is possible.
My first reaction was why is the tank an asset and not an operating location? The pump, agitator and motor can be assets of the tank, and these are referenced by the work order or task, they would naturally add the tank as the location. If you always inspect the components of the tank at the same time then they can be linked together using a Route and the PM references the Tank location and the Route. The Spare Parts are on the assets that they are spare parts of, the pump, agitator, and motor in your example. If you also have spare parts of the tank itself then create an asset for the tank at the operating location of the tank and put the spare parts on the tank asset. You do not need an asset hierarchy unless the assets truly belong as a subasssembly. Think of this more as if you disassembled the parent would you take the subassemblies with it?
There are other factors to consider. Are there continuous meters? If so is the delta reading applied to multiple of the tank's assets? Do you record downtime? In which case on which asset would you record downtime? These are the sort of questions you would ask in a more rigorous analysis of your situation.
What I have suggested above may not be the right answer, but it is the best I can give based on the information you gave. Good luck.
PS. Put three seasoned Maximo consultants in a room with this sort of problem and they would not come up with the same answer, but they would conclude they needed to ask a lot more questions when they did their workshop.
Jeff, your video's are very useful in learning functional concepts in details, thanks for your work, any plans on SCM side or WM side?
Thanks Achanta - The next two areas are Maintenance Planning (Job Plans, PMs, Routes that sort of thing), then Service Management (SR's). On Maximo Secrets if you look at the Podcast there are the first forty transcripts, of which the first 8 in Asset Management now have the podcast audio. After Service Management will be Work Management, then Inventory, Contracts, Procurement and lastly Finance - I have planned about 90 episodes, but this will take me 18 months to do the videos, but I may try and get all the articles/podcasts done by next July.