|
Post by capitalomnibus on May 6, 2022 9:46:09 GMT
About time this happened! After spending time in the iBus room at C in particular, I have noticed that even in this modern era, the iBus computer system in particular runs on a Windows XP built programme which doesn’t look like it’s been substantially upgraded since iBus’s introduction in 2008 and only shows the line of route and stops, and buses come up as squares whereas modern day technologies could show iBus controllers a real time map view of where each bus is if used in conjunction with the telematics system on each vehicle. This could also help drivers radio’s to be more clearer, as when I was speaking to a 453 driver in the SW iBus hub last March to tell him to depart the stand whilst on work experience, the radio was so bad I could hardly hear him! It could also pave the way for new passenger iBus screens to be implemented too. Looking at what SILENCED said re LVF and other apps, I’m sure TFL will release the new API to LVF and other apps that use the current countdown system, and these apps could be evolved even more with new technology in place, for example showing the real-time position of every bus in London. The ibus system does have a line diagram as you mention and real time map. This shows all the streets like Google Maps or an A to Z map. with the buses running along it.
|
|
|
Post by ServerKing on May 7, 2022 7:52:48 GMT
About time this happened! After spending time in the iBus room at C in particular, I have noticed that even in this modern era, the iBus computer system in particular runs on a Windows XP built programme which doesn’t look like it’s been substantially upgraded since iBus’s introduction in 2008 and only shows the line of route and stops, and buses come up as squares whereas modern day technologies could show iBus controllers a real time map view of where each bus is if used in conjunction with the telematics system on each vehicle. This could also help drivers radio’s to be more clearer, as when I was speaking to a 453 driver in the SW iBus hub last March to tell him to depart the stand whilst on work experience, the radio was so bad I could hardly hear him! It could also pave the way for new passenger iBus screens to be implemented too. Looking at what SILENCED said re LVF and other apps, I’m sure TFL will release the new API to LVF and other apps that use the current countdown system, and these apps could be evolved even more with new technology in place, for example showing the real-time position of every bus in London. The ibus system does have a line diagram as you mention and real time map. This shows all the streets like Google Maps or an A to Z map. with the buses running along it. traintimes.org.uk/map/london-buses/ have a detailed map showing each bus tracking from GPS position, showing reg number and ID or each bus on the route. The buses try to stay on the road, but it's not accurate to the nearest metre. Sometimes it's like a bus is in mid air cutting across a park rather than going along the road as the maps are rudimentary
|
|
|
Post by capitalomnibus on May 8, 2022 12:48:41 GMT
The ibus system does have a line diagram as you mention and real time map. This shows all the streets like Google Maps or an A to Z map. with the buses running along it. traintimes.org.uk/map/london-buses/ have a detailed map showing each bus tracking from GPS position, showing reg number and ID or each bus on the route. The buses try to stay on the road, but it's not accurate to the nearest metre. Sometimes it's like a bus is in mid air cutting across a park rather than going along the road as the maps are rudimentary You can see an example of it here www.youtube.com/watch?v=QbxmPBwAIkI at 0:52, it is very accurate.
|
|
|
Post by edvid on Feb 21, 2024 12:00:17 GMT
Procurement Authority for the iBus2 system was approved at the Programmes and Investment Committee meeting on 6 December 2023 ( associated document link). Once the contract award is made (P&IC papers published yesterday suggest this is imminent), it'll take about 2 years for iBus2 to be designed / created / tested / etc (the so-called transition period) and then another year to roll it out. It's very likely iBus will make it to 2027.
|
|
|
Post by edvid on Mar 5, 2024 12:09:19 GMT
|
|
|
Post by abellion on Apr 4, 2024 12:52:28 GMT
It would be nice if the iBus replacement would be more hardy with diversions.
Some stuff from the last 2 days: All the countdowns are showing 466 to Caterham when most buses are turning to Old Coulsdon,
no bus is running down Mitcham Road entirely yet the 57/127/333 sporadically appear on Countdown,
last night Penge High St was shut around Penge West Stn due to emergency works blocking the end of the road yet the 176/197/227 were also sporadically coming up on Countdown despite all diverting around Penge East.
In an ideal world buses would track easily on diversion. For a local example being able to see that a 280 or 355 is going to Streatham and have stop announcements instead of the screen going blank and the bus vanishing from tracking for a while, especially as a ton of people are using the diverted buses to go to Streatham, Southcroft Road, Tooting Bec etc. whilst they’re diverting around there.
Whether or not that is possible, I have no idea!
|
|
|
Post by S.152 on Apr 4, 2024 12:54:23 GMT
It would be nice if the iBus replacement would be more hardy with diversions. Some stuff from the last 2 days: All the countdowns are showing 466 to Caterham when most buses are turning to Old Coulsdon, no bus is running down Mitcham Road entirely yet the 57/127/333 sporadically appear on Countdown, last night Penge High St was shut around Penge West Stn due to emergency works blocking the end of the road yet the 176/197/227 were also sporadically coming up on Countdown despite all diverting around Penge East. In an ideal world buses would track easily on diversion. For a local example being able to see that a 280 or 355 is going to Streatham and have stop announcements instead of the screen going blank and the bus vanishing from tracking for a while, especially as a ton of people are using the diverted buses to go to Streatham, Southcroft Road, Tooting Bec etc. whilst they’re diverting around there. Whether or not that is possible, I have no idea! It's possible with the current system but involves manual data upload which is only uploaded weekly or bi-weekly IIRC, so they don't bother unless it's a relatively long-term diversion like the 60 via Norbury for almost a year due to the gas explosion
|
|
|
Post by M1104 on Apr 4, 2024 13:25:23 GMT
It would be nice if the iBus replacement would be more hardy with diversions. Some stuff from the last 2 days: All the countdowns are showing 466 to Caterham when most buses are turning to Old Coulsdon, no bus is running down Mitcham Road entirely yet the 57/127/333 sporadically appear on Countdown, last night Penge High St was shut around Penge West Stn due to emergency works blocking the end of the road yet the 176/197/227 were also sporadically coming up on Countdown despite all diverting around Penge East. In an ideal world buses would track easily on diversion. For a local example being able to see that a 280 or 355 is going to Streatham and have stop announcements instead of the screen going blank and the bus vanishing from tracking for a while, especially as a ton of people are using the diverted buses to go to Streatham, Southcroft Road, Tooting Bec etc. whilst they’re diverting around there. Whether or not that is possible, I have no idea! In the case of the Mitcham Road senario it's presently just a matter of informing TfL for them to then update the display, although that's something they should've done from the word go. Going slightly off topic I am surprised that with ibus due an overhaul London's buses still have the same type ticket machines from the 1990s.
|
|
|
Post by vjaska on Apr 4, 2024 14:14:25 GMT
It would be nice if the iBus replacement would be more hardy with diversions. Some stuff from the last 2 days: All the countdowns are showing 466 to Caterham when most buses are turning to Old Coulsdon, no bus is running down Mitcham Road entirely yet the 57/127/333 sporadically appear on Countdown, last night Penge High St was shut around Penge West Stn due to emergency works blocking the end of the road yet the 176/197/227 were also sporadically coming up on Countdown despite all diverting around Penge East. In an ideal world buses would track easily on diversion. For a local example being able to see that a 280 or 355 is going to Streatham and have stop announcements instead of the screen going blank and the bus vanishing from tracking for a while, especially as a ton of people are using the diverted buses to go to Streatham, Southcroft Road, Tooting Bec etc. whilst they’re diverting around there. Whether or not that is possible, I have no idea! The Countdown system needs an entire overhaul - it's essentially akin to the original one at the customer end to the one I remember from the early 90's bar the text being orange rather than red and being able to display all routes at a bus stop and not just one or two specific ones. I know it's been mentioned in reports but it seriously needs expanding too - really a screen should of been included when a brand new shelter has been installed previously and any stop that previously had one most definitely should of got one when their shelter was replaced (looking at you southbound Brixton Water Lane stop)
|
|
|
Post by edvid on Apr 4, 2024 18:41:43 GMT
Going slightly off topic I am surprised that with ibus due an overhaul London's buses still have the same type ticket machines from the 1990s. TfL have contracted Cubic to develop and install next-gen card readers (Project Hina). On the buses they'll be connected to iBus2 but remain separate from the old Electronic Ticket Machines, which are set for removal (by whoever wins the Proteus Contract) during the iBus2 rollout. Do drivers still use the old ETMs for anything besides manually logging paper Travelcard usage these days?
|
|
|
Post by capitalomnibus on Apr 5, 2024 21:42:53 GMT
Going slightly off topic I am surprised that with ibus due an overhaul London's buses still have the same type ticket machines from the 1990s. TfL have contracted Cubic to develop and install next-gen card readers (Project Hina). On the buses they'll be connected to iBus2 but remain separate from the old Electronic Ticket Machines, which are set for removal (by whoever wins the Proteus Contract) during the iBus2 rollout. Do drivers still use the old ETMs for anything besides manually logging paper Travelcard usage these days? Used to record driving hours, passenger data for stops etc.
|
|
|
Post by Eastlondoner62 on Apr 5, 2024 22:09:57 GMT
Going slightly off topic I am surprised that with ibus due an overhaul London's buses still have the same type ticket machines from the 1990s. TfL have contracted Cubic to develop and install next-gen card readers (Project Hina). On the buses they'll be connected to iBus2 but remain separate from the old Electronic Ticket Machines, which are set for removal (by whoever wins the Proteus Contract) during the iBus2 rollout. Do drivers still use the old ETMs for anything besides manually logging paper Travelcard usage these days? With the new next generation readers really should be an option to either use a live QR code as a Travelcard or for the option of Oyster to be added to Google/Apple Wallet. It should be possible at least on Google Pay for Oyster to be added in a 'pass' format where it'll be read as an Oyster card instead of as a Contactless Card and is already the case for many tickets and store cards. Something else that should be done is paper tickets NFC enabled. This would crack down on fraud as all tickets would need to be tapped on readers regardless. Or at the very least all paper tickets printed with a scannable QR code.
|
|
|
Post by edvid on Apr 7, 2024 17:45:34 GMT
TfL have contracted Cubic to develop and install next-gen card readers (Project Hina). On the buses they'll be connected to iBus2 but remain separate from the old Electronic Ticket Machines, which are set for removal (by whoever wins the Proteus Contract) during the iBus2 rollout. Do drivers still use the old ETMs for anything besides manually logging paper Travelcard usage these days? With the new next generation readers really should be an option to either use a live QR code as a Travelcard or for the option of Oyster to be added to Google/Apple Wallet. It should be possible at least on Google Pay for Oyster to be added in a 'pass' format where it'll be read as an Oyster card instead of as a Contactless Card and is already the case for many tickets and store cards. Something else that should be done is paper tickets NFC enabled. This would crack down on fraud as all tickets would need to be tapped on readers regardless. Or at the very least all paper tickets printed with a scannable QR code. Some interesting suggestions there. Next-gen Oyster accounts will be stored in the back-office instead of the cards themselves, so that would be a good time to enable the associated tokens in digital wallets. I think TfL would favour that initiative the most and could market it as a fee-free alternative to the physical version. They'll probably continue to promote contactless above all, though. Travelcard barcodes* are very unlikely. You would need readers at every station in Zones 1-9 and TfL only wish to install them at LU/National Rail interchanges, primarily to assist point-to-point NR journeys through Z1. Even that has been set back years by an ongoing dispute with the Rail Delivery Group over the specifics, though portable scanners may be introduced at those interchanges as an interim option ("interim" likely meaning the remainder of the existing Revenue Collection Contract, at least). As for paper NFC Travelcards, I'll split that into inboundary (zones only) and outboundary (includes extension trip from outside the zones): Inboundary - I think it would be simple to produce one-day Travelcards in this format when legacy magstripe tickets are eventually phased out,** at least if one-day Bus and Tram Passes are already issued as such (are they?). Still unlikely though, given TfL's Oyster/contactless preference. Outboundary - Not happening. Post-magstripe,** Travelcards may be limited to ITSO smartcards. Expansion of the London-centric contactless area may eventually lead to withdrawal of the one-day issue (for different reasons to last year's aborted withdrawal). [* NR tickets use Aztec codes, which the general public mistakenly class as QR codes. This confusion is understandable as the latter are far more prolific in everyday use, including bus tickets outside London; they're even visible on many NR gateline barcode readers! Some people involved in ticketing management, like the TfL staff responsible for compiling the FoI-requestable Ticketing and Revenue Updates, also make this mistake.] [** I believe TfL and the RDG want rid of them, so paper singles on TfL services will eventually go. Non-magstripe paper tickets (point-to-point, not Travelcards) with Aztec codes are already being trialled outside London.]
|
|
|
Post by Eastlondoner62 on Apr 7, 2024 17:59:16 GMT
With the new next generation readers really should be an option to either use a live QR code as a Travelcard or for the option of Oyster to be added to Google/Apple Wallet. It should be possible at least on Google Pay for Oyster to be added in a 'pass' format where it'll be read as an Oyster card instead of as a Contactless Card and is already the case for many tickets and store cards. Something else that should be done is paper tickets NFC enabled. This would crack down on fraud as all tickets would need to be tapped on readers regardless. Or at the very least all paper tickets printed with a scannable QR code. Some interesting suggestions there. Next-gen Oyster accounts will be stored in the back-office instead of the cards themselves, so that would be a good time to enable the associated tokens in digital wallets. I think TfL would favour that initiative the most and could market it as a fee-free alternative to the physical version. They'll probably continue to promote contactless above all, though. Travelcard barcodes* are very unlikely. You would need readers at every station in Zones 1-9 and TfL only wish to install them at LU/National Rail interchanges, primarily to assist point-to-point NR journeys through Z1. Even that has been set back years by an ongoing dispute with the Rail Delivery Group over the specifics, though portable scanners may be introduced at those interchanges as an interim option ("interim" likely meaning the remainder of the existing Revenue Collection Contract, at least). As for paper NFC Travelcards, I'll split that into inboundary (zones only) and outboundary (includes extension trip from outside the zones): Inboundary - I think it would be simple to produce one-day Travelcards in this format when legacy magstripe tickets are eventually phased out,** at least if one-day Bus and Tram Passes are already issued as such (are they?). Still unlikely though, given TfL's Oyster/contactless preference. Outboundary - Not happening. Post-magstripe,** Travelcards may be limited to ITSO smartcards. Expansion of the London-centric contactless area may eventually lead to withdrawal of the one-day issue (for different reasons to last year's aborted withdrawal). [* NR tickets use Aztec codes, which the general public mistakenly class as QR codes. This confusion is understandable as the latter are far more prolific in everyday use, including bus tickets outside London; they're even visible on many NR gateline barcode readers! Some people involved in ticketing management, like the TfL staff responsible for compiling the FoI-requestable Ticketing and Revenue Updates, also make this mistake.] [** I believe TfL and the RDG want rid of them, so paper singles on TfL services will eventually go. Non-magstripe paper tickets (point-to-point, not Travelcards) with Aztec codes are already being trialled outside London.] Thank you for the insightful response. It does answer my query as to why digital wallet versions of Oyster do not exist if the data is stored on the card itself and not in the back end of the system. Contactless is certainly the easiest option as people can pay on both their devices and on their physical bank cards with the additional benefit of TfL not needing to maintain any of their own infrastructure. The only other suggestion I might have is the ability to link a travelcard to your card number, so you can use your contactless card but should you already have a travelcard it will not charge you and will validate your travel against the travelcard that's associated with the card. The only reason I suggest this is because I and probably many people who still buy monthly travelcards still need to lug around an Oyster card as the weekly caps work ut to be more than a monthly travelcard, and weekly caps go out of the window completely if you creep out of a zone for a day as you lose your cap, but on an Oyster you'll only be charged the difference for the sole journey out of the zones. Many wishes, probably not many will become reality.
|
|