Location is not a hierarchical component. Therefore, the relationship is called Attribute in this section.
Relationship |
Type |
Organization of Relationship |
---|---|---|
Attribute of |
Position |
If the Position is specific, the Location can be the same or common. Else Location must be common. |
Attribute of |
Asset |
Same as for the Position attribute. |
Attribute of |
System |
Same as for the Position attribute. |
The number of child assets for one parent position is infinite, but with the Tag Option this number will be limited to one. The Tag Option has one major function in that when you associate the position to the work order the child asset will automatically become part of the history.
For many organizations, the tag number is a recognizable number that is often used in communications and as the equipment of the work order. The tag number is ideally a position in HxGN EAM. To include the asset in the history without the Tag Option you must write the work order one level deeper against the asset. The Tag Option does not require that you do this manually.
The advantages are as follows:
-
You do not need to know what the asset is attached to the position.
-
You do not need to know if the position even has an asset associated.
-
You do not need to drill down in the hierarchy and write the work order against the asset.
If a common system can have children of any organization associated and each organization has a different currency associated, it must be clear that the costs that roll up to this common system can also represent different currencies.