Options for integrating our software

aiomatic processes structured machine data such as numerical sensor values, binary signals, and categorical variables. This includes, for example, temperature, pressure, rotational speed, vibration, on/off states, operating modes, or product variants. In addition, event data such as malfunctions, maintenance records, or alarms can help classify a machine's status even more reliably.

Free text, images, videos, or audio data are not the typical core input for the software. While they may provide supplementary information in individual cases, they are not the focus of automated machine data analysis. The most important factor is that the data is available regularly, can be clearly assigned, and maintains a consistent meaning.

To get started, you either need the ability to send data directly to a broker via MQTT or, if our aioConnect solution is used, a permanently available Linux environment, usually in the form of a virtual machine.
This environment must be connected to a data interface on the network side, such as OPC UA. Once aioConnect is installed, the data is automatically processed and transmitted.
Alternatively, additional hardware can be installed that automatically transmits the data via LTE after installation.
All variants use certificate-based encryption methods to enable secure transmission.

To run our data connection client, a Linux VM is required that is permanently available and has internet access.Internally, the VM needs access to the data source, such as an OPC UA server, and then transmits the data to aiomatic via an encrypted outbound connection. The corresponding network and firewall approvals must be set up for this.

For aioConnect, data is provided via OPC UA by default. For direct MQTT data connections, structured JSON messages are used. It is important that the data is transmitted with both a timestamp and the measured values. Only current and valid readings should be transmitted to ensure reliable analysis.

The most important factor is how sensor data is made available in your environment. It matters whether the data is provided via a gateway, a box, a PLC, a SCADA system, a historian, or an IoT platform. Our standard approach is to read data at the source where it is already collected or offered, typically via an OPC UA server. Alternatively, depending on your specific setup, interfaces such as MQTT, REST, or Modbus TCP can also be used. It is essential that the relevant data points are structured, up-to-date, and clearly interpretable.