How Asset Managers Use Condition Data to Plan Repairs and Replacement

As a result, an asset can remain operational long after its condition begins to decline. A roof may continue keeping most water out despite repeated membrane failures. For example, a pump may still meet minimum flow requirements while vibration, seal leakage, and energy consumption increase. A bridge component may remain serviceable even though corrosion is reducing its future capacity.

In addition, the asset manager’s challenge is not simply to determine whether an asset works today. It is to decide what should happen next.

In most cases, the decision falls into one of three categories:

1. Continue operating the asset and monitor its condition.
2. Repair or rehabilitate the asset to restore performance or extend its service life.
3. Replace or retire the asset before further deterioration creates unacceptable cost, risk, or disruption.

However, these decisions cannot be made reliably from asset age alone. They require asset condition data that shows what is deteriorating, how quickly the condition is changing, how the asset affects service delivery, what previous repairs have accomplished, and whether further investment is economically and operationally justified.

This is the practical role of asset condition management. In practice, teams combine inspection records, measurements, photographs, maintenance history, failure data, criticality, repair cost, and remaining useful life to support decisions across the asset lifecycle.

For government agencies, utilities, transportation networks, healthcare campuses, educational institutions, and other asset-intensive organizations, the quality of these decisions affects far more than maintenance expenditure. Importantly, it affects public safety, service reliability, capital budgets, regulatory compliance, emergency response, and the ability to justify long-term investment.

Asset Condition Data Is More Than a Condition Score

Many organizations reduce asset condition to a single rating.

An asset may be classified as:

• Good
• Fair
• Poor
• Critical

For this reason, another organization may use a numerical scale from one to five or one to ten.

Condition scores help asset managers compare large portfolios. As a result, an asset manager responsible for thousands of roofs, pumps, vehicles, road sections, utility structures, medical systems, or school facilities needs a way to identify where attention is required.

The problem begins when teams treat the score as the decision.

A condition rating does not automatically determine whether to repair or replace an asset. For this reason, two assets with the same score may require very different actions because their criticality, deterioration rate, repair history, replacement cost, redundancy, and effect on service are different.

A fair-condition standby generator at a facility with several layers of backup may remain in service under active monitoring. For example, the same condition on the only emergency generator serving a hospital wing may justify immediate intervention.

The rating is therefore a summary of evidence, not a substitute for it.

A complete asset condition record should allow the manager to understand:

• Which components are deteriorating
• The type and extent of deterioration
• Whether the condition is stable or worsening
• The evidence supporting the assessment
• The asset’s current level of performance
• The consequence of failure
• Previous repairs and their effectiveness
• Current operating and maintenance costs
• The estimated remaining useful life
• Available repair, rehabilitation, and replacement options

At the same time, an inspection data management system helps preserve this evidence by connecting each inspection, defect, photograph, measurement, and corrective action to the correct asset record. This produces a condition history rather than a collection of isolated reports.

The Three Decisions Condition Data Must Support

Condition-based capital planning becomes more useful when teams connect every assessment to a clear decision path.

However, the objective is not to produce a condition report and leave the interpretation for another department. The assessment should provide enough evidence to determine whether the asset should remain in operation, receive targeted investment, or leave service.

Decision One: Continue Operating and Monitor

At the same time, continuing to operate an asset is a valid asset-management decision when the current condition remains acceptable and teams can monitor deterioration safely.

This option is appropriate when:

• The defect is minor or stable.
• The asset continues meeting required performance levels.
• Failure consequences are manageable.
• Redundancy is available.
• The deterioration rate is slow or predictable.
• Temporary controls are effective.
• Repair would produce little immediate benefit.
• Replacement is planned but not yet justified.
• Additional condition evidence is needed before committing funds.

Continue-and-monitor does not mean ignoring the asset.

In addition, it is an active decision that should define what the team will observe, how often it will reassess the asset, and which condition will trigger intervention.

For example, a facilities team may identify localized roof membrane deterioration above a noncritical storage area. Moisture testing shows no widespread water entry, the damaged area is not expanding rapidly, and the team is already evaluating a full roof replacement for a future capital cycle.

The asset manager may decide to monitor the area through quarterly inspections and after severe weather. The decision record should identify the defect location, current dimensions, photographic evidence, moisture readings, temporary controls, inspection frequency, and escalation threshold.

A trigger might be:

• Expansion beyond a defined area
• Evidence of water reaching the insulation
• Repeated leakage after patching
• Deterioration near critical electrical equipment
• Increasing repair frequency
• Structural deck damage

In addition, without these thresholds, monitoring becomes indefinite deferral.

Asset managers should also consider whether the cost of collecting more information is justified. Importantly, in some cases, a more detailed engineering assessment, nondestructive test, energy audit, or component inspection can reduce uncertainty enough to avoid premature replacement.

Asset managers should revisit the monitoring decision whenever they receive new condition data.

Decision Two: Repair or Rehabilitate

For this reason, repair and rehabilitation are appropriate when investment can restore acceptable performance, control risk, or extend useful life at a defensible cost.

A repair normally addresses a specific defect or failed component. Rehabilitation is broader. Importantly, it may restore several systems, renew a major portion of the asset, or improve the asset sufficiently to defer complete replacement.

Examples include:

• Replacing a pump seal or bearing
• Repairing concrete deterioration
• Relining a water main
• Rebuilding an elevator drive
• Replacing a roof membrane while retaining the deck
• Rehabilitating a bridge deck
• Retrofitting building controls
• Replacing switchgear components
• Overhauling a chiller
• Strengthening a structural member

The important question is not whether repair is technically possible. In practice, teams can repair almost any asset when they have enough money and time.

The question is whether the repair produces sufficient value.

The asset manager must consider:

• Expected life extension
• Restoration of performance
• Reduction in risk
• Probability of additional hidden defects
• Frequency of previous repairs
• Cost and duration of service interruption
• Availability of replacement parts
• Compatibility with future systems
• Energy or operating performance after repair
• Warranty implications
• Regulatory or code requirements
• Whether the repair addresses the cause or only the symptom

As a result, a recurring defect often changes the decision.

Consider a wastewater pump that has received three bearing replacements in four years. At the same time, if inspection history shows increasing vibration returning within months of each repair, another bearing replacement may not be the most economical response.

The cause may be misalignment, foundation movement, unsuitable operating conditions, hydraulic imbalance, poor lubrication, or an equipment-selection problem. Condition history allows the asset manager to determine whether continued component repair is extending useful life or simply repeating expenditure.

As a result, field Eagle’s asset integrity management software connects condition readings, inspection histories, defects, and corrective actions. This connection allows teams to review recurring deterioration across the asset’s life instead of treating each issue as a separate maintenance event.

Decision Three: Replace or Retire

At the same time, replacement becomes appropriate when the asset can no longer provide the required service at an acceptable level of cost and risk.

Retirement may involve removing the asset without a direct replacement because the organization no longer requires the service, another asset can assume the function, or the organization is changing how the service is delivered.

In addition, replacement decisions are rarely based on one defect. They normally reflect a combination of factors:

• Poor or rapidly declining condition
• High consequence of failure
• Increasing maintenance frequency
• Rising operating cost
• Lack of replacement parts
• Obsolescence
• Repeated service interruptions
• Inability to meet current capacity requirements
• Safety or regulatory exposure
• Low energy efficiency
• Poor compatibility with other systems
• Limited remaining useful life
• Rehabilitation cost approaching replacement value

Organizations should not replace an old asset solely because it has reached an assumed design age. Importantly, some assets perform reliably beyond their expected life because they have operated under favourable conditions and received effective maintenance. Others deteriorate much sooner because of environment, loading, installation quality, usage, or inadequate care.

Condition data allows replacement planning to move away from age-only assumptions.

For example, a 25-year-old air-handling unit with stable performance, available parts, acceptable energy use, and low maintenance requirements may remain a reasonable asset. A 12-year-old unit with severe corrosion, repeated coil failures, obsolete controls, and rising energy consumption may be a stronger replacement candidate.

In practice, asset managers must base the decision on the asset’s actual condition and role.

Inspection History Shows Direction, Not Just Status

A single assessment shows where an asset is today. For this reason, inspection history shows where it is going.

This distinction is central to asset replacement planning.

As a result, consider two bridge components that both receive a condition score of three on a five-point scale.

The first has remained at level three for six years. Deterioration is localized, protective systems are functioning, and measurements show little change.

For this reason, the second was rated one three years ago, two last year, and three this year. Corrosion is spreading, section loss is increasing, and repair costs are rising.

As a result, the current score is identical. The planning implications are not.

At the same time, the first asset may remain under routine observation. The second may require rehabilitation planning before the condition reaches a point where repair becomes difficult or emergency restrictions are required.

Trend analysis should examine:

• Changes in condition score
• Growth in defect size or quantity
• Movement in measurements
• Increasing inspection frequency
• New failure modes
• Expansion from one component to others
• Changes in operating performance
• Reappearance after repair
• Time between maintenance events
• Changes in the consequence of failure

The quality of the trend depends on consistent data.

In practice, teams must take measurements from comparable locations, standardize units, maintain stable asset identifiers, and apply inspection categories consistently over time.

The publication of ISO 55013:2024 reflects the importance of managing data so that it supports asset-management objectives. At the same time, condition data only becomes useful for long-term decisions when it is reliable, traceable, appropriately structured, and connected to the asset it describes.

Criticality Changes the Meaning of Condition

Condition describes what is happening to the asset. In addition, criticality describes why it matters.

Asset criticality may consider:

• Safety consequences
• Environmental consequences
• Service disruption
• Number of users affected
• Regulatory impact
• Financial loss
• Damage to other assets
• Lack of redundancy
• Recovery time
• Public or reputational consequences

Teams may continue operating a poor-condition asset with low criticality until planned replacement funds become available. Importantly, a moderate-condition asset with a catastrophic failure consequence may require earlier intervention.

For example, a school district may have two boilers in similar physical condition.

One serves a small administrative building that can temporarily use portable heating. The other is the only heating source for a residential educational facility in a cold climate.

Although the condition scores are similar, the second boiler has greater service consequence, less operational flexibility, and a more urgent replacement need.

However, criticality should not be used to inflate every decision. It should distinguish assets whose failure would materially affect the organization’s objectives.

For this reason, the updated ISO 55000:2024 frames asset management around realizing value from assets throughout their lifecycles while aligning decisions with organizational objectives, risk, and performance. Therefore, condition data provides the most value when teams interpret it within the service and risk context of the organization.

Repair Cost Alone Does Not Determine the Best Option

A repair may cost less than replacement and still be the worse decision.

Asset managers need to compare lifecycle consequences rather than only the initial project cost.

Asset managers should evaluate a repair option against:

• Expected remaining life after repair
• Future maintenance expenditure
• Operating cost
• Energy or fuel use
• Failure probability
• Service-interruption risk
• Availability of parts and technical support
• Compliance requirements
• Residual value
• Future replacement cost
• Cost of delayed action

Consider a hospital chiller requiring a major compressor rebuild.

For this reason, the repair is estimated at $180,000 and may extend the chiller’s life by four years. A new chiller costs $650,000 but offers lower energy use, better capacity control, a new warranty, current refrigerant technology, and an expected service life of more than twenty years.

As a result, the repair may still be appropriate if capital funds are unavailable or if the facility expects a larger central-plant redevelopment. However, the lower initial price does not by itself make repair the more economical choice.

A simple comparison may include:

Repair cost per year of expected life extension

and

Replacement cost per year of expected service life

A stronger analysis will also include energy, maintenance, downtime, risk, and residual value.

The purpose is not to create false precision. Forecasts contain uncertainty. As a result, the purpose is to make the assumptions visible and compare alternatives consistently.

Remaining Useful Life Is an Estimate, Not an Expiry Date

Remaining useful life is the period an asset is expected to continue providing the required service before replacement, retirement, or major rehabilitation becomes necessary.

It is not simply:

Expected design life minus current age

A more defensible estimate considers:

• Current physical condition
• Deterioration rate
• Operating environment
• Usage and loading
• Maintenance history
• Quality of installation
• Component obsolescence
• Availability of parts
• Functional requirements
• Regulatory change
• Planned service level
• Consequence of failure

At the same time, a building component may have significant physical life remaining but little functional life if it no longer meets capacity, accessibility, efficiency, or regulatory requirements.

Conversely, an asset may be beyond its published design life but remain safe and economical where condition evidence supports continued operation.

Therefore, asset managers should present remaining useful life as a range when uncertainty is material.

For example:

• Most likely remaining useful life: six years
• Optimistic case: nine years
• Conservative case: three years

The range helps capital planners understand timing risk. It also supports scenario planning where inspection evidence is incomplete.

Condition-Based Capital Planning Across a Portfolio

Individual decisions become more difficult when an organization manages hundreds or thousands of assets competing for limited capital.

The asset manager must move from “Which option is best for this asset?” to “Which investments should the organization fund first?”

Condition-based capital planning typically combines:

• Condition
• Criticality
• Deterioration rate
• Remaining useful life
• Repair or replacement cost
• Service impact
• Regulatory obligation
• Project readiness
• Interdependencies
• Funding constraints

A portfolio may contain many poor-condition assets, but not all should receive funding in the same year.

In addition, one project may need immediate delivery because failure would close a critical facility. Teams may bundle another project into a planned renovation. Importantly, a third may be deferred because redundancy exists and the condition is stable. A fourth may require additional investigation before a reliable scope can be prepared.

For example, a centralized asset management software platform helps maintain the asset register, inspection history, specifications, corrective actions, and condition information needed to compare these priorities consistently.

The strongest capital plans explain why teams propose each project, which condition evidence supports it, which risk it addresses, and what may happen if the organization delays the investment.

Government and Public Infrastructure

As a result, government asset managers often need to defend capital decisions to councils, boards, finance departments, regulators, auditors, and the public.

Condition data provides an evidence base for explaining why one facility, road section, bridge, fleet asset, or utility project requires investment before another.

A defensible public-sector business case should be able to show:

• Current condition
• Service affected
• Population or users affected
• Risk of continued operation
• Previous maintenance history
• Available alternatives
• Estimated useful-life extension
• Project timing
• Consequence of deferral

This evidence becomes particularly important when organizations approve capital budgets several years in advance.

For this reason, an asset that appears manageable during budget preparation may deteriorate rapidly before construction begins. Inspection frequency should reflect the rate of change and the length of the capital-delivery process.

As a result, assets with long design, procurement, or regulatory approval periods may require replacement decisions while they still appear operationally acceptable.

If teams wait until failure becomes imminent, they may lose the opportunity to plan the investment.

Water and Wastewater Utilities

At the same time, utilities operate long-lived assets, and often manage buried, continuously operating, geographically distributed, or difficult-to-inspect assets.

Condition-based decision-making may rely on:

• Leakage history
• Break frequency
• Pipe material and age
• Pressure
• Water quality
• Wall-thickness measurements
• Corrosion
• Pump efficiency
• Vibration
• Motor current
• Valve operability
• Structural assessment
• CCTV inspection
• Service consequence

For buried infrastructure, direct condition evidence may be limited. Asset managers may need to combine inspection samples with failure history, soil conditions, pressure zones, material type, construction period, and consequence modelling.

For example, a water main with frequent breaks in a low-consequence area may remain a repair candidate. A similar main crossing a highway, hospital access route, or environmentally sensitive area may justify replacement before failure frequency becomes severe.

At the same time, the decision should consider both probability and consequence.

Transportation Infrastructure

Transportation agencies manage assets such as bridges, culverts, pavements, retaining walls, signals, lighting, drainage systems, and fleet equipment.

However, a component-level defect may not require complete asset replacement.

For example, teams may repair or rehabilitate localized bridge-deck deterioration while the primary structure remains sound. Repeated patching becomes less attractive when defect areas expand, traffic-control costs rise, water reaches structural components, or the remaining deck life becomes too short to justify another repair cycle.

Condition history helps determine when the economic transition occurs from maintenance to rehabilitation and from rehabilitation to replacement.

Operational cost is particularly important because road closures, detours, lane restrictions, and rail possessions may cost more than the physical repair.

In addition, the asset decision should therefore account for disruption as well as construction cost.

Healthcare Campuses

Healthcare facilities contain highly interdependent systems. Importantly, failure of one asset may affect clinical operations, infection control, patient comfort, emergency response, or regulatory compliance.

A condition assessment should consider not only equipment condition but also:

• System redundancy
• Patient-care consequence
• Infection-control requirements
• Shutdown feasibility
• Temporary service arrangements
• Availability of qualified contractors
• Construction phasing
• Access to occupied clinical areas
• Compatibility with future projects

A poor-condition domestic water valve may appear minor until the team determines that replacement requires shutting down an entire patient tower.

For this reason, condition-based planning allows the organization to group related work, establish temporary services, coordinate clinical access, and avoid emergency intervention.

Educational Institutions

Schools, colleges, and universities often manage aging portfolios with constrained funding and limited construction windows.

As a result, condition data helps facilities teams distinguish between cosmetic deterioration, maintainable defects, and failures that threaten building operation.

Repair and replacement planning may need to account for:

• Academic calendars
• Student occupancy
• Residence operations
• Laboratory requirements
• Accessibility
• Indoor air quality
• Seasonal weather
• Heritage constraints
• Deferred maintenance
• Energy performance

A deteriorated building envelope may initially produce localized leaks. Over time, water can affect insulation, structural elements, interior finishes, electrical systems, and indoor environmental quality.

Inspection history helps show when repeated patching has stopped being economical and when a coordinated envelope rehabilitation offers greater value.

The Importance of Component-Level Data

An asset is rarely replaced because every part has failed at the same time.

As a result, a building may have a poor roof but a sound structure. A pump may have a failed motor but a reusable casing. At the same time, a vehicle may have a deteriorated body while the drivetrain remains serviceable.

Component-level condition data helps avoid both premature replacement and fragmented repair.

The asset hierarchy should let teams link inspection findings to:

• Systems
• Subsystems
• Assemblies
• Components
• Locations

This allows the manager to determine whether deterioration is isolated or systemic.

As a result, it also supports phased rehabilitation.

A campus may replace building automation controls this year, renew air-handling equipment in three years, and defer the distribution system for a later project. At the same time, without component-level information, teams may assign one condition score to the entire system that hides these differences.

When Previous Repairs Stop Adding Value

Teams should not read repair history simply as proof that they maintained the asset.

Instead, they should examine it for patterns.

Questions include:

• Are repair intervals becoming shorter?
• Are costs increasing?
• Is the same component failing repeatedly?
• Are failures spreading to adjacent components?
• Does each repair restore full performance?
• Are replacement parts becoming difficult to obtain?
• Is downtime increasing?
• Are temporary repairs becoming permanent?
• Are maintenance teams modifying parts to keep obsolete equipment operating?
• Are inspections becoming more frequent because confidence is declining?

A rising maintenance cost does not automatically justify replacement. Importantly, some high-value assets are economical to maintain for decades.

The issue is whether spending continues producing a predictable and acceptable result.

When repair expenditure increases while reliability, performance, or remaining useful life continues declining, replacement becomes more defensible.

Data Quality Determines Decision Quality

In addition, asset-replacement models can look sophisticated while relying on poor information.

Common data problems include:

• Duplicate asset records
• Inconsistent condition scales
• Missing inspection history
• Measurements without units
• Photographs not linked to assets
• Free-text defect descriptions
• Unrecorded repairs
• Inconsistent component names
• Missing installation dates
• Condition scores copied forward without reassessment
• Replacement costs based on outdated projects

These weaknesses create false confidence.

Importantly, before using condition data for capital planning, organizations should confirm that the most decision-critical fields are complete and consistent.

The asset register does not need to be perfect before useful planning can begin. For this reason, it should, however, be reliable enough that the organization can trace the evidence behind major investment decisions.

Field Eagle’s inspection and asset data management provides a shared record for asset details, inspection findings, condition histories, and reports. As a result, organizations do not need to rebuild the evidence manually each time they review a repair or replacement decision.

A Practical Decision Framework

Teams can structure a condition-based decision around the following questions.

• Is the asset currently safe and capable of providing the required service?

If not, immediate controls, shutdown, repair, or replacement may be necessary.

• Is the condition stable, predictable, and monitorable?

For this reason, a stable condition may support continued operation. Rapid or uncertain deterioration may justify earlier intervention.

• What happens if the asset fails?

As a result, the consequence determines how much uncertainty and risk the organization can accept.

• Can a repair restore acceptable performance?

Teams should define the scope, expected life extension, and probability of recurring defects.

• Does rehabilitation address the wider system?

At the same time, rehabilitation may be more appropriate where several related components are deteriorating.

• What is the expected lifecycle cost of each option?

The comparison should include capital, maintenance, operation, disruption, and risk.

1. How long will replacement take?

Assets with long planning and procurement periods may require early decisions.

1. What evidence would change the decision?

As a result, additional inspections, testing, engineering analysis, or performance monitoring may reduce uncertainty.

1. What is the trigger for moving to the next decision?

A monitored asset should have clear repair or replacement thresholds.

Documenting the Decision

At the same time, a condition assessment should lead to a documented recommendation.

The record should include:

• Asset and component
• Current condition
• Supporting evidence
• Deterioration trend
• Criticality and failure consequence
• Current performance
• Repair history
• Remaining useful life
• Options considered
• Cost assumptions
• Recommended action
• Timing
• Monitoring requirements
• Escalation thresholds
• Decision owner
• Review date

This does not require a lengthy engineering report for every minor asset.

In addition, the level of documentation should reflect the cost, complexity, uncertainty, and consequence of the decision.

Major capital investments should have a clear evidence trail. Importantly, future reviewers should understand why the team made the decision and which assumptions it used, and whether later condition data supports or challenges those assumptions.

Condition Data Turns Capital Planning Into an Ongoing Process

Capital planning is sometimes treated as an annual exercise. Teams review asset lists, rank projects, and often fix the plan until the next budget cycle.

However, asset condition does not follow the budget calendar.

New defects emerge, deterioration accelerates, repair outcomes change, teams delay projects, and service requirements evolve. Importantly, condition-based capital planning must therefore be updated as new evidence becomes available.

A mature process connects field inspections, maintenance, engineering assessments, financial planning, and capital delivery.

Inspectors record the condition. In addition, maintenance teams document what they find during repairs. Asset managers evaluate options. Finance teams test affordability. Leadership approves priorities. For this reason, future inspections confirm whether the decision remains valid.

As a result, this is consistent with the lifecycle approach emphasized by the current ISO 55000 series, which links asset information, decision-making, risk, performance, and organizational value rather than treating asset management as a collection of isolated maintenance activities.

Better Decisions Begin With Better Condition Evidence

However, organizations should not force asset managers to choose between repair and replacement using age, intuition, and incomplete reports.

Reliable asset condition data provides a stronger basis for deciding whether to continue operating and monitor, repair or rehabilitate, or replace and retire.

At the same time, the current condition establishes the starting point. Inspection history shows the direction of change. Criticality explains the consequence. As a result, repair history reveals whether previous interventions created lasting value. Remaining useful life informs timing. At the same time, lifecycle cost shows whether additional investment is justified.

No single field makes the decision.

In addition, the value comes from connecting the evidence.

When teams keep condition information consistent, asset-linked, and current, organizations can intervene before failure, avoid premature replacement, build stronger capital plans, and explain why they direct limited resources toward particular assets.

As a result, that is the difference between recording condition and managing it.

Frequently Asked Questions