Zone intrusion

Draw the line.We'll watch it 24/7.

Polygon zones with class filters, schedules, and optional PLC handshake for automated e-stop. Catch forklift-pedestrian conflicts, after-hours perimeter breaches, and press-cell incursions before they become incidents.

Forklift lanesPress cellsLoading docksPerimeterRobot cellsChemical storage
The problem

The worst incidents happen where no one is watching.

Control rooms are shared. Alarms are noisy. Light curtains catch the body after it's already inside the cell.

#1
Fatality cause in warehousing and distribution.
Forklift-pedestrian incidents. 34,900 serious injuries per year in the US alone (NIOSH).
After-hours
Perimeter breaches fly under the radar.
Most sites can't staff a control room 24/7 — and motion-only alerts are noisy by 22:00.
Press cells
Exclusion zones depend on operator discipline.
Light curtains catch the body after it's already inside. You need to stop the entry, not detect it.
The solution

Four primitives cover every zone we've ever been asked to watch.

Zones, classes, schedules, and an optional PLC handshake. Compose them into rules without writing code.

Polygon zones on any feed

Draw as many zones as you need per camera. Scale to PTZ presets. Version-control every shape.

Class filters

Forbid person, vehicle, or forklift independently — or combine. Allow-lists for known equipment.

Schedules & gating

Activate rules by time-of-day, shift, or PLC input. Exclusion zones that only apply when the cell is running.

PLC handshake (optional)

Siemens S7 and Modbus TCP digital outputs. Trip a beacon, pause a line, or assert e-stop — on-appliance.

Live · DC-03 · Dock 4cam-03 · 1080p
02:41:09
1 intrusion — PLC amber beacon assertedavg inference 68 ms
Benchmarks

Technical measurements, not marketing copy.

Lab-measured figures on reference hardware. Pilot-stage deployment numbers will replace these once available.

< 150ms
Zone entry to PLC output
On-appliance — no cloud hop, lab-measured
< 180ms
P95 inference latency
NAO-A20, 1080p feed, lab-measured
4 wks
Typical PLC handshake rollout
Including OT sign-off
0
Cloud dependencies for detection
All processing on-appliance
Example rules

Three rules, copy-paste-ready.

Visual editor in the UI — YAML export for version control and OT peer review.

Forklift lane · pedestrians forbiddenyaml
rule: zone-forklift-lane
area: polygon("Forklift Lane A")
schedule: always
forbidden_class: person
allowed_class: forklift
min_confidence: 0.82
dwell_seconds: 1
on_violation:
  - notify: teams("#ops-dc-03")
  - plc_out: "lane_a.amber_beacon"
  - snapshot: s3://evidence/zones/
Press cell · active-only exclusionyaml
rule: zone-press-cell-5
area: polygon("Press 5 Exclusion")
forbidden_class: person
when:
  plc_in: "press5.cycle_active"   # Siemens S7
dwell_seconds: 0
on_violation:
  - plc_out: "press5.estop"
  - notify: teams("#press-ops")
  - log: siem("safety.press5")
Perimeter · after-hours onlyyaml
rule: zone-perimeter-night
area: polygon("East Perimeter")
schedule: daily 22:00-05:30
forbidden_class: person, vehicle
dwell_seconds: 3
on_violation:
  - notify: sms("on-call-security")
  - escalate_after: 90s
  - snapshot: s3://evidence/zones/
Model & data

The model that ships with every zone-intrusion release bundle.

Every release bundle carries a signed model card and datasheet. The cross-repo contract below is what the on-appliance inference stack enforces at load time.

Architecture
RF-DETR-Nano detector + BYTETrack multi-object tracker
Detection in a single forward pass; association across frames keeps the track identity stable through occlusions.
ONNX signature
input: 1x3x640x640 · output: detection boxes + class probs
Frozen across releases — changing it requires a coordinated core-library update.
Classes used
person, forklift, agv, pallet-jack, vehicle, negative-background.
Zone-intrusion rules filter by class and apply per-zone dwell thresholds.
Entry-to-alert latency
< 150 ms to PLC digital-out, lab-measured.
Class recognition included; no cloud hop. Field-measured latencies pending first pilot.
PLC handshake
Siemens S7, Allen-Bradley CIP, Modbus/TCP, OPC-UA.
Outbound write to a digital coil or OPC-UA tag; optional inbound interlock read.
Weight provenance
Allowlisted sources only — Apache-2.0 or MIT.
Training refuses to start if the base checkpoint is not in configs/weight_allowlist.yaml.
Integration

Entry → PLC output, measured in milliseconds.

Events flow from the camera through the on-appliance event bus to your operator tooling. Everything stays on-premise until the last hop.

01
RTSP camera
Fixed coverage of the zone — 1080p at 15 fps is plenty.
02
On-appliance inference + tracker
RF-DETR + BYTETrack. Track ID is stable through brief occlusion.
03
Zone evaluator
Polygon containment with dwell threshold + class filter + optional PLC-input gate.
04
PLC digital-out
Amber beacon, audio alarm, or interlock release — under 150 ms from frame.
05
Event bus + operator UI
MQTT detections/{camera}/zone_intrusion → dashboard + SIEM.
ROI estimate

What continuous monitoring replaces, in labour hours.

A conservative calculator. Adjust the inputs to your reality. The only number that appears is the one your inputs produce.

formula: (minutes × checks × days / 60) × €/h

Labour hours avoided per year
375 h
At your hourly cost
20,625 / year

Incident-cost avoidance and regulatory-fine exposure are NOT included — those are customer-specific and the founder does not publish estimates without real pilot data.

Mark the zone. Sleep better.

Send us a clip of the area you need watched. We'll draw the zones and return a live preview running on your actual footage.

PLC handshake covered by our OT integration SOW — signed off by site electrical before go-live.