Clarity in MES selection #3

How to Arrive at a Clear MES Selection

After clarifying the framework conditions for your project, we started the last post with the requirements.

As promised, here is the rest of the topic on requirements, in concrete terms:

• The requirements regarding integration into your production and IT landscape

• Clarity about your expectations of the MES vendor

Let’s get started!

Integration into Your Production and IT Landscape

In addition to the functional, technical, and non-technical framework conditions, there are other points you should consider and communicate clearly from the start: the requirements arising from the necessary integration into your production and IT landscape.

Again, you can distinguish between functional and IT-technical questions:

Functional:

• Is data migration necessary? Does the vendor/integrator have tools for this? Can they support us with their experience?

• Another important question: do we need to adjust, convert, or update data to get the MES up and running successfully? Might this require a separate initiative?

• Do we want to integrate our production machines (i.e., connect them to the MES)? If so, to what extent and on what timeline? What is the vendor’s concept for this, and what training is available?

• Do we need an ERP interface? If yes, how extensive does it need to be?

• Do we need integration into our existing reporting? How should reporting work in the future? Should MES metrics be evaluated within the MES or integrated into our reporting?

• Are we using any special internal software—e.g., specialized testing and measurement programs, inventory management, quality control, etc.—that requires an MES interface?

Tips for Machine Integration

Use the preparation time wisely!
Simplify discussions by doing your “homework” in advance. Create a table of all machines you plan to integrate.

Key details to define scope and costs include:

• Number of machines

• Which and how many different tool types

• How many tools per tool type

• What interface does the machine have? (OPC UA, REST, MQTT, S7, etc.)

• Check the software revision (version), if possible! V1 and V2 can differ significantly in commands or parameters.

• Make sure you have the documentation for the machine interface—especially for the version currently in use.

A word on interfaces: even a text file generated by the machine can be considered a machine interface. This is not a standard and requires individual integration.

Scope considerations:

• Do you want to integrate all machines or only some?

• Do you want a phased approach or start with certain tool types (e.g., only measuring machines at first)?

Remember: different interfaces mean different data volumes and quality. If you want an overarching evaluation of your production machines, such as OEE (Overall Equipment Effectiveness), make sure your machines actually provide the necessary data—otherwise, you’ll be comparing apples and oranges.

Also consider: do you want to integrate new machines yourself later? If so, the solution should offer both a software integration platform and a corresponding “enablement” concept.

ERP Tips

Most companies already use an ERP system. Then the question arises: which system plays what role? Who creates production orders? Who controls them? When are orders updated or transferred?

Defining the roles of each system is crucial. This also determines who is the “master” for certain master data (e.g., products, materials, batches), which directly affects data quality and the success of your MES project.

Also, clarify your use cases: what exact data exchanges with the ERP are necessary? Who provides what? When is data transferred? How much actually needs to be transferred? How are inconsistencies handled, and what should happen in case of errors?

IT-Technical Considerations

Framework conditions also include your IT resources and possibilities:

• How is security managed? (Who handles access control, permissions, remote access, etc.)

• VPN: what are your requirements? Is remote server access possible? This matters for SLAs, software maintenance, and new releases.

• Database: which databases do you already use? Do you have licenses and know-how to operate and scale them? Are there any exclusion criteria for certain databases?

• Same applies to the underlying operating system of the MES. Are there any restrictions on your side? Keep in mind that you’ll ultimately maintain the IT environment, so it must fit your setup.

• Scalability: what is the vendor’s concept for scaling? Can the MES run on a virtual machine (VM)? This matters if your IT landscape is VM-based.

• Software maintenance: not only for the MES itself! For example, Windows patches may require balancing between Microsoft’s recommendations and the vendor’s approval for the MES to run on a specific patch level.

Clarity About Your Expectations for the MES Vendor

As a buyer, you associate purchasing an MES with a set of expectations—both for the product and for the vendor/integrator.

It’s crucial to bring these expectations to the table! Like technical requirements, think in advance about what exactly you expect as a customer or project partner. Only if you are clear can you integrate this into the project.

Of course, MES vendors/integrators bring a lot of experience, but your knowledge of your company, framework conditions, and internal bottlenecks is essential. Experience only comes into play if issues are explicitly mentioned. Arguing “But you are the experts—you should know” is usually not helpful.

Key questions to clarify your expectations:

• What is the vendor’s footprint? Company size, partners, integrators, market presence, financial stability, location. Do you need a local presence or support in your language? Global presence may be important for time-zone-specific support.

• What references does the vendor have in your industry? If none, how well does the technical solution meet your key requirements?

• How do projects typically proceed with this vendor/integrator? How much “project work” will you need to provide externally? Who else is involved?

• What is the vendor’s product roadmap? What trends and concepts are being addressed? Can customers influence the roadmap?

• What impression does the vendor convey? Competence, experience, and partnership in delivering the project?

• What training does the vendor offer, and does it fit your needs?

• Does the vendor work with an integrator? If so, who will be involved in your project, and how is communication structured?

• Finally: how is pricing and the commercial structure handled?

Be aware of the different roles both you and the vendor/integrator play. While you aim to have everything fulfilled, the vendor aims to complete the project efficiently and accountably.

Ultimately, both parties share the goal of successfully implementing the MES! Achieving this allows the vendor to move on to the next project while you take a big step toward digitalizing and automating production.

Keep this in mind during your preparation phase. Clarity, open communication, and focus on shared project goals are half the battle for a successful MES implementation—for both sides.

Clarity for You!

Clarity is essential throughout all phases of MES selection. It should guide the entire selection process. More on this in the next blog post, which will cover the selection phase.

Feeling overwhelmed by all the questions? Wondering how to manage all these aspects?

In that case, a free strategy session is exactly the right solution for you!

Simply click the blue button below this blog post. I look forward to speaking with you!