Maximo Civil Infrastructure on MAS 9
🎯 Who this is for: Asset managers, bridge and pavement program managers, and IT leads at organizations that own public infrastructure — state and county DOTs, municipal public works, toll authorities, transit agencies, and federal infrastructure agencies. If you are trying to decide whether Maximo can run your bridge inspection program, your pavement management, and your federal reporting — and what you would have to configure to get there — this series is written for you.
Series: Part 0 of 5 — Maximo Civil Infrastructure on MAS 9 | Read time: 15 minutes
🌉 Why This Series Exists
Most Maximo material treats an asset as a pump, a motor, or a conveyor: a single record with a nameplate, a few meters, and a work-order history. That model is correct for the plant floor and useless for a bridge.
A bridge is not one asset. It is a structure made of elements — a deck, girders, bearings, expansion joints, a substructure — and each element is inspected and rated on its own scale, on a cycle the federal government mandates, by an inspector whose findings feed a national database. A road is a linear asset scored by condition index over its length. A tunnel carries fire and life-safety systems that a boiler never will. None of these fit the plant-floor asset model, and none of the standard Maximo tutorials tell you how to handle them.
Maximo Civil Infrastructure is IBM's answer to exactly this gap. It is a purpose-built application that ships inside MAS Manage for organizations that own transportation and public-works assets, and it adds the specific inspection, condition-assessment, and regulatory-compliance machinery those asset classes require. This series maps what it actually does — grounded in documented IBM capability and the federal frameworks it serves — across five parts, and it is honest about where a capability is a real application feature versus where it is a configuration pattern or a platform capability the application inherits.
💡 Key insight: The organizing principle of the whole series fits in one line: the inspection is the asset record. For a plant pump, the asset record is the nameplate and the work history. For a bridge, the authoritative record is the element-level inspection — the condition states, the ratings, the deficiencies. Everything Civil Infrastructure does is built to produce and defend that inspection record, because that record is what the FHWA, the state, and the bond auditor all come to see.
🧭 Where This Series Fits
This series is deliberately infrastructure-specific. It is not a general MAS 9 course, and it does not re-argue the platform upgrade case. There is a clear division of labor across TheMaximoGuys series so you never read the same thing twice:
| If you want… | Read… |
|---|---|
| The generic Maximo 7.6-versus-MAS platform delta (architecture, Carbon UI, OpenShift, AppPoints, MAS AI) | THINK-MAS series |
| Feature-by-feature MAS 9 capability walkthroughs (Work Orders on Role-Based Apps, Assistant, Health, Monitor, Predict) | MAS-FEATURES series |
| Core work management, PMs, job plans, and mobile execution | MAS MANAGE series |
| How Visual Inspection trains models, manages GPUs, and detects defects across any industry | MAS VISUAL INSPECTION series |
| How Maximo Health computes asset condition scores and drives condition-based maintenance | MAS HEALTH series |
| The civil-infrastructure solution: the asset model, bridge/road/tunnel inspection, deficiency-to-work-order, and the regulatory crosswalk | This series |
💡 Key insight: Visual Inspection and Health each have their own deep series because they are platform capabilities used by many industries. This series covers how Civil Infrastructure uses them for bridges and roads — the drone-to-deck-condition loop, the health-to-treatment loop — without re-teaching how they work internally. When a part references "the MVI model" or "the Health score," the mechanics live in those sibling series; the infrastructure application of them lives here.
📊 The Series at a Glance
| Part | Title | Focus Area | Read Time |
|---|---|---|---|
| 1 | Product Overview & the Civil Infrastructure Asset Model | What the application is, who it is for, and how bridges/roads/tunnels are modeled as element-based and linear assets; where it sits vs Manage, Health, and MVI; licensing and deployment posture | 16 min |
| 2 | NBI Bridge Inspection & AASHTO Element Condition | FHWA NBIS and 23 CFR 650; 0-9 component ratings; AASHTO element condition states; biennial scheduling; load rating; scour; NBI-format export — with a full worked inspection | 18 min |
| 3 | Pavement, Tunnels & the Deficiency-to-Work-Order Loop | Road condition (PCI, IRI, distress, treatment); tunnel inspection (NTIS, fire/life safety); deficiency tracking and prioritization; condition-based maintenance via Health | 17 min |
| 4 | AI-Augmented Inspection: Visual Inspection & Large Vision Models | Drone imagery through MVI; CNN vs Large Vision Models (9.1) for civil infrastructure; GPU and camera requirements; and the honest watsonx.ai/FedRAMP reality for government customers | 16 min |
| 5 | Compliance, Reporting & Rollout | The full regulatory crosswalk (23 CFR 650, NTIS, MAP-21/FAST Act, GASB 34, FTA State of Good Repair); TAM plans; deployment prerequisites; and a rollout checklist | 16 min |
🔑 What Makes Civil Infrastructure Different
Before the part-by-part guide, three ideas run through every part. Internalize them and the series reads as one argument rather than five articles.
The element is the unit of work, not the asset. In plant EAM you write a work order against an asset. In bridge management you inspect and rate elements — and the deficiency that triggers a work order is attached to an element in a condition state, not to the bridge as a whole. Civil Infrastructure exists to carry that element-level granularity through inspection, condition, deficiency, and work order without losing the thread.
Maximo supplies the record; the regulation defines the scale. The 0-9 NBI condition scale, the AASHTO element condition states, the two-year inspection cycle, the NBI export format — these are federal definitions. Civil Infrastructure implements them faithfully and produces the records, but it does not invent the scales and it does not make the compliance judgment. That division is exactly what a federal reviewer expects.
Government is the primary audience, so the deployment reality matters. The single largest customer base for this application is public agencies, many of them under FedRAMP. That makes the watsonx.ai dependency of the Large Vision Models a real planning constraint, not a footnote — and it is why Part 4 treats it head-on rather than pretending every AI feature is available everywhere.
💡 Key insight: If you remember only one thing from this index, make it this triad: element-not-asset, record-not-judgment, government-deployment-is-real. Every part is an application of one of the three. They are also, not coincidentally, the three places a vendor demo most often oversells — flattening elements into assets, implying compliance automation, and assuming the AI features light up on any cluster.
🏗️ The Asset Classes This Series Covers
Civil Infrastructure is not a single-asset tool; it spans a portfolio of structure types, each with its own inspection regime. The series maps them so you know which part answers which asset owner's question.
| Asset class | What it is | Governing standard | Covered in |
|---|---|---|---|
| Bridges | Structures inspected element-by-element, rated 0-9 by component | FHWA NBIS / 23 CFR 650 / AASHTO | Parts 1, 2 |
| Roads / pavement | Linear assets scored by condition index over length | Agency pavement-management practice; MAP-21 performance measures | Part 3 |
| Tunnels | Structures with structural and fire/life-safety elements | NTIS (National Tunnel Inspection Standards) | Part 3 |
| Culverts, retaining walls, signs, signals | Ancillary structures inspected alongside the network | Agency and state inspection programs | Parts 1, 3 |
| Rail bridges, stations, guideways | Transit fixed-guideway structures | FTA State of Good Repair / Transit Asset Management | Parts 3, 5 |
These classes are not an abstraction. They are why a bridge program manager, a pavement engineer, and a transit asset manager each pick up this series at a different part — and why the crosswalk in Part 5 ties every class to the regulation it answers to in one table.
🧩 Part-by-Part Guide
Part 1: Product Overview & the Civil Infrastructure Asset Model
[Read Part 1 — Product Overview & the Civil Infrastructure Asset Model](/blog/mas-civil-infrastructure-product-asset-model) · 16 minutes
Before you inspect anything, you have to model it. This part explains what Civil Infrastructure is, who it is for, and — most importantly — how it represents a bridge, a road, and a tunnel as assets that the standard Manage data model was never designed to hold.
You will learn: why a civil asset is element-based rather than single-record; how the AASHTO element taxonomy maps onto a Maximo asset hierarchy (walked through with a real bridge); how the application relates to core Manage, Maximo Health, and Visual Inspection; the licensing posture (shared AppPoints pool, industry-solution access) and what is honestly public about it; and the deployment prerequisites (Manage deployed, OpenShift access) before you configure your first structure.
Part 2: NBI Bridge Inspection & AASHTO Element Condition
[Read Part 2 — NBI Bridge Inspection & AASHTO Element Condition](/blog/mas-civil-infrastructure-bridge-inspection-nbi) · 18 minutes
This is the heart of the application. Federal bridge inspection is a precise, prescriptive program, and this part walks the whole cycle — from scheduling through element rating to federal export.
You will learn: how the 0-9 NBI condition ratings for deck, superstructure, and substructure coexist with the AASHTO element condition states; how condition-state quantity tracking works (and why it matters more than a single number); how the two-year inspection cycle is scheduled and how special cycles — fracture-critical, underwater — differ; how load rating and scour-critical status are tracked; and how NBI-format export supports the federal submission — all through a fully worked bridge inspection with sample values.
Part 3: Pavement, Tunnels & the Deficiency-to-Work-Order Loop
[Read Part 3 — Pavement, Tunnels & the Deficiency-to-Work-Order Loop](/blog/mas-civil-infrastructure-pavement-tunnel-deficiency) · 17 minutes
Bridges are the marquee asset, but a DOT owns far more road than bridge, and a transit agency owns tunnels. This part covers the rest of the portfolio and the loop that turns any inspection finding into maintenance.
You will learn: how pavement condition is captured (PCI scoring, distress identification, IRI ride quality) and turned into a treatment recommendation; how tunnel inspection follows NTIS with its fire/life-safety element tracking; how deficiency tracking prioritizes findings by severity and safety impact and links them to work orders; and how condition-based maintenance triggers work when a rating drops below threshold, with Maximo Health supplying the condition score — walked through a pavement-section example end to end.
Part 4: AI-Augmented Inspection: Visual Inspection & Large Vision Models
[Read Part 4 — AI-Augmented Inspection: Visual Inspection & Large Vision Models](/blog/mas-civil-infrastructure-ai-inspection-lvm) · 16 minutes
This is where the modern story and the honest caveat meet. Drones and AI can transform bridge-deck inspection — but only within the deployment reality every government customer lives in.
You will learn: how Visual Inspection analyzes drone-captured imagery to detect defects on decks, piers, and beams; the difference between classic CNN models and the Large Vision Models introduced in MAS 9.1 that are trained for civil infrastructure and need minimal training data; the GPU, camera, and training-data requirements; how visual evidence links back to element-level inspection records; and the watsonx.ai/FedRAMP reality that determines whether the LVM capability is even available to a given agency — walked through a drone-to-deck-condition example.
Part 5: Compliance, Reporting & Rollout
[Read Part 5 — Compliance, Reporting & Rollout](/blog/mas-civil-infrastructure-compliance-reporting-rollout) · 16 minutes (Series Finale)
The whole point of the application is to satisfy a regulator and a bond auditor. This part is the crosswalk you hand them, plus the plan to get there.
You will learn: the full capability-to-regulation crosswalk across FHWA NBIS, AASHTO, 23 CFR 650, NTIS, MAP-21/FAST Act, and GASB 34; how transit's FTA State of Good Repair and Transit Asset Management (TAM) plan data are supported; what reporting the application produces for federal submission and management; the deployment prerequisites and AppPoints posture in one place; and a rollout checklist that mirrors a real pilot from portfolio assessment to first federal-format report.
🧭 Recommended Reading Paths
Bridge Program Manager
"I own the NBI program and the federal submission."
Read Part 2 → Part 4 → Part 5. Start with the element-based inspection cycle, then how drones and MVI augment it, then the crosswalk that proves compliance to the FHWA.
Pavement / Network Manager
"I own the roads, not the bridges."
Read Part 3 → Part 1 → Part 5. Start with PCI, IRI, and the treatment loop, then the asset model that holds a linear network, then the MAP-21 performance-measure reporting.
Transit Asset Manager
"I own rail structures under FTA rules."
Read Part 1 → Part 3 → Part 5. Start with the asset model, then tunnels and the deficiency loop, then State of Good Repair and TAM plan data.
IT / Deployment Lead
"I own the platform, the licenses, and the FedRAMP posture."
Read Part 1 → Part 4 → Part 5. Start with deployment prerequisites and licensing, then the watsonx.ai/GPU reality for the AI features, then the rollout checklist.
💡 Key Themes Across the Series
The inspection is the asset record. For civil infrastructure, the authoritative record is the element-level inspection — condition states, ratings, deficiencies — not the nameplate. Every capability exists to produce and defend that record.
The element is the unit of work. Deficiencies attach to elements in condition states; work orders trace to deficiencies. Civil Infrastructure carries element-level granularity all the way through so nothing is lost between an inspector's finding and a crew's work order.
Maximo supplies the record; the regulation defines the scale. The 0-9 scale, the AASHTO states, the two-year cycle, and the NBI export are federal definitions faithfully implemented. Maximo produces the records; the compliance judgment stays with the program.
Government deployment is a real constraint. The primary audience is public agencies, many under FedRAMP. The Large Vision Models depend on watsonx.ai, whose FedRAMP authorization covers only the AWS GovCloud SaaS — so confirm it is available in your boundary rather than assuming it on day one.
🧰 How to Use This Series
- Scoping a DOT or public-works implementation? Use Part 1 for the asset model, Part 2 for the bridge program, and Part 3 for pavement and tunnels — then Part 5 to name exactly which reports satisfy which regulation. Saying "the element condition states feed the NBI export under 23 CFR 650" is the difference between a credible statement of work and a hand-wave.
- Evaluating the AI story? Part 4 is your reality check. It separates what works anywhere (CNN defect detection with GPUs) from what is gated behind watsonx.ai (the civil-infrastructure Large Vision Models), so you do not promise a federal customer a capability their FedRAMP boundary cannot yet run.
- Preparing for a federal review or a bond audit? Rehearse the Part 5 crosswalk — capability to record to regulation — so a reviewer's question becomes a route, not a hunt.
- Setting a roadmap? Part 1 (asset model, licensing, prerequisites) and Part 4 (GPU and watsonx.ai timeline) are your two anchors for sequencing what to deploy and when.
References
- Maximo Application Suite — Manage add-ons and industry solutions (IBM Documentation)
- IBM Maximo Application Suite overview (IBM Documentation)
- FHWA National Bridge Inspection Standards (23 CFR 650, Subpart C)
- AASHTO Manual for Bridge Element Inspection
- FTA Transit Asset Management (TAM) final rule
Start the Series
Begin with [Part 1 — Product Overview & the Civil Infrastructure Asset Model](/blog/mas-civil-infrastructure-product-asset-model), or jump to the part that matches your role using the reading paths above.
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
Posam Lakshminarayana
Venkat Achanta
Surendra Katta