Public Safety & Mission Software for Transit & Transportation
Public Safety and Mission Software for Transit Agencies
Incident systems, control center situational awareness, and field applications for transit agencies running their own security operations.
A transit agency runs a public safety operation without being a public safety agency. The operations control center watches vehicles, stations, and tunnels around the clock. A transit police or security department takes reports, responds to calls, and answers to safety oversight. Neither group owns the systems the other depends on. When something happens on a platform at rush hour, the controller watching the camera, the supervisor in the field, the responding officer, and the city or county 911 center taking calls from riders are all working from different screens and different versions of the same event.
The systems were bought separately, for good reasons: a scheduling and vehicle location package, a video management system for stations and vehicles, a dispatch and records product for the police unit, and alarm consoles that arrived with the elevators, the traction power equipment, and the tunnel ventilation. Each one works. What no agency buys is the layer that puts an incident in one place and keeps it consistent as it moves from a radio call to a report to a safety record to a federal filing.
What these environments look like
- An operations control center where vehicle location, radio, alarm, and video run on separate consoles rather than a single picture
- A transit police or security department with its own computer-aided dispatch and records system, or a contract with a local law enforcement agency whose systems the transit agency cannot see into
- Video across stations, platforms, garages, and onboard vehicles, with onboard recordings that offload only when a vehicle returns to the yard
- Passenger emergency intercoms, platform call boxes, and elevator phones that route to whoever is staffing the control center
- Fixed guideway infrastructure with its own monitoring: traction power, signals, ventilation, elevators and escalators, bridges and tunnels, each with its own vendor console and alarm vocabulary
- Field staff working from vehicles and platforms, including supervisors, fare inspectors, and security officers, on cellular coverage that disappears underground
- Safety and security event reporting to the National Transit Database, a safety plan built on safety management system principles, and, for rail fixed guideway systems, a state safety oversight agency reviewing how events are investigated
Where HQT helps
- Integration between the transit police dispatch and records systems and the agency's operational systems, so an incident carries the route, run, vehicle, stop, and camera references that a controller and an investigator both need
- Data exchange with local 911 centers and partner law enforcement dispatch systems, scoped so partners get the location and vehicle detail they need without the transit agency exposing systems it should not
- A common operating picture for the control center that puts vehicle positions, open incidents, infrastructure alarms, camera locations, and active work orders on one map, with views by role
- Field and mobile applications for supervisors, inspectors, and security staff: incident and hazard reporting with photographs, capture that works offline in a tunnel and syncs on return, writing into the record the control center already sees
- Emergency management platform work: incident command forms, emergency operations center activations, service suspension and bus bridge workflows, rider and employee notification, and the data an after action review needs
- Infrastructure monitoring software that consolidates elevator, escalator, power, ventilation, and station system alarms into one prioritized console with an audit trail, and routes the ones that matter into maintenance work orders
- Monitoring and reconciliation on every interface between these systems, so a feed that stops is noticed by the agency rather than discovered during an investigation
Where transit police access state or national criminal justice databases, that part of the environment falls under the CJIS Security Policy. HQT staff assigned to that work complete the agency's background screening and security awareness training before they are given access.
How an engagement usually starts
The trigger is usually an event or a replacement. An after action review finds that the control center, the police unit, and the responding fire department each had a different understanding of where a train was and who was on it. A dispatch, records, or video system is being replaced, and every integration built around the old one has to be rebuilt as well. A new line or a consolidated control center forces the question of what belongs on the controller's screen. Sometimes it is simpler: the safety office cannot assemble the event data it reports without someone reading logs by hand.
The first step is a mapping exercise rather than a design. HQT walks every system that records something about an incident, who enters data into it, what happens to that data next, and where it stops. That takes a working session with the control center, the police or security department, the safety office, maintenance, and IT in the same room, because none of them can describe the whole path alone. The output is a picture of the seams and a short list of the ones worth closing first, sized so the first piece of work can be funded and delivered inside one budget cycle.