The Industrial IoT Blog

If you’re running SAP MII (Manufacturing Integration & Intelligence) as the backbone for edge connectivity and IIoT use cases, you’ve probably heard by now: the clock is ticking. SAP has officially announced end-of-life for MII, with mainstream support ending in 2027 and extended support available (at a premium) until 2030. There’s no direct “MII 2.0” coming.

For those of us who’ve built, supported, or modernized manufacturing landscapes around MII, this is a big deal, but it’s not the end of the world. In fact, it’s a chance to build something better, more scalable, and more future-proof. Here’s what I’ve learned, what SAP recommends, and how the new puzzle pieces fit together for a “SAP-centric approach”.

Why the Shift? No Direct MII Replacement

Let’s start with this: SAP MII was the Swiss army knife for plant-to-enterprise integration. It handled machine connectivity, data contextualization, real-time dashboards, and even custom MES logic. But MII was built for a different era, on-prem, tightly coupled, and not designed for the scale or flexibility demanded by today’s cloud, edge, and analytics-driven factories.

Now, as SAP pivots to cloud-native solutions, they’re not offering a 1:1 MII replacement. Instead, they’re splitting the old MII roles across a set of specialized, more modern components, such as:

• SAP Production Connector (ProdCon): The new edge connectivity layer, replacing both MII and PCo for machine connectivity.
• SAP Cloud Connector: The secure on-premise component that creates an outbound tunnel from the plant network to SAP BTP.
• SAP BTP (Business Technology Platform): The cloud platform that now hosts all integration, messaging, data, and extension capabilities. Deployed on this platform are:
  • SAP Digital Manufacturing (DM): The MES application layer for production execution, quality, operator guidance, and configuration surface that defines and pushes equipment models, tags, parameters, triggers, and subscriptions to ProdCon.
  • SAP Event Mesh: Real-time event streaming and pub/sub messaging.
  • SAP HANA Cloud & SAP Datasphere: Operational data layer for structured and time-series data, as well as semantic modeling, analytics, and unified OT+IT data.

Let’s break down each piece, how they work together, and what’s different from the old MII-centric world.

SAP ProdCon: The New Edge-Connectivity Layer

Think of ProdCon as the next-generation replacement for SAP PCo and the “machine connectivity” part of MII. It’s an on-premise Windows service, typically installed inside your production network, with direct access to PLCs, SCADA, sensors, and other shop floor systems. ProdCon acts as the bridge between physical equipment and SAP’s cloud solutions.

A few things to know:

• Protocol Support: ProdCon handles OPC UA (the modern gold standard), MQTT, and other industrial protocols. It’s built for flexibility, but you’ll still need to plan for protocol conversion and tag mapping.
• Central Configuration: You set up connections, user authorizations, and monitoring through SAP Digital Manufacturing’s Production Connectivity apps. No more remote configuration hacks via MII.
• Edge-to-Cloud: ProdCon streams machine data securely to the cloud, where it feeds into BTP and other SAP services. Local buffering and failover are built-in, so you don’t lose data during network outages.

In practice, ProdCon is far more “plug and play” than the old PCo/MII combo, but you’ll still need to invest time in standardizing tag naming, contextualization, and security, especially if you have a big, diverse machine park. Also, SAP’s new architecture introduces a very important distinction between “Design Time” and “Runtime“, and ProdCon sits at the center of both, but its relationship to DM is different in each phase.

Design Time – Defining Behavior, Mapping Sources, Deploying to ProdCon

Design Time is where you configure how equipment behaves and how events are understood by the system. All of this configuration happens in SAP Digital Manufacturing, not in ProdCon.

In Design Time, inside DM you must:

• Create the equipment asset
• Map tags and parameters to OPC UA nodes
• Define Automatic Triggers
• Create Subscriptions, which replace the old PCo Notifications
• Deploy everything to ProdCon through BTP and the Cloud Connector

Even though ProdCon has a UI, you do not configure the logic there. DM is the design surface, and ProdCon is the runtime executor. This replaces the old MII model where configuration and runtime logic were intertwined inside the same application.

Runtime – ProdCon Reacts to Real Machine Events

Runtime begins the moment a machine reports a change:

• OPC UA tag changes → ProdCon receives it → Trigger fires → Action is executed.

In Runtime, ProdCon is not tied to DM. After it receives tag updates, ProdCon can:

• Call DM to trigger MES workflows
• Publish events to Event Mesh
• Call custom REST APIs
• Send MQTT messages
• Forward data to Datasphere or HANA Cloud

This leads to a very important insight: DM is required only at Design Time, not at Runtime. ProdCon is free to route events anywhere in Runtime. DM becomes one of many possible consumers.

The Runtime flow becomes:

• OPC UA → ProdCon → Cloud Connector → BTP →
  • → DM (MES workflows)
  • → Event Mesh
  • → Datasphere or HANA Cloud
  • → REST or MQTT targets

This flexibility did not exist in MII and becomes one of the biggest value shifts in the new architecture.

SAP Cloud Connector: The Missing Piece in Most Diagrams

This is one of the most important parts of the architecture and is often overlooked.

ProdCon is located inside a protected production network. DM cannot directly reach ProdCon. To solve this, SAP uses the Cloud Connector, which is installed on-premise near ProdCon.

The Cloud Connector creates a secure outbound tunnel from the on-prem network to SAP BTP. This allows two-way communication without exposing the internal network.

Through this tunnel:

• DM sends design-time configurations to ProdCon
• ProdCon can send data into BTP, and from there it can be routed to DM, Event Mesh, HANA Cloud or Datasphere.

Everything flows through Cloud Connector. There is no direct DM to ProdCon connection. This is essential for security, compliance, and network isolation.

SAP BTP: The Cloud Integration & Data Platform

Once data leaves the plant, it lands in SAP BTP. Here’s where the magic (and sometimes the headaches) of cloud integration happen. BTP is SAP’s all-in-one cloud platform: it handles data ingestion, transformation, storage, analytics, application development, and integration with both SAP and non-SAP systems.

In my experience, the biggest adjustment is cultural: IT and OT teams need to get comfortable with cloud-first thinking, API-driven integration, and new security models. But the upside is huge, finally, you can break the old silos and make plant data available everywhere it’s needed.

SAP Digital Manufacturing (DM): The MES Application Layer

SAP Digital Manufacturing (sometimes called DMC, DM, or DMe) is SAP’s cloud-native MES. It’s focused on what MES does best: production execution, quality management, operator guidance, resource orchestration, and traceability. DM consumes IIoT data delivered through ProdCon, but it is not responsible for raw machine connectivity or generic data streaming.

Here’s how DM uses IIoT data in real life:

• Production Execution: DM uses structured machine data (delivered via ProdCon/BTP/Event Mesh) to trigger workflows, track order progress, and automate production steps.
• Quality Checks: Sensor readings, alarms, and inspection data flow into DM, where they drive in-process quality checks, SPC calculations, and nonconformance workflows.
• Operator Guidance: DM provides electronic work instructions, checklists, and dashboards (PODs) that pull in real-time machine status and context.
• Resource Orchestration: DM can schedule labor and equipment based on real-time shop floor status.

DM is still evolving. If you’re used to the “anything goes” flexibility of MII, you’ll find DM more standardized and sometimes less customizable. But for most MES use cases, especially those that benefit from structured IIoT data, DM is faster to deploy, easier to support, and better integrated with SAP’s future roadmap.

SAP Event Mesh: The Event-Driven Backbone

Here’s where things get interesting. With MII, most integrations were point-to-point or batch-based. Event Mesh flips that: it’s an event-driven messaging layer, built on publish/subscribe principles. When something happens on the shop floor (machine status change, quality alert, production milestone), an event is published to the mesh. Any application that cares can subscribe and react, whether it’s SAP DM, an analytics dashboard, or a custom app.

Why is this a big deal?

• Real-Time, Decoupled Integration: No more polling or batch transfers. Data flows instantly, and systems are loosely coupled, you can add or remove consumers without breaking everything else.
• WAN-Optimized, Lossless Delivery: Events are streamed globally with guaranteed delivery and low latency, even across unreliable networks.
• IT/OT Convergence: Event Mesh can bridge both operational (OT) and enterprise (IT) systems, streaming events securely between factories, data centers, and the cloud.

In practice, setting up Event Mesh takes some upfront design work, defining event types, topics, and security rules. But once it’s running, it’s a game changer for agility and scalability.

SAP HANA Cloud & SAP Datasphere: The New Data Platform

In many MII landscapes, MII served as a quasi-historian or central integration hub for machine data. In the new SAP world, these roles move to HANA Cloud and SAP Datasphere.

They provide:

• Large-scale storage for structured and semi-structured IIoT data
• Time-series analysis capabilities
• Modeling layers that unify OT and IT datasets
• Integration with BI tools, data science platforms, and machine learning workflows

This becomes your enterprise-wide source of truth for IIoT analytics.

How the New Architecture Replaces MII’s Role

So, what does the new SAP-centric architecture look like?

The original MII-centric architecture was:

• OPC UA → PCo/MII → Cloud targets

The SAP-recommended architecture (with Design Time vs Runtime included) is:

• Design Time:
  • DM (BTP) → Cloud Connector → ProdCon (Design Time deployment)
• Runtime:
  • OPC UA → ProdCon → Cloud Connector → BTP →
    • → DM (primary MES consumer)
    • → Event Mesh
    • → Datasphere or HANA Cloud
    • → REST or MQTT applications

This architecture replaces the old “MII does everything” model with a modular, scalable, and future-ready stack.

Lessons and Advice

Here’s my advice, raw and simple:

• Don’t try to replicate MII 1:1. Use this as a chance to rethink your integration, standardize data models, and embrace modern best practices.
• Invest in foundational work. Tag naming, contextualization, security, and event design matter more than ever.
• Expect a learning curve. Your teams will need to learn new tools (ProdCon, Cloud Connector, BTP, Event Mesh, DM) and new ways of working (cloud, APIs, event-driven thinking).
• Start small, scale fast. Pilot the new architecture on a single line or site, iron out the kinks, then roll out globally.
• Keep it human. Technology is just the enabler, the real goal is to make plants smarter, simpler, and more connected for the people who run them.

Not everything needs to be real-time, cloud-based, or AI-driven. Sometimes, simple is better. But if you want to future-proof your SAP-centric manufacturing, this is the path I’d take.