Connecting your machines with IIoT can open the door to advanced data analytics and actionable metrics, paving the way for process improvements and business objectives.
Most modern machines come equipped with Ethernet connectivity and can communicate over protocols like MT Connect or OPC. They output a suite of data, such as feed rate, status, number of parts produced, and many more. Legacy machines don’t have the ability to capture or communicate this data, but you can still bring them online using sensors or data feedback devices and an IoT gateway.
Here are 5 steps to bringing your legacy systems online with IIoT:
1. Define goals for your IIoT project.
The most important part of any IIoT project is defining clear, measurable goals. These goals should be driven by a solid business case.
Your goals should be measurable by KPIs and pre-defined measures of success. Without a foundation in key business metrics, the new technologies a company implements will fail to live up to their promise.
2. Determine the questions your data should answer.
You should know what questions you want your data to answer before you set out to collect it. Determining the answer to this question should involve a conversation with your production staff and engineers.
Analyze, categorize, and summarize information on areas that can be improved. Chances are you already have an idea of areas for improvement–now you can use data to pinpoint it and make informed decisions.
2. Bring facility infrastructure up to date if necessary.
You’ll also need to consider any changes you need to make to your facility or network infrastructure. For example, if you’re working with machines without any connectivity, chances are your facility isn’t set up for Ethernet connectivity. In this case, you’ll need to install Ethernet drops and run cables, which will require approval from facilities.
Keep in mind that any changes that need to be made will take extra time to implement. It’s also crucial to gain the cooperation of those in your company with IT expertise, as you’ll likely need their approval to make any changes.
3. Map out a plan for collecting data using sensors
You will need to compile a list of all the machines in your facility. They should go into 3 categories:
- Modern machines satisfy two requirements: 1) they can be connected to your network; and 2) they speak a protocol your machine monitoring software can read (Tulip can read any protocol).
- Analog machines do not have network connectivity and do not speak any protocol. These machines will require analog monitoring. These machines will be monitored using external or non-invasive sensors, which will be mapped to machine state.
- Anything in between: machines in the middle may be able to fulfill both requirements with a software upgrade or a physical network expansion card. This will require further research and consultation with whoever is in charge of your machines as well as the machine’s manufacturer.
The following steps primarily concern analog machines.
How can I collect the data I need to meet my goals? What’s the most reliable way to know what I’m trying to identify?
A good example is identifying whether a machine is running. Your instinct might be to track whether or not the conveyor belt is turning–but it’s possible that the conveyor belt is turning without any parts on it. A better indicator, then, of whether the machine is running is whether there are parts coming off the line.
So, a simple and reliable solution to determining whether the machine is running would be to install a break beam sensor where the parts come off the line. As long as the break beam sensor detects motion from the part leaving the conveyor belt, you can map the state of the machine as “running.”
5. Integrate new sensors.
Once your sensors are in place, you can map sensor outputs to machine states. This may seem like a daunting task, but a no-code software platform like Tulip makes it easy to integrate machine data into powerful apps and analytics.
You can now use this information to monitor metrics such as OEE (overall equipment efficiency) and OPE (overall process efficiency), pinpoint issues and areas for improvement, and inform your processes directly.