OEE Score Card

Who it’s for

Production and maintenance teams who track OEE per line, machine, or shift — anyone asking “are we hitting our OEE target today, and what’s eating the difference: availability, performance, or quality?” without opening a separate report.

What it does

• Single OEE score, shown in your chosen accent color
• Availability, Performance, and Quality shown as individual bars, each checked against its own threshold and colored good or critical accordingly, with supporting detail rows — uptime/downtime, actual/ideal count, good/defect count
• Optional target bar comparing the current score against a goal, with a ”+/- pts vs target” readout
• Optional downtime breakdown: the top reasons for lost time, shown as a segmented bar and legend
• Supports more than one entity on the same card, with a dropdown to switch between them
• Switches to a compact single-column layout automatically on cards narrower than 480px, and updates live while you drag-resize the card on the dashboard

How to set up

Data Keys

Each row below has a matching field in the Key Mapping settings group. Type the exact key name your datasource uses for that role — the widget matches on the key’s name or its label, not by position — so leaving the defaults in place means a device or Calculated Field that already outputs oee, availability, performance, and quality plugs in directly. If your keys are named differently, point the matching Key Mapping field at your own key name instead of renaming your telemetry.

Note: downtimeReasons is optional — leave it out (or turn off Show downtime breakdown) and the whole downtime section disappears on its own, nothing else to configure. When you do provide it, store it as a JSON array of { label, time } objects, where time is converted using Downtime reasons time unit:

[
  { "label": "Mechanical failure", "time": 28 },
  { "label": "Material starvation", "time": 20 },
  { "label": "Changeover", "time": 6 }
]

Tip: set Key Mapping before adding a datasource — the Data Keys the widget suggests are generated from your current Key Mapping, so they’ll already carry the right names.

General settings

Each factor now has its own threshold — tune Availability, Performance, and Quality independently instead of one shared value for all three.

Downtime settings

Only apply while Show downtime breakdown is on.

How to Customize

General settings

• To hide the target bar — turn off Show OEE target section.
• To hide the Availability, Performance, and Quality bars — turn off Show OEE factors.
• To hide the downtime breakdown — turn off Show downtime breakdown.

Colors & theme

• To match your dashboard palette — set Main OEE progress color, Good status color, and Critical / bad status color.
• To recolor the track behind each bar — set Track background color.
• To recolor the subtitle, captions, and scale labels — set Secondary text color.

Typography

• To match your dashboard’s font — set Title font, Main score value font, Section labels font, Body text font, and Secondary text font individually.

Downtime settings

• To give specific downtime reasons a fixed color instead of the automatic palette — add rows to Downtime segment colors, matching each Reason name exactly to the label used in the downtime reason log.

Tips (optional)

• Add more than one entity as a datasource to get a built-in switcher for comparing lines or machines on a single card.
• The card’s layout keeps up in real time while you drag-resize it on the dashboard, so you can see the compact layout kick in before you let go.

See also

• Overall Equipment Effectiveness (OEE) Calculated Field — computes oee, availability, performance, and quality from your production data. Add this card on top of it and every key it produces plugs straight in, with no relabeling needed.

${item-link:45a8be40-8bee-11f1-a7f9-9fcf2c6d7d09}