When you compare MES and OEE vendors, you expect a line to have one OEE number, not three. Yet many manufacturers see different OEE results for the same equipment, depending on which tool, screen or report they open. The cause is rarely the math itself. It is usually different definitions, hidden filters and inconsistent data capture.
This article explains how MES vendors calculate and filter OEE, why two tools show two numbers for the same line and how to evaluate platforms so that OEE reflects true performance, not a filtered version of reality.
Request a demo
1. Start with the basic OEE formula, then look at the data beneath it
Most serious MES and OEE platforms use the same textbook OEE formula:
- Availability: Run time divided by planned production time
- Performance: Actual output divided by ideal output at standard rate
- Quality: Good units divided by total units produced
- OEE: Availability × Performance × Quality
The real differences appear one layer below the formula:
- What exactly counts as planned production time
- Which stops are treated as downtime versus not planned to run
- How scrap and rework are recorded and at what point in the process
- Which speed is considered the standard rate for performance
When you compare MES vendors, you are not just comparing calculations. You are comparing the data model and assumptions that feed those calculations.
2. Define your “planned production time” before you compare tools
Planned production time is the foundation of OEE. If two vendors interpret it differently, every comparison will be misleading. Common vendor differences include:
- Including changeovers and setups as part of planned time, or excluding them as planned loss
- Handling breaks and meetings as planned loss, or as part of planned production time with custom availability codes
- Planned maintenance treated as not planned to run, or as downtime that reduces availability
- Line not scheduled excluded from the denominator in some systems, included in others for high level KPIs
If one MES counts breaks and changeovers inside OEE and another keeps them outside, the second will show a higher number, even if the line performance is identical.
Clarify with each vendor:
- What is in the OEE denominator by default
- Which time categories can be toggled in or out of calculations
- How they handle overlapping events, such as maintenance during a changeover
3. Availability: how downtime is captured and classified
Availability is the metric that is most distorted by inconsistent definitions. Key questions to ask any MES vendor:
3.1. What counts as downtime versus minor stops
- Is there a minimum duration that counts as downtime, for example stops shorter than a certain number of seconds classified as micro stops or even ignored
- Are micro stops included in performance instead of availability
- Can users reclassify a micro stop as full downtime if it repeats frequently
If one system ignores frequent 20 second stops and another tracks them as downtime, you will get very different availability values for the same line.
3.2. Automatic versus manual downtime capture
- Automatic capture from machines: Uses signals such as machine state, speed or current consumption to detect stops
- Manual input: Operators log downtime events on terminals
Automatic capture, like Fabrico uses, greatly reduces missed events and misclassification. If a vendor relies heavily on manual input without strong machine integration, expect gaps in small stops, changeovers and short failures. The OEE will often look better than reality.
3.3. Downtime reasons and overlapping events
Every vendor supports downtime reasons, but the logic differs:
- Can operators assign multiple reasons to the same stop, for example mechanical failure and material shortage
- Does the system allow hierarchy of reasons, such as category, subcategory and root cause
- How are long changeovers with embedded cleaning, adjustments and checks represented
Overlapping events are especially important for maintenance versus production delays. A maintenance task started during a material shortage might be double counted as downtime in some systems if the data model is weak.
4. Performance: speed definitions, micro stops and short runs
Performance tells you whether the line is running at the expected rate. Differences between vendors often come from how they define the ideal speed and how they treat short interruptions.
4.1. Ideal cycle time and standard rate
Ask each MES vendor:
- Where does the ideal cycle time come from, such as ERP routing, engineering standards, product master data, historical performance
- Is the ideal speed per product, per SKU, per line or per work center
- Can the ideal rate change based on packaging, format or shift
- How are ramp up and ramp down periods handled during startups and shutdowns
If one system uses a historical average instead of a true standard rate, high OEE may simply mean you did better than your own past performance. That is not the same as meeting engineering expectations.
4.2. Micro stops and speed losses
Performance losses often hide in micro stops and slow running. Good MES tools capture:
- Short stops that do not trigger a full downtime event
- Reduced speed compared to the standard, even when the machine is technically running
Ask vendors:
- How do you detect and store micro stops
- Do micro stops reduce performance, availability or both
- Can we report speed loss by cause, product and shift
Some vendors ignore micro stops and treat everything as running at standard speed until a full stop occurs. That will inflate performance numbers.
To go deeper into how modern OEE tools collect and analyze this data, see the overview of OEE platforms in this article:
OEE software: what matters beyond the OEE score.
5. Quality: where and when scrap is counted
Quality seems straightforward, but in practice different MES implementations can give very different quality components even with identical scrap quantities.
5.1. Definitions of good, scrap and rework
- Are reworked units counted as good, scrap or something in between
- When a unit fails later in the process, is the scrap attributed to the first operation or the last one
- Can specific defect codes be tied to equipment, shift or operator
If quality is measured at final inspection only, you lose the ability to link scrap to particular machines or events. The OEE for upstream equipment will look better than it should.
5.2. Inline versus downstream quality checks
Ask vendors:
- How do you handle inline inspection versus downstream inspection results
- Can OEE be reported at each operation with local quality numbers, not only at the final line
- Do quality events link back to the production and downtime events that created them
The more granular the quality tracking, the more reliable the OEE you get for each machine and cell.
6. Hidden filters: why two tools show two OEE numbers
Even if two systems share the same definitions, filters in the user interface can generate different OEE numbers for the same equipment and time range.
6.1. Time range and shift boundaries
Typical filters that change OEE:
- Calendar day versus shift day, when midnight splits a shift in two in some tools
- Local time versus UTC for multi site deployments
- Partial shifts, for example first 4 hours only, if an operator picks a custom time window
When you compare MES vendors, always ask for OEE based on a clearly defined range, such as one full shift with specific start and end times.
6.2. Product and order filters
Many platforms let users filter OEE by product, SKU or work order. The same line and day can then produce multiple OEE values:
- OEE for one product only, ignoring other orders run in the same period
- OEE for all products, which includes changeovers between them
- OEE that ignores special runs, trials or engineering tests
Clarify how each system:
- Handles overlap between orders during changeovers
- Attributes downtime during a changeover to the previous or next order
- Treats test runs or engineering trials in dashboards and reports
6.3. Event and category filters
Vendors sometimes use filters to keep certain events out of standard OEE. For example:
- Excluding planned maintenance from availability
- Ignoring very short stops below a configured threshold
- Filtering out specific downtime reasons, such as force majeure events
Ask to see:
- The raw event log for a sample period
- The OEE dashboard for the same period
- Exactly which events are ignored, grouped or treated as planned loss
If you cannot reconcile the log with the KPI screens, you will struggle to build trust in the numbers.
7. Unified data: one version of the truth across lines and plants
Differences in OEE definitions are amplified when you deploy across multiple sites, each of which might have its own way of defining downtime, speed and scrap. You need a data model that can standardize OEE definitions, but also reflect local realities.
Ask MES vendors how they:
- Standardize time categories and loss models across plants
- Manage global versus local master data for machines, products and reasons
- Handle different shift patterns and calendars within one company
Fabrico uses unified production and maintenance data to keep OEE definitions consistent across sites, while still allowing local configuration. This approach is discussed in more detail here:
Best OEE software with unified data intelligence.
8. Automated data capture: avoiding OEE inflation
Manual data entry and spreadsheet based OEE calculations almost always inflate performance. Small stops go unreported, setups are inconsistently captured and scrap data appears late or incomplete. When you move to an MES, you should not simply reproduce those biased numbers in a nicer interface.
To ensure OEE reflects reality, focus on:
- Machine connectivity: direct signals for states, speed, counts and alarms
- Integrated maintenance actions: each significant loss can trigger tasks, inspections or analyses within the same platform
- Event timelines: a clear visual timeline that matches the shop floor narrative
- Audit trails: who reclassified a stop, when and why
Fabrico captures production and downtime data straight from the machines, then uses the built-in maintenance management capabilities to turn each loss into specific actions for production and maintenance teams. This helps keep OEE honest: every loss is visible, traceable and actionable on both sides.
9. Built-in maintenance: linking OEE losses to real fixes
OEE by itself is an indicator. Value comes when every loss is linked to a concrete action that reduces future losses. This is where having maintenance management capabilities inside the same MES and OEE platform matters.
When you evaluate vendors, ask:
- Can a recurring downtime reason directly create a maintenance task or plan
- Are completed maintenance activities visible next to the OEE timeline for the same equipment
- Can you correlate failures, work orders and OEE trends without exporting data to another tool
If production and maintenance data live in separate systems, you will spend time reconciling them and still have weak traceability between OEE losses and work done to eliminate them.
Request a demo
10. Practical checklist: questions to ask every MES and OEE vendor
Use this checklist when you compare platforms, including Fabrico, so you can see how each one will represent your true performance.
10.1. Definitions and configuration
- How do you define planned production time and which time categories are in the OEE denominator
- Can we configure what counts as planned loss versus downtime
- How are breaks, meetings and training represented
- How is ideal cycle time defined and managed for each product and line
10.2. Data capture and integrity
- What machine signals do you collect for states, speed and counts
- How do you detect and classify micro stops
- Can I see a raw event log and how it rolls up into OEE reports
- How do you prevent double counting of overlapping events, such as maintenance during a changeover
10.3. Filters and reporting
- Which filters can change the OEE value, such as time, product, order, category
- How do you handle shift boundaries that cross midnight
- Can we standardize filters for corporate reporting, so everyone sees the same numbers
10.4. Multi site and governance
- How do you support consistent OEE definitions across multiple plants
- Can we have global templates for reasons, codes and KPIs with controlled local changes
- What audit trail exists for changes to OEE configuration
10.5. Maintenance integration
- How are OEE losses connected to maintenance tasks, inspections and improvement actions
- Can we track the effect of maintenance work on future OEE
- Do operators and maintenance technicians work in the same platform when responding to downtime
11. How Fabrico approaches OEE for manufacturing leaders
Fabrico is a cloud based MES and OEE platform built for manufacturers that want accurate, actionable performance data without drowning in configuration and custom integrations. It:
- Captures production and downtime data directly from machines, reducing manual entry and missed events
- Calculates OEE and losses in real time, with transparent definitions and configurable time models
- Uses the built-in maintenance management capabilities to turn each loss into targeted actions for production and maintenance teams
- Provides unified data across sites so line level realities and corporate KPIs use the same source of truth
If you are comparing MES and OEE tools and want to understand how Fabrico would reflect your specific definitions and constraints, reach out to our team:
Contact us.
12. Next steps: evaluate OEE tools with your data and constraints
To move from theory to practice:
- Document your current OEE definitions, including what is in and out of planned production time
- List key pain points, such as inconsistent numbers between plants, unreliable downtime capture or lack of traceability from OEE to maintenance work
- Use the checklist in this article to structure your vendor conversations
- Run pilot evaluations using the same lines, periods and filters in each system
For a broader comparison of OEE software options and how they differ in architecture, data model and usability, see:
Best OEE software: how to choose for real world manufacturing.
If you want to see how Fabrico applies these principles on real production lines, you can:
Request a demo
Login
Blog
