Notes
Slide Show
Outline
1
 
2
Content
  • What are we doing?
    • Project background
    • Goals of the project
  • Why?
    • Connected Vehicle efforts /Goals
    • RWMP Roadmaps / Tracks 3 & 4
  • How / With who?
    • Vehicle Data Translator
    • Partnership with State Dots
  • What next?
3
What are we doing?
  • The IMO Project
  • Our hypothesis:
    • Weather has a significant impact on operations and maintenance activities for every agency from a staffing, equipment and budget perspective.
    • Connected Vehicle  promises new data and information on all roads in real or near real-time.
  • Areas of Potential Research
    • How do we integrate Connected Vehicle data into existing weather sources?
    • How do we integrate this new data into information  management and decision support and tools?
    • What efficiencies can be gained as a result of the improved information?
4
Why the IMO Project…?
5
How are we doing this…?
  • Enhancing the capabilities of the VDT
  • Partnering with State Dots



6
How are we doing this…?
  • Enhancing VDT
    • Developing VDT v.3.0
    • Incorporate mobile data to characterize current road weather conditions
    • Ingest, process, and facilitate the archiving of data already present in vehicle probes
    • Quality check the data
    • Ingest ancillary weather data
    • Serve as an “observation database” for decision support and other applications
7
Vehicle Data Translator (VDT) 3.0
8
How are we doing this…?
9
How are we doing this…?
10
Partnership with States…
  • Selection based on
    • Fleet
    • Maturity of the maintenance ITS program
    • Integration of mobile obs into state’s   application – MMS, MDSS, MODSS, TIS….
    • Other factors/synergies (multi-state, corridor, etc.)
    • Willingness to make data and lessons learned widely available /open source
11
Selected States
  • Minnesota


  • Nevada
12
Minnesota
  • Why
    • Mature AVL/MDSS program
    • Relatively new fleet
    • Strong upper management support
    • Strong proposal
      • Significant # of vehicles fitted for the test
      • Proposed integration with MDSS, MMS, TIS
      • Ability to collect desired data parameters (from CAN-Bus and add-on sensors)
  • Funding: Grant - 80/20
13
Why MN….
  • Project Team
    • Champion: Steve Lund
    • Project Manager: Curt Pape
    • Consultant: Ameritrak, LLC
    • NCAR: Sheldon Drobot & Mike Chapman, Brice Lambi
    •  FHWA: Paul Pisano & Gabe Guevara
14
Minnesota: Project Status / Details
    • Ameritrak is the AVL provider; has already developed and tested the prototype system:
    • Mobile Computer Device
      • AVL/GPS
      • CAN-Bus Interface
      • Interface with external sensors, sander/controller, etc.
    • Mounting brackets
    • Wiring harnesses
    • MN uses Cellular as its communication platform
  • By October/November, 2011: 140-160 Snowplow vehicles collecting and sending data
15
FHWA / NCAR / MnDOT
Parameter List
16
FHWA / NCAR / MnDOT
Parameter List (continued)
17
AT500 Transponder
Data Acquisition (DAQ)
18
2010 International
MaxxForce Truck Fleet
19
2010 International
MaxxForce Truck Fleet
20
2010 International
MaxxForce Truck Fleet
21
AT500 MDT
Main Screen
22
AT500 MDT
Road Conditions Input
23
AT500 MDT
Maps: Meridian General Radar
24
AT500 MDT
Maps: Truck-Centered Radar
25
AT500 MDT
Maps: Meridian Forecast
26
Nevada
  • Why
    • Actively pursuing an AVL/MDSS program
    • Fleet adds variety to the study (different manufacturer)
    • Strong upper management support
    • Strong proposal
      • Potential corridor-wide participation (I-80 corridor)
      • Strong partnership with academia (Univ. Nevada-Reno)
      • Proposed integration with MDSS, MMS, TIS
      • Ability to collect desired data parameters (from CAN-Bus and add-on sensors)
  • Level of Funding: 80/20 Grant
  • Accomplished so far:
    • Prototype system fully developed in-house
    • Seven units fitted with the equipment; 20 total units by November/December 2011
27
Nevada
  • Project Team
    • Champion: Rick Nelson
    • Project Manager: Denise Inda
    • Consultant: University of Nevada, Reno
      • Dr. Jeff LaCombe
      • Dr. Eric Wang
    • NCAR: Dr. Sheldon Drobot & Mike Chapman, Brice Lambi
    •  FHWA: Paul Pisano & Gabe Guevara
28
Various Weather & MDSS Data Parameters
29
Data Being Gathered
NV IMO Project (UNR/NDOT)
  • General Data
    • GPS Date, time, location, bearing, speed, altitude, accuracy
  • Road Conditions
    • Road surface temperature
    • Vehicle accelerations (surface friction)
    • Road condition images (camera)
  • Atmospheric Conditions
    • Pressure, temperature, relative humidity, dew point
    • Wind speed and direction
  • Vehicle &  Equipment Data
    • Speed, brake status, engine intake air temperature & pressure
    • Spreader and plow status
    • Steering, traction control, ABS, yaw, accelerations, emissions data, engine data, headlight and wiper status
30
Two Vehicle Types
Based in NV Districts 2 & 3 Along I-80 Corridor
31
What is next…
  • This project will be completed April 2012
  • Further refinements to the VDT
  • Continue to seek partnerships with State DOTS
  • Refinement of Standards and communication protocols
  • Work with the OEM’s to be able to access the         metadata for the parameter ID’s
  • Continue to send data to Clarus, the Prototype Data Environment, any other relevant DCM environments and contribute with the Dynamic Mobility efforts as opportunities arise.
32
FHWA Road Weather Research Team
  • Paul Pisano, Team Leader Dale Thompson
  • FHWA Office of Operations USDOT RITA, JPO
  • 202-366-1301 202-366-4876



  • Roemer Alfelor C.Y. David Yang
  • FHWA Office of Operations FHWA Off. of Operations R&D
  • 202-366-9242 202-493-3284



  • Gabriel Guevara Ray Murphy
  • FHWA Office of Operations FHWA Resource Center (IL)
  • 202-366-0754 708-283-3517