Notes
Slide Show
Outline
1
"DCM/DMA"
  • DCM/DMA  Summer Webinar Series


  • Gene McHale
  • August 10, 2011
2
Overview of Webinar
  • Purpose
    • Provide an update on DCM program status,  an introduction to Research Data Exchange Concept


  • Agenda
    • Introduction to the DCM Program
    • Research Data Exchange Concept
    • DCM Program Next Steps
    • Discussion
3
ITS Research = Multimodal and Connected
4
ITS Research Program Components
5
Mobility Program
6
"Vision"
  • 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
    • Determine required infrastructure for transformative applications implementation, along with associated costs and benefits


    • Program Partners
    • ITS JPO, FTA, FHWA R&D, FHWA Office of Operations
      BTS, FMCSA
7
Data Environments
8
Key Issues in Defining A Data Environment
9
Data Sources and Uses
10
Data Sources and Uses
11
Data Sources and Uses
12
Data Aggregation and Structure
13
Data Aggregation and Structure
14
Data Aggregation and Structure
15
Elements of Data Capture and Management
16
Elements of Data Capture and Management
  • Meta data:
    • Provision of well-documented data environment
17
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
18
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
19
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
20
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
21
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
22
Each Data Environment Supports
Multiple Apps
23

The Need for a Research Data Exchange
  • Data Environment prototyping revealed need for a complex system of multiple data environments to support application development
    • Researchers interested in organizing data in different ways for different purposes – need to support multiple collections
    • Both archived and real-time data provision (static archive not sufficient)
    • Value of local control and documentation of data
    • Single mega-archive (a.k.a., the Death Star) has high technical risk
    • Potential role of data federation – virtual, decentralized collections
24
Federated Data Environments
25

The Research Data Exchange Concept
  • The Research Data Exchange (RDE) is the connected system of data environments we envision to support application research and development
  • The RDE will not be a single, centralized repository
    • but rather a system of systems linking multiple data management systems
    • some of which will be maintained and controlled outside of the USDOT, through a common web-based Data Portal
  • Some data will be archived at USDOT within the RDE, other data will be archived outside of USDOT and federated with the RDE
26
Research Data Exchange
27
Research Data Exchange
28
Research Data Exchange
29
Research Data Exchange
30
Application Developer Example
 (without RDE)
31
Application Developer Example
 (without RDE)
32
Application Developer Example
 (without RDE)
33
Application Developer Example
 (with RDE)
34
Application Developer Example
 (with RDE)
35
Research Example (without RDE)
36
Research Example (without RDE)
37
Research Example (without RDE)
38
Research Example (without RDE)
39
Research Example (without RDE)
40
Research Example (with RDE)
41
Research Example (with RDE)
42
Research Example (with RDE)
43
Research Example (with RDE)
44
Research Example (with RDE)
45
Prototype Data Environment
  • Data (and meta-data) regarding the V2V/V2I Technology Test Bed (MI)
    • Documented probe data samples from recent tests (POC/NCAR)
    • Simulated 100% market penetration data for the test bed environs
      • contributed by the University of Michigan Transportation Research Institute (UMTRI)
    • Open source analytical tools
    • Forums for researchers to register projects, flag erroneous data, contribute analyses and data views
46
 
47
Prototype Data Environment:
Current Utilization and Insights

  • Four registered research projects using the POC/NCAR data
    • U. of Washington:  Adaptive Vehicle Routing on Arterial Networks
    • U. of Virginia: Traffic Signal Control and Performance Measures
    • PATH: Advanced Traffic Signal Algorithms
    • Virginia Tech: Traffic Responsive Signal Control


  • 1870 total visits, 723 unique visitors, 38 countries
    • Most popular features are home page and data download page
    • Steady monthly utilization, number of unique visitors continues to rise


  • Insights from the Prototype Data Environment
    • Revealed need for a complex system of multiple data environments
      • Research Data Exchange (RDE) Concept of Operations
    • Enabled internal collaboration, engaged stakeholders
      • Focal point for discussions on Open Data concepts
48
Evolution from Independent Data Sets to
Research Data Exchange
49
Incrementally Constructing the RDE:
Transition Prototype Data Environment
  • Transition POC/NCAR/UMTRI data from Prototype Data Environment
    to RDE
50
Incrementally Constructing the RDE:
Establish Real-Time Data Feed from Test Bed
  • Maintain capability to feed data directly in real-time from tests at the V2V/V2I Test Bed (Michigan) and tests at the FHWA Turner-Fairbank R&D facility
  • This same capability will be re-used for other real-time feeds connected to the RDE
    • E.g., World Congress Demo
51
Incrementally Constructing the RDE:
Incorporate Weather Program IMO Test Data
  • Integrated Mobility Observations (IMO) Test ongoing
    • Snow plow connected vehicle data from Nevada and Minnesota
    • NCAR coordinating the preparation of data from participating agency vehicles to be archived, with meta-data, within the RDE
52
Incrementally Constructing the RDE:
Incorporate Test Data Sets
53
Incrementally Constructing the RDE:
Data from Application Development/Other Tests
  • The RDE can serve as a repository for archived data from other tests
    • Data generated as part of transformative application development and testing
    • Other programs/volunteer data
  • The RDE will not serve as a junk closet, however
54
RDE Concept of Operations Document
  • Document purpose is to communicate an understanding of user needs and to describe how the system will operate to fulfill those needs.
  • The audience for the document includes:
    • System developers who will create and support the RDE
    • USDOT mobility program stakeholders
    • Analysts, researchers, and mobility application developers requiring access to research data  for analysis and application development
55
RDE Concept of Operations Document
  • Content follows IEEE Guide for Concepts of Operations, including:
    • Current System or Situation
    • Justification for and Nature of Changes
    • Concepts for the Proposed System
    • Operational Scenarios
    • Summary of Impacts
    • Analysis of the Proposed System
  • Draft RDE ConOps document is posted on….
  • We welcome your comments on the document or the concepts presented during today’s webinar
  • Comments will be addressed and a revised draft of the document will be posted on the ITS JPO website
56
Research Data Exchange (RDE):
Key Goals, 12-Month Outlook
  • Initiate RDE Development and Management procurement (Fall 2011)
  • Establish real-time data feed with V2V/V2I Test Bed (Fall 2011)
  • Incorporate new data sets
    • IMO Test Data (Fall 2011)
    • World Congress Demonstration Data (Fall 2011)
    • Test Data Sets (Winter/Spring 2012)
  • PDE-to-RDE transition (March 2012)
  • These data are our initial steps in providing a data-rich environment for transformative applications development
57
 
58
For more information …