What it means
Track trespass detection identifies confirmed occupancy inside a mapped rail danger zone, such as a trackbed, tunnel mouth, or right-of-way boundary.
Why it matters
The physical zone determines urgency. A person on a platform and a person inside the rail envelope are different events.
Evaluation questions
Is the rail envelope mapped in the camera view?
Can authorized maintenance be separated from public intrusion when the scene supports it?
Where does the alert route in the control-room workflow?
Continue Exploring
Track trespass detection
Review the rail use case and alert workflow.
Platform architecture
Review how DHI runs inference, event routing, and camera ingest.
Edge AI safety evaluation guide
Use a structured checklist to evaluate platform fit before a pilot.
Pricing and pilot scope
Understand what changes the final pilot and rollout scope.
Validate track trespass detection in a real pilot.
Use your current cameras, VMS, and response workflow to test whether the concept works in one defined zone.
The checklist is built for operators evaluating a live pilot in the next 30 days.
Request a demo
See the flow on a real operating scenario and scope a pilot around one facility or corridor.
See deployment architecture
Review camera ingest, edge inference, alert routing, and what stays on-premises.
Get the implementation checklist
Download the deployment checklist buyers use before green-lighting an industrial AI pilot.
Talk to an engineer
Bring camera count, VMS constraints, latency expectations, and privacy requirements to a technical review.