---
title: "Shipyard Production Status, Block by Block | Veldarium"
canonical: https://www.veldarium.com/use-cases/production-state
html: https://www.veldarium.com/use-cases/production-state
description: "Represent what is actually complete, underway, waiting or unknown across a block, so the vessel is never assumed further along than its least-ready section."
last_updated: 2026-10-12
representation: registry-derived Markdown
---

# Production state

> Represent what is actually complete, underway, waiting or unknown across a block, so the vessel is never assumed further along than its least-ready section.

## What happens

A crane, workcell, or trade loses capacity. Block sequence and quay timing must change without hiding the new bottleneck in percent-complete.

### The chain

1. **A capacity source drops** (record): The robotic structural weld cell is out. Nominal capacity and schedulable capacity part company, and only one of them is in the plan.
2. **Percent-complete stops helping** (record): An average over a block cannot say which joint is waiting and which is accepted. Reported progress and physical progress diverge without any record being wrong.
3. **The bottleneck moves** (work): Work that was not binding becomes binding. The queue re-forms somewhere the plan was not watching.
4. **Block order and quay timing change** (physical): Erection sequence shifts, and the berth date shifts with it. The whole consequence started as one unavailable cell.
5. **Production control resequences** (decision): Against the capacity that exists rather than the capacity on the plan, with the new binding constraint named instead of averaged away.

**What it costs:** Downstream planning can rely on fictitious progress, mobilize at an unready joint, or hide a blocking wait inside an average percentage.

Percent-complete hides the truth. A block can be reported ninety percent done while the joint the next block needs is blocked, and "unknown" is quietly rounded into "on track" until the schedule slips at the join.

## How VeldBuild would answer it

**Question:** What is genuinely complete, underway, waiting or unknown on this block?

- **Scope:** One block or zone and its declared work packages, joints, dependencies, holds, and acceptance events at a stated time.
- **What it reads:** Block and zone structure, material, systems and inspection state; Work-package states across the block; Predecessor and successor joints; Open holds and nonconformances. Evidence it needs: Per-block state record; Work-package states; Joint and predecessor relationships; Hold and nonconformance records.
- **What it computes:** Reconstruct discrete complete, underway, waiting, and unknown states; Attribute each wait to a cause and owner; Expose the least-ready governing section instead of averaging percentages. Output: Complete, underway, waiting or unknown, block by block; the least-ready section named, and every wait tied to a cause and an owner.
- **Left unknown:** Stale or unattributed execution events; Reported completion without acceptance evidence; A dependency or joint state that cannot be established
- **Decided by:** VeldBuild reports state, including unknown; it does not fabricate progress it cannot evidence; Production planning owns the schedule decision the state informs (MES execution events; Production-planning schedule authority; Supervisor attribution; Quality acceptance state)
- **Status:** Target. Modeled per-block on VS-001. Live MES and scheduling connectors are planned.
- **What would prove it on real records:** Compare a live execution-event reconstruction with supervisor and planning reviews at selected block joints over time.

**Next:** [See schedulable capacity, not nominal](https://www.veldarium.com/industrial-base#capacity). A supplier existing, a supplier being qualified, and a cell being available to this work on this date are different facts. The industrial-base model separates them and shows which one actually binds.

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