Evaluating Technology Support For The Internet of Things

Oct. 19, 2021
As manufacturers digitally transform their operations, finding the right technologies can be an overwhelming process. Donā€™t overlook your supplierā€™s ability to provide the right level of support when assessing technological capabilities.

Though the devices used in many Industrial Internet of Things (IIoT) projects may not be entirely new, the architectures used to facilitate IIoT levels of data aggregation, sharing, and analysis tend to be of a more recent vintage. So, even though you may be experienced in working with the types of controllers, sensors, and I/O systems used for IIoT initiatives, having access to quality support from your technology supplier(s) is critical to your projectā€™s success.

But how do you go about assessing the level of support you should expect from a technology supplier for an IIoT project?Ā 

First, itā€™s important to realize that the evaluation should go far beyond knowing who will pick up the phone when you callā€”though this is an important aspect. The supplierā€™s support team should also be able to help you figure out the value proposition of the IIoT project youā€™re looking to implement. They should be able to help guide you in understanding what you can realistically expect to get out of the project, in operational terms, as well as the return on investment (ROI).

The support you get from your technology supplier should also address the design work typical at the beginning of an IIoT project. Scott McWilliams, vice president of global operations consulting at Emerson Automation Solutions, says, ā€œIIoT opens up a new world and a new approach to how we design [automated production systems]. A vendor on a typical continuous-improvement project might only consider process design issues, but that typically just covers the inputs and outputs of one part of the process. Now, with IIoT, youā€™ve got to look at the inputs across an entire end-to-end processā€”because some critical inputs may originate in a business system outside of the plant. Youā€™ll need the vendor to sit down and help you think out the whole process from the very beginning with a focus on how to improve both process efficiency and efficacy.ā€

Swagelokā€™s experience
Swagelok, a manufacturer of components for gas and fluid systems, was looking for a way to automatically monitor, record, and escalate its assembly process. To do this, the company needed to make information from its Allen-Bradley PLCs more readily available so that its support team could have quicker visibility into its shop floor operations.Ā 

Doing this via an Industrial Internet of Things (IIoT) project seemed a natural fit for collecting, sharing, and analyzing the relevant data. Matt DeLuca, quality engineer for Swagelok, says the company selected Opto 22ā€™s groov EPIC (Edge Programmable Industrial Controller) for this project in no small part due to the quality of Opto 22ā€™s support.

ā€œWhen we first started, they gave us a very in-depth demo to explain the capabilities of the devices. Between then and now, we have done a handful of virtual training sessions and webinars that have helped us take our implementations to the next level,ā€ says DeLuca. ā€œAny time I have a question or issue, I have direct contacts with Opto 22, not an automated phone service. Their team has been more than willing to meet with our engineers and support teams to talk about additional features we would like to see or if a best practice could benefit us.ā€Ā 

Opto 22ā€™s support staff are all engineers with access to an array of test equipment on hand to duplicate customersā€™ exact issues.Ā 

IIoT support: What to look for
Customers beginning an IIoT project should look to their vendors not just for expertise in the products they sell, but for an understanding of the larger technology landscape, says Garrick Reichert, application engineer at Opto 22.Ā 

ā€œThey might need help setting up their IIoT solution to succeed,ā€ adds Reichert. ā€œThatā€™s why we engage in these conversations very early on. We get involved in designing the architecture of the system so that when it comes to any support needs they have later, we understand it from start to finish.ā€Ā 

Emersonā€™s McWilliams advises end users to question how they are supported in three stages of an IIoT project: pre-sale, go live, and post-implementation. ā€œItā€™s not enough that you can call someone when the green light doesn't go on,ā€ he says. Thatā€™s why pre-sales consultations are critical to ensuring you pick the right architecture and support to achieve the benefits you seek.

The customer needs to fully understand IIoT and the implications of the choices they make, says Travis Cox, co-director of sales engineering at Inductive Automation. ā€œThat means being transparent about things like data transportā€”do they own the data or not; and is it transported through an open mechanism where they can use a different cloud service. These aspects are really important.ā€Ā 

Cox adds that customers need to see that their technology supplier will be a committed partner. ā€œYou donā€™t want to call in and always get somebody different or have a person reading off a script. You need to be able to talk to someone who knows what theyā€™re talking about.ā€

The vetting process
Labor shortages driven by COVID-19, coupled with increasing retirements in the manufacturing workforce and the relative newness of IIoT architectures, means that finding knowledgeable support personnel can be difficult.Ā 

ā€œMany IoT platforms are relatively new to the market, so finding experienced IoT developers and solution architects to work on and maintain a system is a challenge,ā€ says Richard Mizuno, Asia-Pacific principal and regional director at Kalypso, a Rockwell Automation company.Ā 

When vetting potential suppliers, keep in mind your need for support will stretch beyond system design, implementation, and maintenance.Ā 

Keith Chambers, Avevaā€™s vice president of operations management software, notes that one of the most critical moments in an IIoT project is when you revisit it to determine if it is delivering on its promise. After finishing a proof-of-concept project is a perfect time to make key adjustments to ensure ROI, he says.

Itā€™s important to realize that ā€œyouā€™ll likely need to fine-tune the solution to deliver real value before you can justify any bigger investments to expand it in one plant or roll it out to others,ā€ says Chambers.

About the Author

Lauren Gibbons Paul | Contributing Editor

Lauren Gibbons Paul is a business and technology freelance writer. She writes frequently on automation and controls topics as well as technology trends for publications, including SAP Insights and CIO.

Sponsored Recommendations

Rock Quarry Implements Ignition to Improve Visibility, Safety & Decision-Making

George Reed, with the help of Factory Technologies, was looking to further automate the processes at its quarries and make Ignition an organization-wide standard.

Water Infrastructure Company Replaces Point-To-Point VPN With MQTT

Goodnight Midstream chose Ignition because it could fulfill several requirements: data mining and business intelligence work on the system backend; powerful Linux-based edge deployments...

The Purdue Model And Ignition

In the automation world, the Purdue Model (also known as the Purdue reference model, Purdue network model, ISA 95, or the Automation Pyramid) is a well-known architectural framework...

Creating A Digital Transformation Roadmap Using A Unified Namespace

Digital Transformation has become one of the most popular buzzwords in the automation industry, often used to describe any digital improvements to industrial technology. But what...