Campus Communications & Networking

Transcription

1 Campus Communications & Networking Committee on IT Infrastructure April 13, 2016

2 Unified Communications: Objectives Define UCLA s future communications needs Develop a roadmap for future communications infrastructure investment Develop of plan for replacement of the legacy campus telephone system 2

3 Unified Communications: Progress Phase 1: Requirements (complete) Interviewed stakeholders to understand the needs of their constituencies Identified how communications are used by different groups to support research, education, public service and campus administration Released requirements document in Spring 2014 Phase 2: Architecture (complete) Conducted vendor briefings / product reviews Analyzed requirements from campus Mapped campus needs to vendor solutions Evaluated potential paths forward Phase 3: Implementation (in progress) Multiple projects 3

4 Unified Communications: Findings Vendor options and packaging are more similar than not Cloud offerings are not yet mature enough to pursue The capabilities that the campus has asked for via the requirements process can be largely, if not completely, met using frameworks that are already deployed on campus One size will not fit all 4

5 Unified Communications: Strategy Focus on leveraging existing platforms Migrate campus voice connectivity from telephony (TDM) to internet protocol (IP) Create a communications clearinghouse to document campus use cases, recommended solution sets, etc. 5

6 Unified Communications: Projects Upgrade Unified Communications Manager (Winter 2016) Pilot softphones (Spring 2016) Implement IP based trunking in lab environment (Spring 2016) Retire Key Service Units (target completion: FY17/18) Retire Remote Switching Centers Wilshire Center during FY16/17 6

7 Campus Wireless Network Completed wireless coverage of all General Assignment Classrooms (GAC) over the summer of 2015 Working to expand wireless coverage to all of campus over next two years Deployment prioritization coordinated through Campus Wireless Advisory Group 7

8 Campus Network Strategy

9 Campus Network: Problem Statement The UCLA Campus Network (as a whole) cannot deliver a consistent and predictable baseline of performance, security, and reliability to the community The delivery of network based services is both more complex and more complicated than would otherwise be expected, resulting in higher costs to deliver network based applications and services This is largely the result of the highly distributed networking environment that has been established As a campus, we must change our approach 9

10 Campus Network: Current State 38 campus backbone connectors 38 independent operations with unique philosophies and practices 38+ different sets of policies, processes, and procedures High variation in infrastructure capabilities High variation in application/service performance High variation in user experience UCLA connected infrastructure investment has been left to decay 10

11 Campus Network: Goal Implement a unified campus network architecture and operations model that provides: high performance connectivity, high reliability, and increased security with a single, converged network infrastructure design 11

12 Campus Network: Partnerships Engineering VI Institute for Digital Research and Education (OIT / IDRE) Social Sciences Computing Anderson School, Digital Humanities, Graduate School of Education and Information Studies School of Medicine 12

13 Campus Network: Partnerships Campus Partnerships Engineering VI Institute for Digital Research and Education (IDRE) Social Sciences Computing Anderson, Digital Humanities, Education & Information Studies School of Medicine Managed Network Services California NanoSystems Institute (CNSI) Campus Human Resources (CHR) Campus Service Enterprises (CSE) Central Ticket Office (CTO) Corporate Financial Services (CFS) Dashew Center for International Students & Scholars (OISS) Events & Transportation Facilities Management Housing & Hospitality Services (H&HS) International Studies & Overseas Programs Joint Institute for Regional Earth System Science & Engineering Office of Research Administration (ORA) Office of Administrative Vice Chancellor School of Law UCLA Faculty Center UCLA Library UCLA Police Department (UCPD) World Policy Analysis Center at Public Health 13

14 Campus Network: Where We Should Be Create a single, unified network architecture for the campus End the practice of independent local networks in departments Unify network operations to provide a consistent and predictable baseline of performance, security, and reliability to the community Fund the complete network as a common good 14

15 Campus Network: Intermediate Goals Unified access layer across campus Common service baseline Consistent expectations for performance and capabilities Establish a regular refresh cycle for network equipment Establish ongoing maintenance of physical infrastructure 15

16 Campus Network: Planning Quantify scope of campus network Request sent to primary contact for all backbone connectors (Sept 2015) Vetted through Common Systems Group (CSG) Limited response with significant gaps Determine extent of necessary infrastructure improvements WTC performed assessment of all networking closets in 2009 IT Services has re engaged WTC to refresh the assessment data (target completion: May 2016) Survey telecommunications building rooms for suitability, cooling, electrical power, rack space, station cabling, fire stopping, etc. Inventory as built equipment deployment 16

17 Campus Network: Proposal Campus provided Campus Backbone Network (under TIF funding) no change Campus provided local area network under TIF funding, including connections to the Science DMZ four year ramp up with $5 $6 increase in monthly TIF rate at end (planning assumption; needs validation) Department and campus co manage the network under a shared services model Departments can opt to contract with IT Services for Managed Network Services (fee based service) 17