Regional Architecture Logo
 

Send Your Comments

E-Mail

On-board Transit Security Equipment Package

Architecture Geographic Scope

Description:

On-board video/audio surveillance systems, threat sensors, and object detection sensors to enhance security and safety on-board a transit vehicles. Also includes silent alarms activated by transit user or vehicle operator, operator authentication, and remote vehicle disabling.

 

Included in:

ATCOG-RTD Transit Vehicles
TAPS Demand Response Vehicles
The Connection Vehicles

Functional Requirements:

1The transit vehicle shall perform video and audio surveillance inside of transit vehicles and output raw video or audio data for either local monitoring (for processing or direct output to the transit vehicle operator), remote monitoring or for local storage (e.g., in an event recorder).
2The transit vehicle shall perform local monitoring of video or audio surveillance data collected inside of transit vehicles, and identify potential incidents or threats based on received processing parameters.
3The transit vehicle shall output an indication of potential incidents or threats and the processed video or audio information to the center along with the vehicle’s current location.
4The transit vehicle shall detect potential threats via sensors for chemical agents, toxic industrial chemicals, biological agents, explosives, and radiation.
5The transit vehicle shall detect potential threats via object detection sensors(e.g. metal detectors).
6The transit vehicle shall output an indication of potential incidents or threats and the processed sensor information to the center along with the vehicle’s current location.
7The transit vehicle shall accept sensor control data to allow remote control of the sensors.
8The transit vehicle shall monitor and output surveillance and sensor equipment status and fault indications.
9The transit vehicle shall accept emergency inputs from either the transit vehicle operator or a traveler through such interfaces as panic buttons, silent or audible alarms, etc.
10The transit vehicle shall output reported emergencies to the center.
11The transit vehicle shall receive acknowledgments of the emergency request from the center and output this acknowledgment to the transit vehicle operator or to the travelers.
12The transit vehicle shall be capable of receiving an emergency message for broadcast to the travelers or to the transit vehicle operator.
13The transit vehicle shall be capable of disabling or enabling the transit vehicle based on commands from the center or authentic inputs from the transit vehicle operator.
14The transit vehicle shall perform authentication of the transit vehicle operator.
  

User Service Requirements (fully or partially addressed):

2.0PUBLIC TRANSPORTATION MANAGEMENT
2.1PUBLIC TRANSPORTATION MANAGEMENT
2.1.0ITS shall include a Public Transportation Management (PTM) function.
2.1.1PTM shall include an Operation of Vehicles and Facilities (OVF) function that provides computer assisted control of the operation of vehicles and their associated facilities.
2.1.1.1To enable the automation of the vehicle and facilities operations OVF shall provide the capability to gather the needed data to include, but not be limited to, the following:
2.1.1.1(a)Vehicle passenger loading by bus stop and trip segment.
2.1.1.1(b)Bus running times between time points.
2.1.1.1(d)Drive-line operating condition.
2.1.1.1(e)Mileage accumulated by individual buses.
2.1.1.1(f)Real-time vehicle location reports.
2.1.2PTM shall include a Planning and Scheduling Services (PSS) function to automate the planning and scheduling of public transit operations.
2.1.2.2The PSS shall include a Schedule Generation capability.
2.1.2.2.1The PSS Schedule Generation function shall collect data for schedule generation including, but not limited to, the following:
2.1.2.2.1(a)Route segment running-time.
2.1.2.2.1(b)Passenger loading at each stop.
2.1.3PTM shall include a Personnel Management (PM) function to facilitate the management of operator, and maintenance personnel.
2.1.3.1PM shall include a Maintenance Personnel Management (MPM) function.
2.1.3.1.1MPM shall automatically track vehicle miles on each bus in real-time.
2.1.3.2PM shall include an Operator Personnel Management (OPM) function.
2.1.3.2.5OPM shall provide the capability for authentication of vehicle operators prior to operating a transit bus or rail vehicle.
2.4PUBLIC TRAVEL SECURITY
2.4.1PTS shall include specific Secure Areas.
2.4.1.1(d)Riding on transit vehicles (bus and rail cars).
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.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.4PTS shall include a Security Management and Control (SMC) function.
2.4.4.1SMC shall provide the capability to receive alarm information through electronic communication systems.
2.4.4.6SMC shall include the capability to remotely disable a transit vehicle (bus or transit rail).
  
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-12-2005 using Ronald C. Ice and Associates Web Spinner Technology.