// Module 02

Auto-Reporting Engine

Shift reports and root-cause briefs, written by the appliance.

The reporting agent runs on a cron or fires on alarm spikes. It pulls from alarm_log, device_diag_log and mistake-proof tables, correlates the events, and writes a plain-language brief that a plant manager can read in 60 seconds.

Inputs

Schedule: Cron (e.g. end of each shift) or event trigger (alarm-rate threshold)
Scope: Lines, stations, time window, severity filter
Sources: alarm_log · device_diag_log · cycle_log
Template: Report skeleton (sections, target length, language)

Outputs

Shift summary: Top stoppages ranked by lost minutes, with station and work-order
Correlated hardware events: VDS / mistake-proof events that overlap each stoppage
Suspected root cause: One-paragraph hypothesis with supporting evidence rows
Distribution: Markdown / PDF / email to a configured recipient list

Example prompts

Operator

Auto-trigger: end of night shift on assembly hall H2.

Appliance

Night-shift report — H2, 22:00–06:00: • Top stoppage: material starvation at Station 03 — 42 min over 3 events (largest at 02:14). • Correlated: 11 VDS heartbeat drops on the tightening tool between 02:09–02:18 — likely shared switch. • Mistake-proofing: 4 rejects on a work order, all upstream of Station 03. • Suspected root cause: upstream logistics delay compounded by intermittent network on the tightening tool. Recommended: check the line-side switch and verify kanban refill cadence on Station 02.

Operator

Auto-trigger: alarm rate on the production line crossed 12/min for 5 minutes.

Appliance

Alarm-burst report — the line, 13:42–13:55: • 73 alarms in 13 min, 4× the baseline. • 62 of 73 are Error 2000 (cycle timeout) clustered at Station 02. • VDS shows the scanner retried 19× in the same window. • Suspected root cause: scanner re-read storm on the scanner is starving Station 02 of part IDs, triggering cycle timeouts. Recommended: swap or reseat the scanner before next shift.

Operating notes

[01]Reports are generated against the sandbox; live MES performance is never affected by a report run.
[02]Templates are versioned — every report links back to the template hash and the exact SQL that produced each figure.
[03]Recipients and schedule are configured on the appliance; no cloud webhook is required.

Other modules

Conversational Copilot

Ask your MES in plain language. Get correct SQL, every time.

Predictive Sentinel

Warnings minutes-to-hours before the line actually stops.