Home » AWP Blog | Latest in AWP » AWP Case Studies » Case Study: Assessment of WFP Procedures and Recommendations
Fort McMurray, Alberta
Approximate TIC $1.8 Billion
Dec 10 2013
The Construction Contractor procedure is developed from the Last Planner Concept. The original thesis is from Dr. Glen Ballard and identifies the Foreman as the Last Planner. The concept is based upon the methodology of:
Can: Can the work be executed – materials, prerequisites, documents, access etc.
Should: Is the work happening in the right sequence?
Will: develop plans that make it happen
The concept is good but the application is flawed. The process calls for the Foreman to develop plans based upon what should happen (derived from the schedule) and then they spend their time removing constraints to prove that it can happen.
During a previous project this process was applied across the 500+ foremen and after 18 months was abandoned because it was not practical to pull the foremen from the field for the long periods of time that were required to produce plans. The Foremen also lacked the access to data that would allow them to remove constraints so the plans that they created were typically not executed as they were planned.
The hybrid system that was developed to satisfy the project’s planning requirements was to supply one foreman who became a full-time planner and he would develop plans for 5 others.
This application became one of the study groups for COAA that led to the identification of the model for Workface Planning. The procedure itself is ambiguous and suggestive, which means that it is subject to interpretation and is difficult to audit.
The process is centered on the idea that the creation of Field Installation Work Packages is a function of Project controls and the Construction Superintendent is expected to execute work based upon detailed plans created from the schedule. The industry has proven many times that this is not effective. The proven methodology is that the Planner reports directly to the Superintendent and that they create plans that are based upon the Superintendents execution strategy.The content or the development process of the FIWPs is not covered in the procedure and there is only a vague reference to the concept that the Workface Planner should build them.
The content or the development process of the FIWPs is not covered in the procedure and there is only a vague reference to the concept that the Workface Planner should build them.
The ideal procedure would identify: Who, Where, When and How FIWPs are created and then identify the process for tracking their execution (Schedule and Earned Value). These are not covered in the procedure.In
In summary, the procedure is not a tool that could be used to establish the process or be used to gauge its effectiveness. It only satisfies the need to have a procedure.
The following pages are the culmination of 54 interviews conducted over 7 days on Project – G. The Stakeholders interviewed ranged from senior project managers to craft workers on both day shift and night shift across all contractors. The interviewers have witnessed hard copy examples of FIWPs, schedules and other project documents in both the field and office environments. With the exception of the Construction Contractor Earned Value system (refused access), every other department was represented and cooperated in the interview process.
The scorecard is derived from the original COAA scorecard that was developed to support the assessment of Workface Planning applications.The ideal use of the findings
The ideal use of the findings are to build upon the strengths of the processes that are working well and to fill the gaps in the processes that have opportunities for growth. This is based upon the premise that scoring well in each of the project areas will identify a robust application of Workface Planning that will lead to predictable project results.
Process: This review tool has been developed to support the evaluation of project planning and execution in preparation for the application of Workface Planning.
Objective: The process of capturing a project’s planning and execution processes, based upon their alignment with Workface Planning fundamentals, will establish a starting point for the development of Workface Planning integration.
Preparation:
Application:
Summary:
The Reviewer will record highlights from the interviews and suggestions from the interviewees. When the scorecard is complete, the Reviewer will summarize the report to formulate an overall score as a % of the attainable. Then add the suggestions proposed by the interviewees and a list of recommendations that would align the existing processes with the application of Workface Planning.
Project: G | SCORE | Date: Dec 2013 | |||||
Question | Strongly Disagree | Disagree | Neutral | Agree | Strongly Agree | Comments | |
1 | 2 | 3 | 4 | 5 | |||
1.0 Project Definition & Planning | |||||||
1.1 | Early project scope definition includes the requirement for constructability and consideration for Workface Planning. | 1 | WFP not considered. | ||||
1.2 | The Project Management Team have procedures that prescribe the application of Workface Planning for all stakeholders. | 1 | No | ||||
1.3 | Request for Proposals are issued with the requirement for Workface Planning. | 1 | No | ||||
1.4 | The requirement for Workface Planning support is a component of every contract | 1 | No | ||||
1.5 | The initial Project Execution Plan requires construction involvement during the development of the Path of Construction | 1 | No | ||||
1.6 | The initial Project Execution Plan includes a requirement for sequential Engineering and Procurement based upon the Path of Construction. | 3 | No evidence to support. | ||||
1.7 | The initial Project Execution Plan has a requirement for Information Management. | 3 | No evidence to support | ||||
1.8 | The WBS is structured to support the progressive elaboration of work through CWAs, CWPs, EWPs and IWPs. | 4 | CWP, yes FIWP no. | ||||
1.9 | The EWP release plan supports the Path of Construction. | 4 | Yes, | ||||
1.10 | The procurement plan supports the Path of Construction. | 2 | Mods being delivered out of sequence. | ||||
Section 1.0 Total (out of 50) |
Project: G | SCORE | Date: Dec 2013 | |||||
Question | Strongly Disagree | Disagree | Neutral | Agree | Strongly Agree | Comments | |
1 | 2 | 3 | 4 | 5 | |||
2.0 Project Controls | |||||||
2.1 | The project schedule activities are structured to represent complete components of the WBS. (CWAs, CWPs, EWPs & IWPs) | 4 | CWPs and FIWPs are in schedule | ||||
2.2 | The level 3 Project Schedule is developed based upon the Path of Construction. | 4 | |||||
2.3 | The engineering level 3 schedule consists of EWPs that are sequenced to support the Path of Construction. | 3 | |||||
2.4 | The procurement level 3 schedule consists of activities that are sequenced to support CWPs and the Path of Construction. | 4 | |||||
2.5 | The construction level 3 schedule consists of CWPs that support the Path of Construction. | 4 | CWPs appear in the schedule. | ||||
2.6 | The construction level 5 schedule consists of IWPs that support the Path of Construction. | 4 | Influenced by material availability. | ||||
2.7 | Installation unit rates from the project estimate are used for Earned Value Management. | 1 | Different rates used by Construction Contractor and Construction mgt | ||||
2.8 | Rules of progress are established by the Contractor and approved by the Project Management Team. | 3 | Rules of progress established by the contractor. | ||||
2.9 | The Project Management Team have established a standard format for weekly stewardship reports from the contractors. | 4 | Standard reports submitted weekly. | ||||
2.10 | The Construction contractor uses a spreadsheet to track and report constraint removal. | 2 | Checklist for pack development, not used for constraint. | ||||
Section 2.0 Total (out of 50) |
Project: G | SCORE | Date: Dec 2013 | |||||
Question | Strongly Disagree | Disagree | Neutral | Agree | Strongly Agree | Comments | |
1 | 2 | 3 | 4 | 5 | |||
3.0 Information Management | |||||||
3.1 | The 3D model is available to construction | 4 | Restricted access. | ||||
3.2 | Planners have direct access to the latest revision drawings through Document Control. | 5 | Hard copies delivered by document control. | ||||
3.3 | Drawings are identified and stored based upon the WBS. | 4 | Yes | ||||
3.4 | The material management system produces material received reports for construction. | 4 | Yes. Packing list | ||||
3.5 | Materials are received and stored based upon the WBS. | 4 | Yes, material stored in grid. | ||||
3.6 | The Construction contractor has a standard format for IWPs. | 4 | Construction Contractorand Electrical contractor are different. | ||||
3.7 | The Construction Contractor has a procedure for Workface Planning. | 5 | Existing | ||||
3.8 | Workface Planners pull information from a backlog of documents and materials. (Clarification: Imminent construction execution is not relying upon the arrival of documents or materials) | 1 | Zero backlog materials truck to hook. | ||||
3.9 | A scaffold management program is in place that ensures scaffold has been erected prior to IWP release. | 1 | Forman requesting scaffolds, not an IWP constraint. | ||||
3.10 | A construction equipment management program is in place that ensures that equipment is assigned to IWP tasks and is fit for purpose. | 1 | Forman request equipment, not an IWP constraint. | ||||
Section 3.0 Total (out of 50) |
Project: G | SCORE | Date: Dec 2013 | |||||
Question | Strongly Disagree | Disagree | Neutral | Agree | Strongly Agree | Comments | |
1 | 2 | 3 | 4 | 5 | |||
4.0 Workface Planners | |||||||
4.1 | Dedicated Workface Planners develop IWPs | 4 | More planners required. | ||||
4.2 | Workface Planners have supervision experience in field construction. | 5 | Developed from craft | ||||
4.3 | Work processes have been established to ensure planners have access to the latest information. | 4 | 3D model-yes Documents–yes Materials- no | ||||
4.4 | Workface Planners are onsite during construction | 4 | Not on night shift. | ||||
4.5 | The ratio of Workface Planners to direct craft labour is 1 – 50 | 1 | 1-150 ratio | ||||
4.6 | Workface Planners report directly to their discipline superintendent. | 1 | Planners don’t follow the standard. | ||||
4.7 | Workface Planners only develop IWPs for their discipline. | 4 | Working towards this standard. | ||||
4.8 | Each Workface Planner has a desk, phone, computer, internet access and access to a site radio. | 3 | Internet sketchy, restricted office space. | ||||
4.9 | Workface Planners conduct regular field tours with their Superintendent. | 1 | No evidence to support. | ||||
4.10 | Workface Planners have attended formal training for Workface Planning. | Most have formal training. | |||||
Section 4.0 Total (out of 50) |
Project: G | SCORE | Date: Dec 2013 | |||||
Question | Strongly Disagree | Disagree | Neutral | Agree | Strongly Agree | Comments | |
1 | 2 | 3 | 4 | 5 | |||
5.0 Installation Work Packages | |||||||
5.1 | IWPs represent 1 rotation of work for 1 foreman and crew. (500–1000hrs) | 2 | Packages not based on superintendents 10 day scope. | ||||
5.2 | IWPs are free of constraints immediately prior to release. | 1 | No formal constraint management. | ||||
5.3 | All IWPs identify all relevant special conditions. | 1 | Planners not considering special conditions. | ||||
5.4 | Every IWP is reviewed and signed off by the superintendent prior to release. | 4 | Supervisors sign as received, not as approved. | ||||
5.5 | Every IWP is reviewed and signed off by the safety representative prior to release. | 1 | Safety not a constraint, no interaction on packs. | ||||
5.6 | Every IWP is reviewed and signed off by the QA representative prior to release. | 3 | ITP present, FIWP not reviewed by QA. | ||||
5.7 | Every IWP contains a complete Bill of Materials | 4 | Requirement for MTOs in FIWP. | ||||
5.8 | Every IWP is checked for latest revision drawings immediately prior to release. | 5 | Yes | ||||
5.9 | Every IWP appears in the project schedule as a level 5 activity for at least 2 rotations prior to release. | 4 | Limited lookahead. | ||||
5.10 | IWP formats are continuously improved through the feedback that the Workface Planners get from the Foremen. | 2 | Little communication between planners and foreman | ||||
Section 5.0 Total (out of 50) |
Project: G | SCORE | Date: Dec 2013 | |||||
Question | Strongly Disagree | Disagree | Neutral | Agree | Strongly Agree | Comments | |
1 | 2 | 3 | 4 | 5 | |||
6.0 Field Execution | |||||||
6.1 | All direct work is executed from IWPs | 2 | <pstyle=””>Not all disciplines using FIWPs | ||||
6.2 | Workface Planners attend daily coordination meeting with all of the Superintendents. | 2 | Formal meeting once per week. | ||||
6.3 | Responsibility for material coordination of IWPs has been assigned to dedicated coordinator. | 1 | Materials not a constraint. | ||||
6.4 | Responsibility for construction equipment assignment has been assigned to a dedicated coordinator. | 1 | Craft responsible for their own equip. Fit for purpose not checked. | ||||
6.5 | Responsibility for scaffold errection has been assigned to a dedicated coordinator. | 4 | Yes, scaffolding is not a constraint | ||||
6.6 | IWP progress is tracked against the project schedule and posted in common areas. | 1 | <pstyle=””>Progress not being tracked in schedule. | ||||
6.7 | IWPs are not left in the field beyond their scheduled completion date. | 1 | No. solid completion date established. | ||||
6.8 | IWPs are returned to the Workface Planner upon completion. | 4 | Yes. | ||||
6.9 | A backlog of constraint free IWPs is maintained. | 1 | IWPs are not reliant on constraints. There is no backlog. | ||||
6.10 | Adequate management audits are undertaken to ensure alignment with Workface planning fundamentals. | 4 | <pstyle=””>WFP first assessment being conducted. | ||||
Section 6.0 Total (out of 50) |
Project: G | SCORE | Date: Dec 2013 | |||||
Question | Strongly Disagree | Disagree | Neutral | Agree | Strongly Agree | Comments | |
1 | 2 | 3 | 4 | 5 | |||
Summary | |||||||
Total score/ 50 | |||||||
1 | Project Definition & Planning | 5 | 2 | 6 | 8 | 21 | |
2 | Project Controls | 2 | 2 | 6 | 20 | 30 | |
3 | Information Management | 3 | 20 | 10 | 33 | ||
4 | Workface Planners | 3 | 3 | 20 | 5 | 31 | |
5 | Installation Work Packages | 3 | 4 | 3 | 12 | 5 | 27 |
6 | Field Execution | 5 | 4 | 12 | 21 | ||
Totals | 21 | 12 | 18 | 92 | 20 | 163/300 |
Three questions that we have been asked to address here:
Question 1: The COAA model is not definitive (by design) and we do see some alignment between them:
5.2.1 identifies Workface Planners as the developer of FIWPs (COAA rule # 1) COAA Rules 2,3 & 4 are not addressed
5.4.4 states that the IWPs must be constraint free two weeks prior to execution, the COAA model is 4 weeks (rule # 5)
5.3 shows that there is an expectation that the Planners will have direct access to documents, material data and the project schedule. (COAA rule # 6)
5.3.6 describes a weekly work plan that sounds like a weekly integration meeting, which covers the intent of the COAA rule number 7 Although rule # 7 suggests that this is done at an IWP level not a component level as described in 5.3.6
5.2.2 identifies a material coordinator, however the need for scaffold coordination (or for it to be identified as a constraint) is not present. There is also no requirement for a dedicated coordinator for construction equipment or specialty tools (COAA rule # 8)
5.4.4 describes the release process that is identified in COAA rule # 9
5.4.5 details the use of a process that calculates and tracks earned value but it does not specifically note that it is linked to the FIWPs. (COAA rule # 10)
There is no specific reference to a backlog of FIWPs as required in COAA rule # 11.
5.2.3 identifies ‘Craft/Subcontractor Planning Group’ but there is no specific reference to the contractual obligations of Construction Contractor themselves or their subcontractor to execute Workface Planning. (COAA rule # 12) COAA Rule# 13 applies to Owner: the requirement to have a Workface Planning Champion, which is not covered in this document.
The Construction Contractor procedure does not address the need to audit the application of WFP. (COAA rule # 13)
The COAA prerequisites identify: Coding, Contracting, Engineering and Tracking as the foundation for the application of WFP. The Construction Contractor procedure address tracking at a component level but not at a FIWP level. There is no reference in the Construction Contractor procedure to Engineering, cost coding (WBS Structure) or contract language.
The COAA Infrastructure standards identify the requirement for the Construction contractor to develop an org chart for the WFP department and to then create job descriptions which identify reporting structure, qualifications and deliverables for the positions.
The Construction Contractor procedure identifies Workface Planners but does not show who they report to or where they fit in the Org chart. Their deliverables are identified as FIWPs with no mention of constraint management. The ratio of Planners to craft is not identified in the Construction Contractor procedure and there is no reference to a plan for implementation, as identified in the COAA WFP Infrastructure document: WFP-PRC-2013-106-A WFP Infrastructure.
# | Item | Effort Required | Value to the Project | Desired State |
1 | WFP for Safety | Med | Very High | Planned predictable execution of work fronts has created a stable environment that allows a greaterfocus upon safety. |
2 | Constraint management program | Med | Very High | FIWPs are only released to the field when they are free of constraints |
3 | Two week backlog | High | Very High | An established backlog of executable work fronts that is maintained so that there is a steady state of work fronts and there are Plan B options for situations where work is interrupted unexpectedly |
4 | PM Standard for WFP | Low | High | The project Management Team develop a standard for Workface Planning and then manage thecontractor against the standard with established KPIs |
5 | Planners Report to Superintendents | Low | High | FIWPs represent the Superintendent’s execution strategy |
6 | EVM in FIWPs | Low | High | Each FIWP is labeled with the Value that will be earned when the work is completed |
7 | FIWPs in the Schedule | Low | High | Level 5schedulepopulatedwithIWPs,resourceloaded,withplannedvalue baseduponquantities, progressed weekly. |
8 | Manage payroll issues | Low | High | The absence of conflict caused by payroll accounting issues |
9 | Reduce permitting | Med | High | Blanket permits issued for repetitive tasks, which allows a great focus on high risks tasks. |
10 | More Planners | Med | High | High quality FIWPs and optimized field productivity |
11 | 3D models for the Workface Planners | Med | High | Each WFPer develops 3D model shots for FIWPs based upon their unique scope |
12 | Material Management Team | Med | High | Single department that controls all aspects of site materials |
13 | Foremen jump time for crossover | Med | High | Smooth transition shift to shift and Permits in place prior to crews starting = increased time on tools. |
14 | Construction Contractor Procedures | Med | High | Creates an effective model for the execution of Workface Planning |
15 | Review facilities | Med | High | Fit for purpose amenities, trucks and radios. |
16 | Reinstate IPMS | High | High | Single source of material received information |
17 | Improve quality of Engineering | High | High | Minimal revisions and RFIs and workable CWPs |
18 | Robust High Speed WIFI | Low | Med | Effective communication |
19 | Expanded FIWPs | Low | Med | High quality FIWPs that address the Foreman’s needs. |
20 | Document Control – CWPs and Revs | Low | Med | Common access to project documents for all stakeholders |
21 | Supers add durations | Low | Med | FIWP durations are based upon the Superintendents execution strategy |
22 | Life Cycle for FIWPs | Low | Med | FIWPs are completed within the allotted duration |
23 | Indirect activities in the Schedule | Low | Med | All activities are identified and progressed in the master schedule. |
24 | Fully integrated schedule | Low | Med | Fully integrated schedule |
25 | Post the Schedule | Low | Med | Common expectation for performance, well communicated |
26 | Tool Time study | Low | Med | Productivity measurement tool that show the impact of changes, which leads to the optimization of the Workforce. |
27 | All direct work in FIWPs | Med | Med | All scope captured and predictably executed |
28 | Address Bussing issues | Med | Med | Hassel free transportation of workforce. |
29 | LEMs to Construction Contractor | Low | Low | Construction Contractor know who is doing what. |
30 | Utilize WFPers to manage RFIs and FCNs | Low | Low | Single source for all scope related issues |