USE CASE · ATEX WORKER SAFETY AI

ATEX worker safety AI
for hazard-zone monitoring.

A LiDAR + camera pair detects when a worker enters a hazardous area — ATEX zone, crane swing radius, conveyor pull-cord zone, automated cell — and feeds slow-down or hard-stop signals into the safety PLC before the worker is at risk. Works in dust, fog and low light. Every event is logged for the safety officer's audit trail. Custom-built for your zone topology and your plant safety logic.

5–25 m typical detection range
< 200 ms typical reaction time
ATEX-aware sensor housings per zone
Auditable event log for the safety officer
USE CASE  ·  ATEX worker safety AI · LiDAR + camera fusion

Person detection in hazard zones, before the worker is at risk.

ATEX worker safety AI is a perception pipeline that detects people entering hazardous zones — ATEX areas, crane swing radius, conveyor pull-cord zones, automated-cell perimeters — and triggers PLC slow-down or hard-stop signals before the worker is at risk, with an auditable event log for the safety officer.

The pain is structural in every dust- or gas-prone plant: existing ATEX safety relies on light-curtains, RFID badges and procedural lockout-tagout. Light curtains miss anyone who walks around them; RFID badges only protect the worker who actually wore one; lockout-tagout is bypassed under schedule pressure more often than safety departments care to admit. And when an incident does happen — a near-miss, a swing-radius excursion, a pull-cord trip — there is rarely a clean record of who was where, when, and why the protection failed. Dust, smoke and low light defeat camera-only systems exactly when you need them most.

Our approach fuses two sensors per zone. A 3D-LiDAR scans the zone geometry — point clouds penetrate dust and smoke far better than RGB, so the system still sees a person when the camera does not. A high-resolution camera adds confirmation — rules out forklifts, animals and pallets that would otherwise trigger false stops. Per-zone safety distance is configured per area (a crane swing radius needs a larger margin than a robot-cell perimeter), and the redundant detection writes interlock signals into the safety PLC. Every event — detection, slow-down, stop, all-clear — goes into an audit log with timestamp, zone, person count, sensor confidence and evidence frames.

This is not an off-the-shelf safety appliance. ATEX zones, crane envelopes and plant safety logic differ per site. We treat every engagement as a discovery + fixed-scope build, descending from our hub service Industrial Perception AI. Typically four to twelve weeks from contract to live tool, with the code and the model handed over to you at the end.

„A near-miss that nobody recorded is a near-miss that will happen again."

Built by the same team that delivers our LiDAR wagon-detection pipeline — six lid centroids, sub-5 cm error, two-second response.

Three stages

From sensor to safety PLC — three stages of the pipeline.

1 · Sensor coverage of the zone

One or more LiDAR + camera pairs cover the hazardous zone with redundant overlap, so no single sensor failure leaves a blind spot. ATEX-aware sensor housings where the zone classification requires it (dust zone 22, gas zone 2, fertiliser silos, refinery process areas). Dust-tolerant optics, runs in fog, smoke and night light — the geometry channel keeps working when the visual channel struggles.

2 · Person detection + confirmation

LiDAR clusters persons by geometry — height, gait, motion signature — so the system separates a worker from a forklift or a pile of pallets. The camera confirms the detection visually, ruling out animals, vegetation and yard equipment that would otherwise trigger false stops. Per-zone safety distance is configured: crane envelopes need larger margins than a robot-cell perimeter.

3 · PLC interlock + audit log

Confirmed detections feed into the plant safety PLC as slow-down or hard-stop signals over the existing safety bus. Every event — detection, slow-down, stop, all-clear — writes into the historian or safety database with timestamp, zone, person count, sensor confidence and evidence frames. The safety officer gets an auditable trail without manual paperwork.

Pipeline architecture · #how-it-works

How the pipeline works — concretely.

We keep the architecture boring on purpose. Three loosely coupled stages, each one independently testable, each one swappable when the sensor stack changes. Built on the same stack we use across all our perception work: PCL, Open3D, OpenCV, PyTorch.

01

Multi-sensor capture in dust + smoke

Each LiDAR delivers a 3D point cloud of the zone — typically several hundred thousand points per scan, multiple times per second. Cameras add synchronised colour frames, lens-calibrated and time-stamped. Raw data writes to local storage with a per-event UUID for audit trail and re-labelling. The LiDAR channel is the resilience layer: it keeps reporting geometry when dust, fog or low light blind the camera.

02

Person classification + safety-distance calculation

The point cloud goes through ground removal, voxel down-sampling and a person classifier trained on real plant data — workers in PPE, helmets, high-vis vests, not the office benchmark. The camera image goes through a second classifier on the same target. Both heads fuse into a confirmed person track with a measured distance to the configured zone boundary. False-positive rate is tuned per zone; the safety distance is configurable per area.

03

PLC interlock + event-log write-back

Confirmed track crossing a zone boundary triggers a slow-down or hard-stop signal into the safety PLC over the existing safety bus — Profisafe, CIP Safety, or hard-wired safety outputs per project. Simultaneously the event writes into the historian or safety database: timestamp, zone, person count, confidence, evidence frames. The control-room operator sees the live overlay on the HUD; the safety officer queries the database for the audit trail.

All three stages run on an industrial PC at the zone cabinet. No cloud dependency, no external API, no licence dial-home. The code is yours at handover.

What you get

Three deliverables — from the same pipeline.

Real-time safety interlock

Slow-down and hard-stop signals into the plant safety PLC, over the safety bus or hard-wired safety outputs. The safety logic stays under your existing functional-safety regime — we feed the inputs; your safety PLC owns the decision and the certification scope.

Audit-grade event log

Every detection logged with timestamp, person count, zone, sensor confidence and evidence frames. Feeds your safety database, your historian, your incident-investigation workflow — the same temporal model we use on stockpile monitoring, applied to safety events instead of material piles.

Operator HUD

A live overlay so the control-room operator sees who is where in real time — zone outlines, active detections, current safety state per area. Same dashboard surfaces the recent event history for shift handover and supervisor reviews.

Why custom

Why a custom build — not an off-the-shelf product.

Every plant has its own ATEX zone topology, its own crane envelopes, its own safety PLC and its own lockout-tagout culture. A generic safety appliance solves the generic case; your case is not the generic case.

Zone-specific safety distance configuration

A crane swing radius needs a larger margin than a robot-cell perimeter; a fertiliser silo with explosive-dust risk needs a different reaction profile than a wood-pellet conveyor. We configure the safety distance, the reaction curve and the false-positive tuning per zone — not one global threshold for everything.

Sensor + housing selection for the actual environment

ATEX-aware sensor housings where the zone classification requires it — dust zone 22 in grain and pellet handling, gas zone 2 in refinery and chemical, dust-and-gas hybrids in fertiliser, IP66+ wash-down in foundry. We pick the housing per zone, not one catalogue option for the whole plant.

Integration with existing safety PLC + lockout-tagout

Most plants already have a safety PLC, light curtains, RFID badges and a lockout-tagout procedure. We feed our detections into what's already there as additional inputs — we do not replace your functional-safety regime. Profisafe, CIP Safety, hard-wired safety outputs and OPC UA for the non-safety audit channel all supported.

IP ownership + audit-log ownership

You own the source code, the model weights, the labelled dataset and the audit log at handover. The audit log lives in your historian, not on a vendor cloud. We document the system, train your team, and walk away clean. No black box, no monthly per-zone licence, no service contract you can't exit. See our FAQs on IP and engagement model for the standard terms.

FAQ

Questions about ATEX worker safety AI.

The engagement-model questions we hear from every plant safety officer considering a custom perception build. Need something more specific to your zone? Ask us.

Industrial Perception AI

What does custom perception AI software cost? +
We don't publish list prices because every project is scoped against your data and your decision logic — but we work to three predictable tiers. Discovery & Assessment — a 1–3 day workshop, on-site or remote, fixed price in the low-four-figure range. You receive a written feasibility note, a recommended next step and (if applicable) a fixed-price quote for the follow-on project. Useful even if you don't then go ahead — many customers use the note to evaluate two or three vendors. Custom Pipeline / Tool — a 4–12 week project delivering a working perception pipeline (parser + algorithm + dashboard or OPC UA integration). Fixed scope, fixed price, you own the code at handover. Typical project size is in the mid-five to low-six-figure range depending on data volume, sensor count and integration depth. Long-term Partnership — a monthly retainer for ongoing development and on-call support. Sized to the team capacity you need (typically 0.5–2 FTE equivalent). Quarterly road-mapping included. All three tiers include source code, written documentation and a clean handover — no licence dependence on us. See our Industrial Perception AI service for the full engagement model.
How long does it take to build a custom perception pipeline? +
From signed contract to a working tool in production, expect 4–12 weeks for a standard custom-pipeline engagement. The spread is driven by three factors. Data readiness. If you already have labelled data or representative recordings, we start training in week 1. If we need to set up data collection, add a sensor, or label from scratch, the front end adds 1–3 weeks. Integration depth. A standalone dashboard with REST output is the fastest path — typically 4–6 weeks. OPC UA integration into a running control system, with interlocks, factory-acceptance tests and a customer change-management process, is closer to 8–12 weeks. Sensor count and site complexity. One LiDAR + one camera in a clean indoor environment is faster than a six-sensor outdoor portal with dust, snow and dynamic lighting. We scope the difference up-front in the Discovery workshop. For a faster first signal we recommend the Discovery & Assessment tier — 1–3 days, fixed price, written feasibility note within a week. See Industrial Perception AI for the full model.
Who owns the code and IP we pay you to build? +
You do. Our standard contract transfers full ownership of the project-specific code, model weights, training data (where the data is yours) and documentation to you on final acceptance. We don't keep a back-door licence and we don't lock you into a maintenance contract. What we retain is our pre-existing toolbox — reusable libraries, calibration utilities, generic data parsers, the OWL EYE® core — which we license to you, royalty-free, for use on the delivered tool. This is the same boundary that any reputable engineering firm draws: we bring the toolbox, you keep the deliverable. If you want a different IP arrangement — for example a joint patent on a novel algorithm, or a co-developed model that we both reuse with consent — we structure that explicitly in the project contract. Tell us up-front in the Discovery workshop. Full engagement details on our Industrial Perception AI page.
Can you use our existing cameras and LiDAR sensors? +
Yes — in most cases. Our toolchain is sensor-agnostic on the data layer. If your sensors deliver a standard format (PCD, LAS, E57 for point clouds; RTSP, GigE Vision, USB3 Vision for cameras) we can ingest them in a day. We've worked with Riegl, Livox, Faro, Hesai, Velodyne, Ouster, Basler, FLIR, Allied Vision and IDS cameras. We'll tell you honestly when the existing hardware isn't the right tool. Common cases where we recommend a replacement: - The existing LiDAR is too narrow (FoV or range) to cover the area you want classified — usually solved by repositioning before buying anything new. - The camera is auto-exposing on a high-contrast scene (sun + shadow at a gate), which breaks classification reliability — solved by switching to a manual-exposure industrial camera with HDR sensor. - The existing sensor's vendor lock-in (proprietary stream format, no documented SDK) makes integration cost more than a Livox replacement. We don't earn a margin on reselling hardware to you. If you do want us to source new sensors, we do that through our normal Hardware & products channel at list price. See Industrial Perception AI for how we scope it.

Send us a zone map and a sample scan.

A zone layout, a few sample point clouds, a description of your existing safety PLC and lockout-tagout procedure — we come back within two business days with a written feasibility note and a fixed-price scope for the discovery workshop. Part of our Industrial Perception AI service.

info@sachtleben-technology.com +49 7831 969 22-190
Send us a message

Tell us about your hazard zone.

Zone classification, sensor setup, your safety PLC interface, your existing lockout-tagout procedure — anything you have. We come back within two business days with an honest first assessment and a fixed-price scope for the Discovery workshop.

Company address (optional)Firmenadresse (optional)Adres firmy (opcjonalnie)Indirizzo azienda (opzionale)Adresse de la société (facultatif)Dirección de la empresa (opcional)Endereço da empresa (opcional)
Direct line Direktwahl Telefon bezpośredni Linea diretta Ligne directe Línea directa Linha direta
Mon — Fri · 08:00 – 17:00 CET Mo — Fr · 08:00 – 17:00 Uhr Pn — Pt · 08:00 – 17:00 CET Lun — Ven · 08:00 – 17:00 CET Lun — Ven · 08:00 – 17:00 CET Lun — Vie · 08:00 – 17:00 CET Seg — Sex · 08:00 – 17:00 CET
Email E-Mail E-mail Email E-mail Correo electrónico E-mail
Response within one business day. Antwort innerhalb eines Werktages. Odpowiedź w ciągu jednego dnia roboczego. Risposta entro un giorno lavorativo. Réponse sous un jour ouvré. Respuesta en un día laborable. Resposta em um dia útil.
Headquarters Unternehmenssitz Siedziba główna Sede principale Siège social Sede central Sede
Sachtleben Technology GmbH
Tresdorf 6
24238 Mucheln
Germany Deutschland Niemcy Germania Allemagne Alemania Alemanha
Last updated: