This document discusses manufacturing systems and processes. It begins by defining what a manufacturing process entails and lists some common process and product strategies used. It then discusses some examples of enterprise systems like SAP, Oracle, and Microsoft Dynamics. It notes pros and cons of different systems. The document also mentions a methodology called Iconix process that the author has found successful. It concludes by discussing costs, noting that off-the-shelf systems require customization, implementation costs more than $50k, and that calling consultants from the start can be cheaper.
1 of 10
More Related Content
Collaborative Mes
1. The New Collaborative Manufacturing Systems Beyond the Recession by Costantino Pipero
2. Table of Answers imho What is a Manufacturing Process? What system(s) do I need? What methodology helps me? How much time and money will I need?
3. Nobody can go back and start a new beginning, but anyone can start today and make a new ending. Maria Robinson
4. Manufacturing Process The nutshell Take Inputs Generate Outputs Manpower Materials Machines Measurements Methods Products Byproducts Waste Cost Revenue
5. Process and Product Strategies cracking the nutshell a little Process Types Stocking Strategies Discrete Manufacturing Batch Processing Continuous Processing Flow Manufacturing Make to Stock Pick to Order Assemble to Order Make to Order Engineer to Order This just gives a glimpse of the complexity of a process and the possible permutations and combinations just within one single enterprise. Think about what you or your customers make and try to relate to the lists.
7. The Systems which one to choose Examples Pro's Microsoft: .NET + SQL + Sharepoint + BizTalk, etc. Oracle: eBusiness Suite + .NET/Java, etc. SAP: Lots of it with xMII, NetWeaver, etc. Home Grown Easy to Implement, Commonly Known. Solid, Multiplatform, No Dev Licenses. Leader, Widely Adopted. Complete Independence from Vendors, Easy to comply with Standards I do not have a particular preference, I tried most of them. I like the idea of multiplatform,because it makes it easier to integrate on a geagraphical scale and reuse the legacy. But that's just an opinion, it really varies among cases. Con's Short on security, expensive. Complex, relatively expensive. Very expensive, very complex. High Risk, High Maintenance
8. The Method the one I used with most success I love this (the Iconix process); the learning curve is so fast. It requires less discipline yet has all the tools and change management in place. The best method I used so far...
9. Costs or what you have to consider Off-the-Shelf is a myth : what you think of saving in maintenance and liability you will pay in specialized services. Even the so called COTS require a lot of customization at the scale. Trading requirements for out of the box will guide you to the right choice. And design is paramount... It's more than 50K : unless you are talking about a proof of concept. And you have to take into account the cost of the end users and internal expertise needed, the commissioning downtime, the changes, etc... It is cheaper if you call me from the start : I've seen it, I've done it, I've won it, and I've lost it...