AWPBI

AWP for Brownfield Projects and Turnarounds

3 min read · Updated Oct 2026

Advanced work packaging applies to brownfield and turnaround work with the same package logic as new construction. The project agrees the sequence, delivers engineering and materials in complete packages, and releases only constraint-free work. Because the work happens inside an operating plant, existing assets, existing documents, and safety-critical changes need their own rules.

The Existing Plant in the Model

The model separates the existing plant from new scope at the top of its hierarchy, and every object carries a scope type of dismantle, existing, new, turnaround, or relocate. Planners can then see which work touches existing equipment and cut packages around it. Model conditioning for AWP covers the attributes.

Existing Documents Stay Under Site Control

Drawings controlled by operations follow the site's drawing numbering standard. Existing drawings are checked out through the site drawing management team and are never renumbered by the contractor. When an existing document is revised, the originator code of the original stays unchanged, so its history remains traceable.

Safety-Critical Changes Go Through MOC First

Changes that touch P&IDs, plot plans, process safety data, interlocks, or hazardous area classification follow the full management of change workflow, with process safety approvals, before they are incorporated into an engineering work package.

Constraints in an Operating Unit

A constraint is any condition that prevents a task from being executed, and installation work packages are released only when they are constraint-free. Inside an operating unit, permits, isolations, and access windows join materials and documents on that list. A construction work package still starts only with 100% of its material on site, unless the construction manager accepts a backlog of constraint-free packages. Material readiness covers the material rules.

Turnarounds

A turnaround compresses execution into a fixed shutdown window, so the make-ready work has to be finished before the unit comes down. Each work order is linked to its equipment, the sequence is checked before the event, and progress is tracked per equipment through milestones suited to the work. Workface planning covers the crew-level planning.

How openAWP Supports It

openAWP holds turnaround work orders as records linked to equipment in the plant model, created in openAWP, imported from Excel, or sent in from the maintenance system through its API. Isolations and permits are tables that reference the work orders, and constraints hold packages out of release. The shutdown window is planned on the lookahead and played through in 4D, and progress rolls up with milestones such as isolated, opened and inspected, work executed, closed and reinstated, tested, and returned to service.

Planning brownfield or turnaround work on an operating unit? See how we support oil and gas projects, or talk to our workface planning team.

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

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

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

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

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

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

How the AWP Package Hierarchy Maps to Software

The eleven AWP package types from CWA to SWP, who owns each one, and the rules AWP software has to hold for parents, one-to-one packages, and the register.

3 min read

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

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

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

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

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.