16.10.2014 Views

Capital Investment Plan 2009 - Heathrow Airport

Capital Investment Plan 2009 - Heathrow Airport

Capital Investment Plan 2009 - Heathrow Airport

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

<strong>Capital</strong> <strong>Investment</strong> <strong>Plan</strong><br />

<strong>2009</strong><br />

(CIP <strong>2009</strong>)<br />

Date : May <strong>2009</strong><br />

Prepared by: <strong>Investment</strong> Strategy Team<br />

Status:<br />

Public


Contents<br />

1 Introduction .......................................................................................................... 1<br />

1.1 Regulatory years ........................................................................................... 1<br />

1.2 CIP 2008 to CIP <strong>2009</strong> ................................................................................... 1<br />

1.3 Executive Summary of Key Issues .................................................................. 2<br />

2 Strategy and Vision ............................................................................................... 3<br />

2.1 Vision for <strong>Heathrow</strong> <strong>Airport</strong>.......................................................................... 3<br />

2.1.1 Output from 2006 Constructive Engagement Process ............................... 3<br />

2.1.2 HAL’s Purpose and Vision.......................................................................... 3<br />

2.1.3 Airline Community Vision.......................................................................... 4<br />

2.1.4 Airline and HAL Joint Alignment of Purpose, Vision and Masterplan<br />

Attributes.............................................................................................................. 4<br />

2.2 <strong>Heathrow</strong> <strong>Airport</strong> Storyboard........................................................................ 5<br />

2.2.1 Q5 Traffic Demand (Extract from CAA Decision)........................................ 5<br />

2.2.2 Long Term Traffic Demand (Q6 and beyond)............................................. 5<br />

2.2.3 <strong>Heathrow</strong> <strong>Airport</strong> Campus 2030 ............................................................... 6<br />

2.2.4 <strong>Heathrow</strong> <strong>Airport</strong> Campus at the end of Q5 ............................................. 6<br />

2.2.5 Masterplan Consultation........................................................................... 6<br />

2.3 Context for the next 10 Years (<strong>2009</strong> to 2019)............................................... 7<br />

2.4 Development Workstreams......................................................................... 10<br />

2.4.1 Terminals including Piers / Satellites......................................................... 10<br />

2.4.2 Baggage ................................................................................................. 11<br />

2.4.3 Airfield.................................................................................................... 11<br />

2.4.4 Surface Access........................................................................................ 12<br />

2.4.5 Connections ........................................................................................... 13<br />

2.4.6 Cargo and Maintenance Areas................................................................ 13<br />

2.4.7 Ancillary Areas and Others...................................................................... 14<br />

2.5 Programmes ............................................................................................... 14<br />

2.6 Possible Future Development Projects in Q6 and Q7 Timescales................... 15<br />

2.6.1 Project for the Sustainable Development of <strong>Heathrow</strong>............................. 15<br />

2.6.2 Eastern Campus Programme ................................................................... 15<br />

2.6.2.1 List of Possible Eastern Campus Programme Projects ....................... 16<br />

2.6.3 Western Campus Programme ................................................................. 16<br />

2.6.3.1 List of Possible Western Campus Programme Projects...................... 16<br />

2.6.4 Baggage Programme .............................................................................. 17<br />

2.6.5 Infrastructure Programme ....................................................................... 17<br />

2.6.5.1 List of Possible Infrastructure Programme Projects ........................... 17<br />

2.6.6 Airline Relocations .................................................................................. 18<br />

2.6.7 Information Technology (IT) / Systems Programme .................................. 18<br />

2.6.8 Rail Programme ...................................................................................... 18<br />

2.6.8.1 List of Possible Rail Programme Projects........................................... 18<br />

2.7 Risks and Assumptions................................................................................ 18<br />

3 Q5 Delivery ......................................................................................................... 19<br />

3.1 Eastern Campus Programme....................................................................... 19<br />

3.1.1 Overview ................................................................................................ 19<br />

3.1.2 List of Projects......................................................................................... 19<br />

3.1.3 Additional Explanatory Notes .................................................................. 20<br />

3.2 Western Campus Programme ..................................................................... 20<br />

3.2.1 Overview ................................................................................................ 20<br />

3.2.2 List of Projects......................................................................................... 20<br />

3.2.3 Additional Explanatory Notes .................................................................. 21<br />

3.3 Baggage Programme .................................................................................. 21<br />

3.3.1 Overview ................................................................................................ 21<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG


3.3.2 List of Projects......................................................................................... 21<br />

3.3.3 Additional Explanatory Notes .................................................................. 21<br />

3.4 Infrastructure Programme ........................................................................... 22<br />

3.4.1 Overview ................................................................................................ 22<br />

3.4.2 List of Projects......................................................................................... 22<br />

3.4.3 Additional Explanatory Notes .................................................................. 22<br />

3.5 Airline Relocations Programme ................................................................... 23<br />

3.5.1 Overview ................................................................................................ 23<br />

3.5.2 List of Projects......................................................................................... 23<br />

3.6 IT / Systems Programme.............................................................................. 23<br />

3.6.1 Overview ................................................................................................ 23<br />

3.6.2 List of Projects......................................................................................... 24<br />

3.6.3 Additional Explanatory Notes .................................................................. 24<br />

3.7 Rail ............................................................................................................. 24<br />

3.7.1 Overview ................................................................................................ 24<br />

3.7.2 List of Projects......................................................................................... 24<br />

3.7.3 Additional Explanatory Notes .................................................................. 24<br />

3.8 PSDH .......................................................................................................... 24<br />

3.8.1 Overview ................................................................................................ 24<br />

3.8.2 List of Projects......................................................................................... 25<br />

3.8.3 Additional Explanatory Notes .................................................................. 26<br />

3.9 Thames Water ............................................................................................ 26<br />

3.9.1 Overview ................................................................................................ 26<br />

3.9.2 List of Projects......................................................................................... 26<br />

3.9.3 Additional Explanatory Notes .................................................................. 26<br />

3.10 Trigger Milestones ...................................................................................... 26<br />

3.10.1 Q5 Regulatory Decision....................................................................... 26<br />

3.10.2 Trigger Completion............................................................................. 27<br />

3.10.2.1 Process........................................................................................ 27<br />

3.10.2.2 Trigger Status.............................................................................. 27<br />

3.10.2.3 Change Control .......................................................................... 27<br />

3.11 Ongoing Scope Gap Review........................................................................ 28<br />

3.12 Anticipated Final Cost (AFC) to Current Control Budget Gap (CCB)............. 28<br />

4 Regulatory and Legislative Context ...................................................................... 29<br />

4.1 Aviation and <strong>Airport</strong> Policy.......................................................................... 29<br />

4.2 Economic Regulation .................................................................................. 29<br />

4.2.1 Current Regulation ................................................................................. 29<br />

4.2.2 Future Regulation ................................................................................... 29<br />

4.3 Other Relevant Issues.................................................................................. 31<br />

4.3.1 Town and Country <strong>Plan</strong>ning.................................................................... 31<br />

4.3.2 Climate Change Policy ............................................................................ 33<br />

4.3.3 New EU Air Quality Directive ................................................................... 33<br />

4.3.4 Noise Map and Action <strong>Plan</strong>s.................................................................... 33<br />

4.3.5 Airspace Issues........................................................................................ 34<br />

4.3.6 Public Safety Zones Review ..................................................................... 34<br />

5 Technical Notes................................................................................................... 36<br />

5.1 Project Definition Sheets ............................................................................. 36<br />

5.2 Financial Data ............................................................................................. 36<br />

5.2.1 Budget Information................................................................................. 36<br />

5.2.2 Anticipated Final Cost Information .......................................................... 37<br />

5.2.3 Revenue and Operational Cost Information............................................. 38<br />

5.2.4 User Charge Impact ................................................................................ 38<br />

5.3 Time Schedule Data .................................................................................... 38<br />

5.4 Inflation...................................................................................................... 38<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG


5.4.1 Terminology............................................................................................ 39<br />

5.4.2 Price Bases and Inflation Indices .............................................................. 39<br />

5.4.3 Inflation Rate Data and Commentary ...................................................... 40<br />

5.4.4 Selection of Construction Inflation Rate 2007/08 to 2008/09 .................. 40<br />

5.4.5 Construction Inflation Outlook and Resultant Action............................... 41<br />

5.5 Control Totals............................................................................................. 42<br />

5.6 Risk ............................................................................................................ 42<br />

5.7 Change Control.......................................................................................... 43<br />

6 Constructive Engagement ................................................................................... 46<br />

6.1 Q5 Delivery of Annex G Commitments........................................................ 46<br />

6.1.1 Main <strong>Capital</strong> Works including Stakeholder Programme Boards................ 46<br />

6.1.1.1 Stakeholder Programme Boards ...................................................... 46<br />

6.1.1.2 Consultation at Gateways ............................................................... 46<br />

6.1.1.3 Change Control .............................................................................. 46<br />

6.1.1.4 Consultation on Risk Allowances..................................................... 46<br />

6.1.2 Rail ......................................................................................................... 47<br />

6.1.3 Information Technology (IT) / Systems ..................................................... 47<br />

6.1.4 Project for the Sustainable Development of <strong>Heathrow</strong> (PSDH) ................. 48<br />

6.1.5 CIP Working Group................................................................................. 48<br />

6.1.6 Constructive Engagement Fora for <strong>Capital</strong> <strong>Investment</strong> ............................ 48<br />

6.2 Discussions on Future Developments (Q6 and beyond)................................ 49<br />

6.3 CIP Development Process............................................................................ 49<br />

6.4 Airline Engagement Status Marker.............................................................. 49<br />

6.5 Aspirations for Future CIP Publications ........................................................ 51<br />

Appendix A: Project for the Sustainable Development of <strong>Heathrow</strong><br />

Appendix B: Trigger Change Control<br />

Appendix C: PDS – Q5 Eastern Campus<br />

Appendix D: PDS – Q5 Western Campus<br />

Appendix E: PDS – Q5 Baggage<br />

Appendix F: PDS – Q5 Infrastructure<br />

Appendix G: PDS – Q5 Airline Relocations<br />

Appendix H: PDS – Q5 IT / Systems<br />

Appendix I: PDS – Q5 Rail<br />

Appendix J: PDS – Q5 PSDH, Thames Water and Support Adjustments<br />

Appendix K: PDS – Eastern Campus Phase 2 Enabling<br />

Appendix L: PDS – Q6 and Beyond Eastern Campus<br />

Appendix M: PDS – Q6 and Beyond Western Campus<br />

Appendix N: PDS – Q6 and Beyond Infrastructure<br />

Appendix O: PDS – Q6 and Beyond Rail<br />

Appendix P: Tracker CIP 2008 to CIP <strong>2009</strong><br />

Appendix Q: Cost Schedules<br />

Appendix R: Time Schedules<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG


1 Introduction<br />

This document is <strong>Heathrow</strong> <strong>Airport</strong> Limited’s (HAL’s) <strong>Capital</strong> <strong>Investment</strong> Programme<br />

(CIP) to formally cover at least the ten year period April <strong>2009</strong> to March 2019 inclusive.<br />

The content of HAL’s CIP will be revised and republished on an annual basis. This<br />

document shall be known as “CIP <strong>2009</strong>”.<br />

The content of this document applies to the broad operating entities knows as<br />

<strong>Heathrow</strong> <strong>Airport</strong> and <strong>Heathrow</strong> Express. Note: <strong>Heathrow</strong> Express Operating Company<br />

Limited (HEx) is a subsidiary of HAL.<br />

In line with HAL’s Annex G 1 commitments this document is effectively a “snapshot” of<br />

HAL’s capital investment plans as at the time of publication and is not documentation of<br />

a mandatory, fixed or confirmed investment programme for either <strong>Heathrow</strong> <strong>Airport</strong> or<br />

<strong>Heathrow</strong> Express. While HAL has consulted locally with the airline community on the<br />

content of CIP <strong>2009</strong> it welcomes comment from them, either locally or from head<br />

offices, upon publication of this document in writing or via the established constructive<br />

engagement fora. During the consultation the airline community asked 2<br />

HAL to make<br />

available to airline community representatives a list of changes from the early drafts,<br />

reviwed jointly in detail, to this published version. Such information is available for<br />

airline community representatives on request from HAL.<br />

1.1 Regulatory years<br />

The period covered by this document formally covers three regulatory quinquennia;<br />

• Years 2 to 5 of the 5 th Quinquennium (Q5)<br />

• Years 1 to 5 of the 6 th Quinquennium (Q6)<br />

• Year 1 of the 7 th Quinquennium (Q7)<br />

However details for Q6 and Q7 are published on the basis of the positions stated later in<br />

this document and are neither definitive or exhaustive.<br />

1.2 CIP 2008 to CIP <strong>2009</strong><br />

CIP 2008 is the previous version of this document. CIP <strong>2009</strong> seeks to be a step change<br />

in HAL’s presentation, for consultation, of its capital investment plans. As such the<br />

format and content has been altered significantly from CIP 2008. This edition of the CIP<br />

has been prepared within the framework of a new process 3 with the intent of improving<br />

the long term visibility of investment options for all users of the document.<br />

The completion of the content of this document has been led by HAL in consultation<br />

with the airline community at <strong>Heathrow</strong>. Additional information on this consultation is<br />

provided in section 6.1.5.<br />

A summary is provided in Appendix P: Tracker CIP 2008 to CIP <strong>2009</strong> to enable linkage<br />

between the CIP 2008 and CIP <strong>2009</strong> publications to be readily accessed by users of this<br />

document. Users should also refer to sections 5.4 and 5.7 for information on inflation<br />

and change control respectively.<br />

1<br />

Annex G of the Economic Regulation of <strong>Heathrow</strong> and Gatwick <strong>Airport</strong>s 2008 to 2013, CAA,<br />

March 2008.<br />

2<br />

At the Special CIPWG held 27 th February <strong>2009</strong>.<br />

3<br />

Presented to CIPWG on 16 th October 2008, followed by JST on 3 rd November 2008 and 8 th<br />

December 2008.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 1


1.3 Executive Summary of Key Issues<br />

The airline community have requested 4 that their broad agreement with the content of<br />

this document and the plans outlined is understood in the context of any significant<br />

issues at large between themselves and HAL. The significant issue outstanding at the<br />

time of publication is the airline community’s view that HAL lacks a high level<br />

masterplan / land use plan for <strong>Heathrow</strong> out to 2030. HAL notes the concerns expressed<br />

and refers to the context set out throughout this document on the matter of the high<br />

level masterplan.<br />

4<br />

At the Special CIPWG held 27 th February <strong>2009</strong>.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 2


2 Strategy and Vision<br />

<strong>Heathrow</strong> <strong>Airport</strong> is the United Kingdom’s only international hub airport and a vital<br />

piece of national infrastructure. This CIP presents the current snapshot view of how the<br />

premier status of the world’s busiest international airport could be maintained and<br />

enhanced through appropriate infrastructure and other capital investment.<br />

2.1 Vision for <strong>Heathrow</strong> <strong>Airport</strong><br />

At the time of writing this document the process for refreshing the joint vision for<br />

<strong>Heathrow</strong> between HAL and the airline community has only recently commenced.<br />

Section 2.1 therefore presents the three current wordings for a <strong>Heathrow</strong> vision.<br />

While there exists a high degree of commonality between the three wordings it is HAL’s<br />

intention to consult with the airline community to achieve a common statement, taking<br />

on board the UK Government announcements on adding capacity at <strong>Heathrow</strong> made in<br />

January <strong>2009</strong> 5 , in time for the publication of CIP 2010.<br />

2.1.1 Output from 2006 Constructive Engagement Process<br />

In the May 2006 document “Interim Results of Constructive Engagement at <strong>Heathrow</strong><br />

<strong>Airport</strong>” the output of the “Vision for <strong>Heathrow</strong>” workstream was described thus;<br />

“A world class international hub airport<br />

In practice this means the following;<br />

• A full-service, mixed mode, three-runways airport, recognised as both the major UK<br />

international hub and as a world leader in its own right.<br />

• Maintain position of traffic leadership as at present but with commensurate service<br />

levels, to achieve continuous top ten placing in IATA / ACI assessments.<br />

• Designed, built and operated as an integrated transport facility, providing effective<br />

surface access, inter-modality and connectivity for passengers, baggage and cargo.<br />

• Infrastructure, service quality and technology which recognise and respond to<br />

travellers’ different needs to encourage a stress free, positive experience for the<br />

customer.<br />

• Predictable, reliable, punctual, cost-effective operations, meeting airline growth<br />

assumptions but not at the expense of delay, congestion and poor service.<br />

• Value for money for the airlines and their customers.<br />

• Flexibility to adapt to meet market demands.”<br />

2.1.2 HAL’s Purpose and Vision<br />

The importance of <strong>Heathrow</strong> to the economy of the UK is such that its hub status must<br />

be maintained and improved to a level that is at least equivalent with it’s European<br />

competitors. This needs to be achieved through the delivery of excellent passenger<br />

experiences and the development of new capacity and service improving infrastructure.<br />

HAL has a stated desire to deliver operational improvement through a structure of<br />

deliverable and tangible targets. To that end HAL refreshed its purpose and vision<br />

statements to;<br />

5<br />

Department for Transport publication “Adding Capacity at <strong>Heathrow</strong>: Decisions Following<br />

Consultation”, dated January <strong>2009</strong>. (Herein after referred to as the Government decision.)<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 3


• Purpose:<br />

“London’s direct connection to the world and leading European hub”<br />

• Vision:<br />

“Become Europe’s hub of choice by making every journey better”<br />

2.1.3 Airline Community Vision<br />

In response HAL invited the airline community to present their view on “vision” for<br />

inclusion in CIP <strong>2009</strong>. The wording below was provided by the airline community at the<br />

JST 6 for inclusion in this document.<br />

“The airline community is concerned that a “new” vision for <strong>Heathrow</strong> has been<br />

developed internally by HAL and endorsed by the BAA Board without the benefit of<br />

ongoing constructive engagement with the airline community. Subsequently HAL has<br />

now recognised that any change to the agreed vision would benefit from and should<br />

include consultation with the airline community as an element of “ongoing”<br />

Constructive Engagement.<br />

Thus, the <strong>Heathrow</strong> airline community believes that, to date the only “agreed” vision<br />

for <strong>Heathrow</strong> is the one that was included as part of Constructive Engagement (Refer to<br />

2.1.1).<br />

“A world class international hub airport”<br />

The airline community appreciates that this vision statement will continue to benefit<br />

from updated and specific goals and objectives and, within this context believes, that<br />

ongoing dialogue with HAL to “flesh out” the vision statement is beneficial.<br />

However, the airline community is concerned about HAL’s suggested refocus of the<br />

vision on the European context of <strong>Heathrow</strong>. The airline community believes that<br />

<strong>Heathrow</strong> must meet and maintain its full potential in the global aviation industry and<br />

that HAL must continue to consider <strong>Heathrow</strong>’s role in the context of “global” aviation,<br />

not just within Europe. <strong>Heathrow</strong> is regarded by the airline industry as one of the key<br />

major GLOBAL hubs and therefore must continue to be benchmarked against<br />

comparable airports. Anything less jeopardises <strong>Heathrow</strong>’s ability to compete as a global<br />

hub and potentially downgrades opportunities for continuous improvement.<br />

The airline community would like to discuss these opportunities in greater detail and<br />

welcomes HAL’s invitation to continue to define the future of <strong>Heathrow</strong>. The interim<br />

goal of becoming “Europe’s hub of choice” and the continuous improvement embodied<br />

within “making every journey better” is positive. Becoming Europe’s hub of choice is an<br />

excellent way point on the journey of becoming world class. However, the vision<br />

statement should never lose sight of being the very best.”<br />

2.1.4 Airline and HAL Joint Alignment of Purpose, Vision and Masterplan<br />

Attributes<br />

Sections 2.1.1, 2.1.2 and 2.1.3 outline the current viewpoints on the “vision” for<br />

<strong>Heathrow</strong>. HAL intends, as outlined to the airline community in JST meetings 7 , to lead a<br />

6<br />

JST held 2 nd March <strong>2009</strong>.<br />

7<br />

JST held 8 th December 2008 and 13 th January <strong>2009</strong>.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 4


joint process of consultation and discussion in order that, in the light of the Government<br />

decision on adding capacity at the airport, a common agreed set of purpose and vision<br />

statements may be agreed prior to the third quarter of <strong>2009</strong>.<br />

Such consultation shall need to be undertaken with the context of simultaneous<br />

discussions on the affordability and the time phasing of possible future investments.<br />

(Refer also to sections 2.2.3 and 2.3 )<br />

2.2 <strong>Heathrow</strong> <strong>Airport</strong> Storyboard<br />

2.2.1 Q5 Traffic Demand (Extract from CAA Decision 8 )<br />

The CAA Decision provides the following table of traffic forecast used to establish the<br />

Q5 price control.<br />

2008/09 <strong>2009</strong>/10 2010/11 2011/12 2012/13<br />

CAA<br />

(Final)<br />

70.4 72.5 74.5 76.2 78.2<br />

All values in Millions of Passengers Annum.<br />

Table 1: Extract of Table 4-5 CAA Forecast Passenger Numbers. From CAA Decision.<br />

Reflective of the current economic environment, the HAL have previously reported the<br />

total traffic for 2008/09 at 65.9 million passengers.<br />

HAL believes that, the long term nature of capital investment decisions means that, at<br />

this time, the current economic downturn does not result in a need to revisit the plans<br />

for the current quinquennium. HAL will consult with the airline community in this<br />

respect during the regulatory year <strong>2009</strong>/10 in line with the discussions outlined in<br />

section 2.2.2 on Q6 and beyond.<br />

2.2.2 Long Term Traffic Demand (Q6 and beyond)<br />

Annex G 9<br />

states that HAL are obliged to consult with the airline community on the<br />

traffic forecasts for the airport in order that correct long term investment decisions can<br />

be made.<br />

In line with the issues outlined in sections 2.1, 2.2.3, 2.2.5, and 2.3 HAL does not<br />

present detailed long term traffic forecasts in this version of the CIP. Consultation on<br />

forecasts, in the light of aviation industry expectations and the recent Government<br />

decision, will be undertaken with the airline community following the process and<br />

timelines outlined below. Such work will be done so as to allow inclusion of full traffic<br />

forecasts in future CIP publications and for interim publication between HAL, airline<br />

community and the CAA as needed before then.<br />

In general the process for consulting on traffic forecasts will follow that for the general<br />

master planning. HAL therefore intends to present its current interpretation of possible<br />

forecast scenarios, aligned with possible future runway capacity scenarios that enable<br />

Air Traffic Movement (ATM) growth beyond the current 480,000 annual ATM limit, by<br />

the end of May <strong>2009</strong>. This initial presentation will be followed by a two to three month<br />

period of iterative discussions with the airline community in general, and airlines holding<br />

8<br />

Economic Regulation of <strong>Heathrow</strong> and Gatwick <strong>Airport</strong>s, CAA Decision, 11 th March 2008.<br />

9<br />

Annex G of the Economic Regulation of <strong>Heathrow</strong> and Gatwick <strong>Airport</strong>s, CAA Decision, 11 th<br />

March 2008.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 5


significant slot holdings, on improvements to the scenarios with a view to creating an<br />

agreed range of forecasts on which the master plan options can be assessed. HAL<br />

expects that elements of this consultation, if it includes individual airline growth<br />

assumptions, will need to be undertaken bilaterally under confidentiality agreements,<br />

with HAL (or an independent party, e.g. ACL) aggregating information provided into a<br />

<strong>Heathrow</strong> wide perspective that is not commercial sensitive to any one airline or group<br />

of airlines. Due to the long term nature of the master planning discussions it will, after<br />

the above process has concluded, be necessary to regularly review the forecasts in order<br />

to ensure that the joint assumptions remain valid.<br />

In advance of such consultation, the airline community have requested that the eventual<br />

Q6 and beyond forecasts reflect the longer term predicted growth of aviation and are<br />

not overly distorted by the shorter term economic issues and related passenger<br />

numbers.<br />

2.2.3 <strong>Heathrow</strong> <strong>Airport</strong> Campus 2030<br />

The Government decision in January <strong>2009</strong> on adding capacity at <strong>Heathrow</strong> allows work<br />

on the development of a full masterplan in the context of the three runway airport to<br />

commence in earnest.<br />

At the time of preparing CIP <strong>2009</strong> this development activity is only at outline stage and<br />

is still subject to significant prolonged and detailed work by both HAL and, through<br />

consultation, the airline community.<br />

Figure 1: Schematic of Possible Passenger Processing and Apron Capacities for<br />

<strong>Heathrow</strong> in 2030.indicates the range of options that could be considered for a three<br />

runway airport in 2030.<br />

In addition to Figure 2 HAL have commenced discussions on what attributes the three<br />

runway masterplan for <strong>Heathrow</strong> should contain. As with the “vision” for <strong>Heathrow</strong><br />

outlined in section 2.1, HAL shall progress this consultation to develop agreed<br />

attributes. In this context the attributes are outcomes that the masterplan should seek<br />

to respond to. Further information is provided in section 2.2.5 below.<br />

2.2.4 <strong>Heathrow</strong> <strong>Airport</strong> Campus at the end of Q5<br />

Figure 2: High level <strong>Plan</strong> of <strong>Heathrow</strong> Campus at March 2013.shows the expected, as at<br />

the time of CIP <strong>2009</strong> publication, nature of completed major development works at<br />

<strong>Heathrow</strong> at the end of this quinquennium (Q5).<br />

2.2.5 Masterplan Consultation<br />

Building on the process outlined in section 2.1.4 HAL advises that it wishes to progress<br />

consultation with the airline community on the attributes for, and general content of, a<br />

full masterplan to 2030. Such consultation shall build on discussions already undertaken<br />

on possible specific investment projects that, on current understanding could form<br />

elements of the full masterplan. Examples of the major projects, on which consultation<br />

has already commenced are;<br />

• An airside tracked transit passenger connectivity system.<br />

• Western Campus (T3/T5) development.<br />

• Eastern campus (T1/T2) development including a T2C facility, and<br />

• Commercial and passenger experience redevelopment of the landside Central<br />

Terminal Area (CTA).<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 6


HAL envisages the consultation following the same timeline as that outlined for the<br />

“vision” as both issues are inextricably linked.<br />

2.3 Context for the next 10 Years (<strong>2009</strong> to 2019)<br />

The introduction of the third runway and associated infrastructure into the <strong>Heathrow</strong><br />

campus will introduce a series of challenges for the operation and development of the<br />

airport. At the time of publishing this CIP <strong>2009</strong>, after the Government announcement<br />

on additional capacity at <strong>Heathrow</strong> earlier in the year, the workstreams to develop and<br />

evaluate options for the future of the airport have not progressed sufficiently to enable<br />

HAL to publish detailed cost and programme information for projects in Q6 and beyond.<br />

At the first special CIP Working Group (Refer to 6.1.5) held to consult on CIP <strong>2009</strong> 10<br />

HAL outlined the following approach to the airline community and received their<br />

endorsement to it.<br />

For the reasons outlined in sections 2.1 and 2.2 HAL do not wish to present a complete<br />

development programme for Q6 and beyond that is populated with detailed cost and<br />

time phased projects as to do so would suggest that such programme;<br />

• Is HAL’s considered response to the Government announcement on adding capacity<br />

at <strong>Heathrow</strong>,<br />

• Has had a number of options developed, evaluated and consulted upon to a point<br />

at which a proposal for development can be made,<br />

• Is reasonably definitive and<br />

• Is considered by HAL and the airline community to be affordable in both the short<br />

and long term.<br />

As a result the cost and time schedules provided as an appendix to this document detail<br />

only the capital investment in Q5 and do not present complete information for Q6 and<br />

beyond.<br />

Project Definition Sheets for possible investments in Q6 and beyond are provided for<br />

information and as an indication of the possible size and nature of the development on<br />

the current <strong>Heathrow</strong> campus. Any projects associated with the third runway and<br />

associated infrastructure are excluded from this publication. Appendix A: Project for the<br />

Sustainable Development of <strong>Heathrow</strong> provides additional information.<br />

At JST meetings 11<br />

and the special CIPWG 12 , HAL has outlined its intention to use the<br />

“vision” and masterplan attribute workstreams to set the context for joint prioritisation<br />

of future airport development with the airline community. HAL further outlined that it<br />

would see such prioritisation including consideration of the affordability of such<br />

development by the airline community. The flow diagram provided below captures this<br />

information.<br />

10<br />

Special CIPWG held 30 th January <strong>2009</strong>.<br />

11<br />

Joint Steering Team held 8 th December 2008 and 13 th January <strong>2009</strong>.<br />

12<br />

Special CIPWG held 30 th January <strong>2009</strong>.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 7


Figure 1: Schematic of Possible Passenger Processing and Apron Capacities for<br />

<strong>Heathrow</strong> in 2030.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 8


Figure 2: High level <strong>Plan</strong> of <strong>Heathrow</strong> Campus at March 2013.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 9


Preparing for Q6<br />

08/09 09/10 10/11 11/12 12/13<br />

CIP <strong>2009</strong> CIP 2010 CIP 2011 CIP 2012 CIP<br />

2013<br />

Masterplan<br />

Refresh Masterplan<br />

Refresh Masterplan<br />

/ storyboard work<br />

/ storyboard work<br />

/ storyboard work<br />

Agree “vision” and<br />

drivers for <strong>Heathrow</strong><br />

R3 / T6 Options &<br />

integration w/ M<strong>Plan</strong><br />

Develop initial info<br />

on Q6 projects<br />

Continue to develop<br />

detail on Q6 projects<br />

Refresh detail on<br />

Q6 projects<br />

Refresh detail on<br />

Q6 projects<br />

Agree Content of<br />

CIP <strong>2009</strong><br />

Start prioritisation of<br />

Q6 and beyond<br />

Refresh prioritisation<br />

of Q6 and beyond<br />

Refresh prioritisation<br />

of Q6 and beyond<br />

Develop User<br />

Charge scenarios<br />

Maintain Cost and<br />

User Charge Info<br />

Maintain Cost and<br />

User Charge Info<br />

Q6 Regulation<br />

Process<br />

Q6 content<br />

80:20 developed<br />

2.4 Development Workstreams<br />

Figure 3: Q6 and beyond consultation framework 13<br />

The following sub-sections are to be read in line with the earlier statements on the need<br />

to progress the vision and masterplan. As such, while they capture HAL’s current<br />

thoughts on future development themes, they are not fixed and shall be subject to<br />

consultation on an ongoing basis. The primary consideration in progressing all<br />

workstreams is the need to balance supply (bringing into operation of investment<br />

projects) against the capacity demand (driven by passenger growth and operational<br />

changes such as new aircraft fleets). The workstreams, and any projects in section 2.5<br />

that stem from them, should be seen as potential elements of a plan to be jointly<br />

prioritised, rather than a fixed proposal from HAL.<br />

2.4.1 Terminals including Piers / Satellites<br />

With the introduction of T5 in 2008, a programme of Q5 works has been enabled to colocate<br />

airline alliances, terminal refurbishment / replacement and importantly the need<br />

to offer competitive equivalence across all <strong>Heathrow</strong> campuses / terminals.<br />

HAL propose, to maximise the efficient use of land (including operationally efficient<br />

taxiway and runway hold processes) on the existing airport, that the principle of main<br />

terminal buildings and satellites being perpendicular to the runways will be continued.<br />

This “toast rack” arrangement, commenced by the Terminal 5 development, will<br />

continue initially in Terminal 2A (formerly known as <strong>Heathrow</strong> East Terminal) and its<br />

associated satellites. Consideration should be given to continuing this onto the Terminal<br />

3 areas of the Western apron (i.e. the land between Terminal 3 and Terminal 5).<br />

13<br />

Presented to the airline community at the London (<strong>Heathrow</strong>) <strong>Airport</strong> Consultative Committee<br />

meeting held on the 5 th February <strong>2009</strong>.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 10


Possibilities are outlined in the Project Definition Sheets in Appendix M: PDS – Q6 and<br />

Beyond Western Campus.<br />

Q6 investment plans should consider the continued development of the infrastructure<br />

along those key themes;<br />

• On the Eastern campus, the completion of T2A and T2B will enable the majority of<br />

STAR airlines to “Move Under One Roof” and develop the STAR product offer at<br />

LHR. It will then enable the commencement of the Phase 2 development which will<br />

result in an extension of T2A to handle 30mppa and a new baggage system.<br />

Possibly complemented by a second satellite (T2C) on which consultation has<br />

commenced. Works will seek to create sufficient capacity to complete the colocation<br />

of STAR airlines at <strong>Heathrow</strong> and provide equivalence to Terminal 5<br />

(connections, terminal, baggage, airfield).<br />

• On the Western Campus, plans should consider British Airways’ desire to have an<br />

integrated hub operation. (A single connected campus including bringing the<br />

Terminal 3 building to Terminal 5 standards.)<br />

• Development options on both campuses are still being considered in terms of the<br />

need to balance demand across the airport in an affordable manner.<br />

There are no significant changes to the nature of Terminal 4 during the period of this<br />

CIP, other than the works already commenced to modify the check-in area and<br />

forecourt.<br />

2.4.2 Baggage<br />

The development of baggage functionality for <strong>Heathrow</strong> is a key element to the robust<br />

operation of the airport in general, and the hub / transfer process in particular. The<br />

production of infrastructure solutions for Q6 and beyond will need to ensure that the<br />

baggage product can provide Minimum Connect Times for transferring passengers that<br />

are at least comparable with those for the passengers themselves, and be comparative<br />

with the other global hubs.<br />

Such functionality shall need to address the needs of intra (within) and inter (between)<br />

terminal / campus connections with a view towards a consistent airport wide product<br />

standard. Works will also need to take account of any ongoing compliance changes<br />

arising from regulatory authority requirements in terms of security (E.g. DfT or TSA) or<br />

safety (E.g. HSE).<br />

Future development of the departure and arrivals baggage systems should focus on joint<br />

end to end process improvement between HAL and the airline / ground handling<br />

communities in order to improve key performance metrics such as; missed bags /<br />

thousand passengers, and arrivals delivery.<br />

2.4.3 Airfield<br />

Other then general modifications to the stand and taxiway arrangements to suit the<br />

“toast rack” principle outlined in 2.4.1 there are no significant changes proposed during<br />

this CIP period. Early work on the positioning, number and nature of “toast rack”<br />

satellites has highlighted a critical need for the number and configuration (dual versus<br />

single) taxiways in both the western and eastern airfield campuses. The following<br />

principles for development of the airfield have been agreed 14<br />

with the airline<br />

community;<br />

14<br />

Eastern Maintenance Base gateway sign off event held 18 th February <strong>2009</strong>.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 11


• Balancing processor and apron capacity (minimise inter campus towing)<br />

• Balancing demand across the aprons<br />

• Taxiway operation<br />

• Efficient taxiway and hold operation<br />

• Redundancy and flexibility<br />

• Minimising towing<br />

• Minimise runway crossings<br />

• Higher pier service levels (>95%) without need for tactical intervention<br />

• Affordable<br />

2.4.4 Surface Access<br />

<strong>Heathrow</strong> is more than just an airport. It is the UK’s busiest transport interchange as<br />

well as its busiest bus and coach hub and, with Terminal 5 now included, there are<br />

seven railway stations on the airport. By any measure the range and variety of<br />

<strong>Heathrow</strong>’s surface access infrastructure plays a key role in HAL’s efforts to reduce<br />

unnecessary car use. The Surface Access Strategy is central to <strong>Heathrow</strong> maintaining this<br />

role. The strategy’s principles are well established. They are:<br />

• To seek to provide, working with third party transport providers, acceptable levels of<br />

service for travel to and from the airport for both air passengers and airport staff, in<br />

terms of journey time, reliability and cost;<br />

• To develop surface access strategies that are achievable and capable of being<br />

sustained within normal financial constraints and any conditions that may be laid down<br />

through the CAA’s regulatory controls;<br />

• To influence and be informed by national, regional and local transport policies and<br />

plans;<br />

• A commitment to the use of public transport and the minimisation of the impact<br />

arising from transport activities; and<br />

• To put the interests of all our surface access users, whether air passengers, staff or<br />

business visitors, at the forefront of our planning.<br />

HAL has maintained a clear, consistent and evolving Surface Access Strategy for<br />

<strong>Heathrow</strong> since the first consultation document was launched in 1996. The latest<br />

version of which was published in October 2008 called “Sustaining the transport<br />

vision:2008-2012”. Core policy statements covering the whole BAA Group were then<br />

agreed, with the first Strategy document for <strong>Heathrow</strong> being issued in 1999. This set<br />

out a rolling five year framework within which improvements to the airport’s surface<br />

access could be identified and taken forward. It also set 19 targets and objectives,<br />

including the goal of maintaining at least a 40% mode share to public transport for air<br />

passengers. The strategy has been reviewed and updated at regular intervals, with the<br />

targets and objectives being assessed for progress and, where appropriate, modified<br />

and new ones added.<br />

The strategic nature of <strong>Heathrow</strong> <strong>Airport</strong> and its ability to act as an interchange and<br />

‘hub’ for bus, coach and rail routes is increasingly being recognised by key stakeholders,<br />

including Transport for London and the South East England Regional Assembly through<br />

its South East <strong>Plan</strong>. <strong>Heathrow</strong> has been instrumental in helping to strengthen public<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 12


transport services in the South East region and we are keen to see the development of<br />

even stronger public transport links as part of airport development.<br />

The strategy for developing <strong>Heathrow</strong>’s Surface Access takes place against a<br />

background of continuing public debate about the nature of transport provision in the<br />

UK, coupled with an increasing awareness of the impact on the environment. If<br />

<strong>Heathrow</strong> is to be able to develop successfully into the future, then HAL are in no doubt<br />

of the need to address the accessibility needs of both air passengers and staff as part of<br />

the airport’s sustainable development.<br />

2.4.5 Connections<br />

Approximately a third of all passengers at <strong>Heathrow</strong> are transferring from one flight to<br />

another. Transfer traffic is important because it enables airlines to maintain the viability<br />

of routes through seasonal peaks / troughs as well as supporting a high frequency /<br />

many destinations route network. <strong>Heathrow</strong> is also unique in Europe as the<br />

developments being pursued will enable it to allow all three airline alliances to offer colocated<br />

transfer products.<br />

Within the previously outlined masterplan attributes context, strategic objectives for<br />

connections should be considered from the following;<br />

• Offer a world class product, equivalent or better to <strong>Heathrow</strong>’s European airport<br />

hub competitors and comparable to airport hubs worldwide;<br />

• Provides ease of transfer through low connection times and reducing hassle / mode<br />

changes that will enable airlines to offer competitive minimum connection times.<br />

• Supporting the forecasted growth in transfer volumes;<br />

A major element of the Q6 and beyond investment plans could be to introduce a new<br />

passenger transfer product based on Track Transit / Automated People Mover<br />

technology. The current airline aspiration is to have one single integrated APM system<br />

linking all Terminals and Satellites that enables both Originating / Destination passengers<br />

as well as connecting passengers a fast, reliable and efficient method of moving around<br />

the <strong>Heathrow</strong> campus.<br />

To enable this core Q6 investment could focus on, as a minimum;<br />

• Western Campus – extending the existing T5 Tracked Transit System to T3 to create<br />

an integrated hub for BA / Oneworld<br />

• Eastern Campus – introducing a new Tracked Transit System that links T2A to<br />

satellites B and C<br />

The aspiration extends to linking both campuses via a sub-surface route across the<br />

Central Terminal Area, with possible extensions to Terminal 4, and eventually full<br />

integration of any new 6 th terminal.<br />

Reference is made to section 2.4.2 and the need for alignment between passenger and<br />

baggage connectivity.<br />

2.4.6 Cargo and Maintenance Areas<br />

<strong>Heathrow</strong> handles significant quantities of cargo for the UK economy. HAL intends to<br />

pursue a review of the cargo operational areas in order to inform the future masterplan<br />

options for the areas. This review and input into the masterplanning work will be<br />

subject to airline consultation.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 13


In Q6 and beyond HAL expects there to be a need to modify the manner in which the<br />

current maintenance areas on the eastern side of the airport are configured in order to<br />

maximise the potential of <strong>Heathrow</strong>. Proposals on this are already being discussed with<br />

the airline community and shall continue to be developed.<br />

2.4.7 Ancillary Areas and Others<br />

As part of the Q6 prioritisation it will be necessary to investigate whether to invest<br />

significant sums in the heavy refurbishment of critical airport infrastructure such as the<br />

main access tunnel, airport utilities and the cargo tunnel. In addition HAL will bring<br />

forward proposals for investments to enable climate change (CO 2 ) and other<br />

environmental targets to be met.<br />

In the Project Definition Sheets for Q6 and beyond those for “Clean Working and<br />

Friendly” (CWF) works (i.e. minor projects and asset renewals) have been structured so<br />

as to link their budgetary value to the specific asset base they are intended to support.<br />

This being in contrast to the Q5 allocation which is <strong>Heathrow</strong> wide. This change in<br />

structure is reflective of HAL’s desire to improve clarity of these funds and allow for<br />

enhanced focused consultation, in Q6, with the relevant local terminal airline<br />

communities on how such monies could be tactically invested.<br />

2.5 Programmes<br />

To enable efficient delivery of the capital investment detailed in this CIP it has been<br />

necessary to divide the whole HAL investment programme into packages for project<br />

management.<br />

These packages, called programmes, are distinct from the workstreams described above,<br />

as they split the broader development needs into their relevant delivery groups. While<br />

the programme splits were originally envisaged for Q5 delivery, the airline community<br />

have asked 15 that this CIP be presented using the same split for Q6 and beyond.<br />

The programmes for the main <strong>Capital</strong> Projects investment works are;<br />

• Eastern Campus [Which covers the facilities in the geographic areas of T1 and T2<br />

including all land to the eastern edge of the operational airport.]<br />

• Western Campus [Which covers the geographic areas of Terminals 3,4, and 5.]<br />

• Baggage [Which covers pan-airport and local terminal baggage systems.]<br />

• Infrastructure [Which covers all airfield areas not explicitly included in Eastern or<br />

Western Campuses together with landside facilities.*]<br />

• Airline Relocations [Which covers the relocation activities for airlines moving<br />

between terminals.]<br />

* Infrastructure also deliver works on behalf of the Eastern and Western programmes.<br />

In addition to the <strong>Capital</strong> Projects investment programmes outlined above the following<br />

other programmes are included in the HAL CIP;<br />

• Information Technology (IT) / Systems [Which covers stand alone IT / Systems<br />

investment not delivered as part of a main capital investment works.]<br />

• Rail [Which covers <strong>Heathrow</strong> Express led investments.]<br />

• Project for the Sustainable Development of <strong>Heathrow</strong> (PSDH) Programme [Which<br />

covers the third runway and sixth terminal development.]<br />

15<br />

At the JST held 8 th December 2008.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 14


• Thames Water [Which covers ongoing payments associated with the purchase of the<br />

Terminal 5 site area.]<br />

2.6 Possible Future Development Projects in Q6 and Q7 Timescales<br />

Notwithstanding the statements made elsewhere in this document, HAL feels that<br />

provision of initial thoughts on possible future development projects, excluding those<br />

related to a third runway and sixth terminal, in this document does provide value into<br />

the consultation process for the period between CIP <strong>2009</strong> and CIP 2010.<br />

Following consultation 16 with the airline community these draft projects are presented in<br />

“programmes” aligned to the current Q5 delivery programmes with which HAL and the<br />

airline community are familiar.<br />

The detailed draft Project Definition Sheets are contained in the referenced appendices.<br />

These documents now need, in their next iteration, to be informed by the vision and<br />

masterplanning work outlined previously.<br />

2.6.1 Project for the Sustainable Development of <strong>Heathrow</strong><br />

For the reasons outlined earlier in sections 2.1 and 2.2, the impact of the January <strong>2009</strong><br />

Government decision on adding capacity at <strong>Heathrow</strong> <strong>Airport</strong>, and the works known as<br />

the Project for the Sustainable Development (PSDH) of <strong>Heathrow</strong> have not yet been fully<br />

assessed. Clearly the decision leads to the need to include, in future editions of the CIP,<br />

information on a third runway and sixth terminal at <strong>Heathrow</strong> together with the<br />

relevant supporting infrastructure.<br />

At this time, however, information on PSDH is detailed in Appendix A: Project for the<br />

Sustainable Development of <strong>Heathrow</strong> only. In future publications of the CIP and in the<br />

consultation processes outlined earlier, HAL considers it is essential that the third<br />

runway / sixth terminal issues are considered as integral with the existing <strong>Heathrow</strong><br />

operation and future development. I.e. Future editions of the CIP will document the<br />

development of a three runway airport.<br />

The airline community have asked 17 that their comment on PSDH be recorded here. The<br />

principal aspects of the comment they have asked be recorded is the different nature of<br />

consultation undertaken by HAL in respect of PSDH, and the manner in which the Q5<br />

monies were included in the regulatory settlement, including the absence of any trigger<br />

rebate type system. At the March <strong>2009</strong> Strategic Choices and JST meetings 18<br />

HAL<br />

furthered the discussions on how to address PSDH consultation and presented a<br />

proposal for “ex post” payment in Q5 by airlines for PSDH related expenditure. HAL<br />

feels that progression of these issues has addressed the central issues raised by the<br />

airline community. Constructive consultation continues.<br />

2.6.2 Eastern Campus Programme<br />

The development of the Eastern Campus in Q6 and Q7 will be done through a number<br />

of highly interdependent projects. At the time of preparing CIP <strong>2009</strong>, HAL are<br />

undertaking a comprehensive review of how this area of the airport could be developed.<br />

The outputs of the study will form part of the ongoing consultation with the airline<br />

16<br />

At the JST held 8 th December 2008.<br />

17<br />

At the Special CIPWG held 27 th February <strong>2009</strong>.<br />

18<br />

Meetings held 2 nd March <strong>2009</strong>.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 15


community and particularly the Star alliance as a key occupant of the area. Given this<br />

position a single project has been defined, for the purposes of CIP <strong>2009</strong> only, as<br />

“Eastern Campus Phase 2” in order that all of the bullet pointed principles espoused in<br />

2.3 can be applied. For the purposes of masterplan and project prioritisation it will be<br />

necessary to disaggregate the single project presented here into its component parts.<br />

The second satellite for T2, known as T2C, is included in this single project but has been<br />

the subject of separate discussion at constructive engagement due to the need, if it is<br />

desired by the airline community, to actively safeguard for the facility in Q5. T2C will<br />

need to be considered a separate project in the process mentioned above. (Reference<br />

should be made to section 3.8 on this point).<br />

2.6.2.1 List of Possible Eastern Campus Programme Projects<br />

Temporary “BCT” No and Project Name<br />

FQ01 : CWF T1 (Q6 & Q7)<br />

FQ02 : CWF T2 (Q6 & Q7)<br />

FQ03 : Eastern Campus Phase 2<br />

Table 2: Possible Q6 and Q7 Projects – Eastern Campus Programme<br />

2.6.3 Western Campus Programme<br />

Possible Western Campus works centre on pier redevelopments in Terminal 3 and a 3 rd<br />

satellite on T5. Further investment could be driven from British Airways’ / oneworld’s<br />

stated desire, as key occupants of Terminals 3 and 5, to operate T3 and T5 as an<br />

integrated hub on the western campus. There is currently no significant specific<br />

investment work envisaged for Terminal 4 which falls within the Western Campus<br />

Programme nomenclature.<br />

2.6.3.1 List of Possible Western Campus Programme Projects<br />

Temporary “BCT” No and Project Name<br />

General<br />

FQ23 : <strong>Heathrow</strong> TTS: T5 to T3 extension<br />

Terminal 3<br />

FQ24 : CWF T3 (Q6 and Q7)<br />

FQ25 : T3 Arrivals Reconfiguration<br />

FQ26 : T3 Check-in and Central Search Relocation<br />

FQ27 : T3 CIP Lounge Development<br />

FQ28 : T3 IDL Reconfiguration<br />

FQ29 : T3 New Northern Pier and Stands<br />

FQ30 : T3 Pier 5 and Stands (330 to 342) Reconfiguration<br />

FQ31 : T3 Pier 5 Demolition / Toast Racked Code F Stands<br />

FQ32 : T3 Pier 6 Extension and Stands<br />

FQ33 : T3 Pier 6 to T2A Link<br />

FQ34 : T3 Pier 7 Redevelopment<br />

FQ35 : T3 Refit for T1 Non-Aligned<br />

Terminal 4<br />

FQ36 : CWF T4 (Q6 and Q7)<br />

FQ38 : T4 Arrivals Reclaim for A380<br />

FQ39 : T4 Code F Stands Phase 2<br />

Terminal 5<br />

FQ37 : CWF T5 (Q6 and Q7)<br />

FQ40 : T5B Phase 2<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 16


FQ41 : T5C Phase 3<br />

FQ42 : T5D and Stands<br />

Table 3: Possible Q6 and Q7 Projects – Western Campus Programme<br />

2.6.4 Baggage Programme<br />

A number of broad themes for Q6 and beyond exist for the baggage product at<br />

<strong>Heathrow</strong>. These are summarised as;<br />

• Western Campus (T3, 4 and 5) – Possible need for improvements to the arrivals<br />

baggage processes.<br />

• Eastern Campus – Phase 2 of the development of the area.<br />

• Campus Wide Compliance – Manual handling and security compliance changes to<br />

the existing systems.<br />

• Campus Wide IT – With IT systems for baggage tending towards short (circa 5 year)<br />

lifecycles a need for replacement with Q6 is probable.<br />

At this time HAL does not present any potential baggage projects for Q6 and beyond.<br />

2.6.5 Infrastructure Programme<br />

In line with the surface access principles outlined earlier HAL expects to propose the<br />

development of a Public Transport Interchange (PTI) in the Central Terminal Area during<br />

Q6.<br />

During early Q6 it will be necessary to resurface / refurbish the two existing runways<br />

(27L / 09R and 27R / 09L).<br />

As explained in 2.4.7, the works known as Clean Working and Friendly (CWF), have<br />

previously been centralised for CIP purposes. For Q5 they are part of the Infrastructure<br />

Programme. Beginning in Q6 HAL propose that these allowances for capitalised minor<br />

asset replacement and renewal works be split by asset type and placed within more<br />

relevant geographic programmes. The list below therefore only includes pan-airport<br />

asset types, with the terminal / geographically specific allowances being presented in the<br />

Eastern and Western Campus listings.<br />

2.6.5.1 List of Possible Infrastructure Programme Projects<br />

Temporary “BCT” No and Project Name<br />

FQ04 : Additional Jetties - FQ<br />

FQ05 : Carbon Reduction<br />

FQ06 : Cargo Tunnel Renovation<br />

FQ07 : Code F A&B Taxiways between E&K Taxiways<br />

FQ08 : CWF Airfield (Q6 & Q7)<br />

FQ09 : CWF Connections (Q6 & Q7)<br />

FQ10 : CWF Other Areas (Q6 & Q7)<br />

FQ11 : <strong>Heathrow</strong> TTS: Inter Existing Terminals<br />

FQ12 : Landside Roads Infrastructure and Systems<br />

FQ13 : Main CTA Tunnel Renovation<br />

FQ14 : Maintenance of Retail Income<br />

FQ15 : Overlay Runway - Northern<br />

FQ16 : Overlay Runway - Southern<br />

FQ17 : PCA (existing facilities) - FQ<br />

FQ18 : Security Projects<br />

FQ19 : Utilities Infrastructure Upgrade<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 17


Table 4: Possible Q6 and Q7 Projects – Infrastructure Programme<br />

2.6.6 Airline Relocations<br />

The purpose of the Q5 Airline Relocations Programme is to deliver the current Move<br />

Sequence, primarily to enable airline alliance co-location and more efficient use of the<br />

airport’s infrastructure. In Q6 and Q7 it is reasonable to assume that as <strong>Heathrow</strong><br />

continues to develop the relocation of airlines between facilities will be an ongoing<br />

feature. HAL have therefore maintained the nomenclature to allow such expenditure to<br />

be readily recognised.<br />

At this time no specific projects are identified, but with the inclusion of the PDS called<br />

“FQ35 – T3 Refit for T1 Non-Aligned” the possible, subject to consultation, basis of<br />

some limited future airline relocations is recognised.<br />

2.6.7 Information Technology (IT) / Systems Programme<br />

In previous issuances of the HAL CIP broader IT investments have been documented<br />

through a single line entry. In section 3.6 the Q5 IT investments are clarified in greater<br />

detail. At this time it is assumed that the same broad investment categories shall apply<br />

for Q6 and beyond. No Project Definition Sheets have been prepared but at a minimum<br />

the following should be expected to be included in CIP 2010 onwards;<br />

• <strong>Airport</strong> Operational Systems (Q6 and beyond).<br />

• IT Infrastructure Renewal (Q6 and beyond).<br />

• Business <strong>Plan</strong>ning & Support IT (Q6 and beyond).<br />

It should be noted that this programme is for IT / Systems works that are stand alone.<br />

I.e. not part of a larger multi-functional project. For example; IT works related to a new<br />

building would be included within that building’s scope.<br />

2.6.8 Rail Programme<br />

As with IT, in previous issuances of the HAL CIP the rail investments have been<br />

documented through a single line entry. In section 3.7 the Q5 rail investments are<br />

clarified in greater detail. At this time it is assumed that the same broad investment<br />

categories shall apply for Q6 and beyond.<br />

2.6.8.1 List of Possible Rail Programme Projects<br />

Temporary “BCT” No and Project Name<br />

FQ20 : Crossrail<br />

FQ21 : HEx Growth Projects (FQ)<br />

FQ22 : HEx Renewal Projects (FQ)<br />

Table 5: Possible Q6 and Q7 Projects – IT / Systems Programme<br />

2.7 Risks and Assumptions<br />

In response to requests raised by the airline community, HAL has agreed to record the<br />

risks and assumptions that underpin the long term development plans. It is intended<br />

that such records shall be one of the main cornerstones of the plans and how they<br />

might be implemented / impact the airport with any points being clearly linked back to<br />

the master planning aspirations. At this time, pending progression of the consultation<br />

on such plans, no record of risks and assumptions is included in the CIP.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 18


3 Q5 Delivery<br />

During the first year of Q5 to 31 March <strong>2009</strong>, HAL has invested approximately £750<br />

million in the Q5 capital investment plan. Completion of the relocation of British<br />

Airways to Terminal 5 did not occur until October 2008, later than originally planned.<br />

HAL and the airline community have been in active consultation regarding the<br />

consequences of this change on the remainder of the Q5 capital investment plan.<br />

As a result, HAL and the airline community have agreed a number of amendments to<br />

the programme including changes to the relocation dates for airlines, re-phasing of<br />

various individual projects within the overall programme and the deferral of capital<br />

expenditure. These amendments have been documented with the airlines through the<br />

CCRS change control process. (Refer to section 5.7.) The highly interdependent nature<br />

of the Q5 capital programme means it is critical that effective consultation between HAL<br />

and the airline community continues throughout the Q5 period.<br />

This section of the CIP <strong>2009</strong> document is split into the programmes identified in section<br />

2.5. Sections 3.1 to 3.9 detail the broad Q5 development of each of the programmes,<br />

while section 3.10 details the Q5 trigger milestones.<br />

3.1 Eastern Campus Programme<br />

3.1.1 Overview<br />

The works centre on refurbishing Terminal 1 and commencing the new Terminal 2<br />

family of facilities. Included are the ancillary works to enable the major component<br />

projects (such as T2A and T2B,) to progress, for example, the demolition of the Queen’s<br />

Building.<br />

3.1.2 List of Projects<br />

BCT Number and Project Name as shown in Schedules<br />

Eastern Campus Airfield<br />

4202 : EA A/side Rd & Taxilane U/pass<br />

7207 : EAD Mid Stands & Taxilanes<br />

Leadership, Logistics and Enabling<br />

8828 : Eastern Campus EIS<br />

Landside<br />

3814 : New Build MSCP - East<br />

8888 : Control Tower Demolition<br />

T2B, T1 and VP<br />

6716 : Pier 3 Demolition<br />

4201 : T2B Centre, Stnds & Pax Connectivity<br />

4539 : T2B North<br />

7205 : T2B NW Stands & Taxilanes<br />

7209 : T2B SE Stands & Taxilanes<br />

7210 : T2B SW Stands & Taxilanes<br />

7212 : Relocation of Substation 56<br />

T2A Phase 1 & Associated Projects<br />

8807 : T2A Phase 1 Stands<br />

T2A Programme Phase 1 (See section 3.1.3)<br />

Table 6: Q5 Projects – Eastern Campus Programme<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 19


3.1.3 Additional Explanatory Notes<br />

The following points are noted to provide additional clarity on some PDS and schedule<br />

information;<br />

• T2A Programme Phase 1 PDS covers the following projects, that would otherwise<br />

have PDS’s in their own right, listed in the schedule;<br />

BCT Number and Project Name as shown in Schedules<br />

7779 : P23223 - T2A A/S Early Services Relocation<br />

8794 : Eastern Campus Leadership Team<br />

7769 : P23224 - T2A L/S Early Services Relocation<br />

7767 : P23225 - T2A Scheme Design Stage<br />

8802 : T2A Building<br />

8799 : QB Demolition<br />

8798 : Eastern Campus Logistics<br />

7230: P22848 – QB Staff Rest Decant<br />

8800 : T2 Demolition<br />

• BCT 4630 – The negative budget shown in the cost schedule reflects changes to the<br />

project management structures on the Eastern Campus only.<br />

• BCT AAAA – This is a temporary provision within the reporting structure which will<br />

be re-provisioned to the relevant projects. No PDS is provided.<br />

• BCT 7720 for T2A Phase 2, listed in the cost schedule, allows for Q5 funds linked to<br />

the Q6 and beyond PDS for Eastern Campus Phase 2. No PDS is provided as the<br />

scope will need to be determined based on the masterplan / prioritisation process<br />

outlined in section 2.<br />

3.2 Western Campus Programme<br />

3.2.1 Overview<br />

Refurbishment of Terminals 3 and 4 allow for general improvement of the facilities in<br />

line with the competitive equivalence and alliance co-location principles. For Terminal 5<br />

the investment centres on the T5C facility.<br />

3.2.2 List of Projects<br />

BCT Number and Project Name as shown in Schedules<br />

Terminal 3<br />

7540 : T3 Office Refurbishment Airline Moves<br />

3829 : MARSing STND 324 - 330 & CTA S<br />

5094 : Pier 5 Departures Walkway<br />

8002 : Pier 7 stands works<br />

7593 : T3 Zone B-G Upgrade<br />

8406 : Pier 7 Connector Refurb<br />

8494 : Pier 5 Gateroom Enclosures<br />

8510 : Landside Departures 1st Floor<br />

8563 : Immigration Hall Refurb<br />

0002 : T3 Additional Transfer Security Lanes - SQR<br />

8569 : T3 Baggage Hall Refit<br />

9222 : T3 Additional Departures Security Lane<br />

Terminal 4<br />

6604 : T4 Airline Relocation<br />

3831 : T4 Check-in Capacity<br />

6693 : Terminal 4 Refurbishment<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 20


8275 : T4 Victor Pier Refurbishment<br />

9028 : T4 Additional Transfer Security Lanes<br />

8274 : T4 Flooring<br />

Terminal 5<br />

T5C (See section 3.2.3)<br />

Table 7: Q5 Projects – Western Campus Programme<br />

3.2.3 Additional Explanatory Notes<br />

The following points are noted to provide additional clarity on some PDS and schedule<br />

information;<br />

• T5C PDS covers the following projects listed in the schedule;<br />

BCT Number and Project Name as shown in Schedules<br />

8335 : T5 Phase 2 Early Stands (Note: no AFC information provided in Appendix B of the<br />

PDS as work completed in 2008.)<br />

5221 : <strong>Heathrow</strong> Terminal T5C<br />

• BCT numbers 0002 and 9222 could be amended. (This applies to the BCT<br />

numbering only not the scope of the projects.)<br />

• BCT 3829 is only a budgetary provision. No work has commenced therefore no AFC<br />

information is provided in the appendix of the PDS.<br />

3.3 Baggage Programme<br />

3.3.1 Overview<br />

The main feature of the programme is the work to provide new or refurbished interterminal<br />

baggage connectivity.<br />

3.3.2 List of Projects<br />

BCT Number and Project Name as shown in Schedules<br />

7541 : T4 Post T5 Baggage Operation<br />

1851 : Post T5 Transfer Baggage System<br />

3798 : T4 Sorter Replacement<br />

3801 : T3 Integrated Baggage System<br />

3810 : System Baggage Cx refit T1 - T4<br />

4191 : Manual Handling Aids<br />

7969 : Terminal 4 Open Skies Baggage<br />

8747 : Baggage Integration<br />

8818 : Baggage Transition<br />

0615 : HBS VIVID replacement prog<br />

Table 8: Q5 Projects – Baggage Programme<br />

3.3.3 Additional Explanatory Notes<br />

The following points are noted to provide additional clarity on some PDS and schedule<br />

information;<br />

• BCT 7664 for T2A Ph2 Baggage System, listed in the cost schedule, allows for Q5<br />

funds linked to the Q6 and beyond PDS for Eastern Campus Phase 2. No PDS is<br />

provided as the scope will need to be determined based on the masterplan /<br />

prioritisation process outlined in section 2.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 21


3.4 Infrastructure Programme<br />

3.4.1 Overview<br />

The content of the programme is highly mixed but includes delivery of all landside and<br />

airfield works not included in the campus programmes.<br />

3.4.2 List of Projects<br />

BCT Number and Project Name as shown in Schedules<br />

Airfield<br />

1832 : Cargo Tunnel Refurbishment<br />

3817 : South East Taxiways<br />

2809 : A380 Taxiways around Pier 1<br />

3353 : Major Fire Appliance Replacement<br />

7206 : T2B NE Stands & Taxilanes<br />

7656 : Additional Jetty provision<br />

8857 : Taxiway / CDS Rebuilds (Q5)<br />

CWF<br />

3428 : CO2 Strategy<br />

6527 : HAL Minor Projects (Incl Retail & Property)<br />

FLI<br />

6136 : PiccEx Station Works<br />

4369 : Landside CTA Redevt Strategy<br />

7050 : N1 Car Parking Decking Project<br />

7718 : Eastern Maint Base Redev<br />

Security<br />

5056 : Physical Perimeter Security<br />

4242 : Self Service Boarder Control<br />

4185 : Cargo Area RZ Road (T5-T4 Rout<br />

8452 : Control Post Programme<br />

8801 : CP5<br />

9105 : Next Generation Autotray System<br />

9213 : Security Projects<br />

Retail<br />

7049 : JCD Media Sites<br />

Utilities<br />

7666 : Energy Infrastructure<br />

Table 9: Q5 Projects – Infrastructure Programme<br />

3.4.3 Additional Explanatory Notes<br />

The following points are noted to provide additional clarity on some PDS and schedule<br />

information;<br />

• BCT 3428 has not yet become a live project and therefore there is no AFC<br />

information provided in the PDS appendix.<br />

• BCT 6527 is delivered in large number (circa 500 over the quinquennium) of small<br />

projects each of which have their own CCB and AFC. As such the line entry and PDS<br />

details the budget allowance only and therefore no AFC information is provided in<br />

the PDS appendix. In addition the following three lines in the schedules are subsets<br />

of minor projects split by the contractor that will deliver the works. (LPI stands for<br />

Local Project Integrator.)<br />

9108 : LPI3 - ROK<br />

9106 : LPI1 - Inviron<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 22


9107 : LPI2 - Kier<br />

• BCT 7049 covers a wide range of small works. The budget provides an allowance<br />

within which sub-projects are allocated as needed. The AFC therefore matches CCB<br />

and no information on AFC is provided in the PDS appendix.<br />

3.5 Airline Relocations Programme<br />

3.5.1 Overview<br />

This programme exists to deliver the ancillary activities, (such as logistics, staff training<br />

and operational trials) that deliver the Airline Relocations Move Sequence. The move<br />

sequence is a key driver of the Q5 CIP delivery. The resource allocated to this<br />

programme provide the overarching support governance to the moves. Consultation<br />

and governance with the airline community is via the Airline Relocations Working Group<br />

which has been running since October 2006.<br />

The current move sequence is shown below.<br />

Note: Steps 4.1 and 4.2 have been completed since publication of the sequence.<br />

Figure 4: Airline Relocations Move Sequence 3.1<br />

3.5.2 List of Projects<br />

BCT Number and Project Name as shown in Schedules<br />

7966 : Operational Readiness<br />

7702 : Relocation of Airlines IT Operations<br />

Table 10: Q5 Projects – Airline Relocations Programme<br />

3.6 IT / Systems Programme<br />

3.6.1 Overview<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 23


The IT programme delivers the key backbone assets for <strong>Heathrow</strong>. The new “projects”<br />

listed below clarify the scope.<br />

3.6.2 List of Projects<br />

BCT Number and Project Name as shown in Schedules<br />

Telecomms Programme<br />

3606 : Telecoms Programme<br />

Central IT<br />

IT01 : <strong>Airport</strong> Operational Systems<br />

IT02 : IT Infrastructure Renewal<br />

IT03 : Business <strong>Plan</strong>ning & Support IT<br />

Table 11: Q5 Projects – IT / Systems Programme<br />

3.6.3 Additional Explanatory Notes<br />

The following points are noted to provide additional clarity on some PDS and schedule<br />

information;<br />

• BCT 4241, IT Major Projects has been removed and replaced by IT01, 02 and 03<br />

shown above.<br />

• IT01, IT02 and IT03 are temporary BCT numbers for the purpose of publishing CIP<br />

<strong>2009</strong> only.<br />

3.7 Rail<br />

3.7.1 Overview<br />

Rail investments are led by <strong>Heathrow</strong> Express. The scope is clarified by the “projects”<br />

listed below.<br />

3.7.2 List of Projects<br />

BCT Number and Project Name as shown in Schedules<br />

<strong>Heathrow</strong> Express<br />

R001 : HEx Growth Projects<br />

R002 : HEx Renewal Projects<br />

Other Rail<br />

R003 : Airtrack<br />

R004 : Connect 4 tph<br />

Table 12: Q5 Projects – Rail Programme<br />

3.7.3 Additional Explanatory Notes<br />

The following points are noted to provide additional clarity on some PDS and schedule<br />

information;<br />

• R001 to R004 are temporary BCT numbers for the purpose of publishing CIP <strong>2009</strong><br />

only.<br />

3.8 PSDH<br />

3.8.1 Overview<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 24


The Q5 CAA decision allowed for monies to be spent on PSDH related work. The nature<br />

of the current PSDH position is outlined in Appendix A: Project for the Sustainable<br />

Development of <strong>Heathrow</strong>.<br />

In addition consultation has been undertaken with the airline community with regard to<br />

the use of Q5 PSDH monies to actively safeguard for PSDH related development. The<br />

two areas of discussion have been around T2C and Eastern Maintenance Base<br />

safeguarding.<br />

Of these the significant elements for CIP <strong>2009</strong> are the safeguarding works in and<br />

around T2B to enable a future T2C to be built. Appendix K: PDS – Eastern Campus<br />

Phase 2 Enabling provides further details of the possible Q5 safeguarding funding<br />

requirements in respect of T2C.<br />

The current consultation on T2C safeguarding concluded in February <strong>2009</strong> with the<br />

following statement being made 19 by the airline community.<br />

“Airlines accept that the £2.8m for T2B substructure & tunnel design should be drawn<br />

down from the <strong>2009</strong>/10 PSDH expenditure.<br />

This approval of the £2.8m from PSDH expenditure in <strong>2009</strong>/10 should not be<br />

misinterpreted as approval from the airline community of the general use of PSDH<br />

funding for non-R3/T6 expenditure for the remainder of the quinquennium, either on<br />

T2C or other projects. As the priority, HAL must detail the anticipated Q5 expenditure<br />

necessary to ensure that R3/T6 is delivered at the earliest opportunity. The primary basis<br />

for the fund is to ensure a swift response to the Government’s go-ahead for Runway 3<br />

and submission of a planning application at the earliest possible date.<br />

Before any consideration/approval of the use of any remaining PSDH expenditure is<br />

given for other projects, HAL must demonstrate the requirement for alternative<br />

expenditure [egT2C]. Given the current economic climate, HAL must also engage with<br />

the airline community to ensure the correct balance between the requirement of other<br />

projects and the potential to return funding.<br />

The airline community will continue to discuss their interpretation of the PSDH funding<br />

agreement with BAA and CAA to ensure a fair and appropriate response to PSDH<br />

requirements. The airlines continue to maintain that they agreed to include PSDH<br />

funding in the Q5 settlement only on the basis that funds would be added to the CIP in<br />

the year after they were expended.”<br />

On the basis of this agreement change control paperwork (Refer to section 5.7) is being<br />

presented to formally transfer budgets.<br />

3.8.2 List of Projects<br />

BCT Number and Project Name as shown in Schedules<br />

R3T6 : PSDH Q5<br />

Table 13: Q5 Projects – PSDH<br />

19<br />

The text in purple was sent, by way of formal agreement to decisions taken in the PSDH<br />

Working Group on 12 th February <strong>2009</strong>, from David Stewart (IATA) on 22 nd February <strong>2009</strong> by<br />

email to HAL.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 25


3.8.3 Additional Explanatory Notes<br />

The following points are noted to provide additional clarity on some PDS and schedule<br />

information;<br />

• R3T6 is a temporary BCT number for the purpose of publishing CIP <strong>2009</strong> only.<br />

3.9 Thames Water<br />

3.9.1 Overview<br />

This publication continues the March 2008 20<br />

separate identification of payments to<br />

Thames Water related to the purchase of land associated with Terminal 5. However,<br />

previous publications of the CIP did not show these monies. These payments continue at<br />

a broadly constant level until 2035.<br />

3.9.2 List of Projects<br />

BCT Number and Project Name as shown in Schedules<br />

TW01 : Thames Water Ongoing Payments<br />

Table 14: Q5 Projects – Thames Water<br />

3.9.3 Additional Explanatory Notes<br />

The following points are noted to provide additional clarity on some PDS and schedule<br />

information;<br />

• TW01 is a temporary BCT number for the purpose of publishing CIP <strong>2009</strong> only.<br />

3.10 Trigger Milestones<br />

3.10.1 Q5 Regulatory Decision<br />

A feature of the CAA price control 21 at <strong>Heathrow</strong> is a series of projects (so called ‘capital<br />

investment trigger projects’) where a deferral in project delivery would lead to an<br />

adjustment to aeronautical charges that can be levied by HAL. These adjustments are<br />

intended to ensure that HAL only starts to earn a return on investment once the relevant<br />

project is delivered.<br />

There are a total of 24 such projects that cover approximately 60% of HAL’s Q5 capital<br />

investment programme. The CAA regulatory settlement for Q5 at <strong>Heathrow</strong> provided<br />

that if none of these projects were delivered at all during Q5, a maximum cumulative<br />

reduction to aeronautical charges of £278 million would occur. Forecast total<br />

aeronautical charges over Q5 in the CAA’s price control document are £5,531 million<br />

meaning that the maximum potential reduction is about 5% of total aeronautical<br />

income. Note: All figures in this section are in 2007/08 prices. Table 13-2 of the CAA<br />

March 2008 publication “Economic Regulation of <strong>Heathrow</strong> and Gatwick <strong>Airport</strong>s”<br />

provides further details.<br />

The specifications of those capital triggers were set out in broad terms and the relevant<br />

dates and rebates determined in the CAA decision. They were, however, not defined to<br />

20<br />

As detailed in table 3.8 of Economic Regulation of <strong>Heathrow</strong> and Gatwick <strong>Airport</strong>s, CAA<br />

Decision, 11 th March 2008<br />

21<br />

See also Section 4.2.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 26


a working level. In March <strong>2009</strong>, following a period of joint working between HAL and<br />

the airline community and formal consultation by the CAA, the CAA published the final<br />

definitions of the trigger projects.<br />

3.10.2 Trigger Completion<br />

3.10.2.1 Process<br />

The CAA has set out that the process for testing whether a trigger has been met will be<br />

as follows:<br />

1. the airport will send certification of completed works to the CAA for confirmation of<br />

successful performance against the triggered project milestone(s); and<br />

2. the CAA will then consult the airline community (by means of a letter to the AOC)<br />

and investigate if any concerns are raised.<br />

In practice the detailed process as implemented by HAL and the airline community is as<br />

follows;<br />

• HAL and relevant airline community representatives meet on site and formally record<br />

the completion of the project / project element including any agreed outstanding<br />

items.<br />

• HAL write to the CAA providing copies of the relevant documentation from the site<br />

meeting. (Point 1 above)<br />

• The CAA then write to the <strong>Heathrow</strong> AOC to request comment on the completion,<br />

or otherwise, of the trigger. (Point 2 above)<br />

• The AOC write to the CAA to comment on the completion.<br />

3.10.2.2 Trigger Status<br />

The current status of the capital investment trigger projects is that 2 projects have been<br />

delivered on time and agreed by the CAA. These are the ‘T4 New CIP Lounge –<br />

Completion of Shell and Core For Fit Out’ and the ‘T1 Completion of bmi Nose Building<br />

Facility’. As a result, the maximum amount of aeronautical charges at risk has reduced<br />

to £268 million (in 2007/08 prices).<br />

Details of the status of all the capital investment trigger projects, as at February <strong>2009</strong><br />

month end, is set out in Appendix R: Time Schedules.<br />

3.10.2.3 Change Control<br />

As explained earlier, at the time of preparing this document the final trigger definitions<br />

only recently been published by the CAA. Due to changes since the start of the<br />

governance, HAL has a number of “pending” changes that it may seek through the<br />

CAA’s trigger change control process. HAL will now commence the process in respect of<br />

these changes as the final definitions have been published. The CAA’s change control<br />

process is outlined in Appendix B: Trigger Change Control. HAL and the airline<br />

community have developed 22<br />

a working level process to define how they will work<br />

together to bring any proposed changes to triggers before the CAA after a period of<br />

consultation.<br />

While the concept of triggers was introduced in Q4, the percentage of the capital<br />

investment plan covered by the triggers in Q5 is significantly greater and is applied to a<br />

22<br />

The process will be presented to the JST meeting scheduled for 11 th May <strong>2009</strong> for final<br />

agreement.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 27


oader sphere of projects. This change in emphasis coupled with the complex<br />

interdependent nature of the Q5 plan means that a number of issues are emerging<br />

which HAL may seek to address via trigger change control requests.<br />

3.11 Ongoing Scope Gap Review<br />

In consultation with the airline community HAL has been undertaking reviewing the<br />

delivery of “transformation” projects in Terminals 1, 3 and 4. The objective for the work<br />

has been shared with the airline community as; “To review the planned suite of<br />

“Transformation” projects for efficient and consistent delivery of the <strong>Heathrow</strong><br />

Transformation Vision. Recognise gaps and what work would be required to fill them”.<br />

“Transformation” in this context being terminology to describe the general uplifting of<br />

the passenger experience within existing terminal facilities during Q5.<br />

This review has resulted in four prioritised classifications of possible project work being<br />

defined;<br />

1. Capacity and Functional,<br />

2. High Passenger Impact/High Airline Expectation,<br />

3. High Passenger Impact, and<br />

4. Lower Passenger Impact.<br />

The airline community have worked with HAL to create the possible projects detailed<br />

against the four classifications. Consultation will continue as to which of these works<br />

can be delivered within Q5 and how they can be funded from within the CIP.<br />

3.12 Anticipated Final Cost (AFC) to Current Control Budget Gap (CCB)<br />

A key part of the governance of the Q5 capital investment programme is the ongoing<br />

monitoring between HAL and the airline community of the difference (or gap) between<br />

the budget (CCB) and anticipated final cost (AFC) of the proposed investment plans.<br />

HAL and the airline community monitor this difference on a monthly basis. As a result<br />

of work completed since the commencement of the quinquennium, including improved<br />

scope clarity, the difference between AFC and CCB is currently assessed to be 3% of<br />

the total spend in the quinquennium. It has reduced in recent months and HAL is<br />

confident that the difference will be eliminated in due course through a combination of<br />

procurement initiatives and delivery efficiencies.<br />

Note: The difference applies only to the <strong>Capital</strong> Projects element of the total HAL CIP.<br />

Refer to section 5.2 for additional information on Anticipated Final Cost (AFC) and<br />

Current Control Budget (CCB).<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 28


4 Regulatory and Legislative Context<br />

<strong>Capital</strong> investment led development at <strong>Heathrow</strong>, as outlined in this document, takes<br />

place within a framework of regulatory and legislative policy. This framework gives rise<br />

to a series of assumptions with regard to how the development / investment takes<br />

place. This section provides an overview of the current key issues.<br />

4.1 Aviation and <strong>Airport</strong> Policy<br />

Government policy essentially provides the context for the development of the third<br />

runway and associated infrastructure at <strong>Heathrow</strong> and as such is, for the purposes of<br />

this CIP publication, detailed within Appendix A: Project for the Sustainable<br />

Development of <strong>Heathrow</strong>.<br />

4.2 Economic Regulation<br />

4.2.1 Current Regulation<br />

The 1986 <strong>Airport</strong>s Act established a system of economic regulation for those airports<br />

with an annual turnover in excess of £1 million (in at least two of the three previous<br />

financial years). Under the terms of the Act, such airports must have permission, granted<br />

by the Civil Aviation Authority (CAA), in order to levy airport charges. In addition, the<br />

act also allows for the designation of airports, by the Secretary of State, for price cap<br />

regulation. For such airports the (CAA),sets an airport charges price cap for a five year<br />

period. The price cap is reviewed every five years.<br />

<strong>Heathrow</strong> <strong>Airport</strong> is currently a designated airport and as such regulated with a price<br />

cap regime by the CAA.<br />

Section 39 of the <strong>Airport</strong>s Act imposes four duties on the CAA in determining the price<br />

formula, namely;<br />

• To further the reasonable interests of users of airports within the United Kingdom;<br />

• To promote efficient, economic and profitable operation of such airports;<br />

• To encourage investment in new facilities at airports in time to satisfy anticipated<br />

demand by the users of such airports; and<br />

• To impose the minimum restrictions that are consistent with the performance by the<br />

CAA of its functions under those sections.<br />

It should be noted that under the third duty above, anticipated demands for airport<br />

users includes future users as well as current users. The definition of users (in Section<br />

82 of the <strong>Airport</strong>s Act 1986) includes both airlines and passengers, and no priority is<br />

specified between these two groups.<br />

The March 2008 CAA Decision 23<br />

sets out the relevant regulatory parameters for Q5<br />

which include the planned capital expenditure totals for Q5. This publication relies of<br />

the capital expenditure allowances set forth in the decision document.<br />

4.2.2 Future Regulation<br />

23<br />

Economic Regulation of <strong>Heathrow</strong> and Gatwick <strong>Airport</strong> 2008 - 2013, CAA Decision, March<br />

2008.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 29


In April 2008, the Secretary of State announced a review of the regulatory framework<br />

for UK airports. The regulatory system for airports is one of the oldest systems having<br />

been in place since the <strong>Airport</strong>s Act of 1986.<br />

The Secretary of State set out the following three objectives for the future development<br />

of the regulatory framework which reflect the Government’s policy objectives.<br />

• Improving the passenger experience;<br />

• Encouraging appropriate and timely investment in additional capacity to help deliver<br />

economic growth in line with wider Government policy; and<br />

• Addressing the wider environmental impacts of aviation on airport development.<br />

The Department for Transport is leading the review with the support from an<br />

independent expert panel. The review is intended to complement the strategic review<br />

of the CAA undertaken by Sir Joseph Pilling and the market inquiry of BAA by the<br />

Competition Commission (CC) (allowing for the DfT to submit evidence to the CC and<br />

take forward recommendations from the CC).<br />

The DfT noted that if legislation is required following this review, it would be taken<br />

forward in a future legislative session and would not impact on the current Q5 price<br />

caps at <strong>Heathrow</strong>.<br />

The table below sets out the key publication dates thus far in the review and BAA’s<br />

understanding of the expected publication dates during <strong>2009</strong>. The below table does not<br />

include the details of additional meetings and seminars the DfT and / or its expert panel<br />

have held.<br />

April 2008<br />

Secretary of State announcement of the review and publication<br />

of the Terms of Reference<br />

June-July 2008 The DfT calls for evidence<br />

September 2008 DfT publish their response to CC’s Provisional Findings and as<br />

part of this response request additional views on the review<br />

November 2008 The Independent Panel publish their Emerging Thinking of the<br />

review<br />

Q1 <strong>2009</strong><br />

DfT published a Consultation document<br />

Q3-4 <strong>2009</strong> DfT are expected to publish conclusions and then legislate at the<br />

earliest opportunity<br />

Table 15: DfT Timetable<br />

In November 2008, the Independent Panel published its Emerging Thinking, a summary<br />

of the key areas and recommendations are noted below:<br />

• Possible objectives of regulation and duties (and process) of the regulator including<br />

a duty to promote the interests of consumers and an environmental duty on the<br />

regulator;<br />

• The introduction of licences with possible classifications of the different types of<br />

licence for airports;<br />

o<br />

o<br />

with significant market power, requiring some form of price control;<br />

those not requiring price control, with relevant aeronautical revenues in<br />

excess of a specified monetary sum which may require consultation with<br />

users; and<br />

o the remainder.<br />

• Consideration whether other airports than <strong>Heathrow</strong> and Gatwick should be<br />

required to publish information in order to improve the passenger experience;<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 30


• Consideration of the role of consumer representation at a national and airport level;<br />

and<br />

• Valuable safeguards that the introduction of Special Administration and ring-fencing<br />

would offer for a small number of airports.<br />

On the 9 th March <strong>2009</strong> the DfT published “Reforming the framework for the economic<br />

regulation of UK airports”.<br />

This possible impacts on HAL with regard to the investment plan stated in this<br />

document for Q6 and beyond are made without prejudice to the above detailed review<br />

and any legislative or regulatory amendments that may arise as a result.<br />

The airline community have expressed 24 a desire to see consultation on future regulation<br />

issues to ensure joint understanding of the emerging issues and minimise any resultant<br />

possible ambiguity.<br />

4.3 Other Relevant Issues<br />

4.3.1 Town and Country <strong>Plan</strong>ning<br />

All development is regulated by primary legislation set out in the 1990 <strong>Plan</strong>ning Act.<br />

Secondary legislation, such as the General Permitted Development Order (GPDO) 1995,<br />

further defines what types of development may require planning permission, including<br />

aviation development. Generally, any development at <strong>Heathrow</strong> involving the extension<br />

of a runway or terminal, the provision of a new terminal, or a non-operational building<br />

(i.e. not connected to the operation or function of the airport) will require planning<br />

permission in the normal manner.<br />

Any development requiring planning permission, and likely to cause a significant<br />

environmental impact, could also be subject to the Environmental Impact Assessment<br />

(EIA) process, whereby the planning application would need to be accompanied by an<br />

Environmental Statement setting out all likely significant environmental impacts arising<br />

from the development. The requirements for EIA are also set out in secondary legislation<br />

but in respect of <strong>Heathrow</strong>, only usually apply to major projects, such as substantial new<br />

stand capacity or new terminal buildings.<br />

The General Permitted Development Order (GPDO) defines what types of development<br />

at an airport can be regarded as ‘permitted development’, i.e. development not<br />

requiring planning permission. Generally, this is defined as development, undertaken by<br />

the airport operator, on operational land, required in connection with the operation of<br />

the airport. This covers most forms of airport related development, such as; new aircraft<br />

hangars, industrial and cargo buildings, multi-storey car parks, office buildings, aircraft<br />

stands, piers and satellites.<br />

Although ‘permitted development’ does not require planning permission, there is a<br />

requirement to consult the planning authority, which means following the same process<br />

as a planning application, albeit that the planning authority cannot refuse approval for<br />

the development. This does not however prevent the planning authority from objecting<br />

to specific developments and, in extreme cases, the planning authority could request the<br />

Secretary of State to remove Hal’s permitted development rights should there be a clear<br />

abuse of it’s powers in this respect. There is also the possibility that any permitted<br />

development over 1ha in site area, and likely to cause a significant environmental<br />

24<br />

At the Special CIPWG held 27 th February <strong>2009</strong>.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 31


impact, could also be caught by the EIA process, in which case permitted development<br />

rights would be lost and the normal planning application process would need to be<br />

followed.<br />

In determining whether development at an airport is acceptable or not, the 2004<br />

<strong>Plan</strong>ning Act sets out the hierarchy and format of the development plan process which<br />

controls the amount and type of development at the national, regional and local levels.<br />

At the national level, aviation development is governed by the Aviation White Paper,<br />

2003 and subsequent updates. At the regional level for <strong>Heathrow</strong>, the London <strong>Plan</strong><br />

provides the relevant planning policy framework for London and must be in general<br />

conformity with national policy. At the local level, planning policies for the <strong>Heathrow</strong><br />

area are contained within the Hillingdon Unitary Development <strong>Plan</strong>, which must also<br />

conform to the higher tier regional and national policies.<br />

Local and regional planning policy specific to <strong>Heathrow</strong> is generally supportive of<br />

development that consolidates <strong>Heathrow</strong>’s growth with five terminals and within the<br />

defined airport boundary. However, there is no local or regional policy framework in<br />

place to yet support <strong>Heathrow</strong>’s growth with a third runway and sixth terminal.<br />

The <strong>Plan</strong>ning Act 2008 provides a new procedure, through the establishment of an<br />

Infrastructure <strong>Plan</strong>ning Commission and National Policy Statements (NPS), for dealing<br />

with nationally significant infrastructure projects in order to overcome the perceived<br />

deficiencies and delay inherent in the previous planning inquiry process. The Act focuses<br />

on the delivery mechanism for any Nationally Significant Infrastructure Projects (NSIP’s).<br />

Such major infrastructure will be addressed in 12 sectors (e.g. Energy, Waste, Water,<br />

Rail & Highways) based NPS’s which provide the strategic planning policy framework for<br />

each type of major infrastructure. In the future, any airport developments that result in<br />

new buildings or runways that would generate in excess of 10mppa or 10,000 cargo air<br />

traffic movements would be subject to the new procedure.<br />

The NPS’s to be produced by the Secretary of State, will integrate socio economic<br />

environmental and planning considerations, will be produced by the Secretary of State<br />

and are programmed to be rolled out from <strong>2009</strong> through to 2011. The NPS for airports<br />

is to be the last NPS with a draft expected in <strong>2009</strong>.<br />

A radical change to the planning system that the Act has introduced is the creation of a<br />

Infrastructure <strong>Plan</strong>ning Commission (IPC). The IPC will be the independent decision<br />

making authority responsible for examining a planning application made for a<br />

development consent order for a NSIP. The Act has permitted that only under very<br />

limited and specific circumstances may a planning decision for a major infrastructure<br />

project now be determined by the Secretary of State. The examination process and<br />

issuing of a decision are to a strict time limit of six and three months respectively, hence<br />

once an application for development consent has been submitted then the process<br />

should, in theory, last a total of nine months.<br />

The Act has also driven the need for greater participation and engagement requiring<br />

pre- application consultation opportunities, extensive consultation of the draft NPS’s and<br />

the ability for interested parties to request the examination process hold an ‘open floor’<br />

public hearing.<br />

The <strong>Plan</strong>ning Act also brings the introduction of a Community Infrastructure Levy (CIL).<br />

This is a new charge which Local Authorities will be empowered to collect on most<br />

forms of development in their area. CIL will be based on a simple formulae which relates<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 32


to the size and character of the development it is being charged against. The levy will be<br />

used by the Local Authorities fund new local and sub regional infrastructure.<br />

4.3.2 Climate Change Policy<br />

The UK Government’s national climate change strategy sets out its commitment to<br />

reduce climate change emissions across the economy, including domestic aviation, by<br />

60 per cent by 2050.<br />

The Stern Review on the economics of climate change, published in autumn 2006,<br />

highlighted the need for an urgent and effective international response to the issue. It<br />

also recommended that the best way to tackle carbon emissions is to ensure that each<br />

activity which consumes carbon is priced in the way that reflects its external costs.<br />

UK Government policy is that the price of air travel should, over time, reflect its<br />

environmental and social impacts. To achieve this, the Government continue to pursue<br />

the inclusion of aviation emissions in the European Union (EU) emissions trading scheme<br />

(ETS) as soon as practicable. The Government’s view, which BAA supports, is that<br />

inclusion of aviation in the EU ETS is the most efficient and cost-effective way to ensure<br />

that the sector plays its part in tackling climate change.<br />

The European Commission brought forward a draft Directive to include aviation in<br />

emissions trading in 2006. The European Parliament voted on this draft legislation in<br />

October 2007, and the European Council reached political agreement on the issue in<br />

December 2007. Discussions have continued during 2008 with the second reading of<br />

the<br />

draft.<br />

The Government is also working towards international agreement on a way to bring<br />

international aviation emissions within the wider post- 2012 framework, following up<br />

the Kyoto Protocol. BAA supports this work and views action at a European level as an<br />

interim step towards a global aviation climate policy framework.<br />

The Government has also recommended that all airports plan to become carbon neutral.<br />

BAA currently has a target to reduce CO2 emissions from its energy use in fixed assets<br />

by 30% below 1990 levels by 2020.<br />

4.3.3 New EU Air Quality Directive<br />

In April 2008, the EU published a new directive (2008/50/EC) whereby member states<br />

are allowed to postpone implementation of some EU air quality limit values. For<br />

nitrogen dioxide, 5 extra years are allowed, meaning that concentration limits would<br />

have to be met in 2015. BAA’s understanding is that DEFRA will request this time<br />

extension for the UK, where it will lay out the measures to be taken to meet the target<br />

by the new date.<br />

The impact of this decision on the future development at <strong>Heathrow</strong> will need to be<br />

assessed in due course.<br />

4.3.4 Noise Map and Action <strong>Plan</strong>s<br />

In accordance with the Environmental Noise Directive (2002/49/EC), BAA’s English<br />

airports are preparing draft noise action plans for public consultation in <strong>2009</strong>. This<br />

follows publication of noise Lden contours UK airports in 2006. BAA are awaiting<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 33


publication of statutory guidance from DEFRA before finalising and launching the<br />

consultation.<br />

4.3.5 Airspace Issues<br />

The December 2006 Air Transport White Paper Progress Report stated that the current<br />

air traffic arrangements for some UK airports are already nearing capacity (especially in<br />

the South East), and the related airspace is among the most congested in the world. The<br />

White Paper recognised the need for a structured programme for the redesign of UK<br />

airspace that would help protect safety standards, relieve current constraints, reduce<br />

delays, take account of environmental impacts and accommodate the forecast increase<br />

in air transport movements where additional capacity was supported in the White Paper.<br />

As a result the DfT, National Air Traffic Services (NATS) and CAA (Directorate of Airspace<br />

Policy) have convened a group looking at Future Airspace Strategy (FAS). NATS have<br />

begun work on a two year scoping study for FAS.<br />

BAA has a new five year contract with NATS for the provision of aerodrome control and<br />

certain approach services at each of the seven UK airports. With the end to “direct<br />

charging” these services are now paid for by the airports. The contract sets out<br />

governance structures, services included, tariffs, procedures for capital projects and exit<br />

managements provisions for each airport.<br />

NATS have consulted on a proposed piece of airspace change for TC North (a wide area<br />

covering North London and parts of East Anglia). This proposes changes to holding<br />

patterns and arrival and departure routes for BAA and non BAA airports in the area, in<br />

particular to take account of precision navigation (PR-NAV), the need to reduce holding<br />

and distance flown, maintain safety and allow for traffic growth. There are implications<br />

for noise profiles on the ground. Consultation closed in June 2008, responses were<br />

addressed and NATS are awaiting a decision on the proposal from the CAA.<br />

The development of a third runway at <strong>Heathrow</strong> will require further changes to the<br />

airspace. A new airspace change proposal will be brought forward to address this, led<br />

by HAL, in conjunction with NATS.<br />

Any possible impacts on HAL’s investment plans arising from this process are currently<br />

excluded from the plans detailed in this document.<br />

4.3.6 Public Safety Zones Review<br />

Public Safety Zones (PSZ’s) are areas of land, at the end of runways at the busiest UK<br />

airports, within which development is restricted in order to control the number of<br />

people on the ground, at risk of death or injury, in the event of an aircraft accident on<br />

take off or landing. The runways at <strong>Heathrow</strong> have PSZ’s associated with them.<br />

Guidance on the policy and administration of <strong>Airport</strong> Public Safety Zones in England and<br />

Wales is published by the Department for Transport (DfT).<br />

The PSZ’s currently published for BAA airports are based on risk contours modelled for<br />

2015. PSZ policy stipulates the circumstances when PSZ’s should be remodelled. This<br />

can be required due to;<br />

• a significant expansion of an airport (The DfT has indicated the broad objectives of<br />

PSZ policy as applicable to existing runways should be applied where possible to<br />

proposed future runways),<br />

• a change to an existing runway’s configuration,<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 34


• the requirement for a general update. (It is a requirement of PSZ policy that PSZ’s<br />

should undergo a general review approximately every 7 years.)<br />

Initial work has begun to develop the programme for reviewing Public Safety Zones.<br />

This work will continue during <strong>2009</strong>. HAL will work with DfT as appropriate to progress<br />

this work.<br />

Pending progression of this work, any capital expenditure associated with complying<br />

with any revision to the PSZ’s at <strong>Heathrow</strong> is currently excluded from the investment<br />

plans.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 35


5 Technical Notes<br />

5.1 Project Definition Sheets<br />

Previous versions of the <strong>Heathrow</strong> CIP have contained “Project Descriptions and Cost<br />

Advisory Sheets”. These documents were completed for projects over £20m.<br />

In CIP <strong>2009</strong>, Project Definition Sheets (PDS’s) have been introduced to fulfil the same<br />

purpose. The Project Definition Sheets have been upgraded, from the previous CIP<br />

equivalents. The template for the Project Definition Sheets was consulted upon with the<br />

airline community at the CIPWG 25 .<br />

The key changes in the PDS content / process are;<br />

• PDS completed for all projects with a budget greater than £3m. (See note 1 below)<br />

• Inclusion of information on BAA and airline higher level objectives for the project.<br />

• Inclusion of specific information on scope, delivery and operational assumptions<br />

underpinning the project.<br />

• Inclusion of a section to capture Operational Costs related to the completed<br />

investment. E.g. Additional security resource. (See note 2 below.)<br />

• Inclusion of a section to capture Revenue Impact related to the completed<br />

investment. E.g. Incremental additional revenue. (See note 2 below.)<br />

• Inclusion of a section to capture User Charge Impact. (See note 3 below.)<br />

• Improved clarity on capital financial information, with;<br />

o Budgets being shown in the main body of the PDS, and<br />

o Anticipated Final Cost (AFC) information being provided in an appendix.<br />

(See note 4 below)<br />

• Key context drawings or images moved to an appendix to improve clarity.<br />

Note 1: PDS’s will not be provided for projects that are due to complete in the<br />

regulatory year preceding CIP publication. I.e. for CIP <strong>2009</strong> any projects due to complete<br />

by April <strong>2009</strong> will not have a PDS regardless of budget value.<br />

Note 2: Initial information only on these sections has been provided in CIP <strong>2009</strong>.<br />

Note 3: This is not completed in CIP <strong>2009</strong>. Refer to section 5.2.4.<br />

Note 4: The AFC information will vary. For projects starting in Q5 the AFC will be<br />

provided from “live” month end information (See section 5.2.2) based on project<br />

delivery. For projects starting in Q6 and beyond the information will be in the form of a<br />

Cost Advice Sheet from HAL’s estimating team. However for the reasons outlines in<br />

sections 2.1, 2.2, and 2.3 limited cost data for Q6 and beyond is provided in CIP <strong>2009</strong>.<br />

In respect of notes 2 and 3 above, refer to section 6.5 for HAL’s aspirations in respect of<br />

the areas where it has not been possible, for CIP <strong>2009</strong> publication, to populate the<br />

enhanced Project Definition Sheets.<br />

5.2 Financial Data<br />

5.2.1 Budget Information<br />

25<br />

CIP Working Groups held on 16 th October 2008 and 18 th December 2008.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 36


A principal objective for any CIP publication is to set out the budgets for the proposed<br />

investment activity. CIP 2008, itself based on the CAA regulatory decision for Q5, was<br />

used by HAL to prepare project specific budgets for Q5. These budgets, known as<br />

Current Control Budgets (CCB’s) are monitored on a monthly basis and can only be<br />

adjusted via the change control process. (Refer to section 5.7 for information on change<br />

control.)<br />

CIP <strong>2009</strong> is, at its most basic level, a publication of the current state of budgets for<br />

possible investments at <strong>Heathrow</strong>. Appendix Q: Cost Schedules provides the detailed<br />

listing of project budgets while Appendix C to Appendix O inclusive shows the<br />

information against each projects via the relevant PDS.<br />

In future publications of the <strong>Heathrow</strong> CIP assumed budgets for Q6 and beyond will be<br />

shown however, until the relevant regulatory processes have been completed, such as<br />

budgets will not become fixed. A number of projects that commence in Q5 will<br />

complete in Q6. While no regulatory settlement exists for Q6, and the general<br />

preparation of a Q6 and beyond capital investment plan needs to sit within the context<br />

of the issues outlined in section 2, this publication needs to show the “roll over” nature<br />

of those Q5 projects into Q6. In order to do this the element of Anticipated Final Cost<br />

(see section 5.2.2), excluding R2 and inflation for the projects that is forecast, at<br />

February <strong>2009</strong> month end, to be incurred during Q6 is shown in Appendix Q: Cost<br />

Schedules as the Current Control Budget. I.e. for projects that start in Q5 but complete<br />

in Q6 the Q6 Anticipated Final Cost has been assumed to equal the Q6 Current Control<br />

Budget. This methodology has been adopted to allow the full cost phasing of currently<br />

planned works to be shown without prejudice to future consultation and regulatory<br />

decisions on Q6.<br />

In line with the information presented in section 5.4 HAL is using CIP <strong>2009</strong> to set Q5<br />

budgets to a “real” 2008 / 09 coat base. These budgets are those that have been<br />

arrived at by;<br />

• February <strong>2009</strong> month end data,<br />

• Change Control (see section 5.7) process, and<br />

• CIP <strong>2009</strong> inflation assumptions (refer to section 5.4).<br />

For clarity the R2 risk pot is treated as a budget for a “project” called R2. Refer to<br />

section 5.7 for further information.<br />

CIP is produced in constant prices (refer to section 5.4). However, on a monthly basis<br />

HAL presents to the CIP Working Group information on budgets including on allowance<br />

for inflation. The inflation allowance is shown as a bottom line adjustment to the<br />

individual project budgets shown in the CIP, the project budgets remain in the current<br />

CIP cost base.<br />

5.2.2 Anticipated Final Cost Information<br />

The monthly reporting that HAL undertakes with the airline community, via the CIP<br />

Working Group, focuses on performance of projects against budget. That performance<br />

is measured by viewing the Anticipated Final Cost (AFC) against the CCB.<br />

The CIP, as a budgetary document, does not present AFC information for the totality of<br />

the investment, but does, from CIP <strong>2009</strong> onwards, provide project specific AFC<br />

information in the PDS documentation.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 37


5.2.3 Revenue and Operational Cost Information<br />

As outlined in section 5.1 the visibility of information on revenue and operational cost<br />

impact of projects is being improved via inclusion in PDS documentation.<br />

Such information is being provided in response to airline community feedback and to<br />

enable enhanced prioritisation of future projects on a whole business impact basis. The<br />

information provided will, at times, be approximated or based on current assumptions,<br />

and will therefore be subject to change.<br />

5.2.4 User Charge Impact<br />

The airline community has requested that HAL provide details on the potential User<br />

Charge impact of the investment plans including that arising from income and<br />

operational cost not just the capital investment. In response HAL have undertaken some<br />

changes to the CIP documentation, as outlined in sections 5.1 and 5.2, to allow<br />

consultation on this aspect of capital expenditure.<br />

HAL have provided the airline community, via the special CIPWG 26 , with some<br />

information on User Charge calculation for the whole of the CIP in Q6. This was done<br />

with the aid of a draft User Charge Calculation Tool 27 applied to the whole of Q6. Due<br />

to the complex formulae that underpin the regulatory calculations a number of<br />

assumptions had to be made in order to generate an approximate impact. It was agreed<br />

at the meeting not to publish the information and assumptions shared as part of CIP<br />

<strong>2009</strong>, but for HAL to continue to develop the tool to aid with consultation on individual<br />

projects and elements of the CIP in the future.<br />

5.3 Time Schedule Data<br />

For the first time this CIP publication will provide information on time schedule<br />

(programme) for capital investment. This information can be viewed in Appendix R:<br />

Time Schedules.<br />

As with CCB and AFC information the airline community are provided with regular<br />

updates on programme via the various constructive engagement fora and the regular<br />

IBR process.<br />

It is envisaged that, once Q6 and beyond project information can be included in the CIP,<br />

time schedule information for future quinquennia will also be included. This will allow<br />

the interdependencies between work elements to be more easily seen and ensure<br />

visibility of the assumptions and impacts on airport operations on which the whole<br />

investment plans for specific quinquennia are built.<br />

5.4 Inflation<br />

Traditionally each CIP publication has been revised to reflect “constant” prices in the<br />

year of publication. Given the current economic conditions HAL has amended this<br />

26<br />

CIP Working Group held 30 th January <strong>2009</strong>.<br />

27<br />

HAL are developing a spreadsheet based tool to aid consultation on specific projects and allow<br />

population of the User Charge Impact section of the Project Definition Sheets in future years.<br />

When this tool enters use it will be subject to a number of provisions that were shared with the<br />

airline community at the special CIPWG meetings.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 38


practice and provides below detailed information on inflation assumptions and issues as<br />

they impact the delivery of the capital investment plans at <strong>Heathrow</strong>.<br />

5.4.1 Terminology<br />

In order that information on inflation is not misunderstood HAL presents below<br />

definitions of the key terminology used.<br />

Constant = Price base is fixed regardless of the year in which investment occurs.<br />

Nominal = Outturn price. I.e. the actual cost of the investment including impact of<br />

inflation.<br />

Real = Known price base where inflation is fixed and no longer assumed.<br />

Inflation Years = Inflation is quoted from middle of regulatory year to middle of the<br />

subsequent year. E.g. Inflation from “07/08 prices” to “08/09 prices” is the year on year<br />

rate from September 2007 to September 2008. “08/09 prices” refers to values as they<br />

would have been in September 2008.<br />

5.4.2 Price Bases and Inflation Indices<br />

The Q5 regulatory decision in March 2008 was published in real 2007/08 prices. This<br />

forms the basis of all calculations for the quinquennium. CIP 2008 was published in<br />

estimated 2008/09 constant prices with values being increased by 4.23% estimated<br />

inflation from the 2007/08 real prices. CIP <strong>2009</strong> is published in real 2008/09 constant<br />

prices with budget values being increased by 5.00% (Refer to section 5.4.4) known<br />

inflation from the 2007/08 real prices. This change allows HAL to define the<br />

management of the project budgets and is explained in the CIP for utmost clarity in line<br />

with Annex G commitments.<br />

The regulatory decision includes five areas of capital expenditure, namely;<br />

• <strong>Capital</strong> Projects<br />

• IT<br />

• Rail<br />

• Thames Water, and<br />

• PSDH.<br />

However, CIP 2008 only detailed <strong>Capital</strong> Projects, IT and Rail expenditure. CIP <strong>2009</strong><br />

details all five areas of expenditure.<br />

The following tables provide a summary of the total capital investment plan for<br />

<strong>Heathrow</strong> in the three cost bases outlined. Note: These are produced with cash flow<br />

assumed to be as per regulatory decision in order to calculate “control totals” for<br />

rephrased budgets.<br />

Actual budgetary cash flow will be shown in Appendix Q: Cost Schedules.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 39


CAA Decision<br />

Cost base: 07/08 Real<br />

Year 1 Year 2 Year 3 Year 4 Year 5 Total<br />

<strong>Capital</strong> Projects 834 1004 840 641 298 3617<br />

TW 3 4 6 6 6 25<br />

Rail 28 35 33 29 26 151<br />

IT 24 23 23 21 20 111<br />

PSDH 163 80 97 123 177 640<br />

All values in £ millions.<br />

Table 16: Total CIP Values - Q5 Decision<br />

4544<br />

CIP 2008 *<br />

Cost base: 08/09 Estimated<br />

Year 1 Year 2 Year 3 Year 4 Year 5 Total<br />

<strong>Capital</strong> Projects 870 1047 876 668 311 3768<br />

TW 3 4 6 6 6 26<br />

Rail 29 36 34 30 27 157<br />

IT 25 24 24 22 21 116<br />

PSDH 170 83 101 128 185 667<br />

All values in £ millions.<br />

* TW and PSDH not included in CIP 2008 publication. Shown in this table for completeness of comparison.<br />

~ True sum of columns is £3,771, but £3768 was published. Difference is rounding error.<br />

Table 17: Total CIP Values - CIP 2008<br />

4734<br />

CIP <strong>2009</strong> *<br />

Cost base: 08/09 Final<br />

Year 1 Year 2 Year 3 Year 4 Year 5 Total<br />

<strong>Capital</strong> Projects 876 1054 882 673 313 3798<br />

TW 3 4 6 6 6 26<br />

Rail 29 37 35 30 27 159<br />

IT 25 24 24 22 21 117<br />

PSDH 171 84 102 129 186 672<br />

All values in £ millions.<br />

* Using and inflation rate of 5.00%. I.e. Inflation index of 1.05.<br />

Table 18: Total CIP Values - CIP <strong>2009</strong> (Regulatory Cash Flow)<br />

5.4.3 Inflation Rate Data and Commentary<br />

With the current economic situation, the Bank of England has stated that “the<br />

prospects for economic growth and inflation are…unusually uncertain” 28 . This context<br />

has defined HAL’s approach to the publication of CIP <strong>2009</strong> in real 08/09 constant prices.<br />

5.4.4 Selection of Construction Inflation Rate 2007/08 to 2008/09<br />

4771<br />

28<br />

Bank of England Inflation Report, November 2008.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 40


In order to publish CIP <strong>2009</strong> HAL has had to select an inflation index from the 2007/08<br />

real price base in the Q5 regulatory decision.<br />

Within the regulatory arrangements a construction inflation assumption of “RPI + 2%”<br />

exists. Depending on the source data and method of calculation used RPI for the period<br />

suggests a construction inflation rate in the order of 5 to 7%.<br />

Following consideration of the various construction inflation indices, including the<br />

RPI+2% methodology, HAL has selected an inflation rate for regulatory year 2007/08 to<br />

2008/09 of 5.00%.<br />

This has been used to create the real cost base for CIP <strong>2009</strong> described in Table 18.<br />

5.4.5 Construction Inflation Outlook and Resultant Action<br />

Comparison of the available forecast construction inflation rates for regulatory year<br />

<strong>2009</strong>/10 and beyond is complicated by the uncertainty of the general economic climate.<br />

A number of assessments reflect the general perception of reduced economic activity<br />

impacting on inflation. The assessment of the magnitude of the possible impact varies<br />

considerably.<br />

Other reports suggest that the market in which HAL invests will not be impacted to such<br />

an extent. One report 29<br />

suggests that the “Olympic effect” on Greater London<br />

construction will no longer be inflationary but will sustain a general level of demand and<br />

mitigate against falls.<br />

With HAL’s investment plans being of a general infrastructure nature (as distinct from<br />

sectors such as schools, or house building), Cyril Sweett’s 30<br />

commentary on the<br />

construction market outlook broken down into sectors is of interest. The table below<br />

shows a possible divergence between the outlook for the infrastructure sector and the<br />

wider construction industry as a whole.<br />

2007* 2008 <strong>2009</strong> 2010 2011<br />

Infrastructure<br />

Sector<br />

<br />

Total New<br />

Work<br />

<br />

* 2007 is based on UK Statistics Authority information.<br />

Table 19: Construction Market Outlook 31<br />

For the reasons outlined above HAL has selected;<br />

1. To fix inflation to nominal outturn prices on non-<strong>Capital</strong> Projects investments (I.e.<br />

Thames Water, Rail, IT and PSDH) at 0% for years 2-4 of Q5, and<br />

2. Not to amend the current inflation allowance for <strong>Capital</strong> Projects, of £231m, being<br />

used in monthly outturn reporting.<br />

3. To prevent any drawdown of the inflation allowance.<br />

The decisions do not directly impact CIP <strong>2009</strong> data or schedules, as they relate to AFC,<br />

but are recorded here for clarity of HAL’s management approach to inflation at the time<br />

of publication.<br />

29<br />

Economic and Regional Inflation Report 4 th Quarter 2008, Gleeds.<br />

30<br />

A construction industry cost consultancy firm.<br />

31<br />

Extracted from Cyril Sweet’s Q4 2008 Quarterly Review<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 41


5.5 Control Totals<br />

On the basis of the information detailed in section 5.4 the various control totals for Q5<br />

that will be monitored against are;<br />

<strong>Investment</strong><br />

Area<br />

Current Control Budget<br />

in 2008/09 real constant<br />

prices<br />

(CIP <strong>2009</strong> Information)<br />

Current Control Budget<br />

in nominal outturn<br />

prices<br />

(Monthly Reporting Information)<br />

<strong>Capital</strong> Projects 3778 4009<br />

Thames Water 26 26<br />

Rail 159 159<br />

IT 137 137<br />

PSDH 672 672<br />

Totals: 4772 5003<br />

Note: The difference between £4,772m quoted above and £4,771m quoted in Table 18 is due to rounding)<br />

Table 20: Control Totals<br />

In order to enact the control total changes to the CCB within HAL’s project<br />

management systems a number of change control documents will be prepared, under<br />

the process outlined in section 5.7, after CIP <strong>2009</strong> publication.<br />

5.6 Risk<br />

In October / November 2008 HAL undertook an exercise to remove a portion of risk<br />

money from each project and centralise the funds. This has created two “pots” of risk<br />

monies;<br />

• R1 = Held inside each project, and<br />

• R2 = Held centrally, but with each project’s element of the “pot” recorded.<br />

R1 funds can be used by the project team without further reference to HAL governance<br />

or airline approval, but R2 funds will only be returned to a project upon application via<br />

the CCRS process. In total approximately 50% of risk allowances have been centralised<br />

into the R2 “pot” and it has been discussed with the airline community that any<br />

drawdown from the central risk allowance would require consultation via the CCRS<br />

process. (See section 6.1.1.4 for details on consultation). While the R1 : R2 split in total<br />

is 50% this has not been the methodology applied to each project. In carrying out the<br />

risk separation exercise HAL considered the DGS / IGS 32 project stage and the nature of<br />

the project before deciding on that projects R1 : R2 split.<br />

The airline community asked that a number of points be recorded on the subject of risk,<br />

namely;<br />

• They support the R1 / R2 exercise and principles behind it.<br />

• They wish to understand more detail on how the sums were apportioned.<br />

• They have a concern about the split between R1 and R2 and feel that the “R2 pot”<br />

should be the larger of the two.<br />

• They do not wish a principle of a 50:50 split to be entered into Q6 and beyond.<br />

(Note: HAL refers to the methodology applied above.)<br />

• They, and HAL, recognise that there is a terminology debate that needs to occur to<br />

ensure a methodology for “risk” for Q6 and beyond can be developed and agreed.<br />

32<br />

See also footnote 40.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 42


5.7 Change Control<br />

A new client change control process has been introduced for Q5, which supports the<br />

consultation requirements of Annex G.<br />

Under the process airlines are invited to raise requests for changes via Issue Request<br />

Forms (IRF’s) available from BAA project teams. Consultation on proposed and<br />

confirmed changes takes place at Stakeholder Programme Boards where records of<br />

airlines’ agreement / disagreement with change proposals are entered on the formal<br />

change records - Change Control Record Sheet (CCRS).<br />

Details of all changes (IRF’s and CCRS’s) are summarised in a Client Change Register and<br />

shared with airlines each month via Stakeholder Programme Boards and the CIP<br />

Working Group.<br />

The high level process map is provided below in figure 6.<br />

As a result of the change process Appendix P: Tracker CIP 2008 to CIP <strong>2009</strong> does not<br />

included financial information shifts. The detail of all budget and scope changes being<br />

contained within the CCRS’s raised and consulted upon. High level cost shift<br />

information due to inflation is detailed in section 5.4.<br />

A dashboard of CCRS closedown performance has been developed by HAL to enable<br />

the SPB’s and CIP Working Group to monitor the efficiency of the process by<br />

programme. A proposed dashboard has been presented to the CIP Working Group 33<br />

and format agreed for implementation.<br />

The data in Figure 6 shows that, as at January <strong>2009</strong> month end, of the 335 CCRS’s<br />

raised;<br />

• 96 were pending,<br />

• 102 were approved,<br />

• 137 were complete (airline community in agreement with change), and<br />

• 0 were complete (airline community in disagreement with change).<br />

33<br />

CIP Working Group Meeting held 19 th February <strong>2009</strong>.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 43


BAA<br />

STAKEHOLDER<br />

IDENTIFIES NEED<br />

FOR CHANGE<br />

AIRLINE<br />

IDENTIFIES NEED<br />

FOR CHANGE<br />

BAA PROJECT TEAM<br />

IDENTIFIES ISSUE THAT<br />

COULD LEAD TO CHANGE<br />

ISSUE<br />

REQUEST<br />

FORM<br />

Raised by:<br />

- BAA Project Team or<br />

- stakeholder<br />

INITIAL ASSESSMENT<br />

(AND STUDY)<br />

CONSULTATION<br />

BAA PROJECT<br />

TEAM IDENTIFIES<br />

DEFINED NEED<br />

FOR CHANGE<br />

GO<br />

NO-GO?<br />

No<br />

STOP<br />

Go<br />

SOLUTION<br />

DEVELOPMENT<br />

RECORD SHEET<br />

Raised by BAA project Team<br />

Includes detailed impact assessment<br />

CHANGE<br />

CONTROL<br />

RECORD SHEET<br />

Raised by:<br />

- BAA Project Team<br />

GOVERNANCE<br />

CONSULTATION<br />

IMPLEMENT<br />

CHANGE<br />

Figure 5: Client Change Control Process<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 44


Figure 6: CCRS Dashboard.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 45


6 Constructive Engagement<br />

6.1 Q5 Delivery of Annex G Commitments<br />

6.1.1 Main <strong>Capital</strong> Works including Stakeholder Programme Boards<br />

6.1.1.1 Stakeholder Programme Boards<br />

Stakeholder Programme Boards (SPB’s) have been established and are operating in all<br />

programmes with meeting dates planned for <strong>2009</strong>. Sub groups are operating to<br />

manage the detail of consultation at a project level. The airline community asked that<br />

comment be made as follows; The degree of efficiency to which the various SPB’s are<br />

working varies by terminal / programme. All of the boards have developed / are<br />

continuing to develop in their efficiency, with some needing to progress still further to<br />

reach a common standard.<br />

Consultation calendars, which set out the programme for <strong>2009</strong> have been developed<br />

and have been circulated. Formal project performance reporting and change control are<br />

now being built into the standard agenda.<br />

6.1.1.2 Consultation at Gateways<br />

Gateway consultation events have begun for significant projects. A consistent model is<br />

required to provide clarity for airline and programme teams on what to expect from a<br />

gateway event at each of the three project stages (Brief, Options and Construction 34 ). It<br />

is intended that this will be rolled out in the second quarter of <strong>2009</strong>.<br />

It is jointly recognised that applying a full gateway review to all Q5 projects is not viable<br />

from an airline resource perspective and is not appropriate for all projects. The<br />

consultation calendars are now being used at the SPBs as a basis of agreeing which<br />

projects are to be taken through a full gateway review. It is intended that all projects<br />

will be subject to consultation through either a gateway event or at the SPB. Details of<br />

the gateway approval dates for <strong>2009</strong> have been circulated to the airline community.<br />

6.1.1.3 Change Control<br />

A Change Control process (known as the CCRS process) has been agreed and<br />

implemented. The process is built around the principle of consultation at the earliest<br />

stage possible As the process is evolving, airline feedback is that the quality and timing<br />

of consultation within this process has improved significantly. The status of outstanding<br />

change issues is reviewed and reported regularly. A pan airport view is provided to the<br />

CIP Working Group.<br />

It has been recognised that consulting on change effectively with large airline groups is<br />

challenging and Airline Leads have been appointed for each SPB. There are agreed<br />

terms of reference for this role and the SPBs retain visibility of all significant change<br />

issues.<br />

6.1.1.4 Consultation on Risk Allowances<br />

34<br />

See also footnote 40.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 46


As a result of the process outlined in section 5.6, a process for consultation on<br />

significant use of R2 risk monies is being developed and will be presented to the CIP<br />

Working Group for validation. The base assumption is that projects will only be able to<br />

request their element of the R2 “pot”.<br />

6.1.2 Rail<br />

This CIP publication, for the first time, expands the investments in rail out into greater<br />

detail. In previous years rail has been covered as single line in the cost schedule<br />

described as “BAA Rail”, with some clarification provided in the project sheets. This year<br />

the same value of investment will be listed over half a dozen project elements reflecting<br />

both airline engagement on key products, such as Crossrail and Airtrack, but also<br />

enhancing visibility of the <strong>Heathrow</strong> Express general investment plans.<br />

In this year’s publication reference is not made to an investment in high speed rail<br />

proposals being developed by third parties. This investment (order of magnitude £5m in<br />

<strong>2009</strong>/10) was consulted upon at the JST 35 where it was agreed to fund this from PSDH<br />

monies. Pending resolution of the PSDH issues, as outlined in the relevant PDS and<br />

Appendix A: Project for the Sustainable Development of <strong>Heathrow</strong>, this is excluded,<br />

however HAL still wishes to undertake this investment and shall change control the<br />

scope in due course. The airline community wished to record that, while the above<br />

endorsement was correct, they were not setting a principle of agreement that large<br />

scale rail development associated with PSDH should be funded by the airlines and / or<br />

via the current RAB arrangements.<br />

At the January JST 36 HAL consulted upon, and received airline agreement to, investment<br />

to support the upgrade of the <strong>Heathrow</strong> Connect rail service to four trains per hour.<br />

6.1.3 Information Technology (IT) / Systems<br />

This CIP publication, for the first time expands the investments in IT / Systems into<br />

greater detail. In previous years IT/Systems has been covered through three headings;<br />

• BAA IT (A single line not defined in any further detail)<br />

• Specific major IT investments (One or two lines detailing any major works. E.g.:<br />

Network Upgrade.)<br />

• IT content within main capital projects (not listed against IT, but content detailed on<br />

Cost Advice sheets for projects with an IT/Systems element.)<br />

This year the same scope covered by the first bullet will be detailed over three separate<br />

projects.<br />

In support of Annex G commitments, HAL commenced discussions with the airline<br />

community to establish a Stakeholder Programme Board for IT. Reflective of the nature<br />

of IT investments HAL have invited the Chief Information Officers of British Airways,<br />

Virgin Atlantic, Emirates, bmi and KLM together with the three airline alliances to<br />

nominate themselves or another senior IT specialist to attend the SPB. In addition the<br />

AOC 37 have confirmed they will provide a representative to the group. The first meeting<br />

was held during March <strong>2009</strong>. HAL envisages that this SPB, as with the others, will need<br />

some time to evolve.<br />

35<br />

Joint Steering Team Meeting held 8 th December 2008<br />

36<br />

Joint Steering Team Meeting held 13 th January <strong>2009</strong><br />

37<br />

<strong>Heathrow</strong> Airline Operations Committee<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 47


6.1.4 Project for the Sustainable Development of <strong>Heathrow</strong> (PSDH)<br />

In the March 2008 decision 38 on Q5 the CAA included monies for the progression of the<br />

PSDH workstreams. These monies were not detailed in the CIP 2008 publication.<br />

Consultation on PSDH workstreams is being undertaken via a PSDH working group.<br />

Consultation on the use of the PSDH monies has agreed use of funds to safeguard for a<br />

T2C satellite building in the development, during Q5, of the T2B satellite. Reference<br />

should be made to section 3.8 and Appendix A: Project for the Sustainable<br />

Development of <strong>Heathrow</strong>.<br />

6.1.5 CIP Working Group<br />

In addition to the Stakeholder Programme Boards, HAL consults with the airline<br />

community and the overall delivery and development of the CIP through a monthly CIP<br />

Working Group. These meetings review the high level progress of Q5 delivery together<br />

with monitoring of capital efficiency, Annex G compliance and overreaching financial<br />

issues for current and future quinquennia. In preparation for the publication of CIP <strong>2009</strong><br />

a series of special CIPWG meetings were convened to allow consultation on this<br />

document. As a result numerous sections of this document have been enhanced by<br />

airline community comments and some elements specifically make reference to airline<br />

provided or requested input.<br />

At recent CIPWG meetings the airline community has requested, and HAL has agreed<br />

to, commencing an audit of certain specific projects in respect of capital efficiency,<br />

consultation and scope changes. HAL has undertaken to start this process by provision<br />

of a “pack” of information for airline community review.<br />

6.1.6 Constructive Engagement Fora for <strong>Capital</strong> <strong>Investment</strong><br />

At the request of the airline community the following diagram of constructive<br />

engagement fora has been included to provide clarity.<br />

Joint<br />

Steering<br />

Team<br />

Stakeholder<br />

Stakeholder<br />

Stakeholder Programme<br />

Programme<br />

Programme Boards<br />

Boards<br />

Boards<br />

Airline<br />

Relocations<br />

Working Group<br />

Strategic<br />

Choices<br />

CIP<br />

Working<br />

Group<br />

PSDH<br />

Working<br />

Group<br />

Stakeholder<br />

Stakeholder<br />

Project Programme<br />

Programme<br />

Working Boards<br />

Boards<br />

Groups<br />

Figure 7: Constructive Engagement Fora<br />

38<br />

Economic Regulation of <strong>Heathrow</strong> and Gatwick <strong>Airport</strong>s 2008 – 2013, CAA Decision, 11 th<br />

March 2008.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 48


6.2 Discussions on Future Developments (Q6 and beyond)<br />

HAL are committed to ongoing consultation with the airline community on the<br />

development of the <strong>Capital</strong> <strong>Investment</strong> <strong>Plan</strong> and Masterplan for <strong>Heathrow</strong> under the<br />

provisions of the Annex G commitments. The aim, as introduced in section 2.3, is to<br />

jointly develop investment plans for Q6 and beyond that have a high level of confidence<br />

in respect of; scope, cost, and schedule, by the time CIP 2011 is published.<br />

In order to help achieve this a number of ongoing consultative working groups are<br />

being held with the airlines. These groups feed information for decision into the<br />

Strategic Choices meetings.<br />

6.3 CIP Development Process<br />

During the last quarter of 2008 HAL has undertaken work to define the new process for<br />

the compilation and maintenance of the CIP.<br />

The process agreed with the airline community at the JST 39<br />

recognises formally that a<br />

project will go through three distinct stages;<br />

a) Identification of strategic aspirations (which will generally be done for a business<br />

or geographical area such as Cargo or Western Apron.) This stage will not be<br />

shown in the CIP appendices.<br />

b) Development of strategic solutions for projects that individually or collectively<br />

meet the aspirations.<br />

c) Detailed delivery of the projects through the DGS / IGS 40 process.<br />

The status of the projects during the middle stage above will be subdivided into;<br />

• Pre-Outline<br />

• Outline, and<br />

• Developed<br />

The appropriate one of these classifications, or the relevant DGS / IGS stage, is shown<br />

on the Project Definition Sheets in the appendices.<br />

A further element of the new process is the Airline Engagement Status Marker which<br />

also recorded on the Project Definition Sheets. Further information on the marker is<br />

given in section 6.4 below.<br />

6.4 Airline Engagement Status Marker<br />

A key element of the new process for the development of the CIP is the inclusion of a<br />

snapshot marker of airline community engagement with particular projects.<br />

Figure 8: Airline Engagement Marker shows how this classification (Red, Amber or<br />

Green) is determined between BAA and the Airline Community. The methodology<br />

outlined below was agreed at the CIPWG 41 .<br />

39<br />

Joint Steering Team held 8 th December 2008<br />

40<br />

The Design Great Solutions (DGS) / Implement Great Solutions (IGS) process is the standard<br />

project delivery methodology adopted by HAL, and in particular the <strong>Capital</strong> and Solutions<br />

directorate. The key aspect of the process, from an airline community and consultation<br />

perspective, is the use of decision gateways known as; Brief Decision, Options Decision and<br />

Construction Decision.<br />

41<br />

CIP Working Group held 18 th December 2008.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 49


The status of each project is shown on the relevant Project Definition Sheets.<br />

Excellent Involvement<br />

Green<br />

Amber<br />

Good<br />

Significant<br />

Strong<br />

Disagreement<br />

Strong<br />

Agreement<br />

Significant<br />

Red<br />

Poor<br />

Very Poor Involvement<br />

Figure 8: Airline Engagement Marker<br />

BAA have allocated the status markers. On any occasion where the marker is not agreed<br />

with the airline community this would be stated in the “Areas of Disagreement” section<br />

of the relevant Project Definition Sheet. At the time of CIP <strong>2009</strong> publication no status<br />

makers are contested 42 .<br />

It should be noted that, in general, possible projects for Q6 have been allocated a “red”<br />

status. HAL have done this recognising that, for this edition of CIP, such individual<br />

possible projects have, to date, not been consulted upon for the reasons outlined<br />

throughout this document. Therefore HAL has stated that these projects have had<br />

below “poor” level of airline involvement, which is not strictly the case as the airline<br />

community have agreed to the manner in which Q6 and beyond have been presented in<br />

this document. No assessment of airline support has been included in these future<br />

projects. This decision on status markers was made in the light of the issues regarding<br />

Q6 and beyond detailed expansively in this document and specifically in section 2. Such<br />

“red” status reflects HAL’s desire to be open about the status of consultation and<br />

agreement.<br />

42<br />

The majority of PDS documents were shared with the CIPWG during the consultation leading<br />

up to CIP <strong>2009</strong> publication. A number were however completed post that consultation. Should<br />

the status of any of these later PDS sheets be contested HAL shall record this fact in the CIPWG<br />

minutes.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 50


6.5 Aspirations for Future CIP Publications<br />

As outlined throughout this document the content of this CIP publication has been<br />

changed significantly from earlier editions. This reflects HAL’s desire to ensure that the<br />

document provides a true “snapshot” of the investment programme and related issues.<br />

The framework for future editions of the CIP put in place by this document and the<br />

processes detailed within it reflects HAL’s aspirations to progress the level of<br />

consultation (in alignment with Annex G commitments) on its investment plans. Future<br />

editions should therefore start to include, amongst other elements, more populated<br />

Project Definition Sheets, together with cost and time information for Q6 and beyond.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 51


Index of Tables and Figures<br />

Table 1: Extract of Table 4-5 CAA Forecast Passenger Numbers. From CAA Decision. ... 5<br />

Table 2: Possible Q6 and Q7 Projects – Eastern Campus Programme........................... 16<br />

Table 3: Possible Q6 and Q7 Projects – Western Campus Programme ......................... 17<br />

Table 4: Possible Q6 and Q7 Projects – Infrastructure Programme ............................... 18<br />

Table 5: Possible Q6 and Q7 Projects – IT / Systems Programme.................................. 18<br />

Table 6: Q5 Projects – Eastern Campus Programme .................................................... 19<br />

Table 7: Q5 Projects – Western Campus Programme................................................... 21<br />

Table 8: Q5 Projects – Baggage Programme................................................................ 21<br />

Table 9: Q5 Projects – Infrastructure Programme ........................................................ 22<br />

Table 10: Q5 Projects – Airline Relocations Programme............................................... 23<br />

Table 11: Q5 Projects – IT / Systems Programme ......................................................... 24<br />

Table 12: Q5 Projects – Rail Programme...................................................................... 24<br />

Table 13: Q5 Projects – PSDH ..................................................................................... 25<br />

Table 14: Q5 Projects – Thames Water........................................................................ 26<br />

Table 15: DfT Timetable.............................................................................................. 30<br />

Table 16: Total CIP Values - Q5 Decision..................................................................... 40<br />

Table 17: Total CIP Values - CIP 2008 ......................................................................... 40<br />

Table 18: Total CIP Values - CIP <strong>2009</strong> (Regulatory Cash Flow) ..................................... 40<br />

Table 19: Construction Market Outlook...................................................................... 41<br />

Table 20: Control Totals ............................................................................................. 42<br />

Figure 1: Schematic of Possible Passenger Processing and Apron Capacities for<br />

<strong>Heathrow</strong> in 2030................................................................................................. 8<br />

Figure 2: High level <strong>Plan</strong> of <strong>Heathrow</strong> Campus at March 2013...................................... 9<br />

Figure 3: Q6 and beyond consultation framework ...................................................... 10<br />

Figure 4: Airline Relocations Move Sequence 3.1 ........................................................ 23<br />

Figure 5: Client Change Control Process ..................................................................... 44<br />

Figure 6: CCRS Dashboard.......................................................................................... 45<br />

Figure 7: Constructive Engagement Fora..................................................................... 48<br />

Figure 8: Airline Engagement Marker.......................................................................... 50<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 52


Appendices<br />

Appendix A: Project for the Sustainable Development of <strong>Heathrow</strong> .............................. 1<br />

Appendix B: Trigger Change Control .......................................................................... 10<br />

Appendix C: PDS – Q5 Eastern Campus ...................................................................... 12<br />

Appendix D: PDS – Q5 Western Campus .................................................................... 77<br />

Appendix E: PDS – Q5 Baggage ................................................................................ 150<br />

Appendix F: PDS – Q5 Infrastructure ......................................................................... 183<br />

Appendix G: PDS – Q5 Airline Relocations ................................................................ 272<br />

Appendix H: PDS – Q5 IT / Systems ........................................................................... 280<br />

Appendix I: PDS – Q5 Rail......................................................................................... 291<br />

Appendix J: PDS – Q5 PSDH, Thames Water and Support Adjustments ..................... 302<br />

Appendix K: PDS – Eastern Campus Phase 2 Enabling............................................... 309<br />

Appendix L: PDS – Q6 and Beyond Eastern Campus.................................................. 315<br />

Appendix M: PDS – Q6 and Beyond Western Campus .............................................. 327<br />

Appendix N: PDS – Q6 and Beyond Infrastructure ..................................................... 381<br />

Appendix O: PDS – Q6 and Beyond Rail .................................................................... 420<br />

Appendix P: Tracker CIP 2008 to CIP <strong>2009</strong> ............................................................... 428<br />

Appendix Q: Cost Schedules..................................................................................... 439<br />

Appendix R: Time Schedules..................................................................................... 446<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 53


Appendix A: Project for the Sustainable Development of <strong>Heathrow</strong><br />

Project for the Sustainable Development of <strong>Heathrow</strong> (PSDH)<br />

This appendix outlines the history and current position with regard to PSDH into the<br />

following sections;<br />

1. Government Aviation and <strong>Airport</strong> Policy<br />

2. HAL’s Current Proposals<br />

3. Recent Developments<br />

1. Government Aviation and <strong>Airport</strong> Policy<br />

a. The Future of Aviation, December 2003<br />

In December 2003 following an extensive exercise considering all options and a long<br />

period of consultation, The Department for Transport produced a White paper on Air<br />

transport (The Future of Aviation). The White Paper reached several key conclusions in<br />

relation to runway capacity in the South East.<br />

The first conclusion was that there was an urgent need for additional runway capacity in<br />

the South East. It also explained that a lack of capacity would significantly damage<br />

national prosperity. It stated that there was no case for a second international hub<br />

within the South East.<br />

In relation to where further capacity should be developed it concluded that the first<br />

priority is to make best use of the existing runways, including Stansted and Luton. It<br />

went on to conclude that provision should be made for two new runways in the South<br />

East by 2030. The first new runway should be at Stansted, to be delivered as soon as<br />

possible (around 2011 or 2012).<br />

In relation to the location of a second new runway the conclusions were less well<br />

formulated. The White paper stated that the further development of <strong>Heathrow</strong> is<br />

supported, including a further new runway and additional terminal capacity to be<br />

delivered as soon as possible (within the 2015 -2020 period) after the new runway at<br />

Stansted, but only if stringent environmental limits can be met. The White paper<br />

announced the start of a further period of study to answer the question of whether<br />

such environmental limits could be met at <strong>Heathrow</strong> were mixed mode or a third<br />

runway to be introduced. This Department for Transport led study became known as<br />

the Project for the Sustainable Development of <strong>Heathrow</strong> (PSDH).<br />

As well as outlining policy in relation to runway development the White Paper included<br />

a number of further obligations which it expected airport operators to comply with.<br />

These included:<br />

• requirements to produce master plans covering thirty years;<br />

• new noise compensation schemes and a requirement to introduce schemes to<br />

address generalised blight where new runways were proposed; and<br />

• a requirement for airport charges to include an air quality element.<br />

b. The Future of Aviation Progress Report, December 2006<br />

The Department for Transport launched an Air Transport White Paper Progress Report in<br />

December 2006. This reviewed the 2003 policy in light of a number of recent issues and<br />

reported on progress against the actions set out in 2003.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 1


The 2006 Progress Report specifically took account of the following:<br />

• The Stern Review of the Economics of Climate Change, 2006;<br />

• Oxford Economic Forecasting – The Economic Contribution of the Aviation Industry<br />

in the UK, 2006;<br />

• Department for Transport Focus on Freight 2006;<br />

• Climate Change: The UK Programme 2006;<br />

• The Eddington Transport Study, 2006;<br />

• The Civil Aviation Act 2006.<br />

The 2006 Progress Report clearly and unequivocally reaffirmed the Government’s<br />

commitment to a strategy of striking the right balance between economic, social and<br />

environmental goals. It again stressed the economic benefits of air travel and stated the<br />

importance of aviation to the UK economy was rising as a result of broader economic<br />

trends. It also described people’s aspirations and attitudes to flying.<br />

It reiterated that the first priority remains making the most of the UK’s existing airports.<br />

It continued to support the development of two new runways in the South East, the first<br />

at Stansted and the second at <strong>Heathrow</strong>, subject to environmental constraints.<br />

It explained that work was continuing on establishing how environmental limits could<br />

be met both for mixed mode and runway 3 during 2007, after which there will be a<br />

public consultation.<br />

It also introduced further environmental obligations on airport operators:<br />

• Recommendation that airports become carbon neutral;<br />

• Produce an environmental statement with master plans;<br />

• Industry reporting on Sustainable Aviation Strategy targets;<br />

• Emissions cost assessment methodology consultation;<br />

• New noise maps and noise action plans;<br />

• <strong>Airport</strong> Consultative Committees to monitor implementation of new Civil Aviation<br />

Act powers by airports;<br />

• Best practice communication for environmental information;<br />

• Public Safety Zone (PSZ) review.<br />

c. Adding Capacity at <strong>Heathrow</strong>: Decisions Following Consultation, January <strong>2009</strong><br />

On 15 January <strong>2009</strong> the Secretary of State for Transport announced to Parliament his<br />

policy decisions on the future development of <strong>Heathrow</strong> airport, following the Adding<br />

Capacity at <strong>Heathrow</strong> <strong>Airport</strong> consultation which closed in February 2008 and the<br />

subsequent consultation on an Equalities Impact Assessment which closed in November<br />

2008.<br />

In summary, the Secretary of State –<br />

• confirms policy support for adding a third runway at <strong>Heathrow</strong> with additional<br />

passenger terminal facilities and a slightly longer runway (2,200m operational<br />

length), but subject to an aggregate limit of 605,000 annual movements, which<br />

would be subject to review in 2020;<br />

• does not support the introduction of mixed mode on the existing runways as an<br />

interim measure before a third runway;<br />

• confirms his intention to end the ‘Cranford agreement’ (which currently limits<br />

easterly departures off the northern runway);<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 2


• confirms his view that the following operating practices should be retained and<br />

continued:<br />

• ‘westerly preference’ (the preferred direction of operation of the runways except in<br />

strong contrary winds);<br />

• ‘night-time rotation’ (the practice of alternating the use of the existing runways at<br />

night between westerly and easterly preference, subject to weather conditions);<br />

• ‘early morning alternation’ (the practice of alternating arriving aircraft between the<br />

two runways in the 0600 to 0700 period, subject to operational requirements).<br />

• intends that additional capacity at the airport should, following consultation, be<br />

subject to a new ‘green slot’ approach, to incentivise the use at <strong>Heathrow</strong> of the<br />

most modern aircraft, with further benefits for air quality and noise.<br />

• requests that the airport operator, in reviewing its existing insulation and mitigation<br />

schemes, considers extending its noise insulation schemes to all community<br />

buildings and households in the new 57dBA contour who will experience an<br />

increase in noise of 3dBA or more; and to give particular consideration to addressing<br />

the impacts on those households who find themselves located closest to the new<br />

airport boundary.<br />

The Secretary of State has also encouraged BAA to work with NATS, the Civil Aviation<br />

Authority and airlines to improve existing airport and airspace procedures and to<br />

develop new ones to deal with delays quickly and efficiently as they develop. The results<br />

of work commissioned by the Secretary of State’s predecessor from the Civil Aviation<br />

Authority on ‘runway resilience’ should help to inform this process.<br />

Separately, the Secretary of State also announced that the Department will work with<br />

BAA and Network Rail to consider schemes that provide better connections to the Great<br />

Western main line whilst maximising the effectiveness of scarce railway paths. The<br />

Department has also set up a new company, High Speed Two (HS2) Ltd, to advise<br />

Ministers on the feasibility and credibility of plans for a new line with specific route<br />

options and financing proposals. This work will include consideration of options for a<br />

new <strong>Heathrow</strong> International interchange station on the Great Western line, providing a<br />

direct 4-way interchange between the airport, the new north-south line, existing Great<br />

Western rail services and Crossrail into central London.<br />

2. HAL’s Current Proposals<br />

In addition to the PDS information provided in Appendix J: PDS – Q5 PSDH, the current<br />

status of HAL’s proposals as consulted upon with the airline community is best<br />

encapsulated in the presentations to;<br />

• the LACC in February <strong>2009</strong>, and<br />

• the Strategic Choices in March <strong>2009</strong>.<br />

a. LACC Presentation<br />

The following slides were presented on 5 th February <strong>2009</strong>.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 3


Agenda<br />

• Summary of Government decision<br />

• Implications of the decision<br />

• High level programme and planning process<br />

• Activities over the next quarter of <strong>2009</strong><br />

www.heathrowairport.com/futuregrowth<br />

Summary of Government decision<br />

• Confirms Government policy support for a third runway and<br />

sixth terminal at <strong>Heathrow</strong> ;<br />

• The policy is subject to an initial limit of 605,000 ATMs,<br />

compared to 480,000 ATMs today. These limits may be revised<br />

upwards following a review in 2020 ;<br />

• This will allow the airport to grow from just under 70 mppa<br />

today to around 115 mppa;<br />

• Does not support the introduction of “mixed mode” as an<br />

interim measure before a third runway;<br />

• Confirms the intention to end the ‘Cranford agreement’<br />

(currently restricting easterly departures from 09L) ;<br />

• Confirms the view that a series of environmental operating<br />

practices on how the runways are used today should be<br />

continued ;<br />

• Proposes significant development of heavy rail proposals to<br />

provide better links with <strong>Heathrow</strong>, as well as improvements to<br />

the national rail network.<br />

www.heathrowairport.com/futuregrowth<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 4


Implications of the decision<br />

• BAA intends to press ahead to delivery of R3 and T6 within the time frame set by Government ;<br />

• Some ten areas of work have been identified including refining the airport development proposals and<br />

working with the relevant agencies (HA, DfT, etc) on road and rail improvements ;<br />

• Work on the business case will be led by the Chief Financial Officer ;<br />

• R3 / T6 enjoys solid support from the airline industry and the business community and BAA will<br />

continue to strengthen links with supporters ;<br />

• BAA will seek to address the concerns of local people and to act in a responsible way. With this in<br />

mind we propose to launch the first of two schemes to buy on a voluntary basis the residential<br />

property that is located on the site of the R3 / T6 ;<br />

• In line with the new policy, and in advance of R3, we will take steps to improve the operational<br />

resilience of <strong>Heathrow</strong>’s existing runways and reduce delays. Several measures have already been<br />

identified and the ending of the Cranford agreement provides new opportunities ;<br />

• We have the support of the airlines and the CAA to meet the cost of this work during the present<br />

regulatory period (Q5). Expenditure beyond that will need further regulatory support, as will any BAA<br />

contributions to road and rail costs ;<br />

• A material risk to the project is the present attitude of the main opposition party but we intend to work<br />

on this as part of our stakeholder management programme.<br />

www.heathrowairport.com/futuregrowth<br />

High Level Programme<br />

Q5 Q6 Q7 Q8<br />

• Government Policy Decision<br />

• Optioneering/Prepare application<br />

• Application for Development Consent<br />

• Examination of application and<br />

decision<br />

• Detailed approvals / possession<br />

<strong>2009</strong><br />

<strong>2009</strong>/10<br />

2010<br />

2012<br />

2014<br />

• Construction<br />

• Phase 1 operational<br />

2017/18<br />

• Phased delivery of further capacity<br />

beyond 2020,<br />

dependent upon environmental limits<br />

2020 ---------> 2028<br />

www.heathrowairport.com/futuregrowth<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 5


Activities over the next quarter<br />

FEB<br />

<strong>2009</strong><br />

MAR APR MAY<br />

• Forecasting and schedules<br />

- Procure consultant support<br />

- Begin forecast & schedule development<br />

• Surface access<br />

- Procure consultant support<br />

- Methodology review<br />

- Data collection, surveys, modelling review<br />

• Master plan concept development<br />

- Procure consultant support<br />

- Refresh of options (BAA / IATA)<br />

- Establish assessment criteria<br />

- Appoint Architects & Environmental<br />

• Programme office<br />

- Procure consultant support<br />

- Commission cost planning, programme,<br />

governance<br />

www.heathrowairport.com/futuregrowth<br />

Masterplan Development Process<br />

Initial Option Development<br />

Final Option Development<br />

EIA & <strong>Plan</strong>ning<br />

Application Preparation<br />

Business Case<br />

Business Case<br />

Business Case<br />

Airspace Change Programme<br />

Airspace Change Programme<br />

Airspace Change Programme<br />

Surface Access Strategy<br />

Surface Access Strategy<br />

Surface Access Strategy<br />

Environmental Impact Measurement & Mitigation<br />

Environmental Impact Measurement & Mitigation<br />

Environment Impact Assessment<br />

Masterplanning work stream<br />

prepare forecasts<br />

Identify scenarios<br />

initial option<br />

development<br />

initial option<br />

evaluation<br />

consultation<br />

final option<br />

development<br />

final option<br />

evaluation<br />

masterplan<br />

selection<br />

scheme<br />

announcement<br />

final scheme<br />

development<br />

Verify previous<br />

PSDH<br />

option development<br />

prepare planning application<br />

submit<br />

planning<br />

application<br />

www.heathrowairport.com/futuregrowth<br />

b. Strategic Choices Presentation<br />

The following are slides extracted from the presentation that are relevant to the<br />

consultation and delivery of PSDH.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 6


Purpose of this discussion<br />

To prompt some thinking about how we will work together on R3/T6?<br />

To understand airline perspective on where we are on the consultation<br />

journey.<br />

To explore the process for developing a top down masterplan<br />

R3 Workstreams<br />

Forecasting – demand<br />

Masterplanning and design<br />

Surface Access<br />

Legal<br />

Stakeholder engagement and communication<br />

Programme Office and Business case<br />

Land acquisition and compensation<br />

Airspace<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 7


Summary of Government decision<br />

• Confirms Government policy support for a third runway and<br />

sixth terminal at <strong>Heathrow</strong> ;<br />

• The policy is subject to an initial limit of 605,000 ATMs,<br />

compared to 480,000 ATMs today. These limits may be revised<br />

upwards following a review in 2020 ;<br />

• This will allow the airport to grow from just under 70 mppa<br />

today to around 115 mppa;<br />

• Does not support the introduction of “mixed mode” as an<br />

interim measure before a third runway;<br />

• Confirms the intention to end the ‘Cranford agreement’<br />

(currently restricting easterly departures from 09L) ;<br />

• Confirms the view that a series of environmental operating<br />

practices on how the runways are used today should be<br />

continued ;<br />

• Proposes significant development of heavy rail proposals to<br />

provide better links with <strong>Heathrow</strong>, as well as improvements to<br />

the national rail network.<br />

High Level Programme<br />

Q5 Q6 Q7 Q8<br />

• Government Policy Decision<br />

• Optioneering/Prepare application<br />

• Application for Development Consent<br />

• Examination of application and<br />

decision<br />

• Detailed approvals / possession<br />

<strong>2009</strong><br />

<strong>2009</strong>/10<br />

2010<br />

2012<br />

2014<br />

• Construction<br />

• Phase 1 operational<br />

2017/18<br />

• Phased delivery of further capacity<br />

beyond 2020,<br />

dependent upon environmental limits<br />

2020 ---------> 2028<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 8


Activities over the next quarter<br />

FEB<br />

<strong>2009</strong><br />

MAR APR MAY<br />

• Forecasting and schedules<br />

- Procure consultant support<br />

- Begin forecast & schedule development<br />

• Surface access<br />

- Procure consultant support<br />

- Methodology review<br />

- Data collection, surveys, modelling review<br />

• Master plan concept development<br />

- Procure consultant support<br />

- Refresh of options (BAA / IATA)<br />

- Establish assessment criteria<br />

- Appoint Architects & Environmental<br />

• Programme office<br />

- Procure consultant support<br />

- Commission cost planning, programme,<br />

governance<br />

3. Recent Developments<br />

HAL and the airline community have been in discussion on the recovery, by HAL, of the<br />

Q5 PSDH monies and the ex-post or ex-ante nature of same. On 2 nd March 2008, HAL<br />

presented the airline community with a proposal for an ex-post arrangement supported<br />

by a consultation / agreement principle. HAL and the airline community agreed to work<br />

through the proposal in further detail in order to develop a way of working on PSDH.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 9


Trigger Change Control<br />

Appendix B: Trigger Change Control<br />

In order to cater for significant external events which could have an adverse impact on<br />

BAA’s ability to adhere to its original project schedules, the CAA proposed that there<br />

should be a clearly defined change control process for capital investment triggers<br />

incorporated within the relevant terms of the price control conditions.<br />

The CAA envisaged that it would amend the standards and rebates in one of two ways:<br />

Changes agreed by the airport and the airlines through the relevant LACC Committee<br />

and notified in writing to be approved by the CAA on an expedited basis. The process<br />

would be:<br />

• The CAA publishes any proposed agreement between the LACC and the airport<br />

inviting objections from interested parties.<br />

• The CAA then allows 28 days for any objections.<br />

• Unless the agreement raises significant issues, the CAA would expect to approve the<br />

agreement within 14 days of the end of the consultation period.<br />

• The CAA would anticipate that changes of this sort are likely to redistribute money<br />

at risk for triggers between projects reflecting changes to the anticipated content or<br />

phasing of the programme. While the CAA would be prepared to approve changes<br />

which either added to or reduced the amounts at risk it would not anticipate that<br />

this would be likely.<br />

Alternatively the CAA could revise the substance of the triggers in the price control<br />

without the agreement of users. This may occur in a range of circumstances where BAA<br />

made a formal application to the CAA for a change which was not agreed by airlines<br />

generally or which did not have sufficient support to allow the agreement of the<br />

relevant LACC committee. It might also be brought forward at the instigation of the<br />

CAA because it considered that such a change would be best calculated to meet its<br />

statutory duties. The process under these circumstances would require the following<br />

elements:<br />

• Any change to the price control condition would require the agreement of the<br />

airport operator under the <strong>Airport</strong>s Act 1986. The CAA would not proceed with any<br />

prospective change unless this was expected to be forthcoming;<br />

• The CAA would publish proposals for consultation and invite interested parties to<br />

respond.<br />

• It would allow an adequate period for written submissions which would not be less<br />

than 12 weeks.<br />

• Depending on the significance of the changes the CAA may then decide to hold<br />

meetings with some of the respondents.<br />

• The CAA would publish a decision with reasoning together with any revision to the<br />

price control to reflect the new triggers.<br />

The CAA would normally seek to limit changes to the price control under these<br />

arrangements to triggers and would not seek to make other changes.<br />

In respect of A - The CAA would expect to withhold approval only in limited<br />

circumstances where it concluded that the change was inconsistent with its statutory<br />

duties, for example where such agreements:<br />

did not give adequate weight to the interests of passengers as users;<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 10


on the basis of objections made, the agreement did not seem to the CAA to represent<br />

the interests of users generally or which appeared unreasonably to discriminate against<br />

any user or class of user.<br />

The CAA has drawn emphasis to the point that it would expect change control to allow<br />

the process of triggers to adapt to circumstances where airport and users priorities<br />

change and monies originally projected for capital expenditure on one project are<br />

diverted to extend the scope of, or bring forward the scope of some other project. It is<br />

certainly not intended to allow the airport to cancel trigger payments where it is no<br />

willing or able to pursue projects (unless the capital expenditure is redirected to<br />

extending the scope or expediting other projects). In this context it should be recognised<br />

that the building block projections allowed a return on such capital expenditure and it<br />

would be unreasonable for the airport to be able to avoid the mechanism in place to<br />

reduce at least some of that return if the relevant projects do not take place.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 11


Appendix C: PDS – Q5 Eastern Campus<br />

Project Definition Sheets – Q5 Eastern Campus<br />

Eastern Campus Airfield<br />

4202 : EA A/side Rd & Taxilane U/pass<br />

7207 : EAD Mid Stands & Taxilanes<br />

Leadership, Logistics and Enabling<br />

8828 : Eastern Campus EIS<br />

8798 : Eastern Campus Logistics<br />

Landside<br />

3814 : New Build MSCP - East<br />

8888 : Control Tower Demolition<br />

T2B, T1 and VP<br />

7230 : P22848 - QB Staff Rest Decant<br />

6716 : Pier 3 Demolition<br />

4201 : T2B Centre, Stnds & Pax Connectivity<br />

4539 : T2B North<br />

7205 : T2B NW Stands & Taxilanes<br />

7209 : T2B SE Stands & Taxilanes<br />

7210 : T2B SW Stands & Taxilanes<br />

7212 : Relocation of Substation 56<br />

T2A Phase 1 & Associated Projects<br />

8807 : T2A Phase 1 Stands<br />

T2A Programme Phase 1 (See section 3.1.3)<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 12


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

Eastern Apron Airside Road (EAAR)<br />

4202 : EA A/side Rd & Taxilane U/pass<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description: Grade separated airside road between T2A, B and C.<br />

Ref. Drawings / Images: Overview plan.<br />

Objectives:<br />

BAA: • provide reliable airside journey times<br />

• minimise the risk of conflict between aircraft and vehicles<br />

• provide a more straightforward east to west airside route<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green Scheme Design<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £47,700,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

04/2007 04/2010 Spring 2012 Spring 2013<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• This Project sits within the Eastern Campus Portfolio of work<br />

• The Project involves the construction of a grade separated airside road to provide<br />

access to the new T2B Terminal and T2C remote stands, which are being developed<br />

as part of the T2A Project.<br />

• The road starts from the roundabout at the SE corner of T2A, at grade, crosses over<br />

the LUL Piccadilly tunnels, descends under the Kilo Taxiway rising towards grade at<br />

T2B descending under the Lima taxiway and rising to grade at T2C<br />

• The scope of work for the road includes:-<br />

• Secant piled retaining walls<br />

• 2 overbridges Kilo and Lima Taxiways<br />

• A 12 m wide road (2 no 5m wide traffic lanes and 1m wide footways each side)<br />

• 4.5m traffic height plus 0.2m clearance zone<br />

• Drainage sumps and pumping<br />

• Electrical supply, distribution and lighting<br />

• Fire protection, Traffic management and control<br />

• The Kilo and Lima taxilane will be operational by Spring 2013. Prior to these dates<br />

the new grade separated road is anticipated to be complete in order not to conflict<br />

with the other construction work. It is also programmed to be carried out in<br />

conjunction with the redevelopment of the southern taxiway.<br />

• The road has been design to fit within physical and logistical constraints especially<br />

the LUL criteria.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 13


• Traffic modelling analysis was not available to verify the road capacity.<br />

• Consequently traffic queuing could be an issue at peak times especially when the<br />

road has been extended eastward to the EMB and eastern perimeter.<br />

Programme<br />

• CCRS Proposal 1 to be undertaken from 14 to 31 January <strong>2009</strong><br />

• Construction Decision Paper – governance boards approval process :-<br />

• 11 February Solutions Assurance Executive<br />

• 17 February Eastern Campus Stakeholder Board<br />

• 19 February Eastern Campus Programme Board<br />

• 26 February BAA Exec ( <strong>Capital</strong> Decision )<br />

• 16 March BAA Board<br />

• Early March approval by CAA of the Safety Case in relation to Kilo overbridge<br />

parapets<br />

• Commence production Design 23 March <strong>2009</strong> including Change of scope design<br />

proposal<br />

• July <strong>2009</strong> - Approval by LUL of Stage 3 Compliance Submission<br />

• Tendering document preparation, OTT and assessment complete by 30 November<br />

• Targets confirmation by 15 December<br />

• Contract award by 18 December <strong>2009</strong>.<br />

• Contractor mobilization and site set up – January 2010 to march 2010<br />

• Construction Start April 2010<br />

• Construction completion Spring 2012<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Maintenance TBD Maintenance costs to be developed but will<br />

include:-<br />

• General cleaning of the roadway and structures<br />

• M & E equipment – lighting, drainage and<br />

pumps, fire protection, traffic management and<br />

control.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• Currently None – however STAR Alliance Airlines may need to review the<br />

equipment, Tugs and 4 ( Dollies) they currently use to transport Baggage.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 14


• Trials will be undertaken in February <strong>2009</strong> along the T5 Airside Road with the<br />

existing Tug and 4 equipment. Should STAR Airlines be unable to use their current<br />

baggage transport vehicles they may need to purchase new and look to BAA for a<br />

contribution.<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 15


Appendix A: Overview: Reference Drawing / Image:<br />

GA Highway Horizontal and Vertical Alignment 000097 08/12/2008<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 16


Appendix B: Project Delivery<br />

Project Information<br />

Project Name:<br />

EA A/side Rd & Taxilane U/pass<br />

BCT No.: 4202 OP No.: 22750<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £42,500,000 80 %<br />

On-Cost: £6,468,591 12 %<br />

Risk (R1 Allowance only) £3,888,304 7 %<br />

Total (As entered into Artemis for Feb 09 Month End) £52,856,895<br />

Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 17


Appendix C: Project Delivery: High Level Project <strong>Plan</strong>:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 18


Header Information<br />

Project Name: T2B Centre Stands<br />

Name in Schedule 7207 : ESD Mid Stands & Taxilanes<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

Objectives<br />

BAA:<br />

Provision of 3 stands & Taxilanes. To serve T2B Central Pier.<br />

None<br />

Increase pier served stand supply.<br />

Improve airfield operations<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green Scheme Design<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £ 12,900,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on<br />

Completion on Site: Operational Use<br />

Decision:<br />

Site:<br />

Commences:<br />

Brief<br />

in 06/2012 09/2013 TBA<br />

Development<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

None<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

To be developed<br />

Impact on User Charges:<br />

Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 19


Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

EAD Mid Stands & Taxilanes<br />

BCT No.: 7207 OP No.: 23646<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £11,340,823 81 %<br />

On-Cost: £1,790,471 13 %<br />

Risk (R1 Allowance only) £919,936 7 %<br />

Total (As entered into Artemis for Feb 09 Month End) £14,051,230<br />

Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 20


Header Information<br />

Project Name: Eastern Campus EIS<br />

Name in Schedule 8828 : Eastern Campus EIS<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Energy & Infrastructure Services (EIS) required to support the<br />

operation of the Eastern Campus Phase 1.<br />

None<br />

Objectives:<br />

BAA: Responsible growth through good environmental<br />

performance.<br />

Service improvement in T2A and E.C Phase 1 being delivered.<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green Options<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £68,010,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Decision:<br />

Start on<br />

Completion on Site: Operational Use<br />

Site:<br />

Commences:<br />

12/2007 06 / <strong>2009</strong> 6/2011 12/2013<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

Key scope assumptions for this project are:<br />

Safeguarding for T2A Phase 2<br />

HV infrastructure to support T2A Phase 1 and T2B<br />

Cooling infrastructure to support T2A Phase 1 and T2B<br />

Heating infrastructure to support T2A Phase 1 and T2B<br />

Provision of other key services to support the construction of T2A Phase 1 and T2B<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

Opex and Revex impacts have not been assessed at<br />

this stage.<br />

Impact on User Charges:<br />

Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 22


The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 23


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

Eastern Campus EIS<br />

BCT No.: 8828 OP No.: 24006<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £47,787,263 81 %<br />

On-Cost: £8,826,488 15 %<br />

Risk (R1 Allowance only) £2,673,150 5 %<br />

Total (As entered into Artemis for Feb 09 Month End) £59,286,901<br />

Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 24


Header Information<br />

Project Name: CTA Redevelopment –T2 MSCP & Forecourt<br />

Name in Schedule 3814 : New Build MSCP East<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

New Build MSCP & forecourt to serve T2 (30mppa)<br />

None<br />

Provide good landside service in the form of an operational<br />

car park and forecourt (phase1) by the opening date of T2A<br />

(phase1)<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Amber Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £135,100,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Decision:<br />

Start on<br />

Completion on Site: Operational Use<br />

Site:<br />

Commences:<br />

March <strong>2009</strong> November 2011 July 2014 July 2013<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

Key scope elements are;<br />

T2A welfare provided in existing control tower until 2011<br />

Local listing of Control Tower and Chapel does not prohibit development<br />

Assumed increase in spaces per mppa from 85(existing T2) to 90<br />

Assumed demand for car park = 22.3m pax in 2025 (STAR, Aer Lingus, Virgin) [1340<br />

spaces 20mppa solution / 1980 30mppa solution]<br />

200 spaces allocated for operational requirements (30mppa solution)<br />

Connection walkways from car park to Terminal 2 arrivals and departures levels, and<br />

from car park to the existing T2 sub-way<br />

No office accommodation provided within “spine”<br />

Car park and forecourt build in two phases<br />

Temporary works for car park included<br />

VCC provision associated with car park, and LUL sub-way connectivity, for both pax and<br />

vehicles provided within the “spine”<br />

No office accommodation provided<br />

Forecourt lane within footprint of the car park<br />

Key scope exclusions are;<br />

Demolition of existing car park<br />

Demolition of control tower and relocation of associated facilities / utilities / tenants<br />

Relocation of the chapel<br />

Cost of modifying and removing the Early Services Gantry<br />

Walkway connection from the car park to the PTI (for passenger)<br />

All grade and elevated roads / forecourt lanes<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 25


Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) / Cost (-) Commentary:<br />

Cost Area: Impact per Annum:<br />

Not yet assessed<br />

Impact on User Charges:<br />

Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

In line with the rationalisation of Terminal 1 / 2; car parks 1,1A & B,2 are combined to a<br />

single facility<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

Capacity of MSCP at opening<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 26


Appendix A: Overview: Reference Drawing / Image:<br />

Cooling Station<br />

Phase 2<br />

Phase 1<br />

Walkway to Terminal<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 27


Appendix B: Project Delivery: Cost Information<br />

Project Information<br />

Project Name:<br />

New Build MSCP - East<br />

BCT No.: 3814 OP No.: 0<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £98,101,955 73 %<br />

On-Cost: £24,902,804 18 %<br />

Risk (R1 Allowance only) £12,074,087 9 %<br />

Total (As entered into Artemis for Feb 09 Month End) £135,078,846<br />

Commentary:<br />

This figure excludes; (1) future £48M Budget & AFC and (2) R2 & Inflation for Q5<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 28


Appendix C: Project Delivery: High Level Project <strong>Plan</strong>:<br />

Brief Decision Feb / March <strong>2009</strong><br />

Options Decision Summer <strong>2009</strong><br />

Construction Decision Spring 2010<br />

Start On Site September 2011<br />

Car Park Operational (phase 1) April 2013<br />

Completion May 2013<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 29


Header Information<br />

Project Name: Control Tower Demolition<br />

Name in Schedule 8888 Control Tower Demolition<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

The demolition and clearance of the existing control tower<br />

site to enable the construction of the new MSCP & forecourt<br />

for T2<br />

None<br />

Provision of proper service for landside access to T2A<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy None to date Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £28,500,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Decision:<br />

Start on<br />

Completion on Site: Operational Use<br />

Site:<br />

Commences:<br />

? March 2011 November 2011 Not applicable<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

Single phase demolition (Q5)<br />

Cost associated with the relocation of IT systems to be included within project scope.<br />

Cost associated with relocation of the HV substation to be included within the project<br />

scope.<br />

Relocation of tenants by others<br />

re-routing or protection of the HTHW main included within CTD scope<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) / Commentary:<br />

Cost Area: Cost (-)<br />

Impact per<br />

Annum:<br />

Assumed nil as demolition only.<br />

Impact on User Charges:<br />

Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact: TBC<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 30


The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 31


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

Control Tower Demolition<br />

BCT No.: 8888 OP No.: 0<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £22,832,705 80 %<br />

On-Cost: £3,397,000 12 %<br />

Risk (R1 Allowance only) £2,308,000 8 %<br />

Total (As entered into Artemis for Feb 09 Month End) £28,537,705<br />

Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 32


Header Information<br />

Project Name: Pier 3 Truncation<br />

Name in Schedule 6716 : Pier 3 Demolition<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Airline:<br />

Status:<br />

The project enables the construction and operation of the new<br />

stands to the West of T2B.<br />

<strong>Plan</strong> layout showing “cut” line.<br />

Operational efficiency through “toast racking” of apron<br />

As BAA’s<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> and Green<br />

DGS<br />

Solutions<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £3,500,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on<br />

Completion on Site: Operational Use<br />

Decision:<br />

Site:<br />

Commences:<br />

10/2006 Spring <strong>2009</strong> 04/2010 04/2010<br />

Estimated<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

The programme for the truncation of Pier 3 is dictated by the overall Eastern Campus<br />

programmes, in particular the stand layout plan, construction of T2B, and programme for<br />

the construction of the Terminal Pier as part of T2A phase 2<br />

Stand availability will allow project to continue as programmed<br />

The demolition of Pier 3 will be delivered in two phases.<br />

Phase 1 partially clears the existing Pier 3 and associated facilities to allow the<br />

reconfiguration of the new taxiway and stands to the West of the Mid-field pier.<br />

Phase 2 clears the area for development of a new Terminal Pier, and will be delivered<br />

under T2A Phase 2.<br />

The scope of works has been defined as follows with the works being divided into two<br />

phases.<br />

Under phase 1, demolition of building 469 and Pier 3 up to but retaining gate 121 at<br />

apron, departures and roof level.<br />

Under phase 2, demolition of Pier 3 up to but retaining the Terminal Control Centre and<br />

gate 117 at apron, departures and roof level.<br />

Works associated with both phases 1 & 2.<br />

the removal of asbestos<br />

re-configuration of M&E services,<br />

creation of weather tight seals<br />

removal of travelators etc.<br />

reconfiguration of airside roads<br />

relocation of assets and operations as required<br />

Completion of pier-served stands on T2B will be completed as programmed<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 33


Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Commentary:<br />

Cost Area:<br />

Pier 3<br />

Operational<br />

costs<br />

Revenue (+) / Cost<br />

(-) Impact per<br />

Annum:<br />

Minor impacts on utilities and manpower<br />

Impact on User Charges:<br />

Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 34


Appendix A: Overview: Reference Drawing / Image<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 35


Appendix B: Project Delivery: Cost Information<br />

Project Information<br />

Project Name:<br />

Pier 3 Demolition<br />

BCT No.: 6716 OP No.: 22534<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £1,919,112 55 %<br />

On-Cost: £1,276,222 37 %<br />

Risk (R1 Allowance only) £285,712 8 %<br />

Total (As entered into Artemis for Feb 09 Month End) £3,481,046<br />

Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 36


Header Information<br />

Project Name: T2B Phase 2<br />

Name in Schedule 4201 : T2B Centre Stands and Pax Connectivity<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

T2B Phase 2 completes T2B, providing pier service to an<br />

additional 10 stands, interim passenger connectivity from T2A<br />

and safeguarding permanent passenger connectivity and<br />

baggage processing within the pier.<br />

Artists impression showing split phases.<br />

High level general arrangements.<br />

Operational efficiency through “toast racking”.<br />

Service improvement.<br />

Alliance co-location.<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green Scheme Design<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £416,520,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Decision:<br />

Start on<br />

Completion on Site: Operational Use<br />

Site:<br />

Commences:<br />

02/2008 10/2010 06/2013 08/2013<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

T2B is a core element of the Eastern Campus development in meeting the following<br />

strategies:<br />

Eastern Campus Masterplan – fits with the “toastrack” vision<br />

Passenger Connectivity – provides safeguarding for a TTS system to be installed for T2A<br />

Phase 2 opening providing T5 equivalence and future proofing for a cross campus TTS<br />

system<br />

Baggage Strategy – provides safeguarding for a intra pier baggage system to be<br />

installed at a future date<br />

Key enablers for project delivery are:<br />

T2B Phase 1 stand provision is the essential prerequisite for decommissioning existing<br />

stands on Europier & enabling site availability<br />

Relocation of the inner taxiway is the prerequisite for availability of the southern portion<br />

of the T2B Phase 2 site<br />

T2A Energy Centre availability & associated permanent pipework route through T2A<br />

T2B must be provided in advance of T2A Phase 1 to provide longhaul stand capacity<br />

Key scope assumptions for this project are:<br />

Pier<br />

Provision of pier service for 10 stands<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 37


Segregated pier completed with open gateroom format<br />

Conversion of T2B Phase 1 (North) from closed gaterooms to open gatelounge<br />

Local flight connections centre<br />

Retail provision of approx 1,275m 2<br />

Total CIP provision of 3,600m 2 in 3 lounges<br />

Approx 4,000m 2 of ramp accommodation<br />

Basement structure for “traditional” transfer baggage facility (connecting tunnels and fit<br />

out by C&B).<br />

Demolition of Europier & Eurolink South<br />

Connectivity and Baggage<br />

Vertical passenger circulation within T2B for underground connectivity<br />

Safeguarding in T2B for future TTS (all fit out by future project) – assumed transfer of<br />

funds from PSDH of £73.6m in Q5 for this element of work<br />

T2A-T2B passenger tunnel with segregated corridors<br />

Interim vertical circulation core outside T2A connecting to passenger tunnel<br />

The baggage basement has been sized to safeguard for the future installation of a<br />

conventional baggage system.<br />

Stands & Taxiways<br />

Provision of 2 No. JX stands and associated taxiway (Q6)<br />

Scope Exclusions<br />

TTS and baggage tunnels beneath Lima and Kilo Taxiways<br />

Safeguarding for Powered Trolley System baggage facility in lieu of traditional<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Cleaning £1.0M Stand alone cost, not incremental<br />

Maintenance £1.3M Stand alone cost, not incremental<br />

Staffing £2.8M Stand alone cost, not incremental. Costs mainly<br />

associated with Connections Centre.<br />

Rates £2.1M Stand alone cost, not incremental<br />

Utilities £1.0M Stand alone cost, not incremental<br />

Property<br />

Income<br />

£3.8M Stand alone cost, not incremental. Income from<br />

CIP Lounges and accommodation<br />

Retail Income £1.2M Stand alone, not incremental. Income from retail<br />

units. Media income not included as allowed for<br />

within T2A package.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• The pier will operate in an open gatelounge format, subject to suitable process and<br />

technological solutions being agreed between STAR and BAA to enable STAR to<br />

operate from open gaterooms<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 38


Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• The pier will commence operations in a closed gateroom format. It is the intention<br />

to convert to an open gate lounge format upon T2B Phase 2 opening in 2013<br />

subject to suitable process and technological solutions being agreed between STAR<br />

and BAA to enable STAR to operate from open gaterooms<br />

• Baggage system – the size of the baggage basement required for safeguarding is<br />

dependant upon the type of system to be installed. The current scheme has been<br />

designed upon a tote/dcv system. Star have indicated that they may<br />

want the PTS system being installed in T2A to be extended out to T2B.<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 39


Appendix A: Overview: Reference Drawing / Image:<br />

Phase 2<br />

Phase 1<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 40


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 41


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name: T2B Phase 2<br />

BCT No.: 4201 OP No.: 23463<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £359,400,951 83 %<br />

On-Cost: £47,997,000 11 %<br />

Risk (R1 Allowance only) £26,450,000 6 %<br />

Total (As entered into Artemis for Feb 09 Month End) £433,847,951<br />

Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 42


Appendix C: Project Delivery: High Level Project <strong>Plan</strong>:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 43


Header Information<br />

Project Name: T2B Phase 1<br />

Name in 4539 : T2B North<br />

Schedule<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

T2B Phase 1 is the first phase of T2B, providing pier service to<br />

6 stands,<br />

Artists impression showing split phases.<br />

Objectives:<br />

BAA: • Operational efficiency through “toastracking”.<br />

• Service improvement.<br />

• Alliance co-location<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green Scheme Design<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £95,800,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

01/2007 06/2008 11/<strong>2009</strong> 01/2010<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• T2B is a core element of the Eastern Campus development in meeting the following<br />

strategies:<br />

• Eastern Campus Masterplan – fits with the “toastrack” vision<br />

• Passenger Connectivity – provides safeguarding for a TTS system to be installed<br />

for T2A Phase 2 opening providing T5 equivalence and future proofing for a<br />

cross campus TTS system<br />

• Baggage Strategy – provides safeguarding for a intra pier baggage system<br />

to be installed at a future date<br />

• Key enablers for project delivery are:<br />

• Airline Relocation Programme – the BA move to T5 reduces the stand demand in<br />

T1 such that the Kilo Cul-de-Sac to be closed. This facilitates site establishment<br />

and the commencement of enabling works<br />

• T2B Phase 1 NW Stands and Taxiways – without the stands and taxiways planes<br />

will not be able to use the pier<br />

• T2B Phase 1 NE Stands and Taxiways – without the stands and taxiways planes<br />

will not be able to use the pier<br />

• 10cm Radar re-provision – the new 10cm radar needs to be operational to<br />

facilitate the demolition of the existing 10cm radar at the end of Europier.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 44


• Key scope assumptions for this project are:<br />

• a fully segregated pier to provide pier service for 4 JW stands and 2 JX stands (JX<br />

with MARSED capability)<br />

• closed gate lounge format supporting the 6 stands (note: it is the intention to<br />

convert the gateroom to an open format when T2B Phase 2 opens in 2013<br />

subject to suitable process and technological solutions being agreed between<br />

STAR and BAA to enable STAR to operate from open gaterooms)<br />

• provision of 1,800m2 (net internal area) of ramp accommodation forming the<br />

first tranche of the 4,000 required for the whole of T2B<br />

• Retail coffee offer of 90m2 and media opportunities at departures and arrivals<br />

level<br />

• Temporary passenger connectivity via Europier<br />

• Temporary energy centre<br />

• The project will be delivered in 2 stages:<br />

• Stage 1 – Pier service to the 3 eastern stands, in Jan 2010<br />

• Stage 2 – Pier service to the 3 western stands in Oct 2010<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Cleaning £0.3M Stand alone cost, not incremental<br />

Maintenance £0.5M Stand alone cost, not incremental<br />

Staffing £0.1 Stand alone cost, not incremental<br />

Rates £0.5M Stand alone cost, not incremental<br />

Utilities £0.2M Stand alone cost, not incremental<br />

Property<br />

Income<br />

£0.8M Stand alone cost, not incremental. Income from<br />

accommodation<br />

Retail Income £0.1M Stand alone cost, not incremental<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• The pier will commence operations in a closed gateroom format. It is the intention<br />

to convert to an open gate lounge format upon T2B Phase 2 opening in 2013<br />

subject to suitable process and technological solutions being agreed between STAR<br />

and BAA to enable STAR to operate from open gaterooms.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 45


Appendix A: Overview: Reference Drawing / Image:<br />

Phase 2<br />

Phase 1<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 46


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name: T2B Phase 1<br />

BCT No.: 4539 OP No.: 22686<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £88,301,000 88 %<br />

On-Cost: £10,784,413 11 %<br />

Risk (R1 Allowance only) £1,000,000 1 %<br />

Total (As entered into Artemis for Feb 09 Month End) £100,085,413<br />

Commentary:<br />

£85m of base cost reflects lump sum agreement in place with BBG other £3m is for<br />

specialist systems. R1 likely to be reduced significantly as a result of BAA supply chains<br />

airbridge procurement directive not providing the AFC saving advised.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 47


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

T2B North West Stands & taxilanes<br />

7205 : T2B NW Stands & Taxilanes<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Provision of stands and realigned taxiways to the NW of T2B.<br />

Ref. Drawings / Images: Overview <strong>Plan</strong><br />

Objectives<br />

BAA: • Increase pier served stand supply.<br />

• Improve airfield allocation<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green Manufacture & Assemble<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £ 62,100,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Options<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

03/2007 27/04/<strong>2009</strong> 09/2010 09/2010<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• The scope of T2B NW Stands & Taxilanes Project is to supply, install, test,<br />

commission and handover the Apron works outlined below:<br />

• A new Kilo taxilane cul de sac<br />

• New permanent stands 231, 232 and 233<br />

• Reconfigure as temporary stands 120, 121 and 122.<br />

• Stands 231, 232 and 233 are JW stands which will become pier served.<br />

• The temporary stands are to be configured as follows:<br />

• 120 Medium stand<br />

• 121 J Marsed stand<br />

• 122 JW Remote.<br />

• The project scope also includes for funding of the Bravo taxiway Realignment works.<br />

Please note £3.7m transferred for enabling works and batcher relocation.<br />

• The phases of this project will be delivered on the following dates:<br />

• Stands & new taxilane will open / become operational in Sept 2010.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Op ex Nil To be developed<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 48


Impact on User Charges: Not included in CIP <strong>2009</strong> publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 49


Appendix A1: Overview:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 50


Appendix B: Project Delivery: Cost Information<br />

Project Information<br />

Project Name:<br />

T2B NW Stands & Taxilanes<br />

BCT No.: 7205 OP No.: 22908<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £24,005,622 84 %<br />

On-Cost: £3,217,875 11 %<br />

Risk (R1 Allowance only) £1,286,000 5 %<br />

Total (As entered into Artemis for Feb 09 Month End) £28,509,497<br />

Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 51


Appendix C: Project Delivery: High Level Project <strong>Plan</strong>:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 52


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

T2B South East Stands & Taxilanes<br />

7209 : T2B SE Stands & Taxilanes<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

Provision of 6 stands & Taxilanes.<br />

Overview <strong>Plan</strong><br />

Objectives:<br />

BAA: • Increase pier served stand supply.<br />

• Improve airfield operations.<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green Brief<br />

Project Delivery<br />

Current Control budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £37,800,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Decision:<br />

Brief in<br />

Development<br />

Operational Use<br />

Site:<br />

Commences:<br />

09/2010 TBA TBA<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

None<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

To be developed<br />

Impact on User Charges: Not included in CIP<strong>2009</strong> publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 53


Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 54


Appendix A: Overview:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 55


Appendix B: Project Delivery: Cost Information<br />

Project Information<br />

Project Name:<br />

T2B SE Stands & Taxilanes<br />

BCT No.: 7209 OP No.: 0<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £36,047,271 80 %<br />

On-Cost: £5,696,745 13 %<br />

Risk (R1 Allowance only) £3,361,080 7 %<br />

Total (As entered into Artemis for Feb 09 Month End) £45,105,096<br />

Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 56


Appendix C: Project Delivery: High Level Project <strong>Plan</strong>:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 57


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

T2B South West Stands & taxilanes<br />

7210 : T2B SW Stands & Taxilanes<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(refer to appendix A)<br />

Provision of 3 stands & Taxilanes to serve South West of T2B.<br />

Overview <strong>Plan</strong><br />

Objectives<br />

BAA: • Increase pier served stand supply.<br />

• Improve airfield operation<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green Scheme Design<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £19,500,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Decision:<br />

Brief in<br />

Development<br />

Operational Use<br />

Site:<br />

Commences:<br />

09/2010 03/2010 TBA<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

Operational Issues<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

To be developed<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 58


The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 59


Appendix A1: Overview:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 60


Appendix B: Project Delivery: Cost Information<br />

Project Information<br />

Project Name:<br />

T2B SW Stands & Taxilanes<br />

BCT No.: 7210 OP No.: 0<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £18,250,809 79 %<br />

On-Cost: £3,141,544 14 %<br />

Risk (R1 Allowance only) £1,853,511 8 %<br />

Total (As entered into Artemis for Feb 09 Month End) £23,245,864<br />

Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 61


Header Information<br />

Project Name: Substation 56<br />

Name in 7212 : Relocation of Substation 56<br />

Schedule<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description: Provision of replacement Sub-Station 56 from T1 pier 3.<br />

Ref. Drawings / Images: Location and overview plan<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA: • Deliver T2B to enable improved passenger and airline<br />

experience.<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green Construction<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £3,400,000<br />

Prior to CCRS transfers - Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Decision:<br />

Start on<br />

Site:<br />

Completion on Site: Operational Use<br />

Commences:<br />

10 / 2007 04 / 2008 06 / <strong>2009</strong> 06/ <strong>2009</strong><br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• With the construction of the T2B and adjacent stands, a requirement exists that part<br />

of Pier 3 be demolished starting October <strong>2009</strong>.<br />

• This project therefore focuses on relocation of Substation 56, and the incorporation<br />

into one facility of both 56 and 87, which will need to be relocated to make way for<br />

the future T2C.<br />

This project forms an integral part of the Toast-rack layout for the Eastern Apron.<br />

• Decommissioning Sub 56 is not part of this project and will be dealt with under the<br />

demolition of Pier 3<br />

• Decommissioning Sub 87 is not part of this project and will be dealt with under the<br />

Outer Pier and Taxiways project<br />

Key Milestones<br />

• Option Decision: 18th October 2007<br />

• Construction Decision: 20 th February 2008<br />

• Target Confirmation: 13 th May 2008<br />

• Completion Confirmation 30th June <strong>2009</strong><br />

Other Key Dates<br />

• <strong>Plan</strong>ned Start on Site: 28th April 2008<br />

• Buildings Weather tight: 5 TH September 2008<br />

• <strong>Plan</strong>ned finish on site: 30th th June <strong>2009</strong><br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 62


Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

Commentary:<br />

per Annum:<br />

Opex Estimated at<br />

+£12 k<br />

Sub 56 currently powers both AGL (block 24i to<br />

32i) and piers uses. The new Sub 56 will cover only<br />

the AGL block. A direct comparison between<br />

current maintenance costs of Sub 56, and the<br />

maintenance costs for the future Sub 56, is not<br />

relevant as power requirements on new substation<br />

will be different from the existing Sub 56.<br />

Maintenance costs for airside AGL substation<br />

approximately £12k pa. It is anticipated that as a<br />

new substation is being built to house both Sub 56<br />

and 87, economies of scale in maintenance will be<br />

30% once sub 87’s circuits have been transferred<br />

across (due to having only a single standby<br />

generator, HV transformer and LV switchboard to<br />

maintain). This will lead to a maintenance saving of<br />

£4k pa.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 63


Appendix A: Overview. Reference Drawings / Image:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 64


Appendix B: Project Delivery: Cost Information<br />

Project Information<br />

Project Name: Relocation of Substation 56<br />

BCT No.: 7212 OP No.: 22916<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £3,097,230 84 %<br />

On-Cost: £517,468 14 %<br />

Risk (R1 Allowance only) £68,680 2 %<br />

Total (As entered into Artemis for Feb 09 Month End) £3,683,378<br />

Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 65


Appendix C: Project Delivery: High Lever Project <strong>Plan</strong><br />

High Level Scope<br />

• Site set up including placement of blast screens, establishment of welfare and<br />

compound;<br />

• Breakout of existing concrete and construction of foundation and trenches and<br />

tie in to existing services infrastructure;<br />

• Off site prefabrication of superstructure elements and cladding;<br />

• Erection of superstructure on site;<br />

• Electrical installations including transformers, generator, fuel tank, switchboards,<br />

CCR’s, isolators, small power and lighting, and all associated cabling;<br />

• Cladding of superstructure and installation of permanent doors;<br />

• Service diversions/transfer of load from existing sub-station 56;<br />

• External works.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 66


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

T2A Phase 1 Stands<br />

8807 : T2A Phase 1 Stands<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description: Stands to fit with T2A phase 1<br />

Ref. Drawings / Images: Overview plan<br />

Objectives:<br />

BAA: • Improve passenger experience<br />

• Improve airline operational efficiency.<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green Scheme Design<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £25,080,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Decision:<br />

Start on<br />

Site:<br />

Completion on Site: Operational Use<br />

Commences:<br />

June <strong>2009</strong> October 2013 December 2013<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• New aircraft stands to the south and east of the terminal are also part of the T2A<br />

programme of works. In high-level terms the scope of the airfield works is<br />

summarised below:<br />

• South of the T2A Terminal Building:<br />

• 2 No. Medium Stands,<br />

• 2 No. JX MARS Stands<br />

• East of the T2A Terminal Building:<br />

• 4 No Medium Stands safeguarded for conversion to 2No. JX MARS Stands,<br />

• 2 No Medium Stands<br />

• Pavements for new aircraft stands, head of stand road, parking/lay-bys and footway<br />

round T2A.<br />

• Airside services (new, abandonment, protection and diversion) including strategic<br />

services required to serve T2A.<br />

• Temporary airside road diversion and airside security fencing.<br />

• Delivery strategy is based on Airline Relocations Move Sequence 3.1 dated 13/01/09.<br />

• The phases of this project will be delivered on the following dates:<br />

• Temporary airside road and security fence in place by April 2010.<br />

• Airside early services diversions complete by April 2010.<br />

• Currently there is no requirement to handover individual stands prior to T2A<br />

opening. All stands will be handed over in 2013.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 67


Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Nil<br />

To be developed<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 68


Appendix A: Overview: Reference Drawing / Image:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 69


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

T2A Phase 1 Stands<br />

BCT No.: 8807 OP No.: 24024<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £19,352,310 80 %<br />

On-Cost: £3,260,016 13 %<br />

Risk (R1 Allowance only) £1,639,372 7 %<br />

Total (As entered into Artemis for Feb 09 Month End) £24,251,698<br />

Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 70


Appendix C: Project Delivery: High Level Project <strong>Plan</strong>:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 71


Header Information<br />

Project Name: T2A Programme, Phase 1<br />

Name in Various : T2A Buildings Project<br />

Schedule:<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Terminal 2 Concourse A (T2A) Phase 1 (and associated<br />

projects)<br />

Artists impression of landside area<br />

Objectives:<br />

BAA: • Improve Passenger experience<br />

• Reduce airline and HAL opex<br />

• Improve operational efficiency<br />

• Co-location airline alliances<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green Various<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> budget (Constant Prices): £ 1,142,080,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Decision:<br />

Start on<br />

Site:<br />

Completion on Site: Operational Use<br />

Commences:<br />

06/<strong>2009</strong> 07/<strong>2009</strong> 08/2013 12/2013<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

T2A replaces outdated facilities in existing Terminal 2 and the forecourt with facilities<br />

primarily for the Star Alliance airlines to enable the consolidation of their operation into<br />

one building at <strong>Heathrow</strong> providing competitive equivalence and to meet the future<br />

needs of Star Alliance passengers and BAA’s requirements for a flexible future proof<br />

capacity.<br />

• The BCT projects captured within this PDS are as follows (Q5/Q6):<br />

• 7767 – T2A Scheme Design Stage £28m<br />

• 8802 – T2A Building £581m<br />

• 8804 – T2A ICS £107m<br />

• 8805 – T2A Baggage £105m<br />

• 7769 – T2A L/S Early Services Relocation £16m<br />

• 7779 – T2A A/S Early Services Relocation £3m<br />

• 8799 – QB Demolition £6m<br />

• 8800 – T2 Demolition £17m<br />

• 8803 – Other CTA Enabling Works £2m<br />

• 8794 – Eastern Campus Leadership Team £58m<br />

Other assumptions:<br />

• Q5 Budget taken from November 08 Artemis Month End Figures<br />

• Future Quinquennia figure covers Q6 Phase 1 programme only<br />

• The vacant possession of T2 and Queens Building, step 6, is achieved on time to<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 72


enable a start on site 27 October <strong>2009</strong>.<br />

• The baggage solution must be agreed with the Star Airlines and wider airline<br />

community.<br />

• The AFC for the project will meet the target budget for the programme<br />

• Pier service levels of 95% will be achieved within the <strong>Heathrow</strong> East Campus<br />

• HETco and Siemens establish an effective working relationship<br />

• All reserved matters are discharged by July <strong>2009</strong> including LUL approval<br />

• Site lines from the Control Tower are acceptable to NATS<br />

• There is no undue effect on the operational running of the airport during<br />

consultation<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) / Cost<br />

(-) Impact per<br />

Commentary:<br />

Terminal<br />

Building<br />

Annum:<br />

£395m The revenue figure represents the EBITDA<br />

(Revenue less Cost before interest, tax,<br />

depreciation and amortisation costs) for the<br />

first full financial year of operation (2014/15) for<br />

the T2A Terminal building<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• Above is based on estimated operational expenditure (business rates,<br />

maintenance costs etc) that may require further definition in due course.<br />

• The Revenue/Cost data does not include the other part of the Eastern Campus<br />

programme<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• There is substantial concern from the airlines community in relation to the<br />

baggage solution for T2A and T2B.<br />

• The forecourt for the new T2A is yet to be successfully integrated into the new<br />

MSCP.<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 73


Appendix A: Overview: Reference Drawing / Image:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 74


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

T2A Building Projects<br />

BCT No.: 7767, 8802,<br />

8799, 8800,<br />

8803, 8794,<br />

OP No.:<br />

7779 &<br />

8798<br />

23225, 24000,<br />

23993, 23995,<br />

24001, 23994,<br />

23223, 23224 &<br />

24013<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £966,709,374 80 %<br />

On-Cost: £181,841,168 15 %<br />

Risk (R1 Allowance only) £62,778,015 5 %<br />

Total (As entered into Artemis for Feb 09 Month End) £1,211,328,557<br />

Commentary:<br />

Base cost incl £25m for Operational Readiness. Accommodation costs, IT, Systems assurance in on-cost<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 75


Appendix C: Project Delivery: High Level Project <strong>Plan</strong>:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 76


Appendix D: PDS – Q5 Western Campus<br />

Project Definition Sheets – Q5 Western Campus<br />

Terminal 3<br />

7540 : T3 Office Refurbishment Airline Moves<br />

3829 : MARSing STND 324 - 330 & CTA S<br />

5094 : Pier 5 Departures Walkway<br />

8002 : Pier 7 stands works<br />

7593 : T3 Zone B-G Upgrade<br />

8406 : Pier 7 Connector Refurb<br />

8494 : Pier 5 Gateroom Enclosures<br />

8510 : Landside Departures 1st Floor<br />

8563 : Immigration Hall Refurb<br />

0002 : T3 Additional Transfer Security Lanes - SQR<br />

8569 : T3 Baggage Hall Refit<br />

9222 : T3 Additional Departures Security Lane<br />

Terminal 4<br />

6604 : T4 Airline Relocation<br />

3831 : T4 Check-in Capacity<br />

6693 : Terminal 4 Refurbishment<br />

8275 : T4 Victor Pier Refurbishment<br />

9028 : T4 Additional Transfer Security Lanes<br />

8274 : T4 Flooring<br />

Terminal 5<br />

T5C (See section 3.2.3)<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 77


Header Information<br />

Project Name: Terminal 3 Airline Relocations<br />

Name in 7540 : T3 Office Refurbishment Airline Moves<br />

schedule<br />

BCT No: 7540 CIP ID: ????<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

This project will provide facilities (primarily office and ramp<br />

accommodation) that support and facilitate the Airline<br />

Relocations Strategy, specifically Step 4, and the collocation of<br />

the oneworld Alliance airlines into Terminal 3.<br />

None<br />

Objectives:<br />

BAA: • Provide facilities that support and facilitate Step 4 of the<br />

Airline Relocations Strategy, and the increased collocation<br />

of the oneworld Alliance airlines into Terminal 3.<br />

• Deliver the spirit and intent of the oneworld<br />

Memorandum of Understanding.<br />

• Provide the oneworld Airline occupiers the opportunity to<br />

operate more efficiently through the provision of<br />

appropriate facilities (standard and location).<br />

Airline:<br />

Airline relocation collocation strategy enabled.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green ???<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £8,200,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Decision:<br />

Site:<br />

MM/ YYYY 06/2008<br />

(Enabling works<br />

started 04/2008)<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

12/<strong>2009</strong> 01/<strong>2009</strong> (Finnair)<br />

02/<strong>2009</strong> (British<br />

Airways and Iberia)<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

The outline scope includes:-<br />

• The reconfiguration and development of landside and airside office and ramp<br />

accommodation to meet the requirements of the new Terminal 3 occupants (British<br />

Airways, Iberia and Finnair)<br />

• Associated HAL and third party moves to enable these Airline relocations.<br />

The agreed delivery programme has been based on meeting the requirements of Step 4<br />

of the Airline Relocations strategy, and the coordination with Airline IT installations and<br />

Operational Readiness dates. The works involved is largely in non public areas,<br />

therefore, there has been no impact to the terminal operation.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 78


Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Cost<br />

Area:<br />

Revenue (+) /<br />

Cost (-)<br />

Impact per<br />

Annum:<br />

Commentary:<br />

See assumptions<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

The key elements of this project are essentially major refurbishment of existing<br />

accommodation and facilities and, therefore, there will not be any major financial<br />

impacts.<br />

Most of the areas are replacing existing tenants in similar space and will be subject to<br />

standard property lease agreements, therefore, no incremental income is expected.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None.<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 79


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

T3 Airline Moves (Office/Ramp)<br />

BCT No.: 7540 OP No.: 23058<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £5,087,710 69 %<br />

On-Cost: £2,195,179 30 %<br />

Risk (R1 Allowance only) £97,977 1 %<br />

Total (As entered into Artemis for Feb 09 Month End) £7,380,866<br />

Commentary:<br />

Q4 and Q5 spend. Works complete on site and nearing completion.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 80


Header Information<br />

Project Name:<br />

Name on<br />

Schedule:<br />

MARSing Stands 324 – 330 and CTA s<br />

3829 : MARSing STND 324 – 330 and CTAS<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Provision to allow, if needed, work in T3 to enable EI to move<br />

to T3 before T2A opening.<br />

Extract from T3 Programme Booklet.<br />

Improved passenger service through flexible use of available<br />

infrastructure.<br />

Airline:<br />

Not discussed<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Red Pre-Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): 14,900,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Decision:<br />

Start on<br />

Site:<br />

Completion on Site:<br />

TBC<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• See Appendix A.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

To be developed if project progresses.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• None.<br />

Areas of Disagreement<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 81


The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• None.<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 82


Appendix A: Overview: Reference Drawing / Image:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 83


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

Pier 5 Refurbishment<br />

5094 : Pier 5 Departures Walkway<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Refurbish the Pier 5 Departures level walkway to a design<br />

standard which is comparable with Pier 6 and other such<br />

facilities across <strong>Heathrow</strong>.<br />

None<br />

Objectives:<br />

BAA: Provide a significantly enhanced passenger and user<br />

experience on Pier 5 and improve QSM scores<br />

Airline:<br />

Provide a facility equivalent to other facilities at <strong>Heathrow</strong>.<br />

Mou objectives delivered.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green DGS<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £5,500,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

MM/ YYYY 09/ 2008 04/<strong>2009</strong> 04/<strong>2009</strong><br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

The outline scope includes:-<br />

• New ceiling and lighting<br />

• Micam wall panelling system<br />

• New character timber wall panels at gateroom entrances with integrated LCDs<br />

• Introduction of glazing into gateroom entrance walls where appropriate<br />

• Rationalisation and upgrade of fire doors<br />

• New signage and wayfinding as appropriate<br />

Upgrade of M&E where required.<br />

• This project has been classed as a Trigger project with a completion date of 1 st<br />

August <strong>2009</strong>.<br />

• The agreed delivery programme is based on the formation of temporary gateroom<br />

entrances required to facilitate the installation of the new entrance doors and<br />

frontage. The works will be undertaken concurrently with other projects in Terminal<br />

3 and this will be carefully managed to ensure that in total they do not have an<br />

unacceptable effect on the existing operation.<br />

• The Pier 5 gaterooms, the end of Pier 5 and the Pier 5 elbow are not included in the<br />

scope of this project, they are being dealt with separately.<br />

• The majority of the works will be undertaken during the night in order to maintain<br />

the operational integrity of the pier at all times.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 84


Operational Issues<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Cost Revenue (+) /<br />

Commentary:<br />

Area:<br />

Cost (-)<br />

Impact per<br />

Annum:<br />

Cleaning/Maintenance +£10k pa Additional cleaning/maintenance costs of<br />

glazing and new systems.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• The key elements of this project are essentially refurbishment works of existing<br />

facilities and, therefore, there will not be any major financial impacts nor any<br />

significant losses on disposals.<br />

• It is assumed that there will be some incremental cleaning costs of approximately<br />

£10k per annum. There will be no impact on retail income as all sites will be<br />

protected.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None.<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 85


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

T3 Pier 5 Departures Walkway<br />

BCT No.: 5094 OP No.: 20706<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £4,744,186 75 %<br />

On-Cost: £1,237,277 19 %<br />

Risk (R1 Allowance only) £370,863 6 %<br />

Total (As entered into Artemis for Feb 09 Month End) £6,352,326<br />

Commentary:<br />

Q4 spend on Scheme Design of £540,056 included in figures above. 100% of base cost total<br />

with CBi (Morgan Ashurst).<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 86


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

Pier 7 Stands and Loading Bridges<br />

8002 : Pier 7 Stands Works<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Extend the loading bridges and reconfigure the stands on Pier<br />

7 in order to overcome existing constraints and reinstate<br />

existing dual loading bridge service for the A340-600 aircraft.<br />

None<br />

Objectives:<br />

BAA: • Improve service standards with increased loading bridge<br />

functionality.<br />

• Deliver elements of Mou’s.<br />

Airline:<br />

As above.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green ???<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £3,400,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

MM/ YYYY 10/ 2008 12/<strong>2009</strong> 05/<strong>2009</strong><br />

(Sequential<br />

Operational Use<br />

commences)<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• This project is part of a programme of expenditure to enable Virgin to centre their<br />

operations onto Pier 7 and, in turn, facilitate the collocation of American Airlines<br />

and the oneworld Alliance airlines onto Pier 5, which is in fulfilment of both parties’<br />

MoU.<br />

• The outline scope includes;<br />

• Extension of 6 number existing loading bridges, and structural repairs, refurbishment<br />

as necessary<br />

• Relocation of redundant loading bridge from stand 314 to stand 322 and associated<br />

foundation works to provide a consistent dual loading bridge service on this stand<br />

• Application of new paint markings and aircraft stop positions as required<br />

• Installation of new PAPA board markings as required<br />

• Future modifications to remote stand 365.<br />

• The agreed programme is based on the sequencing of the Pier 7 Refurbishment<br />

programme and the need to overcome existing loading bridge constraints.<br />

• Works to Stands 313 and 318 are not included within the project scope because of<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 87


existing constraints. The works to remote stand 365 have been put on hold because<br />

of the operational impact, it is anticipated that they will be undertaken in 2010 post<br />

Airline Relocations Step 9.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Cost Revenue (+) /<br />

Commentary:<br />

Area:<br />

Cost (-)<br />

Impact per<br />

Annum:<br />

See assumptions<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• The key elements of this project are essentially alterations to existing facilities and<br />

infrastructure, therefore, it is not expected that there will be any major financial<br />

impacts nor any significant losses on disposals.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• Timing of work to stand 365 which BAA and the airline community agreed to put<br />

on hold due to operational impact.<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 88


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

T3 Pier 7 Stand Works<br />

BCT No.: 8002 OP No.: 23461<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £2,408,867 77 %<br />

On-Cost: £478,940 15 %<br />

Risk (R1 Allowance only) £239,965 8 %<br />

Total (As entered into Artemis for Feb 09 Month End) £3,127,772<br />

Commentary:<br />

Q5 project only. £1.6M of base cost with CBi (Morgan Ashurst) and £0.8M with Pavement<br />

Team.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 89


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

T3 Check In Zones B to G Upgrade<br />

7593 : T3 Zone B-G Upgrade<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description: The project is the refurbishment of T3 Check In Zones B to G.<br />

Ref. Drawings / Images: • T3 ground floor plan layout,<br />

(Refer to Appendix A)<br />

• Check In Visualisations<br />

Objectives:<br />

BAA: • Improve the passenger experience.<br />

• Provide capacity and airline accommodation for Airline<br />

Moves.<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green Delivery<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £16,500,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Decision:<br />

Start on<br />

Site:<br />

Completion on Site: Operational Use<br />

Commences:<br />

07/2008 10/<strong>2009</strong> 12/2008<br />

Phased handovers<br />

of Zones for<br />

operational use.<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

Key scope items are:<br />

• New raft ceiling and replace bulkheads<br />

• Improved lighting<br />

• New walls behind check in desks,<br />

• Reclad passenger area wall linings<br />

• Reclad front of check in desks<br />

• Reclad column casings<br />

• VCC cladding refinished<br />

• Upgraded way finding<br />

• New queue mazes in cul-de-sac areas<br />

• Replace hammerheads on zones F/G with CUSS / SSK<br />

• Local floor repair and polishing<br />

• New zone G entrance door<br />

• New IT communications rooms<br />

• New façade ticket desks<br />

• Back of house accommodation works for airline moves<br />

• Scope changes transferred from HAL minor projects<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 90


• Entrance doors for zones C to F<br />

• New FIDS above desks<br />

• Entrance door FIDS<br />

• The project has a trigger date of 1 April 2010<br />

• Zones F&G are to be complete for the Step 4 move.<br />

• The entrance doors for zones C to F and entrance FIDS have been change controlled<br />

into the scope.<br />

• Majority of work will be done at night<br />

• Check in desk refurbishment retains the existing desk structure and functionality.<br />

• New queue mazes will be delivered after the project completion, post a trial of the<br />

new layout.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Nil<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• This is predominantly a refurbishment of existing assets. It is assumed that impacts<br />

on revex will be negligible (savings balanced against increases)<br />

• Loss on disposals is negligible since the majority of the infrastructure is time expired.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• Back wall branding – Airlines have requested an investigation into technological<br />

approach to the branding behind check in desks, in place of handing boards<br />

currently in use.<br />

• Branding above CUSS and SSK’s. Airlines have been required to follow the branding<br />

guidelines.<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 91


Appendix A: Overview: Reference Drawing / Image:<br />

HAL P+W 23090 A 2000<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 92


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 93


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

T3 Zone B-G Upgrade<br />

BCT No.: 7593 OP No.: 23090<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £13,086,384 79 %<br />

On-Cost: £2,674,188 16 %<br />

Risk (R1 Allowance only) £744,032 5 %<br />

Total (As entered into Artemis for Feb 09 Month End) £16,504,604<br />

Commentary:<br />

Q5 project only. £11.1m of base cost with CBi (Morgan Ashurst) and £2.0M with BAA<br />

Specialist Systems<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 94


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

Pier 7 Refurbishment<br />

8406 : Pier 7 Connector Refurb<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description: • Provide a passenger facing refurbishment solution which<br />

is comparable with the quality and design strategy found<br />

elsewhere in Terminal 3 on Piers 5 & 6.<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

None<br />

Objectives:<br />

BAA: • Provide a significantly enhanced passenger and user<br />

experience on Pier 7 and improve QSM scores.<br />

Airline: • Provide a facility equivalent to other such facilities at<br />

<strong>Heathrow</strong>.<br />

• Mou objectives delivered.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green ???<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £14,800,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

MM/ YYYY 08/ 2008 12/<strong>2009</strong> 12/<strong>2009</strong><br />

(Sequential<br />

Operational Use<br />

commences<br />

10/2008)<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• This project has been classed as a Trigger project with a completion date of 1 st<br />

September <strong>2009</strong>.<br />

The planned replacement of Pier 7 in Q6 has been taken into account when selecting<br />

the relevant finishes and design solutions for this refurbishment without compromising<br />

the main objective.<br />

The outline scope includes:-<br />

• New rubber hard flooring to walkway areas<br />

• New carpet to gaterooms<br />

• Refurbishment of walls and repainting of ceilings on the connector and pier<br />

walkways<br />

• Refurbishment of the walls in the gaterooms<br />

• New character timber wall panels to gateroom entrances with integrated LCD<br />

screens<br />

• Introduction of some additional internal and external glazing<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 95


• New lighting to perimeter wall of pier<br />

• Enlargement of gateroom entrance lobbies and provision of fixed post queue mazes<br />

to maximise space and facilitate airline boarding procedures<br />

• New gateroom desks<br />

• Reupholstered gateroom seating<br />

• New signage and wayfinding as appropriate.<br />

• The agreed programme is based on the refurbishment of one gateroom closure at a<br />

time in order to minimise operational disruption, in particular the impact on remote<br />

coaching and Pier Service levels. The works will be undertaken concurrently with<br />

other projects in Terminal 3 and this will be carefully managed to ensure that in total<br />

they do not have an unacceptable effect on the existing operation.<br />

• The majority of the works will be undertaken during the night in order to maintain<br />

the operational integrity of the pier at all times.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Cost Revenue (+) /<br />

Commentary:<br />

Area:<br />

Cost (-)<br />

Impact per<br />

Annum:<br />

Cleaning/Maintenance +£10k pa Additional cleaning/maintenance costs of<br />

glazing and new systems.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• The key elements of this project are essentially refurbishment works of existing<br />

facilities and, therefore, there will not be any major financial impacts nor any<br />

significant losses on disposals.<br />

• It is assumed that there will be some incremental cleaning costs of approximately<br />

£10k per annum. There will be no impact on retail income as all sites will be<br />

protected.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• Additional external glazing to the gaterooms - BAA has agreed to provide glazing to<br />

4 of a total of 8 gaterooms.<br />

• Baggage chute at Gate 318 - BAA has considered this, a feasible and affordable<br />

solution has been identified and the works have now been included in the project<br />

scope. (This is a resolved area of disagreement).<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 96


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

T3 P7 & Connector<br />

BCT No.: 8406 OP No.: 23693<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £10,513,876 74 %<br />

On-Cost: £2,784,047 20 %<br />

Risk (R1 Allowance only) £914,165 6 %<br />

Total (As entered into Artemis for Feb 09 Month End) £14,212,088<br />

Commentary:<br />

Q5 project only. £10.1m of base cost with CBi (Morgan Ashurst) and £0.4M with BAA<br />

Specialist Systems<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 97


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

Pier 5 Gateroom Enclosures<br />

8494 : Pier 5 Gateroom Enclosures<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

This project is required to enclose the open gaterooms on Pier<br />

5 Terminal 3 in order to facilitate both Transportation Security<br />

Administration (TSA) and Department for Transport (DfT)<br />

security requirements, and in turn enable the stands to be<br />

fully utilised.<br />

None<br />

Improved stand utilization in live with Mou’s<br />

Operational efficiencies through a reduction in Airline and<br />

BAA security staff.<br />

Aid intuitive passenger processes through a consistent<br />

gateroom boarding operation with the rest of Terminal 3.<br />

Airline:<br />

Mou stand preferences met.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green ???<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £3,300,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

MM/ YYYY 11/ 2008 02/<strong>2009</strong> 12/2008 (Functional<br />

use of Phase 1)<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• This project supports the Airline Relocations strategy and directly facilitates the<br />

revised Terminal 3 stand preferences (the oneworld Alliance airlines onto Pier 5 and<br />

Virgin onto Pier 7).<br />

• The outline scope includes:-<br />

Pier 5 Phase 1 Extension (Elbow)<br />

• The enclosure of the 3 gaterooms (330, 332 and 334) by way of a full height<br />

glazed partitioning system<br />

• Re-use of existing desks and introduction of an additional single premium<br />

boarding card desk in each of the 3 gaterooms<br />

• Reprovision of the late bag drop<br />

• Replacement of carpet with a conglomerate floor tile.<br />

Pier 5 Phase 2 Extension (end Pier 5)<br />

• The extension of the low level glazed partitions and interconnecting gates to<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 98


those gaterooms at the end of Pier 5 to the required security height<br />

• Replacement of the existing entrance barriers with new doors.<br />

• The agreed delivery programme is based on an interim handover status which<br />

achieves functional status of Phase 1 by Christmas 2008. The remaining works,<br />

including the works to Phase 2 and the replacement of the floor, will be completed<br />

by the end February <strong>2009</strong>. The works will be undertaken concurrently with other<br />

projects in Terminal 3 and this will be carefully managed to ensure that in total they<br />

do not have an unacceptable effect on the existing operation.<br />

• The majority of the works will be undertaken during the night in order to<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Cost Revenue (+) /<br />

Commentary:<br />

Area:<br />

Cost (-)<br />

Impact per<br />

Annum:<br />

Cleaning/Maintenance +£2.5k pa Cleaning costs of new glazing system.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• The key elements of this project are essentially refurbishment works of existing<br />

facilities and, therefore, there will not be any major financial impacts nor any<br />

significant losses on disposals.<br />

• It is assumed that there will be some incremental cleaning costs of approximately<br />

£2.5k per annum. There will be no impact on retail income as all sites will be<br />

protected.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None.<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 99


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

Pier 5 Gateroom Enclosures<br />

BCT No.: 8494 OP No.: 23765<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £2,170,592 76 %<br />

On-Cost: £486,544 17 %<br />

Risk (R1 Allowance only) £205,734 7 %<br />

Total (As entered into Artemis for Feb 09 Month End) £2,862,870<br />

Commentary:<br />

Q5 project only. £2.1M of base cost with CBi (Morgan Ashurst)<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 100


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

T3 Landside Departures Refurbishment<br />

8510 : Landside Departures 1 st Floor<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

The refurbishment of passenger facing areas in T3 Landside<br />

Departures:<br />

Ref. Drawings / Images: General arrangement plan.<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA: Improve the passenger experience through landside<br />

departures with an improved passenger flow to security<br />

Airline:<br />

search.<br />

Increase efficiency and experience of passengers going from<br />

check in through to security search.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green ???<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £5,200,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

10 / 2008 11 / <strong>2009</strong> 09 / 2010 09 / 2010<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• The project has a trigger date of 01 April 2011<br />

• It assumed that the majority of work will be done at night with minimal impact on<br />

the operation and retail<br />

Key scope items are:<br />

• New ceiling system (excluding south wing annexe)<br />

• Improved lighting<br />

• New wall linings<br />

• Upgraded way finding<br />

• Repair and polish existing terrazzo floor<br />

• Rationalisation of signs and plasma screens.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 101


See assumptions<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• This is a refurbishment project, hence it is assumed that impacts on opex and<br />

income will be negligible.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 102


Appendix A: Overview: Reference Drawing / Image:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 103


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

Landside Departures<br />

BCT No.: 8510 OP No.: 23825<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £3,770,000 72 %<br />

On-Cost: £679,000 13 %<br />

Risk (R1 Allowance only) £801,000 15 %<br />

Total (As entered into Artemis for Feb 09 Month End) £5,250,000<br />

Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 104


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

T3 Immigration Hall Refurbishment<br />

8563 : Immigration Hall refurb<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

This refurbishment project is part of a £68M programme of<br />

expenditure to refurbish Terminal 3, partly driven through<br />

asset replacement, and partly through airline relocations. The<br />

aim is to brighten and lift the overall space in line with T5<br />

design standards, to improve passenger flow throughout, and<br />

to provide a facility that can support the UKBA in improving<br />

service standards. This will include but is not limited to:<br />

• replacement floor, wall, and ceiling finishes to all passenger<br />

facing areas<br />

• increased & flexible queuing maze with increased capacity<br />

• T5 standard staggered immigration desks<br />

• optimised way-finding & improved signage<br />

• reduced congestion in the ‘decision-zone’<br />

HAL Minor Projects are refurbishing toilets and airconditioning<br />

throughout to provide a complete and consistent<br />

refurbishment product<br />

General arrangement of Option C.<br />

The refurbishment will provide a significantly enhanced<br />

passenger and user experience and will support the airline<br />

relocation programme and the relocation of oneworld to<br />

Terminal 3. This will be achieved by:<br />

• Easing congestion whilst improving passenger way-finding<br />

and orientation;<br />

• Improving utilisation of space for passengers and airline<br />

support facilities;<br />

• Improving access and egress links;<br />

• Modernising the appearance consistent with the BAA<br />

design palette;<br />

• Where appropriate, provision of high-quality lighting and<br />

surfaces to receive lighting.<br />

Airline:<br />

Service quality equivalence.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> &Solutions Green Scheme Design<br />

Project Delivery<br />

Current Control budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £10,600,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief Start on Completion on Site: Operational Use<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 105


Decision: Site: Commences:<br />

10 / 2007 01 / 2010 07 / 2010 Continuous<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• A refurbishment programme only with no change to shell and core<br />

• Finishes constrained to the HAL design palette and the standard desk product<br />

established in Terminal 5 to be utilised<br />

• Only passenger facing areas are to be refurbished<br />

• The facility must remain operational throughout construction<br />

• There can be no reduction in the number of functional immigration desks<br />

throughout construction.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Cleaning £0.005M Uplift for glazed finishes & increased numbers of desks<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore information is<br />

indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this project;<br />

• The project is a refurbishment of existing facilities<br />

• BAA will provide a facility within which UKBA can meet their revised and improved Service<br />

Level Agreements however there is no commitment from UKBA to uplift immigration staff<br />

accordingly<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• UKBA are displeased with the ‘standard’ double/ staggered desk arrangement due<br />

to the associated increase in passenger walk time from the queue to the desk. This<br />

desk arrangement is essential to meet requirements for desk numbers and thus to<br />

meet Service Level Agreements. It is understood by all parties that such an<br />

arrangement must be adopted in order to fit the required desk numbers into a<br />

constrained infrastructure. It should be noted that this issue will decline as the<br />

Automated Clearance System is implemented in the future.<br />

• The UKBA desire for the ‘watch-house’ facility to be refurbished however this space<br />

is out of scope and is not a passenger-facing area.<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 106


Appendix A: Overview: Reference Drawing / Image:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 107


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

Immigration Hall Refit<br />

BCT No.: 8563 OP No.: 23826<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £8,393,138 77 %<br />

On-Cost: £1,519,138 14 %<br />

Risk (R1 Allowance only) £947,724 9 %<br />

Total (As entered into Artemis for Feb 09 Month End) £10,860,000<br />

Commentary:<br />

In Scheme Design Stage and a 1st Tier Supplier has not been engaged. Figures include Phase<br />

1 Early Flooring Works<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 108


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

Security Standardisation T3 FCC<br />

0002 : T3 Additional Transfer Security Lanes - SQR<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

The project is about:<br />

• Aligning capacity with post airline relocations capacity<br />

requirements.<br />

• Meet the rising numbers of connecting passengers<br />

• Meet DfT security requirements.<br />

• Standardising of finishes and environment across<br />

<strong>Heathrow</strong> search areas.<br />

• Meet SQR’s for processing passengers.<br />

General arrangement of base option.<br />

Service standard equivalence and SQR’s met.<br />

Airline:<br />

As BAA’s.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Infrastructure Amber Scheme Design<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £12,800,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

02 / 2008 04 / <strong>2009</strong> 12 / <strong>2009</strong> 12 / <strong>2009</strong><br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• Changes in capacity in terminals due to airline relocations<br />

• Comply with Department for Transport (DfT) requirements<br />

• Achieve a common standard of facility across <strong>Heathrow</strong><br />

• Provide additional search lanes, increasing from 5 to 8<br />

• Rationalise staff back of house accommodation to compensate for increased staff<br />

numbers<br />

• Add ticket presentation desks sufficient to safeguard against future changes in<br />

process<br />

• The current airline relocations schedule will remain unchanged and that T3 will go<br />

back to full operation in October 2008<br />

• The staff will work from temporary accommodation whilst their area is being<br />

refurbished.<br />

• DfT requirements will not change.<br />

• There is a requirement for redundancy within the security standardisation guidelines.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 109


Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Security £1.8M The manning of three additional lanes.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• This project is delivering three additional search lanes.<br />

• There is no requirement for ticket presentation.<br />

• The current location will be maintained.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• Closure of the airside road should the “build out” option be selected.<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 110


Appendix A: Overview: Reference Drawing / Image:<br />

This is the build within the existing foot print option;<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 111


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 112


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

T3 Additional Transfer Search Lanes - SQR<br />

BCT No.: 0002 OP No.: 24318<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £8,924,594 70 %<br />

On-Cost: £1,338,689 10 %<br />

Risk (R1 Allowance only) £2,565,821 20 %<br />

Total (As entered into Artemis for Feb 09 Month End) £12,829,104<br />

Commentary:<br />

BCT number 9223 has been generated since month end February <strong>2009</strong>.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 113


Project Name:<br />

Name in<br />

Schedule:<br />

T3 Baggage Hall Refurbishment<br />

8569 : T3 Baggage Hall Refit<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description: This refurbishment project focuses on uplifting the<br />

environment, integrating the new extension, and co-locating<br />

the baggage desks aligned with the available budget.<br />

Ref. Drawings / Images: Overview <strong>Plan</strong><br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA: • Improved passenger experience.<br />

Airline: • As BAA’s.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green Scheme Design<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £11,400,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

10/2007 09/<strong>2009</strong> 09/2010 Continuous<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

The refurbishment will provide a significantly enhanced passenger and user experience<br />

and will support the airline relocation programme and the relocation of oneworld to<br />

Terminal 3. This will be achieved by:<br />

i. Easing congestion whilst improving passenger way-finding and orientation;<br />

ii. Improving utilisation of space for passengers and airline support facilities;<br />

iii. Improving access and egress links;<br />

iv. Modernising the appearance consistent with the BAA design palette;<br />

v. Where appropriate, provision of high-quality lighting and surfaces to receive<br />

lighting.<br />

• HAL Minor Projects are refurbishing toilets and air-conditioning throughout to<br />

provide a complete and consistent refurbishment product<br />

• A refurbishment programme only<br />

• Finishes constrained to the HAL design palette and the standard desk product<br />

established in Terminal 5 to be utilised<br />

• Only passenger facing areas are to be refurbished<br />

• The facility must remain operational throughout construction<br />

Note: Assumptions stated here are to aid understanding and are not necessarily<br />

exhaustive.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 114


Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Cleaning £0.005M Uplift for glazed finishes<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

This project is a refurbishment of existing facilities<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory<br />

decisions and therefore information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• The relocation of airline desks is to consider and respond to the airline relocation<br />

programme and any change associated with it<br />

• A fully operational facility must be maintained throughout the construction<br />

programme<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• A stakeholder request was made to collocate oneworld as part of the refurbishment.<br />

This cannot be accommodated without either enforcing the move of another<br />

alliance or by reducing and thus compromising the oneworld back of house<br />

accommodation. Neither solution is acceptable and therefore oneworld cannot be<br />

collocated until later in the airline moves programme.<br />

• Virgin Atlantic are displeased that their bespoke facility will be replaced with a<br />

standard product which can be differentiated only through branding as defined in<br />

the ‘BAA Branding Guidelines’.<br />

Note: Any disagreement noted must be read in the context of the airline engagement<br />

status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 115


Appendix A: Overview: Reference Drawing / Image:<br />

Please note that the position of airline desks is illustrative only and that endeavours are being made to co-locate by alliance.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 116


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

Baggage Hall Refit<br />

BCT No.: 8569 OP No.: 23827<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £9,372,115 78 %<br />

On-Cost: £1,651,347 14 %<br />

Risk (R1 Allowance only) £916,538 8 %<br />

Total (As entered into Artemis for Feb 09 Month End) £11,940,000<br />

Commentary:<br />

In Scheme Design Stage and a 1st Tier Supplier has not been engaged<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 117


Appendix C: Project Delivery: High Level Project <strong>Plan</strong>:<br />

Brief Decision October 2007 <br />

Options Decision October 2008 <br />

Construction Decision March <strong>2009</strong><br />

Completion Confirmation September 2010<br />

Accounts Finalised November 2010<br />

Trigger Deadline March 2011<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 118


Header Information<br />

Project Name:<br />

Name in<br />

Schedule:<br />

Security Standardisation T3 CSA<br />

9222 : T3 Additional Departures Security Lane<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

The project delivers works in T3 central search to create<br />

standard security product.<br />

General arrangement<br />

Objectives:<br />

BAA: • Aligning capacity with post airline relocations capacity<br />

requirements.<br />

• Meet DfT security requirements.<br />

• Standardising of finishes and environment across<br />

<strong>Heathrow</strong> search areas.<br />

• Meet SQR’s for processing passengers.<br />

Airline: • As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Infrastructure Amber Scheme Design<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £3,600,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

02 / 2008 02 / <strong>2009</strong> 10 / <strong>2009</strong> 11 / <strong>2009</strong><br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• Changes in capacity in terminals due to airline relocations<br />

• Comply with DfT requirements<br />

• Achieve a common standard of facility across <strong>Heathrow</strong><br />

• To roll out a new Premium fast track facility<br />

• Bring an additional search lane<br />

• Rationalise staff back of house accommodation to compensate for increased staff<br />

numbers<br />

• Add ticket presentation desks sufficient to safeguard against future changes in<br />

process.<br />

• The current airline relocations schedule will remain unchanged and that T3 will go<br />

back to full operation in October 2008<br />

• Staff will work from temporary accommodation whilst their area is being<br />

refurbished.<br />

• UK BA embarkation checks will remain airside.<br />

• Shoe scanners will be removed<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 119


Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Security £1.2M The manning of additional lanes.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

o There is the requirement to safeguard for a premium service.<br />

• There will be two main entrances although it is assumed that both will not be open<br />

all the time.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• The use of the CSA Staff Search area by Virgin.<br />

• The temporary disruption to Virgin’s premium dedicated lane.<br />

• The closure of Zone B vertical circulation whilst the slab is in filled.<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 120


Appendix A: Overview: Reference Drawing / Image:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 121


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

T3 Additional Departures Security Lane<br />

BCT No.: 9222 OP No.: 24311<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £2,719,673 76 %<br />

On-Cost: £487,360 14 %<br />

Risk (R1 Allowance only) £360,180 10 %<br />

Total (As entered into Artemis for Feb 09 Month End) £3,567,213<br />

Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 122


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

T4 Airline Relocations<br />

6604 : T4 Airline Relocation<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Office, ramp and CIP accommodation refurbishment to enable<br />

Airline Relocations.<br />

Ref. Drawings / Images: General arrangement plans;<br />

(Refer to Appendix A)<br />

• Ground level<br />

• Mezzanine level<br />

• First floor<br />

• Second floor<br />

Objectives:<br />

BAA: • Enable Airline Relocations<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> Projects Amber Construction Decision<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £27,400,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

01/2007 10/2008 07/2010 Phased<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• The scope comprises the refurbishment and reconfiguration of office, ramp and CIP<br />

Lounge accommodation, creating an environment suitable for the airlines and<br />

handlers moving to Terminal 4 from elsewhere at <strong>Heathrow</strong>.<br />

In summary, the requirements are,<br />

• the creation of extra CIP lounges of circa 14,000sqft,<br />

• the reconfiguration and development of office accommodation including new space<br />

of between 10-20,000sqft<br />

• the reconfiguration and development of ramp accommodation<br />

• Areas are vacated by current tenants in line with an agreed set of dates, based upon<br />

the <strong>Heathrow</strong> Airline Moves sequence.<br />

• Where possible, the refurbishment of office and ramp accommodation will involve<br />

minimal alterations to existing M&E<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 123


per Annum:<br />

Assumed negligible as broadly on change in<br />

tenanted areas<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 124


Appendix A: Overview: Reference Drawing / Image: Ground level HAL-RA-22653-A-A20100<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 125


Appendix A: Overview: Reference Drawing / Image: Mezzanine level HAL-RA-22653-A-A20130<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 126


Appendix A: Overview: Reference Drawing / Image: First floor HAL-RA-22653-A-A20150<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 127


Appendix A: Overview: Reference Drawing / Image: Second floor HAL-RA-22653-A-A20170<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 128


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

T4 Airline Relocation<br />

BCT No.: 6604 OP No.: 22653<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £22,200,349 73 %<br />

On-Cost: £6,152,185 20 %<br />

Risk (R1 Allowance only) £1,951,361 6 %<br />

Total (As entered into Artemis for Feb 09 Month End) £30,303,895<br />

Commentary:<br />

Significantly extended programme (originally late <strong>2009</strong>, now mid/late 2011) is reflected in<br />

increased oncost provision.<br />

Project Team attempting to significantly reduce both programme and associated oncost:<br />

Opportunity up to £800k.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 129


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

T4 Check-In Extension<br />

3831 : T4 Check-in Capacity<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Refurbish and extend T4 check-in<br />

High level layout plan<br />

Objectives:<br />

BAA: • Allow a multi-airline operation to operate from the<br />

terminal in support of airline relocations.<br />

• Enable Skyteam alliance co-location as the anchor alliance<br />

in T4.<br />

Airline: • As BAA’s<br />

• Reduce opex through alliance co-location<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> Projects Green Construction Decision<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £92,130,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

June 2006 October 2007 October <strong>2009</strong> Phased<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

The extension and refurbishment of the T4 Departures Check-In area is designed to:<br />

• Upgrade the passenger experience<br />

• Improve the first impression of T4<br />

• Refurbish the existing check-in area including – floors, ceilings, lighting, check in<br />

desks etc<br />

• Add through an extension 25 meters of additional depth to the check-in concourse<br />

• Add 33 new check-in desks<br />

• Incorporate 64 new ticket desks with back offices<br />

• Include 30 new CUSS units<br />

• Add 1400m2 of accommodation<br />

• Reconfigure the forecourt to include a new pedestrian plaza<br />

• BA will vacate T4 on the dates outlined in the Airlines Relocation Sequence V3.0<br />

• The baggage system refurbishment is completed to programme<br />

• Airlines move in to T4 as per the Airlines Relocation Sequence V3.0<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 130


Revenue / Opex<br />

Cost Area:<br />

Maintenance<br />

increases<br />

Increased Retail<br />

Retail Media<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

The envelope of the building is being extended and<br />

the number of check-in and ticket desks will be<br />

higher, therefore the maintenance costs will<br />

increase. An increase in accommodation will also<br />

affect maintenance costs.<br />

There will be an increase in the number and size of<br />

retail units on the concourse. This should provide<br />

additional revenue. Noting that passenger numbers<br />

and profile has changed with airline relocations.<br />

A small increase in the number of retail media sites<br />

will help to increase revenue.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

Operating processes and compliance documents will be updated in accordance with the<br />

new layout.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 131


Appendix A: Overview: Reference Drawing / Image: Departures Level HAL-RA-22372AE2004<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 132


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

T4 Checkin-In Capacity<br />

BCT No.: 3831 OP No.: 22372<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £88,796,944 84 %<br />

On-Cost: £13,705,818 13 %<br />

Risk (R1 Allowance only) £2,633,333 3 %<br />

Total (As entered into Artemis for Feb 09 Month End) £105,136,095<br />

Commentary:<br />

CBI AFC circa £71.5m<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 133


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

Terminal 4 Refurbishment (CSA etc)<br />

6693 : Terminal 4 Refurbishment<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

The T4 Refurbishment project comprises 3 main areas:<br />

• Expansion and refurbishment of the Central Search Area<br />

(CSA).<br />

• Reconfiguration of retail units and general refurbishment<br />

of the International Departures Lounge (IDL).<br />

• Refurbishment of elements within the Arrivals journey.<br />

CSA: Overview plan<br />

IDL: Overview plan<br />

Arrivals: No plan<br />

BAA: • Increase capacity/efficiency of the CSA.<br />

• Maintain retail income by re-accommodating retail<br />

concessionaires affected by the CSA refurbishment.<br />

• Enhance the passenger experience .<br />

Airline: • Reduce processing times for passengers through CSA<br />

• Enhance customer service standards.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> Projects Amber CSA/IDL – Construction decision<br />

Arrivals – Brief decision<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £22,100,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Decision:<br />

CSA/IDL: 03/2007<br />

Arrivals : TBC<br />

Site:<br />

01/<strong>2009</strong><br />

06/<strong>2009</strong><br />

10/<strong>2009</strong><br />

06/2010<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

10/<strong>2009</strong><br />

06/2010<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• Phased closure of a portion of current CSA, whilst refurbishment is carried out.<br />

• Vacation of a large portion of current retail units by concessionaires.<br />

• Vacation of Terminal 4 by British Airways on agreed dates<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 134


Security<br />

5 additional security lanes will be added, with the<br />

associated resource salary costs and maintenance.<br />

Retail<br />

To be Risk of adverse change in retail revenue.<br />

developed<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

o Expansion of the CSA will produce a greater passenger-facing floor area, requiring<br />

appropriate cleaning and maintenance.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• Proposed scope of the Arrivals refurbishment is currently still being confirmed. The<br />

current budget for this area of the project means that airline expectations exceed<br />

what is actually in plan.<br />

• IDL scope has been rebalanced, based on available budget. Airline expectations<br />

exceed what is actually in plan.<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 135


Appendix A: Overview: Reference Drawing / Image: CSA: HAL-RA-21517-A- SK014_P08<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 136


Appendix A: Overview: Reference Drawing / Image: IDL: HAL-RA-23122-A-I 2000 P5<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 137


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

Terminal 4 Refurbishment<br />

BCT No.: 6693 OP No.: 23122<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £18,197,200 78 %<br />

On-Cost: £3,806,613 16 %<br />

Risk (R1 Allowance only) £1,250,683 5 %<br />

Total (As entered into Artemis for Feb 09 Month End) £23,254,496<br />

Commentary:<br />

Scope includes various workstreams at differing stages of delivery - CBI contract value to be<br />

concluded<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 138


Header Information<br />

Project Name:<br />

Name in<br />

Schedule:<br />

Terminal 4 Victor Pier<br />

8275 : T4 Victor Pier Refurbishment<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

The T4 Victor Pier project comprises of replacing all the<br />

flooring and skirting along the entirety of the Victor Pier,<br />

including Fixed Links and Nodes, Gate Areas.<br />

Ref. Drawings / Images: Victor Pier overview, and the project phases.<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA: • Significantly enhance the passenger experience along<br />

both the Arrivals & Departure route<br />

Airline: • As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> Projects Amber Brief decision<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £3,300,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

Sept 2008 02/03/09 15/05/09 15/05/09<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• Advantage taken of low passenger numbers until October <strong>2009</strong> allows the closure<br />

of Victor Pier to passengers enabling allow day and night works and a shortened<br />

programme (from 30 to 13 weeks)<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

Assumed nil impact<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 139


project;<br />

• Cleaning equipment will be same as required for existing node flooring i.e no new<br />

equipment required<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• Nil in particular – greater degree of refurbishment and replacement of Gate Area<br />

desks has been discussed, but is not in scope<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 140


Appendix A: Overview: Reference Drawing / Image:<br />

Victor Pier Flooring Programme Phase 1<br />

Departures<br />

Corridor<br />

Closed<br />

Toilet Refurbishment<br />

completed during closure<br />

Stand 22<br />

Open for<br />

Arrivals only<br />

Node 22<br />

Closed<br />

Stand 23<br />

open for<br />

arrivals only<br />

Node 23<br />

Closed<br />

Stand 24<br />

Closed<br />

Node 24<br />

closed<br />

Stand 25<br />

Closed<br />

Node 25<br />

closed<br />

Arrivals<br />

Stand 22<br />

Open for<br />

Arrivals<br />

Node 22<br />

open<br />

Stand 23<br />

Open for<br />

Arrivals<br />

Node 23<br />

open<br />

Stand 24<br />

open<br />

Node 24<br />

open<br />

Stand 25 closed<br />

Node 25 closed<br />

Proposed Victor Pier Closure for Day Works<br />

02 March to 17 th April<br />

Victor Pier Flooring Programme Phase 2<br />

Departures<br />

Corridor<br />

Open<br />

Stand 22<br />

Open<br />

Node 22<br />

open<br />

Stand 23<br />

Open<br />

Node 23<br />

open<br />

Stand 24<br />

Closed<br />

Node 24<br />

closed<br />

Stand 25<br />

Closed<br />

Node 25<br />

closed<br />

Arrivals<br />

Stand 25 Closed<br />

Corridor<br />

Closed<br />

Stand 22<br />

Open<br />

Node 22<br />

closed<br />

Stand 23<br />

Open<br />

Node 23<br />

closed<br />

Proposed Victor Pier Closure for Day Works<br />

Stand 24<br />

Closed<br />

Node 24<br />

closed<br />

Node 25<br />

closed<br />

20 th April to 15 th May<br />

Flooring works<br />

completed during<br />

nightshift and will<br />

continue after 15 th May<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 141


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

T4 Victor Pier<br />

BCT No.: 8275 OP No.: 23548<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £2,927,463 88 %<br />

On-Cost: £280,255 8 %<br />

Risk (R1 Allowance only) £120,000 4 %<br />

Total (As entered into Artemis for Feb 09 Month End) £3,327,718<br />

Commentary:<br />

Works to be incorporated into adjacent major T4 projects to maximise efficiencies.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 142


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

Terminal 4 Refurbishment (transfers)<br />

9028 : T4 Additional transfer Security Lanes<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Refurbish T4 transfers area.<br />

Ref. Drawings / Images: None<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA: • Improve capacity/efficiency in line with the increase in<br />

airlines moving into T4<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> Projects Amber Options Decision<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £3,000,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Decision:<br />

Options Decision<br />

February 09<br />

Operational Use<br />

Site:<br />

Commences:<br />

TBC October <strong>2009</strong> October <strong>2009</strong><br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

The refurbishment of the T4 Transfers area is designed to:<br />

• Provide efficient, uncluttered, light and airy Transfer area<br />

• Ensure a sufficient number of Archway Metal Detectors (AMD’s) & Security lanes to<br />

meet SQR’s.<br />

• Provide the appropriate number of Transfer desks<br />

• Ensure sufficient space is provided for security comb queuing<br />

• Ensure sufficient space is provided for Transfer desk queuing<br />

• Provide sufficient ancillary accommodation for Control Authorities<br />

• Improve passenger experience<br />

• Improve natural Wayfinding<br />

• The materials and finishes proposed should where possible meet the criteria set out<br />

in the Security Standardisation Document<br />

• The area needs to remain operational during the refurbishment<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 143


Security:<br />

No change<br />

Nil<br />

Currently the modelling shows that no extra AMD’s<br />

are required.<br />

.<br />

Not included in CIP <strong>2009</strong> Publication<br />

Impact on User Charges:<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

o All CAST modelling undertaken is based on the Crimson and Summer 09 schedule<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• Concerns exist from airlines that the refurbishment will not be significant enough to<br />

ensure that the area functions efficiently at all times.<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 144


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

T4 Additional Transfer Security<br />

BCT No.: 9028 OP No.: 24243<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £1,992,344 66 %<br />

On-Cost: £403,062 13 %<br />

Risk (R1 Allowance only) £604,594 20 %<br />

Total (As entered into Artemis for Feb 09 Month End) £3,000,000<br />

Commentary:<br />

Options Stage<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 145


Header Information<br />

Project Name:<br />

Name in<br />

Schedule:<br />

Terminal 4 Flooring<br />

8274 : T4 Flooring<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

The T4 flooring project comprises of replacing all the flooring<br />

and skirting along the entirety of the Arrivals route, including<br />

the Immigration Hall and ramps to the Baggage Reclaim Hall.<br />

<strong>Plan</strong>ned project phases<br />

Objectives:<br />

BAA: • Significantly enhance the passenger experience along the<br />

Arrivals route<br />

Airline: • As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> Projects Green Arrivals – Construction Decision<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £4,200,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

Sept 2008 02/03/09 20/07/09 n/a<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• Alignment with stand closures requested by the Tarmac replacement project<br />

(Airfield/Infrastructure) has driven part of the programme of this project<br />

• Stand Allocation have identified times of ‘dwell’ where the project may take<br />

advantage of quiet times in aircraft movements to accomplish works<br />

• All other works are night works and will have minimal impact to operations<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

Assumed nil impact<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 146


The following points cover the significant operational assumptions related to this<br />

project;<br />

• Cleaning equipment will be same as required for existing node flooring i.e no new<br />

equipment required<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• Immigration Hall refurbishment generally is not comprehensive enough to meet<br />

UKBAs expectations. (i.e request for new desks in IAH) – This discussion is on-going<br />

• No disagreements with Airlines.<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 147


Appendix A: Overview: Reference Drawing / Image:<br />

Proposed Node Flooring Phasing<br />

Node 7<br />

02 nd Mar to 13 Th March<br />

with stand closure<br />

Node 8<br />

19 th May to<br />

23 rd June<br />

Nodes 9 and 10<br />

22 nd June to 10 th<br />

July with stand<br />

closures<br />

Nodes 11 and 12<br />

20 th April to 18 th May<br />

with stand closures<br />

Node 14<br />

18 th May to 8 th<br />

June<br />

Nodes 1 to 3<br />

19 th May to 16 th June<br />

Node 21 only<br />

23 rd Feb to 6 th<br />

March<br />

Node 20 and 21<br />

9 th March to 21 st<br />

April<br />

Node 15 and 16<br />

10 th June to 16 th<br />

July<br />

Node 17 and 19<br />

9 th March to 14 th<br />

April<br />

Node flooring - Freudenburg<br />

Dayshift<br />

Nightshift<br />

•Aligning of Flooring programme to existing Stand<br />

Closures plan<br />

•Night working in other areas to minimise impact<br />

Proposed Conglomerate Flooring Phasing<br />

GL 5 to 25<br />

02 nd Mar to 29 th May<br />

GL 25 to 42<br />

29 th May to 1 st July<br />

Proposal to close corridor<br />

GL 42 to 61<br />

02 nd Mar to 16 th June GL 61 to 64<br />

18 th May to 8 th June<br />

with Stand 12 closure<br />

Transfers corridor<br />

23 rd Feb to 6 th May<br />

Victor Pier Corridor 27 th April<br />

to 15 th May<br />

With Victor Pier closure<br />

Immigration Hall Corridor<br />

22 April to 25 th June Flooring to suit<br />

Immigration hall<br />

programme<br />

Conglomerate flooring phasing<br />

•Night work for minimal impact<br />

•Day shift where possible to speed project delivery<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 148


Appendix B: Project Delivery: Cost Information:<br />

Project Name: T4 Flooring<br />

BCT No.: 8274 OP No.: 23547<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £3,463,590 83 %<br />

On-Cost: £558,692 13 %<br />

Risk (R1 Allowance only) £150,000 4 %<br />

Total (As entered into Artemis for Feb 09 Month End) £4,172,282<br />

Commentary:<br />

Works to be incorporated into adjacent major T4 project to maximise efficiencies.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 149


Appendix E: PDS – Q5 Baggage<br />

Project Definition Sheets – Q5 Baggage<br />

7541 : T4 Post T5 Baggage Operation<br />

1851 : Post T5 Transfer Baggage System<br />

3798 : T4 Sorter Replacement<br />

3801 : T3 Integrated Baggage System<br />

3810 : System Baggage Cx refit T1 - T4<br />

4191 : Manual Handling Aids<br />

7969 : Terminal 4 Open Skies Baggage<br />

8747 : Baggage Integration<br />

8818 : Baggage Transition<br />

0615 : HBS VIVID replacement prog<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 150


Header Information<br />

Project Name: T4 Airline Moves – Phase 1<br />

Name in 7541 : T4 Post T5 Baggage Operation<br />

Schedule<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Baggage system upgrades to facilitate the Terminal 4 Airline<br />

Relocations Programme<br />

None<br />

• Provide a robust & reliable baggage operation within<br />

Terminal 4 that aligns with the functionality agreed under<br />

airline constructive engagement so that Airlines based in<br />

Terminal 4 are not considered to be at a commercial<br />

disadvantage<br />

• Provide facilities that support / facilitate the airline<br />

relocation strategy<br />

• Improve the efficiency of the direct product by reducing<br />

missed bags & departure delays<br />

Airline:<br />

• Service quality equivalence<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green Construction<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £8,800,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

May / 2007 Oct / 2008 May /<strong>2009</strong> May /<strong>2009</strong><br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• This project was developed as part of the overall strategy to improve the Terminal 4<br />

BHS during the optimal delivery window between the BA vacation to Terminal 5 &<br />

the introduction of new airlines as part of the overall <strong>Heathrow</strong> Airline Relocations<br />

Programme.<br />

• Minimal operational disruption during implementation<br />

• The delivery programme has been based on completing the works in a timely<br />

manner to permit operational trials by others prior to implementing the <strong>Heathrow</strong><br />

Airline Relocations Programme.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Cost Revenue (+) / Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 151


Area: Cost (-)<br />

Impact per<br />

Annum:<br />

Assumed negligible.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• The numbers of airlines & handling agents will entail considerable changes to the<br />

baggage process / facilities. The number of handling agents has been assumed to be<br />

limited to four.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• Location of handling agents within baggage hall or satellite facilities<br />

• Number of flight build make up segregations achievable not consistent with current<br />

operational processes<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 152


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name: T4 Post T5 Phase 1 & 2<br />

BCT No.: 7541 OP No.: 23046<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £7,288,436 68 %<br />

On-Cost: £2,993,661 28 %<br />

Risk (R1 Allowance only) £402,719 4 %<br />

Total (As entered into Artemis for Feb 09 Month End) £10,684,816<br />

Commentary:<br />

Total cost excludes £200k banked savings<br />

Only Phase 1 has been approved with a PER £5,616,501.00<br />

Phase 2 is unscoped with and AFC of £5,072,717.00.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 153


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

Post T5 Transfer Baggage System - T5 to T3 to T1/HET<br />

1851 : Post T5 transfer Baggage System<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

An automated DCV transfer baggage system (for in gauge<br />

bags) to operate as an extension to the T5 system extending<br />

to provide a transfer link through to T3 and T1.<br />

<strong>Plan</strong> Layout with key dates<br />

Objectives:<br />

BAA: • Passenger Service improvement (predictability of transfer<br />

baggage process including reduction in missed bag rates,<br />

reduction in minimum connection times)<br />

• Business Improvements (income, health and safety and<br />

environmental efficiencies)<br />

Airline: • Predictability of transfer baggage process<br />

• Reduction in missed bag rates<br />

• Reduction in minimum connection times<br />

• Reduced overall operating costs<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Amber Civil works/tunnelling - Construction<br />

Baggage & Buildings - Scheme<br />

Project Delivery<br />

Current Cost Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £255,700,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Decision:<br />

Start on<br />

Site:<br />

Completion on Site: Operational Use<br />

Commences:<br />

09 / 2007 02 / 2008 03 / 2012 08 / 2011<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• The capacity of the system will be 3000 bags per hour each way with a 15 min peak<br />

of 750 bags<br />

• The current intention is that the Western Interface Building function will be located<br />

within an extended T3 Integrated Baggage building and will provide an integrated<br />

facility and system.<br />

• Construction completion T5 to T3 on 31.08.11and T3 to T1 on 31.03.12 defined as:<br />

The tunnel completed and fully equipped with M&E services with the cart tracks<br />

installed and fully tested to meet the bag through put and 'in system time' trials<br />

(using test bags). Operational readiness will proceed after this completion date.<br />

• At the T5 to T3 milestone completion date discharge from the tunnel at T3 will be<br />

onto docks for onward transport of transfer bags to the T3 baggage system as the<br />

new system will not be fully integrated until December 2011. Docks will also be<br />

used to load bags transferring from T3 to T5 by tunnel.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 154


• Operational readiness will be carried out from 31.08.11 for the fully integrated<br />

system at T5C and the dock arrangement at T3. Operational readiness will then be<br />

carried out again at T3 from 31.12.11 when the new T3 Baggage system is<br />

complete and again from 31.03.12 for the fully integrated systems at T3 and T1<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Baggage Opex c.£4m saving Potential £4m pa saving on the current five terminal<br />

campus Inter Terminal Operation (ITO) van based<br />

baggage service after estimated tunnel opex costs<br />

taken into account. This would be reflected in the<br />

cost per bag charge<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• Overall saving in transfer baggage operation will be achieved but details of system<br />

down time contingency utilising ITO van operation still to be confirmed.<br />

• Out of gauge transfer baggage ITO van service will remain between terminals and<br />

will be utilised in tunnel system down time contingency.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• Airlines have requested a 15 min peak of 1000 bags (against 750 bag agreed design<br />

capacity) for robustness in peak periods but all subject to simulation during design.<br />

Capacity model that was issued and agreed by the Connectivity Airline Working<br />

Group (appointed by JST) in August 2007, based on a statistical approach resulted in<br />

a 15 min demand result of 750 bags max which was expressed as a 3000 bag per<br />

hour capacity. The tunnel diameter and baggage system is sized on this capacity.<br />

The Oneworld audit dated October 2008 states that this approach is sound thus<br />

closing this issue.<br />

• Star Alliance stated at the August 2008 Connectivity Airline Working Group that<br />

until the Eastern Apron Baggage strategy had been agreed they would not agree to<br />

the Eastern Interface Building baggage and building design. EIB basement location,<br />

already agreed in April 2008, and re-confirmed by Star Alliance at the August 2008<br />

Airline Working Group<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 155


Appendix A: Overview: <strong>Plan</strong> Layout with key dates<br />

T5C TBM Launch Chamber<br />

from April 2008<br />

T3 WIB Shaft<br />

from June 2008<br />

T1 EIB Shaft<br />

from September 2008<br />

Open-face TBM Delivery<br />

Tunnel Drive Commences<br />

February <strong>2009</strong><br />

December 2008 T5–T3 Operational – August 2011<br />

Commence Baggage<br />

Installation<br />

January 2010<br />

T3–T1 Operational – March 2012<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 156


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

Post T5 Transfer Baggage System<br />

BCT No.: 1851 OP No.: 16701<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £189,032,535 73 %<br />

On-Cost: £41,527,105 16 %<br />

Risk (R1 Allowance only) £29,303,367 11 %<br />

Total (As entered into Artemis for Feb 09 Month End) £259,863,007<br />

Commentary:<br />

On-costs include a project specific insurance policy which is greater than usual for BAA<br />

<strong>Capital</strong> Projects (circa £3m).<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 157


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

T4 Sorter Replacement<br />

3798 : T4 Sorter Replacement<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Asset replacement of Terminal 4 BHS existing sorters (SAL &<br />

SAR) with a single loop sorter<br />

None<br />

• Provide a robust & reliable baggage operation within<br />

Terminal 4 that aligns with the functionality agreed under<br />

airline constructive engagement:<br />

• Provide greater baggage operational reliability, flexibility &<br />

maintainability<br />

• Fit with future terminal occupancy strategy – multiple<br />

occupancy post BA vacation<br />

Airline:<br />

• Improved operational flexibility by the provision of any input<br />

to any output<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green Construction<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £5,900,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

May / 2007 Oct / 2008 May /<strong>2009</strong> May /<strong>2009</strong><br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• This project was developed as part of the overall strategy to improve the Terminal 4<br />

BHS during the optimal delivery window between the BA vacation to Terminal 5 &<br />

the introduction of new airlines as part of the overall <strong>Heathrow</strong> Airline Relocations<br />

Programme.<br />

• Minimal operational disruption during implementation<br />

• The delivery programme has been based on completing the works in a timely<br />

manner to permit operational trials by others prior to implementing the <strong>Heathrow</strong><br />

Airline Relocations Programme.<br />

• The T4 Open Skies Project & Sorter Replacement will be delivered concurrently<br />

• Required to achieve US Carrier Screening solution within the main baggage hall<br />

• Enables other T4 baggage works including:<br />

o Additional flight build make up chutes<br />

o Additional flight build reclaim<br />

o Transfer feed onto front sorter<br />

• The numbers of airlines & handling agents will entail considerable changes to the<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 158


aggage process / facilities. The number of handling agents has been assumed to be<br />

limited to four.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Cost<br />

Area:<br />

Revenue (+) /<br />

Cost (-)<br />

Impact per<br />

Annum:<br />

Commentary:<br />

To be developed.<br />

See assumptions<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• New sorter will deliver improvements in operational reliability & reductions in<br />

maintenance costs.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 159


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

T4 Sorter Replacement<br />

BCT No.: 3798 OP No.: 22489<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £8,724,948 75 %<br />

On-Cost: £2,555,949 22 %<br />

Risk (R1 Allowance only) £389,764 3 %<br />

Total (As entered into Artemis for Feb 09 Month End) £11,670,662<br />

Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 160


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

T3 Integrated Baggage System<br />

3801 : T3 Integrated Baggage System<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Provide a single modern facility to process all T3 arrivals and<br />

departure baggage.<br />

None<br />

Objectives:<br />

BAA: • Service quality equivalence.<br />

• Improved safety.<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green Options<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £234,100,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Decision:<br />

Start on<br />

Site:<br />

Completion on Site: Operational Use<br />

Commences:<br />

May / 2007<br />

Enabling<br />

~Aug 08<br />

Nov / 2011 Jan / 2012<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

The project shall provide replacement T3 baggage handling facility which has;<br />

• A capacity aligned to 2026 forecasts<br />

• Provides like for like system functionality across the <strong>Heathrow</strong> campus<br />

• Provide screening and processing of baggage in line within European and USE (TSA)<br />

legislative requirements<br />

Provides a safe and efficient operating environment<br />

The project proposes to use new can management technology “automation” and<br />

proposes to phase the implementation of this technology in such that risk is limited. This<br />

new technology requires a new operating model and endorsement by the airlines.<br />

The existing system in Terminal 3 is very cheap to run but this is because it is of limited<br />

capacity and has significantly less functionality than that of the other terminals in<br />

<strong>Heathrow</strong>. An increase in functionality and step increase in capacity could increase the<br />

bag charge. Challenging targets have been placed on the designers in this regard.<br />

The project has been made aware of the challenges surrounding the post 2025 airport<br />

masterplan strategy. This masterplan imposes significant operational boundary<br />

restrictions on the logical site for the new baggage system.<br />

More detailed project objectives are;<br />

• To provide an integrated baggage system which provides integrated make-up<br />

facilities for direct and transfer in/out-bound baggage.<br />

• To provide a solution which has a modular expandable design construction<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 161


philosophy in line with the phasing strategy.<br />

• To provide an Early Bag Store<br />

• To provide any input to any output functionality<br />

• To meet the H&S requirements for a safe environment that meets BAA standards –<br />

including manual handling<br />

• To provide a HBS operation that is equivalent to those in other HAL terminals, in<br />

line with Department for Transport (DfT) requirements, which also provides OPEX<br />

savings.<br />

• To provide secure and reliable SAC & SCADA systems, comparable to those in other<br />

<strong>Heathrow</strong> Terminals<br />

• To meet <strong>Heathrow</strong>’s intra-terminal transfer target as defined in the <strong>Heathrow</strong><br />

Baggage Product Service Level Agreement.<br />

• To meet <strong>Heathrow</strong>’s inter-terminal transfer target MCT as defined in the <strong>Heathrow</strong><br />

Baggage Product Service Level Agreement.<br />

• To provide expedite facilities.<br />

• To provide tug charging facilities in a suitable orientation and location to be agreed<br />

with the airlines<br />

• To provide airline office accommodation and appropriate levels of handling staff<br />

accommodation giving due consideration to impact of automation. Airline<br />

accommodation should be a “like for like” fitout specification with new for old<br />

replacements for equipment currently owned and maintained by BAA.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

Being evaluated as part of options stage work<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• Automation will be accepted by the airline unions<br />

• Automation (part 1 and 2) technology can be proven in the airport environment<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• Confidence in automation of can management needs to be provided<br />

• Staff training and staffing level changes need to be managed carefully<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 162


Appendix A: Overview: Reference Drawing / Image:<br />

Early option 10 solution<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 163


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

T3 Integrated Baggage<br />

BCT No.: 3801 OP No.: 22380<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £185,229,000 78 %<br />

On-Cost: £36,364,461 15 %<br />

Risk (R1 Allowance only) £14,572,000 6 %<br />

Total (As entered into Artemis for Feb 09 Month End) £236,165,461<br />

Commentary:<br />

Figures based on DL Cost Model Nr 3 (Rev 2) which include £27,002,000 for WIB which is<br />

due to be transferred out to the Cross Campus Connectivity Project<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 164


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

T1-T4 Tunnel Refurbishment<br />

3810 : System Baggage Cx refit T1 – T4<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Extension of serviceable life of automated connectivity<br />

baggage system between T1 & T4<br />

None<br />

• Replacement of time expired controls & re-life the facility<br />

for a further 10 years<br />

• Reduction in operation & maintenance costs<br />

• Provide greater baggage operational reliability & flexibility<br />

• Provide improved maintainability<br />

Airline:<br />

• Automated connectivity for Terminal 4 airlines to those<br />

located within CTA<br />

• Equivalent inter-terminal MCT’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green Construction<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £8,800,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

May / 2007 Sept / 2008 March /<strong>2009</strong> March /<strong>2009</strong><br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• This project was developed as part of the overall strategy to improve the Terminal 4<br />

BHS during the optimal delivery window between the BA vacation to Terminal 5 &<br />

the introduction of new airlines as part of the overall <strong>Heathrow</strong> Airline Relocations<br />

Programme.<br />

• Minimal operational disruption during implementation<br />

• This project is a ‘trigger’ project – date for completion Jan <strong>2009</strong><br />

• Total closure of tunnel system from Sept 2008 to March <strong>2009</strong> in order that works<br />

can be undertaken in an extended working window.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Cost<br />

Area:<br />

Revenue (+) /<br />

Cost (-)<br />

Impact per<br />

Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 165


Annum:<br />

See assumptions<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• Total closure of tunnel system from Sept 2008 to March <strong>2009</strong> requires ITO van<br />

operation between T1 & T4.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 166


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

T1 T4 Tunnel Cx Refit<br />

BCT No.: 3810 OP No.: 23393<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £6,442,964 72 %<br />

On-Cost: £2,038,769 23 %<br />

Risk (R1 Allowance only) £492,700 5 %<br />

Total (As entered into Artemis for Feb 09 Month End) £8,974,433<br />

Commentary:<br />

Total cost exclude the £150k banked savings<br />

Costs exclude Technical Assurance / System Assurance<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 167


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

Manual Handling (Baggage)<br />

4191 : Manual Handling Aids<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Manual handling equipment within T1, T4 & T5<br />

None<br />

• Supports the over arching baggage strategy to reduce<br />

muscular skeletal injuries & therefore reductions in staff<br />

absenteeism.<br />

Airline:<br />

• As BAA’s.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green Option Development<br />

Project Delivery<br />

Current control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £3,800,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

2006 Oct / 2008 March /<strong>2009</strong> March /<strong>2009</strong><br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

Project is based on a delivery of the following:<br />

• T5 Priority 1 works – Essential Health & Safety works to reduce manual handling risks<br />

as agreed with the HSE using manual handling products e.g. Vaculux system<br />

• T5 Priority 2 works – Non-Essential works to reduce manual handling risks , using<br />

manual handling products<br />

• Test Cell - Test Cell for the automation product provided by INDEC in Belgium<br />

• T4 & T1 Works – Health & Safety works to reduce manual handling risks using existing<br />

Product range<br />

• Future requirements assumed to be included within individual project scopes<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Cost<br />

Commentary:<br />

Area:<br />

Revenue (+) /<br />

Cost (-)<br />

Impact per<br />

Annum:<br />

Opex reduction due to reduction in lost time<br />

due to injury.<br />

See assumptions<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 168


Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• This project will assist in the reduction of muscular skeletal injuries for both BAA &<br />

Airline staff.<br />

• The baggage processing rates will not be compromised by the introduction of this<br />

equipment.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 169


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

Manual Handling Aids<br />

BCT No.: 4191 OP No.: 22654<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £2,581,323 73 %<br />

On-Cost: £789,311 22 %<br />

Risk (R1 Allowance only) £143,162 4 %<br />

Total (As entered into Artemis for Feb 09 Month End) £3,513,796<br />

Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 170


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

T4 Open Skies<br />

7969 : Terminal 4 Open Skies Baggage<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description: Provide an automated US Carrier Screening solution<br />

integrated within the T4 Baggage handling System (BHS)<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

None<br />

Objectives:<br />

BAA: • Provide a robust & reliable baggage operation within<br />

Terminal 4 that aligns with the functionality agreed under<br />

airline constructive engagement<br />

• Provide equivalence for US Carriers operating from T4<br />

with those operating within the CTA i.e. integrated TSA<br />

compliant screening facilities<br />

• Improve the passenger experience by:<br />

• Enable ‘on time’ departures for US Carriers by providing<br />

pre-screening of potential ‘selectee’ passenger transfer<br />

baggage<br />

• Reducing passenger check in waiting time by providing an<br />

integrated solution within the BHS for originating<br />

‘selectee’ passenger baggage<br />

Airline:<br />

• Improved operational efficiency through an automated<br />

solution within the BHS<br />

• Reduction in manual handling of ‘selectee’ baggage<br />

• Reduction in dedicated screening operatives<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green Construction<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £8,300,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

May / 2007 Jan / <strong>2009</strong> May /<strong>2009</strong> May /<strong>2009</strong><br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• This project was developed as part of the overall strategy to improve the Terminal 4<br />

BHS during the optimal delivery window between the BA vacation to Terminal 5 &<br />

the introduction of new airlines as part of the overall <strong>Heathrow</strong> Airline Relocations<br />

Programme.<br />

• This project is not required to facilitate the Airline Relocation Programme.<br />

• The delivery programme has been based on completing the works in a timely<br />

manner to permit intra terminal airline relocations prior to commencement of the<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 171


Airline Relocations Programme.<br />

• This project does not provide additional BHS capacity<br />

• Airlines will modify their Departure Control System (DCS) to enable the necessary<br />

transfer of correct baggage messaging between the BHS & the Baggage<br />

Reconciliation System (BRS)<br />

• OOG US Carriers bags will be processed via an existing OOG facility<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Cost<br />

Area:<br />

Revenue (+) /<br />

Cost (-)<br />

Impact per<br />

Annum:<br />

Commentary:<br />

Assumed negligible.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• None.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• Lack of BAA visibility of TSA approval of the solution & the related security protocols<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 172


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

T4 Open Skies US Carriers<br />

BCT No.: 7969 OP No.: 23392<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £6,410,811 70 %<br />

On-Cost: £2,091,098 23 %<br />

Risk (R1 Allowance only) £662,036 7 %<br />

Total (As entered into Artemis for Feb 09 Month End) £9,163,945<br />

Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 173


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

Baggage Integration<br />

8747 : Baggage Integration<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Integration of the baggage product & assurance across the<br />

programme where not already included within individual<br />

projects scopes<br />

None<br />

• Provide a robust & reliable baggage operation across the<br />

baggage portfolio that aligns with the functionality agreed<br />

under airline constructive engagement:<br />

• Provide greater baggage operational reliability, flexibility &<br />

maintainability<br />

• Fit with future terminal occupancy strategy<br />

• Standard baggage product solutions across the portfolio<br />

Airline:<br />

• Service quality equivalence<br />

• Standard baggage product solutions across the portfolio<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green Various<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £10,000,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Decision:<br />

Start on<br />

Site:<br />

Completion on Site:<br />

Operational Use<br />

Commences:<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• When the baggage programme was created there was recognition that not all<br />

projects included all required costs for assurance and integration. This project was<br />

created to provide budget to cover baggage product integration costs that are not<br />

already included within specific project cost plans.<br />

• There is not yet sufficient clarity on the total package values to be held within<br />

projects to change control the budget out to projects. Future requirements are to be<br />

included within individual project scopes<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Cost<br />

Area:<br />

Revenue (+) /<br />

Cost (-)<br />

Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 174


Impact per<br />

Annum:<br />

To be developed on a project by project<br />

basis.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 175


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

Baggage Integration<br />

BCT No.: 8747 OP No.:<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £0 0 %<br />

On-Cost: £7,000,000 100 %<br />

Risk (R1 Allowance only) £0 0 %<br />

Total (As entered into Artemis for Feb 09 Month End) £7,000,000<br />

Commentary:<br />

Holding account to cover Baggage Operational Readiness and Technical Assurance costs that<br />

are not already provisioned for in specific cost plans.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 176


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

Baggage Transition<br />

8818 : Baggage Transition<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Baggage programme transition across the baggage portfolio<br />

None<br />

• Provide a robust & reliable baggage operation across the<br />

baggage portfolio that aligns with the functionality agreed<br />

under airline constructive engagement:<br />

• Provide greater baggage operational reliability, flexibility &<br />

maintainability<br />

• Fit with future terminal occupancy strategy<br />

• Standard baggage product solutions across the portfolio<br />

Airline:<br />

• Service quality equivalence<br />

• Standard baggage product solutions across the portfolio<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green Various<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Expenditure (Constant Prices): £16,830,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Decision:<br />

Start on<br />

Site:<br />

Completion on Site:<br />

Operational Use<br />

Commences:<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• The Baggage & Flight Connections Programme was created after the Q5 CIP was<br />

set. To create the programme, scope was transferred from other programmes and<br />

from within existing projects. This project is a holding account in recognition that<br />

the projects created from this exercise may not include all user requirements. This<br />

fund is used to provide budget currently being ‘transitioned’ between baggage<br />

projects and to re-balance the baggage programme budget post Q5 CIP.<br />

• There is not yet sufficient clarity on the total package values to be held within<br />

projects to change control the budget out to projects.<br />

• Future requirements are to be included within individual project scopes<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Cost<br />

Area:<br />

Revenue (+) /<br />

Cost (-)<br />

Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 177


Impact per<br />

Annum:<br />

To be developed on a project by project<br />

basis.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 178


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

Baggage Transition<br />

BCT No.: 8818 OP No.:<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £0 #DIV/0! %<br />

On-Cost: £0 #DIV/0! %<br />

Risk (R1 Allowance only) £0 #DIV/0! %<br />

Total (As entered into Artemis for Feb 09 Month End) £0<br />

Commentary:<br />

Baggage Transition is an Account set up to hold budget currently being “Transitioned” between<br />

projects. This is being used by the leadership team to “Re-Balance” the baggage programme<br />

budget<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 179


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

HBS Vivid Replacement<br />

0615 : HBS VIVID replacement prog<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Asset replacement of time expired Hold Baggage Screening<br />

equipment across <strong>Heathrow</strong><br />

None<br />

Objectives:<br />

BAA: • Supports the over arching baggage strategy to deliver fully<br />

integrated design builds within terminal baggage halls<br />

• Minimise operational risk by replacement of time expired<br />

assets with new technology<br />

• Maintain <strong>Heathrow</strong>’s licence to operate from DfT by<br />

meeting required security standards<br />

• Improvements in operational reliability, flexibility &<br />

maintainability<br />

Airline:<br />

• Improved operational efficiency through matrixed screening<br />

machines – thus reducing airline screening operators<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green Construction<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £43,100,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

May / 2007 Jan / <strong>2009</strong> May /<strong>2009</strong> May /<strong>2009</strong><br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• Project is based on a phased strategy of ‘just in time’ replacement of time expired<br />

assets<br />

• Excludes replacement of any HBS machines within Terminal 3 as these are deemed<br />

to be included within the T3 Integrated Baggage Project scope<br />

• This project is not required to facilitate the Airline Relocation Programme.<br />

• Elements of the project within Terminal 4 BHS have been planned to be completed<br />

during the optimal delivery window between the BA vacation to Terminal 5 & the<br />

introduction of new airlines as part of the overall <strong>Heathrow</strong> Airline Relocations<br />

Programme.<br />

• This project does not provide additional BHS capacity<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 180


Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Cost<br />

Commentary:<br />

Area:<br />

Revenue (+) /<br />

Cost (-)<br />

Impact per<br />

Annum:<br />

Assumed negligible to minor reduction in<br />

opex as replacement of existing assets with<br />

new equipment.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• New technology will deliver improvements in operational reliability & reductions in<br />

maintenance costs<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 181


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

HBS Replacement<br />

BCT No.: 615 OP No.: 18490<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £41,110,276 73 %<br />

On-Cost: £12,402,614 22 %<br />

Risk (R1 Allowance only) £2,656,697 5 %<br />

Total (As entered into Artemis for Feb 09 Month End) £56,169,587<br />

Commentary:<br />

The AFC includes the HBS Direct, HBS Transfer and HBS T1 projects.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 182


Appendix F: PDS – Q5 Infrastructure<br />

Project Definition Sheets – Q5 Infrastructure<br />

Airfield<br />

1832 : Cargo Tunnel Refurbishment<br />

3817 : South East Taxiways<br />

2809 : A380 Taxiways around Pier 1<br />

3353 : Major Fire Appliance Replacement<br />

7206 : T2B NE Stands & Taxilanes<br />

7656 : Additional Jetty provision<br />

8857 : Taxiway / CDS Rebuilds (Q5)<br />

CWF<br />

3428 : CO2 Strategy<br />

6527 : HAL Minor Projects (Incl Retail & Property)<br />

FLI<br />

6136 : PiccEx Station Works<br />

4369 : Landside CTA Redevt Strategy<br />

7050 : N1 Car Parking Decking Project<br />

7718 : Eastern Maint Base Redev<br />

Security<br />

5056 : Physical Perimeter Security<br />

4242 : Self Service Boarder Control<br />

4185 : Cargo Area RZ Road (T5-T4 Rout<br />

8452 : Control Post Programme<br />

8801 : CP5<br />

9105 : Next Generation Autotray System<br />

9213 : Security Projects<br />

Retail<br />

7049 : JCD Media Sites<br />

Utilities<br />

7666 : Energy Infrastructure<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 183


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

Cargo Tunnel Refurbishment – Q5<br />

1832Cargo Tunnel Refurbishment<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

“Light Tough” refurbishment of the cargo tunnel.<br />

Location <strong>Plan</strong> and images<br />

Objectives:<br />

BAA:<br />

Maintain a safe airside operational link between CTA, T4 and<br />

Cargo.<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Amber Explore<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £ 3,100,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

01 / <strong>2009</strong> 05 / <strong>2009</strong> 06 / 2010 -<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• Constructed in 1966, the Cargo Tunnel comprises a single bore 10.29m dia. Tunnel<br />

approximately 885m in length. The tunnel is in operation 24 hours a day, 7 days a<br />

week and forms a critical link between the Cargo Area / T4 and the CTA.<br />

• Although driven initially by the need to replace an obsolete lighting system, this<br />

project will review all elements of the tunnel infrastructure as well management<br />

process and procedures against current operational risk. This will in turn inform a<br />

prioritised scope of work to be delivered by projects in Q5 and Q6 to progressively<br />

and methodically mitigate business risk, improve passenger experience and extend<br />

the life of the tunnel.<br />

• provide a safe, efficient and reliable route between the Southern Campus and the<br />

CTA, ensuring that the Cargo Tunnel meets all necessary Regulations and applicable<br />

H&S guidelines.<br />

• carry out essential repairs and maintenance to ensure the structural integrity of the<br />

Cargo Tunnel<br />

• supply and install new equipment to meet necessary Regulatory and compliancy<br />

guidelines<br />

• ensure that O&M plans (inc. Emergency orders) are aligned and appropriate to the<br />

level of risk<br />

• ensure the operational availability of the Cargo Tunnel for our key stakeholders<br />

• ensure the existing and any new Cargo Tunnel plant and equipment utilises current<br />

efficiencies in operation and energy consumption<br />

• The project will review all elements of the tunnel including<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 184


• Structure & Civils<br />

• M&E (Ventilation, Lighting, Fire/smoke dampers)<br />

• Drainage<br />

• Systems (Air quality monitoring, Fire detection, comms, etc)<br />

• Management systems and operational protocols will be reviewed simultaneously.<br />

• It is assumed that interfaces with the proposed T2 district heating project can be<br />

effectively managed with no adverse impact on the operation.<br />

• It is further assumed that the QDR does not highlight significant high priority items<br />

needing attention in Q5, requiring funds over and above the budget allowance.<br />

• The tunnel is in use 24 hours a day, 7 days a week.<br />

• Access for inspections & maintenance of trafficked areas is limited to the runway<br />

dealternation pattern, when vehicles can be diverted across the surface during<br />

night-time closure of the southern runway.<br />

• Opportunities to divert vehicles out of hours via the T5 road system will also be<br />

investigated.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Revenue £ nil This project will not result in any change to revenue<br />

streams.<br />

Op ex +£1m The recorded maintenance costs for the cargo<br />

tunnel in 2007 were £165k.<br />

Using an industry standard “rule of thumb”, the<br />

O&M cost for the cargo tunnel is expected to be<br />

circa. £1.2m – 1.5m. Once enhanced practices<br />

enabled by this project are put into place.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 185


Appendix A1: Overview:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 186


Appendix B: Project Delivery: Cost Information<br />

Project Information<br />

Project Name:<br />

Cargo Tunnel Refurbishment<br />

BCT No.: 1832 OP No.: 24271<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £2,310,000 74 %<br />

On-Cost: £490,000 16 %<br />

Risk (R1 Allowance only) £321,311 10 %<br />

Total (As entered into Artemis for Feb 09 Month End) £3,121,311<br />

Commentary:<br />

Project in early stages to establish work required. Assumed 20% Risk allowance (less R2) &<br />

14% On-cost<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 187


Appendix C: Project Delivery: High Level Project <strong>Plan</strong>:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 188


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

South East Taxiway<br />

3817 : South East Taxiways<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Upgrade and realignment of taxiways in SE portion of Eastern<br />

Airfield.<br />

Ref. Drawings / Images: Overview plan<br />

Objectives:<br />

BAA: • Enhanced airfield operations especially on 27L holds.<br />

• Improved airline operation.<br />

• Improved passenger experience.<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green Manufacture & Assemble<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £60,800,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

10/2006 01/2008 10/2010 See below<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• This project forms part of the Eastern Campus programme, providing airfield<br />

infrastructure to support the Eastern Apron Development and full Code F (A380)<br />

operations. It is a key enabler, and on the critical path, for the T2A and T2B<br />

developments; creating the necessary construction space and providing pit and duct<br />

routes for services. The project phasing is aligned with the requirements of these<br />

projects.<br />

• This project creates the required space for the Eastern Apron Development by<br />

realigning the main Alpha and Bravo taxiway system in the South east corner of the<br />

airfield, including: new taxiway construction, reconfigured 27L holds, and provision<br />

of major service ducts for T2A and T2B.<br />

• The business benefit of this project relates to: maximising the developable space on<br />

the airfield, providing re-lifed infrastructure, creating a Code F (A380) compatible<br />

taxiway system, and maintaining sufficient holding capacity for an efficient runway<br />

operation. The reconfigured 27L Hold solution does not compromise potential longterm<br />

future Eastern Apron Developments.<br />

• The phases of this project will be delivered on the following dates:<br />

• Phase 1A: 23 rd January <strong>2009</strong><br />

• Phase 1C: 23 rd January <strong>2009</strong><br />

• Phase 2: 19 th April <strong>2009</strong><br />

• Phase 3A: 16 th June <strong>2009</strong><br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 189


• Phase 3B: 10 th September <strong>2009</strong><br />

• Phase 3C: 11 th April 2010<br />

• Phase 4: 4 th January 2010<br />

• Phase 5: 11 th April 2010<br />

• Phase 6: 30 th September 2010<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Maintenance Nil Areas of new pavement equate closely to the<br />

original area therefore no significant change in<br />

maintenance costs<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 190


Appendix A: Overview: Reference Drawing / Image:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 191


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

South East Taxiways<br />

BCT No.: 3817 OP No.: 22333<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £57,086,788 88 %<br />

On-Cost: £6,263,293 10 %<br />

Risk (R1 Allowance only) £1,757,191 3 %<br />

Total (As entered into Artemis for Feb 09 Month End) £65,107,273<br />

Commentary:<br />

Works undertaken Q4 (Before 1st April 08) £1,709,367.00<br />

Works undertaken Q5 ( 1st April 08 to 31st March 2013) £63,397,905.99 (AFC less Q4<br />

VOWD)<br />

<strong>Plan</strong>ned works Q6 (1st April 2013 onwards) - £0<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 192


Appendix C: Project Delivery: High Level Project <strong>Plan</strong>:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 193


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 194


Header Information<br />

Project Name: A380 Taxiways Around Pier 1<br />

Name in 2809 : A380 Taxiways around pier 1<br />

Schedule<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Removal of the 160 stands and the Eastern Apron<br />

Development has created a temporary shortfall in Terminal 3<br />

JW stands. This project will enable the airline relocations and<br />

partially address the shortfall by providing three 757 coaching<br />

stands and one remote JW stand, relocating the BA 757 fleet,<br />

and freeing up T3 JW stands for wide bodied aircraft.<br />

See Appendix A<br />

Objectives:<br />

BAA: This project will replace three medium stands with two 757<br />

remote stands. A remote JW stretch stand with MARS for<br />

two more 757-200s, and a further remote 757 stand. Thus<br />

three pier served stands are replaced with three remote stands<br />

able to accommodate the larger 757-200 aircraft.<br />

Airline: This project will allow stand planners to allocate the BA 757<br />

fleet to these stands freeing up the larger stands for widebodied<br />

aircraft<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions<br />

Manufacture & Assemble<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £9,400,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

17/03/2008 22/06/<strong>2009</strong> 01/2011<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

The phases of this project will be delivered on the following dates:<br />

Phase 10A<br />

<strong>Plan</strong>ned start on site: 22 nd June <strong>2009</strong> (Phase 10A)<br />

<strong>Plan</strong>ned finish on site: 19 th December <strong>2009</strong> (Phase 10A)<br />

Phase 10B<br />

<strong>Plan</strong>ned start on site: September 2010 (Phase 10B)<br />

<strong>Plan</strong>ned finish on site: January 2011 (Phase 10B)<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 195


Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

Maintenance Nil There will be no incremental income. The OPEX will<br />

not measurably change.<br />

Impact on User Charges:<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 196


Appendix A Area Locations<br />

Phase 10A<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 197


Phase 10B<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 198


Appendix B: Project Delivery: Cost Information<br />

Project Information<br />

Project Name:<br />

Enter the Artemis Project Name here<br />

BCT No.: 2809 OP No.: 23851<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £7,767,426 77 %<br />

On-Cost: £1,522,271 15 %<br />

Risk (R1 Allowance only) £755,954 8 %<br />

Total (As entered into Artemis for Feb 09 Month End) £10,045,651<br />

Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 199


Appendix C: Project Delivery: High level Project <strong>Plan</strong><br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 200


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 201


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

Major Fire Appliance Replacement<br />

3353 : major Fire Appliance Replacement<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Replacement of elements of HAL Fire appliance fleet.<br />

Ref. Drawings / Images: None.<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Maintain Safety, and statutory fire coverage compliance<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Red Explore<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £5,000,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

05/2008 05/<strong>2009</strong> 05/2012 05/2010<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• The BAA major fire appliance fleet is on average, 13 years old. This project is<br />

exploring the options for replacing and/or refurbishing the major fire appliance fleet<br />

for <strong>Heathrow</strong>, Gatwick, Stansted and Southampton. Additionally, the option to<br />

include the Scottish airports is being reviewed. The Total <strong>Capital</strong> Expenditure figures<br />

used are for <strong>Heathrow</strong>.<br />

• All existing major fire appliances will need to be replaced or refurbished over the<br />

next 5 years. It is expected that the supplier will only be able to provide 4 or 5<br />

appliances a year.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Revenue<br />

Nil<br />

Opex Costs Unknown Maintenance costs are increasing as the vehicles<br />

continue to age, therefore a new fleet will have an<br />

input on maintenance costs, but the costs are not<br />

significant.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 202


None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• The new appliances will reduce maintenance costs. Additionally, the new appliances<br />

will comply with current and known future environmental standards<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• Project in explore - no formal discussions with airlines have been held<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 203


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

Major Fire Appliance Replacement<br />

BCT No.: 3353 OP No.: 24092<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £3,698,831 66 %<br />

On-Cost: £784,600 14 %<br />

Risk (R1 Allowance only) £1,120,858 20 %<br />

Total (As entered into Artemis for Feb 09 Month End) £5,604,289<br />

Commentary:<br />

Assumed 20% Risk, 14% On-costs, balance = Base costs. All spends in Q5<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 204


Appendix C: Project Delivery: High Level Project <strong>Plan</strong>:<br />

Brief Decision May 2008<br />

Options Decision February <strong>2009</strong><br />

Construction Decision April <strong>2009</strong><br />

Procurement Contracts May <strong>2009</strong><br />

First refurbished Appliance Dec <strong>2009</strong><br />

First New Appliance April 2011<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 205


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

T2B North East Stands & taxilanes<br />

7206 : T2B NE Stands & Taxilanes<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

Provision of stands and realigned taxiways to the NE of T2B<br />

Overview plan<br />

Objectives<br />

BAA: • Enhance airfield operations especially on 27L.<br />

• Improved airline operations .<br />

• Improved passenger experience.<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green Manufacture & Assemble<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £14,200,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Options<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

03/2007 04/2008 10/<strong>2009</strong> 06/<strong>2009</strong> onwards<br />

NB: phased.<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• The T2B NE Stands & Taxilanes project is part of the Eastern Campus Programme.<br />

• The scope of the project is to supply, install, test, commission and handover the<br />

Apron work outlined below:<br />

1. Construction of 3 new permanent stands 249, 248 & 247.<br />

2. Construction of HoS, interstand and Delta crossing roads.<br />

3. Services infrastructure below Apron to meet needs of stands and MF Pier.<br />

4. Tie into existing taxilane to the East.<br />

5. Tie into new MFPN VCC (Node) Buildings including parking areas and<br />

footpaths.<br />

6. Landscaping of grass area to the North.<br />

NB: AFC now includes significant approved scope change in terms of NW enabling<br />

works being undertaken by this project.<br />

• The phases of this project will be delivered on the following dates:<br />

• Stand 249 – 16 June <strong>2009</strong> (as a remote stand)<br />

• Stands 247 & 248 – 10 Aug <strong>2009</strong> (as remotes).<br />

• Overall Project completion – October <strong>2009</strong>.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 206


Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Opex Nil Areas of new pavement equate closely to the<br />

original area therefore no significant change in<br />

maintenance costs<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 207


Appendix A: Overview:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 208


Appendix B: Project Delivery: Cost Information<br />

Project Information<br />

Project Name:<br />

T2B North East Stands and Taxilane<br />

BCT No.: 7206 OP No.: 22909<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £13,051,799 88 %<br />

On-Cost: £1,474,958 10 %<br />

Risk (R1 Allowance only) £240,988 2 %<br />

Total (As entered into Artemis for Feb 09 Month End) £14,767,745<br />

Commentary:<br />

£314,406 of on-cost, included in the above total, was Q4 expenditure.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 209


Appendix C: Project Delivery: High Level Project <strong>Plan</strong>:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 210


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 211


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

Additional Jetties – Q5<br />

7656 : Additional Jetty Provision<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Provision of additional airbridge jetties in Q6<br />

Location plans for T2, 3, 4 and 5.<br />

• minimise connection times<br />

• maximise customer service by maximising pier service levels<br />

• minimise airline operational costs<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Amber Options<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £4,900,000<br />

Prior to CCRS transfers - Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Decision:<br />

Start on<br />

Site:<br />

Completion on Site: Operational Use<br />

Commences:<br />

05 / 2008 08 / 2008 03 / 2013 01 / <strong>2009</strong><br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• Following consultation with the airline community in 2006/7 a commitment was<br />

made to provide 2 airbridges on all JW stands and 3 airbridges on all JX Stands at<br />

<strong>Heathrow</strong>, by the end of Q6.<br />

• A budget of £ 10.5 was allocated in Q5 to commence this project. The remaining<br />

funds will be allowed for in Q6.<br />

• This Project does not allow for additional provision of Pre-conditioned Air or Fixed<br />

Electrical Ground Power.<br />

• Airbridge costs based on BAA Standard Product and Framework<br />

• Project Management<br />

o Overall strategy to be agreed at the Infrastructure Stakeholder Programme<br />

Board. Project delivery will be managed by local project teams at T2, T3, T4<br />

and T5 consulting with Terminal AOCs at a more detail level regarding<br />

implementation.<br />

• Terminal 2<br />

o The T2A & T2B Projects scope include provision of 2 airbridges on all Code E<br />

(JW) and Code F (JX) Stands.<br />

o This project will fund the provision of additional airbridges to 6 No. Code F<br />

stands in Q5 and a further 5 No. in Q6.<br />

o T2 Phase 2 will allow for 3 airbridges on all Code F stands.<br />

• Terminal 3<br />

o Airbridge supplier can minimise operational impact of installing third jetty on<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 212


Pier 6 stands to levels acceptable to the T3 Airline Community.<br />

• Terminal 4<br />

o Airbridge suppliers are able to meet timescales driven by the taxiway<br />

refurbishment project, taking the opportunity to install additional jetties<br />

during planned stand closures minimising operational disruption.<br />

• Terminal 5<br />

o This project assumes that a third jetty can be installed on stand 565 – this is<br />

to be verified by the T5 team. Based on earlier design studies, the T5 brief<br />

accepted that this would not be possible due to the need to accommodate<br />

the Piccadilly Line extension ventilation fans.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Revenue £ nil This project will not add to Jetty service levels or<br />

revenue in any significant way as airbridges are<br />

being added to current Jetty served stands.<br />

Op ex / Estimated at<br />

+£275 k<br />

Maintenance cost - £10,500 / annum / airbridge<br />

Operating cost - £ tbc / annum / airbridge<br />

20 No. new airbridges to be provided resulting in<br />

an increase of £ (10,500 + tbc) x 22 = £ tbc per<br />

annum<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• Opex based on historic maintenance costs.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• Carriers currently operating A380 aircraft in T3 would like the third airbridge<br />

delivered as soon as possible, and ideally prior to Airline Relocations Step 4. With<br />

the on-going stand closure programme due to the Pier 7 refurbishment project, the<br />

T3 AOC will not accept further stand closures. The project has been challenged to<br />

develop a programme which minimises stand closure to acceptable levels.<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 213


Appendix A: Overview: Scope of Additional Airbridge Project – T2:<br />

n.b. T2A Ph 1 & T2B Project scope - All JW Stands delivered with 2 airbridges<br />

T2A Ph2 & T2C Project scope - include 3 bridges on JX stands and 2 on JW<br />

Q5 Additional Airbridge<br />

T2A T2B Total<br />

JW - - -<br />

JX 1 5 6<br />

Q5 Additional Airbridge<br />

Active Safeguarding<br />

JW<br />

T2A<br />

-<br />

T2B<br />

-<br />

Total<br />

-<br />

JX 2 3 5<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 214


Appendix A: Overview: Scope of Additional Airbridge Project – T3:<br />

Q5 Additional Airbridge Scope<br />

JW<br />

P5<br />

-<br />

P6<br />

-<br />

P7<br />

-<br />

Tota<br />

-<br />

JX - 4 - 4<br />

Assumption: Future development projects at Pier 5, 6 & Pier 7 will allow funding for 2<br />

airbridges on JW stands and 3 on JX stands<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 215


Appendix A: Overview: Scope of Additional Airbridge Project – T4:<br />

Safeguard for JX stand upgrade<br />

Q5 Additional Airbridge Scope<br />

JW<br />

2<br />

JX<br />

2<br />

3 Aug 09 – 23 Oct 09<br />

Block 123 Works<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 216


Appendix A: Overview: Scope of Additional Airbridge Project – T5:<br />

Terminal 5 – Q5 Proposals<br />

Q5 Additional Airbridge Scope<br />

T5A T5B T5C Total<br />

JW - - - -<br />

JX - - 8 8<br />

JW<br />

JX<br />

Q5 Active Safeguarding<br />

T5A<br />

-<br />

T5B<br />

-<br />

T5C<br />

4<br />

Total<br />

4<br />

- - - -<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 217


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

Additional Jetty Provision<br />

BCT No.: 7656 OP No.:<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £3,308,840 76 %<br />

On-Cost: £685,160 16 %<br />

Risk (R1 Allowance only) £360,000 8 %<br />

Total (As entered into Artemis for Feb 09 Month End) £4,354,000<br />

Commentary:<br />

Actual Risk, 14% Oncosts, Balance = Base Costs. Information taken from Mike Bartletts<br />

Archived Risk Summary<br />

.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 218


Appendix C: Project Delivery: High Level Project <strong>Plan</strong>:<br />

Additional Airbridges Project - Proposed Q5/Q6 Scope & Programme<br />

Jetty Served Stand No. Approx Additional Jetties Project<br />

Additional Jetties Project - Q5 Spend<br />

Additional Jetties - Q6 Spend<br />

Terminal Number New / Size Installation Possible Q5 Q6 <strong>2009</strong> 2010 2011 2012 2013 2014 2015 2016 2017 18<br />

Existing Date Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1 Q2 Q3 Q4 Q1<br />

2A - P2 201 New C May-17<br />

2A - P2 203 New JX(m) May-17<br />

2A - P2 205 New JX(m) May-17<br />

New Project - assume<br />

2A - P2 206 New JW May-17<br />

additional airbridge provision<br />

2A - P2 208 New JW May-17<br />

included in project scope<br />

2A - P2 210 New JX(m) May-17<br />

2A - P1 218/9 New JX(m) Feb-17 1 1<br />

Stand initially used for Dom<br />

2A - P1 221 New JX(m) Mar-13 1 1<br />

/ SH flights<br />

2A - P1 223 New JX(m) Feb-17 1 1<br />

2B - P1 231 New JW<br />

2B - P1 232 New JW<br />

2B - P1 233 New JX Oct-13 1 1<br />

Restricted to JW til 2013<br />

2B - P2 234 New JX 1 1 Programme dependant on<br />

2B - P2 235 New JX 1 1<br />

Connectivity solution<br />

2B - P2 236 New JX 1 1 Restricted to JW til thru t/w<br />

2B - P2 238 New JX Nov-12 1 1<br />

2B - P2 239 New JW<br />

2B - P2 241 New JW<br />

2B - P2 242 New JX Jan-13 1 1<br />

2B - P2 243 New JX Jan-13 1 1<br />

2B - P2 244 New JX Nov-16 1 1<br />

2B - P2 246 New JX Feb-13 1 1<br />

2B - P1 247 New JX Feb-13 1 1<br />

2B - P1 248 New JW<br />

2B - P1 249 New JW<br />

3-P6 301 Existing JX Dec-09 1 1<br />

3-P6 303 Existing JX Sep-09 1 1<br />

3-P6 305 Existing JX Oct-09 1 1<br />

3-P6 307 Existing JX Feb-10 1 1<br />

3-P6 309 New JX<br />

All bridges to be provided<br />

3-P6 321 New JX<br />

as part of Pier 6 - P2<br />

3-P6 322 New JX<br />

project<br />

3-P5 323 Existing JW<br />

3-P5 327 Existing JW<br />

3-P5 331 Existing JW<br />

3-P5 342 Existing JW<br />

3-P5 335 Existing JW Jan-14 1 1<br />

3-P5 340 Existing JW Oct-16 1 1<br />

Long term plans show<br />

3-P5 336 Existing JW Nov-16 1 1 changes to these stands,<br />

3-P5 334 Existing JW Jan-17 1 1 therefore likely to be benefit<br />

3-P5 332 Existing JW Feb-17 1 1<br />

is likely to be short<br />

3-P5 328 Existing J<br />

3-P5 326 Existing JW<br />

3-P7 371 New JX Jan 16? -<br />

3-P7 372 New JX Jan 16? -<br />

3-P7 373 New JX Jan 16? -<br />

All airbridges to be provided<br />

3-P7 377 New JX Jan 16? -<br />

as part of the Pier 7 Project<br />

3-P7 378 New JX Jan 16? -<br />

3-P7 379 New JX Jan 16? -<br />

3-P7 380 New JX Jan 16? -<br />

4 402 Existing JW 1 1<br />

Stand closed for taxiway<br />

4 403 Existing JW 1 1 works bet 3 aug & 23 Oct 09<br />

4 405 New JX Underway 1 1<br />

CCRS for £1,037,833 signed<br />

4 406 New JX Underway 1 1<br />

off transferred<br />

4 407 Existing JW 1 1<br />

4 408 Existing JW 1 1<br />

4 409 Existing JW 1 1<br />

4 410 Existing JW 1 1 N.B. Long term plans allow<br />

4 411 Existing JW 1 1 for Stand 410, 411,412 to be<br />

4 412 Existing JW 1 1<br />

upgraded to 2 JX, 1 L<br />

4 422 Existing JW 1 1<br />

4 423 Existing JW 1 1<br />

4 424 Existing JW 1 1<br />

4 425 Existing JW 1 1<br />

5A 514 Existing 1 1 Study reqd. MCA & HoS bag<br />

5A 516 Existing 1 1 may make add a/b imposs,.<br />

5A 518 Existing 1 1<br />

5B 532 Existing JW 1 1<br />

5B 533 Existing JW 1 1<br />

5B 534 Existing JW 1 1<br />

Draft prog - for discussion<br />

5B 535 Existing JW 1 1<br />

with T5<br />

5B 536 Existing JW 1 1<br />

5B 537 Existing JW 1 1<br />

5B 538 Existing JW 1 1<br />

5B 539 Existing JW 1 1<br />

5B 542 Existing JW 1 1<br />

5B 543 Existing JW 1 1<br />

5B 544 Existing JX 1 1 Feasibility to be assessed<br />

5B 545 Existing JX 1 1 due to HoS Baggage - Doc.<br />

5B 546 Existing JX 1 1<br />

T5-OG-DV-VH-246-BB-<br />

5B 547 Existing JX 1 1<br />

00001 refers<br />

5B 548 Existing JW 1 1<br />

5C 552 Existing JW Apr-10 1 1<br />

5C 553 Existing JW Mar-10 1 1<br />

5C 554 Existing JW Mar-10 1 1<br />

5C 555 Existing JX Mar-10 1 1<br />

5C 556 Existing JX Mar-10 1 1 Check stand 556 -..<br />

5C 557 New JX Jun-10 1 1<br />

5C 561 New JX Jun-10 1 1<br />

5C 562 New JX Jun-10 1 1<br />

5C 563 New JX Dec-11 1 1<br />

Stands follow Baggage<br />

5C 564 New JX Dec-11 1 1<br />

Connectivity project works<br />

5C 565 New JX May-10 1 1<br />

5C 566 Existing JW May-10 1 1<br />

66 20 46<br />

JX Jetty Served Stand Active Safeguarding - inc Node and foundations Airbridge Operational Stand Constructio<br />

JW Jetty Served Stand Airbridge Installation Restricted opening of stand<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 219


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

Taxiway and Cul-de-sac Rebuild Q5<br />

8857 : Taxiway ? CDS Rebuilds (Q5)<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

This project represents a financial provision for the rebuild and<br />

rehabilitation of areas of the existing airfield (taxiway system<br />

and cul-de-sacs) that will reach the end of their operational<br />

life during the course of Q5.<br />

Indicative phase 1 location plan<br />

Objectives:<br />

BAA: • Ensure safe airfield operation through correct<br />

maintenance.<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green Ph 1 Manufacture & Assemble<br />

Ph 2 Options<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £16,000,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

16/10/2008 16/02/<strong>2009</strong> 04/12/<strong>2009</strong> 18/12/<strong>2009</strong><br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

Individual projects will be set up to respond to specific requirements as they arise and<br />

these will help to prevent unplanned closures and reduce the risk of Foreign Object<br />

Debris (FOD) from breakdown of the airfield surfaces. Areas of taxiway<br />

rebuilt/refurbished will be relifed by up to 30 years as a result of the works carried out.<br />

Key lower level objectives are;<br />

• To prevent unplanned closures and reduce the risk of Foreign Object Debris<br />

(FOD) from breakdown of the airfield surfaces.<br />

• Ensure airfield capacity (stands, taxiways and runways) is not compromised in<br />

the chosen solution during construction.<br />

• Deliver majority of area within the project before switch 6/7, 27th October<br />

<strong>2009</strong>.<br />

The initial phases of this project will be delivered on the following dates:<br />

Phase 1 construction start: February <strong>2009</strong><br />

Phase 1 construction finish: February 2010<br />

Phase 2 construction start: March 2010<br />

Phase 2 construction finish: December 2010<br />

Phase 1 areas:<br />

• Western Sierra Taxiway – Block 105 & 106<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 220


• Southern Tango Taxiway – Block 123<br />

• Northern Tango and part of Sierra Taxiway – Block 119 & 120<br />

• Block 88 Stopbar<br />

• Northern Runway Access A11<br />

Phase 2 areas:<br />

• Northern Runway Access A10E<br />

• Block 57 (Outer)<br />

• Block 34 (Inner)<br />

• Delta Taxiway between Alpha and Bravo<br />

Note: Assumptions stated here are to aid understanding and are not necessarily<br />

exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Maintenance Nil This project will not increase the total paved area of<br />

the airfield and therefore will not be an incremental<br />

increase in cost to maintain and operate the<br />

taxiway system.<br />

Revenue Nil There is no incremental income directly associated<br />

with this project.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 221


Appendix A<br />

Phase 1 Indicative Locations<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 222


Appendix B: Project Delivery: Cost Information<br />

Project Information<br />

Project Name:<br />

Taxiways / Cul-de-Sac & Runway Access Rehabilitation<br />

BCT No.: 8857 OP No.: 24088<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £13,269,389 83 %<br />

On-Cost: £1,978,444 12 %<br />

Risk (R1 Allowance only) £752,880 5 %<br />

Total (As entered into Artemis for Feb 09 Month End) £16,000,713<br />

Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 223


Appendix C: Project Delivery: High Level Project <strong>Plan</strong>:<br />

Phase 2 Scope of Works is currently at Options Stage<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 224


Header Information<br />

Project Name:<br />

Name on<br />

Schedule:<br />

C02 Strategy<br />

3428 : CO2 Strategy<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA: • Reduce Opex<br />

This project provides a financial provision to improve energy<br />

efficiency in line with the HAL CO2 Strategy via minor projects<br />

None<br />

• Maintain licence to grow through sustainable operations<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Amber Explore<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £4,500,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

Jan <strong>2009</strong> Feb <strong>2009</strong> Mar 2013 Jan <strong>2009</strong><br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• Delivered under Minor Projects banner with spend throughout Q5 when carbon<br />

saving initiative opportunities are identified<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

To be assessed on a project by project basis as<br />

opportunities identified.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 225


Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Header Information<br />

Project Name:<br />

Name on<br />

Schedule:<br />

HAL Minor Projects<br />

6527 : HAL Minor Projects (incl Retail and Property)<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

The Minor Projects portfolio consists of a large number of<br />

small, low value projects rolled up to maximise delivery<br />

efficiencies.<br />

N/A<br />

Support the <strong>Heathrow</strong> operation through investment in<br />

critical assets and facilities.<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> and<br />

Solutions<br />

Green<br />

Various<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £92,300,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Decision:<br />

Start on<br />

Site:<br />

Completion on Site:<br />

Various<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• The prioritisation of projects is carried out annually and focuses on asset<br />

replacement/refurbishment and service enhancement including commercial/retail<br />

areas.<br />

• For information the total number of projects for 2008/09 is circa 100. This rate<br />

continues throughout the quinquennium.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 226


per Annum:<br />

N/A due to minor nature of each project.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 227


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

London Underground T123 Station Enhancement<br />

6136 : PiccEx Station Works<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Including new lifts from platform to ticket hall.<br />

Station refurbishment.<br />

Previously known as “PiccEx Station Works” in CIP 2008<br />

<strong>Plan</strong> layout<br />

Objectives:<br />

BAA: • To increase the flow capacity of T123 London<br />

Underground station.<br />

• Provide usable reduced mobility access to platform level.<br />

Provide a more ambient environment<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> -<br />

Infrastructure<br />

Green<br />

Brief<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £16,600,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

March <strong>2009</strong> November 2011 July 2014 July 2013<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

Background<br />

As part of the delivery of T5, funds were allocated to London Underground for<br />

“remodelling the Terminal 123 Station”<br />

Inclusions<br />

• 2 x 16 person lifts from ticket hall to platform level to provide ‘step free access’<br />

and unlock capacity on the escalators – reducing accident rate.<br />

• A refurbishment of the station is already in plan by LU (using PPP funds).<br />

Remaining funds from the lift project will be used to enhance the refurbishment<br />

project to focus on ambience related items: wall tiling, lighting, new signage.<br />

Exclusions<br />

• Standard communications systems upgrade and ‘deep clean’ refurbishment –<br />

funded by LU.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 228


Revenue / Opex<br />

Cost Area:<br />

Revenue (+) / Cost (-)<br />

Impact per Annum:<br />

None<br />

Commentary:<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

London Underground opex area.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 229


Appendix A: Overview: Reference Drawing / Image:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 230


Appendix B: Project Delivery: Cost Information<br />

Project Information<br />

Project Name:<br />

PicEx Station Works<br />

BCT No.: 6136 OP No.: 0<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £14,130,952 72 %<br />

On-Cost: £3,000,000 15 %<br />

Risk (R1 Allowance only) £2,500,000 13 %<br />

Total (As entered into Artemis for Feb 09 Month End) £19,630,952<br />

Commentary:<br />

Appendix C: Project Delivery: High Level Project <strong>Plan</strong>:<br />

Brief Decision Part of T5 Project – Agreement signed 06<br />

Aug 2004<br />

Options Decision March <strong>2009</strong><br />

Construction Decision August <strong>2009</strong><br />

Start On Site January 2010<br />

Completion<br />

December2011<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 231


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

Landside CTA Roads Redevelopment<br />

4369 : Landside CTA Redevt Strategy<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Q5 landside road modifications in the CTA.<br />

None<br />

Improve the efficiency of the road system within, and leading<br />

to/from, the Central Terminal Area to enhance the surface<br />

access connectivity to the terminals and other points.<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Amber Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £19,300,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

06/<strong>2009</strong> TBC TBC TBC<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• Throughout Q5 and Q6 a requirement exists to redevelop the central terminal area.<br />

This sheet deals with the Q5 scope which is at a very early stage of development.<br />

• It is currently anticipated that the final solution for the CTA will include<br />

redevelopment of the road system within the CTA and potentially a new bus<br />

terminal with links to the Underground and <strong>Heathrow</strong> Express stations and<br />

walkways linking the terminals with the CTA.<br />

• Within Q5 the project will involve facilitating road access to the new T2 MSCP and<br />

carry out service diversions and relocations, building relocation and demolition as<br />

required. The project will review the CTA approach capacity (main tunnel<br />

refurbishment and the Concorde roundabout).<br />

• To be confirmed – the overall master plan is currently in progress. A high level or<br />

grade level forecourt for T2 fundamentally affects the road infrastructure servicing<br />

T2, MCSP2, Bus & Coach Station.<br />

• Interim / temporary road system will be required for the opening date of T2A<br />

• Includes all grade and elevated roads servicing the footprint of the T2 MSCP and<br />

forecourt<br />

• Development of new Public Transport Interchange (PTI) i.e. Bus & Coach Station and<br />

Rail / Tube access is post Q5<br />

• CTA Masterplan is agreed<br />

• Project is to enable opening of T2<br />

•<br />

Project will be complete for T2 opening<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 232


Exclusions (covered by separate PDS’s)<br />

• Demolition of existing T2 car park<br />

• Demolition of control tower and relocation of associated facilities / utilities /<br />

tenants, and relocation of the chapel<br />

• New MSCP2 and T2 forecourt<br />

• New Public Transport Interchange (PTI) i.e. Bus & Coach Station and Rail / Tube<br />

access and walkway connections to terminals & MSCPs<br />

• Cost of modifying and removing the Early Services Gantry<br />

• Cooling Station<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

TBC<br />

TBC<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 233


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

Landside CTA<br />

BCT No.: 4369 OP No.:<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £14,136,198 73 %<br />

On-Cost: £2,900,000 15 %<br />

Risk (R1 Allowance only) £2,300,000 12 %<br />

Total (As entered into Artemis for Feb 09 Month End) £19,336,198<br />

Commentary:<br />

This project is still in strategy (Predominantly roads scope). A more detailed understanding of<br />

the above split will be developed over the next 3 months. Above split is therefore a high level<br />

estimate only<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 234


Header Information<br />

Project Name:<br />

Name in<br />

Schedule:<br />

N1 Parking Deck<br />

7050 : N1 Car Parking Decking Project<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Following an initial study, the project to increase capacity at<br />

the N1 car park is no longer required as assumptions on<br />

which this requirement was based have since changed.<br />

Pending endorsement from the airline community, the<br />

remaining budget (spend to date: £136,706) associated with<br />

this project is to be reassigned to a number of priority<br />

landside infrastructure projects not previously identified in the<br />

Q5 CIP. These projects are likely to result from emerging<br />

Health and Safety Issues as well as the need to comply with<br />

legal commitments.<br />

Ref. Drawings / Images:<br />

They include:<br />

- CTA Main Tunnel<br />

- Fowles Yard<br />

- <strong>Heathrow</strong> Firemain<br />

- Passenger Trolley Issues<br />

None<br />

Objectives:<br />

BAA: • BAA objectives are to<br />

• Comply with legal commitments, legislative and<br />

regulatory requirements<br />

• Replace safety critical-infrastructure<br />

• Support operation to deliver targeted passenger service<br />

standards<br />

Airline: • Not yet consulted upon, but expected to be as BAA’s.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Red Strategy<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £7,600,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

N/A N/A N/A N/A<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

None<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 235


Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Not applicable<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 236


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

Eastern Maintenance Base Redevelopment<br />

7718 : Eastern maint Base Redev<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Airline:<br />

This project is to redevelop the Eastern Maintenance Base to<br />

align with Phase 1 of the Eastern Maintenance Base<br />

Masterplan. The full extent of the scope is to be determined,<br />

but will include as a minimum the diversion of East Church<br />

Road , associated service diversions and<br />

modifications/relocation of facilities effected by the alignment.<br />

Draft layout plan.<br />

Enable growth in the east through the efficient use land<br />

within the airport boundary at <strong>Heathrow</strong>.<br />

Enable future proposed maintenance & fleet operations and<br />

create opportunity for consolidation of operations.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green Options Development<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> budget (Constant Prices): £28,000,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

Aug 2008 Apr 2010 Mar 2013 Jul 2011<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• Divert East Church Road to create a site for the development of a twin bay A380<br />

hangar. Which, facilitates the demolition of Cathedral hangar and construction of<br />

the outer taxiways to create the site for the construction of T2C.<br />

• Agreement will be reached on the timing and implementation of the Restricted<br />

Zone.<br />

• Does not include Phase 2 scope.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

To be assessed through Options Development<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 237


Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None at present, consultation ongoing regarding new Masterplan and revised Trigger<br />

definition and milestone date based on the new scope.<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 238


Appendix A: Overview: Reference Drawing / Image:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 239


Appendix B: Project Delivery: Cost Information:<br />

Project Name: Eastern Maintenance Base<br />

BCT No.: 7718 OP No.: 23923<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £20,484,023 73 %<br />

On-Cost: £4,548,250 16 %<br />

Risk (R1 Allowance only) £3,000,000 11 %<br />

Total (As entered into Artemis for Feb 09 Month End) £28,032,273<br />

Commentary:<br />

AFC above consists of a base cost of £8.67M for Phase I and £12,87M for Phase II. The make<br />

up of the total base cost and the split between Phase I & Phase II will change once the Options<br />

Paper is approved at the end of this month.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 240


Appendix C: Project Delivery: High Level Project <strong>Plan</strong>:<br />

ID<br />

1<br />

Task N ame<br />

<strong>2009</strong> 2010 2011 2012 2013<br />

Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr May Jun Jul Aug Sep Oct Nov Dec Jan Feb Mar Apr<br />

2 Eastern Main ten ance Base Red evelop men t<br />

3 Phase 1<br />

4 Option s Develop men t<br />

8 Scheme Design<br />

12 Prod uction Desig n<br />

16 Manufactu re & Assembly<br />

20 Trigger Milestone Road Div ers ion<br />

30/06<br />

21 Integ rate & L earn<br />

23 Phase 2<br />

24 Explore<br />

28 Option s Develop men t<br />

32 Scheme Design<br />

36 Prod uction Desig n<br />

40 Manufactu re & Assembly<br />

44 Integ rate & L earn<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 241


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

Perimeter Security Projects<br />

5056 : Physical Perimeter Security<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

This project delivers a response on VBIED/PBIED risk on<br />

perimeter fencing and control posts.<br />

Ref. Drawings / Images: Withheld on security grounds<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Migrate security risks to perimeter security.<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green Delivery<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £4,900,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

April 2008 Sept 2008 Mar 2010 Dec 2008<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• Work delivered in phases in line with MATRA risk assessment.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

To be assessed<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 242


The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 243


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

Physical Perimeter Security<br />

BCT No.: 5056 OP No.: 21412<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £4,950,000 100 %<br />

On-Cost: 0 %<br />

Risk (R1 Allowance only) 0 %<br />

Total (As entered into Artemis for Feb 09 Month End) £4,950,000<br />

Commentary:<br />

Phase 1 is forecast to be final accounted at circa £3.35M. Phase 2 scope yet to be defined<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 244


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

Automated Clearance Services – Formerly in the CIP as Self Service<br />

Border Control<br />

4242 : Self Service Border Control<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Installation of automated UK Border Agency ACS Product.<br />

Ref. Drawings / Images: Artists Impression<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Improved passenger experience in the Immigration hall.<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Amber Brief<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £8,600,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

12 / 2008 08 / <strong>2009</strong> 12 / <strong>2009</strong> 12 / <strong>2009</strong><br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

To develop, build and launch ACS at Terminals 1, 3, 4 & 5 by October <strong>2009</strong>.<br />

Within the overall ACS programme there are two service variants. These are defined<br />

by the type of passport passengers already have;<br />

ACS - EEA (UK & EU) passengers with ePassports<br />

• free to use service<br />

• facilitated via face image reconciliation technology stored within the<br />

ePassport and verified at the point of use by UKBA<br />

ACS+ - all passengers without ePassports<br />

• paid for service (reflecting additional enrolment costs incurred)<br />

• facilitated via fingerprint reconciliation technology stored by UKBA and<br />

verified at the point of use by UKBA<br />

This project will:<br />

• will facilitate (ACS & ACS+ combined) 20% of passengers via automatic<br />

gates between <strong>2009</strong> and 2014<br />

• prepare the way for the introduction of 2nd generation ePassports during<br />

2012/13<br />

• de-risk and reduce the impact of the re-introduction of embarkation exit<br />

controls<br />

• deliver sufficient commercial return to balance associated opex<br />

• Installation of 5 x ACS portals (20 in total) within each Immigration Hall<br />

• Installation of 1 x enrolment desk (4 in total) in each Immigration hall<br />

• Removal of equipment to enable installation of the portals and desks<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 245


• Review of the layout of the Immigration Hall to ensure that the passenger flow<br />

and Wayfinding works with the new ACS equipment<br />

• Additional Wayfinding as required<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue (+) /<br />

Commentary:<br />

Cost (-) Impact<br />

per Annum:<br />

See Assumptions<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

BAA related assumptions and constraints:<br />

• Service standards over the period will continue to decline using existing Border<br />

clearance methods<br />

• Border transaction times will continue to increase as more onerous checks are<br />

introduced<br />

• The existing UKBA IRIS scheme will continue to offer low volumes and poor<br />

quality service<br />

• Biometric identity verification will continue to be acceptable to UKBA<br />

• Issue of new ePassports will not exceed 25%pa (currently 10%)<br />

• Frequent travellers (non-ePassport) will continue to pay an annual user fee of<br />

£30<br />

• Associated opex is balanced over the period by ACS+ income<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 246


Appendix A: Overview: Reference Drawing / Image:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 247


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

Self Service Boarder Control<br />

BCT No.: 4242 OP No.: 24187<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £7,320,591 88 %<br />

On-Cost: £728,000 9 %<br />

Risk (R1 Allowance only) £289,770 3 %<br />

Total (As entered into Artemis for Feb 09 Month End) £8,338,361<br />

Commentary:<br />

ACS, ACS+ and CMS cost (i.e. hardware and software) is around £4.7 M and Works to<br />

Immigration hall is around £1.4M. Remainder includes, CBI's Preliminaries and their overhead<br />

and profit. BAA internal charges is included within the Base Cost.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 248


Appendix C: Project Delivery: High Level Project <strong>Plan</strong>:<br />

Brief Decision Dec 08<br />

Present options to Stakeholders Dec 08 – Feb 09<br />

Option Decision Feb 09<br />

Construction Decision Apr 09<br />

Main construction activities commence Jul 09<br />

T3 Open Aug 09<br />

T5 Open Aug 09<br />

T1 Open Nov 09<br />

T4 Open Nov 09<br />

Project completion Nov 09<br />

OR Complete Nov 09<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 249


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

Cargo Area RZ Road<br />

4185 : Cargo Area RZ Road<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

This project will;<br />

• develop a technology solution to monitor/detect/respond<br />

to the current CA/RZ boundary,<br />

• develop a solution for the Royal Suite,<br />

• develop a permanent solution for the LHR Cargo area to<br />

comply with EU legislation.<br />

None<br />

Objectives:<br />

BAA: • to deliver a solution by which the whole of the airside<br />

area of <strong>Heathrow</strong> complies with EC legislation (this<br />

project includes the <strong>Heathrow</strong> Cargo areas and Royal<br />

Suite but excludes the East/West Maintenance Bases).<br />

• to reduce Deficiency Notices to zero.<br />

• to remove the inefficient opex (in the order of £1.5m pa),<br />

dependant on the chosen option, and re-deploy the<br />

security resources elsewhere in the business.<br />

• to introduce screening processes (for qualifying flights) at<br />

the Royal Suite.<br />

• to support performance targets at Control Posts.<br />

• Provide an EU compliant security.<br />

• Reduce opex.<br />

• Maintain operation of related infrastructure (e.g. Royal<br />

Suite).<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Amber Options Development<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £6,200,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

Dec 2008 May <strong>2009</strong> Mar 2012 Sept <strong>2009</strong><br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• Agreement will be reached on the timing and implementation of the Restricted<br />

Zone.<br />

• Does not include the removal of the CA zone in the Eastern Maintenance Base<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 250


Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Security £1.5M To be assessed through Options Development but<br />

value given is indicative if security post can be<br />

removed.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

The airlines are aware that removing the controlled areas from <strong>Heathrow</strong> is not<br />

optional, however there are a number of operators and handlers involved with differing<br />

and conflicting business requirements. It is unlikely that a solution is found which meets<br />

the requirement of all stakeholders and this will lead to disagreement.<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 251


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

Cargo Area RZ Road<br />

BCT No.: 4185 OP No.: 24231<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £4,573,347 74 %<br />

On-Cost: £1,112,436 18 %<br />

Risk (R1 Allowance only) £494,416 8 %<br />

Total (As entered into Artemis for Feb 09 Month End) £6,180,198<br />

Commentary:<br />

This project underwent Brief Decision in December 2008, and is currently in the Options<br />

Development stage. The cost planning process has not yet commenced, and as such the<br />

figures above are provisional and are based on a % calculation of the total AFC.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 252


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

Control Post Programme<br />

8452 : Control Post Programme<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Improve control post facilities to meet Q5 SQR targets.<br />

None<br />

Objectives:<br />

BAA: • Ensure SQR requirements.<br />

• Reduce operational expenditure.<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Amber Explore<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £22,100,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

11/2008 TBC TBC 12/2013<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• This project covers a series of sub projects that will gradually be completed through<br />

Quinquennium 5.<br />

• Base data and forecast traffic demand data is accurate.<br />

• No significant change in master planning activity impacting Control Post programme<br />

delivery.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

To be developed<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 253


None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 254


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

Control Post Programme<br />

BCT No.: 8452 OP No.: 24023<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £18,614,179 75 %<br />

On-Cost: £2,529,436 10 %<br />

Risk (R1 Allowance only) £3,840,653 15 %<br />

Total (As entered into Artemis for Feb 09 Month End) £24,984,268<br />

Commentary:<br />

CP8 & Southside Control Posts Base Cost £11,474,179<br />

Building 1082 Base Cost £750,000<br />

CPQueue Measurement Base Cost £1,350,000<br />

Optimization Base Cost £5,040,000<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 255


Header Information<br />

Project Name: Control Post 5<br />

Name in 8801 : CP5<br />

Schedule<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Enhance control post 5 functionality in support of T2A<br />

consultation and CTA airside access requirements.<br />

None<br />

Objectives:<br />

BAA: • Enable the delivery of the T2A & B project by enabling the<br />

closure of Control Post 4 whilst maintaining sufficient<br />

flow through the CTA<br />

• Satisfy current and future demand while ensuring SQR.<br />

• Queue measurement requirements can be met .<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Amber Construction<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £4,600,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

N/A 04/<strong>2009</strong> 12/<strong>2009</strong> 12/<strong>2009</strong><br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

The T2A/B construction programme determines that the existing CP4 will close in Dec<br />

<strong>2009</strong><br />

• A total of 3 vehicle lanes will need to be provided by December <strong>2009</strong> with a fourth<br />

vehicle lane safeguarded for future growth.<br />

• In order to accommodate the forecast shortfall, options to enhance existing CP5<br />

capacity have been explored resulting in a three lane replacement facility (with<br />

safeguarded space for a fourth lane) having been designed, and space for the new<br />

facility identified (100m south of the existing CP5). The positioning is dictated by<br />

geographic constraints (primarily the ART tunnel) and the need to provide sufficient<br />

queuing length to avoid disruption to the CTA road system. A fourth vehicle lane is<br />

safeguarded and could be provided following the demolition of MSCP2. An agreed<br />

programme of works has been developed for delivery of an operationally ready<br />

Control Post in December <strong>2009</strong> to meet the business requirement<br />

• Accessibility – security roles prohibit disabled staff working in the Control Post<br />

although provisions to ensure accessibility need to be made to accommodate<br />

disabled users<br />

• <strong>Plan</strong>ning permission is granted<br />

• Delivery is integrated with master planning work<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 256


• Design safeguards for ability to expand to a fourth vehicle lane<br />

• Maximum vehicle length of 18 metres (rigid lorry with drawbar trailer)<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Staff cost -£0.19M Saving of 5 FTE’s in security<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• CP5 is a similar size to the existing facilities that it replaces so maintenance and<br />

utilities costs are unchanged.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 257


Appendix A: Overview: Reference Drawing / Image:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 258


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

CP5<br />

BCT No.: 8801 OP No.: 23996<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £3,761,428 76 %<br />

On-Cost: £801,209 16 %<br />

Risk (R1 Allowance only) £415,608 8 %<br />

Total (As entered into Artemis for Feb 09 Month End) £4,978,245<br />

Commentary:<br />

Base Costs CBI Prelims £721k Fee £148k<br />

Substructures £211k, Frame £251k, Roofing £158k, External Walling £114k, Fit-out £236k,<br />

Primary & Secondary services £415k, External Works £570k,IT/Networks £81K, Specialist<br />

Systems £461k<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 259


Appendix C: Project Delivery: High Level Project <strong>Plan</strong>:<br />

Construction of this new control post is design to incorporate the functions currently<br />

undertaken in both existing Control Post 4 & 5 and, whilst its is not linked to a<br />

regulatory trigger, its completion is critical to allow closure of the exiting CP4 and<br />

completion of the demolition of Terminal 2.<br />

The new Control Post will be constructed downstream of the existing CP5 and its<br />

construction will be phased to permit its continued use until the new CP5 comes on<br />

stream.<br />

Release of the area for construction to commence is dependent upon the Eastern<br />

Campus Project completing relocation of the tug charging units & vacating the ramp<br />

accommodation airside on the ground floor of MSCP 2 by 27 th<br />

April <strong>2009</strong> (process<br />

underway to create an Artemis link between the Eastern Campus & CP5 programme of<br />

works).<br />

New CP5 will be fit for operational readiness training to commence on the 7 th October<br />

<strong>2009</strong> allowing the new CP5 to commence operation on the 1 st December <strong>2009</strong>.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 260


Header Information<br />

Project Name:<br />

Name on<br />

Schedule:<br />

Next Generation Autotray System<br />

9105 : Next Generation Autotray System<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Project is to deliver a prototype automatic tray return system<br />

for use at passenger and staff search x-ray machines, followed<br />

by roll-out of new system.<br />

None.<br />

Objectives:<br />

BAA: • Reduce manpower and related opex.<br />

• Reduce manual handling risks in the operation.<br />

• Improved passenger experience.<br />

Airline: • As BAA’s.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Amber Options<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £5,100,00<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

Dec 08 TBC TBC TBC<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• Prototype can be developed and implemented at all security locations.<br />

• Programme for implementation can be developed within operational constraints.<br />

• Prototype delivers the objectives required to enable roll-out throughout <strong>Heathrow</strong>.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Security TBA Objective calls for potential reduction in manpower.<br />

Actual numbers to be developed once prototype<br />

tested.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 261


Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• None.<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 262


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

Next Generation Autotray System<br />

BCT No.: 9105 OP No.: 24230<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £3,737,000 74 %<br />

On-Cost: £909,000 18 %<br />

Risk (R1 Allowance only) £404,000 8 %<br />

Total (As entered into Artemis for Feb 09 Month End) £5,050,000<br />

Commentary:<br />

This project underwent Brief Decision in December 2008, and is currently in the Options<br />

Development stage. The cost planning process has not yet commenced, and as such the<br />

figures above are provisional and are based on a % calculation of the total AFC.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 263


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

Security Projects<br />

9213 : Security Projects<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

This project provides:<br />

• A year on year financial provision to allow the <strong>Airport</strong> to<br />

respond at short notice to changes in legislation from the<br />

DfT which requires a minor capital project to be set up in<br />

order to maintain compliance.<br />

• A response to threats that the airport faces from terrorist<br />

and criminal activities which have been identified by the<br />

<strong>Heathrow</strong> MATRA Working Group.<br />

• Develop solutions to transform security at <strong>Heathrow</strong> in line<br />

with the Q5 Security Strategy.<br />

None Available<br />

Objectives:<br />

BAA: • Maintain a secure airport<br />

• Delivery of the National Aviation Security Policy.<br />

• Reduced security and police opex costs<br />

Airline:<br />

As BAA’s.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Amber Explore<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £19,700,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

May <strong>2009</strong> Jan 2010 Mar 2013 Sept 2010<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

Projects are selected if they meet;<br />

• Agile delivery of security in response top a wide range of threats<br />

• All infrastructure, systems, people and processes combine to deliver robust and agile<br />

security responses<br />

• Agree legislative approach between EC and UK to allow HAL to meet all compliance<br />

requirements.<br />

• Improved technology supports improvements in detection and compliance<br />

• The Security Projects budget does not allow for major projects which are beyond<br />

brief decision at Jan 09 namely: Control Post Programme (BCT 8452), CP5 (BCT<br />

8801), Cargo Area CA/RZ (BCT 4185), Self Service Border Control ACS (BCT 9105),<br />

Next Generation Autotray (BCT 9105), Physical Perimeter Security (BCT 5056). Each<br />

of these projects has a specific PDS.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 264


• The Security Projects budget does allow for minor projects which are beyond brief<br />

decision at Jan 09 namely: Fixed post reduction (BCT 9109), Guard Tour (BCT 5058)<br />

• The Security Project has been formed out of the consolidation of Managed Campus<br />

Security (BCT 4183), Managed Campus Enhanced Security Programme Impl. (BCT<br />

4182), Remote Goods Screening (BCT 8451) to specifically align these projects with<br />

the Q5 Security Strategy. (CCRS approved Feb 09).<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

On a project by project basis<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 265


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

Security Projects<br />

BCT No.: 9213 OP No.:<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £14,253,767 72 %<br />

On-Cost: £3,000,000 15 %<br />

Risk (R1 Allowance only) £2,500,000 13 %<br />

Total (As entered into Artemis for Feb 09 Month End) £19,753,767<br />

Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 266


Header Information<br />

Project Name:<br />

Name in<br />

Schedule:<br />

Media Site Development<br />

7049 : JCD Media Sites<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

The capital spend listed below is made up of various<br />

advertising projects (see attached list) which are part of our<br />

commercial commitment and agreement with JC Decaux, our<br />

Media Agency. All Projects were designed to deliver a strong<br />

media offer at <strong>Heathrow</strong> to keep <strong>Heathrow</strong> at the fore front<br />

of the Outdoor Media Industry and to maximise our Revenue<br />

from Advertising.<br />

None<br />

Objectives:<br />

BAA: • To maintain retail income into the single till.<br />

Airline: • As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> and<br />

Solutions<br />

Project Delivery<br />

Amber<br />

Various<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £3,590,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Decision:<br />

Start on<br />

Site:<br />

Completion on Site:<br />

Operational Use<br />

Commences:<br />

n/a March 2007 March 2014 Various. Some<br />

projects are already<br />

in operation<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

All projects will be managed and delivered by JC Decaux. All technical approvals will be<br />

carried out via the Commercial Services Team. All works will take place at night to<br />

minimise any impact on the <strong>Airport</strong> Operation.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

Assumed nil / negligible.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 267


Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None.<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 268


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

Utilities – Combined Heat and Power (CHP)<br />

7666 : Energy Infrastructure<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

This project will;<br />

• Deliver CHP plant and Infrastructure to support the<br />

Energy demands due to the development in Q5<br />

• Support the <strong>Heathrow</strong> wide Energy Strategy and CO2<br />

Strategy<br />

• Support future development<br />

None Available<br />

Objectives:<br />

BAA: • Define the optimum solution for CHP at <strong>Heathrow</strong><br />

considering CO2 emissions versus value and supporting<br />

the <strong>Heathrow</strong>’s Low Carbon Energy Strategy.<br />

• Reduce <strong>Heathrow</strong> energy supply and energy systems<br />

maintenance costs.<br />

• Support Q6 strategy and future development at<br />

<strong>Heathrow</strong>.<br />

Airline: • Ensure efficient and reliable energy supply.<br />

• CO2 reduction<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Amber Options Development<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £21,500,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

Sept 2008 Jan 2010 July 2012 Dec 2012<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• The budget and scope currently sits in both Eastern Campus and Infrastructure,<br />

however a <strong>Heathrow</strong> wide solution is being developed. This definition sheet only<br />

refers to the budget and the original CIP ID in the Infrastructure Programme.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 269


To be assessed through Options Development<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 270


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

Energy Infrastructure<br />

BCT No.: 7666 OP No.: 23821<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £17,867,851 75 %<br />

On-Cost: £3,500,000 15 %<br />

Risk (R1 Allowance only) £2,500,000 10 %<br />

Total (As entered into Artemis for Feb 09 Month End) £23,867,851<br />

Commentary:<br />

Project at early stages of cost planning & feasibility study. Generally assume average of 15%<br />

on cost calc. A more detailed understanding of the above split will be developed over the next<br />

3 months. Above split is therefore a high level estimate only<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 271


Appendix G: PDS – Q5 Airline Relocations<br />

Project Definition Sheets – Q5 Airline Relocations<br />

7966 : Operational Readiness<br />

7702 : Relocation of Airlines IT Operations<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 272


Header Information<br />

Project Name:<br />

Name on<br />

Schedule:<br />

Airline Relocations<br />

7966 : Operational Readiness<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Airline Relocation Programme – relocation of airlines between<br />

terminals as per the agreed airline relocation sequence<br />

Latest sequence version 3.1 (as at Jan 09)<br />

Objectives:<br />

BAA: • Improve the passenger experience by collocation of<br />

Alliance airlines.<br />

• Allow Airlines and Alliances to grow their business.<br />

Airline: • Airline Alliance Collocation<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Green Delivery<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £10,500,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

N/A Various Various Various<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• Majority of capital is capitalisation of staff costs for the Integration. <strong>Plan</strong>ning and<br />

Ops Trial teams. (Currently FIT/FAM and Migration are revenue costs).<br />

• Other costs include 3 rd party suppliers (ie Premier moves), materials and passenger<br />

communications.<br />

• Funding of “forced” moves for airlines and associated support.<br />

• Does NOT include any project/facility provision or delivery – this sits within other<br />

programmes.<br />

This project is part of the Airline Moves programme for <strong>Heathrow</strong> and involves the<br />

relocation, decommissioning and re-provision of existing IT systems. Relocation<br />

agreements are based on the provision of like-for-like facilities and services.<br />

• Airlines / Handling Agents will fund any changes required to their operation in their<br />

new Terminal as per commercial principals;<br />

• HAL operational impacts (roster changes etc) will be facilitated by the Operational<br />

teams.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) / Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 273


Cost Area:<br />

Cost (-) Impact<br />

per Annum:<br />

Alliance co-location and enabling of T2A introduce<br />

complex changes to opex and revenue which is<br />

generally covered either by specific projects<br />

elsewhere in the CIP or through general business<br />

planning.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 274


Appendix A: Overview: Reference Drawing / Image:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 275


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

Operational Readiness<br />

BCT No.: 7966 OP No.:<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: 0 %<br />

On-Cost: £10,338,300 100 %<br />

Risk (R1 Allowance only) 0 %<br />

Total (As entered into Artemis for Feb 09 Month End) £10,338,300<br />

Commentary:<br />

Essentially all costs associated with this project are BAA staff or other on-cost type allowances.<br />

This project does not fund any physical construction activity and therefore the standard<br />

descriptions above do not apply.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 276


Header Information<br />

Project Name:<br />

Name in<br />

Schedule:<br />

Airline Relocation Systems<br />

7702 : Relocation of Airlines IT Operations<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Works on airline IT systems to enable Airline Relocations<br />

None<br />

Objectives:<br />

BAA: • Improve the passenger experience by collocation of<br />

Alliance Airlines.<br />

• Allow Airlines and Alliances to grow their business.<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

IT<br />

Step 3 - Green Complete<br />

Step 4 - Green Integrate & Learn<br />

Step 4a - Green Manufacture & Assembly<br />

Step 5 - Green Production Design<br />

Step 6 - Green Production Design<br />

Step 7 - Green Production Design<br />

Step 9 - Green Explore<br />

Step 9a - Green Explore<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £25,200,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

11/2007 03/2008 08/2010 07/2008 (As per<br />

move sequence 3.1)<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

The project was developed as part of the overall strategy to deliver the Airline Moves<br />

Programme. The business objectives of Airline Moves are to:<br />

• Enable closure of T2 to support HET delivery<br />

• Improve the transfer product through collocation of alliances<br />

• Ensure competitive equivalence post T5 opening<br />

• Ensure robust operations post T5 opening<br />

Create opportunities for growth<br />

This project is part of the Airline Moves programme for <strong>Heathrow</strong> and involves the<br />

relocation, decommissioning and re-provision of existing IT systems. Relocation<br />

agreements are based on the provision of like-for-like facilities and services.<br />

The scale of these works and the potential for operational disruption is greater than any<br />

prior systems project at <strong>Heathrow</strong>, as the works contain Airline, Terminal, Ground<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 277


Handler and <strong>Airport</strong> related activities. The airlines cannot fulfil their operational activities<br />

and run their business without their supporting IT systems. Many Airlines share the same<br />

hosting services and the same service providers and ground handlers. Relocation<br />

agreements are based on the provision of like-for-like facilities and services. As a result<br />

the Airline Moves programme requires a supporting Systems work-stream, both to<br />

prove systems operationally and to relocate airlines with minimal operational disruption.<br />

• The Airlines have been consulted and are supportive.<br />

• Airlines move to agreed schedule.<br />

• Like for like systems replacement/re-provision only.<br />

• All Operation requirements are managed through other work streams within the<br />

Airline Moves Programme<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

See Assumptions<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact: N/A<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

o Like for like provision assumes no increase in Opex.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 278


Appendix B: Project Delivery: Cost Information:<br />

Airline Relocations Systems (23198)<br />

Construction Decision (Phase 3)<br />

PROJECT COST PLAN SUMMARY m2 GFA =<br />

Anticipated<br />

Final Cost (£k)<br />

Cost/m 2<br />

GFA<br />

Total Project Costs<br />

(£/m2)<br />

%<br />

Project Specifics<br />

Airline Costs per step:<br />

Pre Step 3 (TAM) 300 1%<br />

Step 3 1,098 5%<br />

Step 4 2,115 9%<br />

Step 4a 782 4%<br />

Step 5 1,339 6%<br />

Step 6 - 0%<br />

Step 7 2,552 11%<br />

Step 9 772 3%<br />

Step 9a 327 1%<br />

T4 Common Infrastructure 2,659 12%<br />

Airline Paging System (APS) 2,750 12%<br />

Project Specific Cost Sub-Total 14,694 66%<br />

Project Design & Management Costs<br />

BAA<br />

Technical & Solution Assurance 238 1%<br />

HAL IT Systems 235 1%<br />

Heighten Support 250 1%<br />

Programme Management, Delivery & Controls 950 4%<br />

Programme Development 505 2%<br />

Systems Integration 1,870 8%<br />

D & M Cost Sub-Total 4,048 18%<br />

Risks 3,172 14%<br />

Inflation 349 2%<br />

TOTAL PROJECT COST 22,263 100%<br />

Note: The total AFC in this support information does not match that in the schedules. This<br />

project is in the process of preparing for revised funding approval and has revised AFC,<br />

downwards, since February month end.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 279


Appendix H: PDS – Q5 IT / Systems<br />

Project Definition Sheets – Q5 IT / Systems<br />

Telecomms Programme<br />

3606 : Telecoms Programme<br />

Central IT<br />

IT01 : <strong>Airport</strong> Operational Systems<br />

IT02 : IT Infrastructure Renewal<br />

IT03 : Business <strong>Plan</strong>ning & Support IT<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 280


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

HAL Telecoms Strategic Deployment Programme<br />

3606 : Telecoms Programme<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Replacement of the Data Network to remove red risks and<br />

provide a more reliable and resilient network for all customers<br />

at <strong>Heathrow</strong>. To also replace the current voice telephones<br />

with IPT (Internet Protocol Telephony).<br />

Diagram of IP infrastructure<br />

Objectives:<br />

BAA: • To provides a reliable, supportable data network which<br />

can be used to deliver services to BAA and it’s customers.<br />

• To provide a reliable, supportable voice system that will<br />

enable airline moves.<br />

Airline:<br />

None<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

BAA Network<br />

Projects<br />

Red<br />

Implementation<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £7,800,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

01 / 2004 01 / 2006 09 / <strong>2009</strong> 02 / <strong>2009</strong><br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• Project can deliver to its current plan<br />

• Project scope remains fixed<br />

• The Telecoms Programme will only go to areas where there is currently a network<br />

device; it will not extend the network.<br />

• It is anticipated that the airport will support the Telecoms Programme through the<br />

changes that it has to make to the operational network, while changes will be made<br />

at times to minimise disruption at certain times this may impact the airport.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

IT Ops + £1M Additional IT resources required to support<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 281


Telecoms - £3M Savings to the BTGS contract and PSTN<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 282


Appendix A: Overview: Reference Drawing / Image:<br />

Use<br />

BAA Infrastructures<br />

Public & Partner Infrastructures<br />

Vodafone<br />

Specialist<br />

PBXs<br />

Partner<br />

PBX<br />

WiFi<br />

WiFi<br />

IP LAN<br />

BT<br />

3 rd Party<br />

PBX<br />

Internet<br />

Consolidated infrastructures<br />

Combined, reduced costs<br />

Increased functionality & opportunity<br />

Radio<br />

Radio<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 283


Appendix C: Project Delivery: High Level Project <strong>Plan</strong>:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 284


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 285


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

<strong>Airport</strong> Operational Systems<br />

0000 : <strong>Airport</strong> Operational Systems<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Develop a simpler, cheaper to operate IT architecture which<br />

supports the operational needs of <strong>Heathrow</strong> <strong>Airport</strong>, in terms<br />

of passengers, airlines, baggage handlers, other business<br />

partners and BAA staff. Key operational systems for airfield<br />

and terminal support include AOS/IDAHO, FIDS, security roster<br />

management and queue measurement, access control<br />

(MAID), air quality & noise measurement/ tracking, asset<br />

management.<br />

None<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA: • Sustain value in IT asset base<br />

• Reduce complexity and number of systems<br />

• Reduce opex costs for IT solutions<br />

• Enhance the passenger experience<br />

• Support improvement in airport operational KPI’s.<br />

Airline:<br />

Status:<br />

BAA Lead Team:<br />

Project Delivery<br />

To be consulted through IT Stakeholder Programme Board<br />

Airline Strategic Solution or DGS/IGS Stage<br />

Engagement:<br />

IT Red Various<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £57,100,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Decision:<br />

Start on<br />

Site:<br />

Completion on Site:<br />

Operational Use<br />

Commences:<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• This “project” is an allowance for works done on the above operational systems.<br />

• Key operational systems for airfield and terminal support include AOS/IDAHO, FIDS,<br />

security roster management and queue measurement, access control (MAID), air<br />

quality & noise measurement/ tracking, asset management.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily<br />

exhaustive.<br />

Operational Issues<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 286


Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

Assessed on a per project basis<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory<br />

decisions and therefore information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• <strong>Investment</strong>s are aimed at reducing opex costs for IT solutions when asset refreshes<br />

take place and minimising additional opex costs for new business improvement<br />

solutions.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement<br />

status shown above.<br />

Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

IT Infrastructure Renewal<br />

0000 : IT Infrastructure Renewal<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings /<br />

Images:<br />

(Refer to Appendix A)<br />

Projects to renew centralised IT infrastructure which delivers IT<br />

business services (systems and applications) at <strong>Heathrow</strong><br />

<strong>Airport</strong>.<br />

None<br />

Objectives:<br />

BAA: • Maximise useful asset lives<br />

• Ensure asset availability maximised<br />

• Protect customer experience<br />

• Minimise ongoing cost of operation, support and<br />

maintenance<br />

Airline:<br />

Status:<br />

BAA Lead Team:<br />

To be consulted through IT Stakeholder Programme Board<br />

Airline Strategic Solution or DGS/IGS Stage<br />

Engagement:<br />

IT Architecture Red Various<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 287


Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £30,300,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Decision:<br />

Start on<br />

Site:<br />

Completion on<br />

Site:<br />

Operational Use<br />

Commences:<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• This “project” is an allowance for works done on the above business services.<br />

• Examples of the business services are; data centres, servers & software<br />

infrastructure, extranet, IT security, wireless network infrastructure, network<br />

management applications, customer support application etc.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue /<br />

Opex Cost<br />

Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

Assessed on a per project basis<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• <strong>Investment</strong>s are aimed at reducing opex costs for IT solutions when asset refreshes<br />

take place and minimising additional opex costs for new business improvement<br />

solutions.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and<br />

the Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Header Information<br />

Project Name:<br />

Name in<br />

schedule<br />

Business <strong>Plan</strong>ning & Support IT Solutions<br />

0000 Business <strong>Plan</strong>ning & Support IT<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 288


Description:<br />

Ref. Drawings/ Images:<br />

(Refer to Appendix A)<br />

Systems delivered to meet the needs of business planning and<br />

other back office business areas of <strong>Heathrow</strong> <strong>Airport</strong>. .<br />

None<br />

Objectives:<br />

BAA: • Develop a simplified suite of systems which support<br />

business processes at a lower operational cost<br />

• Maintain and improve systems and services for business<br />

planning and back office functions<br />

• Enable exploitation of management information and<br />

collaborative working opportunities with business<br />

partners.<br />

Airline:<br />

Status:<br />

BAA Lead Team:<br />

Project Delivery<br />

Not applicable<br />

Airline Strategic Solution or DGS/IGS Stage<br />

Engagement:<br />

IT Red Various<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £39,600,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Decision:<br />

Start on<br />

Site:<br />

Completion on Site:<br />

Operational Use<br />

Commences:<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• This “project” is an allowance for works done in the above business areas.<br />

• Examples of the business areas are; ERP (Enterprise Resource <strong>Plan</strong>ning), web<br />

developments (BAA.com, intranet and Connect Live), commercial, content &<br />

collaboration (email, document management and office applications, etc.)<br />

income management, financial, HR and payroll systems, etc.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

Assessed on a per project basis<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• <strong>Investment</strong>s are aimed at reducing opex costs for IT solutions when asset refreshes<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 289


take place and minimising additional opex costs for new business improvement<br />

solutions.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 290


Appendix I: PDS – Q5 Rail<br />

Project Definition Sheets – Q5 Rail<br />

<strong>Heathrow</strong> Express<br />

R001 : HEx Growth Projects<br />

R002 : HEx Renewal Projects<br />

Other Rail<br />

R003 : Airtrack<br />

R004 : Connect 4 tph<br />

Header Information<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 291


Project Name:<br />

Name in<br />

Schedule<br />

<strong>Heathrow</strong> Express Growth Projects FQ/Q7<br />

0000 : Hex Growth Projects<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Projects to improve revenue earning opportunities for<br />

<strong>Heathrow</strong> Express<br />

None<br />

Objectives:<br />

BAA: • Increase revenue earning through:<br />

• Improving customer experience<br />

• Make it easier to buy tickets and travel on HEx/ Connect<br />

services – eg. Airside ticket desks; e and m ticketing<br />

development<br />

• Exploit non fare revenue earning opportunities eg. Build<br />

digital Advertising infrastructure on rail network<br />

• Signage improvements to ensure ease of location of HEx<br />

network<br />

Airline: • Improve passenger access to <strong>Heathrow</strong><br />

• Encourage increased use of <strong>Heathrow</strong> airlines<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Rail Red Various<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £14,800,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

n/a n/a n/a n/a<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

This “project” is an allowance. Each project delivered using these funds will be<br />

evaluated on its individual merits in terms of value to the Hex business<br />

Operational Issues<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Commentary:<br />

Cost Area:<br />

Pax / Revenue<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Revenue impact will be estimated on each project<br />

individually,.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 292


Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 293


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

<strong>Heathrow</strong> Express Renewal Projects<br />

0000 : Hex Renewal Projects<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Projects to renew <strong>Heathrow</strong> Express rail assets through Major<br />

repair or replacement.<br />

None<br />

Objectives:<br />

BAA: • Maximise useful asset lives<br />

• Ensure asset availability maximised<br />

• Protect customer experience<br />

• Minimise ongoing cost of maintenance through proactive<br />

identification replacement needs<br />

Airline: • Maintain/ improve passenger access to <strong>Heathrow</strong><br />

• Encourage increased use of <strong>Heathrow</strong><br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Rail Red Various<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £34,700,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Operational Use<br />

Commences:<br />

Decision:<br />

Site:<br />

n/a n/a n/a n/a<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

Each project will be evaluated on its individual merits / needs / value to business<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Commentary:<br />

Cost Area:<br />

Revenue / Cost<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Maintenance projects are implemented to protect<br />

revenues and minimise costs, through ensuring rail<br />

assets are available, fully functional throughout<br />

their useful lives.<br />

Impact on User Charges:<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

Not included in CIP <strong>2009</strong> Publication<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 294


None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 295


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

Airtrack<br />

7067 : Airtrack<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Building a case for improved surface access to <strong>Heathrow</strong> from<br />

the south west.<br />

Airtrack route map.<br />

Objectives:<br />

BAA: • Improve passenger access and arrival times to <strong>Heathrow</strong><br />

via South West route.<br />

• Link to wider public transport rail network to encourage<br />

increased volumes of passengers arriving via public<br />

transport rather than by private vehicle.<br />

• Encourage increased use of <strong>Heathrow</strong>.<br />

Airline: • Improve passenger access to airline services at <strong>Heathrow</strong>.<br />

• Encourage increased use of <strong>Heathrow</strong>.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Rail Red Pre - Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £89,800,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Decision:<br />

Options decision<br />

made October 2006<br />

Site:<br />

Subject to<br />

successful outcome<br />

of TWA application<br />

– target 2010<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Not yet scheduled Target 2013/14<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• TWA application completed successfully and government approval given<br />

• Viable business case constructed for Airtrack operation to be implemented<br />

• Local consultation addresses local concerns<br />

• Agreement reached on rail pathways for services to be offered. Options include<br />

Staines – T5 link, plus wider routing onto South West network<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 296


Rail<br />

Income<br />

Fare<br />

Evaluation<br />

progress<br />

in<br />

As part of initial project work, route structure and<br />

revenues/ costs are being estimated. The final<br />

outcome for BAA will be a combination of:<br />

• What the final structure looks like<br />

• who operates the services,<br />

• What routes will be operated<br />

• Likely passenger volumes<br />

Cost structure being evaluated as part of initial<br />

TWA work<br />

Op Cost Evaluation in<br />

progress<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

Airtrack would create additional rail infrastructure. If operated by BAA there would be<br />

additional operational requirements / costs incurred in running the operation.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 297


Appendix A: Overview: Reference Drawing / Image:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 298


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 299


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

<strong>Heathrow</strong> Connect 4 Trains per Hour (4tph)<br />

4133 : Connect 4tph<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Enhance the current <strong>Heathrow</strong> Connect service from, 2 trains<br />

per hour from London Paddington to <strong>Heathrow</strong> Terminal 4<br />

and a Terminal 4 to Central Terminal shuttle, to a 4 trains per<br />

hour service from London Paddington to Terminal 4. The<br />

airlines are full supportive of the improvement to the T4<br />

service.<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

None<br />

• Increases surface access to <strong>Heathrow</strong> airport using a<br />

sustainable mode (ref. ASAS)<br />

• Removes interchange confusion at CTA station (ref. SQR) –<br />

better service offering to passenger<br />

• More staff will travel available to airport by rail (ref. ASAS)<br />

• Allays current airline concerns that T4 poorly served by rail<br />

(AOC)<br />

• Improves western access to <strong>Heathrow</strong> (via Hayes) – main<br />

criticism of TVEP, an important stakeholder<br />

• Demonstrates Crossrail paths without detriment to<br />

<strong>Heathrow</strong> Express Service<br />

• Significant contribution to stretch revenue generation<br />

targets for current quinquennium,<br />

• Re-introduction of turn up and go through service from T4<br />

to Paddington.<br />

Airline: • Improve passenger access to <strong>Heathrow</strong> T4.<br />

• Improves passenger rail experience in travelling to/ from T4;<br />

• Customer experience reduced following the opening of T5<br />

and the transfer of HEx services away from T4 to T5. There<br />

is an expectation amongst the airlines that efforts will be<br />

made to improve the T4 service.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Rail Red Options Decision<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £20,000,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site:<br />

Decision:<br />

Principle of Connect<br />

service agreed<br />

Operational Use<br />

Site:<br />

Commences:<br />

TBC TBC 2010<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 300


August 2008<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• Train paths can be agreed with Network rail / Other train operators<br />

• Agreement over running the additional services can be agreed with First Great<br />

Western (partner in current Connect venture).<br />

• Viable business case, return can be established<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Revenue<br />

Impact being assessed<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 301


Appendix J: PDS – Q5 PSDH, Thames Water and Support Adjustments<br />

Project Definition Sheets – Q5 PSDH, Thames Water and<br />

Support Adjustments<br />

R3T6 : PSDH Q5<br />

TW01 : Thames Water Ongoing Payments<br />

9036 : HAL Central Risk (R2)<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 302


Header Information<br />

Project Name:<br />

Name in<br />

Schedule:<br />

Q5 PSDH Funding<br />

R3T6 : PSDH Q5<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

PSDH Allowance for Q5<br />

None<br />

Progress PSDH related work in Q5 to deliver a 3 runway<br />

<strong>Heathrow</strong><br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Amber Pre-Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £672,000,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Decision:<br />

Start on<br />

Site:<br />

Completion on Site:<br />

Not applicable<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

Q5 PSDH monies were provisioned in the regulatory settlement with only limited<br />

information.<br />

Discussions have introduced the concept of PSDH, now R3 / T6 only with no mixed<br />

mode on the existing runways, into a number of workstreams;<br />

• Forecasting – demand<br />

• Masterplanning and design<br />

• Surface Access<br />

• Legal<br />

• <strong>Plan</strong>ning and Environment<br />

• Stakeholder engagement and communication<br />

• Programme Office and Business case<br />

• Land acquisition and compensation<br />

• Airspace<br />

In addition work has progressed on a possible estimating structure for the planning<br />

stage which suggest the following breakdown;<br />

• HOSS<br />

• PMSB<br />

• Land Acquisition<br />

• Airspace Design<br />

• Environmental Impact<br />

• Legal and <strong>Plan</strong>ning<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 303


• BAA staff costs<br />

• Surface Access (roads)<br />

• Surface Access (rail)<br />

• Design<br />

• Preliminary works.<br />

At the JST on 2 nd March <strong>2009</strong> it was agreed that use of the PSDH Q5 monies would be<br />

approved in advance by the airline community and HAL would seek payment on an expost<br />

basis.<br />

Work will now progress on giving clarity for drawdown of funds within a structure in<br />

order that clarity can be maintained.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Not assessed<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• Detailed implementation of the scope pre-approval / ex-post cost recovery<br />

mechanism for the Q5 PSDH monies.<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 304


Header Information<br />

Project Name:<br />

Name on<br />

Schedule:<br />

Thames Water Ongoing Payments (Q5)<br />

TW01 : Thames Water Ongoing Payment (Q5)<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

The “project” covers the ongoing payment to Thames Water<br />

in respect of T5 land purchase.<br />

None.<br />

N/A.<br />

Airline:<br />

N/A.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Green N/A<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £26,300,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Decision:<br />

Start on<br />

Site:<br />

Completion on Site:<br />

N/A<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• These payments arise from the legal agreements related to the purchase, for T5, of<br />

the Thames Water Perry Oaks site.<br />

• Payments continue to 2035.<br />

• This PDS only details Q5 at this time.<br />

• No AFC information provided due to pending legal issues with Thames Water.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 305


• None.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• None.<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 306


Header Information<br />

Project Name:<br />

Name on<br />

Schedule:<br />

Central Risk “R2”<br />

9036 : HAL Central Risk (R2)<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Central holding “pot” for the management of risk monies.<br />

None.<br />

Objectives:<br />

BAA: • Improved project management of Q5 projects.<br />

• Improved visibility of risk allowances.<br />

• Improved consultation on use of risk monies.<br />

Airline: • As BAA’s.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

<strong>Capital</strong> & Solutions Amber N/A<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £300,800,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Decision:<br />

Start on<br />

Site:<br />

Completion on Site:<br />

N/A<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• The creation of the R2 risk allowances is covered by CCRS which provides full<br />

details.<br />

• R2, while central, identifies the projects that “own” the monies within the “pot”.<br />

• Drawdown of funds from R2 is via CCRS process.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Not applicable<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 307


• None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• While endorsing the principle of the R2 approach the airline community have yet to<br />

be presented with the detail behind the CCRS raised to cover the removal of the<br />

monies from individual projects.<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 308


Appendix K: PDS – Eastern Campus Phase 2 Enabling<br />

Project Definition Sheets – PDS – Eastern Campus Phase 2<br />

Enabling<br />

9206 : Eastern Campus Phase 2 Safeguarding<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 309


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

EC Phase 2 Safeguarding<br />

9206 : Eastern Campus Phase 2 Safeguarding<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description: Possible Q5 safeguarding for Eastern Campus Phase 2<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Baggage Masterplan Option 3 – <strong>Plan</strong> Drawing<br />

T2A/B/C Tunnel Requirements – <strong>Plan</strong> Drawing<br />

Objectives:<br />

BAA: Reduce future operational impact of Eastern Campus Phase 2<br />

delivery by actively safeguarding for T2C & T2D<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Amber Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £206,000,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Decision:<br />

Start on<br />

Site:<br />

Completion on Site: Operational Use<br />

Commences:<br />

03/2008 06/<strong>2009</strong> 06/2011 12/2013<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

This project is needed to effectively safeguard for the future construction of the Eastern<br />

Campus Phase 2. Active safeguarding of Energy and Infrastructure, Baggage and TTS<br />

requirements at this point will provide the least cost and disruptive solution for the<br />

future construction of the Eastern Campus Phase 2<br />

Key scope assumptions for this project are as follows:<br />

• Energy & Infrastructure<br />

• HV infrastructure (Underground routings)<br />

• Cooling and heating enabling infrastructure (Increases in size of pumps &<br />

pipes & containment where necessary)<br />

• Baggage<br />

• Design of the baggage connectivity tunnel between T2A, B & C<br />

• Construction civils only of baggage connectivity tunnel between T2B & C<br />

(Excludes Fitout)<br />

• Details all based on Baggage Masterplan Option 3<br />

• TTS<br />

• Design of the TTS Running Tunnels between T2A, B & C<br />

• Design and construction civils only of TTS station area under T2B<br />

(Excludes Fitout)<br />

• Construction civils only of TTS Running Tunnel between T2B & C<br />

(Excludes fitout)<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 310


Operational Issues<br />

• TTS Running Tunnels to include necessary civil construction space<br />

provisions for Energy & Infrastructure pipe work.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

Opex and Revex impacts have not been assessed at<br />

this stage.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• The principle of using Q5 PSDH funds for active safeguarding was agreed at the JST,<br />

however detailed CCRS documentation or review post the government PSDH<br />

decision has not been undertaken.<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 311


Appendix A: Overview: Reference Drawing / Image:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 312


Eastern Campus Phase 2 Safeguarding<br />

Elements for Construction and Design only<br />

New Transfer<br />

Bag Facility<br />

Early<br />

Bag<br />

St<br />

“ECph2 Safeguard” Design only<br />

“ECph2 Safeguard” Design & construct<br />

For demolition<br />

ECph1 projects<br />

E.C. ph2<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 313


Appendix B: Project Delivery: Cost Information:<br />

Project Information<br />

Project Name:<br />

Eastern Campus Phase 2 Safeguarding<br />

BCT No.: 9206 OP No.:<br />

AFC Cost Information:<br />

All information extracted from February <strong>2009</strong> month end process<br />

Base Costs: £163,000,000 79 %<br />

On-Cost: £25,000,000 12 %<br />

Risk (R1 Allowance only) £18,000,000 9 %<br />

Total (As entered into Artemis for Feb 09 Month End) £206,000,000<br />

Commentary:<br />

These values represent a budget allowance and excludes R2 risk<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 314


Appendix L: PDS – Q6 and Beyond Eastern Campus<br />

Project Definition Sheets – Q6 and Beyond Eastern Campus<br />

FQ01 : CWF T1 (Q6 & Q7)<br />

FQ02 : CWF T2 (Q6 & Q7)<br />

FQ03 : Eastern Campus Phase 2<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 315


Header Information<br />

Project Name: CWF T1 (Q6 & Q7)<br />

Name in FQ01 : CWF T1 (Q6 & Q7)<br />

Schedules:<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Clean Working and Friendly (CWF) is an allowance for minor<br />

projects in an area. The projects should be focused on asset<br />

replacement and minor works that improve at least one of the<br />

following; service quality, safety, environmental performance<br />

or security.<br />

None<br />

To ensure the main asset base is maintained and that<br />

statutory and service quality objectives can be met and / or<br />

improved.<br />

Airline:<br />

As BAA’s.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Amber Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

£7.4M<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site: Operational Use<br />

Decision:<br />

Site:<br />

Commences:<br />

Each project created from CWF funds will have its own delivery dates that will be<br />

determined at project definition.<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• The CWF allowance is based upon a renewal percentage of X% over a 5 year period<br />

on the asset base NPV (2008) of £310,226,000. 2% has been selected to reflect the<br />

current age of the asset base.<br />

• Cost shown for 5 years of Q6 and 1 year of Q7.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Refer to assumptions below<br />

Impact on User Charges:<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

Not included in CIP <strong>2009</strong> Publication<br />

Not stated<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 316


None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• The nature of CWF projects is such that any revenue / operational cost impact for<br />

each project is minor in the context of the overall <strong>Heathrow</strong> budget also not possible<br />

to calculate at this allowance level.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 317


Header Information<br />

Project Name: CWF T2 (Q6 & Q7)<br />

Name in FQ02 : CWF T2 (Q6 and Q7)<br />

Schedule:<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Clean Working and Friendly (CWF) is an allowance for minor<br />

projects in an area. The projects should be focused on asset<br />

replacement and minor works that improve at least one of the<br />

following; service quality, safety, environmental performance<br />

or security.<br />

None<br />

To ensure the main asset base is maintained and that<br />

statutory and service quality objectives can be met and / or<br />

improved.<br />

Airline:<br />

As BAA’s.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Amber Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

£7.8M<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site: Operational Use<br />

Decision:<br />

Site:<br />

Commences:<br />

Each project created from CWF funds will have its own delivery dates that will be<br />

determined at project definition.<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• The CWF allowance is based upon a renewal percentage of X% over a 5 year period<br />

on the asset base being, at this time, the T2A AFC of £1.3bn. 0.5% has been<br />

selected to reflect the current age of the asset base.<br />

• Cost shown for 5 years of Q6 and 1 year of Q7.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Refer to assumptions below<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 318


Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• The nature of CWF projects is such that any revenue / operational cost impact for<br />

each project is minor in the context of the overall <strong>Heathrow</strong> budget also not possible<br />

to calculate at this allowance level.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 319


Header Information<br />

Project Name: Eastern Campus Phase 2<br />

Name in 0000 : Eastern Campus Phase 2<br />

Schedule<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description: Continued development of the Eastern Campus (Q6 & Q7)<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Indicative Eastern Campus Layouts at;<br />

• Phase 1 Opening<br />

• Phase 2 Completion<br />

• Baggage Masterplan Option 3<br />

Objectives:<br />

BAA: • Alliance collocation<br />

• Service quality improvement<br />

• Operational efficiencies<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Red Pre-Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

£”TBC”<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

Completion on Site:<br />

TBC<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• The need for a Phase 2 of the Eastern Campus is driven by ;a) passenger growth<br />

and, b) asset life expectancy. Current forecasts excluding Mixed Mode effects<br />

suggest T2A Phase 1 will reach its design capacity by 2020, along with this Pier<br />

Service demands in Terminal 3 and the Eastern Campus would suggest the<br />

construction of additional infrastructure. Other key drivers are the life expectancy of<br />

Terminal 1 and the removal of T2A’s reliance on the Terminal 1 Baggage System.<br />

• Enablers to the commencement of this project are:<br />

• Completion of T2A Phase 1<br />

• Relocation of the Terminal 1 non aligned airlines BCT ????<br />

• Completion of the Eastchurch Road re-alignment and Hanger BCT ???<br />

• Eastern Campus Phase 2 Safeguarding completed during Q5 BCT ????<br />

• BCT 7720 will be used during Q5 to fund early management and design<br />

resources for EC Phase 2<br />

• Key scope assumptions for this project are:<br />

• Demolition & Enabling<br />

• Removal of the remaining elements of the ESR Gantry<br />

• Vacant Possession of all demolition & work zones<br />

• Demolition of BA facility TBE<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 320


• Demolition of BA facility Cathedral Hanger<br />

• Demolition of southern sections of T1 Piers 3, 4, Eurolounge and FCC<br />

• Demolition of MSCP1/T2A Phase 1 VCC Passenger Connector<br />

• Re - alignment of Alpha and Bravo Taxiways including the necessary AGL<br />

substations<br />

• Re - alignment of the Northern & Southern Runway Holding areas<br />

• Code F compliant re-alignment of a section of the Bravo Taxiway north of T1<br />

• Remodelling of Terminal 1 to facilitate demolition zones and continuing airline<br />

operations for EI and FI<br />

• Temporary re-provision of the Hounslow Suite, or upgrading of the Hillingdon<br />

Suite<br />

• Maintenance Base property acquisition costs to support the construction of T2C<br />

• New Infrastructure<br />

• Eastern Airside Road extension to either Viscount Way or the diverted<br />

Eastchurch Road including a new control post<br />

• Additional infrastructure services to support EC Phase 2<br />

• New segregated T2C Pier with an additional 7 Code F and 5 Code E stands (with<br />

2 (Code E)/3 (Code F ) Airbridges & PCA per stand)<br />

• Civil Construction and fitout of TTS Maintenance base east of T2C<br />

• Civil Construction of the TTS running tunnel between T2A, B and the remaining<br />

sections connecting T2B to T2C<br />

• Fitout of T2A, B and C TTS station zones and the interconnecting running<br />

tunnels<br />

• Installation, testing and putting into operation of the new TTS System<br />

• TTS system safeguarding for Inter-Terminal TTS operation.<br />

• Baggage System fitout of T2A, B and C based on Masterplan Option 3<br />

• Extension of the T2A Terminal per existing <strong>Plan</strong>ning Permission for an additional<br />

10MPPA with additional 4 Code C and 1 code F stand (Code F stand to have 3<br />

Airbridges & PCA)<br />

• Baggage civils zones & basements in the extension of the T2A Terminal based<br />

on Baggage Masterplan Option 3<br />

• Passenger transport zones in the extension of the T2A Terminal based on an<br />

Eastern Campus TTS System including active safeguarding for an inter-terminal<br />

TTS.<br />

• Civil Construction and fit out of a further 2 Code F, 2 Code E and 1 Code D<br />

remote stands associated with the extension of the T2A Terminal<br />

• Retrofit and integration works required inside T2A Phase 1<br />

• Eastern Campus Phase 2 Operational Readiness<br />

• Excludes the necessary Forecourt/MSCP extension and CTA works required for<br />

this development.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

Opex and Revex impacts have not been assessed at<br />

this stage.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 321


Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• This project being the provision of significant infrastructure will create as a minimum<br />

increases in the following operational fields; Security, Maintenance, Cleaning and<br />

Baggage Ops.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• While not a specific disagreement, the airline occupancy for Eastern Campus Phase<br />

2 has not been agreed.<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 322


Appendix A: Overview: Reference Drawing / Image:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 323


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 324


Appendix C: Project Delivery: High Level Project <strong>Plan</strong>:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 325


Eastern Campus Phase 2 - Initial Review Programme<br />

2012<br />

2013 2014 2015 2016<br />

2017<br />

2018 2019<br />

Multiple Projects - Production Design<br />

T2A & Eastern Campus<br />

Phase 1 Operational<br />

Airline Decants From T1<br />

Enabling Works<br />

T1 Airline Decant Complete<br />

Phase 1 of New Baggage<br />

System in T2A Operational<br />

Baggage System Operational to T2B<br />

TTS Operational<br />

Demolitions & Site Clearance<br />

T2 A Phase 2 & T2 C Fully Operational<br />

Baggage & TTS Tunnels<br />

TTS Maintenance Base Structure<br />

Construct T2 A Phase 2<br />

TTS Installation Incld Operational Trials<br />

Construct Terminal Pier / Pier 4 Replacement<br />

Construct T2 C<br />

Construct Phase 2 MSCP<br />

Airfield Works<br />

Airfield Works<br />

Airside Road Tunnel & Control Post<br />

Infrastructure Services Upgrade<br />

Ref : Diagrammatic Summary of 10000-XX-TS-XXX-000131 R2 0.1 15 th December <strong>2009</strong><br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 326


Appendix M: PDS – Q6 and Beyond Western Campus<br />

Project Definition Sheets – Q6 and Beyond Western Campus<br />

General<br />

FQ23 : <strong>Heathrow</strong> TTS: T5 to T3 extension<br />

Terminal 3<br />

FQ24 : CWF T3 (Q6 and Q7)<br />

FQ25 : T3 Arrivals Reconfiguration<br />

FQ26 : T3 Check-in and Central Search Relocation<br />

FQ27 : T3 CIP Lounge Development<br />

FQ28 : T3 IDL Reconfiguration<br />

FQ29 : T3 New Northern Pier and Stands<br />

FQ30 : T3 Pier 5 and Stands (330 to 342) Reconfiguration<br />

FQ31 : T3 Pier 5 Demolition / Toast Racked Code F Stands<br />

FQ32 : T3 Pier 6 Extension and Stands<br />

FQ33 : T3 Pier 6 to T2A Link<br />

FQ34 : T3 Pier 7 Redevelopment<br />

FQ35 : T3 Refit for T1 Non-Aligned<br />

Terminal 4<br />

FQ36 : CWF T4 (Q6 and Q7)<br />

FQ38 : T4 Arrivals Reclaim for A380<br />

FQ39 : T4 Code F Stands Phase 2<br />

Terminal 5<br />

FQ37 : CWF T5 (Q6 and Q7)<br />

FQ40 : T5B Phase 2<br />

FQ41 : T5C Phase 3<br />

FQ42 : T5D and Stands<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 327


Header Information<br />

Project Name:<br />

Name in<br />

Schedule:<br />

<strong>Heathrow</strong> TTS: T5 to T3 Extension<br />

FQ23 : <strong>Heathrow</strong> TTS: T5 to T3 Extension<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Extend the existing T5 TTS system to T3, with additional<br />

stations at T5D, Pier 7 and T3.<br />

Ref. Drawings / Images: Indicative route map<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA: • Improved service offer<br />

• Reduced passenger travel time<br />

• Reduction in walking distances<br />

• Improved ease of transfer<br />

• Increased capacity for transfer traffic growth<br />

• Supports <strong>Heathrow</strong> development plan<br />

Airline: • Improved transfer product offer<br />

• Enabler to grow transfer volumes<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Green Pre-Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

TBC<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

Completion on Site:<br />

TBC<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• Assume station box shell and core for T5D and Pier 7 are delivered as part of new<br />

Satellite development<br />

• Assume project is delivered using cut and cover construction methodology and<br />

operational disruption to taxiways and stands is co-ordinated with other projects.<br />

• Scope of works;<br />

o Automated People Movers and control systems<br />

o Tunnel systems<br />

o Station box for T3<br />

o TTS maintenance base reprovision<br />

o All stations fit out<br />

o Mechanical and electrical systems<br />

• The boundary of the system is defined from which the passenger is committed to<br />

using the system (ie: escalator to and from system).<br />

• Assume a contingency passenger walkway is NOT delivered or required.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 328


• Include all statutory approvals for railway operations.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

To be developed<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact: £0.01<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• Operating expenditure yet to be calculated<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 329


Appendix A: Overview: Reference Drawing / Image:<br />

HATTS West Extension<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 330


Header Information<br />

Project Name: CWF T3 (Q6 & Q7)<br />

Name in FQ24 : CWF T3 (Q6 & Q7)<br />

Schedule:<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Clean Working and Friendly (CWF) is an allowance for minor<br />

projects in an area. The projects should be focused on asset<br />

replacement and minor works that improve at least one of the<br />

following; service quality, safety, environmental performance<br />

or security.<br />

None<br />

To ensure the main asset base is maintained and that<br />

statutory and service quality objectives can be met and / or<br />

improved.<br />

Airline:<br />

As BAA’s.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Amber Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

TBC<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site: Operational Use<br />

Decision:<br />

Site:<br />

Commences:<br />

Each project created from CWF funds will have its own delivery dates that will be<br />

determined at project definition.<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• The CWF allowance is based upon a renewal percentage of X% over a 5 year period<br />

on the asset base NPV (2008) of £696,800,000. 2% has been selected to reflect the<br />

current age of the asset base.<br />

• Cost shown for 5 years of Q6 and 1 year of Q7.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Refer to assumptions below<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 331


Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• The nature of CWF projects is such that any revenue / operational cost impact for<br />

each project is minor in the context of the overall <strong>Heathrow</strong> budget also not possible<br />

to calculate at this allowance level.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 332


Header Information<br />

Project Name:<br />

Name in<br />

Schedule:<br />

T3 Arrivals Reconfiguration<br />

FQ25 : T3 Arrivals Reconfiguration<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Modification of the baggage hall capability to support the<br />

multiple concurrent arrival of A380 aircraft.<br />

None<br />

Objectives:<br />

BAA: • Improve passenger experience.<br />

Airline: • As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Red Pre-Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

TBC<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

Completion on Site:<br />

TBC<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• A possible extension of the baggage hall (Within existing footprint)<br />

• Introduction of an additional 90m baggage belt (capacity to be determined)<br />

• Fit out of any incremental area and the interface between the existing and<br />

incremental areas<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

To be developed<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 333


Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 334


Header Information<br />

Project Name:<br />

Name in<br />

Schedule:<br />

T3 Check-in and Central Search Relocation<br />

FQ26 : T3 Check-in and Central Search Relocation<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Remodel ground floor of T3 to accommodate revised check-in<br />

and central search facilities.<br />

Indicative impression only.<br />

Objectives:<br />

BAA: • Improve passenger experience (QSM/ASQ) in check in,<br />

security search and IDL areas<br />

• Increase capacity of the IDL<br />

• Deliver an enhanced search capability<br />

• Facilitate the adoption of the new search technologies<br />

• Derive business efficiencies as a result of the co- location<br />

of transfers and international search<br />

• Deliver a walk through check in routing directly into<br />

search process as per T5 & T2<br />

Airline:<br />

As BAA<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Red Pre-Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

TBC<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

TBC<br />

Completion on Site:<br />

Operational Use<br />

Commences:<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

Project only occurs if the main Terminal 3 baggage facility is relocated away from the<br />

main building, the void space that is created results in an opportunity to reconfigure<br />

check in and relocate security search.<br />

The project scope is:<br />

• Relocation of search from 1 st floor to ground floor; adoption of new search<br />

technologies and co-location of transfer and international search<br />

• New circulation from Search up into a reconfigured IDL;<br />

• Remodel check in – removal of cul-de-sac arrangement and creation of a linear,<br />

walk through check in set-up<br />

Note that there will be significant interface between IDL reconfiguration project and<br />

this project.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 335


Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

To be developed<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

More efficient and flexible co-located transfers and main security search<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Appendix A: Overview: Reference Image:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 336


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 337


Header Information<br />

Project Name:<br />

Name in<br />

Schedule:<br />

T3 CIP Lounge Development<br />

FQ27 : T3 CIP Lounge Development<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

This project is to provide replacement and additional CIP<br />

lounge capacity in T3.<br />

None<br />

Objectives:<br />

BAA: • Provide enhanced CIP space with in T3 to meet airline<br />

needs.<br />

• Maximise commercial revenue.<br />

Airline: • Deliver excellent premium product.<br />

• Maintain or increase overall till income.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Amber Pre-Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

TBC<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

TBC<br />

Completion on Site:<br />

Operational Use<br />

Commences:<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

Allows demolition of the CIP building located on the existing P7 connector. (Previously<br />

estimated as an area of 4,500 sqm)<br />

Specification of new CIP is equivalent to the new T4 CIP facility.<br />

This project creates allowances to be made for additional volume in pier 5, 6 or 7, plus<br />

increased foundations etc. (5400m2) to accommodate CIP facilities.<br />

(Note potential interdependency / connection to the New Pier 7, Pier 6 extension and<br />

Northern Pier projects)<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

To be developed<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 338


Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 339


Header Information<br />

Project Name:<br />

Name in<br />

Schedule:<br />

T3 IDL Reconfiguration<br />

FQ28 : T3 IDL Reconfiguration<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Reconfigure T3 International departure lounge to expand<br />

retail and service offer.<br />

Indicative layout<br />

Improve passenger experience and ASQ/QSM performance<br />

within the following areas:<br />

• Seating availability<br />

• Congestion<br />

• Eating and drinking facilities<br />

• Way finding<br />

Protect and grow existing retail income<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Red Pre-Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

TBC<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

Completion on Site:<br />

TBC<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• Project only occurs if the main Terminal 3 baggage facility is relocated away from<br />

the main building, the void space that is created results in an opportunity to relocate<br />

security search and the landside departures function. This then allows the extension<br />

of the IDL into the areas vacated by the relocation of search and landside departure.<br />

• The extension of the IDL would allow the re-planning of the IDL, and the<br />

introduction of new passenger focussed facilities. (e.g.) additional seating, catering,<br />

toilet and circulation areas.<br />

• Vertical circulation from the new search facility into the IDL we require the New<br />

Check In / Search project to be implemented and the teams to work closely to<br />

ensure an effective interface.<br />

• The scope of the security search project will include the provision of vertical<br />

circulation from the new search area to the existing IDL and the resulting<br />

reconfiguration requirements.<br />

• The IDL scope of works would be inclusive of a full fit out of the additional new area<br />

and a reconfiguration of significant areas of the existing lounge.<br />

• Assume the following level of works within existing IDL areas:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 340


• 25% of whole current IDL area to be completely stripped back and new fit out<br />

undertaken. (30% retail & 70% BAA IDL)<br />

• 30% of new space = retail, 70% of new space is BAA customer IDL areas (seating,<br />

circulation etc)<br />

• The scope of the check-in and central search project will include the provision of<br />

vertical circulation from the new search area to the existing IDL.<br />

• The IDL must remain fully operational during the delivery of these improvements to<br />

the IDL.<br />

• Continuity of trade should be maintained for the Terminal Three IDL retail offer.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

To be developed<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 341


Appendix A: Overview: Reference Drawing / Image:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 342


Header Information<br />

Project Name:<br />

Name in<br />

Schedule:<br />

T3 New Northern Pier and Stands<br />

FQ29 : T3 New Northern Pier and Stands<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

The provision of a new (Code F) northern pier and stands to<br />

replace the time expired pier 4a.<br />

Indicative T3 apron layout image.<br />

Objectives:<br />

BAA: • Provide additional code F pier serviced stands on the<br />

western campus.<br />

• Improve passenger experience and ASQ/QSM scores.<br />

• Improved taxiway operation by creating a further element<br />

of a fully ‘toast racked’ western campus apron.<br />

• Maximise tenant accommodation and retail opportunities.<br />

Airline: • Improved service offer<br />

• Increased tenant accommodation<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Red Pre-Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

TBC<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

TBC<br />

Completion on Site:<br />

Operational Use<br />

Commences:<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• This pier forms the northern section of any future toast rack on layout of the<br />

western campus. (It is a northern replication of Pier 6).<br />

• New pier to be linked to the T3 main building and TTS system via a tunnel.<br />

• A requirement to re-provide D’albac house (Cleared <strong>Heathrow</strong> <strong>Airport</strong> Limited land<br />

available at zero project cost)<br />

• Project scope is inclusive of stands and equipment areas, and any requirement to<br />

clear these areas and or required associated / adjacent areas.<br />

• The project will be responsible for clearing the construction area and if necessary reproviding<br />

the following existing facilities:<br />

• Cooling & High pressure hot water infrastructure<br />

• D’albic House<br />

• Pier 4a and associated infrastructure<br />

• CFL Building<br />

• Building 139<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 343


Key features of the Pier will be:<br />

• Similar design and layout to Pier 6, T5B, T5C and T2b satellites<br />

• Pier serviced code F stands<br />

• Ability to operate either closed or open gaterooms<br />

• Vertical segregation of departures / arrivals<br />

• Passenger connectivity to the T3 Track Transit station<br />

• Code F stands – all MARSed, 3 airbridges per stand, 2 PCA units per stand.<br />

• The extension solution should protect for a future/current interfaces with:<br />

• a new pier 5<br />

• the new northern code F taxi ways<br />

• the west to east track transit system<br />

• T6 airside road tunnel<br />

• The design of this pier will draw on the experience of delivering and designing the<br />

existing Pier 6, Terminal 5 and Terminal 2a satellites.<br />

• Provide decant facilities to facilitate the later demolition of the existing CIP building<br />

adjacent to the old pier 7 connector.<br />

• The delivery of this project must successfully manage a delivery interface with:<br />

• the code F northern taxi way<br />

• the introduction of a west to east track transit system<br />

• the T6 airside road tunnel<br />

• Pier 5 reconfiguration<br />

• It is likely that the northern pier stands will be undertaken as a first stage of works<br />

to deliver the new pier. (It is possible that several years may separate the delivery of<br />

the stands and the new northern pier).<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

To be developed<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 344


Appendix A: Overview: Reference Drawing / Image:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 345


Header Information<br />

Project Name:<br />

Name in<br />

Schedule:<br />

T3 Pier 5 and Stands (330 to 342) Reconfiguration<br />

FQ30 : T3 Pier 5 and Stands (330 to 342) Reconfiguration<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

The reconfiguration of Pier 5 to allow the operation of a dual<br />

code F taxi way north of the CTA.<br />

Indicative layout image<br />

Objectives:<br />

BAA: • Improved passenger experience and ASQ/QSM scores.<br />

• Improved taxi way operation by creating a further element<br />

of a fully toast racked western apron.<br />

• Remove any pier 5 operational constraints to the full<br />

operation of code F aircraft on the northern taxi way.<br />

• Improve airfield flexibility and functionality<br />

• Support the introduction of a western campus toast rack<br />

Airline: • Code F flexible taxiway system in CTA<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Red Pre-Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

TBC<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

TBC<br />

Completion on Site:<br />

Operational Use<br />

Commences:<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

Code F stands – all MARSed, 3 airbridges per stand, 2 PCA units per stand.<br />

The scope of this project is to:<br />

• Undertake the stand and building reconfigurations required to support code F<br />

operations from pier 5.<br />

• Remove any pier 5 operational constraints to the full operation of code F aircraft on<br />

the northern taxi way.<br />

• No new air bridge on existing MARSed stand.<br />

• All stands require pre conditioned air.<br />

• Use and Refurbish existing Air bridges for 2No / stands.<br />

• Provide 1 new stand.<br />

• All Parking for stands needs relaying, inclusive of assoc services work.<br />

• Road scope, extends to white line only.<br />

• An ability to board / disembark simultaneously on MARSed stands is required.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 346


• Existing closed gate rooms require reconfiguration of partitions etc and the provision<br />

of new hard flooring. (No other Refurbishment with project scope).<br />

• No work to taxiways included.<br />

• The delivery team must maintain operations on at least one of the existing dual taxi<br />

ways routes throughout construction of the code F taxi ways.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

To be developed<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 347


Appendix A: Overview: Reference Drawing / Image:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 348


Header Information<br />

Project Name:<br />

T3 Pier 5 Demolition / Toast racked Code F Stands<br />

Name<br />

Schedule:<br />

on<br />

FW31 : T3 Pier 5 Demolition / Toast Racked Code F Stands<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description: • The demolition of Pier 5 (between stand 329 and the<br />

entrance to the phase two extension).<br />

• Creation of a toast rack stand arrangement between the<br />

new Pier 7 and Terminal 3.<br />

• Creation of 13 extra code F stands (7xPS & 6xR) on the<br />

Western apron<br />

• Creation of a code F taxi way between the new Pier 7 and<br />

Terminal 3.<br />

• Create an arrivals and departures link between the new<br />

Pier 7 and the phase 2 extension of P5 (As per existing<br />

width of the re-used phase 2 link, Arrivals & Departures).<br />

This solution assumes that Pier 7 has only a single level of<br />

ramp accommodation and is constructed with a façade that<br />

supports 4 x code F stands and 1 x code E.<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Overview schematic<br />

Objectives:<br />

BAA: • Optimise the operational efficiency of the western apron<br />

taxi ways<br />

• Provide additional code F capacity on the Western apron<br />

• Optimise apron and taxi way efficiency on the western<br />

apron<br />

• Deliver an affordable solution that builds towards a full<br />

toast rack between the main runways<br />

• Re-use the existing phase 2 link bridge to provide an<br />

element of the new link between phase 2 and a new pier<br />

7<br />

Airline:<br />

TBC<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Red Pre outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

TBC<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

Completion on Site:<br />

TBC<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 349


• This project would be undertaken following the completion of the new Pier 7 and<br />

the extension to Pier 6.<br />

• The existing Pier 7 connector CIP block would be demolished following the relocation<br />

of the CIP facilities into the new Pier 6 extension.<br />

• The existing link bridge (P5 phase 2 to P5 Phase 1) would be re-used to provide part<br />

of a new link between the new Pier 7 and Pier 5 phase 2 extension.<br />

• This project would undertake the following scope:<br />

o Demolition of a section of Pier 5<br />

o Demolition of the Pier 7 connector CIP building<br />

o Re-location of the phase 2 connector and resulting reconfiguration of phase<br />

two building<br />

o Construction of a link between the new Pier 7 and phase 2 of Pier 5<br />

(Utilising phase 2 connector) and the interface with the new Pier 7<br />

o<br />

o<br />

Construction of code F taxi way<br />

Construction of 13 MARSed code F stands (7 pier served and 6 remotes) and<br />

2 pier served code D<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

To be developed<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 350


Appendix A: Overview: Reference Drawing<br />

Western Campus Interim Layout – 2021<br />

Retain Dual<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 351


Header Information<br />

Project Name:<br />

Name in<br />

Schedule:<br />

T3 Pier 6 Extension and Stands<br />

FQ32 : T3 Pier 6 Extension and Stands<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Extension to Pier 6, to provide 3nr code F gaterooms and<br />

stands in place of 2nr code M stands. (Note interdependency<br />

with the new CIP development project BCT 4217)<br />

Indicative T3 apron layout<br />

Objectives:<br />

BAA: • Improve passenger experience and ASQ/QSM scores.<br />

• Improved taxiway operation by creating a further element<br />

of a fully ‘toast racked’ western campus apron.<br />

• Maximise tenant accommodation and retail opportunities.<br />

• Provide decant facilities to facilitate the later demolition of<br />

the existing CIP building adjacent to the old pier 7<br />

connector.<br />

Airline: • Improved service offer<br />

• Increased tenant accommodation<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Red Pre-Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

TBC<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Decision:<br />

Start on<br />

Site:<br />

Completion on Site: Operational Use<br />

Commences:<br />

MM/YYYY MM/YYYY MM/YYYY MM/YYYY<br />

TBC<br />

Refer to appendix C for programme information detail.<br />

The following points cover the significant delivery assumptions related to this project;<br />

Assumptions:<br />

Key features of the extension will be:<br />

• Similar design and layout to existing Pier 6<br />

• Ability to operate either closed or open gate rooms<br />

• Vertical segregation of departures / arrivals<br />

• Code F stands – all MARSed, 3 air bridges per stand, 1 PCA units per stand.<br />

• CIP Lounge space<br />

• Ramp level accommodation<br />

• Scope is inclusive of 3 additional air bridge to the existing pier 6.<br />

• Dual pre conditioned air provision is required on all MARSed stands.<br />

• No work to taxiways included within the scope of this project. (Taxi way scope is<br />

within Pier 7 replacement project scope)<br />

• The extension solution will seek to interface effectively with the existing pier 6 but<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 352


will draw on the experience of delivering and designing the Terminal 5 and Terminal<br />

2 satellites.<br />

• It is likely that the Pier 6 phase two stands will be undertaken as a first stage of<br />

works to deliver the extension of pier 6. (It is possible that several years may<br />

separate the delivery of the stands and the new satellite pier).<br />

• Code F stands – all MARSed, 3 air bridges per stand, 1 PCA units per stand.<br />

• The solution should protect for the future connection of the extension to a new pier<br />

5 configured to fit with a toast rack layout on the western apron.<br />

• This project is enabled by the construction of the new pier 7, economies maybe<br />

achieved by delivering both projects simultaneously.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

To be developed<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 353


Appendix A: Overview: Reference Drawing / Image:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 354


Header Information<br />

Project Name:<br />

Name in<br />

Schedule:<br />

T3 Pier 6 to T2A Link<br />

FQ33 : T3 Pier 6 to T2A Link<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Link from T3 Pier 6 to T2A.<br />

Indicative T3/T1 apron layout.<br />

Provide flexible CTA infrastructure between Western and<br />

Eastern aprons.<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Red Pre-Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

TBC<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

Completion on Site:<br />

TBC<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project<br />

The link will include;<br />

• Both arrivals and departures links between Pier 6 and Terminal 2A.<br />

• No Travelator’s within links<br />

• 3.5m width walkway<br />

• Vertical segregation of departures and arrivals (Segregated vertical circulation at T2A<br />

end of facility)<br />

• Associated jetty and stand access<br />

• Arrivals and departures route Travelator’s<br />

• A route round T2A cooling facility<br />

• The realignment of existing T2A air bridges (Westernmost stands).<br />

• The extension solution will seek to interface effectively with the existing pier 6 but<br />

will draw on the experience of delivering and designing the new Terminal 5 and<br />

Terminal 2A satellites.<br />

• The delivery of this link should aim to not result in any stand or gate closures within<br />

Pier 6 or T2A<br />

• It will be necessary to providing both arrivals and departures links between Pier 6<br />

and Terminal 2A.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 355


Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

To be developed<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 356


Appendix A: Overview: Reference Drawing / Image:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 357


Header Information<br />

Project Name: T3 Pier 7 Redevelopment Phase 1<br />

Name on FQ34 : T3 Pier 7 Redevelopment Phase 1<br />

Schedule:<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Reprovide pier 7 (built in the late 1960’s) with a “toast rack”<br />

satellite facility.<br />

T3 apron layout image<br />

Objectives:<br />

BAA: • Improve passenger experience and ASQ/QSM scores<br />

• Improved segregation solution to deliver opex efficiencies<br />

• Improved taxiway operation by removing cul-de-sac and<br />

creation of a through taxiway<br />

• Maximise CIP accommodation, other tenant<br />

accommodation and retail opportunities<br />

Airline: • Improved service offer<br />

• Improved tenant accommodation<br />

• Improved CIP Lounge opportunities<br />

• Commonality of product on the western apron<br />

• Similar operating processes for staff<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Amber Pre-Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

TBC<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

Completion on Site:<br />

TBC<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

TTS West will commence A.S.A.P in Q6 and will start on site before P7.<br />

Passenger access to and from the first open phases of the new Pier 7 will be via coach.<br />

Key features of the Satellite will be:<br />

• 300m long satellite, 36m wide.<br />

• Similar design and layout to T2B and T2C satellites<br />

• Pier service to 5xJX stands,1xD stand and 2xE stand<br />

• Ability to operate either closed or open gaterooms<br />

• Vertical segregation of departures / arrivals<br />

• Passenger connectivity via Track Transit System<br />

• Automated Baggage connectivity from T3 only<br />

• Removal of Romeo cul-de-sac and creation of a through Golf taxiway<br />

• A single level of ramp accommodation along the full length of the new pier<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 358


The project scope is inclusive of the provision of temp relocations, the refurbishment of<br />

existing areas for relocated facilities and or the re-provision of relocated facilities,<br />

inclusive of VAA Crew facilities, AOSU and SIS into the new pier 7 facility.<br />

Project scope to be inclusive of (expedite and transfer break baggage link) baggage<br />

connectivity T3 to pier 7.<br />

Project scope to exclude any cost for alteration to T3 integrated baggage works.<br />

The project needs to safeguard for inbound DCV from T5D.<br />

The project shall provide a segregated tunnel walkway<br />

between the new pier and Terminal 3.<br />

The vertical circulation that is required by this project will be located within the “pier 6<br />

triangle”<br />

Project scope to be inclusive of the realignment of the adjacent taxi ways and<br />

equipment areas and any resulting requirement to clear these areas and or associated<br />

and adjacent areas.<br />

Permanent decant solutions shall be provided that fit with the western campus master<br />

plan.<br />

• The project will have to be phased because the operation cannot offer up all of the<br />

pier and stands for construction purposes. An outline phasing strategy has been<br />

drawn up based on no more than 4 stands being taken out of operation at one<br />

point in time<br />

• For part of the construction period, passenger connectivity from T3 to the satellite<br />

will be via a coach operation from T3<br />

• Vacant possession of site required – relocation of VAA crew report, AOSU area,<br />

tenant accommodation, L18 baggage facility, staff access to Control Tower. (All<br />

included in this project scope.)<br />

• Project to construct TTS station box, shell and core standard only. Full fit out to be<br />

delivered by the TTS project.<br />

• JX stands – all MARSed, 3 airbridges per stand, 2 PCA units per stand.<br />

• Project enables Pier 6 Phase 2 stands delivery – economies may be achieved by<br />

delivering both projects simultaneously.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

To be developed<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• BAA security operational efficiencies will be achieved by removal of horizontal<br />

segregation scheme.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 359


Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 360


Appendix A: Overview: Reference Drawing / Image:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 361


Header Information<br />

Project Name:<br />

Name in<br />

Schedule:<br />

T3 Refit for T1 Non-aligned<br />

FQ35 : T3 Refit for T1 Non-aligned<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Airline:<br />

This project provides for the refit of vacated areas in Terminal<br />

3 to accommodate the move of non aligned carriers from T1.<br />

None<br />

Further Toastracking of the Eastern Apron<br />

Service standard improvement<br />

Alliance collocation on the Eastern Apron<br />

Service standard improvement<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Red Pre-Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

TBC<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

Completion on Site:<br />

TBC<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

This project is an enabler to the construction of elements of Eastern Campus Phase 2<br />

Enablers to the commencement of this project are:<br />

• Completion of T2A Phase 1 & the subsequent airline moves<br />

• Airline moves into T2A & T2B are funded by airlines under terms of commercial<br />

policy<br />

Key scope assumptions for this project are:<br />

• Refit of vacated areas of T3 for provision of CIP lounge, airline accommodation,<br />

ramp accommodation, handler accommodation etc<br />

• Relocation of systems infrastructure for LY & CY<br />

• Provision of airline specifics and support to facilitate the required moves<br />

• Excludes vacant possession and demolition activities in T1<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

Opex and Revex impacts have not been assessed at<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 362


this stage.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

Discussion on the timeframe and nature of T1 closure has been commenced with the<br />

Airline Community but has not been concluded.<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 363


Header Information<br />

Project Name: CWF T4 (Q6 & Q7)<br />

Names in FQ36 : CWF T4 (Q6 & Q7)<br />

Schedule:<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Clean Working and Friendly (CWF) is an allowance for minor<br />

projects in an area. The projects should be focused on asset<br />

replacement and minor works that improve at least one of the<br />

following; service quality, safety, environmental performance<br />

or security.<br />

None<br />

To ensure the main asset base is maintained and that<br />

statutory and service quality objectives can be met and / or<br />

improved.<br />

Airline:<br />

As BAA’s.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Amber Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

£4.8M<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site: Operational Use<br />

Decision:<br />

Site:<br />

Commences:<br />

Each project created from CWF funds will have its own delivery dates that will be<br />

determined at project definition.<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• The CWF allowance is based upon a renewal percentage of X% over a 5 year period<br />

on the asset base NPV (2008) of £12345. X% has been selected to reflect the<br />

current age of the asset base.<br />

• Cost shown for 5 years of Q6 and 1 year of Q7.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Refer to assumptions below<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 364


Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• The nature of CWF projects is such that any revenue / operational cost impact for<br />

each project is minor in the context of the overall <strong>Heathrow</strong> budget also not possible<br />

to calculate at this allowance level.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 365


Header Information<br />

Project Name:<br />

Name on<br />

Schedule:<br />

T4 Arrivals Reclaim for A380<br />

FQ38 : T4 Arrivals Reclaim for A380<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

The provision of a baggage hall capable of supporting the<br />

concurrent arrival of A380 aircraft.<br />

None<br />

BAA: Improved flexibility and service quality in T4.<br />

Airline:<br />

As BAA<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Red Pre-Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

TBC<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

Completion on Site:<br />

TBC<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

The scope shall include;<br />

• a small extension of the baggage hall (Within existing footprint)<br />

• the introduction of an additional 90m baggage belt<br />

• the fit out the incremental area and the interface between the existing and<br />

incremental area.<br />

• Need to undertake the demolition and reconfiguration of existing internal area<br />

required to provide 1 additional 90m A380 belts. The net impact will be that the<br />

baggage hall will contain 2 x 90m new baggage belts and 5 standard (std) existing<br />

baggage belts (Assumes that 1 x 90m A380 belt is delivered in Q5, reducing existing<br />

provision from 7 std baggage belts to 1 large and 5 std baggage belts).<br />

• Project scope is inclusive of the re-provision of any removed office space to areas<br />

within existing building. (Needs provision for strip out and BAA specification CAT A<br />

only).<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

To be developed<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 366


Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 367


Header Information<br />

Project Name: T4 Code F Stands Phase 2<br />

Name on FQ39 : T4 Code F Stands Phase 2<br />

Schedule:<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

The provision of additional stand and gate room facilities to<br />

support the increased operation of A380 aircraft on the<br />

southern campus.<br />

None<br />

Flexibility of T4 operation<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Red Pre-Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

TBC<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

Completion on Site:<br />

TBC<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• The delivery team must maintain operations on adjacent stands and taxiways routes<br />

throughout construction of the code F stands.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

To be developed<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 368


Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 369


Header Information<br />

Project Name: CWF T5 (Q6 & Q7)<br />

Name on FQ37 : CWF T5 (Q6 & Q7)<br />

Schedule:<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Clean Working and Friendly (CWF) is an allowance for minor<br />

projects in an area. The projects should be focused on asset<br />

replacement and minor works that improve at least one of the<br />

following; service quality, safety, environmental performance<br />

or security.<br />

None<br />

To ensure the main asset base is maintained and that<br />

statutory and service quality objectives can be met and / or<br />

improved.<br />

Airline:<br />

As BAA’s.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Amber Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

£53.4M<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site: Operational Use<br />

Decision:<br />

Site:<br />

Commences:<br />

Each project created from CWF funds will have its own delivery dates that will be<br />

determined at project definition.<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• The CWF allowance is based upon a renewal percentage of X% over a 5 year period<br />

on the asset base NPV (2008) of £4,452,951,000. 1% has been selected to reflect<br />

the current age of the asset base.<br />

• Cost shown for 5 years of Q6 and 1 year of Q7.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Refer to assumptions below<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 370


Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• The nature of CWF projects is such that any revenue / operational cost impact for<br />

each project is minor in the context of the overall <strong>Heathrow</strong> budget also not possible<br />

to calculate at this allowance level.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 371


Header Information<br />

Project Name: T5B Phase 2<br />

Name on FQ40 : T5B Phase 2<br />

Schedule:<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description: • Provision of additional gate room area and air bridge /<br />

jetty infrastructure to optimise the pier service from T5B.<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

General arrangement drawing showing safeguarding area<br />

(circled)<br />

Objectives:<br />

BAA: • Improve passenger experience and ASQ/QSM scores<br />

• Improve pier service<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Red Pre-Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

TBC<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

Completion on Site:<br />

TBC<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• T5B to remain operational throughout construction works.<br />

Ideally no more that one remote stand to be removed from operation at any stage<br />

of construction.<br />

• This project will deliver pier service and code F compliance to 3 / 4 existing remote<br />

stands.<br />

• Code F stands – all MARSed, 3 air bridges per stand, 2 PCA units per stand.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

To be developed<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 372


Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 373


Appendix A: Overview: Reference Drawing / Image:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 374


Header Information<br />

Project Name: T5C Phase 3<br />

Name in FQ41 : T5C Phase 3<br />

Schedule:<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description: • Position of additional gate room areas and air bridge /<br />

jetty infrastructure to optimise the pier service from T5C.<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

General arrangement drawing showing safeguarded area<br />

(circled.)<br />

Objectives:<br />

BAA: • Improve pier service<br />

• Improve passenger experience and ASQ/QSM scores<br />

Airline: • Improved service offer<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Red Pre-Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

TBC<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

Completion on Site:<br />

TBC<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• This project will deliver pier service and code F compliance to 2 existing remote<br />

stands at the south end of T5C<br />

• Existing Code F stands to be MARSed, 3 air bridges per stand, 1 PCA units per<br />

stand.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

To be developed<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 375


project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 376


Appendix A: Overview: Reference Drawing / Image:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 377


Header Information<br />

Project Name:<br />

Name in<br />

Schedule:<br />

T5D and Stands<br />

FQ42 : T5D and Stands<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Provision of a T5D Satellite building and reconfiguration to<br />

create 14 pier served stands.<br />

Indicative T5 apron layout image in appendix A<br />

Objectives:<br />

BAA: • Provide increased levels of pier service Improve passenger<br />

experience and ASQ/QSM scores.<br />

• Improved taxiway operation by creating further ‘toast<br />

racked’ apron.<br />

• Additional tenant accommodation and retail<br />

opportunities.<br />

Airline: • Improved service offer<br />

• Increased tenant accommodation<br />

• Opportunity for increased single till income.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Red Pre-Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

TBC<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

TBC<br />

Completion on Site:<br />

Operational Use<br />

Commences:<br />

Refer to appendix C for programme information detail.<br />

The following points cover the significant delivery assumptions related to this project;<br />

Assumptions:<br />

The fuel farm (on T5d site) needs to be removed by 2018, and will be undertaken by<br />

another project.<br />

The T5d cost sheets do not include the cost of basements, which are within the<br />

<strong>Heathrow</strong> Track Transit System cost plan.<br />

Key features of the Pier will be:<br />

• Similar design and layout to T5B, T5C and T2a satellites<br />

• 14 Pier serviced stands (Code F and Code E)<br />

• Ability to operate either closed or open gaterooms<br />

• Vertical segregation of departures / arrivals<br />

• Passenger connectivity via Track Transit System<br />

• Code F stands – all MARSed, 3 airbridges per stand, 2 PCA units per stand.<br />

The following assumptions have been made:<br />

• Fuel farm is relocated, demolished, redirected etc by another project.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 378


• The requirement to remove above ground T5 TTS facility will be undertaken by<br />

another project.<br />

• HATTS maintenance base facility to be re-provided by another project.<br />

• The pier width is equivalent to T2B.<br />

• A replacement of the Fire station at ramp level and within the pier is within the<br />

scope of the T5D project.<br />

• A replacement of BA’s EAA facilities to an area of existing <strong>Heathrow</strong> <strong>Airport</strong> Limited<br />

land (zero project land cost) is within the scope of the T5D project.<br />

• The provision of a DCV link from T5C to T5D to pier 7 is within the scope of the T5D<br />

project.<br />

• Extended passenger connection tunnel from T5C to T5D is within the scope of the<br />

T5D project. (Specification as per the T5a to T5b passenger connection tunnel)<br />

• The satellite solution will draw on the experience of delivering and designing the<br />

new Terminal 5 and Terminal 2a satellites.<br />

• The new satellite will be linked to Terminal 5 via an extension to the existing track<br />

transit system.<br />

• The new satellite will be linked to Terminal 3 via the proposed track transit system<br />

extension.<br />

• It is likely that the T5D stands will be undertaken as a first stage of works to deliver a<br />

new T5D satellite pier. It is possible that several years may separate the delivery of<br />

the stands and the new satellite pier.<br />

• The new T5D satellite can only be constructed if the existing fuel facility has been<br />

relocated (COMA regulations).<br />

• Project to construct TTS station box, shell and core standard only. Full fit out to be<br />

delivered by the TTS project.<br />

• Code F stands – all MARSed, 3 airbridges per stand, 2 PCA units per stand.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

To be developed<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• Increased levels of pier service will deliver increased operational efficiency and<br />

reduced airline operational expenditure.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 379


Appendix A: Overview: Reference Drawing / Image:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 380


Appendix N: PDS – Q6 and Beyond Infrastructure<br />

Project Definition Sheets – Q6 and Beyond Infrastructure<br />

FQ04 : Additional Jetties - FQ<br />

FQ05 : Carbon Reduction<br />

FQ06 : Cargo Tunnel Renovation<br />

FQ07 : Code F A&B Taxiways between E&K Taxiways<br />

FQ08 : CWF Airfield (Q6 & Q7)<br />

FQ09 : CWF Connections (Q6 & Q7)<br />

FQ10 : CWF Other Areas (Q6 & Q7)<br />

FQ11 : <strong>Heathrow</strong> TTS: Inter Existing Terminals<br />

FQ12 : Landside Roads Infrastructure and Systems<br />

FQ13 : Main CTA Tunnel Renovation<br />

FQ14 : Maintenance of Retail Income<br />

FQ15 : Overlay Runway - Northern<br />

FQ16 : Overlay Runway - Southern<br />

FQ17 : PCA (existing facilities) - FQ<br />

FQ18 : Security Projects<br />

FQ19 : Utilities Infrastructure Upgrade<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 381


Header Information<br />

Project Name:<br />

Name on<br />

Schedule:<br />

Additional Jetties – FQ<br />

FQ04 : Additional Jetties – FQ<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Provision of additional airbridge jetties in Q6<br />

Location plans for T2, 3, 4 & 5<br />

BAA objectives are to:<br />

• minimise connection times<br />

• maximise customer service by maximising Jetty service<br />

levels<br />

• minimise abortive project costs<br />

minimise airline operational costs<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Amber Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices): £41,500,000<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Decision:<br />

Start on<br />

Site:<br />

Completion on Site:<br />

TBC<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• Following consultation with the airlines a commitment was made to provide 2<br />

airbridges on all JW stands and 3 airbridges on all JX Stands at <strong>Heathrow</strong>, by the<br />

end of Q6.<br />

• This project commences in Q5 and provides funds for additional airbridges currently<br />

outside the scope (and cost plan) of planned development projects<br />

• This Project does not allow for additional provision of Pre-conditioned air or Fixed<br />

Electrical Ground Power.<br />

• Airbridge costs based on BAA Standard Product<br />

• Project Management<br />

o<br />

o<br />

Overall strategy to be agreed at the Infrastructure Stakeholder Board.<br />

Project Delivery will be managed by local project teams at T2, T3, T4 and T5<br />

consulting Terminal AOCs at a more detail level.<br />

It is assumed that the airbridges planned to be installed in Q5 are completed<br />

within the programme set.<br />

• Terminal 2<br />

o The T2A & T2B Projects scope includes provision of 2 airbridges on all Code<br />

E (JW) and Code F (JX) Stands.<br />

o T2 Phase 2 will provide all airbridges on T2A Phase 2 and T2C<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 382


o This project will fund the provision of additional airbridges to 7 No. Code F<br />

stands in Q6.<br />

• Terminal 3<br />

o Q6 Projects at Pier 5, 6 and 7 will include second / third airbridges on all new<br />

/ reconfigured stands illustrated on diagram in App A2.<br />

o This project will fund the provision of an additional airbridge to 1 No. Code E<br />

stands in Q6. Should the Pier 5 project be cancelled – a second airbridge will<br />

be required on a further 4 Code E stands.<br />

• Terminal 4<br />

o<br />

JX Stands Phase 2 project planned for Q6 goes ahead and includes funding<br />

for three airbridges. If not, additional bridges will need to be installed on<br />

the existing JW stands.<br />

• Terminal 5<br />

o This project allows for 3 No. additional airbridges on Code E stands on T5A –<br />

The inclusion of a Multi-choice apron to provide operational flexibility is likely<br />

to make the inclusion of additional airbridges difficult.<br />

o<br />

Operational Issues<br />

The Project assumes the ability to install a third airbridge on Code F stands at<br />

T5B. Due to the inclusion of “Head of Stand” baggage delivery in the<br />

original T5 project scope, the initial brief published by BA & BAA accepted<br />

that the third airbridge would not be possible – This will require further<br />

investigation.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

Commentary:<br />

Revenue /<br />

airbridge<br />

Op ex /<br />

airbridge<br />

per Annum:<br />

£ nil This project will not add to Jetty service levels or<br />

revenue in any significant way as airbridges are<br />

being added to current Jetty served stands.<br />

Estimated<br />

+£525 k<br />

at<br />

Maintenance cost - £10,500 / annum / airbridge<br />

Operating cost - £ tbc / annum / airbridge<br />

No. new airbridges to be provided resulting in an<br />

increase of £ (10,500 + tbc) x 22 = £ tbc per annum<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact: TBC<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• Opex based on historic maintenance costs.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 383


Appendix A1: Overview: Scope of Additional Airbridge Project – T2:<br />

Taxilane<br />

178<br />

C<br />

176<br />

D<br />

174 101<br />

D<br />

n.b. T2A Ph 1 & T2B Project scope - All JW Stands delivered with 2 airbridges<br />

T2A Ph2 & T2C Project scope - include 3 bridges on JX stands and 2 on JW stands<br />

D<br />

Q6 Additional<br />

201<br />

Airbridge Scope<br />

D<br />

C<br />

F<br />

T2A T2B Total<br />

JW - - -<br />

JX 2 5 7<br />

203<br />

C<br />

205<br />

C<br />

C<br />

F<br />

E<br />

E<br />

C<br />

F<br />

C<br />

C<br />

C<br />

C<br />

C<br />

206<br />

208<br />

210<br />

212<br />

211<br />

214<br />

215<br />

231<br />

232<br />

233<br />

234<br />

253<br />

E<br />

E<br />

F<br />

F<br />

F<br />

E<br />

E<br />

C<br />

F<br />

C<br />

C<br />

F<br />

C<br />

C<br />

F<br />

C<br />

249<br />

248<br />

247<br />

246<br />

244<br />

231<br />

257<br />

256<br />

255<br />

254<br />

E<br />

E<br />

E<br />

F<br />

F<br />

E<br />

E<br />

E<br />

F<br />

F<br />

249<br />

248<br />

265<br />

265<br />

264<br />

C<br />

C<br />

C<br />

F<br />

C<br />

216<br />

217<br />

218<br />

236<br />

238<br />

F<br />

F<br />

C<br />

F<br />

C<br />

F<br />

243<br />

242<br />

253<br />

252<br />

F<br />

E<br />

F<br />

E<br />

263<br />

262<br />

273<br />

272<br />

F<br />

E<br />

JW<br />

JW<br />

F<br />

C<br />

226<br />

C<br />

225<br />

F<br />

F<br />

C C C C<br />

223 221<br />

C<br />

E<br />

C<br />

220<br />

239<br />

E<br />

E<br />

241<br />

251<br />

E<br />

E<br />

261<br />

271<br />

E<br />

JW<br />

M<br />

Q6 Additional Airbridge Scope<br />

T2A<br />

T2B<br />

Total<br />

JW<br />

-<br />

-<br />

-<br />

JX<br />

2<br />

5<br />

7<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 384


Appendix A2: Overview: Scope of Additional Airbridge Project – T3:<br />

JW<br />

JX<br />

Q6 Additional Airbridge Scope<br />

P5<br />

P6<br />

P7<br />

Total<br />

1<br />

-<br />

-<br />

1<br />

-<br />

-<br />

-<br />

-<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 385


Appendix A3: Overview: Scope of Additional Airbridge Project – T4:<br />

Safeguard for JX stand upgrade<br />

Q6 Additional Airbridge Scope<br />

JW<br />

8<br />

JX<br />

-<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 386


Appendix A4: Overview: Q6 Scope of Additional Airbridge Project – T5:<br />

JW<br />

JX<br />

Q6 Additional Airbridge Scope<br />

T5A<br />

T5B<br />

T5C<br />

Total<br />

3*<br />

11<br />

6<br />

20<br />

4*<br />

4<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 387


Header Information<br />

Project Name:<br />

Name in<br />

Schedule:<br />

Carbon Reduction<br />

FQ05 : Carbon Reduction<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Projects to deliver national targets in Co2 reduction.<br />

None<br />

To exceed climate change targets as part of the sustainable<br />

development of <strong>Heathrow</strong>.<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Red Pre-Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

TBC<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

Completion on Site:<br />

TBC<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

The UK targets for Co2 reduction are;<br />

- 30% by 2020 (from 1990 levels)<br />

- 80% by 2050 (from 1990 levels)<br />

BAA/s strategy has five key elements;<br />

- “ We recognise the need to avoid dangerous climate change”<br />

- “Climate change presents a long-term risk – finding solutions will be critical to<br />

our licence to grow”<br />

- “Where we have direct control over emissions (e.g. energy use in our facilities)<br />

we aim to lead the airport industry in managing them”<br />

- Where we do not have direct control over emissions (e.g. flights) we aim to use<br />

our influence to lead changes”<br />

- We believe that emissions trading is the most environmentally effective and<br />

economically efficient way of addressing aviations contribution to climate<br />

change”<br />

Q5 Co2 reductions are driven by meeting the published <strong>Heathrow</strong> Energy Strategy<br />

(HES), which has three components;<br />

- Energy Demand Management<br />

- Utilities Supply Infrastructure<br />

- New Building Design<br />

The Q6 and Q7 will need to address each of the following five levels;<br />

- Energy Demand Management<br />

- Utility Supply Infrastructure<br />

- New Build Design<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 388


- Off Site <strong>Investment</strong><br />

- Offsetting<br />

At this stage this project is a allowance to address these issues that should be further<br />

detailed through development of HES and during <strong>2009</strong>.<br />

This allowance is £10M / year based on Q5 spend, leading to a total of £60M for<br />

CIP<strong>2009</strong> (5 years in Q6 and 1 year in Q7)<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Not yet understood<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 389


Header Information<br />

Project Name:<br />

Name on<br />

Schedule:<br />

Cargo Tunnel Renovation<br />

FQ06 : Cargo Tunnel Renovation<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Comprehensive renovation and relife of the existing CTA to<br />

T4 cargo tunnel<br />

None<br />

To bring an essential asset up to date and to extend operating<br />

life for a further 20 years.<br />

Airline:<br />

Ensure the operationally essential airside link is maintained.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Red Pre-Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

TBC<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

Completion on Site:<br />

TBC<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

Scope to include;<br />

- Survey all civil, M&E and all other engineering systems, and response to findings.<br />

- Installation of current UK and EU best practice fire detection and response<br />

systems.<br />

- Complete replacement of the ventilation system.<br />

- Complete road resurfacing including access ramps.<br />

- Repair of all civil engineering elements.<br />

- Recladding of tunnel lining.<br />

- Replacement of all M&E Systems.<br />

- Implementation of best practice tunnel management process.<br />

Works will need to be done in phases with significant (75%) night work with the tunnel<br />

being operational 05:30 to 22:30 daily.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

No revenue increase. Negligible opex impact<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 390


Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 391


Header Information<br />

Project Name:<br />

Name on<br />

Schedule:<br />

Code F A&B Taxiways between E&K Taxiways<br />

FQ07 : Code F A&B Taxiways between E&K Taxiways<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

The re-alignment of the existing Northern Code E taxiways in<br />

a southerly direction by approx. 30 metres to enable Code F<br />

clearances on both taxiways from the northern runway.<br />

Indicative plan image<br />

Objectives:<br />

BAA: • Improve taxiway operations and reduce delays /<br />

congestion in response to the growth in Code F<br />

movements at LHR;<br />

• Improve airfield flexibility and functionality<br />

Airline: • Reduced taxiway delays and congestion.<br />

• Improved punctuality.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Red Pre-Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

TBC<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

Completion on Site:<br />

TBC<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• Works to provide the northern code F taxiway will not commence until 2018<br />

• The scope of this project is to undertake only the taxi way reconfiguration within the<br />

footprint of the existing taxiways and stands supporting pier 4a.<br />

• Works to demolish pier 4a and provide new Code E stands are within the scope of<br />

the new northern pier.<br />

• The delivery team must maintain operations on at least one of the existing dual<br />

taxiways routes throughout construction of the code F taxi ways.<br />

• The delivery team need to be aware / manage the interfaces with the following<br />

adjacent projects:<br />

• West to East track transit link<br />

• New Northern Pier & Stands<br />

• Terminal 6 Airside Road Tunnel<br />

• Pier 5 stand re-configuration<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 392


Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

To be developed<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

Assured negligible opex impact.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 393


Appendix A: Overview: Reference Drawing / Image:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 394


Header Information<br />

Project Name: CWF Airfield (Q6 & Q7)<br />

Name on FQ08 : CWF Airfield (Q6 & Q7)<br />

Schedule:<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Clean Working and Friendly (CWF) is an allowance for minor<br />

projects in an area. The projects should be focused on asset<br />

replacement and minor works that improve at least one of the<br />

following; service quality, safety, environmental performance<br />

or security.<br />

None<br />

To ensure the main asset base is maintained and that<br />

statutory and service quality objectives can be met and / or<br />

improved.<br />

Airline:<br />

As BAA’s.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Amber Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

£10.4M<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site: Operational Use<br />

Decision:<br />

Site:<br />

Commences:<br />

Each project created from CWF funds will have its own delivery dates that will be<br />

determined at project definition.<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• The CWF allowance is based upon a renewal percentage of X% over a 5 year period<br />

on the asset base NPV (2008) of £575,982,000. 1.5% has been selected to reflect<br />

the current age of the asset base.<br />

• Cost shown for 5 years of Q6 and 1 year of Q7.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Refer to assumptions below<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 395


Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• The nature of CWF projects is such that any revenue / operational cost impact for<br />

each project is minor in the context of the overall <strong>Heathrow</strong> budget also not possible<br />

to calculate at this allowance level.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 396


Header Information<br />

Project Name: CWF Connections (Q6 & Q7)<br />

Name in 0000 : CWF Airfield (Q6 & Q7)<br />

Schedule<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Clean Working and Friendly (CWF) is an allowance for minor<br />

projects in an area. The projects should be focused on asset<br />

replacement and minor works that improve at least one of the<br />

following; service quality, safety, environmental performance<br />

or security.<br />

None<br />

To ensure the main asset base is maintained and that<br />

statutory and service quality objectives can be met and / or<br />

improved.<br />

Airline:<br />

As BAA’s.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Amber Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

£3.4M<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Start on Completion on Site: Operational Use<br />

Decision:<br />

Site:<br />

Commences:<br />

Each project created from CWF funds will have its own delivery dates that will be<br />

determined at project definition.<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• The CWF allowance is based upon a renewal percentage of X% over a 5 year period<br />

on the asset base NPV (2008) of £188,094,000. 1.5% has been selected to reflect<br />

the current age of the asset base.<br />

• Cost shown for 5 years of Q6 and 1 year of Q7.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Refer to assumptions below<br />

Impact on User Charges:<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

Not included in CIP <strong>2009</strong> Publication<br />

TBC<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 397


None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• The nature of CWF projects is such that any revenue / operational cost impact for<br />

each project is minor in the context of the overall <strong>Heathrow</strong> budget also not possible<br />

to calculate at this allowance level.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 398


Header Information<br />

Project Name: CWF Other Areas (Q6 & Q7)<br />

Name in 0000 :CWF Other Areas (Q6 & Q7)<br />

Schedule<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Clean Working and Friendly (CWF) is an allowance for minor<br />

projects in an area. The projects should be focused on asset<br />

replacement and minor works that improve at least one of the<br />

following; service quality, safety, environmental performance<br />

or security.<br />

None<br />

To ensure the main asset base is maintained and that<br />

statutory and service quality objectives can be met and / or<br />

improved.<br />

Airline:<br />

As BAA’s.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Amber Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

£52.4M<br />

Refer to appendix B for cost information detail.<br />

Time:<br />

Brief<br />

Decision:<br />

Start on<br />

Site:<br />

Completion on Site: Operational Use<br />

Commences:<br />

Each project created from CWF funds will have its own delivery dates that will be<br />

determined at project definition.<br />

Refer to appendix C for programme information detail.<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• The CWF allowance is based upon a renewal percentage of X% over a 5 year period<br />

on the asset base NPV (2008) of £2,181,570,000. 2.5% has been selected to reflect<br />

the current age of the asset base.<br />

• Cost shown for 5 years of Q6 and 1 year of Q7.<br />

• “Other areas” includes; Landside, non terminal assets, IT and Utilities.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Refer to assumptions below<br />

Impact on User Charges:<br />

Estimated Per Passenger Cost Impact:<br />

Not included in CIP <strong>2009</strong> Publication<br />

Not stated<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 399


Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• The nature of CWF projects is such that any revenue / operational cost impact for<br />

each project is minor in the context of the overall <strong>Heathrow</strong> budget also not possible<br />

to calculate at this allowance level.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

• None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 400


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

HATTS Inter Terminal (existing airport)<br />

0000 : <strong>Heathrow</strong> TTS: Inter Existing Terminals<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Airline:<br />

This project contains 2 key elements of scope:<br />

• Twin track TTS system connecting T3 to T2A, enabling the<br />

East and West intra-TTS systems to be connected.<br />

• Twin track TTS system connecting T2C to T4, enabling T4<br />

to be connected to both the East and West systems.<br />

Overview plan layouts.<br />

1. Improved service offer<br />

2. Reduced passenger travel time<br />

3. Reduction in walking distances<br />

4. Improved ease of transfer<br />

5. Increased capacity for transfer traffic growth<br />

6. Supports <strong>Heathrow</strong> development plan<br />

1. Improved transfer product offer<br />

2. Enabler to grow transfer volumes<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Green Pre-Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

£TBC<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

Completion on Site:<br />

TBC<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• This project is dependent upon the T5 system being extended to T3 by another<br />

project.<br />

• Assume station boxes for T3 and T2A are delivered by other projects;<br />

• Assume project is tunnel bored across the CTA;<br />

• Assume B139/D’Albiac House area is no longer required and vacant possession is<br />

achieved. Area is used as an entry point for TBM<br />

• Scope of works:<br />

• Additional Automated People Movers<br />

• Tunnel systems<br />

• Station box for T3<br />

• M&E fit out of tunnels<br />

• Safeguarded stub tunnels to a future T6<br />

• Assume a contingency passenger walkway is NOT delivered or required<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 401


Operational Issues<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

To be developed<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

Significant opex cost increase expected.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 402


Appendix A: Overview: Reference Drawing / Image:<br />

T3 to T2A<br />

T2C to T4<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 403


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

Landside Roads Infrastructure & Systems<br />

0000 : Landside Roads Infrastructure and Systems<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description: Road network improvements and new UTMC traffic<br />

management system .<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

None<br />

• To maximise the use of the existing road network<br />

• To improve staff and passenger service by;<br />

• Delivering additional road capacity<br />

• Increase journey time reliability on the <strong>Heathrow</strong><br />

road network<br />

• Reducing delays on the network at key locations<br />

and to insure network resilience is maintained<br />

• Keeping road users informed about the status of<br />

our road network<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Red Pre-Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

£TBC<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

Completion on Site:<br />

TBC<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

Scope includes:<br />

UTMC and ANPR network management system costs for CTA.<br />

All current VMS sites (including car park ‘space’ signs) and mobile devises<br />

All design, equipment and civil costs<br />

Any ANPR system will safeguard for future uses including road user charging<br />

UTMC system should safeguard for future data inputs for CO2 and NOx<br />

Scope excludes:<br />

Maintenance costs of existing assets<br />

Any forecourt and car park management system costs<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 404


Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Reduction in manual vehicle counting for traffic modelling<br />

Reduction in staffing costs for network management<br />

New maintenance costs for ANPR/VMS/UTMC equipment<br />

Commentary:<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact: ?<br />

Commentary:<br />

Detailed opex impacts to be developed.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

• Existing UTC and SCOOT systems will be superseded or incorporated into UTMC<br />

• Current contract with SERCO for managing signals equipment can incorporate new<br />

system upgrades and maintenance<br />

• Staff will receive relevant training and support to have operational capability to use<br />

new systems effectively.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 405


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

Main Tunnel Renovation<br />

0000 : Main CTA Tunnel Renovation<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Comprehensive renovation and relife of the existing CTA<br />

landside access tunnels.<br />

None<br />

To bring an essential asset up to date and to extend operating<br />

life for a further 20 years.<br />

Create a fresh “front door” to T1,T2 and T3 and the CTA<br />

generally.<br />

Airline:<br />

Improve passenger perception of T1,T2 and T3 access.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Red Pre-Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

£TBC<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

Completion on Site:<br />

TBC<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

Scope to include;<br />

• Survey all civil, M&E and all other engineering systems, and response to findings.<br />

• Installation of current UK and EU best practice fire detection and response systems.<br />

• Complete replacement of the ventilation system.<br />

• Complete road resurfacing including access ramps.<br />

• Repair of all civil engineering elements.<br />

• Recladding of tunnel lining.<br />

• Replacement of all M&E Systems.<br />

• Implementation of best practice tunnel management process.<br />

100% of works will need to be done at night.<br />

Access ramps to include up to 50m from tunnel portals only.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Cost Area:<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Commentary:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 406


No revenue increase. Negligible opex impact.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 407


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

Maintenance of Retail Income<br />

0000 : Maintenance of Retail Outcome<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Minor reconfiguration and alterations to retail spaces / areas<br />

around / <strong>Heathrow</strong>.<br />

None<br />

To maintain the standard of the <strong>Heathrow</strong> retail offer through<br />

correct alteration and reconfiguration of retail offer facilities<br />

and related M & E services.<br />

Airline:<br />

Allow maintenance of single till related retail income.<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Red Pre-Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

£TBC<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

Completion on Site:<br />

TBC<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

Based on previous allowances contained within CWF funds a budget of £4M / year is<br />

proposed. For CIP <strong>2009</strong> this equates to £24M total (5 years Q6 + 1 year Q7)<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Nil revenue impact as maintains current provision only. Negligible opex impact.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 408


None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 409


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

Overlay Runway - Northern<br />

3089a : Overlay Runway - Northern<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Resurface and relife (for another 10 years) the Northern<br />

runway and associated exits.<br />

None<br />

Ensure critical asset maintained to best practice.<br />

Airline:<br />

As BAA<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Red Pre-Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

£TBC<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

Completion on Site:<br />

TBC<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

Scope includes all civil and M&E works required to return the runway to cap168 and<br />

best practice standards.<br />

Works to be done during the summer season on nights only.<br />

Note: The £1.2M in Q5 for design work is covered under BCT no 3089.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

No revenue increase. Negligible opex impact.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 410


None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 411


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

Overlay Runway - Southern<br />

3089b : Overlay Runway - Southern<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Resurface and relife (for 10 years) the Southern runway and<br />

associated exits.<br />

None.<br />

Ensure Asset maintained to best practice.<br />

Airline:<br />

As BAA<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

£TBC<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

Completion on Site:<br />

TBC<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

Scope includes all civil and M&E Works required to return the runway to CAP168 and<br />

best practice standards.<br />

Works to be done during the summer season on nights only.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

No revenue increase. Negligible opex impact.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 412


Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 413


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

PCA (existing facilities)<br />

3874 : PCA (existing Facilities) - FQ<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Installation of PCA onto existing pier served stands<br />

Ref. Drawings / Images: None<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Air quality improvements<br />

Airline:<br />

Opex reduction<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Red Pre-Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

£TBC<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

Completion on Site:<br />

TBC<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

Installation of Pre-Conditioned Air facilities onto pier served stands that do not have an<br />

existing PCA service and are not scheduled for reconfiguration within Q6 and the first 2<br />

years of Q7.<br />

Assume, subject to greater clarity still being required on pier developments, this will be<br />

40 stands in terminals 1,3 and 4.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

Increase in opex cost due to additional assets. Revenue position still to be developed.<br />

See areas of disagreement.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 414


None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

The airline community have expressed a view that PCA should be charged as an<br />

additional service where available as use of PCA saves fuel for those airlines using it. This<br />

document is not intended to form any view on charging, but to ensure an allowance for<br />

PCA works in Q6 is maintained.<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 415


Header Information<br />

Project Name:<br />

Name in<br />

schedule<br />

Security Projects<br />

0000 : Security Projects<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Security development and enhancement works primarily<br />

arising from responses to MATRA risk assessments and DfT<br />

legislative requirements.<br />

None<br />

Maintain a secure <strong>Heathrow</strong> meeting legal and best practice<br />

security requirements.<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Red Pre-Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

£TBC<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

Completion on Site:<br />

TBC<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

This is an allowance for project content still to be determined. A number of projects may<br />

involve works that, are due to security considerations, can not be consulted upon in a<br />

normal manner.<br />

Previously this work was called “Managed Campus Security Projects”<br />

Based on previous allowances a budget of £3M / year is proposed. For CIP <strong>2009</strong> this<br />

egrets to a total of £18M (5 Years Q6 + 1 year Q7)<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

No revenue impact as compliance works negotiable opex cost assumed, but each<br />

project will need to check specific impact.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 416


information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 417


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

Utilities Infrastructure Upgrade<br />

4169 : Utilities Infrastructure Upgrade<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Objectives:<br />

BAA:<br />

Upgrade of core utility infrastructure.<br />

None<br />

Ensure base assets required for a safe reliable operation to be<br />

maintained.<br />

Airline:<br />

As BAA’s<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Strategy Red Pre-Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

£TBC<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

Completion on Site:<br />

TBC<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

Significant portions on key utility infrastructure require complete replacement due to<br />

their age and condition.<br />

This project is an allowance to be allocated on a risk basis, after a comprehensive survey,<br />

over the relevant assets.<br />

The assets envisaged to be covered are;<br />

- Fire mains (dirty water on airfield and landside areas)<br />

- Foul water (external mains from buildings to public main)<br />

- Portable water (external mains and storage facilities from incoming public supply<br />

to buildings)<br />

- Communications pit and duct system (focusing on the civil aspects of such<br />

systems not replacement of the cabling contained within unless necessary)<br />

- Heating and cooling external pipes, pits and ductwork.<br />

All should be upgraded for a 20 year life.<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex Revenue (+) /<br />

Commentary:<br />

Cost Area: Cost (-) Impact<br />

per Annum:<br />

No revenue impact. Reduction in opex, TBC, based on new best practice assets being<br />

installed.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 418


Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None.<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

That new replacement infrastructure is lower cost to maintain.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 419


Appendix O: PDS – Q6 and Beyond Rail<br />

Project Definition Sheets – Q6 and Beyond Rail<br />

FQ20 : Crossrail<br />

FQ21 : HEx Growth Projects (FQ)<br />

FQ22 : HEx Renewal Projects (FQ)<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 420


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

CrossRail<br />

9098 : Crossrail<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

BAA support for government’s CrossRail cross London rail<br />

transport link<br />

CrossRail route map<br />

Objectives:<br />

BAA: • Provide financial support to the CrossRail project by<br />

making a £230m# contribution.<br />

• Supports CrossRail delivering passengers to <strong>Heathrow</strong> via<br />

public transport.<br />

• BAA demonstrates commitment to working with the<br />

government on CrossRail.<br />

Airline: • Improve passenger access to <strong>Heathrow</strong> from cross<br />

London locations<br />

• Encourage increased use of <strong>Heathrow</strong> airlines<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Rail Red Outline<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

£TBC<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

Completion on Site:<br />

TBC<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

• BAA contribution to Crossrail has been confirmed. The assumption is that the<br />

Crossrail project will be undertaken and completed as planned.<br />

• BAA’s contribution is fixed at £180M at Q1 2007 press.<br />

• The contribution will be paid in two instalments linked to progress on construction<br />

of the Stockley Works, which will deliver greater capacity and reliability for rail<br />

services into <strong>Heathrow</strong>.<br />

• The contribution will be paid by <strong>Heathrow</strong> <strong>Airport</strong> Ltd<br />

• Crossrail will operate four times per hour between the hours of 07:00 to 21:00 on<br />

weekdays, 09:00 to 21:00 on Saturdays and 12:00 to 21:00 on Sundays. At other<br />

times the service will run two times per hour. This will significantly improve access to<br />

<strong>Heathrow</strong> for 185,000 passengers and 72,000 airport workers every day.<br />

• Crossrail services are in addition to the four trains per hour non-stop <strong>Heathrow</strong><br />

Express services which will continue to operate. It will replace the existing <strong>Heathrow</strong><br />

Connect stopping service that runs from Terminal 4 to London Paddington.<br />

• The total length of Crossrail is 118.5km, including 41.5km in tunnels. 38 stations<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 421


will be served by the line and 24 trains an hour will run through the central section<br />

in each direction at peak times.<br />

Operational Issues<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Commentary:<br />

Cost Area:<br />

Revenue<br />

Cost<br />

&<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

The introduction of CrossRail in Q6 - 2017/18 - will<br />

significantly impact both <strong>Heathrow</strong> Express &<br />

Connect services; the assumption is that CrossRail<br />

will take over 100% of T4 rail passenger traffic, and<br />

50% of CTA traffic.<br />

Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

Crossrail’s introduction will significantly impact BAA Rail (Hex and Connect). It is not yet<br />

clear what the impact will look like.<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 422


Appendix A: Overview: Reference Drawing / Image:<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 423


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

<strong>Heathrow</strong> Express Growth Projects FQ/Q7<br />

0000 : Hex Growth Projects (FQ)<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Projects to improve revenue earning opportunities for<br />

<strong>Heathrow</strong> Express<br />

None<br />

Objectives:<br />

BAA: • Increase revenue earning through:<br />

• Improving customer experience<br />

Make it easier to buy tickets and travel on HEx/ Connect<br />

services – eg. Airside ticket desks; e and m ticketing<br />

development<br />

• Exploit non fare revenue earning opportunities eg. Build<br />

digital Advertising infrastructure on rail network<br />

• Signage improvements to ensure ease of location of HEx<br />

network<br />

Airline: • Improve passenger access to <strong>Heathrow</strong><br />

• Encourage increased use of <strong>Heathrow</strong> airlines<br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Rail Red Various<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

£TBC<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

Completion on Site:<br />

TBC<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

This “project” is an allowance. Each project delivered using these funds will be<br />

evaluated on its individual merits in terms of value to the Hex business<br />

Operational Issues<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Commentary:<br />

Cost Area:<br />

Pax / Revenue<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Revenue impact will be estimated on each project<br />

individually,.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 424


Impact on User Charges: Not included in CIP <strong>2009</strong> Publication<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 425


Header Information<br />

Project Name:<br />

Name in<br />

Schedule<br />

<strong>Heathrow</strong> Express Renewal Projects<br />

0000 : Hex Renewal Projects (FQ)<br />

Project Overview, Objectives and Status<br />

Overview:<br />

Description:<br />

Ref. Drawings / Images:<br />

(Refer to Appendix A)<br />

Projects to renew <strong>Heathrow</strong> Express rail assets through Major<br />

repair or replacement.<br />

None<br />

Objectives:<br />

BAA: • Maximise useful asset lives<br />

• Ensure asset availability maximised<br />

• Protect customer experience<br />

• Minimise ongoing cost of maintenance through proactive<br />

identification replacement needs<br />

Airline: • Maintain/ improve passenger access to <strong>Heathrow</strong><br />

• Encourage increased use of <strong>Heathrow</strong><br />

Status:<br />

BAA Lead Team: Airline Engagement: Strategic Solution or DGS/IGS Stage<br />

Rail Red Various<br />

Project Delivery<br />

Current Control Budget:<br />

Total <strong>Capital</strong> Budget (Constant Prices):<br />

Time:<br />

Brief<br />

Decision:<br />

£TBC<br />

Refer to appendix B for cost information detail.<br />

Start on<br />

Site:<br />

Completion on Site:<br />

TBC<br />

Refer to appendix C for programme information detail.<br />

Operational Use<br />

Commences:<br />

Assumptions:<br />

The following points cover the significant delivery assumptions related to this project;<br />

Each project will be evaluated on its individual merits / needs / value to business<br />

Note: Assumptions stated here are to aid understanding and are not necessarily exhaustive.<br />

Operational Issues<br />

Financial Revenue and Operational Cost (Opex) Impact:<br />

Revenue / Opex<br />

Commentary:<br />

Cost Area:<br />

Revenue / Cost<br />

Revenue (+) /<br />

Cost (-) Impact<br />

per Annum:<br />

Impact on User Charges:<br />

Estimated Per Passenger Cost Impact:<br />

Commentary:<br />

None<br />

Maintenance projects are implemented to protect<br />

revenues and minimise costs, through ensuring rail<br />

assets are available, fully functional throughout<br />

their useful lives.<br />

Not included in CIP <strong>2009</strong> Publication<br />

Impact not known.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 426


Note: Impact on User Charge is subject to a number of complex variables and regulatory decisions and therefore<br />

information is indicative only.<br />

Assumptions:<br />

The following points cover the significant operational assumptions related to this<br />

project;<br />

None<br />

Areas of Disagreement<br />

The following points cover any significant areas of disagreement between BAA and the<br />

Airline Community regarding this project.<br />

None<br />

Note: Any disagreement noted must be read in the context of the airline engagement status shown above.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 427


Tracker CIP 2008 to CIP <strong>2009</strong><br />

Appendix P: Tracker CIP 2008 to CIP <strong>2009</strong><br />

In response to Airline requests and to aid clarity in the interpretation of CIP <strong>2009</strong>, HAL<br />

have prepared this appendix.<br />

Notes on each column in tracker table;<br />

CIP 2008 Information:<br />

CIP Ref No. = CIP 2008 and earlier iterations used an bespoke numbering system. This is<br />

being discontinued and is shown in the tracker for clarity only.<br />

Line / Project Description = This is the wording as shown in CIP 2008.<br />

Additional Comment = This column is used to identify any lines that were “hidden” (i.e.<br />

below £3m) in Appendix 1 of CIP 2008 and are now relevant to interpretation of CIP<br />

<strong>2009</strong>. (Appendix 1 of CIP 2008 listed projects over £3m. Projects of a lesser budget<br />

value were not shown, but did contribute to the totals.)<br />

CIP <strong>2009</strong> Information:<br />

Revised Project Name = This shows any major change in project name from CIP 2008 to<br />

CIP <strong>2009</strong>. E.g. Mid-field Pier becoming T2B.<br />

BCT No. = BCT stands for Business Case Tool which is an internal BAA software tool.<br />

This is the unique reference number that can be used to locate projects on the CIP <strong>2009</strong><br />

Cost Schedule.<br />

PDS? = This advises if the project has, in CIP <strong>2009</strong>, one or more PDS sheets.<br />

Additional Commentary = Comments to clarify and more complex changes between CIP<br />

2008 and CIP <strong>2009</strong>.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 428


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 429


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 430


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 431


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 432


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 433


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 434


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 435


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 436


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 437


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 438


Appendix Q: Cost Schedules<br />

Cost Schedules<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 439


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 440


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 441


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 442


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 443


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 444


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 445


Appendix R: Time Schedules<br />

Time Schedules<br />

The information presented in this appendix is extracted from February <strong>2009</strong> month end data, which will also be used as the basis for IBR5 analysis discussed in the main document.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 446


Trigger Milestones<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 447


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 448


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 449


All Milestones<br />

The tables of all milestone status presented have been provided in preference to Gantt chart style programme information in order to allow simple review to be undertaken.<br />

Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 450


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 451


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 452


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 453


Internal File Name: 0903XX-CIP <strong>2009</strong> Main Document-V71-IG 454

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!