Analytics header

Tuesday, January 11, 2011

Finally a clear explanation of what MES is!

I was browsing the blogshpere and came across this post explaining what MES is in real world terms. Since Gartner has now coined MES as MOM the author of this blog uses an analogy with mom (as in mother) to explain what MES is. I think this is a great way to explain the very complicated domain in simple terms. This is also what I tried to do in the my previous "What is it that I do" post.

Here is an excerpt:
 An MES system is:
Software (mom’s brain)
That connects to multiple plant and business systems (spouse, children, school, work, home)
Collects relevant data (children’s and spouse’s schedules; play dates; doctor’s appointments; clothing and shoe sizes of every family member; contents of pantry and refrigerator; supplies needed for school/daycare; immunizations required; daily intake of children’s fruits and vegetables; recommendations on pediatric dentists; educating oneself about any number of topics, not to exclude best techniques for discipline, potty training and how to get your child to broccoli; birthdays; anniversaries; dates of holiday family gatherings on both sides; … uh, not to mention everything required for any work that’s outside the home)
And presents it as easy-to-understand, real-time intelligence (may exist in rudimentary lists, a calendar, or electronic planner, but probably all three; also, constant verbal communication to tell spouse and children everything that needs to be done)
For productivity analysis, data mining, querying and reporting (to coordinate activities and process information in the most succinct and orderly way possible so mom, spouse and children can make the best decisions and achieve optimum life satisfaction and achievement)
The blog is named "On the Night You were Born" and I could not find the name of the blog's owner, but I have to extend out thanks from the MES/MOM community. All that remains is counter with a DAD system explanation.

Monday, December 20, 2010

Once again ROI from MES - Not Really!

So much has bee written and discussed about ROI for MES. I got involved in the latest discussion on a LinkedIn group. I guess that this question is one of the great phenomena of the MES domain. Unlike other types of systems (ERP, QMS, PLM, etc.) the returns and direct benefits hardly provide enough to justify the investment. To complicate matters even more the actual reasons for employing MES differ not only by industry but also by customer. Para-phrasing Paul Boris from the LinkedIn discussion “it is like explaining to your kids why they should eat their veggies”.

It is no wonder that MES solutions are typically the last ones to be implemented in the typical manufacturing solution landscape. It is simply too hard to provide a clear and concise return or benefit from an MES alone or at least to justify the investment – and MESs do not come cheap. On the other hand it is obviously much easier when there is a specific and typically catastrophic event that needs to be remedied, such as a recall, 483 (FDA warning letter), regulatory compliance, detrimental quality issues, etc.

MES need to be thought of as enablers for operational excellence where the ROI and benefit come from the “Whole” solution and not the system. For example more efficient process, better quality, effective material management, etc. The ROI and/or benefits have to then be attributed to The Whole Solution – focus on the solution rather than the System (i.e. MES).

Tuesday, December 7, 2010

The power of collaboration

Last week I participated in a conceptual design process for a facility and process revamp with one of our customers. This is the first time in quite a few years where I worked in multi-disciplinary team that was tasked with coming up with options and solutions for a new process line. Obviously my responsibilities where around the Manufacturing Systems – nothing new here.

It was one of those experiences where I knew how effective such a collaborative process is, yet a verbal explanation does not do it justice. Kind of like trying to teach somebody how to ride a bicycle by reading a book. Quite simple you would think -just peddle and hold your balance – right?

So I now once again have renewed appreciation not only for the other engineering disciplines and level of competency required but also for the importance of collaboration in engineering projects. It is refreshing to once in a while get back to basics, hopefully I will get a few more chances to do that.

Tuesday, November 23, 2010

The 4 Misunderstanding About Manufacturing Systems Implementations

A few weeks ago I attended the ISPE annual meeting in Orlando. My company was hosting a session about technology and operational excellence that was pretty well attended. I take that as a sign of general interest in the topic. I believe that the interest was on the pure operational excellent side, yet the session tried to highlight the synergies that exist between manufacturing systems and operational excellence.

My colleague Carsten Holm Pedersen held a talk on the synergies between systems and operational excellence. The main theme of his talk was what he called “The 4 Myths” about manufacturing information systems or as I refer to them as “The 4 Misunderstanding” about Manufacturing System implementations. I really liked his message so I wanted to share it here.

Focus ROI
Sole focus on ROI ensures success because it defines qualitative business goals and sets a defined scope. However this also means that focus is diverted to “easy wins” rather than usable solutions and enhancement that have obvious value are ignored or rejected as “scope creep”. Furthermore there is risk that synergies from process improvement and other OpEx initiatives are not incorporated or supported by the system.


Use of Standard Systems
Application of standard systems is more effective and guarantees use of “Best Practices”. They reduce risk and provide superior maintainability. The reality is that these so-called “Best Practices” are not necessarily a good fit to your process and sometimes they are not “best” at all, but simply a result of “that is the way we have always done it” thinking. As such they sometimes do not provide the flexibility or adaptability to specific processes and force unnecessary constraints. Focus is diverted to “What we can buy” rather than “What we need”.


Competitive approaches increase productivity
Employing a competitive approach where different projects are competing for the same funds motivates and steers project teams to achieve better results. In fact just the contrary is true, this approach only ensures sub-optimization. It inhibits collaboration and does not leverage the inherent need for systems to be built to support the process. Systems are built to provide specific point solutions and not enable a streamlined lean manufacturing process or superior process understanding.


Integration should be avoided.
Interoperability between systems is not that important and if it is implemented has to be in real time. On the contrary one of the inherent attributes of Manufacturing Systems is interoperability with all levels in the manufacturing process. Not including interoperability with other system may seriously inhibit the usability of a solution and some obvious benefits to process visibility may be ignored. Also each interface may have different “real-time” requirements that have to be evaluated by needs and value.

There is obviously much more to these than what I can put in this post so let me know what you think and make sure to follow Carsten for more discussion on these topics.