{"id":6036,"date":"2024-05-13T12:54:40","date_gmt":"2024-05-13T12:54:40","guid":{"rendered":"https:\/\/www.novotek.com\/co-uk\/?p=6036"},"modified":"2025-11-28T10:28:36","modified_gmt":"2025-11-28T10:28:36","slug":"avoiding-the-connectivity-potholes-on-the-industry-4-0-motorway","status":"publish","type":"post","link":"https:\/\/www.novotek.com\/co-uk\/news\/avoiding-the-connectivity-potholes-on-the-industry-4-0-motorway\/","title":{"rendered":"Avoiding connectivity potholes"},"content":{"rendered":"
\n

Nowadays, there\u2019s a lot of talk about cloud connectivity, \u201cedge-based\u201d data processing, machine learning, and the like. The rush to focus on outcomes and benefits leads to some assumptions that deserve attention. Most advocates for Industry 4.0 ideas depict a scenario where OPC-UA and\/or MQTT generate all source data.<\/p>\n<\/div>\n\n

\n

Read more:<\/strong> What is OPC and OPC UA?<\/a><\/p>\n<\/div>\n\n

\n

In reality, most industrial sites have a mix of integrations that have evolved in place. Often reflecting point-to-point integrations needed to accommodate specialty devices and protocols. How you resolve that either create flexibility in the way data is made available for many purposes \u2013 or it doesn\u2019t.<\/p>\n<\/div>\n\n

\n
\"Avoid<\/figure>\n<\/div>\n\n
\n
<\/div>\n<\/div>\n\n
\n

Connectivity strategy – Industry 4.0 <\/h2>\n<\/div>\n\n
\n

How can you be sure you\u2019ll get your foundation right? Working your way through the following questions should help you see why the right connectivity strategy can really matter.<\/p>\n<\/div>\n\n

\n
<\/div>\n<\/div>\n\n
\n
\n
\n
\"Connectivity<\/figure>\n<\/div><\/div><\/div>\n<\/div>\n\n
\n
\n

Question 1<\/strong><\/p>\n<\/div>\n\n

\n

Do I have a lot of direct connections via multiple legacy protocols between controls and other systems?<\/strong> <\/p>\n<\/div>\n\n

\n

This is still incredibly common<\/em>. It often means that other old applications like SCADA have a mix of very old 3rd party direct drivers.<\/em> It may also be because of custom interpreters of legacy device data. And those old SCADAs may not be very connectible either!<\/em><\/p>\n<\/div><\/div>\n<\/div><\/div>\n<\/div>\n\n

\n
\n
\n
\"Connectivity<\/figure>\n<\/div><\/div>\n<\/div>\n\n
\n
\n

Question 2<\/strong><\/p>\n<\/div>\n\n

\n

Could a more modern connectivity toolkit open up other options for using\/reusing data?<\/strong><\/p>\n<\/div>\n\n

\n

If your history has been defined by single-purpose connections (1 for SCADA, 1 for logging, 1 for connecting different control systems), you may have an opportunity to reduce complexity in your existing systems at the same time as freeing data to flow for those Industry 4.0 efforts.<\/em><\/p>\n<\/div><\/div>\n<\/div><\/div>\n<\/div>\n\n

\n
\n
\n
\"Connectivity<\/figure>\n<\/div><\/div>\n<\/div>\n\n
\n
\n

Question 3<\/strong><\/p>\n<\/div>\n\n

\n

Could I make the modernization of control systems easier if I de-couple legacy kit and the comms tools used around it?<\/strong> <\/p>\n<\/div>\n\n

\n

Something as simple as wanting to use a modern SCADA is easier if the sensors and controls feed a connectivity layer that provides modern protocols for modern software to talk to. Thinking of connectivity as its own requirement can open up staged modernization of the automation around your processes with less cost and risk.<\/em><\/p>\n<\/div><\/div>\n<\/div><\/div>\n<\/div>\n\n

\n
<\/div>\n<\/div>\n\n
\n
\n
\n

Read these articles for more insights about connectivity and Industry 4.0:<\/strong><\/p>\n<\/div>\n\n

\n
<\/div>\n<\/div>\n\n
\n