IntelliDrive SM Connectivity − Mobility

1. IntelliDriveSMConnectivity − Mobility

2. Drivers Vehicles Infrastructure Wireless Devices What is IntelliDriveSM? • IntelliDriveSM is a suite of technologies and applications that use wireless communications to provide connectivity: • With and between vehicles of all types • Between vehicles and roadway infrastructure • Among vehicles, infrastructure and wireless consumer devices

3. Networked Environment

4. 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

5. 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

6. Why IntelliDriveSM? Environmental Problem • 2.9 billion gallons of wasted fuel each year • 22% CO2 emissions from vehicles Environmental Benefits • ↓Emissions ↓Greenhouse Gases ↓ Particulates: • 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

7. IntelliDriveSM Mobility Data Environment Safety, Mobility, and Environmental Applications Real-time Data Capture and Management

8. 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

9. 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 Capture Data Environment Information Raw Data Application

10. Key Issues in Defining A Data Environment What Data Do We Keep? How Do We Structure The Data? How Do We Use The Data? What Data Do We Capture?

11. USES SOURCES Data Sources and Uses SOURCES USES PERFORMANCE MEASUREMENT TRAVELER ECO- DRIVE QUEUE WARNING LOCATION DECISONS TRAVELER INFORMATION VEHICLE ENVIR. MOBILITY SAFETY LIGHT VEHICLE TRANSIT FREIGHT VARIABLE SPEED LIMITS INFRASTRUCTURE OTHER OTHER OTHER LOOP RADAR OTHER

12. Data Aggregationand Structure AGGREGATION AGGREGATION STRUCTURE AREA-WIDE AGGREGATION STANDARDS ACCESS QUALITY IP RAW DATA PRIVACY STORAGE STRUCTURE REGULATION STRUCTURE AGGREGATION

13. End State “a few” ~ 3-5% TRAVELER VEHICLE “nearly all” ~ 99% INFRASTRUCTURE “where needed” ~ 40% T V I T T V V I I Potential Interim States Data Environment Evolution Current State TRAVELER < 0.1% VEHICLE < 1% INFRASTRUCTURE 15-20%

14. GOVERNANCE HISTORY/CONTEXT VIRTUAL WAREHOUSING META-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 Capture Data Environment Information Raw Data Application

15. Projected Outcomes • Establish one or more data environments • Broad collaboration supporting data environment utilization • Implementation of data management processes representing best practices

16. 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

17. 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

18. Leverage Multi-Source Data VEHICLES FREIGHT LIGHT VEHICLE • 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 TRANSIT INFRASTRUCTURE TRAVELERS DATA ENVIRONMENT c a MODE-SPECIFIC APPLICATIONS (e.g., for freight vehicles) CROSS-MODAL APPLICATIONS (e.g., for system managers) b MULTI-MODAL APPLICATIONS (e.g., for travelers)

19. Multi-Modal Applications Development and Test • Coordinated development of mode-specific and multi-modal applications: • avoid duplication • cost-effective INFRASTRUCTURE FLEET OPERATORS VEHICLES MANAGERS c DATA ENVIRONMENT b a APPLICATIONS TRAVELERS TRAVELERS

20. 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

21. Encourage competitive application commercialization HIGH PROGRAM FOCUS OPEN SOURCE DATA OPEN SOURCE DEVELOPMENT COOPERATIVE RESEARCH AND DEVELOPMENT COMPETITIVE APPLICATION COMMERCIALIZATION TECHNOLOGY TRANSFER LOW PROGRAM FOCUS SUPPORT RESEARCH COMMERCIALIZATION DEVELOPMENT APPLICATION DEPLOYMENT LIFE-CYCLE

22. 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

23. 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

24. Practice long-term technology stewardship

25. Projected Outcomes • Multiple applications developed leveraging multi-source data • Research spurs commercialization • Applications enable transformational change

26. 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. Draft Agendafor 16 March (Savannah) • Scheduled for 1-5 PM, Room TBD • Welcome and Introductions 1:00-1:10 • IntelliDrive Overview, Valerie Briggs 1:10-1:45 • Recap and Q&A based on Valerie’s briefing earlier in day • Planned outreach and stakeholder engagement events • ITE IntelliDrive Activities, ITE Task Force 1:45-2:00 • Current and planned ITE activities • Data/Mobility Applications Roadmap Discussion, USDOT 2:00-3:00 • Overview of planned program activities • BREAK 3:00-3:20 • Opportunities for Participation, USDOT and ITE 3:20-4:20 • Discuss specific opportunities, potential outcomes • Next Steps and Wrap-Up 4:20-5:00

29. For More Information… http://www.intellidrive.org/