1

IntelliDriveSM Connectivity − Mobility

Karl WunderlichMeenakshy Vasudevan

Noblis8 June 2010

What is IntelliDriveSM?

• IntelliDriveSM is a suite of technologies and applications that use wireless communications to provide connectivity:– Among vehicles of all types– Between vehicles and 

roadway infrastructure– Among vehicles, 

infrastructure and wireless consumer devices

Vehicles

WirelessDevices

Infrastructure

Drivers

2

Networked Environment

3

Why IntelliDriveSM?

Safety Problem• 40,000 highway deaths/year• 6 million crashes/year • Leading cause of death for ages 

4 to 34

Safety Benefits• Dramatically reduced fatalities 

and injuries through greater situational awareness:– Driver Advisories– Driver Warnings– Vehicle Control

4

Why IntelliDriveSM?

Mobility Problem• 4.2 billion hours of travel delay• $78 billion annual drain on US 

Economy

Mobility Benefits• Information‐rich environment 

benefits users and operators of all travel modes:– Travelers have real‐time 

information on rerouting or “modal shift” options

– System operators have real‐time data to enable better system operations for optimal performance

– Planners can use data to improve major investment plans

5

Why IntelliDriveSM?

Environmental Problem• 2.9 billion gallons of wasted fuel 

each year• 22% CO2 emissions from 

vehicles 

Environmental Benefits• ↓Emissions  ↓Greenhouse 

Gases ↓ Par culates:– Reduced stopping/starting at 

traffic signals which consumes 3‐5 times more fuel than constant driving

– Nav systems with real time information can reduce fuel consumption by 10.5% over systems without real time traffic data

6

IntelliDriveSM Mobility

7

Data Environment

Real‐time Data Capture and ManagementMobility and Environmental 

Applications

Reduce Speed 35 MPH

Weather Application

Transit Data

Transit Signal Priority

Real‐Time Data Capture and Management

Vision• Active acquisition and systematic provision of integrated, multi‐source 

data to enhance current operational practices and transform future surface transportation systems management

Objectives• Enable systematic data capture from connected vehicles (automobiles, 

transit, trucks), mobile devices, and infrastructure• Develop data environments that enable integration of data from multiple 

sources for use in transportation management and performance measurement

• Reduce costs of data management and eliminate technical and institutional barriers to the capture, management, and sharing of data

8

Creating a Data Environment

Data environment:• well‐organized collection of data 

of specific type and quality• captured and stored at regular 

intervals from one or more sources

• systematically shared in support of one or more applications

Data Environment

Application

Data Capture

Information

Raw Data

9

Key Issues in Defining A Data Environment

What Data Do We Keep?

How Do We Structure The Data?

What Data Do We 

Capture?

How Do We Use 

The Data?

10

Data Sources and Uses

SOURCES

USES

SOURCES USES

MOBILITY SAFETYENVIR.TRANSIT FREIGHTLIGHT VEHICLE

LOOP RADAR OTHER

VEHICLE

INFRASTRUCTURE

LOCATION DECISIONS

TRAVELERPERFORMANCEMEASUREMENT

TRAVELERINFORMATION

VARIABLESPEED LIMITS

OTHER

OTHEROTHER

ECO‐DRIVE

QUEUEWARNING

11

STRUCTURE

Data Aggregationand Structure

STRUCTURE

AGGREGATION

AGGREGATION

AREA‐WIDEAGGREGATION

RAWDATA

QUALITY

IP

PRIVACY

ACCESS

STANDARDS

REGULATION

STORAGE

AGGREGATION

STRUCTURE

12

Potential End StateCurrent State

Potential Interim States

T

V

IT

V

I

T

V

I

Data Environment Evolution

13

TRAVELER

VEHICLE

INFRASTRUCTURE

“some”

“a few”

“nearly zero”

VEHICLE

TRAVELER

“nearly all”

“some”

“where needed”

INFRASTRUCTURE

GOVERNANCE

HISTORY/CONTEXT

VIRTUAL WAREHOUSING

Application

META‐DATA

Capture

InformationRaw Data

Elements of Data Capture and Management

• Meta data:– Provision of well‐documented 

data environment

• Virtual warehousing:– Supports access to data 

environment and forum for collaboration

• History/context:– Objectives of data assembly

• Governance:– Rules under which data 

environment can be accessed and procedures for resolving disputes

Data Environment

14

Projected Outcomes

• Establish one or more data environments• Broad collaboration supporting data environment utilization• Implementation of data management processes representing best 

practices

15

Dynamic Mobility Applications

Vision• Expedite development, testing, commercialization, and deployment of innovative 

mobility applications:– maximize system productivity– enhance mobility of individuals within the system

Objectives• Create applications using frequently collected and rapidly disseminated multi‐

source data from connected travelers, vehicles (automobiles, transit, freight) and infrastructure

• Develop and assess applications showing potential to improve nature, accuracy, precision and/or speed of dynamic decision making by system managers and system users

• Demonstrate promising applications predicted to significantly improve capability of transportation system to provide safe, reliable, and secure movement of goods and people

16

Guiding Principles

• Leverage multi‐source data• Develop and test mode‐specific and multi‐modal applications• Feature open source application research and development• Encourage competitive application commercialization• Prioritize program resources based on expected impact• Enhance analytical capabilities related to mobility applications• Practice long‐term technology stewardship

17

Leverage Multi‐Source Data

• Leverage high‐quality data integrated from mobile and fixed sources to develop multiple applications (mode‐specific and multi‐modal)

• Requires coordination with Real‐Time Data Capture and Management program

DATAENVIRONMENT

MODE‐SPECIFICAPPLICATIONS

(e.g., for freight vehicles)

a

b

c

VEHICLES

TRAVELERSINFRASTRUCTURE

TRANSIT

FREIGHTLIGHT VEHICLE

MULTI‐MODALAPPLICATIONS

(e.g., for travelers)

CROSS‐MODALAPPLICATIONS

(e.g., for system managers)

18

Multi‐Modal Applications Development and Test

• Coordinated development of mode‐specific and multi‐modal applications:– avoid duplication– cost‐effective

a

b

cDATA

ENVIRONMENT

VEHICLES

INFRASTRUCTURE

TRAVELERS TRAVELERS

MANAGERS

FLEET OPERATORS

APPLICATIONS

19

Open Source Research and Development

• Research issue is too complex or big for isolated researchers to solve• Promotes highest level of collaboration• Preserves intellectual capital• Serves to engage partners from academia and industry who may not be 

directly involved in funded applications development and testing

20

Encourage competitive application commercialization

21

APPLICATION DEPLOYMENT LIFE‐CYCLE

RESEARCH DEVELOPMENT COMMERCIALIZATION SUPPORT

PRIVATESECTORFOCUS

PUBLICSECTORFOCUS

COMPETITIVEAPPLICATION

COMMERCIALIZATION

COOPERATIVERESEARCH

ANDDEVELOPMENT

Prioritize resources based on expected impact

• Develop prototype mobility application that focuses on performance measures:– exploits new or integrated data sources– enhances traditional measures or creates new measures to capture 

full impact of mobility applications• Prioritization of development and test of candidate applications:

– applications must improve system productivity or user mobility– well‐defined, quantitative performance measures (multi‐modal or 

mode independent)– applications must have broad stakeholder interest and support

22

Enhance analytical capabilities

• Develop analytic tools and processes to accurately predict impacts:– assess long‐term performance– use real‐time prediction to support improved decision making by 

travelers, system managers and other transportation system stakeholders (e.g., fleet operators)

• Employ tools to refine and identify promising applications prior to committing resources for field testing or full demonstration

23

Practice long‐term technology stewardship

24

Projected Outcomes

• Multiple applications developed leveraging multi‐source data• Research spurs commercialization• Applications enable transformational change

25

FOUNDATIONAL ANALYSISPHASE 1Program Activity Track

IntelliDriveSM Data Capture and Management Program: High‐Level Roadmap

Program Planning 

Stakeholder Engagement

Decision pointLEGEND:High‐Level Roadmap v1.0 ( 4/5/2010)

Demonstrations

Institutional and Policy

Standards

Research and Development PHASE 2 DECISIO

N PO

INT

Proof‐of‐Concept Testing

Inst. & Policy Assessment

Standards Plan

Phase 2ApplicationsDownselect

RESEARCH, DEVELOPMENT & TESTING PHASE 2

DEMONSTRATIONPHASE 3

Years 0‐1.5 Years 1.5‐3.5 Years 3.5‐5

Outreach

Evaluation

POC Testing

POC Data Environment(s)

Prototype Data Environment

PHASE 3 DECISION PO

INT

Data + Applications Mapping

Phase 3Demo Site

Downselect

Phase 3 Demonstration(s)

Phase 3 Data Environment(s)

Phase 3 Demo Planning

Data Environment

Standards DemonstrationStandards Development and Testing

State‐of‐the‐Practice and Innovation Scan Innovative Data Cap. & Mgt. Methods Development

Inst. and Policy Requirements Revised Policies, Possible Rulemaking

Data Capture

Data Capture

Data Capture

ProgramActivity

Is there substantive research to be conducted in a proof‐of‐concept test?Is the program well‐defined and connected to the ITS Program?

Do the results from the POC tests motivate larger‐scale demonstrations?

Near‐Term Demo Data Environment(s)

Near‐term Mobility Demo(s)

Optional Testing

Phase 3 Data Environment(s)

Data Capture

Keys to Success for IntelliDriveSM Mobility

• Facilitate easy, secure access to data environment and enable collaboration in mobility application development

• Accumulate and share intellectual capital while respecting IP rights• Coordination with other IntelliDrive program areas and broader ITS 

programs• Active interaction with broader group of stakeholders outside the federal 

research and development efforts• Not a one‐time engagement, will require ongoing collaboration to:

– refine program goals– refine data needs– structure relevant and feasible data environment development efforts– prioritize applications development and testing

27

Stakeholder Participation

• Provide feedback on program direction, goals, data environment, mobility applications

• Respond to upcoming funded requests for research and development of mobility applications

• Seek to leverage IntelliDrive data and applications resources in other non‐federal or non‐IntelliDrive federally funded research projects

• Offer new data sets and applications• Actively commercialize mobility applications developed within the 

IntelliDrive program

28

Completed Activities

• Vision and program roadmaps• Stakeholder interaction roadmap• Inventory of USDOT/Federally funded data warehousing projects• White paper on Federal role in Data Capture and Management• POC/NCAR test data assessment

29

Next Steps

• Develop prototype data environment• Populate data environment with POC/NCAR data for 12 days, develop 

documentation• Initiate Dynamic Mobility Applications Near‐Term demonstration 

procurement• Develop candidate applications template• Start prototype applications development• Develop preliminary rules of engagement

• applications development environment• open data

30

For More Information…

http://www.intellidrive.org/