IT that keeps buses on the map, fares flowing, paratransit on time.IT that keeps busesonthemapfaresflowingparatransitontime
CAD/AVL, onboard networks and fare systems run and protected, so riders get accurate arrivals and rides that show up.
Transit operations
Service riders feel within minutes
A transit agency is a fleet, a payment processor, a scheduling service and a public information office at the same time. Each depends on systems that span the admin building, the depot, dozens of vehicles on the street and vendors who host half the stack. Here’s where that service is fragile, and what we build so it isn’t.
01 · The pressure
Dispatch, fares and riders who depend on you
Dispatchers watch every vehicle on CAD/AVL and talk to operators all shift. Fareboxes and mobile ticketing feed revenue reports. Real-time data flows to arrival signs, trip planners and the agency app. Paratransit schedulers book trips for riders with disabilities who can’t wait for the next bus. Federal reporting depends on accurate ridership and mileage data. When systems go down, riders are stranded, phones light up and board members hear about it before you do.
- Dispatch tracking every vehicle on the street
- Paratransit riders who can’t wait for the next bus
- Ridership data feeding federal reports
Trapeze PASSClever Devices CleverCADAvail myAvailSwiftlyMasabi JustrideEsri ArcGISMicrosoft 365
02 · How it breaks
Depot Wi-Fi, vendor tunnels and phished schedulers
Vehicles download schedule and software updates over depot Wi-Fi that shares a password with the break room. Onboard routers keep factory admin credentials. Several vendors hold standing remote access into CAD/AVL and fare servers, and nobody is sure which tunnels are still used. A scheduler’s mailbox gets phished, exposing rider eligibility files. Ransomware on the admin network spreads to the dispatch servers because everything shares one flat network.
- Depot Wi-Fi shared between buses and break room
- Onboard routers left on factory credentials
- Flat networks linking admin PCs to dispatch
Trapeze PASSClever Devices CleverCADAvail myAvailSwiftlyMasabi JustrideEsri ArcGISMicrosoft 365
03 · What we change
Segmented depots and controlled vendor access
We separate admin, dispatch, depot vehicle networks, fare systems and public Wi-Fi into distinct segments with firewall rules between them. Onboard routers get unique credentials and central management. Vendor access to CAD/AVL and fare servers moves to a brokered, logged path. Schedulers and finance staff get phishing-resistant MFA. Fare systems are scoped and hardened for PCI. Changes inside vehicle electronics stay with the OEM and integrator.
- Depot, dispatch, fare and admin networks separated
- Onboard routers centrally managed with unique logins
- Vendor tunnels brokered and logged
Trapeze PASSClever Devices CleverCADAvail myAvailSwiftlyMasabi JustrideEsri ArcGISMicrosoft 365
04 · The after
Service that keeps running on a bad day
If an admin PC gets compromised, dispatch keeps tracking buses because the networks aren’t connected. Your fare data and PCI scope are documented when the processor asks. Paratransit rider files are protected by access controls and MFA, not just a shared drive password. When the board or a federal reviewer asks about cybersecurity, you show inventories, vendor access logs and a tested recovery plan instead of reassurances.
- Dispatch isolated from admin-side incidents
- Fare systems documented for the processor
- Recovery plan tested, not theoretical
Trapeze PASSClever Devices CleverCADAvail myAvailSwiftlyMasabi JustrideEsri ArcGISMicrosoft 365