Does TfL keep a record of which buses start late? And whether the late
start is the driver's fault?
Do they publish the results?

Most people assume there's nothing much the driver can do about late
running buses, aside from things like skipping sections of route (which
is more trouble than it's worth for the passengers) but it's been
observed that occasionally there's an inspector on the B14, and when
that happens it's been running to time (almost unheard of on that
route). And several times I've seen them laid over at Bexleyheath when
they should have started already.

And I'm sure uneven starting times at Woolwich are a big part of the
reason why the 96s are bunched!

--
Aidan Stanger
http://www.bettercrossrail.co.uk

On Sat, 11 Feb 2006 21:54:28 +1030, (Aidan Stanger)
wrote:

Does TfL keep a record of which buses start late?

Yes where these are surveyed.

And whether the late
start is the driver's fault?

Don't know.

Do they publish the results?

Yes

http://www.tfl.gov.uk/buses/about/pe...-route-B14.pdf

Most people assume there's nothing much the driver can do about late
running buses, aside from things like skipping sections of route (which
is more trouble than it's worth for the passengers) but it's been
observed that occasionally there's an inspector on the B14, and when
that happens it's been running to time (almost unheard of on that
route). And several times I've seen them laid over at Bexleyheath when
they should have started already.

As the contract has just changed to a Quality Incentive Contract I
imagine Metrobus will be paying the route a bit more attention.

This shows Metrobus's rank for on time departures for low frequency
services (the B14 is one of those)

http://www.tfl.gov.uk/buses/about/pe...n-time-new.pdf

early running

http://www.tfl.gov.uk/buses/about/pe...-early-new.pdf

Looking at some of the other league tables for mileage and traffic
congestion it seems Metrobus has slipped quite a long way. To what
extent this reflects issues on the Orpington routes you can't determine
from the information available.

And I'm sure uneven starting times at Woolwich are a big part of the
reason why the 96s are bunched!

http://www.tfl.gov.uk/buses/about/pe...e-route-96.pdf

would suggest all is not well given the mileage losses and the below
standard excess waiting time. You can't necessarily say that late
departures by drivers are entirely to blame for that performance level
as the 96 is a long route serving some notorious traffic blackspots.

If you want to see really disastrous performance look up some of the
data for routes run by Centra and then be pleased you don't live on
those routes.

--
Paul C


Admits to working for London Underground!

Paul Corfield typed

early running

http://www.tfl.gov.uk/buses/about/pe...-early-new.pdf

So my impression that Metroline's low-frequency 305 often runs early
might not be an illusion then!

Interesting...

--
Helen D. Vecht:
Edgware.

On Sat, 11 Feb 2006 23:12:41 GMT, Helen Deborah Vecht
wrote:

Paul Corfield typed

early running

http://www.tfl.gov.uk/buses/about/pe...-early-new.pdf

So my impression that Metroline's low-frequency 305 often runs early
might not be an illusion then!

Interesting...

The individual route chart for the 305 shows a bit of topsy turvy
performance for the service. As it is low frequency the performance
"window" is between 2 mins early and 5 mins late of the advertised
departure time. Metroline have struggled to meet the minimum target but
you can't see from the stats how much is early vs late running.

Metroline have lost the 305 on retender to Arriva the Shires (Watford
garage - same as the 142, 340 and now 258). Metroline's overall
performance has slipped badly in the performance rankings and past
performance across the company (on a number of measures) is now used as
part of the tender assessment criteria.

You have to hope that Arriva can do a better job. On my local route
(123) they have certainly improved performance which I will confess is
something of a surprise but a pleasant one nonetheless!
--
Paul C


Admits to working for London Underground!

Beware of the early running stats, however...

It is not always 'early' running that is shown, but it could be very 'late'
running...

For example:

30 min frequency
Bus a is running 25 minutes late, therefore will be picked up in stats as
running early (as for the passenger at the stop arriving 4 mins before
advertised departure time, they will see the back of a bus, and presume it
is running early!)..

Low frequency routes are all about running to time, and therefore, the best
service control could be to hold buses that are running excessively late, to
run them on the time of the next trip, which will result in one set of
passengers being delayed, but the next set not being becuase to all intents
and purposes, the bus has run on time...





"Helen Deborah Vecht" wrote in message
...
Paul Corfield typed

early running

http://www.tfl.gov.uk/buses/about/pe...-early-new.pdf

So my impression that Metroline's low-frequency 305 often runs early
might not be an illusion then!

Interesting...

--
Helen D. Vecht:
Edgware.

"Andy Corbett" typed


Beware of the early running stats, however...

It is not always 'early' running that is shown, but it could be very 'late'
running...

For example:

30 min frequency
Bus a is running 25 minutes late, therefore will be picked up in stats as
running early (as for the passenger at the stop arriving 4 mins before
advertised departure time, they will see the back of a bus, and presume it
is running early!)..

Low frequency routes are all about running to time, and therefore, the best
service control could be to hold buses that are running excessively
late, to
run them on the time of the next trip, which will result in one set of
passengers being delayed, but the next set not being becuase to all intents
and purposes, the bus has run on time...

The 305 passes my door and I watch it like a hawk.

Running 25 minutes late is rather unlikely on a route that's just four
miles long, from end to end.

AIUI 41 minutes are timetabled for the whole return trip!

Off-peak, the bus runs empty and early, so empty that we call it our
personal taxi...

--
Helen D. Vecht:
Edgware.

But then the 305 runs every 15 minutes, so the bus only has to be 10 minutes
late for it to be recorded as the next bus running early!



"Helen Deborah Vecht" wrote in message
...
"Andy Corbett" typed


Beware of the early running stats, however...

It is not always 'early' running that is shown, but it could be very
'late'
running...

For example:

30 min frequency
Bus a is running 25 minutes late, therefore will be picked up in stats as
running early (as for the passenger at the stop arriving 4 mins before
advertised departure time, they will see the back of a bus, and presume
it
is running early!)..

Low frequency routes are all about running to time, and therefore, the
best
service control could be to hold buses that are running excessively
late, to
run them on the time of the next trip, which will result in one set of
passengers being delayed, but the next set not being becuase to all
intents
and purposes, the bus has run on time...

The 305 passes my door and I watch it like a hawk.

Running 25 minutes late is rather unlikely on a route that's just four
miles long, from end to end.

AIUI 41 minutes are timetabled for the whole return trip!

Off-peak, the bus runs empty and early, so empty that we call it our
personal taxi...

--
Helen D. Vecht:
Edgware.

"Andy Corbett" typed


But then the 305 runs every 15 minutes, so the bus only has to be 10
minutes
late for it to be recorded as the next bus running early!

Agreed. It's only that frequent before 7pm though.

--
Helen D. Vecht:
Edgware.