|
Post by DE20106 on Jul 7, 2024 22:15:48 GMT
It's bad enough TfL's taken so long to catch up on LED displays for buses only to then stop at full rear displays being optional. I'm especially a bit disappointed Go Ahead never went for them as for starters they make the E400EVs look even better throughout than they already do. I do wonder if TfL will eventually make that spec an obligation for later orders, like they did with the electric mirrors. A spec is coming soon apparently according to the latest bus design standards. I’m really hoping this new spec includes perfectly programmed Johnston destination screens 😂
|
|
|
Post by COBO on Jul 8, 2024 3:04:33 GMT
When did the 474’s SO’s enter service?
|
|
|
Post by lonmark on Jul 8, 2024 3:30:44 GMT
When did the 474’s SO’s enter service? I don't think SO belonged to 474 but it started on 425 instead on 5th July 2008.
|
|
|
Post by COBO on Jul 8, 2024 3:40:18 GMT
When did the 474’s SO’s enter service? I don't think SO belonged to 474 but it started on 425 instead on 5th July 2008. When did the OmniDekka’s enter service?
|
|
|
Post by cl54 on Jul 8, 2024 4:41:23 GMT
What other checks are being skipped before buses go on the road? Compliance is there for a reason. The fault may have occurred once the vehicle was on the road.... The comment was about covering the Bus stopping message with masking tape. A driver wouldn't have done that. In any case if a fault occurs whilst the bus is in service it should be subbed at the first opportunity. One example I saw a while back when I was on a 386 where the windscreen wipers were faulty.
|
|
|
Post by southlondon413 on Jul 8, 2024 7:33:42 GMT
The fault may have occurred once the vehicle was on the road.... The comment was about covering the Bus stopping message with masking tape. A driver wouldn't have done that. In any case if a fault occurs whilst the bus is in service it should be subbed at the first opportunity. One example I saw a while back when I was on a 386 where the windscreen wipers were faulty. A windscreen wiper impedes operation and vehicle functionality, so yes the bus should be subbed or a mobile engineer should visit the bus whilst on stand to assess it. An iBus display that is functioning as in showing the next stop, declaring voice announcements but continually showing “Bus Stopping” is not going to impede operations so, in my opinion, the bus wouldn’t need to be taken out of service. Common sense would prevail and it would be merely be a “note it and maintenance will look at it later” situation. They don’t even take buses out of service for faulty oyster readers.
|
|
|
Post by enviroPB on Jul 8, 2024 10:30:38 GMT
I don't think SO belonged to 474 but it started on 425 instead on 5th July 2008. When did the OmniDekka’s enter service? Online documentation is pretty vague, but the 55 plate OmniDekkas likely came for the 474 extension to Manor Park in December 2005.
|
|
|
Post by redexpress on Jul 8, 2024 11:30:09 GMT
When did the OmniDekka’s enter service? Online documentation is pretty vague, but the 55 plate OmniDekkas likely came for the 474 extension to Manor Park in December 2005. That's correct, the 5 SOs were ordered for the 474 extension.
The 425 (mentioned in another post above) used the 08-reg SOCs.
|
|
|
Post by southlondon413 on Jul 8, 2024 11:35:47 GMT
Online documentation is pretty vague, but the 55 plate OmniDekkas likely came for the 474 extension to Manor Park in December 2005. That's correct, the 5 SOs were ordered for the 474 extension.
The 425 (mentioned in another post above) used the 08-reg SOCs.
If I’m not mistaken those SOs were amongst the last vehicles to be refurbished into GAL livery for TfL service before the rules changed in 2011.
|
|
|
Post by vjaska on Jul 8, 2024 11:52:21 GMT
When did the 474’s SO’s enter service? I don't think SO belonged to 474 but it started on 425 instead on 5th July 2008. The SO’s were for the Manor Park extension of the 474 in 2005 as stated by others and ran alongside the V reg TL’s which was were new in 1999. The SOC’s were for the 425 and were late on delivery for the route which began service with a collection of Blue Triangle Presidents alongside hired in ones from other operators and within the Go-Ahead group.
|
|
|
Post by cl54 on Jul 8, 2024 12:12:11 GMT
The comment was about covering the Bus stopping message with masking tape. A driver wouldn't have done that. In any case if a fault occurs whilst the bus is in service it should be subbed at the first opportunity. One example I saw a while back when I was on a 386 where the windscreen wipers were faulty. A windscreen wiper impedes operation and vehicle functionality, so yes the bus should be subbed or a mobile engineer should visit the bus whilst on stand to assess it. An iBus display that is functioning as in showing the next stop, declaring voice announcements but continually showing “Bus Stopping” is not going to impede operations so, in my opinion, the bus wouldn’t need to be taken out of service. Common sense would prevail and it would be merely be a “note it and maintenance will look at it later” situation. They don’t even take buses out of service for faulty oyster readers. Sorry but a working Bus stopping display is a requirement of the Disability Discrimination Act and TfL requirements. Oyster card readers are not essential to the operation of the bus.
|
|
|
Post by southlondon413 on Jul 8, 2024 12:15:12 GMT
A windscreen wiper impedes operation and vehicle functionality, so yes the bus should be subbed or a mobile engineer should visit the bus whilst on stand to assess it. An iBus display that is functioning as in showing the next stop, declaring voice announcements but continually showing “Bus Stopping” is not going to impede operations so, in my opinion, the bus wouldn’t need to be taken out of service. Common sense would prevail and it would be merely be a “note it and maintenance will look at it later” situation. They don’t even take buses out of service for faulty oyster readers. Sorry but a working Bus stopping display is a requirement of the Disability Discrimination Act and TfL requirements. Oyster card readers are not essential to the operation of the bus. Reread what I wrote, whenever I’ve them like I described the visual is still displaying the next stop and the audio is still announcing. They are just stuck displaying “Bus Stopping” on the lower line. Otherwise it is fully functional. Better yet read this slowly so you can understand what I’m typing out.
|
|
|
Post by mkay315 on Jul 8, 2024 12:46:06 GMT
I don't think SO belonged to 474 but it started on 425 instead on 5th July 2008. The SO’s were for the Manor Park extension of the 474 in 2005 as stated by others and ran alongside the V reg TL’s which was were new in 1999. The SOC’s were for the 425 and were late on delivery for the route which began service with a collection of Blue Triangle Presidents alongside hired in ones from other operators and within the Go-Ahead group. Exactly that. To also add another point to this was that in 2007 when Blue Triangle became a part of Go Ahead, Docklands buses joined a year prior they decided to do busical chairs which involved the 248 and 474. In November 2007 the 474 became 24 hrs and as a result they ended up swapping the East Lancs Loylnes (TLs or DLs depending on which era one remembered them coded as) that was on the 248 with the 474 and the Omnidekkas went the other way for a bit but then when the 248 went to Stagecoach in 2008 the Omnidekkas went back onto the 248 as Go Ahead wanted to do a mass cleansing of the Blue Triangle vehicles. I did miss them floating around East Ham and Canning Town
|
|
|
Post by southlondonbus on Jul 8, 2024 13:12:25 GMT
I don't think SO belonged to 474 but it started on 425 instead on 5th July 2008. The SO’s were for the Manor Park extension of the 474 in 2005 as stated by others and ran alongside the V reg TL’s which was were new in 1999. The SOC’s were for the 425 and were late on delivery for the route which began service with a collection of Blue Triangle Presidents alongside hired in ones from other operators and within the Go-Ahead group. Those SOCs had quite a short london life really. I did use them a few times on the 425 and they had an usual seat design. I think 10 were ordered?
|
|
|
Post by cl54 on Jul 8, 2024 14:02:23 GMT
Sorry but a working Bus stopping display is a requirement of the Disability Discrimination Act and TfL requirements. Oyster card readers are not essential to the operation of the bus. Reread what I wrote, whenever I’ve them like I described the visual is still displaying the next stop and the audio is still announcing. They are just stuck displaying “Bus Stopping” on the lower line. Otherwise it is fully functional. Better yet read this slowly so you can understand what I’m typing out. Plenty of nothing displayed on the bottom line on the single deckers on my local routes from MG. I'm not mentioning the other part of the display. No need to reread where you are making excuses for the operator.
|
|