Office of Operations
21st Century Operations Using 21st Century Technologies

Collaboration Across the Road Weather Enterprise: The Pathfinder Project

CHAPTER 6. GUIDANCE FOR PATHFINDER PROJECT STANDUP

LINKS TO FEDERAL INITIATIVES

The expansion of the collaborative model nationwide has been supported by initiatives at federal headquarters for both the Federal Highway Administration (FHWA) and the National Weather Service (NWS), such as:

  • The Strategic Highway Research Program 2 (SHRP2) Capability Maturity Model (CMM).
  • The Weather-Ready Nation (WRN) Roadmap.

The SHRP2 CMM provides transportation agencies with a tool to improve transportation system management. It was refined for several sub-topics, including road weather management (RWM). The model classifies the mature program as one that operates with a high degree of collaboration with the weather community before an event and proactively messages the public. Recommended tasks for maturing in the area of collaboration with the weather enterprise include:

  • Establish lines of communications between Department of Transportation (DOT) and identified meteorologists.
  • Create an email list of points-of-contact in the weather community.
  • Institute a list serve for exchange of coordination information.
  • Develop standard operating procedures for coordination.
  • Establish and attend local joint meetings between the weather and transportation communities to discuss road weather management.
  • Hold post-event debriefings between DOT staff and the weather community.
  • Establish methods for archiving weather data and forecasts.

The establishment of the collaborative relationship is optimized when there is a dedicated weather position within the DOT, when joint meetings are made routine prior to hazardous weather events, and when NWS, private sector and academic resources are integrated into DOT operational procedures. These are the traits of a mature Road Weather Management Program (RWMP).

PARTNERS' RESPONSIBILITIES THROUGHOUT WEATHER EVENTS

There are numerous facets to State DOTs, the weather forecasting offices (WFOs) and, when present, DOT-contracted weather service providers. This section provides an overview of the responsibilities of each partner as they relate to operating procedures during hazardous weather events. The following section refines the responsibilities to interaction and relationship-building among the partners.

Refer to Appendix E to Learn More
For additional details on Federal initiatives.

Tyler Elkins, traffic operator, works in the control room during an open house at the Utah Department of Transportation's Traffic Operations Center in Salt Lake City, Wednesday, Oct. 30, 2013. He monitors situations that impact traffic and sends out messages to the public.

Figure 9. Photo. Traffic Operations Center.
(Source: Utah Traffic Operations Center)

Pathfinder Testimonial

"Before Pathfinder, working together was often disjointed because there were misunderstandings, and a lack of knowledge and end goals. After Pathfinder, relationships improved, communication was more consistent and action-oriented. Pathfinder helped build structure and an organized path of communication between all parties involved."

- Vice President of Road Weather/Meteorologist, DayWeather, Inc.

STATE DEPARTMENT OF TRANSPORTATION

State DOT traffic management and maintenance operations function in real time. A few of their typical operational responsibilities (both general and storm-specific) are listed in Table 1. Due to the intrinsic nature of weather in DOT resource allocation, planning divisions have weather- related responsibilities as well. The financial needs of DOT operations change from year to year with changes in the weather, updates to operational methodologies, and the availability of technological advances. Therefore, planning divisions should remain intimately aware of the weather and climate that dictate the actions and changing nature of the DOT's operational divisions.

Table 1. Typical Responsibilities of a State Department of Transportation.

Traffic Management Responsibilities

Maintenance Operations Responsibilities

General Responsibilities:

Manage traffic and incidents (weather is considered an incident).

Maintain highways and infrastructure.

Maintain (a pre-determined) level of service (LOS) through traffic control devices and techniques.

Maintain (a pre-determined) LOS through maintenance activities.

Manage Intelligent Transportation System (ITS) infrastructure signals/timing, Variable Message Sign (VMS), Variable Speed Limit (VSL), Closed-Circuit Television (CCTV), Road Weather Information System (RWIS).

Manage resources (equipment, material, etc.).

Gather information (from field devices, field crews, other agencies, other States).

Communicate (within and with traffic operations).

Disseminate information (to public, other agencies, other States).

Safety (themselves, public).

Monitor (traffic flow, road conditions, road weather).

Gather, understand, and utilize road weather information.

Share weather information with weather enterprise.

Manage performance metrics.

Event-Specific Responsibilities:

Pre-event: gather a detailed understanding of the upcoming weather, its impacts to the road system, locations and timing.

Pre-event: gather a detailed understanding of the upcoming weather, its impacts to the road system, locations and timing.

Develop a traffic management plan.

Develop a maintenance plan.

Warn travelers of expected impacts.

Prepare infrastructure (e.g., apply anti-icers, clear culverts, etc.).

During the event: continue to gather road condition and traffic information and continue to keep the public updated on road conditions, traffic speeds, and incidents.

During the event: continue to gather road weather and traffic information.

Use traffic control devices to manage travel by reducing speeds, altering traffic signal timing, offering information and alternative routes, etc.

Help to maintain mobility and safety through mitigation of weather-related hazards.

Post-event: maintain communication with the public regarding road conditions as roads are cleared and/or congestion is relieved.

Provide timely information about hazardous driving conditions and roadway or lane closures or blockages due to adverse weather conditions within 20 minutes or less from the time the conditions are observed.

Compose Word documents and convert to HTML easily online for free. Please leave this message unchanged or subscribe now for a htmlg membership.

WEATHER ENTERPRISE

"Weather Enterprise" is a term which encompasses all weather service-providing organizations within the public and private sector (including news media), each catering their forecasts and data products to their customers' needs. For the purpose of DOT-Weather Enterprise interaction, the broad field of providers is focused into two participating entities: The National Oceanic and Atmospheric Administration's (NOAA's) NWS and private road weather service providers.

NATIONAL WEATHER SERVICE

The NWS is a division of NOAA within the U.S. Department of Commerce. Its nationwide offices include:

  • One hundred and twenty-two (122) WFOs that cover set geographical areas called county warning areas (listed in Appendix F).
  • NWS national headquarters and regional headquarters (refer to Appendix F).
  • Thirteen (13) River Forecast Centers collocated with WFOs.
  • Nine (9) Centers for Environmental Prediction, including the Storm Prediction Center and the National Hurricane Center.

The official mission of the NWS is to "provide weather, water, and climate data, forecasts and warnings for the protection of life and property." Its stated vision is: "A Weather-Ready Nation," in which "society is prepared for and responds to weather-dependent events." To this end, the NWS has catered its forecast products to the general public and to emergency managers alike to mitigate impacts from daily weather to high-impact events. The NWS has worked to build and maintain relationships with government agencies to better understand their weather information needs. Table 2 lists a few of their typical operational responsibilities (both general and storm- specific).

Prior to a weather event, NWS forecasters assign a watch, warning or advisory designation to the event. The criteria are based on the severity of the event, as designated by numerical forecast values (e.g., snow amount, wind speed, etc.). However, recent efforts have sought to alter the thresholds for these products to expected impact, instead of numerical forecast values. For example, a winter storm is forecast to accumulate two inches of snow, which would place the event in advisory criteria. However, the precipitation is expected to occur quickly, beginning at 5 p.m. and local road temperatures have been hovering just above freezing. Snow is expected to first melt on the road surface, but quickly freeze as road temperatures drop, creating a slick layer of ice and snow. At 5 p.m., traffic volume will be high. The combined effects from the weather, road temperature and traffic would create a higher impact event than would be expected from the forecast alone. A WFO may re-assign the event to warning level for its expected transportation impact. The text contained in the forecast product would provide decision support by explaining the impact and including "call-to-action statements."

Table 2. Typical National Weather Service Operational Responsibilities.

Routine National Weather Service Services

National Weather Service Services in Support of Public Safety Officials

General Responsibilities

Produce a suite of weather, water, and climate information services, including non-routine watches, warnings, and advisories.

Partner on outreach and education efforts, including customer workshops and awareness weeks.

Disseminate observation and forecast information via legacy text products, National Oceanic and Atmospheric Administration (NOAA) Weather Radio, and digital services, including websites and social media.

Facilitate sharing of National Weather Service (NWS) forecast and observation data for use in partner information services.

Conduct community outreach and education efforts in support of a Weather-Ready Nation.

Coordinate and provide input on selection of sites for Department of Transportation (DOT) and NWS observation systems.

Build relationships with core partners and learn and document their decision thresholds and community impacts.

Coordinate seasonal meetings.

Conduct employee training to improve impact- based decision support services and situational awareness.

Interact for non-routine situations that may be critical to public safety, such as fires, hazardous materials incidents, dense fog, and dangerous conditions that are not well covered by standard NWS products.

Event-Specific Responsibilities

Provide decision support services remotely and on-site to community leaders and decision makers.

Provide Site-specific (Spot) Forecasts essential to public safety.

Serve as a conduit to media, ensuring dissemination of key messaging.

Collaborate regarding significant weather events where public safety is at risk, to include timing and impacts, and to ensure consistent public messaging.

Gather and disseminate past and current storm-related information (e.g. precipitation totals, wind speeds).

Share storm reports for use in messaging and verification.

Conduct post-event after-action reviews and surveys as deemed necessary.

Participate in post-event after action reviews.

Clean CSS files are essential for an optimized website. Free online tool by HTML Cleaner.

THE PRIVATE SECTOR

The meteorological private sector includes a range of companies that provide weather forecasts, observation-based technologies and Decision Support Systems (DSS), and/or data services to various clientele. They may be independent, associated with a media group, or contract with other companies and agencies. The forecasters are especially trained in transportation-specific weather, and their products focus on weather interaction with the road surface and with traffic mobility. Table 3 lists a few typical operational responsibilities (both general and storm-specific) for private sector entities.

There are several private weather firms serving State DOTs nationwide. Almost all of the firms provide internal operational forecasts and decision support, but the DOT may request other services, such as modeling and software development, weather instrumentation, research, data management, personnel training, collaboration with other agencies, decision support (e.g., winter maintenance treatment recommendations), and producing TI weather conditions and forecasts. During weather events, the company will usually be asked to: conduct briefings with maintenance, traffic operations, emergency managers, and others; interpret and disseminate weather observations, interact with other divisions and agencies; answer questions from DOT personnel; provide weather alerts; and so on, as requested.

Each DOT has a different working arrangement with their contractor, though there are a few DOTs that have no contracted weather support. Forecasters may be located within a Traffic Management Center (TMC), elsewhere in-state or elsewhere out-of-state. Various configurations of these arrangements will dictate the manner of collaboration between the DOT, its contractors and the NWS.

Table 3. Typical Private Sector Responsibilities.

Private Sector Collaboration

General Responsibilities

Learn the capabilities of maintenance operations.

Produce weather and road weather forecast information and/or support.

Provide decision-support for various decision-makers.

Accommodate other potential Department of Transportation (DOT) needs, such as modeling and software development, weather instrumentation and data management, personnel training, research, program management, collaboration with other agencies and producing TI weather conditions and forecasts.

Event-Specific Responsibilities

Conduct briefings with maintenance, traffic operations, emergency managers, or others.

Conduct annual event scenario response training.

Interpret and disseminate weather observations.

Interact with other divisions and agencies.

Answer questions from Department of Transportation (DOT) personnel.

Provide weather alerts.

EMERGENCY MANAGERS

Emergency management encompasses all actions to prepare for, respond to, and recover from a disaster or emergency. Sometimes you will hear about emergency preparedness or emergency response. Each State dictates when emergency management is initiated based on a set of thresholds (e.g., closure, NWS warning). After an analysis of the current and/or forecasted weather and there is an indication that thresholds will be met, the emergency management team should be included in the collaborated messages to the public. With this inclusion, all messages will be consistent and the proper information will be conveyed.

EMERGENCY RESPONDERS

Emergency responders depend on roadways to provide crucial services to individuals and communities. People who are in danger or are physically hurt rely on emergency responders to come to their rescue without being affected by the weather condition. Communication flows with emergency responders is needed at the start to insure they can effectively continue to operate without the repercussions of hazardous weather conditions. Furthermore, the very nature of hazardous weather conditions will likely increase the need for emergency responders making their inclusion even more imperative to include them when establishing collaborative relationships.

ACADEMIA

It is important to remember that academia is also an important partner to State DOT weather-related operations. Although academia's role of forecasting is rarely operational in nature, the State DOT can work with local universities or transportation institutes to conduct research or build tools to assist operations. A State DOT can also leverage the data management resources of universities to quality control and archive its road weather information systems (RWIS) data. In these ways, academia serves as an important segment of the weather enterprise.

Refer to Appendix F to Learn More
For a list of all weather forecast offices within the United States.

As mentioned in the previous section, every State DOT has a different operational configuration with their private sector contractor, and some DOTs do not have one. The operational configuration of the partners will affect how collaborative communication takes place. The following five configuration cases were identified nationwide:

  • Case 1: Private Sector Meteorologist in the TMC.
  • Case 2: Private Sector Meteorologist outside the TMC.
  • Case 3: No Private Sector Meteorologist.
  • Case 4a: Private Sector and DOT Meteorologists in the TMC.
  • Case 4b: Private Sector and DOT Meteorologists outside the TMC.

For Cases 1, 2 and 3, there is no DOT-employed meteorologist on staff. In Case 4, the DOT has an employed meteorologist. Cases 1, 2, 4a and 4b show that the physical location of the private sector meteorologists may be inside or outside of the TMC. The physical location of all partners during events will affect communication between them.

For Cases 1, 2 and 3, there is no DOT-employed meteorologist on staff. In Case 4, the DOT has an employed meteorologist. Cases 1, 2, 4a and 4b show that the physical location of the private sector meteorologists may be inside or outside of the TMC. The physical location of all partners during events will affect communication between them.

Refer to Appendix G to Learn More
Illustrates how event-specific communication flows. Media is included as an important part of the weather enterprise and an important conduit for traveler information and forecasts.

The participating State DOT should be aware of the configuration of their public and private partners, as well as any tools that would ease communication between each. This guidance will not suggest specific ways of communicating among each of these five configuration cases.

Successful collaborative partnerships arise from building relationships between all participants within the State DOT and weather enterprise. Relationships should be fostered through successive and varied joint activities throughout the year. It is important that many modes of interaction become part of standard operating procedures. Interaction methodologies should be clearly outlined and practiced regularly. While partner interaction may become a requirement in operational policy, authentic trust, open dialogue and true collaboration are built over time and

by working toward a common goal. Each partner must be willing not only to give information, but also to listen and to consider the viewpoint from the other agency. Ultimately, the purpose of the collaboration is to provide the traveling public with consistent road weather impact information so they can make better decisions, and this goal must be kept central to the effort.

In many ways, this effort is about changing operational culture at the State DOT, in the private sector, and at the NWS. Naturally, there will be disagreements with weather forecasts, specific timing, etc., but there will also be commonalities. It is imperative to the collaborative effort to look past potential disagreements and identify the commonalities in each entity's tools, resources, and expertise. Open communication will aid in developing road impact agreements.

Throughout the Pathfinder project, meteorologists on both sides needed to be reminded each time that the ultimate goal of the collaboration goes beyond having the "best" weather forecast, to having a shared impact message so the public can take appropriate action. At the same time, State DOT management must realize that putting forth the effort to collaborate pays off on the transportation system and the efficiency of their operations.

Getting Started Quick Reference Guide:
Setting Initial Collaboration Guidelines and Procedures
Identify partners
  • Determine the key points of contact across all of the key agencies, organizations and companies.
Determine qualifying collaboration events
  • Impactful precipitation events effecting travel such as high winds, etc.
Select communication mediums and set procedures
  • NWSChat
    • Decide if the chat room is private or public.
    • Initiate the conversation.
    • Discuss 3 main items until general agreement is reached:1) Impact potential 2) Location of potential impact 3)Timing of potential impact.
  • Conference calls- as necessary scheduled through chat or email.
Establish point person at each participating entity
  • Announce regular shift hours.
  • Obtain name and contact information for after hours.
  • Define lines of communication, i.e., determine who will be communicating with whom, especially doing weather events.
Synchronize forecast schedules
  • As much as possible, synchronize.
    • Releases of information to the public.
    • Schedules for Pathfinder collaboration chats and conference calls.
Establish definitions and create shared resources
  • Photo repository, PowerPoint templates, shared impact messages, dynamic message sign message templates.
Create shared Impact message for the public
  • Recognize contributions of each entity (retweet, utilize other entity's graphic on your social media post, etc.).
  • Set goals for distribution of messages based on the event type: For example, for an ice event ~ Release and distribute impact messages at least 24 hours before the event.

Conduct post event review, and archiving data, and document operating procedures.

Office of Operations