---
title: "Material Readiness for Shipyard Work Packages | Veldarium"
canonical: https://www.veldarium.com/use-cases/material-readiness
html: https://www.veldarium.com/use-cases/material-readiness
description: "Determine whether the correct material for a work package is physically present and accepted at receipt. Ordered, or in stock on paper, does not count."
last_updated: 2026-10-12
representation: registry-derived Markdown
---

# Material readiness

> Determine whether the correct material for a work package is physically present and accepted at receipt. Ordered, or in stock on paper, does not count.

## What happens

Critical material does not arrive, or arrives on hold. The area loses executable work while labor and access windows keep running.

### The chain

1. **Receipt lands with a hold** (record): Two of the nine spools are in stores, made to the revision Rev D supersedes. ERP counts what was purchased and landed, which is not the same as usable at the revision that governs this work.
2. **The kit is checked against the package** (record): The material gate reads open for WP-019. Bought, landed, reserved and accepted are four different facts in three different systems.
3. **Executable work disappears** (work): The work planned for the shift and the work the yard can physically do stop being the same list, and only one of them is on the schedule.
4. **Labor and access strand** (physical): A crew and a released access window in zone MS-03 are both committed to work that cannot start, and both are consumed whether or not it does.
5. **Material control dispositions** (decision): Accept, substitute, or resequence. Production then re-releases against the material that is actually there.

**What it costs:** A crew can be blocked, install the wrong material, or close work without the evidence that the material was accepted.

A kit can read complete in one system and be short on the floor. Items are received but not accepted, accepted but re-specified by a change, or present but held for a certificate. The work package inherits the shortfall without warning.

## How VeldBuild answers it

**Question:** Is the WP-019 kit complete and accepted, or short at receipt?

- **Scope:** The material kit for one work package, governing revision, physical location, receipt lot, certificate set, and applicable discrepancies.
- **What it reads:** Work-package material kit; Purchase and receipt records; Receipt acceptance and discrepancy state; Material certificates and evidence; Change notices that re-specify material. Evidence it needs: Receipt and acceptance records; Discrepancy records; Material certificates; Kit-to-work-package linkage.
- **What it computes:** Distinguish ordered, received, physically located, and accepted state; Check quantity, specification, lot, certificate, discrepancy, and revision applicability; Never treat receipt as acceptance. Output: Accepted or short, item by item: what is held, why, and the revision each item must clear against.
- **Left unknown:** Missing certificate or lot trace; Unestablished physical location; Unresolved discrepancy or revision applicability
- **Decided by:** VeldBuild reports the accepted-material state; it does not accept material or clear a discrepancy; Material control owns receipt acceptance and disposition (ERP purchase and receipt transactions; Receiving and material-control acceptance; Quality disposition; Engineering material specification)
- **Status:** Synthetic. Demonstrated as a readiness gate on VS-001 (2 of 9 spools short). Live ERP and receiving connectors are planned.
- **What would prove it on real records:** Reconcile a live ERP, receiving, and quality slice against floor-verified kits and reviewed material-control dispositions.

**Next:** [See why ERP cannot answer this](https://www.veldarium.com/systems#integration). Each source system stays authoritative for its own fragment: ERP for what was purchased, receiving for what landed, quality for what is accepted. The integration map shows which of them may establish a claim and which may only bear on it.

## 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)