Apr
9th

MES Requirements, MES Selection


Posted by Scott Whitlock In Basics, Best, MES, Standards
At 9:22 pm. 2 comments

There is no substitute for good requirements, good specifications, and a good selection process in any IT project.  Especially those projects that are complex and touch so many people and disciplines, like MES projects.

I often liken MES projects to building a house.  It isn’t enough to go to a custom builder and give them requirements like this:

  • 5 bedrooms
  • 4 full baths
  • 3 car garage
  • 5,500 square feet
  • Oh, and we want this to be our dream home.

NO, NO, NO!  We all know that a builder would laugh you out of his office and say, “Come back with some architectural blueprints, some specifications, and a budget.”  Even if the builder was a Design Build firm, you would expect the clock to start then, and to pay for the design of your new home!

However, so many times I see companies trying to do the same thing with MES projects.  Requirements go something like this:

  • OEE
  • Tracking and Genealogy
  • Reporting (including drill-down and ad-hoc reports)
  • Schedule dispatch
  • Label printing
  • NO, NO, NO!  There is no way the customer is going to get what they want.  There is no way they are going to get an apples-to-apples comparison from different vendors.

In coming posts, I will explore how manufacturing companies can do a better job of laying out requirements.  Who knows, maybe we will even post some templates!


Mar
7th

Justifying MES


Posted by Scott Whitlock In ERP, Friday Funnies, MES, People
At 11:22 am. Be the first to comment!

We once had a MES project with a large medical devices company.  This was a great project, that started well, and then the project sponsor went on vacation.  After a week he did not return, then two weeks, then three….

Then, not at all.

We all (Flexware and the customer) found out the way he had justified the MES project was by using some budget left over from another project.  They certainly needed the MES, and we all knew this was going to be a great solution.  These games get played with capital money sometimes, but this one got some real scrutiny when this guy left the company.  The project manager we were working for (she worked for the sponsor that left) called us and asked us to stop our work immediately.

The big meeting….

So here we are, a small company with this large project, stalled.  The Plant Manager called a meeting and asked us (now this was our problem) how we were going to justify this project.  He said “If you can’t tell me right now how much this project is going save me, we are not going to do it.”  Of course, he meant finish it.  I replied by saying “Justifying MES systems is very difficult and requires good data, great understanding of the problems and opportunities, and will take some time.  I can have the project finished in the amount of time it will take to do the justification.”

After some more flaming hoops, we got to finish the project and it all ended well.  It is a constant reminder that sometimes MES takes vision and faith.  I liken it to on-line banking.  There were probably many “old-school” banks that probably scoffed when someone said “you better get online banking up and running here or you may be out of business.”  “Where is the ROI?  Prove it to me!”, they said.  I hope they took the leap of faith and invested in these improvements, because if not, they may be watching from the sidelines.

Same goes for manufacturing and MES investments.  Sometimes it is ROI, vision, and faith combined that gets these projects done.  Sometimes it is leftover capital budget.


At least once a month I have a customer say something like “That is like paying you to do a quote.” Or, “I am not going to pay you to do a quote.” 

MES solutions are among the toughest Manufacturing IT projects out there.  They touch IT, Operations, Automation and Engineering, Quality, ERP, and most of all PEOPLE!  So, approaching a MES project without a plan, some specifications, a few requirements, or at least something written down, is sure disaster.

Here is my house analogy:

You want a new custom home, or at least you think you are ready to embark on the journey.  You are not sure what it is going to cost, but you think you know what you want.  You show up to talk with the builder with no prints, no specs, knowing nothing about the types of cabinets, fixtures, carpet, or appliances that you want, and you want the builder to tell you how much it is going to cost.  You sit down with the builder and start saying things like “we want 3 bedrooms and 3 full-bathrooms.”  Image the builder’s position….do you want granite counters?  Walk-in showers?  Closets the size of small bedrooms?  How is he supposed to help you if you have not defined your requirements?

In the house analogy, this is where the designer and/or architect come into play.  You could also use a builder that does “Design-Build.”  In either case, you typically define what it is you want so that you can get what you want from the final result.  Also, this allows you to go get “apples-to-apples” quotes from multiple builders.

As for MES, most manufacturers don’t know where to start in defining their MES requirements.  And, many vendors are eager to get started on something, so they will start building something for the manufacturer without designing the entire solution.  In our house analogy, this is what I call the Tree House analogy.  If you don’t plan it out up front, your house will start looking like a tree house all thrown together.

Final Suggestions:

  • Define your MES Requirements up front - if you don’t know how to do this, call me.
  • With your definition in hand, seek input from a few builders.
  • Start Small, but with a final design in mind.

 
Opinion Polls & Market Research