Defining the source of the data to be reported
A monitoring project begins by identifying which machine and signal will generate each displayed value. PLC access, existing sensors, communication options and the facility network are examined. Running, waiting, fault and planned-stop definitions are clarified with the business so that different states on different machines are not counted under the same heading.
- The condition that increments the production counter and the source of good-product classification
- Shift times, timestamps and reporting periods
- Data retention period, user roles and access requirements
Establishing the connection from the field to the screen
After the required sensors, data-acquisition and communication components are selected, installation points and connection scope are determined. The engineering work includes data mapping, record structure and user screens. Network access is coordinated with the facility’s IT team. If machine control is requested in addition to monitoring, permissions and control responsibilities are evaluated separately.
- Machine-specific views of status, counters and alarms
- Avoiding the presentation of stale values as current when a connection is lost
- Recording behaviour after an outage and visibility of data gaps
Comparing reports with actual production
At acceptance, field counts and time records from selected machines are compared with system outputs. Counter reset, shift change, connection loss and restart scenarios are tested. The update interval, acceptable data difference and report scope are agreed in advance. Ensuring that authorised users can reach the correct screens is also part of the handover checks.
- Matching field and screen totals for the same time interval
- Checking downtime by cause and shift
- Clarifying data-export and backup responsibilities
Frequently asked questions
Can production data also be collected from older machines?
Some data can be collected through existing outputs or suitable additional sensors. The values that can be obtained reliably are assessed at the machine; unavailable information is not filled in by assumption.
Can an OEE report be prepared directly?
In addition to running time, inputs such as planned production time, ideal cycle time and good-product quantity are required. OEE can be included in the scope if the data sources and calculation definitions are verified.
Will recording continue if the internet connection fails?
This depends on the selected local recording and communication architecture. The data to be retained during an outage, capacity and transfer behaviour when the connection returns are defined and tested at the beginning of the project.