##Introduction
Most UK train users are unaware of their rights, e.g. to compensation after cancellations or delays. This was raised as an issues by the Office for Rail Regulation in its "Rail passenger compensation and refund rights" report, published on 20/2/2014.
Athough the situation is improving, the amount of money paid out in compensation during the last surveyed year was of just by £3m. Our early calculations estimate that the total value of the disservice to UK passengers, calculated as the total value of the compensations they are entitled to, is in the order of £500m every year. More can be done to make Network Rail and the rail operating companies accountable for the disservice they are responsible of.
As much as we accept that not all incidents can be avoided, we believe that the huge amount of compensations that passengers are not claiming is allowing Network Rail and the operating companies to sleep over the problem, minimising intervention while keeping patting each others' backs and awarding their directors 6-digit bonuses (although, to be fair, they only got 5-digit bonuses in 2014...).
Some are fighting this using policy. We believe there is one more channel we can use, that is supporting passengers to do what is in their rights and claim compensation down to the last penny.
##About Railsponsibility
The Railsponsibility project is aimed at building a system to monitor all train services being cancelled or delayed that match the criteria for compensation, to then remind the passengers who were affected of the disservice they were affected by and support them in filing the claim, automating as much as possible the process.
As of today, Raisponsibility can receive requests of monitoring delayed trains by using Twitter and by specifying the stations by using their three-letter codes, e.g. 'EUS' for London Euston (also called the CRS code). Railsponsibility will tweet back in any case at the train's arrival, whatever the delay, even if it is not sufficient to entitle you to compensation. Cancellations are not yet monitored.
To use Railsponsibility, tweet as in the following example. Imagine you are on the train from Berkhamsted (BKM) to London Euston (EUS), scheduled to leave Berkhamsted at 7:32. At some point, you realise that the train is delayed and you want Railsponsibility to monitor that for you. You will tweet:
@railspo from bkm to eus 732
Almost immediately, you will receive an acknowledgement, saying:
@your_twitter_handle thank you for using Railsponsibility, we will tweet back when your train has arrived at EUS dico.im/railspo
Sometime later, after the train arrival, you will receive another tweet, saying:
@your_twitter_handle your train leaving from BKM to EUS at 7:32 has arrived 5 minutes late, at 8:10
If you don't know your stations' CRS codes, look them up here. Sometime soon Railsponsibility will be able to interpret your tweets and understand the stations' full names if you use them.
###It's broken, what should I do?
First check the known issues on the project's GitHub page. If you can't find anything that applies to you, add a new issue, or, alternatively, write to [email protected].
##A bit of history
###International Open Data Day 2014
The first brainstorming and prototyping work was developed for the London Open Data Dat 2014 hackfest. You can read the team's original notes and view the outcome.
Among the contributors were:
... and others who did not leave their contacts! :-( In the picture are, from left to right, giacecco, andylolz, mz2 and, standing, dasmoth. Sorry we don't have a better one.
###Joint Open Data Hackathon
Railsponsibility went on to win the UK Cabinet Office, Stride and Network Rail's "Joint Open Data hackathon" on 18 March 2014, as the best smart transport applications using data available from the sponsors' open data sources.
###Today
The project awoke again on 31/3/14 for additional development by Giacecco focusing exclusively on gathering train arrival data (not only delayed trains). The software has been re-written from the ground-up to be production- rather than hackathon-quality. He also migrated from Stride to Transport API first and then directly to Network Rail's "Data Feed" service, as there is no reason to add more points of failure to the already long chain between the source data and the software.
Active contributors to the project are:
##Licence
The trains schedule and arrival data are sourced from the Network Rail "Data Feeds" service. As a result, Railsponsibility contains information of Network Rail Infrastructure Limited licensed under the following licence http://www.networkrail.co.uk/data-feeds/terms-and-conditions/.
The train operating companies' "business", "numeric" and ATOC codes are sourced from the documentation for the above: the Network Rail Open Data wiki, whose content is licensed under Creative Commons Attribution-ShareAlike 3.0 Unported.
The stations' CRS, NLC, TIPLOC and STANOX codes are sourced from the "Railway Codes and other data" website by Phil Davies. We have contacted him to verify the licensing for the data, that appears to be collated from OGL-ed sources.
The team picture at the International Open Data Day was taken by @raimondiand, the one at the Joint Open Data Hackathon was taken by @eehcnas. Both were enhanced a little by giacecco.