Child assets have only one indicator of membership under a parent. There are cases where the child may be one of several copies under a parent.

the reason to know what position the child is in are several:

• find the right asset to repair maintain,
• code the counters from the asset with the specific position. different positions are differentially loading assets and parents for wear and tear.
• Allow a position type to be included in a position code so that attachments can be added to a parent which are recognized as non-core sub-systems. Attachments in construction or manufacturing have an impact of the costs or prices for the asset as a consumed resource.

for the purpose of setting the subsystem a new parent, this wuld require only one added field to specify.

The setup of the position table would only be a handful of fields to include the nature: (core vs. attach)