Network Unification is UCLA’s effort to modernize and unify campus networking to make it more reliable, more secure, and easier to operate. It includes foundational network infrastructure upgrades and a phased approach to building migrations.

The current network is aging and increasingly at risk. Reliability issues and security gaps create real operational pressure today. NU is a critical campus priority because modern, secure, and reliable networking is foundational for teaching, research, patient care, and everyday operations.

Impact depends on the building/location and the type of network equipment being replaced or installed. In pilot and Wave 1, the focus is on DTS-managed network services (MNS) equipment and stakeholders. Department-managed equipment is addressed in subsequent waves. Information about when buildings will be impacted will be communicated as planning progresses. Regardless of waves, every impacted location will receive communications leading up to the change and will be coordinated with units.

Yes. Strengthening Wi-Fi is a core priority of Network Unification. The program is focused on improving wireless performance across campus, while prioritizing high-impact spaces, such as classrooms, common areas, and research spaces.

The campuswide survey confirmed inconsistent coverage, congestion in high-use areas, and interference from unmanaged access points. It also reinforced the need for a next-generation wireless design that supports higher device density and modern standards (Wi-Fi 6/7 capable).

As a result, NU is prioritizing a stronger wireless foundation as a central feature of the modernized network, to be implemented through a phased rollout.

Funding is in place to complete the core infrastructure build that will serve as the foundation for the campus and the pilot. In parallel, the campus budget approval process continues for the broader program. Completing the pilot helps validate the technical approach and informs the plan and sequencing for the wider rollout.

We are preparing for multiple budget outcomes (full or partial funding) and building contingency plans accordingly. Full campus-wide unification depends on securing program funding; however, regardless of the final outcome, DTS will continue to prioritize reliability and risk reduction, especially for instructional spaces, research, and health and safety systems.

If campus decisions require changes to scope, timing, or sequencing, we will communicate those updates once confirmed. The program team will share what is changing, why, and what it means for units, using the NU update channels.

Please reach out if urgent network needs surface in your area. We understand the urgency and that outages and failures can happen without warning. DTS Network Services will respond with options based on current resources, expertise, and the situation. For issues that can be addressed with available capacity and existing inventory, we will act quickly. 

The preferred path is to move units through the planned Network Unification wave approach whenever possible. This ensures the highest quality and reduces rework. However, in truly urgent cases, we can evaluate earlier interim support options, including, in some circumstances, transitioning a unit into the MNS service model ahead of its planned wave. 

If your unit has a critical need, contact Ju Kim to discuss it further.

The core infrastructure build includes the build and test of the future state core network infrastructure to enable pilot and wave migrations. Completion of the core infrastructure build is required before the pilot phase begins.

The core infrastructure build includes critical networking components such as:

• Firewall, security, and network segmentation
• Services network, including DDI, ClearPass, NDFC
• Core network and backbone upgrades
• Campus network, including wired and wireless components, to enable building migrations
• Network access control
• Legacy integration

The goal of the pilot is to test and validate components of the new network design and migrate select devices to the new network. The scope includes select buildings, telecommunication rooms (TRs), and DTS Managed Network Services (MNS) devices. This phase includes readiness activities, pre‑migration meetings, migrations, and lessons learned.

Unit-facing preparation (e.g., discovery/coordination, readiness validation) for DTS MNS customers will begin in March 2026. Actual pilot migration activities are targeted for May 2026. In other words, March is the preparation period; May is when pilot migrations begin.

Waves are phased groups of buildings/units that transition to the new network over time. There will be three waves: wave 1 focuses on DTS-managed customers and locations, and waves 2-3 include department-managed units and locations. 

Network Unification will modernize wired and wireless infrastructure by building and units using a phased migration approach. The current approach is to begin with DTS Managed Network Services (MNS) and early adopters in Wave 1, with department-managed networks addressed in Waves 2–3, which will be identified up front. Units will be able to communicate key blackout dates or constraints as planning becomes more detailed.

Because the budgeting process may require adjustments to sequencing and resourcing, this wave approach should be understood as the current plan and may be refined as budget decisions are finalized.

Units will receive targeted communications ahead of any activity that affects their building or services, including readiness steps, expected timing, and points of contact. We will aim for “no surprises” and clear expectations as migrations approach.

Any activity that may affect a service will be communicated in advance, including the expected timing and instructions. The intent is to minimize disruption and provide clear guidance on what to do before, during, and after a change window.

The future-state operating and funding model will define how the modernized network is run and paid for day to day, including who is responsible for which services, how decisions are made, how support is provided, and how costs are allocated and sustained over time. The detailed model is still being designed in partnership with project leadership and technical teams, and we will share specifics, gather feedback from key stakeholder groups, and communicate any changes well in advance of relevant migrations so departments understand what to expect and can plan accordingly.

You can email the project team at connectandsecure@it.ucla.edu with your questions, and our team will respond as soon as they can.

Our intent is to provide quarterly program updates moving forward, supplemented by interim status updates through established channels and the NU web presence as it develops.

We will share recap materials after live updates (when applicable) and post key information in this web space, including updated FAQs and links to additional resources as they become available.