Analytics header

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.

Tuesday, November 2, 2010

What is a Manufacturing System - Part I

This is a post that is long overdue. A central discussion topic on this blog is Manufacturing Systems and I have not yet really explained what I mean by a Manufacturing System. I have talked about manufacturing system that are agile and Holonic, so it is about time that I posted a more practical or at least clear description of what I mean.

Most definitions of Manufacturing System are focused on describing a solution, or more precisely the functionality and architecture of a Manufacturing System solution. For example the MESA model presents number of functional categories from a business perspective, where as the ISA-95 (S-95) model provides a solution architecture based on functional decomposition. All these are of course relevant and useful yet it seems that the problem only interesting to academia – try to Google it. It is assumed that we in industry all know what it is – a dangerous proposition to have.

We all agree that the key to a successful deployment of a Manufacturing System is the understanding of the problem that it is designed to solve. This obviously not a novel approach – it is what everybody attempts to do with the system’s requirement or URS. Yet my experience shows that even in the requirement phase many resort to using the existing models, thus reverting to describe the problem with the solution itself. Quite confusing isn’t it?

So here is my take on what a Manufacturing System is, or in other words the Shop Floor Management Problem. I like to describe it as the problem of integrating 3 important flows in a manufacturing organization. The 2 vertical flows provide Product and Logistical information while the horizontal flow is the physical flow of material, equipment and people.


The Shop Floor Management problem is therefore: How to make use of the information provided by the Product and Logistical flow to efficiently and effectively manage the physical flow of Resources and Materials (also known as the production process). Simple isn’t it - that is what a Manufacturing System is designed to do. Try to imagine a seasoned and effective production supervisor or plant manager – the Shop Floor Management problem is very close to his real life job duties.

It is obviously not that simple and there is of course much more detail that is yet to be discussed. I plan to provide some of this in upcoming posts (hence this post is named Part I). Also this is not meant to take away from the importance and complexity of product development, process engineering, operations, and planning. It is a model that is focused on explaining the particulars of managing a shop floor (yes this is my disclaimer).

More detail to come in future posts…

Friday, October 15, 2010

Next week at AdvaMed2010 in DC

Next week I will be attending AdvaMed2010 in Washington DC in an attempt to mingle with the top of the food chain of the Medical Device industry. If you didn’t know AdvaMed is the premier industry organization for the Medical Device industry and the AdvaMed2010 conference is its annual meeting. Essentially it is a place for smaller Med Device companies to market themselves to venture capitalist and larger companies.

Medical Devices is one of our core markets at NNE Pharmaplan and hence we are hoping to leverage this event to make ourselves better known in the industry. Kind of old school marketing but I am hoping that there is value there? I look forward to an interesting week and getting to meet some interesting companies and people. Also last time I have been to DC is in 1995 so I am long due. If you are around give me a shout.

Monday, September 27, 2010

Common question - What MES should I use?

I just returned from the CBI MES conference and found that the main theme or at least that many the attendees were interested in finding the right MES. Yes I know - “it is maybe easier to achieve world peace”. It seems there is no clear answer – no surprise! “It depends”, was a common answer, some said “it is what you make of it”, and I completely agree.


In my many years of studying the “Shop Floor Management” (aka Manufacturing Systems) problem I found that apart from all the technical and functional aspects, the common element that makes an MES implementation and operation successful is user involvement. The users (across all functions) really have to want it! MESs are complex and sometimes cumbersome. They touch many different functions in a manufacturing business, most critically they manage the value stream – or where value is being made. That makes their adoption and acceptance brittle.

In most cases MES products are aligned with specific industries and hence it is pretty straightforward to make an initial short list. But this is not always true, a vendor may be trying to penetrate your specific vertical opening up potential to influence them – and possibly also get a good deal. There are obviously many other factors that can and do play in. “It depends” is always a true statement when talking about fit of a specific MES product to your environment, and therefore it is always important to know what you need.

So how do you determine what you need? Most people will tell you, and correctly so, that you have to use formal (true and tested) models such as the MESA model or the ISA 95 standard. This is the boring but necessary part of the preparatory and selection phases for the MES. I am not saying you should skip the detail; it is by all means necessary. We all know that the devil is in the details, but using these models with no clear focus will not help either. You should use these models to make sure that you have not forgotten or omitted something not to define your problem. That is something only you and your company know, and in most cases it is very specific to your company or business. I prefer to use the 5 whys method to get to the root-cause and then write up as a series of problems – in simple language.

Another important thing to remember is to build on success as Lean practitioners advocate. It works best with a focused Kaizen-like event where a specific need is addressed. When people in the company observe or have taken part in a successful change the value seems transparent and obvious - and you don’t have to even explain or sell it. It is infinitely easier to convince people this way. In fact the only really successful MES projects, at least in my experience, have been when the operators and engineers embraced the system because it addressed a specific problem they had. Yes I know this seems trivial and is also the basis of modern product management, but it is really much more challenging than it seems.

So what have we learned from all of this? As many of the speakers at the conference re-iterated; you need to have a clear focus of the problem. It makes it is easier to build a business case to justify the investment – trivial really. But at the end of the day you have to want it, otherwise it will never happen.