Automotive MES Operator Dashboard Design Best Practices

By David Cook on October 7, 2026

automotive-mes-operator-dashboard

An automotive MES operator dashboard should tell a person on the line three things in a glance: am I on target, is anything wrong, and what should I do next. Most MES screens do not. They are designed by engineers, packed with tags and trends, and hard to read from two meters away in gloves. This guide covers practical design rules for operator screens, backed by HMI standards and research, with numbers you can apply this week. To see an operator dashboard built this way, book a short walkthrough.

Automotive execution · Operator dashboards

Automotive MES Operator Dashboard Design Best Practices: Screens Operators Actually Use

Show the count, the problem and the next step. Keep everything else one tap away. Design rules that turn an MES screen into action on the floor.

Quick numbers
48% vs 10%
Share of abnormal events operators caught before an alarm on a well-designed interface versus a traditional one (ASM Consortium study)
~4
Items people hold in working memory at once (Cowan, 2001)
~1 cm
Recommended minimum touch target size (Nielsen Norman Group)
What an operator needs from a screen
Question and what to showWhere
Am I on target?
Top of screen
Count against plan for this hour and shift
Is anything wrong?
Center
One clear abnormal signal
What do I do next?
Beside the problem
The next action in plain words
Who do I call?
Always visible
Help request for quality, material, maintenance
Key takeaways
1
Operators need answers, not data

On target or not, what is wrong and what to do next.

2
Less on the screen works better

People track about four things at once; most MES screens show dozens.

3
Color is for problems only

A calm gray screen makes the one abnormal item stand out.

4
Test with the people who use it

Five minutes at the station tells you more than a design review.

01The problem

Why Most MES Screens Fail Operators

Most MES screens are built to show everything the system knows, not what the operator needs.

  • Too much on one screen. Dozens of values compete for attention.
  • Engineer language. Tag names and codes where plain words are needed.
  • Small text and targets. Unreadable at arm’s length and hard to press with gloves.
  • Color everywhere. When everything is bright, nothing stands out.
  • No next step. The screen shows a fault but not what to do about it.
48% vs 10%

In a study with 21 professional operators, those using a well-designed interface spotted abnormal events before any alarm 48% of the time. On the traditional interface it was 10%.

Source: ASM Consortium study, reported by Chemical Processing

That study was in a chemical plant, but the lesson travels. The same people did much better with a clearer screen.

A screen review at one station shows the gap quickly. We can do one with you on a call.

02Who it is for

Operator View vs Engineer View

Operators and engineers ask different questions, so they need different screens.

Engineer view
  • Every signal available
  • Trends over hours and days
  • Tag names and addresses
  • Used at a desk
  • Time to explore
  • Goal: find root cause
Operator view
  • A handful of key values
  • Now, this hour, this shift
  • Plain words
  • Used standing, in gloves, at a distance
  • Seconds to read
  • Goal: act now

MES sits at Level 3 of the ISA-95 model, between the controls on the floor and the business system above. It holds far more data than any one person needs, which is why role-based views matter.

Building the operator view first, then the others, keeps the focus right. See role-based views in a demo.

03Core content

The Five Things an Operator Screen Must Show

If a screen shows these five things clearly, it is already better than most.

1
Count against target

Jobs done versus plan for this hour and this shift, with the gap as a number.

2
Current state

Running, waiting, stopped or changeover, in one word.

3
The one problem

The most important abnormal condition, in plain language.

4
The next action

What to check or do, taken from the work instruction.

5
Call for help

One press to call quality, material or maintenance.

Example: where operator attention goes
Target vs actual count41%

Current fault and next step30%

Quality alerts16%

Material calls9%

Everything else4%

Illustrative. Give screen space in the same proportion.

Everything else belongs on a detail screen, one tap away. Our specialists can help decide what moves.

04Structure

Use a Display Hierarchy

The ISA-101 standard for HMIs organizes displays into four levels, from overview to detail.

LevelPurposeAutomotive example
Level 1Overview of the whole span of controlLine or zone status board: count, state, top issue
Level 2Operating display for an areaStation screen: target, current job, quality checks
Level 3Detail for troubleshootingRobot or tool detail: faults, cycle steps, history
Level 4Support and diagnosticsWork instructions, wiring views, maintenance procedures

Most operators live on Level 2 and glance at Level 1. Levels 3 and 4 are for when something is wrong.

One power company cut its graphics from 300–500 per plant to 75–85 after applying these ideas. Fewer, better screens.

A clear hierarchy also makes training easier. We map yours in every rollout.

05Color

Color, Contrast and Alarms

High-performance HMI design uses a calm background and saves strong color for abnormal conditions.

Background
Gray or muted, with low-contrast shapes. No gradients, shadows or 3D effects.
Normal state
Shown quietly. Normal should not shout.
Abnormal state
Strong color reserved for problems and alarms only.
Redundant coding
Priority shown by color, shape and text together, never color alone.
Targets and ranges
Show the value against its normal range so the operator sees where they are compared with where they should be.
Animation
None unless it carries meaning.
1 in 12

men have red-green color vision deficiency. A screen that relies on red against green fails for them.

Source: City St George’s, University of London

Shape and text beside color solve this at no cost. Ask our team for a sample palette.

06Sizing

Sizes That Work on the Shop Floor

Operators read from a distance and press with gloves, so sizes matter.

~1 cm
minimum touch target recommended by Nielsen Norman Group
Nielsen Norman Group
1 inch per 10 ft
letter height for viewing distance, a signage rule of thumb
Signs.com
About 4
chunks of information held in working memory
Cowan, 2001
  • Make buttons larger than the minimum. Gloves and movement call for more than a phone-sized target.
  • Size the main number for distance. A count read from 3 meters needs digits about 2.5 cm tall by the signage rule.
  • Limit the main view. Four or five key items, not twenty.
  • Leave space. Gaps between buttons prevent wrong presses.
  • Check in real light. Glare and dust change what is readable.

A quick test is to stand where the operator stands and read the screen aloud. Our engineers do this on every station.

07Layout

A Simple Layout That Works

A consistent layout means operators find things without thinking.

Top
Count and target

Jobs this hour and shift against plan, large digits.

Center
State and problem

Line state and the single most important issue.

Right
Next action

The step to take now, in plain words.

Bottom
Help calls

Buttons for quality, material and maintenance.

Left
Current job

Model, variant and any special checks.

Hidden
Detail

Trends, history and diagnostics one tap away.

Keep the same layout at every station. An operator who moves from trim to chassis should not have to relearn the screen.

See the layout on a real station in a session.

08Andon

Andon and Help Calls on the Screen

The dashboard should make it easy to call for help and easy to see that help is coming.

In plain words
Andon

A visual management tool that shows the status of operations at a glance and signals whenever an abnormality occurs, in the words of the Lean Enterprise Institute.

Step 1
Call

Operator presses one button for the type of help.

Step 2
Signal

Board, light and team leader’s device show the call.

Step 3
Acknowledge

The operator sees who is coming.

Step 4
Resolve

Cause recorded in a few taps.

Step 5
Learn

Calls counted by station and reason.

The acknowledgement step is often missing. An operator who cannot tell whether the call was seen will call again or stop asking.

Call history by station is one of the most useful improvement tools a plant has. Discuss it with our advisors.

09Roles

Role-Based Views From the Same Data

One MES, several views. Each role sees what it needs.

RoleMain questionScreen focus
OperatorAm I on target and what do I do next?Count, state, problem, action, help
Team leaderWhich station needs me?Open calls, stations behind, quality alerts
SupervisorWill we make the shift number?Line rate, losses by cause, staffing
MaintenanceWhat is failing and why?Fault history, repeat faults, open work orders
EngineerWhat is the root cause?Trends, cycle steps, detailed signals

The MES market is growing fast, from an estimated $15.95 billion in 2025 to $25.78 billion in 2030 according to MarketsandMarkets. Much of that spend will be judged by whether people on the floor actually use the screens.

Designing for roles from the start avoids rework later. We can sketch your role views in a working session.

10Testing

Test the Screen With Operators

The fastest way to improve a dashboard is to watch someone use it.

Step 1
Draft

Build a simple version of the screen.

Step 2
Observe

Watch three or four operators use it for real.

Step 3
Ask

What did you look for? What was missing?

Step 4
Remove

Take off anything nobody used.

Step 5
Repeat

Test again after each change.

  • Time to answer. How long to say whether the line is ahead or behind?
  • Time to act. How long from a fault appearing to the first correct action?
  • Wrong presses. How often is the wrong button hit?
  • Unused items. Which parts of the screen are never looked at?

These four measures make design discussions short. A screen review gives you a baseline.

11Checklist

MES Operator Dashboard Checklist

Use this list to review any operator screen.

Content
Count against target is the largest item
One clear problem shown at a time
Next action in plain words
Help call always visible
Clarity
Calm background
Strong color only for abnormal states
Shape and text beside color
No decorative graphics
Use
Readable from working distance
Buttons sized for gloves
Same layout at every station
Detail one tap away
Process
Tested with real operators
Unused items removed
Role-based views defined
Reviewed after every model change

Most screens fail on content before they fail on style. We can run this check with you in a pilot.

12iFactory

How iFactory Builds Operator Dashboards

iFactory sits on top of your MES, PLC and quality data and gives each role a screen designed for its job.

The count, the problem and the next step, on every station.
01
Operator screens

Target, state, top issue and action.

02
Plain language

Fault codes translated into words and steps.

03
Help calls

One-press andon with acknowledgement.

04
Role views

Team leader, supervisor, maintenance and engineer.

05
AI assistance

Suggested next step from fault history.

06
Works with your MES

An overlay, not a replacement.

It runs on premises on the iFactory server. Send a photo of one current screen and we will redesign it in a trial.

Screen review

See One of Your Operator Screens Redesigned

Send a photo of a current station screen. We redesign it around count, problem and next step, and show both side by side.

Illustrative alert
Operator screen · Weld cell 7

The current screen shows 46 values. Operators use 5 of them every cycle. The other 41 belong on a detail view one tap away.

Values used every cycle5 of 46

Window
Next screen release
Action
Move the rest to a detail view
13In practice

From 46 Values to 5

This is how a manufacturing engineer might work through a redesign.

Manufacturing engineer and iFactory AI
Engineer
Operators say the weld cell 7 screen is useless. What does the data say?
iFactory AI
The screen shows 46 values. In the last month, operators opened detail for only 5 of them: count, current fault, tip-dress counter, part present and quality hold.
Engineer
What do they do when a fault appears?
iFactory AI
On average it takes 40 seconds before the first correct action. The fault text is a code, and the instruction is on a separate page.
Engineer
What would you change first?
iFactory AI
Put those 5 values on the main view, show the fault in plain words with its first step beside it and move the other 41 to a detail view.
Turnkey hardware and software

iFactory ships as a pre-configured NVIDIA AI server, racked and ready with the operator dashboards and execution models loaded. Rack it, plug in power and Ethernet, and the AI is live. Scope covers data connections across press, body, paint, assembly and machining areas, PLC/SCADA, MES, CMMS and ERP integration, cabling and network setup, team training and 24×7 remote monitoring.

Weeks 1–4
Ship, network, data

Server installed, PLC, MES and CMMS links live, history loaded.

Weeks 5–8
Train models, pilot

Models tuned on your own lines, then piloted in one area with your team reviewing every output.

Weeks 9–12
Go live, train teams

Rollout to the agreed lines, team training done, 24×7 remote monitoring in place.

Software, server and integration come as one package. For pricing, contact our sales team.

FAQQuestions

Frequently Asked Questions

What should an MES operator dashboard show?

Count against target, current line state, the single most important problem, the next action and a way to call for help. Everything else belongs on a detail view.

How many items should be on an operator screen?

As few as possible. Research puts working memory at about four chunks, so four or five key items on the main view is a sensible limit.

What colors should an operator screen use?

A calm gray or muted background, with strong color reserved for abnormal conditions. Always pair color with shape and text, since about 1 in 12 men have red-green color vision deficiency.

How big should touch buttons be?

At least about 1 cm, per Nielsen Norman Group, and larger for gloved hands on the shop floor.

What is ISA-101?

The ANSI/ISA standard for human machine interfaces. It defines an HMI lifecycle and a four-level display hierarchy from overview to detailed diagnostics.

How long does it take to deploy new operator dashboards?

A first line is typically live within 6–12 weeks, working on top of your existing MES. Plan it with our specialists.

Next step

Give Operators a Screen That Helps

iFactory turns MES data into operator screens that show the count, the problem and the next step, with help one press away.

Illustrative dashboard view
What operators look at, share of glances
Target vs actual count41%

Current fault and next step30%

Quality alerts16%

Material calls9%

Everything else4%

Illustrative. A good operator screen gives most of its space to the top two rows.


Share This Story, Choose Your Platform!