[bok-callout]Relation & Relation Type

A Relation defines how two Assets are related to each other. A Relation is an instance of exactly one Relation Type.

A Relation Type formally defines the type of a relation between two Asset Types. A Relation Type is bidirectional: going from the header asset (source) to the tail asset (target) of the relation and the other way around. The source and target of a relation are both asset types.

For example:

• An example of a relation type is Data Asset is parent of/is child of Data Asset. The source and the target of this relation type are both asset type Data Asset. One direction, from source to target, reads Asset Type is parent of Asset Type. The other direction, from target to source, reads Asset Type is child of Asset Type. This relation type thus allows Asset Types to have children of the same type. The following figure gives a visual representation of the different concepts and their relations.
• an asset with name ‘Customer’ and an asset with name ‘CRM’ are related to each other through a relation “CRM is system of record for / has system of record Customer has system of record”, where ‘CRM’ the header asset and ‘Customer’ the tail asset  respectively..
• “CRM is system of record for / has system of record Customer has system of record” is an instance of Relation Type “Technology Asset is system of record for / has system of record Business Term”.

[/bok-callout]

Following table contains the out-of-the-box relation types.