Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Blog: Why FlowFuse is the Complete Toolkit for UNS? #2883

Merged
merged 21 commits into from
Jan 20, 2025
Merged
Show file tree
Hide file tree
Changes from 7 commits
Commits
Show all changes
21 commits
Select commit Hold shift + click to select a range
f68c878
Create why-flowfuse-is-complete-toolkit-for-uns.md
sumitshinde-84 Dec 16, 2024
bb583f9
add image
sumitshinde-84 Dec 16, 2024
dd2b28b
Update why-flowfuse-is-complete-toolkit-for-uns.md
sumitshinde-84 Dec 16, 2024
d9c0ba4
Optimised images with calibre/image-actions
github-actions[bot] Dec 16, 2024
fa678de
Update why-flowfuse-is-complete-toolkit-for-uns.md
sumitshinde-84 Dec 16, 2024
974608c
Update why-flowfuse-is-complete-toolkit-for-uns.md
sumitshinde-84 Dec 16, 2024
64a51be
Update why-flowfuse-is-complete-toolkit-for-uns.md
sumitshinde-84 Dec 16, 2024
65962b8
Apply suggestions from code review
sumitshinde-84 Dec 19, 2024
7593afe
Update why-flowfuse-is-complete-toolkit-for-uns.md
sumitshinde-84 Dec 19, 2024
0ceb80a
Update why-flowfuse-is-complete-toolkit-for-uns.md
sumitshinde-84 Dec 19, 2024
d932370
Update why-flowfuse-is-complete-toolkit-for-uns.md
sumitshinde-84 Dec 19, 2024
4a7b7c4
Update why-flowfuse-is-complete-toolkit-for-uns.md
sumitshinde-84 Dec 19, 2024
0ac0ed7
Update why-flowfuse-is-complete-toolkit-for-uns.md
sumitshinde-84 Jan 8, 2025
88dc40b
update blog
sumitshinde-84 Jan 8, 2025
a7837de
Update src/blog/2025/01/why-flowfuse-is-complete-toolkit-for-uns.md
sumitshinde-84 Jan 10, 2025
ffcdb55
Apply suggestions from code review
sumitshinde-84 Jan 10, 2025
7f3679b
Merge branch 'main' of github.com:FlowFuse/website into why-flowfuse-…
sumitshinde-84 Jan 10, 2025
46f2ad0
add updated tile and diagram
sumitshinde-84 Jan 10, 2025
7865f4a
Merge branch 'why-flowfuse-is-complete-toolkit-for-uns' of github.com…
sumitshinde-84 Jan 10, 2025
c42f638
Update why-flowfuse-is-complete-toolkit-for-uns.md
sumitshinde-84 Jan 10, 2025
dd39a2c
Optimised images with calibre/image-actions
github-actions[bot] Jan 10, 2025
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Binary file added src/blog/2024/12/images/component-of-uns.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
104 changes: 104 additions & 0 deletions src/blog/2024/12/why-flowfuse-is-complete-toolkit-for-uns.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,104 @@
---
title: Why FlowFuse is the Complete Toolkit for UNS?
sumitshinde-84 marked this conversation as resolved.
Show resolved Hide resolved
subtitle: An In-Depth Look at FlowFuse's Features for Unified Namespace Integration
sumitshinde-84 marked this conversation as resolved.
Show resolved Hide resolved
description: Discover how FlowFuse is the ultimate solution for managing and implementing Unified Namespace (UNS) in industrial IoT environments.
date: 2024-12-18
authors: ["sumit-shinde"]
image:
keywords: uns, unified namespace, building uns with flowfuse, building uns using node-red, core components of unified namespace
tags:
- flowfuse
- flowfuse features
- unified-namespace
---

For the past few weeks, I’ve been diving deep into the Unified Namespace (UNS) concept with FlowFuse, frequently mentioning that FlowFuse is the complete toolkit for building and managing a UNS. However, I haven't yet shared the whole picture. What makes FlowFuse the ultimate solution for UNS? What sets it apart in the crowded industrial IoT solutions? In this Article, I’ll explain precisely how FlowFuse is not just another tool but a complete solution that will enhance your UNS strategy and streamline your data operations like never before.
sumitshinde-84 marked this conversation as resolved.
Show resolved Hide resolved

<!--more-->

At its core, a [UNS](/solutions/uns/) is a data architecture that combines all your data from different devices and systems into one place. It helps everything work together, making tracking and using data across your entire operation easier. For more information, check out our Article: [Introduction to the Unified Namespace](/blog/2023/12/introduction-to-unified-namespace/).

## **Core Components of a Unified Namespace**

To truly understand why FlowFuse is the ultimate toolkit for UNS, we need to look at its core components. As mentioned earlier, a UNS is designed to act as a single source of truth, one unified view of your entire manufacturing environment. But how does this happen? What components are necessary to make it work effectively?

![Core Components of UNS](./images/component-of-uns.png){data-zoomable}
_Core Components of UNS_

### **1. Connectivity Layer**
sumitshinde-84 marked this conversation as resolved.
Show resolved Hide resolved

The first step in any successful UNS strategy is the **Connectivity layer**. This is the part of the system where data flows into the UNS from various sources—whether it's sensors on the factory floor, data from PLCs, readings from SCADA systems, or other devices. This layer is critical because it ensures that all the necessary data is captured in real-time, providing a comprehensive view of the operation. Without a reliable connectivity layer, your UNS won’t be able to gather the information it needs to create a unified view.

The connectivity layer needs to be flexible and adaptable, supporting a range of communication protocols to ensure compatibility with everything from legacy systems to next-gen IoT devices. It ensures that no matter what technologies you’re working with, they can all work within your UNS framework.

### **2. Data Transformation Layer**

However, capturing data is only half the battle. In industrial environments, data often comes in many different formats, units of measurement, and structures. This is where the **data transformation layer** comes into play. The data transformation layer ensures the data is standardized and enriched for use across the entire system. Without Transformation, you end up with disconnected systems and complex [point-to-point integrations](/blog/2024/11/why-point-to-point-connection-is-dead/), just like the old days of OT/IT silos.

### **3. Message Broker**

Once the data is captured and transformed, a message broker is the following essential component of a UNS. This is where the data is sent to a central location, ready to be consumed by interested parties. In a UNS, data is typically handled by a broker based on a [publish-subscribe (pub-sub) architecture](/blog/2024/11/why-pub-sub-in-uns/), which is the backbone of the UNS system.

## How FlowFuse Supports These UNS Core Components

Before discussing how FlowFuse supports the core components of a Unified Namespace, let’s define FlowFuse and how it fits into the picture.

FlowFuse is an industrial data platform that empowers engineers to build, manage, scale, and secure their Node-RED solutions for digitalizing processes and operations. It enables seamless integration of IT and OT environments, allowing teams to connect, collect, transform, and visualize data quickly and efficiently to optimize industrial workflows.

Node-RED, the core tool orchestrated within FlowFuse, is a popular open-source, low-code platform that integrates various hardware devices, APIs, and services. Due to its simplicity and flexibility in creating custom workflows, it’s widely used in industrial IoT, home automation, and personal projects. When combined with FlowFuse’s enterprise layer, Node-RED becomes a powerful tool for digitalizing industrial operations, making it easy to integrate, process, and manage data at scale.

### **Connectivity Layer with FlowFuse**

As discussed earlier, the Connectivity Layer is the foundation of any successful Unified Namespace. This is where FlowFuse really stands out. At its core is Node-RED, an open-source, low-code platform with an active community that has contributed over 5,000 nodes. These nodes simplify integration with various devices, services, and APIs.

FlowFuse is even more powerful because it extends Node-RED’s connectivity options for enterprise-scale needs. FlowFuse ensures that all your devices and systems can easily send and receive data to and from your UNS, whether working with Modbus, MQTT, OPC-UA, REST APIs, or custom protocols. Regardless of your infrastructure's complexity, FlowFuse helps everything stay connected and work seamlessly together.

This flexibility makes it easy to integrate legacy systems and cutting-edge IoT devices into your UNS, ensuring your operations stay adaptable and future-proof.

For example, imagine a factory with a mix of legacy and modern edge devices, each communicating through different protocols like Modbus, OPC-UA, or even proprietary protocols like Siemens S7 or Mitsubishi's MC protocols. Now, you want to build a Unified Namespace (UNS) to integrate data from all these PLCs, edge devices, and sensor systems. The challenge is that these devices don’t natively communicate using modern protocols like MQTT, AMQP, or Kafka, often preferred in UNS architectures.

To bridge this gap, you typically need protocol converter devices or a virtual gateway to communicate between your legacy systems and the UNS. This is where FlowFuse comes into play. With FlowFuse running on the edge, it acts as the protocol converter or gateway, seamlessly translating data from legacy protocols (like Modbus or OPC-UA) into modern protocols (such as MQTT, AMQP, or Kafka). This allows all devices, regardless of their communication protocol, to send and receive data to and from your Unified Namespace without disruption.

### **Data Transformation Layer with FlowFuse**

Data coming from devices, sensors, or systems is rarely ready to be used directly. It often arrives in different formats, units of measurement, and structures. FlowFuse simplifies this challenge by transforming and contextualizing incoming data into a standardized format, making it easier to integrate and use across your entire system.

The data transformation layer within FlowFuse ensures that all data collected from various devices, sensors, or systems is organized, structured, and standardized. This layer allows you to integrate diverse systems and scale your Unified Namespace (UNS) infrastructure seamlessly.

FlowFuse provides an intuitive, low-code approach to data transformation. With Node-RED’s powerful interface and an extensive library of nodes, you can handle tasks like unit conversions, cleaning raw sensor data, and reformatting it to meet your specific business needs. The low-code nature of Node-RED within FlowFuse means you don’t need advanced coding skills—simply drag and drop nodes to customize your workflows.

Contextualizing data is just as critical as transforming it. Raw data often lacks the context needed for meaningful analysis, such as timestamps, geolocation, equipment IDs, or other business-specific information. FlowFuse makes it easy to add this metadata to the data streams, ensuring the meaning behind the numbers is clear and actionable.

For example, consider receiving temperature data from multiple sensors, each using different units—some reporting in Celsius, others in Fahrenheit, and others in Kelvin. Additionally, the data may be sent as numbers or strings. To make sense of this data, you need consistency in formats and meaningful context. With FlowFuse, you can automatically convert all these readings into a standard unit, like Celsius, and enhance each reading with metadata (e.g., sensor location, equipment type, or operating conditions). This contextualization ensures the data can be easily understood and leveraged for valuable insights into your operations at any given moment.

### **MQTT Broker with FlowFuse**

In a Unified Namespace (UNS), it’s crucial for data to flow smoothly between devices, systems, and applications. MQTT is often the preferred protocol because it is lightweight, efficient, and supports real-time communication, even in environments with limited network resources.

FlowFuse simplifies this by providing a built-in MQTT broker. This means there’s no need to set up or manage an external MQTT system—FlowFuse handles everything for you. By integrating MQTT directly into the platform, it ensures seamless data communication across your entire UNS, eliminating unnecessary complexity.

The FlowFuse-built MQTT Broker service offers an easy-to-use interface for securely managing clients and organizing the topic hierarchy. These interfaces are essential: one provides control over who can receive specific data, while the other lets you monitor and manage your entire topic hierarchy, which is structured like a tree, with topics organized one under another.

Additionally, Node-RED within FlowFuse includes standard MQTT nodes, allowing you to configure connections to the broker with key security features like TLS encryption and username/password authentication. These nodes also enable dynamic configuration of topics and brokers, making it simple to customize your MQTT setup and ensure secure, efficient communication throughout your UNS.

<hr style="border: none; border-top: 3px solid rgba(173, 192, 252, 0.55); opacity: 0.3; margin-bottom: 20px;">

FlowFuse makes building and managing a Unified Namespace (UNS) easy. It connects devices, transforms data into a usable format, and ensures smooth communication using an MQTT broker. Powered by Node-RED, it works with old and new systems, helping you scale and adapt quickly.

## **What Makes FlowFuse Stand Out in Industrial IoT?**

FlowFuse is not just another tool for industrial IoT—it’s an all-in-one platform for building, managing, and scaling a Unified Namespace (UNS). Unlike other platforms that focus on only one part of the process, FlowFuse brings together connectivity, data transformation, and message brokering into a single, smooth solution.

Many tools are good at one thing but struggle in other areas. For example, some connect systems well but have trouble transforming data, or they work with MQTT brokers but can’t handle older systems. FlowFuse solves these issues by providing everything you need in one place, so you don't have to use separate tools or deal with complex integrations.

FlowFuse also offers some unique features designed for industrial needs. One key feature is real-time collaboration, allowing multiple engineers to work on Node-RED flows simultaneously, speeding up the deployment process. It also lets you remotely manage edge devices, saving time and costs by avoiding on-site visits for troubleshooting or reprogramming.

When it comes to scaling, FlowFuse excels. It supports horizontal scaling, which helps manage workloads across multiple systems, and vertical scaling, making it easy to add more resources to handle growing demands. Whether your operations are expanding or dealing with heavy workloads, FlowFuse keeps your infrastructure stable and efficient.

Security is another strength of FlowFuse. It includes features like role-based access control, strong and different types of authentications, encrypted communication, and detailed audit logs to protect your data and meet industry standards.

## **Summary**

FlowFuse is more than just a Unified Namespace (UNS) toolkit. It’s an all-in-one platform that integrates connectivity, data transformation, and message brokering, simplifying the management of industrial IoT systems. With features like real-time collaboration, scalability, and strong security, FlowFuse goes beyond traditional UNS solutions, providing a complete, flexible, and secure solution for your operations.

***Want to learn more about how FlowFuse can help? [Talk with Our experts!](/book-demo/)***
Loading