Physical Object: Emergency Management Center
Emergency Secure Area Sensor Management
Overview
'Emergency Secure Area Sensor Management' manages sensors that monitor secure areas in the transportation system, processes the collected data, performs threat analysis in which data is correlated with other sensor, surveillance, and advisory inputs, and then disseminates resultant threat information to emergency personnel and other agencies. In response to identified threats, the operator may request activation of barrier and safeguard systems to preclude an incident, control access during and after an incident or mitigate impact of an incident. The sensors may be in secure areas frequented by travelers (i.e., transit stops, transit stations, rest areas, park and ride lots, modal interchange facilities, on-board a transit vehicle, etc.) or around transportation infrastructure such as bridges, tunnels and transit railways or guideways. The types of sensors include acoustic, threat (e.g. chemical agent, toxic industrial chemical, biological, explosives, and radiological sensors), infrastructure condition and integrity, motion and object sensors.
This functional object is included in the "Emergency Management Center" physical object.
This functional object is included in the following service packages:
This functional object is mapped to the following Functional View PSpecs:
Requirements
# | Requirement |
---|---|
01 | The 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. |
02 | The 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. |
03 | The 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. |
04 | The center shall exchange security sensor data with other emergency centers. |
05 | The center shall identify potential security threats based on collected security sensor data. |
06 | The center shall verify potential security threats by correlating security sensor data from multiple sources. |
07 | The center shall perform threat analysis based on correlations of security sensor and surveillance data. |
08 | The center shall exchange threat analysis data with Alerting and Advisory Systems and use that data in local threat analysis processing. |
09 | The center shall disseminate threat information to other agencies, including traffic, transit, maintenance, rail operations, and other emergency management centers. |
10 | The center shall respond to control data from center personnel regarding security sensor data collection, processing, threat detection, and threat analysis. |
11 | The center shall request activation of barriers and safeguards on request from center personnel. |
12 | The center shall maintain the status of the security sensor field equipment. |
Information Flows
Standards
Currently, there are no standards associated with the functional object itself though the interfaces may have standards associated with them.