How Network-as-a-Service eases IT burdens for widely dispersed federal branch offices

A vast majority — over 80% — of the federal workforce operates far from the Beltway, delivering essential government services from thousands of branch and field offices nationwide. Yet, ensuring these dispersed locations have modern, secure, and reliable network connectivity is a growing challenge, often hampered by a critical lack of on-site IT expertise.

Network-as-a-Service (NaaS) is emerging as a compelling solution for agencies struggling with this resource gap, offering access to advanced technology and skilled management without the need for extensive in-house staff, according to government and industry executives speaking on a recent video panel.

The National Oceanic and Atmospheric Administration (NOAA), part of the Department of Commerce, exemplifies the complexities agencies face with diverse, far-flung operations. Adam Nemethy, deputy director in NOAA’s Office of the CIO, described the various sites NOAA supports, ranging from typical multi-story office buildings to weather forecast centers, research ships, and even temporary setups for meteorologists deployed to incidents like wildfires.

“It’s really the lack of access to the same (IT) resources,” Nemethy explained. “Sometimes you have a single person in these offices, and they’re doing all the functions. They’re not IT people, and so they’re developing solutions to things with their limited knowledge.” This reliance on non-specialists can hinder performance and prevent smaller sites from leveraging the complete expertise within the agency or available externally.

The core issue, Nemethy noted, often boils down to getting specialized IT help. Providing NaaS internally within parts of NOAA and Commerce has shown the value of connecting users directly with engineers. “Almost all of it boils down to access to network professionals that can solve their needs” and understanding users’ daily tasks.

Scott Andersen, distinguished solution architect at Verizon, elaborated on what NaaS looks like in practice for these field offices. It involves assessing site needs to determine the right mix of connectivity — potentially including wireless-only setups, broadband, traditional circuits, and SD-WAN capabilities, all managed through a single point.

He noted that the viability of options like wireless-only has dramatically increased. “If I said to you, oh, I’m going to make some of your sites wireless-only as recently as 10 years ago… after the pitchforks were sharpened… they’d be chasing me,” Andersen quipped. “But now it becomes a very much more viable conversation.”

Beyond basic connectivity, agencies also must consider security and efficient use of network resources. Andersen highlighted the potential for cost savings in multi-tenant federal buildings where a provider like Verizon might already have a presence. Consolidating multiple agencies’ needs into a single, larger connection can be more efficient than managing numerous smaller ones. He also stressed the importance of adequate bandwidth, especially with the rise of video collaboration. “…When you force people to be on video and they can’t because of bandwidth, you start to cause other problems within the entity for how people operate,” Andersen warned.

Justin Fields, leader of cross-architecture solutions at Cisco, added that there are operational and economic advantages to consider when weighing investing in network infrastructure versus relying on NaaS. A primary benefit is the shift from unpredictable capital expenditures (CAPEX) for equipment purchases to consistent operational expenses (OPEX).

“Consistency is key,” Fields asserted. “So not only can I have a consistent operating expense OPEX… I also get… consistent visibility if the outages were to happen, I don’t have to worry about… overtime or anything along those lines.”

This consistency extends beyond costs. “From a resource perspective, patching maintenance — all those costs that it takes to run an infrastructure — are all included in that network as a service model, if you choose correctly,” Fields explained. This frees up limited agency staff from routine upkeep and complex troubleshooting.

When considering NaaS, agencies need to evaluate factors beyond the technology itself. Fields emphasized the critical role of identity management — ensuring the right people have the right level of access — and the overall user experience. “Obviously, I think security is of the utmost importance. But I think above that… agencies should consider the customer experience, right? Do we have adequate bandwidth?” he asked. Balancing robust security with seamless user access is crucial for productivity and satisfaction.

Looking ahead, the executives see the continued evolution of technology playing a factor in network investment decisions. Andersen pointed to the integration of satellite services promising “always available connectivity,” while Fields predicted that “security is going to become more integrated… within the network… to create that seamless experience,” coupled with enhanced visibility across the infrastructure.

For agencies like NOAA grappling with supporting a distributed workforce that often lacks local IT support, NaaS presents a strategic alternative. By outsourcing network management, operations, and security to experienced providers, federal entities can ensure their field offices have the reliable, modern infrastructure needed to fulfill their missions effectively, regardless of location or the availability of in-house technicians.

Learn more from Verizon and Cisco about how Network-as-a-Service can simplify agency branch office operations.

This video panel discussion was produced by Scoop News Group for FedScoop and underwritten by Verizon and Cisco.