Common Industrial Cloud Interface – Uses Cases andTechnical Requirements for Data Transfer
Stephen C. Briant
Rockwell Automation
Tom Whitehill
Schneider ElectricFebruary 22, 2017

Agenda•
•
•••
•
•
•

Introduction
Reference Architecture
Cloud Technologies
Guiding Principles
Information Exchange Patterns
Use Cases
Proof-Of-Concept
Conclusion – Next StepsTechnical Track© 2017 ODVA, Inc.

2017 Industry Conference & 18th Annual Meeting
All rights reserved.

www.odva.org

2

Introduction
••
•

•
•
•

The Industrial Internet of Things is here, bringing new technologies, challenges andopportunities to industrial automation
Companies are looking to the internet and cloud computing to provide new ways toimprove operations and increase productivity as well as addressing concerns of an aging
workforces
Cloud computing offers many advantages that were previously unavailable, starting withthe ability to connect to devices across an enterprise or a machine type across multiple
enterprises. In addition, the ability to scale computing power and storage are enabling new
possibilities for analyzing data streams.
Acquiring data from devices is the primary focus in the market today, but there aredefinitely opportunities to do more
In April, 2016, ODVA announced the formation of a new Special Interest Group (SIG) forthe Common Industrial Cloud Interface (CICI) to address these opportunities.
This new SIG intends to leverage technologies available in cloud platforms and “connect”
them with the rich information defined in CIP Devices in a simple and secure manner.

Technical Track© 2017 ODVA, Inc.

2017 Industry Conference & 18th Annual Meeting
All rights reserved.

www.odva.org

3

Reference Architecture
Reference Architecture

Cloud

On Premise

CIP Network
Device 1...

Public Cloud

CiCi Scope
Security &Identity

CiCi Gateway (Field)

Device 2

CIP InterfaceCloudInterface

Gateway

Applications
Message Routing

Technical Track© 2017 ODVA, Inc.

Stream Processing

Messaging
Endpoint

Device nDevices

DataStorage

Analytics

GatewayDevices2017 Industry Conference & 18th Annual Meeting
All rights reserved.

Cloud

www.odva.org

4Cloud Technologies•AMQP
Advanced Message Queuing Protocol, is the open standard and has emerged as a very popular
protocol for sending messages to and receiving messages from Cloud-based systems. In
addition to being Open and Standard, AMQP was designed with these characteristics Security,Reliability, Interoperability.

•MQTT
Message Queue Telemetry Transport, is an ISO standard (ISO/IEC PRF 200922),
publish/subscribe, lightweight messaging protocol used for Cloud-connectivity for limited network
bandwidth, remote applications.

•JSON
JavaScript Object Notation, is a terse, readable, structured data format. It is very popular as a
payload format for Device-to-Cloud and Cloud-to-Device messaging. A benefit to using JSON isthat many stream processing applications are built to natively consume JSON structures
efficiently and cost-effectively. Below is a very basic JSON message:{“name”=”CICI”,“message”=”Hello World!”}

Technical Track© 2017 ODVA, Inc.

2017 Industry Conference & 18th Annual Meeting
All rights reserved.

www.odva.org

5

Guiding Principles•

There are fundamental differences in Cloud-based vs CIP-network based
application development … a few are summarized here:– Distribution: Cloud-based applications are intrinsically distributed, combining
resources from multiple compute, storage and service platforms to achieve function.
– Real-Time: due to its distributed nature and platform dependencies, the notion of realtime is an uncommon concept in public Cloud computing.
– Protocols and Payloads: Message payloads that are easily programmaticallydigestible and extensible– Cloud communication protocols are generally widely used, open standards which are
not industry specific and which may be replaced at any time
– CIP communications, while an open standard, is industry specific and slow to change.
– Application scope and lifecycle: Cloud-based applications can have very broad scope,
virtually no limitations and can be modified or updated very rapidly

Technical Track© 2017 ODVA, Inc.

2017 Industry Conference & 18th Annual Meeting
All rights reserved.

www.odva.org

6

Guiding Principles•Security– all communication must be initiated from the device or gateway.

•Performance– Communication must be performant and scalable across the Reference
Architecture, therefore CIP must “stay home” or stay on premise•

Four V’s of Big Data––––

Volume (must handle the scale of data)
Variety (must handle different forms of data)
Velocity (must handle the speed required for analysis of the data)
Veracity (must handle the uncertainty or quality of the data)

Technical Track© 2017 ODVA, Inc.

2017 Industry Conference & 18th Annual Meeting
All rights reserved.

www.odva.org

7

Information Exchange Patterns• Telemetry––Device > CloudOne Way• Inquiry––•

Inquiry

Notification

CommandCloud

CloudCloudCloudCIP Device

CIP Device

CIP Device

CIP Device

Device > Cloud w/Response
Two Way

Notification––•

Telemetry

Cloud > Device
One Way

Command––

Cloud > Device w/Response
Two Way

Technical Track© 2017 ODVA, Inc.

2017 Industry Conference & 18th Annual Meeting
All rights reserved.

www.odva.org

8

Use Cases – Device Lifecycle•Commissioning–––––•Operating––––––––•

Out-of-the-box definitions (Inquiry, Command)
Cloud Registration / backend business setup (Inquiry, Command)
On-boarding/Provisioning (Inquiry, Command)Context of device in application (Inquiry, Command)
Control/Application loading (Inquiry, Notification, Command)
Monitoring (Telemetry)
Maintenance (Telemetry, Command)
Calibration (Inquiry, Command)
Diagnosis (Telemetry)
Enable/Disable (Command)
Optimization / Changing Parameters / Programs (Telemetry, Command)
Software updates (Inquiry, Notification, Command)
Device Replacement (Inquiry, Command)

Decommissioning–Removing a device (Telemetry, Command)

Technical Track© 2017 ODVA, Inc.

2017 Industry Conference & 18th Annual Meeting
All rights reserved.

www.odva.org

9Proof-Of-Concept•

Telemetry Use Case–––

•Goal–––•

A cloud application needs a list of CIP Devices
A cloud application needs a list of product names of CIP Devices
A cloud application needs the firmware version of a CIP Devices

Set up a simple application that accomplishes the Telemetry use case
Leverage open standards were possible
Leverage existing code and content to expedite efforts

Results–––––

Used a prototype CIP Stack and CIP Scanner in Node.JS
Used an open source OPC UA Server in Node.JS
Used Microsoft’s open source C# application to read OPC UA Server, connect to Azure IoT Hub via AMQP
Defined an Azure IoT Device on Azure IoT Hub
Used Device explorer on Azure to view AMQP message stream

Technical Track© 2017 ODVA, Inc.

2017 Industry Conference & 18th Annual Meeting
All rights reserved.

www.odva.org

Proof-Of-Concept
Reference Architecture: Proof-Of-Concept

Azure Cloud

On Premise
CIP NetworkDevice 1CICI Scope
CICI GatewayIngressQueue

Data Flow

Device 2...

Device nTechnical Track© 2017 ODVA, Inc.

CIP Interface+CIP Identity
Reader

OPC UA
Server +OPC UA
Client toAMQP

Example:- Protocol = AMQP
- Gateway Publishes Telemetry,
Identity Object

2017 Industry Conference & 18th Annual Meeting
All rights reserved.

Azure IoT Hub
AMQP Endpoint

www.odva.org

Backend Cloud Applications
and Presentation

Inspection
Here11CIP Stack/CIP Scanner•Load application into Node.JS•Print output of discovered CIP Devices are loaded into OPC UA ServerTechnical Track© 2017 ODVA, Inc.

2017 Industry Conference & 18th Annual Meeting
All rights reserved.

www.odva.org

12

Proof-Of-Concept
Reference Architecture: Proof-Of-Concept

Azure Cloud

On Premise
CIP Network
Device 1

CICI Scope
CICI Gateway
IngressQueue

Data Flow

Device 2...

Device nTechnical Track© 2017 ODVA, Inc.

CIP Interface+CIP Identity
Reader

OPC UA
Server +OPC UA
Client to
AMQP

Example:- Protocol = AMQP
- Gateway Publishes Telemetry,
Identity Object

2017 Industry Conference & 18th Annual Meeting
All rights reserved.

Azure IoT Hub
AMQP Endpoint

www.odva.org

Backend Cloud Applications
and Presentation

InspectionHere13

Setup OPC UA Client to OPC UA Server•OPC UA Server address•

Node to start data transfer

Technical Track© 2017 ODVA, Inc.

2017 Industry Conference & 18th Annual Meeting
All rights reserved.

www.odva.org

14Set up OPC UA Client to Azure IoT Hub•

Set up path to Azure•

Name of endpoint device•Name for event hub•

Selection of transport

Technical Track© 2017 ODVA, Inc.

2017 Industry Conference & 18th Annual Meeting
All rights reserved.

www.odva.org

15

Proof-Of-Concept
Reference Architecture: Proof-Of-Concept

Azure Cloud

On Premise
CIP Network
Device 1

CICI Scope
CICI Gateway
IngressQueue

Data Flow

Device 2...

Device nTechnical Track© 2017 ODVA, Inc.

CIP Interface+CIP Identity
Reader

OPC UA
Server +OPC UA
Client toAMQP

Example:- Protocol = AMQP
- Gateway Publishes Telemetry,Identity Object

2017 Industry Conference & 18th Annual Meeting
All rights reserved.

Azure IoT Hub
AMQP Endpoint

www.odva.org

Backend Cloud Applications
and Presentation

Inspection
Here16Observe messages on Azure IoT Hub

Technical Track© 2017 ODVA, Inc.

2017 Industry Conference & 18th Annual Meeting
All rights reserved.

www.odva.org

17

Conclusion – Next Steps•••••The Common Industrial Cloud Interface SIG was formed to enable cloud
applications to have access to the valuable information available in CIPDevices
There are many opportunities or use cases; however, the most obvious setof use cases are grouped around managing the lifecycle of CIP devices
The Common Industrial Cloud Interface SIG will use guiding principles andInformation Exchange Patterns to flush out functionality needed for theseuse cases
The next step will be map needed functionality to available technologies andstandards, including those shown in the Proof-Of-Concept
If you would like more information or want to contribute, please consider
joining the Common Industrial Cloud Interface SIG!

Technical Track© 2017 ODVA, Inc.

2017 Industry Conference & 18th Annual Meeting
All rights reserved.

www.odva.org

18