Document No. 028 Network Rail HS2 Requirements 13-0409 Appendix

Document No. 028 Network Rail HS2 Requirements 13-0409 Appendix

APPENDIX 1 – REQUIREMENTS Appendix 1.1: Document no. 028 Network Rail HS2 Requirements 13-0409 Appendix 1.2: HS2’s Project Definition Statement (PDS) C241 – Calvert East-West Rail C241-PBR-DS-STA-020-000001 revision P08 Appendix 1.3: Client Requirements Document for the East West Rail Phase 2 project HS2-EWR Integration GRIP 2 Feasibility Report 148476-NWR-REP-MPM-000003 Page 61 of 357 Appendix 1.3: Client Requirements Document for the East West Rail Phase 2 project HS2-EWR Integration GRIP 2 Feasibility Report 148476-NWR-REP-MPM-000003 Page 145 of 357 Client Requirements Document- OP133735 EAST WEST NetworkRail RAIL PHASE 2 -&~ Client Requirements Document OP133735 EAST WEST RAIL PHASE 2 Client Requirements Document Template: ref: NR/PSE/FRM/0239, Issue 02, 10th December 2013 Prepared by : Senior Programme Development ·• :'.,er /i!!.il:fli. {late" t N:! o' 'f Bernmtfffulland Checked by : Programme Development Manager ~ate :oLt/os /L::> r 4 Approved by: Lead Strategic Planner ;iPJ:~~ Date S 3 z.._c l'-r Z{ Tony Rudge Accepted by : Senior Programme Developme~t ~~e r B~ Date s/$1'-oll-f This document is the property of Network Rail. It shall not be reproduced in whole or in part, nor disclosed to a third party without prior written permission. Copyright 2014 Network Rail Document Ref: Issue: 1 CRD Date: 25 February 2014 Page: 1 of 33 Client Requirements Document – OP133735 EAST WEST RAIL PHASE 2 Document History Issue Date Originator Modification 1 25 February Bernard First draft for comment 2014 Hulland 2 3 February Bernard Final Version 2014 Hulland Document Ref: Issue: 1 CRD Date: 25 February 2014 Page: 2 of 33 Client Requirements Document – OP133735 EAST WEST RAIL PHASE 2 Contents 1 Purpose ........................................................................................................................... 4 1.1 Background Information ............................................................................................... 4 1.2 Stakeholders ................................................................................................................ 5 2 General Description of the Scheme................................................................................. 6 2.1 Business Objectives (Aspirations)................................................................................ 6 2.2 Scheme Definition ........................................................................................................ 7 2.3 Boundaries and Relationships ..................................................................................... 7 2.4 Assumptions, Dependencies, Constraints & Risks ...................................................... 7 2.4.1 Assumptions ......................................................................................................... 7 2.4.2 Dependencies ....................................................................................................... 8 2.4.3 Constraints............................................................................................................ 8 2.4.4 Risks ................................................................................................................... 11 2.5 Whole Life Cost Strategy ........................................................................................... 11 2.6 Scheme Key Milestones and Configuration States .................................................... 12 2.7 Scheme Acceptance Strategy.................................................................................... 12 3 Scheme Requirements .................................................................................................. 14 3.1 Safety Strategy - Requirements ................................................................................. 14 3.2 General Scheme - Requirements............................................................................... 14 3.3 Performance Aspiration - Requirements .................................................................... 15 3.4 Maintenance Strategy - Requirements....................................................................... 18 Appendix A - Deliverables..................................................................................................... 19 Appendix B - References ...................................................................................................... 33 Appendix C - Glossary .......................................................................................................... 33 Document Ref: Issue: 1 CRD Date: 25 February 2014 Page: 3 of 33 Client Requirements Document – OP133735 EAST WEST RAIL PHASE 2 1 Purpose 1.1 Background Information The “East West Rail” (EWR) project proposes the introduction of direct rail passenger services between Oxford, Milton Keynes and Bedford, and also between London (Marylebone) and Milton Keynes (via Aylesbury), by reconstructing and upgrading the partially-disused Oxford – Bicester – Bletchley – Bedford, and Princes Risborough - Aylesbury – Claydon Junction routes. The project was promoted for a number of years by the East West Rail Consortium, formed by a partnership of Local Authorities along the line of route, who commissioned a series of studies culminating in 2009 in the issuing of a Project Prospectus, supported by a feasibility report, roughly equivalent to GRIP 3, produced by Atkins. These documents reflected an output specification which delivered a basic pattern of regular passenger services between the main centres served by the EWR route, together with some additional capacity for new freight and inter-regional passenger services, which is referred to today as the “core” scheme. In 2012, the “core” EWR scheme was included in the High Level Output Statement (HLOS) for Control Period 5 (CP5) issued by the Department for Transport (DfT). Subsequently, in recognition of the potential of the reconstructed routes to exploit new markets, the DfT proposed an enhanced output specification, including additional capacity, higher line speeds, and enhanced route availability and loading gauge. The Oxford – Bletchley - Bedford section was also identified as an integral part of the “Electric Spine” proposal to create an electrified network to create additional capacity, primarily for freight, between the south coast and the East and West Midlands. The section of the route between Oxford and Bicester was also proposed for substantial reconstruction under the “Evergreen 3” project, promoted and developed by Chiltern Railways. Following inclusion of the EWR project in the CP5 HLOS, and in order to secure efficiencies in delivery, the works required for both schemes were combined into a composite project as “East West Rail Phase 1”, to be delivered by Network Rail in accordance with timescales dictated by Chiltern’s franchise commitment to start the new Oxford – London service in March 2016. Construction of Phase 1 started in September 2012, and work is now progressing on site. Owing to the enhanced specification now proposed by DfT and the potential need to integrate electrification, the remainder of the EWR project east of Bicester is, at the time of writing, at a much earlier stage of development (about mid-GRIP2), and much work remains to finalise the definitive output specification and secure funding for design and construction. To progress project development, an Industry Plan Group has been convened to secure, by March 2014, support across the industry for enhanced route capabilities. Following this, it is intended that the options identified will be developed and costed, with a view to securing funding for the project in the Final Determination in March 2015. The current programme includes a final completion date of March 2019 to comply with Network Rail’s commitment to deliver the project within CP5, but both the DfT and the EWR Consortium support earlier introduction of the new services by December 2017 if this can be realistically achieved. Document Ref: Issue: 1 CRD Date: 25 February 2014 Page: 4 of 33 Client Requirements Document – OP133735 EAST WEST RAIL PHASE 2 The new EWR route intersects the proposed alignment of High Speed 2 (HS2) near Steeple Claydon, where a major construction site (later to become the main HS2 Infrastructure maintenance Depot) is to be built, and both vertical and horizontal realignment of the Bicester - Bletchley and Aylesbury – Claydon will be necessary. These alterations are included in the HS2 hybrid bill submitted in December 2013 which is planned to receive royal assent in Summer 2015. The HS2 programme assumes that the EWR route will be available for disposal of spoil by rail from West London during 2018, and subsequently HS2 construction traffic between 2020 and 2026. These considerations may result in further enhancement of the EWR output specification, and will influence the EWR delivery programme. 1.2 Stakeholders The following stakeholders have been identified: Name Role Contact Network Rail Paul Plummer Group Strategy Director Paul.plummer @networkrail.co.uk Jo Kaye Director, Strategy & [email protected] Planning (LNW & LNE) David Golding Principal Strategic [email protected]. Planner, LNW Route uk Graham Botham Principal Strategic [email protected] Planner, LNE & EM Route Chris Aldridge Principal Strategic [email protected] Planner, Western Route Bernard Hulland Senior Programme [email protected] Development Manager, East West Rail Francis McGarry Programme Manager, [email protected]

View Full Text

Details

  • File Type
    pdf
  • Upload Time
    -
  • Content Languages
    English
  • Upload User
    Anonymous/Not logged-in
  • File Pages
    35 Page
  • File Size
    -

Download

Channel Download Status
Express Download Enable

Copyright

We respect the copyrights and intellectual property rights of all users. All uploaded documents are either original works of the uploader or authorized works of the rightful owners.

  • Not to be reproduced or distributed without explicit permission.
  • Not used for commercial purposes outside of approved use cases.
  • Not used to infringe on the rights of the original creators.
  • If you believe any content infringes your copyright, please contact us immediately.

Support

For help with questions, suggestions, or problems, please contact us