Delay and Disruption - The Dynamic Role of the Programme© Daniel Atkinson 2001 22 November 2001
SUMMARYThere are
two main roles for programmes in the
management of projects, the Monitor Role and the Dynamic Role.
Five functions of programmes can be identified, three fulfilling the Monitor
Role and two the Dynamic Role. The role assigned by the contract
and the particular terms will define which of the five function
programmes is required. The Dynamic Role and the two functions of the
Management Programme and Compensation Programme are described in this
Article.
The Dynamic Role of the ProgrammeA programme will allow the performance of time related obligations to be monitored. The function of the programme will depend upon the terms of the contract, although frequently the parties adopt a programme for practical common sense reasons to manage the project, despite the absence of a contractual requirement. The three functions of a programme used for monitoring are given below and described in the Article Monitor Role: The Dynamic Role of the programme is described in this Article Dynamic Role and includes an additional two functions as follows:
Function 4 Management Programme
Function 5 Compensation ProgrammeThe fifth possible function of the programme is as a Compensation Programme to establish a contractual entitlement and its measure, or to establish the circumstances necessary for the exercise of certain rights. The particular entitlement or right (the compensation) needs to be identified in order to ascertain the exact role of the programme and include:
Establishing the contractual entitlements and the rights requires the comparison of baseline and actual progress, as well as compliance with any contractual pre-conditions. In the case of the obligation to complete by a specified date, this only requires the date of actual completion to be compared with the specified date, to establish whether the obligation has been discharged. Even this conceptually most simple obligation requires interpretation of the meaning of "completion" in the contract and evidence of when "completion" actually occurred. If the date for completion is not specified in the contract, then evidence will be required to determine the reasonable time for completion which will depend upon all the circumstances (see Contractors Obligation to Complete the Works). In the case of the obligation to progress the works, this requires the actual progress measured in terms of both time and resources to be compared to the standard of progress specified in the contract. The obligation is most difficult to monitor and analyse. It requires the standard required to be determined by interpretation of the contract. Inevitably the obligation is specified in most general terms (see Contractors Obligation to Progress the Works). A programme can provide evidence of necessary facts, either as evidence of fact or opinion, of both the reasonable standard of progress and the actual progress achieved for comparison as follows:
The cogency of the evidence provided by the planned programme will depend upon the accuracy of the available information and the effort applied in producing the programme. Programmes produced at tender will reflect the usually limited time available to contractors to prepare their bid, the liklihood of being awarded the contract and the contractual status of the tender programme. In most projects the most realistic programme is usually prepared some weeks after award of the contract, when subcontract packages are more clearly defined. By then inadequacies in the contractor's bid may have become apparent. Programmes may then include an element of optimism or programmemanship and not state realistically achievable productions or durations. For all these reasons the assumptions made in any planned programmes must be verified and tested as accurate. The cogency of the evidence provided by revised programmes and programmes showing actual progress, depends upon the accuracy of the record of dates and events and the providence of the evidence on which they are based. The programme should refer directly the source of dates and durations. Programmes show clearly defined start and finishes of activities, but it is usually difficult in practice to define these two dates precisely. The finish date for the purpose of defining the end of tasks for that activity may not be the same date as the finish required to allow another activity to start. There may be different finish dates for the same activity for different Logic Links. To further complicate matters, in practice once an activity has reached a level of completion to allow other activities to commence, the activity may be left for some time before being finished. If records show the later date of finish and the programme uses logic links based on that date, the programme will be inaccurate and of little evidential value. The planned programmes and the revisions will be evidence of the steps taken, or the failure to take sufficient steps, by the Contractor to fulfill his obligations as to programme (see Contractors Obligations as to Programme). The specific obligations vary with the contract, but may include the requirement to revise and update programmes, to record actual progress and projected future progress and to show the steps to be taken to overcome the delay caused by events. The evidence provided by the programme of works is not sufficient in itself to justify compensation. It is necessary to establish
Establishing the incidence of liability for a Causative Event requires the event to be identified as a fact and the liability determined by interpretation of the contract terms and/or recognition of the operation of law. Many Causative Events which change the planned progress of the works, or change actual progress, can be identified without reference to the programme of works. Ordered Variations, weather conditions, changed ground conditions or defects in either drawings, materials, plant or workmanship are some of the events which may be identified directly. Other Causative Events are identified from documents, such as notifications to contractors from subcontractors or suppliers. In some situations however, the events are first identified by their effect on progress. The late supply of information or plant and the increased quantities of work are some events which may be first identified by comparison of actual progress to planned progress. In these cases an accurate planned programme of works is essential for early identification. In some cases the Causative Event identified may itself have been caused by a previous Causative Event. The delay and loss of productivity caused by winter working for example may have been caused by the delay into winter due to an earlier Causative Event. This chain of causation, the incidence of secondary Causative Events, will need need to be established by a logic analysis of the inter-relationship of activities and events. In complex situations a network programme analysis of as-built progress and events will usually be required. Whether or not the Causative Event has caused the type of loss which is required to be compensated is a matter of analysis of Causation - of cause and effect - which is a mixed question of fact and law In the case of the right to deduct liquidated damages for the contractor's breach of the obligation to complete by a specified date, usually no complicated analysis of cause and effect is required. The contractor may however properly rely on the prevention principle to prevent a Purchaser from taking advantage of its own breach, even in the absence of an extension of time (for a recent example see the Article Notices and Liquidated Damages). It is suggested that this is essentially an issue of causation. The right to liquidated damages may not arise unless the pre-conditions to that right are fulfilled and this will usually be notice provisions if at all. In the case of compensation in the form of the right to an extension of time, the contract will usually prescribe causation, either in terms of the actual delay to the date for completion and/or the estimated future delay and/or the probable future delay. These provisions will therefore determine the method of analysis that is required. It is usual in all but the most simple of cases to carry out the analysis using a Network Analysis Programme. The method of network analysis, whether impact analysis on the planned programme, window or snapshot analysis or collapse method using the as-built programme will depend upon the prescription for causation in the extension of time clause. For details of these methods refer to the Index of Articles. The accuracy of any analysis will depend upon the accuracy of the information on which it is based. For this aspect of programmes see the commentary above on the Prediction Programme. In the case of compensation in the form payment for delay and/or disruption and/or acceleration, the compensation may be prescribed in terms of costs or rates and may state whether or not overhead and profit are to be part of the compensation. The prescription may determine the causation rules, whether evidence that actual loss has been caused is required. The role of the programme is usually to demonstrate the period in which the delay or disruption or acceleration occurred so that a separate analysis can be carried out of the change in resources in the period and hence the compensation. Once it has been established that there is a right to compensation, then the same method used to establish causation may determine the Measure of Compensation. In the case of the right to extension of time, a network analysis will show not only the link between event and change in progress, but also the extent of the change. Problems of concurrency will usually be resolved by interpretation of the extension of time clause or principles of causation at law. The standard of proof for the measure of compensation for time may not be the same as the measure for time related financial compensation, a matter of interpretation of the contract. Frequently, available evidence is not sufficient to establish the precise measure of compensation even in the case of extension of time, but more so in the case of disruption and acceleration compensation. The contract itself may state the standard to be adopted by terms such as "he ... estimates is fair and reasonable" or "... the delay suffered fairly entitles the Contractor to an extension of time .." or "... such extension of the Time for Completion as may be reasonable". PRACTICE NOTE The
identification of float and the critical path is an essential part of
management using programmes. Usually a Critical Path Network Analysis
will be required for any but the simplest project. Programmes need to
be reviewed constantly as the project develops, since assumptions implied in
the logic may be shown not to be accurate. Certain construction restraints may only become
apparent as the project develops.
|