The Challenge / Context ODOT is faced with aggressive, legislatively mandated targets to slash transportation greenhouse gas emissions to 80% below 1990 levels by 2050. Concurrently, they must address deep funding deficits and prioritize multi-modal investments across starkly different urban and rural landscapes.
Traditional “predict-then-act” forecasting models fell short because they rely heavily on a single, deterministic baseline for economic growth and travel behavior. In an era disrupted by explosive telecommuting shifts, rapid electric vehicle (EV) transitions, and autonomous vehicle (AV) ambiguity, building a 25-year plan around a single “most likely” future risked making multi-billion-dollar infrastructure investments fragile and highly vulnerable to real-world volatility.
Securing Stakeholder Buy-In The ultimate catalyst occurred around 2018 when empirical data revealed Oregon was significantly off-track from meeting its mid-century climate mandates. This triggering event forced leadership to acknowledge that status-quo planning assumptions were no longer viable.
To “sell” DMDU to non-technical stakeholders and executives, the technical team reframed the narrative from predicting a single future to managing risk and institutional flexibility. They introduced a clear separation between Strategic Models (designed for open scenario screening and identifying systemic uncertainty) and Tactical Models (designed for project-level facility detail, legal certifications, and immediate dollar allocation). To make the math tangible, ODOT utilized “Transportation Personas,” which quantified and visualized how individual households across various demographics would realistically experience these uncertain futures.
Discussion Question: “When you explicitly divided the analysis into 'Strategic' vs 'Tactical' frameworks, did that immediately ease tensions with board members who are traditionally anxious to see specific local highway projects on a map? How hard was it to get leadership to accept that a strategic model must intentionally sacrifice local granular detail to achieve scenario breadth?”
The DMDU Approach (Methodology) ODOT shifted away from a single “preferred alternative” to a highly interactive, exploratory sandbox. While a strict XLRM framework wasn’t explicitly advertised under that name, the approach mirrored its principles:
Technical Implementation The technical heavy lifting was handled by the open-source VisionEval framework. Structurally, VisionEval relies on a “disaggregate demand/aggregate supply” setup. Because it processes synthetic populations but handles travel without requiring computationally intensive, explicit network routing, its runtimes are exceptionally fast. This speed allowed the team to seamlessly overlay the TMIP-EMAT interface, executing a massive exploratory sweep of thousands of scenarios that would be impossible with a traditional, cumbersome travel demand model.
Discussion Question: “Many agencies struggle with the technical learning curve of TMIP-EMAT. Did you face computing, staffing, or data extraction bottlenecks when analyzing thousands of runs? If you were advising another DOT on scaling up VisionEval + EMAT, what is the one data pipeline lesson you wish you knew before starting?”
Crucially, it changed the institutional conversation by transforming the long-range plan into an adaptive “plan to learn” document. By setting up strategic monitoring benchmarks at the operational level, the agency can now explicitly flag when an uncertainty is drifting outside anticipated bounds, signaling exactly when to refine policy levers.
Discussion Question: “We are in 2026, roughly three years post-adoption of the OTP. Has this 'plan to learn' and 'monitoring at the operational level' strategy triggered any real-world policy pivots yet? How are you tracking and feeding real-world emissions and VMT data back into the strategic loop?”
Discussion Question: “What has been the hardest part of managing the analytical handoff between your strategic exploratory insights (VisionEval) and your tactical travel demand models (like SWIM) when regional planners request project-level backing? Do the two datasets ever feel like they are speaking different languages to local stakeholders?”
Pro-Tip for the Conversation Use Question 1 as your icebreaker. Agencies all over the country struggle with engineers wanting to use massive, slow travel demand models for high-level exploratory planning. Hearing exactly how ODOT drew the boundary line between “strategic scenario exploration” and “tactical project delivery” will yield an incredibly valuable case study for the entire DMDU community.
Zephyr is a community effort — join as a member, support our activities, or say hello in the Zephyr Forum.
Become a Member Donate Join the Zephyr Forum