CONDITION AND RISK FRAMEWORK
Know why each asset ranks where it does before you fund it
A single blended score is hard to defend in procurement and budget reviews. Our framework keeps six measures separate, so each rating answers one question: condition, functionality, criticality, risk, financial exposure, and capital priority. Condition is not risk: condition describes what was observed in the field, while risk combines likelihood and consequence of failure. Your team owns calibration (weightings, thresholds, cost assumptions, risk appetite). Our qualified engineers own review: they check every rating and record the rationale. You receive a scored asset register and work packages your team can act on. It supports your asset management plan and does not replace it.
NEXT STEP
Turn risk rankings into a capital plan
See how calibrated, engineer-reviewed scores become sequenced maintenance, repair, and replacement packages, or request a fixed-scope assessment for your assets and budget cycle.
01 · CONDITION
What state is the asset in?
Observed physical state only, rated against asset-class criteria. Enables: likelihood-of-failure inputs and a field-verified condition baseline.
- Deterioration: wear, corrosion, leakage, age-related decline
- Severity and extent: how serious and how widespread defects are
- Asset-specific rules: criteria tailored to each asset class
- Confidence: recorded to reflect data completeness and observation quality
02 · FUNCTIONALITY
Does it still do its job?
Fitness for current purpose, rated separately from condition, since a sound asset can still fall short of current needs. Enables: upgrade and right-sizing scopes.
- Component performance: operating as intended
- Capacity: meeting current demand and use
- Code and standards fit: alignment with applicable requirements
- Obsolescence: parts and support availability
03 · CRITICALITY
How much does failure matter?
Consequence of failure, rated independently of condition, so an asset in good condition that the operation depends on still ranks as critical. Enables: consequence-of-failure inputs and inspection focus.
- Operations and continuity: disruption to occupants and mission
- Safety, environment, regulatory: harm, releases, compliance exposure
- Redundancy: whether backup capacity exists
- Replacement complexity and lead time: access, shutdowns, procurement
04 · RISK
Likelihood × consequence
Likelihood of failure comes from condition and functionality. Consequence of failure comes from criticality. Each is scored on its own before they are combined. Your team calibrates the matrix and thresholds, and the result shows which assets carry the most risk, not just which look worst. Enables: a ranked risk register.
05 · FINANCIAL EXPOSURE
What could it cost?
Kept separate from criticality. Cost assumptions you approve are applied to each risk to estimate repair, collateral damage, and downtime costs if the risk is realized. Enables: risk-cost comparison for budget cases.
06 · CAPITAL PRIORITY
When should you spend?
Maintenance, repair, and replacement are sequenced by exposure, available budget, and timing, so the work lands in a defensible order. Enables: scoped, implementable work packages.
Traceable from rating to work package. Formulas, weightings, and assumptions are calibrated with your team and reviewed by qualified engineers. Every recommendation traces back to its data and can be defended in procurement and budget reviews. Review responsibilities: your team approves calibration and cost assumptions; our engineers review ratings and document rationale; final funding decisions remain with your organization. Assumptions and limitations: scores reflect conditions observed at the time of assessment, the data available, and the calibration your team approves. They are not a universal standard, and results from different portfolios or calibrations should not be compared directly. Your organization's asset management system and strategic planning stay in your hands.
Reference note: This proposed internal methodology is informed by concepts from the U.S. Army Corps of Engineers (USACE) BUILDER sustainment management system and by asset management principles described in ISO 55000, ISO 55001, and ISO 55013. These are cited for reference only. This methodology is not the official BUILDER methodology and does not represent USACE endorsement, BUILDER compliance or certification, or ISO certification or compliance.
PRIORITIZATION LOGIC
From condition data to the right next decision
Each assessed asset in the infrastructure model follows the same logic: field-verified condition indicates how far the asset has deteriorated; criticality reflects how important it is to operations; consequence of failure describes the impact if it fails; and likelihood, informed by condition, age, and redundancy, indicates how probable that failure is. Together these set action timing: what to address now, what to plan within the horizon, and what to monitor. Each asset is then routed to a recommended action: repair, replace, monitor, further investigation, system modernization, capital project development, or a portfolio scenario decision, with cost, dependencies between systems, access, sequencing, and budget availability refining the order of work. This is a planning framework applied to owner-specific priorities, not a universal standard. Final decisions remain with the owner and their engineering team.
01 · ENGINEERING
Repair
Deficiencies that can be corrected without replacing the component, documented with location and field evidence. Repair is favored when condition allows, consequence is manageable, and cost and access make correction the practical choice.
02 · ENGINEERING
Replace
Components or whole units whose condition, age, or performance supports planned replacement. Timing reflects criticality, redundancy, dependencies on connected systems, and budget availability within the owner's planning horizon.
03 · ENGINEERING
Monitor
Conditions that do not yet warrant action but should be tracked and reassessed over time. Monitoring keeps the model current where low consequence or available redundancy allows decisions to wait.
04 · ENGINEERING
Further Investigation
Findings where field data indicates a concern that needs targeted testing or engineering review before funds are committed—used when uncertainty about condition or consequence is too high to decide responsibly.
05 · ENGINEERING
System Modernization
Systems where upgrading or reconfiguring—rather than like-for-like replacement—better addresses performance, obsolescence, or dependencies, often sequenced alongside related work to limit disruption.
06 · ENGINEERING
Capital Project Development
Related needs grouped across systems and locations into scoped projects, giving owner-side engineering a validated starting point that accounts for sequencing, access, and cost.
07 · OWNER DECISION
Portfolio Scenario Decisions
Because findings are held in one model, owners can compare priorities across the portfolio—balancing condition, criticality, consequence, redundancy, cost, dependencies, access, sequencing, and budget availability to decide what moves forward, what waits, and what is grouped.
Portfolio questions the model helps answer
- Which sites and systems need attention first?
- What can be handled through repair versus replacement or modernization?
- Where is further investigation needed before committing funds?
- Which needs should be grouped into capital projects?
- How do condition, criticality, consequence, redundancy, and dependencies change the order of work?
- How do access, sequencing, and budget availability affect timing?
Illustrative planning scenarios
- Minimum budget: funds only the most critical, high-consequence needs; other items are deferred and their condition tracked. Trade-off: a larger backlog carried forward.
- Preventive intervention: addresses deteriorating assets before they reach replacement condition. Trade-off: added near-term spend in exchange for more planned, less reactive work.
- Planned replacement: schedules end-of-life equipment and phases funding across the planning horizon. Trade-off: steadier annual budgets, longer timelines for some systems.
- Risk reduction: directs funds first to high-consequence, low-redundancy systems. Trade-off: lower-consequence needs may wait longer.
- Consolidation / modernization: groups related work across systems and locations into scoped projects. Trade-off: larger capital commitments, coordinated sequencing and access.
- Scenarios are illustrative, planning-level comparisons built on owner-provided budget assumptions. They do not predict failure dates, guarantee savings, or represent construction cost estimates.