Making The Case For Advanced Work Packaging As A Standard (Best) Practice
Making The Case For Advanced Work Packaging As A Standard (Best) Practice
Prepared by
Construction Industry Institute
Research Team 319, Making the Case for Advanced Work Packaging
as a Standard (Best) Practice
CII members may reproduce and distribute this work internally in any medium at no cost
to internal recipients. CII members are permitted to revise and adapt this work for their
internal use, provided an informational copy is furnished to CII.
All CII members, current students, and faculty at a college or university are eligible to
purchase CII products at member prices. Faculty and students at a college or university
may reproduce and distribute this work without modification for educational use.
Chapter Page
1. Introduction 1
v
consistent improvements across six project performance dimensions:
productivity, cost, safety, schedule, quality, and predictability. The
research team also documented additional benefits, difficulties, and
lessons learned to support practitioners during AWP adoption.
A key finding was that even initial implementations (i.e., projects with
low maturity) garner significant benefits from AWP. This is encouraging
for organizations that are low on the AWP learning curve. At the same
time, benefits increase as AWP implementation matures, which supports
further investment. Overall, the data collected by both research teams
presents strong evidence that the benefits of AWP are consistent and
that there is a compelling case for further adoption by the industry.
vi
1
Introduction
1
ADVANCED WORK PACKAGING
WORKFACE PLANNING
Construction
Front End Planning
Commissioning
Detailed Engineering Start Up
3
Objective
Validate AWP Benefits Identify AWP Maturity Levels
5
2
Productivity
Process
Adherence Cost
Schedule
AWP
Organizational
Implementation
Alignment
Safety
Contract Quality
Integration
Predictability
7
RT 319 identified and investigated these prerequisites on the basis
of the RT 272 finding that effective AWP implementation requires early
strategic planning and the commitment of resources to align AWP
deliverables at the CWP/EWP/IWP level. Once the level of AWP practice
is assessed, it can be related to performance outcomes. The RT 319 AWP
implementation framework organizes performance improvement data
into six main dimensions: productivity, cost, schedule, safety, quality, and
predictability. When attached to qualitative and quantitative measures,
this framework supports data analysis and generates meaningful results.
The following section discusses the case study and survey results of the
team’s model validation effort.
The research team canvassed the CII membership and the audiences
at international AWP-related conferences to identify appropriate industrial
projects for its case studies. The unit of analysis of the case study was the
single project. The final sample involved different industrial construction
sectors and included small, medium, large, and mega-projects in the
United States and Canada. (See Figure 4.). The case study results are
strongly supported by the team’s expert interview findings, and these are
incorporated into the discussion of the case studies below.
AWP Prerequisites
After identifying and defining the most recurrent and significant AWP
prerequisites, the research team sought to validate their impact through
its case studies. The results confirmed the relevance of the three
antecedents, isolating the following characteristics:
8
Chemical
15% (3)
Power
25% (5)
Infrastructure
10% (2)
Medium
10% (2)
Small
25% (5)
Large
35% (7)
Mega
30% (6)
9
flexibility is allowed and encouraged. To ensure that all AWP core
principles are effectively incorporated, each project management
team should adapt the prescribed procedures in accordance
with project characteristics and participants’ background. An
elaboration process should be in place to translate recommended
flowcharts into specific execution procedures.
2. Organizational Alignment. The alignment across project
disciplines, particularly among engineering, procurement, and
construction teams, is a fundamental driver of successful AWP
implementation. To achieve this alignment, the project team
should define a coordinated and integrated information flow
throughout the different project phases. Organizational alignment
also depends on minimizing change aversion to AWP; it is critical
to resolve and minimize disputes among project participants
and to ensure the team building progression that is necessary to
achieving AWP benefits. Top management buy-in and continuous
commitment have been proposed as the best ways to minimize
change inertia. After an initial implementation period, workforce
satisfaction related to AWP execution typically increases. This
is a consequence of the enhanced engagement of construction
representatives during the planning process and a result of higher
crew morale from safer and more productive onsite operations.
This deeper engagement also increases crews’ awareness of
the impact of changes on the chain of activities, discouraging
unauthorized deviations from approved plans.
3. Contract Integration. The inclusion of AWP in contracts can
greatly affect the behavior of project participants and is crucial
to the implementation process. Contracts should define payment
plans and control processes in line with AWP deliverables. When
the schedule of payments is not coherent with AWP milestones,
project participants are not incentivized to adopt AWP and change
traditional planning practices. The controls process plays a
significant role in supporting AWP implementation and should be
integrated across the various disciplines to prevent opportunistic
behaviors. To enforce the adherence to construction sequence at
an operational level, project planning and completion should be
10
monitored by IWP. It is the responsibility of the owner to identify
and require that specific AWP data are collected, analyzed,
and stored, to ensure that AWP deliverables are on track with
project plans. The case study analysis revealed the importance
of defining specific roles and responsibilities in alignment with
AWP processes. Responsibilities should be identified as early
as possible during preliminary planning and included in key
participants’ contracts. An ad hoc project responsibility matrix for
AWP implementation should be developed to prevent responsibility
and skill gaps.
Project Performance
The case study analysis provided detailed findings on the relationship
between AWP implementation and higher levels of project performance,
compared to traditional project execution. The case studies generated
the following results for AWP performance improvements:
11
2. Cost. The findings revealed consistent cost savings for all projects
implementing AWP, showing most of the reductions to be between
five and 10 percent of TIC. These savings were mostly related
to productivity improvements. The case studies also showed
systematic budget overruns on previous projects without AWP.
When AWP was used, the budget definition itself was a more
precise and accurate estimate. Contractors reported cost savings in
relation to the increased utilization of equipment, even with time and
materials contracts. The simultaneous execution of AWP on sites
with multiple projects presented an opportunity to share common
equipment, which provided consistent savings during construction.
AWP enhanced cost performance by allowing the identification of
cost savings opportunities, starting at preliminary planning. The
project management teams were also able to reduce scope overlap
during the preliminary planning stages. These savings should be
shared between the owner’s representative and the EPC contractor
to foster cost optimization behavior among all participants.
3. Safety. The 20 case studies reported zero lost time accident after
more than 25 million construction hours. Construction managers
reported that, after the introduction of AWP, they saw safety
performance improve in comparison with historical averages.
The case studies deduced six main reasons for the positive
relationship between AWP implementation and improved safety
performance.
–– AWP formally focused attention on identifying and mitigating
safety issues during the planning and development of IWPs,
before field mobilization.
–– The area-based design of IWPs helps keep crews in one
single area to perform their specified work; in this approach,
field workers become familiar with the areas they work in, and
unnecessary movement around the site is minimized
–– Crews have to remove all materials from the site after each
shift, thus reducing the risk of accidents.
–– The reduction of schedule compression that characterizes
the AWP methodology reduces the recourse to overtime,
which reduces worker exposure to hazards by shortening
time spent in the field.
12
–– The IWP closeout process prescribes the collection and
incorporation of feedback, including safety observation. This
process supports the minimization of safety hazards for
construction activities in the future.
–– IWPs are designed to include a specific “safety requirements”
section. Because crews are briefed on safety topics before
the beginning of construction activities, their awareness of
potential risks increases.
13
Another quality enhancement was related to the integration of
the different quality assurance programs among key project
participants. The early identification of IWP quality standards
provided project team alignment and a clear definition of
responsibilities, making quality controls and reporting easier. This
allowed all project parties to use the same measurement base
for the whole set of construction activities, shedding tremendous
light on the project’s quality. In general, AWP was also related
to the reduction, in absolute terms, of total RFIs generated. The
proportion of RFIs also shifted from the construction phase to the
detailed engineering phase, a point in the project life cycle at which
their impact on project cost and schedule is comparatively minor.
6. Predictability. AWP was related to high project predictability due
to the high reliability of the cost, schedule, and quality estimates it
generates. AWP fosters the proactive identification and mitigation
of construction constraints, starting at initial project definition. The
various packages are released and issued to the field only when
they can be promptly executed; and they arrive with all necessary
materials, drawings, and equipment specifications. Each
package is developed with the support of construction personnel,
ensuring that the estimates are realistic and achievable. Project
predictability was also related to more consistent process stability.
Planning and implementation errors are typically discussed during
meetings and are incorporated into project procedures to prevent
future mistakes. AWP is effectively a tool to manage project
variance and to incorporate construction flexibility, isolating the
effects of contingencies and uncertainty on individual packages
without affecting the entire chain of activities.
If a package is stopped by a constraint, the availability of a backlog
of IWPs allows the project team to shift the working crews onto
other activities while restoring operability to the jeopardized
package. The continuous monitoring process at the EWP and
IWP levels allows the quick identification of recovery measures,
so that the working capacity can be redirected to other IWPs. The
performance of contractors is measured more precisely with AWP,
14
and the performance data provide the owner with useful data
about partner selection for future selection. The contractors for the
case study projects were working on multiple projects at the same
time and were able to collect lessons learned from one site and
implement them on other sites.
Engineering
Process Deliverable
Adherence
Contract
Integration
15
For practical reasons, the research team chose to test only the
predictability dimension—instead of the entire set of performance
improvements—during the data collection process. The team selected
the Partial Least Square (PLS) statistical technique to accomplish the
following hypothesis-testing:
16
in a favorable light). To minimize expert bias, the audience was asked to
refer only to the most recently completed project, so that respondents
should not choose between the best or the worst executed projects. The
choice to ask for data on the last executed project was also intended to
reduce potential memory bias. To minimize the social desirability bias,
data were collected by means of hand-held response devices, which
guaranteed the anonymity of every response. A potential drawback of
using hand-held response devices lay in the fact that, once respondents
had answered a question, they could not return to it if they felt the need
to revise or change it. To minimize the risk of misunderstanding, each
question was projected and explained by one of the academic team
members. Since the polling time for each question was approximately
one minute, participants could change their final answer for a specific
question during that time.
From a total of 104 distributed devices, the team collected a final set
of 92 complete responses. The sample was considered representative
of the industrial construction sector, populated by respondents with
considerable construction experience. (See Table 1.) The survey
population also comprised a variety of industry roles (See Figure 6.)
Experience Number of
Percentage
(years) Respondents
Less than 10 20 22%
Between 10 and 20 26 28%
Between 20 and 30 30 33%
More than 30 16 17%
Total 92 100%
17
Other Owner
13% (12) 24% (22)
Supply Chain
5% (5)
Engineering
13% (12)
Constructor
45% (41)
In the course of the data analysis, the team addressed sample issues
by checking for under-coverage bias, nonresponse bias, and voluntary
response bias. Under-coverage bias was reduced through the selection
of multiple companies with different project participants. Nonresponse
bias was negligible, since 88 percent of interviewed participants
provided complete answers (92 out of 104). Voluntary response bias was
also minimized through random distribution of the devices among the
conference participants. This approach meant that the respondents with
potentially strong opinions had the same chance of being selected as
those with more neutral perspectives.
Once the data had been analyzed, the research team accepted the
two hypotheses and confirmed the relationships depicted in the survey
model illustrated in Figure 5. The analysis yielded the following results:
18
• AWP causes project predictability, measured in terms of
time, schedule, and rework. Among all factors influencing
project predictability, AWP emerged as especially significant.
The results showed that AWP influences 25 percent of project
predictability (strong effect).
• AWP causes both timely and complete engineering
deliverables and project predictability, regardless of project
size and the role of the company.
After performing more than 10 statistical tests of the analysis and data, the
team found that they all confirmed the validity of results (i.e., they confirm
the reliability and robustness of findings, the adequacy of the sample, and
the goodness of fit of the model). (See RR 319-11, for further detail on the
PLS methodology and on the additional validity tests performed.)
To say more about the nature of the survey and the interpretation of the
results, it is important to note that PLS technique is a well-established
statistical tool within the social sciences, used to assess data similar to
that collected through the RT 319 survey. The PLS analysis provides
both support for causality (expressed as the direction of the arrows in
Figure 5) as well as degree of influence between constructs. Thus, the
team concluded that the statistical model (an expression of the RT 319
analysis framework shown in Figure 3) is supported, and that the analysis
shows causality between AWP implementation and performance results.
The survey results also indicate that AWP has significant explanatory
power and, hence, is a major driver of performance outcomes (e.g., the
model shows 30-percent explanatory power for predictability). These
results do not indicate the expected level of performance improvements
(i.e., the 30-percent explanatory power does not equate with 30-percent
performance improvements). Case study data should be used to assess
performance improvement potential; this is explored in more detail in the
following chapter.
19
3
AWP is a rich practice with many touch points across the project life
cycle. RT 272 observed that projects and organizations generally adopt
AWP practices in stages. This motivated RT 272 to conceptualize three
incremental levels of AWP implementation maturity: 1) AWP Early
Stages; 2) AWP Effectiveness; 3) and AWP Business Transformation.
(See IR 272-2 Volume II for a detailed discussion of these levels.) The
maturity model characterizes these stages in terms of work processes
and required capabilities, recommending a stepwise progression through
the levels to achieve full AWP benefits.
21
level of the specific project (i.e., the gap between planned and actual
project performance in accordance with the six performance dimensions
in the AWP framework). To measure the level of AWP maturity, the
research team adopted the same six scales that were pre-tested and
validated in the survey analysis. To measure the six project performance
dimensions, the research team discussed and adopted six different
indicators: 1) the percentage increase of field productivity in comparison
with previous similar projects or company average (productivity); 2) the
percentage of TIC variation in comparison with estimates (cost); 3) the
percentage of TRIR and DART variation in comparison with previous
similar projects or company average (safety); 4) the difference between
actual and estimated project delivery dates, together with frequency and
magnitude of delays (schedule); 5) the impact caused by field rework
on IWP during construction execution (quality); and 6) the amount and
frequency of changes to and modifications of IWP estimates, in terms of
cost, schedule, and quality (predictability).
Summary Findings
The 15 case studies received a total of 60 different ratings (four ratings
per project). Each team member independently rated five different
projects. The research team then analyzed how each performance
dimension evolved, depending on the AWP maturity values. Results
showed that increasing levels of AWP maturity were associated with
consistent improvements in each project performance dimension. While
RR 319-11 discusses each of these performance measures in detail,
this section presents them in aggregated form. Accordingly, the 60 team
expert ratings were plotted and then interpolated with a polynomial fitting
line. Figure 7 depicts the pattern of project performance at different
levels of AWP maturity. This pattern roughly describes an S-curve, with
moderate performance improvement during the introduction phase,
followed by fast-growing performance during the middle stage, after
which comes continuous improvement, but at a slower rate, as the
company becomes more mature in implementing the methodology.
22
Project Performace
AWP Maturity
The team also tested the validity of this distribution by assessing the
consistency of the various ratings related to same project. Firstly, all the
ratings related to the same project had similar scores and showed a
negligible variance. Secondly, the average of ratings per project evinces
the same S-curve pattern, confirming the validity of the initial S-curve
pattern. (See Figure 8.)
23
Project Performace
AWP Maturity
Each maturity stage builds on the elements of the preceding stage, and
all stages are characterized by specific traits, ranging from AWP strategy,
to organizational integration, control processes, and training support.
The three stages also present distinctive performance expectations and
varying adoption barriers that senior managers should take into account
to advance the implementation process and, consequently, to improve
performance.
24
Project Performace AWP Early Stages AWP Effectiveness AWP Business Transformation
AWP Maturity
25
Productivity
Quality Cost
Predictability Safety
Stage I
Stage II
Schedule Stage III
26
Table 2. AWP Maturity Stages and Project Performance
Maturity Stage
Performance 3. AWP Business
1. AWP Early Stage 2. AWP Effectiveness
Dimension Transformation
Productivity Around 10% increase Around 25% increase Around 25% increase
Cost Project on budget TIC 10% below estimates TIC 10% below estimates
Safety Zero lost time incidents (TRIR Zero lost time incidents (TRIR Zero lost time incidents (TRIR
27
below company average) improves with sporadic first- improves with sporadic first-
aids and near misses.) aids and near misses.)
Predictability Significant deviation from Minor changes to execution Execution schedule to plan
baseline estimates schedule
Quality Rework in line with previous Rework slightly below Rework substantially below
quality performance company's average company average; substantial
reduction of RFIs
Schedule Project on schedule or Project slightly ahead of Project slightly ahead of
experienced minor delay schedule during execution schedule during execution
The research findings for each stage are discussed in more detail below.
This examination of the first maturity stage shows that AWP adoption
is initially a top-down process that is expected to generate aversion to
change. At this stage, construction companies have to pay particular
attention to having the necessary flexibility to adapt AWP guidelines to
existing processes. This flexibility prevents cookie-cutter approaches that
only generate further resistance and increase process complexity. This
initial implementation stage is probably the most risky period. A limited
allocation of resources and a partial commitment to AWP adoption can
result in limited performance improvements. Such lackluster results can
in turn lead managers to reduce the amount of effort and support for
the adoption process. Senior managers have the responsibility of guiding
the company through this early adoption stage, and should provide
adequate resources during the pre-planning stage. They should set
moderate performance goals with a slow growth rate and should clearly
28
communicate the commitment of the organization to the implementation
(e.g., by establishing dedicated development teams).
The major risk at this implementation stage comes from the illusion of
doing more than required, which may cause project teams to refrain from
completing the full implementation. So, while a fast rate of performance
improvement is expected, AWP implementation can be further
improved. Construction companies should not reduce the resources
for AWP training activities, but rather increase them to cover as many
personnel as possible. Specifically, companies at Stage 2 had difficulty
obtaining the same level of maturity from project participants that had
not mastered the AWP methodology. Senior management should refrain
from accepting these performance improvements as definitive, but rather
should use the momentum generated by successful project completion
to foster a continuous improvement logic throughout the organization.
Managers should set ambitious goals that grow at a fast rate during
project execution. Publicizing project successes is recommended, since
it can foster a generally positive effect on project team morale.
29
Stage III: AWP Business Transformation
The companies within this group had acquired substantial AWP
maturity, having mastered and implemented the procedures across
multiple projects at once. AWP drove project execution strategy and
was systematically used to create project value by differentiating the
companies from competitors. Implementers extended AWP beyond the
boundaries of the single project and aligned it with plans to advance
strategic business needs. Companies at this maturity stage are
recognized as AWP leaders and, as such, they are expected to share
their know-how with representatives of other project organizations. This
leadership provides an adequate level of expertise across the entire
project management team.
After reaching the third maturity stage, the project management team
had to identify more complex and more resource-intensive improvement
projects. These projects were aimed at developing new skills/roles among
craft personnel—such as AWP planners with extensive construction
experience. They also sought to build networks of project stakeholders
with a similar level of AWP expertise, to minimize bottle-neck effects.
To realize benefits, these projects require a long-term horizon, as well
as continuous top management commitment at the inter-company
level. Senior managers should grant local managers considerable
30
independence, thereby balancing top-down direction with increased
bottom-up autonomy. Senior managers can also leverage local expertise
by moving mature middle management to projects on which the AWP
maturity level does not meet organizational standards. Managers
should set ambitious project goals, but should expect a slow rate of
improvement during project execution. The awareness of the S-curve
effect is fundamental to preventing the withdrawal of additional resources
for AWP implementation. Indeed, understanding this effect counters
the common, but mistaken, assumptions that the slower improvements
are due to a completed implementation process and that aggressively
pursuing efficiency is the correct way to progress.
31
4
33
• AWP implementation is positively related to project performance
at every maturity stage. Achieved benefits consistently surpassed
the resources allocated for AWP implementation. Managers are
encouraged to allocate adequate resources during the planning
stage to achieve the demonstrated benefits.
34
Notes
35
Notes
37
Research Team 319, Making the Case for
Advanced Work Packaging as a Standard (Best) Practice
Steve Autry, ConocoPhillips
Michael Bankes, Fluor Corporation
Joel Gray, Coreworx
John Hyland, Lauren Engineers & Constructors
Robin Mikaelsson, Bentley Systems
* William J. O’Brien, The University of Texas at Austin
Bryan Parsons, KBR
* Simone Ponticelli, The University of Texas at Austin
* Jim Rammell, Wood Group Mustang
Stan Stasek, DTE Energy
Glen Warren, Retired – Construction Owners Association of Alberta
* Principal authors