Aligning IT and Operations for Successful Smart Manufacturing

Finding success with Smart Manufacturing requires more than software. Six questions will help position your team for improved production with Smart Manufacturing.

By David Oeters, Corporate Communications with CIMx Software

The key to Smart Manufacturing is “alignment” between IT and operations. In a perfect production system, IT-driven tools collect, analyze, archive and deliver critical data to operations, fueling production. Tasks are automated when appropriate and possible, letting users focus on value-added work. IT delivers the appropriate tools, collects the right data, and synchronizes with operations, while operations adapt processes and workflow to make effective use of the data and tools.

MES Success WEB 082813

Digital and Smart manufacturing deliver tremendous benefits for companies that align the efforts of IT and operations. Image by http://www.colourbox.com

The Key to Success with Smart Manufacturing

Success with Smart Manufacturing isn’t a measure of the amount of data or processing power, or the number of integrations or drop-down menus you inflict on a production line. IT-driven tools don’t necessarily mean more software, functionality and systems. Unnecessary complexity will hurt production. Alignment, and success with Smart Manufacturing, requires the right tools and right processes.

Consider the following questions as you plan your own Smart Manufacturing program:

  • Are you putting good data into your system? Many companies moving from a paper-based or legacy system will load bad or incomplete data into a new MES or paperless manufacturing system. Inefficient processes are required to cope with bad data, and continue because no one bothers to correct it. Take time to correct errors before the project begins or adopt a solution that has built in error identification and correction.
  • Are you collecting the right production data? With the IoT (Internet of Things) and modern MES, there is no limit to the data you can collect. Don’t overwhelm operations with data that adds little practical value. Consider the ROI of the data you collect, and set up appropriate data collection.
  • Do you have the shop floor control to make use of the data? You need to synchronize the effort of IT and operations. The tools implemented by IT should match production needs. Operations should adapt to optimize the benefits of the new system, and not cling to old and inefficient processes. Both teams need to communicate and work towards a common goal.
  • Can you analyze trends to track overall efficiency? Process improvement is a core benefit of an MES or paperless manufacturing system. With a software system robust enough to analyze trends, you can identify process weaknesses and help make shop floor management a science rather than guesswork. Move from reacting to problems to proactively avoiding those problems.
  • Can you avoid operator fatigue once the software is in place? Software shouldn’t require operators service the system rather than focus on production. More than overly complex interfaces, it may also lead to operators refusing to use the system or creatively finding ways to avoid it. Consider if the system is truly easy-to-use for both operations and IT.
  • Can the system manage change efficiently? Once installed, many software systems will reflect the operational needs at a certain point in time. As the system ages, those needs will change. Determine how effectively the system can accommodate change, as this will affect the long-term value and TCO (Total Cost of Ownership) of the software.

Optimize Production with Digital Manufacturing

Smart Manufacturing brings IT and Operations into alignment. IT-driven tools improve operations and the shop floor, increase operational efficiency, and deliver better production results. Operations need processes in place to optimize usage of these tools.

Companies that take the time to explore digital manufacturing and design a Smart Manufacturing program that meets the needs of both IT and operations find significantly more success once the system is in place.

Want to learn more, or see how an implementation program can help prepare your company for Smart Manufacturing, then contact CIMx today for a free initial shop floor evaluation with an application engineer. We’re always happy to help harmonize your people, processes and technology.

Easy Solutions to Legacy Software for Manufacturing

Many companies cling to dusty, inefficient software, hindering production and holding back shop floor growth. In a few simple steps, you can move your shop floor to a sustainable, modern software solution.

By David Oeters, Corporate Communications with CIMx Software

How much is your dusty and inefficient software systems costing you? Illustration by www.colourbox.com

How much is your dusty and inefficient software systems costing you? Illustration by http://www.colourbox.com

Legacy software.

We’ve seen companies struggle with old, dusty, inefficient and unproductive software systems written years ago in an outdated software language, and kept on hardware that can’t even be replaced. IT resources are tasked with keeping the system working, but the best they can do is minimize outages. Many times, the system may be used for a single function – to create a single critical report or capture critical manufacturing data, and then all of production becomes beholden to the single, fragile and temperamental piece of software.

Still, the company believes they have no choice but to cling to the glitchy software program, keeping that critical function on software that could fail at any time. They’ve reasoned themselves into a corner.

This may have been true a few years ago, but today there are modern software tools that can not only quickly and easily replace the legacy software, but deliver measurable benefits. You can overcome the limitations of legacy software with confidence and move to a better, more cost-effective solution. The steps to the solution aren’t difficult, or expensive. Start with…

  • Retrieving the Data.

The first step is retrieving the data from the old system. This requires accessing the database, converting the data to a neutral file, then organizing and tagging the data. CIMx has database retrieval experts on staff, and we have the experience to not only complete the work, but finish it faster and with fewer errors or problems. The team will scan the data for errors and problems, ensuring it can safely be used on the new system.  Preparing the system can be done concurrently with retrieving the data, and it starts by…

  • Mapping the Processes.

Using a modern and adaptable MES or paperless manufacturing system, you can map the processes and functionality of the legacy system to the new software system. Many times, this will only require building a script or adding a function or operation to the MES. You should also prepare the database to accept the data you’ve retrieved and copied from the old software system, ensuring the data is correctly stored so it can be used in future operations. In most (if not all) cases this won’t require customization, but a simple configuration or use of an already existing process in the system, and then you’re ready to…

  • Move the Data.
Escaping the constraints of legacy software is much easier than you might think.  Image by www.colourbox.com

Escaping the constraints of legacy software is much easier than you might think. Image by http://www.colourbox.com

Once you have the new MES or paperless manufacturing system prepared, move the data from the old software to the new. Please note, you shouldn’t remove the data from the old system, just copy it over. You’ll load the data, and then review it to ensure no mistakes or problems occurred in the transfer. Repairing the data will correct most problems, but you still want to…

  • Test the New Software.

Now that you have the data moved and the operations and functionality in place in the new software, it’s time to test. Run a series of test cases on the new system to ensure the processes and functionality are running correctly. Make adjustments if necessary. Once testing is done, you’re ready to…

  • Run the New Software.

It’s time to test the new software system in production. In the beginning, you will run the new software simultaneously with the old Legacy system. Each will perform the same operations in parallel. This will give you the assurance you have the functionality of the old software while you are running the new software live in production. During this time, you can see how effective the MES is in replacing the old Legacy system, and make adjustments as needed because eventually you will…

  • Replace the Legacy Software with New System.

After testing the new software and making any necessary adjustments, you can begin rolling over all the functionality of the legacy software to the new system. This may be as simple as having the team use the new software instead of the old. While having the two systems run parallel, you can easily move over to the new system in phases, starting with one production line or area before moving to another. The final goal should be having the entire plant running on the new software system. Then you can celebrate and shut the old software down completely.  While much of the schedule will be dependent on the data being retrieved, normally the process can be completed in weeks or, in a difficult case, two months if the MES has built-in integration and migration tools.


Deliver solutions to legacy software to your shop floor with minimal cost and effort.  Illustration by www.colourbox.com

Deliver solutions to legacy software to your shop floor with minimal cost and effort. Illustration by http://www.colourbox.com

There are a number of advantages to this process, and to moving away from an old system to a new one. In addition to more uptime and stability, your data is now in a more secure database. Many times, this means it is easier to use in analytics. By putting it in an MES, you can also more easily link the functionality of the legacy software to the integrated production records. In addition, you have an integrated and complete manufacturing software solution with the MES. Production goes to a single system for all the information they need for operations.

When you consider how easy it is to deliver all the necessary digital functionality you need for the software in a single system, it’s an easy choice to phase out old software that can’t provide the functionality and efficiency you need. Want to learn more, or discuss how CIMx can help you replace your antiquated software? Give us a call today for a free shop floor review of you software. We’re happy to help.

4 Tips for Evaluating New Technology for Manufacturing

Use these insider tips to cut through the hype and evaluate new tech and tools with a critical eye to deliver benefits rather than bloatware for your shop floor.

Written by David Oeters, Corporate Communications with CIMx Software

Evaluate new shop floor technology with this easy-to-use tool. Image by www.colourbox.com

Evaluate new shop floor technology with this easy-to-use tool. Image by http://www.colourbox.com

Today, new technology and applications for manufacturing are flooding the market. Companies are trying to capture Smart Manufacturing lightning in a bottle for quick profits, or discover how, exactly, the Internet of Things (IoT) is going to work. Every one of these products promises they can make everything better with their application, or system, or plug-on (or –in), or tool, or some other magic widget that will add instant Industry 4.0 deliciousness to your existing MES or paperless manufacturing system.

There is so much noise out there; it’s difficult to separate hype from truth, or fact from fiction. Products can promise the world, but in manufacturing if it’s not improving workflow and processes, it’s not worth it. A new manufacturing tool or system must be implemented with operational need in mind, and not just for the flashy “new-ness” of it.

Even so, manufacturing leaders must work to maintain a competitive edge, and be prepared to seize the opportunity offered by new technology. In a tight market, even a small improvement can lead to increased profit. You need a tool to evaluate new technology for potential benefit. With that in mind, we’ve prepared 4 critical questions you can use to more accurately evaluate new technology. As you ponder the promises made by a tech company, consider the following:

  1. Does it solve a problem or improve operations?

From our experience, most companies install new software or technology to solve a specific problem. It might be a failed audit, or out of control paper on the shop floor or inscrutable production documents stored in boxes. Before installing a new tool, evaluate the benefit. Will it solve a specific problem? How will it improve operations? Don’t add functionality without a clear benefit.

  1. Do you have an accurate estimate of the ROI for the investment?

You will need an objective way to evaluate the new software or tool. The ROI (Return on Investment) is a comparison of the cost of the tool against the benefit of the functionality. Before installing anything, make sure you have an accurate estimate of the ROI. Many of the flashy, shiny new tools will offer “Wow” factor with little return. A system that offers a low cost solution that improves production in a number of ways will have a much greater ROI.

  1. Will the solution grow with you?

Static, custom-built software systems are no longer a viable investment. Technology and operational needs change so quickly, the moment you install a system it will begin to lose value. Before you install or implement anything, have an upgrade path in place. What is the TCO (Total Cost of Ownership) of the solution, once you consider the cost of updates? You need a software system that adapts and grows as your needs change.

  1. Are there gaps in how you will utilize the system?

You need to think beyond the data collected by a new system to determine the benefit. Do you have a way to act on and implement real-time data, or are you still relying on error-prone paper-based work instructions? Do you have machines with an output that can’t be used by the monitoring system? Want to use dynamic scheduling? Make sure you are collecting the data you need to adequately feed the system.


New technology promises to reshape manufacturing in ways that were unheard of a few short years ago. But, you need to approach the marketing promises with a critical eye to ensure you can adequately benefit from the investment, or you aren’t putting your faith in a piece of flashy tech that will be outdated in a few short months.

Got more questions? Contact us for a free evaluation to identify technology gaps that may be holding your shop floor back. We love manufacturing, and we love technology, and we’re happy to help any way we can.

What Can You Do to Keep Your Company from Drowning in Technology Debt?

Many companies today are drowning in tech debt, and they don’t even know it. A few simple tips will help you manage your tech debt and determine your next steps in enterprise upkeep.

By David Oeters, Corporate Communications with CIMx Software

Technology debt is a term that originated in programming. Originally, it explained the programming debt developers would incur while writing code. A quick and easy solution in programming might incur a future “tech debt” – when that quick solution would require significant modification or hinder future progress. Another solution might require more development resources to implement, but will drastically reduce or eliminate the need for modification and better support future development.

Modern manufacturing relies on solid support from IT. What can you do to support production? Illustration by www.colourbox.com

Modern manufacturing relies on solid support from IT. What can you do to support production? Illustration by http://www.colourbox.com

In manufacturing, the Technology Debt is the total cost of replacing outdated technologies or systems as they begin to degrade the overall functionality of the company. In general, manufacturing is reluctant to add new technology, and so as systems age the overall effectiveness of the operation degrades. Companies struggle to determine when they finally have to pay their technology debt.  When is it the right time to make a change or add a new system? What risk will they take with a technology purchase or implementation? In the end, many manufacturing companies fool themselves into continually delaying a project – their technology debt becoming a massive expense. This will hinder production, increase errors and decrease efficiency, but as long as production limps along, these companies continue to wait.

Evaluate Your Manufacturing Technology Debt

Are you curious to know how large your tech debts might be? Use the following questions to analyze your current systems and better understand the benefits of your software and technology systems:

  • What is the cost of the current software or system?

Most enterprise software and systems have a licensing cost, which is only one part of the cost of the system, but it is a good place to start. You also need to study the hidden costs of the system.  Look at the amount of time and resources necessary to maintain the system. If IT spends an average of 20 – 30 hours a week maintaining, or repairing, the system, this is a significant expense that must be added to the analysis. Lost production during times when the system is down will also add to the cost. Finally, look at the expense you may be incurring by using a less than optimal system. For example, if you can’t integrate a legacy system with your current ERP, then there will be a cost for manually moving data from one system to another.

  • Is the current system upgradeable?

Look at the current system, and determine if it can be upgraded.  What is the cost of the upgrade? If you have a custom software system, the cost of any upgrade will be significant. Over time, this cost will only grow as you continue to upgrade to pay off that tech debt, increasing the TCO (Total Cost of Ownership) of the software. In addition, systems that are difficult to upgrade, or don’t have a clear upgrade path, will degrade your overall productivity exponentially. The system you have isn’t going to get any better, and you risk the eventual cost of the tech debt becoming prohibitive. Keep this in mind as you consider a new system versus an upgrade of your current system.

  • How much will the new system increase shop floor productivity?

Too often, as companies begin to evaluate their systems, they don’t consider manufacturing and operations. They will look at the front office and IT compatibility, but not the potential dramatic benefit the new system will have to shop floor productivity. For example, eliminating paper from the shop floor with a paperless manufacturing system will save on the cost of paper and ink travelers and build books. Scrap and errors can be eliminated. The need to input the same data multiple times is removed. Redline edits and change orders are improved. Even so, some companies are satisfied meeting the need with a lesser, forms-based system that leaves paper on the shop floor. Understand your current processes and evaluate the benefits to the process with the new system. Many times, the benefit to productivity will more than pay for the entire new system.

  • What is the overall cost of the replacement or new system?

Many companies today still believe a new manufacturing software system will cost millions of dollars, and require several years to full develop and implement. With new software technology, that’s no longer the case. A new system can be implemented in as little as a few months, and may cost much less than the licensing costs of your current, outdated system. As you evaluate your tech debt, work with a vendor you trust to understand your current shop floor and find a solution that meets your needs, then determine the true cost. As you study the cost, look at the licensing fees, the cost of product support, and the internal resources necessary to maintain the system. Before selecting a course of action, make sure you are comparing the true costs of both your current system and a potential replacement system.

  • What does an “integrated” system really mean?

Often, and with good reason, IT resources in manufacturing will be reluctant to add a “new” system to their enterprise. They are reluctant to tackle new software without an idea of potential benefit and an understanding of the internal resources necessary to maintain the software. Anything new is immediately seen as “system bloat” no matter the manufacturing benefit. Because of this, many companies look at “modules” or extensions of a currently implemented system, and end up creating the problem they hoped to avoid. The truth is, many companies offer “modules” they purchased from another software vendor. The module isn’t really linked to their product, and may not even be compatible to past versions of their software. Integration, implementation and installation becomes a massive project more complex than adding an entirely new system. For an honest analysis, study the benefit of competing systems, and identify the support needs of each individually. Don’t be fooled by a system having the same name.

The Enterprise Cost of Increased Tech Debt

As companies delay paying off their tech debt or upgrading their current systems, the problems faced by their operations team will only grow. The problems – shop floor errors, scrap, the inability to meet customer needs and lost production – will explode. Technology and modern manufacturing has reached the point when companies that haven’t upgraded, and haven’t addressed their tech debt, will no longer be able to compete or operate in the global marketplace.

As your manufacturing tech debt grows, the cost to your company will grow exponentially. Illustration by www.colourbox.com

As your manufacturing tech debt grows, the cost to your company will grow exponentially. Illustration by http://www.colourbox.com

Many times, tech debt grows because of the separation between operations and IT. Both operate in enterprise silos, and overcoming challenges without understanding the perspective of other departments create problems.  It’s in these cracks the tech debt grows. Operations have a growing production need which IT doesn’t understand, so the company waits to fill that need because operations can’t adequately communicate the value of the system. IT is only added to the implementation team late in the process, and their needs are never factored into the decision. Miscommunication leads to projects being shelved and the tech debt growing – the problem being put off for another year.

That old paradigm will no longer work in the new world. New technology and processes, increased customer demands, government regulations and the need to operate on a global scale are pushing many companies to finally eliminate enterprise silos and pay their tech debt. Companies can no longer wait – they have to adapt, update and embrace technology and new systems and software.

What are your greatest technology challenges? How are you managing your tech debt? Let us help you eliminate your tech debt and overcome operational challenges. Contact CIMx for a free evaluation of your shop floor today.

Insider Secrets to System Integration for MES and Paperless Manufacturing

There’s confusion out there in the MES and paperless manufacturing market about what “system integration” means and what it can do for your company.  We cut through the confusion and offer tips for ensuring integration leads to benefits for you and your shop floor.

By David Oeters, Corporate Communications with CIMx Software

Considering an "integrated" software solution for your shop floor?  Get the facts before you invest. Image by www.colourbox.com

Considering an “integrated” software solution for your shop floor? Get the facts before you invest. Image by http://www.colourbox.com

System integration.

For many manufacturers, the term has taken on mythical, magical, properties.  Like some IT or software unicorn, many companies are questing for the holy grail of total “SYSTEM INTEGRATION.”  They call it the “digital enterprise,” “enterprise integration,” or “operation integration.”  Companies feed into the myth, believing they cannot achieve operational Nirvana without system integration.  Current IT trends and tools lend support to these beliefs, especially big data and advanced analytics – both require integrated systems.

There are benefits to system integration for savvy manufacturers.  It’s worth the investment, but many companies fail to fully realize the benefits in their single-minded focus on complete system integration.  They may even be hurting production.  The goal shouldn’t be a monolithic digital enterprise, but improved productivity and better business processes.

We want to take a brief look at system integration, focusing on the benefits and dangers rather than the technology (which can change quickly as new products and techniques are released), and offer tips on how you can design a more successful integration project.

What is System Integration?

System integration is a computer technique where individual software components are combined into an integrated whole.  With interconnected systems, electronic data is shared and exchanged across the network, ensuring accurate information is available anywhere and at any time.  Integration improves communication and coordination.  By linking computer systems or software applications together, either physically or functionally, the entire computer network acts as a coordinated whole, eliminating information “silos” that occur when data is input in different locations.

There are several methods of system integration.  Most utilize a variety of techniques, not just new software or hardware.  Cultural adaptation and coordination, as well as an evaluation of business processes, are also required for a successful integration.

The Benefits of System Integration

The primary benefit of integrated systems is improved functionality.  Data within the organization will be fully harmonized, creating a more capable system, improving performance and enhancing existing systems.  Reports will access more data, improving accuracy and decision-making while delivering better operational management.

How much integration do you need? Consider the costs and ROI before making a final decision.  Illustration by www.colourbox.com

How much integration do you need? Consider the costs and ROI before making a final decision. Illustration by http://www.colourbox.com

Manufacturing pioneered the early study and use of system integration as companies sought improved operations through the use of Computer Integrated Manufacturing (CIM).  In CIM, companies used computers to integrate manufacturing activities.  By integrating computer systems, such as product development, process planning, production, and delivery and after sales, companies could deliver accurate information where and when it was needed, and in the format that was required.

Companies that smartly invested in CIM were rewarded.  The US National Research Council asserts production can be improved through CIM by as much as 40 to 70 percent.  Design costs can be reduced by 15 to 30 percent, and overall lead time can be reduced by 20 to 60 percent.

Navigating the dangers of system integration

Simply pushing computer systems together, or imposing a new workflow process or computer application, is not enough to achieve beneficial system integration.  Many times, the drive (or quest) for system integration begins in the front office, not the shop floor, which can lead to a number of problems for production.  A system that benefits one department may not benefit or even work for another, hindering productivity, reducing benefit, and building resistance to the overall integration plan.

The fact is, the business processes and computer systems that work for finance, IT, or product design aren’t an optimal solution for production.  An ERP is a transaction-based system, and the data, output and processes are different than a behavior- or process-based MES or paperless manufacturing system. A transaction-based system catalogs data, while a process-based system manages workflow with information.  Trying to impose a transaction-based system on shop floor workflow is inefficient.  Any advantage gained from the system integration is lost as more resources are required to complete work.

In an effort to create a common data format or a shared operational system for the integration, many companies will sacrifice operational efficiency.  Manufacturers will lose the operational functionality they need.  A transaction-based system will never offer the tools necessary to optimally manage redline edits or deliver process enforcement, even if it works great for HR or design.

Consider the cultural side of the equation.  Can you imagine imposing engineering workflow or finance workflow on an assembly or production line?  It sounds silly, but many companies do that when the purchase a “suite” of pre-integrated software systems.  It delivers front office benefits by sacrificing operational efficiency.

Tips for successful software integration

Consider these tips as you evaluate the opportunities for system integration:

  • Set specific goals for the integration, and ensure those goals are met with a clear ROI. Many times, companies will continue to add functionality as their costs and project complexity grows exponentially.  Add in the costs a piece of functionality may have to one area, and for some projects an ROI will never be achieved.  Manage your initial expectations to focus on the initial key project drivers.
  • Look at not only a technical solution, but a cultural one as well. Start the process by breaking down the cultural boundaries in your company before rolling out a technical solution.  This will require buy-in and consensus.  Make clear not only the goals, but the expectations.  Give each area a voice in the final solution, and ensure their needs are met.
  • Look at delivering the project in phases, rather than a single, massive installation. Any enterprise-wide system integration is more than just software installation, it requires a cultural shift.  Tackling an enterprise project is not just technically difficult, but culturally difficult as well.  A phased implementation will eliminate many of these problems.
  • Look for added value in the project, and ensure it is real value, and not just functionality. For example, linking design and production on a single system is one tactic, but many times system integration can be as simple as sharing a single database with revision control and an approval process, and doesn’t require an entirely new software package.  The value of the project is achieved without the additional and unnecessary complexity.
  • Beware of vendors promising an “integrated” solution. Many companies are working to build “digital enterprise” software.  Their tactic  is to “purchase” solutions to be integrated into their own system.  The result of these purchases is often problematic.  The integration the vendor makes by smashing the system together may not match your current processes or needs, and will add complexity to the installation at your site.  The benefit the vendor gains by marketing an “integrated” solution does not translate to your shop floor or enterprise.
  • System integration doesn’t require a single “master” system to manage operations. Look at sharing data across relevant systems using an application-independent data format.  This project can easily be done in phases.  For example, send orders from your ERP to your MES, automatically generating orders for production.  Once a product ships, send the product data to the PLM to create a master record.  Strategically link your systems to maximize value and increase functionality, rather than making wholesale changes to your operation or workflow that lead to enterprise disruption and the never-ending project “roll-out” that is outdated by the time it finally launches.
Don't be fooled by "integrated" hype.    Illustration by www.colourbox.com

Don’t be fooled by “integrated” hype. Illustration by http://www.colourbox.com

Just like a magic unicorn, more often than not a single “enterprise” system sounds good, but the implementation is problematic.  Forcing change and new processes to ensure a single system isn’t integration.  It leads to unnecessary complexity, project delays, and problems.  When planning a project, consider the needs of each area, and how the system will benefit them.  Conduct the project in phases, with clear goals and expectations.  Want to learn more, or see how you can begin a phased implementation of a system integration project?  Give us a call or leave a message.

5 Ways You Can Tell If Your Software is Wasting Money

Is your software getting old and dusty?  If so, it is likely costing you money, resources and productivity. We offer ways you can tell if it’s time for an upgrade or new system.

By David Oeters, Corporate Communications with CIMx Software

Are you sacrificing productivity and profit to a dusty computer system?  Illustration by www.colourbox.com

Are you sacrificing productivity and profit to a dusty computer system? Illustration by http://www.colourbox.com

Is your software getting dusty, stale, moldy and old?  Is it costing you more to maintain it than it makes for your business?  Many companies are currently using old applications that hurt production and siphon away profits.

It’s true – code can get old and dusty, becoming Legacy code or a dusty deck.  It can collect (digital) mold and (binary) creaks and cracks, just like an old house or any other human construct.  Just like an old house, code and applications become increasingly costly and begin to degrade and deteriorate over time, unless you invest in adequate system upkeep.

Identifying a Dusty MES System

Want to know if your system is getting dusty?  Here are a few telltale signs it’s time to upgrade your application:

  • Bitrot in your code.

Bitrot is the silent, and normally barely noticeable corruption of data.  Over time, a random piece of data in the application may become corrupt.  A malfunctioning piece of hardware or a loose cable can result in even more data corruption.  Eventually, this degradation can cause software rot, resulting in diminishing responsiveness and deterioration of performance.  Even worse, bitrot can permanently corrupt your code and data, resulting in lost information.  Worst of all, regular back-ups won’t solve bitrot.  Your back-up system will happily store the corrupt code just as easily as the good data.

Look for systems that have become sluggish, error-prone or non-responsive, a clear sign of bitrot.

  • Architecture and platform constraints.
Operational technology relies on a solid Information technology support system. Are you delivering the right tools?  Illustration by www.colourbox.com

Operational technology relies on a solid Information technology support system. Are you delivering the right tools? Illustration by http://www.colourbox.com

Many older applications are built on an outdated platform or architecture that constrains production and your business.  Client/Server was once a popular architecture model, but today many companies are turning to Web 2.0 applications or the cloud – though there are dangers lurking in the cloud, especially for companies that want to protect their intellectual property.  Today, some companies (not all) are constrained by this once popular platform, and an upgrade or update will be very expensive.  So, they chug along using older technology and hoping nothing breaks.

When considering a new system or upgrade, be aware of the constraints placed on your choices.  Evaluate the platforms you work on, and see if one is causing more trouble than benefit.

  • Exceedingly expensive to upgrade.

Many computer applications start out as an OTS (off-the-shelf) solution, but over time additions are made to the core system.  Eventually the OTS solution becomes custom software.  Even configurations can lead to customization.  Make enough of them, especially in the core code, and the developer or original vendor won’t be able to recognize the product.  You won’t be able to utilize a new integration or make any changes or updates to the system without adding to the custom code, which can be expensive, risky, and time-consuming.

  • You are adapting to the application, and the application can’t adapt to you.

This is more of a question for operations than IT, but, potentially, it can be the most costly symptom of a dusty application.  Many times, especially with template-based systems, the application will be designed for a certain workflow.  Over time, as customer or market needs change or new technology or techniques are added, the shop floor workflow will change.  With a dusty computer system, unable to adapt to changes, you’ll end up twisting and cramming your production into old templates or non-optimized workflows.  Many times, this results in a significant productivity loss.

Ask your shop floor how well the computer system works for them, and if there are specific capabilities or functions that just aren’t performing well.  This is another sign of dusty software.  In some cases the software is actually slowing the workflow and creating an inefficient production process.

  • You can no longer integrate new technology or systems.

This symptom could be caused by an older architecture or custom code, but not always, and it is another sign of dusty software.  There may be times when a new technology or new computer system is introduced to the shop floor – the release of a new version of Java, or a new browser.   If the software can’t support the new technology, and there are no plans to support it, you clearly have dusty software.  This symptom can take a number of forms – for example, if the application in question can’t integrate with newer systems or technology you are bringing online, or it is costing more money to maintain or holding back vital upgrades, then the system is likely old and dusty.

Problems such as this should be addressed quickly.  Many companies let a small problem become a massive crisis when Microsoft announced they were no longer supporting Windows XP.

Wiping Away the Dust

Once you’ve determined your software is dusty, there are a few steps you should take.

Success depends on the right tools working efficiently to support the business.  Position yourself for success.  Illustration by www.colourbox.com

Success depends on the right tools working efficiently to support the business. Position yourself for success. Illustration by http://www.colourbox.com

First off, look at what the software and application is costing you.  This is more than just maintenance costs of licenses, there is also the cost of lost productivity and revenue.  Ask your operations team how well the software is working, and what it could be doing better.  Look at your current workflow and identify areas the functionality is not meeting production needs.  You don’t need an exact figure, but with a little work you can quickly determine if the software is providing the reliable operational technology your team needs.

The next step is to ask the vendor if there is an upgrade.  If there is, look at the functionality and improvements provided by the upgrade.  Does the upgrade provide the functionality you need, and will it fix the degradation and problems hindering production?  Ask about the cost, both in resources, money and potential shop floor downtime.  Determine if the ROI for the upgrade is worth the cost.

Finally, if you’ve determined you have dusty software that is hindering production and affecting productivity, and an upgrade is too costly or won’t eliminate enough of the problems to make it worthwhile, you need to start looking at alternate solutions.

Start your investigation by looking at the latest technology and computer platforms; otherwise you may be swapping one problem for another.  Look at Web 2.0 solutions for their adaptability and innovative ways it can present, store, and deliver information.  It is extremely easy to maintain and upgrade, supports collaboration, and eliminates many of the problems earlier information systems had.

Integration may be of initial concern, but, to be honest, most modern paperless manufacturing and MES systems integrate fairly easily with other current systems.  Ask the vendor about the integration costs before you get too far in the selection process.

Selecting the Right Solution

I would still wait on implementing cloud-based solutions, especially for companies where intellectual property is a concern.  Manufacturing is the revenue generator for a business, and offering manufacturing intellectual property to the cloud can be a great risk, especially when there are an increasing number of threats out there.

Evaluate a potential solution before selecting a product and beginning implementation.  Image by www.colourbox.com

Evaluate a potential solution before selecting a product and beginning implementation. Image by http://www.colourbox.com

If you still feel the cloud offers benefits hard to ignore for your business, look at building an internal cloud, closed to the public.  Building an internal cloud is easy to do, offers most, if not all, of the benefits, and eliminates the risk for little cost.

Finally, make sure you involve operations in any decision you make.  While the job of IT is to provide the foundation for operational technology and tools, it’s operations that will use them to generate the revenue and ROI to pay for the tools.   You need to make sure any system that’s implemented meets their needs and will work for their workflows.  They must be involved in the selection process.

Want to know more, or take a quick review of your current systems to see how dusty they are?  Give CIMx a call today or leave us a message.  We can do a review of your current shop floor and computer systems for no cost to determine how much you can save with a new system.  In some cases the cost of a modern replacement solution will be less than the annual cost of maintaining the existing creaky system.

We’re happy to help.

What do we mean by “Off-the-Shelf” Paperless Manufacturing?

For manufacturers searching for an Off-the-Shelf (OTS) software solution for the shop floor, but the truth is, you may be surprised what OTS for different vendors.

By David Oeters, Corporate Communications with CIMx Software

It’s easy to see why an Off-the-Shelf (OTS) paperless manufacturing software is an appealing option for manufacturers.

What does your vendor mean when he tells you software is off-the-shelf.  Illustration by www.colourbox.com

What does your vendor mean when he tells you software is off-the-shelf. Illustration by http://www.colourbox.com

Custom software solutions may be designed specifically for your shop, but it’s expensive – both in money and resources.  Upgrades and changes will be equally expensive.  Systems take years to build, and are risky.  Many projects never even make it to the shop floor.

An OTS system costs a fraction of a custom system, and can be installed and working in significantly less time.  Most OTS systems offer more functionality and an upgrade path, and are supported by the software vendor.  It’s less risky, and project success is easier to achieve.

Researching OTS solutions on the market will quickly reveal a strange truth.    Some companies say they are OTS because they use a library of “modules.”  They design a solution using modules to shave a few months off the implementation.  Other vendors purchase a company (or three), and mix and match functionality to create a Frankenstein-like solution.  Perhaps OTS means they use old code (you know… code written 15-20 years ago) for the foundation of your new solution, then customize the rest.  Some call this “custom off-the-shelf,” as if they have discovered a magic bean offering you the best of both worlds.

To alleviate doubt and questions you might have, here’s some of what you’ll find in our off-the-shelf solution:

  • A Complete Software Solution

CIMx offers all customers their complete software solution, not individual modules or functionality thrown together to design a “custom” solution.  Our solution is completely integrated, built entirely in-house, and is designed to offer all the functionality and tools manufacturing will need.

However, if you don’t need all that functionality, you can easily turn off parts of the product, paying for only those sections you need.  In the future, expanding the solution is as simple as turning on features already installed.

Installation takes a day of work.  When complete, you have a fully-tested, functioning software solution, with a clear and easy path for upgrades, updates and patches.  Support is simplified.  You won’t struggle to adapt and integrate custom code in your system.  Offering customers a complete solution simply makes sense, and lowers the initial cost and overall TCO (Total Cost of Ownership).

  • Behavior-based Solution

When looking at MES or paperless manufacturing software, there are two types of systems: behavior-based and template-based.

A template-based system requires specific screens of information and sequences of data input.  The system utilizes forms to guide work through highly formatted templates.  Templates are a structured format that drives consistency, but the system struggles to adapt to changing processes.   A template-based system might be marketed as “OTS,” but it will require significant time and effort to format to your needs.  Some companies call this “configuration,” when really it is customization of the solution and a redo of all your existing planning and specifications.

A behavior-based system, such as the one CIMx uses, adapts to shop floor processes and behaviors, offering tools to improve your current manufacturing work flow and shop floor processes, rather than dictating an entirely new process or workflow.  Users configure the screens, and attach the information they need, including their current work instructions.  The system adapts and supports behaviors that produce an efficient and productive shop floor, and doesn’t require extensive configuration, delivering true OTS functionality.


Because CIMx utilizes a behavior-based system requiring minimal initial configuration and installs the entire system implementation is a quick and easy process.  If you have the necessary hardware on your shop floor, the system can be installed and set-up within a few days.  Since your existing work instructions can be attached to operations within the system, the planner can begin creating work plans almost immediately.  You can slowly add data collections and other elements, building a library of approved planning.  Training can be completed in a few hours on the shop floor.

Most customers have the system up and running within a few weeks, depending on the amount of work instructions that need to be loaded into the system.

That’s how we define Off-the-Shelf.  Next time a vendor tells you they offer an off-the-shelf solution, take a moment and ask a few questions.  Discover how “off-the-shelf’ their system truly is.  You’ll be surprised at what you discover.  As always, let us know if you have questions.  We’re happy to help.

Is Paperless Manufacturing Moving to the Cloud?

The cloud is changing the way software and IT service is delivered, but is it ready for manufacturing?

By Nick Stonebraker, CIMx Software Developer

Can the cloud deliver shop floor visibility and control through paperless manufacturing? Image by www.colourbox.com

Can the cloud deliver shop floor visibility and control through paperless manufacturing? Image by http://www.colourbox.com

Ever have someone put in an IT Service ticket and ask you to “get” their Yahoo email account to work?  “I click on the email,” they might ask. “And it doesn’t do anything.  Can’t you open it?”  Of course, after checking their web browser, there’s not much you can do (unless you work for Yahoo).  Many don’t understand that subtle fact, because the cloud is still a mystery for so many users.

Try to explain where an application or file is in the cloud, and many get this slightly lost look and begin peering everywhere, hoping for a glimpse of the “cloud.”  It’s a mystery, but it’s a cool mystery that saves money and provides a host of user benefit.  Most users may not fully understand the cloud, but they know it works and appreciate the benefits – which is why you should be prepared to answer the (inevitable) question, “Why isn’t the shop floor on the cloud?”

Cloud computing, computing services hosted over the Internet, offers a number of advantages for the shop floor.  For example, we all know cloud service is often fully managed by the provider, eliminating many upkeep costs and lowering overall expense.  Patches, updates and product maintenance can be done remotely, requiring little time and resource investment but still ensuring users have the latest releases.  With the cloud, users pay for only the services they use.  The service can be quickly scaled when need arises, eliminating many of the emergency crisis that overworked IT departments (understandably) struggle to handle.  But, there are hazards hiding in the promise of cloud computing.

Data Loss

A recent survey by Symantec found that 43% of the respondents using Cloud services admitted to data loss.  Admittedly, some of the data loss could be attributed to user error, including misplaced or misfiled information.  For a shop floor, secure information and data management is necessary, especially in heavily regulated industries facing potential audits.  Effective paperless manufacturing relies on secure data management, revision control, and secure production records.

Data Security

Is a cloud-based MES right for you?  Illustration by www.colourbox.com

Is a cloud-based MES right for you? Illustration by http://www.colourbox.com

Because so many users are accessing the cloud, a number that significantly increases with public cloud services, data security is a challenge.  More users increase the risk. Unauthorized users can (accidentally or otherwise) access data they shouldn’t.  Adding a cloud-based ERP system to shop floor systems magnifies the risk, because you have even more users potentially accessing the manufacturing system.  Potentially, secure data could be inadvertently moved to a less secure area of the cloud, especially on shared servers. The truth is, with any new technology it takes time to develop standards, and the operational standards for cloud computing are still a work in progress.

Trust

With cloud services, you are entrusting data to another company, opening yourself to risk.  Theft from your service provider is one potential risk.  Inadvertent mistakes by employees of the service provider, such as unsecured apps on a work device connected to your data, is another potential risk.  Consider the “neighborhood,” or server, where your data is stored.  In a recent example, an FBI raid on a server used by cybercriminals led to several businesses losing data.  They unknowingly shared a server with criminals, and during the investigation their data was lost.  Finally, there is the question of who, ultimately, owns the data – you or the company providing the server?  Assumptions over ownership and responsibility may not be clear at first, and can lead to significant problems in the future.

Service Failure

Growing cloud use leads to another problem – failure of service availability.  Recently, Gartner predicted that as more businesses move to the cloud, there will be an increased risk of “cascade” service failures.  Businesses are connected on shared servers, and problems can quickly spread, leading to widespread service outages that would have been contained if computer services were localized.  As more and more companies rely heavily on the cloud, this risk will grow, and since significant downtime is not an option for most shop floors, failure of service is a risk to operations you can’t control.

Mobile Manufacturing

A recent report from the Cloud Security Alliance (CSA) cited a survey of more than 200 enterprise executives concerned with mobile device security and data in the cloud.  More and more industries are using mobile devices in business, including manufacturing.  Mobile manufacturing holds tremendous advantages for the shop floor.  But, as businesses adopt cloud services; unsecured mobile devices create unintentional “back doors” into secure data.  Potentially, any mobile device could access your cloud, including devices you can’t control.


Cloud computing hold tremendous promise for the future, and will continue to grow as businesses adopt the new technology.  It is a powerful tool.  Data protection and recovery is a strength of cloud computing, significantly decreasing the cost and time for disaster recovery, especially in automating backup and speeding up the restoration process.  Almost all data in the cloud is encrypted, which will significantly improve security.  There are cost savings in the cloud, and the ability to scale resources to meet current needs can significantly improve a businesses ability to overcome challenges

But there are currently hazards to moving your shop floor data management to the cloud.  Service providers and enterprise IT resources have not been able to provide the appropriate level of security, both in the cloud and among users.  The cloud is an emerging technology, still struggling with growing pains, which may impact the ability of a provider to deliver the level of service, speed and accuracy necessary for the modern, dynamic and constantly changing shop floor.

But, cloud computing is a promising technology.  As service providers find better solutions and tools for enterprise cloud services, it will become a viable option for the shop floor.

Have you ever considered preparing for the cloud with an internal cloud-based system to manage production data?  A web-based paperless manufacturing solution hosted on an internal server is a cloud-based process control solution that, when there is an appropriate level of security and reliability, can be uploaded and served on the cloud.  This is a step toward the future without experiencing any of the current risks in cloud computing.

What experience have you had with moving your MES, paperless manufacturing or ERP services to the cloud?  Are there benefits to adopting a “cloud” strategy for your shop floor we haven’t covered here?  Speed and the ability to quickly make global changes to a system is a significant benefit we haven’t touched on.  Are there challenges or hazards we missed?  Let us know what your experience has been with the cloud.

How Can IT Prepare for the Future on the Shop Floor

We’ve already begun studying ways to use Augmented Reality on the shop floor.  Are you ready for the future of manufacturing?

By Nick Stonebraker, CIMx Software Developer

It sounds like a scene from a science fiction movie – a shop floor worker wanders a warehouse or production area.  He wears a device over his eyes, and everywhere he looks data scrolls before his eyes.  The temperature of a machine appears in a graphic. An arrow points in the direction of the material he is looking for, while a red warning sign flashes over a danger on the floor.

It’s known as augmented reality – using technology and computer-generated sensory input to enhance the user’s view of the real world.  With Augmented Reality, technology works to enhance our current perception of reality.

The Reality of Augmented Reality Within Manufacturing

The future is coming to your shop floor.  Are you ready?  Illustration by www.colourbox.com

The future is coming to your shop floor. Are you ready? Illustration by http://www.colourbox.com

But it’s not science fiction.  With Google glass and similar devices it is a reality.  Technologists are already studying how Augmented Reality will shape the future.  A recent article (Could augmented reality make work easier?) by BBC News details how a mock- up shop floor in Munich, Germany, is experimenting with Google Glass to determine how augmented reality could improve production, eliminate errors, and aid the shop floor in their daily tasks.

According to the article, the system uses a combination of Google Glass and software so workers can “see” (through Google glass) where items need to be collected or stored without referencing a clipboard or another device.  Workers aren’t confused or lost as they search for materials.  Service managers are provided step by step instructions on fixing broken equipment – presumably overlaying the instructions on the broken equipment leaving both hands free for the work.  Data collection can be completed with a glance (literally) as the necessary data is collected by Google and recorded as needed.

At this point, the benefits to manufacturing are obvious.  Non-value added work is eliminated from the shop floor.  Workers have information sent directly to their eyes, leaving their hands free.  Productivity increases, and data collection is streamlined.

This is not to say there aren’t challenges to the technology.  Right now, setting up the system is very expensive and difficult, and with current battery usage, users have only 15 minutes before a recharge is needed.  However, the promise of the technology is there, and it’s coming.  The only question is when an executive or shop floor manager is going to ask what work you’ve done to research Augmented Reality.

How do you manage shop floor information?

One important step to preparing for Augmented Reality is to study your current systems that manage shop floor information.  Successful modern manufacturing requires effective information management.  Consider this… a review of the characteristics found on the most successful shop floors, such as complete as-built reports, material genealogy, process enforcement, and data collection, there is a focus on information management.  You need to get the right information to the right people at the right time in a way that eliminates complexity and maximizes efficiency.  You also need to collect data on what is happening at each work station.  Effective information management is a primary benefit of paperless manufacturing and MES.  Paper-based records and work plans are inefficient and are largely unsuited for modern manufacturing.  Paper is error-prone and holds back a shop floor from achieving effective production.

Consider more than just the status of your work plans and records, but how information is collected from the shop floor.  Can you efficiently collect data?  Do you have access to real-time production information?  How will you train employees in using the new system, and do you have reliable process enforcement to maximize the benefit of new technology?  You need more than just devices and work plans on PDF to operate efficiently, you need an information support system in place.  Consider what you currently have in place, and the role augmented reality will play in your shop floor processes sometime in the future.  Paperless solutions have already proven to reduce errors through process enforcement and continuous quality management.  They provide continuous monitoring and reporting of detailed shop floor work on visual dashboards, an important first step in sending information to mobile devices – a critical first step in providing augmented reality for your shop floor.

Preparing for the future

While many companies still struggle with paper-bound build books and excel spreadsheet work instructions, developers are already working on Augmented Reality Apps for Equipment Manufacturers.  These iPad and Android apps, which provide a foundation for augmented reality beyond Google glass, deliver enhanced training, walk through work instructions for assembly, and more.  The foundation for Augmented Reality is being installed in companies today so the future is coming sooner than you think.

It’s an exciting application of modern technology for manufacturing, but it will ask a lot of IT (sorry!).  Most shop floors aren’t ready to roll over to augmented reality operations.

Take a moment to evaluate your current operations, and consider what you can do to prepare for the future of manufacturing.

Build Vs. Buy: How to Get the Paperless Manufacturing System You Want

There are numerous options for companies researching MES and paperless manufacturing, we take a close look and evaluate two of those options.

By David Oeters, Corporate Communications at CIMx Software

It is much more difficult to build a car than buy one.  So, even though I’m annoyed by the side view mirror controls that dig into my wrist, and I bang my head when I lean into the car, I won’t re-engineer the work involved in current car designs to build my own (even though a robot vacuum is a brilliant idea).

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.

Design

The ability to design a paperless manufacturing system that exactly fits company needs and control the final product is often the primary reason a company will build rather than buy.  Every manufacturer is different, with different processes.  Some feel an off-the-shelf system can’t give them the functionality they need.

Whether you are building or buying an MES system, a successful project starts with careful planning. Image by www.colourbox.com

Whether you are building or buying an MES system, a successful project starts with careful planning. Image by http://www.colourbox.com

Understanding existing processes and needs is the first critical step before you begin designing the system.  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 you start writing code.  The largest problem in many cases is not anticipating the continuing flow of adjustments and enhancements needed to meet ever changing shop floor processes.

A purchased system will also require planning to determine requirements in order to properly evaluate the options on the market.  In all systems, items not included in the initial requirements may exponentially increase the cost of the project.  With systems built in-house, consider each requirement identified will add to the cost, while in purchased systems functionality can be bundled.  That said, if you have the stomach for cost (in time and money) to complete an in-house system, you will have much greater control over the final product.

MES or paperless manufacturing is never done.  Adequately supporting the changing work flow processes across the shop floor is a continual work-in-progress.  If you build it yourself, you need to build in the cost of a continuous dedicated development team in IT or, as in some companies, let the system drift into obsolescence.  Purchasing a solution flexible enough to “fit” your work flow process allows you to share the cost of development with other customers, and allows most customers the ability to modify the system to meet changing needs – ensuring a much less expensive system if you are willing to research systems that will fit your needs.

Tip: When purchasing a system from a vendor, 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.  Conversely, if building a system first create a simulated model of the system to show the users how it will function and the ease of use.

Implementation

Implementation involves taking the initial design and writing code for it, then installing it on the shop floor.

An average schedule for a system built internally begins with 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).  System 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. Depending on the platform, system specifications, the functionality and the size of the team working on the project, a finished MES or paperless manufacturing system can take 2 -3 years or more to complete

There are ways to lower cost in a system built in-house, such as removing functionality, minimizing testing, or utilizing other internal resources during the project, but there are costs associated with these measures, and could affect the long term viability of the system and the ROI.  Evaluate the return and cost for each decision before making choices you may regret.

System integration is another point to consider for both in-house and purchased systems.  Determine integration points early in planning to evaluate the added cost.  Manufacturers and businesses use a number of different software systems and databases.  Ensuring those systems work together smoothly is often overlooked in planning.

A much shorter implementation time in a purchased system is a clear advantage.  There are off-the-shelf systems on the market today that can be installed and running in as little as three weeks.  Configuration and system integration may add to the implementation time.  Also, beware of systems that require that your shop floor processes adapt to the software, which can significantly increase implementation, cost and lack of flexibility in the future.

Tip: Look for MES or paperless manufacturing systems which can reuse your existing work instructions and processes to reduce implementation time and training.

Reliability

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 and determining the ROI.  Every system requires maintenance and upkeep, especially in an industry such as manufacturing where changes in technology and processes are common.

Reliability is a key factor in determining the ROI of the system.  Image by www.colourbox.com

Reliability is a key factor in determining the ROI of the system. Image by http://www.colourbox.com

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.

Remember, a system that is no longer maintainable with current software standards is a Legacy system, slowly separating you from your valuable data.  Without a focus on maintenance, your shiny new MES will quickly become a legacy system or worse, an obsolete system that no longer supports production.  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.  In our experience, most companies intend to maintain the system, but as the true requirements become apparent, sacrifices are made to soften the costs and the solution slowly degrades until it’s no longer 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 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.  Are there fees for upgrades or patches?  How is the product maintained?  Answering these questions will help determine the TOC (Total Ownership Cost) for the system.

Tip: 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. A system with training to enable internal IT to support and enhance it themselves helps defray costs, while a system that restricts upgrade and support to only the provider will increase service costs.

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.


Make sure you consider the maintenance and upkeep costs of your MES system before purchasing or deciding to build one.  Image by www.colourbox.com

Make sure you consider the maintenance and upkeep costs of your MES system before purchasing or deciding to build one. Image by http://www.colourbox.com

As you evaluate paperless manufacturing options, keep in mind a company specializing in manufacturing software systems has years of expertise in both manufacturing and software development. They will be marketing the product for years, and will continue maintenance and testing, to ensure the system works.  The cost of upgrades, patches and improvements are shared by all users.

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.

Which is why my brilliant robot vacuum is still a dream, and there are still crumbs in the backseat of my car.