Net counts of packs, cartons, and pallets at loading bays and lines. Two synced cameras, an auditable ledger, a review queue.
Dock 4 — loading bay
--:--
In
138
Out
3
Net
135
edge-dock-04 · healthy
video stays on site
IFA Counting (In-Factory Analysis — Counting) counts what moves through a doorway, gate, or line: packs, cartons, and pallets loaded onto a truck at a loading bay, or units leaving a packing line.
Two synchronized cameras watch the same gate from different angles. A crossing only counts when it passes two calibrated lines in order — in is A then B, out is B then A — so jitter at the doorway cannot count, and anything carried back out is subtracted. Each truck or session closes with in, out, and net totals.
Every crossing is written to an auditable ledger with its timestamp, direction, a cropped image, and the evidence it was established on. A thrown pack, a pack hidden in a worker's arms, or two cameras disagreeing lands in a review queue instead of silently changing the total.It runs on an edge box on the camera network, rides through camera dropouts, and never sends video off site. Session totals and review items flow into the same IFA dashboard and no-code automations as IFA QA.
Direction-aware in and out at two calibrated gate lines. Out crossings subtract, and totals are always re-derived from the ledger, never from a running counter.
One ledger row per crossing — time, direction, quantity, a cropped image, and how it was established. Low-confidence events go to a review queue with the frames attached.
A close doorway camera and a wide second angle are fused per crossing: confirmed, conflicting, or seen by one camera only — and a camera outage never inflates the total.
The IFA dashboard
IFA QA and IFA Counting report into the same web dashboard. It is built so 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.
IFA Counting questions
Packs, cartons, and pallets moving through a dock door or gate onto a truck, and units leaving a packing or wrapping line. For a pallet, the quantity is estimated from the wrap colour and stack height recorded for that product, so one crossing can book six or twelve packs rather than one. Product family recognition is optional and never changes the quantity.
They are handled, and they are flagged. A pack thrown through the gate is tracked at lower confidence and its path is projected if it vanishes mid-flight. A pack that disappears into a worker's arms is counted when the worker completes the crossing. A pack sliding behind the door frame is counted on the evidence of where it was last seen. Every one of these carries a review flag, so the number you sign off on separates observed crossings from inferred ones.
Two IP cameras on the gate — one close on the doorway, one wide from a second angle — streaming their main RTSP feed to a GPU edge box on the camera network. Geometry is calibrated once per camera from a still frame. Before go-live, we run the system against footage of your own loading sessions and compare it with a manual hand count, and that comparison is replayable whenever a counting rule changes.
No. Detection, tracking, and counting run on the edge box; what leaves is the ledger — timestamps, directions, quantities, and small crops of the counted item. Full-frame recording is off by default and only enabled deliberately for a debugging session.
Same platform, different question. IFA QA judges each unit — pass or fail on labels, caps, or safety. IFA Counting measures quantity — how many went in, how many came back out, and the net. Both run as modules on the same edge box, report to the same dashboard, and feed the same no-code automations, so a plant can start with one and add the other.
Last updated:
