Hi Eric,
You made a great question and I'm sure many others may be on the same boat as you.
Here are a few insights to help out solving your questions about this topic:
- You want to sort out your assets in the best way to help your asset management
- If you are setting, for example, your VFD as parent of your cooking kettle, you are thinking on terms of electrical diagram/blueprints downstream, but we are not looking to represent an electrical diagram on our asset management system.
- The VFD controlling your cooking kettle is just another constraint/requirement that helps your cooking kettle to work properly. If you are using also water, or gas on this asset, these would also be constrains/requirements to allow your asset a propper operation.
- I would definetely suggest you to set as asset parent is your electrical distribution system (not the VFD specifically)
- Going backwards to the idea of organizing it on a way to help your asset management, if your cooking kettle is down, it may be because of an issue with the VFD or with anything else on the asset. So if you were talking with your production team, you just don't say your VFD is down because something is wrong with you cooking kettle since it would sound awkwards. Also if later on you want to investigate on all issues related to your cooking kettle, you want to see your VFD failures, hence you want to have it as a child.
- Overall in my opinion, set electrical distribution system (all the way before VFD) and Cooking Kettle as as parent assets, and set VFD as the child asset of your Cooking Kettle.
Hope I helped you gain some clarity on this topic.
Cheers,
ignacio@factorycare.ca
Hello Ignacio,
I think I follow what you’re saying, but I am wondering if
- the VFD would normally be considered a child asset of the kettle (or)
- the VFD would normally be considered a child of the electrical control cabinet that it’s in (or)
- the electrical/instrumentation for that room would be the parent asset, then the electrical enclosure as the child asset, and then the VFD in the enclosure would be a childe of the electrical enclosure…
As I’m getting more involved in this process, I’m starting to think it could be #3
Thanks, Eric
Hi Eric,
I believe the right answer for this specific case, it's #1. When your company bought the Kettle, you had to acquire that VFD ( or probably came included) to run your Kettle. Your VFD is a device that helps you run your Kettle. When we are talking about life cycle management, we will always think on the whole asset that we are purchasing to produce money (Kettle). There are certain cues we need to identify.
In regards of #2 and #3, Yes, your electrical control cabinet could be your parent asset (if it's not shared) however, the Kettle would still be the grandparent asset. I wouldn't suggest you to include the electrical control cabinet and instead skip it because I'm sure you have many other assets that share common spaces like electrical panels. We should try to make it as descriptive as our operations require it, as for example you may ask your self, how offen do I need to replace/repair/troubleshoot the electrical control cabinet by itself? (the box) and most probably you don't replace it every 6 months or year because it's just a box (unless you have a dangerous environment with lots of cranes and forklifts where accidents tend to be something regular....).
Overall, it depends on your application and operations. If you never do work orders related to the electrical cabinet by itself (the box), I would suggest you to keep it simple:
Parent asset: Kettle
Child asset: VFD
But if for example if you have a cleaning PM for that electrical cabinet (that it's shared between other assets), it would be:
Parent asset: Kettle
Child asset: VFD
and
Parent asset: Electrical distribution system
Child asset: Electrical control cabinet
The electrical distribution systems it's an asset that provides a service for all your other assets, and it ends before any specific electrical devices (VFD) for specific assets (like your Kettle).
Watch out for the perfectionist trap. You could spend endless hours writing down all assets in MaintainX. Try to keep it simple.
Hope I gave you some valuable insights.
Cheers
ignacio@factorycare.ca
Thank you for your input! Much appreciated