Use case · Configuration control
Configuration authority
Determine which released definition governs a piece of work at a point in time when drawings, redlines, change notices and field copies disagree.
- Records
- Released work
- Physical build
- Human authority
What happensReleased drawings, field redlines and active work disagree. Build to the wrong revision and the error is in steel.
Three definitions circulate, Records
A released revision, a bounded field exception, and the revision WP-019 is actually written against. All three are real records.
Precedence, not recency, Records
Release state governs and a newer timestamp does not. The definitions that lose are named as non-controlling rather than quietly dropped.
Active work is re-checked, Released work
Work still attached to a superseded definition is listed. Nothing is silently re-pointed at the winner.
The consequence reaches steel
The yard builds the wrong thing correctly, Physical build
Fabrication, installation and inspection can each be executed perfectly against a definition that does not govern. Quality will not catch it, because the work matches its drawing.
Engineering confirms what governs, Human authority
A named owner confirms the governing definition and the scope of any exception. No software releases a drawing or edits a source of record.
How VeldBuild answers it
Which revision governs this object, zone and effective date, and why?
What it reads
- Scope
- One governed object or work package within an explicit hull, block, zone, serial, time, and approved-exception boundary.
- Records
- Release records and revision lineage · Engineering drawings and redlines · Approved change notices · Zone, block or field exceptions · The revision a work package is written against
- Evidence it needs
- Release and approval records · Revision lineage · Effective-date and applicability metadata · Active-work references
What it computes
- Steps
- Released state governs; a newer file does not
- Resolve effectivity, applicability, supersession and approved exceptions
- Name every plausible definition that does not govern
- Output
- The revision that governs, the ones that do not and why, and the work still written against a superseded one.
What stays with people
- Left unknown
- Missing approval or release evidence
- Conflicting applicability or effectivity
- An exception whose approved scope cannot be established
- Decided by
- VeldBuild proposes the governing definition; it never releases a drawing or alters the source of record
- Engineering or configuration control confirms which definition governs
What would prove it on real records
- Test
- Compare reconstructed governing revisions with configuration-control decisions across a blinded set of disputed live work objects.
Questions that usually come next
- Which competing definitions were rejected as non-controlling?
- What active work is still attached to a superseded revision?
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.