|
The source graphic, a Windows Metafile (WMF), for the TSDs can be downloaded here:
TSD Part 1,
TSD Part 2,
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.
-
Mayday originating from a Driver. The Driver communicates a request for Mayday service to the Vehicle subsystem (request for service). Current vehicle location is determined (position fix) and an emergency notification message is transmitted to the Emergency Management subsystem, representing a Telematics Service Provider or other center that handles mayday messages. The Emergency Management Subsystem provides the incident information to the Emergency System Operator (emergency operations status), who verifies that an incident has occurred and assistance is needed, and determines and initiates an appropriate response (emergency operations inputs). The center acknowledges receipt of the Mayday (emergency acknowledge) and maintains contact with the driver (driver updates) as a response is initiated
-
When required, the verified incident information (incident report) is provided to the appropriate responding organization (e.g., the public safety answering point covering the vehicle’s location), represented by “Other Emergency Management”.
-
Mayday originating from the Vehicle subsystem. In this case, basic vehicle measures are monitored for indicators that an incident has occurred (e.g. airbag deployment, unusual vehicle attitude, extreme acceleration/deceleration). Current location is determined (position fix) and an emergency notification message is issued to the Emergency Management subsystem (as if the message was issued by a Driver). All other operations are the same as above except that instead of an emergency acknowledge message, an emergency data request message is issued to query the vehicle subsystem for any change in incident status. Depending on the scenario, additional emergency data requests may be issued for either driver or vehicle initiated Maydays and updated information is returned (emergency notification) for each request.
-
An incident report may be issued at the same time to another Emergency Management subsystem ("Other Emergency Management") for appropriate response or mutual aid in responding to the incident.
-
Mayday originating from a Traveler with a Personal Information Access subsystem (PIAS). The Traveler communicates a request for Mayday service to the PIAS (traveler inputs), which issues the emergency notification message to the Emergency Management subsystem, which forwards the information from the traveler to the Emergency System Operator (emergency operations status). The operator returns an acknowledgment message using the same path back to the traveler (emergency operations inputs, emergency acknowledge, and traveler interface updates).
-
An incident report may be issued at the same time to another Emergency Management subsystem ("Other Emergency Management") for appropriate response or mutual aid in responding to the incident.
-
Mayday originating from a Remote Traveler Support subsystem (RTS). The Traveler communicates a request for Mayday service to the RTS (traveler inputs), which, issues the alarm notification message to the Emergency Management subsystem, which forwards the information from the traveler to the Emergency System Operator (emergency operations status). The operator returns an acknowledgment message using the same path back to the traveler (emergency operations inputs, alarm acknowledge, and traveler interface updates).
-
An incident report may be issued at the same time to another Emergency Management subsystem ("Other EM") for appropriate response or mutual aid in responding to the incident.
-
The Emergency Management subsystem may control the RTS surveillance equipment (secure area surveillance control e.g., pan/tilt/zoom for a CCTV camera) and receive secure area surveillance data including images and other surveillance data from the RTS in order to classify or monitor the incident. The actual environment that is monitored is represented by the secure area characteristics flow.
|
-
This icon indicates that the associated architecture flow either has
been or will be addressed by ITS Standards. Select the architecture flow
for more information on relevant standards activities.
