Namespaces
The Namespace Stops At The Plant Wall
Each plant, and often each line, builds a useful Unified Namespace (UNS) in Ignition. Without a layer above, those namespaces stay separate, and comparing plants means custom scripts and exports.
Fuuz + Ignition · Plant floor to enterprise
Run Every Ignition Gateway As One
Whether a plant runs one Ignition® Gateway or a hundred, Fuuz connects each one as a device, monitors them all, and gives the enterprise a single governed data layer on top. Keep Ignition where it is strong, at the plant and the line. Add Fuuz for everything above it.
Fuuz is the Industrial Operations Platform: one environment for data, applications and AI across every facility, so the entire enterprise can operate as one.
Reference architecture · Many gateways, one enterprise
One Enterprise Layer Above Every Plant And Gateway
One Fuuz enterprise
Applications, Level 3 and upExecution, warehouse, quality, maintenance and your own
Real-time reporting and analysisEvery plant on live data, in one model
AI agent access and APIModel Context Protocol and GraphQL, under each user's permissions
GovernanceRoles, policies and audit across every site
Enterprise Unified NamespacePlant and line topics, persisted in one governed data model
Plant 01 · Ignition
1 Ignition Gateway
Line and plant namespaces stay in Ignition
Fuuz GatewayGateway connects as a device
Plant 02 · Ignition
14 Ignition Gateways
Line and plant namespaces stay in Ignition
Fuuz GatewayEvery gateway connects as a device
Plant 03 · Ignition
100 Ignition Gateways
Line and plant namespaces stay in Ignition
Fuuz GatewayEvery gateway connects as a device
The gap
Your Gateways Aren't The Problem. The Gaps Between Them Are
Ignition does its job at the plant and the line. The gaps appear above it, as gateways multiply through growth and acquisitions.
Visibility
Nobody Sees The Whole Fleet
Status, health and data flow are checked one gateway at a time. At one gateway per plant that is manageable. At a hundred it is not.
Data
The Enterprise Needs One Model
Reporting, AI and enterprise applications need data in one governed model, not a hundred exports in a hundred shapes.
How it works
Connect What You Have. Unify It. Build On It
01
Connect every gateway
Install the Fuuz Ignition Module in each Ignition Gateway. It creates Fuuz subscriptions where the tag data lives, instead of polling from outside. Each gateway then connects to the Fuuz Gateway as a device. You browse and subscribe to tags and user-defined types (UDTs) natively, live values stream in as they change, and there is no added OPC layer to run or patch.
02
Unify across facilities
Plant and line topics roll up through the Fuuz Gateway into the enterprise Unified Namespace. The data is persisted in one governed model, not just passed through. Machine data joins work orders, lots, inventory and quality, and enterprise, site, area, line and cell are defined once.
03
Build above the plant
Build Level 3 and up applications on that model. Level 3 is the operations management layer of the ISA-95 standard. Use accelerators for manufacturing execution system (MES), warehouse management system (WMS), quality and maintenance, and connect enterprise resource planning (ERP) once, not once per plant.
Beyond the single gateway
From One Gateway To An Enterprise Stack
Elevate your MES from a single gateway to a modern, scalable enterprise stack that runs in Fuuz, right alongside Ignition. The same pattern repeats at every factory, and every factory feeds one Fuuz enterprise.
- MES, WMS, CMMS and more in one platform. Warehouse management, computerized maintenance management system (CMMS), quality and your own applications run on the same model and the same security.
- Deployments that stay simple. Operational apps change and evolve constantly, and Fuuz makes that painless compared to legacy products and stitched-together modules and solutions. Every customer gets Build, QA and Production environments, so changes follow one governed path.
- Bi-directional exchange of data. The Fuuz Ignition Module runs natively in Ignition, so data flows into Fuuz and back, with governed role-based access control (RBAC) delivered by the Fuuz platform.
- Operations separated from the SCADA layer. Interfaces and integrations live in Fuuz, not in the control gateway, for a secure, scalable solution across all your factories.
Two layers, one pattern
Fuuz · Operations layerOperations, interfaces and integrations: MES, WMS, CMMS and quality; ERP, EDI, carriers and partner systems; Build, QA and Production.
Fuuz Ignition ModuleDirect, bi-directional access. Runs natively in Ignition.
Ignition · SCADA layerControl, tags and the plant network: tags and UDTs, alarms, PLCs and devices, screens.
One place to watch
Monitor Every Gateway From One Screen
Each Ignition Gateway is a device in Fuuz, so the whole fleet is visible in one application, with the same permissions as everything else.
- See connection state for every gateway, across every plant.
- Keep data through drops. The Fuuz Gateway buffers locally and forwards when the connection returns. Expect 4 or more hours of buffering in a hybrid deployment, depending on implementation.
- Open no inbound ports. The gateway reaches out to the platform, so your network team is not asked to open the firewall.
Illustration with sample data · 6 gateways: 4 connected, 1 buffering, 1 offline
p01-line-1 · Plant 01Connected · 18,420 tags · last value 0.4 s ago
p01-line-2 · Plant 01Connected · 17,905 tags · last value 0.6 s ago
p02-packaging · Plant 02Buffering · 9,310 tags · last value 2 min ago
p02-utilities · Plant 02Connected · 4,220 tags · last value 0.9 s ago
p03-site · Plant 03Connected · 31,870 tags · last value 0.3 s ago
p03-warehouse · Plant 03Offline · 6,540 tags · last value 14 min ago
The Fuuz Ignition Module
Native In The Gateway. Four Jobs, One Module
A native Ignition module that installs into the gateway you already run. It is not a bolt-on appliance, and it is not a separate server to deploy at every site.
Connect
Access operational data
- Native tag and UDT browsing, with no separate tag database to maintain
- Real-time subscriptions: live values stream in as they change
- No added OPC layer: connects into the gateway you already run
Contextualize
Add manufacturing meaning
- Manufacturing models: work orders, lots, equipment and quality objects come modeled
- Automatic normalization of inconsistent tag data, without custom scripting
- Machine data joins work orders, inventory and quality records
Automate
Execute business logic
- Trigger the same low-code data flow engine that runs the rest of Fuuz
- Alarms, thresholds and state changes fire approvals, holds, escalations and notifications
- Ignition builders keep authoring logic visually
Integrate
Enterprise connectivity and UNS
- Pre-built enterprise connectivity, without point-to-point interfaces per site
- Native industrial drivers through the Fuuz Gateway: OPC UA, Modbus, EtherNet/IP, Sparkplug, S7, FOCAS and MQTT
- Build an integration once and reuse it at every plant running Ignition
The enterprise layer
Give IT The Guardrails. Give Every Plant The Data
Once every gateway feeds one governed model, three things become possible that no single gateway can offer.
Reporting
Real-Time Enterprise Reporting
Compare plants, lines and assets on live data across facilities, with no export pipeline between them. Analytics tools and dashboards read the same model the applications use.
AI
MCP Tool Access For AI Agents
The Fuuz Model Context Protocol (MCP) server lets agents query governed data and use tools under each user's permissions. Typed relationships mean agents follow real connections instead of guessing how records relate. One GraphQL API reaches the same data. Run MCP against all of your Ignition gateways from one connection to Fuuz.
Applications
Level 3 And Up, Across The Stack
Build and run operations applications that span every plant and every system, from accelerators you configure and extend. Applications can read from Ignition, from ERP, or from both, in one model.
Governance
Controls That Reach Every Gateway
Gateway-to-gateway
Outbound-only connections. Never cloud-direct to the shop floor.
Role-based access
Access controls reach down to individual UNS topics, with policy-based data sharing.
Full audit trail
Who changed what and when, with before and after values.
SOC 2 Type 2
Audited controls, with reports available under NDA from the trust center.
Who it is for
One Foundation. Four Teams Who Use It
IT leaders
Govern without the sprawl
One place to secure, monitor and audit every gateway, connection, user and agent.
Controls engineers
Keep building in Ignition
Your projects, screens and tag logic stay in place. Fuuz adds the layer above them.
Plant managers
Machine data with context
Line data arrives with the asset, order and lot attached, so questions get answered in the application.
Data and AI teams
Ready for analytics and agents
Modeled, contextualized data with one API and governed MCP access. No bespoke export pipeline.
With Fuuz, Ignition no longer has to carry the lift of everything it was not designed to do.
Working alongside Ignition
The Layer Above
Ignition connects to your industrial equipment and helps you organize that data locally. Fuuz takes it the rest of the way.
Your Ignition projects, screens and tag logic stay in place. Fuuz is the enterprise layer above them.
Keep and add
Stays in IgnitionProjects, screens, tag logic, alarms and control
Added by FuuzEnterprise Unified Namespace, governance, reporting, applications and AI access
Proven at scale
Running In Production Worldwide
750+
Global cloud instances
Cloud instances running Fuuz today.
10 years
In the market
A decade of industrial software behind every release.
Questions
Ignition And Fuuz, Answered
Does Fuuz replace Ignition?
No. Ignition stays in place for plant-level work. Fuuz connects to your Ignition Gateways and adds an enterprise data layer, governance, reporting and applications above them.
Can we run MES, WMS and CMMS in Fuuz and keep Ignition for SCADA?
Yes. Ignition keeps the supervisory control and data acquisition (SCADA) layer. Operations applications, interfaces and integrations run in Fuuz, which includes Build, QA and Production environments. The Fuuz Ignition Module, running natively in Ignition, gives Fuuz direct, bi-directional access to the SCADA network.
How does an Ignition Gateway connect to Fuuz?
The Fuuz Ignition Module installs inside the Ignition Gateway and creates Fuuz subscriptions where the tag data lives, instead of polling from outside. The gateway then connects to the Fuuz Gateway as a device, and its data flows into the enterprise Unified Namespace.
How many gateways can one plant connect?
Plants differ. Whether a plant runs one Ignition Gateway or a hundred, each one connects as a device to the Fuuz Gateway, and all of them are monitored from one place.
What happens to plant data if the network goes down?
The Fuuz Gateway buffers data locally and forwards it when the connection returns, so a network drop does not become lost data. Expect 4 or more hours of buffering in a hybrid deployment, though the exact time depends on your implementation.
Can we start with one plant?
Yes. Most enterprises start with one site, then roll out. The enterprise layer is built for many sites from day one, so plant two reuses everything plant one built.
Get started
Start With One Gateway. Scale To The Enterprise
Tell us what you run today and what you need next. We will map how Fuuz fits above your Ignition foundation, without ripping anything out.
Prefer to talk? Call 1-877-801-FUUZ (3889)
Ignition is a registered trademark of Inductive Automation. Shown to illustrate connector compatibility only. Plant names, gateway names and values in the illustrations are invented.