Bring your signals together.
Collect machine states, counts, and measurements from equipment. Start with the signals needed to answer one useful question.
OPEN INFRASTRUCTURE / REAL-WORLD DATA
The factory floor.
Connected.
Know what is running, where time is lost, and how production is progressing. Bring machine data and business systems together through a Unified Namespace: one shared structure for your factory data.
OPEN SOURCESELF-HOSTEDVENDOR-NEUTRAL
UNS / SYSTEM OVERVIEW01—03
Physical machines. Shared digital context.MQTT / ISA-95
PUT THE DATA TO WORK
Built for the people
who keep things moving.
Choose a question your team needs to answer. These are examples of what you can build as you connect and validate the relevant data.
01 / OPERATIONS
See your shop floor.
Machine states, production progress, and stoppages in one operational view.
See the implementation ↗02 / ENGINEERINGKeep the whole story.
Capture events with their timestamps and context. Trace a signal from the machine to the historian.
See the implementation ↗03 / ANALYSISGive AI real context.
Use structured manufacturing data for anomaly detection, shift summaries, and contextual analysis.
See the implementation ↗01 / THE IDEA
Connect once.
Build from there.
A Unified Namespace is a shared, structured data layer for your factory. Machines publish what happens. Other systems subscribe to what they need.
Understand the UNS →Give every signal a place.
Agree where each signal belongs and what it means, from the site down to the machine. Give every team the same names and context.
Let your systems share it.
Use that data in dashboards, production reports, and analysis. Add new uses without asking people to assemble the same exports again.
THE PIPELINE / FROM SIGNAL TO INSIGHT
One connection.
A whole world of context.
Machines publish. Functions process. Dashboards, systems, and AI work from the same structured data. Follow the connections through a reference architecture.
02 / THE TOOLKIT
An open standard.
A working starting point.
The framework describes your factory. The fn-uns implementation shows how to use that description. Its deployment tool, fnkit, is for the team running the software.
01 / DEFINE
UNS Framework
The open standard. YAML definitions, topic hierarchy, and conventions for manufacturing data.
↗02 / BUILDfn-uns
The reference implementation. A pipeline from machine simulation to history, KPIs, and AI analysis.
↗03 / RUNfnkit
The functions platform. Run Go, Node.js, or Python in containers on your own infrastructure.
↗STRUCTURE IS THE STARTING POINT
Raw signals.
Real context.
A value means more when you know where it came from. The framework gives your data a consistent address, from the site down to the equipment.
See a complete example →THE NAMESPACEISA-95 / EXAMPLE
v1.0└─ sheffield └─ machining └─ line-01 └─ cell-01 └─ cnc-01 └─ state → running
Every signal has a place.
Every system gets the same context.
Every system gets the same context.
START WITH ONE CONNECTION