[jakub-przepiora]

What

Completes the Plant overview admin dashboard from the design mockup, on top of the foundation (#379) and the production targets (#380) already in develop. Admin → Dashboard now has every section of the mockup, fed by live data:

• Line activity · this shift: one bar per line, Running / Idle / Blocked / Down up to Now, with uptime.
• OEE · this shift: plant OEE since shift start, A/P/Q bars and per-line OEE against each line's target. The target is the line's Planning efficiency, or 85 % when that is not set.
• Downtime: shift total by reason with the affected lines and the share of planned time. Unclassified stops link to the Shift Monitor.
• Production · planned vs actual and Output per hour: the plan comes from the Schedule, actual from a new output ledger.
• KPI tiles: orders not scheduled (the planner's own backlog rule), lines producing, scrap rate and first-pass yield, each against its target.
• Needs action: down and blocked lines, low stock, failed inbound inspections, quarantined lots and overdue corrective actions. Each row has a button that leads only to existing pages or actions.
• Line cards (order progress, ETA or the reason the line stopped) and a summary strip.
• Review fixes to feat: add plant overview header and live line states to the dashboard #379:
  • "2 h 59 min left" rounding;
  • a line whose collector went silent shows No data instead of its last state;
  • several open stops per station are handled;
  • the header shows the default shift window when no shifts are set up.
• Review fixes to feat: add production targets and first-pass yield #380: the OEE target no longer counts finished or cancelled orders, FPY is computed with a SQL aggregate, and the targets card loads lazily.

Two fixes outside the dashboard, found while analysing it:

• Overdue alerts use the plant's midnight. The badge and alerts used the UTC date.
• Work-order create/edit enforce WorkOrderPolicy. Having the Orders tab was enough before. The pages now return 403 without the permission and the buttons are hidden.
  • This also restores the operator sidebar for granted admin tabs, which a redesign had dropped.
  • It also fixes saving Settings → Tab Access.

Why

The admin dashboard had no view of the shift in progress. The mockup asked for one screen showing what each line is doing, how far production is from plan, and what needs attention.

How it was built

Each section was built as its own task, and the tasks were then integrated here:

• One line-state mapping. The machine state is mapped to a line state in one place (PlantOverviewService::machineCandidate()), shared by the current state, the timeline, the cards and Needs action.
• Lines are resolved once per refresh and shared by the line states, KPI tiles and Needs action. A line can no longer read differently in two sections.
• No import cycle between sections. OverviewCard has its own module. Sections took it from OverviewGrid, which imports every section.
• One line-state vocabulary. All sections use lineStates.js for labels and colours.
• No new dependencies. Charts are hand-drawn SVG.
• Untouched: GET /api/v1/admin/dashboard (used by the mobile app), the shared synced collections, OeeCalculationService and its cache key, OeeGauge, dashboard_widgets and the WidgetRegistry contract.
• Existing widgets stay under Last 30 days.

Please review

• Schema change: new table work_order_output_entries, written by WorkOrderOutputObserver on every change to produced_qty. It is the source of output per hour. All produced_qty writes in app/ go through the model, so none bypass it. Hourly figures start from the upgrade.
• Line state rule: a line is Down while any of its stations is down (fault, maintenance, unplanned stop). Workstations have no "critical" flag, so every station counts. On lines with parallel stations this can overstate Down.
• Left out on purpose: a change to realtimeCollection.js that re-read every live collection after any form submit. It is app-wide and unrelated to this work, so it is a separate follow-up.

How it was verified

• php artisan test: 3715 passed (1 skipped, 1 risky, as on develop).
• Frontend: npx vitest run, 251 passed.
• vite build passes, pint --test is clean on the changed files, and en.json / pl.json have the same key set.
• The dashboard was checked by hand on a local instance with all three example companies (machine shop, print shop, bakery) plus the Shift Monitor demo seeder:
  • every section renders and there are no console errors;
  • no horizontal scroll at 1440, 1024 and 390 px, in light and dark;
  • section figures were cross-checked against direct database queries: downtime minutes, work orders in progress, output in the shift, and the line-state reasons.

Known follow-ups (not in this PR)

• System reset fails without ADMIN_* env (web-installer and manual installs). With the Docker compose defaults it recreates the admin with a known password.
• The timeline's hour labels are crowded on phones.
• Page-level performance measurement and admin-guide docs for the dashboard.

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Auto reviews are limited based on label configuration.

🏷️ Required labels (at least one): 1

• cla-signed

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

Run configuration

• Source mode: Auto
• Repository: Mes-Open/OpenMes
• Branch: develop
• File: .coderabbit.yaml
• Commit: 64c5af7
• Layers: Repository YAML
• Review profile: CHILL
• Plan: Advanced
• Run ID: ddd04c64-bedb-4e58-89d8-20d34f4fb483

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}