Building Smart Factories Using Legacy Equipment

July 26, 2018

Retrofitting IoT technology into existing factories is a major challenge. Just getting equipment connected is a problem; Cisco estimates that 92% of the 64 million manufacturing machines are unconnected to any network, and simple network connectivity isn’t enough.

Manufacturers who want to deploy a smart factory solution face a range of problems. There's a wide variety of controllers in use in the field, each with its own protocols, and no single standard common to them all.

Data capture is also an issue. PC-based legacy equipment can often create log files, but said files may not be captured in real time, they may not contain all of the information a modern smart factory deployment requires, and the files themselves may be written in proprietary formats for which source code is not available.

ADLINK recently partnered with Intel to deploy a smart factory platform designed to enable several specific capabilities and outcomes. Among them:

  • Efficient data capture from existing legacy elements and new hardware infrastructure, followed by prompt data analysis from cloud platforms to better inform production decisions
  • Full “smart” integration between the legacy elements themselves, thereby ensuring that the entire factory supports a common standard.
  • Secure, stable connections between elements on the factory floor, to keep the entire factory in sync.
  • A customized IoT platform providing edge, cloud, workshop, and ERP services, supporting optimization of large-scale production

As part of its smart factory design, Intel installed Remote Terminal and Remote Control Units (RT/RCU). These elements provide remote control and operational data retrieval from legacy, non-connected equipment. This information is then combined with data from IoT-enabled elements and transmitted to backend platforms for cloud processing. This system allows the client to monitor operations in real time across the entire factory.

For communication, Intel recommends DDS (Data Distribution Service), which uses a publish-subscribe pattern for distributing periodic system updates. In this architecture, devices “publish” data specifically to other IIOT devices that have “subscribed” to receive it (Figure 1).

Figure 1. Data Distribution Service (DDS) employs a flat architecture.

The advantage to DDS is that it simplifies networking and limits the impact of any single failure. Because communication flows from publisher to subscriber rather through any static, fixed point, failure in any given sensor or device won’t prevent other devices from properly reporting their own states.

Once connected in this manner, real-time pub/sub M2M communication can minimize downtime and increase efficiency by enabling predictive maintenance and failure analysis. Flat, decentralized, peer-to-peer data sharing eliminates latency from single-point failure.

While buying all-new, modernized manufacturing equipment might be the best way to go, the vast majority of industrial facilities can’t afford to do so in one fell swoop. Luckily, they don’t have to – there are significant advantages to even an incremental approach.

Previous Article
Edge-ifying Machine Learning for Industrial IoT
Edge-ifying Machine Learning for Industrial IoT

Machine learning is transforming the industrial sector. But to make the most of this new technology, you ne...

Next Article
What’s Old Is New Again—CNC Systems Join Industry 4.0
What’s Old Is New Again—CNC Systems Join Industry 4.0

Now with data collection, analytics, and integrated management, all your CNC machines—new and old—can be in...


First Name
Last Name
Your Company
Phone Number
Subscribe To Intel Updates
Subscribe To Alliance Partner Updates
By submitting a form on this site, you are confirming you are an adult 18 years or older and you agree to Intel and Intel® IoT Solutions Alliance members contacting you with marketing-related emails or by telephone. You may unsubscribe at any time. Intel's web sites and communications are subject to our Privacy Notice and Terms of Use.
I would like to be contacted by: - optional
Your contact request is submitted.
Error - something went wrong!