A Practical Guide to the Industrial Internet Connectivity ... · - DDS - OPC UA - OneM2M - HTTP -...

A Practical Guide to the Industrial Internet Connectivity Framework (IICF)

Stan Schneider, PhD

RTI CEO

IIC Steering Committee Vice Chair

©2019 IIC or Real-Time Innovations, Inc. Permission granted to distribute unmodified pdf.

The Big Picture

NGC3370


EducationColleges & UniversitiesConferences & WorkshopsLaboritoriesPublicationSchoolsTrade Schools

Aerospace & DefenseAir ForceArrmyAviationHome Land SecurityMilitaryNavySpace Flight

AgricultureFarmingFishingForestryHydrologyLife SciencesRanchingWeather

Buildings & FacilitiesApartmentsBuilding & ConstructionBuilding Maintenance Building SecurityCommercial BuildingsConstructionEngineeringHomeHousing AuthoritiesHVACOfficeReal Estate

Consumer & HomeAutomotiveCommercial CookingConsumer ProductsDay CareElder CareEntertainmentFood and BeverageFood TrucksGroceryHome ProductsHospitalityPet CarePharmaciesPhotographyRecreation ServicesRestaurantsSporting EventsStreet VendorsTourismTravel

Energy & UtilitiesChemicalsElectricMiningOil & GasPetro-ChemicalsPowerRenewableSewerWater

EnvironmentAir Pollution ControlBiodiversity Eco-constructionEnvironmental Monitoring & InstrumentationEnvironmental Research & DevelopmentHeat & Energy Saving and Management

MetrologyNature ProtectionNoise & Vibration Control

OceanographyRecycled Materials Remediation & Clean Up of Soil & Groundwater Renewable Energy Production Waste Management & RecyclingWaste Water Treatment Water Supply

Finance & BankingAccounting SystemsATM SystemsCredit Card SystemsPoint of SalesRetail Banking

Public SectorCityCivil Administration Disaster PreventionEducationEmergency & Crisis ResponseEnvironmentFireLaw Enforcement & PoliceMunicipalities & CountiesPublic SafetyPublic SecuritySurveillanceTransportationWaste ManagementWater

HealthcareAssisted Care

Clinical Trials

Connected Medical Devices

Continuous Patient Monitoring

Dentistry

Disease Diagnosis

Home Healthcare

Hospitals

Life Sciences

Medical Offices

Medical Therapy

Pharma

Pharmacies

Media & Communication

Cable Providers

Computers

Entertainment

Global Media

Phones

Satellite TV

Telecommunications Carriers

Televisions

Video Recorders

Wireless Services

ManufacturingApparelBeverage & Tobacco ProductChemicalsComputer & Electronic ProductsElectrical Equipment & ComponentsFabricated Metal Products

FactoryFoodFurniture & Related Products

Industrial AutomationLeather & Allied ProductsMachineryNonmetallic Mineral ProductsPaperPetroleum & CoalPlastics & Rubber ProductsPrimary Metal ManufacturingPrinting & Related Support ActivitiesTextile MillsTextilesTransportation EquipmentWood Products

Mining & MetalsAluminum

Coal

Diamonds & Gemstones

General Mining

Gold

Iron & Steel

Nonferrous Metals

Platinum & Precious Metals

Near Space & New SpaceClosed Loop Ecological Systems

Closed Loop Living Systems

Constellation Controllers

Consumer Traffic Analytics

Ecological Planning

Environmental Monitoring

Hyper-Local Agriculture

Hyper-Local Construction

Hyper-Spectral Imaging

In-Flight Satelite Servicing

On-Site Materials Analytics and Inventory

On-Site Materials Optimization

Parametric City Planning

Parametric Construction Planning

Remote Maintenance and Diagnostics

Space Based Planning

Weather Pattern Analytics

TransportationAeronautics

Airport

Cargo Handling

Cruise Industry

Fleet Management

Freight Management

Logistics

Mobility

Pipelines

Postal & Delivery Services

Public Transportation

Rail

Roads

Shipping

Traffic Infrastructure

Transportation

Trucking

Vehicle

Wholesale & Distribution RetailApparel RetailersBroadline RetailersDrug RetailersFood Retailers & WholesalersHome Improvement RetailersSpecialized Consumer ServicesSpecialty Retailers

The IIoT is a $10T opportunityBut it’s 1m * $10m use cases across all industries

The challenge is understanding

IIoT #1 Blocker


Industrial IoT Application Categories


DeviceMonitoring Edge

Autonomy

Databus

Databus

AnalyticOptimization

The Industrial Internet Consortium

A Global,Open Membership Consortium

spanning 30+ countriesThe World’s Largest IoT Consortium

The IIC created the IIoT market


The Industrial Internet Connectivity Framework

• The industry’s only detailed analysis of IIoT Connectivity Technologies

• Architecture

• Assessment

• Standards- DDS- OPC UA- OneM2M- HTTP- MQTT- CoAP

• Examples & selection guidance

• Years of work by many architects across industries, standards, & technologies


Released Feb 28, 2017

IICF Goals

Clarity

Guide map to the rich but

often confusing landscape of

IIoT connectivity

Useful, practical, tangible

guidance for requirements

assessment, technology

evaluation and selection

Stable long term

foundation for IIoT

interoperability


Industry Connectivity Architecture

Evolution of the IIoT Connectivity Stack

7-Layer OSI Stack Model

(1984)

4-Layer Internet Stack Model

(1970s)

Industrial IoT

(2014)

Transport

Link

Framework

Distributed Data

Interoperability and Management

Physical

Network

IIoT Connectivity Stack Model

(2017)



IIoT Connectivity Stack Model Participant X

Connectivity

Information

Networking

IICF Focus

Information (Data in Context)

Participant X

Transport

Link

Framework

Distributed Data


Physical

Network

Participant Y

Data (State, Events, Streams)

Messages

Packets

Frames

Bits

Transport

Link

Framework

Distributed Data


Physical

Network

Technical Interoperability (opaque blocks)

SyntacticInteroperability

(data structures)

Semantic Interoperability (data context)

Technical Interoperability Example…

Messages

Share opaque data (byte sequences)


Syntactic Interoperability Example…

Messages


ShapeType

x y

color

Share structured datatypes


Semantic Interoperability Example…

Messages


Information (Data in Context)

ShapeType

Room

x

Temperature

y

Humidity

color

Room Color

ShapeType

Car

x

Row

y

Column

color

Car Color

?

Share data-objects in context


Fundamental N2 Connectivity Challenge

Reality Check

Accept that there will be

multiple connectivity

technologiesO(N2)



Connectivity Core Standards Architecture

• Connectivity Core Standards- Provide syntactic

interoperability- Stable, deployed, open

standard- Standard Core Gateways

to all other CCS• Domain-Specific

Connectivity Technologies- Connect via non-

standard gateway to any connectivity core standard

Few Core StandardsStandard Core

Gateways

Many domain technologies

Assessment Template

• Which layers(s) of the Connectivity Stack does it provide?

• What Core Functions does it provide?

• How does it rank against the Typical Considerations (of the layers spanned) ?

• How does it impact system Architectural Qualities?

• Does it fit Connectivity Core Standard Criteria?

Transport

Link

Framework

Distributed Data

Interoperability and

Management

Physical

Network


IICF Catalog of Connectivity Standards

• Frameworks

• DDS

• OPC-UA

• oneM2M

• Transports

• HTTP

• MQTT

• CoAP

Assessment Template Worksheets


Connectivity Standards


Manufacturing Origin

TSN /

Ethernet

(802.1,

802.3)

DDS

Wireless

PAN

(802.15)

Wireless

2G/3G/LTE

(3GPP)

Wireless

LAN

(802.11 Wi-

Fi)

Internet Protocol (IP)

CoAP MQTT

Web

Services

Wireless

Wide Area

(802.16)

HTTPDDSI-RTPS

oneM2M OPC-UA

OPC-UA Bin

Telecommunications Origin

UDP TCPTCP

Transport

Link

Framework

Distributed Data


Physical

Network

Healthcare TransportationManufacturing… …Energy &

Utilities

Where to Start?

Choosing a Connectivity Standard


B

CA

X

Your application:

Choose A or B or C

Requirement 1, e.g. latency

Req

uir

eme

nt

2, e

.g. f

an-o

ut

IIoT Connectivity Perception


X

Clearly DDS

Clearly UA

Interstellar space

Your application

The IIoT is So Big…Standards Don’t Overlap

©2019 IIC or Real-Time Innovations, Inc. Permission granted to distribute unmodified pdf.Requirement 1

Req

uir

emen

t 2

Clearly MQTT

How to Choose?


System Aspect Example User Approach Standard

Software Integration & Autonomy

Software Architect integrating components

Data-centric DDS

Device interchangeability

Device manufacturer sellingdevices to technicians

Device-centric

OPC-UA

Web & Mobile User I/F App builder supportingback-end services

RESTful Web services/HTTP

ICT integration Wide-area wireless telecom integrator

Common services layer

oneM2M

Selection Guide


Simple Diagnostic Questions

http://

RTI extends & interprets the IICF in this section

DDS is the standard that defines the data-centric databus

Data Centricity Designs the System Around the Data


Application

Data

Application

Application

Application

MessagingRemote ObjectsClient/serverSOAs

Database

Data-centric storage and search of old data

Data-centric sharing and filtering

of future data

Databus

Choose DDS?

• Are there severe consequences of failure for one minute?

• Are “milliseconds” important in your communications?

• Do you have more than 10 software engineers?

• Does your data have many destinations (as opposed to just the cloud)?

• Are you implementing a new IIoT architecture?


3+ Yes?

©2017 Real-Time Innovations, Inc.

OPC UA

• Device-Centric Object-Oriented Framework

- Device models for common devices

- Integrate devices into workcells

- Client-server architecture

- Browsable address space

- New simple variable pub-sub


Motor Starter 01

Configuration

Control Function Local Operation

Multifunction Input DI0

ParameterSet Motor Parameters

Motor Current Low

Motor Current High

Service Info

Number of Starts

Motor Starter 01

Parameter Set

Control Function

Local Operation

Configuration

Multifunction Input DIO

Motor Current Low

Motor Current High

Number of Starts

Motor Current Low

Motor Current High

Service Info

Address Space

Choose OPC UA?

• Are you in in discrete manufacturing?

• Are you associated with the German Plattform Industrie 4.0?

• Are you building a device that will be integrated by industrial or control engineers and technicians, rather than software engineers?

• Will your product be used in different applications in different systems, as opposed to a single (type of) system where you control the architecture?

• Are you building equipment for a “workcell”?


3+ Yes?

• Common Service Layer Architecture- Services provided by telco- Platform Tier (cloud) applications can

seamlessly connect to diverse IoTdevices over many protocols

• Targets home automation, large mobile systems

• Typical uses• Register and connect to devices

and applications• Charge an account for service• Manage application and devices• Monitor systems

OneM2M


Choose OneM2M?

• Do you know what “ICT” stands for, and does it describe what you do?

• Is the cellular network your primary connection technology?

• Are your target applications largely composed of mobile devices?

• Can the components of your system tolerate intermittent connections and loosely-controlled latencies?

• Will your system leverage services provided by a communications provider such as a telco?


3+ Yes?

Choose RESTFul HTTP?

• Are you connecting independent devices to a single web service API?

• Are you building an HMI interface to an IoT device or service?

• Does your application only need to be fast enough for human interaction?

• Must your dataflow cross firewalls that you do not control?

• Is there no device-to-device communication?


3+ Yes? http://

MQTT: Collect Device Data

Message Queuing Telemetry Transport

(MQTT)

Collect datafrom sensors

For cloud


Choose MQTT?

• Do you think of your application as data collection?

• Is there little device-device communications?

• Is interoperability not a consideration?

• Do you have many small devices?

• Is software a minor challenge?


3+ Yes?

Choose CoAP?

• Are you running on a low-powered device?• Does your device have limited ROM/RAM?• Does your network have high package error rates throughput of

10-100 kbit/s?• Do you need direct machine to machine communication, but not

real-time?• Is your goal to connect your devices to a RESTful HTTP system?


3+ Yes?

What if None Fit?


Are They That Different?

DDS & OPC UA in Depth


Data Centric is the Opposite of OO


Object Oriented• Encapsulate data• Expose methods• Sequential execution

Data Centric• Encapsulate methods• Expose data• Parallel updates

ExplicitShared

Data Model

OPC UA and DDS Are Opposites

Aspect OPC UA DDS

Integration Users Engineers/technicians Software teams Opposite

Abstraction Object Oriented Data Centric Opposite

Primary markets Discrete manufacturing Transportation, medical, power, robotics, defense, etc. … but notdiscrete manufacturing

Opposite

System data model Dynamically built at runtime Fundamental integration point Opposite

Product support Extensive: hardware devices, software (HMI, historians)

None Opposite

Data model Hierarchical Relational Opposite

Data sharing model Variables CRUD type management (with matching)

Opposite

Sends data Yes Yes Similar


OPC UA & DDS Systems Differ Most in Software Origin


DDS

End User Software

DDS

End User Software

DDS

End User Software

End use application software interoperates

via a shared data model.

OPC UA

Supplier Software

OPC UA

Supplier Software

OPC UA

Supplier Software

Supplier device software interoperates

via detailed “companion specs”

Users and Applications are Very Different!

• You are a software architect. You:• Manage & integrate software development

teams• Design & control architecture & data model• Face challenges in defining software module

interfaces, implementing redundancy, complex data flow

• You are a device manufacturer. You:• Build a device for many applications• Do not control the installation data architecture• Face challenges of device vendor

interoperability, users who are not software experts


OPC UA

Device Integration for Vendor Interoperability


OPC UA Exposes Data through Servers

• Client/Server Model- Servers expose Address Space- Clients access information using services

• Object-oriented meta-model- Used for sensors, actuators…- Information as nodes in Address Space- Nodes are organized hierarchically

• OPC UA Services:- Connection management- Node management- View, Query- Attribute, Method- Subscription, Monitor items


OPC UA Object-Oriented Abstraction

• Entities- Objects with methods

(execution) and state (data)

• Entity Interaction- Get data by calling

methods, or “subscribing” to methods

- Update by calling methods

• State lives in objects- Operational data- “Meta data”, e.g. units, part

numbers

• Browsable information model “rolls up” the system from sub-parts hierarchically


Source: The Everyman’s Guide to OPC UA by John S. Rinaldi, used with permission

OPC UA DNA is Device Integration for Vendor Independence

• Challenges- Interoperate between

vendors- Assembled by engineers

or technicians

• Components- Devices- Reusable software

products (e.g. HMI)

• Interfaces- Standard device models- Dynamic address space

rollup- Read/write variables


Device A

Device B

HMI

Historian

Device E

• Standard device types• Read/write variables

OPC UA Interoperability Decouples Vendors


• Crisp protocol definition• Companion specs define

device & component models• Formal conformance testing

DDS Databus

Software Integration for Distributed Control


Data Centricity is Like Having All the Data “Inside”


Application

Data

• Logically, all data is “inside” every application

• Apps read or write like local memory

• With full control over timing, reliability, filtering, security

• No servers

• No objects or devices

• Any CPU, language,

OS, network

• Transparent mobility

DDS Arose to Meet Autonomous System Challenges

• Manage complex data flow and state• Ease system integration• Ensure reliable data availability• Guarantee real-time response• Allow any network• Build in security from the start• Make deployment flexible• Ease safety certification• Adapt Intelligence• Connect with Cloud Systems


RTI founded from Stanford Aerospace Robotics Lab

Integrate Complex Software for Real-Time Distributed

Control

DDS Provides Dataflow Control

• Autonomy combines:

- Volume- Frequency- Latency- Reliability- Destination

• A single abstraction that can handle all greatly simplifies the system


Cameras

Lidar

Radar

GPS

Control Cmd

Error

Data Source

Video Stream

Data List

Point cloud

Bin data struct

Bin data struct

Text String

Data Type Data Volume

Data Frequency

Scale with the Layered Databus Architecture


Fog

Edge

IT/C

lou

d

vMobile

HIS PACS LIS

GATEWAY to Ward DatabusRoom Systems Apps

Database

Ward

Medical Device

System Apps

Clinical Apps

Medical Device

Imaging Device

Imaging Device

GATEWAY to Enterprise Databus

GATEWAY to Cloud

IT Systems/Enterprise Databus (DDS)

ADTEMR

Clinical Apps

Database

Patient Room, Operating Room or ICU Databus (DDS)

Data LakeSystems Apps

Ward Databus (DDS)

Un

ifie

d D

ata

Mo

del

Cloud Server

Redundant data routers connect data spaces

reliably & transparently

RadarRadarDisplays Logging

Existing SCADA (to be replaced)

AlarmingMonitor

Interested in many quantities

IPCIPC

IPC

Segment Bus

Redundant Routing

IPCIPC

IPC

Segment Bus

IPCIPC

IPC

Segment Bus

VPN/Firewall

Local quantity interest

TCP (WAN)

VPN/FirewallVPN/Firewall

Control Room Bus

Control Room

Migration Server

Layered Databus: Grand Coulee Dam


Layered Databus: City Power Control


Interoperability across several proprietary systems

Data are often both critical and real-time

Avoid bottle necks

Cloud/edge hybrid solution

“Edge” often meant limited processing capacity

Connected systems and components need only to receive and elaborate some of the data

Large volume of real-time data as well as corporate business data (System-of-Systems)

Cybersecurity is an obligation

Quality of Service (QoS) characteristics

Data spaces (domains, partitions and topics) and data structures

Layered Databus Architecture Pattern

Layered Databus: Control Room to Vehicle


DDS incorporates control rooms for operational monitoring

DDS delivers in-vehicle data for autonomy

DDS DNA is Software Integration for Distributed Control

• Challenges- Interface many software teams- Interoperate between

software modules- Version matching- Decouple software modules in

flow, space, and time

• Components- Custom software - AIs, libraries

• Interfaces- Global data abstraction- Dataflow control- Common system data model


• Custom data model• Dynamic types• Dataflow control


DDS Applications Span the IIoT

Combining DDS & OPC UA with the Connectivity Core Architecture


Combine Software and Device Integration


DDS Control Bus

OPCUA

DDS

Gateway

DDS

OPCUA

OPCUA

DDS

DDS

OPCUA

Gateway

DDS

OPCUA

OPCUA

DDS

Higher Domains

Integrate Autonomy Software With DDS

Connect Interoperable Devices with OPC UA

Device A

Device B

HMI

Historian

Device E

Scales to Handle Large Plants

Provide transparent interoperability between existing DDS and OPC UA applications.

OPC-UA/DDS Gateway Standard


OMG mars/2018-02-01

Shared Global Data Space

DDS DataBus

Use Case #1: Scale Access to OPC UA devices


OPC UAServer

Device Supporting OPC UA

OPC UA as a universal“device driver”

OPC UA/DDS Gateway

OPC UAClient

DDS Participant

DDS Participant

DDS Participant

DDS Participant

DDS DataBus

Software on PLC or device!No extra box to configure

Use Case #2: Interface to DDS Systems


OPC UAClient

OPC UA/DDS Gateway

OPC UAServer

DDSParticipant

SCADA tool supporting OPC UA

OPC UA HMI Tool interface to DDS

DDS DataBus

DDSParticipant

DDSParticipant

DDSParticipant

Summary


Key Takeaways

• The IICF stack defines levels of interoperability

• IICF assessment templates clarify connectivity technology capabilities

• The IICF analyzes key IIoT technologies- DDS, OPC-UA, oneM2M, HTTP, MQTT,

CoAP• Connectivity technologies are very

different!• The Core Connectivity Standard

architecture enables combinations

Transport

Link

Framework

Distributed Data

Interoperability and

Management

Physical

Network


The Industrial IoT Disruption


The real value is a common architecture that connects sensor to cloud, interoperates between vendors, and spans industries

You don’t compete against competitors. You compete against market transitions.

– John Chambers

Connect!!

• [email protected]

@RTIStan

LinkedIn: Stan Schneider

• Bio- CEO Real-Time Innovations, Inc

- IIC Steering Committee Vice Chair

- Advisory Board, IoT SWC

- Top-25 Global IIoT Influencer

- PhD, EE/CS, Stanford


https://www.linkedin.com/in/stan-schneider-102466/

A Practical Guide to the Industrial Internet Connectivity ... · - DDS - OPC UA - OneM2M - HTTP -...

Documents

Transcript of A Practical Guide to the Industrial Internet Connectivity ... · - DDS - OPC UA - OneM2M - HTTP -...