How is a queue measured?
You draw a queue zone on the camera view. The system counts the people standing inside it and reports that as the queue length, continuously.
Queue length at counters, gates, and desks from existing cameras, with alerts when lines build up.
Store 04 — Front of store
--:--
In store
412
Flow
38/min
Waiting
23
Checkout 1
6 in queue
Checkout 2
11 in queue
Checkout 3
4 in queue
Service desk
2 in queue
edge-04 · healthy
pax/min
Queues measures how many people are waiting in a line — at a checkout, a service desk, a gate, or a counter — from the cameras that already cover it.
Teams see queue length live and over time, so they can open another counter before a line gets long, not after customers complain.
Detection runs on-premise and is anonymous: people are counted inside a queue zone you draw. No faces are stored and no one is identified.When a queue passes the length you set, no-code automations send an alert, and the dashboard shows when and where lines build up across the day.
People waiting in each queue zone you draw on the camera view, updated continuously.
Set a length per queue and get an email alert when it is passed, with a cooldown so one busy minute is one alert.
Queue length by hour and day, per counter and site, to plan staffing around real demand.
Powered by IFA
Runs as a module on the IFA edge box beside your cameras.
The IFA dashboard
Every IFA module reports into the same web dashboard. A new module shows up with its charts, events, and automations the day it is deployed — nothing is coded per module.
Plant overview — today
Events per hour
Events by severity
184 events · 2 modules · 4 cameras
Streams
Automation runs
Every camera as a health card: online, degraded, or offline, with frame rate, latency, and uptime, and a live view from the edge box when it is streaming. Refreshes on its own.
Pick a metric, group by line, zone, severity, or product, and bucket by hour, day, or week. Line, bar, area, stacked, and pie — all built from the events a module emits, never hand-coded.
Every event, filterable by module, type, and severity, with the frame that triggered it. Email and WhatsApp notifications go out through automations, with a per-run record of what was sent and what was suppressed.
A drag-and-connect flow builder: a trigger (a module event, a camera going offline, a schedule), logic (filter, window, cooldown, time gate), then actions — send an email, send a WhatsApp message, capture the frame, generate a report.
A report action turns a session or a shift into a readable document — totals, shares, per-product detail — attached to the notification email and kept in the dashboard's report list.
Queue questions
You draw a queue zone on the camera view. The system counts the people standing inside it and reports that as the queue length, continuously.
A camera that sees the whole queue, usually existing CCTV with an RTSP/ONVIF stream. Long or winding lines may need a second view. Processing runs on the IFA edge box on site.
No. People are counted inside the zone without storing faces or identifying anyone. Only queue lengths and alerts leave the site.
Anyone you choose. Alerts are no-code automations in the dashboard: pick the queue, the length, and a cooldown, then the email recipients. Every alert is logged.
Last updated: