The document outlines the implementation of eduroam Wi-Fi on 11 buses across 4 routes, requested by students for enhanced connectivity. It discusses requirements, timelines, and cultural considerations involved in the project's execution, emphasizing its success and high data usage. Additionally, it highlights the importance of seamless Wi-Fi access for passengers traveling between university campuses.

1. eduroam on
the buses
Darren Wheatcroft

2. • Requirements
• Timeline
• Implementation
• Success!
• Next Steps
Agenda

3. • Hopper buses contract renewal
• Wifi everywhere
• Generally thought to be a “good
thing”
• Student requested feature
• Asked for IS involvement early!

4. The requirements ..
• 11 buses
• 4 routes
• An app
• Real-time GPS updates
• Wifi (eduroam)
The requirements

5. Understanding our Culture (10 minutes)
• Divide into groups of 5/6:
• Individually, think of a word that you think best describes our
current culture in IS, write your word on a post-it
• In your group, discuss the different words and why they were
chosen
• Pick the top 3 words that you collectively think describes our current
culture and explore the following questions:
• Is this culture consistent across IS teams and locations?
• Is this the culture that you want to have in IS?
• Does this culture support employee engagement and the
achievement of IS objectives/goals?
Each group to feedback for 1 minute summarising their discussions
• All service vehicles shall be equipped with wi-fi for the use of passengers
• The University primary SSID is eduroam, and it is preferred that this SSID is
broadcast to passengers to enable seamless connectivity for travel between
campuses. eduroam is a federated, authenticated (802.1X) network for many
academic institutions worldwide, supported through JISC. Further information can
be found in Appendix X, or https://www.jisc.ac.uk/eduroam. It provides encrypted
secure access to the internet for our users, without the need to maintain multiple
sets of credentials
• Wifi usage data and geographical (GPS) data shall be made available to the
University for use in mobile apps and dashboards
The requirements

6. Timeline
First discussions with
Estates
Dec. 2017
Draft tender questions
Jan. 2018
Publication of tender
Mar. 2018
End of Tender process
Apr. 2018
Begin discussions with
Arriva / Icomera
June 2018
Daily RFU from IS
management
Aug. 2018
SoS!
Sep. 2018

7. Implementation issues
• Initial placeholder SSID ‘eduroam’
• Problems!
• Quite a few interested parties
• Arriva, UoN Estates, UoN IS management,
Icomera
• Funnel everything through Arriva PM
• Testing & Go-live
• Engine off, wifi off…
• Start of Session!

8. Success
Success!!!
• Go live for Start of Session
• Data use higher than anticipated
• Popular service with users

9. Route data
Wi-Fi Usage
Number of scheduled journeys Total Route patronage Total Unique Patronage Total Authentications Unique Users Data Usage
Aug-18 635 26,467
Sep-18 800 56,091
Oct-18 3925 184,793 29,803 304,402 31,467 1,381GB
Nov-18 4029 116,900 17,758 417,344 35,063 1,766GB
Dec-18 1790 54,456 10,130 181628 29,301 784GB
Jan-19 2447 61,183 174,970 28,648 780GB

10. Thank you