Back to all posts
Plant Data7 min read·October 25, 2026

What Should a Production Shift Dashboard Show?

TB
ThynkBlox Automation Team
Automation Engineering

What should a production shift dashboard show?

A production shift dashboard should show where the shift stands against its plan, what is limiting production and what the team can do next. It should also make clear how current the information is and provide a route to the detail behind each exception. Choose information around decisions the shift team can make, with definitions that everyone reading the screen understands.

Start with a practical question: if this value changes, who needs to do something? Give the main screen to information with a clear answer.

What belongs on the main screen?

Use the opening view to answer the questions raised during a shift review.

QuestionRecommended displayUseful next step
What are we making?Line, order, product and shiftOpen the order details
Are we on plan?Planned output by now, actual good output and gapCompare progress over the shift
What is holding us back?Current constraint, start time and confirmed reasonOpen the relevant event or work item
What needs attention?Unresolved issue, owner and next actionReview or update the action
Can we trust this view?Last valid update and missing-data statusInspect the affected data
What carries into the next shift?Open constraints and outstanding decisionsOpen the handover record

Treat this as a starting layout. A batch process may need batch stage and quality-release status where a repetitive assembly line needs good-unit counts.

Keep historical summaries available through drill-downs. Give them space on the main screen only when they change an immediate decision.

How should plan versus actual be presented?

Compare quantities with the same scope, unit and time boundary. Label whether actual output means total produced, accepted good output or completed orders. Show rejects, rework and material awaiting inspection separately where those distinctions matter.

Display the full-shift target alongside the target due by now. Ask the planner to define how that expected progress should develop through breaks, changeovers and scheduled stops.

Illustrative example: a shift has a target of 800 good units. At the review point, the agreed plan calls for 350 good units, and accepted output is 320. The current gap is 30 good units.

The screen should show all three values together. A comparison with only the full-shift target leaves the reader without a clear measure of progress at that point.

If the plan changes, retain the original target and identify the revision. Agree how units produced before and after a product change are counted. Avoid adding unlike products into a single quantity unless the team has defined a meaningful common unit.

Which constraints and actions should be visible?

Show conditions that currently prevent the team from meeting the plan. Candidate categories include equipment stops, missing material, unavailable labour, blocked downstream capacity and quality holds.

For each active constraint, request:

  • The affected line, operation or order.
  • When the condition started.
  • Whether the reason is confirmed or awaiting classification.
  • The person or role responsible for the next step.
  • The next action and review point.

Separate observed conditions from explanations. “Line stopped” can be the recorded state while “awaiting maintenance diagnosis” remains the reason status. Do not force an operator to select a guessed cause just to clear an empty field.

Keep the action practical: “Confirm replacement material availability” gives the shift lead something to follow up. “Improve material performance” belongs in a longer improvement discussion.

Use the dashboard to summarise production impact. Define alarm response separately; our guide to why operators ignore alarms covers decisions to make about alarm handling.

How should freshness and uncertainty be shown?

Put freshness beside the value it qualifies. Production counts, quality results and manually entered reasons may each have different update arrangements.

Define what “last updated” means. For a production count, distinguish the time of the last valid data update from the time the count last increased. A stopped line may have a valid, unchanged count.

Agree distinct labels for:

  • Current data received as expected.
  • Delayed data beyond the agreed update interval.
  • No valid data available.
  • Manually entered information.
  • Provisional information awaiting confirmation.

Set the delay threshold according to the process and the decision being made. Describe the expected update interval in the detail view.

When data becomes unavailable, retain the last valid value with a visible warning and its time. Do not replace an unknown quantity with zero. Provide a clear route for reporting a suspected data problem.

Where should each drill-down lead?

Give each main-screen value a specific destination.

Selecting the output gap should open planned and actual progress across the shift, with relevant stops and changeovers. Selecting a constraint should open its event history, reason and action. Selecting a quality hold should reveal the affected quantity and release status, subject to the reader's access.

Preserve the selected line, order and shift when moving between views. Include the count definition, unit and any exclusions where the reader inspects the calculation.

If OEE appears, provide access to its component calculations and underlying events. Our guide to what the OEE number hides offers a useful companion discussion when deciding how much space that summary deserves.

How can the dashboard support shift handover?

Reserve a compact area for unresolved work. Include active constraints, held material, pending checks and decisions the incoming team must revisit.

Illustrative handover entry: “Packaging line awaiting approved labels. Stores checking availability. Incoming shift to confirm supply before restarting this order.”

Keep the action status separate from the production state. A machine returning to operation does not necessarily mean every follow-up action is complete. Require an explicit closure decision where one is needed.

Let the incoming team open the supporting record and see the latest update. Avoid asking them to reconstruct the situation from a long list of closed events.

What should be agreed before building it?

Write down the meaning and ownership of each displayed item.

Use this acceptance checklist:

  • Every main-screen item supports a named shift decision.
  • Plan and actual use matching units and boundaries.
  • Good output, rejects and held quantities have clear definitions.
  • Breaks, changeovers and plan revisions have agreed treatment.
  • Missing, delayed and provisional data have distinct labels.
  • Active constraints have an owner and next step.
  • Drill-downs retain the selected production context.
  • Corrections and manual entries remain identifiable.
  • The display has been reviewed at its intended viewing distance.
  • Colour is supported by text or symbols with clear labels.

Record these choices in the functional design specification. Use realistic scenarios during acceptance: a normal run, a stop, a revised plan, a lost data connection and a shift change with unfinished work.

What common mistakes should you avoid?

Filling space with unrelated metrics. Start with the decisions required during the shift. Move measures without an immediate use into a supporting view.

Showing unexplained red and green indicators. Label the condition, its meaning and the next step. Make the rule behind each status available.

Hiding uncertainty. Identify an unconfirmed reason or stale value explicitly. Keep unknown data distinguishable from a confirmed result.

Presenting a forecast as a commitment. If you include projected end-of-shift output, label it as an estimate and explain its assumptions.

Treating the dashboard as a safety function. Keep production reporting separate from safety-related control. Any proposed safety-related design should be developed with a qualified assessor.

For long-cycle, experimental or highly variable work, reconsider hourly unit targets. Milestone completion, batch stage or readiness for the next operation may be more useful.

What are the frequently asked questions?

Should the dashboard show OEE?

Include it when the shift team has an agreed use for it. Keep output progress and active constraints visible, and provide access to the OEE calculation.

How often should it update?

Agree the interval from the decision the information supports. Display that expectation and show when valid updates stop arriving.

Can manual entries be included?

Yes. Label them, record their author and time, and define who can correct them. Make provisional entries recognisable.

How do you know whether the dashboard is ready?

Ask the shift team to explain the current position, identify the main constraint and find the next action using the proposed screen. Verify the displayed figures against agreed records before accepting it.

Next step

Want to apply this to your plant?

Every project starts with a fixed-fee assessment, and you can stop after the report.