Cloud, App Services and Integrated IIoT:Why the in-house software development is the keystone to successful business

practices in the era of IIoT

Hamid Montazeri

Director, SW Engineering and Robotics

Digital Accelerator

Stanley Black &Decker

Tools and Storage Security Industrial

• Power Tools

• Hand Tools, Accessories, Storage

• Commercial Electronic Security

• Mechanical Access

• STANLEY Engineering Fastening

• Infrastructure

1st Wave 2nd Wave 3rd Wave

People Connecting

to the Internet

via Mobile Devices“Things”

Connecting

to the Internet

People Connecting

to the Internet

4

“Things”

Connecting

to the Internet

Transformative for

Customers/PartnersTransformative for

Operations

Connected ProductsSmart

Manufacturing

Connected Places

CONNECTED

PRODUCTS

CONNECTED

WORKSPACES

• Tools

• Appliances

• Vehicles

• Heavy Machinery

• Factories

• Homes

• Warehouses

• Farms

Application Categories

Connected Products Example

6

Smart Tools

Smart Batteries

Connector - Backward

compatibility

Area Light

Sync

Wirelessly

Complimentary tools

for Inventory

Management &

reporting

IoT and Backend

Services

TAG – for

everything else

Focus on Customer Benefits

7

Diagnostics & customization

Customize tools as the user wants them

Asset TrackingInventory Management

Location of assets using app and cloudAssign & Manage assets

Connected Workspaces Example

8

DEWALT JOBSITE WI-FI

Eco-System development is

an integral part of developing

a connected places product

road-map

Smart Manufacturing

9

Optimize manufacturing through:

• Application of advanced sensors

• Distributed throughout the

manufacturing and supply chain steps

• Connected through an IoT eco-system

• Generating data

• Analyzed using ML/AI

IoT in Enterprise

62%

Lead their own

IoT Projects

79%

Preventative

Maintenance

80%

Collect device

generated

data

Why IoT?

#1 Revenue

#2 Predictive

Maintenance

Opportunity

#1 Predictive

Maintenance

#2 Extend

Warranty

Data

#1 Time -

Location

#2 Feature

Usage

IoT: Blueprint for Getting Started

11

Identify Opportunities

• Customer Needs

• Market Research

• Innovation

Technical Competency

• Understand Technology

• Define Guiding Principles

• Track Technology Road map

• Define Architectural Layers

Select Partners

• Select by executingPOCs

• Influence partner technology based on guiding principles

Execute Projects

•Start small

•Integrate Early

•Learn and adapt

•Think Big

Disruptive Innovation: Rapid Prototyping and Agile Development

12

Solution

Efficiency

Platform

+

Dev Environment

Maturity

Reusable

Components

DevOps

Fusion

Serverless

+

IoT Platform

Base

Platform

16 weeks

to POC

8 weeks

to POC

4 weeks

to POC

91% operational

efficiency gain

• Speed of prototyping and solution

development is key for disruptive

innovation.

• Leveraging new development paradigms

makes rapid prototyping possible.

IoT System Layers: General Definition

13

WiFi BLE Any G LoRaLicensed

LPWA

Application

Enablement

Device

Management

Remote

AccessConfiguration OTA/FOTA

Delta

Updates

Security

Certificate

Device Drivers Edge Agents Data Management

AnalyticsVisualization Reporting API Integration/GW

Message

BrokerRules Engine

Device

Registrar

Device

Gateway

Virtual

Device

S

E

C

U

R

I

T

Y

B

I

L

L

I

N

G

M

O

N

I

T

O

R

I

N

G

Real-time

Data Store

Edge/Fog

Connectivity

Management

IoT System Layers: Application Enablement and Analytics

14

WiFi BLE Any G LoRaLicensed

LPWA

Application

Enablement

Device

Management

Remote

AccessConfiguration OTA/FOTA

Delta

Updates

Security

Certificate

Device Drivers Edge Agents Data Management

AnalyticsVisualization Reporting API Integration/GW

Message

BrokerRules Engine

Device

Registrar

Device

Gateway

Virtual

Device

S

E

C

U

R

I

T

Y

B

I

L

L

I

N

G

M

O

N

I

T

O

R

I

N

G

Real-time

Data Store

Edge/Fog

Connectivity

Management

15

Device Gateway

Device Gateway

Sensors

Actuators

Smart Devices

• A device or software system that enables

machine-to-machine communications across

a network.

• Device gateways often allow systems that

communicate with different protocols to

interact with each other.

• Device gateways allow remote

sensors/actuators/devices to report their

information to edge or cloud based IoT

backend systems.

16

Device Gateway

Sensors

Actuators

Smart DevicesMessage Broker

Message Broker

• An Intermediary software

system that allows two or

more devices or applications

to communicate with each

other.

17

Device Gateway

Sensors

Actuators

Smart DevicesMessage Broker

Device Registry

• A device (or thing) registry

maintains (and establishes)

a record of device (thing)

identities.

• The device registry

optionally maintains

metadata about a device.

Device Registrar

18

Device Gateway

Sensors

Actuators

Smart DevicesMessage Broker

Device Registry

AlgebraicAlgebraic

LogicLogic

DiscreteDiscrete

Rules Engine

• A Rules Engine

allows

execution of

desired rules

at run-time.

• Localizes rule

changes in an

application.

Rules Engine

19

Device Gateway

Sensors

Actuators

Smart DevicesMessage Broker

Device Registry

AlgebraicAlgebraic

LogicLogic

DiscreteDiscrete

Rules Engine

Data Storage

20

Real Time

Analytics

Device Gateway

Sensors

Actuators

Smart DevicesMessage Broker

Device Registry

AlgebraicAlgebraic

LogicLogic

DiscreteDiscrete

Rules Engine

Interaction With Real Time Analytics

21

Rules Engine

Data Storage

Analytics

Client Authentication/Authorization

Message Broker

Device

Gateway

Device

Registry

AWS IoT

22

Device Management And Device Provisioning

Update IoT DM with device security and configuration data

Test device connectivity and application function

Add device to inventory

Provision firmware on device

Create security and identity credentials

Provision connectivity platform

Setup VPN and OTA

It takes a substantial amount of time to manually

onboard a single device

Automation is key for device

provisioning and device management

Many IoT applications could be

developed efficiently by

leveraging Serveless paradigm

in the cloud

DevOps: Automating Build And Deployment

24

Typical Build Steps:

1. Infrastructure

2. Backend Deployment

3. Smoke Test

4. Mobile Deployment

Note:

Different availability zones and

regions

25

Thank You!