The package logic of advanced work packaging runs without a 3D model, but the full method expects one. A rigorous AWP procedure treats the model as a construction deliverable, so every engineering work package (EWP) includes the model or its extract, and every construction work package (CWP) is defined by a 3D envelope. A project without a usable model can still package, sequence, and release work, with some controls rebuilt by hand.
What the Model Does in the Full Method
In a project run to a complete AWP procedure, the model carries several jobs at once.
- CWP boundaries. The construction team decomposes each construction work area (CWA) into CWPs drawn as volumes in the model, and those volumes go to the material and AWP software
- EWP content. An EWP has exactly three components, which are the documents, the model or its extract with EWP attributes, and the material takeoff (MTO)
- Quantities. Bills of material are generated from the model, with non-modeled and detail-level items expanded into a Secondary MTO
- Status. The model colored by EWP, material, and fabrication status is how packages are communicated to stakeholders
What BIM looks like on capital projects covers the model requirements in detail.
What Still Works Without One
The core of AWP is making construction the customer of engineering and procurement. The project agrees how the plant will be built, then engineering and materials are delivered in complete packages in that order. That logic does not depend on geometry.
- The path of construction is developed in 2D first and then in the model, so a 2D sequence is a working starting point
- The package hierarchy and naming work as records, tied together by one register of all packages and their relationships
- Scope by tag comes from a single Tag Register, reconciled weekly, which gives every item an identity and its package association
- Material readiness still applies, so a CWP starts only when 100% of its material is on site, as material readiness explains
- Constraints still gate release, and installation work packages (IWPs) go to the field only when they are constraint-free
What Has to Be Rebuilt by Hand
Three controls move from the model to manual checks.
- Boundaries. With no volumes to inspect, package overlaps and gaps are found by reconciling tag lists against the package register
- Quantities. The Secondary MTO carries everything, and every component still has to be its own data row, never a note on a drawing
- Status views. Progress is reported in tables and skylines, without a colored model
Projects in this position rely more on information management, because the registers are the only record of scope.
How openAWP Handles Projects Without a Model
A project in openAWP can start without a model and add one later. CWAs, CWPs, EWPs, IWPs, and tags are records in tables the project defines, loaded from registers, spreadsheets, or the schedule. Constraints, releases, and progress all run on those records. When a model is loaded, matching rules link its components to the same records, and the packages gain 3D views and status coloring.
Starting AWP on a brownfield or fast-tracked project? Our AWP consulting team sets up the registers and package hierarchy, or explore openAWP directly.