When a venue opens, the AV system works. The question that was never properly asked is: will it still work in year five? In year ten? And if it needs to change - because the exhibit changes, the technology evolves, or the audience grows - how much will that cost?
Supportability is the capacity to maintain, repair, update, and evolve a system over time without replacing it entirely. It is not a feature that can be added after commissioning. It is a consequence of how the infrastructure was designed.
The decisions that determine supportability
Supportability is determined before a contractor is hired. The decisions that matter are made during architectural design:
- Proprietary vs. non-proprietary hardware: Proprietary hardware is serviceable only by the manufacturer or authorized partners. When the manufacturer changes its service model, exits the market, or discontinues the product line, the venue has no options. Non-proprietary hardware can be serviced by any competent IT team.
- Fixed-function vs. compute node endpoints: Fixed-function hardware does one thing and cannot be updated to do something different. Compute nodes are software-defined - their function can change without hardware replacement.
- Conduit sizing: Undersized conduit cannot be retroactively expanded without opening walls. Conduit sized for the final system at the design stage costs almost nothing more; undersized conduit discovered at integration costs a multiple of the original AV contract to remediate.
- Network topology: A network designed for signal transport only cannot support AI data flows without redesign. A network designed as AV++® infrastructure can support both from day one.
- Serviceability access: Compute nodes and network infrastructure that cannot be accessed without specialty tools, lifts, or structural intervention will not be serviced on the schedule that keeps them reliable.
What unsupportable venues look like in practice
A venue with unsupportable AV infrastructure typically presents as one or more of the following in years three to seven after opening:
- Critical components are no longer manufactured and cannot be replaced with equivalent parts
- Software updates that would fix known problems require hardware replacement that was not budgeted
- Service calls take longer and cost more than anticipated because access is difficult and parts are scarce
- The exhibit wants to change, but the AV system cannot accommodate the change without a capital replacement project
- AI personalization becomes desirable, but the network and compute infrastructure cannot support it
None of these failures are surprises. They are the predictable result of decisions made - or not made - during architectural design.
AV++® and the supportability specification
AV++® is Mad Systems' patented infrastructure specification designed explicitly for 15–20+ year supportability. Its key design choices:
- Non-proprietary compute nodes - standard IT hardware, serviceable by any qualified team, no vendor dependency
- Software-defined endpoints - function determined by software, not hardware, enabling capability upgrades without hardware replacement
- IT-aligned infrastructure - standard networking, power, and environmental requirements that IT teams already know how to manage
- Remote management - nodes can be diagnosed, updated, and reconfigured without physical access to the venue
AV++® is not a product that can be added to an existing installation. It is an infrastructure specification that must be designed into the construction documents - conduit sized for its nodes, power circuits allocated for its load, network backbone designed for its traffic. This is why architectural engagement at the design stage is not optional if AV++® is the goal.
Supportability and the total cost of ownership
Venues that evaluate AV systems on first cost consistently underperform venues that evaluate on total cost of ownership over a 15–20 year lifecycle. The delta between a properly designed long-lifecycle system and a first-cost-optimized system is typically negative - the long-lifecycle system costs less over its operational life, because remediation, emergency service, and premature replacement are far more expensive than correct design.
Mad Systems does not pitch on first cost. It works with owners and operators who understand that the infrastructure decisions made before construction begin have more leverage on total cost of ownership than any procurement decision made afterward.
The cost of making the right infrastructure decision during design is approximately zero - it is the difference between specifying one conduit diameter and another, one network topology and another. The cost of remediating a wrong infrastructure decision after construction is typically 10–100× the original decision cost. Supportability is not expensive to design in. It is expensive to retrofit.
Building a System That Needs to Last?
Supportability is designed in, not added later. Mad Systems specifies non-proprietary components, documents everything, and remains available for the life of the system - because we invented the technology inside it.