83,99 €
The most significant unanticipated costs on many construction projects are the financial impacts associated with delay and disruption to the works. Assessing these, and establishing a causal link from each delay event to its effect, contractual liability and the damages experienced as a direct result of each event, can be difficult and complex.
This book is a practical guide to the process of delay analysis and includes an in-depth review of the primary methods of delay analysis, together with the assumptions that underlie the precise calculations required in any quantitative delay analysis. The techniques discussed can be used on projects of any size, under all forms of construction contract, both domestic and international.
The authors discuss not only delay analysis techniques, but also their appropriateness under given circumstances, demonstrating how combined approaches may be applied where necessary. They also consider problematic issues including ‘who owns the float’, concurrent delay, early completion programmes, and disruption. The book has been brought fully up to date, including references to the latest publications from the CIOB, AACEI and SCL, as well as current case law. Broad in scope, the book discusses the different delay analysis approaches likely to be encountered on national and international projects, and features practical worked examples and case studies demonstrating the techniques commonly used by experienced practitioners.
This is an invaluable resource to programmers and schedulers, delay analysts, contractors, architects, engineers and surveyors. It will also be of interest to clients’ professional advisors managing extension of time or delay claims, as well as construction lawyers who require a better understanding of the underlying assumptions on which many quantitative delay analyses are based.
Reviews of First Edition
"John Keane and Anthony Caletka are pukka analysts in that tricky area of delays, programming and extension of time. I highly recommend their book Delay Analysis in Construction Contracts. Buy the book." (Building Magazine, February 2009)
"The book′s stated purpose is to provide a practical guide for those interested in schedule delay analysis. It provides a good in–depth review of the most common delay analysis techniques.... An excellent book, full of practical tips for the reader and very timely in its publication. It is well worth the cost and a good read for anyone involved in schedule delay analysis." (Cost Engineering, February 2009)
It achieves in spades its stated aim of being a practical guide for contractors, contract administrators, programmers and delay analysts, as well as construction lawyers who require a better understanding of the underlying assumptions on which many quantitative delay analyses are based. (Construction Law Journal, 2009)
Sie lesen das E-Book in den Legimi-Apps auf:
Seitenzahl: 542
Veröffentlichungsjahr: 2015
Cover
Title Page
Copyright
About the Authors
Preface to the Second Edition
Preface to the First Edition
Chapter 1: Introduction
1.1 General
1.2 Construction delays
1.3 Burning issues in delay analysis
1.4 Presentation and case study
Chapter 2: Construction Programmes
2.1 Introduction
2.2 Planning and programming
2.3 CPM programming techniques: the fundamentals
2.4 Baseline validation
2.5 Other planning techniques
2.6 Why use CPM planning or scheduling techniques?
2.7 Project controls and the project control cycle
2.8 Records, records, records…
2.9 Predatory programming practices
2.10 Guidance
Chapter 3: Identification of Construction Delays
3.1 Establishing a basis for identifying delay
3.2 Factual evidence and as-built programmes
3.3 Identification of delay events
3.4 Identification and analysis of disruption
Chapter 4: Analysis of Construction Delays
4.1 Introduction
4.2 Selection criteria and guidance
4.3 Summary
Chapter 5: Delay Analysis Techniques
5.1 Introduction to delay analysis techniques
5.2 Summary
Chapter 6: Problematic Issues
6.1 Introduction
6.2 Float and delay claims
6.3 Concurrency
6.4 Programme approvals and onerous specifications
6.5 Acceleration and mitigation
Chapter 7: Effective Presentation of Delay Analysis
7.1 Introduction
7.2 Case study: airport terminal expansion
7.3 Float mapping: approach and methodology
7.4 Demonstrating acceleration
7.5 Presentation skills: demonstrative evidence
Appendix: Contractors Programme Submittals
1.1 Description
1.2 Contractor's Work-plan
1.3 Preparation Guidelines
1.4 Review Update and Revisions
Glossary
Table of Cases
Index
End User License Agreement
ix
xi
xiii
xiv
1
2
3
4
5
6
7
8
9
10
11
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
Cover
Table of Contents
Preface to the Second Edition
Begin Reading
Chapter 2: Construction Programmes
Figure 2.1 Example of a work breakdown structure.
Figure 2.2 Typical work breakdown structure coding definitions.
Figure 2.3 Checklist for creation of a baseline programme.
Figure 2.4 Activity-on-arrow technique diagram.
Figure 2.5 Activity box.
Figure 2.6 Precedence diagram method.
Figure 2.7 Logical relationships.
Figure 2.8 Bar chart.
Figure 2.9 PDM diagram.
Figure 2.10 Example of a network calculation.
Figure 2.11 Completed forward pass.
Figure 2.12 Completed backward pass.
Figure 2.13 Completed forward and backward pass.
Figure 2.14 Planning factors for consideration at a joint baseline review.
Figure 2.15 Frequency distribution curves.
Figure 2.16 Basic Gantt chart.
Figure 2.17 Progressed Gantt chart and Gantt chart with target bars.
Figure 2.18 Line of balance chart. As-planned – internal trades.
Figure 2.19 Line of balance curves 1. Planned versus actual progress – internal trades.
Figure 2.20 Line of balance curves 2. Planned versus actual progress – internal trades.
Figure 2.21 Line of balance curves 3. Planned versus actual progress – internal trades.
Figure 2.22 Project control cycle.
Figure 2.23 Example of cost and programme status.
Figure 2.24 Performance index trend lines.
Figure 2.29 Out-of-sequence – corrected logic.
Figure 2.25 Out of sequence progress report.
Figure 2.26 Originally planned sequence
.
Figure 2.27 Out-of-sequence – retained logic.
Figure 2.28 Out-of-sequence – progress over-ride.
Chapter 3: Identification of Construction Delays
Figure 3.1 As-built programme.
Figure 3.2 Sample updated programme data schedule.
Figure 3.3 As-planned sequence of activities.
Figure 3.4 Activities updated using an ‘auto-update’ function.
Figure 3.5 Effect of inserting manual progress compared with auto-update function.
Figure 3.6 Example of data capture schedule.
Figure 3.7 Typical as-planned and as-built programme.
Figure 3.8 Typical event analysis sheet.
Figure 3.9 Sample of delay register or schedule.
Figure 3.10 Stacking of trades.
Figure 3.11 Disruption – measured mile.
Figure 3.12 As-built programme summary.
Figure 3.13 Labour histogram for mechanical labour hours.
Figure 3.14 Labour histogram for electrical labour hours.
Figure 3.15 Labour histogram for electrical labour hours with additional information.
Figure 3.16 Illustration of multiple trade labour distribution.
Figure 3.17 Productivity curves.
Chapter 4: Analysis of Construction Delays
Figure 4.1 Taxonomy and nomenclature for retrospective methods of delay analysis.
Chapter 5: Delay Analysis Techniques
Figure 5.1 Programme comparison.
Figure 5.2 Fragnet.
Figure 5.3 As-planned sequence with as-planned logic.
Figure 5.4 As-built sequence 1.
Figure 5.5 As-built sequence with as-built logic.
Figure 5.6 As-built sequence with alternative as-built logic.
Figure 5.7 Multiple critical paths.
Figure 5.8 Month-to-month update analysis.
Chapter 6: Problematic Issues
Figure 6.1 Float definitions.
Figure 6.2 Positioning of float.
Figure 6.3 Critical activity profile.
Figure 6.4 Equal concurrent delay.
Figure 6.6 Concurrent delay scenario 3.
Figure 6.5 Concurrent delay scenario 2.
Chapter 7: Effective Presentation of Delay Analysis
Figure 7.1 Float deterioration chart.
Figure 7.2 Case study – driving critical path (April 2007).
Figure 7.3 Driving activities.
Figure 7.4 Case study – concurrent driving critical paths
.
Figure 7.5 Illustration of critical paths.
Figure 7.6 Calculated completion dates.
Figure 7.7 Delays mapped against the as-built critical path.
Figure 7.8 Concurrent critical path employer risk event table.
Figure 7.9 Tribunal expert analysis result.
Figure 7.10 Calculated completion dates.
Figure 7.11 Progress reports output.
Figure 7.12 Power station project.
Figure 7.13 CAD (computer-aided design) model of the power station.
Figure 7.14 Illustration of relocated gas main.
Figure 7.15 Animated model.
Figure 7.16 Weather depiction chart.
Chapter 2: Construction Programmes
Table 2.1 Completed forward and backward pass calculation table.
Table 2.2 Constraint forms.
Table 2.3 Planning tools and techniques.
Table 2.4 Assumed values.
Table 2.5 Steps in calculating the EAC.
Table 2.6 Worked example.
Table 2.7 Main categories of job specific records.
Chapter 3: Identification of Construction Delays
Table 3.1 Hierarchy of documents.
Table 3.2 Sample as-built source reliability hierarchy.
Table 3.3 Types of Delay.
Table 3.4 Categories of source data.
Table 3.5 Causes of disruption and loss of efficiency.
Chapter 4: Analysis of Construction Delays
Table 4.1 Delay classifications.
Table 4.2 The SCL Protocol points of principle.
Table 4.3 Factors for choosing an appropriate delay analysis technique.
Chapter 5: Delay Analysis Techniques
Table 5.1 Categories of delay analysis
Table 5.2 Strengths and weaknesses of the impacted as-planned technique
Table 5.3 Combined IAP model results
Table 5.4 Stages in the application of the TIA technique
Table 5.5 Windows for analysis
Table 5.6 Time impact liability table
Table 5.7 Strengths and weaknesses of the impacted as-planned technique
Table 5.8 Stages in the application of the collapsed as-built technique
Table 5.9 Impact liability Table – collapsed as-built technique
Table 5.10 Strengths and weaknesses of the collapsed as-built technique
Table 5.11 As-built critical path summary table
Table 5.12 Activity level variance table
Table 5.13 Strengths and weaknesses of the as-planned versus as-built technique
Table 5.14 As-built critical path windows
Table 5.15 Window level variance reconciliation table
Table 5.16 Liability assessment
Table 5.17 Identifying the as-built critical path
Table 5.18 Strengths and weaknesses of contemporaneous windows analysis technique
Table 5.19 Summary of delay identified using the month-to-month technique
Table 5.20 Strengths and weaknesses of the month-to-month update analysis technique
Chapter 6: Problematic Issues
Table 6.1 Project float deterioration summary
Chapter 7: Effective Presentation of Delay Analysis
Table 7.1 Available programmes
Table 7.2 Excusable risk events
Table 7.3 Conclusions of time analysis
Table 7.4 Event D, calculations to revised columns
Table 7.5 Raw data for the float map
Table 7.6 Employer risk event table
2nd Edition
P. J. Keane & A. F. Caletka
This edition first published 2015
© 2015 John Wiley & Sons, Ltd
2015 Blackwell Publishing Ltd (First edition first published 2008)
Registered office
John Wiley & Sons Ltd, The Atrium, Southern Gate, Chichester, West Sussex, PO19 8SQ, United Kingdom
For details of our global editorial offices, for customer services and for information about how to apply for permission to reuse the copyright material in this book please see our website at www.wiley.com.
The right of the author to be identified as the author of this work has been asserted in accordance with the Copyright, Designs and Patents Act 1988.
All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, electronic, mechanical, photocopying, recording or otherwise, except as permitted by the UK Copyright, Designs and Patents Act 1988, without the prior permission of the publisher.
Wiley also publishes its books in a variety of electronic formats. Some content that appears in print may not be available in electronic books.
Designations used by companies to distinguish their products are often claimed as trademarks. All brand names and product names used in this book are trade names, service marks, trademarks or registered trademarks of their respective owners. The publisher is not associated with any product or vendor mentioned in this book.
Limit of Liability/Disclaimer of Warranty: While the publisher and author have used their best efforts in preparing this book, they make no representations or warranties with respect to the accuracy or completeness of the contents of this book and specifically disclaim any implied warranties of merchantability or fitness for a particular purpose. It is sold on the understanding that the publisher is not engaged in rendering professional services and neither the publisher nor the author shall be liable for damages arising herefrom. If professional advice or other expert assistance is required, the services of a competent professional should be sought
Library of Congress Cataloging-in-Publication Data
Keane, P. J. (P. John)
Delay analysis in construction contracts / P.J. Keane & A.F. Caletka.— 2nd edition.
pages cm
Includes bibliographical references and index.
ISBN 978-1-118-63117-1 (cloth : alk. paper) 1. Construction industry– Cost control. 2. Construction industry– Planning. 3. Production scheduling. 4. Construction contracts. I. Caletka, A. F. (Anthony F.) II. Title.
HD9715.A2K443 2015
690.068′5— dc23
2015008907
A catalogue record for this book is available from the British Library.
Dr P John Keane, PhD, MSc, FCIOB, FCIArb, DipArb, has 35 years of experience in the construction industry and is currently the principal of a private consultancy practice. Following training as a quantity surveyor, he graduated in construction and commercial management practice, subsequently holding executive directorships within contracting and professional consulting firms.
In the last 25 years, John specialised in the area of dispute resolution and has represented parties in arbitration, adjudication and mediation. He has extensive experience in the United Kingdom as well as in international environments, particularly in the preparation and delivery of expert witness testimony with regard to delay and programming disputes. He is an experienced arbitrator, author and speaker. He also lectures to undergraduate and postgraduate students on construction law-related topics.
Anthony F. Caletka, PE, CFCC, CCM is a civil engineer with over 25 years of experience in construction project and programme management, particularly in large civil engineering projects within the energy, mining, power, and utility sectors, and is a principal with a leading professional services firm. He establishes governance frameworks, contract strategies, project control systems and tools aligned with global best practice, which in turn contribute to the avoidance and resolution of disputes.
Tony is a recognised expert in critical path programming, forensic scheduling, earned value and risk management. He has extensive experience in the delivery of expert witness testimony and advising parties in all dispute resolution forums. He is a frequent speaker and lecturers to post-graduate students on project management and forensic scheduling. He was a member of the drafting committee that produced the SCL Delay and Disruption Protocol.
Accurate delay analysis is an important element in the construction management of projects. For example, early identification of delay events or issues affords an opportunity to manage and mitigate the potential impact on a project. It is also a requirement in post-contract situations where liability and cost impacts for parties have to be identified. The first edition of this book, which was published in 2008, was designed principally to serve as a practical guide to the evolving practice of forensic delay analysis, including a critical review of the main delay analysis techniques available.
Since the publication of the first edition, the evolution of digital technology in processing and communications has been significant. For example, the unfolding technology of ‘cloud’ based data management and transmission offers significant potential benefits to project management and collaboration in terms of identifying, avoiding, tracking, recording and analysing delay issues in real time by multi-disciplined teams based in different locations. Additionally, the volume of information available to delay analysts has increased dramatically, with emails and social media platforms becoming accepted forms of day-to-day communication to facilitate efficiencies in the work flow on most major projects, especially for those in remote locations. To a lesser extent, there have been a number of legal cases that have livened up the debate on certain aspects of delay analysis, for example, float ownership and the principle of apportioning delay.
The feedback we have received on the first edition has been welcome and of assistance in the drafting of this second edition. The new edition has been restructured into a seven-chapter format to balance up the topic areas. The topic of delay analysis techniques is now contained in a separate chapter – Chapter 5. Problematic Issues are now reviewed in Chapter 6, which also includes a modest update to our case law references in order to frame further discussion on a number of subjective issues, which will continue to feed the debates that drive alternative interpretations by delay analysts. Chapter 7 contains updated material regarding delay analysis presentation approaches.
We are once again grateful to those who assisted in the preparation of this new edition. We extend our special thanks to Dr. Paul Sayer, Harriet Konishi and the team at Wiley-Blackwell Publishing for their encouragement and guidance.
John KeaneTony Caletka
Construction delay claims are a common occurrence in projects. When they arise, they need to be evaluated quickly and managed efficiently. However, the whole topic of delay and the various analytical techniques available is one that provokes much debate and controversy due to the seemingly complex and sometimes conflicting guidance provided on these techniques. The purpose of this book is to serve as a practical guide to the process of delay evaluation and includes an in-depth review of the primary delay analysis methodologies available.
The chapters flow logically from an overview of construction programmes in Chapter 2 through to the identification and analysis of delays in Chapters 3 and 4. Due to the complexity of construction contracts and the varying levels of familiarity with programmes or delay analysis, problematic issues arise from time to time when preparing or reviewing claims for additional time. The more common problematic issues are reviewed in Chapter 5, followed by a commentary on some recommended presentation approaches and a case study in Chapter 6.
The views we express are based on combined experience of over fifty years working on a wide range of projects and dealing with programming and delay issues. In practice, most projects are delivered within acceptable time and cost parameters. However, when there is disagreement over the responsibility for unacceptable delays to project completion, major disputes can arise due to the failure to manage the impact of change and claims for additional time in a timely or effective manner during the course of the project. In these situations, there is a requirement for reliable analysis and assessment of the delay impact, which addresses qualitative, quantitative and entitlement perspectives to facilitate an agreement. Much of course turns on the selection and implementation of the most appropriate delay analysis technique. Currently there is little by way of formal instruction in the understanding and application of these techniques with many practitioners being self-taught. Accordingly, one main purpose of this book is to assist those construction professionals responsible for assessing delays by way of explaining some of the underlying assumptions and difficulties that may be faced when using some of the more popular and widely used delay analysis techniques.
As we were trained and practised mainly in the UK and US construction industries, respectively, we have sought to identify and include in this book best practice guidance from these countries. In addition, our experience gained on major civil engineering, building and infrastructure projects around the world provided us with a broad perspective of the nature of delay analysis in practice, which in turn, we have reflected in the approaches and recommendations included in this text.
Delay analysis, which involves both the study and investigation of historic events, also entails assessing which of those events actually affected the completion of a project. This function is fundamental to the success of traditional construction management activity when potential delays must be identified and managed to prevent or reduce their impact on the project's duration and out-turn cost. When carried out forensically, the process takes on a higher significance due to the accumulation of legal and consulting fees, interest on capital and other related costs as well as diversion of key management and operational staff. While forensic delay analysis may take on a higher relevance in the legal forum, it is important for construction and project management staff to familiarise themselves with the prevailing trends regarding the use of critical path method (CPM) programming and project management software as well as recent case law relevant to delay claims and the recovery of time-related damages. This should assist when attempting to settle negotiations over the impact of change and unforeseen events, at the earliest opportunity.
Delay analysis is practised internationally across multinational jurisdictions. We have refrained from including extensive commentary on case law or legal doctrines relevant to compensation for time-related costs. With regard to project management and delay analysis terminology, we have tended, for consistency, to follow traditional UK terminology. For example, although ‘scheduling’ is the common term used in US CPM network analysis, the term scheduling traditionally has a different meaning in the United Kingdom. Although the term ‘scheduling’ is being used more widely for CPM applications in the United Kingdom, we have elected to use the terms ‘planning’ or ‘programming’ for consistency with prevailing UK guidance, texts, terminology and case law.
It is important to note that forensic delay analysis, like many technical fields requiring analysis, is a combination of science and art and requires many subjective decisions and assumptions by the analyst along the way. The methods described in this book do not represent every possible application of the techniques described nor does the book attempt to address every available technique. The appropriate method, and the appropriate application of that method, will depend largely on the circumstances and facts relevant to the case or project at hand. For example, deducing an as-built critical path cannot be computed using computer-based CPM software alone and requires a diligent and objective analysis of the body of information available to the analyst. Any method of delay analysis used should be transparent, forward looking and, most importantly, consistent with and based on a reliable body of factual evidence.
We are indebted to friends and colleagues in the fields of construction and law who through discussion, argument and general banter have contributed in the preparation of this work. We are also grateful to Julia Burden and her team at Wiley-Blackwell for their encouragement and guidance. Finally, last but not least, we thank our families who have patiently endured our absence and supported us most during the writing of this book.
John KeaneTony Caletka
Construction output1 in the United Kingdom represents approximately 7% of the UK Gross Domestic Product (GDP2). In the United States, the proportion for construction output, including manufacturing and mining, constituted 17% of the GDP output3 for 2013 with construction output alone valued at around $900 billion.4 Construction is a unique industry due to it being a fast-moving, complex and dynamic process which depends on the successful coordination of multiple discrete business entities – including professionals, tradesmen, manufacturers, trade unions, investors, local authorities, specialist trade contractors and so on to ensure the delivery of a project on time, within budget and of the required quality. This coordination is dependent on the application of sound planning, programming and project controls, allied to the implementation of tried and tested management techniques. Much of this work is carried out using increasingly sophisticated computer applications that are continually advancing by offering more and more capabilities to the end user.
A survey5 carried out among UK contractors in the mid-1990s found that 49% of contractors did not use computers on construction site locations. Now, not only are computers commonplace in one form or another, but also the use of specialist planning software is common as is computer-aided delay analysis.
Risk is an inherent feature of construction, and it is well known that ‘no construction project is risk free. Risk can be managed, minimised, shared, transferred or accepted. It cannot be ignored6’. If it is accepted that risk is inherent in construction, then it must also be accepted that the likelihood of delays is also inherent in the process and should therefore be anticipated, managed and treated in a similar fashion as risk. When delays are experienced, this is not necessarily an indication that the process or management team is breaking down. Delays are often simply the result of an event which must be managed by a systematic process so as to anticipate the impact of that event on the programme and to minimise the risk of further delay. Systematic management of delay during the course of a project also ensures that the cause of that delay is identified, and documented, at the earliest opportunity. When there is a requirement to identify the cause and effect of delay to establish entitlement to additional time or money, the results of any relevant analysis should be capable of being presented in a clear and unambiguous way.
The most significant unanticipated cost in most construction projects is the financial impact associated with delay and disruption to the works. Assessing the impact of delay and disruption and establishing a direct causal link from a delay event (‘cause’) to its impact (‘effect’), the liability and resulting damages, can be difficult and complex. Contractors and subcontractors require these skills for successful evaluation and presentation of time delay claims. The employer's professional team also requires similar skills and techniques when analysing and evaluating extension of time entitlements under a construction contract. Where these delay issues are not resolved by the contract administrator and contractor in the normal commercial way, then such issues are often left to be decided by third parties in arbitration or adjudication, before dispute review boards or, ultimately, in litigation. All these steps within the dispute resolution hierarchy have different timetables and expectations regarding the evidence required to demonstrate cause and effect. In selecting the most appropriate technique to suit the project and to ensure proportionality is maintained, the following factors must be considered: the relevant facts, the timetable, the nature and number of delay events and the size of the potential dispute.
The purpose of this book is to provide a practical guide to the process of delay analysis for programmers and delay analysts and to inform non-programmers of the nuances of delay analysis techniques available. The book also considers the assumptions which underlie the precise calculations of a quantitative delay analysis, in order to ‘level the playing field’ for non-programmers and experts alike. This entails an in-depth review of the primary methods of delay analysis in use today, along with some familiar secondary methods. The timing and purpose of delay analysis is also discussed, together with a review of the fundamentals of critical path method (CPM) programming. The ‘project control cycle’ is also described in detail. Contemporaneous programming evidence, whether flawed or not, will usually be preferred to retrospectively created programme data, so the emphasis should be on establishing and maintaining an accurate and effective CPM programme throughout the performance of the works.
This book is intended for project and construction management practitioners, contract and legal advisors and programming consultants alike, who not only seek an understanding of the principles, techniques and methodologies involved in the process of delay analysis but also want to understandw the techniques and underlying processes in some detail. Such individuals include those employed by project owners (employers), contractors/subcontractors, legal experts and consultants who often find the need to manage extension of time or delay claims.
The techniques discussed in the book can be used on projects under all forms of construction contract, both domestic and international. Disputes involving delay entitlement and quantification, and which have to be resolved by the intervention of a third party trier of fact, are a frequent occurrence in the construction industry. Over the years, judicial decisions on several key aspects of delay dispute have been handed down by the courts, which have assisted, to some extent, in shaping the way in which delay analysis is undertaken in certain aspects. However, while the implications of these decisions clearly have a great bearing on the work of a delay analyst, it must be remembered that most, if not all, decisions regarding delay analysis are made not necessarily on the method of analysis, but rather on the underlying facts presented and relied upon.
The courts are only presented with delay issues after the event, and therefore decisions handed down mainly provide guidance on retrospective delay analysis techniques which demand, and rely upon, a high level of accuracy and detail with regard to the as-built programme. Notwithstanding the influence of the courts on the process of developing claims for delay and disruption, in order to accord with the ethos of this book, and the actual circumstances and facts many construction professionals find themselves managing, the authors have restricted the use of case law references to a minimum; for instance, where a principle has clearly been established and is commonly referred to in delay claims. Where cases have been referred to, this has not only been restricted to English case law but also includes a small number of significant US cases which are relevant to topics addressed. The US courts have accepted the concept of CPM programming and computer-generated delay analysis submissions since the early 1970s. The English courts appear to lean in the direction of ‘common sense’, whereby the method of analysis is secondary, whether CPM programming techniques were relied upon or not.
It is important that a delay analyst should not become blinkered or be constrained by past judicial decisions in devising and applying delay analysis techniques prospectively in a live project environment. If a delay analyst adopts an unorthodox approach which is acceptable by both parties and resolves a time entitlement claim, then that is to be commended. In the same vein, it is important not to get too hung up on ‘named’ approaches; this is largely another spin-off from judicial involvement in the development of delay analysis. Such named approaches include ‘time impact analyses’, ‘as-planned versus as-built’ and ‘collapsed as-built’ (CAB). These names really only start to have any significance when used as expert evidence to provide a general indication of the approach being adopted by the delay analyst. Even so, there has been little guidance, until recently, as to how each method should be carried out. The primary named methods are often misused in court proceedings, arbitrations and adjudications.
Court decisions and arbitral awards sometimes indicate either a lack of willingness to come to grips with the issues and terminology or a difficulty in fully grasping the intricacies of sophisticated delay analyses. This is entirely understandable as judges are not usually presented with easy issues. The complexity of even the simplest of construction processes often proves to be extremely difficult to convey. Also courts, along with parties' legal advisers, are not always assisted by delay analysts who misdescribe or misapply these techniques and opposing experts who do not take one another's approach ‘head on’. When two opposing party appointed experts refuse to engage the other's method of analysis, this leaves a void where agreed programming evidence should be. These cases often conclude by the tribunal making an assessment based on the facts.
In summary, it is somewhat arbitrary to ‘badge’ and thereby restrict a piece of analysis, and while reference is made in this book to the primary delay analysis approaches, the authors urge caution in becoming too prescriptive because even these primary methods have secondary derivatives and many variations as to how they can be carried out. Also, for this reason, the authors have restricted the use of case law references to a minimum, to allow the site-based practitioner to make informed judgement calls when developing a delay claim rather than simply discounting one method of delay analysis over another, based on his or her understanding of the latest judicial decision mentioning a method of delay analysis being applied by either party.
This book discusses delay analysis techniques and approaches, with their appropriateness under given circumstances, and demonstrates how a combined, or hybrid, approach can be applied, complete with worked examples and case studies. Delay analysis is becoming an increasingly complex activity and there is continual debate and commentary on the primary approaches available. This book brings together the main techniques available in comprehensive primary and secondary categories. The particular techniques described in this book have been successfully tried and tested by the authors in both the commercial environment and in dispute resolution proceedings: adjudication, arbitration, dispute review boards and litigation. This book will serve as a resource guide for those practitioners, advisors, clients or contractors preparing or responding to construction delay claims.
Two major guides have been produced on both sides of the Atlantic to assist those dealing with time extension claims and delay analysis. The first is the Society of Construction Law's Delay and Disruption Protocol, published by the Society in October 20027 (SCL Protocol). The stated aim of the SCL Protocol is to provide useful guidance on some of the common issues that arise on construction contracts, where one party wishes to recover from another an extension of time and/or compensation for the additional time spent and the resources used to complete the project. The second more recent guide was published by the Association for the Advancement of Cost Engineering International (AACEI) in the form of its ‘Recommended Practice No. 29R-03 Forensic Schedule Analysis8’ (RP-FSA). This document, issued on July 1, 2007 was officially launched on July 15, 2007. The RP-FSA is primarily focused on the terminology and the application of forensic analysis and is a much more technical document than the SCL Protocol, although it does not address as broad a spectrum as the Protocol. The stated purpose of the RP-FSA is to provide a unifying technical reference for the forensic application of CPM scheduling and to reduce the degree of subjectivity involved in the current ‘state-of-the-art’ concept while the state of the art in the United States differs from the state of the art in England. Both of these documents are discussed and contrasted in Chapter 4.
Most construction projects will benefit from CPM programming. Only the most basic of projects can and should be planned and managed intuitively. The rest require systematic planning and control. Over the past 30 years, planning and programming have been fundamental building blocks in any project management and control system and, in some organisations, are given equal weight with the budgeting and cost management functions.
CPM is the planning technique most commonly used in the construction industry today and is based on the same critical path analysis principles established in the 1950s. In Chapter 2, the principles of construction planning and programming are explained. These techniques are fundamental in enabling a project to be successfully managed. CPM programming is a tried and tested method and is today essentially unchanged from the earliest applications almost 60 years ago. The chapter describes the essential elements of a successful project through the planning and programming phase and identifies the pre-construction tasks which not only are prerequisites to effectively planning a project but also, conversely in the case of insufficient pre-construction planning, can result in programmes being developed which contain inherent delays.
The stages and life cycle of a construction project are described in detail. The project planning stage is the most important to the development of an effective baseline programme. During the planning stage, the project definition is established. Executing a successful project requires a significant pre-construction effort which questions the underlying assumptions and business case for the project. During this stage, the professional team considers such issues as whether a project is feasible and buildable, whether any new or novel method of construction will be required and whether there are technical, geographical, time and/or financial constraints which would prevent the success of a project.
Chapter 2 also discusses the process of preparing a construction programme, the creation of a work breakdown structure and the fundamentals of CPM programming.
A significant aspect of delay analysis is the interrogation of records upon which reliance will be placed in analysis output. Accordingly, the need for good records and the various categories of required record keeping are explained. Finally, there is a cautionary note on predatory programming practices which should be avoided, along with advice as to how to detect and defend against each.
The identification and assessment of delay entitlement can be difficult and time-consuming. When any degree of complexity is introduced to the mix, it can become particularly difficult for project staff who are often overworked dealing with site issues and other project demands, and who may also be untrained in forensic analysis or programming skills. This often manifests itself as a poor strike rate in achieving extensions of time entitlements by contractors. When the employer's team lacks these skills and awareness, the risk is created of granting inadequate or excessive extensions of time to contractors. To be successful, a time extension claim should adequately establish causation and liability and assist in demonstrating the extent of time-related damages or disruption costs experienced as a direct result of the delay events relied upon. The purpose of delay analysis is to satisfy the causation requirement in such a way that it can be used to assess the resulting damages.
Establishing a basis for identifying delay is the first topic dealt with in Chapter 3. This chapter also deals with the construction phase of a project, as that is generally where the bulk of a project budget is usually dedicated. The construction phase is also the phase in which design delays, or lack of sufficient pre-construction planning, will often culminate into critical delays to completion, as measured by delays to site activities.
Delays may be categorised as excusable, non-excusable, compensable and non-compensable. When demonstrating that a delay is both excusable and compensable, the delay must be shown to be critical, by reference to a reliable critical path analysis. The tests which must be satisfied for a delay to be considered excusable and compensable are described and discussed in Chapter 3.
The carrying out of a successful delay analysis requires the preparation of a reliable as-planned programme and an accurate as-built programme. The effectiveness of delay analysis techniques can be greatly increased when it can be demonstrated that the as-planned programme was reasonable. Further discussion on as-planned programmes is also to be found in Chapter 2. The as-planned or baseline programme is useful contemporaneous evidence of a contractor's original intentions and should serve as the starting point when identifying delays. Unfortunately, there are many ways in which as-planned and progress programmes can be manipulated. Chapter 3 highlights checks that should be made to validate the reliability of such a programme before it should be used for any method of delay analysis.
One of the main objectives of delay analysis is the establishment of a factual matrix and a chronology of the events which actually delayed the project's completion date. One important use of this data is to assist in the preparation and/or validation of an as-built programme. In the ideal situation, an as-built programme will have been prepared and maintained during the course of the works. The data required to periodically maintain and update a project programme can also be relied upon when forensically constructing an as-built programme. The primary sources of raw data required for the compilation of an as-built programme are discussed in Chapter 3, together with a cautionary note about the use of lazy scheduling practices, such as the overuse of constraints, negative lags and ‘auto update’ functions, which can be found in commercially available planning software.
The process of identifying delay events is a fundamental aspect of delay analysis and can be undertaken in two primary ways: either an ‘effect-based’ approach or a ‘cause-based’ one. Both of these are explained in Chapter 3, along with a discussion on contractor and employer risk events.
While this book is principally concerned with delay analysis, it is inevitable that the issue of disruption will have to be dealt with to some extent. Chapter 3 is confined to a general overview of disruption, particularly its interface with delay analysis. In the construction industry, delay and disruption are two terms that are often used in the same breath. This is understandable as delay and disruption often result from the same events. However, disruption, unlike delay, always has a direct consequence on financial loss. The main differences between delay and disruption are discussed, together with a review of the many causes of disruption, and factors that affect productivity. An example of calculating disruption is illustrated.
If there is no agreed model or method for quantifying the effects of disruption factors in advance, the establishment of the magnitude of the disruption or loss incurred will likely require the preparation of expert evidence. Accordingly, a number of approaches have been developed which include the measured mile, measured productivity method, work sampling, modified total cost approach and site sampling (time and motion studies). These are discussed along with brief practical examples which are provided to assist in demonstrating the process of each type of analysis.
The effect of delay and disruption can be identified and assessed using several dissimilar techniques. There is much discussion about the various approaches to delay analysis along with explanations as to why it should not be surprising when two opposing programming experts can apply the same technique and produce widely varying and inconsistent conclusions. Delay analysis techniques are known by many generic titles and each method can be applied in several ways. The most widely known methods of delay analysis are subject to frequent misuse, but the name applied to a technique is not as important as the application of the chosen method. All commonly applied forensic delay analysis techniques generally fit within one of the following primary categories: impacted as-planned, collapsed as-built (CAB), as-planned versus as-built and time impact analysis (TIA).
The ‘windows’ method is also described in detail, using several of the primary methods listed above. The term ‘windows’ simply refers to the period of time being analysed. When key milestones are relied on, the same approach is sometimes referred to as ‘watershed’ analysis. Each of these primary delay analysis techniques has secondary derivative methods of application, which may be used in prospective or retrospective settings. All of these named techniques are fully explained in Chapter 5, which also not only explains how to carry out and present several secondary derivative methods but also contrasts the strengths and weaknesses of each method and considers the underlying assumptions the analyst must make when using any of these techniques. The four primary methods of delay analysis are also reviewed in detail in Chapter 5, complete with a step-by-step guide to their usage and an indication of some secondary approaches which can be derived from each of these primary approaches.
The chapter also explores the use of CPM and total float management techniques relative to delay analysis. CPM programming is essential when attempting to identify which activities are either critical or non-critical. The CPM programme is therefore the key to demonstrating those events which actually contributed to the critical delay to completion and those which may be deemed merely concurrent ‘events’. The concept of ‘pacing’ is also explained in detail. In the US courts, the use of CPM programmes to demonstrate delay has been a requirement for some years, to the point where delay analysis in US courts almost exclusively rely on delay analyses which used CPM methods of proving entitlement.
There are many names used in the construction industry for the ‘TIA’ approach, probably because there are as many ways to apply the technique. A summary of the perceived strengths and weaknesses of the TIA technique are summarised in Chapter 5, along with many of the variations and options available to the analyst when carrying out this technique.
The ‘collapsed as-built’ (CAB) approach is a modelling technique which is traditionally carried out on a single-base programme, for example the as-built programme. The other side of the spectrum of the basic methods of analysis includes as-built based analytical techniques which do not rely on calculated CPM models. In its simplest form, an as-built versus as-planned analysis compares the planned duration with the actual duration of a project and asserts the difference as being both excusable and compensable. These are referred to as ‘Observational’ in the AACEI RP-FSA.
On projects where the effects of acceleration (or attempted acceleration) or early completion programmes are at issue, it advisable to apply both a deterministic technique and an analytical technique, which is explained in Chapter 5. This provides a tribunal with a range of opinions, based on different assumptions.
The contemporaneous windows analysis is a technique which relies on the analysis of contemporaneous progress information and is considered to be dynamic because it considers the dynamic nature of the critical path. The as-built critical path of a programme shifts from time to time for many reasons as explained in Chapter 5.
A similar method to the contemporaneous windows analysis is the ‘month-to-month update’ analysis, whereby the progress achieved in 1 month, is superimposed on a previous month's programme update. This is a method which discretely determines the loss/gain experienced due to both progress achieved/not achieved, and programming revisions made by the contractor. This is a form of ‘what if’ analysis, which identifies and isolates delays caused purely by progress, from delays (or gains) which resulted from changed logic, constraints or durations. This method of analysis is very effective when a contractor is seeking to demonstrate acceleration and needs to demonstrate what the ‘likely’ effect of a delay event would have been, as opposed to the ‘actual’ effect. The case study in Chapter 7 applies this technique in a worked example.
Determining which technique is the most appropriate to use under given circumstances is a subjective decision, guided by experience, the available information and other relevant factors. Even when agreement is reached between the parties, often the application of the same ‘technique’ varies to such an extent that neither party is willing to accept the other's conclusions. These issues have been addressed in both the SCL Protocol and the AACEI's RP-FSA. Chapter 4 provides detail of the SCL Protocol and the 21 core principles. The approach to event analysis and delay quantification must be both systematic and pragmatic. Notwithstanding the importance of this activity, it is also essential to keep a sense of balance with regard to what is a proportionate cost-to-benefit ratio and to avoid overly complex analyses. These may be accurate, or precise, but may not be intuitive, at the risk of conflicting with a tribunal's view of ‘common sense’. While courts have judicial latitude, contractors and contract administrators cannot be seen to base extensions of time on impressionistic assessments. The methods set out in Chapter 5 assist parties in arriving at an approach that is pragmatic, systematic and appropriate for the circumstances of their project.
Each and every delay claim has its own life cycle. The various stages may be summarised as follows:
Baseline programme is established
Project commences
Deviation from baseline programme is identified (or projected)
Delay occurrence/discovery
Delay analysis
Delay claim submission and presentation
Delay claim response
Negotiations (and award of appropriate extension of time)
Revised baseline programme is established and agreed
Dispute resolution procedures (if award is not agreed)
Delay claim resolution
Delay claims are a very effective way to spend money and divert management resource from running a business. Resolution by way of a mutually acceptable extension of time should be sought at the earliest opportunity to avoid the dispute stepping up to the next, more formal process. There are many pitfalls on the path to a successful delay claim resolution as well as steps that can be taken to improve the outcome. For example, the contracting parties could agree the delay impacts contemporaneously (i.e. as they arise during the course of the project works) rather than adopting a ‘wait-and-see’ approach. Chapter 6 considers a number of problematic issues which arise in connection with both programming and delay analysis. These include problematic issues related to the ownership of float in construction programmes, concurrency, programme submission and approvals, acceleration, disruption and mitigation of delay.
Effective communication of sophisticated delay analysis requires quality in the presentation. There are many ways to present similar facts with different conclusions. The benefits of visual aids with worked examples are explained in Chapter 7, together with methods of graphical presentation that are described and critiqued. In addition, a number of worked examples are included and case studies explained.
Chapter 6 discusses a number of problematic issues which have arisen in connection with both programming and delay analysis. These include:
Issues related to the ownership of float in construction programmes
Concurrency
Programme approvals
Mitigation
Acceleration
Pacing
Contractors' entitlement to early completion
The assessment of disruption damages
Float is an integral part of CPM programming and delay analysis. The concept of float, which has given rise to much debate, is introduced in Chapter 2 and further explained in Chapters 4 and 5. In Chapter 6, float is discussed in detail, relative to its usage, measurement and ownership. Float loss can reduces a contractor's contingency time cushion and increases the probability of critical delay to the project. Even where it does not result in critical delay, float loss can cause financial loss to discrete task related resources. Chapter 6 discusses float loss measurement and also ways in which both employers and contractors can seek to influence a programme, and ways in which planners can manipulate float using various float suppression techniques. An issue of much debate for many years is ‘who owns the float in a construction programme?’; the implication being that the owner of the float has exclusive use of it. Chapter 6 reviews the various viewpoints on this matter.
Another common problematic issue, which arises in delay analysis, is that of dealing with, and defining, concurrent events and concurrent delay. The uncertainty as to how concurrent delay should be managed or defined continues to cause difficulty to contract administrators, in particular in their task of assessing extensions of time and compensation events during the course of a project.
These issues impact both on the level of extension of time that might or might not be granted and on the amount of compensation, for example loss and/or expense, that might be due. Chapter 6 reviews definitions of concurrency and considers alternative approaches for dealing with concurrent delay including ‘first-in-line’, the dominant cause approach and the apportionment approach. When concurrent culpable delays are identified by the employer, contractors often argue that it was simply ‘pacing the work’. This concept is discussed, including how it might apply equally to the employer's professional team as well as to contractors.
Another area of potential difficulty is that of programme approvals and onerous specifications. Many of the major building and civil engineering forms of contract require the contractor to prepare and submit a construction programme. The content and standard of construction programming data that employers have required to be submitted by contractors in the past has varied quite considerably. However, in more recent times, with the advances in computer generated output and a growing awareness of the nature of construction planning, employers have been requesting ever increasing detailed and sophisticated programmes from contractors. In the United States, particularly on government forms of contract, it is a more common practice to require quite detailed and sophisticated programme requirements. These issues together with approval or acceptance of construction programmes are discussed in Chapter 6.
The final issues reviewed under this chapter are those of delay mitigation, acceleration and contractors' rights to early completion. The latter topic is when a contractor submits a programme which indicates an intention to finish a project earlier than the agreed contract completion date.
Effective communication of sophisticated delay analysis requires quality and sufficient level of detail in the presentation. It has been established that people usually understand and retain information at a much higher rate when it is presented to them visually. Studies in the United States have shown that jurors, for example retain as little as 10–20% of the material presented to them orally yet retain as much as 65–80% of material presented to them visually or with visual supplements. The effect of using high-impact, demonstrative evidence assists greatly in the success of a case which includes complex technical issues. There are many ways to present similar facts with different conclusions. The benefits of visual aids with worked examples are explained in Chapter 7 together with methods of graphical presentation which are described and critiqued.
In addition in Chapter 7, various methods of delay analysis are demonstrated using a case study, largely based on actual assignments. The information available on the case study project is listed and the method of identifying the as-built critical path is described in detail. The purpose of this chapter is to show how these methods of delay analysis may be carried out. It is important to note that the methodology demonstrated in this case study is neither the only one, nor the only variant on the method demonstrated, for carrying out this type of delay analysis.
1
Estimated annual volume of construction output in 2013 was £112.6 billion [online] Available at
http://www.ons.gov.uk
[Accessed 26 May 2014].
2
UK GDP forecast for 2013 is £1581.2 billion [online] Available at
www.ukpublicspending.co.uk
[Accessed 26 May 2014].
3
United States GDP Growth Rate [online] Available at
www.tradingeconomics.com/united-states/gdp-growth
[Accessed 26 May 2014].
4
Wiggins T., 2014.
U.S. Construction Outlook for 2014
.
5
Keane P. J., 1994.
Survey on Computer Usage in Construction Claims Management
.
6
Sir Michael Latham, 1994.
Constructing the Team
. Final Report. HMSO.
7
The SCL protocol can be downloaded from
http://www.eotprotocol.com
.
8
Association for the Advancement of Cost Engineering International—Recommended Practice No. 29R-03
Forensic Schedule Analysis
.
In this chapter, the principles of construction planning and programming are explained with a review of the merits of the main planning techniques currently in use in the industry. All but the smallest of projects require systematic planning, particularly due to the nature of construction projects. These are often one-off productions, on a site where few if any production facilities exist, with an array of trade contractors marshalled together and to be coordinated with material, plant and service providers. Each project effectively brings the factory to the job and each is different: from the location, to the design, to the participants. Each project requires customised, systematic coordination to avoid delays and cost overruns.
Planning as a systematic function is a principle cornerstone of effective construction management. In the past, construction planning was something of a Cinderella activity, not entirely recognised as an important discipline in its own right. This all changed with the development of economically available personal computing power in the mid-1980s. Prior to this, construction planning was a time-consuming and limited manual process, often most recognisable in the form of bar charts (or Gantt charts) posted like wallpaper in site conference rooms. Due to the effort required to edit, update or re-plan the works manually, these often remained posted, yellowed and faded, without an updated programme or as-built record of progress in sight.
It is difficult to envisage a project involving design, engineering, procurement and/or construction which would not benefit from some form of critical path method (CPM) programming or scheduling. While few relatively simple projects may still be planned and managed intuitively, the rest require systematic planning and control. Construction planning and programming have come to the foreground of project management and control systems. In some organisations, construction planning effort is treated on par with the financial elements of the project control cycle (PCC). Historically, planning was considered to be primarily a supporting activity, usually most relevant in the tender phase of a project. Little attention was paid to the project planner (if there was a dedicated planner), and the programmes, updated or not, were referred to very little (if at all) during the remaining life cycle of a project.
It is widely accepted among design and construction professionals that critical path analysis is the most appropriate tool for the management of complex construction projects and is at the heart of any functional project control system. The most commonly used planning technique based on critical path analysis principles is the CPM. Many derivatives of the CPM approach have been developed, and it is still an evolving standard with some advances made in software and management theories, such as the application of the theory of constraints (TOCs), the critical chain method (CCM), the use of probabilistic and conditional branching, the enhanced precedence diagramming method (EPDM) and Last Planner programming techniques. All of these derivative applications have their foundation in the basic principles of CPM which were developed some 50 years ago.
This chapter describes the tools required to enable a project to be successfully planned, programmed and controlled using CPM philosophies. These are tried and tested methods that have worked for the past 50 years and are today essentially unchanged from the earliest applications. The advancement in the development of computer hardware and processing speeds, together with the availability of low-cost, easy, user-friendly software, have encouraged the widespread adoption of CPM-based project control systems. These systems track and correlate cost and resource information with the planned and actual progress of work. Control systems and critical path programming, when developed hand in hand, assist project executives decide what progress information is important to decision making during the course of a project. Where required, they also assist courts in allocating damages to parties involved in construction-related litigation.
Other forms of planning are also reviewed, from the traditional and still widely used bar chart to the more specialist applications such as line of balance charts and mass haul diagrams. The PCC entails the entire effort involved in creating, monitoring and managing change to both the cost and time elements of a project. The main functions which make up the PCC include planning, programming and control, as follows:
Planning.
defining project; determining scope; setting overall duration, budget and contingencies; identifying risks and overall project goals.
Project Programming or Scheduling.
identifying individual tasks; assigning resources and budgets to each; creating a baseline which determines the earliest and latest allowable start and finish times for each activity, the available float to each activity and the critical path through the project.
Project Control.
updating project programme; monitoring progress against the baseline for both cost and schedule performance; measuring and managing the effects of progress, delays or changes (re-assigning resources and re-scheduling tasks as required to maintain progress).
The nuances between the terms ‘planning’, ‘programming’ and ‘controlling
