Book a demo
Login
Advanced Work Packaging (AWP) is a project execution methodology developed to improve construction productivity and schedule performance on capital projects in oil and gas, energy, chemicals, utilities, and industrial sectors. AWP structures the entire project delivery process from early engineering through field installation around a hierarchy of work packages that define, sequence, and manage project scope in progressively smaller, field-executable units.
Projects that implement AWP fully and consistently demonstrate measurable improvements in labour productivity, schedule performance, and total installed cost compared to projects executed without a structured work packaging approach. Research from the Construction Industry Institute (CII) and the Construction Owners Association of Alberta (COAA) has quantified these benefits across a large sample of capital projects, establishing AWP as a proven methodology rather than an aspirational framework.
AWP is now a recognized practice in major capital project execution globally, particularly in North American energy and petrochemical projects, and increasingly in LNG, offshore, refining, and renewable energy developments worldwide.
AWP was developed through collaborative research between COAA (Construction Owners Association of Alberta) and CII (Construction Industry Institute) over two decades of applied research on capital project productivity. The methodology is documented in CII Implementation Resource 272, which provides the foundational framework for AWP implementation. COAA has also published AWP implementation guides and best practices, and the two bodies continue to update their guidance as the methodology evolves.
The development of AWP was driven by observed productivity losses in large capital project construction, particularly the pattern of out-of-sequence work caused by constraints — missing materials, incomplete engineering, unresolved permit requirements — that were not identified and resolved before field work began. AWP addresses this systematically by structuring the entire project around the concept of constraint-free work packages that are only released to the field when all prerequisites have been confirmed.
The AWP methodology is built around a hierarchy of work packages that decompose the full project scope from high-level engineering groupings down to field-executable installation units. Each level of the hierarchy has a specific purpose and governs a specific phase of project delivery.
Engineering Work Packages are the highest level in the AWP hierarchy. An EWP defines a specific scope of engineering deliverables — drawings, specifications, calculations, and vendor documents — that supports a defined physical area or system of the facility. EWPs are aligned to the Path of Construction from the beginning of detailed engineering, ensuring that engineering prioritizes and sequences its deliverables to support the planned construction sequence rather than producing documents in an engineering-convenient order that may not match field execution needs.
Each EWP feeds one or more Construction Work Packages, creating a direct traceability linkage from engineering deliverables to field installation scope. This linkage is foundational to AWP: it allows the project to track whether the engineering prerequisites for a given construction work package are complete before that package is released to the field.
Procurement Work Packages align the procurement process to the same Path of Construction framework that governs engineering and construction. A PWP groups the materials and equipment required for a defined construction scope, tracks the procurement and delivery status of those items, and provides the supply chain visibility needed to confirm material availability as an IWP prerequisite check.
PWPs connect purchase orders, expediting status, and delivery records to the construction scope they support. When a procurement work package is complete, the materials it covers are confirmed delivered, inspected, and available at the workface for the associated IWPs. Incomplete vendor documentation — missing datasheets, unreviewed inspection records, unprocessed certificates — is captured as a PWP constraint that must be resolved before the corresponding IWPs can be released.
Construction Work Packages are the discipline-specific work packages that define the physical installation scope for a given Construction Work Area (CWA) and a given trade or discipline. A CWP covers a defined scope of piping, structural, electrical, instrumentation, or civil work within a specific area and is the primary unit of construction planning and resource allocation at the project level.
CWPs are designed by the engineering team in alignment with the Path of Construction and the planned sequence of construction activities through each CWA. A well-defined CWP has clear scope boundaries, a manageable man-hour estimate, and a complete set of engineering and procurement prerequisites that can be tracked and confirmed before the CWP is executed.
Installation Work Packages are the fundamental executable unit of AWP. An IWP defines a specific scope of field installation work — typically three to five days of work for a crew of specified size and composition — that can be executed continuously without interruption when all its constraints have been resolved. IWPs are the packages that are physically handed to the foreman in the field; they contain the drawings, specifications, material lists, and work instructions required to execute the defined scope.
The defining characteristic of an IWP is that it must be constraint-free before it is released to the field. Constraint-free means that every prerequisite for the IWP — engineering complete, materials available, permits in place, equipment certified, work area clear, vendor documentation received and reviewed — has been confirmed as satisfied. An IWP released with unresolved constraints generates out-of-sequence work, crew waiting time, and rework that directly undermines AWP's productivity benefits.
The Path of Construction (PoC) is the planned sequence in which construction progresses through the facility. It defines which physical areas of the plant will be constructed first, in what order systems and disciplines will be installed, and how the completion of early scopes enables access to later scopes. The PoC is established collaboratively between engineering, construction, and commissioning early in the project, and it governs the prioritization of engineering deliverables, procurement activities, and construction resource allocation throughout the project lifecycle.
Construction Work Areas (CWAs) are the physical zones of the facility that structure the work packaging hierarchy. The plant is divided into CWAs, typically by geography or system, and all CWPs and IWPs are assigned to a CWA. The PoC defines the sequence in which CWAs will be completed, creating a spatial and temporal framework for the entire construction execution plan.
Commissioning systems are aligned to the PoC and CWA structure, enabling the commissioning and startup sequence to flow logically from the construction completion sequence. This alignment between engineering prioritization, construction sequencing, and commissioning planning is one of AWP's most significant contributions to capital project efficiency.
Implementing AWP successfully requires more than deploying AWP software. It requires organizational commitment to the methodology across engineering, procurement, and construction functions, and it requires the underlying data infrastructure to be in place for the methodology to function as designed.
On the engineering side, AWP implementation requires that engineering disciplines align their deliverable production sequence to the Path of Construction from the start of detailed engineering. This means that the areas where construction will begin first are prioritized in engineering workload planning, and that EWP boundaries are defined in a way that supports the construction sequence rather than engineering convenience. It also requires that the engineering document register and tag register are structured to support work package tracking — so that the completeness of engineering prerequisites for each CWP can be measured and reported.
On the procurement side, AWP implementation requires that materials and equipment are tracked against the construction work packages they support, not just against purchase orders in isolation. Vendor data — datasheets, inspection records, certificates, manuals — must be received, reviewed, and linked to project tags before the PWP for a given scope can be confirmed complete. In practice, this vendor data management requirement is one of the most challenging aspects of AWP implementation: large projects with hundreds of suppliers generate volumes of vendor documentation that cannot be processed manually at the speed AWP requires.
On the construction side, AWP implementation requires that IWPs are prepared by a dedicated work package team well in advance of field execution, that constraint checks are conducted systematically against confirmed data rather than assumed status, and that the field is held to the discipline of executing IWPs as released rather than modifying scope informally in the field.
AWP software platforms — such as O3 Solutions' ONBuild, ONPlan, and related products — provide the planning, sequencing, constraint tracking, and execution management capabilities that AWP requires at a project-wide scale. They manage the work package hierarchy, track constraint status, provide visibility into IWP readiness and release status, and give project controls teams the data they need to manage construction execution against the planned Path of Construction.
AWP software is an execution management tool. It tracks the status of engineering, procurement, and other constraints — but it does not govern the underlying engineering data that determines whether a constraint is genuinely resolved. Whether engineering is complete for a given CWP scope is a question that can only be answered by a governed engineering data environment: one where the engineering document register and tag register are current and accurate, where documents are linked to the correct tags and revisions, and where vendor data has been received, validated, and associated with the right equipment records.
Without a governed engineering data layer, AWP constraint checks rely on manual confirmation of status — which is inherently unreliable, particularly in projects with large supplier bases and complex engineering change management. For AWP to deliver its promised productivity benefits, the data that drives constraint resolution must be accurate, complete, and governed. This is the connection between AWP methodology and engineering data management — and it is where many AWP implementations fall short. For a detailed analysis of this data dependency and how to address it, see our article on why AWP projects need a governed engineering data layer.
CFIHOS (Capital Facilities Information Handover Specification) is the industry data model that defines which equipment attributes must be populated, in what structure, and traceable to what source documents, for a facility to meet owner-operator handover requirements. In the context of AWP, CFIHOS provides an objective definition of what complete engineering data means for each equipment class.
When an AWP project adopts CFIHOS as its data completeness standard, IWP constraint checking for engineering data completeness becomes measurable rather than subjective. For a given tag, either the CFIHOS-required attributes are populated with validated, traceable values, or they are not. This provides the data foundation that AWP constraint management requires: not a status reported by a document controller, but a verifiable, queryable completeness metric against a defined standard.
CFIHOS alignment also ensures that the engineering data collected during the project is in the format required for facility handover, reducing or eliminating the data transformation effort that often occupies the final months of a project and frequently delays commissioning and startup.
Sharecat provides the engineering data governance layer that AWP depends on but that AWP tools are not designed to deliver. The Sharecat platform manages the master tag register, structures supplier and vendor data submissions against CFIHOS templates, links every document to the tags it covers, and tracks engineering data completeness at tag level throughout the project lifecycle.
For AWP projects, this means that the constraint checks on which IWP release decisions are based draw from a governed, accurate, real-time data environment rather than from manual status reports. Engineering completeness for a given IWP scope is a query against the Sharecat tag register and document index, not a phone call to the document controller. Vendor data completeness is a measurable metric in Sharecat's supplier submission workflow, not a guess based on when the purchase order was expected to be fulfilled. Tag register currency is maintained through Sharecat's governed change management process, ensuring that IWP scope reflects the current engineering state.
Sharecat integrates with AWP platforms to provide the data foundation they need for effective constraint management. The combination of a governed engineering data environment and a capable AWP execution platform gives capital projects the complete solution: accurate data and the tools to turn that data into productive field execution. On the BP Tangguh LNG Expansion, Sharecat managed 170,812 tagged equipment items and 7,650,321 data attributes from 391 suppliers, demonstrating the scale at which the platform can operate in support of complex capital project execution.
A Construction Work Package (CWP) is a discipline-specific scope of work within a Construction Work Area, typically covering weeks or months of construction activity for a given trade. It is the primary unit of construction planning and resource allocation. An Installation Work Package (IWP) is a subset of a CWP: a specific, tightly-scoped field installation task covering three to five days of work for a defined crew that can be executed without interruption when all constraints are resolved. The CWP defines the scope; the IWP is the executable unit that the foreman receives in the field.
A constraint-free IWP is one for which every prerequisite for field execution has been confirmed as satisfied: engineering design for the scope is complete and at the correct revision, all required materials are available at the workface, necessary permits are in place, the work area is physically accessible, required vendor documents have been received and reviewed, and no safety, environmental, or logistical issues block the work. AWP discipline requires that IWPs are not released to the field unless they are genuinely constraint-free — not just administratively checked, but verified against confirmed data.
The Path of Construction (PoC) is the planned sequence in which construction progresses through the facility, defining which areas are constructed first, in what order disciplines and systems are installed, and how the completion of early scopes enables access and progress in subsequent scopes. The PoC is established early in the project and governs the prioritization of all engineering, procurement, and construction activities. Engineering deliverable sequencing, procurement urgency, and commissioning planning are all aligned to the PoC to ensure that the project's physical construction sequence is supported by the right information and materials at the right time.
AWP improves productivity primarily by eliminating out-of-sequence work in the field — the situation where a crew begins an installation task only to be stopped by a missing material, an incomplete drawing, an unresolved permit, or an access conflict that should have been identified and resolved before the IWP was released. Out-of-sequence work generates waiting time, rework, and resource inefficiency that compound across a large construction workforce. By requiring that IWPs be constraint-free before field release, AWP systematically eliminates the root causes of these productivity losses. CII research has found that projects implementing AWP fully consistently outperform non-AWP projects on labour productivity metrics.
AWP is governed primarily by CII Implementation Resource 272 (IR-272), which provides the foundational framework, implementation guidance, and assessment tools for AWP. COAA has published complementary AWP implementation guides and best practices documents. In practice, individual owner-operators and EPCs develop their own AWP execution plans and work packaging standards within the IR-272 framework, adapting the methodology to their specific project types, contracting strategies, and organizational structures. CFIHOS provides the data quality standard that defines engineering data completeness for AWP constraint checking in oil and gas, energy, and chemicals projects.
Yes. While AWP was developed primarily in the oil and gas and petrochemical sectors and remains most widely adopted there, the methodology is applicable to any large capital project with significant construction scope: LNG facilities, offshore platforms, onshore refineries, power generation and transmission infrastructure, mining and minerals processing, and increasingly to major renewable energy developments. The core AWP principles — alignment of engineering to the Path of Construction, systematic constraint management, constraint-free IWP release discipline — are applicable wherever large-scale construction execution is organized around a structured work packaging hierarchy.
Understanding Advanced Work Packaging is supported by familiarity with related concepts in capital project execution and engineering data management. The master tag register is the governed list of all tagged equipment items in a project; in AWP, the tag register is the foundation of IWP scope definition and engineering completeness tracking. CFIHOS (Capital Facilities Information Handover Specification) defines the data model for equipment attributes at handover and provides the completeness standard for AWP engineering data constraint checking. Supplier data management covers the processes for collecting, validating, and linking vendor documentation to project assets — one of the largest sources of IWP constraint delays in AWP projects. Engineering document management provides the document control infrastructure on which AWP's engineering completeness tracking depends.
ISO
27001
Certified
