What Model Conditioning Is and Why AWP Needs It

Model conditioning is the work of preparing the design model so construction can package from it. Every object carries the attributes advanced work packaging needs, including its construction work area, construction work package, and engineering work package. Tags match across every system, vendor and fabricator models are checked before they join, and the conditioned model reaches the AWP software every week.

Why AWP Needs a Conditioned Model

Workface planners build installation work packages from the model, in the AWP software, with the general foremen. An object with no CWP, the wrong EWP, or a tag that differs from the tag register falls outside the package it belongs to, and the gap shows up at the workface. What BIM looks like on capital projects covers the model as a construction deliverable.

What Conditioning Covers

1. Attributes per the data requirements. Every engineering tag is associated to an EWP and parent-child relationships follow the data requirements, with no attribute, tag, or hierarchy level changed on any authoring platform without the owner information manager's approval
2. CWP volumes. The construction team defines CWP boundaries during interactive planning, and the design model's administrator turns them into volumes so every object is assigned to its CWP
3. A tree structured by EWP. The model selection tree is organized by EWP, so every object can be retrieved by package as well as by CWA and CWP
4. Execution attributes. Each object carries a modularization flag and module name, ship-loose identification, and a scope type of dismantle, existing, new, turnaround, or relocate
5. Tag reconciliation. Model tags reconcile weekly against the single tag register, the document register, and the package register
6. Vendor and fabricator models. Each is checked for attributes and tags before acceptance, returned if short, and integrated into the master model once issued for construction

Keeping It Current

Every EWP revision includes the matching model attribute updates, and a revision is complete only when the model is updated and verified against the package register. The conditioned model is delivered weekly, and a full material takeoff export every two weeks allows independent checks of quantities, attributes, and package assignment.

How openAWP Handles It

openAWP scans each model into its database so its properties can be searched, pivoted, and matched. A property parser normalizes values during the scan, and matching rules link components to records by exact value, prefix, or pattern, across the whole project in one run. Its assistant can write parser rule sets from the model's real property names, for an administrator to review and apply.