Research

DOT-Sponsored Research Activities

The U.S. Department of Transportation’s (DOT’s) IntelliDriveSM research program fosters public and private sector advancements in transportation system connectivity by:

  • Engaging stakeholders;
  • Advancing research and testing;
  • Developing policy and institutional foundations; and
  • Facilitating the development of standards and potential regulations.

Research Roadmap Development

Research Roadmaps currently are under development in the following program areas:

Michigan Test Bed

DOT ‘s Michigan Test Bed facility, located outside Detroit, MI, is designed to test IntelliDrive technologies and applications. The facility has 75 highway and arterial center lane-miles of roadway, equipped with 52 Dedicated Short Range Communications (DSRC) roadside equipment (RSE) units.

IntelliDriveSM Levels

IntelliDriveSM Levels

Intellidrive Levels Download as PowerPoint

IntelliDriveSM Taxonomy Describes Possible Implementation Scenarios

IntelliDriveSM covers a broad spectrum, ranging from applications that already are on the market—such as E-Tolling—to much more complex active safety systems that truly have the potential to transform the surface transportation environment, but will not enter the marketplace for years to come. To help us all wrap our minds around the universe of IntelliDriveSM applications, and their relationships, the U.S. Department of Transportation (USDOT) has developed the “IntelliDriveSM Taxonomy” diagram, which describes a range of potential IntelliDriveSM implementation scenarios in terms of:

  • Entry points;
  • Levels of capability & complexity;
  • Applications supported;
  • Technology options and constraints;
  • and Stakeholder interests.

The first level of distinction in the diagram is between Level 1 and Level 2. Level 1 applications can be developed as stand-alone devices that do not require connections with the vehicle, other than perhaps for power. Level 2 devices require access to vehicle-based data.

After the primary distinction between Levels 1 and 2, the second distinction is between applications that are time-critical, requiring very fast transaction speeds, and those that are not time-critical. Active safety applications, and some mobility applications, are time-critical, as indicated in Levels 2C and 1B respectively.

Level 2 has also been subdivided into applications that require proprietary vehicle data (Levels 2B and 2 C) and those that do not (Level 2A). Proprietary data refers to data that requires connections to protected safety systems and other systems that could compromise vehicle security. Access to these systems is protected by the vehicle manufacturers, so any applications requiring data from theses systems would require cooperation with the vehicle manufacturers. On the other hand, some non-proprietary data from the vehicle is already made available for external uses through the on-board diagnostics (OBD) port, which contains both proprietary and non-proprietary data. Aftermarket applications could be built around this data without vehicle manufacturer involvement.

Summary of Levels and Applications

Level 1A
  • Applications do not require vehicle based data and are not extremely time-critical.
  • Can use multiple communications technologies.
  • Includes:
    • Most of today’s probe data applications that only require position and speed (which can be obtained from devices with GPS or other positioning capabilities);
    • Electronic tolling using various communications methods;
    • Many of today’s transit and commercial vehicle management applications;
    • SafeTrip-21 applications.
Level 1B
  • Applications do not require vehicle based data but are time-critical.
  • Applications include “here I am” messages from the vehicle. These can improve general situational awareness and can be used to track anonymous vehicle flows through an intersection for traffic planning purposes and other mobility applications.
Level 2A
  • Applications are not extremely time-critical and require vehicle data that is publicly available through the OBD port.
  • An example of a Level 2A application would be a weather application that would use data such as ambient temperature, barometric pressure, etc.
Level 2B
  • Applications are not extremely time-critical, but require vehicle data from critical systems.
  • Coordination with vehicle manufacturers is necessary.
  • Many potential applications for traffic, transit and fleet management, and for weather, energy efficiency and emissions reduction.
Level 2C
  • Applications are time-critical and require vehicle data from critical systems.