Facility Condition Assessment Software: What Happens When the Consultant Report Ages Out?

Why a facility condition assessment is stale before you present it

The binder arrives in June. Eleven volumes, 340 buildings, a spreadsheet appendix with 26,000 line items, and a headline number: $412 million of deferred maintenance, Facility Condition Index of 0.19. The facilities director presents it to the board in September. By the following March, three chillers have been replaced, two roofs failed early after a hail event, a building was taken offline, and a residence hall was handed over from a capital project with brand new systems. None of that is in the spreadsheet. The next assessment is scheduled for year five. For the intervening four years, the official number is wrong, and everyone in the room knows it is wrong, which quietly undermines every funding request built on top of it.

The stack around this is usually a CMMS such as Maximo, AiM, TMA, or Archibus holding work orders, a finance system holding capital project ledgers, an Excel model the director maintains for the board, the consultant deliverable, and possibly a licence for Accruent VFA, Brightly Predictor, or Gordian. Those are serious products with real assessment methodology behind them. The problem is not their engineering. It is that the assessment and the operation are two separate universes: the assessment describes a moment, the operation moves every day, and nothing reconciles the two. So the backlog ages, the FCI drifts from reality, and the capital plan becomes a document produced for a meeting rather than a system anyone runs the estate from.

Across the institutional estate projects we have delivered, the recurring cost is not the assessment fee. It is that renewal decisions get made from a stale list, so an asset that failed early gets funded as an emergency at a premium while an asset on the list at high priority is quietly still fine, and nobody can prove either way. The second recurring cost is credibility. When a trustee asks why the backlog went up despite $30 million of spend last year, and the answer takes two weeks to assemble, the next funding request lands differently.

Problem 1: the assessment is a document, not a data set you can operate

Consultant deliverables come as PDFs plus a spreadsheet export in the consultant's own schema. The line items carry a system, a deficiency description, a cost, a priority, and a recommended year. What they usually do not carry is a stable identifier that survives to the next assessment, so when the follow up survey happens in year five, matching this cycle's findings against last cycle's is a manual exercise. That means you cannot answer the single most important question about your estate: what did we fix, what got worse, and what did we predict wrongly.

What a custom build does: the asset, not the finding, is the permanent record. Each building gets a hierarchy down to the system and component level, and every assessment produces observations against those components rather than free standing line items. Now a chiller has a history: installed 2004, assessed fair in 2019, assessed poor in 2024, repaired twice in between, replaced in 2026. The FCI is derived from that history rather than restated from scratch. This is the change that turns a consultant deliverable into an operational system, and it is the reason to build rather than to keep buying surveys.

Problem 2: your asset hierarchy is not the standard hierarchy, and forcing it costs you the data

Uniformat II gives you a sensible classification of building systems, and any credible build should map to it. But a health system with central utility plants, medical gas, and a linear accelerator vault does not fit the same tree as a university with residence halls and a stadium, and a state agency with 900 small rural structures does not fit either. Off the shelf platforms ship with a fixed hierarchy and a fixed cost model. Accruent VFA and Gordian both bring strong cost libraries, Gordian in particular because RSMeans data sits behind it, and that is a genuine advantage you should weigh honestly. The friction shows up when your asset classes do not exist in the tree, so your assessors put them in Other, and three years later Other is 18 percent of your backlog and completely unusable for planning.

What a custom build does: a hierarchy that maps to Uniformat for external reporting and grant applications, while carrying your own asset classes as first class objects underneath. Your renewal categories, your criticality ratings, your funding source restrictions. A build should also carry the awkward things that never fit a product: leased space you maintain but do not own, assets on a ground lease, historic structures with restricted intervention, and infrastructure such as steam tunnels and campus distribution that is not inside any single building.

Problem 3: expected life tables are averages, and your buildings are specific

Every renewal forecast rests on expected useful life. Published service life data gives you a starting number for a rooftop unit or a membrane roof, and it is a reasonable starting number. It is also an average across climates, duty cycles, and maintenance regimes, and your estate has a building where the air handlers run at coastal exposure and another where they sit in a conditioned penthouse.

What a custom build does: keep the published life as the default, then let it be adjusted per asset with a recorded reason, and, once you have a few years of your own replacement history, compare actual service life against the assumed life by asset class and location. That comparison is the most valuable data an institution can own, because it converts a generic forecast into your forecast, and it is the argument that wins a budget hearing. No purchased table can tell you that your 1970s residence hall roofs last 22 years and your 1990s academic building roofs last 31.

Problem 4: the backlog never reconciles with the work you actually did

This is the failure that erodes trust fastest. A trustee sees $30 million spent and the backlog unchanged or higher. Both facts are usually true, because the spend went to items outside the assessed backlog, or to renewals whose completion was never written back, or the backlog grew through escalation and new findings faster than it was retired. Without a reconciliation, you look either incompetent or evasive.

What a custom build does: link work orders and capital projects back to the components they touched, using the CMMS as the source of work history rather than duplicating it. Then produce a bridge: opening backlog, plus escalation, plus new findings, minus completed renewals, minus deferrals reclassified, equals closing backlog. That single view answers the board question in the meeting instead of in a fortnight. Practically this means a two way integration with Maximo, AiM, TMA, or Archibus, and a rule set for deciding which work orders count as renewal against which count as routine maintenance, because that judgment is yours and no product will guess it correctly.

Problem 5: the deliverable is a funding scenario, and it has to survive a hostile room

Facilities directors do not get funded for a condition index. They get funded for an answer to a question like: if we hold funding flat for six years, what is our FCI in 2032, which buildings go below acceptable, and what is the probability of a failure that closes a teaching space. That is a scenario model, and it needs to run in front of people, not overnight.

What a custom build does: scenarios as first class objects. Flat funding, bond issuance, targeted reinvestment in the worst quartile, demolish and consolidate. Each scenario projects backlog, FCI by building and by portfolio, and risk exposure by criticality band, on your budget cycle and your fiscal calendar. Project bundling matters here too: 40 separate roof line items across a campus are one procurement, and a plan that cannot bundle produces a list nobody can actually execute. The output your board sees should be three charts and a building level table, generated from live data, not a deck assembled by an analyst over two weeks.

What this costs and how long it takes

Across the 2,000-plus projects Digital Heroes has delivered, here is the honest shape. A focused first release, meaning the asset register with hierarchy and condition, the backlog and FCI engine, life and escalation modelling, and a capital renewal forecast with scenarios, runs $65,000 to $140,000 and ships in 12 to 18 weeks. A full platform adding an offline capable field inspection app for assessors, CMMS reconciliation, project bundling and procurement handoff, funding source tracking, and board reporting runs $160,000 to $400,000, phased over 7 to 12 months.

What drives price up specifically for institutional estates: the number of distinct asset classes, since a health system with clinical infrastructure carries far more model complexity than an office portfolio. CMMS integration depth, because reading work orders is straightforward and writing renewal completions back is not. Offline field capture, if your assessors work in basements and remote sites with no signal, which is a real engineering requirement rather than a checkbox. Cost library licensing, if you want commercial unit cost data rather than your own historical bid data. And migrating multiple legacy assessments into one comparable history, which is the item most often underestimated.

What keeps price down: starting with your top 50 buildings by replacement value and your three highest risk systems, typically roofing, primary HVAC, and electrical distribution. That covers most of the money and teaches the model before you scale it.

Build versus buy, and when buying is the right answer

Buy if you are under roughly 1 million square feet with a stable estate, a single funding source, and no legislative or trustee reporting obligation beyond an annual number. Brightly Predictor is a reasonable fit there, and commissioning a Gordian assessment on a cycle is a perfectly defensible way to run a small portfolio. Custom software would be an expensive way to hold 26,000 rows.

Build when two or more of these are true. Your estate is large enough that the assessment cycle costs more than a small team. Your asset classes genuinely do not fit a product hierarchy, which is normal for health systems, ports, transit agencies, and research campuses. You have to reconcile backlog against completed work in front of a board or a legislature. You hold multiple funding sources with different restrictions, so a single prioritised list is useless and you need per source plans. Or your renewal decisions have started diverging from the assessment because everyone knows it is out of date, which is the clearest signal that the document has stopped being a system.

How to choose a developer for facility condition and capital planning software

Ask them to draw the model before you sign. You should see building, system, component with an identity that persists across assessment cycles, observation, deficiency, renewal event, and funding source. If the sketch is buildings and repairs, they will rebuild the consultant spreadsheet with a login screen.

Ask specifically how the backlog reconciles to completed work. If they cannot describe the bridge from opening backlog to closing backlog, they have not sat in a board meeting where that question was asked, and you will be the one holding the silence.

Ask what they have integrated. Maximo, AiM, TMA, and Archibus are four different problems with four different data models, and a GIS layer for campus infrastructure is a fifth. Ask for the specific system and version, not a claim about integration capability.

Ask who owns the code and the asset data, and get it in writing before kickoff. You should own the repository, the infrastructure accounts, and the right to bring in another firm. At Digital Heroes the client owns the code from the first commit, and the asset history you build is an institutional record that should never sit behind someone else's licence.