ThingConnectBook a demo

OEE software

OEE software your operators don’t have to feed

ThingConnect calculates OEE from data it reads directly off the CNC controller — machine state, part counts, cycle times — so availability, performance, and quality reflect what actually happened on the floor, not what got written on a form at shift end.

Product simulation

Why OEE numbers usually can’t be trusted

  • Availability comes from a logbook filled in at 5:55 PM, from memory.
  • Every department calculates OEE differently, so meetings argue about the number instead of the loss.
  • Micro-stops never get recorded — the 4-minute stops that add up to an hour a shift are invisible.
  • The spreadsheet takes a day to compile, so the loss is a week old before anyone sees it.

How ThingConnect does it

Controller-sourced A × P × Q

State and counts come from the control itself. The three OEE components are shown separately, with the math visible — numbers people can interrogate get trusted.

Your plant’s OEE rules

Tea breaks, planned maintenance, changeovers — you decide what counts against availability. The definitions are configured once, applied consistently, and printed on every report.

Live, not month-end

Shift OEE updates as parts drop. Supervisors see the gap while the shift can still close it.

Common questions

How does ThingConnect calculate OEE?

As availability × performance × quality. Availability and performance come from controller data (run state, cycle times, part counts); quality comes from good/reject counts entered by operators or read from the control where available. Each component is shown separately so the number is auditable.

Can we change what counts against availability?

Yes — that is a core feature. Planned maintenance, tea breaks, trial runs, and changeovers are classified per your plant’s rules, configured during deployment and adjustable later by your admin.

Do operators need to enter data for OEE?

Not for availability and performance — those are read from the controller automatically. Operators only classify downtime reasons (two taps) and enter reject counts where the control can’t report them.

Does OEE data leave our plant?

No. ThingConnect runs on a server inside your plant. Production data stays on your network.

See it on machines like yours

A 30-minute demo, then a pilot on your own floor if it fits.