- Identifies current capabilities in the state as well as gaps in services
- Provides a common framework for the planning, design, implementation, integration, and operation of ITS throughout the state
- Enhances the efficiency of ITS project deployment and enhancements
- Improves integration between systems and coordination between stakeholders
- Improves utilization of National ITS Standards
- Compliance with the National ITS Architecture allows Mn/DOT to receive Federal funds for ITS projects
- URS Corporation
- TranSmart Technologies
- Volume 1 - Overview (pdf)
- Volume 2 - ATIS Market Package Bundle (pdf)
- Volume 3 - ATMS Market Package Bundle (pdf)
- Volume 4 - APTS Market Package Bundle (pdf)
- Volume 5 - CVO Market Package Bundle (pdf)
- Volume 6 - EM Market Package Bundle (pdf)
- Volume 7 - MCM Market Package Bundle (pdf)
- Volume 8 - Regional ITS Architecture (pdf)
- Volume 9 - Implementation Projects (pdf)
- Minnesota Regional ITS Architecture 2009 (tbo)
- Link to Turbo Architecture Database Software
- Rashmi Brewer, P.E.
ITS Planning and Regional Architecture (2009 version)
**A new 2014 version of the ITS Architecture is available at: Minnesota Statewide Regional ITS Architecture**
The Minnesota Regional ITS Architecture represents a shared vision of how each agency’s systems work together by sharing information and resources to enhance transportation safety, efficiency, capacity, mobility, and security. The information exchange among the many transportation stakeholders helps illustrate various integration options, gain consensus on cost-effective ITS technologies and systems to be considered prior to investing in the design, development and deployment of ITS.
The National ITS Architecture is a resource to the Minnesota Regional ITS Architecture, providing a framework for planning, defining and integrating ITS. The Minnesota Regional ITS Architecture is a living document and will evolve as needs, technology, stakeholders and funding change. The latest architecture version includes a detailed Operational Concept for each service and identified need, providing more information on how a system will be used and what stakeholder will use it.