|
Relationship |
Type |
Quantity |
Organization of Relationship |
|---|---|---|---|
|
Child |
Position |
Infinite |
If the Position is specific, the child can be the same or common. Else child must be common. |
|
Child |
Asset |
Infinite |
Same as for the Position child. |
|
Parent |
Position |
1 |
If the Position is common, the parent can be the same or any specific. Else parent must be the same specific. |
|
Parent |
Asset |
1 |
Same as for the Position parent. |
|
Parent |
System |
Infinite |
If the Position is common, the parent can be the same or any specific. Else parent can be the same specific or common. |
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 which 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.