 I travel quite a lot by train and I suspect lots of you folks do as well. The one thing I really don't like is when the train I'm getting ends up being delayed and I'm sitting there twiddling my thumbs for ages waiting for it to go. When I'm planning a journey, this is the kind of thing going through my head. I want to pick a train that's not going to be delayed, but how do I do that? That's the inspiration behind this ODI summer showcase project. We've built a website that allows you to plug in the details of your train and see how punctual it has been over the past few months. In you put where you're going from. Here we've got Basingstoke going to Waterloo on weekdays at about 8 in the morning. That's a commute I did for a while. It should take about an hour, but sometimes it takes a lot more. You can see straight away over on the right there all the trains that do that journey around then. We've got in particular the 0816 not looking too great. These blocks are for each day of the week and basically it's a scale from green. It means it's very punctual. It's always on time. Down through yellow and orange meaning it's a bit late. Sometimes down to red meaning it's permanently running late. We can see that that second one there is probably the weaker one. Looking a bit closer at it, you can see it's generally most of the time particularly on Wednesdays there. It's been about somewhere in the 5-15 minutes late window. That's not too great. I could actually travel 10 minutes earlier on the train before it and spend a lot less time sitting in delays. Let's have a look at where these delays happen. The three stops on that train goes from Basingstoke and then Woking and then Waterloo. You can see on every day the colour getting a bit worse on the spectrum in that last bit up to Waterloo. Basically what's happening? That train is doing all right up to Woking and then probably rush our congestion on the way into Waterloo is holding it up so it always seems to be late. How do we do this? There's loads of open data in the rail industry. Things like timetables are open. The signalling system provides real-time information on the movement of every train. Every time a train moves around in the network you can get a notification of what's happened. Then national rail enquiries have built this system called Darwin which basically aggregates all this real-time data and non-real-time data like timetables and also some proprietary data from train operating companies that is not available any other way as open data. Pulls it all into one and gives you an open data feed that you can subscribe to. This is widely used systems. The departure boards you see in stations use it. Mobile applications you might have used also use it and our delay explorer on the previous slides uses it. The one catch is it's a real-time feed so it's pumping out data as it happens. So we've had to build a big system to record all that data and analyse it so that we can show you how trains performed over history. So delay explorer is great if you want to sort of geek out or look at your train in detail but if you're actually travelling how can you make use of this information when you're on the go? We build a mobile application called Fasteroot and it's basically live travel information for UK rail and we're starting to incorporate this data from the delay explorer from the summer showcase project into it. The way we've done that so far is we give you this traffic light to these left bars down the left-hand side. We're looking at trains departing from Stoke-on-Trent and you can see the yellow-red green bars. It's basically a traffic light. Green means this train's generally on time. Yellow means this train's a bit unreliable and red means this one's regularly problematic so you might want to avoid it if you've got a choice. And then when you're looking at the details of the train we give you a bit of an explanation. So the example on the right there, the reason it's... You can't really read it, it's a bit blurry on the screen but the reason it's been given a red sort of quality is because it's often 15 minutes or so late. So fairly unreliable as trains go. So if you want to trial this out delayexplorer.fasteroot.com gets you to the website where you can look up the history of trains in detail. You can download the Fasteroot app from the app store or from Google Play. The features I've just shown you around train reliability are in the Android version right now but it'll be a couple of weeks until the update lands in iOS with the same things. And also the code for the delayexplorer is all open source. You can see it on GitHub. So that's all I've got to say but if you're interested in any of this or want to discuss it any more with me, I'm around all day looking to chat to anyone else in this. Thanks.