Regional Architecture Logo
 

Send Your Comments

E-Mail

Mayday Support Equipment Package

Architecture Geographic Scope

Description:

This Equipment package receives Mayday messages, determines an appropriate response, and either uses internal resources or contacts a local agency to provide that response. The nature of the emergency is determined based on the information in the mayday message as well as other inputs. This package effectively serves as an interface between automated mobile mayday systems and the local public safety answering point for messages which require a public safety response.

 

Included in:

City of Laredo Emergency Communications Center
US Border Patrol Dispatch Center

Processes:

5.1.1Identify Emergencies from Inputs
5.1.2Determine Coordinated Response Plan
5.1.3Communicate Emergency Status
5.1.6Process Mayday Messages
5.2Provide Operator Interface for Emergency Data
  

User Service Requirements (fully or partially addressed):

4.5HAZARDOUS MATERIAL INCIDENT RESPONSE
4.5.0ITS shall include a Hazardous Materials (HAZMAT) Incident Response (HIR) service.
4.5.1.1HIN shall include the capability to provide enforcement and HAZMAT response teams with timely and accurate information on cargo contents when the vehicle is involved in an incident.
4.5.1.2HIN shall be capable of providing the following Information :
4.5.1.2(a)Time of incident.
4.5.1.2(b)Location of the incident.
4.5.1.2(c)The material(s) involved.
4.5.3HIR shall include a Communications (COMM) function.
4.5.3.1COMM shall provide the capability for distress signals to be sent to a focal point.
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 faster notification when travelers are involved in an incident.
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.2EMERGENCY VEHICLE MANAGEMENT
8.0MAINTENANCE AND CONSTRUCTION MANAGEMENT
8.1MAINTENANCE AND CONSTRUCTION OPERATIONS
8.1.1Maintenance and Construction Operations shall provide a Maintenance Vehicle Fleet Management (MVFM) function to schedule and dispatch, monitor and track location, and monitor operational condition and maintenance requirements of public and contracted fleets of maintenance, construction, and specialized service vehicles. This function includes interactions among Traffic Managers, Supervisors, Dispatchers, Field Crews, Construction Crews, Vehicle Maintenance Crews, Equipment Maintenance Crews, Weather Services Organizations, and Information Service Providers.
8.1.1.6MVFM shall be capable of providing dispatchers and operators of maintenance, construction, and specialized service vehicles with information regarding potential and actual roadway problems.
8.1.1.6.1MVFM shall provide information to dispatchers and vehicle operators, including but not limited to:
8.1.1.6.1(b)Incidents
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 06-14-2003 using Ronald C. Ice and Associates Web Spinner Technology.