---
title: "Engineering Change Impact in Shipbuilding | Veldarium"
canonical: https://www.veldarium.com/use-cases/change-impact
html: https://www.veldarium.com/use-cases/change-impact
description: "Engineering change management, followed past the drawing: when a configuration change is released, trace it to the work, material, inspection and schedule it actually affects. Mark honestly what cannot be traced."
last_updated: 2026-10-12
representation: registry-derived Markdown
---

# Change impact

> Engineering change management, followed past the drawing: when a configuration change is released, trace it to the work, material, inspection and schedule it actually affects. Mark honestly what cannot be traced.

## What happens

A design revision lands after fabrication has started. Material, work packages, inspections and the next blocks may all inherit it.

### The chain

1. **The route is re-released** (record): CFG-029 moves DR-118 from Rev C to Rev D on the seawater-cooling route, while the crew is at the bench.
2. **The reach is traced** (record): Every governed object related to the drawing family becomes a candidate. Related-with-no-assessment is its own state, never a quiet "unaffected".
3. **Released work is re-evaluated** (work): Two objects it reaches are affected and must be re-evaluated before release (work package and material). One is known not affected, because an assessment cleared it. One has no assessment and stays impact not established.
4. **Steel is already cut** (physical): Material cut to Rev C is either still good or is rework, and nothing at the bench looks different either way.
5. **Configuration authority decides** (decision): What proceeds, what is re-released at Rev D, and what comes back out. The impact set is evidence for that call, not the call.

**What it costs:** A superseded definition can reach material, fabrication, inspection, or schedule before its downstream consequence is recognized.

A revision changes on one drawing and the consequence scatters. The routed work package, the material kit specified against the old revision, and the inspection criteria all move. Nothing walks the change to those objects, so the yard learns the impact when a part does not fit.

## How VeldBuild answers it

**Question:** What did CFG-029 affect? And what did it explicitly not affect?

- **Scope:** The declared Build Graph neighborhood of one change: affected configuration objects, work packages, material, inspections, and schedule dependencies.
- **What it reads:** Engineering change notice and revision lineage; Work packages written against the affected object; Material specified at the prior revision; Inspection and acceptance criteria; Downstream schedule dependencies. Evidence it needs: Change notice; Revision lineage and supersession edges; Affected work-package references; Affected material and inspection records.
- **What it computes:** Follow the change to everything it is declared to touch; Call nothing affected or not affected without evidence; Keep an unmodeled or unverified relation as impact not established. Output: What the change reaches, what it does not, and what nobody has assessed yet, each with an owner.
- **Left unknown:** An unmodeled dependency; Missing applicability or effectivity evidence; An affected object without completed disposition evidence
- **Decided by:** VeldBuild reports affected, not affected, and impact-not-established; it does not invent a relation it cannot trace; Engineering dispositions the change and everything it leaves unresolved (Configuration control; Engineering release authority; Supply and material control; Quality and production planning)
- **Status:** Synthetic. Change impact demonstrated on synthetic VS-001 records (CFG-029), with a defined evaluation. Live PLM connectors are planned.
- **What would prove it on real records:** Run it against a controlled slice of real PLM dependencies and measure, on reviewed changes, what it found, what it missed, what it left open and how dispositions closed.

**Next:** [Inject the change and watch it travel](https://www.veldarium.com/veldbuild#loop). The build graph on VeldBuild takes CFG-029 as an input. Select an object, introduce the revision, and see which released work survives it and which does not.

## Contact

To discuss a first VeldBuild deployment, or the company: [chris@veldarium.com](mailto:chris@veldarium.com). Name the release decision your team rebuilds by hand. Do not send confidential information in the first message.

## Sitemap

- [Full site map](https://www.veldarium.com/sitemap.md)
- [Machine context](https://www.veldarium.com/llms.txt)