Accelerator · Installs into a tenant
A Production Execution Backbone You Can Actually Read
The MES Accelerator ships work order dispatch, Control Panel execution, quality checks and full genealogy as one installable package. This publication unpacks it into its 18 modules, so every flow, screen and model can be reviewed and diffed before a single thing is installed.
What it does
Workunit-Centric By Design
Every production event ties to a Workunit — a specific machine or station — rather than a generic line.
Work order dispatch
A WorkOrder is broken into WorkOrderProcess and WorkOrderProcessDistribution records, dispatched to a configured Workunit per the Product Strategy.
Control Panel execution
Operators run production against a Workunit. Production Setup records stage what the unit is currently set up to build; PLC codes for production, idle, disabled and maintenance states are configured per unit.
Quality in the run
Quality Specifications scoped to a product, process or step are presented at the Control Panel. Results land on a Quality Report, and a check can be flagged to block production until it is done.
Genealogy that is never implicit
Production History, Production History Data and Operator History record what happened, on what unit, by whom — with container and kit-of-parts content traced through.
Exceptions from the floor
Defects, Deviations and Andon Requests can be raised at any point in a run, classified by configurable severity and type.
Adjacent accelerators
Packaged MES_WMS Inventory, MES_WMS Material Replenishment and MES_CMMS_Request flows connect a WMS and a CMMS without custom integration work.
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 |
|---|---|---|
configuration | 2 | 2 screens |
controlPanels | 13 | 4 dataFlows · 9 screens |
employees | 2 | 2 screens |
engineering | 1 | 1 dataFlows |
genealogyTracking | 2 | 2 screens |
integration | 3 | 3 dataFlows |
manufacturing | 17 | 5 dataFlows · 12 screens |
orchestration | 1 | 1 dataFlows |
productConfiguration | 6 | 6 screens |
productDataManagement | 10 | 3 dataFlows · 7 screens |
quality | 13 | 3 dataFlows · 10 screens |
resources | 3 | 2 dataFlows · 1 screens |
scheduling | 1 | 1 screens |
testing | 3 | 3 screens |
wipDashboard | 1 | 1 screens |
workOrderManagement | 7 | 3 dataFlows · 4 screens |
workOrderUtilities | 1 | 1 dataFlows |
workunits | 9 | 3 dataFlows · 6 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.
Configure before you run
This package ships no seeded status or reference data — Work Order Status, Container Status, Defect Severity and Type, Deviation Type, Kanban Status and Location Status are all empty on install. Every tenant defines its own set before go-live. The Setup & Configuration Guide walks the sequence.
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.