|
|
Post by snoggle on Jun 27, 2018 16:30:37 GMT
Looks like work is now underway to start the replacement of I-Bus and associated contract performance measurement and payment systems. The bus radio and schedules systems are also being renewed but each project is at different stages. As already reported the new radio system is on trial at TB.
From the TfL Q4 Investment Report
|
|
|
|
Post by SILENCED on Jun 27, 2018 17:36:22 GMT
Looks like work is now underway to start the replacement of I-Bus and associated contract performance measurement and payment systems. The bus radio and schedules systems are also being renewed but each project is at different stages. As already reported the new radio system is on trial at TB. From the TfL Q4 Investment Report Half expecting LVF and the apps to stop working once it has been upgraded! |
|
|
|
Post by snoggle on Jun 27, 2018 18:42:17 GMT
Looks like work is now underway to start the replacement of I-Bus and associated contract performance measurement and payment systems. The bus radio and schedules systems are also being renewed but each project is at different stages. As already reported the new radio system is on trial at TB. From the TfL Q4 Investment Report Half expecting LVF and the apps to stop working once it has been upgraded! To be fair we are a number of years away from that. I actually doubt TfL would be that crass. It knows how valuable its external data feeds are. I would expect it to give plenty of advance warning to users of the data feeds of any changes to the data structures or frequency of creation. I would also expect a lot of the standing data to remain the same (stop IDs, operator codes). However I could foresee TfL moving to a less rigid structure of vehicle IDs and that could create issues for LVF where data is mapped to other data behind the scenes. |
|
|
|
Post by YY13VKP on Jun 27, 2018 18:49:30 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. |
|
|
|
Post by snoggle on Jun 27, 2018 20:17:08 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. What is going to be interesting is how TfL cope with the vast amounts of hardware. The current system is a bespoke system which the supplier has refused to license to TfL to allow TfL to get other suppliers on board. Therefore TfL has to effectively dismantle the existing system and replace it with separate elements which are not bespoke to any supplier and use as much "open" technology as possible. How on earth TfL are going to do this is anyone's guess as the current supplier probably has the ability, if it wanted to, to "switch off" the driver terminals - I'm assuming they own them but I might be wrong about that. Even if TfL own them there will come a time when they are no longer supported and TfL will need to replace them. Similar issues apply to the on vehicle screens. As TfL have effectively re-engineered the old EMTs umpteen times but don't really need an ETM it's very unlikely they would move to industry standard ETMs that incorporate GPS and tracking functionality. Therefore TfL will probably be tied to the current system structure for a fair while as it will be too expensive to dump large elements of the on vehicle kit. Back room systems are a different thing altogether and will no doubt be on bog standard kit but perhaps with the software development done in house (as it was for a lot of recent Oyster and Contactless stuff). We shall see what TfL opt to do. |
|
|
|
Post by ServerKing on Jun 29, 2018 17:04:57 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. What is going to be interesting is how TfL cope with the vast amounts of hardware. The current system is a bespoke system which the supplier has refused to license to TfL to allow TfL to get other suppliers on board. Therefore TfL has to effectively dismantle the existing system and replace it with separate elements which are not bespoke to any supplier and use as much "open" technology as possible. How on earth TfL are going to do this is anyone's guess as the current supplier probably has the ability, if it wanted to, to "switch off" the driver terminals - I'm assuming they own them but I might be wrong about that. Even if TfL own them there will come a time when they are no longer supported and TfL will need to replace them. Similar issues apply to the on vehicle screens. As TfL have effectively re-engineered the old EMTs umpteen times but don't really need an ETM it's very unlikely they would move to industry standard ETMs that incorporate GPS and tracking functionality. Therefore TfL will probably be tied to the current system structure for a fair while as it will be too expensive to dump large elements of the on vehicle kit. Back room systems are a different thing altogether and will no doubt be on bog standard kit but perhaps with the software development done in house (as it was for a lot of recent Oyster and Contactless stuff). We shall see what TfL opt to do. They will sub out the work to the likes of Daisy Group or SCC for the Server stuff. These type of IT contracts always overrun and spend crazy amounts of cash as well  |
|
|
|
Post by capitalomnibus on Nov 29, 2018 23:04:59 GMT
Most of the south was upgraded today with some of the north. The rest of London would be upgraded to digital tomorrow 30/11/18 at 2am. Only 2$ of buses would then remain analog until February next year.
|
|
|
|
Post by snoggle on Nov 29, 2018 23:11:18 GMT
Most of the south was upgraded today with some of the north. The rest of London would be upgraded to digital tomorrow 30/11/18 at 2am. Only 2$ of buses would then remain analog until February next year. Is the radio system you're referring to? If so that's a very fast installation programme - only taken a few months. |
|
|
|
Post by Pilot on Nov 29, 2018 23:36:01 GMT
So what's gonna be the difference?
|
|
|
|
Post by capitalomnibus on Dec 2, 2018 23:01:53 GMT
Most of the south was upgraded today with some of the north. The rest of London would be upgraded to digital tomorrow 30/11/18 at 2am. Only 2$ of buses would then remain analog until February next year. Is the radio system you're referring to? If so that's a very fast installation programme - only taken a few months. Not so fast, considering it was a change of some wires, changing the radio unit, (not the MDT in the drivers cab) and testing it out. Takes around 10-20 mins to do. The 2% of buses that were not done, would have been away for repaint, bodywork, mechanical repairs etc.
|
|
|
|
Post by capitalomnibus on Dec 2, 2018 23:02:45 GMT
So what's gonna be the difference? Clearer radio system, less breakdowns, end to overloading of calls etc. |
|
|
|
Post by Pilot on Dec 3, 2018 22:28:49 GMT
So I got to hear it and I think I like this more, seems like the message is consistent at being clear but controllers sound like they got a sponge in their mouths.
|
|
|
|
Post by grubbysa on Dec 3, 2018 22:44:32 GMT
So what's gonna be the difference? Clearer radio system, less breakdowns, end to overloading of calls etc. So far I've found this new system to be very problematic, drivers can hear iBus but controllers can't hear the drivers, thankfully the landline is there to save us. Hopefully this is just us experiencing teething issues with the digital radios. |
|
|
|
Post by snowman on May 4, 2021 14:21:15 GMT
Seems the tender for I-bus 2 is now issued at an estimated cost of £395,000,000 Divided into 3 parts : 2 suppliers of On board equipment each approx 4500 vehicles for 21.5 years estimated at £105,000,000 each Back office services estimated value £185,000,000 bidstats.uk/tenders/2021/W15/748945859 |
|
|
|
Post by snowman on May 5, 2022 6:10:28 GMT
Seems that I-bus 2 is delayed Instead the existing contract for I-bus which was due to expire this month, has been extended until at least May 2025, with options to extend to May 2027. Which suggests the replacement will not be rolled out for at least 3 years www.ukauthority.com/articles/london-bus-services-extend-ibus-deal-with-trapeze-its/The first contract for iBus was awarded to Siemens in 2005, then novated to Trapeze in 2009. In 2015 it was extended for seven years to 2022. It has now been extended again. It suggests I-bus might reach its 20th birthday |
|
