Rejseplanen – future development

Rejseplanen – future development
The Future of Urban Mobility, 24th February 2015
Birgitte Woolridge, Product Manager, blw@rejseplanen.dk
Agenda
n 
Rejseplanen – who, what and why
n 
BilRejseplanen – an early attempt
n 
Present strategy
n 
Push messages
n 
Future work
+
Rejseplanen setup
n 
n 
n 
Rejseplanen is a public limited company, founded in 2003 – but the
cooperation on a Danish journey planner started in the mid 1990s
n 
Owned by all the PTOs in Denmark (trains, busses, metro)
n 
Small office of 8 people
Products
n 
Iphone, www, Android, iPad, Windows Phone
n 
White labels products & services for owners
n 
Open data policy, API and deals with Google, Apple, Nokia
Operations of servers
n 
n 
Outsourced
Development
n 
Currently future development in tender
n 
Until now majority from HaCon GmbH – supplier of DSB, DB, ÖBB, SBB, SNCF, Railteam
m.fl
+
Rejseplanen facts
n 
Rejseplanen is the preferred channel for public transport information with an
established brand and many users
n 
Awareness of is high, in the Capital region 95% and outside of Copenhagen ca.
70 %.
n 
Every month Rejseplanen shows more than 20 mill journeys
n 
¾ come from mobile phones/apps
n 
On a good/bad(?!) day (weather/disruption) Rejseplanen has more than 1 mill
requests
n 
Rejseplanens apps have been downloaded more than 2 mill times
+
Rejseplanen’s
products are
popular
+
Rejseplanen in the future
n 
Popular products – but lots to work on!
n 
User demands
n 
Better display of fares for journeys
Better data/info on disruptions and delays
n 
”Why can’t I buy a ticket on Rejseplanen?!”
n 
n 
But what about mobility?
n 
We did try a few years ago
+
An early attempt: 2010 BilRejseplanen
+
An early attempt: 2010 BilRejseplanen
n 
In 2010, Rejseplanen and the Danish Road Directorate together launched
”BilRejseplanen” (CarJourneyplanner), comparing public transport with
realistic travel times for the car.
n 
The user could compare the journey on
n 
Time spent
n 
Environmental impact
n 
Costs
n 
Despite efforts to increase the number of users, usage remained low and
BilRejseplanen was closed down again in 2013.
n 
Learnings for Rejseplanen:
n 
Customer demand did not seem to be there at the time
n 
Resources were spent on something that is not the core product => We need to focus
on making public transport information even better before we expand to other modes
of transport
n 
Competition from Google, Nokia, Garmin etc is fierce – difficult to make product good
enough to compete
n 
Owners/PTOs did not at the time involve themselves in similar activities (like DB in
Germany)
+
Good information can improve image and
satisfaction with public transport
n 
Keeping people informed is one of the simplest ways to reduce
complaints, increase satisfaction and gain a reputation for good
customer service, writes David Whitley – Head of Regional Services
at London Midland. It’s all part of thinking like a passenger, and
arguably more important than operational performance itself: a
quick scan through the National Rail Passenger Survey reveals that
Britain’s least punctual train operator has a higher customer
satisfaction rating than Britain’s most punctual! The same survey
points out that handling delays well is the single biggest way to
reduce customer dissatisfaction. In fact, it has three times the
impact of punctuality itself.
Artikel i European Railway Review (http://www.europeanrailwayreview.com/22305/err-magazine/past-issues/
issue-6-2014/developing-and-evolving-rtpi-strategies/?utm_medium=email&utm_term=&utm_content=Read%20This
%20Article&utm_campaign=ERR%20-%20Issue%20%236%202014&utm_source=Email+marketing#.VK_KLaNOVYI)
Why good information isn’t easy…
Rejseplanen receives data from 11 larger train/bus companies and some
minor bus and ferry operators. Data varies in quality.
rm
rture
g term
ort te
a
n
h
p
o
l
s
e
d
–
e
ing
ing
Befor
Plann
Plann
minor
–
o
g
e
On th anges
ch
Timetables
Timetables / HIM
HIM + real time
Real time
125 yearly updates
Mostly used for
planned changes
Varying use/input and
varying quality of
input
Delays and
cancellations
Covers only parts of
the country and not
all means of
transport
Data quality varies
All means of
transport
Fairly good quality
Varying use/input and
varying quality of
input
Web/mobile
Infrequent usage
Rejseplanen relevant today
Web + mobile
– big
o
g
e
On th ption
disru
Textual
information
Either through
HIM or via a feed from
PTAs own webpage.
Does NOT enter the
individual journey
Primarily mobile
and commuters
Rejseplanen less relevant
today
10
+
Rejseplanen strategy 2014-2016
Focus on 4 pillars
Activities with PTOs
Data input
Customer facing activities
Rejseplanen
Manual input (changes)
Automated input (Timeables, realtime)
Data output
Rejseplanen products
Data engine
White label products (at PTOs)
Data quality
Processing
Customer focus
Rejseplanen demands good
data, support all situations of
transport and focuses on joint
solutions for public transport
Data quality is secured
through documented
processes on a stable
system platform
Rejseplanen covers all types of journeys
(commuter/infrequent) and is available on
the entire journey. Rejseplanen supplies
accurate, personal and thrustworthy
information
Cover all of the journey
Rejseplanen focuses on mobile first and
adapts the solution and platform to the
customer’s demand as well as assists with
purchasing of tickets
+
Push services is good
information (if data is okay!)
+
Push services
n 
Based on the same data the customers sees on all platforms –
the data that already comes in from PTOs
n 
Option to receive a message on a specifik train journey or with
busses on Fyn
n 
Not yet ready to offer as commuter based service
n 
Early findings (Wilke report dec. 2014): n 
User indicate that they n  Want to travel more
n 
n 
Have a higher satisfaction with public transport
Believe it can contribute to raising public transport’s image
+
Further future development
n 
n 
n 
Further extend push – more areas, all apps, last minute info
Commuter-based services
n 
Better display of fares
n 
Tickets?
n 
n 
Data, data, data!!!
Mobile first - develop apps, then website
All based on customer demands!
n 
Mobility: One option is 3rd party development based on open
data from Rejseplanen??