In nuclear EPC bids, Owners increasingly expect contractors to show an Advanced Work Packaging (AWP) execution plan as evidence that the team can sequence the scope into packages ready for crews to build. Many Owners describe the capability they want instead of naming a vendor, so bidders have to prove that their process, people and software work together in a form the Owner can score.
When a nuclear package reaches the field before its drawings and materials are ready, the Owner pays for idle crews, rework and schedule delays. Work stalls at hold points nobody planned for, and inspection records have to be rebuilt before turnover.
The cost grows when the same plant scope repeats across units and sites. Owners planning multi-unit programs want contractors who plan every unit the same way, so lessons from the first build carry into the next.
AWP is the method built to get work ready before it reaches the field. The Construction Industry Institute (CII) treats AWP as a standard best practice, and CII research found that projects using AWP decreased total installation cost by up to 10% and increased field productivity by up to 25%. Owners want the same gains on their own projects, so they compare bidders on execution as well as on price and schedule.
Owners who ask for an AWP execution plan look at four areas.
Owners want to see how your team will divide the site into Construction Work Areas and set their order in a Path of Construction (PoC). Your team then breaks scope into Construction Work Packages (CWPs), with engineering and procurement delivering in PoC order. On nuclear construction, the outage plan drives the PoC for a refurbishment and the module setting sequence drives the new-build PoC.
Expect questions on how your team releases Engineering Work Packages in construction sequence and tracks material status against each CWP. Owners then check how a design change reaches packages already in the field before crews build to a superseded revision.
Constraint management is where Owners test whether the execution plan will hold up once crews start work. They want proof that Installation Work Packages (IWPs) reach crews only after drawings, materials, procedures, permits, scaffolding and inspection resources are confirmed. Owners also expect workface planners to track those constraints in software the whole team can see.
Owners want every progress number tied to rules of credit, the agreed steps that earn percent complete on each component. The plan should link each package from installation to completions, testing and turnover. Owners will ask how your team records inspection results as crews finish each package and when the Owner's team can see those results.
Evaluators score evidence and give little weight to promises. A strong AWP section of the proposal does four things:
When the Owner provides a requirement matrix, answer every line directly. For each line, state whether your software fully supports, partly supports or lacks the capability listed. Then note whether that capability works out-of-the-box (OOTB) or needs configuration, and point the evaluator to a demonstration. Owners compare matrix answers across bidders, and a "yes" your team can't demonstrate makes evaluators doubt every other answer in the matrix.
Owner evaluators often find the same five weaknesses in a contractor's AWP section, and any of the five can lose the bid. Look for:
The contractor, in most bids. Owners leave the choice to the EPC or contractor, then score the software as part of the execution plan and look for proof that the software works on a live project. Some Owners also want progress data across contractors, so check the bid documents for data-sharing terms before your team commits to its software.
Most Owners combine three inputs: a written execution plan, answers to a requirement matrix and a live demonstration. Evaluators check the plan and matrix answers against the demonstration, so build all three from the same project data.
Yes. Show where your team has run AWP on other capital projects and explain how the PoC changes for outage-driven or module-driven work. Then name the planners who will lead the packaging, so the Owner can see that the people who ran AWP on those projects will run the nuclear work.
If you haven't done AWP on another capital project, reach out to O3 to discuss how our services may be able to get you prepared.
Many nuclear EPCs are new to AWP. A team that bids with an AWP plan on paper and stands up the software after award loses the first months of the project to setup, just when the Owner expects packages in the field.
With O3, an EPC builds its AWP execution plan and sample packages in the software that will run the project, so the plan the Owner scores is the plan the team executes. ONBuild, O3's AWP software for EPCs and contractors, connects engineering, procurement, and construction in one digital environment. Workface planners track constraints and release IWPs in ONBuild, and the office follows field progress in real time. O3 integrates with any system seamlessly through OOTB integrations or enterprise REST APIs, from the P6 schedule to document control and materials management.
Teams get running fast on O3: a global EPC went live in under 30 days mid-project, working from an Owner-supplied 3D model. Técnicas Reunidas adopted O3 as its corporate standard for all AWP projects after a proof of concept. O3 has supported 600+ projects and 30,000+ users across Owners, EPCs and contractors, and is built to stay with a nuclear program from the first unit to the last.
To see a bid from the Owner's side before the RFP arrives, start with the AWP Software Requirement Matrix. The Matrix shows what Owners want in AWP software: more than 250 requirements an Owner uses to judge a contractor's AWP plan and tools.
Download the AWP Software Requirement Matrix and request a personalized demo to walk through package release and progress tracking in ONBuild.