Skip to content

Cookie preferences

We use cookies for our own analytics, to see how our campaigns perform and, if you allow it, to load content from other services such as the Google site search. We never sell your data. Necessary cookies keep the site working and cannot be switched off. See our Cookie Policy for details and our Privacy Policy for how we handle personal data.

Security, load balancing and remembering your cookie choice.

Show us which pages people read, how they find the site and where they get stuck, so we can improve it (Google Analytics, Microsoft Clarity).

Show us which of our ad campaigns bring visitors to the site and remember the campaign or partner link you arrived from (Google Ads, LinkedIn, Meta, partner program). We do not use these cookies to build advertising profiles.

Load the site search from Google when you use it. Google sets its own cookies and shows ads in the search results.

© 2026 The ThingsBoard Authors

ThingsBoard Cloud

Choose your data region

Your data stays in the region you choose, for residency and compliance. No credit card required.

Rather run it yourself? Install on your own servers

OEE Score Card

  • Widget
  • 20 installs
  • v1.0.0
  • Aug 28, 2026
  • MIT license
  • v4.2+

Displays Overall Equipment Effectiveness (OEE) as a single score with Availability, Performance, and Quality breakdowns, a target-vs-actual comparison, and a top-downtime-reasons chart for a device or asset.

Widget Type
  • Latest
Category
  • Cards & Info
Use Cases
  • Predictive Maintenance
  • Industrial Automation
  • SCADA

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.

Key Mapping field Role Type Description
OEE (%) — default oee Main score Timeseries Overall Equipment Effectiveness, 0–100
Availability (%) — default availability Availability factor Timeseries Availability %, shown as the first factor bar
Performance (%) — default performance Performance factor Timeseries Performance %, shown as the second factor bar
Quality (%) — default quality Quality factor Timeseries Quality %, shown as the third factor bar
Good items count — default goodCount Good units Timeseries Good-unit count, shown under Quality and used to work out defects
Total items count — default totalCount Total units Timeseries Total-unit count, shown under Performance and used to work out defects
Operating time — default operatingTime Actual run time Timeseries Time the equipment actually ran, shown under Availability as Uptime
Ideal cycle time — default idealCycleTime Ideal cycle time Attribute Design cycle time per unit, used to work out the Ideal count under Performance
Planned production time — default plannedProductionTime Planned production time Attribute Scheduled run time; the gap versus Operating time is shown as Downtime
Downtime reasons (optional) — default downtimeReasons Downtime reason log (optional) Attribute JSON array of downtime reasons, each with a duration; the breakdown section hides itself automatically if this key isn’t present

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

Setting Default Effect
Target OEE (%) 85 Sets the benchmark used for the target marker and the ”+/- pts vs target” readout
Availability threshold (%) 90 Availability bar and value use the good color at or above this value, the critical color below it
Performance threshold (%) 95 Performance bar and value use the good color at or above this value, the critical color below it
Quality threshold (%) 99 Quality bar and value use the good color at or above this value, the critical color below it
Time unit Minutes Unit that Operating time and Planned production time are stored in, used to work out Uptime and Downtime

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.

Setting Default Effect
Top N downtime reasons limit 2 How many of the longest-duration reasons from the downtime reason log are shown
Downtime reasons time unit Minutes Unit that each reason’s duration is stored in

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}

Share Your Widget with the Community

Built a custom widget? Export it as a JSON from ThingsBoard and publish it to the IoT Hub through a simple 4-step wizard (Upload, Listing, Readme, Review & Submit). Share it with thousands of ThingsBoard developers worldwide and get featured in the catalog.