Applications / Safety

Slips and Trips

Detects the floor conditions that produce same-level falls — spills, wet floors, leaks, debris, cables and clutter — and logs how long each one stays uncorrected.

See it in action

Spills, wet floors and trip hazards, as they appear

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.

Spills and wet floors

Flags visible liquid on a walking surface, including after cleaning where the floor is still wet.

Leaks and standing water

Surfaces water leakage, flooding and standing water in plant rooms, yards and back-of-house areas.

Debris, loose material and parts on the floor

Detects parts, packaging, offcuts and loose material left on walking surfaces.

Cables and hoses across walking surfaces

Identifies trailing cables, leads and hoses run across a route people walk.

Workstation clutter and tools out of place

Covers the 5S conditions — clutter at stations, tools left on the floor, materials outside their marked area.

Bin overflow and waste accumulation

Flags waste build-up and overflowing containers before they spread into a walkway.

Slip, trip and fall events themselves

Logs the fall itself with the clip, so the condition and the outcome sit in the same record.

Time-to-clear per hazard

Measures how long each condition persists between first detection and correction.

Housekeeping and 5S score by zone

Rolls the raw detections into a per-zone, per-contractor housekeeping score rather than a single site figure.

Where it applies

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

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

The Q3 food & beverage paper treats wet floors as a persistent exposure rather than an incident type, and the construction and power generation papers both ask for a housekeeping score broken down by contractor, floor or work zone. The common thread is duration: a spill that is cleared in two minutes and a spill that sits for two hours look identical in an incident log and are not the same operational problem.

The control objective is therefore visibility of floor condition over time, not just a hazard alert. What the operator gains is a per-zone housekeeping figure with time-to-clear behind it, which is the number that makes a cleaning contract, a shift handover or a 5S review measurable instead of anecdotal.

Related solutions

Clean Pedestrian Way

View solution →

Clean Vehicles Paths

View solution →

Pedestrian Way Violation

View solution →

See Slips and Trips running on your own cameras

Bring a camera stream and a floor area. We will show you what the model surfaces on your site, not on a demo reel.