Maurice van den Akker SURFnet Mobile & Wireless Team Lead Wi-Fi-as-an-NREN-Service providing end-to-end connectivity from the start

WaaS (Wifi-as-an-NREN-Service) agenda Drivers for WaaS: Users, Technology and Outsourcing Business Model of WaaS for NRENs Key features of SURFnet’s WaaS and support structure Setup and lessons learned SURFnet’s WaaS pilot SURFnet’s WaaS Tender and future plans

Drivers for WaaS: Users demand HQ Wi-Fi By 2018, more than half of all users will use a tablet or smartphone first -- instead of a laptop or desktop -- for all online activities. By 2018, 40 percent of enterprises will specify Wi-Fi as the default connection for nonmobile devices, such as desktops, desk phones, projectors, conference room. Source: Gartner Title: "Predicts 2015: Mobile and Wireless." url: Growing expectations quality of Wi-Fi

Drivers for WaaS: outsourcing strategy N=75 Growing dependency of Wi-Fi & BYOD Excellent Wi-Fi is not an intitute’s core business Outsourcing by cooperation: opportunity for NREN Survey (2014): Are you interested in a managed Wi-Fi-service of SURFnet already in next 2 years?

Drivers for WaaS: technology More scalable Wi-Fi environments Centralized management Controller layer: central, distributed, virtual, Controlling AP’s Backbone network must accommodate high demand of Wi-Fi (1 Gbit/s now, 10 Gbit/s coming up) Integration with 3G/4G/5G/DAS/etc Evolving in free (white space) high-band spectrum  Opportunities for innovation! Source: Redusers.com

Cost savings through efficiency and scalability Shared Central Management Shared Wi-Fi expert personnel Shared Support Structure Demand Aggregation & Shared European Tender Procedure Shared IP-pool (optional) Use existing Assets (NREN- network, LAN, Radius, etc) Applying local policies (security, SSIDs) Access to Local Resources (Local breakout or Centralized Switching)

WaaS: a matter of strategy Does the NREN believe investments in wireless are nescessary forICT innovation? Yes Is the NREN willing and capable to deliver shared services (or: manage) upon the campus? Yes Does the NREN want to be wireless innovator? Yes Ambition 4 Shared Wireless Innovation Center No Ambition 3 Shared Wireless Service Center No Ambition 2 Temporary supporter (some procurement) No Does the NREN temporary wants to be involved in wireless? No Ambition 1 Minimalistic (eduroam only) Yes

Minimum requirements for SURFnet 1. State-of-the-Art Wi-Fi-network (and affordable ;-) 2. Scalable, efficient, while maintaining local policies 3. Keep It Simple (Support) This implies: Excellent Wi-Fi network: coverage and capacity (speed, latency) Innovative: new features, standards available quickly Reliable, Stable Excellent monitoring & radio management eduroam, ac, r, IPv6 HD coverage at crowded areas Real-time: Voice, Video, Location Based Services Roaming Great first line support at the institutes High flexibility for (small) changes Mature security and privacy Guest access System (eduroam Visitor Access)

SURFnet’s WaaS delivery model Vendor WOC Wireless Operating Center NREN Institutes Equipment 24x7 Management WaaS Innovation Partner

Business Case is not very complex Hardware costs Maintenance fees Hardware costs Maintenance fees Procurement fee Management fee Price Model: One amount per AP per month One-time for large changes, new site, etc One-time investment by SURFnet: lease or buy: Large Impact on turnover/ Balance sheet Price Model: One amount per AP per month One-time for large changes, new site, etc One-time investment by SURFnet: lease or buy: Large Impact on turnover/ Balance sheet Innovation Subsidy (optional)

… but the delivery chain & demarcation points are! Searchquotes.com

SURFnet WaaS delivery chain choices (in progress) SURFnet: New customer intakes, (Major) Change Management, Product Management, Accountable for Problem management, SURFnet backbone, WaaS procurement (every 4-6 years) WOC: Operations, Day-to-day monitoring and support, Site Survey, Radio Planning, delivery hardware, 2nd line support Institute: Local LAN, Mount AP’s, 1st line support (ICT support desk)

Keep it Simple (Support)

How does WaaS work in practice? Pilot Setup (2014/2015) Goals: Technical Proof of Concept Experience with Processes (RASCI) Replacement(old equipment) Greenfield (new office) Merge (Use of existing AP’s)

Outcome of PoC Fills in the need of the institutes Architectural constraints: Combination of Multiple Domains, Local Break Out, maximum number of AP’s and IPv6 Unclear responsiblitily for (group of) client-related problems (bug iMac, Android): Cause determining Demarcation of responsibilities is not clear enough Lack of documentation Different requirements for Accepting Communicate, communicate, communicate!

From PoC to Service  Preparing procurement since January 2014  Involved 2 mid-size launching customers  Mandatory green field deployment  Possibility for institutes to deploy WaaS gradually (per building)  Tender started Q4 2014: Competitive Dialogue Procedure: 5 parties + vendors selected

Planning for SURF WaaS operational 2015 Q3: Bidding Phase: Assessing Proposal and Rewarding, contracting Q4: Pilots with one location of each launching customer 2016 WaaS Operational Service for all customers Growth Roadmapping of service Start procuring for “Waa2”: …