Why Apply Replacement Asset Value (RAV) in Capital Planning
- JD Solomon
- Aug 3
- 4 min read
Replacement Asset Value (RAV) is one of the most widely used numbers in maintenance and reliability. It’s also one of the most misunderstood when the conversation shifts to capital planning. The problem isn’t the math. The problem is that RAV was never designed to answer capital‑planning questions, yet we can count on it as a good starting number if we don’t have anything else.
If we want better capital decisions, we need to frame RAV correctly from the start.
From the Real World
“So we have added thirty percent of our assets over the past 10 years,” quipped the chairman of the board. “The other sixty percent was added over 30 years, and O&M costs are rising. Do we have any idea about what impact the most recent slug of assets will have?”
The General Manager started a response, then stopped. “We have no idea,” he plainly stated.
A quiet pause and a pointed look from the chair.
“Our bid tabs and engineering estimates are old and have a lot of indirect costs,” the GM continued. “However, we do have a good list of what we have been paying for the equipment directly in the procurement and maintenance departments. My gut is that we will build from there, and cross-check with our engineering and other financial records.”
The chair responded something like “get on it” and moved to the next item. The next day we got on it, with the best information we had available.
RAV Was Born in Maintenance, Not Capital Planning
RAV originated as a maintenance benchmarking metric, not a capital or operations budgeting tool. Leaders like Ramesh Gulati use it to compare maintenance spending across facilities and industries. The intent is simple: provide a consistent denominator for metrics like maintenance cost as a percentage of RAV.
RAV = Equipment cost + removal/disposal + installation
RAV covers the basics – the cost of the equipment plus the labor to put the new one back on the ‘bolts’. Not included are:
Engineering
Permitting
Project management
Procurement
Owner’s overhead
Controls redesign
Capital contingency
The things that are not included belong to a capital replacement estimate.
This distinction matters. When capital planners treat RAV as a fully burdened replacement cost, the conversation goes sideways.
Why RAV Gets Misused in Capital Planning
The misuse usually comes from one of three places.
1. The Word “Replacement” Tricks People
Capital planners hear “replacement” and naturally think of a full capital project. Operation and maintenance leaders hear “replacement” and think of swapping out equipment. Same word, different worlds.
2. RAV Is Convenient (Maybe Too Convenient)
RAV is easy to calculate. Capital replacement estimates are not. When time is short, people grab the number that’s available, not the number that’s appropriate.
3. RAV Looks Like a Planning Number
It’s big, round, and asset‑specific. It feels like a capital number. But feeling like a capital number doesn’t make it one.
RAV asks, “What would it cost to replace the asset in its operating context?”
What Capital Planners Actually Need
Capital planning requires a fully burdened replacement cost, which includes:
Engineering and design
Permitting and environmental reviews
Procurement and bidding
Construction management
Owner’s overhead
Integration and controls
Commissioning and testing
Contingency
Conversions to CIP Projects - General
Remember, RAV is normally two times equipment cost. Disposal of the existing asset and installation of the new one on the existing footprint are the labor components of RAV, and that labor typically runs about the same as the equipment cost itself – which is why RAV commonly lands around 2× equipment cost.
1. On‑Call Contractor Replacement
Minimal Engineering, Minimal Permitting
Typical multiplier: [1.2 to 2.0] × RAV
2. Limited‑Design Replacement
Task‑Order Engineering, Moderate Permitting
Typical multiplier: [2.0 to 3.5] × RAV
3. Full Design‑Bid‑Build Capital Project
Heavy Engineering, Full Permitting, Formal Procurement
Typical multiplier: [3.5 to 6.0] × RAV
4. Major Capital Program or System‑Level Replacement
Multiple Assets, Complex Integration, Major Site Re-Design
Typical multiplier: [6.0 to 10.0] × RAV
Two Frequently Asked Questions
Two questions come up constantly once teams start building these estimates.
Can We Use Insurance Replacement Values?
Yes, selectively because there are similar concerns as we have with RAV.
Insurance replacement values reflect what it would cost to rebuild an asset as it exists today, which often includes like‑for‑like materials, code upgrades, and contingency assumptions that inflate the number. There are nuances to insurance replacement values, and there’s always a question about the rigor used to develop them.
Capital project estimates must be based on future scope, design, and market conditions, so using just the insurance values leads to systematic overestimation and misalignment with actual project requirements.
Can We Use AI to Produce the Estimated Values?
Yes, but with major limitations. You need to be able to tell AI exactly what you want. And recognize that AI may fill in values if it has none.
Currently, AI is most helpful to complete raw equipment cost values and can be used in RAV. AI is best used to fill the gaps.
RAV Is a Foundational Number
RAV is a powerful metric—when used for the purpose it was designed for. It provides consistency, clarity, and a common language for maintenance and reliability. We call on RAV in capital planning because it’s the most consistent number that most organizations have.
Capital planners need fully burdened replacement estimates. Maintenance leaders need consistent RAV calculations. When organizations frame these concepts correctly, they reduce confusion and improve outcomes.
JD Solomon writes and consults on decision-making, reliability, risk, and communication for leaders and technical professionals. His work connects technical disciplines with human understanding to help people make better decisions and build stronger systems. Learn more at www.jdsolomonsolutions.com and www.communicatingwithfinesse.com.
Comments