19.01.2013 Views

Ticketing and Concessionary Travel on Public Transport - United ...

Ticketing and Concessionary Travel on Public Transport - United ...

Ticketing and Concessionary Travel on Public Transport - United ...

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.

Integrati<strong>on</strong> Nati<strong>on</strong>ally<br />

<strong>Transport</strong> Committee: Evidence Ev 125<br />

1.12 Nati<strong>on</strong>ally, there are significant structural, legal <str<strong>on</strong>g>and</str<strong>on</strong>g> commercial barriers to ticketing integrati<strong>on</strong>.<br />

1.13 Barriers <strong>on</strong> the rail network include:<br />

(a) The fact that the TOCs carry the revenue risk within the franchise agreement <str<strong>on</strong>g>and</str<strong>on</strong>g> therefore any<br />

change to ticketing or fares policy (whosoever makes it) is seen as a potential risk to their business.<br />

(b) An integrated ticketing system requires a level of cooperati<strong>on</strong> <str<strong>on</strong>g>and</str<strong>on</strong>g> sharing that is culturally diYcult<br />

for a competiti<strong>on</strong>-based industry focused <strong>on</strong> short to medium term profit maximising, particularly<br />

if it requires any significant capital investment with a l<strong>on</strong>ger payback period than the durati<strong>on</strong> of<br />

the franchise.<br />

(c) As a c<strong>on</strong>sequence of the value of the franchise agreements they are caught by the European<br />

mergers <str<strong>on</strong>g>and</str<strong>on</strong>g> competiti<strong>on</strong> rules. Since the TOC owning groups are mostly also major UK bus<br />

operators, they can be reluctant to integrate fully nati<strong>on</strong>al rail <str<strong>on</strong>g>and</str<strong>on</strong>g> local bus services in order to<br />

avoid the possibility of being regarded as having exploited a dominant positi<strong>on</strong>.<br />

(d) The diVering characteristics of each TOC (traditi<strong>on</strong>ally characterised as L<strong>on</strong>d<strong>on</strong> <str<strong>on</strong>g>and</str<strong>on</strong>g> South East<br />

(LSE), Intercity, <str<strong>on</strong>g>and</str<strong>on</strong>g> Regi<strong>on</strong>al) is a barrier to integrati<strong>on</strong>. There is a str<strong>on</strong>g <str<strong>on</strong>g>and</str<strong>on</strong>g> positive business<br />

case for those franchisees for LSE TOCs, where there is heavy usage <str<strong>on</strong>g>and</str<strong>on</strong>g> where overcrowding is<br />

an issue. But “pay-as-you-go” from a stored value <strong>on</strong> the card has little benefit from a passenger’s<br />

perspective for Intercity services where the average fare value is over £20. Passengers will not want<br />

to tie up cash to pay Intercity fare levels from a stored value. C<strong>on</strong>versely, in regi<strong>on</strong>al TOCs the<br />

fare paid by the passenger is <strong>on</strong>ly c25% of the real cost of providing the service (eg Arriva Trains<br />

Wales or Northern franchise) <str<strong>on</strong>g>and</str<strong>on</strong>g> in these cases the value of an integrated system is a functi<strong>on</strong> of<br />

the importance of an integrated system with local bus services.<br />

(e) Who is, or will be, the customer with the visi<strong>on</strong> to drive it forward?<br />

1.14 On the bus network, the barriers to integrati<strong>on</strong> include:<br />

(a) the de-regulati<strong>on</strong> of bus services outside of L<strong>on</strong>d<strong>on</strong> <str<strong>on</strong>g>and</str<strong>on</strong>g> the multiplicity of small operators mean<br />

it is diYcult to deliver a nati<strong>on</strong>al integrated system unless it is m<str<strong>on</strong>g>and</str<strong>on</strong>g>ated at the outset as part of<br />

an operators’ licence—this may be possible through the interventi<strong>on</strong> of PTEs; <str<strong>on</strong>g>and</str<strong>on</strong>g><br />

(b) Nati<strong>on</strong>ally integrated ticketing will be low <strong>on</strong> the agenda for the multitude of small local bus<br />

operators because they will be reluctant to pay for the infrastructure cost associated with a<br />

Nati<strong>on</strong>al system.<br />

2. Does the Government have an adequate strategy for developing the integrati<strong>on</strong> of ticketing systems?<br />

2.1 No, TranSys does not believe that the current strategies being pursued will result in a Nati<strong>on</strong>al<br />

integrated ticketing system in the short to mid term that truly benefit both regular mass transit passengers<br />

<str<strong>on</strong>g>and</str<strong>on</strong>g> operators.<br />

2.2 The current strategies are:<br />

— to m<str<strong>on</strong>g>and</str<strong>on</strong>g>ate ITSO compliant cards <strong>on</strong> nati<strong>on</strong>al rail in franchise agreements <str<strong>on</strong>g>and</str<strong>on</strong>g> require bidders to<br />

submit bids for smartcard schemes;<br />

— TranSys is not aware of any policy <strong>on</strong> buses other than to m<str<strong>on</strong>g>and</str<strong>on</strong>g>ate ITSO cards; <str<strong>on</strong>g>and</str<strong>on</strong>g><br />

— integrati<strong>on</strong> of L<strong>on</strong>d<strong>on</strong> into a nati<strong>on</strong>al scheme will be by requiring TfL to accept ITSO cards.<br />

2.3 TranSys believes this will not deliver an integrated ticketing system because:<br />

— A nati<strong>on</strong>al integrated ticketing system is an achievable but very complex system—the ticket<br />

medium (smartcard) or ITSO specificati<strong>on</strong> used <strong>on</strong> the card is <strong>on</strong>ly a small element in that system.<br />

Other key features of a successful integrated system are base data, ticket logic <str<strong>on</strong>g>and</str<strong>on</strong>g> fares tables,<br />

revenue allocati<strong>on</strong> protocols, inter-device <str<strong>on</strong>g>and</str<strong>on</strong>g> device-to-communicati<strong>on</strong>s processing<br />

communicati<strong>on</strong>s protocols, security protocols, comprehensive business rules <str<strong>on</strong>g>and</str<strong>on</strong>g> operati<strong>on</strong>al<br />

rules, data outputs <str<strong>on</strong>g>and</str<strong>on</strong>g> formats, system <str<strong>on</strong>g>and</str<strong>on</strong>g> equipment redundancy, disaster recovery<br />

arrangements, maintenance <str<strong>on</strong>g>and</str<strong>on</strong>g> service levels <str<strong>on</strong>g>and</str<strong>on</strong>g> device availability.<br />

— The ITSO specificati<strong>on</strong> is “permissive” (allowing diVering soluti<strong>on</strong>s <str<strong>on</strong>g>and</str<strong>on</strong>g> opti<strong>on</strong>s) rather than<br />

“definitive” (providing a measurable <str<strong>on</strong>g>and</str<strong>on</strong>g> defined envelope of parameters or performance). It is<br />

therefore capable of being met by a number of diVerent interpretati<strong>on</strong>s.<br />

— By allowing multiple operators to develop smartcard soluti<strong>on</strong>s within franchises there is the danger<br />

that they develop ITSO compliant soluti<strong>on</strong>s that meet their franchise obligati<strong>on</strong> but do not<br />

c<strong>on</strong>sider a nati<strong>on</strong>al perspective as part of the delivery <str<strong>on</strong>g>and</str<strong>on</strong>g> are therefore unlikely to be an integrated<br />

soluti<strong>on</strong>. The worst outcome would be a passenger taking a journey from (for example) Bright<strong>on</strong><br />

to Birmingham that requires 3 separate smartcards.<br />

— Following the franchise replacement route will mean that a totally integrated ticketing system will<br />

not be available until late in the next decade.

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

Saved successfully!

Ooh no, something went wrong!