An end-to-end solution for the railcar
End-to-end solution — from sensor in railcar to OCC
TRAFFIQ delivers an end-to-end solution for the railcar: cameras and sensors, analysis on board, and an event that reaches the control room — violence, running, fire and documentation, with no data leaving to the cloud. The solutions we offer are deployed worldwide, at different security levels. All of it runs while the railcar is moving.
Violence · alert in the railcarRunning in the aisleEnd-to-end · deployed worldwideTransport standardOccupancy heat map
One railcar, an end-to-end solution
Tap a zone in the railcar and see what TRAFFIQ sends the control room
This is an end-to-end solution: cameras and sensors in the railcar, analysis on board, and an event in the control room — no raw stream to the cloud. The same solutions are deployed worldwide, at different security levels.
One railcar, an end-to-end solution
Analysis unit
This is where analysis runs inside the railcar — part of an end-to-end solution, without sending raw video out. It keeps working while the railcar is moving, even when space is tight.
What actually gets seen
Eight layers in an end-to-end solution for the railcar
01
Violence events
A fight, a blow, a violent surge in the aisle or by the door. The control room receives a frame and context — not a passenger’s identity.
02
Running in the railcar
A run down the aisle is an early sign: panic, a chase, or someone trying to pass between railcars in motion. The threshold is tuned to the railcar, not a generic catalogue.
03
Fire and smoke
Smoke and heat as an early layer, including a thermal sensor beside the video. It sits with a certified fire system — it does not replace it.
04
Documenting the railcar
A local video record for investigation, coaching and evidence. Documentation stays on the railcar and on your network — it is not uploaded to the cloud by default.
05
An end-to-end solution in the railcar
From the sensor to the control room: analysis on board, an event at the desk, with no data leaving to the cloud. The same model is deployed worldwide, at different security levels.
06
Cameras and extra sensors
Rugged video for the railcar, thermal, audio, and sometimes radar or an occupancy sensor. We do not stop at one lens — we build a sensing layer for that railcar.
07
Information security without the cloud
Analysis runs in the railcar. Data does not leave. That is not a slogan — it is architecture: no raw stream to an outside vendor.
08
And more, to the actual need
Violence, running and fire are examples. We analyse and specify many other solutions from what actually happens in your railcars — not from a closed shelf list.
09
Heat maps for occupancy
A heat map of the railcar shows where it packs, where it stays empty, and where someone is still there after the stop — without identifying a passenger. Occupancy for the control room, not a ticket count.
10
Transport standard
Fit-out and gear go through what the railcar is already bound by: the transport standard, fire, electromagnetic compatibility and motion endurance. There is no generic install that skips the approval.
How it is actually built
Standard, algorithm, privacy, heat map — and scenarios the system can still take
Transport standard
A railcar is not a shelf in a warehouse. Gear and software line up with the vehicle’s transport standard: vibration, fire, EMC, full operation in motion. Without that approval there is no solution.
Our algorithm
The algorithm runs in the analysis unit in the railcar. It turns cameras and sensors into an event a control room already knows how to read — not a generic model sitting in a cloud and asking for the stream.
Keeping privacy
Privacy here is not a sticker. Raw video does not leave. There is no passenger identity by default. The control room gets a frame and context, and the operator keeps the footage.
Heat maps for occupancy
The heat map shows how the railcar fills along the run: door, aisle, seats. Occupancy for the control room and for operations — without building a file on a person.
Many other scenarios
Violence, running and fire are examples. The system can take many other scenarios from what actually happens in your railcars: a door left open, someone still there, a blocked aisle, and more according to procedure.
Israel rail, in motion
Stations and railcars the analytics layer is built for
Israel Railways and light rail — free photographs, not a hosted film.
Three steps
End-to-end — without replacing the control room you already built
1
We specify your railcar
A custom-made solution: which events matter, which cameras and sensors you already have, and where there is a gap. There is no single pack for everyone — and it is fitted to your security level.
2
We fit an end-to-end solution in the railcar
Cameras, sensors and on-board analysis — end to end, rugged gear, and the approvals the railcar requires. Processing runs in motion. That is how we deploy the solution worldwide, at different security levels.
3
The control room gets a decision, not another screen
An alert with a frame, a zone in the railcar and a confidence — into tools already open. Raw video stays with you. A person decides what happens next.
Want your railcars on a single picture?
Start with a short pilot of an end-to-end solution: one railcar, a handful of tailored scenarios, written success criteria. Accuracy is measured on your fleet — in the same approach deployed worldwide, at different security levels.