From 0d3c6f8ea9233b494abca4d1ff3668d1f44c347e Mon Sep 17 00:00:00 2001 From: ZJ van de Weg Date: Mon, 10 Aug 2026 13:19:08 -0700 Subject: [PATCH] Fix internal blog/changelog links that point at redirecting URLs Rewrites 33 internal links across 28 blog/changelog posts to their final redirect targets, resolving nuxt-link-checker warnings for the 11 old hrefs listed in nuxt/redirects.ts (Phase 2 of the redirect link-checker cleanup, following #5560's pattern). --- src/blog/2022/09/community-news-08.md | 2 +- src/blog/2022/11/community-news-10.md | 2 +- src/blog/2022/12/community-news-11.md | 2 +- src/blog/2023/01/community-news-12.md | 2 +- src/blog/2023/02/community-news-02.md | 2 +- src/blog/2023/06/import-modules.md | 2 +- src/blog/2023/12/flowfuse-year-review-2023.md | 2 +- src/blog/2023/12/introduction-to-unified-namespace.md | 2 +- src/blog/2024/01/dashboard-2-multi-user.md | 2 +- .../2024/03/installing-operating-node-red-behind-firewall.md | 2 +- src/blog/2024/04/node-red-architecture.md | 2 +- src/blog/2024/05/product-strategy-updates.md | 2 +- src/blog/2024/08/using-mqtt-sparkplugb-with-node-red.md | 2 +- src/blog/2024/10/announcement-mqtt-broker.md | 2 +- .../10/managing-node-red-instances-in-centralize-platfrom.md | 2 +- src/blog/2024/11/building-uns-with-flowfuse.md | 2 +- src/blog/2024/12/why-uns-need-data-modeling.md | 2 +- src/blog/2025/01/mqtt-frontrunner-for-uns.md | 2 +- src/blog/2025/01/why-flowfuse-is-complete-toolkit-for-uns.md | 2 +- src/blog/2025/06/what-is-mes.md | 4 ++-- ...tween-information-technology-and-operational-technology.md | 4 ++-- src/blog/2025/12/what-is-mttf.md | 2 +- src/blog/2025/12/what-is-teep.md | 2 +- src/blog/2026/01/opcua-vs-mqtt.md | 2 +- src/blog/2026/01/what-is-system-integrator.md | 2 +- .../02/what-is-event-driven-architecture-in-manufacturing.md | 4 ++-- src/blog/2026/04/rosetta-stone-for-industrial-data.md | 2 +- src/changelog/2023/10/certified-nodes.md | 2 +- 28 files changed, 31 insertions(+), 31 deletions(-) diff --git a/src/blog/2022/09/community-news-08.md b/src/blog/2022/09/community-news-08.md index 6ebbea30a7..b66c1b3ad3 100644 --- a/src/blog/2022/09/community-news-08.md +++ b/src/blog/2022/09/community-news-08.md @@ -23,7 +23,7 @@ If you’d like to learn more about what else was included in 0.9 you can do so [**Node-RED Con 2022**](https://nrcon.nodered.org/) We are happy to again be involved in Node-RED con. The event is being held online on 7th October, with content for both English and Japanese speakers. You can find out more on the [Node-RED Con website](https://nrcon.nodered.org/). -[**FlowFuse Team News**](/team/) +[**FlowFuse Team News**](/about/) We’d like to welcome Rob Marcer to the FlowFuse team. Rob has joined as our Developer Educator, he's going to work to help you get the best value from FlowFuse by developing our documentation and community support. We are also recruiting for [NodeJS Developers](https://boards.greenhouse.io/flowfuse/jobs/4463977004), if you’re interested in joining our team please [apply here](https://boards.greenhouse.io/flowfuse/jobs/4463977004#app). diff --git a/src/blog/2022/11/community-news-10.md b/src/blog/2022/11/community-news-10.md index 50950d5de4..c38666b911 100644 --- a/src/blog/2022/11/community-news-10.md +++ b/src/blog/2022/11/community-news-10.md @@ -29,7 +29,7 @@ Earlier this week, we announced a $7.25M seed round led by [Cota Capital](https: [**Node-RED Dashboard - Beginners Guide**](https://stevesnoderedguide.com/node-red-dashboard) It's great to see members of the Node-RED community taking their personal time to help us all build better projects. This write up takes you through the basics of creating your first Dashboard through to more advanced techniques to help your interfaces look professional and provide great user experiences. -[**FlowFuse Team News**](/team/) +[**FlowFuse Team News**](/about/) We are currently recruiting [NodeJS Developers](https://boards.greenhouse.io/flowfuse/jobs/4463977004), a [Product Manager](https://boards.greenhouse.io/flowfuse/jobs/4717778004), a [Recruiter / PeopleOps Manager](https://boards.greenhouse.io/flowfuse/jobs/4687876004) and a [Senior Community Manager](https://boards.greenhouse.io/flowfuse/jobs/4700809004). You can view any of the roles we currently have open and apply on our [Jobs page](https://boards.greenhouse.io/flowfuse). We'd also like to welcome [Pez Cuckow](https://github.com/Pezmc) who joined FlowFuse as a Senior Software Engineer in October. diff --git a/src/blog/2022/12/community-news-11.md b/src/blog/2022/12/community-news-11.md index e4c75a4308..a15576e16b 100644 --- a/src/blog/2022/12/community-news-11.md +++ b/src/blog/2022/12/community-news-11.md @@ -31,7 +31,7 @@ FlowFuse is a fully remote team, we currently have a strong skew towards western !["The FlowFuse team pictured during our visit to Clue Capers"](./images/clue-capers.jpg "The FlowFuse team pictured during our visit to Clue Capers") -[**FlowFuse Team News**](/team/) +[**FlowFuse Team News**](/about/) We are currently recruiting a [Product Manager](https://boards.greenhouse.io/flowfuse/jobs/4717778004), and a [Senior Community Manager](https://boards.greenhouse.io/flowfuse/jobs/4700809004). You can view any of the roles we currently have open and apply on our [Jobs page](https://boards.greenhouse.io/flowfuse). [**Try FlowFuse for Free**](https://app.flowfuse.com/account/create?code=RELEASE11) diff --git a/src/blog/2023/01/community-news-12.md b/src/blog/2023/01/community-news-12.md index 21bc77da5f..1b7d0e54ec 100644 --- a/src/blog/2023/01/community-news-12.md +++ b/src/blog/2023/01/community-news-12.md @@ -29,7 +29,7 @@ According to this detailed article from iot-analytics.com, on average, four new [**Custom Node Spotlight - node-red-contrib-string**](https://flows.nodered.org/node/node-red-contrib-string) String manipulation is the bread and butter of so many programming tasks. Node-RED has a lot of tools to help you edit your strings including support for [JSONata](https://jsonata.org/) and using the trusty function node. For those of us who prefer to keep things 'no-code' [node-red-contrib-string](https://flows.nodered.org/node/node-red-contrib-string) allows you to stack string manipulations together quickly and easily. It has a huge library of ready to use functions. -[**FlowFuse Team News**](/team/) +[**FlowFuse Team News**](/about/) We’d like to welcome two new members to the FlowFuse team. [Ian Skerrett](https://twitter.com/ianskerrett) has joined as our Head of Marketing and [Tracy Anthony](https://www.linkedin.com/in/tracyanthonyfernandez/) has joined as our HR Manager. FlowFuse continues to grow and we are becoming a truly global team. Would you like to work for FlowFuse? We are currently recruiting [NodeJS Developers](https://boards.greenhouse.io/flowfuse/jobs/4463977004) to join our team. You can view any of the roles we currently have open and apply on our [Jobs page](https://boards.greenhouse.io/flowfuse). diff --git a/src/blog/2023/02/community-news-02.md b/src/blog/2023/02/community-news-02.md index 85c8c376b4..d54ef62980 100644 --- a/src/blog/2023/02/community-news-02.md +++ b/src/blog/2023/02/community-news-02.md @@ -37,7 +37,7 @@ We're now working towards release 1.4 which is due on 16th February. You can see If you’d like to learn more about what else was included in 1.3 you can do so on our [blog post](/blog/2023/01/flowforge-1-3-0-released/), [GitHub release page](https://github.com/FlowFuse/flowfuse/releases/tag/v1.3.0), and [Youtube channel](https://www.youtube.com/watch?v=ey3xv5j5x7k). -### [Team News](/team) +### [Team News](/about/) We are currently recruiting [NodeJS Developers](https://boards.greenhouse.io/flowfuse/jobs/4463977004) as well as a [Graphic Designer](https://boards.greenhouse.io/flowfuse/jobs/4785058004) to join our team. You can view any of the roles we currently have open and apply on our [Jobs page](https://boards.greenhouse.io/flowfuse). ## Node-RED in the Community diff --git a/src/blog/2023/06/import-modules.md b/src/blog/2023/06/import-modules.md index 164880ea3b..ad0ec3bffc 100644 --- a/src/blog/2023/06/import-modules.md +++ b/src/blog/2023/06/import-modules.md @@ -101,7 +101,7 @@ Something we see [a lot on the Node-RED Forums](https://discourse.nodered.org/se -Node-RED is great for [data integration](/solutions/data-integration/). We use PostHog for our internal Product Analysis. We record live events as they occur on FlowFuse Cloud to better understand features that are (and are not) used. +Node-RED is great for [data integration](/use-cases/data-integration/). We use PostHog for our internal Product Analysis. We record live events as they occur on FlowFuse Cloud to better understand features that are (and are not) used. We wanted to investigate whether or not we could add backdated data, which in theory was possible via their posthog-node module. We wanted to populate it with data driven from our own database and API. diff --git a/src/blog/2023/12/flowfuse-year-review-2023.md b/src/blog/2023/12/flowfuse-year-review-2023.md index 23f4894521..05ac83a958 100644 --- a/src/blog/2023/12/flowfuse-year-review-2023.md +++ b/src/blog/2023/12/flowfuse-year-review-2023.md @@ -22,7 +22,7 @@ First off; in 2023 we were known as FlowForge. But, due to some trademark challe On the product side: Growth in adoption of the FlowFuse platform has been tremendous, in many dimensions; revenue generated, customers onboarded, and how many users are now professionalizing their usage of Node-RED. Our development platform has been used by thousands of developers to acquire data from various sources and visualize it to build rich applications for their use cases. And at every step of the way we’ve been able to improve their experience. -Data acquisition was always possible without FlowFuse, however we’ve improved on the status quo through the [Certified Nodes](/certified-nodes/) program. A nascent program that vets often used custom nodes from the community to ensure business readiness and validate nodes to ensure there’s no malicious code installed. +Data acquisition was always possible without FlowFuse, however we’ve improved on the status quo through the [Certified Nodes](/integrations/?certified=1) program. A nascent program that vets often used custom nodes from the community to ensure business readiness and validate nodes to ensure there’s no malicious code installed. Further, this year we’ve started [Dashboard 2.0](https://dashboard.flowfuse.com/). The development of the successor of [node-red-dashboard](https://flows.nodered.org/node/node-red-dashboard), which is built on deprecated technology and effectively on life-support. The development of the new Dashboard technology has taken massive steps and it’s very stable. Feature parity is not yet achieved, though we’re happy with the adoption of Dashboard 2.0 and the community [reporting issues and improvements](https://github.com/FlowFuse/node-red-dashboard/issues). diff --git a/src/blog/2023/12/introduction-to-unified-namespace.md b/src/blog/2023/12/introduction-to-unified-namespace.md index c461bcf4c2..35f40a8a36 100644 --- a/src/blog/2023/12/introduction-to-unified-namespace.md +++ b/src/blog/2023/12/introduction-to-unified-namespace.md @@ -14,7 +14,7 @@ tags: As your organization is generating more data there’s key architectural decisions to be made to ensure the full value can be unlocked and you’re -leveraging not just the tip of the iceberg. The [Unified Namespace (UNS)](/solutions/uns/) +leveraging not just the tip of the iceberg. The [Unified Namespace (UNS)](/use-cases/uns/) provides a blueprint to allow data to be consumed by many data-consumers. FlowFuse helps you manage this migration and the operationalization of your data. diff --git a/src/blog/2024/01/dashboard-2-multi-user.md b/src/blog/2024/01/dashboard-2-multi-user.md index be4ec9c526..12ac3a0e76 100644 --- a/src/blog/2024/01/dashboard-2-multi-user.md +++ b/src/blog/2024/01/dashboard-2-multi-user.md @@ -40,7 +40,7 @@ All instances on FlowFuse can be configured with _"FlowFuse User Authentication" _Note: Every instance created from today onwards automatically comes with the necessary configuration. Already created instances need to be manually restarted._ -The Personalised Multi-User Dashboard plugin, `@flowfuse/node-red-dashboard-2-user-addon`, is available in our [Certified Nodes](/certified-nodes/) catalogue, accessible to our Teams and Enterprise customers. +The Personalised Multi-User Dashboard plugin, `@flowfuse/node-red-dashboard-2-user-addon`, is available in our [Certified Nodes](/integrations/?certified=1) catalogue, accessible to our Teams and Enterprise customers. Once the "FlowFuse User Authentication" option has been enabled on your instance, you can then install our plugin, `@flowfuse/node-red-dashboard-2-user-addon`, through the "Manage Palette" option in the Node-RED Editor. diff --git a/src/blog/2024/03/installing-operating-node-red-behind-firewall.md b/src/blog/2024/03/installing-operating-node-red-behind-firewall.md index ec4da2a6df..d4035fe616 100644 --- a/src/blog/2024/03/installing-operating-node-red-behind-firewall.md +++ b/src/blog/2024/03/installing-operating-node-red-behind-firewall.md @@ -27,7 +27,7 @@ First, ask for a temporary exception. Node-RED is installed in a few minutes, so As FlowFuse can be installed in a VPN behind a firewall, there’s no requirement to open up a ‘gate’ in your firewall to FlowFuse servers. The safe perimeter provided remains to the outside world. The security aspect remains, though as a Node-RED developer, there are still everyday tasks you’ll need access to the outside world. -Consider installing third party nodes to connect your Node-RED instance to virtually any protocol or digital service. There are over 5000 of these nodes available, and as an organization it’s challenging to keep on top of. Your firewall provides one layer of security so that the data you’re accessing remains safe. FlowFuse provides a second layer of protection; we’ve introduced a [“Certified Nodes” catalog](/certified-nodes/). These nodes have gone through automated and manual inspection to prevent malicious code from making it onto your production systems. +Consider installing third party nodes to connect your Node-RED instance to virtually any protocol or digital service. There are over 5000 of these nodes available, and as an organization it’s challenging to keep on top of. Your firewall provides one layer of security so that the data you’re accessing remains safe. FlowFuse provides a second layer of protection; we’ve introduced a [“Certified Nodes” catalog](/integrations/?certified=1). These nodes have gone through automated and manual inspection to prevent malicious code from making it onto your production systems. Installing these packages would typically still require you to obtain files from NPM. With FlowFuse however, a cache can be built with only vetted nodes – All other nodes remain unavailable. diff --git a/src/blog/2024/04/node-red-architecture.md b/src/blog/2024/04/node-red-architecture.md index 6425b17145..b621c0011e 100644 --- a/src/blog/2024/04/node-red-architecture.md +++ b/src/blog/2024/04/node-red-architecture.md @@ -19,7 +19,7 @@ cta: description: FlowFuse helps you deploy and manage Node-RED across every layer of your factory, from shopfloor devices to enterprise systems, with centralized control and full visibility across every instance. --- -The architecture of a factory's Node-RED infrastructure is a common topic of discussion and inquiry. Fundamentally, my response to such queries unfolds in two parts. Initially, the focus must be on data organization. I champion a structure centered around a [Unified Namespace](/solutions/uns/), a concept I explore in depth in this article ["Node-RED in a Unified Namespace Architecture."](/blog/2024/02/node-red-unified-namespace-architecture/) However, this is only one part of the inquiry. The other part of the question delves into the positioning of FlowFuse and Node-RED within the network infrastructure. +The architecture of a factory's Node-RED infrastructure is a common topic of discussion and inquiry. Fundamentally, my response to such queries unfolds in two parts. Initially, the focus must be on data organization. I champion a structure centered around a [Unified Namespace](/use-cases/uns/), a concept I explore in depth in this article ["Node-RED in a Unified Namespace Architecture."](/blog/2024/02/node-red-unified-namespace-architecture/) However, this is only one part of the inquiry. The other part of the question delves into the positioning of FlowFuse and Node-RED within the network infrastructure. diff --git a/src/blog/2024/05/product-strategy-updates.md b/src/blog/2024/05/product-strategy-updates.md index 095b74e438..f4fc59ca78 100644 --- a/src/blog/2024/05/product-strategy-updates.md +++ b/src/blog/2024/05/product-strategy-updates.md @@ -64,4 +64,4 @@ In the mean time, please do reach out if there are any features you'd like to se If you're interested in learning more about our company and product strategies, you can read more detail in our Handbook: - [Company Strategy](/handbook/company/strategy) -- [Product Mission Statement](/handbook/engineering/product/strategy) \ No newline at end of file +- [Product Mission Statement](/handbook/engineering/product/) \ No newline at end of file diff --git a/src/blog/2024/08/using-mqtt-sparkplugb-with-node-red.md b/src/blog/2024/08/using-mqtt-sparkplugb-with-node-red.md index 0b2e9b7590..071a13c63a 100644 --- a/src/blog/2024/08/using-mqtt-sparkplugb-with-node-red.md +++ b/src/blog/2024/08/using-mqtt-sparkplugb-with-node-red.md @@ -45,7 +45,7 @@ Connected devices can generate a lot of data, but without a standardized format, ## What is MQTT Sparkplug? -MQTT Sparkplug B is an open-source specification governed by the [Eclipse Foundation Specification Process (EFSP)](https://www.eclipse.org/projects/efsp/). It defines a standardized MQTT topic namespace and payload format specifically designed for Industrial IoT (IIoT), with particular focus on real-time [SCADA](/solutions/scada/), control systems, and [HMI](/blog/2025/11/building-hmi-for-equipment-control/) solutions. +MQTT Sparkplug B is an open-source specification governed by the [Eclipse Foundation Specification Process (EFSP)](https://www.eclipse.org/projects/efsp/). It defines a standardized MQTT topic namespace and payload format specifically designed for Industrial IoT (IIoT), with particular focus on real-time [SCADA](/use-cases/scada/), control systems, and [HMI](/blog/2025/11/building-hmi-for-equipment-control/) solutions. At its core, Sparkplug B extends MQTT 3.1.1 by adding structured topic namespace conventions, Google Protocol Buffer encoded payloads, state-aware birth and death certificates, metric aliasing for bandwidth optimization, and store-and-forward capabilities for intermittent connectivity. These additions transform MQTT from a simple messaging protocol into a complete industrial communication framework. diff --git a/src/blog/2024/10/announcement-mqtt-broker.md b/src/blog/2024/10/announcement-mqtt-broker.md index a08d9d1407..52541e1ec9 100644 --- a/src/blog/2024/10/announcement-mqtt-broker.md +++ b/src/blog/2024/10/announcement-mqtt-broker.md @@ -17,7 +17,7 @@ In our [recent product update](/blog/2024/10/flowfuse-release-2-10) we have adde -The MQTT Service is available now on [FlowFuse Cloud](/platform/cloud/). FlowFuse permits you to setup your own secure clients to begin publishing and subscribing to your own topics. +The MQTT Service is available now on [FlowFuse Cloud](https://app.flowfuse.com/account/create/). FlowFuse permits you to setup your own secure clients to begin publishing and subscribing to your own topics. You can now use FlowFuse to manage your own MQTT Clients alongside your Node-RED instances, making it easier to build full-stack, event-driven applications within FlowFuse. diff --git a/src/blog/2024/10/managing-node-red-instances-in-centralize-platfrom.md b/src/blog/2024/10/managing-node-red-instances-in-centralize-platfrom.md index a24731167d..3991367a23 100644 --- a/src/blog/2024/10/managing-node-red-instances-in-centralize-platfrom.md +++ b/src/blog/2024/10/managing-node-red-instances-in-centralize-platfrom.md @@ -57,7 +57,7 @@ With FlowFuse, you can organize your Node-RED instances into teams for improved ![Immersive Editor](./images/imersive-editor.png) *Image showing how FlowFuse's immersive editor simplifies managing settings and configuration within the Node-RED editor.* -FlowFuse also simplifies the [monitoring and controlling of edge devices](/solutions/edge-connectivity/) through the [FlowFuse Device Agent](/platform/device-agent/), which quickly connects your devices to the cloud platform and allows you to build and monitor applications remotely. +FlowFuse also simplifies the [monitoring and controlling of edge devices](/use-cases/edge-connectivity/) through the [FlowFuse Device Agent](/platform/device-agent/), which quickly connects your devices to the cloud platform and allows you to build and monitor applications remotely. ![Device Management](./images/devices.png) *Image showing remote edge devices connected through the FlowFuse platform for remote monitoring and control.* diff --git a/src/blog/2024/11/building-uns-with-flowfuse.md b/src/blog/2024/11/building-uns-with-flowfuse.md index 2a7faccb14..38f6773191 100644 --- a/src/blog/2024/11/building-uns-with-flowfuse.md +++ b/src/blog/2024/11/building-uns-with-flowfuse.md @@ -17,7 +17,7 @@ cta: description: FlowFuse brings together Node-RED, a built-in MQTT broker, and centralized device management, everything you need to connect your shop floor data into a single, real-time namespace. --- -As systems and devices become more connected, managing data from different sources can be tricky. A [Unified Namespace (UNS)](/solutions/uns/) solves this by centralizing all your data in one place, making it easy to access and use. +As systems and devices become more connected, managing data from different sources can be tricky. A [Unified Namespace (UNS)](/use-cases/uns/) solves this by centralizing all your data in one place, making it easy to access and use. diff --git a/src/blog/2024/12/why-uns-need-data-modeling.md b/src/blog/2024/12/why-uns-need-data-modeling.md index 072104f604..8ce61b6f53 100644 --- a/src/blog/2024/12/why-uns-need-data-modeling.md +++ b/src/blog/2024/12/why-uns-need-data-modeling.md @@ -16,7 +16,7 @@ cta: description: FlowFuse helps you connect, collect, transform, and visualize industrial data, with the data modeling tools you need to make your Unified Namespace actually work. --- -In manufacturing, data flows from various sources, machines, sensors, enterprise systems, and more. A [Unified Namespace (UNS)](/solutions/uns/) brings all this data into a central hub. However, centralizing data isn't enough to truly call it a UNS. It's not just about aggregating information. A true UNS goes beyond being a data repository; it organizes, structures, and contextualizes that data, transforming it into something valuable and actionable for your business. +In manufacturing, data flows from various sources, machines, sensors, enterprise systems, and more. A [Unified Namespace (UNS)](/use-cases/uns/) brings all this data into a central hub. However, centralizing data isn't enough to truly call it a UNS. It's not just about aggregating information. A true UNS goes beyond being a data repository; it organizes, structures, and contextualizes that data, transforming it into something valuable and actionable for your business. diff --git a/src/blog/2025/01/mqtt-frontrunner-for-uns.md b/src/blog/2025/01/mqtt-frontrunner-for-uns.md index 88b02900a9..e49e1edd1e 100644 --- a/src/blog/2025/01/mqtt-frontrunner-for-uns.md +++ b/src/blog/2025/01/mqtt-frontrunner-for-uns.md @@ -19,7 +19,7 @@ Choosing the right broker for your UNS is crucial. It must support real-time dat In this first part of our series, we’ll explain why MQTT is the standout choice for UNS implementations. With its focus on lightweight, real-time messaging and robust reliability, MQTT delivers the performance IIoT environments demand, making it the perfect fit for a future-proof, scalable UNS. -The [Unified Namespace (UNS)](/solutions/uns/) is a data architecture (not just a tool or new technology) that centralizes and organizes data from various sources into a single, unified structure. It eliminates data silos by providing a standardized way to represent, access, and share information across different devices, systems, and services. For more information on what is UNS, read our article: [Introduction to the Unified Namespace](/blog/2023/12/introduction-to-unified-namespace/). +The [Unified Namespace (UNS)](/use-cases/uns/) is a data architecture (not just a tool or new technology) that centralizes and organizes data from various sources into a single, unified structure. It eliminates data silos by providing a standardized way to represent, access, and share information across different devices, systems, and services. For more information on what is UNS, read our article: [Introduction to the Unified Namespace](/blog/2023/12/introduction-to-unified-namespace/). When choosing a broker for your UNS, it's crucial to consider how well the selected broker fits the specific requirements of your IIoT environment, including the types of devices and systems involved, as well as factors like scalability, reliability, and ease of integration. Several options are available alongside MQTT, including [AMQP](/node-red/protocol/amqp/), [Kafka](/blog/2024/03/using-kafka-with-node-red/), and cloud message brokers like AWS Kinesis and GCP Pub/Sub. While these alternatives offer unique features, MQTT stands out, and we’ll explain why later in this article. But If you’re interested in a brief overview of why these alternatives are not the best fit for UNS, check out our article: [Unified Namespace: What Broker to Use?](/blog/2024/01/unified-namespace-what-broker/) diff --git a/src/blog/2025/01/why-flowfuse-is-complete-toolkit-for-uns.md b/src/blog/2025/01/why-flowfuse-is-complete-toolkit-for-uns.md index 13c20cc186..e7116c191c 100644 --- a/src/blog/2025/01/why-flowfuse-is-complete-toolkit-for-uns.md +++ b/src/blog/2025/01/why-flowfuse-is-complete-toolkit-for-uns.md @@ -21,7 +21,7 @@ Unified Namespace (UNS) is changing the way data is managed in industrial enviro -At its core, a Unified Namespace ([UNS](/solutions/uns/)) is a data architecture that centralizes all your data from devices, sensors, and systems into a single hub. It helps you make sense of everything by organizing, structuring, and standardizing your data for easy access and analysis. Instead of dealing with fragmented data silos, you get a unified, real-time view of your entire operation. +At its core, a Unified Namespace ([UNS](/use-cases/uns/)) is a data architecture that centralizes all your data from devices, sensors, and systems into a single hub. It helps you make sense of everything by organizing, structuring, and standardizing your data for easy access and analysis. Instead of dealing with fragmented data silos, you get a unified, real-time view of your entire operation. Think of it as the brain of your entire operation, connecting all your business events in one place. Whether you're tracking performance, optimizing workflows, or making real-time decisions, a well-designed UNS makes it all possible. For more details, check out our article: [Introduction to the Unified Namespace](/blog/2023/12/introduction-to-unified-namespace/). diff --git a/src/blog/2025/06/what-is-mes.md b/src/blog/2025/06/what-is-mes.md index 7349614c36..62ed5f7b50 100644 --- a/src/blog/2025/06/what-is-mes.md +++ b/src/blog/2025/06/what-is-mes.md @@ -16,7 +16,7 @@ Running a factory means constantly pushing for better production. You want to ma -A [Manufacturing Execution System (MES)](/solutions/mes/) solves this. It's the central system that connects your factory's production to its plans. It gives you clear, instant visibility and control over every step on your shop floor. +A [Manufacturing Execution System (MES)](/use-cases/mes/) solves this. It's the central system that connects your factory's production to its plans. It gives you clear, instant visibility and control over every step on your shop floor. Whether you've managed factory operations for years or are just starting to understand how they work, the need for this kind of clarity is universal. @@ -44,7 +44,7 @@ It's easy to get confused about all the different computer systems in a factory. Many people think an MES is the same as their ERP system. But that's not quite right. Your ERP (Enterprise Resource Planning) handles the big company plans like money, sales orders, and buying materials for the long run. An MES doesn't do this planning. Its job is focused purely on the factory floor, managing what's happening right now to build products. It makes sure the production plans actually get done. -Another common confusion is that an MES is like a [SCADA](/solutions/scada/) or PLC system. Again, this isn't accurate. SCADA (Supervisory Control and Data Acquisition) and [PLC](/blog/2025/12/what-is-plc/) (Programmable Logic Controller) systems are connected directly to individual machines. They tell machines what to do, like turning them on or off, and collect basic data from them. An MES doesn't control machines directly. Instead, the MES acts like the main manager for the whole factory's production. It gathers information from those machine controllers (SCADA/PLCs) and uses it to oversee the entire process, including guiding workers, checking quality, and making sure all the machines work together to finish an order. +Another common confusion is that an MES is like a [SCADA](/use-cases/scada/) or PLC system. Again, this isn't accurate. SCADA (Supervisory Control and Data Acquisition) and [PLC](/blog/2025/12/what-is-plc/) (Programmable Logic Controller) systems are connected directly to individual machines. They tell machines what to do, like turning them on or off, and collect basic data from them. An MES doesn't control machines directly. Instead, the MES acts like the main manager for the whole factory's production. It gathers information from those machine controllers (SCADA/PLCs) and uses it to oversee the entire process, including guiding workers, checking quality, and making sure all the machines work together to finish an order. So, while ERP plans the business, and SCADA/PLC run the machines, the MES is the crucial system that manages the actual production process that happens in between. diff --git a/src/blog/2025/09/it-vs-ot-difference-between-information-technology-and-operational-technology.md b/src/blog/2025/09/it-vs-ot-difference-between-information-technology-and-operational-technology.md index 371490d309..d36645b27b 100644 --- a/src/blog/2025/09/it-vs-ot-difference-between-information-technology-and-operational-technology.md +++ b/src/blog/2025/09/it-vs-ot-difference-between-information-technology-and-operational-technology.md @@ -63,7 +63,7 @@ The defining characteristics of IT systems reflect their business-oriented natur Operational Technology refers to the hardware and software systems that monitor and control physical devices, processes, and infrastructure in industrial environments. OT directly manages your production operations, making it the backbone of manufacturing execution. -OT systems include Industrial Control Systems (ICS), which serve as the umbrella term for all control systems used in industrial operations. Within this category, you'll find [Supervisory Control and Data Acquisition (SCADA)](/solutions/scada/) systems that provide centralized monitoring and control, [Programmable Logic Controllers (PLCs)](/blog/2025/10/plc-to-mqtt-using-flowfuse/) that execute real-time control logic, and Distributed Control Systems (DCS) that manage complex continuous processes. [Human-Machine Interfaces (HMI)](/blog/2025/11/building-hmi-for-equipment-control/) provide operators with visualization and control capabilities, while Safety Instrumented Systems (SIS) protect people and equipment from hazardous conditions. Building Management Systems (BMS) and [Manufacturing Execution Systems (MES)](/solutions/mes/) round out the OT ecosystem. +OT systems include Industrial Control Systems (ICS), which serve as the umbrella term for all control systems used in industrial operations. Within this category, you'll find [Supervisory Control and Data Acquisition (SCADA)](/use-cases/scada/) systems that provide centralized monitoring and control, [Programmable Logic Controllers (PLCs)](/blog/2025/10/plc-to-mqtt-using-flowfuse/) that execute real-time control logic, and Distributed Control Systems (DCS) that manage complex continuous processes. [Human-Machine Interfaces (HMI)](/blog/2025/11/building-hmi-for-equipment-control/) provide operators with visualization and control capabilities, while Safety Instrumented Systems (SIS) protect people and equipment from hazardous conditions. Building Management Systems (BMS) and [Manufacturing Execution Systems (MES)](/use-cases/mes/) round out the OT ecosystem. The characteristics of OT systems stand in stark contrast to IT. OT prioritizes safety, availability, and reliability above everything else. These systems were historically air-gapped or completely isolated from external networks, receiving infrequent updates, often annually or only when absolutely necessary during planned shutdowns. OT environments rely on proprietary and industrial protocols like [Modbus](/node-red/protocol/modbus/), Profibus, [OPC-UA](/blog/2025/07/reading-and-writing-plc-data-using-opc-ua/), [EtherNet/IP](/blog/2025/10/using-ethernet-ip-with-flowfuse/), and DeviceNet rather than standard internet protocols. Equipment lifecycles stretch fifteen to twenty-five years in operation, designed for stability and deterministic performance rather than flexibility. In OT, downtime tolerance is essentially zero because every minute of stopped production directly costs money. Real-time processing happens in milliseconds, where timing precision can mean the difference between safe operation and catastrophic failure. @@ -176,7 +176,7 @@ OPC-UA (OLE for Process Control - Unified Architecture) represents a modern, sec EtherNet/IP adapts standard Ethernet and TCP/IP protocols for industrial automation, particularly in North American manufacturing. This protocol is common in discrete manufacturing, packaging, and material handling applications. DeviceNet provides a low-cost network for connecting simple industrial devices like sensors, motor starters, and actuators to PLCs and controllers. -The diversity of industrial protocols creates significant integration challenges. A single manufacturing facility might use half a dozen different protocols across equipment from various vendors and vintages. Protocol converters, gateways, and translation tools are often necessary to achieve connectivity, adding complexity and potential points of failure. This protocol fragmentation makes unified [IT/OT integration](/solutions/it-ot-middleware/) technically challenging and expensive. +The diversity of industrial protocols creates significant integration challenges. A single manufacturing facility might use half a dozen different protocols across equipment from various vendors and vintages. Protocol converters, gateways, and translation tools are often necessary to achieve connectivity, adding complexity and potential points of failure. This protocol fragmentation makes unified [IT/OT integration](/use-cases/it-ot-middleware/) technically challenging and expensive. ## The Organizational Challenge: Bridging IT and OT Teams diff --git a/src/blog/2025/12/what-is-mttf.md b/src/blog/2025/12/what-is-mttf.md index ad396c70e5..d58aeb4f3c 100644 --- a/src/blog/2025/12/what-is-mttf.md +++ b/src/blog/2025/12/what-is-mttf.md @@ -185,4 +185,4 @@ The math is straightforward: unplanned breakdowns cost 3-5x more than scheduled Your facility is unique. Your conditions, loads, and environment create a reliability profile unlike any other operation. The only MTTF numbers that truly matter are the ones you measure yourself. -As your equipment base grows, manual tracking becomes cumbersome. [FlowFuse](/) automates this by connecting to [PLCs](/blog/2025/12/what-is-plc/), [SCADA](/solutions/scada/) systems, [MES](/solutions/mes/) platforms, and your CMMS, pulling operating hours directly from equipment through industrial protocols like [Modbus](/node-red/protocol/modbus/), [OPC UA](/blog/2025/07/reading-and-writing-plc-data-using-opc-ua/), and [EtherNet/IP](/blog/2025/10/using-ethernet-ip-with-flowfuse/), then capturing failure events to recalculate MTTF in real-time across your entire facility. +As your equipment base grows, manual tracking becomes cumbersome. [FlowFuse](/) automates this by connecting to [PLCs](/blog/2025/12/what-is-plc/), [SCADA](/use-cases/scada/) systems, [MES](/use-cases/mes/) platforms, and your CMMS, pulling operating hours directly from equipment through industrial protocols like [Modbus](/node-red/protocol/modbus/), [OPC UA](/blog/2025/07/reading-and-writing-plc-data-using-opc-ua/), and [EtherNet/IP](/blog/2025/10/using-ethernet-ip-with-flowfuse/), then capturing failure events to recalculate MTTF in real-time across your entire facility. diff --git a/src/blog/2025/12/what-is-teep.md b/src/blog/2025/12/what-is-teep.md index 377574fa5d..18dec8a077 100644 --- a/src/blog/2025/12/what-is-teep.md +++ b/src/blog/2025/12/what-is-teep.md @@ -169,7 +169,7 @@ Companies that want accurate TEEP need good data collection systems. Writing dow The money spent on measurement systems should match decision-making needs. Companies making frequent capacity investment decisions benefit from real-time TEEP monitoring. Organizations with stable capacity and clear bottlenecks might find quarterly manual calculations work fine. -Building TEEP dashboards has become much simpler with modern tools. FlowFuse offers a practical solution for companies that want real-time equipment monitoring without complex programming. The platform bridges the gap between OT (Operational Technology) on the factory floor and IT systems in the office. It connects directly to your equipment, whether through [PLCs, SCADA systems](/solutions/scada/), or [machine controllers and MES platforms](/solutions/mes/), and creates visual dashboards that track performance metrics. You can see how straightforward the process is by looking at their [OEE dashboard blueprint](/blueprints/manufacturing/oee-dashboard/). The same approach works for TEEP, connect your data sources, set up the calculations, and view your equipment utilization in real-time. This makes professional-grade monitoring accessible even for smaller manufacturers or companies without dedicated programming staff. +Building TEEP dashboards has become much simpler with modern tools. FlowFuse offers a practical solution for companies that want real-time equipment monitoring without complex programming. The platform bridges the gap between OT (Operational Technology) on the factory floor and IT systems in the office. It connects directly to your equipment, whether through [PLCs, SCADA systems](/use-cases/scada/), or [machine controllers and MES platforms](/use-cases/mes/), and creates visual dashboards that track performance metrics. You can see how straightforward the process is by looking at their [OEE dashboard blueprint](/blueprints/manufacturing/oee-dashboard/). The same approach works for TEEP, connect your data sources, set up the calculations, and view your equipment utilization in real-time. This makes professional-grade monitoring accessible even for smaller manufacturers or companies without dedicated programming staff. ***Want to see how TEEP monitoring would work for your specific equipment and production environment? [Book a demo](/book-demo/) with FlowFuse to explore how you can track equipment utilization, identify capacity opportunities, and make data-driven decisions about your manufacturing assets.*** diff --git a/src/blog/2026/01/opcua-vs-mqtt.md b/src/blog/2026/01/opcua-vs-mqtt.md index a45d14b124..da65c5e38e 100644 --- a/src/blog/2026/01/opcua-vs-mqtt.md +++ b/src/blog/2026/01/opcua-vs-mqtt.md @@ -258,7 +258,7 @@ Work with your equipment, not against it. Siemens PLCs, Rockwell controllers, an Five hundred vibration sensors streaming to cloud storage align with MQTT's horizontal scaling through broker clusters. Fifty machines requiring discovered operations and validated method calls align with OPC UA's self-describing address spaces. Different problems, different optimal solutions. -For example, you're connecting 50 CNC machines, 500 environmental sensors, [MES](/solutions/mes/), predictive maintenance, and cloud analytics. +For example, you're connecting 50 CNC machines, 500 environmental sensors, [MES](/use-cases/mes/), predictive maintenance, and cloud analytics. ``` - Machines → Edge: OPC UA (semantic interoperability for production coordination) diff --git a/src/blog/2026/01/what-is-system-integrator.md b/src/blog/2026/01/what-is-system-integrator.md index 3d89d234fb..6914b787b4 100644 --- a/src/blog/2026/01/what-is-system-integrator.md +++ b/src/blog/2026/01/what-is-system-integrator.md @@ -100,7 +100,7 @@ System integration used to mean custom work every time. Integrators hard-coded p That approach no longer works. Industry 4.0 has changed manufacturing priorities. Data isn't just a byproduct of production: it's the foundation for optimization, predictive maintenance, and competitive advantage. Modern factories generate massive amounts of data, evolve quickly, and can't afford brittle, one-off integrations. -The industry is moving toward architectures like the [Unified Namespace (UNS)](/solutions/uns/). Instead of systems talking directly to each other, data flows to a central hub. A PLC publishes data once. MES, ERP, analytics platforms all subscribe to it. Add a new system, and it just subscribes. No rewiring. No breaking existing connections. +The industry is moving toward architectures like the [Unified Namespace (UNS)](/use-cases/uns/). Instead of systems talking directly to each other, data flows to a central hub. A PLC publishes data once. MES, ERP, analytics platforms all subscribe to it. Add a new system, and it just subscribes. No rewiring. No breaking existing connections. This shift demands different tools. Tools that support many protocols without custom drivers. Tools that are quick to understand and easy to maintain. Tools where you can see how data flows at a glance instead of digging through legacy code. diff --git a/src/blog/2026/02/what-is-event-driven-architecture-in-manufacturing.md b/src/blog/2026/02/what-is-event-driven-architecture-in-manufacturing.md index 0cfc05c32b..cf8feb754a 100644 --- a/src/blog/2026/02/what-is-event-driven-architecture-in-manufacturing.md +++ b/src/blog/2026/02/what-is-event-driven-architecture-in-manufacturing.md @@ -86,7 +86,7 @@ The factories pulling ahead right now aren't the most automated. They're the one ## What It Takes to Move to Event-Driven Architecture -The hardware is already there. Sensors, [PLCs](/blog/2025/12/what-is-plc/), [SCADA systems](/solutions/scada/). All running. EDA doesn't replace them. It changes how they communicate. +The hardware is already there. Sensors, [PLCs](/blog/2025/12/what-is-plc/), [SCADA systems](/use-cases/scada/). All running. EDA doesn't replace them. It changes how they communicate. You need an event broker and something that connects to legacy systems. [MQTT](/blog/2024/06/how-to-use-mqtt-in-node-red/) for shop floor devices. Kafka for enterprise loads. [Node-RED](/node-red/) to bridge the gap. That's the stack. @@ -96,7 +96,7 @@ Your team already knows which deviations matter. Which delays cascade. Which var Start where waiting costs the most. Downtime reported late doesn’t need better sensors. The stop event needs to fire when it happens and route to maintenance, scheduling, and analytics simultaneously. One workflow. Measured impact. Studies show event-driven systems responding in milliseconds rather than minutes, reducing manual intervention dramatically and improving process completion rates at scale. Prove it on one line, then expand to the next bottleneck. -The broker is straightforward. The translation layer isn't. Your [MES](/solutions/mes/) doesn't listen for events. Your [ERP](/blog/2025/06/connect-shop-floor-to-odoo-erp-flowfuse/) expects scheduled queries. Your quality system runs batch jobs. Bridging that gap is where real effort lives. +The broker is straightforward. The translation layer isn't. Your [MES](/use-cases/mes/) doesn't listen for events. Your [ERP](/blog/2025/06/connect-shop-floor-to-odoo-erp-flowfuse/) expects scheduled queries. Your quality system runs batch jobs. Bridging that gap is where real effort lives. Brownfield doesn’t require cutover. Legacy runs. New workflows build on events. Each migration reduces polling overhead and creates durable audit trails. Value compounds. diff --git a/src/blog/2026/04/rosetta-stone-for-industrial-data.md b/src/blog/2026/04/rosetta-stone-for-industrial-data.md index da9556b8bd..b2e3d469c3 100644 --- a/src/blog/2026/04/rosetta-stone-for-industrial-data.md +++ b/src/blog/2026/04/rosetta-stone-for-industrial-data.md @@ -79,7 +79,7 @@ What actually works is three things aligned together. **A reliable transport layer.** OPC-UA defines the vocabulary. [MQTT](/blog/2024/06/how-to-use-mqtt-in-node-red/) moves it. Lightweight, publish-subscribe, designed for the unreliable networks and constrained hardware that characterise real factory floors rather than data centre diagrams. Sparkplug B closes the gap that vanilla MQTT leaves open: without it, two systems both speaking MQTT can still be writing in different dialects. With it, every message has a predictable structure before you read a single byte of content. -**An architecture that removes the N² problem entirely.** The [Unified Namespace](/solutions/uns/) is what changes the geometry. Instead of bilateral connections between systems, every device and every application publishes to and subscribes from a single broker. The broker is the fixed reference point, the Rosetta Stone. Every system maps to it. Every system becomes readable to every other system, not because they were directly connected, but because they share the same anchor. +**An architecture that removes the N² problem entirely.** The [Unified Namespace](/use-cases/uns/) is what changes the geometry. Instead of bilateral connections between systems, every device and every application publishes to and subscribes from a single broker. The broker is the fixed reference point, the Rosetta Stone. Every system maps to it. Every system becomes readable to every other system, not because they were directly connected, but because they share the same anchor. !["Industrial data flow from PLC to analytics via MQTT broker"](./images/flowfuse-uns.png) _Industrial data flow from PLC to analytics via MQTT broker_ diff --git a/src/changelog/2023/10/certified-nodes.md b/src/changelog/2023/10/certified-nodes.md index ea2ef33a1c..b3526a7361 100644 --- a/src/changelog/2023/10/certified-nodes.md +++ b/src/changelog/2023/10/certified-nodes.md @@ -13,6 +13,6 @@ Teams Tier customers can now leverage a curated selection of certfied Node-RED n - Support: Assistance for certified nodes is provided, aiming for, but not promising, issue resolution. How? You can find all certified nodes in your Node-RED palette manager or on the -[dedicated page](/certified-nodes/) on our website. +[dedicated page](/integrations/?certified=1) on our website. ![Certified Nodes Screenshot](./images/certified-nodes.png) \ No newline at end of file