A data requirements document states, discipline by discipline, which attributes every tag, document, model object and material line must carry, in what format and by when. It is agreed before execution habits form, and compliance is checked before each EWP is issued for construction.
What the Document Covers
Five parts carry most of its weight.
- Tags. The tagging philosophy, the numbering structure, parent and child relationships for skids and assemblies, and the Tag Register that every other tag table is reconciled against
- Attributes per discipline. The equipment class library and document class library, the attributes each class carries, the allowable picklist values and the units of measure, aligned to CFIHOS, the IOGP Capital Facilities Information Handover Specification, where the project adopts it
- MTO fields. What a Primary MTO row and a Secondary MTO row must hold, including quantity, unit, specification, size, catalog reference, the EWP, CWP and IWP each item belongs to, the 3D model GUID and the parent tag
- 3D model attributes. The CWA, CWP and EWP on every object, the system, a module flag and module name, a ship-loose flag, a scope type (new, existing, dismantle, turnaround or relocate), and a selection tree organized by EWP
- Reference data libraries. The plant breakdown structure, area and unit codes, and the controlled code lists that every organization on the project uses
The CII AWP Data Requirements Implementation Guideline is the industry reference, and a project's document is written against it with its own disciplines and systems filled in.
Lead Times Are the Leading Indicators
The dates in the document are watched weekly because they predict package readiness. Every tag an EWP needs is requested and reserved at least 10 weeks before the planned IFC date. Every document the package will contain exists as a placeholder in the master document register at least 8 weeks before the planned release, with the request made 10 weeks before. Changes to the register reach the document system within five business days. A package whose placeholders are short six weeks out is already late, whatever its drawing count says. Weekly data reconciliation is where those counts are checked.
A Package Can Be Rejected on Data Alone
Compliance with the data requirements and the 3D model attributes is verified as part of the EWP review, before the package is issued IFC. A package whose model objects lack their EWP attribute, or whose tags disagree between the P&ID, the model and the MTO, is returned with the drawings untouched. The same requirements flow into every procurement work package at purchase order issuance, so a vendor bill of material or packing list that misses them is rejected on the same grounds. Compliance is a deliverable, with the same standing as the drawings.
What Goes in the Request for Proposal
The document itself, the 3D model attribute specification, the uniform packing list template, the bill of material template, the discipline list and the AWP naming convention all attach to the engineering and procurement RFQ. Vendors and fabricators inherit them through the contract, and their ability to deliver intelligent 3D models and structured data is evaluated before purchase order award. In the RFQ, the requirements cost a few pages. After the first isometrics are issued, they cost a renegotiation with every organization already producing data.
Writing the document and running the weekly checks against it is part of the information management service. The requirements and the registers that prove compliance belong to the owner, and they stay in the owner's tenant when the contractor's contract ends.