Executive summary
The subject should not be treated as an isolated technical point. It must be read as an industrial transformation challenge: decision quality, operational robustness, operational support capacity and measurable value creation.
The difference between a standard approach and a rigorous approach is the depth of the diagnosis. It is not enough to identify what is malfunctioning. It is necessary to understand why the organization has allowed this dysfunction to settle, what decisions have not been taken, which indicators have masked the problem and what governance will prevent its reappearance.
Industrial digital performance does not come from the stacking of tools. It comes from the alignment between processes, data, responsibilities, systems and management routines.
The problem: OEE is measured, but performance does not improve
OEE is often displayed as a flagship indicator of industrial performance. However, it often happens that it is discussed without producing structuring decisions. The figure exists, the dashboards are available, but the causes of losses remain poorly qualified, the actions are not tracked, the responsibilities are unclear and the shop-floor routine does not change.
The differentiating point is simple: a useful OEE is not an indicator, it is a management system. SAP and MES can make the measurement more reliable, automate collection, link production, quality and maintenance, and accelerate analysis. But without a loss model, without a decision ritual and without data governance, they will only industrialise reporting that does not support action.
The question to ask is not, “Do we have an OEE? " The real question is: “What operational decisions does our OEE trigger every day, every week and every month? »
Clarify the definition of OEE before digitizing
OEE combines availability, performance and quality. This apparent simplicity masks many decisions. What counts as required production time? What stops are excluded? How to treat micro-stoppages? Which nominal rate should be used? Are the scraps captured at the operation, the batch, the station or the end of the line? Are rework considered as loss of quality or loss of performance?
Before you configure an MES or exploit SAP data, you need to stabilize these definitions. Without this, every site, line or team can produce a mathematically correct but operationally non-comparable OEE.
| Component | Common decisions | Risk if not clarified |
|---|---|---|
| Availability | Scheduled shutdowns, format changes, maintenance, quality hold | Biased comparisons between lines or teams |
| Performance | Standard rate, actual rate, micro-stoppages, underspeed | Loss of credibility of the indicator |
| Quality | Scrap, rework, rejections, blocked batches, start-up losses | Underestimation of actual quality losses |
| Consolidation | Line, shop floor, site, product family, period | Aggregate OEE that masks the bottlenecks |
Connect SAP, MES and shop floor without creating an overly complex system
In a target architecture, SAP typically carries orders, materials, bills of materials, routings, batches, quality status, inventory movements, maintenance and costs. MES carries detailed execution, machine events, operator reporting, downtime, causes of loss, operational monitoring and sometimes work instructions. The equipment provides real-time signals.
The value comes from the alignment of these layers. A machine shutdown can create a loss of availability in MES, trigger an SAP PM notification or order if the cause is maintenance, impact SAP PP production plan and feed a continuous improvement action plan. Conversely, a bad architecture produces duplicate data entry or contradictory indicators.
Build an actionable loss taxonomy
The granularity of the causes of losses is a major decision. Too few causes do not allow action. Too many causes make the input painful and degrade the quality of the data. The right level is the one that allows an operational decision.
An effective taxonomy distinguishes losses related to equipment, format changes, materials, quality, organisation, methods, internal logistics, waiting, micro-stoppages and speed losses. It must be understood by the operators and actionable for managers.
| Family of losses | Examples | Expected decision |
|---|---|---|
| Equipment | Failure, unstable adjustment, sensor, safety stop | Plan PM, recurrence analysis, reliability equipment |
| Material | Lack of component, material defect, change batch | Supply chain action, supplier quality, critical inventory |
| Organization | Operator's Expectation, Team Change, Away Record | Standard of work, staffing, training, visual management |
| Quality | Scrap, rework, batch blocking, non-compliant start | Cause analysis, quality plan, process adjustment |
| Performance | Underspeed, micro-stoppages, unknowned rate | Line analysis, adjustment, standard cadence, continuous improvement |
Anonymised case study: gain 2 points of OEE without adding sensors
On an automated line, the site planned to invest in more advanced machine collection to improve OEE. The analysis showed that the existing collection was sufficient for a first phase, but that the losses were poorly qualified. Operators mostly recorded generic causes such as “technical shutdown” or “wait.” Reporting existed, but it did not support action.
The project consisted in simplifying the taxonomy, training the teams for useful entry, linking the five main causes to daily management routines and creating a weekly production/maintenance/quality ritual. Some of the losses identified actually came from micro-stoppages related to the change in format and waiting time material at the edge of the line.
The value was not created by a new screen. It was created by an understandable loss model, an analytical discipline and a recurring action plan. This is an important lesson: digitalization can accelerate improvement, but it does not replace managerial clarity.
Link OEE, SAP PM and preventive maintenance
OEE becomes much more powerful when it feeds maintenance. Recurrent availability losses must be related to equipment, sub-equipment, causes of downtime, notices and maintenance orders. Without this loop, losses remain production events, not levers of reliability.
However, integration with SAP PM must be pragmatic. Not all stops should generate an order. The rule must distinguish significant incident, recurrence, duration threshold, criticality equipment and need for analysis. Otherwise, the organization creates an unusable volume of reviews.
Link OEE, SAP QM and quality losses
The quality component of OEE should not be treated as a simple percentage of scrap. Quality losses must be related to batches, critical features, defects, causes, suppliers, process steps and release decisions. SAP QM can provide a robust structure when controls, inspection batches and usage decisions are aligned with MES and shop floor.
The risk is to separate the world from performance and quality. A quality loss not related to the process causes becomes an accepted cost. A quality loss related to the order, batch, position and action plan becomes a lever for improvement.
Move from dashboards to a management system
The trap of digital programs is to deliver dashboards without transforming routines. An OEE dashboard must be designed based on the decisions it should serve. A daily meeting does not need the same level of analysis as a monthly performance review. A team leader, a maintenance manager and an industrial management do not need the same screen.
| Level | Expected decision | Useful view |
|---|---|---|
| Team / quarter | Responding to the losses of the day | Top stops, open incidents, immediate actions |
| Line Manager | Prioritizing Recurrent Causes | Pareto losses, trend, actions, managers |
| Site | Arbitrate Investments and Resources | OEE by line, major losses, ROI, risks |
| Group | Compare and standardize | Harmonized definitions, maturity, good practices |
Decision checklist
- Align on the definition of OEE before any digital deployment.
- Limit the taxonomy of losses to the level that actually allows the action.
- Distinguish between automatic, manually reported, calculated and corrected data.
- Connect equipment losses to SAP PM when it creates value.
- Link quality losses to SAP QM, batches and process causes.
- Design dashboards around decision-making routines.
- Measure the quality of loss-cause capture, not only the final OEE figure.
Operational conclusion
Improving OEE with SAP and MES requires going beyond reporting. Value is created when losses are defined, captured, classified, assigned to clear owners and converted into action.
Fenlynks helps build this complete chain: the data model, SAP/MES architecture, shop-floor routines, indicators and performance governance.
Fenlynks provides scoping, rapid audits, business project support (AMOA), project governance, testing assurance, SAP/MES roadmaps, change management and post-go-live stabilisation.