IoT - Market, Value Chain,

Technology, Solution
December, 2020
Overview of Talk
• IoT Market View, Motivation, Value Chain
• IoT Edge Technology, Networks, Interfaces, Gateway
• IoT Platform Overview
• IoT Use cases/Case Studies – Smart Energy Management, OEE, , Heavy Vehicle
Monitoring, SWM, OBD

2
Why IoT?
▪ Exponential growth forecast for IoT
Endpoints
▪ 4.8 Billion end points in 2019

Source: Gartner 2019

3
IoT Market
• Key Potential Verticals (IoT endpoints)
❯ Utilities – Smart metering (residential and
commercial)
❯ Physical security – intruder detection, indoor
surveillance
❯ Connected cars
❯ Building automation (connected lights)
❯ Geography – North America, Grater China,
Western Europe

Source: Gartner 2019

4
IoT Hype Cycle IoT, 2020

5
5
Why IoT Now?
• Three main things that have changed in recent years are accelerating the number
and value of connected things
• The cost of connectivity and embedded technology is no longer a barrier to adoption
• Evolution to support ever-broadening range of use cases.
• The provision of information via sensors and the resulting analytical opportunities and
context-setting are transforming how we look at the world and at ourselves.

• Benefits
• Improving customer experience
• Increase cost efficiency
• Create new revenue
• Improve product performance

6
6
IoT Value Chain
Apps IoT Apps and Use Cases

Application
Development Modelling, Orchestration,
Layers testing and deployment

Service Enablement, Ingestion, Database and Analytics

IoT Platforms

Device Management, Device onboarding, monitoring etc.

Monitoring

Network connectivity, Service Different protocols and data network

Providers

IoT Devices, Sensors, Gateways Gateways and sensors - Intel,

ARM, Dell, Advantech

7
7
Fragmented IoT Market, Many Vendors

Source: Gartner

8
Gateway
• Key entity for connectivity back to the cloud for transferring data
• Support for various interfaces to collect data from different sensors/machines. Such
as Serial port, Ethernet Port.
• RS485 for Modbus
• Ethernet for TCP/IP
• Robust and Industrial grade – sustain high temperature, vibrations, humidity – IP67
ratings, DIN Rail
• Firmware and General purpose OS based software

9
OPC-UA
Analog
Temperature
Sensor

PLC Ethernet

Digital I/O
Ethernet/ WiFi /GSM
OPC UA IoT Cloud
Server Platform
PLC
Air Flow Serial IIoT Gateway
Meter
RSRs-485/Other
REST/HTTP
Industrial interfaces
Multi-
Function
Meter Other Systems
Induction
(e.g.
Motor +
Drive
ERP/CRM…) Mobile Web
Application Application

10
 Source: https://www.postscapes.com/iot-gateways/
11
Network Connectivity
• MQTT, AMQP, XMPP
• HTTP, HTTPS
• CoAP

• RPL, 6LoWPAN

• LPWAN – LoRA, SigFox, NB-IoT

• Others – WiFi, Ethernet, ZigBee, BTLE
etc

12 Source: IBM Blog

IoT Networking Considerations
Protocols Typical Use Cases Others
• Range Range
• Bandwidth Bluetooth, 20m- Devices that stay in close proximity Personal Area Networks
WiFi 50m of each other, like between a (PAN) protocols
• Power usage smartphone and a headset, heart
rate monitor, bicycle speedometer.
• Interoperability
LoRaWAN 5-10km City level, sending data at low LoRaWAN is a low speed,
• Security frequency e.g,. Moisture sensors in but long range and low
farm power communication
protocol
Sigfox 20km Remote electricity or water meter Sigfox is a proprietary
reading. Mostly uses where you do network and protocol.
not need to have downlink
messages to the device.
NB-IoT 10- Mostly for sensor readings, tracking NB-IoT runs in the mobile
15km and fleet management. In the future telephone radio
the coverage should be comparable spectrum, and
Source: polymorph to GSM. piggybacks on old,
unused GSM channels, or
free space between LTE
13 channels.
MQTT – Application Layer Protocol
• A lightweight publish/subscribe messaging protocol
• Publish/Subscribe
• Hierarchical Topics e.g., sensors/COMPUTER_NAME/temperature/HARDDRIVE_NAME
• QoS

14
14
Sample MQTT Message Payload

• Device – Home Gateway 1

• Sensors
• Thermostat Temp
• Lights
• TV

15
Device Management
• Key Functionalities
• Provisioning and authentication
• Configuration and control
• Monitoring and diagnostics
• Firmware and Software updates and maintenance

• Standards
• OMA-DM – OMA - Towards mobile devices
• LWM2M – OMA – Lightweight M2M
• TR-069 – Broadband forum

16
IoT Platform and Service
Creation Layer
Azure Typical IoT Solution Architecture
Stream Processing AKS Nodes
Azure IoT Hub Messages KeyCloak/Active
Directory
Messages Authentication

AKS Nodes Load Balancer

Edge Controller
AKS Nodes
Alert Processor Azure Functions
Microservices API & Web
Rule Engine Microservices
Sensor Data Sensor Data
Users
Azure Load
Sensor Data Azure Datastore Balancer

AKS Nodes SQL DB AKS Nodes Web or Mobile

Applications
Business Logic Cosmos DB Data Analytics
Microservices (ML, AI)
Elastic Search

Power Bi and Data Azure Azure Active

Azure Key Vault Azure Monitor Azure DevOps Azure DNS Service
Analytics Tools Email Services Directory

Other Azure Services In Use

18
AWS IoT:: Typical Cloud IoT PaaS

Source: AWS IoT

19
Data Model
• Critical part of any IoT Platform
• Defines how the IoT Platform can handle various use cases of IoT
• Provides a way to specify
• Sensor Units
• Sensor Types – sensors of specific units and range.
• Device Types – attached sensors, attributes.
• Devices – instances of device types
• Other entities.

20
Orchestration Layer or Rule Engine
• Features
• Low Code Platform for rapid application creation
• Define actions on the data being received

• Examples
• Node-Red

21
Security

Security in Transit Security at Rest Identity & Access Management

- Role Based Access
 MQTT over TLS 1.2  Firewall implementation
 HTTPS
 Device Certificate based
Identity and Authentication

22
Operations Excellence

Cloud Deployment On-premise Monitoring

Monitoring  Device Connectivity Loss
 Azure Monitor/AWS Detection and Alarms
Cloudwatch Alarms  Data Logging During Outage
and Metrics
 Dashboards

23
Scalability and Availability

Compute Scalability Data Scalability

for Microservices
 SQL DB Managed
 Vertical and Horizontal Service of Azure
 Auto Scaling Mechanism  Cosmos DB NoSQL Managed
 Load Balancers Service of Azure
 Upgrade the deployment for
enhanced data availability
through replication

24
Opensource IoT Platforms

▪ Thingsboard.io

▪ Thinger.io

▪ wso2

25
 Use Cases

26
Use Cases
• Industrial Internet of Things (IIoT)
• Smart Energy Management
• Overall Equipment Effectiveness
• Predictive Maintenance
• Smart Cities
• Solid Waste Management
• Smart Community
• Utilities
• Electricity Meter Reading
• Heavy Equipment Monitoring
• Asset Monitoring
• Fleet Management
• Critical Assets tracking
27
Smart Energy Management
Key Features
• Real time dashboard of following data from smart meters
• Energy consumption (KWH and KVAH)
• Voltage (3 phases)
• Current (3 phases)
• Power factor
• Energy cost (computed)
• Historic trends for above parameters for a given duration (specified start date and end
date)
• Alerts for power factor deviation

29
IIoT Gateway

Source: Advantech UTX-3117 Datasheet

30
IIoT Gateway

31 Source: Ewon Flexy Gateway (HMS Networks)

Solid Waste Management

Solid Waste Management

32
SWM - Solution Overview
➢ GPS based tracking
of collection
vehicles.

➢ RFID based waste

pickup monitoring.

➢ Provides Field
sensor data
collection, alerts and
dashboards.

➢ Insights on field
about optimized
route to follow and
bins to pickup.

➢ Based on industry
standard approach.

33
33
OBD Use Case
OBD-II
• On-Board-Diagnostics-II
• Control and measure emissions
• Provides readings
• Coolant temp
• Throttle
• RPM
• Acceleration
• Speed

• Other Use cases

• Insurance premium optimization
• Driving Behavior

35
Heavy Machinery Telematics
Forklift Monitoring

37 Source: Link
Telematics
• Enhanced Customer Experience
• Health Monitoring and Notification – Engine Temp, RPM, Engine Oil Pressure, Coolant Temp

• Service and Maintenance Automation

• Breakdown notification and correction

• Warranty Claim Validations

38
Summary
Summary
• IoT market is maturing as it progresses
• Certain industry verticals hold promise for IoT solutions where the ecosystem is
maturing and business case is justified.
• The value chain of IoT is fragmented and it is expected to get consolidated as we
move further.
• Various use cases that we saw can be piloted using very low cost tools/open source
frameworks.

40
Thank You