Applications / Security

Open-Closed Doors

Detects the state of doors, gates, hatches and cabinets — open, closed, left open too long — and the events that should have accompanied a change of state.

Open-Closed Doors – AI Security Monitoring — Fogsphere detection illustration

See it in action

Door state, open duration and the events behind it

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.

Door left open, with duration

Reports not only that a door opened but how long it has stayed open.

Fire-door and emergency-exit state

Flags fire doors propped, wedged or held open, and emergency exits used outside an emergency.

Cold-room and cold-chain door monitoring

Detects prolonged cold-room door-open events where product exposure follows from the duration.

Dock door open with no trailer present

Surfaces the specific combination the Q3 logistics paper calls out as a security exposure.

Trailer and container door-open detection

Covers seal-check workflows and doors opened away from a dock.

Maintenance panel and cabinet left open

Applies the same rule to electrical panels, valve cabinets and key cabinets.

Safety-door and interlock state on machine cells

Reads cell door state as part of the same detection rather than a separate system.

Confined-space hatch state

Detects open hatches on vessels, tanks and pits.

Doors and gates left open at the perimeter

Flags perimeter openings that stay open outside a movement window.

Door events without a matching badge or WMS record

Correlates the state change with the systems that should have authorised it.

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

Confined-space hatch and door status on rigs and offshore platforms. Valve-cabinet tamper detection at wellheads and isolation points. Refinery control-room access and after-hours door monitoring.

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

Door state looks like the simplest thing on this list and turns up in the Q3 papers under four different headings: security (perimeter doors and gates left open), cold chain (door-open duration and product exposure), egress (fire doors propped open) and machine safety (interlock and cell door state). The common failure is that a door sensor, where one exists at all, reports a transition and nothing about context.

The control objective is door state read together with what was around it — whether a trailer was present, whether a badge event accompanied it, how long it stayed open, whether anyone went through. What the operator gains is a door record that supports a cold-chain deviation, a security investigation and an egress audit from the same detections.

Related solutions

Worker Access

View solution →

Time Limited Area

View solution →

Unattended Objects

View solution →

See Open-Closed Doors running on your own cameras

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