Presentation is loading. Please wait.

Presentation is loading. Please wait.

Quarterly Review May 8, 2012 Real-Time Data Capture and Management Program Dynamic Mobility Applications Program.

Similar presentations


Presentation on theme: "Quarterly Review May 8, 2012 Real-Time Data Capture and Management Program Dynamic Mobility Applications Program."— Presentation transcript:

1 Quarterly Review May 8, 2012 Real-Time Data Capture and Management Program Dynamic Mobility Applications Program

2 2 U.S. Department of Transportation Agenda  Data Capture and Management (Dale Thompson)1:00-1:35 PM □ Key Program Accomplishments □ Innovations Scan: Lessons Learned and Findings □ Research Data Exchange: Next Steps □ Financial and Project Status Summary  Dynamic Mobility Applications Program (Kate Hartman)1:35-2:10 PM □ Key Program Accomplishments □ Application Bundle Development Update □ Stakeholder/Outreach Summary □ Financial and Project Status Summary  DCM+DMA Joint Topics2:10-2:30 PM □ Issues and Items for Senior Management Attention □ Phase 2 Integrated Research Plan

3 Real-Time Data Capture and Management Program Program Status

4 FOUNDATIONAL ANALYSIS PHASE 1 Program Activity Area Data Capture and Management and Dynamic Mobility Applications Programs: Integrated Roadmap Decision Point LEGEND: DCM/DMA Integrated Roadmap v0.5 (1/24/2012) Real-World Application Demonstrations Organizing and Utilizing Connected Vehicle Data Defining, Prototyping and Testing Applications RESEARCH, DEVELOPMENT & TESTING PHASE 2 DEMONSTRATION PHASE 3 9/09 Phase 3 Demo Sites Downselect Phase 3 Demonstration(s) Safety Pilot Model Deployment RDE Data Feed 9/11 9/13 Develop Research Data Exchange 9/15 Maintain and Enhance Research Data Exchange Research Data Exchange Mobility Benefits Evaluation Define Mobility Measures v1 v2 v3 v4 BSM Assessment Research Data Exchange (RDE) Prototype Data Environment Develop and Refine Tools/Analytics For Impacts Assessment Assess App. Impact -- ModelsAssess App. Impact -- Demos Phase 2 Applications Downselect Application Prototyping and Testing Applications Identification Demo Coordination Planning Other Demonstrations (e.g, FDOT) Data to RDE Determine Application Data and Communications Needs Standards Planning and Development Role of Standards Standards Testing and Assessment Downselect Applications Ready for Demonstration Define Implementation State Data Environment(s) Data to RDE CONOPS Mobility Demo Planning BSM DATA ANALYSIS EST. IMPACT MEASURED IMPACT v5 Data to RDE APPLICATION DESCRIPTIONS BSM Assessment/OEM Engagement BSM Assessment Papers preliminary v1 v5 final Key Activity Informing BSM Assessment Data Environment Mobility Applications

5 5 U.S. Department of Transportation Data Capture and Management Program: Key Accomplishments (11/11-5/12)  Initiated Research Data Exchange (RDE) development effort, 12/1 □ RDE to be launched at ITS America, 5/21  Acquired Test Data Sets from four sites, 1/1 □ Portland, Seattle, Pasadena, San Diego □ These data will be available on RDE  US-Japan Probe Data: Research plan and annotated outline of research report agreed upon by USDOT and MLIT, next US-Japan Task Force meeting 5/25  Safety Pilot data workshop held 3/6-7, coordination effort now expanded to include discussion of contextual and non-vehicle data with UMTRI  Data Business Plan completed summary of stakeholder interviews regarding surface transportation data-related efforts across FHWA/USDOT, 4/9  Completed Innovation Scan project (11/11) □ Lessons learned influencing RDE development, other efforts

6 Real-Time Data Capture and Management Program Innovations Scan: Lessons Learned and Recommendations

7 7 U.S. Department of Transportation Innovations Scan Project  Assessed industry best practices in data capture and management methods and technologies that are applicable to the DCM Program  Identified four "most promising" emerging concepts and technologies  USDOT Lead: Mohammed Yousuf (FHWA R&D)  Contractor: SAIC/Delcan/University of Virginia (PI: Dick Mudge)  POP: 9/22/10-11/30/11

8 8 U.S. Department of Transportation Data Capture Challenge: Bandwidth Overload Innovation: DIDC  Issue: Potential data explosion due to new forms of data will likely over- burden the computational and communication systems □ Large volumes of data with connected vehicles, infrastructure, and travelers ▪ Approximately 1.2 MB of accelerometer data generated per vehicle per mile (Source: Cooperative Transportation Systems Pooled Fund Study on Pavement Assessment by Auburn University) ▪ Translates to 2 TB of data per day just for pavement assessment for Washington, DC □ Capturing, transmitting, cleaning, and storing large volumes of data can over- burden the system and be cost-prohibitive  Innovation: Dynamic Interrogative Data Capture (DIDC)

9 9 U.S. Department of Transportation Dynamic Interrogative Data Capture (DIDC)  Each device (in a vehicle, on the infrastructure, or on a person) can set and reset message priorities to different data elements  Each device can intelligently and dynamically decide on data aggregation levels and transmission frequencies, based on its own state (local conditions) as well as the state of the network (global conditions)  Each device can query other devices in its vicinity, depending on its data needs, and request certain data aggregation levels Wireless Sensor Networks (WSNs): Adaptive management of data flow in complex systems Mote Technology Example WSN Topologies Example of DIDC Concept  Value to DCM: Can cut communications and energy costs up to 99% compared with fixed interval approaches -- with same impact (defense applications)  Challenges: Adapting and structuring an analog system for transportation, determining potential benefits

10 10 U.S. Department of Transportation Data Capture Challenge: Data from Travelers Innovation: Crowdsourcing  Issue: Envisioned transformative applications require new forms of real time and archived data that are extremely costly to obtain, or create possible privacy conflicts if required from all vehicles or travelers  Innovation: Crowdsourcing  Practice of tapping into the collective intelligence of the public at large to complete tasks that a company would normally either perform itself or outsource to a known entity (blend of crowd and outsourcing) When is crowdsourcing beneficial?Benefits Need massive amounts of real-time data Need continuous temporal and spatial data Create data archives Solve challenging problem Need innovation Improves productivity Minimizes labor and research expenses Consumers involved in creating product

11 11 U.S. Department of Transportation Crowdsourced Traveler Data  Inrix: provides traffic information using crowdsourced traffic data) ▪ crowdsources data from 3 million GPS enabled vehicles and devices covering 450,000 miles of roadways  Waze: provides 100% crowsourced, free real-time traffic information on mobile devices ▪ crowdsources data from GPS enabled vehicles of volunteers for real-time traffic information and maps (passive participation is sufficient) ▪ crowdsources data for map correction (requires active participation) Image Source: Image Source:  Value to DCM: Opt-in crowdsourcing could lead to systematic capture of traveler trip data including itinerary and traveler behavior/response data (transform ATIS and multi-modal corridor management?)  Challenges: Structuring public-private partnerships, privacy

12 12 U.S. Department of Transportation Data Management Challenge: Large Volumes of Data Innovation: Virtual Data Warehousing  Issue: Large volumes of diverse spatial data call for new methods of data management □ Infrastructure costs, operations and maintenance costs, storage costs, labor costs can quickly add up □ Wide range of multi-source data needs to be widely accessible to integrate systems (e.g., signal systems, traveler information systems, transit operations)  Innovation: Virtual Data Warehousing (VDW) Concepts □ Cloud Computing □ Data Federation

13 13 U.S. Department of Transportation Cloud Computing  "Model for enabling ubiquitous, convenient, on‐demand network access to a shared pool of configurable computing resources that can be rapidly provisioned and released with minimal management effort or service provider interaction" (Source: National Institute of Standards and Technology (NIST)) Image Source: Computing-linear-utility-or-complex-ecosystem  Value to DCM: For RDE, increased flexibility, reduced costs, improved scalability, location independence  Challenges: Security, potential data transfer bottlenecks, data consistency

14 14 U.S. Department of Transportation Data Federation  Form of data virtualization where data from multiple, heterogeneous, autonomous data sources are made accessible to data consumers as if it is contained in one single relational database, by using on-demand data integration  Value to DCM: incorporates data from many sources without issues associated with centralized services, local data experts maintain local data, brings data to users rapidly and consistently  Challenges: Interfaces and IP rights must be carefully defined, security

15 15 U.S. Department of Transportation Capitalizing on Innovation: Related Next Steps  Dynamic Interrogative Data Capture □ Concept development white paper  Crowdsourcing □ Nomadic platform testing  Data Federation and Cloud Computing □ RDE currently being developed in cloud environment □ Opportunities to test federation with the RDE identified ▪ FDOT SunGuide system ▪ UMTRI (Safety Pilot Data) ▪ Clarus

16 Real-Time Data Capture and Management Program RDE Next Steps and Agile Development

17 17 U.S. Department of Transportation RDE Development: Next Steps  Complete transition of PDE content to RDE  Prepare test data sets (Portland, Seattle, Pasadena, San Diego) for RDE □ Standardize meta-data □ Load into cloud-based RDE  Demonstrate at ITS America, Mobility Workshop (5/21-24)  Update and enhance the RDE using agile approach

18 18 U.S. Department of Transportation Agile Development  Agile software development is a proven IT industry practice, but new for ITS program sponsored initiatives  Incremental development based on backlog of desired features □ In each 2-4 week sprint, new features selected from the backlog are tested and implemented into a working version  Agile approaches are most successful when there is uncertainty about how users will utilize the product, and can be developed over time □ RDE and DMA Open Source Portal using agile development  So far so good – we will report lessons learned next review

19 Dynamic Mobility Applications Program Program Status

20 FOUNDATIONAL ANALYSIS PHASE 1 Program Activity Area Data Capture and Management and Dynamic Mobility Applications Programs: Integrated Roadmap Decision Point LEGEND: DCM/DMA Integrated Roadmap v0.5 (1/24/2012) Real-World Application Demonstrations Organizing and Utilizing Connected Vehicle Data Defining, Prototyping and Testing Applications RESEARCH, DEVELOPMENT & TESTING PHASE 2 DEMONSTRATION PHASE 3 9/09 Phase 3 Demo Sites Downselect Phase 3 Demonstration(s) Safety Pilot Model Deployment RDE Data Feed 9/11 9/13 Develop Research Data Exchange 9/15 Maintain and Enhance Research Data Exchange Research Data Exchange Mobility Benefits Evaluation Define Mobility Measures v1 v2 v3 v4 BSM Assessment Research Data Exchange (RDE) Prototype Data Environment Develop and Refine Tools/Analytics For Impacts Assessment Assess App. Impact -- ModelsAssess App. Impact -- Demos Phase 2 Applications Downselect Application Prototyping and Testing Applications Identification Demo Coordination Planning Other Demonstrations (e.g, FDOT) Data to RDE Determine Application Data and Communications Needs Standards Planning and Development Role of Standards Standards Testing and Assessment Downselect Applications Ready for Demonstration Define Implementation State Data Environment(s) Data to RDE CONOPS Mobility Demo Planning BSM DATA ANALYSIS EST. IMPACT MEASURED IMPACT v5 Data to RDE APPLICATION DESCRIPTIONS BSM Assessment/OEM Engagement BSM Assessment Papers preliminary v1 v5 final Key Activity Informing BSM Assessment Data Environment Mobility Applications

21 21 U.S. Department of Transportation Dynamic Mobility Applications Program: Key Accomplishments (11/11-5/12)  Completed four application bundle Concepts of Operations/Operational Concepts □ FRATIS, EnableATIS, IDTO, INFLO  M-ISIG bundle development effort initiated by Cooperative Transportation System (CTS) Pooled Fund Study (Virginia DOT, lead), 2/27  Initiated Open Source Portal implementation effort, 3/12 □ ConOps and Systems Requirements effort completed, 12/1  Continued program of extensive stakeholder engagement □ Initiated a new task with the VIIC, held a Mobility 101 briefing, 3/20 □ CTS Pooled Fund briefing on BSM, 3/25 □ 19 bundle-specific stakeholder workshops and other events  Completed BSM Assessment white paper Ver. 1, 2/12

22 22 U.S. Department of Transportation Freight Advanced Traveler Information System (FRATIS): Concepts and Potential Impacts  FRATIS App: Freight-Specific Dynamic Travel Planning and Performance □ Enhances traveler information systems to address specific freight needs □ Integrates data on wait times at intermodal facilities (e.g. ports), incident alerts, road closures, work zones, routing restrictions (hazmat, oversize/overweight)  FRATIS APP: Drayage Optimization □ Optimize truck/load movements between freight facilities, balancing early and late arrivals □ Individual trucks are assigned time windows for pick-up or drop-off  10-year transformative impact targets □ Reduce truck travel times, 17% □ Reduce bobtail (empty) trips, 15% □ Reduce terminal wait times, 35% □ Reduce freight-involved incidents, 35% □ Reduce fuel consumption/emissions, 10% FRATIS USDOT Lead: Randy Butler (FHWA Office of Operations)

23 23 U.S. Department of Transportation FRATIS Mobility Application Bundle: Accomplishments and Next Steps  Accomplishments □ ConOps completed, System Requirements walkthrough held 5/1 □ Strong IFTWG stakeholder interest for early prototyping (Los Angeles, Miami) □ Interest in FRATIS bundle to support evacuation planning (Miami)  Next Steps □ Prototyping activity preparing for procurement □ Considering RFA/RFP supporting prototyping in up to two sites  Cross-cutting needs identified □ Application Enabled Device (AED), carry-in device to convey information to drivers when planning trips pre-trip or en route (without distraction) □ Dual-mode BSM-generating device to assess value of BSM concepts in meeting FRATIS data needs (in concert with other data sources) FRATIS System Concept Diagram (from ConOps)

24 24 U.S. Department of Transportation Intelligent Dynamic Transit Operations (IDTO): Concepts and Potential Impacts  IDTO App: Dynamic Transit Operations (T-DISP) □ Links available transportation service resources with travelers through dynamic transit vehicle scheduling, dispatching and routing capabilities  IDTO App: Connection Protection (T-CONNECT) □ Enable coordination among public transportation providers and travelers to improve the probability of successful transit transfers  IDTO App: Dynamic Ridesharing (D-RIDE) □ Uses dynamic ridesharing technology, personal mobile devices, and voice activated on-board equipment to match riders and drivers  10-year transformative impact targets □ Increase percentage of connections requested and then made that involve fixed and flexible modes to 90% □ Reduce duration of time from making a request to receiving a trip confirmation to 45 seconds □ Reduce passenger wait time to less than 10 minutes IDTO USDOT Lead: Ron Boenau (FTA)

25 25 U.S. Department of Transportation IDTO Mobility Application Bundle: Accomplishments and Next Steps  Accomplishments □ Stakeholder webinar, 11/2 □ Stakeholder workshop held concurrent with 2012 TRB Annual Meeting (1/26-27) □ ConOps completed, ConOps walkthrough held 4/16  Next Steps □ Finalize System Requirements, July □ Prototyping RFA/RFP to examine IDTO application synergies across bus, rail and ridesharing options  Cross-cutting needs identified □ Dual-mode BSM-generating device to assess value of BSM concepts in meeting IDTO data needs (in concert with existing data and communications, e.g., AVL) □ Test vehicle-device integration (e.g., distinguish transit passengers from pedestrians) □ Examine data gap associated with traveler itinerary and trip flexibility T-CONNECT Operational Concept (from ConOps)

26 26 U.S. Department of Transportation EnableATIS: Concepts and Potential Impacts  10-year transformative impact targets □ Widespread availability of end-to-end trip planning and management applications (integrating time of departure, cost, mode, route, and parking decisions) □ Emergence of at least one state-of-the-art corridor or regional transportation management systems utilizing systematically obtained traveler trip data EnableATIS USDOT Lead: Bob Rupert (FHWA) Weather Data Traveler Decisions Itinerary Data M2V Integration Increasingly Capable Mobile Platforms and Services Will Transform ATIS (EnableATIS OpCon)  EnableATIS Operational Concept identified high- value federal roles and activities □ Not applications, as in other bundles  Nomadic Platform Concept □ Originally envisioned as a challenge, now the program is considering a phased BAA approach to acquire devices for testing in 2013 □ Gather or infer decisions/itinerary data from adaptive interaction with the traveler □ Devices may obtain or infer vehicle status data when carried into a vehicle (e.g., obtain external temperature by using a camera to read dashboard display)

27 27 U.S. Department of Transportation EnableATIS Mobility Application Bundle: Accomplishments and Next Steps  Accomplishments □ Operational Concept completed, 4/9  Next Steps □ Utilize Test Data Sets in a no-reward challenge or BAA to develop multi- modal traveler applications □ Initiate outreach to crowdsourcing application developers to explore concept of systematic collection of traveler itinerary/behavioral data □ Specify and procure nomadic platform prototypes  Cross-cutting needs identified □ Explore use of mobile device data to better anticipate traveler response to information for corridor/system management □ Utilize BSM-capable devices in experiments conducted in test beds □ Examine vehicle-device integration, role of J2735 probe data process □ Remotely configurable devices can test DIDC concept, tailoring data generation to dynamic data needs Enable ATIS Operational Laissez-Faire Scenario (from OpCon)

28 28 U.S. Department of Transportation Intelligent Network Flow Optimization (INFLO): Concepts and Potential Impacts  INFLO App: Speed Harmonization (SPD-HARM) □ Dynamically adjust and coordinate vehicle speeds in response to congestion, incidents, and road conditions to maximize throughput and reduce crashes □ Recommend speeds by lane, by vehicle weight and size, by pavement traction  INFLO App: Cooperative Adaptive Cruise Control (CACC) □ Dynamically adjust and coordinate cruise control speeds among platooning vehicles to improve traffic flow stability and increase throughput □ Closely link with SPD-HARM to reduce shockwaves  INFLO App: Queue Warning (Q-WARN) □ Provide drivers timely warnings and alerts of impending queue backup, V2I and V2V  10-year transformative impact targets □ Improve throughput (veh/hr) in CACC lane by 50% □ Reduce unreliability (planning time index) by 25% □ Reduce primary crashes 25%, secondary crashes 50% □ Reduce fuel consumption, emissions by 25% INFLO USDOT Lead: Mohammed Yousuf (FHWA) SPD-HARM CACC Q-WARN

29 29 U.S. Department of Transportation INFLO Mobility Application Bundle: Accomplishments and Next Steps  Accomplishments □ Broad interest and participation in stakeholder webinar 12/8, user needs workshop 2/8 □ ConOps completed, walkthrough held 4/27 with VIIC in Detroit  Upcoming Deliverables □ System Requirements, August 2012  Next Steps □ Leverage speed harmonization research planned at TFHRC and continue coordination with FHWA ATDM program □ Prototype INFLO bundle components using BSM Part 1 (CACC) and augmented BSM to support speed harmonization and queue warning INFLO Vision (from ConOps)

30 30 U.S. Department of Transportation Multi-Modal Intelligent Traffic Signal System (M-ISIG Bundle): Concepts and Project Status  M-ISIG App: Intelligent Traffic Signal System (I-SIG) □ Overarching system optimization application accommodating signal priority, preemption and pedestrian movements  M-ISIG App: Transit Signal Priority (TSP) □ More accurate monitoring of transit vehicles through intersections and corridors for priority  M-ISIG App: Mobile Accessible Pedestrian Signal System (PED-SIG) □ Automated pedestrian call sent to the traffic controller from the smart phone of registered users  M-ISIG App: Freight Signal Priority (FSP) □ Provides signal priority along an arterial corridor near a freight facility  M-ISIG App: Emergency Vehicle Preemption (PREEMPT) □ Adjusts preemption and signal recovery cycles under multiple emergency responses  Project Status □ Jointly funded by Cooperative Transportation System Pooled Fund Study (CTS PFS) and the DMA Program, CTS PFS includes FHWA, VDOT and state and local agencies □ ConOps, SyRS and Test Planning will carry forward to Spring 2013, follow-on prototyping in Arizona and California test beds in 2013 M-ISIG USDOT Lead: Ben McKeever (FHWA)

31 31 U.S. Department of Transportation Response, Emergency Staging and Communications, Uniform Management, and Evacuation (R.E.S.C.U.M.E.)  App: Incident Scene Pre-Arrival Staging Guidance for Emergency Responders (RESP-STG) □ Situational awareness information to responders while en route  App: Incident Scene Work Zone Alerts for Drivers and Workers (INC-ZONE) □ Alerts drivers of lane closings and unsafe speeds for temporary work zones □ Warns on-scene workers of vehicles with trajectories or speeds that pose a high risk to their safety  App: Mayday Relay (MAYDAY) □ Sends crash notification to a roadside DSRC hot spot  App: Emergency Comm. and Evacuation (EVAC) □ Addresses needs of evacuees with and without their own transportation  Project Status □ Draft ConOps in development □ Likely to focus on temporary work zone management (INC-ZONE) and incident response staging (RESP-STG) applications for prototyping in 2013 □ Build off of cross-cutting device development, particularly BSM generating mobile device for responders R.E.S.C.U.M.E USDOT Lead: Linda Dodge (ITS JPO)

32 32 U.S. Department of Transportation Open Source Portal Vision (from ConOps) Open Source Applications Development Portal: Project Status and Next Steps  Accomplishments □ Stakeholder needs assessment, ConOps and SyRS task completed □ Implementation task initiated, 3/12  Next Steps □ Finalize draft governance and licensing, May 2012 □ Initiate agile development for initial prototype, June 2012 □ Go-live for Open Source Portal, September 2012  Cross-cutting roles for the Open Source Portal in Phase 2 □ Support traveler information applications developed in EnableATIS phased BAA □ House and maintain algorithms and code from prototyping efforts ▪ E.g., use of single connected-vehicle algorithm predicting arrival times of vehicles in intersections (useful for multiple M-ISIG applications) □ Distribute code developed for mobile devices, including BSM emulation and DIDC prototypes


Download ppt "Quarterly Review May 8, 2012 Real-Time Data Capture and Management Program Dynamic Mobility Applications Program."

Similar presentations


Ads by Google