Professional Documents
Culture Documents
PS.13
PEER REVIEWED PAPER
his paper briefly describes the development of • Short duration provides rapid feedback on probability of
PS.13.1
2006 AACE International Transactions
OBJECTIVE
• Determine a detailed list of bills of material (BOMs).
Improve poor productivity and reduce risk due to reactive • Determine cost breakdown structure (CBS).
construction management and poor workforce planning. • Determine resource requirements, i.e. labor, equipment and
materials.
• Sign off on estimating readiness checklist.
CWP (CONSTRUCTION WORK PACKAGE) • Identify work environment, height, complexity, accessibility,
DEVELOPMENT PROCESS etc.
• Expected productivity factors.
The CWP development process was developed as a result of • Inclusions and exclusions.
root-cause analysis, lessons learned and the need to take a more • Execution constraints.
proactive approach to project execution. Refer to figures 1
through 3. Field Engineering
Engineering work packages (EWP) are frequently too large
for effective management and control; their execution can last • Identify and resolve technical issues prior to construction.
several months to over a year. • Develop an inspection and testing plan (ITP) package.
Typically the crew is several months into construction • Develop a CWP quality document.
execution before the realization that the schedule is starting to • Create a CWP-specific scope statement.
slip. By the time there is a clear understanding of where things are • Develop pre-pour plans, rigging plans and other specialized
going it is usually too late to change the outcome. EWPs must be plans.
broken down into manageable sizes, hence the CWP philosophy. • Determine and ensure necessary equipment is available.
The CWP process requires a Field Engineer and a Discipline • Prepare turnover documentation.
Construction Specialist who from the 3-D model pre-package • Review bills of material (BOMs) for technical and quality
chunks of work by area and discipline (according to the Work compliance.
Breakdown Structure (WBS)) into packages roughly estimated to • Initiate purchase orders (POs).
have construction duration of one month. The rules for work • Receive and verify incoming orders.
packaging that apply are: • Initiate non-conformance reports (NCRs) for non-
conforming products.
• No overlap between discrete work packages; • Identify material overages, shortages and damages (OS&Ds).
• Seamless integration of the packages; • Ensure warehousing of materials and supplies retains
• Clear cost and estimating delineation. products as fit for purpose.
• Sign off on field engineering, materials management and
These work packages are entered into a log for future use and quality management readiness checklists.
integration into turnover work packages (as most of these large • Ensure all materials are ordered.
projects are turned over and started up as systems). • Ensure all materials are ready for construction.
As soon as the CWP package has been defined, the necessary • Sign off on field engineering readiness checklist
engineering information is compiled and sent to document
control. The CWP development team then assembles it. Project Controls
The CWP is developed in two sections: The first section
provides essential information, documents, plans, drawings, • Ensure measurement metrics are in place.
hazard analysis, turnover and quality documents etc. necessary for • Ensure budgets are in place.
the construction crews to execute the work. The second section • Ensure cost structure is developed and in place
provides site-sensitive data such as detailed estimating data; • Ensure scope items are correctly cost coded.
project controls metrics, turnover and acceptance criteria, • Develop a schedule that is manpower-loaded and optimized.
performance data and other information that may or not may not • Identify out-of-scope work and initiate change requests.
be issued to Construction depending on the organization. • Set up cost-coding structure against Work Breakdown
Structure (WBS).
• Set up time tracking for CWP.
ROLES AND RESPONSIBILITIES • Ensure correct coding of effort.
• Verify quantities against original scope.
Each team member has two roles: • Measure installed quantities.
• Verify completion of CWP.
1. One as a Subject Matter Expert (SME), • Sign off on project controls readiness checklist.
2. The other as a supervisor / functional team lead.
Estimating
PS.13.2
2006 AACE International Transactions
Construction • Less claims resulting from endless changes;
• Use a separate crew for executing changes after the package
• Develop comprehensive scope statement. has been completed.
• Determine construction methodology.
• Identify constraints and potential hazards. CWP Team Collectively
• Identify special construction issues.
• Determine crew size and mix for the CWP. • Ensure good integration of all activities, i.e. information flows
• Develop a mini plan on how the CWP will be executed with seamlessly from one activity to another.
team support. • Review and discuss opportunities for improvement.
• Sign off on construction readiness checklist. • Ensure all the pieces of the puzzle come together prior to
construction.
Safety • Sign off on an overall construction readiness checklist. Any
deficiency requires the project manager to make a go or no go
• Review CWP for special safety requirements. decision to proceed with execution.
• Carries out HAZOP to identify specific hazards to the CWP.
• Identify and establish appropriate Personal Protection Special Instructions
Equipment (PPE).
• Arrange timely safety training. • Any special instructions pertaining to a work package need to
• Sign off on safety readiness checklist. be stated to ensure nothing is missed. This will prevent
substantial re-work. This might also identify specific risks, that
Document Control the construction team is aware of can be prevented or
mitigated.
• Ensure all drawings for the CWP are current and that the
latest revisions have been used for the CWP development.
• Receive completed CWPs that are ready for construction. LESSONS LEARNED
CWPs that cannot be completed or are not ready are also
placed in document control but have a hold placed until the Several "lessons learned" were identified early on and one of
outstanding issues are resolved. the problems due to a late start was the co-location of the CWP
• Document all arrival and departure dates of information and development team could not be implemented as team members
data flow. were distributed over three distant locations. A scheduled CWP
review meeting effectively reduced the problem. Teams should be
Project Planner treated as though they were co-located to ensure unity of purpose.
Another issue was the availability of quality assurance staff for ITP
• Determine scheduling priorities in conjunction with the development. Using field engineers, who effectively managed
construction manager. quality, field engineering and material management issues,
• Support work face planning with construction supervision mitigated this. This reduced the overall cost and size of the CWP
• Ensure the correct number of CWPs is under execution development team. Originally the intent was for the CWP team to
according to the agreed cash flow and manpower loading. package the work but this did not work. It was more effective to
use a Field Engineer and a Construction Specialist to pre-package
CWP Development Team (typically 5 members) the work using the 3-D model prior to the CWP team packaging
the work.
• Provide issue resolution for construction teams The Field Engineer and the Construction Specialist
• Have a comprehensive understanding of the CWPs that they managed both the packaging and subsequent development and
have developed. this kept the team to a manageable cost and size.
• Are able to provide clear understanding of execution strategy, Optimal work package sizes have been stated as not
basis of estimate and what is in scope and what is not. exceeding 80 hours. Given the sheer size of the project this would
result in an excessive number of CWPs and this remains to be
Construction Crew optimized for these large projects. Early results are extremely
positive and feedback indicates a high probability of
• Execute CWP according to mini plan that provides the strat- organizational acceptance.
egy for execution, the scope, schedule, and all of the For optimal cost / benefit ratio, work-package sizing should be
necessary information to execute as planned. a one-step process rather than the current two-step process
Once the CWP has been executed and signed off as complete and
Expect the following benefits all quality requirements are met, lessons learned review is carried
out between the CWP Team and the Construction Crew.
• Motivated workforce;
• Minimal changes and disruption during execution; The Questions to Ask
• Better productivity;
PS.13.3
2006 AACE International Transactions
• Did we provide you with the right amount of information to a multi-stage process at best. At worst, large CWPs (i.e., EWPs)
properly execute this work package? will continue to be executed without further decomposition and
• What can we do better for future CWPs? projects will continue with unreliable forecasts. Work packaging
• Did we provide you with too much information? If so where can become an effective tool in the project management process
can we reduce it? if implemented with specific goals in mind. They are not a
panacea for construction planning failures and they take time to
This is carried out a few times until the process is optimized. implement and to be learned effectively. CWP Provide a
Requirements vary form project-to-project and are dependent consistent methodology that facilitates optimization and cost
upon the experience of the crews. It is essential that this lessons reduction (over time).
learned review be carried out as soon as possible to ensure rapid
optimization and cost benefit to subsequent CWPs. It is important
that once a CWP has been executed that it is closed out and no CHALLENGES
further activity is necessary until system turnover and
commissioning takes place. Generally implementation went well the biggest challenges
were:
PS.13.5
2006 AACE International Transactions
PS.13.6
2006 AACE International Transactions
PS.13.7
2006 AACE International Transactions
PS.13.8
2006 AACE International Transactions
PS.13.9
2006 AACE International Transactions
Figure 5
PS.13.10