Published 14 October 2026 · Source-linked research prepared with AI assistance. Proposed services require an agreed scope and qualified delivery team.
A useful first question
Are the observations reliable and representative enough for the decisions this corridor needs?
A road-weather station describes conditions at its location. Drivers encounter a moving sequence of elevations, curves, bridges and microclimates. The first question is where the current measurements represent the road—and where they do not. Weatherhill proposes a bounded study of existing observations, incident records, maintenance evidence and operating requirements.
Who the study serves
DOT traffic-operations and road-weather teams, toll-road operators, concessionaires and intelligent transportation system contractors.
Before quoting, confirm a budget owner, the decision the work must inform and the person who can approve data access. A funding announcement or a sector-wide problem is not a substitute for those three facts.
Define the included work
Start with records and a small number of fixed locations. Installation, roadside work, speed-limit decisions, traffic-control design and automatic warning activation remain with the responsible authority and qualified contractors. Corridor geometry support in Exposure Watch needs a separate implementation scope.
The statement of work names the included locations, available records, interviews, specialist review and deliverables. Equipment, installation, travel and continuing monitoring are separately identified where needed. A proposed planning duration is not a promise of procurement timing.
Records needed to begin
- A defined corridor or fixed set of high-consequence locations
- RWIS station inventory, siting, maintenance and calibration records
- Available weather, incident and operations logs with time zones
- Existing decision thresholds and responsible authority
- Access and traffic-management requirements for any field visit
Use a non-confidential description for the initial inquiry. Detailed operating records should move through an agreed access and retention process after the scope is established.
What you receive
- A coverage map with station limitations and data gaps
- A time-aligned weather and operations baseline
- A sensor and communications evidence review
- A prioritized observation and maintenance plan
- A commissioning specification for a separately procured pilot
Each finding identifies its source and limitation. Missing information becomes a visible follow-up item, rather than an inferred passing answer. Recommendations distinguish actions supported by the existing record from questions requiring field evidence.
Delivery and acceptance
The buyer can trace each recommendation to an operating question, an observation gap or a documented reliability issue. The study identifies what a pilot must measure and how its data will be accepted. It does not claim to establish crash causation from a simple weather correlation.
- Agree the decision, scope and acceptance criteria.
- Reconcile the supplied records and identify missing evidence.
- Review the findings with the relevant technical owner.
- Deliver the baseline, action register and next-step recommendation.
Target delivery: 3–6 weeks after records and access. Record access, site work and specialist availability can change the schedule.
What comes next
Commission a bounded monitoring package through the incumbent ITS or engineering team, then maintain instrument and event evidence.
Ask for a fixed-fee scope after the initial fit review. Proposed services are subject to delivery capacity, a named technical reviewer and written terms. The inquiry is a request to scope work; no payment or contract is created here.
Sources & further reading
- FHWA EDC News: Weather-Responsive Management Strategies ↗I-77 roughly $7.5M, 12 miles, nearly 75% fewer low-visibility crashes; 2013–2022 fatal-crash weather context.
- USDOT FHWA Weather Data Environment catalog ↗Existing road-weather data collection, quality checks and archive.
- Grants.gov PROTECT FY2024–2026 opportunity 363732 ↗$787M; October 9, 2026 deadline; closed as of research date.
- NIST — Community Resilience Planning Guide A Playbook ↗Guide and current planning resources. Recovery targets tied to community functions and supporting infrastructure.