Understanding the differences between MOM and MES
Clearing up the confusion a process of wading through history
By Matthew Littlefield, LNS Research
Terminology can be confusing in the software industry, especially if you’re just starting. Unfortunately, this observation holds true for software in the manufacturing industry as well. For those trying to actively learn more about the industry, this article aims to clear a few things up.
Over the years, there have been many different acronyms and terms used for manufacturing-focused software, but there are two that I want to focus on:
- MES – Manufacturing Execution System
- MOM – Manufacturing Operations Management
MES was first used by AMR in the 1990s and was the heir apparent to the computer integrated manufacturing (CIM) term first coined in the late 1980s at Purdue University. This era was before many of the standards in the industry had been established, like ISA-95, and before ERP had taken root as the main IT backbone for most global manufacturing companies.
The problems with early MES
Because of these market conditions, many early MES systems were purpose-built closed systems that lacked the configurability and flexibility needed to adapt to changing business needs. This caused many early implementations to have a very high service-to-software ratio and often created an implementation process that seemed to have no end. For these reasons, and others, MES earned a reputation early on as an expensive and risky endeavor that often did not deliver on initial ROI goals.
Of course, those vendors that did succeed did not stop innovating and the market at large did not stop maturing. As mentioned above, over the late 1990s and early 2000s, the growth and consolidation in the ERP market was unprecedented. However, this growth often did not include shop floor capabilities, which left a need to be filled in managing manufacturing operations and integrating the shop floor with the top floor.
At the same time, much of the good work done by the automation industry in creating batch level standards, like ISA-88, was being extended to the enterprise with the ISA-95 standard. In this standard, the term “manufacturing operations management” was laid out. Detailed activities and business processes were defined within the MOM space, focusing on the areas of production, quality, maintenance, and inventory.
The rise of MOM
These new market conditions gave rise to a number of vendors wishing to rebrand and differentiate themselves from the products of the past, namely MES. Many of these vendors took up the MOM term and referred to offerings as a MOM solution or a MOM platform. There were many similarities among these new MOM solutions that created the flexibility and scalability needed to become a true enterprise application, including:
- Re-architected system based on a configurable and extendable platform
- Standards-based integration with ERP
- Standards-based integration with industrial automation
- Standardized manufacturing data model
- BPM for manufacturing capabilities – model, visualize, optimize, update, and harmonize manufacturing business processes globally
- Event management – ability to collect, aggregate, analyze, and respond to real-time manufacturing events
Despite this trend, nothing is ever cut and dry. There were more than a few leading MES vendors that decided not to switch from their original MES branding even though they did re-architect their systems and have capabilities that align to the above MOM solution capabilities.
So what is next?
The evolution of MOM and MES goes to show how some industrial technology trends take off while others stay stagnant. To review the above:
- MOM, without any other descriptive words, usually refers to business processes, not software.
- MOM Platform or MOM Solution is usually used to differentiate from older MES solutions and has capabilities in-line with those listed above.
- MES is still used by many vendors. In some cases it can refer to a company that has similar capabilities to those of a MOM vendor, but in other cases it can refer to companies that have not kept pace with technology advancements and still promote legacy systems.
Still confused? I’m not surprised. The system has not necessarily been designed to create clarity. The only other advice that can be lent is not to focus on the acronyms. Instead, focus on becoming an educated buyer. Understand your own business needs and identify vendors you can confidently partner with based on the experiences and case studies they can provide in successfully addressing these issues for other companies in a similar position to you.
Matthew Littlefield is president and principal analyst at LNS Research.
|Search the online Automation Integrator Guide|
Case Study Database
Get more exposure for your case study by uploading it to the Control Engineering case study database, where end-users can identify relevant solutions and explore what the experts are doing to effectively implement a variety of technology and productivity related projects.
These case studies provide examples of how knowledgeable solution providers have used technology, processes and people to create effective and successful implementations in real-world situations. Case studies can be completed by filling out a simple online form where you can outline the project title, abstract, and full story in 1500 words or less; upload photos, videos and a logo.
Click here to visit the Case Study Database and upload your case study.