Manufacturing data is trapped. We fix that. A YAML standard for describing your factory, serverless functions for computing KPIs, and an open platform to run it all. Three open-source projects that give every machine on your shop floor a voice.
An open standard for structuring manufacturing data, an open platform for deploying serverless functions, and a reference implementation that brings them together.
An open standard that defines how to structure manufacturing data in MQTT using YAML files. ISA-95 topic hierarchy, versioned namespaces, payload conventions, and best practices. Vendor-neutral — any system that follows the standard can participate.
A lightweight Functions-as-a-Service platform that runs anywhere Containers run. Write functions in any language — Go, Node.js, Python — scaffold with one command, deploy via git push. No cloud vendor required.
Serverless functions that implement a complete UNS data pipeline on fnkit. From machine simulation to KPI computation — capture, process, and report on manufacturing data using the UNS Framework standard.
The UNS Framework is an open-source initiative that offers a technically-driven approach to MQTT and Unified Namespace through the use of YAML files. Inspired by standards like Docker and Kubernetes, it establishes a universal standard that is both human-readable and machine-readable.
It is not a software product but a descriptive standard that seamlessly integrates with any new or existing UNS deployments. It complements existing standards like Sparkplug, OPC/UA, and MT Connect by focusing on describing what you have.
By articulating your UNS with the framework, you enable seamless integration across documentation, applications, analytics, security tools, and AI systems.
The UNS Framework configuration encompasses sites, areas, lines, cells, equipment, sensors, functions, producers, consumers, MQTT brokers, and databases.
Every data point follows the ISA-95 standard. Any consumer can parse the topic path to understand where data comes from — no mapping tables or documentation required.
Read the standard, explore the YAML definitions, or dive straight into the fn-uns reference implementation with real serverless functions.