You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 11 Next »

Overview

MQTT and Unified Namespace (UNS) integration aims to provide data management and communication across devices and applications. MQTT facilitates data transmission using a publish-subscribe model, while UNS acts as a centralized repository for this data, enabling integration and accessibility across different systems.

Integrating MQTT with UNS is designed to overcome the asset modeling challenges posed by disparate data sources and formats, offering structured and contextualized data by providing a unified data format and access point.

This document contains information on how to access elements from an MQTT Broker data model in any area of the Engineering Environment, and it includes information on how to access the entire or just a part of the Asset Model Structure.

On this page:


Introduction to MQTT and UNS


Unified Namespace

Context

Unified Namespace is a software solution that acts as a centralized repository of data, information, and context where any application or device can consume or publish the data needed for a specific action.

It allows users to collect data from many sources and transform it into a format that other systems can understand. Without a centralized data repository, it could take months to deploy a new analytics application across the entire enterprise versus hours with a unified namespace.

Asset Modeling

In your solution, you can have a full or partial view of the MQTTspB Data Mode. On Unified Namespace → Asset Tree, you can create your data structure and assign MQTT nodes to them.

Workshop

This workshop provides an overview of these tools and instructions on integrating them into your projects.

Workshop used version 9.2

The following workshop used the version 9.2, not the version 10, so its users interface is the classic one. 

Despite changes on the configuration user interface, many of the concepts introduced in the workshop still applies as a valid architecture

Solution Examples

Take a look in the following solutions, on examples on how to use Unified Namespaces, AssetTree and TagProviders

ProductionLine Demo

SolarPanel Demo


In this section...

The root page @parent could not be found in space v10.

  • No labels