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.

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

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!