Networks designed for general data have very different priorities than those required for real‑time AV. Data networks can buffer and retry packets without users noticing; audiovisual traffic cannot. Every additional millisecond of latency is experienced as lip‑sync drift, conversational lag, or cursor delay during shared content.

The traffic shape is different as well. Data traffic tends to be bursty and asymmetrical, while AV traffic is sustained, predictable, and often symmetrical, especially in bi‑directional collaboration scenarios. Packet loss that might be acceptable when downloading a file becomes visible and audible as dropouts and artifacts when transporting audio and video streams. Finally, switching characteristics matter: standard office switches are chosen for low cost per port, whereas AV switches must offer sufficient non‑blocking throughput, deeper buffers, and robust multicast handling to keep streams stable under load.

When organizations retrofit real‑time media onto an office network designed purely for data, the outcome is familiar: stuttering video, intermittent audio, and reliability that degrades as utilization rises.

Modern AV networks succeed when architecture is intentional. Segregating AV traffic using dedicated VLANs prevents cross‑traffic congestion, improves security posture, and makes troubleshooting straightforward. Core infrastructure should be built on managed switches—unmanaged gear cannot prioritize real‑time flows or provide visibility. Features like IGMP snooping for multicast, quality of service for traffic prioritization, and port mirroring for diagnostics are table stakes.

Bandwidth planning matters enormously. A single 4K video stream can consume 50–100 Mbps; multiply by the number of simultaneous streams, add audio, control, and overhead, and the math quickly demands 10 Gbps or faster uplinks. Switching fabrics must be non‑blocking at full capacity, not just on paper. Redundancy is equally critical: single points of failure in the network create single points of failure for the entire AV system.

Protocol choices shape design. Dante demands precise clocking (via PTP), low latency, and thoughtful multicast domains; it thrives on dedicated networks or rigorously segmented VLANs. NDI can consume hundreds of megabits per HD stream, so switching backplanes and uplinks must be sized accordingly. AES67 and SMPTE 2110 bring broadcast‑grade timing requirements that may depend on GPS‑disciplined or highly accurate PTP grandmasters. Control protocols are comparatively light but are latency‑sensitive; keep them reliable and segregated from noisy traffic. Selecting protocols up front informs switch features, VLAN topology, and timing sources.

Design for the next decade, not just the next deployment. Assume higher resolutions, higher frame rates, and denser rooms; choose cabling, optics, and switch fabrics that won't need early replacement. Software‑defined capabilities make it possible to reconfigure flows and apply policies remotely, shrinking operational overhead. Invest in documentation as a first‑class artifact—diagrams, VLAN maps, addressing, and baseline configs shorten outages and accelerate change. Favor modular topologies so capacity can be added without surgery. Keep firmware and security posture current; an AV network is still a network and must be maintained as such.