We’ve been talking about the integration of capital and maintenance planning for years. At conferences, in whitepapers, in client conversations. And the response is almost always the same: heads nod, people agree it makes sense, and then they go back to running their capital and maintenance programs the way they always have – in parallel, with separate data, separate teams, and separate goals.

Why is that? Because it’s hard. If it were easy, as Bill Roth has written, everyone would have figured it out by now.

But the reason it’s worth pursuing – even though it’s hard – is that the return on investment, when you find that sweet spot between capital and maintenance, is significant. And the organizations that get it right have a meaningful competitive advantage in how they manage, fund, and sustain their built environments.

The Missing Link

For decades, property and asset managers have been developing capital renewal strategies independent of their maintenance management strategies. Both efforts have matured considerably. Most larger organizations now have a reasonable understanding of their DCRM backlog, built on a foundation of Building Condition Assessments completed on a five-year cycle. Many also have functioning CMMS platforms managing their reactive and preventive maintenance workflows.

The gap is the connection between them.

Roth IAMS has identified four key roadblocks that keep capital and maintenance from being truly integrated:

First, the data granularity is different. Maintenance planning requires equipment-level data – individual rooftop units, specific chillers, individual pumps. Capital planning typically works at the element level – roofing systems, HVAC systems, mechanical systems overall. These two levels of detail don’t naturally talk to each other.

Second, the departments are often siloed. The teams responsible for capital renewal and the teams responsible for operations and maintenance frequently report through different organizational structures, use different language, and operate on different planning timelines.

Third, the tools are different. Maintenance is managed through a CMMS. Capital is often managed through spreadsheets, or at best a separate capital asset management system. These platforms rarely share data automatically.

Fourth, the rhythm of the two functions is fundamentally different. Maintenance is transactional – thousands of work orders generated every year. Capital is more of an annual or multi-year process with a much smaller number of decisions. Connecting a high-volume transactional system to a low-frequency strategic planning process requires deliberate design.

Why It’s Worth Overcoming

The benefits of integration are not abstract. They show up in concrete, operational ways.

True lifecycle costing – spending more capital initially to save maintenance dollars over the long lifespan of an asset – is only possible when you can see both sides of the equation. Most organizations can’t make that calculation because the capital cost and the maintenance cost are tracked in completely separate systems with no common language.

Reducing equipment failure and extending the lifespan of major building systems through a well-designed preventive maintenance program is only achievable when that program is informed by the condition of the assets it’s maintaining. An FCA gives you that condition data. But if the FCA data never reaches the maintenance team, it’s not informing anything.

Ensuring relevant maintenance data is available to inform capital planning closes the loop in the other direction. When a capital planner can see that a specific piece of equipment has required emergency repair four times in three years, they have evidence to accelerate its replacement – evidence that doesn’t exist if work orders are tracked at the building level rather than the equipment level.

And consolidating asset data into a single source, rather than maintaining two independent datasets for the same building, reduces duplication, improves accuracy, and makes it easier for any member of either team to get the information they need quickly.

Doing More With Less

The practical reality for most facility and asset managers is that resources are stretched thin. You’re being asked to do more with less, year after year. That reality makes integration feel like a luxury – something to tackle when capacity improves, which it never quite does.

Here’s the reframe: integration is precisely what creates capacity. When maintenance resources are directed at the right assets at the right time – informed by capital data – you reduce waste and increase the impact of every dollar spent. When capital plans are informed by maintenance history, you spend less on emergency replacements and more on planned, budgeted renewals that cost less and disrupt operations less.

The “sweet spot” between capital and maintenance isn’t a destination you reach after years of perfect alignment. It’s a direction of travel. Each step toward integration creates returns that fund the next step. You don’t have to solve all four roadblocks at once. You just have to start moving.

Where to Begin

The most practical starting point is the asset inventory. Specifically: does your FCA data and your CMMS asset registry describe the same buildings, systems, and equipment using the same identifiers and naming conventions?

If the answer is no – and for most organizations, it isn’t – that’s your first project. Before any meaningful data sharing can happen, the two systems need a common language. That means consistent asset IDs, consistent location hierarchies, and consistent naming at whatever level of granularity is shared between the two datasets.

From there, you can start building the bridges: workflows that route capital-flagged assets into appropriate PM queues, reporting that surfaces repeat maintenance failures to capital planners, and over time, a single source of truth for asset data that both teams trust and use.

It won’t happen overnight. But organizations that commit to the direction find, consistently, that the return is worth the effort.