Discussion frame

A practical discussion about the American Mobility Grid.

Seventy years after the Interstate Highway System helped define American mobility, the country has an opportunity to reinvest in that backbone for the next era. Corridor activity is accelerating, but the question is whether those efforts can become coherent enough to add up to a national operating capability.

The stakes Safety·Reliability·Resilience·Economic performance·National readiness

This is not a technology deployment agenda. It is a market-formation and operating-model agenda: how to make state-led corridor efforts coherent enough for public agencies, industry, operators, and capital to build toward the same system.

Capability-led, not vendor-led

Platform-neutral · outcome-focused

State-led, federally supported

Local and regional priorities · operationally grounded

A way to make efforts add up

Shared operating model · scalable market · investable

Discussion The goal is to pressure-test the organizing logic: where to start, what to build, how to engage industry, and how to make corridor efforts scalable.

Factor Advisory Notes

This is a discussion frame, not a formal presentation.

The question is whether there is a practical way to let corridor efforts stay state-led and grounded in real operational needs, while still adding up to something more coherent nationally.

There is a lot of activity starting to move. That is encouraging. But without a shared organizing logic, those efforts can easily remain separate projects, each useful on its own, but not necessarily building toward a national capability.

The frame to test is this: this is not a technology deployment agenda. It is a market-formation and operating-model agenda.

How do we create enough coherence around corridors, digital infrastructure, use cases, governance, and investment signals that public agencies, industry, operators, and capital can build toward the same system?

The stakes are safety, reliability, resilience, economic performance, and national readiness.

OST-R and research to action

OST-R can play a catalytic role by helping the Department translate years of research into corridor operating models, data frameworks, validation pathways, and implementation signals that the rest of USDOT and state partners can use now. Research can continue, but much of the foundation is ready to be operationalized.

Questions to pressure-test

This framing is meant to be tested, not assumed. A few practical questions are worth holding in view from the start.

Is this a useful way to frame the opportunity?
Where does USDOT have the clearest role?
What role should other parts of the federal government play, given the connections to energy, communications, emergency response, resilience, commerce, logistics, and national readiness?
What would make this more operationally useful to states?
What would make it more compelling to industry?
What role could industry groups and associations play, such as ITSA, 5GAA, AASHTO, IBTTA, and others?
Where does this risk becoming too broad or too abstract?

Interdependence

Transportation is part of a larger operating environment.

Transportation depends on freight, emergency response, communications, energy, weather, ports, and public agencies. These systems are deeply interdependent, but their operating models have not yet caught up.

Current state Limited visibilitySlow coordinationSiloed operations

With digital infrastructure Shared visibilityCoordinated responseOperational readiness

A digital infrastructure layer turns interdependence into an operating capability.

Factor Advisory Notes

The starting point is that transportation is no longer a standalone system.

Transportation depends on freight, emergency response, communications, energy, weather, ports, airports, public agencies, and private operators. These systems are deeply interdependent, but they are still too often operated separately.

When something happens on a corridor, it is rarely just a traffic issue. It can affect freight movement, emergency response, port access, energy logistics, workforce movement, and public safety.

The issue is not that no one is working on these problems. There is a lot of work underway. The issue is that interdependent systems are still operated in silos.

The shift is this: not just connected transportation. Connected infrastructure.

A digital infrastructure layer makes those relationships visible, coordinated, and measurable. It gives agencies and operators a way to see across systems, coordinate across jurisdictions, and measure outcomes in a more operational way.

That is the context for this discussion.

From activity to capability

Momentum needs a vision.

The activity is real, but it will not become a national capability on its own. A shared vision and repeatable execution model are what keep corridor efforts from remaining separate projects.

Factor Advisory Notes

There is real momentum right now.

There are corridor discussions. There are digital infrastructure discussions. There are AI and data initiatives. There are safety and freight efforts. There are state-led pilots and regional coalitions.

But the motion does not yet add up.

Without a shared vision and a repeatable execution model, each effort can stay its own project. That creates a risk that we get a set of useful but disconnected pilots, rather than a scalable national capability.

A shared vision is a way to organize that activity.

It is not meant to replace state priorities. It is not meant to turn this into a federal takeover. It is a way to organize infrastructure, operations, institutions, funding, and private investment around a national mobility system.

The point is to create enough of a shared digital operating model that separate efforts can reinforce each other.

The first network

Backbones turn networks into systems.

Networks become scalable when they have an organizing backbone: a shared structure that carries demand, creates connection points, and gives local systems something to build around.

Capacity

carries demand

Connection

creates access points

Expansion

lets local systems and use cases grow around it

Every durable national system has a backbone

Interstate highways

A designated national network that state and local roads connect into.

Freight rail

Class I trunk lines, with branch and short lines feeding in.

The electric grid

High-voltage transmission first; local distribution grows off it.

Communications

Long-haul backbones that regional and local networks connect into.

Factor Advisory Notes

One reason corridors matter is that networks become scalable when they have a backbone.

A backbone creates structure. It carries demand. It creates connection points. It gives local systems something to build around.

That does not mean the backbone is the whole system. It means the backbone is what makes the system buildable and expandable.

That is the role of strategic corridors here. The first corridors are not the whole grid. They are the organizing backbone that lets a grid become buildable, expandable, and useful.

The Interstate System gave the country a physical backbone. The next era requires a digital and operating backbone that helps strategic corridors work as a system.

The question is not whether every road, every city, every asset, or every operating environment gets included on day one. The question is where to start in a way that creates real operational value and gives the broader ecosystem something coherent to build around.

USDOT action

Designate the first strategic corridors.

A national mobility system does not start everywhere. It starts with backbone corridors where systems meet, operational needs are visible, and digital infrastructure can be organized around measurable outcomes.

What designation sets in motion

Designating corridors is not the end state. It is the policy mechanism that creates the first defined places to build, measure, and scale the digital infrastructure layer.

Designate the digital backbone

Select strategic corridorsAnchor operating outcomesEstablish the first places to build

Define the digital layer

Corridor visibilityInteroperable data exchangeShared performance measuresCross-jurisdiction operations

Create the market signal

Repeatable delivery modelPublic / private investment focusScalable digital infrastructure market

Factor Advisory Notes

This is where USDOT has an important organizing role.

A national mobility system does not start everywhere. It starts with backbone corridors where systems meet, operational needs are visible, and digital infrastructure can be organized around measurable outcomes.

Designation matters because it creates defined places to build, measure, and scale.

It does not mean USDOT owns the corridors. It does not mean every corridor has the same use case. It does not mean the federal government dictates the operating model.

It means there are named, visible, strategically important corridors where the country can begin to organize the digital infrastructure layer.

Designation does three things. First, it designates the backbone and creates a clear starting portfolio. Second, it defines where the digital layer can be built and tested in a serious way. Third, it creates a market signal.

That market signal tells agencies, industry, OEMs, logistics providers, technology companies, integrators, and investors that these are not isolated pilots. They are part of a larger national direction. Industry will engage differently if it can see a path from one corridor to many.

Open design questions

This frame defines the organizing logic, not the implementation. Turning it into action would require decisions on the federal mechanism for designation, funding alignment, governance, procurement pathways, and performance measures.

The first build

Build the digital infrastructure layer.

Strategic corridors become useful when they carry a digital and operating layer that makes conditions visible, connected, coordinated, and measurable.

Digital infrastructure is the shared operating layer that gives corridors real-time visibility, interoperable data exchange, coordinated response, and measurable performance across jurisdictions.

See the corridor

Real-time corridor visibility Work zones, incidents, weather, traffic, and freight movement Shared situational awareness

Connect the actors

DOTs, responders, freight, transit, and private operators Interoperable data exchange Common operating picture

Coordinate operations

Cross-jurisdiction incident response Work zone and event management Emergency and resilience coordination

Measure performance

Safety Reliability Response time Throughput Readiness for future use cases

Factor Advisory Notes

Once corridors are designated, the first practical build is the digital and operating layer.

Digital infrastructure should not be treated as a generic technology stack. It is a shared operating layer that gives corridors real-time visibility, interoperable data exchange, coordinated response, and measurable performance across jurisdictions.

The capabilities are concrete.

See the corridor. Work zones, incidents, weather, traffic, freight movement, and the operating environment in real time.

Connect the actors. DOTs, responders, freight, transit, private operators, and other infrastructure stakeholders.

Coordinate operations. Incident response, work zones, events, emergency response, resilience, and cross-jurisdiction issues.

Measure performance. Safety, reliability, response time, throughput, and readiness for future use cases.

This is the layer that turns designated corridors into operating corridors.

It is also where AI, automation, connectivity, and advanced analytics become much more useful. The technology is powerful, but it needs an operating environment. It needs data, governance, workflows, users, feedback loops, and measurable outcomes.

The Mobility Grid does not minimize technology. It creates the conditions for technology to scale.

A concrete corridor example can make this practical by showing how one operating layer supports shared visibility, coordination, and performance measurement.

Ecosystem engagement

Give the ecosystem something to align around.

Once the corridor and digital layer are defined, engagement becomes a question of confidence: whether public agencies, industry, operators, and capital see enough sustained national resolve to organize around repeatable use cases, clear roles, shared expectations, and a path to investment.

Associations and conveners help translate the signalConvene · standardize · socialize use cases · align public and private actors

Align demand

Repeatable use casesCommon operating outcomes

Define participation

Clear operating rolesData and governance expectations

Focus investment

Investable delivery modelPublic / private investment focus

Build the market

Common capability categoriesA path from one corridor to many

Engagement needs

Factor Advisory Notes

Once the corridor and digital layer are defined, ecosystem engagement becomes a question of confidence, not just interest.

Right now, many companies can see pieces of opportunity. OEMs see vehicle readiness. Technology companies see data and AI. Logistics players see freight use cases. Integrators see deployment opportunities. Capital sees potential infrastructure models.

But if the market is not legible, everyone waits for someone else to define it.

The ecosystem needs something to align around. That means repeatable use cases, clear operating roles, data and governance expectations, a path to investment, common capability categories, and a way to understand how one corridor can become many.

This is where the national framing matters. A single corridor can be useful. A corridor that is part of a defined national direction can become a market signal.

The Grid becomes real when ecosystem participation is organized around defined corridors, repeatable use cases, and a market that can scale.

This is also where USDOT can convene without over-owning. The role is not to pick every technology or prescribe every deployment. The role is to help make the market coherent enough that serious public and private actors can organize around it.

Industry associations are well placed to translate the signal: convening members, helping standardize, and socializing use cases across public and private actors. Examples include ITSA, 5GAA, AASHTO, and IBTTA, among others.

From efforts to a model

Make the corridor efforts add up.

Each corridor should stay state-led and grounded in its own priorities. A shared digital operating model across the portfolio is what makes the efforts coherent, repeatable, and investable, rather than a set of fragmented, one-off pilots.

Keep corridors state-led

Agency-led prioritiesOperationally grounded

Create the shared model

Shared use casesData + performance model

Give industry a path to scale

Repeatable capabilitiesTechnology + capital pathway

Turn pilots into a market

Procurement pathwaysOne corridor to many

Factor Advisory Notes

This is the core conclusion. The opportunity is not to replace the corridor efforts. It is to make them add up.

Each corridor should stay state-led and grounded in its own priorities. The use cases may differ. The operating conditions may differ. The lead agencies may differ. The local partnerships may differ.

But across the portfolio, there needs to be enough of a shared digital operating model that the efforts become coherent, repeatable, investable, and transferable.

That shared model does not mean uniformity. It means a common way to think about use cases, the digital operating model, data and governance, performance measures, capability categories, and eventually procurement and delivery pathways where possible.

That is what lets distinct corridor efforts grow into a national operating and market model.

This is not a replacement for existing corridor programs. It is a way to make corridor investments more coherent around a shared digital operating model.

The reason this matters is not organizational neatness. It is the ability to create safer corridors, more reliable movement, faster response and recovery, scalable technology deployment, and clearer public and private investment.

The bottom four moves are the practical version of that.

Keep corridors state-led. The agencies that operate the system need to shape the work.
Create the shared model. The portfolio needs shared use cases, operating models, data expectations, governance principles, and performance measures.
Give industry a path to scale. Technology, AI, capital, delivery partners, OEMs, logistics providers, and operators need to understand how participation in one corridor can translate to others.
Turn pilots into a market. That means procurement pathways, delivery models, and a credible path from one corridor to many.

That is the difference between a set of pilots and a national infrastructure market.

Questions to pressure-test

This framing raises a few practical questions: where the logic holds, where it gets too broad, and what role would be most useful across USDOT, the broader federal government, states, and industry.

Is this a useful way to frame the opportunity?
Where does USDOT have the clearest role?
What role should other parts of the federal government play, given the connections to energy, communications, emergency response, resilience, commerce, logistics, and national readiness?
What would make this more operationally useful to states?
What would make it more compelling to industry?
What role could industry groups and associations play, such as ITSA, 5GAA, AASHTO, IBTTA, and others?
Where does this risk becoming too broad or too abstract?

Appendix · Federal How

How federal action makes corridors executable.

Funding, finance, and lifecycle operations

Strategic corridors need more than designation. They need a federal delivery model that enables whole-corridor participation, lifecycle operations, and financeable execution.

The problem to solve

1

Every state in the corridor must participate

One missing segment weakens the corridor logic.

2

Digital infrastructure has lifecycle obligations

O&M, cybersecurity, software, data services, refresh, and performance reporting must be funded.

3

Corridors need to become financeable programs

The corridor cannot remain a set of disconnected state projects.

Federal levers

Whole-corridor funding

Corridor completion reserve

O&M eligibility + lifecycle set-aside

Existing program alignment

Build America Bureau finance track

Rapid Corridor Execution Package

From near-term signal to scaled execution

Near-term NOFOEstablish the corridor operating model

Surface reauthorizationFund whole-corridor execution and lifecycle O&M

Factor Advisory Notes

This appendix is not intended to turn the discussion into a funding presentation. It is included to show that the delivery model has to be part of the federal strategy.

The near-term NOFO may not be large enough to fund strategic corridors at scale, but it can establish the operating logic that surface reauthorization could later fund and expand.

Designation alone is not enough. Strategic corridors will only work if every state in the corridor participates, if digital infrastructure can be operated and maintained over time, and if corridors can be packaged as financeable programs rather than disconnected projects.

Existing programs should not be replaced. They should be organized. Programs such as INFRA, Mega, Rural, PROTECT, formula funds, TIFIA/RRIF, and Build America Bureau assistance can each fund pieces of a strategic corridor, but corridor designation should give those investments a common operating model and delivery path.

USDOT should remain the organizing lead. Other departments should participate where designated corridors advance their missions. For example, DOD could support defense mobility and installation access; DOE could support energy resilience; DHS/CISA could support emergency response and cybersecurity; Commerce/NTIA could support communications and broadband; and other agencies could support mission-specific corridor overlays.

USDOT organizes the corridor framework. Mission agencies fund the mission overlays.

Surface reauthorization should therefore address whole-corridor funding, variable state match, a corridor completion reserve, O&M eligibility, lifecycle funding support, existing program alignment, a Build America Bureau corridor finance track, and rapid Corridor Execution Packages that move in 90 to 180 days rather than years.

The key test is whether the first corridors make the next corridors easier, faster, and less expensive.

Appendix · Whole of Government

How mission agencies align around the corridor.

USDOT leads the framework. Other departments support mission-specific overlays.

Strategic corridors touch multiple national missions, but the operating model should remain transportation-led. The federal role is to align mission contributions to a shared corridor framework.

Shared corridor framework

USDOT organizing role

Designates strategic corridors

Defines the shared operating model

Sets data, interoperability, and performance expectations

Coordinates state-led corridor execution

Mission overlays

Defense mobility

DOW · installation access · deployment routes · port-to-base movement

Energy resilience

DOE · power reliability · charging · grid coordination

Emergency response + cyber

DHS · CISA · FEMA · incident response · critical infrastructure protection

Communications

Commerce / NTIA · broadband · fiber · corridor connectivity

Rural + freight continuity

USDA · rural segments · agricultural freight · supply-chain continuity

Environment + public health

EPA · emissions · air quality · freight / port impacts

Factor Advisory Notes

This appendix extends the federal delivery logic from the prior frame. The point is not to create a sprawling whole-of-government process. The point is to show how other federal missions can align to a USDOT-led corridor framework.

USDOT should remain the organizing lead because the corridor operating model is fundamentally transportation-led: designation, state coordination, interoperability, performance expectations, and execution cadence.

Other departments should participate where designated corridors advance their missions. DOW / Defense may have an interest in defense mobility, installation access, deployment routes, and port-to-base movement. DOE may have an interest in power reliability, charging, and energy resilience. DHS, CISA, and FEMA may have an interest in cybersecurity, emergency response, and critical infrastructure protection. Commerce and NTIA may have an interest in broadband, fiber, and communications capacity. USDA may have an interest in rural corridor participation and agricultural freight. EPA may have an interest in emissions, air quality, and freight or port impacts.

USDOT leads the corridor framework; mission agencies support the overlays.

This matters because strategic corridors are not only transportation assets. They are part of the operating environment for defense readiness, emergency response, energy resilience, freight movement, communications, rural access, and public health.

The key test is whether the framework lets agencies contribute to a shared corridor model without fragmenting governance or turning the corridor into a collection of separate federal projects.

Appendix · Corridor Readiness

What the first corridors need to bring.

Federal action can create the signal, but the first corridors have to prove the operating model the next corridors can reuse.

Corridor readiness requirements

01

Accountable champion

Lead state or convener owns cadence and decisions.

02

Multi-state participation

Every state has a defined role.

03

Shared use cases

Start with practical corridor operations.

04

Digital readiness baseline

Inventory assets, gaps, and build needs.

05

Governance + data sharing

Define what is shared, with whom, and why.

06

Performance + market case

Measure outcomes and build the case to scale.

Candidate corridors for applying the model

I-80 I-10 I-95 I-35 I-40 I-90/94 I-75 I-5

Factor Advisory Notes

This appendix is the corridor-side complement to the federal delivery frame. Federal action can designate, align, fund, finance, and coordinate, but the first strategic corridors also need to show readiness.

The first corridors should not be treated only as grant recipients. They should be treated as the first proof points for a repeatable national operating model.

That means each corridor needs an accountable champion, multi-state participation, shared use-case priorities, a digital readiness baseline, governance and data-sharing rules, and a performance and investment case.

Corridor readiness should also include an industry engagement posture. The goal is not to invite vendors into disconnected sales conversations. It is to give industry a clear view of the use cases, operating requirements, data expectations, procurement pathways, and performance measures that matter across corridors.

The corridor candidates shown here are not meant to be a final list. They are useful places to pressure-test whether the readiness model works across different operating contexts: freight, weather, ports, rural segments, dense urban corridors, cross-state coordination, resilience, and future-use-case readiness.

This is also where OST-R can play a catalytic role. Research can help define the readiness template: what each corridor should assess, validate, standardize, and measure before federal support scales.

The key test is whether the first corridors make the next corridors easier, faster, and less expensive.