The Agnostic Model Foundation
The Configurator is the per-project definition of how each vendor's resources map into the agnostic model. It is the single place that governs naming, typing, and structure — making the platform work identically across all supported vendors.
Core Concepts
Agnostic Model
Vendor-neutral representation of resources and their relationships. One design and one view work across all vendors.
Skeleton
Structural template of the tree: node types, disciplines, and parent-child rules that frame where resources belong.
Transformer
Converts resource data between vendor-specific and agnostic forms in both directions.
S2A — Specific → Agnostic
The discovery direction. Vendor resources are read and translated into the agnostic tree.
A2S — Agnostic → Specific
The deployment direction. An agnostic design is translated into vendor-specific resources.
Per-Project Config
The configurator is selected per project. Each project can have its own mapping and hierarchy rules.
Role & Access Configuration
The Configurator also manages the identity-to-role mapping and tool access rules for each project.
IDG → Roles
Maps identity provider groups to IANC roles. Controls which role a user gets on login per project.
Tool Registry
Defines which tools are available per role. Tree, Finance, and Configurator access is role-scoped.
Role Hierarchy
Roles follow a hierarchy — a higher role inherits access to all tools of lower roles automatically.