Civil Infrastructure Compliance, Reporting & Rollout

🎯 Who this is for: Program managers preparing for a federal review or a bond audit, transit asset managers under FTA rules, and implementation leads who need the crosswalk that proves compliance and the checklist that gets a pilot to its first federal-format report.

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

🎯 Why This Part Exists

The four preceding parts built the capability: the asset model, the bridge inspection, the pavement and tunnel loop, the AI. This part answers the question that pays for all of it — how do I prove it to the people who hold me accountable?

For civil infrastructure, accountability is unusually concrete. A state DOT answers to the FHWA for its bridge program. A transit agency answers to the FTA for State of Good Repair. Every public agency answers to auditors under GASB 34 for how it values and reports infrastructure. The value of Civil Infrastructure is not the software — it is that the records it produces satisfy those obligations. So the finale is a crosswalk you can hand a reviewer, a catalog of the reports the application produces, and a rollout plan to get there.

💡 Key insight: The single most useful artifact from this whole series is the crosswalk in the next section. When a federal reviewer or an analyst asks "does Maximo cover our compliance obligations," you do not want to answer with adjectives. You want to walk a table: this regulation → this capability → this record. A table survives an audit; enthusiasm does not.

📋 The Regulatory Crosswalk

Here is the capability-to-regulation map. Each row is a framework, what it requires, and the Civil Infrastructure capability that produces the record.

StandardWhat it governsCivil Infrastructure capability that answers it
FHWA NBISNational Bridge Inspection Standards — the bridge inspection program itselfElement-based inspection, 0–9 component ratings, scheduling against the cycle, inspection reports
AASHTO Manual for Bridge Element InspectionThe element-based inspection methodologyElement condition states, condition-state quantity tracking
23 CFR 650Federal regulation for bridge inspection frequency and reportingAutomated scheduling, NBI-format data export for federal submission
NTISNational Tunnel Inspection StandardsElement-based tunnel inspection, structural/functional element and fire/life-safety tracking
MAP-21 / FAST ActFederal transportation legislation — performance-based planningCondition and performance data (bridge condition, pavement PCI/IRI) supporting performance measures
GASB 34Government accounting for infrastructure — valuation and depreciationAsset inventory, condition data supporting the modified approach to infrastructure reporting

Read the crosswalk the way an auditor does — from the regulation inward. It does not matter that Maximo has a nice inspection screen; it matters that when 23 CFR 650 asks "show me your inspection frequency and your federal submission," you can point to the scheduling and the NBI export, and when GASB 34 asks "how do you support the modified approach," you can point to the inventory and the condition data.

💡 Key insight: The honest boundary runs through every row: Maximo supplies the record; it does not make the compliance determination. The application produces the inspection, the rating, the export, the condition history. Whether the program is compliant — whether inspections happened on time, by qualified inspectors, to standard — is a judgment the program owner makes and defends. Claiming Maximo "ensures compliance" oversteps; claiming it "produces the records compliance requires" is exactly right, and it is the claim that survives scrutiny.

🏦 GASB 34 and the Modified Approach

One row of the crosswalk deserves its own section because it touches the finance office, not the inspection team — and because it is where an agency's condition program either saves money or does not.

GASB Statement No. 34 governs how a government reports its infrastructure assets in its financial statements. For infrastructure, it offers a choice that most other assets do not, and that choice hinges on condition data.

Depreciation versus the modified approach

Under the default, an agency depreciates its infrastructure — spreading the asset's cost over its useful life as an accounting expense, the same as a vehicle or a building. That is simple to administer and says nothing about whether the bridge is actually in good shape.

The alternative is the modified approach. An agency may elect not to depreciate an infrastructure network if it can demonstrate two things: that it manages the assets using an asset management system with an up-to-date inventory and periodic condition assessment, and that it is preserving the assets at or above a condition level it has established and disclosed. In exchange, maintenance and preservation spending is expensed as incurred rather than depreciation being booked — and, more importantly, the agency reports condition rather than book value, which is a far more honest picture of infrastructure health.

Where Civil Infrastructure fits

The modified approach is exactly the kind of obligation Civil Infrastructure supports without doing anything special: it maintains the inventory (the asset model from Part 1), it runs the periodic condition assessment (the inspections from Parts 2 and 3), and it produces the condition data that demonstrates the network is being held at the disclosed level. The application supplies the records the modified approach requires; the election itself and the disclosed condition target are decisions the agency and its auditors own.

💡 Key insight: The modified approach is where the inspection program and the balance sheet meet. An agency that captures element condition, PCI, and deficiency history is not only running a maintenance program — it is generating the evidence that lets its finance office elect the modified approach and report condition instead of depreciation. That is a rare case where the same data serves the bridge engineer and the CFO, and it is worth naming when you scope an implementation for a public agency.

🚆 Transit: State of Good Repair and TAM

Transit agencies are a distinct slice of the audience with their own federal regime, and Civil Infrastructure serves it with the same machinery.

A transit agency owns rail bridges, tunnels, stations, and guideways, and it answers to the FTA under two related obligations:

  • State of Good Repair (SGR) — the FTA's requirement that transit assets be maintained in, or brought to, a state of good repair, measured by asset condition.
  • Transit Asset Management (TAM) — the requirement to maintain a TAM plan, set condition targets, and report progress against them.

Civil Infrastructure supports the transit use case directly:

  • Manage rail bridges, tunnels, stations, and guideways using the same element-based inspection and condition model as highway structures.
  • Track FTA State of Good Repair by carrying the condition data that SGR is measured against.
  • Generate Transit Asset Management (TAM) plan data — the condition and inventory data a TAM plan reports.
  • Prioritize capital investment based on condition, using the deficiency loop and Health scoring from Part 3 to put limited capital where condition demands it.

The elegance is that transit is not a separate application — it is the same element-and-deficiency machinery pointed at rail structures, with the reporting shaped to FTA rather than FHWA. An agency that runs both highway and transit assets runs them in one system with one model.

📊 Reporting the Application Produces

Compliance is proven through reports, so it is worth cataloging what the application generates. Everything here is produced from the system of record — the element inspections, condition states, and deficiencies — rather than re-keyed into separate tools.

Report / outputAudienceSourced from
FHWA-compliant inspection reportThe inspection file, FHWAElement inspection + component ratings
NBI-format data exportFederal National Bridge InventoryInventory attributes, ratings, element data
Deficiency reportManagement, regulatorsDeficiency tracking (severity/safety-ranked)
Condition / performance dataMAP-21 performance measuresBridge condition, pavement PCI/IRI
TAM plan dataFTA (transit)Transit asset inventory + condition
Load rating / scour statusPosting and flood-response decisionsStructure-level tracking

The recurring theme — and the reason Part 1 insisted on the element model and Part 2 insisted on validating the export — is that good reporting is a downstream consequence of a good model. If the elements, condition states, and deficiencies are captured correctly, the reports fall out of the system. If the model was shortcut, the reports have to be hand-built, which is slow, error-prone, and exactly what a federal review finds.

💳 Deployment and Licensing, Consolidated

Pulling the practical prerequisites into one place for the roadmap conversation.

Deployment

Civil Infrastructure runs on the standard MAS foundation — Manage on Red Hat OpenShift — plus the module itself, plus (for AI inspection) GPU compute and, for the Large Vision Models, watsonx.ai availability. The dependency chain is:

  • Manage on OpenShift — the baseline for everything.
  • Civil Infrastructure module — deploys on the cluster (4–8 hours).
  • Maximo Health — for condition-based prioritization (Part 3).
  • Visual Inspection + GPU — for AI-augmented inspection (Part 4); CNN anywhere with GPUs, LVM gated by watsonx.ai/FedRAMP.

Licensing

Access is entitled through the shared MAS AppPoints pool. As established in Part 1, IBM's licensing documentation lists Civil Infrastructure users at the Premium or Limited tier plus a per-install allocation of 50 AppPoints, so the honest statement is: user access draws on the shared pool alongside the rest of Manage, the install allocation sits on top, and the exact entitlement for your user profile is an IBM quote. Because the pool also entitles Health, Monitor, and Visual Inspection, an agency using only bridge inspection is leaving value unused — the condition-based and AI-augmented capabilities are already within reach.

💡 Key insight: Sequence the deployment to value, not to the org chart. Manage and Civil Infrastructure first gets you the inspection program and the federal export — the compliance floor. Health next gets you condition-based prioritization across the portfolio. Visual Inspection with GPUs gets you AI-augmented inspection (CNN now, LVM on the watsonx.ai timeline). Each layer is usable on its own, so you can show compliance value before you have finished the AI story.

🔧 Worked Example: An FHWA Reviewer's Traversal

Make the crosswalk concrete by walking how a federal reviewer's question resolves — the traversal that turns an audit from a hunt into a route.

The reviewer asks: "Show me that Bridge 04512 is inspected on the required frequency, that the inspection follows the element methodology, and that your data reaches the National Bridge Inventory."

The traversal:

  1. Frequency (23 CFR 650). Open the structure's schedule: the 24-month routine cycle, plus the fracture-critical and underwater schedules if applicable, with the inspection history showing on-time completion. Regulation → scheduling capability → inspection history record.
  2. Methodology (AASHTO / FHWA NBIS). Open the latest inspection: element condition states with condition-state quantities for the deck, girders, bearings, and substructure, and the 0–9 component ratings. Regulation → element inspection capability → condition-state record.
  3. Federal submission (23 CFR 650). Show the NBI-format export carrying the structure's attributes, ratings, and element data. Regulation → NBI export capability → submission record.
  4. Supporting evidence (optional). If drones are in use, show the MVI visual evidence linked to the element records, with inspector adjudication. Capability → evidence record.

Every step is a straight line from a regulation to a capability to a record. The reviewer is not shown a demo; they are shown the file. That is what the whole series was building toward, and it is why the honest posture — records, not judgment — is also the strong one: a reviewer trusts a system that shows its records and lets the program own the compliance call.

⚠️ Edge Cases and Gotchas

Regulations evolve. Inspection intervals, element definitions, and performance measures change (the shift toward risk- and reliability-based inspection intervals is ongoing). Treat the crosswalk as living, and confirm current requirements against the source rather than a fixed table.

Mixed portfolios. An agency with highway bridges, transit structures, and pavement answers to FHWA, FTA, and its own accounting under GASB 34 at once. Keep the reporting mapped per obligation so a transit audit and an FHWA review each get the right slice.

"Compliance" language in proposals. The most common self-inflicted wound is a statement of work that promises the software "ensures compliance." It does not; it produces records. Fix the language before it is signed, or own an obligation the software cannot meet.

Export validation as an ongoing gate. The NBI export was validated at pilot (Part 2), but model changes, custom elements, and data migrations can break it later. Re-validate the export whenever the inspection model changes materially.

🩺 Troubleshooting Compliance and Reporting

  • If a report cannot be produced from the system, it means the underlying model (elements, condition states, deficiencies) is incomplete, so fix the model rather than hand-building the report.
  • If the NBI export is rejected, it means an inventory attribute or element mapping is non-conformant, so validate against the federal coding requirements (Part 2).
  • If TAM condition data looks wrong, it means transit assets are not modeled with the same element/condition discipline as highway structures, so confirm the transit assets carry real condition records.
  • If an audit becomes a hunt rather than a traversal, it means the capability-to-record links are unclear, so rehearse the crosswalk traversals before the review.
  • If licensing is a surprise, it means the AppPoints entitlement was assumed from a blog rather than an IBM quote, so confirm the entitlement with IBM for your user profile.

📋 The Rollout Checklist

A realistic Civil Infrastructure pilot mirrors the documented task set — roughly 60–112 hours, two to three weeks:

StepTaskTypical effort
1Assess applicability to your infrastructure portfolio4–8 hours
2Review the current bridge/tunnel inspection program and tools8–16 hours
3Deploy the Civil Infrastructure module (Manage + OpenShift in place)4–8 hours
4Configure the pilot bridge inventory (10–20 structures)8–16 hours
5Configure inspection forms for NBI compliance8–16 hours
6Conduct pilot inspections in the application16–24 hours
7Generate NBI-format reports and validate4–8 hours
8Evaluate the Visual Inspection integration for deck scanning8–16 hours

The shape of the effort tells the story: deploying the software is a few hours (step 3), and the real work is the program — the inventory, the inspection forms, the real inspections, and the export validation. Staff the pilot with an inspection SME, pick a representative structure set, and treat the clean NBI-format export as the definition of done.

💡 Key insight: Define "pilot success" as a validated federal-format export, not as "the module is installed." Installation proves nothing about your program; a clean NBI export proves your inventory, elements, condition states, and mapping are all correct together. Make that export the gate between pilot and scale, and you will catch modeling defects while they are ten bridges instead of five thousand.

Key Takeaways

  • The crosswalk is the deliverable — Civil Infrastructure maps to FHWA NBIS, AASHTO, 23 CFR 650, NTIS, MAP-21/FAST Act, and GASB 34, and the way to answer a reviewer is regulation → capability → record.
  • Transit is served by the same machinery — FTA State of Good Repair and Transit Asset Management plan data come from the same element inspection and deficiency loop, pointed at rail structures.
  • Reporting is a downstream consequence of a good model — FHWA reports, the NBI export, deficiency reports, and performance/TAM data are generated from the system of record, not re-keyed.
  • Maximo supplies the record; the program owner makes the compliance call — the honest posture is also the one that survives an audit.
  • A realistic pilot is 60–112 hours dominated by inventory and inspection-form configuration, and a validated federal-format export is the true definition of done.

References

Series Navigation

Previous:Part 4 — AI-Augmented Inspection: Visual Inspection & Large Vision Models
Next:You have completed the series — Maximo Civil Infrastructure on MAS 9.

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