Regional Architecture Logo
 

Send Your Comments

E-Mail

Transit Center Security Equipment Package

Architecture Geographic Scope

Description:

Monitor transit vehicle operator or traveler activated alarms; authenticate transit vehicle operators; remotely disable a transit vehicle; alert operators, travelers, and police to potential incidents identified by these security features.

 

Included in:

BTD Transit Dispatch
Independent School District Dispatch

Functional Requirements:

1The center shall monitor transit vehicle operational data to determine if the transit vehicle is off-route and assess whether a security incident is occurring.
2The center shall receive reports of emergencies on-board transit vehicles entered directly be the transit vehicle operator or from a traveler through interfaces such as panic buttons or alarm switches.
3The center shall support the back-office portion of functionality to authenticate transit vehicle operators.
4The center shall exchange transit incident information along with other service data with other transit agencies.
5The center shall receive information pertaining to a wide-area alert such as weather alerts, disaster situations, or child abductions. This information may come from Emergency Management or from other Alerting and Advisory Systems.
6The center shall send wide-area alert information to travelers (on-board transit vehicles or at stations/stops) and transit vehicle operators.
7The center shall coordinate the response to security incidents involving transit with other agencies including Emergency Management, other transit agencies, media, traffic management, and traveler information service providers.
8The center shall receive threat information and status on the integrity of the transit infrastructure.
9The center shall provide support to remotely disable (or reset the disabling of) a transit vehicle in service.
  

User Service Requirements (fully or partially addressed):

1.0TRAVEL AND TRAFFIC MANAGEMENT
1.8.0ITS shall include a Travel Demand Management (TDM) function. Travel Demand Management will generate and communicate management and control strategies that will support and facilitate the implementation of TDM programs, policies and regulations. It consists of two major functions, which are, (1) Increase Efficiency of Transportation System and (2) Provide Wide Variety of Mobility Options.
1.8.1TDM shall include a communications function.
1.8.1.2The communications function shall include the capability to send information and rates needed to implement management and control strategies that respond to changing environments, conditions, and policy needs to include, but not limited to, the following locations of action:
1.8.1.2(c)Transit centers.
1.8.1.3TDM shall provide the capability to receive information and rates needed to implement management and control strategies that respond to changing environments, conditions, and policy needs to include, but not limited to, the following locations of action:
1.8.1.3(c)Transit centers.
1.8.1.4The communications function shall provide the capability to send information and data as needed to implement management and control strategies that respond to changing environments, conditions, and policy needs to include, but not limited to, the following:
1.8.1.4(c)Parking availability.
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(e)Mileage accumulated by individual buses.
2.1.1.2OVF shall include a Command and Control (CC) capability.
2.1.1.2.1CC shall provide the capability for real-time Vehicle Command and Control (VCC).
2.1.1.2.1.1VCC shall provide the capability to compare received information with predetermined operating condition specifications and note any deviations.
2.1.1.2.4CC shall include the capability for its computational capabilities to be located either on-vehicle and/or at remote locations.
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.1The PSS shall include a Planning capability.
2.1.2.1.2PSS Planning shall include processing of the data in a manner that will permit improvements in routes and services.
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(c)Revenue information.
2.1.3PTM shall include a Personnel Management (PM) function to facilitate the management of operator, and maintenance personnel.
2.1.3.2PM shall include an Operator Personnel Management (OPM) function.
2.1.3.2.3In generating fair vehicle operator assignments, OPM shall include factors relating to operators' preferences and qualifications to include, but not be limited to, the following:
2.1.3.2.3(b)Operator schedule preference.
2.1.3.2.5OPM shall provide the capability for authentication of vehicle operators prior to operating a transit bus or rail vehicle.
2.1.4PTM shall include a Communications function.
2.1.4.1PTM Communications shall provide the capability to establish two-way voice communication between vehicle operators and the central facility.
2.1.4.2PTM Communications shall provide the capability for two-way data communications between individual buses and the control facility (e.g., sensor data and bus position).
2.1.4.3OVF Communications shall provide the capability to send information from individual facilities to a central facility for processing and analysis.
2.1.4.4As support for responding to the detection of an on-board emergency, the OVF Communications shall provide dispatchers with the capability to inform the following:
2.1.4.4(a)Police.
2.1.4.4(b)Fire department.
2.1.4.4(c)Paramedic.
2.1.4.4(d)Vehicle operator (initiation of silent or audible alarm notification).
2.4PUBLIC TRAVEL SECURITY
2.4.0ITS shall include a Public Travel Security (PTS) function to create an environment of safety in public transportation, including bus transit systems and passenger rail systems.
2.4.1PTS shall include specific Secure Areas.
2.4.1.1The Secure Areas shall encompass all physical areas related to public transit travel including the following:
2.4.1.1(a)Transit (bus and rail) stop areas, including Bus Rapid Transit stops.
2.4.1.1(b)Transit (bus and rail) stations.
2.4.1.1(c)Park and Ride areas.
2.4.1.1(d)Riding on transit vehicles (bus and rail cars).
2.4.1.1(e)Kiosks.
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.2SMC shall include monitoring equipment to assist in responding to terrorist incidents.
2.4.4.3SMC shall include the capability for transit operators to direct and control fleet operations in a manner that supports law enforcement and emergency response agencies with flexible and responsive transportation for large numbers of people.
2.4.4.4SMC shall include the capability to generate coordinated preplanned responses for incidents.
2.4.4.5SMC shall include the capability to support coordinated multiple agency responses to incidents.
2.4.4.6SMC shall include the capability to remotely disable a transit vehicle (bus or transit rail).
2.4.4.7SMC shall include the capability to identify when a transit vehicle has deviated from its assigned route.
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.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.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.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.1Disaster Response shall provide a Coordinate Response Plans (CRP) function to support dissemination and coordination of emergency response plans, continuity of operations plans, and other emergency plans between agencies in preparation for a potential future disaster.
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.2(f)Clear obstructions
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.4DVE shall alert transportation agencies to disasters that have been identified by other agencies
5.3.5Disaster Response shall include a Manage Area Transportation (MAT) function that manages the transportation system in the vicinity of the disaster. Depending on the nature of the disaster and the status of the infrastructure, the following actions may be taken.
5.3.5.3Transit and transit fare schedules and toll schedules shall be modified.
5.3.9Evacuation Coordination shall provide an Evacuation Planning Support (EPS) function.
5.3.9.2EPS shall support the development of regional and multi-regional evacuation plans.
5.3.9.4EPS shall assist in defining the required resources for evacuation strategies.
5.3.10Evacuation Coordination shall include an Evacuation Traveler Information (ETI) function.
5.3.10.12ETI shall provide emergency public information including diversion information and information on refuges of last resort and other safe havens if emergency termination of an in-progress evacuation is necessary.
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.3ETM shall include a strategy selection function that maximizes efficiency during evacuation and reentry operations and supports the overall response plan of the principal responding agencies.
5.3.11.3.10The strategy shall consider the use of transit and school bus fleets during mandatory evacuations.
5.3.11.11ETM shall have the capability to monitor the location and status of transit vehicles participating in evacuation operations.
8.0MAINTENANCE AND CONSTRUCTION MANAGEMENT
8.1MAINTENANCE AND CONSTRUCTION OPERATIONS
8.1.0ITS shall provide Maintenance and Construction Operations (MCO) functions to support monitoring, operating, maintaining, improving and managing the physical condition of roadways, the associated infrastructure equipment, and the required resources. MCO shall focus on four major functions: 1) the Maintenance Vehicle Fleet Management function, to monitor and track locations and conditions of fleets of maintenance, construction, and specialized service vehicles; 2) the Roadway Management function, to monitor and forecast conditions and manage treatment of roadways during various travel conditions; 3) the Work Zone Management and Safety function, to support effective and efficient roadway operations during work zone activities; and 4) the Roadway Maintenance Conditions and Work Plan Dissemination function, to coordinate work plans and to communicate conditions. This User Service will utilize ITS systems and processes to support interchange of information among diverse groups of users, to improve efficiency and effectiveness of operational, maintenance, and managerial activities.
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.2MVFM shall be capable of supporting route scheduling and dispatching of public and contracted fleets of maintenance, construction, and specialized service vehicles.
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(a)Congestion
8.1.1.6.1(b)Incidents
8.1.1.6.1(c)Roadway restrictions
8.1.1.6.1(d)Environmental conditions
8.1.1.6.2MVFM shall be capable of filtering, fusing, processing, and presenting data from multiple weather and environmental sources.
8.1.1.6.3MVFM shall be capable of receiving fused weather and roadway information from external sources, including but not limited to:
8.1.1.6.3(a)Surface transportation sources
8.1.1.6.3(b)Weather service organizations
8.1.1.6.4MVFM shall be capable of using fused weather and roadway information from external sources to aid in scheduling roadway maintenance and construction activities.
8.1.1.6.6MVFM shall support transmission of fleet operations data to other Operations centers.
8.1.2Maintenance and Construction Operations shall provide a Roadway Management (RWM) function to monitor traffic, road surface, and environmental conditions and forecast traffic and road surface conditions to support management of routine and hazardous road condition remediation and to communicate changes in conditions. This function includes interactions among Traffic Managers, Supervisors, Dispatchers, Field Crews, Construction Crews, Asset Managers, Planning Agencies, and Weather Services Organizations.
8.1.2.2RWM shall support provision of efficient and effective roadway operations during normal and severe weather or adverse travel conditions.
8.1.2.4RWM shall determine the need for forecasted and scheduled roadway treatment.
8.1.2.4.1RWM shall be capable of filtering, fusing, processing and presenting data from multiple weather and environmental sources.
8.1.2.4.2RWM shall be capable of receiving and fusing weather and roadway information from external sources, including but not limited to:
8.1.2.4.2(a)Surface transportation sources
8.1.2.4.2(b)Weather service organizations
8.1.2.4.3RWM shall make use of information on current and forecast weather.
8.1.3Maintenance and Construction Operations shall provide a Work Zone Management and Safety (WZMS) function, which provides support for the effectiveness, safety, and efficiency of roadway operations during all work zone activities. This function includes interactions among Traffic Managers, Supervisors, Dispatchers, Field Crews, Construction Crews, Public Safety Organizations, Information Service Providers, and Travelers.
8.1.3.1WZMS shall monitor, control, and direct activity in the vicinity of work zones.
8.1.3.1.1WZMS shall provide information about work zones, including but not limited to:
8.1.3.1.1(a)Anticipated delays
8.1.3.1.1(b)Alternate routes
8.1.3.1.1(c)Suggested speed limit
8.1.3.2WZMS shall support the management of data about work zones.
8.1.3.2.1WZMS shall collect information concerning work zone activities, including but not limited to:
8.1.3.2.1(a)Location
8.1.3.2.1(b)Nature / type
8.1.3.2.1(c)Scheduled start time
8.1.3.2.1(d)Duration
8.1.3.2.1(e)Lane shifts
8.1.3.2.1(f)Staging areas
8.1.3.2.1(g)Length of work zone
8.1.3.2.1(h)Scheduled phases of work zone configuration
8.1.3.2.1(i)Alternate routes
8.1.3.2.1(j)Anticipated delays for travel route
8.1.3.2.1(k)Anticipated delays for diversion route
8.1.3.2.4WZMS shall provide information on work zone activities to other agencies, including but not limited to:
8.1.3.2.4(e)Traffic management systems
8.1.3.3WZMS shall provide systems that communicate reliable, accurate, and timely traveler information, including but not limited to:
8.1.3.3(a)Location, including lane closure information
8.1.3.3(b)Alternate route / detour
8.1.3.3(c)Work zone speed limit
8.1.3.3(d)Delay
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(c)Transit
  
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.