Skip to main content

Nested maps

Nested maps display assets as hierarchical blocks computed from relationships in the inventory.

Use them when you want to reveal containment, hierarchy, or dependency paths that already exist in the knowledge base.

Use a nested map when the hierarchy itself is the message. If the goal is freeform explanation or workshop discussion, a diagram is usually better.

Principle​

A nested map organizes assets in successive levels, each level being visually contained in the previous one.

Typical example:

Business Capability
└── Functional Domain
    └── Process
        └── Application

Unlike a manually drawn hierarchy, a nested map is generated from rules:

  • which root asset type to start from
  • which relationships to follow
  • in which direction to traverse them
  • which filters to apply at each step

That means the quality of the result depends mostly on the quality of the relationships in the inventory.

Access​

  1. Click "Nested Maps" in the navigation
  2. The catalog displays on the left
  3. Select an existing map or create a new one

Create a nested map​

  1. Click "+" in the catalog
  2. Select "New nested map"
  3. Configure the root and traversal rules
  4. Name and save

Configuration​

Root asset type​

Select the asset type that will act as the top level of the map.

Traversal rules​

Traversal rules tell Boldo how to move from one level to the next.

For each level, define:

  • the target asset type
  • the relationship to follow
  • the direction to use

Filters​

You can apply filters at every level of the map.

Those filters can target:

  • attributes
  • properties
  • relations

They can also be combined with logical operators such as and or or.

What nested maps are best for​

Nested maps are especially useful when your data already forms a meaningful hierarchy, for example:

  • capability to process to application
  • domain to sub-domain to application
  • zone to sub-zone to component
  • organization to team to responsibility

They are less useful when the relationships do not form a stable hierarchy.

Display​

Nested maps display:

  • parent blocks
  • child blocks nested inside them
  • colors based on asset type or selected logic

This makes them useful for large structural patterns that are hard to read in a diagram or table.

Use cases​

NeedConfiguration
Capability mappingCapabilities → Domains → Applications
Organizational viewDepartments → Teams → Responsibilities
Technical architectureZones → Sub-zones → Components
Value chainMacro-processes → Processes → Activities

Export​

Use the download action when you need the map as an image. The exported file is an image.

Best practices​

  • limit the number of levels for readability
  • filter the roots when the top level is too large
  • use relationships that make business sense
  • use colors to add a second reading dimension