Problem at Hand:

The current mapping in Harness does not align with the hierarchy used on the NAB side.

Ideally:

Harness “Organisation” should align with NAB CIOs

Harness “Projects” should align with NAB Domains

However, over time, the NAB hierarchy (NAB → CIO → Domain → Service) has drifted out of sync with how it is represented in Harness (NAB → Orgs → Projects → Services).

Proposal

We attempted to use System Entities to replicate NAB’s hierarchy inside Harness:

Created one System Entity for CIO

Created another System Entity for Domain

Differentiated the two using tags

The goal was to link Domain as a child of CIO

The challenge:

We are currently unable to display Domain entities under a CIO in a tabular format, even though we have linked Domain system to CIO system.

We already have reliable mapping at the service level.

So during service ingestion, we can:

Map each service to its corresponding Domain (System)

Map each service to its corresponding CIO (System)

This effectively reconstructs the true NAB hierarchy inside Harness without relying on the “Hierarchy” construct