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
| Package | What it is | Owner |
|---|---|---|
| CWA | A geographic area of the plot, all disciplines | Engineering, with construction input |
| CWP | One discipline inside one CWA, defined by a 3D envelope, sized for one general foreman for 6 to 8 weeks | Construction contractor |
| EWP | All engineering information for one CWP, which is its documents, model, and MTO | Engineering contractor |
| VEWP | Vendor engineering needed for one CWP, managed as attributes | Engineering, with vendors |
| FEWP | Fabricator engineering for its parent EWP | Fabricator |
| PWP | The material data for one CWP against its required-on-site date | Engineering contractor |
| FPWP | A fabricator's shop package feeding exactly one CWP | Fabricator |
| MWP | Load, ship, and set of a module at site | Module fabricator |
| IWP | Constraint-free work for one foreman and crew for 7 to 10 days, from one CWP | Construction contractor |
| TWP | Testing work, linked to IWPs by line number | Construction contractor |
| SWP | All remaining work for one system, for turnover | Construction contractor |
The Rules Software Has to Hold
- One parent per record. Every CWP sits in exactly one CWA and every IWP comes from a single CWP, so a tag knows its IWP and, through it, the CWP and CWA
- One to one by the 30% model review. Early EWPs can cover several CWPs, and by the 30% model review each CWP has one EWP and one PWP with matching boundaries
- Names that carry the relationship. A name such as EWP-H01-PIP-GEN-001 holds type, area, discipline, sub-discipline, and sequence, and the CWP and IWP names inherit that root
- One register of relationships. The AWP Matrix maps each CWP to its EWP, VEWP, FEWP, PWP, FPWP, and MWP, and the schedule, document register, and AWP software align only after it is issued
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.