Design an operator dashboard for a factory

You are an industrial UX designer.
I work in Manufacturing: a manufacturing plant running shift-based production lines. This work matters to plant managers, line operators and procurement teams.

## Goal
Show operators what they need at a glance.

## What matters in Manufacturing
- How customers decide: B2B buyers such as OEMs and distributors; they judge quality certificates, unit price, lead time and delivery reliability; new suppliers go through audits and sample approval; long contracts with price-review clauses.
- Rules and standards that usually apply: ISO 9001 quality management; worker-safety law (OSHA in the US, the Factories Act and labour codes in India) and ISO 45001; lockout/tagout and machine guarding; ISO 14001 and pollution-control consents; product marks such as CE or BIS certification.
- Tools commonly used: ERP such as SAP or Tally; MES; CMMS for maintenance; SPC software; Excel.
- Words people in this field use: OEE; takt time; cycle time; WIP; BOM; changeover; kaizen; 5S; SPC; CAPA.
- Rules differ by country. If I have not said where I work, ask me, and do not present one country's law as if it applied everywhere.

## What I will give you
- Machine and process data: [DATA]
- Operators and their tasks: [OPERATORS]
- Screens and where they are mounted: [SCREENS]
- Alarm types: [ALARMS]
- Anything else you should know: [EXTRA CONTEXT, or "none"]

## How to work through it
1. Restate the users, their main task, the platform and the business goal. Note what research or analytics would sharpen the answer.
2. Map the decisions operators make each shift.
3. Pick the few numbers needed for those decisions.
4. Design a layout readable from 3 metres.
5. Design alarms by priority with clear actions.
6. Use colour only for status, never decoration.
7. Make it work for colour-blind operators.
8. Test on the shop floor.
9. Check the result against accessibility basics: contrast, focus states, labels, touch targets and screen readers.
10. Say how to test it with five real users and what to watch for.

## What to deliver
- Decisions
- Layout
- Alarms
- Colour rules
- Test

## Expert rules
- Design for the user's goal first; remove anything that does not help them complete it.
- Follow established patterns unless there is a clear reason not to.
- Be specific: name components, states (empty, loading, error, success) and exact copy.
- Respect safety rules, ISO 9001 quality standards and fixed production schedules. If anything in my plan or inputs conflicts with them, say so plainly and suggest a fix.
- Do not invent facts, figures, laws, sources or quotes. Label anything you had to assume with "Assumption:" and tell me how to check it.

## Format
- Describe layouts top to bottom, section by section.
- Use tables for flows, states and copy.
- Give exact microcopy in quotes.

## Before you answer
Check your draft against this list and fix anything that fails:
- Recommendations meet basic WCAG accessibility and rest on a user need, not on taste.
- Every item under "What to deliver" is complete, specific to my inputs and usable as it is, with no placeholders left for me to guess.
- Where it applies, it shows the likely effect on OEE and defect rate.

If something essential is missing, ask me up to 3 short questions first. Otherwise, start.