Analytics header

Tuesday, May 11, 2010

My Presentation at the MESA 2010 Annual Conference

In June I will be presenting at the MESA 2010 North American conference. The conference is going to be held in Dearborn, MI (near Detriot) hosted by Ford at their conference facility. I wanted to share the abstract here on my blog. I will be co-presenting with Kasper Larsen from Novo Nordisk and my colleague from NNE Pharmaplan, Asger Sharp-Johansen

The presentation shares our experiences from the current global MES rollout project at Novo Nordisk. This is an ongoing long term multi faceted project that involves a staggered deployment of a commercial MES software package to all of Novo Nordisk’s manufacturing sites.

Deploying a new manufacturing system is a complex and risky proposition for any company, rolling out such a system to multiple sites on a global scale may be even considered scary. In order to mitigate the risks and manage the complexity of this immense undertaking Novo Nordisk makes the best use of people and technology to evolve a best practice approach that is continually improved upon. This approach includes technical and organizational aspects that cover the complete life cycle of the manufacturing system’s deployment. In addition the “out-of-the-box” feature set of the software obviously did not suffice and navigating this predicament, coined as "Customize or Compromise", is another interesting topic.

Novo Nordisk is a global healthcare company with 87 years of innovation and leadership in diabetes care, haemophilia care, growth hormone therapy, and hormone replacement therapy. It has international production facilities and employs more than 29,300 employees in 76 countries.

Thursday, March 25, 2010

Word Cloud of this Blog

Just for fun I thought it was interesting to visualize what this blog is about. I found this tool called Wordle via the Duct Tape Marketing blog that I read. I think it is an amazing way to visualize out what a blog is about, in my case not surprisingly mine is about... well metrics, intelligence, and manufacturing. It is nice to get this verified.


Customize or Compromise

I am currently involved in a global project to rollout a specific MES (Manufacutirng Execution System) to a host of sites. This is an immense undertaking and therefore we are spending some time pondering some of the things that we can do to ease the pain and more importantly learn as we go along. I think that I will have quite a few more posts on this topic as we progress; initially I wanted to share some thoughts about using a commercially available MES software product, sometimes also called COTS (Commercial Off The Shelf) and the customizations that are always required.

The first topic is revolves around the question whether a COTS MES product can be productively used in a real world scenario only using the features that are available OOTB (Out-of-the-box). I believe that the answer is a resounding NO, but I may be wrong. It is obviously something that many practitioners are challenged with and therefore I think it makes a good discussion topic.

A COTS system will always be a compromise. The end customer wants his requirements satisfied based on his priorities. The vendor’s priorities, on the other hand, are driven by the need to pick the customer’s requirements that he knows the product can solve best – and then sometimes even persuade the customer that its best for him.

Such COTS MESs have a specific set of features that can be applied to a given scenario sometimes represented by a functional requirement. I like to call these "solution scenario" or "solution approaches" since sometimes a requirements is satisfied by a specific way to use a number of available features. This may be somewhat comparable to a software Design Pattern. Unlike a system that is a custom (or tailored) solution this presents some challenges.
  1. For specific scenarios there may exists one or more solution approaches using available OOTB features. This is the postive scenario - in such cases we are good to go.
  2. For specific scenarios the OOTB feature set may not provide a solution approach. In other words an OOB solution does not exist and hence a customization may be required. the question here becomes: "Can we live with out this?"
  3. For specific scenarios the OOTB feature set may be able to provide a solution approach but it is constrained or lacking. In such cases a decision has to be made to compromise or customize.
If you only encounter scenario #1 then there is no problem, however I have never seen this happen. Dealing with scenarios #2 and #3 can be summed up as "compromise or customize". What do you want to do?

Tuesday, February 23, 2010

What is Intelligence, and why do we need it?

I believe that it is time to get back on topic in this blog, which is Intelligence in manufacturing and manufacturing systems in general. With that in mind I was looking thru my archives and came across something I once wrote as a positioning statement for an intelligence product – I guess it is not hard to figure out what company that was for? So here goes…

In one of my previous posts I tried to bring up the point that we need to consider metrics in the context of what they are needed for and how they are going to be used. I believe that is the best way to understand how to provide the right intelligence in a given scenario. But what is Intelligence? Well that is a very serious subject, but let’s take in the context of manufacturing and process improvement.

Intelligence implies the ability to comprehend; to understand and profit from experience. As such Intelligence is information valued for its timeliness and relevance rather than its detail or accuracy in contrast with "data" which typically refers to precise or particular information, or "fact".

In the context of manufacturing, Intelligence is a fundamental ingredient influencing the system’s level of performance in reaching its objectives. A manufacturing business system (humans included) is a system that learns during its existence. In other words, it learns, for each situation, which response permits it to reach its objectives. It continually acts and by acting reaches its objectives more often than pure chance would indicate. We can observe the following about Intelligence in manufacturing:
Intelligent manufacturing is not a smarter way of producing things; it is a human centric approach where humans interact with the process be it automatic or manual, gathering the right information to take intelligence decisions based on actionable information. It is much more than visibility. Just having the information is of course helpful, but it needs to be taken one step farther. It needs to be provided in a way that people can intuitively capitalize on it using their knowledge and understanding to make effective decisions.
Henri Poincare once noted in a related topic that “Science is facts; just as houses are made of stones, so is science made of facts; but a pile of stones is not a house and a collection of facts is not necessarily science.”
What is an effective decision then? It is a decision that has an outcome that drives increased performance and continuous improvement. Intelligence is therefore not solely about metrics, KPIs or the ability to drill down into the data. In order to increase performance we need to quantify what is important. Hence intelligence is about quantifying what is important, or quantifying the unquantifiable.