EM10-Disaster Traveler Information Transaction Set Diagram



Get the Source Graphic, a Windows Metafile (WMF), in ZIP format.
More about ZIP files

The following discusses how the National ITS Architecture provides the transportation service described by this service package. Each numbered item describes the operation of that portion of the service package identified with the corresponding number on the transaction set diagram.

Note that this transaction set diagram (TSD) is only 1 of the 2 TSDs and so only a portion of the numbered items below refer to the above TSD.

EM10 transaction set diagrams: 1 2 Next TSD

  1. The entire process is under the asynchronous monitoring (ISP operations information presentation) and control (ISP operator inputs) by the ISP Operator.

  2. Concurrently and asynchronously, information is collected by the Information Service Provider from many sources. The ISP collects from the Emergency Management Subsystem information characterizing the disaster (incident information), its impact on the transportation system and alternative transportation services that are available (transportation system status), and evacuation instructions and information (evacuation information).

  3. The ISP collects care facility information, identifying permanent and temporary facilities providing emergency healthcare, including facility type and capabilities, facility status, and ability to admit new patients (care facility status).

  4. The ISP collects weather information, including weather watches and warnings and other severe weather information (weather information) as well as weather information tailored to surface transportation (transportation weather information) based on request parameters (transportation weather information request).

  5. The ISP collects travel service information from Yellow Pages Service Providers, including information on basic travel services in the disaster area, along evacuation routes, and at evacuation destinations. Services include lodging, restaurants, fueling stations, retail, rest areas, and restrooms. This information can be tailored based on a travel service information request.

  6. The ISP collects transit service information, including special transit services supporting transport in the disaster area and evacuation (emergency transit schedule information).

  7. The ISP collects current traffic and road information for the disaster area, evacuation routes, and evacuation destinations (road network conditions and incident information) from the Traffic Management Subsystem (TMS). This includes detours and restrictions, closure information, road conditions, and current and forecast traffic conditions.

  8. The ISP collects shelter information from Shelter Providers, including location, hours of operation, special accommodations, and current vacancy/availability information.

    Information collected by the ISP from some sources may come as the result of a specific request or be obtained through subscriptions. With subscriptions, providers may send periodic or as-needed updates.

  9. Asynchronously, and as often as desired, Travelers may enter requests for information (traveler inputs) into the Personal Information Access Subsystem (PIAS) (e.g. personal computing device). Requests may be for personalized evacuation route information, information for a particular route in a disaster area, or any other specific traveler request. The traveler request could be satisfied locally based on information that was previously downloaded, but more likely, the request is in turn made to the ISP (emergency traveler information request). This request elicits a specific response (emergency traveler information) from the ISP. This information is provided to the Traveler by the PIAS through visual or audio means (traveler interface updates). The cycle of request and response may be repeated as often as needed. A single request may identify the area of interest and register a user for future updates, depending on implementation. Also, emergency traveler information may be provided as broadcast or multicast information, without need for an explicit request message.

  10. In a similar manner, Drivers may make information requests (driver inputs) and then an emergency traveler information request and corresponding emergency traveler information may be exchanged between a Vehicle and an ISP, and the result (driver updates) are returned to the Driver. This allows drivers to receive updated emergency traveler information while en-route.

  11. In a similar manner, Travelers may enter requests (traveler inputs) into the Remote Traveler Support Subsystem, RTS (e.g., kiosks at rest stops, shelters, etc.) and then an emergency traveler information request and corresponding emergency traveler information may be exchanged between the RTS and an ISP, and the result (traveler interface updates) is returned to the Traveler.

  12. Emergency traveler information is also made available over voice-based traveler information systems like 511. Information (voice-based traveler information) is made available in response to traveler requests (voice-based traveler request).

  13. Emergency traveler information is also made available to shelter providers, for use in informing shelter users of current travel conditions, reentry information, and other emergency travel information.

  14. Systems such as reverse 911 systems that distribute salient information about an incident to the general public in a precise geographic area may also be used. In the architecture, this is represented by the incident information for public flow to the Emergency Telecommunications System.

  15. Emergency traveler information is also made available to the media (incident information for media).