Differences

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

Link to this comparison view

Next revision
Previous revision
ardiadminguide:relationships [2016/08/01 00:02]
optrix created
ardiadminguide:relationships [2017/12/10 23:01] (current)
optrix
Line 1: Line 1:
-====Relationships==== 
- 
 {{page>​ardibasics:​relationships}} {{page>​ardibasics:​relationships}}
 +
 +===Hierarchies===
 +
 +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===
Line 11: Line 25:
 To get around this - while at the same time making the relationships between your assets even more informative - we suggest splitting loops such as this into **two** relationships. To get around this - while at the same time making the relationships between your assets even more informative - we suggest splitting loops such as this into **two** relationships.
  
-To take the cooling system as an example, rather than having ​single '​Cooling Water' relationship,​ you instead have a 'Cold Cooling Water' and 'Hot Cooling Water' relationship instead. The '​Cold'​ side occurs before it reaches the asset to be cooled, and the '​Hot'​ side occurs //after// the asset to be cooled, but before the water is brought back to ambient temperature again.  +In a hydraulic closed systems, you can have a '​Hydraulic Supply'​ and '​Hydraulic Return'​ relationship,​ which then clearly marks if the oil within the hydraulic line is travelling //to where it is used//, or //from where it has been used//.
- +
-Similarly for hydraulic closed systems, you can have a '​Hydraulic Supply'​ and '​Hydraulic Return'​ relationship,​ which then clearly marks if the oil within the hydraulic line is travelling //to// where it is used, or //from// where it has been used.+
  
 ===Similar Relationships=== ===Similar Relationships===
Line 27: Line 39:
 If you have these relationships,​ try to ensure that you have **common words** between the various relationship names. ARDI will use this as a hint that they are related, and will in some places offer extra navigation hints based on this fact. If you have these relationships,​ try to ensure that you have **common words** between the various relationship names. ARDI will use this as a hint that they are related, and will in some places offer extra navigation hints based on this fact.
  
-Ie. if you reach the end of the //coarse ore// relationship in a [[ardiuserguide:​diagram|diagram]],​ you'll be shown any //Granulated Ore// relationships,​ as these might indicate a point where your ore has changed state. ​+Ie. if you reach the end of the //coarse ore// relationship in a [[ardiuserguide:​diagram|diagram]],​ you'll be shown any //granulated ore// relationships ​that are present, as these might indicate a point where your ore has changed state. ​ 
 + 
 +===Administering Properties=== 
 + 
 +See the article [[Managing Relationships]] to see an example of how new relationships are created, existing relationships are edited, and useless ones removed.