Aurora Board Meeting Des Moines, Iowa Thursday, December 1, 2005

1. Proof of Concept Demonstration Selection Criteria for the Clarus Initiative Aurora Board Meeting Des Moines, Iowa Thursday, December 1, 2005 Road Weather Management

2. Proof of Concept (PoC) • What is it? • A small scale demonstration to implement and test the design of the Clarus System • Limited in the number of collectors that will provide data to the Clarus System • Provides valuable insight and input into all aspects of system design • The results of the PoC will be used in the broader scope ‘Multi-State Demonstration’

3. Clarus Roadmap FY04 FY05 FY06 FY07 FY08 FY09 Stakeholder Coordination Track 1 System Design Track 2 Multi-State Regional Demonstration Final Design, Model Deployment Track 3

4. Proof of Concept • Partnership between FHWA and the Aurora Consortium • Acknowledge Aurora member participation at ICC and Task Force Meetings • Recognize Aurora interest/sponsorship • It is not meant to solicit open competition between Aurora members • It is open to U.S. State DOTs

5. Selection Criteria • The Selection Criteria Sheet is only guidance as a tool to help gauge ITS capabilities and State DOT support • Minimum requirements: • have personnel willing to support a demo • routinely collect RWIS/ESS data, • provide RWIS/ESS to MADIS*, and • must be a U.S. State (PoC is not Int’l)

6. Aurora Consortium Member States (Fall 2005) 20/10 154/83 56/90 58/43 43/40 169/44 31/20 60/15 86/52 86/52 87/49 41/37 81/47 Map Legend: XX/YY Current MADIS Contributor Number of Fed ASOS & AWOS Number of ESS (as of 06/05)

7. Selection Structure • Aurora leadership • will be responsible for polling interest among DOT members • will negotiate with members and based on the fundamentals of the criteria worksheet can provide the top 3 recommendations for PoC participation to FHWA • Soft Deadline: If the recommendations can be provided to FHWA by the CDR, a decision may be announced before Xmas

8. State DOT Support (45 pts) • Personnel agree to be trained • Commit a minimal amount of time • Review QCh summary daily/provide feedback • Participate in monthly conference calls • Participate in Post-Demo briefing • Must share data/metadata & allow publishing of results • Commit without needing FHWA funds • Approval/Support from DOT supervisory management (not commish level)

9. ESS Network Maturity (30 pts) • Allow access through DOT firewalls to push/pull data & adjust ESS polling rates • Must have deployed at least 30 ESS • Routine ESS access at least hourly • Must provide data to MADIS • Bonus Points • Observations from mobile platforms • Collection servers from different vendors • Access to turnkey operated data products

10. Miscellaneous • Must be able to provide minimal Metadata (MADIS set) • Bonus: Provide full metadata • Supplemental observations available for QCh (at least 50% of ESS total) • Person responsible for maintaining metadata • Provide access to maintenance records • Bonus • have calibration records • identify party responsible for ESS maintenance

11. Minimum Metadata for ESS • From a MADIS data table: • |MN001|Twin Lakes I-35 Mile Post 1 • |371.1000|43.50833|-93.35406|GMT| • Station Name/Identifier (5 characters) • Long Name String (35 characters) • Station Latitude/Longitude (to 5 digits) • Station Elevation (to 4 digits) • Time Basis (Greenwich Mean Time)

12. Miscellaneous • Must be able to provide minimal Metadata (MADIS set) • Bonus: Provide full metadata • Supplemental observations available for QCh (at least 50% of ESS total) • Person responsible for maintaining metadata • Provide access to maintenance records • Bonus • have calibration records • identify party responsible for ESS maintenance

13. Graphical Metadata I-80 EB Puck Layout Diagram RWIS

14. Miscellaneous • Must be able to provide minimal Metadata (MADIS set) • Bonus: Provide full metadata • Supplemental observations available for QCh (at least 50% of ESS total) • Person responsible for maintaining metadata • Provide access to maintenance records • Bonus • have calibration records • identify party responsible for ESS maintenance

15. Distribution of ESS, ASOS & AWOS in Minnesota 83 Federal ASOS & AWOS stations are deployed across Minnesota 154 Atmospheric, Pavement & Hydrologic ESS are deployed (93 Roadside ESS with 7 more planned)

16. Miscellaneous • Must be able to provide minimal Metadata (MADIS set) • Bonus: Provide full metadata • Supplemental observations available for QCh (at least 50% of ESS total) • Person responsible for maintaining metadata • Provide access to maintenance records • Bonus • have calibration records • identify party responsible for ESS maintenance

18. Miscellaneous • Must be able to provide minimal Metadata (MADIS set) • Bonus: Provide full metadata • Supplemental observations available for QCh (at least 50% of ESS total) • Person responsible for maintaining metadata • Provide access to maintenance records • Bonus • have calibration records • identify party responsible for ESS maintenance

19. Contact Information • Clarus Initiative Managers • James Pol (James.Pol@fhwa.dot.gov) • Paul Pisano (Paul.Pisano@fhwa.dot.gov) • Primary Clarus Support Contractor • Mixon Hill, Inc. • Kyle Garrett (J.Kyle.Garrett@mixonhill.com) • Brenda Boyce (Brenda.Boyce@mixonhill.com)

20. Straw Poll • If the next MDSS Stakeholder Meeting were to be held Labor Day week 06 in Atlantic City: • Would people be willing to travel on Labor Day to have a Tues/Wed meeting? • Would people rather have a Thurs/Fri meeting? • Would this be too much if it were appended to the Eastern Snow Expo (e.g. fatigue, Watch for Dan’s 3rd glass of wine)?