Zone Violation Detection
Entry, dwell-time and headcount rules for every polygon you draw.
The unwritten rules of a site move into software as polygons drawn over the camera view: nobody enters here, at most two people here, at most five minutes here.
A rule does not have to be static; it can be tied to machine state — the zone is red while the guard door is open and green when closed. The result is enforcement that does not slow production and catches only genuine risk.
How it works
Polygon defined
An area is drawn over the camera view; each area carries its own rule.
Person–zone intersection
The foot contact point is used, so merely appearing in frame is not a violation.
Tie it to machine state
A PLC signal or vision-based machine state activates or suspends the rule.
Not the number of violations, but their cause
A violation that repeats in the same zone is usually not a breach of the rule but a design fault: the walking route goes through it. The distribution of duration and frequency separates the zones where the rule should be redrawn from those that need a physical barrier.
| Press surroundings | 86 |
| Robot cell | 54 |
| Chemical filling | 38 |
| In front of electrical panel | 29 |
| Escape route | 17 |
70% of violations around the press occur during die changes; tying the rule to machine state eliminates the unnecessary alarms.
| W1 | 12 |
| W2 | 11 |
| W3 | 9 |
| W4 | 8 |
| W5 | 7 |
| W6 | 6 |
Once threshold calibration is complete, the remaining events are entries that carry genuine risk.
Use cases
Machine safety zone
Restricted zones around robots and presses.
Panel and transformer
Preventing unauthorized personnel entry.
Escape route
Alert when the route is blocked by material.
Crane working area
Control of entry under a suspended load.
Technical requirements
| Camera | Fixed camera seeing the zone floor; oblique angle ideal |
| Rules | Entry, dwell time, maximum headcount, time window |
| Conditioning | Dynamic activation via PLC/IoT signal or machine state |
| Integration | SCADA/PLC, alarm relay, panel, REST API |
| Verification | 10 s of pre-event footage stored per event |
Frequently asked questions
How does Zone Violation Detection work?
The unwritten rules of a site move into software as polygons drawn over the camera view: nobody enters here, at most two people here, at most five minutes here.
Are our existing cameras suitable for this solution?
Required camera specification: Fixed camera seeing the zone floor; oblique angle ideal. Before installation we assess your camera inventory free of charge and report which points are suitable and, if needed, which camera should be added.
How accurate is it in the field?
Measured accuracy: 93%. 70% of violations around the press occur during die changes; tying the rule to machine state eliminates the unnecessary alarms. Thresholds are calibrated on your own site during the pilot.
Which systems does it integrate with?
SCADA/PLC, alarm relay, panel, REST API. Events are published over REST API and MQTT, so it connects to your existing MES, ERP, VMS and alarm infrastructure.
Is it compliant with KVKK, Türkiye's data-protection law?
By default, video is processed on an on-premise server inside the facility and raw video is not sent to the cloud; if preferred, processing can also run in the cloud. Facial recognition is not used; analytics outputs are anonymous and event clips are deleted automatically when the defined retention period ends.