Regional Architecture Logo
 

Send Your Comments

E-Mail

Center Secure Area Surveillance Equipment Package

Architecture Geographic Scope

Description:

Management of security surveillance devices and analysis of that data to detect potential threats. Areas under surveillance may include 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 video images and audio surveillance 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 data may be raw or pre-processed in the field.
2The center shall remotely monitor video images and audio surveillance 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 data may be raw or pre-processed in the field.
3The center shall remotely monitor video images and audio surveillance data collected on-board transit vehicles. The data may be raw or pre-processed in the field.
4The center shall exchange surveillance data with other emergency centers.
5The center shall identify potential security threats based on collected security surveillance data.
6The center shall verify potential security threats by correlating security surveillance data from multiple sources.
7The center shall remotely control security surveillance devices in secure areas including facilities (e.g. transit yards) and transportation infrastructure (e.g. bridges, tunnels, interchanges, roadway infrastructure, and transit railways or guideways).
8The center shall remotely control security surveillance devices 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).
9The center shall remotely control security surveillance devices on-board transit vehicles.
10The center shall match traveler video images against a database from the Alerting and Advisory Systems of known images that may represent criminals and terrorists.
11The center shall exchange traveler images with other emergency management centers to support traveler image matching.
12The center shall respond to control data from center personnel regarding security surveillance data collection, processing, threat detection, and image matching.
  

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.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.
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.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.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.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.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:
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.