It is much more difficult to build a car than buy one. So, even though I’m annoyed by side view mirror controls that dig into my wrist, and I bang my head when I put my daughter in the car seat, I won’t re-engineer the work involved in current car designs to build my own (even though a robot vacuum to clean up after the kids is simply brilliant).
Build versus buy is not only a question in cars, but also MES and paperless manufacturing. As businesses research the benefits to production, quality, and data collection found in paperless manufacturing, each must decide whether to build their own system, or buy from a vendor. There are advantages and disadvantages to each option. For this blog, we’ll look at points to consider as you make your own evaluation.
The ability to design a paperless manufacturing system and control the final product is often the primary reason a company will build rather than buy. Every manufacturer is different, with different processes and unique needs. Incorporating internal processes and needs at the beginning of development helps ensure a better product.
To successfully build your own system, you must understand those processes and needs before you begin. Determining the system requirements can take 2 months or more, and requires significant input from the manufacturing team (pulling them from the shop floor), and management. You should also assume some slippage in the project timeline. No matter how much planning is done, you can’t plan for everything once the code begins flowing.
Any items not included from the initial system requirements will exponentially increase the cost in time and resources for the project. You also need to consider that every requirement you identify for the system will add to the cost. If you have the stomach for the time and money it will take to complete the system, you’ll have the system you want.
Making changes to a system you bought can also be costly. A risk companies run into is creating a “custom” system that will be more difficult to support. When purchasing, make sure to do your research and ask for demos using your current work instructions to see how the installed system will work on your shop floor.
Implementation involves taking the initial design and writing code for it, then installing it on the shop floor.
A system built internally begins with the 2+ months to determine the system requirements before programming and development begins. In addition to programmers, the project requires an expert in User Interface to eliminate unnecessary complexity, and a Data Base Administrator (DBA). Specifications will also affect the final cost of the system. Consider the database and platform, and plan for a product that will work not only now, but in the future for your business.
There are ways to lower cost, such as removing functionality, minimizing testing, or utilizing internal resources, but there are costs associated with these measures, and could affect the long term viability of the system. Evaluate the return and cost for each decision before making choices you may regret.
System integration is another point to consider. Manufacturers and businesses use a number of different software systems and databases. Ensuring those systems work together smoothly is often overlooked in planning.
Purchased systems offer a much lower cost for implementation. Today, there are paperless manufacturing systems that can be installed and integrated in less than two weeks with no disruption of shop floor processes. However, you will not have the design control you have in a built system.
Configuring, adapting, and integrating the system can take longer. Also, beware of systems that require that your shop floor processes adapt to the software, which can significantly increase implementation. Look for MES or paperless manufacturing systems which can reuse your existing work instructions and processes to reduce implementation time and training.
A paperless manufacturing system is only useful if it is up, running, and secure. The long-term reliability and maintainability of the system must be considered in planning.
Every system requires maintenance and upkeep, especially in an industry such as manufacturing where changes in technology and processes are common.
With a system built internally, evaluate how much time and resources you will assign to the maintenance. Will you have access to the team that originally built the software? They are best positioned to maintain the system. How will you handle bugs? How much time in testing, both integration and regression testing, will you accept to repair bugs and flaws in the system. If you see maintainability as a low priority, are you and your team willing to accept temporary patches, flaws, and workarounds in addition to a slow slide toward software obsolescence? Is there a plan to upgrade the system? Considering these issues early in the planning process will help eliminate future surprises, and determine the lifetime cost of the system.
The truth is, many businesses significantly underestimate the resources necessary to successfully maintain a system. Most times they won't intentionally underestimate to work required for maintenance, but once they better understand the requirements, they'll be forced to make sacrifices and the solution will no longer be optimized.
Almost all home built software become “legacy” once the project is complete. If the team that built the system isn’t on staff, the product cannot be tested and is therefore legacy software. Future modifications will be exponentially more expensive.
Reliability and support for a purchased system will depend on the vendor supplying the software. Many vendors offer an inexpensive system initially, and then charge higher fees for service and maintenance. For example, a consultant will often install a base system very quickly, and then require further services to ensure the system works as promised.
Look at the product support before making a purchase. A system with a large support staff will expect customers to help pay for the staff through service charges. Are there fees for upgrades or patches? How is the product maintained?
Many software systems require a license fee, which often includes product support. Most purchased systems have been installed and used countless times, which can be seen as continual product testing, ensuring a more reliable and error free platform. The total cost of the software and maintainability is shared by all the customers.
Reliability in the system helps build the ROI, so take time to make an informed decision.
But, building a system internally allows a level of customization and control a purchased system can’t match. Your evaluation comes down to a simple question – is the benefit of increased customization and control (or other motives driving you toward the solution) worth the increased cost in time, resources, and risk? Look at not just the initial product, but the long-term investment. Have a plan in place for continuing to maintain the system and ensuring the design of the system isn’t trapped in an information silo.
There is also risk and cost in purchasing a system. Some vendors sell systems that aren’t well maintained or supported, or have hidden costs. paperless manufacturing in the Cloud has associated risks. You may not have all the functionality you wanted with the system, since it wasn’t designed internally, but you benefit from lower cost and lower risk for your shop floor.
There are advantages and disadvantages to building and purchasing an MES or paperless manufacturing system, and each company must evaluate the options with internal criteria before making a decision. When building a system, you can get what you want if you are willing to spend the money and resources necessary, and you can mitigate the risk of potential failure. You also need to be aware that a paperless manufacturing system is not a "one and done" project. It requires ongoing maintenance to continue to meet the needs of your business.
Success requires willingness to pay, a stomach for risk, and a devotion to maintainability. Which is why my brilliant robot vacuum is still a dream, and there are still crumbs in the backseat of my car.