Siân Morgan examines Campus NaaS offerings

Recent insights on Campus Network as a Service (NaaS) highlight the lack of standardized definitions across the industry, which could lead to confusion for IT decision-makers. Siân Morgan investigates various vendor offerings, clarifying features and characteristics relevant to enterprises.

Market Understanding

The current market for Campus Network as a Service (NaaS) is characterized by diverse interpretations and frameworks from vendors like Extreme and HPE. Morgan advises that establishing clear definitions can assist both enterprises and vendors in aligning expectations and experiences.

Characteristics of Campus NaaS

Campus NaaS differs from traditional cloud offerings by necessitating substantial on-site equipment. This requirement limits the ability to centralize resources compared to standard Infrastructure-as-a-Service (IaaS) or Software-as-a-Service (SaaS) models, as physical infrastructure must be installed within the enterprise premises.

Outcome Orientation

Certain Campus NaaS providers base pricing on anticipated results rather than the quantity of technology resources. Examples include Meter and Nile, which tie costs to factors like device count and user experience metrics, transferring complex network design responsibilities to the vendor.

Elasticity Features

Due to the physical constraints of Local Area Network (LAN) hardware, unlimited capacity is unfeasible. Some vendors propose flexible pricing structures based on branch size, allowing for optimized billing related to network demand, as seen in arrangements from HPE.

Operational Expenses Framework

Various Campus NaaS suppliers implement operational expense (opex) models where the vendor retains ownership of infrastructure, albeit at an increased service cost. This model typically includes fixed contract durations that address potential risks associated with early contract termination.

Maintenance Responsibilities

Maintenance presents a challenge with Campus NaaS due to extensive on-site hardware requirements. Vendors may collaborate with Managed Service Providers (MSPs) to offer lifecycle services or provide centralized monitoring themselves, balancing customer visibility with the cost of service.

Conclusion

IT leaders assessing Campus NaaS options are encouraged to prioritize the significance of various service characteristics and ensure clear service definitions from prospective vendors. Clear engagement on these aspects is essential for optimizing network performance and achieving desired outcomes.