Home
/
Case studies
/
From hardcoded MES to a data-driven engine covering 14 machine types
MES and traceability

From hardcoded MES to a data-driven engine covering 14 machine types

Client
An abrasives manufacturer
Industry
Abrasives
96%

test scenarios resolved (320 of 333) in the first month

An abrasives manufacturer replaced a hardcoded, per-station MES with one data-driven engine Plantformance built for 14 machine types. Rollouts need no custom code, so adding a machine or site is a configuration task. At the first site, test validation reached 96%, with 320 of 333 scenarios resolved, and rollout-ready machines rose from 8 to 40 of 75.

Key results

  • 96% test scenarios resolved (320 of 333) in the first month
  • 8 to 40 rollout-ready machines (of 75) in two weeks
  • 14 machine types on one engine

The problem

The first-generation MES was launched without formal technical specifications. Two years of reactive development followed, built by trial and error with machine operators. The code was hardcoded per station, for example 14 separate identical machine windows, so maintenance got harder and more expensive with every machine added. Duplicated code meant customers had to re-test every machine and function on each update. ERP data was also inconsistent across plants and countries, with missing Bills of Materials and non-standard units that blocked basic square-meter scrap and cost calculations.

What it looked like before

The legacy framework ran on 100+ machines across multiple countries and seven to eight machine types, needed constant re-engineering for unstandardized parameters, and could not take on new functions the business needed.

How Plantformance solved it

The rebuild followed a structured multi-phase plan. Phase A set clear technical specifications, validated with stakeholders across multiple factories. Phases B and C built and validated a standardized backbone covering 14 machine types. The core became a single, extendable engine driven purely by configuration data, so rollouts need no custom code. Every station follows the same workflow: order check, setup, production, verification and completion. Unified material balance rules, standard data dictionaries and centralized ERP, configurator and Ignition interfaces sit underneath. A single business owner vets every new feature request, and each one is validated on a test bench before worldwide deployment.

What changed

A plug-and-play framework now manages 14 machine types without per-factory code forks, upgrades ship in one release cycle, and adding machines or sites is a data-entry exercise.

Results

  • Test validation at the first site rose from 78.4% in early January 2022 to 96% by the end of that month, with 320 of 333 test scenarios resolved
  • Rollout-ready machines at that site jumped from 8 to 40 of 75 in two weeks
  • Redundant per-machine development costs eliminated, with much lower testing effort and downtime
  • Later rolled out to several more factories and handed over to the client's own development team

Plantformance products and services used

Professional Services

Frequently asked questions

Why does a hardcoded MES get expensive to maintain?

In this abrasives manufacturer's first-generation MES, code was hardcoded per station, for example 14 separate identical machine windows. Every added machine raised maintenance cost, and duplicated code meant customers re-tested every machine and function on each update. Plantformance replaced it with one engine driven by configuration data.

How do you roll out an MES to new machines without custom code?

Plantformance built a single, extendable engine driven purely by configuration data, with one workflow per station: order check, setup, production, verification and completion. Adding machines or sites became a data-entry exercise, and the framework now manages 14 machine types without per-factory code forks.

How fast did the new MES pass validation?

At the first site, test validation rose from 78.4% to 96% in the first month, with 320 of 333 test scenarios resolved. Rollout-ready machines at that site went from 8 to 40 of 75 in two weeks. Plantformance later rolled the engine out to several more factories.

Related Ignition case studies

Planning a similar project? Talk to a Plantformance Ignition engineer or browse all 37 Ignition case studies.

Planning a similar Ignition project?

Tell us about your plants and your Ignition setup. A Plantformance engineer will show you how a project like this would work for you.