Architecture and deployment

Enterprise Architecture From The Edge To The Cloud

Fuuz runs in full cloud, two-tier or three-tier deployments. Every Fuuz-hosted environment runs on AWS, in public cloud, private cloud or GovCloud, depending on what your business needs. Or host the Fuuz platform yourself, on any cloud or your own infrastructure. Every option runs the same platform and applications, from one site to an entire enterprise.

Deployment options

Deploy Fuuz The Way Your Enterprise Runs

Every option runs the same platform and applications, and every deployment includes build, QA and production environments. Choose how your sites connect, then choose Fuuz-hosted on AWS or self-hosted for each tier.

Data connectionFuuz-to-Fuuz syncFuuz drives or controlsFuuz GatewayOptional

Option 1

Full cloud

Fuuz-hosted on AWS, or self-hosted on any cloud or your own infrastructure

Fuuz runs as one enterprise that people, sites and business systems connect to directly.

  • Hosting: Fuuz-hosted on AWS (public cloud, private cloud or GovCloud), or self-hosted on any cloud or your own infrastructure
  • Gateway: not required; add one when integrations run inside your network
  • Structure: one Fuuz enterprise
ENTERPRISE SYSTEMSFUUZYOUR SITESPLANT FLOORERPCloud and SaaS appsData platformsFuuz enterpriseBuild · QA · productionPeople and devicesBrowsers, tablets, scannersFuuz GatewayOnly if neededEquipment and on-prem systemsAPIAPIHTTPSoutbound only

Option 2

Two-tier

Fuuz-hosted on AWS, or self-hosted, with gateways at your sites

Fuuz Gateways at each site connect equipment and on-premises systems and feed one Fuuz enterprise shared by every site.

  • Hosting: Fuuz-hosted on AWS (public cloud, private cloud or GovCloud), or self-hosted on any cloud or your own infrastructure
  • Gateway: Fuuz Gateways on premises at each site (common, not required); topics on edge connections form a local UNS that is visible in the Fuuz enterprise
  • Structure: many gateways feeding one Fuuz enterprise
  • Offline: gateways buffer data locally; expect 4+ hours, depending on implementation
ENTERPRISE SYSTEMSFUUZEDGE TIERPLANT FLOORERPCloud and SaaS appsFuuz enterpriseOne enterprise shared by every siteFuuz GatewaySite 1Fuuz GatewaySite 2Fuuz GatewaySite NEquipmentSite 1EquipmentSite 2EquipmentSite NAPIAPIstore and forwardoutbound onlyOPC UAMQTTModbus

Option 3

Three-tier

Fuuz-hosted on AWS, self-hosted on any cloud or your own infrastructure, or a mix

Each plant or warehouse runs its own Fuuz enterprise in the site tier, fed by gateways in the edge tier. Site-tier enterprises roll up to a Fuuz enterprise in the central tier. Every tier runs the same platform.

  • Hosting: any tier can be Fuuz-hosted on AWS or self-hosted on any cloud or your own infrastructure
  • Gateway: one or more per site (common, not required)
  • Structure: edge tier (gateways), site tier (a Fuuz enterprise per site), central tier (one Fuuz enterprise)
  • Offline: each site runs on its own for as long as it needs, then synchronizes
ENTERPRISE SYSTEMSCENTRAL TIERSITE TIEREDGE TIERPLANT FLOORERPPLMAnalytics and BICentral Fuuz enterpriseEnterprise model · cross-site reportingSite 1Fuuz enterpriseSite 2Fuuz enterpriseSite NFuuz enterpriseFuuz GatewaysSite 1Fuuz GatewaysSite 2Fuuz GatewaysSite NEquipmentSite 1EquipmentSite 2EquipmentSite NAPIsyncsyncsync

Reference deployment architecture

How The Tiers Fit Together

A closer look at the three and two-tier options: what runs in each layer, and how the layers connect. Site and gateway names are examples.

Three-tier

Three-tier reference deployment

An enterprise layer in a private cloud, a site layer with an application gateway installed per site, and edge gateways line-side. Each site keeps local control of its critical operational applications, and the sites connect up to the enterprise layer over HTTPS through a site-to-site VPN.

TIER 1 · ENTERPRISE LAYERFuuz Enterprise HubPrivate cloudGovernance & policyERP integrationSAP · Oracle · QADMulti-site analyticsCross-plantaggregationIT appsCRM · RMA · SalesTIER 2 · SITE LAYERApplication gatewayInstalled centrally per siteLocal control of criticaloperational applicationsSITE A · CEDAR RAPIDSSchedulingWork orders · ShiftplansProductionDock-to-dock ·Line OEEQualityInspections ·NCRsInventoryMaterial · BinlocationsSITE B · FOLEYSchedulingWork orders · ShiftplansProductionDock-to-dock ·Line OEEMaintenanceWork orders ·MTBFTrack & TraceGenealogy · SerialtrackSITE C · TROYSchedulingWork orders · ShiftplansProductionDock-to-dock ·Line OEEShippingLabels · ASN ·OutboundReceivingPO match · DockdoorsTIER 3 · EDGE LAYEREdge gatewayLine-side or edge installationTime-sensitive andsecurity-critical connectivitySITE A · CEDAR RAPIDSCedar RapidsGW-01Line 1 PLCsSensors · RoboticsCedar RapidsGW-02Line 2 PLCsSCADA historianconnectivitySITE B · FOLEYFoley GW-01Paint Line 1Foley GW-02Paint Line 2Foley GW-03PLCs · RecipeConfigurationCycle trackingSITE C · TROYTroy GW-01Assembly · WeldingConveyorsTroy GW-02AGV · Scanners · QCAutomated labelingHTTPS traffic over site-to-site VPNInternal network · DMZ
Fuuz applicationsFuuz GatewayTwo-way connectionSite footprint

Two-tier

Two-tier reference deployment

The enterprise layer runs the enterprise apps and every site's applications, and edge gateways connect each site's equipment to it over HTTPS through a site-to-site VPN. Fewer layers to operate on the same platform.

TIER 1 · ENTERPRISE LAYERFuuz Enterprise HubPrivate cloudEnterprise apps and everysite's applicationsENTERPRISE APPSGovernance & policyERP integrationSAP · Oracle · QADMulti-site analyticsCross-plantaggregationIT appsCRM · RMA · SalesSITE A · CEDAR RAPIDSSchedulingWork orders · ShiftplansProductionDock-to-dock ·Line OEEQualityInspections ·NCRsInventoryMaterial · BinlocationsSITE B · FOLEYSchedulingWork orders · ShiftplansProductionDock-to-dock ·Line OEEMaintenanceWork orders ·MTBFTrack & TraceGenealogy · SerialtrackSITE C · TROYSchedulingWork orders · ShiftplansProductionDock-to-dock ·Line OEEShippingLabels · ASN ·OutboundReceivingPO match · DockdoorsTIER 2 · EDGE LAYEREdge gatewayCentralized, line-side oredge installationTime-sensitive andsecurity-critical connectivitySITE A · CEDAR RAPIDSCedar RapidsGW-01Line 1 PLCsSensors · RoboticsCedar RapidsGW-02Line 2 PLCsSCADA historianconnectivitySITE B · FOLEYFoley GW-01Paint Line 1Foley GW-02Paint Line 2Foley GW-03PLCs · RecipeConfigurationCycle trackingSITE C · TROYTroy GW-01Assembly · WeldingConveyorsTroy GW-02AGV · Scanners · QCAutomated labelingHTTPS traffic over site-to-site VPN
Fuuz applicationsFuuz GatewayTwo-way connectionSite footprint

Fuuz-hosted on AWS

Every Fuuz-Hosted Environment Runs On AWS

AWS public cloud

Fuuz-hosted in AWS public cloud and run by Fuuz, with nothing for your team to host.

AWS private cloud

Fuuz-hosted in an AWS private cloud environment, run by Fuuz, when your needs call for a private deployment.

AWS GovCloud

Fuuz-hosted in AWS GovCloud for customers with U.S. government and other regulated requirements. Compliance follows a shared responsibility model.

Prefer to run it yourself? You can host the Fuuz platform on any cloud or on your own infrastructure instead. It is the same platform either way.

Hosting

Fuuz-Hosted Or Self-Hosted On Your Terms

Every tier of every option can be Fuuz-hosted on AWS or hosted by you, on any cloud or on your own infrastructure. Here is what changes.

Self-hosted: any cloud or your own infrastructure

  • You host and operate the infrastructure
  • You apply platform updates and patches
  • You monitor security and resources
  • Fuuz service level agreements do not apply

Fuuz-hosted (AWS public, private or GovCloud)

  • Hosted on AWS: public cloud, private cloud or GovCloud
  • Updates and patches delivered by Fuuz
  • The latest updates and enhancements arrive nightly in your build environment
  • Production environments are updated monthly
  • Security monitoring, resource monitoring and optimization
  • Fuuz service level agreements and premium support options

Included in every deployment

Same Platform, Same Discipline

Build, QA and production

Every deployment includes build, QA and production environments, so every change follows the same governed path. Additional build or QA environments are optional.

Self-updating gateways

Fuuz Gateways support automatic updates, so edge connectivity stays current without site visits.

Scale by adding sites

Add gateways to a Fuuz enterprise, or add sites to the site tier of a three-tier deployment, as the business grows.

Layers

How The Platform Is Built

Edge

The Fuuz Gateway connects equipment with outbound connections only and buffers through network drops.

Platform

Event-native services, the data store, modeling, ORM and the GraphQL API.

Applications

Accelerators and the applications you build, all reading from one model.

People and agents

Users and AI agents on any modern browser, governed by one access model.

How do these layers line up with the new industrial AI stack? See where Fuuz fits.

Isolation by design

Your Data Stays Yours

Fuuz does not put every customer's data in one shared database. Your enterprise has its own database and its own services for your applications and data, and a shared service layer provides the platform features everyone uses. We call this the Enterprise Mesh architecture: the scale of the cloud, with your data kept separate from everyone else's.

Inside your enterprise, data is organized in four levels. The application is the isolation boundary: each one has its own data, so a plant, a facility or a function stays separate from the next. The custom fields, tables, screens and workflows you build belong to your enterprise and do not change anything for other customers.

  • Your own database per enterprise, never mixed with other customers' data
  • Applications as the data isolation boundary, usually one per site or function
  • Build, QA and Production environments, each a complete instance
  • Access types and roles control who can see and do what in each application
  • Applications were called tenants in some older material

Four levels

EnterpriseYour top-level boundary, with its own address.
OrganizationGroups business units, campuses or regions.
ApplicationThe data isolation boundary, typically a site, facility or functional area.
EnvironmentBuild, QA or Production: a full instance for each stage.

Structure it your way

Shape The Enterprise To Fit The Business

The same four levels fit very different companies. Here are three common ways customers organize them.

A regional manufacturer

One enterprise, with an organization for each region and each plant as its own application. Regional managers oversee several facilities while each plant's data stays isolated.

A diversified industrial company

A separate enterprise for each business unit, so divisions run independently with their own IT management, with organizations and applications arranged inside each one.

A single site

One enterprise and one campus, with separate applications for the production floor, quality lab, warehouse, maintenance and an employee portal, so access can be set function by function.

Share on purpose

Isolated By Default. Connected When You Choose

Applications are fully isolated until you decide otherwise. When you want a wider view, you build it deliberately, with data flows and shared applications.

A shared data model

A dedicated application holds common data, such as products or customers, for other applications to use.

Roll-ups by region

An application gathers data from the plants in an organization for regional reporting.

One enterprise view

An enterprise-wide application consolidates every organization for executive dashboards and corporate analytics.

Complete isolation

Keep every application separate with no sharing, which maximizes separation and keeps access control simple.

Designing how data is shared takes thought about the people and developers who will use it. Your implementation partner or the Fuuz team can help, and the Governance and security page covers the controls that apply across every level.

Built to scale

One Site Or Hundreds

Isolation per enterprise

Each enterprise has its own database, and each application has its own data model, so your data is never mixed with other customers'.

Always current when Fuuz-hosted

Fuuz-hosted build environments receive the latest updates nightly, and production is updated monthly, without upgrade projects.

Nothing to install

Applications run in current versions of Chrome, Edge, Firefox and Safari.

Get started

Ready To Run Every Operation As One?

Tell us what you run today and what you need next. We will map how Fuuz fits, without ripping anything out.

Prefer to talk? Call 1-877-801-FUUZ (3889)