---
title: "Unified Namespace (UNS) Toolkit: Connect, Contextualize, Transport | FlowFuse"
description: "Build your Unified Namespace with one toolkit: connect every machine, contextualize raw tags, run a built-in MQTT broker, and manage the namespace across every plant."
canonical_url: "https://flowfuse.com/use-cases/uns/"
meta:
  keywords: "Unified Namespace, UNS, UNS architecture, ISA-95, MQTT broker, Sparkplug B, OPC UA, Modbus, Siemens S7, industrial data, Node-RED, FlowFuse"
  "og:description": "Build your Unified Namespace with one toolkit: connect every machine, contextualize raw tags, run a built-in MQTT broker, and manage the namespace across every plant."
  "og:image": "https://flowfuse.com/images/node-red/flowfuse-broker-hierarchy-framed.webp"
  "og:title": "Unified Namespace (UNS) Toolkit: Connect, Contextualize, Transport | FlowFuse"
---

> Index of every page on this site: [llms.txt](https://flowfuse.com/llms.txt)

# **The complete toolkit **for your Unified Namespace

Give every plant one source of truth, and every system the same language. FlowFuse connects the machines you already run and turns their data into live information your whole business can act on. Build your UNS once, then roll it out to every site.

[**Talk to Us**](https://flowfuse.com/book-demo/) [**Build With Us**](https://flowfuse.com/build-with-us/)

![Diagram: PLCs, machines and SCADA feed into FlowFuse, which connects, collects, transforms and contextualizes their data and transports it through a built-in MQTT broker to MES, ERP and AI.](https://flowfuse.com/images/use-cases/uns/uns-hero.webp)

## **Over 36,000 users have trusted FlowFuse**

![Newell logo](https://flowfuse.com/images/home-logos/newell-logo.svg)![Cargill logo](https://flowfuse.com/images/home-logos/cargill-logo.png)![Verduyn logo](https://flowfuse.com/images/home-logos/verduyn-logo.png)![Pem logo](https://flowfuse.com/images/home-logos/pem-logo.svg)![Ardo logo](https://flowfuse.com/images/home-logos/ardo-logo.png)![Bosch logo](https://flowfuse.com/images/home-logos/bosch-logo.svg)![Milliken logo](https://flowfuse.com/images/home-logos/milliken-logo.svg)![Abrasive\_technology logo](https://flowfuse.com/images/home-logos/abrasive_technology-logo.svg)![Knobelsdorff logo](https://flowfuse.com/images/home-logos/knobelsdorff-logo.png)![Wings logo](https://flowfuse.com/images/home-logos/wings-logo.png)![Wenco logo](https://flowfuse.com/images/home-logos/wenco-logo.svg)![Energinet logo](https://flowfuse.com/images/home-logos/energinet-logo.png)![Topsoe logo](https://flowfuse.com/images/home-logos/topsoe-logo.svg)![Walter logo](https://flowfuse.com/images/home-logos/walter-logo.svg)![Decospan logo](https://flowfuse.com/images/home-logos/decospan-logo.svg)![Wilson tool logo](https://flowfuse.com/images/home-logos/wilson-tool-logo.png)![Protolabs logo](https://flowfuse.com/images/home-logos/protolabs-logo.svg)![Agristo logo](https://flowfuse.com/images/home-logos/agristo-logo.svg)![Arch systems logo](https://flowfuse.com/images/home-logos/arch-systems-logo.png)![Epcor logo](https://flowfuse.com/images/home-logos/epcor-logo.png)![Sky io logo](https://flowfuse.com/images/home-logos/sky-io-logo.svg)![Moderna logo](https://flowfuse.com/images/home-logos/moderna-logo.svg)![Ensign energy logo](https://flowfuse.com/images/home-logos/ensign-energy-logo.png)![L2l logo](https://flowfuse.com/images/home-logos/l2l-logo.png)

![Newell logo](https://flowfuse.com/images/home-logos/newell-logo.svg)![Cargill logo](https://flowfuse.com/images/home-logos/cargill-logo.png)![Verduyn logo](https://flowfuse.com/images/home-logos/verduyn-logo.png)![Pem logo](https://flowfuse.com/images/home-logos/pem-logo.svg)![Ardo logo](https://flowfuse.com/images/home-logos/ardo-logo.png)![Bosch logo](https://flowfuse.com/images/home-logos/bosch-logo.svg)![Milliken logo](https://flowfuse.com/images/home-logos/milliken-logo.svg)![Abrasive\_technology logo](https://flowfuse.com/images/home-logos/abrasive_technology-logo.svg)![Knobelsdorff logo](https://flowfuse.com/images/home-logos/knobelsdorff-logo.png)![Wings logo](https://flowfuse.com/images/home-logos/wings-logo.png)![Wenco logo](https://flowfuse.com/images/home-logos/wenco-logo.svg)![Energinet logo](https://flowfuse.com/images/home-logos/energinet-logo.png)![Topsoe logo](https://flowfuse.com/images/home-logos/topsoe-logo.svg)![Walter logo](https://flowfuse.com/images/home-logos/walter-logo.svg)![Decospan logo](https://flowfuse.com/images/home-logos/decospan-logo.svg)![Wilson tool logo](https://flowfuse.com/images/home-logos/wilson-tool-logo.png)![Protolabs logo](https://flowfuse.com/images/home-logos/protolabs-logo.svg)![Agristo logo](https://flowfuse.com/images/home-logos/agristo-logo.svg)![Arch systems logo](https://flowfuse.com/images/home-logos/arch-systems-logo.png)![Epcor logo](https://flowfuse.com/images/home-logos/epcor-logo.png)![Sky io logo](https://flowfuse.com/images/home-logos/sky-io-logo.svg)![Moderna logo](https://flowfuse.com/images/home-logos/moderna-logo.svg)![Ensign energy logo](https://flowfuse.com/images/home-logos/ensign-energy-logo.png)![L2l logo](https://flowfuse.com/images/home-logos/l2l-logo.png)

## Where UNS projects get stuck

One source of truth sounds simple. The trouble starts when you try to build it, and it usually starts in the same six places.

1. 01

   ### **Most machines don't speak MQTT**

   Legacy PLCs, SCADA and serial devices get left out of the namespace because nothing reads them.
2. 02

   ### **Point-to-point links keep breaking**

   Every new system needs a custom link to every other system, and each one breaks on its own.
3. 03

   ### **Raw values have no meaning**

   A register address like %MW104 tells the MES, the dashboard or the analyst nothing at all.
4. 04

   ### **Every layer is a separate product**

   The broker, the integrations and the applications each need their own tool, vendor and team.
5. 05

   ### **The topic tree drifts**

   As more teams publish, topic names and payloads stop matching and consumers break.
6. 06

   ### **Every plant starts from scratch**

   What worked at the first site gets rebuilt by hand at the next, and the two drift apart.

## Every layer of your UNS, in one platform

Each of those problems lives at a different layer. FlowFuse answers every one, so you build your whole UNS in one place instead of stitching together a separate tool for each layer.

**Connect & Collect**

### **Bring every machine into the namespace**

A UNS only works if every machine publishes to it, and most plant equipment doesn't speak MQTT.

- Connect over certified OPC UA, Modbus, Siemens S7 and EtherNet/IP nodes, plus 5,000+ other integrations
- Read from PLCs, SCADA and historians without changing a line of PLC logic
- Collect at the edge, right beside your machines, and send a value only when it changes

[Explore industrial integrations](https://flowfuse.com/integrations/)

**Transform & Contextualize**

### **Give every value a name, a unit and a place**

A raw register means nothing to the MES, the dashboard or the analyst reading it.

- Rename cryptic tags: %MW104 becomes filler/temperature in °C
- Organize every value by site, area, line and machine, following ISA-95
- Give MES, dashboards and analysts data they can use without a tag list from the PLC programmer

[Explore data integration](https://flowfuse.com/use-cases/data-integration/)

**Transport**

### **Run your namespace on a built-in MQTT broker**

The broker is the hub of a UNS, where every producer publishes and every consumer subscribes.

- Use the MQTT broker built into FlowFuse, with nothing extra to install
- Or keep the MQTT broker you already run and manage it from FlowFuse
- Run plain MQTT and Sparkplug B in the same namespace

[Explore IT/OT integration](https://flowfuse.com/use-cases/it-ot-middleware/)

**Browse & Manage**

### **Keep the namespace consistent as it grows**

A UNS falls apart when every team names topics its own way.

- See every topic in your namespace as a live tree
- Get topic schemas generated from live data and documented for you
- Give every team, at every plant, the same documented structure to build against

[Explore the FlowFuse platform](https://flowfuse.com/product/)

**AI**

### **Map thousands of tags in minutes, not weeks**

Mapping tags into a hierarchy is the slowest part of building any UNS.

- Describe your register map to FlowFuse Expert, and it builds the flows that name, scale and place every tag
- Or connect the AI agent your company already approved, such as Microsoft Copilot or ChatGPT, to do the same work
- Nothing is deployed until an engineer has reviewed and approved it

[Explore FlowFuse AI](https://flowfuse.com/ai/)

**Manage & Scale**

### **Run every plant's UNS from one place**

A UNS proves itself on one line and pays off only when every plant runs it the same way.

- See every plant's instances, versions and changes in one view
- Promote changes from dev to test to production, with one-click rollback
- Roll the proven setup out to the next site without rebuilding it

[Explore remote device management](https://flowfuse.com/use-cases/remote-device-management/)

## Built to pass IT review at every plant

Rolling your UNS out to every plant means IT has to approve each one. FlowFuse is SOC 2 Type I and Type II certified, with single sign-on, role-based access, audit logs, and self-hosted or air-gapped options for sites that can't use the cloud.

[Review our security and compliance details](https://flowfuse.com/platform/security/)

SOC 2 Type II

Single Sign-On

Audit Logs

Role-Based Access Control

Air-Gapped / Self-Hosted Deployment

## You're never alone, and never locked in

Software is only half of a UNS rollout. We become part of your team from the first plant, and stay long after the last one goes live.

- ### **Built with your team**

  Our engineers work alongside yours to design the namespace and deliver the first plant, then stay close whenever a site needs help. See [how we build with your team](https://flowfuse.com/build-with-us/).
- ### **No lock-in, ever**

  FlowFuse is built on open-source [Node-RED](https://flowfuse.com/node-red/) and MQTT. Your flows, topics and schemas belong to you, and your team can change them without waiting on us.
- ### **Your team grows with it**

  Your engineers learn by building alongside ours, and come away able to [run and extend it on their own](https://flowfuse.com/docs/).

**From IT and OT teams**

## What customers say about FlowFuse

A UNS succeeds when OT gets every machine connected and IT can govern it at scale. Here's how both teams describe taking FlowFuse from one site to many.

[Read customer stories](https://flowfuse.com/customer-stories/)

> ***“We started using Node-RED at the plant level, but FlowFuse is what turned it into an enterprise-grade solution. Everything runs centrally from corporate IT, across multiple plants, with the dev and production pipelines and controls our organization requires.” ***

***James Wise** Sr. Product Owner, Milliken & Company**IT***

> ***“I built out the FlowFuse deployment from scratch: machine monitoring, machine dashboards, ERP integration. What FlowFuse gave us was revision control and a platform the whole team could own. That made the deployment self-sustaining.” ***

***Lidiya Shutaya** OT Architecture & Standardization, formerly with Penn Engineering**OT***

> ***“FlowFuse is like a Swiss Army knife that I can drive most of our IT systems from, versus having 10 different vendor relationships, 10 different point solutions, and then having to build practices around all that.” ***

***Chris Meyer** IT Director, Wilson Tool International**IT***

> ***“We had expensive equipment sitting idle for 8 to 12 hours a day, capital doing nothing. Now those same machines run production validation during the day and automatically switch to reliability stress testing at night. Same hardware performing two jobs, with zero manual setup between shifts. With FlowFuse, we have 1 connected station to update every controller, instantly.” ***

***Rhythm Agarwal** Sr. Manufacturing Engineer, Aperia Technologies**OT***

> ***“FlowFuse removes most of our concerns about scalability and reliability. It's also making it a lot easier for us to complete security audits for our customers. FlowFuse's stack is open, widely used and well documented, which gives auditors confidence in our applications built on your platform.” ***

***Alan Yeung** CTO, Power Workplace**IT***

> ***“Once we settled on using Node-RED, we knew we needed a solution to help us manage our edge devices as well as our central control system. FlowFuse has helped us take our Node-RED from proof-of-concept through to a reliable, scalable solution for the future.” ***

***Robert VanHofwegen** District Manager, Paloma Irrigation and Drainage District**OT***

01/06

## Unified Namespace resources

Guides and deep dives on building a UNS, from structuring topics to choosing a broker.

- [![Why FlowFuse is the Complete Toolkit for Building Your UNS](https://flowfuse.com/blog/2025/01/images/why-flowfuse-is-complete-toolkit-for-uns.jpeg)

  **Why FlowFuse is the Complete Toolkit for Building Your UNS**](https://flowfuse.com/blog/2025/01/why-flowfuse-is-complete-toolkit-for-uns/)
- [![Designing a Clear Topic Structure for Your UNS, over the FlowFuse broker topic hierarchy](https://flowfuse.com/blog/2025/01/images/uns-topic-structer.png)

  **Designing a Clear Topic Structure for Your UNS**](https://flowfuse.com/blog/2025/01/designing-topic-hierarchy-for-your-uns/)
- [![MQTT: The Frontrunner for Your UNS Broker, with FlowFuse and MQTT at the center of a UNS](https://flowfuse.com/blog/2025/01/images/mqtt-for-uns-1.png)

  **MQTT: The Frontrunner for Your UNS Broker**](https://flowfuse.com/blog/2025/01/mqtt-frontrunner-for-uns/)
- [![Data Modeling: The Key to a Successful Unified Namespace](https://flowfuse.com/blog/2024/12/images/data-modeling-uns.png)

  **Data Modeling: The Key to a Successful Unified Namespace**](https://flowfuse.com/blog/2024/12/why-uns-need-data-modeling/)

[Read all UNS articles](https://flowfuse.com/blog/uns/)

## Unified Namespace and FlowFuse: FAQs

###

###

###

###

###

###

###

###

###

## **Start with the line that's hardest to connect**

Tell us what equipment it runs. We'll show you its data in your namespace, named and in context, and how the same setup reaches every other site.

[**Talk to Us**](https://flowfuse.com/book-demo/)

```json
{"@context":"https://schema.org","@graph":[{"@id":"https://flowfuse.com/#website","@type":"WebSite","description":"FlowFuse builds your first industrial solution with your team, proves it at one plant, then helps you roll it out to every plant, faster each time.","inLanguage":"en","name":"FlowFuse","url":"https://flowfuse.com/","alternateName":["FlowForge","Flow Fuse"],"publisher":{"@id":"https://flowfuse.com/#identity"}},{"@id":"https://flowfuse.com/use-cases/uns/#webpage","description":"Build your Unified Namespace with one toolkit: connect every machine, contextualize raw tags, run a built-in MQTT broker, and manage the namespace across every plant.","name":"Unified Namespace (UNS) Toolkit: Connect, Contextualize, Transport | FlowFuse","url":"https://flowfuse.com/use-cases/uns/","@type":["WebPage","FAQPage"],"isPartOf":{"@id":"https://flowfuse.com/#website"},"mainEntity":[{"@id":"https://flowfuse.com/use-cases/uns/#/schema/question/1"},{"@id":"https://flowfuse.com/use-cases/uns/#/schema/question/2"},{"@id":"https://flowfuse.com/use-cases/uns/#/schema/question/3"},{"@id":"https://flowfuse.com/use-cases/uns/#/schema/question/4"},{"@id":"https://flowfuse.com/use-cases/uns/#/schema/question/5"},{"@id":"https://flowfuse.com/use-cases/uns/#/schema/question/6"},{"@id":"https://flowfuse.com/use-cases/uns/#/schema/question/7"},{"@id":"https://flowfuse.com/use-cases/uns/#/schema/question/8"},{"@id":"https://flowfuse.com/use-cases/uns/#/schema/question/9"}],"potentialAction":[{"@type":"ReadAction","target":["https://flowfuse.com/use-cases/uns/"]}],"primaryImageOfPage":{"@id":"https://flowfuse.com/#logo"}},{"@id":"https://flowfuse.com/#identity","@type":"Organization","legalName":"FlowFuse Inc.","name":"FlowFuse","url":"https://flowfuse.com","alternateName":["FlowForge","Flow Fuse"],"logo":{"@id":"https://flowfuse.com/#logo"},"sameAs":["https://twitter.com/FlowFuseinc","https://github.com/FlowFuse","https://www.linkedin.com/company/flowfuse/","https://www.facebook.com/FlowFuse/","https://www.youtube.com/channel/UCbBzP8NZbv3WDtlt4UouA-g"]},{"@id":"https://flowfuse.com/use-cases/uns/#/schema/question/1","@type":"Question","inLanguage":"en","name":"What is a Unified Namespace?","acceptedAnswer":{"@type":"Answer","text":"A Unified Namespace (UNS) is one shared, structured place where every machine, system and application publishes and reads its data, organized by enterprise, site, area, line and device. Instead of building a connection between every pair of systems, each one connects once to the UNS. Read the introduction to UNS."}},{"@id":"https://flowfuse.com/use-cases/uns/#/schema/question/2","@type":"Question","inLanguage":"en","name":"Do we need to replace our SCADA or historian?","acceptedAnswer":{"@type":"Answer","text":"No. FlowFuse connects to the SCADA, historians and other systems you already run and publishes their data to the UNS alongside data from your machines. They keep doing their jobs. See how FlowFuse works alongside SCADA."}},{"@id":"https://flowfuse.com/use-cases/uns/#/schema/question/3","@type":"Question","inLanguage":"en","name":"Can FlowFuse connect equipment that doesn't speak MQTT?","acceptedAnswer":{"@type":"Answer","text":"Yes. FlowFuse connects PLCs and machines over OPC UA, Modbus, Siemens S7 and many other industrial protocols, then publishes their data to your UNS. Legacy equipment stays as it is, with no changes to PLC logic."}},{"@id":"https://flowfuse.com/use-cases/uns/#/schema/question/4","@type":"Question","inLanguage":"en","name":"Do we have to use the FlowFuse MQTT broker?","acceptedAnswer":{"@type":"Answer","text":"No. FlowFuse includes a built-in MQTT broker, but you can also connect the broker you already run and manage your UNS from FlowFuse. Learn how to choose a UNS broker."}},{"@id":"https://flowfuse.com/use-cases/uns/#/schema/question/5","@type":"Question","inLanguage":"en","name":"Does FlowFuse support Sparkplug B?","acceptedAnswer":{"@type":"Answer","text":"Yes. You can publish and consume Sparkplug B alongside plain MQTT topics in the same UNS. See how to use MQTT Sparkplug B with Node-RED."}},{"@id":"https://flowfuse.com/use-cases/uns/#/schema/question/6","@type":"Question","inLanguage":"en","name":"How do we keep topics and payloads consistent across plants?","acceptedAnswer":{"@type":"Answer","text":"FlowFuse shows your full topic hierarchy and generates a schema from live data, documenting every topic automatically. Every team builds against the same structure, and new plants start from the one that already works."}},{"@id":"https://flowfuse.com/use-cases/uns/#/schema/question/7","@type":"Question","inLanguage":"en","name":"Can we start with one plant and expand later?","acceptedAnswer":{"@type":"Answer","text":"Yes, and most teams do. Prove the UNS on one line or plant, then reuse the same flows, topic structure and deployment pipelines at every new site."}},{"@id":"https://flowfuse.com/use-cases/uns/#/schema/question/8","@type":"Question","inLanguage":"en","name":"Where can FlowFuse run?","acceptedAnswer":{"@type":"Answer","text":"On FlowFuse Cloud, on your own servers, or both, with instances on edge devices managed from either. Self-hosted deployments can run fully air-gapped."}},{"@id":"https://flowfuse.com/use-cases/uns/#/schema/question/9","@type":"Question","inLanguage":"en","name":"Does FlowFuse meet enterprise security requirements?","acceptedAnswer":{"@type":"Answer","text":"Yes. FlowFuse is SOC 2 Type I and Type II certified and supports single sign-on, multi-factor authentication, role-based access and a full audit log. See FlowFuse security."}},{"@id":"https://flowfuse.com/#logo","@type":"ImageObject","caption":"FlowFuse","contentUrl":"https://flowfuse.com/handbook/images/logos/ff-logo--square--dark.png","inLanguage":"en","url":"https://flowfuse.com/handbook/images/logos/ff-logo--square--dark.png"}]}
```

## Sitemap

See the full [sitemap](https://flowfuse.com/sitemap.md) for all pages.
