iBus (London)

From Infogalactic: the planetary knowledge core
Jump to: navigation, search
File:London iBus display.JPG
An iBus display on a London bus, announcing that the vehicle is stopping at Liverpool Street Station.

The iBus is an Automatic Vehicle Location (AVL)[1] system to improve London's buses using technology installed by Siemens AG.[2] The system tracks all of London's 8000 buses to provide passengers with audio visual announcements,[1] improved information on bus arrivals,[3] and to trigger priority at traffic junctions.[4][5]

On 16 June 2005 it was reported that London's buses 'fail' deaf people.[6] As a result, the iBus system was announced on 16 January 2006 and was tried on route 149[7] for an eight-week trial. The system was proved to be successful, and on 18 May 2006, radio presenter Emma Hignett was announced to be the 'Voice of London's Buses' after 99% in the survey said she had the right voice.[8] iBus was launched on many routes in 2007 and continued throughout 2008 and 2009. All routes now have the system.[9]

Announcements

Upon boarding the bus, for example, route 240 serving Edgware, iBus plays the announcement "240 to Edgware" and corresponding text appears on the visual displays. As the bus approaches the stop, the on-board system will announce and display the bus stop name.[3] Since March 2014, the space below this name shows the current time. When a passenger has requested the bus to stop, this is replaced by the message "Bus stopping".

Similarly to the London Underground, iBus has a feature that tells passengers to alight at a key stop, which is near a key place that the bus will not serve. For example, a bus arriving at Stratford will say, "Stratford: alight here for Stratford station," and this will scroll across the dot matrix indicators.

Each bus contains a Microsoft Windows-based computer[10] that has the details of all 19,000 bus stops in London.[10] The system has over 30,000 announcements for 700 bus routes.

The bus driver is able to play recorded announcements such as:

  • Bus will wait here whilst drivers are changed.
  • This bus terminates here. Please take all your belongings with you.
  • This bus is on diversion. Please listen for further announcements.
  • The destination of this bus has changed. Please listen for further announcements.
  • The next bus stop is closed.
  • Watch out for traffic when leaving the bus.
  • Seats are available on the upper deck.
  • Please move down inside the bus.
  • No standing on the upper deck or stairs please.
  • Smoking is not permitted on London’s buses.
  • Drinking alcohol is not permitted on London’s buses.
  • The wheelchair space is now required. Can passengers in this area please make room. Thank you.
  • Closed circuit television is in operation on this bus.
  • Please keep all your personal belongings with you at all times.
  • For everyone’s security, please inform the driver of anything suspicious.[11]

Tracking

The iBus system aims to provide a better fix on bus locations than the old Selective Vehicle Detection (SVD) system.[4] iBus can locate every bus to an accuracy of about ten metres, or its distance from the nearest stop by around ten seconds.[10] It does this using several instruments:

The essential part of the system relies on GPS satellite data that roughly determine the location of a bus down to 100 metres.[2] Data collected from GPS is passed into a Kalman filter,[12] and other data including velocity[12] and temperature[12] is calculated on the bus and transmitted every 30 seconds via GPRS.[2] With the bus network map, this helps the Central System to make a "best guess" of the bus position and depicts the overall image derived from the data provided by all buses,[2] even in areas with poor GPS reception. The Central System[12] can update the countdown signs as before[12] that now has a more accurate prediction derived from all this data. Knowing the location of the bus, controllers have the means to regulate the service more efficiently,[3] and priority can be given to a bus at traffic lights.[4][5][12]

CentreComm, the 24/7 Emergency Command and Control Centre, is able to track the location of every bus in the fleet and can be shared this information immediately with the emergency services in the event of an emergency or accident.[13]

Other applications

Although iBus was rolled out in 2008, it was not until 2011 that the data was made available to other applications, such as text messaging and the Internet.

With text messaging, bus users can send a text with the bus stop code to receive realtime bus arrival times for that stop. Visually impaired passengers will be able to use the text-to-speech facility on their mobile phones to get the information too. However, users will have the pay the standard network rate for sending the text, plus an additional 12p charge to receive the response.[14]

On the Internet, the latest service information is available using mobile web or the Internet.[14]

Countdown signs are signs at bus stops giving users information about when the next bus is due. With iBus, Countdown is able to provide real-time information at 2,500 key bus stops in London. Communications improvements have also meant that Countdown can now display service updates, disruption information and network-wide messages. The roll out of the new signs at key locations was completed in June 2012. iBus was integrated with Countdown by Telent. And the signs were supplied, installed and maintenance by ACIS and Trueform.[14] IVU.realtime from IVU Traffic Technologies AG, Germany, forms the central system of Countdown II.[15]

Cost

The cost of fitting iBus to buses and garages up to 3 January 2009 was £18.8m[16] which was part of a Transport for London (TfL) £117m upgrade to the bus fleet communications system.[17][18]

Complaints

The number of complaints received from bus companies or TfL employees relating to the use of the iBus between 23 January 2008 and 11 February 2009 was 254.[16] Most of these complaints were due to faults in iBus, with the majority stating there were no display data or no announcements being made. However, there were also complaints associated to incorrect display data and announcements, thus giving bus users incorrect information of when to get off if they were relying on iBus.[19]

See also

References

  1. ↑ 1.0 1.1 Lua error in package.lua at line 80: module 'strict' not found.
  2. ↑ 2.0 2.1 2.2 2.3 Lua error in package.lua at line 80: module 'strict' not found.
  3. ↑ 3.0 3.1 3.2 3.3 Lua error in package.lua at line 80: module 'strict' not found.
  4. ↑ 4.0 4.1 4.2 4.3 4.4 http://www.tfl.gov.uk/assets/downloads/businessandpartners/svd-brochure-2006.pdf
  5. ↑ 5.0 5.1 http://www.tfl.gov.uk/assets/downloads/TfL-bus-signals-priority.pdf
  6. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  7. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  8. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  9. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  10. ↑ 10.0 10.1 10.2 10.3 10.4 Lua error in package.lua at line 80: module 'strict' not found.
  11. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  12. ↑ 12.0 12.1 12.2 12.3 12.4 12.5 12.6 http://www.nlondon.bcs.org/pres/mdjun06.pps
  13. ↑ http://www.tfl.gov.uk/corporate/projectsandschemes/technologyandequipment/7203.aspx
  14. ↑ 14.0 14.1 14.2 http://www.tfl.gov.uk/corporate/projectsandschemes/11560.aspx
  15. ↑ http://www.aachener-zeitung.de/news/wirtschaft/mit-aachener-technik-durch-londons-city-1.611496
  16. ↑ 16.0 16.1 http://www.whatdotheyknow.com/request/ibus_technology
  17. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  18. ↑ Lua error in package.lua at line 80: module 'strict' not found.
  19. ↑ http://www.whatdotheyknow.com/request/6056/response/21252/attach/html/3/ST%2081289%20Urquhart%20complaints%20in%20full.xls.html

External links

Retrieved from "https://infogalactic.com/w/index.php?title=IBus_(London)&oldid=5356323"