Electronic Bus Service Registration and TransXChange

What are EBSR & TXC?

TransXChange (TXC) Is a data transfer protocol that has been developed to

allow for data on passenger transport services to be transferred in a standard and consistent format

Electronic Bus Service Registration (EBSR) Is a business process that allows bus service registrations

to be submitted to VOSA and local authorities in an electronic format.

To ensure that data is provided in a standard format, this process uses TXC to structure the data that is included in the registration

Why Do We Need EBSR & TXC?

The origins of TXC & EBSR lie in a move to modernise systems that began in the late 1990’s affecting both VOSA and the increasing need to share data about public transport services VOSA – programme to update their business systems &

processes and make them suitable for 21st Century (TAN21 Programme)

Wider transport information community – development of Traveline and emergence of new systems such as RTI

Both of these initiatives challenged the traditional view of bus data and bus registrations

The Bus Schedule …Different Interpretations

Bus operator’s registration Timing points Sufficient data to show route taken

Local authority (or traveline) schedule database

All stops served Interpolated times Sketchy beyond area boundary

Real-time system Precise times Seasonal/ date variations Vehicle allocation

Coarse: sufficient detail to meet regulations

Medium: sufficient detail for journey planning

Fine: detail necessary to drive real-time stop signs

The Bus Schedule …Different Interpretations

Bus operator’s registration Timing points Sufficient data to show route taken

Local authority (or traveline) schedule database

All stops served Interpolated times Sketchy beyond area boundary

Real-time system Precise times Seasonal/ date variations Vehicle allocation

Coarse: sufficient detail to meet regulations

Medium: sufficient detail for journey planning

Fine: detail necessary to drive real-time stop signs

Typically, separate systems; manual intervention in each

The Case For Electronic Data Transfer

Reduce the need for separate systems and manual intervention

Recognise that the bus schedule is material common to core business for:

Bus operator Local transport authority Information provider

Each party has been re-writing/copying bus schedules/routes/timetables

Introducing error Diverting resources Slowing timely delivery

Each party has something to gain from more efficient schedule description & data transfer

What is EBSR?

Moving the bus service registration from paper.....

…To data (suitable for import into other systems) Via the use of the EBSR process and the

TransXChange/XML data format

…And making sure that this data can be reproduced in a readable format Using the TransXChange Publisher

The Role of EBSR An electronic business system and process to

register a bus service with the Traffic Commissioners and VOSA

A formal transaction between parties:- Operators LTAs / PTEs VOSA

A system that can carry the full information required downstream by:-

LTAs Traveline Transport Direct Other information systems

Benefits

Produce schedule once, then share, import & edit electronically

Reduce re-keying of schedules Re-use schedules for operations, publicity,

traveline, real-time etc. Improve timeliness Reduce errors Reduce operational costs Improved visibility of route/timetable details for

operator, local authority/PTE, VOSA etc.

Outline Process/Timelines

Submit Registration to

VOSA

Pre-56 days 56 days 28 days

Registration in operation

Finalise operational details for info.

systems

Clarify any queries on Registration

Pre-Registration discussions

with LA

Service Start Date

Preapre information needed for e.g RTI systems (more detail than for

registrations)

VOSA acceptance. LA notified.

Details available from

VOSA

LA consider imapct on services

Share updates

Timeline VOSA EBSR pilot capability enabled 1 Jun 2007

Registrations submitted from 14 Aug 2007

EBSR became VOSA operational service 20 Sep 2007

Technology launch at York INFORM 8 Nov 2007

VOSA moved pilot to ‘business as usual’ 14 Dec 2007

EBSR Launch by Secretary of State 31 Jan 2008

Progress EBSR is now a fully live service

Operational service at VOSA since December 2007 Formal launch by Secretary of State January 2008

Only one outage since EBSR became operational That was the failure of an external web service used in the process

5 registration failures One of which has led to fix in EBSR Publisher

Service characteristics of successful e-registrations include:- Linear routes Express journeys Forked routes Complex Services (Circulars, Cloverleaf, Lollipop routes etc.) Special day timetables Frequent Services/Long Routes (275 vehicle journeys & 75 stop points) Pick-up/set-down only H&R

Service Registrations & EBSR

At end May 2009

1,435193

4,800

1,67014,306

EBSR Transition Committed OLBS Self-Service Paper

Rollout – Larger Operators Planned:

All remaining Stagecoach companies by end 2009 Further Arriva companies, linked to RTI & other data exchange needs by

end 2009 Firstgroup testing TransXChange file creation & transfer Firstgroup pilot EBSR implementation in Edinburgh & Lothians EYMS pilot implementation starts in 2009 National Express Group pilot data exchange trials in Coventry National Express West Midlands transition during 2009

Under consideration: EBSR Evaluation by National Express Coaches TransXChange evaluation by Go Ahead

Local Authorities & EBSR

At 12 June 2009

17

13

48

41

27

TXC - Local TXC - Traveline Receiving EBSRs Email Set Up Non-EBSR

Rollout – Smaller Operators Various LAs/ PTEs intending to include EBSR in

their bus contracting arrangements Review of internal processes/ systems Consider timing with technology refresh EBSR just small part of electronic bus service tendering system Prior experience in London may be relevant Consider including agency service for small operator commercial

registrations Consider joint work with neighbouring authorities Technical trials started:

Norfolk Kent Buckinghamshire Metro South Yorkshire PTE

EBSR Submissions

At end May 2009

Traffic Area “O” LicencesRegistrations Submitted during “refresh” period

Revisions submitted since

“go live”

Eastern 6 423 197

North East 7 404 66

North West 2 368 127

Scotland 6 712 0

South East & Met

3 159 11

Wales 6 256 52

Western 6 473 67

West Midlands 1 18 0

TOTAL 37 2813 520

Implementing EBSR

The Transition to EBSR

Before an operator switches to EBSR there needs to be an agreed transition process in place Manage the transition from paper to electronic

Local meetings with operators, LTAs and traveline regions before the EBSR process starts

Review EBSR process as it would work for local depots Establish stakeholder requirements & opportunities Review local NaPTAN quality/stop updating Existing registrations submitted as EBSRs to compare

current with electronic data. Resolve any discrepancies Convert fully to EBSR - No reversion to paper!

The Benefits of EBSR for Local Authorities

Faster production of information for leaflets, roadside displays, etc

Faster supply of data to traveline More efficient working with real-time systems Less effort creating interpolation of stop times Develop/ use tools to compare the proposed

against the existing registration From second electronic version onwards

Other Possible Uses of this Data?

Better links with accessibility planning/ Local Transport Plan

Quicker updating of “Accession” data – the annual snapshot of bus service schedules

Smaller operators Working through LTA or others as a registration agent Potential for TXC to be used within LA contract procedures

What do Local Authorities Need for EBSR & TXC?

VOSA set up a mailbox on their system where EBSRs for your area are lodged

LAs/PTEs need to set up an EBSR email address and register this with VOSA

VOSA will advise LAs/PTEs of new registrations received for your area

EBSR files with TXC data made available to LAs/PTEs. How will these be processed? Import to local systems? TXC Publisher?

The Benefits of EBSR for Operators

Simpler process Create data once for a variety of uses No more photocopying/faxing/posting to LAs etc. Fewer queries about proposed registrations Clear version of what is registered (PDF from VOSA)

No risk of missing out Authorities that should receive a copy of the registration

More efficient supply of data to travel information systems

Simpler working with real-time systems

What do Operators Need for EBSR & TXC?

Need to have the capability of producing EBSR or TXC data Scheduling system Use an agent Work with local authorities On-line system?

Make VOSA and affected local authorities aware of your plans

Develop a transition plan – moving from paper to electronic