Edge computer vision for factory lines. Packaged modules run quality, counting, and safety checks next to your cameras.
Catch faults before they leave the line. Modules run beside your existing cameras and flag misaligned labels, missing caps, and short packs the moment they appear.
Defect flagged on Line 3
--:--
Flagged 12s ago
Flagged 48s ago
Flagged 2m ago
Flagged 4m ago
IFA (In-Factory Analysis) is an edge computer vision platform for production lines. Each capability ships as a module — one task on one line, such as label misalignment and missing caps on a bottling line, or pack counting at a loading bay.
A module runs on a small edge box beside your existing cameras. It decides pass or fail on site and emits a standardized event, so the line keeps running whether or not the network does.
Events stream to a cloud dashboard: live line and camera health, analytics derived automatically from each module, and a full audit trail of every check.No-code automations turn events into action — filter, window, and cooldown rules that trigger email alerts, frame captures, or reports, without writing code or touching the box.
Each line task ships as a packaged module — label misalignment, missing caps, pack counting. Adding one is configuration, not a new project.
Inference runs on an edge box beside your cameras. The verdict leaves as an event; the video stays on site.
Connect any event to an action — email alerts, frame capture, reports — with every run logged step by step.
IFA questions
Modules in production cover label misalignment, missing caps, person detection, and pack counting — a counting module closes each session with in, out, and net totals plus a flag for low-confidence counts that need review. Each module targets one task on one line, and new modules are built around what your plant needs.
Your existing cameras and a small edge box beside the line. The box takes a camera index, a video file, or a stream URL as its source, then asks the cloud which module it should run and loads it at runtime — so changing what a line checks does not mean a site visit.
You build a flow in the dashboard: a trigger (a module event, a stream going offline, a schedule), then logic (filter, a window such as 'five or more in ten minutes', a cooldown), then an action (send an email, capture the frame, generate a report). Every run is recorded with per-step detail, including runs that were suppressed.
No. The live view is an in-memory latest-frame stream that is never written to disk, and the events sent to the cloud carry data, not media. Frames are only stored when you explicitly add a frame-capture action to an automation.
Last updated:
