NBI Bridge Inspection & AASHTO Element Condition in Maximo

🎯 Who this is for: Bridge program managers, inspection team leads, and Maximo architects who own the FHWA inspection program and need to know exactly how Civil Infrastructure captures element condition, rolls it up to the federal ratings, schedules the cycle, and produces the NBI submission.

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

🌉 Why This Is the Heart of the Application

Everything else in Civil Infrastructure orbits bridge inspection. The asset model in Part 1 exists to hold the inspection. The deficiency loop in Part 3 exists to act on it. The AI in Part 4 exists to augment it. The crosswalk in Part 5 exists to prove it. So this part is the center of gravity, and it is worth doing carefully.

Federal bridge inspection is not a best-effort activity. It is a prescriptive federal program under the National Bridge Inspection Standards (NBIS), codified in 23 CFR 650, Subpart C. It defines who may inspect, how often, on what scale, and what must be reported to the National Bridge Inventory. Civil Infrastructure implements that program — and this part walks it end to end.

Here is the documented set of capabilities the application provides for bridge inspection:

CapabilityWhat it does
NBI element inspectionInspect per the AASHTO element-based methodology
Condition ratings0–9 NBI condition ratings for deck, superstructure, substructure
Element condition statesTrack quantity in each condition state per element
Inspection schedulingAutomated scheduling against the FHWA cycle
Inspection report generationGenerate FHWA-compliant inspection reports
NBI data exportExport data in NBI format for federal reporting
Load rating trackingRecord and track bridge load ratings
Scour assessmentTrack scour-critical bridges and countermeasures
💡 Key insight: Read that table as a program, not a feature list. Scheduling puts the inspection on the calendar; element inspection and condition states capture the truth; component ratings summarize it for the feds; load rating and scour track the two conditions most likely to close a bridge; and NBI export closes the loop to Washington. Miss any one and you do not have a compliant program — you have a spreadsheet with extra steps.

🎚️ Two Layers of One Inspection

The most common point of confusion — even among people who run bridge programs — is the relationship between the 0–9 NBI component ratings and the AASHTO element condition states. They are not competing systems; they are two layers of the same inspection.

Layer 1 — the AASHTO element condition states (the detail)

This is the engineering-grade record. Each structural element — deck, girder, bearing, joint, abutment — has a defined set of condition states, conventionally four:

StateConventional labelMeaning
1GoodSound; no or minor deterioration
2FairMinor deterioration; no strength impact
3PoorAdvanced deterioration; may affect strength/serviceability
4SevereWarrants a structural review; strength/serviceability affected

The inspector does not pick one state for the whole element. They record how much of the element's total quantity sits in each state (the next section). This is the detailed, defensible record of the structure's actual condition.

Layer 2 — the 0–9 NBI component ratings (the summary)

For the federal National Bridge Inventory, each major component — deck, superstructure, substructure — carries a single 0–9 condition rating, where 9 is excellent and 0 is failed/closed. This is the number that appears in the federal database and drives the Good/Fair/Poor bridge-condition classification used for federal performance reporting. (The legacy Sufficiency Rating and Structurally Deficient/Functionally Obsolete status items were discontinued with the SNBI.)

The 0–9 rating is a summary that reflects the element picture beneath it. Civil Infrastructure carries both layers so the inspector records element condition states and the component ratings are captured for the federal submission — the detail and the summary side by side, not one instead of the other.

💡 Key insight: If you only carry the 0–9 numbers, you have a federal report and no engineering record — you cannot tell whether a "6" is a uniformly fair deck or a mostly-good deck with one severe patch, and those demand different work. If you only carry element states, you have engineering detail and nothing to submit. The application's job is to carry both, which is exactly why Part 1 insisted the element be a real, addressable thing.

📏 Condition-State Quantity Tracking

This is the mechanic that makes element inspection meaningful, so it deserves its own section.

Instead of assigning one condition to an element, the inspector distributes the element's total quantity across the condition states. Consider a reinforced-concrete deck with a total area of 12,400 square feet. A real inspection might record:

Condition stateQuantityShare
1 — Good9,300 sq ft75%
2 — Fair2,480 sq ft20%
3 — Poor500 sq ft4%
4 — Severe120 sq ft1%
Total12,400 sq ft100%

Three things fall out of this immediately:

  1. The distribution is the record. "12,400 sq ft: 75/20/4/1" tells a bridge engineer far more than "deck: Fair." It says most of the deck is sound but there is a small, worsening area demanding attention.
  2. Deficiencies are quantity-based. The 500 sq ft in Poor and 120 sq ft in Severe are the seed of a deficiency (Part 3) and a quantity-based cost estimate — you can price 620 sq ft of repair.
  3. It ties to the federal number. The distribution is what supports the 0–9 deck component rating and what the element-level federal data expects.

The application tracks quantity in each condition state per element, which is precisely this mechanic. Over successive inspections, the quantity migrating from Good toward Severe is your deterioration signal — the raw material for condition trending and for Health scoring in Part 3.

🗓️ Scheduling the Inspection Cycle

An inspection you forget to do is a compliance finding, so scheduling is not clerical — it is the backbone of the program.

The standard cycle

Under the NBIS, routine bridge inspections are performed on a defined maximum interval — under the 2022 NBIS (23 CFR 650.311) Method 1 regular interval, 24 months — with extended intervals up to 48 months for bridges meeting all the qualifying criteria (up to 72 months under the more rigorous Method 2 risk assessment), and reduced intervals of no more than 12 months where any deck, superstructure, or substructure rating is 3 or less. Civil Infrastructure provides automated scheduling against the FHWA cycle, so inspections recur without someone maintaining a manual calendar, and overdue structures surface rather than slip.

This rides the Maximo scheduling machinery you already know from PMs: a recurring generation, a due date, a lead time to plan the inspection work, and visibility of what is coming due and what is late.

Special cycles

Not every inspection is the routine 24-month one. The program includes inspection types that carry their own requirements and intervals:

Inspection typeWhy it differs
RoutineStandard maximum-interval condition inspection
Fracture-critical (NSTM)Nonredundant steel tension members — the 2022 NBIS term for fracture-critical members — require hands-on inspection on their own interval (24 months regular under Method 1)
UnderwaterSubstructure elements below the waterline require diver or specialized inspection on their own interval (60 months regular under Method 1)
Damage / specialTriggered by an event (impact, flood, overload) outside the cycle
In-depthA closer look prompted by findings, beyond routine scope

The point for configuration is that a single structure can carry multiple, overlapping cycles — a fracture-critical steel bridge over a river needs routine, fracture-critical, and underwater schedules. Model them as distinct recurring schedules against the structure so each type comes due on its own clock.

💡 Key insight: The scheduling failure that bites agencies is treating every bridge as "inspect every 24 months." The fracture-critical and underwater intervals are separate obligations, and an inspector arriving to do a routine inspection does not discharge the fracture-critical requirement. Configure the cycles as independent schedules per structure, and let overdue visibility do the nagging.

⚖️ Load Rating and Scour — the Two That Close Bridges

Two conditions matter enough to their own tracking because they are the ones most likely to restrict or close a bridge.

Load rating

A bridge's load rating is the analytic capacity that governs posting and permitting — how much load the structure can safely carry. It changes as the structure deteriorates or is rehabilitated, and it drives weight postings and overweight-permit decisions. Civil Infrastructure records and tracks bridge load ratings, keeping the current rating with the structure so posting decisions and permit reviews reference a live number rather than a filed-away calculation.

Scour-critical status

Scour — the erosion of streambed material around piers and abutments during high flows — is a leading cause of bridge failure over water. Bridges are evaluated for scour vulnerability, and scour-critical bridges require monitoring and countermeasures (riprap, monitoring plans, flood-action plans). The application tracks scour-critical bridges and their countermeasures, so a flood event maps to a known set of structures and a known response, not a scramble.

Together, load rating and scour are the two conditions where "the record is current" is not paperwork — it is the difference between an informed posting/closure decision and a dangerous one.

📤 NBI-Format Export for the Federal Submission

The inspection program exists partly to feed the National Bridge Inventory, and the submission has a defined format. That format changed: the Specifications for the National Bridge Inventory (SNBI) supersede the 1995 Coding Guide, FHWA took its last Coding Guide submittal in March 2025 and its first SNBI submittal in March 2026, and 100% populated, verified SNBI data is due by March 2028. Confirm with IBM that your Civil Infrastructure release produces SNBI-format output before relying on it for a federal submittal. Civil Infrastructure exports data in NBI format for federal reporting — the component ratings, the inventory attributes, and the element data — so the annual submission is generated from the system of record rather than re-keyed into a separate federal tool.

This is where all the earlier discipline pays off. Because elements are real records, condition is captured as state quantities, and component ratings are carried alongside, the export has genuine data to enumerate. An agency that shortcut the model — one asset, one condition — has nothing structured to export and ends up hand-building the submission, which is both error-prone and exactly the kind of gap a federal review finds.

💡 Key insight: Validate the NBI export on your pilot set before you scale (this was the Part 1 practical note, and here is why it matters most). The export is the acid test of your element and condition-state modeling. If the export is clean and matches a known-good submission, your model is right. If it is blended or empty, you have a modeling defect to fix while it is still ten bridges, not five thousand.

🔧 Worked Example: Inspecting Bridge 04512

Take the two-span steel-girder bridge you modeled in Part 1 — Bridge 04512 — through a full routine inspection.

Step 1 — The inspection comes due. The 24-month schedule generates the inspection with a due date and a lead time. The bridge program manager sees it on the upcoming-inspections view alongside the fracture-critical and underwater schedules if they apply.

Step 2 — The inspector records element condition states. In the field, the inspector distributes each element's total across the states. The deck comes in at 9,300 / 2,480 / 500 / 120 square feet (Good/Fair/Poor/Severe) as above. The steel girders are mostly Good with a section of active corrosion recorded in Poor. The bearings: six Good, two Fair. The expansion joints: both Fair with leakage. The concrete substructure: mostly Good, with spalling at the pier recorded in Poor.

Step 3 — The component ratings are captured. From that element picture, the inspector records the 0–9 component ratings for the federal record — say deck 6, superstructure 6, substructure 6. These are the numbers that will hit the NBI.

Step 4 — Load rating and scour are reviewed. The current load rating is confirmed (no change this cycle). Scour status is reviewed; the bridge is over a stream, scour-critical, and its countermeasure (riprap) is confirmed in place — recorded against the structure.

Step 5 — Deficiencies are generated. The 500 sq ft of Poor and 120 sq ft of Severe deck, the girder corrosion, and the pier spalling become deficiencies (Part 3), each attached to its element and carrying a quantity. These are what will drive work orders.

Step 6 — The report and the export. The application generates the FHWA-compliant inspection report for the file, and the structure's data flows into the NBI-format export for the annual federal submission.

At the end, Bridge 04512 has a complete, defensible inspection record: element condition-state quantities, component ratings, current load rating, confirmed scour countermeasure, a set of element-attached deficiencies, a report, and federal-ready data — all traceable, all in one system.

⚠️ Edge Cases and Gotchas

Multiple overlapping cycles on one structure. As noted, fracture-critical and underwater are separate obligations. The gotcha is a structure that has a routine schedule but is missing its fracture-critical schedule — it will look "on track" while a required inspection type goes undone.

Element quantity reconciliation after rehab. When an element is partially replaced, its total quantity and the condition-state distribution both reset for the replaced portion. Failing to update the total after a rehab leaves the deterioration math wrong for years.

Component rating versus element detail disagreement. If the 0–9 component rating and the element condition states tell different stories (a "7" deck with 15% in Poor), that is a QA flag — usually a data-entry error in one layer. Reconcile before the submission, not after.

Agency-defined elements in the export. Custom elements a state defines must map correctly into the federal element data or the export will drop or mis-code them. Test custom elements explicitly in the export validation.

🩺 Troubleshooting the Inspection Program

  • If an inspection is overdue but nobody was warned, it means the schedule was not configured or the lead time was too short, so verify the recurring schedule and set a lead time that gives the team planning room.
  • If a fracture-critical bridge shows only a routine inspection history, it means the fracture-critical schedule is missing, so add it as a distinct recurring schedule against the structure.
  • If deficiencies are not appearing from an inspection, it means findings are being recorded against the structure rather than element condition states, so confirm the inspection form binds findings to elements with quantities.
  • If the NBI export rejects or mis-codes a structure, it means an inventory attribute or element mapping is wrong, so validate the structure's attributes and element mapping against the NBI coding requirements.
  • If a load-rating or scour change is not reflected in postings, it means the record was updated in a side document rather than in Maximo, so enforce that the current rating and scour status live on the structure record.

📋 Practical Notes for Rollout

  • Configure the inspection forms with an inspection SME. The element sets, the condition-state criteria, and the component-rating mapping are inspection knowledge; a Maximo administrator alone will get them subtly wrong.
  • Set up all applicable cycles per structure — routine, and where relevant fracture-critical and underwater — as independent schedules from day one.
  • Adopt condition-state quantity capture as the standard, not a single element rating. It is more work in the field and it is the entire value of element inspection.
  • Validate the NBI export against a known-good submission on the pilot set before scaling.
  • Keep load rating and scour status on the structure record, not in adjacent files, so posting and flood decisions reference live data.

Key Takeaways

  • Civil Infrastructure provides FHWA-compliant bridge inspection — element-based inspection, 0–9 component ratings, condition-state tracking, scheduling, report generation, NBI export, load rating, and scour assessment.
  • The 0–9 component ratings and the AASHTO element condition states are two layers of one inspection — detailed element states beneath, a federal summary number on top — and the application carries both.
  • Condition-state quantity tracking distributes each element's total across states, which is what makes element inspection defensible, drives quantity-based deficiencies, and feeds the federal element data.
  • The standard cycle is a maximum 24-month interval, with fracture-critical and underwater inspections carried as separate, overlapping schedules per structure.
  • Load rating, scour-critical status, and NBI-format export are tracked and produced for the federal submission under 23 CFR 650 — and the export is the acid test that your model is correct.

References

Series Navigation

Previous:Part 1 — The Civil Infrastructure Asset Model
Next:Part 3 — Pavement, Tunnels & the Deficiency-to-Work-Order Loop

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