Occupational safety
PPE monitoring, restricted-zone entry, falls and inactivity, smoke and fire, lone working, presence under a suspended load.
Connect your existing CCTV cameras to an AI video analytics system that monitors PPE, restricted zones, attendance and vehicle movement.
An illustration of the control panel: four camera tiles — PPE monitoring, restricted zone, vehicle plate recognition and an access point. Beside them a list of event types: PPE check, restricted zone, vehicle entry. This is a demo interface, not real camera footage.
The site has cameras, but they only record. Whatever happened is usually discovered after the incident, while reviewing the archive. Here are the five situations most common on industrial sites.
Twenty or thirty cameras feed a video wall. The operator sees only a few tiles at a time; the rest go unwatched.
A worker entering without a helmet or vest is usually not logged anywhere. Yet an inspection asks for documented proof that the rules were followed.
Arrival and departure times are written by hand or entered into a logbook. Working out late arrivals and early departures per shift takes separate effort.
Finding when an incident happened means scanning hours of footage. And that is repeated not only for investigations but for routine reports.
Who entered, how long a truck waited, how long loading took — this data sits in scattered logbooks or does not exist at all.
All three directions run in a single system: one server, one control panel and shared reporting. Modules are selected for your site — you do not have to enable everything at once.
AI video analytics platform
PPE monitoring, restricted-zone entry, falls and inactivity, smoke and fire, lone working, presence under a suspended load.
RFID/NFC card entry confirmed by camera, late arrivals and early departures, reporting by shift and crew.
Licence plate recognition, entry and exit log, machine-to-person proximity, on-site speed and loading time.
Each module is enabled separately and has its own rules. Below is what each module detects and where it is useful.
Some modules (smoking, phone distraction and similar) are agreed separately, depending on site conditions and camera angle.
Accuracy depends on camera angle, lighting, distance and the real test set. Final figures are determined after the technical audit and the pilot trial.
The set of modules differs by industry. Below is the direction most sites enable first.
In open pits and underground work: PPE monitoring, restricted-zone entry and proximity to machinery. At the exit, haulage vehicles are logged through ANPR.
Helmet and vest monitoring, safety harness for work at height, the area under crane loads and attendance of contractor crews.
PPE checks at the workshop entrance, restricted zones around conveyors and equipment, attendance by shift and turnstile integration.
Forklift-to-pedestrian proximity in aisles, loading time at the dock, ANPR at the gate and detection of vehicles without clearance.
Lone working monitoring, access to tank and process zones, smoke and fire indicators, and vehicle logging at the checkpoint.
Unauthorised entry onto high-voltage yards, PPE monitoring, prolonged inactivity and an access log at substations.
The camera stream never leaves the site: analysis runs on a server on the premises, and only the notifications and reports you allow go outside.
Architecture
Video never leaves the site
Camera streams are not sent to a cloud. For industrial and government sites with strict confidentiality requirements this is usually the deciding condition.
Not dependent on the internet
Analysis continues even if the connection drops. The internet is only needed for remote panel access and outbound notifications.
Lower latency
Analysis runs on the same network as the cameras, so an alert arrives faster than a round trip to a cloud service.
The list above shows what is possible. Which of these your project includes is decided by the technical audit.
A module has to be able to see the object in the frame. That makes distance, angle, lighting and the size of the detected object decisive — resolution alone is not a sufficient criterion.
| Distance | Approximate resolution | Note |
|---|---|---|
| 3-10 m | 2 MP | Entry points, turnstiles, close-range PPE checks |
| 10-20 m | 4 MP | Inside a workshop, warehouse aisles, mid-range zone monitoring |
| Over 20 m | 4K or PTZ | Open areas, quarries, long-range perimeters |
Entry points, turnstiles, close-range PPE checks
Inside a workshop, warehouse aisles, mid-range zone monitoring
Open areas, quarries, long-range perimeters
Final camera requirements are determined after a site audit and measurements. At some points the existing camera is enough; at others a replacement or an extra camera may be needed.
Output from every module is collected in one panel — separate programs and logbooks are no longer needed.
Camera streams are viewed in the browser and the required camera is selected from a list.
Every record is stored in a list with its time, zone and module.
Each record carries a frame and a short clip — they can be attached to a report.
Zone boundaries and when each rule is active are configured in the panel.
Reports by shift, crew and module, exported to Excel or PDF.
Access to data is limited by role and actions inside the panel are recorded.
The project starts at one point: the module is tested there in real conditions, and once the result is confirmed it is extended to the remaining zones.
We review the site: which process is left unmonitored, where the incident risk is highest and which module delivers value first.
Stage outcomeA list of monitoring points and the module selection for the first stage.
Existing cameras are checked: do distance, angle, lighting and frame quality meet the module's requirements.
Stage outcomeA written statement of which cameras suffice and which need replacing or adding.
The module is tested and tuned on real frames captured at your site.
Stage outcomeThe result at the pilot point and settings that reduce false alerts.
The server is installed, modules enabled, the panel configured and the agreed systems connected.
Stage outcomeA working platform with configured zones and alert channels.
Safety and HR staff are trained on the panel and the system is formally accepted.
Stage outcomeA handed-over system, a guide and the technical support period.
The timeline is set by the chosen modules, the number of cameras and the complexity of the site — an exact schedule follows the technical audit.
The plans below are a starting point for the software. Cameras and server hardware are quoted separately.
Basic computer vision solution
15,000,000 UZS
Who it suits
Sites starting with one or two monitoring points.
Professional computer vision solution
30,000,000 UZS
Who it suits
Sites that need several zones, face recognition and real-time analysis.
Enterprise computer vision solution
50,000,000 UZS
Who it suits
Sites with many cameras that require integration with corporate systems.
The price excludes cameras, installation, network equipment and server hardware — these are quoted separately for the site. An exact estimate follows the technical audit.
Answers to the questions asked most often before a technical audit.
IP cameras that provide an RTSP stream can be connected. But not every camera suits every module: distance, angle and lighting have to meet its requirements. That is why cameras are checked point by point during the audit, and it is stated in writing which are sufficient and which need replacing.
During the technical audit we review your existing cameras, distances, lighting and monitoring points. Then we prepare the matching modules and a project proposal.