Funding & Compliance
TAMP Software and MAP-21 Compliance: How DOTs Build and Maintain Their Plan
Quick answer. TAMP software is the system a state DOT uses to build, update, and defend its Transportation Asset Management Plan — the risk-based plan that MAP-21 (§1106) requires for National Highway System pavement and bridges. To support MAP-21 compliance, the software has to manage the asset inventory and condition, forecast deterioration, run risk-based investment scenarios against performance targets, and produce a documented, defensible plan that FHWA can review and the DOT can maintain on a rolling cycle.
TAMP software and MAP-21 compliance: what the tool actually has to do
TAMP software is the application a transportation agency uses to develop and maintain its Transportation Asset Management Plan (TAMP) and to demonstrate MAP-21 compliance. A TAMP itself is the risk-based strategic document — required under the Moving Ahead for Progress in the 21st Century Act (MAP-21) — for managing the condition and performance of pavement and bridge assets on the National Highway System (NHS). FHWA codified the requirement in 23 CFR Part 515: every state DOT must develop, and keep current, a risk-based asset management plan for NHS pavements and bridges (FHWA Transportation Asset Management Plans).
The decision a DOT asset or pavement manager actually faces is not “what is a TAMP” — FHWA and AASHTO own that definition — but “what system do we run it in, and how do we keep it compliant and current without rebuilding it from scratch every cycle.” That is the question this guide answers. The stakes are real: the American Society of Civil Engineers estimates a roughly $373 billion 10-year investment gap for bridges alone (ASCE 2025 Report Card — Bridges), so the plan that allocates scarce NHS dollars has to be both defensible and maintainable.
TAMP software is the owner-side planning layer above a DOT’s systems of record — it turns live inventory and condition data into the risk-based plan MAP-21 requires.
What MAP-21 requires a TAMP to contain
MAP-21 compliance means a TAMP includes the elements FHWA prescribes in 23 CFR 515 — and TAMP software exists to assemble and maintain each of them from live data rather than a static report. Under the rule, the plan must address NHS pavement and bridge assets and document, at minimum:
- Asset inventory and condition of NHS pavements and bridges.
- Objectives and measures tied to the national performance targets for pavement and bridge condition.
- Performance gap identification — the difference between current and target condition.
- Lifecycle planning — managing assets across their lifecycle to minimize cost while achieving condition targets.
- Risk management analysis, including risks that can affect NHS condition and system performance.
- A financial plan and investment strategies that make progress toward targets and a state of good repair.
The last two are where most of the analytical work lives, and where spreadsheets fall short. Lifecycle planning and investment strategies require forecasting how condition changes over time under different funding levels — exactly the scenario budgeting a DOT runs to show FHWA that its strategy moves pavement and bridge condition toward targets.
Lifecycle planning and investment strategies are where most of the analytical work lives — and where spreadsheets fall short.
What to look for in TAMP software: a MAP-21 compliance checklist
Evaluating TAMP software for MAP-21 compliance comes down to whether the tool can produce each required element from current data and keep it current as conditions change. Use the table below as an evaluation rubric.
| MAP-21 / 23 CFR 515 element | What the software must do |
|---|---|
| Inventory & condition | Maintain NHS pavement and bridge inventory and condition; ingest from existing systems of record. |
| Performance gaps | Compare current condition to national targets and quantify the gap by asset class. |
| Lifecycle planning | Forecast deterioration and model treatment timing to minimize whole-life cost. |
| Risk management | Score and document risks (condition, financial, hazard) and how they are mitigated. |
| Investment strategies | Run funding-level scenarios and optimize the program toward targets and state of good repair. |
| Financial plan | Tie strategies to a 10-year financial plan and exportable, review-ready documentation. |
| Maintainability | Support rolling updates so the plan stays current between required revisions, not rebuilt each cycle. |
How DOTs maintain the TAMP: deterioration forecasting feeds the plan
Maintaining a TAMP means keeping its condition forecasts and investment strategies current as new inspection data arrives — and the quality of those forecasts is what makes lifecycle planning credible. A TAMP’s lifecycle and investment sections rest on deterioration models: how a pavement section or bridge component is expected to degrade, and therefore when a treatment is most cost-effective. Conventional models use straight-line or family-average condition curves; AI deterioration models fuse condition, age, traffic loading, environment, and failure history to forecast each asset individually, and can be validated against inspection records.
Better forecasts change the investment strategy, not just the paperwork: they identify the assets where a timely, lower-cost treatment prevents an expensive reconstruction, which is precisely the whole-life-cost minimization MAP-21’s lifecycle-planning element asks for. We compare the two approaches in detail in AI vs. traditional deterioration models, and the pavement-specific economics in the pavement management software guide.
- New inspection data arrives. Updated pavement and bridge condition flows in from the systems of record.
- Forecasts re-run. Deterioration models project each asset forward and flag where a timely treatment is most cost-effective.
- Investment strategies refresh. Funding-level scenarios re-optimize the program toward condition targets and state of good repair.
- The plan stays current. The TAMP is maintained on a rolling basis between required revisions — not rebuilt from scratch each cycle.
How the TAMP relates to the STIP, GASB 34, and the CIP
The TAMP is the risk-based strategy; other documents turn that strategy into programmed projects and financial reporting, and TAMP software should keep them reconciled. The TAMP’s investment strategies inform the Statewide Transportation Improvement Program (STIP) — the fiscally constrained, multi-year list of programmed projects — so the projects a DOT actually funds trace back to the plan’s risk-based logic. On the reporting side, GASB Statement 34’s modified approach lets agencies report eligible infrastructure assets by maintaining them at a disclosed condition level instead of depreciating them — which depends on exactly the condition data and asset-management system a TAMP already maintains (GASB Statement No. 34). For the reporting workflow specifically, see the GASB 34 reporting use case.
The TAMP is the strategy; its investment strategies inform the STIP’s programmed projects, and the same condition data feeds GASB 34 modified-approach reporting.
For a municipal owner, the analog of the TAMP’s investment strategy is the multi-year capital improvement plan; the difference between that plan and the appropriated capital budget works the same way at a DOT, where the STIP carries the programmed dollars.
National Highway System pavement and bridge assets a state DOT’s TAMP must cover.
Where InfraMind fits: the AI planning layer above your TAMP systems
InfraMind is AI capital-planning software that sits on top of the pavement, bridge, and GIS systems a DOT already runs and produces the risk-based, defensible analysis a MAP-21 TAMP requires — deterioration forecasting, risk scoring, funding-level scenarios, and investment-strategy optimization toward condition targets and a state of good repair. It is the owner-side planning and optimization layer, not a replacement for systems of record. DOT and pavement teams can see the full vertical approach on the capital planning for state DOTs page and the compliance-specific framing on the TAMP / MAP-21 use case.