SAP DM Integration

Every Machine Into SAP DM. And Back. Any Protocol. Any Site.

The open source industrial data platform for your production data. With plug-and-play SAP DM integration, store-and-forward buffering, and bidirectional data exchange. Your other use cases run on the same foundation.
Talk to our team
Read the HiPP case study
SAP DM asset model mirror for plug-and-play integration
ISA-95 data modeling and Unified Namespace built in
All major industrial protocols: OPC UA, S7, Modbus, EtherNet/IP, MQTT, Beckhoff ADS, and more
Store-and-forward buffering for offline resilience
Bidirectional data exchange with SAP DM via REST API
Open Source (Apache 2.0)

Trusted by global enterprises

The Challenge

SAP DM is your next-generation MES. But it can't reach most of your machines.

SAP DM's native connectivity stops at a handful of protocols
SAP DM's Asset Connectivity App supports OPC UA and a few legacy server types. No S7, no Modbus, no EtherNet/IP, no MQTT. In a brownfield factory with decades of mixed equipment, that leaves most of your machines disconnected. And SAP controls the supported list. You can't add protocols yourself.
Raw machine data doesn't match what SAP DM expects
SAP DM needs structured indicator values mapped to its asset model. Your machines produce raw signals in vendor-specific formats. Someone has to clean, merge, and reshape that data before SAP DM can use it. Without a data modeling layer, every integration becomes a custom project.
SAP DM runs in the cloud. Your production doesn't stop when the internet does.
SAP DM is cloud-based. An internet outage means your data pipeline stops, but your production keeps running. Without local buffering and store-and-forward, you lose data or create gaps your MES can't explain. SAP PCo, the traditional bridge, reaches end-of-life in 2027.
"With UMH, we gained real-time insight into our production for the first time. The platform’s flexibility allowed us to connect all our machines and drastically reduce manual data work. This has been a game-changer for our efficiency."
Head of Manufacturing IT
Read the full story >
Our solution

Every protocol. Modeled for SAP DM. Delivered reliably.

UMH sits between your shop floor and SAP Digital Manufacturing. It connects to every machine regardless of protocol, models the data to match SAP DM's asset structure, and delivers it via REST API with store-and-forward buffering. Because UMH is a full data platform, SAP DM integration is one of many use cases running on the same infrastructure.
UMH supports all major industrial protocols out of the box: OPC UA, S7, Modbus, EtherNet/IP, MQTT, IO-Link, and more. Connect PLCs, sensors, energy meters, scales, and legacy systems through a single platform. No custom adapters, no middleware stack.
Connect any machine, any protocol
Import your SAP DM asset structure into UMH. UMH maps its data models 1:1 to SAP DM's asset types, indicators, and metadata. Data is already cleaned, merged, and structured on the UMH side. On the SAP DM side, it's plug and play.
Mirror SAP DM's asset model
UMH runs on the edge with Kafka-based message streaming. If the connection to SAP DM drops, data is buffered locally and delivered when the link is back. No data loss, no gaps, no manual reconciliation. Production data is always complete.
Reliable delivery with store-and-forward
UMH isn't middleware. It's the same infrastructure that powers OEE dashboards, energy monitoring, batch traceability, and AI applications. SAP DM integration runs on the same data foundation your other use cases already use.
More than a connector: a full data platform

90% less effort
One data platform for SAP DM and all other use cases
1000s of hours saved
Templates, not custom middleware projects
Future-ready
SAP DM today, AI and analytics tomorrow, same foundation

From shop floor to SAP DM in four steps

Step
Connect your machines

Pre-built templates for OPC UA, S7, Modbus, MQTT, and more. Select, configure, connect.

step
•
TEXT
Connect your machines
Who:
Jeremy (CTO)
Format:
Video call with screen sharing

The format:

  • 30 minutes to code.
  • 15 minutes to discuss what you'd change to make it production-ready.

The format:

  • 30 minutes to code.
  • 15 minutes to discuss what you'd change to make it production-ready.

The format:

  • 30 minutes to code.
  • 15 minutes to discuss what you'd change to make it production-ready.

The format:

  • 30 minutes to code.
  • 15 minutes to discuss what you'd change to make it production-ready.
Step
Model the data

Map raw signals to ISA-95 structures. Merge, clean, and contextualize at the edge.

step
•
TEXT
Model the data
Who:
Jeremy (CTO)
Format:
Video call with screen sharing

The format:

  • 30 minutes to code.
  • 15 minutes to discuss what you'd change to make it production-ready.

The format:

  • 30 minutes to code.
  • 15 minutes to discuss what you'd change to make it production-ready.

The format:

  • 30 minutes to code.
  • 15 minutes to discuss what you'd change to make it production-ready.

The format:

  • 30 minutes to code.
  • 15 minutes to discuss what you'd change to make it production-ready.
Step
Mirror SAP DM's asset model

Import your SAP DM asset structure. UMH maps 1:1 to asset types and indicators. New machines under an existing asset ID are added automatically.

step
•
TEXT
Mirror SAP DM's asset model
Who:
Jeremy (CTO)
Format:
Video call with screen sharing

The format:

  • 30 minutes to code.
  • 15 minutes to discuss what you'd change to make it production-ready.

The format:

  • 30 minutes to code.
  • 15 minutes to discuss what you'd change to make it production-ready.

The format:

  • 30 minutes to code.
  • 15 minutes to discuss what you'd change to make it production-ready.

The format:

  • 30 minutes to code.
  • 15 minutes to discuss what you'd change to make it production-ready.
Step
Deliver to SAP DM

Push structured data via REST API. Store-and-forward ensures nothing is lost.

step
•
TEXT
Deliver to SAP DM
Who:
Jeremy (CTO)
Format:
Video call with screen sharing

The format:

  • 30 minutes to code.
  • 15 minutes to discuss what you'd change to make it production-ready.

The format:

  • 30 minutes to code.
  • 15 minutes to discuss what you'd change to make it production-ready.

The format:

  • 30 minutes to code.
  • 15 minutes to discuss what you'd change to make it production-ready.

The format:

  • 30 minutes to code.
  • 15 minutes to discuss what you'd change to make it production-ready.
At scale: Template one integration, replicate across sites. AI agents generate and deploy configurations programmatically.

Frequently asked questions.

What about SAP PCo (Plant Connectivity) end-of-life?

SAP PCo reaches end-of-life in 2027. UMH provides the same shop-floor-to-MES bridge with broader protocol support, built-in data modeling, and store-and-forward that PCo never had.

Does UMH replace SAP Digital Manufacturing?

No. UMH feeds data into SAP DM. It sits below SAP DM in the architecture, connecting and modeling shop floor data so SAP DM can consume it without custom integration work.

Can we use UMH before our SAP DM rollout is complete?

Yes. UMH runs independently as a full data platform. Start with OEE dashboards, energy monitoring, or process analytics today. When SAP DM is ready, add it as another data consumer.

Which protocols does UMH support for SAP DM integration?

All major industrial protocols including OPC UA, S7, Modbus, EtherNet/IP, MQTT, IO-Link, Beckhoff ADS, and more. At HiPP, UMH connected most source types at a single site.

How does pricing work?

Per-site licensing, not per-connector or per-data-point. Typical investment is $25-50K per year per site. No surprise overages as you connect more machines.

START WITH UMH

Connect your shop floor to SAP Digital Manufacturing.

Talk to our experts about your machines, protocols, and SAP DM setup. Or explore the platform yourself, fully open source.
Talk to our team
Explore the platform