Create a hierarchy model to define hierarchy relationships between code lists. Later, you can add code values from the code lists to define hierarchy relationships.
To create a hierarchy model, perform the following actions:
1Create a hierarchy asset.
2Define the hierarchy model.
3Assign stakeholders.
Step 1. Create a hierarchy
Create a hierarchy and configure the general properties and status.
Note: You must be assigned the Planner role to work with hierarchies. For more information, see Users, groups, and roles.
1Click New and select Hierarchy.
The New Hierarchy page appears and displays the Summary tab.
2Enter a name for the hierarchy.
3 Optionally, complete the general properties fields.
Note: The domain, confidentiality, and priority are inherited by code lists in the reference data set.
Field
Description
Version
The version information of the hierarchy.
Description
A description of the hierarchy.
Application
The source application of the hierarchy.
Domain
An area or grouping to describe the hierarchy.
Confidentiality
The confidentiality level of the hierarchy.
Priority
The priority of the asset. The priority levels are critical, high, medium, and low.
Status
The state of the asset in the life cycle.
Effective Date
The date from when the status is effective.
Note: You can't type a date. To select or modify a date, use the Calendar icon. To clear the selection, click the Remove icon.
Approved by
The user who approved the asset.
Approved on
The date of approval.
Note: You can't type a date. To select or modify a date, use the Calendar icon. To clear the selection, click the Remove icon.
Note: If you do not see options in some lists, configure your system reference data values. For more information, see Adding values to system reference data.
4Click Save.
The Definition tab appears and displays an undefined node in the Hierarchy Designer.
Step 2. Define the hierarchy model
Define the top level node and then add child nodes to the hierarchy model. You can add flat and hierarchical code lists as nodes to different levels of the hierarchy model. For example, you might define the Enterprise Regions code list as the top level node. Then you create a relationship from the Enterprise Regions code list to the Enterprise Country Codes code list.
The following video shows you how to define the hierarchy model:
1In the Properties panel, select a code list as the top level node for the hierarchy model.
The undefined node name is replaced with the code list you selected.
2In the Hierarchy Designer, hover over the node and click Add Child.
A child node appears in the Hierarchy Designer.
3In the Node field, select a code list to create a relationship.
The following image shows a relationship from the top level node to the child node:
The undefined node name is replaced with the code list you selected.
4Optionally, add additional child nodes.
5Click Save.
Step 3. Assign stakeholders
Assign stakeholder roles to users who play a role in using, creating, or maintaining the asset. Stakeholder roles determine a user's privileges for the asset.
When a user manages an asset as a stakeholder, they have the combined privileges provided by their stakeholder role and their Reference 360 role. For more information about stakeholder roles, see Stakeholder roles. For more information about assigning roles, see Guidelines for assigning roles.
The following video shows you how to assign stakeholders:
1Click Stakeholders.
The Stakeholder tab opens.
2Click Add.
A list appears in an empty row.
3In the Role list, select a stakeholder role.
The New Stakeholder dialog box appears.
4Select a user name and click Add.
The user name of the stakeholder appears in the row.
