Accelerator · Installs into a tenant
The Connection Layer, Made Legible
The Integration Orchestrator is how a Fuuz tenant talks to what is around it — other tenants, an ERP, a host MES. It is deliberately small: six data models and four flows that give every other accelerator somewhere to send data, rather than each one growing its own integration.
What it does
Small On Purpose, Shared By Everything
One module, and the reason the MES and WMS accelerators do not each carry their own connection code.
Cross-tenant movement
Move records between Fuuz tenants without either side needing bespoke flows.
External systems
The touchpoint for an ERP, a host MES or a CMMS — configured rather than coded per connection.
Shared by the accelerators
MES ships MES_WMS and MES_CMMS_Request flows that assume this orchestrator is where connections are built out.
Readable by design
Nine components in total. Small enough that the whole integration surface can be read in a sitting.
Modules
Published As Components, Not A Blob
A .fuuz package is a single archive. This publication unpacks it
into one directory per module, so a change to a flow reads as a change to a flow.
| Module | Components | Contains |
|---|---|---|
integration | 9 | 4 dataFlows · 5 screens |
Why some components sit outside modules/
Only data flows and screens carry a module in the package. Data models, document designs and seed data carry none, so they are filed by type at the repository root rather than assigned to a module on a guess.
Documentation
Read It Before You Install
Shipped with the accelerator, converted to markdown in the repository.
Technical Overview
What it is and is not, the core design, and what ships — at a glance.
Setup & Configuration Guide
Step-by-step configuration in a tenant where the package is installed.
AS IS Build Reference
Architecture, functional-area map and the flow pattern the package follows.
The modules
Every flow, screen and model as committed JSON — the reference that cannot go stale.
Where connections belong
MES and WMS ship touchpoints — packaged flows that hand off to an adjacent accelerator. Building the connection itself out to an external system is this orchestrator's job, which is why the touchpoint flows are thin.
Before you install
A Jump Start, Not A Finished Answer
An accelerator is a pre-built, configurable starting point that addresses the bulk of the common challenges in its domain. It is not intended to solve every possible variation off the shelf — requirements that fall outside it are expected and normal for the model, not a shortcoming of this one.
Standard
Delivered and working as-is. No configuration needed.
Configurable
A base capability you adapt with the platform's own no-code and low-code tools — screen builder, transforms, workflow rules, flow parameters — without professional services.
Custom development
Feasible on the platform but outside this accelerator's current scope. A scoped change through Fuuz or a certified partner.
Once installed, it is yours
Installation forks the flows, models and screens into your environment as your own copies. Later versions published against this accelerator do not propagate to you automatically — picking up a change means deliberately re-applying it.