ROADSHOW The Canary Publisher ROADSHOW MQTT Overview Runs

ROADSHOW The Canary Publisher

ROADSHOW MQTT Overview ► Runs over TCP (transmission control protocol) ► Designed to be lightweight, open, simple and easy to implement ► These characteristics make it ideal for M 2 M and IIo. T applications, especially when a small footprint or low network bandwidth is required ► Can publish any type of data…. a benefit and a drawback ► https: //docs. oasis-open. org/mqtt/v 3. 1. 1/mqtt-v 3. 1. 1. html Publisher

ROADSHOW MQTT Deeper Dive ► Designed for publish/subscribe architecture ► Messages are published on a topic, e. g. , Factory. A/Line 2/Machine 4 ► Subscriptions support single level (+) and multilevel (#) wildcards, e. g. , Factory. A/Line 2/# ► ► Any client can be a publisher, subscriber, or both MQTT messages support three different Quality of Service (Qo. S) levels ► 0 = at most once ► 1 = at least once (potential duplicates) ► 2 = only once Publisher

ROADSHOW Sparkplug. B Overview ► Standard that defines the payload and topics used across an MQTT infrastructure ► ► Example – HTML is to HTTP as Sparkplug is to MQTT Defines a standard topic namespace ► sp. Bv 1. 0/<Group ID>/Message. Type/<Node. ID>/<Device. ID> ► Message types: NBIRTH, NDEATH, NDATA, NCMD, DBIRTH, DDEATH, DDATA, DCMD ► Efficient serialization of data (small payload sizes) ► Supports report by exception ► https: //www. eclipse. org/tahu/spec/Sparkplug%20 Topic%20 Namespa ce%20 and%20 State%20 Management. V 2. 2 with%20 appendix%20 B%20 format%20 -%20 Eclipse. pdf Publisher

ROADSHOW Publisher Architecture Based on our environment ► Publisher reads Views ► Configured to publish to Azure hosted Hive. MQ broker Publisher

ROADSHOW Why Use Publisher ► Publishes data to external systems from the Views service ► Initiates connection to those systems ► Formats include: ► Sparkplug. B over MQTT ► JSON over Websockets Publisher

Publisher ROADSHOW Sparkplug. B over MQTT ► Stream can be: ► Last value only ► Durable stream that publishes all values and tracks change since last publish ► Supports compression (GZIP and DEFLATE) ► Supports message aliasing for smaller payloads ► Can be configured with a primary host to detect when that host goes offline ► Supports multiple MQTT servers for a high availability MQTT architecture ► Supports TLS ► Supports connecting with a password options client certificate as well as username /

ROADSHOW JSON over Websockets ► User configured JSON record with fields mapped to a tag value, timestamp, quality, or property value. ► Can be configured to match a target system format ► Every value change will trigger Publisher to produce a new JSON record ► Can choose to publish based on asset type ► e. g. , publish all instances of asset type ‘Pump’ Publisher

ROADSHOW Publisher Best Practices ► ‘Last value’ streams are most efficient and should be used whenever a system only needs current value from the historian or isn’t concerned with missing a few values between scheduled historian reads ► ► Tested to 100, 000 updates per second ► Frequency should stay at one second or greater ‘Durable’ streams are more costly but ensure all data values are published ► Tested to 10, 000 updates per second

Publisher ROADSHOW Demo & Duplicate