One document, one drawing, one sheet means every drawing sheet is registered, issued and revised as its own controlled record, with its own document number and its own revision history. The rule exists so that a sheet can be allocated to a work package, checked for revision and found in both the register and the document management system without anyone translating between them.
Why One Sheet
A combined PDF of forty isometrics is one record in the document system. When the eleventh isometric changes, the whole file revises, every package that referenced any of the forty is now at risk, and nobody can tell which sheet actually moved. Registered one sheet at a time, each isometric carries its own revision, belongs to one EWP, and shows up by itself when the weekly revision check asks whether the construction contractor holds the latest issue.
Four things depend on it. Individual registration, independent revision, allocation to a package through the Document Allocation Matrix, and the revision checks that keep fabricators and the field on the current sheet.
Isometrics Are Sheets
Isometrics are managed as discrete sheet-level documents in the register and the document management system, for above-ground and underground scope alike, and steam tracing isometrics follow the same rule. Grouping isometrics into lists conflicts with package-based execution because a package releases when every one of its documents is IFC, and a grouped list hides which ones are.
Where a grouped list cannot be avoided, the rule is that one list equals one EWP. Splitting or merging the package splits or merges the list, and a revision to any isometric revises the list and the package.
Fabricator Deliverables Follow the Same Rule
Erection drawings and other fabricator deliverables are issued individually, one document per drawing, and assigned to their FEWP. Fabrication status reports carry the construction isometric number and the document system number and revision, so the isometric list, the fabrication status and the controlled document match without a lookup table.
A Document Is Never Renamed
Once a document has been issued into the controlled environment, its number and title do not change. A correction supersedes the record, with the superseded document issued for void and the replacement referencing the number it replaces, so traceability runs both ways. Renaming after issue breaks the link to every package, transmittal and HOLD that referenced the original.
The Register and the Document System Stay in Step
New register records, including placeholders for documents not yet produced, exist in the document management system within five business days of being created. Metadata updates and revision status changes are synchronized within the same window, and any synchronization failure is corrected within five business days of detection. Holds on a document are recorded in the register and tracked in the HOLD register until released.
Keeping one record per sheet is what lets the register, the document system and the 3D model agree at the end of the week. AWPBI's information management service writes the document control requirements into the procedure and runs the weekly revision check.