ServicesV — Industrial Applications: Production, Quality and Warehouse
Line Data, OEE and the MES/SCADA Connection
Production data exists as three separate truths — in the machine, in a spreadsheet and in the ERP. Downtime reasons are typed in by hand, OEE comes out differently in every department, and the shift report barely makes it to the morning meeting.
We take the data where the machine speaks it — PLC/OPC UA, the SCADA archive or an existing MES — and bring it into one production data layer. Stoppages are labelled automatically and the operator only picks the reason the machine cannot tell apart. OEE is calculated once, in one place, with one formula, and the same number goes to the ERP.
Shift reports nobody assembles by hand, downtime reasons recorded at the moment the line stops, and one OEE number everybody looks at. How it is calculated is written down too — the argument moves from the formula to the data.
The machines have to be able to emit data: OPC UA, Modbus, a serial port or an existing SCADA archive. If they cannot, collection hardware is planned first — a separate job, run with your integrator.
We start with a single line: which machine, which tag, which stoppage class. Once data flows, three things follow in order — downtime records, the OEE calculation, the report. At every step the numbers are compared with the hand-calculated ones; where they differ, the difference is explained before anything moves on.
We do not write PLC programs or touch machine automation. We do not sell an MES either: if you have one we connect to it, and if you do not we build the data layer and treat "do you actually need an MES" as a separate decision.