Pavement, Tunnels & the Deficiency-to-Work-Order Loop

🎯 Who this is for: Pavement and network managers, tunnel asset owners, and maintenance planners who need to know how Civil Infrastructure captures road and tunnel condition and — crucially — how any inspection finding becomes a prioritized, traceable work order.

Series: Part 3 of 5 — Maximo Civil Infrastructure on MAS 9 | Read time: 17 minutes

🛣️ Beyond the Bridge

Bridges get the attention because the federal program is prescriptive and the failures are dramatic. But a state DOT owns thousands of centerline miles of pavement for every bridge, and a transit agency's tunnels carry life-safety obligations a bridge never will. If the application only did bridges, it would cover a fraction of the portfolio.

This part covers the rest — pavement and tunnels — and then the mechanic that unifies the whole application: the deficiency-to-work-order loop. That loop is what turns Civil Infrastructure from an inspection database into an asset-management system, because it is the point where a finding stops being a note and becomes maintenance.

💡 Key insight: The unifying idea across bridges, pavement, and tunnels is the one from Part 1 — the unit of condition and work is finer than the whole asset. For a bridge it is the element; for a road it is the segment; for a tunnel it is the element and the life-safety system. Every asset class decomposes into addressable units, and the deficiency-to-work-order loop works the same way on all of them.

🛤️ Roads Are Linear Assets

A road is not inspected element-by-element like a bridge; it is scored segment-by-segment along its length. The condition of a five-mile route is not one number — it is a profile, and the treatment decision is per segment.

Civil Infrastructure supports road condition assessment with the standard pavement-management toolkit:

MeasureWhat it captures
Pavement Condition Index (PCI)A composite 0–100 score of surface condition derived from observed distresses
Distress identificationThe specific distresses present — cracking, rutting, raveling, potholes — and their quantity
Ride quality (IRI)International Roughness Index — how rough the ride is, a proxy for user experience and a MAP-21 performance measure
Treatment recommendationA recommended treatment based on the condition profile

PCI: the composite score

The Pavement Condition Index is a 0–100 composite: 100 is a newly constructed pavement, and the number falls as distresses accumulate. It is computed from the observed distresses — their type, severity, and extent — so it is not a subjective grade but a defensible rollup of what the inspector recorded. Like the bridge component rating, PCI is a summary; the underlying distress quantities are the detail beneath it.

Distress identification and quantification

Beneath the PCI sits the distress record: which distresses are present (fatigue cracking, transverse cracking, rutting, raveling, potholes), at what severity, over what quantity of the segment. This is the pavement equivalent of condition-state quantity tracking from Part 2 — the detail that supports the score and drives the treatment.

IRI: ride quality

The International Roughness Index measures how rough the pavement rides. It matters for two reasons: it is what the traveling public actually experiences, and it is one of the federal MAP-21 performance measures states report on (Part 5). A segment can have a decent PCI and a poor IRI, or vice versa, so both are carried.

Treatment recommendation and preservation

The payoff of condition data is a treatment recommendation. The condition profile maps to a treatment strategy — and the strategy that saves the most money is preservation: treating a pavement while it is still in fair condition, before it drops into the expensive reconstruction range.

PCI bandConditionTypical strategy
85–100Good / excellentRoutine maintenance; do nothing structural
70–85SatisfactoryPreventive preservation (crack seal, fog seal)
55–70FairPreservation / thin overlay — the sweet spot
40–55PoorStructural overlay / rehabilitation
0–40Very poor / failedReconstruction — the most expensive outcome
💡 Key insight: The reason condition-based pavement management pays for itself is the shape of the deterioration curve. A dollar of preservation spent in the "fair" band (PCI 55–70) prevents several dollars of reconstruction later. The value of capturing PCI, distress, and IRI is not the report — it is catching segments in the fair band and treating them before they fall off the cliff. An agency that only reconstructs failed roads is spending the most money for the least network condition.

🚇 Tunnel Inspection Under NTIS

Tunnels combine the element-based structural model with something bridges do not have: life-safety systems. A tunnel is a structure and a life-safety environment at once, and its inspection reflects both.

Civil Infrastructure provides tunnel inspection aligned to the National Tunnel Inspection Standards (NTIS):

  • Element-based tunnel inspection — the same condition-state approach as bridges, applied to tunnel structural elements (liner, invert, portal, ceiling)
  • Structural and functional element condition tracking — both the structure and the functional systems
  • Fire/life-safety system tracking — ventilation, fire suppression, emergency lighting, communications, egress

The fire/life-safety dimension is the differentiator. A crack in a tunnel liner is a structural finding; a failed ventilation fan or a dead emergency-lighting circuit is a life-safety finding — and both need to be tracked, prioritized, and worked, often with the life-safety items carrying the higher priority. Modeling the tunnel's functional systems as inspectable, condition-tracked elements is what lets the same deficiency loop cover "the liner is spalling" and "emergency lighting section 3 is out."

💡 Key insight: For tunnels, do not let the structural inspection eclipse the life-safety systems. A structurally sound tunnel with a degraded ventilation or fire-suppression system is a serious problem, and a program that inspects the liner carefully but treats the fans as an afterthought has the risk backwards. Configure the functional and life-safety systems as first-class inspectable elements so their deficiencies get the priority they deserve.

🔁 The Deficiency-to-Work-Order Loop

Here is the mechanic that unifies the whole application. Every inspection — bridge element, pavement segment, tunnel system — can produce deficiencies, and Civil Infrastructure tracks them through to resolution:

  1. Identify — deficiencies are recorded during inspection, attached to the specific element or segment that has them.
  2. Prioritize — deficiencies are prioritized by severity and safety impact, so the worst and most dangerous rise to the top of the queue.
  3. Link to work — deficiencies are linked to maintenance work orders in core Manage, which run the labor, materials, and cost.
  4. Track resolution — deficiency resolution is tracked over time, so open findings are visible and closure is recorded.
  5. Report — deficiency reports are generated for management and regulators.

The design virtue here is traceability. Because the deficiency is attached to "bearing #4" or "segment MP 12.3–13.1," the work order traces back to exactly what was found, the closure updates exactly that record, and the next inspection can see whether last cycle's deficiency was actually resolved. This is the difference between an inspection program that generates findings and an asset-management system that closes them.

Loop stageWhere it livesWhat it produces
Inspection findingCivil Infrastructure inspectionA deficiency on an element/segment
PrioritizationCivil Infrastructure deficiency trackingA ranked queue by severity/safety
Work orderCore ManageLabor, materials, cost, schedule
ResolutionCore Manage → back to the deficiencyClosure recorded against the finding
ReportingCivil Infrastructure / Manage reportingDeficiency and status reports

🩺 Condition-Based Maintenance with Maximo Health

The most mature version of the loop does not wait for a human to notice a deficiency — it drives maintenance from condition data directly. Civil Infrastructure supports condition-based maintenance:

  • Drive maintenance decisions from inspection condition data rather than a fixed calendar.
  • Trigger work orders when condition ratings drop below thresholds — a deck component rating falling to a defined level, a pavement segment dropping below a PCI threshold.
  • Integrate with Maximo Health for condition scoring — Health computes the asset health score from the condition data, giving a single prioritization signal across a diverse portfolio.
  • Support preservation-based strategies — act while the asset is still in fair condition.

The division of labor is clean and worth restating: Civil Infrastructure produces the condition (element states, PCI, IRI, tunnel-system status), Maximo Health turns condition into a score and a prioritization signal, and core Manage runs the resulting work. The Health mechanics — how the score is computed, weighted, and trended — belong to the MAS Health series; here, Health is the engine that lets you rank a bridge deck, a pavement segment, and a tunnel fan on one comparable scale so the limited capital budget goes to the right place.

🔧 Worked Example: Pavement Segment MP 12.3–13.1

Walk a real pavement section — segment MP 12.3–13.1 on a state route — through the loop.

Step 1 — The condition survey. The segment is surveyed. The inspector records the distresses: moderate fatigue cracking over 30% of the segment, rutting averaging 0.4 inches, some transverse cracking. The composite PCI comes out at 58 — squarely in the "fair" band. The IRI is recorded and is trending up (rougher).

Step 2 — The treatment recommendation. A PCI of 58 with those distresses maps to a preservation/thin-overlay strategy — the fair-band sweet spot where treatment is cheapest and most effective. The alternative, waiting, would let the segment fall toward the 40s and the reconstruction range.

Step 3 — Deficiency and prioritization. The condition generates a deficiency on the segment. It is prioritized against the network: not a safety emergency (a pothole would rank higher), but a high-value preservation opportunity that will get more expensive if deferred.

Step 4 — Health scores it. Maximo Health folds the PCI and IRI into a condition score for the segment, letting the network manager compare it against every other segment and against the bridges and tunnels competing for the same budget.

Step 5 — The work order. The preservation treatment becomes a work order in Manage — a thin overlay of the 0.8-mile segment, with the crew, materials (asphalt tonnage estimated from the segment area), and cost. It is scheduled with the paving program.

Step 6 — Resolution and the next survey. The overlay is completed; the work order closes and updates the segment's deficiency. The next condition survey should show the PCI back near 85, confirming the treatment worked — and the whole cycle is traceable from the distress reading to the closed work order.

The point of the example is that pavement management is not a separate silo — it runs through the same deficiency-to-work-order loop as bridge and tunnel inspection, with Health providing the common prioritization currency.

⚠️ Edge Cases and Gotchas

PCI and IRI disagree. A segment can score well on PCI (few surface distresses) but poorly on IRI (rough ride from base-layer issues), or the reverse. Do not collapse them into one number — carry both, because they drive different treatments and IRI is separately reportable.

Safety deficiencies must jump the queue. A pothole or a failed tunnel fire-suppression component is not a normal-priority preservation item. Make sure the prioritization actually elevates safety-impact deficiencies above condition-optimization ones, or the queue will bury an urgent finding under a hundred preservation opportunities.

Threshold tuning. Condition-triggered work orders are only as good as the thresholds. Set them too tight and you flood the crews with low-value work; too loose and you miss the preservation window. Tune thresholds against the deterioration curve and revisit them.

Segment boundaries drifting. If pavement segments are re-cut between survey cycles, condition history stops lining up. Keep segment definitions stable, or maintain a mapping, so trend analysis and deficiency history survive.

🩺 Troubleshooting the Loop

  • If inspection findings are not turning into work, it means deficiencies are being recorded but not linked to work orders, so confirm the deficiency-to-work-order link and that someone owns the deficiency queue.
  • If an urgent safety finding sat in the queue, it means prioritization is weighting condition over safety impact, so review the prioritization so safety-impact deficiencies elevate correctly.
  • If condition-based work orders are not triggering, it means thresholds are unset or the condition-to-trigger link is not configured, so verify thresholds and the trigger configuration.
  • If Health shows no comparable scores across asset classes, it means condition data is not feeding Health for some classes, so confirm each class (bridge, pavement, tunnel) is wired into Health scoring.
  • If a closed work order did not update the deficiency, it means the closure is not writing back to the finding, so verify the work order's completion updates the linked deficiency.

📋 Practical Notes for Rollout

  • Establish a stable linear referencing system for pavement (route-and-milepost) before loading condition data, so segments and history stay aligned.
  • Model tunnel life-safety systems as first-class inspectable elements, not notes, so their deficiencies get proper priority.
  • Define and document your treatment decision rules (PCI/distress → treatment) so recommendations are consistent and defensible.
  • Wire every asset class into Health so the capital budget is allocated on one comparable condition scale.
  • Tune condition thresholds against the deterioration curve and revisit them after the first full cycle, when you have real data on what the triggers produced.

Key Takeaways

  • Roads are linear assets scored segment by segment — PCI (0–100 composite), distress quantification, IRI ride quality, and treatment recommendation — with preservation in the fair band the highest-value play.
  • Tunnel inspection follows NTIS, combining element-based structural inspection with fire/life-safety system tracking, and life-safety systems must not be treated as an afterthought.
  • The deficiency-to-work-order loop unifies the application — findings attach to elements/segments, are prioritized by severity and safety, become traceable work orders in Manage, and are tracked to resolution.
  • Condition-based maintenance triggers work when ratings drop below threshold, with Maximo Health turning condition into a comparable score across bridges, roads, and tunnels.
  • The loop is the same across every asset class, which is what makes Civil Infrastructure an asset-management system rather than an inspection database.

References

Series Navigation

Previous:Part 2 — NBI Bridge Inspection & AASHTO Element Condition
Next:Part 4 — AI-Augmented Inspection: Visual Inspection & Large Vision Models

About TheMaximoGuys: We help Maximo developers and teams navigate the move to MAS 9 with practical, no-hype guidance grounded in how the platform actually behaves.

Published by TheMaximoGuys | July 2026