Key concepts

The National Digital Twin (NDT) framework is depicted as seven concentric circles, each representing a coherent layer of concern. From the outermost ( technical) to the innermost (most technical), these are:

1. Information Quality Management
This topmost circle addresses how organizations ensure that data shared across the NDT is “fit for purpose.” It encompasses governance structures, defined roles and responsibilities, training programs, and performance measurement against information-quality KPIs. Everyone in the organization—regardless of role—contributes to and benefits from these practices.

2. Information Requirements Specification
A process-model-based methodology defines exactly what information is needed to support decision-making within business processes. By translating questions such as “What historical data is required to forecast maintenance?” into precise requirements, this layer ensures that the right data reaches decision makers at the right time.

3. Integration Architecture (IA)
The IA circle develops secure, managed data-exchange protocols. All exchanges reference the RDL and FDM layers beneath it, guaranteeing that every transfer conforms to the NDT’s shared technical standards.

4. Reference Data Language (RDL)
RDL forms the “vocabulary” of the NDT, comprising an evolving ecosystem of IMF-compliant libraries. Each library defines standard terms (e.g., “valve,” “sensor”) and links them to entities in the FDM, enabling semantic interoperability.

5. Foundation Data Model (FDM)
Built on a top-level ontology, the FDM provides the “grammar” that ensures consistent data definitions across systems. It underpins IA protocols and RDL libraries, serving as the structural backbone for digital-twin communications.

6. Top-Level Ontology (TLO)
The TLO defines the most abstract categories (such as “Thing” and “Class”) and fundamental relationships (membership, whole-part, specialization). Unique to the NDT, it adopts a four-dimensional view—treating entities as extending in both space and time—which is applied consistently across the upper five circles.

7. Core Constructional Ontology (CCO)
At the core, the CCO formalizes the abstract building blocks—parts, sets, and tuples—that underpin the TLO’s categories and relationships. Only a small group of specialized experts work here, but their efforts ensure that the entire stack is extensible and domain-agnostic.

Mechanisms

Data and requirements flow bidirectionally through the seven layers:

• Governance and Quality Assurance
  Information Quality Management defines policies, roles, training, and KPIs to make sure that every piece of data entering the NDT meets organizational standards.

• Requirements Engineering
  Information Requirements Specification captures decision-support needs by mapping business processes to data elements, ensuring clarity before technical implementation begins.

• Secure Exchange
  Integration Architecture prescribes APIs, message formats, validation rules, and security controls, all built upon the semantics of the RDL and structure of the FDM.

• Semantic Standardization
  Reference Data Language libraries codify domain terms, while the Foundation Data Model embeds those terms within a formal ontology, creating a shared semantic framework.

• Ontological Foundations
  Top-Level Ontology experts articulate core categories and relationships in four dimensions, and Core Constructional Ontology specialists define the mathematical notions (parts, sets, tuples) that give rise to those abstractions.

Examples

• A local authority introduces an information-quality dashboard, mandates quarterly training on data entry, and tracks KPI improvements—resulting in a measurable uplift in data accuracy.

• A utilities operator applies process-model analysis to its maintenance workflows, identifying specific data needs (e.g., pipe-failure histories) that reduce unplanned outages.

• Two agencies implement an IA-compliant API, exchanging real-time sensor data structured against a shared FDM schema.

• Multiple infrastructure partners adopt a standardized RDL library, harmonizing terms like “pipeline” and “sensor” to enable cross-organizational analytics.

• Engineers use the four-dimensional TLO to model a bridge’s components with spatial coordinates and temporal attributes (installation, inspections, repairs).

• An ontology working group formalizes a tuple structure linking physical assets, control systems, and environmental data.

Further reading

• British Standards Institution, PAS 1192-3 & PAS 1192-6: Guidance on information management in digital built environments

• UK BIM Framework, Digital Twin Primer: Introductory overview of principles and standards

• ISO 19650 series: International standards for life-cycle information management of built assets

• Gibb, A., & Isikdag, U., A Framework for Future Smart Infrastructure: Examination of large-scale digital twins

• Smith, B., & Welty, C., OWL Web Ontology Language Guide: Foundational concepts for top-level ontologies

• OMG, Unified Foundational Ontology (UFO): Advanced four-dimensional modeling techniques