Bridging the Gap: How ERP and MES Systems Adapt to the Industrial IoT Revolution

Modern IoT platforms sift through vast data streams to deliver actionable insights that feed into ERP and MES workflows.

However, integrating that raw IoT data into ERP and MES remains a persistent challenge.

ERP and MES were originally built as self‑contained, monolithic solutions, each with its own data store. They were never intended to ingest continuous streams from sensors, cameras, or other IoT devices.

In March 2020, SolutionsX—a manufacturing consultancy focused on digital system upgrades—reported that multiple studies reveal a clear gap between IoT and ERP integration. Only 16 % of companies leverage IoT data within their ERP platforms, and many are finding legacy systems inadequate as they move toward smarter, data‑centric solutions.

The core issue lies in integration. Many IIoT devices ship with proprietary operating systems and lack a common API, making it difficult to plug them into ERP or MES. Conversely, legacy ERP/MES were built for discrete barcode readers, RFID scanners, tablets, and smartphones, not for continuous sensor feeds.

With IIoT networks proliferating on factory floors—enabling real‑time reporting and automation—manufacturing leaders ask whether real‑time IIoT could replace ERP and MES.

ERP and MES providers have answered by building middleware that bridges the gap. By adding edge‑computing capabilities, these platforms can ingest device streams in real time and translate them for the central ERP or MES system.

For example, SAP uses its cloud‑based Leonardo IoT foundation platform to interface with, network, and securely manage IIoT devices that follow standard industry protocols. Companies can also tap into the SAP IoT Application Enablement Toolkit to build custom IoT applications.

On the MES side, Sensrtrx has partnered with Siemens, Allen Bradley, and others to create interfaces with IoT in manufacturing. Its IoT Edge platform connects to hundreds of PLCs, controllers, and databases.

These stories illustrate a broader trend: middleware developed by ERP and MES vendors is enabling a wide range of IoT devices—via standard interfaces—to become part of a company’s resource‑planning and execution strategy. Legacy systems are evolving, and their core value remains.

When dealing with non‑standard IoT, many ERP and MES vendors now offer cloud‑based versions that act as an integration platform. Cloud middleware incorporates comprehensive, industry‑standard APIs and webhooks, allowing organizations to translate proprietary protocols into the language of ERP or MES in real time.

Cloud services cannot solve every integration scenario. For truly unique IoT solutions—especially those with non‑standard operating systems or communication protocols—custom code or a specialized consultancy may be required.

ERP systems continue to drive enterprise operations by linking every department and fostering collaboration. MES systems add value by synchronizing shop‑floor activity with corporate objectives. Together, they provide robust reporting and analytics, earning them the “legacy” label for good reason.

What has changed in the last five years is IIoT’s real‑time communication, status alerts, and automation capabilities on production and warehouse floors. These benefits accelerate time‑to‑market and reduce operational costs.

Recognizing this, most ERP and MES vendors have spent the past five years enhancing their platforms with IIoT middleware, creating a reliable “connection” between the two. While some integration challenges remain with niche device subtypes, vendors that embrace industry‑standard solutions will thrive.

To navigate this evolving landscape, companies with legacy ERP/MES systems should:

• Engage with vendors to understand current and future IIoT integration plans.
• When evaluating an IIoT solution, scrutinize its operating system and communication protocol. If they are not industry‑standard, consider alternative options.
• Prioritize security. ERP and MES systems are typically secure, but IIoT often isn’t. Define an end‑to‑end security strategy that starts at the IoT edge and extends through the existing ERP/MES safeguards.