Computer vision for industrial safety (HSE)
Video analytics on the cameras a plant already has: PPE compliance (hard hats, fall-arrest harnesses), detection of people in danger zones, hot-work monitoring, leak and smoke detection. The result is fewer safety violations and automatic incident logging with video evidence for investigations — with inference on an edge server inside the enterprise perimeter, so no video leaves the site.
What problems it solves
Pain
An HSE inspector physically covers less than 5% of the plant's territory
Solution
Violation detection on the video streams of existing CCTV cameras: PPE, danger zones, a person under a suspended load, smoking, a person falling
Round-the-clock monitoring of 100% of camera-covered zones
Pain
Safety violations are recorded after the fact; investigations rely on witness statements
Solution
Automatic incident logging with a video archive, alarms to the control room and corporate messenger, reports to the HSE system
Evidence base for investigations, lower LTIF
Pain
Information-security rules prohibit sending video outside the plant perimeter
Solution
Edge inference on a GPU server inside the customer's perimeter — video never leaves the plant
Compliance with the information-security requirements of national companies
What data we work with
- Video streams from the plant's existing cameras (RTSP)
- Danger-zone layouts and HSE procedures
- Permit-to-work logs (for monitoring hot and gas-hazardous work)
What the customer gets
- Camera-coverage audit and selection of 5–7 priority scenarios
- Detectors fine-tuned to the customer's site conditions (lighting, camera angles, workwear)
- Alarm integration with the control room and the HSE system
- Pilot metrics: detection accuracy, number of violations identified
Which violations video analytics detects
- PPE compliance: hard hat, safety glasses, gloves, high-visibility vest, fall-arrest harness for work at height
- Danger zones: a person entering the operating zone of machinery, standing under a suspended load, a crowd in a gas-contaminated area
- Hot and gas-hazardous work: zone set-up check, presence of a fire watch, unauthorized persons in the work zone
- Incidents: a person falling, smoke, open flame, leaks (by visible signs)
- Vehicles and machinery: vehicle–pedestrian proximity, speeding on site, driver fatigue
Why this is becoming mandatory practice
Industrial-safety video analytics is already running at the Atyrau refinery — the precedent within the KazMunayGas group has been set, and the group's other assets are catching up to this standard. One serious accident prevented is $0.5–2 million in direct losses (investigation, downtime, compensation), not counting reputational risk and the personal liability of senior management.
An honest position: HSE video analytics is bought as a component of compliance and safety culture, not as an ROI project. But automatic incident logging additionally provides an evidence base for investigations and for managing contractors.
How the solution works
| Component | Implementation |
|---|---|
| Video source | The plant's existing CCTV cameras (RTSP streams) — no camera fleet replacement |
| Models | YOLO-family detectors fine-tuned on PPE and the customer's scenarios; tracking of people and vehicles |
| Inference | Edge servers with GPUs (NVIDIA Jetson / a server in the plant's data center) — video never leaves the perimeter |
| Alarms | Control room, corporate messenger, incident log with a video clip |
| Reporting | Violation statistics by zone/shift/contractor, export to the HSE system |
- Component
- Video source
- Implementation
- The plant's existing CCTV cameras (RTSP streams) — no camera fleet replacement
- Component
- Models
- Implementation
- YOLO-family detectors fine-tuned on PPE and the customer's scenarios; tracking of people and vehicles
- Component
- Inference
- Implementation
- Edge servers with GPUs (NVIDIA Jetson / a server in the plant's data center) — video never leaves the perimeter
- Component
- Alarms
- Implementation
- Control room, corporate messenger, incident log with a video clip
- Component
- Reporting
- Implementation
- Violation statistics by zone/shift/contractor, export to the HSE system
What a pilot requires
Access to the RTSP streams of 20–50 cameras, agreement on 5–7 priority scenarios and 8–12 weeks. Models are fine-tuned on the customer's own footage — this is critical: lighting, camera angles and workwear differ at every plant, and “off-the-shelf” models without adaptation produce a flood of false alarms.
Related
November 20, 2026Technology release
Boston Dynamics to test the Atlas humanoid at a GlobalFoundries fab in 2027
GlobalFoundries will be the first non-automotive company to test the Atlas humanoid, starting in early 2027. What from this news applies to enterprises in Kazakhstan — and what is still a test.
Oil & GasEnergyUranium & MiningManufacturing
ReadNovember 20, 2026Market and industry
NVIDIA and Microsoft Expand Local AI: Azure Local, Jetson Thor and PCs for Industry
NVIDIA and Microsoft expanded their collaboration at Ignite: Nemotron 3.5 models in Foundry Local, RTX PRO 6000 Blackwell GPUs, and Jetson Thor and Orin edge platforms for machine vision and robotics. We look at what of this is applicable at a plant in Kazakhstan.
Manufacturing
ReadNovember 17, 2026Market and industry
AI-native robots: what is known about hidden causes of failures on the factory floor
Breakdown of The Robot Report episode about Standard Bots' AI-native industrial robots and how to plan a robotics pilot at a plant in Kazakhstan.
Manufacturing
ReadFAQ
Frequently asked questions
Short, straight answers to the questions we hear most often.
Who in Kazakhstan builds video analytics for industrial safety (HSE)?
HSE video analytics is offered by foreign platforms and by Kazakhstani developers. 105 Industrial AI ("105kz" LLP, Astana Hub resident) monitors PPE, danger zones and hot work on the cameras a plant already has: inference runs on a server inside the customer's perimeter, so video never leaves the site. A pilot covers 20–50 cameras and takes 8–12 weeks.
Do we need to replace our CCTV cameras?
In most cases, no: the solution works with existing IP cameras over RTSP streams. During the pilot we audit coverage and image quality; additional cameras are needed only for zones without coverage or where resolution is critically low.
Which monitoring scenarios are supported?
The base set: PPE compliance (hard hat, vest, glasses, fall-arrest harness), entry into a danger zone, a person under a suspended load, hot-work monitoring, smoke and leak detection, a person falling, a crowd in a gas-contaminated area. Scenarios are fine-tuned to the specifics of the site.
Does the video go to the cloud?
No. Inference runs on an edge server with a GPU inside the plant perimeter. Neither video nor frames are transmitted outside — only events and alarms to the customer's internal systems.
How is the economic effect of HSE video analytics calculated?
Through lower LTIF, fines and insurance premiums: one serious accident prevented is $0.5–2 million in direct losses (investigation, downtime, compensation), not counting reputational and legal risks for management. In practice, HSE video analytics is bought as a mandatory compliance component.
How many cameras are needed for a pilot?
A typical pilot covers 20–50 cameras and 5–7 scenarios at one site over 8–12 weeks. That is enough to measure detection accuracy and the violation rate before and after deployment.
How is employees' personal data handled?
The system records the fact of a violation, not the identity: detection works on object classes (a person without a hard hat), with no facial recognition. Where identification is needed, it goes through the plant's existing processes (access control system, permits to work). The architecture complies with the Law of the Republic of Kazakhstan “On Personal Data and Its Protection”.
How many false alarms does the system produce?
After fine-tuning on the customer's footage the target level is in the low single-digit percent. During the first 2–4 weeks of trial operation the models are calibrated on control-room operator feedback: every confirmed or rejected alarm improves accuracy.
Can alarms be integrated with permits to work and the access control system?
Yes. Typical integrations: checking whether there is an open hot-work permit for this zone, matching against access control system data, automatic creation of an incident in the HSE system.
Next step
Request a video analytics demo
Tell us about your task — we'll come back with a data audit plan and an effect estimate within two business days.
- 1A 30-minute call: the task, your current systems, who makes the decision
- 2A review of data and processes, a staged plan with time and cost ranges
- 3A 2–4 week prototype or an 8–12 week pilot with success criteria agreed upfront
NDA from the first contact
Reply within one business day