Railways & Subways
Track and tunnel intrusion, train surfing, platform-edge crowding and unattended luggage, in the visual conditions underground stations actually have.
Read More
Transportation Security: Four Estates, One Platform
Transit is four estates, not one. A tunnel platform, a bus shelter, an airport concourse and a motorway junction have almost nothing in common physically, and the same operator problem: too many cameras, too few people watching, and incidents that are rare until they are not.
The Pattern
One Platform, Four Very Different Estates
What changes between a metro network and a bus corridor is not the software. It is the camera specification, the connectivity, and who receives the alert. An underground platform has hostile lighting and reflections but excellent fiber; a bus shelter has good daylight and no fiber at all. The same detectors run in both, configured differently.
The rare-event problem is what these estates share. Someone on the track, dangerous crowding at a platform edge, and abandoned luggage almost never happen, which is exactly why generic analytics fail at them and why IREX built the training data deliberately, with transport authorities and with synthetic 3D environments.
Pick the estate you actually operate. Each page below describes the deployment for that estate rather than a transit story in general.
Facts
- Connectivity
- Direct fiber where it exists, high-availability edge where it does not, and a single cost-effective edge server at small stops.
- Offline Resilience
- Edge sites keep recording when the link drops and synchronize events automatically once it returns.
- Datasets
- Built with transport authorities and with synthetic 3D environments, because these incidents are too rare to learn from naturally.
By Estate
Choose Your Transit Estate
Bus Shelters & Transit Stops
A dispersed estate with variable connectivity, where a single edge server per stop is usually the right answer rather than a fiber run.
Read MoreAirports & Seaports
High-throughput terminals and port estates: watchlist recognition, unattended luggage, weapons at access points and crowd density at peak.
Read MoreRoads & Highways
The road side of the same mobility problem: multi-camera enforcement, incident and debris detection, and transit-priority and yield violations.
Read MoreFAQ
Do all four estates need the same cameras?
No, and that is the point of separating them. Each module sets its own resolution and placement requirements, which a site survey confirms per estate: an underground platform, a bus shelter and a motorway gantry are three different specifications running the same detectors.
Can one deployment cover a whole transport authority?
Yes. The multi-tenant architecture puts users in a hierarchical catalog of groups, each granted specific cameras, watchlists, locations and monitors, so a network tier and individual depots or corridors share a platform without sharing everything.
Do we have to replace our cameras?
No. Reusing the existing fleet is the standard deployment model: any camera that supports ONVIF or streams RTSP with H.264 or H.265 on a static IP can be connected, and each module then sets its own resolution and placement requirements, which a site survey confirms. Note that connection is not plug-and-play: a qualified network engineer configures each camera and router.
Who owns the data?
You do. Customers retain 100% ownership and control of their data, and IREX neither owns nor accesses customer video, events, logs, watchlists, or floor plans. On-premises deployment is the data-residency mechanism.
How do we start?
With a pilot: one site, three to five use cases, six to twelve weeks, and two or three measurable success criteria agreed in writing before it begins. Accuracy is benchmarked on your own cameras, and the measured numbers go into the contract.
Start with One Station
A single station or corridor, instrumented properly, tells you more about a network program than a paper study of all of them.