Information management (IM) keeps every dataset on a capital project coherent: documents, tags, models, and the relationships between them. Here is the discipline explained, and how our team and products support it.
A practitioner definition of IM on capital projects, covering the framework, the reference data library, controlled identity, response codes, and the data warehouse that reports it all.
8 min read · Updated Jul 2026
What an AWP data requirements document covers, the tag and placeholder lead times that predict package readiness, and why an EWP can be rejected on data alone.
4 min read · Updated Oct 2026
The governed set of project systems and the rules that keep them in agreement, with one owner per dataset.
4 min read · Updated Oct 2026
Raw, validated and reporting layers explained by what they hold on a capital project, who reads and writes them, and how the services are sized to the data.
4 min read · Updated Oct 2026
One Tag Register as the source of truth, what it holds, the weekly reconciliation that keeps every system matched, and the ten week reservation lead time.
4 min read · Updated Oct 2026
Why every drawing sheet is its own controlled record, how isometrics and erection drawings are registered, and why a document is never renamed after issue.
4 min read · Updated Oct 2026
How an owner runs AWP across several EPC contractors with a standard set before contracts are signed, owner roles, one naming convention, data, and audits.
3 min read · Updated Oct 2026
The Secondary MTO expands an engineered design into every installable item as a digital row, with the fields that let planners and procurement join it.
4 min read · Updated Oct 2026
Explore the platform these articles describe, or talk to the team that deploys the discipline on real projects.