Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
ardiadminguide:relationships [2016/08/01 00:05]
optrix
ardiadminguide:relationships [2017/12/10 23:01] (current)
optrix
Line 3: Line 3:
 ===Hierarchies=== ===Hierarchies===
  
-As well as logical ​and physical relationships, ​+A special note about hierarchies - an asset may only ever be attached (related) to a hierarchy at **one point**. An asset can't be in two locations, two places in the org chart etc. 
 + 
 +If you have a situation where you would like to place an asset in more than one hierarchy, consider using [[types|types]] instead, as these can fulfill a similar goal. 
 + 
 +===Directional Names=== 
 + 
 +Relationships have directional names. ​As well as the main name that describes the relationship as a whole (ie. Water Supply or Mains Power), they also have a description that applies when the relationship is going upstream (from child to parent) ​and another description that applies when it is going downstream (from parent to child). 
 + 
 +For example, the relationship 'Mains Power' is a physical ​relationship describing the power coming from the power grid. 
 + 
 +It has a relationship name of 'Mains Power',​ but it's upstream name is '​Powered By' and it's downstream name is '​Powers'​. 
 + 
 +These directional names are used when trying to describe these relationships ​in plain language. Rather than saying 'The light bulb has a downstream Mains Power relationship with the switch',​ we instead say 'The light bulb is powered by the switch'​. And vice-versa'The switch powers the light bulb'.
  
 ===Avoiding Cycles=== ===Avoiding Cycles===