Solutions

PPE detection using your existing CCTV cameras

Automatically flag missing hard hats, vests and other required PPE in defined zones — continuously, on every shift, without replacing cameras.

PPE detection is a computer-vision application that analyses camera footage to identify people and check whether they are wearing the protective equipment required in a given area, such as a hard hat or high-visibility vest.

The problem

HSE teams can only be in one place at a time. Walk-arounds and spot checks capture a sample of what happens on the floor, usually during day shifts, and violations at shift changes, at night or in low-traffic areas go unrecorded.

Without data, it is hard to tell whether a rule is being followed, where non-compliance concentrates, or whether a training campaign actually changed behaviour.

How it works

  1. 1Video streams are read from existing IP cameras or the NVR over RTSP/ONVIF.
  2. 2A deep-learning model detects each person and classifies the PPE items configured for that zone.
  3. 3Zone, duration and schedule rules decide when a detection becomes an event (for example, "no hard hat for more than 5 seconds inside the press area").
  4. 4Events are sent to the dashboard and notification channels with a short evidence clip or snapshot, and are stored for reporting.

Existing IP cameras / NVR

RTSP / ONVIF streams

Edge device on-site

AI models + rules; video stays local

Events

Time, camera, zone, evidence frame

Dashboard, alerts, API

Notifications, relays, REST/webhook

Typical on-premise deployment. Cloud and hybrid options are also available.

What can be detected

  • Missing hard hat / helmet
  • Missing high-visibility vest
  • Other PPE items such as safety glasses, gloves or masks — evaluated per site and camera view
  • Repeated violations in the same zone or time window
  • PPE compliance trends by zone, shift and day

Typical scenarios

  • Entrances to production halls where PPE is mandatory
  • Loading docks and warehouse aisles with vehicle traffic
  • Construction or maintenance areas with temporary rules
  • Turnstile or door control where entry is refused when required PPE is not detected

Deployment options

On-premise / edge

Analysis runs on hardware inside your network. Video does not leave the site; only events and metrics are stored or shared.

Cloud

Suitable for distributed, low-camera-count sites where central management matters more than keeping video on-site.

Hybrid

Video is processed on-site, while events, dashboards and multi-site reporting are managed centrally.

Working with existing cameras

  • Standard 1080p IP cameras are usually sufficient when the person occupies a reasonable part of the frame.
  • A slightly elevated, angled view works better than a straight top-down view for helmet and vest classification.
  • Small items (glasses, gloves) need closer framing; suitability is checked on sample footage before the pilot.
  • Most IP cameras and NVRs that provide RTSP or ONVIF streams can be connected, regardless of brand.
  • Before a pilot, sample footage from each candidate camera is reviewed for resolution, angle, distance and lighting.
  • Where a view is not suitable, the recommendation is usually to reposition the camera or add one — not to replace the whole system.

Integration

  • Web dashboard and mobile notifications
  • REST API / webhook for EHS, ERP or ticketing systems
  • Relay or PLC signals for sirens, beacons or turnstiles

Privacy and security

  • No face recognition is used in safety and operations analytics; events describe what happened, not who.
  • On-premise processing keeps video inside your network.
  • Evidence clips, retention periods and user access are configurable and should follow your GDPR/KVKK policies.
  • Workplace monitoring should be introduced with clear employee information and, where applicable, consultation with employee representatives.

Limitations

  • Detection quality depends on resolution, distance, lighting and occlusion; it is measured per camera during the pilot.
  • The system identifies a PPE violation, not a person. It does not use face recognition.
  • Rules must reflect site policy — the same item may be mandatory in one zone and optional in another.

How a pilot works

  1. 01

    Discovery

    We agree on the problem, the owner, the sites and what a successful outcome would look like.

  2. 02

    Camera assessment

    Sample footage from candidate cameras is reviewed for angle, resolution, distance and lighting.

  3. 03

    Use-case definition

    Events, zones, rules, alert recipients and success metrics are written down before deployment.

  4. 04

    Pilot deployment

    Edge hardware or cloud processing is set up and connected to the selected cameras.

  5. 05

    Validation

    Detections are checked against reviewed footage; true detections, false alarms and misses are counted per camera.

  6. 06

    Report

    Results, limitations and recommended changes are documented and shared with all stakeholders.

  7. 07

    Rollout decision

    Based on measured results, you decide whether and how to expand to more cameras, sites or use cases.

Frequently asked questions

Can PPE detection work with our current CCTV cameras?

In most cases, yes. If the cameras provide an RTSP/ONVIF stream and the area is visible at a usable size, they can be analysed. Camera suitability is checked on sample footage before committing to a pilot.

Does the video leave our site?

Not in an on-premise/edge deployment. Analysis runs on hardware inside your network and only event data (and evidence clips, if enabled) is stored.

How is detection accuracy validated?

During the pilot, events are reviewed against labelled footage from your own cameras. True detections, false alarms and missed events are counted per camera so results reflect your site, not a lab dataset.

Start with the cameras you already have

Send us a few frames from your cameras and the problem you want to solve. We will tell you honestly what is feasible.