Regional Architecture Logo
 

Send Your Comments

E-Mail

Emergency Call-Taking Equipment Package

Architecture Geographic Scope

Description:

Provides interface to the emergency call-taking systems such as the Emergency Telecommunications System (e.g., 911) that correlate call information with emergencies reported by transit agencies, commercial vehicle operators, or other public safety agencies. Allows the operator to verify the incident and forward the information to the responding agencies.

 

Included in:

Angelina Neches River Authority Dispatch
City of Livingston Fire/Police/EMS Dispatch and PSAP
City of Livingston Traffic Operations Center
City of Lufkin Fire/Police/EMS Dispatch and PSAP
City of Lufkin Traffic Operations Center
City of Nacogdoches EMS Dispatch
City of Nacogdoches EOC
City of Nacogdoches Police/Fire Dispatch
City of Nacogdoches Traffic Operations Center
Concierge Service Provider
County EOC
County Public Safety Dispatch and PSAP
DPS Communications Service
Forest Service Dispatch
LA DPS Dispatch
Lower Neches Valley Dispatch
Municipal Public Safety Dispatch
Private Ambulance Dispatch
Private Hazmat Dispatch
Private Tow/Wrecker Dispatch
Regulatory Agencies
Sabine River Authority Gulf Coast Division
State EOC
TranStar and Other Texas Region TMCs
Trinity River Authority Control Center
TxDOT Lufkin District TMC

Functional Requirements:

1The center shall support the interface to the Emergency Telecommunications System (e.g. 911 or 7-digit call routing) to receive emergency notification information and provide it to the emergency system operator.
2The center shall receive emergency call information from 911 services and present the possible incident information to the emergency system operator.
3The center shall receive emergency call information from motorist call-boxes and present the possible incident information to the emergency system operator.
4The center shall receive emergency call information from mayday service providers and present the possible incident information to the emergency system operator.
5The center shall receive emergency notification information from other public safety agencies and present the possible incident information to the emergency system operator.
6The center shall receive emergency notification information from public transit systems and present the possible incident information to the emergency system operator.
7The center shall receive emergency notification information from commercial vehicles, commercial vehicle check stations, or commercial fleet operators and present the possible incident information to the emergency system operator. This may include detection of non-permitted transport of security sensitive hazmat, hazardous cargo spills, etc.
8The center shall receive details of the cargo being carried by commercial vehicles from their commercial fleet manager for incidents involving potential hazardous materials.
9The center shall coordinate, correlate, and verify all emergency inputs, including those identified based on external calls and internal analysis of security sensor and surveillance data, and assign each a level of confidence.
10The center shall send a request for remote control of CCTV systems from a traffic management center in order to verify the reported incident.
11The center shall update the incident information log once the emergency system operator has verified the incident.
12The center shall provide the capability for digitized map data to act as the background to the emergency information presented to the emergency system operator.
13The center shall forward the verified emergency information to the responding agency based on the location and nature of the emergency.
  

User Service Requirements (fully or partially addressed):

4.0COMMERCIAL VEHICLE OPERATIONS
4.3ON-BOARD SAFETY AND SECURITY MONITORING
4.3.0ITS shall include an On-Board Safety and Security Monitoring (OBSSM) function, that provides monitoring and warnings of safety and security problems. For safety related issues, the primary importance is to inform the driver, as soon as possible, of any problem that has been detected. Of secondary importance is notifying the carrier of detected safety problems. Last in importance is the notification of appropriate enforcement agencies. For security related issues, the commercial vehicle driver and authorized freight data users are informed of any problems related to freight container, trailer or commercial vehicle integrity. For commercial vehicle driver/commercial vehicle/freight container or trailer assignment mismatches, authorized freight data users are informed of a potential problem. Requirements for On-Board Safety and Security Monitoring are given below:
4.3.3OBSSM shall include a Freight Security Management (FSM) function
4.3.3.2FSM shall include a commercial vehicle driver/commercial vehicle/freight container or trailer Assignment Integrity (AI) function.
4.3.3.2.7AI shall alert authorized freight data users when a driver/commercial vehicle/freight container or trailer mismatch has been detected and verified.
4.5HAZARDOUS MATERIAL SECURITY AND INCIDENT RESPONSE
4.5.0ITS shall include a Hazardous Materials (HAZMAT) Security and Incident Response (HSIR) 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.2HSIR shall provide an Operation Focal Point (OFP) for initiating appropriate responses.
4.5.2.1OFP shall be capable of being implemented as either a centralized dispatch or several de-centralized dispatch units or vehicles.
4.5.2.2OFP shall provide the capability for existing dispatch centers to receive the calls, determine response requirements, and route distress calls to predesignated responding agencies.
4.5.2.3OFP shall provide the capability for operators to coordinate with other agencies and response services to include, but not be limited to, the following:
4.5.2.3(a)State and/or local transportation officials.
4.5.2.3(b)Police departments.
4.5.2.3(c)Highway patrol.
4.5.2.3(e)Emergency medical services.
4.5.2.3(f)Environmental protection agencies.
4.5.2.3(g)HAZMAT teams.
4.5.2.3(h)Towing and other "courtesy" services.
4.5.3HSIR shall include a Communications (COMM) function.
4.5.3.1COMM shall provide the capability for distress signals to be sent to a focal point.
4.5.3.3COMM shall provide the capability for data to be sent from any location covering all areas of the contiguous United States.
4.5.3.4COMM shall provide the capability for linkages/interfaces with various existing networks.
4.5.4HSIR shall include a HAZMAT Security (HS) function.
4.5.4.1HS shall include a security sensitive HAZMAT shipment tracking function (HSTF).
4.5.4.1.6HSTF shall include the capability to notify public safety agencies, including those having jurisdiction over the location, when a significant security sensitive HAZMAT route deviation has been detected and verified.
4.5.4.1.7HSTF shall include the capability to notify traffic management agencies when a significant security sensitive HAZMAT route deviation has been detected and verified.
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.6DA shall include the capability to notify public safety if an unauthorized driver attempts to operate the vehicle.
4.5.4.3.7DA shall include the capability to notify traffic management if an unauthorized driver attempts to operate the vehicle.
4.6FREIGHT MOBILITY
4.6.0ITS shall include a Freight Mobility (FM) function.
4.6.3FM shall include a Route Management (RM) function
4.6.3.4RM shall notify authorized freight data users when an asset deviates from its planned route or trip itinerary.
5.0EMERGENCY MANAGEMENT
5.1EMERGENCY NOTIFICATION AND PERSONAL SECURITY
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(d)Vehicle location.
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.2ENPS shall include an Automated Collision Notification (ACN) function.
5.1.2.2When sending notification of a collision ACN shall send pertinent information about the collision including the following:
5.1.2.2(b)Accurate vehicle location.
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.2RSEM shall include a Surveillance and Sensors (SS) function.
5.1.3.2.1SS shall provide surveillance and sensor technology and the data processing required to alert operators and appropriate agencies of potential incidents and threats at the Secure Areas.
5.1.3.2.1.3SS shall provide data processing based on surveillance and sensor inputs to determine when an anomaly or suspicious activity (vehicle or human) has been detected in the Secure Area and alert the operators, travelers, appropriate agencies and organizations of a security threat.
5.1.3.4RSEM shall include a Monitor Alert Levels (MAL) function.
5.1.3.4.2MAL shall assess risk based on current activities and conditions.
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.4ENPS shall include a Wide Area Alert (WAA) function to notify the public in emergency situations using ITS driver information and traveler information capabilities.
5.1.4.1WAA shall notify transportation operators and information providers when an emergency situation occurs that requires public notification.
5.1.4.1.1The WAA notification shall identify the originator, the nature of the emergency, the geographic area affected by the emergency, the effective time period, and information and instructions necessary for the public to respond to the alert.
5.1.4.1.2The WAA shall provide necessary information for emergencies including, but not limited to, child abductions, severe weather watches and warnings, military activities, civil emergencies, other natural and human-caused disaster advisories, and law enforcement warnings.
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.2.1EVM Service shall include an Emergency Vehicle Fleet Management System.
5.2.1.1Emergency Vehicle Fleet Management System shall maintain the availability status of relevant emergency vehicles.
5.2.1.2Emergency Vehicle Fleet Management System shall determine the emergency response vehicles best suited to respond to an incident.
5.2.1.3Emergency Vehicle Fleet Management System shall dispatch the appropriate emergency response vehicle (s) to the incident.
5.2.2EVM Service shall include a Route Guidance System.
5.2.2.1Route Guidance System shall maintain real-time information on traffic conditions in urban and rural areas, emergency response vehicle locations, and emergency response vehicle destinations.
5.2.2.2Route Guidance System shall advise emergency response vehicles of appropriate routes.
5.2.3EVM Service shall include a Signal Priority System.
5.2.3.1Signal Priority System shall maintain real-time information on signal timing, emergency vehicle locations and emergency vehicle routing.
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.1MAL shall monitor alert levels and threat information provided by federal, state, and local agencies to include the Homeland Security Advisory System (HSAS) and related systems for terrorist alerts, the weather forecasts, watches, and warnings issued by the National Hurricane Center, other National Weather Service components and other weather service providers, and the various early warning systems operated by federal, state, and local emergency management agencies..
5.3.2.2MAL shall increase system preparedness as the alert level or the likelihood of a disaster increases, taking actions including:
5.3.2.2(b)Pre-staging activities
5.3.2.2(d)Stage resources
5.3.2.2(e)Assign personnel
5.3.3Disaster Response shall provide a Detect and Verify Emergency (DVE) function that provides initial emergency situation information to all allied agencies.
5.3.3.1DVE shall use available sensors, weather information, and field reports to detect potential emergencies.
5.3.3.2DVE shall verify the emergency and collect available information to include location, nature of the emergency, nature and extent of the damage, nature and extent of the impact area, and potential hazards.
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.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.1RMCWPD shall coordinate information on planned maintenance and construction activities, including work zone information, and unplanned remediation activities, such as inclement weather responses, so that routing, scheduling, and resource allocation can be accomplished.
8.1.4.2RMCWP shall support inter-agency coordination of response and scheduling of resources for significant events with broad impact, like natural disasters, major incidents, and large planned or seasonal events.
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.