# Digital Thread and Genealogy

Canonical URL: https://babadook.tech/modules/maxacor-digital-thread-genealogy
Entity: modules
Content hash: e53039ed4260330da86a144f95531475ef024083c20d250d193dc02f06ec357b

Trace a physical outcome back through the part, software, workflow, telemetry and evidence that produced it.

A field failure appears months after deployment. One investigation moves from the affected serial number to its CAD revision, installed controller, software rollout, telemetry and maintenance history without losing the original evidence. Each source system retains its records; MAXACOR owns the evidence-bearing physical correlation between them.

## When it matters

A field failure appears months after deployment. One investigation moves from the affected serial number to its CAD revision, installed controller, software rollout, telemetry and maintenance history without losing the original evidence.

### data Viz

### data View

section: module-scene

### Section 1

col Title: CAD, BOM and Runtime Binding

col Cont: An engineer clicks a part in the model and reaches every deployed unit, controller and workflow that depends on it. Engineering change impact reaches the floor before the wrong configuration runs.

### Section 2

col Title: Configuration Drift

col Cont: A staged software wave changes behavior on one cohort while another remains on the previous build. Operators see which outcome belongs to which configuration and rollout wave.

### Section 3

col Title: Genealogy and Transformation Trace

col Cont: A defect appears in one finished assembly and the graph reveals every contributing lot and sibling output. Quality teams can bound investigation and recall populations without guessing.

## Digital Thread and Genealogy

data View: maxacor-digital-thread-genealogy:submodules

### CAD, BOM and Runtime Binding

desc: Connect design objects and BOM revisions to installed units and runtime behavior.

link: /sub-modules/maxacor-cad-bom-runtime

### Configuration Drift

desc: Detect when accountable hardware, software or policy no longer matches the approved physical configuration.

link: /sub-modules/maxacor-configuration-drift

### Genealogy and Transformation Trace

desc: Track how materials and assemblies split, merge, transform, quarantine and become final units.

link: /sub-modules/maxacor-genealogy-trace

## CAD, BOM and Runtime Binding

action: Connect design objects and BOM revisions to installed units and runtime behavior.

mechanism: An engineer clicks a part in the model and reaches every deployed unit, controller and workflow that depends on it.

workflow role: An engineer clicks a part in the model and reaches every deployed unit, controller and workflow that depends on it.

operational outcome: Engineering change impact reaches the floor before the wrong configuration runs.

maturity: specified

evidence: MAXACOR Part 3, §§11–15.

### Section 1

Operations team

### Section 2

Engineering team

### Section 1

Qualified physical state

### Section 2

Current work context

### Section 1

Evidence-bearing operational disposition

### Section 1

MAXACOR is not a CAD or PLM authoring system.

## Configuration Drift

action: Detect when accountable hardware, software or policy no longer matches the approved physical configuration.

mechanism: A staged software wave changes behavior on one cohort while another remains on the previous build.

workflow role: A staged software wave changes behavior on one cohort while another remains on the previous build.

operational outcome: Operators see which outcome belongs to which configuration and rollout wave.

maturity: specified

evidence: MAXACOR Part 3, §§11–15.

### Section 1

Operations team

### Section 2

Engineering team

### Section 1

Qualified physical state

### Section 2

Current work context

### Section 1

Evidence-bearing operational disposition

### Section 1

Build and deployment provenance remain with Haephestus.

## Genealogy and Transformation Trace

action: Track how materials and assemblies split, merge, transform, quarantine and become final units.

mechanism: A defect appears in one finished assembly and the graph reveals every contributing lot and sibling output.

workflow role: A defect appears in one finished assembly and the graph reveals every contributing lot and sibling output.

operational outcome: Quality teams can bound investigation and recall populations without guessing.

maturity: specified

evidence: MAXACOR Part 3, §§11–15.

### Section 1

Operations team

### Section 2

Engineering team

### Section 1

Qualified physical state

### Section 2

Current work context

### Section 1

Evidence-bearing operational disposition

### Section 1

Genealogy does not manufacture supplier or enterprise truth.

## Relationships

### products

- MAXACOR — https://babadook.tech/products/maxacor

### sub modules

- CAD, BOM and Runtime Binding — https://babadook.tech/sub-modules/maxacor-cad-bom-runtime
- Configuration Drift — https://babadook.tech/sub-modules/maxacor-configuration-drift
- Genealogy and Transformation Trace — https://babadook.tech/sub-modules/maxacor-genealogy-trace