Switch Vendors Start Selling AV Workflow Design

NETGEAR Enterprise announced on 23 October that it has extended its Professional Services programme beyond the network layer to cover AV-over-IP workflows, with NDI as the first ecosystem partner. The mechanics matter as much as the headline: the work is scoped and sold as project-based professional services through the same two-tier channel partners already use, it is separate from the vendor's premium support tiers, and it can be bought alongside switches that have carried protocol-specific profiles for years. Until now the services wrapped around those switches stopped at the network itself, covering design, deployment and optimisation of the infrastructure rather than what runs on top of it. The company says further ecosystem partners will be added, and that it remains protocol-neutral across the AV-over-IP technologies its switches support.

The reasoning offered by Massimo Mazzeo, the company's vice president of global systems engineering, customer support and services, is the sentence integrators should read twice: the programme started at the network layer and this partnership extends it to what runs on top of the network, so that expertise for the network and expertise for the production layer come from one place. That is a description of a failure mode as much as a product. AV-over-IP deployments rarely stay the size they were designed for: a handful of channels in a meeting room or a studio becomes dozens and then hundreds of endpoints across a campus, and at that point the fault is frequently neither in the workflow nor in the network but in how the two interact. A stream that stutters at nine in the morning can be a multicast group with no querier, a DSCP value the switch rewrites, a PTP domain that drifted after a firmware update, or a discovery boundary that a firewall closed. Charles Dobson of NDI framed the same shift from the protocol side, noting that the growth of NDI in professional AV has brought in customers who depend on their integrator to design the system rather than building it themselves.

What changes for the integrator is the scope letter. A workflow scope has to name the layer-two and layer-three design, where IGMP snooping and the querier live, the QoS and DSCP mapping per protocol, the PTP grandmaster and boundary clock plan, VLAN segmentation and the discovery traffic that has to cross it, flow counts and bandwidth budgets per endpoint class, the approved firmware matrix, configuration backups, and an acceptance test that produces packet captures rather than opinions. Single-vendor accountability is genuinely useful when a truck roll is at stake, but it does not remove the obligation to document the design, and a certified switch loaded with the wrong global profile behaves exactly like an uncertified one. Buyers should also ask what the service covers after handover: a design review is not a warranty, and the moment when a campus system needs help is usually two years after commissioning.

Amtune works at the point where a good network design either holds or fails: the endpoint. Our AV over IP decoders terminate streams at displays with fixed, documented behaviour, HDBaseT and HDMI extenders keep point-to-point runs out of the IP fabric where determinism matters more than reach, and multi-viewers give operations one surface to confirm what the network is actually delivering. We test interoperability before a truck rolls, not after. Design support at sales@amtune.com.