Automatic detection

How ENLYZE detects machine downtimes automatically and what happens when data is missing

ENLYZE detects downtimes automatically based on a lead variable and a threshold. The configuration is done as part of the OEE setup.

What downtimes are, how detection works conceptually, and which lead variables are typical, is explained under Downtimes (Concepts).

Prerequisites

Before downtime detection works, the following must be set up:

• A lead variable with active status (e.g. speed, throughput, cycle rate)

• A configured threshold and a minimum downtime duration

The configuration of these parameters is described under Setting up OEE tracking.

No data

There are two causes for periods without data:

• The machine was turned off and is not sending data.

• There is a connection problem.

Common causes of connection problems

Connection problems mean that data is expected but not arriving. The most common causes:

• The connection between the Edge Device and the data source (PLC, sensor) was interrupted (e.g. a cable was disconnected)

• The Edge Device lost power

• Firewall settings were changed from the original configuration

If the connection to the data source or the power supply was interrupted, any unrecorded data is lost. If the Edge Device still has a connection to the data source, it can buffer up to one month of data locally. Once the connection to the cloud is restored, all buffered data is delivered.

Related topics

• Setting up OEE tracking: Configure downtime detection.

• Defining downtime reasons: Set up the reasons catalogue.

• Downtime contextualisation: Assign reasons.

• Common issues: Further help with connection problems.