Making integration and continuous improvement easier
For companies working with manual and semi-automated assembly processes, continuous improvement is a daily topic.
Error-proofing, kaizan, poka-yoke, six-sigma, quality management or quality assurance are a way of life when humans are involved in part of the assembly process. Your teams work hard to catch as many of these defects as possible before the mistake makes it to the customer or consumer. ‘Quality is our Culture’ or ‘Continuous Improvement Conscious’ are regularly seen in factories as not-so-subtle reminders to all of us that while perfection is impossible, the pursuit of perfection in our product is something we should live daily.
For those in management or engineering who are responsible for the quality of production in a factory, this can be a heavy burden. Regardless of how flexible we are in manufacturing, the more things we can automate in our processes will help reduce our errors and improve the end quality of our products. When looking for flexible automation equipment, there are always some base decisions that must be made:
- Will it work with what we have now? We can’t rip out what we have working.
- How do we integrate the solution? We have limited time and resources.
- Can we also get it from a different supplier later if we have to replace it?
- Can we get it implemented ASAP? Like during a lunch break or scheduled shutdown?
Control architectures have significant impact on how a total error-proofing program is implemented. Having a system that works well initially is somewhat easy. The real test is how well it works as time goes on. In an error-proofing environment, easy expandability is a unique requirement. It is important to specify the appropriate control architecture during the initial design and build phase. This requires an architecture that easily integrates poka-yoke devices and traceability devices, such as RFID, into one seamless system that allows easy and low-ost expansion for the future. An expandable architecture built around the open standard of IO-Link seamlessly integrates poka-yoke devices and industrial identification devices. By keeping a few IO-Link ports open, future expansion is easy and cost effective. And the best part is the ability to implement the expandable architecture on popular control platforms from Allen-Bradley, Siemens, Mitsubishi and others.
These questions sometimes end up ruling out our first ideas and go-to solutions. However, IO-Link can easily meet these questions and challenges. IO-Link is a vendor-neutral, widely accepted technology that is regularly referenced as the USB for industrial automation. IO-Link is the next generation of continuous improvement with flexible control architectures, easy fast integration, diverse inspection options, visibility and traceability.
The objective of this article is not to make you an IO-Link expert. However, a few high-level points must be addressed to see the full benefits of the technology.
Use YOUR network and control architecture
You can’t rip out what you have now. IO-Link easily utilises your existing industrial network infrastructure. The benefits can be seen regardless of whether you currently use industrial networks like EtherNet/IP or no networks with centralised PLCs. Addressing of the devices is point-to-point with a master/slave relationship as seen in Figure 1. Connectivity is made with low-cost, unshielded, standard 4-wire sensor cables with up to 20 m between the master and slave.
Automate configuration and replacement
Smart field devices can require a higher degree of skill for technicians to be able to configure or replace. A typical error-proofing sensor usually has a measurement value or pre-programmed set points for tolerances. IO-Link devices are capable of being automatically configured on set-up or replacement, eliminating manual programming of the error-proofing device (Figure 2). If troubles occur, the sensor can report diagnostic issues like a dirty lens or more importantly could possibly report if the sensor has been bypassed or disconnected.
Choose what makes sense for your business
With a universal and open standard, products and technologies can be sourced from over 60 known vendors in the automation industry. This reduces your risk in selecting and implementing components because you keep control of which organisations you do business with. With over 24 IO-Link-enabled technologies from electrical drives to proximity sensors and everything in between, the technology needed to implement error-proofing is available today with IO-Link capabilities.
Define your continuous improvement implementation plan
Your CI Implementation Plan must be flexible
Quality errors can come in a troubling variety, so the technologies utilised to detect these trouble spots tend to be various and assorted as well. Being able to flexibly implement the proper technology is vital to success. Think about these types of questions when defining your implementation process for flexibility:
- How many variants do we need to inspect?
- What technologies do we use to contain and identify nonconforming parts?
- How do we ensure rework was done properly?
- What technologies do we typically use to inspect part assemblies?
- Can we accommodate new discrete and analog inputs?
Flexible implementation architectures allow for multiple technologies to be selected, modified and adapted to changing requirements in the factory. The plug-and-play nature of IO-Link means that devices can be used in one application, modified for another application or moved to a better inspection location. The flexibility to plug any device, including standard discrete sensors, into an IO-Link master gives you virtually unlimited possibilities for control of your error-proofing applications like colour detection, analog I/O and linear measurement with lasers, ultrasonic and position transducers (Figure 3).
Your CI Implementation Plan must be easy to use
If you want the team to live continuous improvement, it must be clear, simple and easy to implement. The harder we make it to do the right thing, the less likely we are to implement change. So selecting an implementation plan that can be executed easily is a must.
- What does it take to set up a new inspection in production?
- How do we define the mistake or quality issue?
- How do we ensure that the issue does not appear again?
- How do we make sure the technology is implemented properly to ensure detection?
With IO-Link the ability to parameterise smart sensors and devices makes implementation and changes to inspections very easy. Some intelligent lasers and sensors can have more than a dozen programmable settings that must be accessed via a small, sometimes hard-to-see, push-button interface. The engineer or technician has to spend a significant amount of time understanding how the product is configured properly. However, with IO-Link there are a variety of ways to configure a device and parameters can be stored for future or repeated use across similar installations. In addition, a large combination of parameters can be stored, uploaded and downloaded for use in the most flexible of production capabilities (Figure 3).
In the case of a device failing, a failure in quality could occur again due to a mistake in configuration of the replacement device. With IO-Link the ability to store parameters in the master and automatically configure the device means that once the configurations are determined, the quality inspection can be maintained.
Your CI Implementation Plan must be fast to integrate
Selecting a technology that integrates into your existing control system is a major requirement when trying to implement improvements on the fly. Quality errors and deviations must be identified, contained and rectified with minimal effect on delivery to the end customer or consumer.
When integrating smart sensors and industrial network-ready technologies, the learning curve to implementation can be steep. Days or weeks of bench testing, software programming and trials can add costly delay to detection implementation. Control-ready devices that provide software function blocks or Add-On Instructions can dramatically reduce the complexity and time to integrate into the PLC.
While hardware selection is important to the success of a project, if the hardware is not easily integrated into the engineering software, any benefits gained could be lost. However, Distributed Modular I/O is easily integrated into typical engineering software with an easy three-step process.
In a typical measurement application the inspection device provides an analog output. The engineer then has to do multiple calculations based on resolutions and scaling to determine the actual engineering unit of measure, such as psi or millimetres. Many IO-Link devices provide the pre-converted actual engineering units of the measurement they are providing. For example, in Figure 4, a laser sensor would provide the position value in millimetres in the process data to allow for easy integration. This eliminates any calculations required, reduces set-up mistakes and gets the inspection operational faster.
Real-world implementation in action
By selecting IO-Link as the controls architecture in their facility, a Michigan-based manufacturer is able to reliably implement on-the-fly improvements to their production equipment. Using Allen Bradley CompactLogix PLCs and the industrial Ethernet network, EtherNet/IP, they implemented a wide variety of technologies into their assembly processes; both before and after the initial machine build. Applications in use today include: discrete poka-yoke sensors looking to ensure components were in the proper place; analog measurements inspecting component orientation; and smart sensors with diagnostics and automatic configuration.
Once they decided to have IO-Link as the architecture of choice, it was very easy for them to continuously make improvements. A process improvement engineer at this facility was tasked recently to determine the presence and orientation of a nut fed into a pedestal welder. His task was to make sure the nut was there as well as to ensure that the nut was not upside down. He stated, “With IO-Link, I was able to install the linear position transducer mechanically in the application, go into the code and have the entire project integrated in 20 minutes. I had planned a full day for implementing this application, but it was that easy.”
So by selecting IO-Link as their continuous improvement implementation plan they were able to integrate error-proofing solutions flexibly, easily and fast.
The truth behind the hype.
For most OT professionals long responsible for edge-based computing systems in their...
The idea of network convergence sets the stage for interactions between IT and OT network...