Simat Labs

Assembly Line QA

Assembly Line QA

Pass/fail quality checks on production lines — labels, caps, and fill, decided next to your cameras.

Line 3 — Bottling

--:--

LIVE·1,284 upm·CAM-03

Inspected

48,201

Pass rate

99.2%

Defects

386

Defect flagged on Line 3

4 open

Bottle #B-4471

high

Label misaligned — 7.4° skew

vision-label·41 ms·12s ago

Bottle #B-4488

medium

Cap missing

cap-presence·38 ms·48s ago

Pack #P-1203

high

Short count 11/12

pack-count·44 ms·2m ago

Bottle #B-4502

low

Fill level below spec

fill-level·36 ms·4m ago

edge-01 · healthy

38 ms p95

Assembly Line QA checks every unit that passes a camera on a production line: a misaligned label, a missing cap, a wrong fill, a misprinted date code. Each check is one task on one line.
The check runs on a small edge box beside your existing cameras. It decides pass or fail on site and emits a standard event, so the line keeps running whether or not the network does.

Events stream to the dashboard: live line and camera health, analytics derived from every check, and a full audit trail of each verdict.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.

Modules, not custom builds

Each line check ships as a packaged module — label misalignment, missing caps, wrong fill, print and date-code errors. Adding one is configuration, not a new project.

Decides at the line

Inference runs on an edge box beside your cameras. The verdict leaves as an event; the video stays on site.

No-code automations

Connect any event to an action — email alerts, frame capture, reports — with every run logged step by step.

Powered by IFA

Runs as a module on the IFA edge box beside your cameras.

About IFA

The IFA dashboard

One dashboard for every module

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

HourDayWeek·group by: line

Events per hour

Line 3 · QA failsDock 4 · crossings
020406006:0008:0010:0012:0014:0016:00Dock 4 · crossingsLine 3 · QA fails

Events by severity

Critical6
Warning41
Info137

184 events · 2 modules · 4 cameras

Streams

  • Line 3 — labeleronline · 24 fps · 41 ms
  • Dock 4 — closeonline · 20 fps · 38 ms
  • Dock 4 — fardegraded · 11 fps · 2 reconnects
  • Line 1 — capperoffline · last seen 09:12

Automation runs

  • Label fail → email shift leadok11:42
  • 5 fails in 10 min → capture + WhatsAppok11:38
  • Dock 4 far offline → emailsuppressed11:20
  • Session closed → reportok10:57

Live camera monitoring

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.

Charts derived from events

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.

Event log and notifications

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.

No-code automations

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.

Reports for managers

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.

Assembly line QA questions

What does Assembly Line QA detect today?

Checks in production cover label misalignment and missing caps. Each check targets one task on one line and returns a pass or fail verdict with the frame that decided it. New checks are built around what your line needs, and counting what leaves the line is its own solution, Pack counting.

What do I need on site?

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.

What happens after a detection?

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.

Does video leave the factory?

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: