Clarus ICC Meeting

1
ClarusICC Meeting 4

• Washington, DC
• August 8-9, 2006

2
Agenda Day One
3
Agenda Day Two
4
Introductions

• Name
• Organization

5
HousekeepingAndy Stern

• Paul PisanoRoad Weather Program ManagerFHWA
  Office of Transportation Operations

6
Meeting Logistics

• Mitretek Systems is a secure facility
• Check in/Check out at the security desk in the
  south lobby when entering/exiting the building
• Always wear your ID in the building
• Your ID limits you to the immediate vicinity of
  the auditorium and cafeteria
• You can access the cafeteria, phones or restrooms
  at any time, unescorted
• If you have a laptop and want an outside Internet
  connection, see me during a break

7
Building Layout (first floor)
Breakout Room
8
Building Layout (second floor)
Breakout Room
Demo Center Room 2301
Stairs to 1st Floor Controlled Access
Men
Women
Elevator Lobby
9
A Final Word on Logistics

• Smoking is only permitted in the designated area
  (access thru cafeteria)
• Phones are available in food service hall
• Light refreshments will be available during
  breaks
• Cafeteria is open 7am-2pm for additional items
• 1 hour designated for lunch in the cafeteria
  pay for your own

10
Clarus OverviewPaul Pisano

• Paul PisanoRoad Weather Program ManagerFHWA
  Office of Transportation Operations

11
SAFETEA-LU, Section 5308

• Establish a Road Weather RD program
• Follow NRC report Where the Weather Meets the
  Road
• Promote Technology Transfer
• Expand Research Development
• Integrating existing observations
• Improve weather modeling forecast tools
• Enhance mechanisms for communicating information
• Integrating technologies into a broader
  infrastructure
• Multi-disciplinary stakeholder input
• NOAA - NSF
• AASHTO - Private sector
• Non-profit orgs.
• Funding 5m/yr for 4 years

12
The Clarus Initiative

• Clarus is a system that assimilates, quality
  checks, and disseminates the nations road
  weather observations
• Initiative Objectives
• Design, develop and demonstrate these
  capabilities
• Work with our public and private partners to
  develop and evaluate the value-added road weather
  information products that Clarus enables
• Establish partnerships to move from demonstration
  to deployment of a nationwide network

13
Beyond the Clarus Initiative

• The DOT-funded Clarus initiative will design,
  develop and demonstrate the value of
  assimilating, quality checking and disseminating
  road weather observations
• We are working with NOAA to make it an
  operational system

14
The Process
Societal Benefits
15
Clarus Roadmap Overview
FY04 FY05 FY06 FY07 FY08 FY09
Stakeholder Coordination
Track 1
System Design
Track 2
Multi-State Regional Demonstration
Final Design, Model Deployment
Track 3
16
Review of Clarus ICC 1

• September 2004 at University of Oklahoma
• Over 60 Participants
• Validation on approach towards developing Concept
  of Operations
• Validation on management of the ICC
• Identification and launch of task forces

17
Review of Clarus ICC 2

• March 2005 in Las Vegas
• Over 100 participants
• Validated the user scenarios of the Concept of
  Operations
• Input led to completion of the Concept of
  Operations

18
Review of Clarus ICC 3

• November 2005 in Salt Lake City
• Over 90 Participants
• Validated the Detailed Requirements for the
  Clarus System Design
• Established Critical Design Review Panel
• Established initial reviews of VII-Weather
  application development

19
ICC 4
State DOT Participants

• Nearly 90 participants!
• 21 State DOTs
• 30 Businesses
• 7 International
• 8 Federal Agencies
• 5 Academia

20
Clarus Progress to DateJames Pol

• Paul PisanoRoad Weather Program ManagerFHWA
  Office of Transportation Operations

21
Clarus System Design Documentation

• Concept of Operations
• System Architectural Description
• Architectural Alternatives Analysis
• Systems Engineering Analysis of Related Systems
• High Level Requirements Specification
• Detailed Requirements Specification
• Design Gaps Analysis
• Draft System Design Description
• All documents available- http//www.clarusinitiati
  ve.org

22
Proof of Concept Demonstration

• Implementation of the requirements design
  process
• Partnership with 3 Aurora state DOTs Alaska,
  Minnesota Utah
• Implementation Spring 06
• Demonstration Summer 06
• Report Evaluation Fall 06

PoC Participation
23
Purpose of Proof of Concept

• Exercise and Validate System Design
• Individual Test Plans for System Components
• Function Verification
• Performance Testing
• Interface Integrity
• Output Integrity
• Prepare Operating and Maintenance Instructions
• Identify System Design Weaknesses
• Documented through Test Plan results
• Development of Proof-of-Concept Test Results
  Document
• Establish System Design Correction and Enhancement

24
Proof of Concept Observation Opportunities

• Quality Checking
• Sixteen quality checks in system requirements
• Nine quality checks performed in Proof of Concept
• Addition of a Pavement Sensor Test
• Assimilation and Ingest of Data from Collector
  Sites
• Working with TMCs and other Collector entities
• Conformance to Interface Specification
• Metadata
• Real-time observations
• TMDD 2.1, CMML, NTCIP 1204
• Expandability and Extensibility of the System
  Design

25
Clarus VII (NCAR Study)

• Prepare a Feasibility and Concept Development
  Report
• Assess the potential value of using vehicle data
  to improve surface transportation weather and
  road condition observations and predictions
• Workshop 1 February, 2006
• Discussed range of weather observation needs and
  how vehicle data support such needs
• Workshop 2 June, 2006
• Validation and input to the creation of vehicle
  data element standards
• Results of this effort will enable the
  development of weather applications enabled
  through VII data

26
Clarus VII (Other Activity)

• VII Use Case Review Task Force
• Improved Weather Forecasting
• Traveler Notification with Clarus
• Winter Maintenance
• Traveler Notification without Clarus
• Pothole Maintenance
• Concept of a Weather Data Translator emerged
• Need to accommodate Fleet Vehicles established
• VII Application Development Process being
  developed

27
Path to Operations

• Strengthening partnership with NOAA
• Section 5308, SAFETEA-LU
• NOAA/FHWA MOU
• Transition of MADIS to operations (NSWOS)
• Convergence of the NSWOS and Clarus engineering
  efforts
• Building interest and expertise in using
  Clarus-related data
• Regional demonstrations

28
Goals for the Regional Demonstration(s)

• Proactive management of transportation operations
  with respect to weather conditions
• Elevated state-of-the-practice in the application
  of weather information products for state DOT
  operations
• Improved quality of weather information products
• Increased presence of road weather information in
  traveler information products

29
About ICC 4
30
Objectives for this Meeting

• Demonstrate the Clarus System Proof of Concept
  progress
• Describe and validate approach for conducting the
  Clarus Multi-state Regional Demonstrations
• Review guiding principles for policy and business
  activities for Clarus Initiative
• Update the members on VII-Weather application
  development activities

31
Additional Information

• Paul PisanoRoad Weather ManagementPaul.Pisano_at_do
  t.gov202-366-1301
• www.clarusinitiative.org