DOCUMENTATION
Find what you need to build.
Use the standard to describe your data, the implementation docs to run fn-uns, and the guides to connect equipment and plan the work.
Describe your factory
Definitions, examples, and a common structure for equipment and signals.
Read the standard →IMPLEMENTATIONTry the data pipeline
Run simulated machines and verify that their data reaches the cache.
Run the sample →GUIDESPlan and connect
Team planning, hardware setup, data modelling, and implementation choices.
Choose a guide →Common tasks
Where fn-uns fits
fn-uns is the reference implementation used in these docs. Its components collect machine signals, store current values and history, and serve results to dashboards and other applications. It uses fnkit to package and deploy the software. For a walkthrough of what it provides, explore the implementation.
How the implementation fits together
Capture signals through MQTT, process them into records, then use those records for metrics and analysis. The diagram shows the reference architecture; the architecture reference explains the shared services and deployment model.
Component reference
There are 12 documented components, including the dashboard and optional AI analysis. Start with the sample capture pipeline, then add the components your use case needs. Compare their roles and dependencies.