Skip to main content

0002 - Engineering Knowledge Graph

Status​

Accepted

Date​

2026-07-19

Context​

Engineering knowledge is typically distributed across specialized tools such as Requirements Management, MBSE, Test Management, Risk Management and Project Management.

Each tool maintains its own data model and relationships.

As a result, engineering knowledge becomes fragmented, difficult to trace and expensive to maintain.

ATON requires a single, technology-independent representation of engineering knowledge.

Decision​

ATON shall represent all engineering knowledge as a versioned Engineering Knowledge Graph.

The graph consists of:

  • Artifacts
  • Relations
  • Versions

Reviews and Baselines provide governance over the graph.

Every capability contributes to the same shared Engineering Knowledge Graph.

Rationale​

A shared graph

  • eliminates isolated data models
  • enables end-to-end traceability
  • allows cross-domain queries
  • provides a common foundation for all engineering capabilities

The Engineering Knowledge Graph is independent of persistence and implementation technology.

Consequences​

Positive​

  • Unified engineering model
  • Consistent traceability
  • Extensible architecture
  • AI can reason over one shared graph

Negative​

  • Requires a well-defined Kernel Domain Model
  • Graph consistency becomes a core responsibility of the Kernel

Notes​

The Engineering Knowledge Graph is the central data model of the ATON Engineering Operating System.