Middleware

Middleware is software that sits between different applications, services, or devices and manages how they communicate with each other. In industrial and manufacturing environments, it commonly refers to the layer that connects shop-floor systems (such as PLCs, SCADA, and MES) with higher-level IT systems (such as ERP, LIMS, or quality systems).

Core characteristics

Middleware typically:

• Enables data exchange between systems that were not originally designed to work together
• Performs protocol conversion (for example, from fieldbus or OPC UA to HTTP/REST or message queues)
• Transforms and maps data formats and structures between sending and receiving systems
• Provides routing, queuing, and buffering of messages or transactions
• May enforce basic security controls such as authentication, authorization, and encryption for system-to-system traffic

Middleware is not a user-facing application and does not usually provide the primary business logic of production, planning, or quality processes. Instead, it supports those systems by handling integration and communication tasks.

Common types of middleware in manufacturing

• Message-oriented middleware (MOM): Uses queues, topics, or buses to send and receive messages between systems asynchronously. Examples include industrial message brokers that handle telemetry from machines to analytics platforms.
• Integration / enterprise service bus (ESB): Provides a centralized integration layer with routing, orchestration, and transformation capabilities, often used between MES, ERP, WMS, and quality systems.
• Database middleware: Manages access to one or more databases, connection pooling, and sometimes data virtualization, so applications do not connect directly to production databases.
• API gateways and service middleware: Manage access to REST or SOAP APIs, including rate limiting, authentication, and request/response transformation.
• OT/IT gateway middleware: Connects operational technology (for example, PLCs, DCS, historians) with IT applications, often using industrial protocols on one side and standard IT protocols on the other.

Operational role in regulated environments

In regulated manufacturing, middleware often plays a role in:

• Collecting machine or process data for electronic batch records, genealogy, and traceability
• Coordinating workflows between MES, laboratory systems, quality management systems, and ERP
• Enforcing consistent data models and reference data across systems
• Managing audit-relevant event streams, such as status changes, alarms, and electronic signatures, for downstream storage and review

Middleware itself is typically part of the infrastructure layer, but its configuration and operation can affect data integrity, audit trails, and system interoperability.

Common confusion

• Middleware vs. MES/ERP: MES and ERP are end-user applications that implement business and production processes. Middleware connects these systems to each other or to equipment but does not usually define the process logic itself.
• Middleware vs. gateway device: A physical gateway device may include middleware, but the term “middleware” refers to the software function, not the hardware.
• Middleware vs. custom integration scripts: Point-to-point scripts can act like very simple middleware, but the term usually implies a more general, reusable integration or messaging layer.