GET STARTED

One question.
One useful first step.

A connected factory starts with a question people need answered. Explore the idea, plan a small pilot with your team, or try the software with simulated machines.

01 / UNDERSTAND

See what a UNS changes

Follow a shift utilisation question from disconnected records to shared data. No software setup needed.

Explore the idea →02 / PLAN

Choose a first use

Agree a useful question, the signals it needs, and who will own the result.

Plan a pilot →03 / TRY

Run simulated machine data

For an engineer with Docker, Git, and an MQTT broker. Start the sample capture pipeline and read its JSON output.

Open the quick start →

PLAN A PILOT

Make the first result specific.

Pick a question. For example: how long was CNC-01 running last shift? Agree how you will use the answer.
Agree the meaning. Define “running,” the shift boundary, and how to handle missing data with the people who use the machine.
Choose one source. Identify the signal, its owner, and a way to collect it. Compare the result with an observation or an existing record.
Assign ownership. Name who connects the equipment, manages the software, and checks the result. Expand after the first use is trusted.

Plan the team →Explore connection options →Describe your first machine →

WHAT YOU WILL FIND HERE

The description and the software.

UNS Framework is an open standard for describing your factory and its data in YAML files. fn-uns is a working implementation with components for capturing signals, keeping history, and calculating production metrics. fnkit is the tooling used to build and deploy those components.