AWP Software for Nuclear EPCs: A Buyer’s Checklist

Two demands shape every nuclear refurbishment: a fixed outage window and a traceable record for every installation step. To meet both demands, Advanced Work Packaging (AWP) software for nuclear EPCs needs to do three jobs:

• Turn your 3D model, schedule and materials data into construction and installation work packages
• Release a package to field crews only after all its constraints clear
• Link installed work to completions and turnover records

When the software falls short on any of these three jobs, your planners end up manually checking readiness and chasing records while the outage clock runs.

What Nuclear EPCs Need from AWP Software

Whether the work is a refurbishment or a new build, your planners need software that supports the full work package hierarchy, from Construction Work Areas through Construction Work Packages (CWPs) down to Installation Work Packages (IWPs). The software has to keep every package up to date as engineering changes. New builds add one more demand: the same plant scope often repeats across units and sites, so the software has to let planners template the project and start each new unit from the last unit’s setup and lessons learned.

On every unit, work packages cross company lines, passing between your team, subcontractors, fabricators and the Owner. Each company should see and change only what its contract role allows, but every company should work from the same up-to-date package data. When a subcontractor updates a package, your team and the Owner should see the change right away.

Integration with Engineering Suites, Primavera P6 and Document Control

A work package is only as up to date as its source data, so integration is the first thing to test. Ask every vendor to demonstrate these five connections live:

• 3D model parsing: Can the software load large models from your design suites as whole files, then break each model into components that planners can group into packages?
• Schedule link: Does a schedule change in P6 update every affected work package, and does field progress flow back to P6?
• Materials status: Does the software pull component-level material status from your materials management and enterprise resource planning systems?
• Document control: When a drawing or procedure is revised in your document control platform, does the software flag every package the revision affects?
• Open APIs: For systems without a pre-built connector, does the vendor offer documented enterprise REST APIs?

Field Execution and Readiness Tracking

Once integration keeps package data up to date, the next test is whether field crews receive packages ready to start. In a demo, spend the most time on workface planning and readiness tracking. Look for:

• Suggested package scopes that planners can adjust graphically in 3D
• Constraint tracking on every IWP for engineering, materials, procedures, permits, scaffolding, access and inspection resources
• Scaffolding requests created from each IWP
• An approval workflow that releases only constraint-free packages to crews
• Mobile access so forepersons, field engineers and crews can open and update their packages at the workface
• Component-level progress against rules of credit, rolled up to earned value

Then ask the vendor to walk one IWP live from model to release to completion, clearing each constraint along the way. Score any capability missing from that walkthrough as not supported until the vendor demonstrates it.

Audit Trail and Records

Every package release and every progress update from the field becomes part of the project record. For a nuclear project, that record is itself a deliverable. Look for software that keeps a full change history on every package, showing who made each change and why. The same software should tie each inspection record, walkdown and material certification to its installation or test package.

Your team should be able to link IWPs to the plant systems they complete. A system completions view then shows status, open punch list items and test results for every system in one place. With completions and inspection records in the same software, your team builds turnover packages without chasing records across tools.

Evaluation Checklist for Nuclear AWP Software

Use these 15 items to score vendors side by side. Rate each item as out of the box, configurable, on the roadmap or not supported.

1. Builds the Path of Construction (PoC) and CWPs graphically, with scenario planning
2. Templates the project so each new unit starts from the last unit’s setup and lessons learned
3. Controls access by contract role across companies
4. Gives the Owner visibility without forcing a tool change on subcontractors
5. Parses large 3D models from your design suites
6. Links packages to P6 activities in both directions
7. Pulls material status at the component level
8. Flags packages affected by drawing or procedure revisions
9. Tracks constraints on every IWP and releases only constraint-free packages
10. Gives forepersons, field engineers and crews mobile access to their packages at the workface
11. Rolls component-level progress up to earned value using rules of credit
12. Keeps a full audit trail of who changed each package and why
13. Ties inspection records, walkdowns and material certifications to their installation or test packages
14. Links installation work to plant systems and their test and turnover packages
15. Runs your project in a single-tenant environment with enterprise-grade security, backed by SOC 2 Type II, a SOC 3 report and ISO certification, with country-specific hosting available

For criteria that apply to any capital project, from workflow fit to scalability, see our guide to evaluating AWP software.

Frequently Asked Questions

Can You Run AWP on a Nuclear Project with Spreadsheets?

You can start with spreadsheets, but a spreadsheet can't connect constraints to model revisions, so readiness checks turn into manual work. On a multi-unit program, your planners repeat those checks on every unit.

Do the Owner and the EPC Need to Use the Same AWP Software?

No. Each EPC can plan and execute in its own system. Owners increasingly expect EPCs to show an AWP execution plan, and some Owners then use oversight software to read each EPC's package data. Your AWP software still has to share that data with the Owner's tools, so test that connection in every demo.

Explore AWP Software for Nuclear EPCs from O3

Nuclear EPCs need AWP software that keeps packages ready for field crews and the record complete through turnover. O3 has a product for each team on the program:

• Planning teams use ONPlan, O3's front-end planning software, to run scenario planning for the PoC before execution starts.
• Execution teams use ONBuild, O3's engineering and workface planning software for construction execution, to scope IWPs graphically, manage constraints and track package releases from engineering through completions.
• Commissioning teams use ONComplete, O3's completions software built for owners, EPCs and contractors who need to carry a project from mechanical completion through commissioning and startup. 
• Field crews use ONField, O3's mobile app, to work their packages at in the field.
• Owners use ONSight, O3's oversight software, to track progress on each work package while EPCs and subcontractors keep their tools of choice.

With O3 Solutions, every team works from the same up-to-date package data instead of reconciling separate spreadsheets. O3 integrates with any system seamlessly through out-of-the-box (OOTB) integrations or enterprise REST APIs, so it connects to the design, scheduling and document control systems your team already uses.

To see what Owners want in AWP software, download the AWP Software Requirement Matrix. It sets out more than 250 requirements Owners use to judge an EPC's AWP plan and tools.

Request a demo to see how O3 works for your nuclear program.