Data Networks

• Increasingly Mobile Users
• Expectations that connectivity just works and it works everywhere on campus
• Number of devices and bandwidth needs continue to increase
• New technology from cellular 5G, to Wi-Fi 6, to new regulations and standards means almost everything wireless is changing in next 2 years. High level of uncertainty.
• Demand for guest Wi-Fi services, including requests for venue specific networks (e.g. Burke)
  

Current

• Expand Outdoor Wi-Fi
• Increase Wi-Fi density
• Improve cellular
  
  • HMC Distributed antenna system
  • Wi-Fi Tech Refresh
  • Passpoint trial

Planned (within 12 mo)

• Update campus strategy for wireless services support and technology mix
• Optimize Wi-Fi for mobile voice
  • evaluate private-LTE as technology option
• Provide campus-wide guest Wi-Fi services

Future (1-3 years)

• Improve cellular - 
  • Sprint on campus? - waiting for T-Mobile/Sprint merger decision

• Connectivity everywhere
• Experience is similar across multiple access methods
• User experience for devices is close to how it works at home
• Proper mix of wired and wireless technologies to support our missions
• Standard Wi-Fi offering permits guest users easier access in different venue types

• Increase reliability
• Simplifying operations & architectures to adapt to increasing scale (users, devices, device types, new buildings, clinics)
  • routing to edge, reduce layers
  • automation
  • alignment of services with needs/use
    
    
• Wi-Fi is being used or Planned (within 12 mo for Increasingly critical functions, including some in UW Medicine.

Current

• Routing to the Edge Project (also down on row 6)
• Switch configuration automation
• Improve documentation process for circuits (DLR wiki pages, etc).
• Continue AOS 8 rollout and improve configuration standard practices
• Deploy Aruba Service Assurance (Cape Networks) sensors to evaluate and report client performance
  
• Deploy Wi-Fi staging environment to UW Medicine

Planned (within 12 mo)

• Networks.uw self-service improvements - set 12 mo -18 mo roadmap
• Improve documentation process for circuits (DLR wiki pages, etc).
• Create services VRF for critical UW-IT services (bypasses IPS)
• Evaluate wired service assurance capabilities
• Set standard MTU 1500 at edge
• Update UW Medicine Wi-Fi infrastructure to improve relability and allow for less disruptive changes.

Future (1-3 years)

• Redefine service catalog with standard bundles with automated ordering
• Self-reporting/healing of issues
• Evaluate next-gen network management platform

• Improved network reliability & availability
  • Reduce single points of failure
  • Automate routine provisioning
  • Hit target KPIs
• Make network infrastructure transparent to the consumer
• increase self-help, self-change options (via networks.uw.edu, etc)
• Repeatable service options for "special needs" projects
• Reliability & availability of networks are aligned with the needs and funding of the client for nonstandard services.
• Consolidate databases to help support staff more efficiently and effectively perform lookups.
• Impact from network service outages are further isolated.

Desire by customers and staff to simplify service ordering and changes

Current

• Improve network provisioning process
• Evaluate and lay road map for IPAM/DDI tool set
• Self-service firewall policy administration for Managed Firewall service
• Visibility into HON-D logs by department (aka Splunk)
  

Planned (within 12 mo)

• PRJ0016879 - Improve Incident Management Customer Communications Project (eOutage, Advisory, Service Status)

Future (1-3 years)

• Updated DHCP & DNS platforms with feature roadmap

• increase self-help, self-change options (via networks.uw.edu, etc)
• improve service delivery efficiency and consistency
• additional services such as DDNS - self-service where possible

• Budgets are decreasing while costs to deliver base services are increasing
• Funding models across the UW are changing

Current

• Evaluate and confirm existing expenditures
• Improve cost recovery models (T&M for special needs; wifi design, install and management; communication infrastructure designs;
• Improve CPD cost recovery model
  • • Visibility of UW-IT contributions, if any
• Routing to the Edge Project (also up on row 2)
• Develop service lifecycle calendar and cost planning
• Support Westin power modernization

Planned (within 12 mo)

• increase self-help, self-change options (via networks.uw.edu, etc)
• Sustaining funding models for needed activities/services
• Costs are transparent within all relevant UW communities
• Reduced financial risks:
  • reduce annual maintenance charges
  • evaluate designs, assumptions, and needs to ensure proper alignment
  • smooth out refresh/infrastructure upgrades into more predictable chunks
• planned cadence for deferred maintenance. Reduced future deferred maintenance.

Increase Privacy & Security

Current

• IPv6 border firewall
  
• Self-service firewall policy administration for Managed Firewall service
  
• UW-IT all to RFC 1918 space!
• Visibility into HON-D logs by department (aka Splunk>)

Planned (within 12 mo)

• Develop plan to aid in migrating campus edge networks to RFC 1918. Multi-year initiative
• Develop capability to expose more log information to departments
• Update network security plan
• Improve DDoS detection for campus
• microsegmentation
• Mac Authentication
• Analytics for security use
• IPv6 border firewall
• IPv6 for Husky OnNet

Future (1-3 years)

• Site to site IPsec VPN to Cloud Providers (AWS/Azure)
• Develop segmentation, firewall, and access service bundles
  
• Redefine service catalog with standard bundles with automated ordering
• Automate campus DDoS mitigation
• Husky OnNet Department for secure access to off-campus resources (AWS, Azure)
• Wifi inside department firewall

• Standard service options to ease ordering and management of security service bundles
• Provide necessary visibility to CISO to support their mission
• Self Help & Increase Privacy & Security controls for departments.
  • DNS/IP
  • IP addressing
  • Firewall rules; Power over Ethernet; subnetwork boundaries, and other service provisioning changes
• Departmental specific needs/services

• Aging platforms and planned vendor obsolescence (e.g. router & switch code, Aruba AOS 8, FortiGate, etc)
• UW "campus" continues to expand geographically while users expect a more campus-like experience
• Deferred maintenance (tunnel, platform upgrade, cabling, physical infrastructure, increasing needs)
  
  

Current

• Out of band network management evaluation
• Turn down dial-in modem service
• Define and monitor equipment lifecycles
• Update existing buildings from multi-mode to single-mode riser cables - multi-year
  
• Tunnel infrastructure cleanup - remove old cables, re-route vulnerable cables - multi-year
  
• Updated Aruba architecture to 8.x
  
  

Planned (within 12 mo)

• Evaluate wireless backhaul to augment fiber/MOE 
• Routing to building edge
• Minor Capital upgrades
• Tunnel infrastructure cleanup - remove old cables, re-route vulnerable cables

Future (1-3 years)

• Tunnel infrastructure cleanup - remove old cables, re-route vulnerable cables

• Align capital funding with physical plant and infrastructure needs
• Retire obsolete platforms and services
• UW-IT tunnel infrastructure is clear of old tech, properly supports existing needs and is well positioned for future needs.
• IT/Communications infrastructure is an intregal part of capital planning and funding processes

• Demands for bandwidth, power, and connectivity are increasing
• New standards to meet these demands are coming (802.11 ax, 802.11 ad, 802.3bz, 802.3 bt, etc)
• IPv6 demand is expected to continue to increase

Current

• Tech Refresh & evolution
  • Wired
  • Wi-Fi
• IPv6 standard border security protections
• Update wiring, switch and infrastructure standards and designs

Planned (within 12 mo)

• • Establish service roadmaps for key improvement, standards, and technology
  • Next generation Wi-Fi service architectures (AOS 8, 802.11 ax, 802.11 ad adoption, etc)

• Established service/business service roadmaps forecasting adoption (or non-adoption) of relevant/updated standards
• IPv6 is on course to have support on par with IPv4 across campus