20.01.2013 Views

R A I LT R AC K - The Railways Archive

R A I LT R AC K - The Railways Archive

R A I LT R AC K - The Railways Archive

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

2.2<br />

2.2 Consultation with our customers,<br />

funders and passengers<br />

Last year, we strengthened our account planning through a<br />

structured exercise to agree with each of our train operating<br />

customers – and with each of the Passenger Transport<br />

Executives (PTEs) – a statement of their reasonable<br />

requirements.Customers and funders were invited to<br />

set out their requirements,which resulted in over 2,000<br />

individual proposals varying widely in both scale and type.<br />

Each was discussed with the customer or funder to agree<br />

output deliverables.<br />

We have taken forward those requirements which:<br />

• represent ways of delivering an output for which we are<br />

already funded (eg in meeting our criteria for<br />

maintenance and renewal of the network,including<br />

renewal in modern equivalent form);or<br />

• relate to enhancement of the capability or capacity of<br />

the network (or are for additional train services where<br />

no access agreement currently exists) where the<br />

requirement is consistent with the relevant Route<br />

Strategy. In these cases, we will examine how risks and<br />

benefits might be shared.<br />

Table A Analysis of customer requirements received<br />

and proposals for action<br />

Source:Railtrack analysis<br />

30%<br />

20%<br />

10%<br />

Completed or withdrawn<br />

Account management process<br />

Access agreement negotiation<br />

Operational performance<br />

Track quality<br />

Renewal programme<br />

Enhancement feasibility study<br />

Enhancement included in NMS<br />

Still under discussion<br />

A summary of the types of requirements received from<br />

customers and funders is shown in Table A.<br />

Further information is given in Appendix 4.<br />

Requirements relating to enhancement of the network are<br />

also referred to in each Route Strategy of this document.<br />

<strong>The</strong> agreed outcome of each reasonable requirement<br />

relating to development of the network is shown in the<br />

relevant Route Strategy, including the impact on options for<br />

solving capacity constraints.Significant requirements,and the<br />

agreed way forward,are also set out in the relevant<br />

descriptions of Route Strategies in this NMS.Where the<br />

requirements relate to performance or track quality, these<br />

have been considered as part of the network-wide<br />

commitments that we have given.Requirements concerning<br />

our renewals programme, including incremental<br />

improvement options where possible, are being discussed<br />

with each customer. At the time that this NMS went to<br />

press,a small number of requirements (2%) were still being<br />

discussed with customers to agree a way forward.<br />

Action plans have been agreed either to implement<br />

each reasonable requirement,or to carry out the next stage<br />

of feasibility or development work.<strong>The</strong>se are now<br />

incorporated into the Account Plans,whether or not details<br />

of the proposal are published in this NMS,and will be used<br />

to monitor and report progress.Where new or modified<br />

requirements arise in future, these will be treated in the<br />

same way.<br />

Discussions have also been held with the Franchising<br />

Director to understand his requirements for changes to the<br />

output of the network.Those requirements related to the<br />

capacity and capability of routes,such as frequencies or<br />

journey times, have been considered within the relevant<br />

Route Strategies.<br />

Discussions have also<br />

been held with the<br />

Franchising Director<br />

to understand his<br />

requirements for<br />

changes to the output<br />

of the network<br />

23

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

Saved successfully!

Ooh no, something went wrong!