Wednesday 30 March 2011

Metro Performance Update #2

This is my second blog entry showing actual data on Metro's performance.
 
Metro Performance Update #1 (MPU1) supported my argument that Metro's performance statistics are NONSENSE.  It was based on a small number of observations, so there was obviously a risk that random outcomes were making things look worse than they were.  See the blog entry for details.

Performance has been really quite consistent since MPU1.  That is, consistently poor.  There has been a slight deterioration in perfromance of city bound trips, and a slight improvement in performance on Sandringham bound trips.  All the MPU2 data is shown at the bottom of this entry.

To ensure that this blog has integrity, I have only recorded data for trips that I have taken.  In addition, I have noted disruptions to other services that I become aware of (either through physical observation or receiving SMS updates from Metro).  I don't intend to capture and analyse these disruptions with vigour, but I thought it would be worth making a note of what I've seen to date on trips to the city.  Remember that this is in addition to the poor performance captured by my core data.

Date Other disruption on trips to city
17/03/2011 7.58 cancelled, 8.17 running around 7 minutes late.
18/03/2011 8.17 cancelled.
22/03/2011 8.08 running about 9 minutes late.
23/03/2011 8.08 cancelled.
30/03/2011 8.17 running about 8 minutes late.


Now, I don't have the data to support this argument properly, but it does look like Metro is failing to meet its reliability performance hurdle during rush hour periods.  Remember that the target is for no more than 2% of services to be cancalled.

But, back to my punctuality data (the real focus of this blog).  MPU2 again shows that rush hour performance is much worse than the statistics that Metro publishes.  Of the 23 train trips that I have taken, 43.48% have been 5 minutes or more late.  On the run into the city in the morning, 46.15% have been 5 minutes or more late.

This level of service just isn't good enough.  Melbourne deserves better.  Metro's performance statistics are NONSENSE.  Please tell you friends and family about this blog.  The more people that become aware of this issue, the better.  And I'd love to have some regular readers!


Performance Update #2


All journeys in observation period
Number of trips in observation period 23
Trips 5 minutes or more late 10
Proportion of trips late 43.48%
Cumulative minutes late 96
Average minutes late 4.17



Trips to the city
Number of trips in observation period 13
Trips 5 minutes or more late 6
Proportion of trips late 46.15%
Cumulative minutes late 58.32
Average minutes late 4.49

Detailed trip data:
DateFrom SandringhamMinutes late at Flinders Street
09/03/20118:173.73
10/03/20118:270.83
11/03/20118:170.47
16/03/20118:170.25
17/03/20118:278.83
18/03/20118:085.10
21/03/20119:202.00
22/03/20118:178.17
23/03/20118:278.47
24/03/20118:171.33
28/03/20118:178.30
29/03/20118:274.33
30/03/20118:276.50



Trips from the city
Number of trips in observation period 10
Trips 5 minutes or more late 4
Proportion of trips late 40.00%
Cumulative minutes late 37.48
Average minutes late 3.75



Until my next update, good luck with your commuting.  You'll need it.