Regional Architecture Logo
 

Send Your Comments

E-Mail

Mayday Support Equipment Package

Architecture Geographic Scope

Description:

Collection and response to Mayday messages received from vehicles and drivers.

 

Included in:

Angelina Neches River Authority Dispatch
City of Livingston Fire/Police/EMS Dispatch and PSAP
City of Lufkin Fire/Police/EMS Dispatch and PSAP
City of Nacogdoches Police/Fire Dispatch
Concierge Service Provider
County Public Safety Dispatch and PSAP
DPS Communications Service
Lower Neches Valley Dispatch
Municipal Public Safety Dispatch
Private Hazmat Dispatch
Regulatory Agencies
Sabine River Authority Gulf Coast Division
Trinity River Authority Control Center

Functional Requirements:

1The center shall collect mayday messages from vehicles and drivers.
2The center shall collect mayday messages from travelers via personal handheld devices.
3The center shall acknowledge the request for emergency assistance, whether originated by the driver, automatically by the vehicle's safety systems, or by a traveler via a personal handheld device.
4After the mayday becomes a verified incident, the center shall determine the appropriate response to the mayday message.
5The center shall determine whether the mayday message indicates an emergency that requires the attention of public safety agencies, and forward mayday emergency data to the appropriate agency as necessary.
6The center shall support the activation of remote controlled functions requested by a vehicle, such as requests to unlock doors.
7The center shall request additional emergency details from or issue commands to the vehicle's security systems or vehicle driver if needed.
8The center shall maintain a log of all mayday signals received from vehicles.
9The center shall provide all mayday data to center personnel and respond to the vehicle, driver, or traveler using the portable handheld device as directed by the personnel.
  

User Service Requirements (fully or partially addressed):

4.0COMMERCIAL VEHICLE OPERATIONS
4.5HAZARDOUS MATERIAL SECURITY AND INCIDENT RESPONSE
4.5.4HSIR shall include a HAZMAT Security (HS) function.
4.5.4.2HS shall provide a roadside security sensitive HAZMAT security (RHS) function.
4.5.4.2.5RHS shall include the capability to notify traffic management agencies when unauthorized security sensitive HAZMAT activity has been detected and verified.
4.5.4.3HS shall include a Driver Authentication function (DA)
4.5.4.3.7DA shall include the capability to notify traffic management if an unauthorized driver attempts to operate the vehicle.
5.0EMERGENCY MANAGEMENT
5.1EMERGENCY NOTIFICATION AND PERSONAL SECURITY
5.1.0ITS shall include an Emergency Notification and Personal Security (ENPS) function that provides for automated notification when travelers are involved in an incident and security in remote areas frequented by travelers and of critical transportation infrastructure.
5.1.1ENPS shall include a Driver and Personal Security (DPS) function.
5.1.1.1DPS shall include an in-vehicle manually initiated distress signal capability to provide a first-alert that an incident has occurred to include the following:
5.1.1.1(a)Medical services required.
5.1.1.1(b)Minor property damage only crashes.
5.1.1.1(c)Breakdowns.
5.1.1.1(d)Vehicle location.
5.1.1.1(e)Vehicle identification.
5.1.1.2DPS shall include the capability to cancel a previously issued manual request for help.
5.1.1.3DPS shall include the capability to send an acknowledge signal to the motorist to indicate that the signal was received and help is on the way.
5.1.1.4DPS shall include the capability for in-vehicle sensors to automatically detect vehicle problems and in certain cases, automatically send the appropriate distress signal.
5.1.2ENPS shall include an Automated Collision Notification (ACN) function.
5.1.2.1ACN shall provide the capability to automatically identify that a collision has occurred.
5.1.2.1.1ACN shall provide the capability to instantly transmit information about the occurrence of a collision.
5.1.2.1.2The ACN crash sensors shall include the capability to provide information about the extent of crash damage.
5.1.2.2When sending notification of a collision ACN shall send pertinent information about the collision including the following:
5.1.2.2(a)That vehicle has been in a collision.
5.1.2.2(b)Accurate vehicle location.
5.1.2.2(c)Severity of collision and/or injuries.
5.1.3ENPS shall include a Remote Security and Emergency Monitoring (RSEM) function to create an environment of safety in secure areas.
5.1.3.4RSEM shall include a Monitor Alert Levels (MAL) function.
5.1.3.4.3MAL shall increase system preparedness as the likelihood of an incident increases, including:
5.1.3.4.3(a)Activating physical security systems and implementing security procedures
5.1.3.4.3(b)Adjusting parameters of surveillance and sensor devices.
5.1.3.5RSEM shall include a Physical Security System (PSS) function.
5.1.3.5.2PSS shall allow system operators to monitor and control operation of the physical security system devices, including operator override.
5.1.3.5.3PSS shall provide current status of the system including readiness and activation to operators.
5.1.4.2WAA shall use available dynamic message signs, highway advisory radio, in-vehicle displays, 511 and other telephone information systems, traveler information web sites, transit vehicle information systems, message display boards, and other information systems to provide the WAA information to the public.
5.1.4.2.1WAA shall tailor the information provided for individual driver and traveler information systems, limiting messages to short notifications for human-factors limited devices like dynamic message signs.
5.1.4.3WAA shall keep the WAA initiator apprised of the current status of public notification, including an accounting of the driver and traveler information resources that are being utilized.
5.1.4.4WAA shall notify transportation operators and information providers when public notification is no longer required.
5.1.5ENPS shall include a Protect Sensitive Traveler Information (PSTI) function to inhibit distribution of traveler information that is deemed to be sensitive.
5.1.5.1PSTI shall notify transportation operators and information providers when access to information from ITS surveillance and sensor systems must be restricted.
5.1.5.2The PSTI notification shall identify the geographic area, time, specific devices, and/or other information necessary to determine the traveler information that must be protected.
5.1.5.3PSTI shall restrict access to traveler information for the affected area until access restrictions are removed.
5.1.5.4PSTI shall notify transportation operators and information providers when traveler information access restrictions are removed.
5.2EMERGENCY VEHICLE MANAGEMENT
5.3DISASTER RESPONSE AND EVACUATION
5.3.0ITS shall provide a Disaster Response and Evacuation (DRE) function that provides for effective, coordinated management of the surface transportation system during all types of disasters including natural disasters (hurricanes, earthquakes, floods, severe winter storms, tsunamis, etc.), terrorist acts, and other catastrophic events (e.g., nuclear power plant disasters). Two primary subservices are provided: (1) Disaster Response and (2) Evacuation Coordination. The Disaster Response Subservice provides support for planning, transportation management, resource sharing, and information coordination between transportation agencies and principal responding agencies (emergency management, public safety, and other allied agencies) to improve the effectiveness and safety of a disaster response. The Disaster Response Subservice consists of eight major functions: 1) Coordinate Response Plans, 2) Monitor Alert Levels, 3) Detect and Verify Emergency, 4) Assess Infrastructure Status, 5) Coordinate Response, 6) Critical Service Restoration, 7) Manage Area Transportation, and 8) Disaster Traveler Information. The Evacuation Coordination (EC) Subservice efficiently manages an evacuation and provides evacuees with the information they need during evacuation and subsequent reentry to the evacuated area. The Evacuation Coordination (EC) subservice includes four additional major functions: 9) Evacuation Planning Support, 10) Evacuation Traveler Information, 11) Evacuation Transportation Management, and 12) Evacuation Resource Sharing.
5.3.2Disaster Response shall provide a Monitor Alert Levels (MAL) function.
5.3.2.2MAL shall increase system preparedness as the alert level or the likelihood of a disaster increases, taking actions including:
5.3.8Disaster Response shall include a Disaster Traveler Information (DTI) function that will coordinate with public information offices of the principal responding agencies in providing traveler information for the disaster scene and surrounding area to include:
5.3.8(a)Special traffic restrictions,
5.3.8(b)Detours and closures,
5.3.8(c)Special transit schedules,
5.3.8(d)Traffic conditions at and around the scene.
5.3.8(e)Special traffic allowances (HOV restrictions lifted, tolls lifted, shoulder use, reverse lane operation).
5.3.10Evacuation Coordination shall include an Evacuation Traveler Information (ETI) function.
5.3.10.8ETI shall provide road and traffic conditions on evacuation routes including:
5.3.10.8(b)Incident information
5.3.11Evacuation Coordination shall provide an Evacuation Transportation Management (ETM) function to assist evacuation coordination personnel as they manage evacuation operations.
5.3.11.6ETM shall manage incidents on evacuation routes.
8.0MAINTENANCE AND CONSTRUCTION MANAGEMENT
8.1MAINTENANCE AND CONSTRUCTION OPERATIONS
8.1.4Maintenance and Construction Operations shall provide a Roadway Maintenance Conditions and Work Plan Dissemination (RMCWPD) function to provide Intra- and Inter-agency coordination of work plans. This function includes interactions among Traffic Managers, Supervisors, Planning Agencies, Public Safety Organizations, and Information Service Providers.
8.1.4.3RMCWPD shall coordinate information with other transportation agencies, including but not limited to:
8.1.4.3(a)Public Safety
8.1.4.3(b)Emergency Medical Management
  
The detailed process and user service requirement traceability information on this page was extracted from the National ITS Architecture. Consult the National ITS Architecture web site for more information.

Last updated on 05-25-2005 using Ronald C. Ice and Associates Web Spinner Technology.