高鐵香港段於2 0 11年6月及7月錄得項目進度的黃色燈號後， 又於2 0 11年8月至2 0 1 4年5月期間連續錄得項目進度共3 4 次紅色燈號。但運房局在2014年5月才驀然驚醒，高呼被港鐵欺騙。
專家表示，若路政署在當初能檢視這一指數，也應該看到，大量『追回措施』( Delay Recovery Measures programme )的成效有限。 (注1)
進度追補指數是(計劃進度 - 實質進度 ) / ( 1 - 實質進度 )。它表達餘下工程要趕上通車日期所需作出的改善程度。
Schedule Performance Index
7.10 The Independent Experts found that the interpretation of delays can be informed by the automated reporting system. The actual programme progress and the planned programme progress can be used to calculate a Schedule Performance Index (SPI), for the programme at a certain stage, as:
SPI = Actual Progress / Planned Progress.
7.11 Figure 7 shows the SPI from November 2011 to July 2014 against the 2015 opening date. The graph shows that Project has gradually deteriorated from November 2011 until September 2013 when the performance index reached the lowest point of 0.65. The curve shows that at the lowest point the SPI for the civil work reached 0.6. The graph also shows that E&M finished most of the design work in July 2013 and subsequently ran out of work sites to achieve progress.
Schedule Performance Index (SPI) of the XRL
7.12 In the view of the Independent Experts, if this information had been included in past reporting meetings it would have been clear to decision makers that: (1) despite the large number of DRMs being implemented, their effect on Project progress was minimal; and (2) the productivity of civil contracts started to improve slightly after October 2013 but at the same time the E&M contracts significantly deteriorated due to lack of work spaces.
Schedule Recovery Index
7.13 An alternative way of reporting the recoverability of delays is to estimate the productivity increase that needs to be achieved and sustained for the remainder of the project in order to meet the opening date. This Schedule Recovery Index (SRI) is calculated as:
SRI = (Planned Progress - Actual Progress) / (1 – Actual Progress)
7.14 Figure 8 depicts the required productivity increase for the Project between November 2011 and July 2014 to achieve the 2015 opening.
7.15 In the view of the Independent Experts, a productivity improvement of more than 30% is highly unlikely. Achieving and sustaining a 30% improvement is equivalent to working 3 hours overtime per 10 hour work day. The historic data in Figure 8 shows that after April 2013 the Project needed to achieve a more than 30% productivity increase to meet the 2015 opening date. By the end of 2013 the required increase in productivity was higher than 60%. It is the view of the Independent Experts that achieving such an increase would have been almost impossible.
7.16 Consequently, if decision makers had been presented with information like that above, they would, in the view of the Independent Experts, have concluded no later than the second half of 2013 that the Project was irrecoverable.
Enhancement to the programme KPI
7.17 As discussed above, the Independent Experts found that the Project reported red lights for a prolonged period in time. This indicates that either the KPI definition was flawed or appropriate action was not taken.
7.18 According to the KPI definition, a red light indicates a delay of more than eight weeks. The buffer in the original baseline was twelve weeks. The Independent Experts recommend tailoring the definition of traffic lights to the specific cost and schedule contingencies in the current baseline of projects rather than using a consistent definition across all projects.
7.19 The Independent Experts further recommend that clear rules are defined that a project cannot report more than a given number of consecutive red lights (depending on the overall length of the project) before triggering a review of the project. The outcome of the review should be a re-baselining of the project and an actionable turn-around plan, in the view of the Independent Experts.
7.20 Consecutive red lights must be linked to a clear plan of action with clear accountabilities and deadlines to bring project performance back on track. In other words, the PjT and the contractors must have responsibility to demonstrably recover performance by a set deadline.
Suggested DRMs need to clearly specify by when they are going to be met and how much they will improve performance, so that the PjT can select the appropriate steps for short and long term recovery. The decision as to whether DRMs are sufficient needs to be driven by data.