OEE calculation: get the data right before the formula
Calculate availability, performance and quality for the same time window and the same definition of production.
Read the guideSolutions
Make production losses visible with consistent data.
Production managers and continuous-improvement teams
Relate downtime, output and quality to shifts and products. Track availability, performance and quality separately to identify which losses require action.
The OPC UA Client reads state, counter and downtime-reason tags.
Counter differences are taken and reset and missing-data rules applied; records are associated with shift and product.
Records are written to an SQL database with the source timestamp; OEE components are calculated in the database or the BI layer.
Pilot acceptance criterion
Compare calculated times and counts against production records for one shift. Flag performance over 100% and missing telemetry separately.
Connector availability, version compatibility and licence scope are verified for each project.
Calculate availability, performance and quality for the same time window and the same definition of production.
Read the guideOPC Router builds the workflow that collects counter, state and downtime data and delivers it to the destination. Where the OEE formula is calculated (in the workflow, in an SQL view or in a BI tool) is decided in the project. See the OEE entry for the definitions and try the OEE calculator.
Performance can exceed 100% when the ideal cycle time is defined slower than the real speed or when a counter reset is misread. Flag it as an error and review the ideal cycle. See common OEE measurement mistakes for detail.
Your next step
Share your source, destination and intended outcome. We’ll help define the project scope.