Regional Architecture Logo
 

Send Your Comments

E-Mail

Center Secure Area Sensor Management Equipment Package

Architecture Geographic Scope

Description:

Management of security sensors, analysis of sensor data, correlation with surveillance data and alerts from other agencies to detect potential threats, and dissemination of threat information to other agencies. Sensors may be placed in areas such as transit stops, transit stations, rest areas, park and ride lots, modal interchange facilities, on-board a transit vehicle, etc.

 

Included in:

City of Livingston Fire/Police/EMS Dispatch and PSAP
City of Lufkin Fire/Police/EMS Dispatch and PSAP
City of Nacogdoches Police/Fire Dispatch
County Public Safety Dispatch and PSAP
Municipal Public Safety Dispatch

Functional Requirements:

1The center shall remotely monitor and control security sensor data collected in secure areas including facilities (e.g. transit yards) and transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and transit railways or guideways). The types of security sensor data include environmental threat (e.g. chemical agent, toxic industrial chemical, biological, explosives, and radiological sensors), infrastructure condition and integrity, intrusion and motion, and object detection sensors. The data may be raw or pre-processed in the field.
2The center shall remotely monitor and control security sensor data collected in traveler secure areas, which include transit stations, transit stops, rest areas, park and ride lots, and other fixed sites along travel routes (e.g., emergency pull-off areas and travel information centers). The types of security sensor data include environmental threat (e.g. chemical agent, toxic industrial chemical, biological, explosives, and radiological sensors), intrusion and motion, and object detection sensors. The data may be raw or pre-processed in the field.
3The center shall remotely monitor and control security sensor data collected on-board transit vehicles. The types of security sensor data include environmental threat (e.g. chemical agent, toxic industrial chemical, biological, explosives, and radiological sensors) and object detection sensors. The data may be raw or pre-processed in the field.
4The center shall exchange security sensor data with other emergency centers.
5The center shall identify potential security threats based on collected security sensor data.
6The center shall verify potential security threats by correlating security sensor data from multiple sources.
7The center shall perform threat analysis based on correlations of security sensor and surveillance data.
8The center shall exchange threat analysis data with Alerting and Advisory Systems and use that data in local threat analysis processing.
9The center shall disseminate threat information to other agencies, including traffic, transit, maintenance, rail operations, and other emergency management centers.
10The center shall respond to control data from center personnel regarding security sensor data collection, processing, threat detection, and threat analysis.
  

User Service Requirements (fully or partially addressed):

2.0PUBLIC TRANSPORTATION MANAGEMENT
2.4PUBLIC TRAVEL SECURITY
2.4.1PTS shall include specific Secure Areas.
2.4.1.2All public Secure Areas shall have traveler activated alarms monitored by central dispatch or local police.
2.4.1.3There shall be silently activated alarms and/or audible alarms on board public transit vehicles which are capable of activation by the operator, monitored by central dispatch or local police.
2.4.2PTS shall include a Security Sensors (SS) function.
2.4.2.1SS shall provide sensor technology required to alert operators and police of potential incidents.
2.4.2.2SS shall include video and audio systems at key locations, including rest areas, transit stops and stations, and transit facilities (i.e., transit yards and shops), to monitor activities, incidents, and potential threats. These systems and sensors shall be monitored by central dispatch.
2.4.2.3SS shall include threat sensors such as chemical agent, toxic industrial chemical, biological, explosives, and radiological sensors on board transit vehicles (bus, rail car) and at key locations, including transit stations, and transit facilities (i.e., transit yards and shops), to monitor activities, incidents, and potential threats. These systems shall be monitored by central dispatch.
2.4.2.4SS shall include systems on board the public transit vehicle (bus, rail car) for video, audio (including covert microphones that can be triggered by the transit vehicle operator), and event recorder (i.e., "black box") outputs to monitor activities, incidents, and potential threats. These systems and sensors shall be monitored by central dispatch.
2.4.2.5SS shall include sensors for metal (and other object) detection on board the public transit vehicle (bus, rail car), and at key locations, including rest areas, transit stops and stations, and transit facilities (i.e., transit yards and shops), to detect contraband, such as knives, guns, and other potential weapons.
2.4.2.6SS shall include a method of intrusion detection (or motion detection) at transit facilities (i.e., transit yards and shops).
2.4.2.7SS shall include video, audio, intrusion (or motion) detection, and infrastructure integrity monitoring of transit infrastructure (rail track, bridges, tunnels, bus guideways, etc.).
2.4.2.8SS shall include the capability for biometric analysis of video images.
2.4.2.9SS shall include integration of sensor inputs and possible threat analysis.
2.4.2.10SS shall include sharing of sensor information with appropriate security agencies or systems to assist in analysis of possible threats.
2.4.2.11SS shall include notification of appropriate security agencies or systems regarding potential threats.
4.5HAZARDOUS MATERIAL SECURITY AND INCIDENT RESPONSE
4.5.0ITS shall include a Hazardous Materials (HAZMAT) Security and Incident Response (HSIR) service.
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.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.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.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.2.2SS shall allow operators to monitor and control operation of surveillance and sensor devices including operator override.
5.1.3.2.3SS shall allow operators to verify an alarm.
5.1.3.3RSEM shall include a Security Alarm (SA) function.
5.1.3.3.2Secure areas shall include automatically activated alarms for natural disasters, terrorist threats, fire, theft, vandalism, etc.
5.1.3.3.3Secure Areas shall have operator-activated alarms.
5.1.3.3.4Alarms for Secure Areas shall be received from other agencies.
5.1.3.4RSEM shall include a Monitor Alert Levels (MAL) function.
5.1.3.4.1MAL shall monitor alert levels and threat information provided by federal, state, and local emergency management and public safety agencies.
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.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.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.
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.