15-minute Shopfloor KPI Huddle — Dashboard Template & Playbook

Purpose

Use this template to build a visible, repeatable 15‑minute shopfloor huddle that focuses shift teams on the small set of KPIs that drive daily action: OEE, unplanned downtime, and quality. The dashboard layout, calculation rules, huddle script, role assignments, action template, and escalation ladder below are designed to minimize noise, create clear ownership, and speed meaningful follow-up.

Quick Principles

• Keep it short and focused: this is an action huddle, not a status meeting.
• One single source of truth for each KPI (MES, PLC, OEE tool, or validated spreadsheet).
• Show current shift metrics + short trend windows (rolling 24h, last 7 days) so context is visible.
• Top-of-dashboard alerts highlight only exceptions above tuned thresholds.
• Every item on the board must have a clear owner, due time, and next-step.

Recommended KPIs & Calculation Rules

Data Rules & Quality

• Define "planned production time" clearly (exclude breaks, meetings, scheduled maintenance).
• Downtime must be tagged with one primary cause and free-text note optional.
• Use rolling averages for trends; avoid single-event volatility being treated as systemic unless repeated over the window.
• Timestamp every recorded action — this enables audits and follow-up.

Visual Layout (optimized for 15-minute review)

1. Top row (full width): Critical Alerts bar — only items exceeding tuned thresholds (red/yellow) and requiring action.
2. Left column: Big OEE tile (current shift %), with a 7‑day sparkline and delta vs. same shift yesterday.
3. Center column: Unplanned Downtime (minutes), event count, and top 3 downtime causes with mini trend lines.
4. Right column: Quality snapshot — scrap rate, first pass yield, and top scrap reasons.
5. Bottom area (full width): Top‑3 Actions (action cards) with columns: Action, Owner, Due (time or shift), Status, Escalation level.
6. Persistent element: A small table with last 5 closed actions and outcomes (so teams see follow-through).

Thresholds (examples — tune during pilot)

• OEE: green > 80%, yellow 65–80%, red < 65%
• Unplanned downtime: red if > 30 min lost in an hour block or > 60 min total for the shift (adjust to plant norms)
• Scrap rate: red if scrap > 2% (or plant-specific target)

15-minute Huddle Script (time-boxed)

1. 0:00–0:90 — Quick welcome & safety note (facilitator), call out any immediate safety concerns (15–30s).
2. 0:90–4:00 — Data snapshot: OEE, downtime minutes, quality. Facilitator reads top alerts; data champion confirms metrics source.
3. 4:00–10:00 — Discuss top exceptions (max 2–3): each exception quickly summarized (what happened, immediate containment actions) and assigned an owner.
4. 10:00–13:00 — Assign actions: define owner, due time, and expected next update. Capture in action tracker on the board.
5. 13:00–15:00 — Escalation check and close: confirm owners understand escalation thresholds and next update time; end with a short recognition or learning note.

Roles & Responsibilities

• Facilitator (Shift Lead): Keeps the huddle on time and action-focused.
• Data Champion: Confirms metric source, validates calculations, and resets displays if needed.
• Scribe / Board Owner: Enters actions into the dashboard/action tracker (or triggers the interactive form).
• Action Owners (Operators / Tech / Maintenance): Accept ownership for assigned actions and report status by due time.
• Escalation Contact: Named person for next-level support (Team Lead → Shift Supervisor → Plant Manager)

Escalation Ladder & Response Times (example)

Action Card Template (board row)

• Action Title — short, specific (e.g., "Replace worn roller on line 2")
• Owner — named person (not role)
• Due — specific time or next huddle
• Status — Open, In progress, Blocked, Closed
• Escalation Level — number (1–4)
• Notes / Containment — one-line initial note

Pilot & Tuning Plan (2-week pilot)

1. Run the huddle every shift for 2 weeks using the dashboard spec as-is.
2. Collect: number of actions created per huddle, % closed by due time, number of escalations, and team feedback (3 quick questions after huddle: useful? too long? confusing alerts?).
3. Adjust thresholds after week 1 to reduce noise (raise yellow thresholds where too many false positives; lower where problems were missed).
4. After week 2, decide on persistent changes: KPIs to keep, alerts to tune, and whether to add automation (e.g., auto-create action when downtime > X minutes).

Common Pitfalls & Tips

• Don’t show too many KPIs — three primary metrics plus top causes keeps focus.
• Avoid re-running the entire shift report — highlight exceptions and actions only.
• Make the board visible on the shopfloor and accessible on mobile for remote supervisors.
• Record every action via the board or an interactive form so follow-up is traceable.
• Celebrate quick wins — short recognition helps sustain participation.

Example Script Snippets

• Facilitator: "Good morning — safety note first. OEE is 62% (red) mainly driven by 45 minutes of downtime on machine 3. Data champion, confirm source?"
• Data champion: "Confirmed — downtime logged at 09:12–09:57, cause: spindle failure. MTTR recorded as 45 minutes."
• Facilitator: "Action: Inspect spindle and order spare. Owner: Alex. Due: 14:00 today. Escalation level 2 if unresolved by 14:30."

How to Use

Configure your dashboard to these specs using your MES/OEE tool or a validated spreadsheet. Run a 2‑week pilot and use the Pilot & Tuning Plan above to refine thresholds. Ensure the team understands roles and that every action has a named owner and a due time. After pilot, lock the dashboard as the single source of truth for the huddle and consider adding interactive capture of actions so historical follow-up is easier.

Next Steps & Suggested Attachments

• Attach a 1‑page cheat sheet of calculations for the data champion.
• Create an action tracker template (CSV or interactive form) to capture actions and auto-store them for follow-up.
• Consider adding a short training video for the first-line team explaining the huddle flow and roles.