Open for Voting

Deeper asset structure than PARENT -> CHILD

For example router and switch chassis (parent) contains often modules like Linecards, Supervisor Engines (childs) and so on.

This is perfect representable in the current asset structure of WHD.

But there are other components than the above-named, e.g. Daughterboards, HDD, Softwaremodules, optical interface modules located on child components.

Unfortunately it's not possible to assign "grand-child" or even "great grand-child" components to childs.

If I relocate a child asset from one chassis to another, the childs of the child are not also relocated because they are not assignable.

It would be great, if a deeper asset structure (proposal: 5 steps) would be possible.