Data collection from PLCs, machines and industrial devices connects production with MES, ERP, SCADA, databases, BI applications and cloud platforms. We help acquire data from PLCs, robots, CNC machines, sensors and analogue or digital signals, standardise it via OPC UA, MQTT and database interfaces, and securely transfer it to enterprise systems.
Where do you need to obtain the data, and where should it be transferred?
We will discuss the data sources, communication protocols, number of devices and data points, target systems, required availability and future development of the solution.
More about data collection, platform selection and OT/IT integration
From the production device to the enterprise system
Every data collection project starts with the information source. Data can come directly from a PLC, CNC machine, robot, industrial device, sensor or separate analogue or digital signal. The data must then be read, standardised, possibly transformed and securely transferred to the target system.
Siemens, Rockwell, Mitsubishi, Omron, Beckhoff, CNC machines, robots, meters, analogue and digital signals.
Reading, standardising, storing, transforming and routing production data.
OPC UA, MQTT, SQL, REST API, SAP, Power BI and other enterprise applications.
Select a solution according to the application
Kepware OPC Server
A central platform for reading and standardising data from many PLCs, CNC machines, robots and other industrial devices.
- many communication drivers in one platform,
- data standardisation via OPC UA,
- connection to SCADA, MES, ERP and other clients,
- suitable for central plant-wide data collection.
OPC Router
An integration data hub connecting production with MES, ERP, databases, SAP, MQTT, cloud platforms and other IT systems.
- graphical configuration of data flows,
- data transformation and routing,
- bidirectional OT/IT communication,
- SAP, database, MQTT and REST API connectivity.
SIA Connect
A compact hardware or software solution for reading, storing and bidirectionally transferring data between PLCs, devices, databases and IT systems.
- DIN-rail hardware or standalone software,
- OPC UA Client and Server, MQTT and REST API,
- databases and Store & Forward,
- PLC ↔ PLC and PLC ↔ database transfer.
When data cannot be obtained directly from the PLC
For older machines, closed control systems or devices without a suitable communication interface, data can be acquired directly from physical signals, standalone sensors or wireless I/O modules.
Collection and control of digital and analogue signals without changing the PLC program. Also suitable for retrofitting older production equipment.
View I/O modulesDirect measurement of temperature, humidity, pressure or CO₂ concentration and transfer to a higher-level system.
View industrial sensorsTransfer of digital and analogue inputs and outputs where wired connections are not possible or suitable.
View wireless I/OQuick comparison of the main solutions
| Area | Kepware | OPC Router | SIA Connect |
|---|---|---|---|
| Main role | Reading and standardising industrial data | Data integration, transformation and routing | Compact data collection, storage and transfer |
| Large numbers of PLCs and protocols | Very suitable | Complements Kepware | Small and medium-sized projects |
| OPC UA | Yes | Yes | Yes |
| MQTT | Yes | Yes | Yes |
| Database communication | Via additional modules | Yes | Yes |
| SAP, MES and ERP integration | Source of standardised data | Very suitable | Via databases, MQTT, OPC UA or API |
| Store & Forward | Depending on configuration | Yes | Yes |
| Typical use | Central data collection in a plant | Connecting production with enterprise systems | Machines and small to medium-sized projects |
For central collection from many PLCs and industrial devices, Kepware is usually the best choice. For connecting production data with MES, ERP, SAP, databases and cloud platforms, we recommend OPC Router. For individual machines, machine builders and small to medium-sized projects, SIA Connect is often ideal. The products can also be combined in one architecture.
How do we design a data collection solution?
- Identify data sources and communication protocols.
- Determine the number of devices, data points and read rates.
- Review target MES, ERP, SCADA, BI or cloud systems.
- Design the appropriate OT/IT architecture.
- Select the required licences, software and hardware.
- Consider cybersecurity and access management.
- Configure, implement and test the solution.
- Provide training and ongoing technical support.
Jak na sběr dat15

How KASKO connected sensors on 42 machines to its MES system and reduced downtime and scrap rates
As part of its efforts to streamline production, KASKO was looking for a way to expand data collection to include data from sensors retrofitted to dozens of injection molding machines. The goal was to find the simplest possible way to get the data into the MES system. The solution was the OPC Kepware Server, which helps reduce downtime and number of defective parts.

OPC Router vs. Node-RED: Does it make sense to pay for software when an open-source alternative exists?
Sometimes you ask us: “Why should we pay for OPC Router when we can use Node-RED for free?” The answer is not about money, but primarily about operational risk, stability, security, and efficiency in live production. We have prepared a comparison to help you decide which solution is the right fit for your infrastructure.

Kepware Server 7.0: One Platform Instead of Two, Higher Security, and the End of OPC .NET
Kepware Server 7.0.236.0 unifies the former KEPServerEX and ThingWorx Kepware Server into a single product. It introduces security changes, adds support for Windows Server 2025, and removes legacy technologies present in the previous products. Below is an overview of what’s new and what has changed so you can upgrade smoothly.
Question or Inquiry
Highlighted items are mandatory.















