AWPBI

How the AWP Package Hierarchy Maps to Software

By AWPBI Dev Team · Updated Oct 2026 · 3 min read

The AWP package hierarchy maps to software as linked records, with one table per package type, each record pointing to the one it belongs to, and one controlled register of how the packages relate. The Construction Industry Institute (CII) describes AWP as developing constraint-free work packages aligned to an optimized path of construction, and a full AWP procedure expands its core levels into eleven package types, each with one owner and one definition.

The Package Types

PackageWhat it isOwner
CWAA geographic area of the plot, all disciplinesEngineering, with construction input
CWPOne discipline inside one CWA, defined by a 3D envelope, sized for one general foreman for 6 to 8 weeksConstruction contractor
EWPAll engineering information for one CWP, which is its documents, model, and MTOEngineering contractor
VEWPVendor engineering needed for one CWP, managed as attributesEngineering, with vendors
FEWPFabricator engineering for its parent EWPFabricator
PWPThe material data for one CWP against its required-on-site dateEngineering contractor
FPWPA fabricator's shop package feeding exactly one CWPFabricator
MWPLoad, ship, and set of a module at siteModule fabricator
IWPConstraint-free work for one foreman and crew for 7 to 10 days, from one CWPConstruction contractor
TWPTesting work, linked to IWPs by line numberConstruction contractor
SWPAll remaining work for one system, for turnoverConstruction contractor

The Rules Software Has to Hold

No package is created, split, or merged outside that register. How Primavera P6 carries an AWP program covers how the same structure appears in the schedule.

Where the Levels Live

CWAs sit at Level 2 of the schedule, packages at Level 3 as real activities of about eight weeks, and IWPs at Level 4 in the AWP software, never in the Level 3 schedule.

How openAWP Maps It

openAWP supports the full hierarchy, with each package type as its own table and a single parent reference on each record, so everything above a record is derived. Its AWP Standard template starts a project with that structure, and every field in it can be changed.

Our AWP consulting team writes AWP procedures and the package structure behind them.

Related Articles

What Is Advanced Work Packaging?

A plain-language definition of AWP, why capital projects use it, and how it changes execution planning.

7 min read · Updated Jul 2026

How Workface Planning Fits Into Advanced Work Packaging

Workface planning is the last step in AWP, turning engineered scope into packages a crew can execute.

5 min read · Updated Jul 2026

Advanced Work Packaging Without a 3D Model

What the 3D model does in a full AWP procedure, what still works when a project has no usable model, and which controls have to be rebuilt by hand.

4 min read · Updated Oct 2026

Self-Hosted AWP Software with P6 and Power BI

What self-hosting AWP software means for project data, how it divides work with the Primavera P6 schedule, and how Power BI reads package data from it.

4 min read · Updated Oct 2026

Which Project Phases AWP Software Should Cover

What AWP software should hold from FEED to turnover, covering the path of construction, EWPs and PWPs, IWPs and the lookahead, testing, and system completion.

4 min read · Updated Oct 2026

What It Takes to Set Up AWP Software on a Project

How AWP software is set up from FEED, with the structures agreed before engineering packages, data loaded every week, the model link, and full-time leadership.

3 min read · Updated Oct 2026

How to Evaluate Advanced Work Packaging Software

Seven areas to evaluate in AWP software, drawn from what an AWP procedure asks of it, from building IWPs from the model to completing work by system.

3 min read · Updated Oct 2026

How Advanced Work Packaging Software Is Priced

The three parts of AWP software cost, which are the license, the setup, and support through execution, and what each one covers on a capital project.

3 min read · Updated Oct 2026

AWP for Brownfield Projects and Turnarounds

How advanced work packaging applies inside an operating plant, from the existing plant in the model and site-controlled drawings to MOC and turnarounds.

3 min read · Updated Oct 2026

How Owners Run AWP Across Several EPC Contractors

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 AWP Record Should Outlive the Contract

The AWP registers, the matrix and the readiness history sit in the contractor's system and leave when the contract ends. The fix is where the standard lives.

9 min read · Updated Oct 2026

What Complete Means for Each AWP Package Type

The definition of complete for all eleven AWP package types, fixed in the procedure, plus the one binary rule of credit that measures EWP progress.

5 min read · Updated Oct 2026

An EWP Release Plan the Owner Can Audit

How an engineering contractor runs an EWP release plan an owner can audit, with four statuses, one rule of credit, weekly forecasts and a skyline.

5 min read · Updated Oct 2026

Placeholders Are the Earliest Warning an EWP Will Be Late

Why a short placeholder count eight weeks before an EWP release predicts a late package, who owns the count, and the weekly check that catches it early.

4 min read · Updated Oct 2026

What the AWP Matrix Is and Who May Change It

The AWP Matrix is the one controlled list of every work package and its relationships, owned by the owner's AWP lead and issued weekly before systems change.

4 min read · Updated Oct 2026

What an Owner Checks in an Engineering AWP Audit

The items an owner checks in an engineering AWP audit, when the audits happen, and the weekly routine that lets an engineering contractor pass every time.

4 min read · Updated Oct 2026

How EWP Changes Are Managed After IFC

The five categories of EWP change, the change notice that precedes revised drawings, and the re-transmitted package that keeps every recipient on one set.

4 min read · Updated Oct 2026

What a HOLD Register Must Contain

What every row of an engineering HOLD register carries, how HOLDs are accepted at the EWP review, and why a HOLD is released by revising the package.

3 min read · Updated Oct 2026

What a Document Allocation Matrix Does

How a Document Allocation Matrix assigns each document to an EWP, VEWP or FEWP when its placeholder is created, with an example and the rule on unassigned ones.

4 min read · Updated Oct 2026

The Lean Owner AWP Organization

The small set of AWP roles an owner needs from FEED, who reports to whom, the deliverables each lead owns, and where a partner fills the gaps.

4 min read · Updated Oct 2026

Why the Module Yard Is an Extension of the Site

Why module fabrication follows the same AWP requirements as site construction, what FEWPs and MWPs are, and the review two weeks before a module ships.

4 min read · Updated Oct 2026

When a Project Moves from IWPs to System Work Packages

When a project repackages remaining scope into system work packages, what an SWP contains, and why the lookahead and constraint process stay the same.

4 min read · Updated Oct 2026

What Model Conditioning Is and Why AWP Needs It

What model conditioning covers, from attributes per the data requirements and CWP volumes to an EWP-structured tree, tag checks, and vetted vendor models.

3 min read · Updated Oct 2026

See How openAWP Supports Advanced Work Packaging

Explore the product these articles are about, or book a live demo to see it on your own project.