The call about the AV lifecycle comes in year six or year seven. A core switch dies or a DSP that went end of life years earlier finally quits, and a system that has run reliably since commissioning becomes a six-figure emergency by lunch. The customer is frustrated, the facilities director is exposed and the replacement has to come out of a budget built with no room for it.
Everyone in the room treats it as bad luck. Nobody can name the day a specific device will fail and customers translate that uncertainty into a belief that the replacement itself is uncertain, so it never gets a line in the AV budget. That is the mistake. The failure date may be uncertain, but the replacement always was.
Buildings Already Fund What Wears Out
Commercial buildings already know how to fund assets that wear out. Roofs, chillers and elevators all carry known service lives and their owners fund replacement over time instead of absorbing it as a shock. AV is one of the few durable systems in a building that routinely escape this discipline. Part of the reason is habit.
For decades, AV was purchased like furniture — a one-time capital event expected to last until someone decided otherwise. Part of the reason is the AV industry itself.
Accrual language is missing from our proposals and replacement planning is almost never a contracted deliverable, so the subject stays out of scope.
Last year, my team retired a digital mixing console that still powered on and still passed audio on every channel. Nothing about it had failed. However, the manufacturer had ended support, spare parts had dried up and the risk of keeping it in a critical room had grown past the cost of replacing it.
End of life belongs in the buying decision from day one — priced and dated — and not discovered later.
Annualize the AV Lifecycle from Day One
In an exchange that started on LinkedIn, Seth Garrepy (an IT infrastructure architect I have known since graduate school) pushed that argument further.
IT already runs on replacement cadences. The planning ranges vary by organization, but servers typically turn over at four to five years, endpoints at three to four, network switches at seven to 10, wireless access points around five.
Then, he added the mechanism that AV has been missing: Annualize the replacement cost from the day the system goes live, so the money exists when the date arrives.
Call it a reserve or a sinking fund if your accountant prefers the term. Essentially, the arithmetic is short: A $500,000 system on a seven-year cycle is roughly $70,000 a year. Fund that annually and nobody has to find $500,000 in year seven.
Three Clocks, One Date
AV integrators are ideally situated to help customers establish the replacement date. Assigning the service life is judgment and the judgment has structure. Three clocks run on every device in the rack: physical life, supportable life and economic life. The date belongs to whichever clock runs out first.
The physical clock is the one everyone watches and it almost never sets the date. The console we retired proved it. Duty cycle is where physical life genuinely matters. A laser light engine rated at 20,000 hours runs out in under three years of around-the-clock signage duty and may outlast the room itself in a boardroom used two hours a day.
The supportable clock usually rings first. Manufacturer lifecycle policy is the place to start, since end-of-sale and end-of-support announcements are published for most major product lines. End of support should be treated as the planning deadline for anything sitting on a network or depending on security patches.
Platform dependency runs on the same clock. A perfectly healthy UC appliance dies the day its conferencing platform drops certification. Wireless microphone owners who lived through the 600 MHz repack know the regulator can set the date too.
The economic clock is the quiet one. Sometimes nothing external moves at all; the device simply becomes more expensive to keep than to replace, counted in maintenance, spares and risk.
The service life of any device is the earliest of those dates, not the friendliest.
Costing Traps in the AV Lifecycle
Costing has its own traps. Price the replacement at today’s cost for the full project, not the original hardware invoice. The boxes are only part of the cost. Labor, programming, commissioning, freight, project management and engineering do not disappear because the racks already exist, and the replacement budget needs to account for the whole project, not just the new equipment.
Reprice the schedule once a year instead of guessing at escalation. The annual repricing review is a simple task and it keeps the budget realistic instead of resting on inflation guesswork.
And do not price a single full restack at a set date. Endpoints, network hardware and core processing do not share a service life, so a well-built schedule replaces the system in waves rather than all at once which flattens the accrual line and keeps any single year survivable.
The View from the Owner’s Chair
I learned how hard this conversation is from the owner’s chair, years before I moved to the integration side.
As director of technical operations at a performing arts center near Boston, I inherited a building full of production equipment and a budget with no replacement money for anything we owned. Building the first version of that plan became one of my projects.
The work itself was straightforward: an inventory with install dates, service lives and replacement costs at today’s prices. The board discussion, however, was not.
Nobody wants to approve a line item for equipment that is working fine and every dollar assigned to a future replacement is a dollar unavailable for programs the audience can see. The argument that finally landed was that if we wanted to maintain an operational facility, the money was leaving either way.
The only question was whether we picked the year or a failure picked it for us. Once the reserve existed, replacements stopped being argued as emergencies and started being scheduled.
Two Paths to the Same Conversation
Customers arrive at the AV lifecycle funding by two paths. Most arrive after a failure, when something critical dies and the replacement competes with every unplanned expense in the building. A few arrive at the end of a large capital project, when the system is new, the numbers are fresh and the conversation costs nothing.
Moving customers from the first path to the second is work integrators are positioned to do better than anyone else. We know the service lives and the replacement costs and we were there when the system was commissioned.
The Case for Integrators
There is a commercial case here and it does not require a planning contract. An account manager who helps a customer build a replacement schedule is shaping that customer’s budget years in advance, at exactly the moment no competitor is present. The customer who has been funding a reserve since commissioning is the customer who can approve the refresh without a capital fight.
Large accounts may still bid the work and the integrator who helped build the plan has spent years demonstrating value before the replacement ever goes to market.
The profitability case is quieter but real. Planned replacements get engineered, staged and scheduled on normal labor. Emergency replacements get expedited freight, overtime and a customer whose patience ran out before the purchase order was signed.
New tools are not required and neither is new contract language. What it takes is an integrator willing to raise the subject while the system is still new and a customer willing to write down a year. Ask what the replacement year is, ask what the system costs today and divide.
The integrator who runs that arithmetic with the customer has already won the year-seven conversation, and they’ve won it years before a competitor knows it is on the calendar.
David Shriver, CTS-I, CTS-D, is division manager of the Houston division at Ford Audio-Video Systems.
