SenseYield logo Production Intelligence
Broker Connecting… Offline — waiting for live data --:--:--

Live Production · Run Control Line 1

No active run
No active run
—
Run elapsed
--:--
Started by
—
Run progress
—
Rejects — manual entryNot tracked The line's one sensor counts every part — that count is the run's total. Rejects are entered here by the operator; Good and Quality are derived from them. Nothing is assumed.
0
Rejects this run
Start a run to begin logging rejects.

No rejects logged yet for this run — Quality shows “Not tracked” until at least one entry is logged, or a sensor supplies a measured reject count.

Target reached — this run has hit its target. End production, or keep going if the plant is overproducing on purpose. The run will not close on its own.
This run is still open. No new counts have come in for a while — if production has finished, end the run so its totals are saved.

Runs are started and ended here, on the dashboard — no reset button or extra input is needed on the line, and the machine counter is never reset. A power cut mid-run doesn't lose the run: counting picks up where it left off.

0%
Overall OEE
— 0.0 vs last shift

Waiting for live data

No live MQTT data has been received yet. Values appear here as soon as the line starts publishing.

Availability 0.0% — 0.0
Performance 0.0% — 0.0
QualityNot tracked Not tracked — 0.0
Quality is not tracked for this run — no reject data has been logged, so the OEE above assumes Quality = 100%. That 100% is an assumption, not a measurement. Log rejects on the Live Production panel (or connect a reject sensor) to get a measured Quality.

Production —

0 / 12,000 units
0.0% of target 12,000 to go
Target reached — run stays open until an operator ends it.
Total (sensor count)
0
Rejects
0
Good = Total − Rejects
—
Pace
Waiting for live data
Projected finish
—
Rejects
0

Line rate units / min · live

Current0 /min
Ideal rate59 /min
Shift average0.0 /min

Machine state Filler · FL-01

OFFLINE
Status
—
Stopped — —
Current SKU—
Current rate0 units/min
Downtime this shift0 min
Minor stops—
Stops this shift0

Shift timeline Waiting for live data — no MQTT messages received yet

Shift startNowShift end
Running Stopped Changeover Remaining

Downtime Pareto downtime only · stops ≥ 5 min · this shift

Recent stops tap a stop to add its note

Completed runs

CSV ready
⬇ Download the file

No completed runs yet this session. End a production run above and its summary will land here.

How long data is kept: raw 2-second readings are retained about 30 days, minute-level trends for 12 months, and run & shift summaries are kept indefinitely. Download any run as CSV to keep your own copy forever.

Run audit log

Who started / ended what, and when
    OEE · Line 1
    0%
    Availability 0% · Performance 0% · Quality 0%
    SKU · —
    Line state
    OFFLINE
    Waiting for live data
    Units vs target
    0 / 12,000
    Current rate
    0 units / min

    Motor Health Waiting for motor data — no motor messages received yet

    Every machine gets its own graphs — vibration, load / current and temperature are kept per machine and never mixed together. Pick one machine to inspect it on its own, or view all machines at once.

    Motor gateways publish JSON to senseyield/demo-mkaur/motors/<machine-id> with fields vibrationMmS, currentA (or loadPct) and tempC. The two line machines are shown in their waiting state; any other machine's panel appears the first time it publishes.