A second button on the Manufacturing Dashboard, next to Production
Status Board, opens the Production Control Board — a supervisor-facing view of one production
line (or all of them together) built around six panels: a KPI strip, where work is waiting,
what is blocking it, the lists in production, a 14-day throughput chart and a chart of why
units were remade. It is shown to every company. Where the Production Status Board is a
per-list operator worksheet, the Control Board is a whole-line “how are we doing today” view.

Shared ideas behind every panel

• A live list is a production batch that has been released to the shop floor and is
  not yet complete — the same batches the Production Status Board shows.
• A unit is one assembly inside a live list. If a unit is scrapped and remade, its
  replacement is a unit of its own — it counts as extra work and extra output, on top of the
  original.
• A unit is packed once it has passed final inspection and been recorded shipped —
  the same milestone the app’s “Manufactured” tiles already use elsewhere.
• A card’s throughput rate is the average number of distinct unit scans at its
  station (for a department, at its member stations) per working day (a unit scanned at two of its stations counts twice, the same
  way its queue counts it), over the last 5 working days (today is excluded — it is still in progress,
  so counting it would understate the rate early in the day).
• “Working day” follows your company’s own calendar (your company’s weekends and holidays; there is no
  screen to edit them today, your OpenJanela administrator sets them up), falling back to the country calendar, and finally to a plain
  Saturday/Sunday weekend if neither is set up.

Opening it, the line selector, refresh, TV mode

• A line selector at the top lets you pick one production line, or All lines
  (every active line, excluding glass-only lines, combined with their own sub-lines).
• The board refreshes itself every 60 seconds in the background — there is nothing
  to click. If a refresh fails (e.g. a momentary server hiccup), the board keeps showing the
  last good data and the status line reads “Last updated HH:mm — refresh failed:
  <reason>” instead of freezing or clearing; the next refresh 60 seconds later tries
  again automatically.
• TV mode is a toggle for a shop-floor screen at a distance: it switches to larger
  text, hides the line selector and the Refresh button, and — matching what the shop floor
  actually wants up on the wall — also hides the Blockers panel, the throughput/remake-reasons
  charts, and the Next column on the lists table, leaving the KPI strip, the station panel and
  the lists table. Switch back to Manager mode the same way; the choice is not remembered
  between visits to the screen.

A. KPI strip

A KPI with no target set on the line (0) shows “no target set” instead of comparing against
zero, rather than reading as permanently red.

B. Where work is waiting

One card per flagged station or department; a department’s card sums the work of all
its member stations (see the section below): its queue (routings to its stations minus those scanned there, i.e. work
sitting in front of the department; a unit routed to two of its stations counts twice), done
today, its 5-day rate, and days of work (queue ÷ rate). Every flagged
department or station on the selected line gets a card, even one with nothing queued and no
recent scans (the flag alone decides what shows). The
bottleneck is the department with the highest days of work among departments that actually
have a queue; one with no recent scans (rate 0) is never picked as the bottleneck —
dividing a real queue by a zero rate does not produce a meaningful “days” figure, so that
card shows “no recent scans” instead. Below the cards the board opens the bottleneck’s waiting
units straight away (when there is no bottleneck, the first card with a queue; otherwise the
first card); click any other card to show its units instead. For a department the
detail is broken down station by station: each member station gets its own heading with
its own queue, done today and days of work (or “no recent scans”), followed by the units
waiting at that station — the order/item, the list and a waiting since time.
For an ordinary station the tiles also name the station the unit waits at.

C. What is blocking us

D. Lists in production

One row per live list: batch number, series, units, progress (packed ÷
units), ship date, projected finish, a status chip (On track / At risk / Late,
with “(material)” appended when a material shortage is part of why), and the next
department the list still has work waiting at (the first one in dashboard order). Projected
finish looks, department by department, at this list’s own remaining work plus the remaining
work of every list ahead of it in that department, divided by the department’s rate — the
slowest department to clear wins; a list that has nothing left in any department is projected
to finish today, and a list stuck behind a department with no recent scans cannot be projected
at all (“cannot project”).

E. Units packed per day

A 14-working-day bar chart of units packed, with the line’s daily target drawn as a
line across it when a target is set.

F. Why units were remade

Reject reasons for remakes raised in the last 30 days, ranked by units (a pareto chart) —
useful for spotting the one or two causes worth chasing first.

Targets — set on the production line

The Daily Target (units) and Remake Target (%) that drive the Output Today and
Remakes KPIs, and the target line on the 14-day chart, are set on the production line’s own
setup screen (Stations & production lines), in a
Targets panel between Routing and Glass. Both default to 0, meaning “no target set”, on
every line until someone sets them. When All lines is selected on the board, the daily
target shown is the sum of every real line’s own target, and the remake target is a weighted
average (weighted by each line’s daily target).

How a station or department gets onto the board

The panel (B) uses the same flag rule as the Production Status Board’s columns: only
production_stations rows with show_on_dashboard = 1 get a card. A
flagged department (is_department = 1) gets a card when at least one of its
member stations (stations whose department_id points at it; they need no flag) is
on the selected production line (or one of its sub-lines), and it sums their work. A flagged
ordinary station gets a card when it is itself on the line, and shows its own work; if it is also
a member of a flagged department it still counts inside that department’s card. Either way the
card needs work queued or recent scans. Unflagged stations whose department is not flagged are
not shown. dashboard_label gives the card its label (falling back to the row’s own
description) and dashboard_sequence
(then id) sets its order. As with the Status Board, there is no setup screen for these fields
yet — they are set directly in the database.