How to plan the working life of an experience

Opening day is followed by ordinary days: staff start the system, content is updated, a connection fails or a component needs attention. The design should make those events understandable to the people who operate the venue.

Begin by following the staff workflow. Identify what they need to start, stop, inspect and recover; which tasks they can complete themselves; and when specialist help is required. That exercise reveals useful requirements for controls, documentation and access.

Mad provided AV systems for the original Blue Planet Theater at Gwinnett Environmental and Heritage Center in Buford, Georgia.

Gwinnett later brought Mad back to renew the AV hardware. The theater also gained a new film, with the renewed experience opening in March 2024 following the original 2006 project. The theater’s story continued through a new phase of media and system work.

That history gives an owner a useful planning question: how will a future team understand the installation well enough to renew it? The answer involves the records, access and relationships that continue after the first handover.

A symptom at an exhibit may have several causes. Missing audio could involve content, routing, control, a network connection, an amplifier or a loudspeaker. Useful diagnostic information helps narrow the investigation before equipment is changed.

Define what can be observed remotely and what requires a person in the room. A software status report, a captured image and an acoustic measurement each establish different things. Access, monitoring coverage and response arrangements belong in the agreed support scope.

Standard computer architecture can provide practical options when compute or storage needs replacement. The next available component still has to meet the software, interface and performance requirements of the installed system.

Review the condition and compatibility of displays, projectors, loudspeakers and other peripherals before deciding what to retain. If the goal is to add AV++ capabilities to a legacy installation, first establish the required QuickSilver playback and control foundation. The additions then have their own content, interfaces and engineering scope.

Keep configuration backups, diagrams, software versions and content records aligned with the working installation. Record why a change was made, what was tested and any effect on operation or recovery.

When considering a newer capability, identify whether it is an established function, a working demonstration or further development. A refresh plan can include new possibilities while keeping the present operating requirements and acceptance criteria explicit.