Hierarchy Map Prior V5.2

Hierarchy Maps provide a management consumable format to visualize data being always in sync with realtime data.

This article describes all relevant aspects to utilize the hierarchy map feature of Designer:

 

Hierarchy Maps provide a management consumable format to visualize data. Typical Hierarchy Maps are Org Charts, Capability Maps, Service Maps etc.

Building-Hierarchy-Map

Designer provides a flexible way to create Hierarchy Maps visualizations on any table. This feature processes the underlying data in the following way:

  • Shows parent/child relationships (hierarchical data) as nested containers by hiding the connections visually.
  • Includes elements connected via downstream m2m relationships (CI relationships) within the container by hiding the connections visually.
  • Shows elements connected via upstream m2m relationships (CI relationships) by keeping the connections visually.
  • Keeps flexibility to change shape styling and positioning.
  • Supports any other feature e.g. Realtime Indicators.

Creating a Hierarchy Map

In order to create a hierarchy map follow these instructions:

A – Click the INSERT ribbon.
B – Click the ‘Hierarchy Map’ Icon.

hierarchy_map_ribbon

Configuring the Hierarchy Map

The following settings form shows the different options to create the Hierarchy Map:

Designer_Hierarchy_Map_Settings

A — Select Layout Type for the Hierarchy Map


There are 3 different types of layouts you can select from:
1. Traditional
The traditional hierarchy map type will keep the original styling from the class definition table. In the example below the Business Capabilities are using the UPM·X shapes including icons, label with table name, and the name of the Business Capabilities.

2. Compact
The compact hierarchy map type keeps the icon of the shape if available, but removes the table name label. Additionally, it scales down the shape size to 170x46 pixel to provide a more compact view of the hierarchy map.

3. Text Only
The text only hierarchy map type removes any shape icon and table name label. The shape size is scaled down to 160x40.

Leveraging the Text Only Hierarchy Map

Be aware, that the Text Only Hierarchy Map consumers will not directly see the type or table name of the shapes. Ideally, only use one type of objects e.g. Business Capabilities to make the diagram consumable.

Designer_Hierarchy_Map_Types

B — Select Orientation of the Hierarchy Map


The Orientation is influencing the layout and positioning of the shapes within the containers.
1. Autofit
Designer will try to make the full diagram fit by orienting all containers and shapes into a single page.

2. Vertical
The Vertical orientation will ensure, that the containers are oriented from top to bottom. Change the number of columns to influence the amount of shapes per line.

3. Horizontal
The Horizontal orientation will ensure, that the containers are oriented from left to right. Change the number of columns to influence the amount of shapes per line.

Designer_Hierarchy_Map_Orientation

C – Select the ‘Target Table’ which indicates the starting point and basis of the hierarchy map. E.g. if you want to create a map where applications are grouped by capability, select Business Capabilities here. The capabilities will be shown hierarchical. If a hierarchy (parent/child relationships) does not exists, elements will be shown as single containers including related items within the container.

D – Select the number of levels the capability map should include. Maximum 10 levels are supported.

Based on the level depth and number of relationships the creation of the Hierarchy Map can take up to multiple minutes. Use the ‘Include Tables’ and ‘Include Relationships’ options to minimize the query time.

E — This area shows the selected and total number of elements. Once the target table is selected (see point C) you can see the data available. Increase the number of levels (see point D) and selected the required entries (see point F).

F — Select the parent's and child's to be included and unselect those to be excluded.

G – The ‘Include Table’ option provides the ability to exclude all other tables except the selected ones. E.g. selecting Business Applications will show them as part of the selected Target Table (see point C). All other tables except Business Applications will be ignored.

Showing only a single object type

Selecting the same table for both Target Table and Include Table will provide you a hierarchy map excluding all other object types. E.g. selecting Business Capabilities for Target and Include Table will show a Business Capability Map without any other tables.

H – The ‘Include Relationships’ option provides the ability to exclude all other suggested relationship types except the selected ones.
In the example above Business Capabilities connected to Business Applications and/or Strategies only connected via the suggested relationships ‘impacts::impacted by’ and ‘Provided by::Provides’ will be shown—all other relationship types will be ignored.

Use this option to filter the view for specific suggested relationship types.
Leave this option empty to include all relationship types.
Combine this option with the ‘Target Tables’ option to further restrict the query to selected target tables.

I – Any global and personal filters defined can be selected here to restrict the content of the hierarchy map.

J – Turn on the ‘Elements with Relationships Only’ option to remove any Target Table elements, which do not have m2m relationships to any other elements.
Turn off this option to show elements, too which does not have any upstream or downstream related items.

K – Turn on the 'Show Upstream Elements As Container' to visualize connected upstream elements as containers.
Turn off this option to show upstream elements based on the Class Definition shape styling and its relationship.

Designer_Hierarchy_Map_Show_Upstream_Elements_as_Container

Upstream Elements as Container

Using this option can multiply number of containers if the upstream element is connected to multiple Target Table elements.

Applying Realtime Indicators

The Hierarchy Map Settings allows to apply quickly Realtime Indicators. These settings can be saved for quick reuse.

Designer_Hierarchy_Map_Settings

L — Select the table to apply a realtime indicator to.

M — Select the field.

N — Select where the realtime indicator should be shown on the shape e.g. background, border etc.

O — You can see the applied realtime indicators in this area. Click the X icon to remove an indicator.

 

Saving & Loading Hierarchy Map Settings

Hierarchy Map settings can be saved for quick reuse including realtime indicator settings. Additionally, the hierarchy settings can be used as part of the presentation mode to render the hierarchy map live every time you visualize it in the presentation mode without saving the diagram.

P — Shows the available saved hierarchy map settings. Click to load the settings.

Q — Once settings are saved and selected, additional options to rename and delete are available:

Designer_Hierarchy_Map_Settings_OptionsDesigner_Saving_Hierarchy_Map_Settings

S — After the layout and main settings of the hierarchy are set, the save button is enabled. Click the save button and enter a name for the settings. The settings name will be shown under point P.

 

Realtime Rendered Hierarchy Maps

R —Once settings are saved (see point S) you can copy a special link for the presentation mode, which renders a diagram with the settings in real-time including the realtime indicator settings. This way you can ensure, that the hierarchy map is always 100% updated and in alignment with your live data in the presentation mode.

Updating Hierarchy Maps

Only Realtime Rendered Hierarchy Maps are completely rebuilding the full hierarchy map in the presentation mode.
Hierarchy Maps created and saved as a diagram will not update automatically. Only realtime indicators are updating automatically.