The Manufacturing Execution Systems market has always been fragmented by industry and technology. A Magic Quadrant cannot do justice to the nuanced differences, so in conjunction with the release of the Magic Quadrant for Manufacturing Execution Systems, there will be six industry specific context documents. These documents focus on the unique challenges in the industry, and feature MES vendors not found in the Magic Quadrant document. This blog discusses the Consumer Goods/Food and Beverage Context.
Traditionally, the main differentiators for consumer products manufacturing in the manufacturing execution systems (MES) market are speed and flexibility in support of high-volume manufacturing. MES in consumer packaged goods (CPG) both drive and are driven by highly automated factories, producing tens of thousands of units of product. This is an industry that has thin margins, and has been reluctant to invest in MES unless there’s necessity and clearly defined returns. Flexibility is required to support both the tradition of high-volume manufacturing and the emerging challenge of more variants and personalization — the inflated mix of high mix, high volume. Just take a look at something as simple as Oreo cookies, that now have regional and seasonal offerings, Wikipedia lists nearly 100 varieties.
There are a handful of large vendors in the MQ that are often found in CPG and food & beverage facillities, but do not overlook the unique vendors profiled in this context document. You can find the document and all of the details here.
Comments or opinions expressed on this blog are those of the individual contributors only, and do not necessarily represent the views of Gartner, Inc. or its management. Readers may copy and redistribute blog postings on other blogs, or otherwise for private, non-commercial or journalistic purposes, with attribution to Gartner. This content may not be used for any other purposes in any other formats or media. The content on this blog is provided on an "as-is" basis. Gartner shall not be liable for any damages whatsoever arising out of the content or use of this blog.