Industry 4.0 : ERP and MES in Discrete Manufacturing: Moving to the Cloud

Reluctance toward cloud ERP usually has little to do with a lack of openness to new technologies. It is often a matter of responsibility. Those who need to safeguard stable processes, delivery capabilities, and established system landscapes are right to take a closer look. That is precisely why it is worth taking a sober look at where SaaS can actually deliver benefits.

A key factor is operational overhead. A simple rule applies here: the more complex a system landscape is, the more resources are required for technical support, security requirements, maintenance, and update capabilities. SaaS models can significantly reduce this burden because certain operational tasks can be better consolidated and more easily organized. This applies not only to the technical foundation but also to the question of how consistently systems can be maintained over the long term.

Especially in the ERP environment, the benefits are often greatest where dependencies are manageable. Individual functions or modules can be more easily transitioned to a cloud-based operating model than deeply intertwined, custom-built end-to-end systems. The progress then lies not in a complete switch, but in a clearly defined first step.

A second key consideration is scalability. When companies want to connect new locations, collaborate more closely on an international level, or standardize processes across teams, they need solutions that can be easily deployed and reliably operated. The cloud can help here—not because it is automatically better, but because it often makes it easier to standardize workflows and structures.

However, for this approach to be feasible, a clear procedural and technical foundation is required. Where processes are already largely mapped via existing ERP and MES functions and extensions are implemented through transparent mechanisms, a stable foundation for cloud models is established. Where, on the other hand, custom code, ad-hoc logic, and unclear responsibilities dominate, the real challenge is usually not the operating model itself, but the lack of structural clarity.

With SaaS, it’s not just the location where systems are operated that changes. Responsibilities for day-to-day operations are also redistributed. As a result, some traditional operational tasks now fall more heavily on the provider. This can relieve the burden on internal IT teams and free up resources, but it does not mean that responsibility is eliminated altogether.

Technical operational issues in the narrower sense are often less within one’s own sphere of responsibility. Instead, other topics become more important, such as clearly defined roles, reliable service processes, and a structured approach to changes and releases.

This is a particularly sensitive issue in discrete manufacturing. This is because ERP and MES do not affect isolated administrative processes, but rather deeply impact workflows that are closely linked to availability, on-time delivery, and production reliability. This makes it all the more important to clearly define responsibilities. In the event of a malfunction, it must be clear who the first point of contact is, how escalations are handled, what response times apply, and how changes can be implemented in a way that fits the specific operational reality.

This also brings the interplay between the customer’s operational model and the provider’s service organization more into focus. Whether a SaaS model works in practice depends not only on the technology, but also on how well support, communication, monitoring, and release management are coordinated.

Especially in the ERP environment, it is important not to dismiss interface responsibility as a minor issue. Those moving toward the cloud in a modular fashion must clearly define where responsibilities begin and end at every step. This is the only way to prevent technical relief in one area from creating new coordination problems elsewhere.

In discussions about ERP Cloud, the focus is often initially on the target system. In practice, however, the greater challenge usually lies in the architecture. This is because ERP and MES do not operate in isolation but are connected to planning processes, quality assurance, maintenance, data platforms, shop floor systems, and a wide variety of third-party systems.

The real risk therefore often lies not in whether a system runs in the cloud, but in how robust the interfaces, data flows, and responsibilities are. Especially in mature IT landscapes, this quickly becomes the sticking point.

Anyone planning to migrate should therefore check before each step which connections are particularly critical, which integrations must remain stable even in the face of changes, and which components should deliberately be left untouched for the time being. Not every connection needs to be migrated immediately. It often makes more sense to preserve stable parts of the landscape first and to migrate only those components that can be clearly delineated both functionally and technically.

This architectural perspective applies equally to ERP and MES, albeit to varying degrees. In ERP, module-related dependencies are often the primary focus. In MES, production-related functions place high demands on responsiveness, availability, and process reliability. This is precisely why it falls short to view MES in the cloud merely as a counterpoint to on-premises solutions. What is important is a nuanced view of which functions are best located where. Time-critical functions remain close to production, while other tasks—such as transparency, analysis, or cross-site control—can benefit from a cloud-based deployment.

For companies in the discrete manufacturing sector, the cloud is therefore primarily a matter of architecture and organization. Not every department needs to follow suit immediately. Not every use case is suitable as a first step. And not every hesitation is an obstacle; rather, it is often an expression of essential quality standards for operations and production. That is precisely why a sober assessment is worthwhile. Where standards are in place, responsibilities are clear, and integrations remain manageable, SaaS can provide real relief.