Video Walls and Operational Visualisation

A control room wall is not a bigger monitor. It is a shared picture that has to stay up while the room keeps working.

Which changes what matters about it. Not size, not resolution in isolation, but how many sources it carries at once, who can put something on it in an incident without help, and what it does at 03:00 when a processing path fails and nobody in the room is an AV engineer.

Christie and Samsung both build the display and processing systems behind continuously monitored walls. SECCOM specifies against whichever platform a room already runs.

Arrange SECCOM to review the real source count, resolution and refresh rate a wall has to carry before any processor is selected, at no cost. Sources are always more numerous and less standard than the brief says.

What you get. A source-to-window map, a stated switchover behaviour with its time in seconds, brightness and pixel pitch calculated from the nearest and furthest operating position, and a spares holding stated in modules and power supplies.

Failure behaviour is stated. Primary path faults, switchover holds the output automatically within the stated time. Manual fallback drives a named source direct to a display group with the processor bypassed. Time to service is contracted, and the room runs at a defined reduced capability until then.

Where SECCOM stops. Lobby, experience-centre and broadcast walls are specified under SECCOM's AV & Collaboration practice. This capability covers walls people work from.