Applications / Operations Intelligence

Minimum Worker Count

Counts how many people are present for a task and flags when the count drops below the minimum that task requires — attendant, banksman, standby or second person.

Minimum worker Count – Task Distribution in Hazardous Regions — Fogsphere detection illustration

See it in action

Tasks running below the crew the task requires

What it detects

Harvested from the computer-vision use-case columns of the Q3 industry papers. Every item below is a rule you can switch on, tune per zone and report on.

Count below the configured minimum

Flags a zone or work front operating with fewer people than the rule for that task sets.

Attendant presence at confined-space entry

Detects entry proceeding without the attendant or watch-person the entry requires.

Fire-watch and standby-person presence

Checks that a standby role named in the Q3 chemical and power generation papers is actually at the work front.

Two-person lifting compliance

Surfaces manual handling being done alone where the task calls for a pair.

Banksman presence during reversing

Detects a reversing manoeuvre starting with no banksman in view.

Lone presence in a paired-work area

Flags a single person in an area the rule says should never hold one person alone.

Crew arrival and work-front occupancy

Reports when a crew arrives and how the work front fills through the shift.

Task started with an incomplete crew

Separates a crew that thinned out mid-task from one that never assembled.

Duration spent below minimum

Measures how long the shortfall lasted, which is the figure a review needs.

Compliance rate by task type and shift

Aggregates the record so the tasks that routinely run short are identifiable.

Where it applies

The sub-sectors below are the ones the Q3 industry papers name for this detection. Each links to the industry hub.

In Oil & Gas

Required two-person operations on hazardous tasks (hot work, confined spaces, line breaks). Banksman attendance during reverse maneuvers in refinery and construction yards.

How it works

01

Runs on the cameras you already have

Inference happens at the edge on your existing CCTV and IP streams. No new camera estate, no video leaving site, no cloud round-trip in the detection loop.

02

Thresholds and zones you configure

Draw the zone, set the rule, set the dwell, count and confidence thresholds. Rules differ by area, shift and task, because sites do.

03

Evidence, not just alerts

Every event is logged with camera, zone, timestamp and a clip, so the record is reviewable afterwards and usable in a corrective action.

04

Integrates with what you already run

Events push into your VMS, alerting and reporting stack through Fogsphere Manager, with dashboards broken down by area, shift and crew.

Risk & control objective

This is the thinnest Q3 coverage of the seventeen: the papers name attendant and watch presence at confined-space entry, fire-watch and standby-person presence, and two-person lifting compliance, but they do not develop a minimum-crew use case at the length they give to occupancy. The underlying control is nonetheless well established in permit-to-work practice — a role is nominated on the permit and is expected to be present for the duration.

The control objective is therefore presence of a required role for the duration of a task, not just at its start. What the operator gains is a record of how long a task ran below its nominated crew, which turns a permit condition that is normally confirmed by signature into something with evidence behind it.

Related solutions

Maximum Worker Count

View solution →

Dynamic Area Delimitation

View solution →

See Minimum Worker Count running on your own cameras

Bring a work-front camera and a crew rule. We will show you what the model surfaces on your site, not on a demo reel.