|
Post by Red Dragon on Jan 8, 2017 11:52:33 GMT
Sullivans are advertising for an iBus controller:
If they are just creating it now, how were the 298 and the school routes controlled?
|
|
|
Post by snoggle on Jan 8, 2017 12:05:12 GMT
Sullivans are advertising for an iBus controller: If they are just creating it now, how were the 298 and the school routes controlled? Possibly a shared responsibility amongst other duties at present with responsibility on the drivers to keep to time? As the scale of activity is due to build up considerably then I can see why a dedicated role is being established. The risk of delays is greater across three routes and the 217 is high frequency which, in theory, needs a different management approach to low frequency routes (298 and W9 plus schools).
|
|
|
Post by capitalomnibus on Jan 9, 2017 20:21:14 GMT
Sullivans are advertising for an iBus controller: If they are just creating it now, how were the 298 and the school routes controlled? They have had that on LOTS for a few weeks now.
|
|
|
Post by eggmiester on Jan 10, 2017 12:40:53 GMT
They probably had a supervisor manning the front counter who also looked after the ibus but as others have said their TFL portfolio is growing so will require a dedicated team of controllers to manage the routes during the busiest times and keep the current arrangements for 'out if hours' cover.
Metrobus have a similar thing. Because the Metrobus's ibus is still separate from GAL and they only run 1 night route at present (N119) they have a separate night cover controller who is based at Croydon who from midnight takes control of both C and MB routes until 5am. They also share this role, with managing the front desk at C garage through the night until the first allocation supervisor arrives in the morning.
|
|