IT‑IS‑Networking
Technology › Audiovisual & Broadcast

Audiovisual Architecture

What happens to an audiovisual estate when video becomes network traffic — rooms stop being closed systems, and a purchase becomes a network design question.

Also known as AV over IP, AVoIP, Broadcast Systems, Encoders and Decoders, Room Control

Left to right is time. Each row is one of the 10 disciplines this one worked alongside, ordered so kindred disciplines sit next to each other rather than alphabetically — a landscape only means anything if neighboring rows belong together. Height is the work running in that domain in that year, weighted by what failure would have cost — life-safety ×3, a statutory obligation ×2.2, the estate itself ×1.5, an evaluation ×1. Every project declares which of those it was, so each ridge traces to an entry you can open and disagree with. Only the work that used this technology is counted, so what shows here is the company it kept rather than the record around it. Height and color are on the record-wide scale rather than this page’s own, so a modest estate draws a modest landscape and any two of these pages can be read against each other.

For most of its history an audiovisual installation was a closed system: sources, a matrix switch, displays, a control panel, and a room that neither knew nor cared what was outside it. Every room was its own project and every project ended at the door.

Moving to networked encoders and decoders changes the category. Once video is network traffic, rooms can feed each other — a council chamber can reach an emergency operations center, a backup facility can carry a session — and the estate becomes one fabric rather than a set of installations. That is the gain, and it brings three consequences that belong to architecture rather than to audiovisual.

The network becomes a dependency with real requirements. Uncompressed or lightly compressed video across a switch fabric is not a traffic profile a general-purpose access switch was sized for. The platform stops running on whatever is in the closet, which turns an audiovisual purchase into a network design question — usually discovered by an integrator, late, on a site that has already been specified.

A standard only holds where a procurement can see it. On a publicly bid job the solicitation is the last place anyone can put a requirement. A switch model named in a reference architecture is a suggestion a vendor is free to value-engineer; the same model named in the bid document is a requirement they have to price. Getting the standard into the solicitation is the whole of the governance work, and it has to happen before the document goes out.

One hardware model across many sites is a common-mode failure. The moment the same encoder carries five buildings, a supply problem anywhere is an availability problem everywhere, and sparing stops being a line item and becomes the resilience position. That is an unfashionable thing to argue for in a capital request and the only time it gets noticed is after it was not done.

And underneath all of it, the older obligation does not go away: in a room where proceedings are a public record, the recording and the broadcast are the record, so availability is statutory rather than a courtesy.