Save the Train forum

Dedicate to campaigning to retain an appropriate "TransWilts" passenger train service ... Swindon - Chippenham - Melksham - Trowbridge - Westbury - Dilton Marsh - Warminster - Salisbury ... and to other services too

THIS FORUM IS NOW A READ-ONLY ARCHIVE. Please use our Coffeeshop Forum for new posts

link to main site
Save the Melksham Train

Welcome, Guest. Please login or register.
May 23, 2012, 10:17:26 PM

Login with username, password and session length
Search:     Advanced search
Recommended service - hourly, according to the GWRUS. Let's work towards that service and towards ensuring all services are used.
7889 Posts in 5009 Topics by 97581 Members
Latest Member: zftlhiiyfq
* Home Help Search Calendar Login Register
+  Save the Train
|-+  General Discussion
| |-+  Greater Britain
| | |-+  DfT High Level Output Specification - Specimen Capacity Options
0 Members and 1 Guest are viewing this topic. « previous next »
Pages: [1] Print
Author Topic: DfT High Level Output Specification - Specimen Capacity Options  (Read 1208 times)
Lee
Administrator
*****
Offline Offline

Posts: 3633


View Profile WWW
DfT High Level Output Specification - Specimen Capacity Options
« on: August 20, 2007, 03:48:36 PM »

A guide to where extra carriages may be deployed (link below.)
http://www.dft.gov.uk/about/strategy/whitepapers/whitepapercm7176/railwphlsospecimen
Logged
Industry Insider
Sr. Member
****
Offline Offline

Posts: 128


View Profile
Re: DfT High Level Output Specification - Specimen Capacity Options
« Reply #1 on: August 20, 2007, 06:51:13 PM »

"Illustrative specimen capacity enhancement options were developed by DfT, and modelled in the Network Modelling Framework (NMF), to demonstrate that the HLOS output metric requirements can be delivered within the Statement of Funds Available; as outlined in the Schedule to Appendix A of the Rail White Paper ‘Delivering a Sustainable Railway."

Good to see a nice friendly worded catchy opening paragraph to the document...  Roll Eyes

Great Western – Provision of additional 2tph 6-car semi-fast Reading-Paddington service, with the existing Paddington - Greenford service running between Greenford and West Ealing at enhanced frequencies.  Additional suburban train lengthening, 7-cars in the peak from Reading and 6-cars from Slough.

I've often thought that the Paddington-Greenford service running at 30 minute intervals in the peak with a maximum of 2 coaches (due to platform lengths) was a huge waste of peak capacity, given that West Ealing has land owned by the railway that could easily be transformed into a nice little bay platform. OK, the relatively small number of commuters from Paddington/Acton/Ealing Broadway to Drayton Green/Castle Bar Park/Greenford would have extended journey times and a change of train at West Ealing, but overall it would offer so many extra seats on the other suburban routes out of Paddington that means it would be of huge benefit.

The first time I heard this officially mentioned was in this year's Network Rail Business Plan and all of a sudden it seems to be gaining support. It would also enable an increase to 3tph between West Ealing and Greenford using the same two trains that provide a 2tph sevice on the through route. Most people would be benefitting from the scheme. However you watch complaints flood in from various organisations and the public about cutting the through trains from London.

The question I am interested in seeing the answer to is what type of train will provide these additional coaches? With the Pendolinos and some of the other modern trains they can just build extra coaches to the specification of the original order. With the 165/6's used on suburban routes out of Paddington being over 15 years old, I assume they will be new build units, possibly like the 168's build rescently for Chiltern? Does anyone know?

Logged
Pages: [1] Print 
« previous next »
Jump to:  

Powered by MySQL Powered by PHP Save the Train | Powered by SMF 1.0.5.
© 2001-2005, Lewis Media. All Rights Reserved.
Valid XHTML 1.0! Valid CSS!
Page created in 0.313 seconds with 19 queries.