T3 Webinar Presentation

Go Ahead. Rain on My Parade: Best Practices for Developing an Integrated and Effective Road Weather Information System (RWIS) (October 13, 2009)

Presenter:   Dave Van Stensel
Presenter's Org:   Michigan Department of Transportation

HTML version of the presentation
Image descriptions are contained in brackets. [ ]
Back to Webinar Files

T3 Webinars are brought to you by the ITS Professional Capacity Building Program (ITS PCB) at the U.S. Department of Transportation's (USDOT) ITS Joint Program Office, Research and Innovative Technology Administration (RITA)


Slide 1:  RWIS Scope of Work

Dave Van Stensel, P.E.
Michigan Department of Transportation

Slide 2:  Research

[This slide contains a picture of a screenshot of software that the Colorado Department of Transportation uses to make decisions about the maintenance of their RWIS.]

  • RWIS/ESS Siting Guidelines Version 2.0
  • Maintenance Decision Support System (FHWA)
  • Other Agencies

Slide 3:  Synthesize

  • Understand what an RWIS and ESS is
  • Learn how other agencies have used RWIS and ESS
  • Take your knowledge and use it to incorporate RWIS into your agency.

Slide 4:  Concept of Operations

[This slide shows the V Model. The V Model resembles the letter "V" with the addition of two wings extending from the top left and right of the V. The V is divided into 14 steps, beginning on the top left wing and ending at the right wing. The steps are in sequence and extend down the left side of the V, to the bottom of the V, and up the right side of the V. The steps, from left to right are:

  • Regional Architecture(s) (the lone step on the left wing)
  • Feasibility Study/Concept of Exploration
  • Concept of Operations
  • System Requirements
  • High-level Design
  • Detailed Design
  • Software/Hardware Development and Field Testing (the step at the bottom of the V)
  • Unit/Device Testing
  • Subsystem Verification
  • System Verification & Deployment
  • System Validation
  • Operations and Maintenance
  • Changes and Upgrades (the first step on the right wing) and Requirements/Replacement (the last step on the right wing and last step on the V Model).
  • Opposite the steps running down left side of the V is an arrow "Decomposition and Definition." Along the bottom of the V is an arrow "Timeline." Running up, along the right side of the V, is an arrow "Integration and Recomposition." Finally, arrows within the V connect steps on the left and right sides of the V, indicating a validation process of a left side step that take place in a right side step. From top to bottom:
    • Concept of Operations (step) opposite System Validation/Initial Deployment, where the link is the Systems Validation Strategy/Plan
    • System Requirements (step) opposite System Verification/Systems Integration, where the link is the Subsystem Verification Plan (Systems Acceptance)
    • High-Level Design/Subsystem Requirements opposite Subsystem Verification /Subsystem Integration, where the link is the Subsystem Verification Plan
    • Detailed Design (step) opposite Unit Testing (step), where the link is the Unit Test Plan]

Slide 5:  Assessing Needs

  • Engage Internal Stakeholders
    • Maintenance
      • How can RWIS make it more effective?
    • Will this change how we do business?
      • If RWIS won't change the way you do business, it's a liability.
      • If you can visualize how this will change your business then you have a great topic of discussion when you engage your external stakeholders.
      • Staffing
    • Staffing
      • Head count
      • Funding sources for future operations
      • What portions of the system will be vendor operated

Slide 6:  Integration

[This slide contains two maps. The map on the bottom shows the locations of where there is a critical need for RWISs in Michigan. The top map shows the location of the existing weather stations or weather collecting sites from other agencies. This map demonstrates where collocating equipment is possible.]

  • How are we going to build our system?
  • Are we going to use existing data sources in our system?

Slide 7:  Contact Information

Dave Van Stensel, P.E.
Michigan Department of Transportation
269-337-3967
vanstenseld@michigan.gov

back to top