MnDOT briefed committee on connected and automated vehicles, urging careful policy work and stakeholder engagement
Get AI-powered insights, summaries, and transcripts
Subscribe
Summary
MnDOT’s director for connected and automated vehicles summarized Minnesota’s Governor’s Council work, gaps in state regulation, stakeholder outreach and two in‑state pilots; members pressed MnDOT on certification, data and congestion impacts from empty vehicle miles.
Tara Olds, director of connected and automated vehicles at the Minnesota Department of Transportation, gave the committee an overview of Minnesota’s work preparing for higher levels of vehicle automation and the resources available to policymakers.
Olds said the Governor’s Council on Connected Automated Vehicles was created by executive order in 2018 and has developed policy themes and council recommendations to guide Minnesota as SAE Levels 4–5 technology advances. She told members Minnesota is one of about 16 states without state rules specific to automated vehicles, which creates uncertainty for industry partners. "Most industry partners stress the importance of having clear legislation on the legality of driverless vehicles as a key component for them to look at investing in technology in specific states," Olds said.
Olds described the council’s process—reviewing state laws across the country, identifying legislative themes and gaps, and engaging more than 70 stakeholders—and highlighted resources for legislators, including a policy themes packet and the council’s recommendations. She invited members to Automated Vehicle Day at the State Capitol (April 14) and noted two Minnesota pilots: Southwest Transit’s Southwest Prime pilot in Eden Prairie with May Mobility and a Grand Rapids project supported through Iron Range Resources and federal funds.
Members raised questions about longer‑range visioning (how AVs could alter transit and land use), data collection and reporting (lessons from California on measuring vehicle miles and empty trips), and certification (who validates safety and interoperability). Olds said MnDOT has done scenario planning over the past five to six years, is tracking different state approaches to data and certification, and that many stakeholders advocate for federal standards on certification and interoperability.
The committee thanked MnDOT for the briefing and indicated members expect follow‑up on pilots and notable AV programs in Minnesota. No committee action was requested at the hearing.