Industrial Internet of

Things (IIoT)
 Difference between IoT
and IIoT

▪ IIoT refers to the application of IoT to a broader set of industrial

sectors other than manufacturing, such as energy, healthcare,
transportation, smart cities, retail, and smart infrastructure.

▪ IIoT is also known as Industry 4.0 when applied to manufacturing

industry and it is a subset of the fourth industrial revolution.
Industry 4.0
▪ Industry 4.0: Current trend of automation and data exchange in manufacturing systems leading
to SMART FACTORIES.
Industry 4.0
AUTOMATION PYRAMID:
Classical Architecture

6
AUTOMATION PYRAMID: Classical Architecture
 Industrial IoT : Considerations

Automation
Pyramid

• Decentralized Intelligence
• Rapid Connectivity
• Open standards and systems
• Real time context integration
• Autonomous behavior
 Latency requirements for Control
➢
 Why CLOUD ? …. Time Varying Resource Requirement

Powerful
Standalone Server

Datacenter

INTERNET Load
Balancing

Clients Distributed Servers

AUTOMATION PYRAMID CLOUDIFICATION : STEP 1

Controllers and Field Devices on Independent Clouds

AUTOMATION PYRAMID CLOUDIFICATION : STEP 2

Controllers and Field Devices on Connected Clouds

 AUTOMATION PYRAMID CLOUDIFICATION : STEP 3

Controllers , Field Devices and higher AP levels on a Common Cloud

 AUTOMATION PYRAMID CLOUDIFICATION : STEP 5

Upper Automation Pyramid levels partly replaced by Cloud Services

 AUTOMATION PYRAMID CLOUDIFICATION : STEP 5

Upper Automation Pyramid levels Completely replaced by Cloud Services

AUTOMATION PYRAMID CLOUDIFICATION : STEP 6

Automation Pyramid replaced by Automation Cloud

 Industrial
Automation
as a
Cloud Service

17
 What is Industrial IoT?

▪ The industrial internet of things (IIoT) refers to interconnected

sensors, instruments, and other devices networked together with
computers, industrial applications, including manufacturing and
energy management.

▪ This connectivity allows for data collection, exchange, and

analysis, potentially facilitating improvements in productivity and
efficiency as well as other economic benefits.

▪ The IIoT is an evolution of a distributed control system (DCS) that

allows for a higher degree of automation by using cloud
computing to refine and optimize the process controls.
Needs
 Address Core Industry Problems

Note: OpEx: An operating expense, operating expenditure, operational expense,

operational expenditure or opex is an ongoing cost for running a product, business, or
system. Its counterpart, a capital expenditure (capex), is the cost of developing or providing
non-consumable parts for the product or system.
Regulatory compliance is an organization's adherence to laws, regulations, guidelines and
specifications relevant to its business processes. Violations of regulatory compliance
regulations often result in legal punishment including federal fines.
 How IIoT works?

Note: OPC Unified Architecture (OPC UA) is a machine to machine communication protocol for
industrial automation developed by the OPC Foundation. Distinguishing characteristics are: Focus
on communicating with industrial equipment and systems for data collection and control.
 Vendor Specific IIoT framework

Note: Data is aggregated from the vendor “A” specific equipment and from the DCS, PLC and other
process data (this is useful for analytics, since this equipment is coupled with other equipment also.
Datalake is the database storage of aggregates data.
Multivendor-specific IIOT Framework
Back to Basics!
 Connectivity in Automation

Devices in the automation world also need to talk

• To gather information from sensors

• And send control signal to actuators

Communication standards are essential

• Hardware & software defined protocols

 Connectivity in Automation

There are dozens of industrial networking standards!

• If you’re starting an application, how do you choose?

• If you are planning to build products, which networks

will bring the most success?
 Connectivity in Automation:
Serial vs Ethernet

Most popular industrial networks started out on serial bus

• 1970’s and 1980’s
• RS-485 or CAN were available at the time to serve as the physical
layer: the wires, connectors etc..

Rapid growth of Ethernet in office nets

• Drove Ethernet costs down, speed up
• Serial bits rates: 9.6k to 12Mbits/sec
• Ethernet: 100 – 1000 Mbits/sec
• 32 bit IP addressing allows practically unlimited number of nodes
• Most fieldbus standards were adapted to Ethernet in early 2000’s
 Connectivity in Automation:
Serial vs Ethernet

Many popular serial protocols have been updated to run on Ethernet:

• Modbus/RTU → Modbus/TCP
• DeviceNet → EtherNet/IP
• CANopen → EtherCAT COE
• Profibus → Profinet
• CC-Link → CC-Link IE
 Connectivity in Automation:
Serial vs Ethernet

Why migrate to Ethernet?

• More speed
• More nodes
• Mixed protocols on same net
 Modbus RTU

Introduced by Modicon, a PLC maker, in 1979:

• First popular industrial network
• Reliable but not fast: 9.6k to 115k bits/sec
• Tames RS-485 which is otherwise a less than reliable medium
• Good communication standard but not specialized for
applications
• Standard organization: The Modbus Organization
 Modbus RTU

RS-232 is point to point so only one slave device can

connect
 RS-485 allows multiple devices to share the network:

Modbus RTU • All devices share a parallel, two wire bidirectional bus
• Up to 247 devices, depending on manufacturer
• Most RS-485 transceivers limit the number of nodes to 32
 RS-485 can also be implemented as a four wire network:

• Modbus is inherently half duplex so using four wires does

Modbus RTU not increase network bandwidth.
• Modbus masters always wait for a response (or a time out)
before sending another message.
 Modbus RTU: Physical Layer

• Simple and low cost

• Most DSP and MCU have built-in UARTs, making
Modbus designs incredibly simple and affordable
 Modbus TCP

• Introduced in 1999 by Schneider Electric

• Runs on standard Ethernet TCP/IP
• more speed (1000x), more devices on the wire
• Can share the network with other protocols and standard
TCP/IP traffic
• IPv4 allows nearly unlimited addressing (232 devices)
• A typical subnet would be limited to 28 or 216 devices
 CANopen

• Introduced in 1995
• Standards body: CAN in Automation (CiA)
• Up to 127 devices: All devices share a parallel, two wire
bidirectional bus

“Standards do not guarantee interoperability”

 CANopen: Physical Layer

• Simple and low cost

• Most DSP and MCU have built-in CANopen controllers,
making CANopen hardware designs inexpensive
 DeviceNet

Developed by Allen-Bradley (now Rockwell):

• Introduced in 1994
• Uses CIP (Common Industrial Protocol) protocol on CAN
physical and data link layers
• Low cost to implement
• Many DSP’s and MCU’s have built-in CAN controllers
• CAN transceivers are widely available and inexpensive
• Up to 127 devices: All devices share a parallel, two wire
bidirectional bus
 DeviceNet
• Simple and low cost
• Many DSP and MCU have built-in CAN controllers,
making DeviceNet hardware designs inexpensive
 EtherNet/IP
• Developed by Allen-Bradley (now Rockwell)
• Introduced in 2001
• Standards organization: ODVA
• Runs on standard Ethernet
• Uses Common Industrial Protocol (CIP)
• Uses TCP transport for explicit messages
• UDP for fast, cyclical implicit messaging
• IPv4 allows nearly unlimited addressing (232 devices)
• A typical subnet would be limited to 28 or 216 devices
EtherNet/IP
 EtherNet/IP

• MAC/PHY can be built into CPU – very common in ARM

processors –simple, low cost
• Magjack includes transformers and RJ-45 jack
• For harsh environments, M12 connectors can be used with
separate magnetics
 Profibus DP
• Devised in Germany in 1987
• Primary controller: Siemens
• Popular in Europe
• Enhanced RS-485 physical layer
• Speeds to 12 Mbits
• Requires ASIC for data link layer
ASIC: “An application-specific integrated circuit is an integrated circuit (IC) chip
customized for a particular use, rather than intended for general-purpose use”
 Profibus DP

• Enhanced RS-485 allows multiple devices to share the

network at high speeds
• All devices share a parallel, two wire bidirectional bus
• Up to 32 devices per segment
 Profibus DP

Network model

Physical layer
 Profibus IO

Network model

Physical layer
Summary of Protocols
THANK YOU