Use case · Planning
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.
- Records
- Released work
- Physical build
- Human authority
What happensA crane, workcell, or trade loses capacity. Block sequence and quay timing must change without hiding the new bottleneck in percent-complete.
A capacity source drops, Records
The robotic structural weld cell is out. Nominal capacity and schedulable capacity part company, and only one of them is in the plan.
Percent-complete stops helping, Records
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.
The bottleneck moves, Released work
Work that was not binding becomes binding. The queue re-forms somewhere the plan was not watching.
The consequence reaches steel
Block order and quay timing change, Physical build
Erection sequence shifts, and the berth date shifts with it. The whole consequence started as one unavailable cell.
Production control resequences, Human authority
Against the capacity that exists rather than the capacity on the plan, with the new binding constraint named instead of averaged away.
How VeldBuild would answer it
What is genuinely complete, underway, waiting or unknown on this block?
What it reads
- Scope
- One block or zone and its declared work packages, joints, dependencies, holds, and acceptance events at a stated time.
- Records
- 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
- Steps
- 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.
What stays with people
- 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
What would prove it on real records
- Test
- Compare a live execution-event reconstruction with supervisor and planning reviews at selected block joints over time.
Questions that usually come next
- Which section is the block least ready at the joint it needs next?
- What is each waiting package actually waiting on, and who owns it?
If your team answers this by hand, start with one work area.
Email the release decision, the systems that hold its records, and who owns it. Keep the first message non-confidential.