SAP Digital Manufacturing

Once mainstream maintenance ends, only customers enrolled in extended support will continue to receive fixes and patches. After 2030, the situation becomes uncertain; while some providers may attempt to offer private support, such service is limited and comes with clear risks since they do not have access to the source code.

When it comes to a system as essential as MES, depending on software that is no longer fully supported poses a major risk. Even small issues like downtime, security holes, or compliance problems can snowball into real financial and operational impact and, in the worst case, impact the customer trust and operational integrity.

SAP Digital Manufacturing: a new generation of MES

SAP Digital Manufacturing is positioned as the successor to ME and MII but calling it an ‘upgrade’ does not do it justice. SAP DM is a fundamentally different solution built as a cloud-native MES rather than an on-premises system.

Over time, many ME/MII landscapes have grown into highly customised, plant-specific environments. SAP DM takes a different approach. By offering a standardised and configurable product that is natively built to scale globally and support continuous improvement.

At a high level, SAP DM is characterised by:

This foundation enables capabilities such as close to real-time production visibility, integrated IoT scenarios, and advanced analytics, areas where traditional ME/MII systems often struggle without significant custom development.

Functional coverage and industry readiness

SAP Digital Manufacturing is already in use across both discrete and process industries, including automotive, consumer goods, chemicals, and pharmaceuticals.

Core capabilities include:

• Close to real-time production execution and monitoring
• Integrated quality management and possibility for electronic batch records
• Native IoT connectivity
• Embedded analytics and near-real-time reporting
• Audit trails and electronic signatures

For regulated industries, SAP DM is GxP-compliant and supported by official documentation and there are already pharmaceutical companies live on the platform. That said, companies used to highly customised MES setups may need to shift their mindset. SAP DM focuses on standardisation rather than custom development, which simplifies upgrades and support but changes how MES solutions are built and managed.

From ME/MII to SAP DM: why this is a transformation

A common misconception is that existing ME/MII solutions can be technically migrated to SAP DM.

In practice, a simple lift-and-shift is not possible. Trying to recreate legacy customisations in a cloud MES often works against the very benefits organisations are aiming for.

A successful move to SAP DM should be seen as a broader manufacturing transformation, not just a system migration. A successful transformation typically involves:

For organisations with many sites, especially where each plant has its own localised solution, this effort should not be underestimated. Even with a common template, rollouts require time for preparation, validation, and adoption. Companies starting late may find themselves dependent on extended support beyond 2027.

Why S/4HANA matters in the SAP DM journey

MES does not operate in isolation, and a successful SAP DM implementation relies on close integration with the ERP landscape like EWM, IBP, and ePPDS. For this reason, many recommend implementing S/4HANA first or at least alongside SAP DM to ensure alignment and maximise benefits.

There are practical reasons for this:

• S/4HANA programmes typically drive process standardisation that benefits MES design
• Simplifying interfaces, master data, and custom logic reduces integration effort
• Coordinating both initiatives helps avoid rework and architectural inconsistencies

While SAP DM and S/4HANA can go live at the same time, organisations that view S/4HANA as the foundation often find it easier to keep SAP DM close to standard and maintainable over the long term.

Standing still is falling behind

For CIOs and manufacturing leaders, the question is not whether the system has the latest features, but whether production keeps moving without disruption. MES systems sit at the core of production and running them without reliable vendor support exposes organisations to unacceptable risk.

The NetWeaver sunset should therefore be seen not just as a technical deadline, but as a trigger to:

• Revisit and clarify IT/OT architecture and MES strategy
• Enable more real-time, data-driven manufacturing operations
• Enable for future use of AI and Industry 4.0 initiatives
• Build the data foundation for enabling AI in production

Organisations that address these challenges proactively can avoid costly disruptions and create a foundation for more resilient, flexible manufacturing operations rather than scrambling at the last minute.

What organisations should start investigating now

Organisations should start their MES journey now by assessing their current MES landscape and defining a structured transformation roadmap. The goal of SAP Digital Manufacturing is not standardisation alone, but enabling real-time visibility, better execution, and continuous improvement. Standardisation supports this by reducing complexity and creating a scalable foundation for operational excellence.

Between now and 2027, manufacturers should focus on:

The NetWeaver sunset is more than a technical deadline; it is a great opportunity to transform manufacturing operations. Organisations that embrace SAP Digital Manufacturing now can reduce risk, streamline processes, and gain real-time visibility, turning an end-of-life challenge into a competitive advantage.