The Varied Power of the Industrial IoT

While much of the IoT buzz has been going to consumer and medical products, the industrial IoT sector shows faster growth.

With Intel projecting IoT products growing to 2000 billion devices by 2020 – just three years from now – the talk of IoT-everything is running high. We’re hearing about connected watches and a multitude of medical devices. But the quickest way to a clear return-on-investment in IoT, according to analyst groups such as ARC Advisory, is in industrial settings.

Many of the technologies that make up Industrial IoT are actually well-established in their own right. The diagram below shows six layers that make up what most people consider to be the Industrial IoT.

 

Cambashi, IoT, Industrial Internet of Things, sensors, control systems, automation, networks

 

Cambashi recently completed a research project into the industrial application of the IoT (Internet of Things). The aim was to establish the market’s structure and direction based on interviews with many of the major players combined with desk research.

Here are the layers of IoT applications with a look at what's emerging in eash area:

This can cover anything from vehicles to component parts. Most publicity has so far been around personal IoT devices such as fitness monitors and home appliance controls. But recent surveys show that the industrial applications of IoT are now growing faster.

Electronics, software, sensors and actuators

These days, every consumer and industrial item with a battery or an on/off switch almost certainly includes software-controlled electronics (this is what makes it a smart product).  These technologies have been around for decades. A recent trend is that component providers who offer all the digital metadata that describes their components may well have an advantage at this stage, because the metadata can feed into systems engineering and other tools, thus helping the project team structure, simulate, then plan the development project. Many teams responsible for control software are used to developing for the closed environment of a standalone machine. Making use of new network connectivity can be quite a disruptive but positive change for these teams.

Connectivity

This is the means by which devices communicate with the back-end systems and includes a range of methods from proprietary to standards-based. Of course, it has been possible to connect devices for some time, but historically this has used proprietary, custom-built systems. Today, cloud computing provides a more convenient and cost-effective way to connect to other systems.

Two other areas where innovation is improving connectivity are:

  • Edge computing – i.e. servers located close to the smart products or factories that act as a ‘collection point’ for the data. Because vast amounts of data can be collected from the billions of devices in the field, it makes sense to do as much data processing and selection as possible, near to the devices or sensors. This means that less data have to be transmitted to the cloud and less processing will later be required.
  • Evolving connectivity standards: the Industrial Internet of Things Connectivity Framework (IIC:PUB:G5:V1.0:PB:20170228) from the IIC (Industrial Internet Consortium) lists ten Core Standard Criteria ranging from Providing syntactic interoperability to Having readily-available SDKs. Against these, it rates four Connectivity Standards – DDS; Web Services; OPC-UA and oneM2M. Each of these standards is evolving to provide specific advantages in IIoT implementation. For example, DDS is an emerging, new standard; its main distinguishing feature is that, unlike the other three, DDS has no concept of messages – the software application talks to the databus thus providing a more efficient solution when the data has many destinations.

Product Access and Data Routing

Almost every connected product has more than one organization interested in reading its data, and sending it commands. The Product Access and Data Routing layer controls and manages who has access to what. For example, the manufacturer of a machine, and a third-party service company may offer machine monitoring, optimization and predictive maintenance. What data will they see? What settings can they change? If something is changed, who is responsible for documenting the change and matching it to other records of use of the machine (for example, batches of food production)?

Can the machine owner, or a local operator, or an on-site service technician control this access? The company that supplied the electric motors inside the machine may offer an automated motor monitoring service. Who will authorize their computer systems to gather data from the motors? These data flows form a complex network, but it is worth noting that PLM (Product Lifecycle Management) systems have for many years handled access control to manage these kinds of data flows to and from design data. Repurposing and scaling this to cover all operational machines may not be straightforward, but PLM contains relevant experience of the necessary business logic and procedures.

Product-Specific Software Applications

This is the heart of many new capabilities of smart, connected products. For example, a new capability to observe and analyze the status of a set of connected devices, and make a plan to operate or service them, will be provided by software in this layer. This layer also has the vital role of making appropriate connections and integration with other enterprise applications. For example, an update to embedded software will only be sent to devices being used by customers with a valid subscription – and it is the CRM (customer relationship management) or perhaps sales order processing system that has this information.

Other Enterprise Applications

MRO (Maintenance, Repair, Operations) may well be the focus of a smart connected product initiative, perhaps a switch from fixing breakdowns to usage-based or predictive maintenance. But many MRO issues stay the same: fault handling, whether real or predicted; configuration; part or software availability for fix; schedule technician or online access to product; fix problem, report the fix; share the know-how; customer acceptance.

 

 

So, the emphasis on the use of tools is probably on tracking orders and configurations, scheduling technicians and parts for maintenance and fault fixing. Good integration of these applications enables ‘servitization’ – enabling companies to supplement their products with additional services.

To summarize, smart products, such as diggers (Komatsu, etc.) and industrial machines (Siemens, GE, etc.) have been around for 20 years or more. But these were only used on high-value, long-life equipment.

What is leading to the well-publicized multi-trillion-dollar market with billions of sensors on-line? This is answered succinctly by Rhonda Dirvin, director IoT vertical markets for ARM (now part of Softbank): “The first driver for the spread of IIoT was the proliferation of mobile phones, which drove down the cost of sensors – cameras, GPS, accelerometers.

“This drove down the cost of acquiring data. At the same time, Cloud computing emerged, which provided a platform where this data could be stored and analyzed relatively cheaply. Altogether, this provides the basic framework for IoT. Other technologies such as Big Data, AI (artificial intelligence) and Machine Learning are now coming into play to help make sense of this data, taking it to a whole new level.”

There is little doubt that the Industrial IoT will continue to be disruptive – changing conventional business and software implementation models – and that the main elements, shown in the six-layer model above, are in place to support this.

But there is still plenty of room for innovation in the way the industrial IoT is applied, the way smart-connected devices are developed and manufactured, and the capabilities of the tools and components used across all six layers of IOT.

This innovation will increasingly be in response to business rather than technical needs or opportunities as the supporting technology becomes more mature and affordable.

 

The Embedded Systems Conference (ESC) is back in Minnesota and it’s bigger than ever. Over two days, Nov. 8-9, 2017, receive in-depth education geared to drive a year’s worth of work. Uncover software design innovation, hardware breakthroughs, fresh IoT trends, product demos, and more that will change how you spend time and money on your next project. Click here to register -- Use the code " SAVE15ESCMINN" to save 15% on conference passes.

 

Alan Griffith is principal consultant for Cambashi. He studies how engineering and manufacturing organizations use technical software applications to meet their business needs and assists software companies that develop and market those applications with their market planning. Griffith has an engineering degree from Cambridge University and he’s qualified as a Chartered Engineer and PRINCE2 project manager.

Image courtesy of Cambashi

Comments (0)

Please log in or register to post comments.
By submitting this form, you accept the Mollom privacy policy.
  • Oldest First
  • Newest First
Loading Comments...