Häufig gestellte Fragen
What is IoT ERP — and is it a standalone software product?
IoT ERP refers to the integration of networked sensor and machine data from the Internet of Things into the business processes of an ERP system, so that physical events — such as a fill level dropping below a threshold or an operating-hours threshold being reached — automatically trigger or enrich business transactions. It is not a standalone software type but an integration pattern between existing devices, an upstream IoT platform and the ERP. The commercial value is created not by the sensor alone but by linking the measured values with orders, inventory, maintenance and invoicing in the ERP. IoT ERP is thus a building block of Industry 4.0 and of connecting the shop floor with the top floor.
Do I need a dedicated IoT platform, or is the ERP alone sufficient?
With many connected devices and high-frequency time-series data, an upstream IoT or edge platform is advisable in practice: it collects, filters and normalises the data and forwards only the relevant business events to the ERP. The ERP is meant to process documents, master data and workflows, not to archive large volumes of raw measurement data — fully mirroring all sensor data into the ERP is rarely sensible. Widely used platforms include Microsoft Azure IoT, AWS IoT Core, Siemens Insights Hub (formerly MindSphere), the SAP Business Technology Platform and PTC ThingWorx, while former providers such as the Bosch IoT Suite have since exited the market. For smaller setups with only a few machines, direct integration via REST APIs, OPC UA or an iPaaS layer may also suffice.
Which interfaces and protocols are used to connect IoT to the ERP?
The dominant standard for machine data in Industry 4.0 is OPC UA (standardised as IEC 62541), which enables vendor-independent, semantically described connectivity from the field level up to the ERP. For lightweight, scalable sensor data streams, the publish-subscribe protocol MQTT is frequently used, and it can also be combined with OPC UA via the OPC UA PubSub specification (Part 14). For the direct ERP connection, REST APIs or an iPaaS integration layer are typically used, while field-level bus and industrial Ethernet systems such as Profinet, EtherCAT or Modbus are often connected via an OPC UA bridge. Mobile or distributed devices additionally use wireless standards such as LoRaWAN, NB-IoT or 5G.
Which security and compliance requirements apply to connected equipment?
Networked devices enlarge the attack surface, which is why device identity with certificate management, encrypted communication via TLS, network segmentation and an end-to-end firmware update process are considered mandatory. The IEC 62443 series has established itself as the central standard for industrial cybersecurity; with its zone-and-conduit model and security levels SL 1–4 it prescribes a segmented, multi-layered architecture and, in its current editions, explicitly also covers IIoT and cloud-based analytics. Added to this are regulatory requirements such as NIS-2 and the GDPR as soon as personal data is processed. The EU Cyber Resilience Act (CRA) entered into force on 10 December 2024; its reporting obligations for actively exploited vulnerabilities apply from 11 September 2026, and the main manufacturer obligations from 11 December 2027.
How does IoT ERP differ from MES, SCADA and a pure IoT platform?
IoT ERP replaces neither a Manufacturing Execution System (MES) nor SCADA; rather, it makes their data usable in the commercial ERP world. SCADA controls and visualises machines in real time and sits at the very bottom of the OT stack, an MES translates ERP orders into shop-floor control and collects feedback, while an IoT platform is device-based and event-driven, collecting and analysing large time series. The ERP, by contrast, works transactionally and process-centrically, posting the business consequences of physical events. The digital twin is also a related but distinct concept that maintains a virtual replica of an object and is not necessarily coupled to the ERP.
What ROI is realistic with IoT ERP, and what does a pilot cost?
Studies and practical reports from mechanical engineering show effects above all in condition-based maintenance: various analyses, including evaluations by McKinsey, cite a reduction in unplanned downtime of up to around 50 percent and lower maintenance costs in the range of roughly 10 to 40 percent compared with purely interval-based maintenance. Further levers are shorter service response times for connected products, additional service revenue in equipment-as-a-service models, and more accurate materials planning based on actual consumption; the specific figures depend heavily on industry, machine fleet and data quality. As a rough guide, investment sums in the low six-figure to lower seven-figure range are quoted for a first pilot project with around 10 to 30 machines, with correspondingly more for company-wide rollouts. Well-founded, vendor-neutral selection support helps scope the pilot sensibly instead of prematurely mirroring all raw data into the ERP.