Glossary · Backbone

    Engineering Backbone: the Single Source of Truth for Hardware Teams

    An engineering backbone is the spine of typed entities and relationships that every other tool federates around. This page is the architecture reference, what the backbone owns vs what federates, the cost ledger of drift when there is no backbone, and how it differs from a data warehouse or a data lake despite the overlapping marketing language.

    What the backbone owns vs what gets federated

    A backbone is not the system that holds everything. It is the system that holds the structure: typed entities, identifiers, relationships, lifecycle states, cryptographic baselines. The leaf payloads, CAD files, test rigs, MES traveler data - stay where they are, owned by the tools that produced them. The backbone holds the spine; everything else federates around it through four predictable patterns.

    01

    Owned by the backbone

    Typed identifiers · relationships · lifecycle · baselines · audit trail

    Requirement.id, Component.partNumber, the bidirectional verifiedBy edge between them, the lifecycle state (Draft / Reviewed / Released / Obsolete), the cryptographic baseline that includes them at v1.2.

    02

    Federated by reference

    CAD geometry · firmware binaries · large test datasets

    The CAD vault keeps the .STEP file. The backbone holds Component.geometryUri → vault://creo/rev/B412. When a baseline freezes, the URI is captured immutably; the file content is fetched from the vault on demand.

    03

    Materialized read-only

    Computed rollups · coverage matrices · audit packs

    Mass rollup, requirement coverage %, certification readiness, recomputed live on the graph, exposed as materialized read-only views. Engineers and AI agents query them; no one writes them by hand.

    04

    Event-driven sync

    ERP MBOM ↔ engineering BOM · MES asBuilt ↔ asDesigned

    When the backbone changes an EBOM line, an event publishes to your MES; the MBOM acknowledges. AsBuilt records flowing back become typed events the backbone records as state transitions.

    The drift-cost ledger

    Concrete failure modes from the patchwork-of-tools approach, with order-of-magnitude cost. Each is structurally impossible against a typed backbone.

    Scenario
    How drift happens
    Typical cost
    Broken VLOOKUP in mass budget
    Spreadsheet BOM maintained manually. A row insertion shifts a VLOOKUP target by one cell. Mass total reads wrong by 7% for 3 weeks before someone catches it at design review.
    €20-60k rework, 1 baseline reissue
    Requirement edited, test plan not
    Systems engineer revises SR-128 acceptance criterion in the RM tool. The test plan in the ALM tool still references the old criterion. Test passes; product fails customer acceptance.
    €50-250k field rework
    Three baselines disagree
    ‘Baseline v2.1’ in the PLM = mechanical only. ‘Baseline v2.1’ in the RM tool = requirements only. ‘Baseline v2.1’ on the shared drive = whatever someone zipped that day.
    2-6 weeks audit reconstruction
    Supplier qualification orphaned
    Component switches from supplier A to B. Procurement system updates. Engineering qualification record still points to A. Six months later, an audit finds B used without qualification on file.
    Audit non-conformity, possible recall
    AsBuilt diverges from AsDesigned
    MES allows minor deviation at production. Deviation flagged in MES but never propagated to engineering. Field issue investigation hits a configuration that doesn't match any design baseline.
    Days to weeks per investigation
    Integration test caught at validation, not design
    Mechanical chose 80 mm. Firmware chose 75 mm. Both correct in their tool. Issue surfaces at integration, 4 months and €200k after the divergent decisions.
    10× the design-time fix cost

    Backbone vs warehouse vs lake

    Three data architectures get pitched as "single source of truth". They are not the same category. Only one carries the engineering structure.

    Property
    Data warehouse
    Data lake
    Engineering backbone
    Primary purpose
    Analytics, known questions, fixed schema.
    Storage, raw payloads, schema-on-read.
    Operational engineering substrate, typed, queryable, computable.
    Schema discipline
    Strict at write time, but business-analytical (fact tables, dimensions).
    Loose. Each consumer guesses at the structure.
    Engineering-semantic: Requirement, Component, Test, Baseline, RiskItem, with constraints validated on every write.
    Write authority
    Periodic ETL from operational systems.
    Anyone with credentials drops anything.
    Engineers and AI agents write through scoped, audited APIs. The graph rejects malformed writes.
    Versioning model
    Slowly-changing dimensions or snapshots.
    Versioning depends on naming convention.
    Cryptographic baselines (Merkle-tree). Replay any past state.
    What audit gets
    Analytic exports. Not the artifacts.
    Files. No structural guarantees.
    Design History File, lifecycle data items, CDE delivery, generated from the graph at the baseline asked for.
    AI agent surface
    SQL views on derived data.
    Raw payloads, agents must rebuild structure.
    MCP-native API over typed entities, agents act with scoped, auditable permissions on the live graph.

    The five engineering primitives the backbone makes load-bearing

    01

    Typed identifiers

    Requirement.id, Component.partNumber, Test.testId, guaranteed unique, never recycled, never reassigned. The audit trail can resolve any reference 20 years later.

    02

    Typed relationships

    verifiedBy, derivesFrom, integratesInto, hasRiskControl, relationships are first-class with their own constraints. The schema can validate ‘a Requirement must have at least one verification’.

    03

    Lifecycle states with transition rules

    Draft → Reviewed → Released → Obsolete. State transitions require approvers, leave audit records, propagate to dependent entities. State is not a label; it is a contract.

    04

    Cryptographic baselines

    Content-addressed snapshot of the typed graph at freeze time. Replay deterministic, tamper-evident, fork-able. The historical record of every engineering decision.

    05

    Computable views

    Coverage matrices, mass rollups, risk dashboards, certification readiness, computed on the live graph, materialized read-only. The view is always consistent with the source.