Use case · Factory floor

Factory floor displays, built by your agent

Sam is a controls engineer. In Claude Code, one request turns production data into a live Line 3 board, publishes it to the floor displays and keeps it current. Every version is a release, so rolling back takes one sentence.

Set up your agentGet a Demo →

Watch the factory floor film

01Watch

2:00

Film / Factory floor

2:00

A fictional plant with sample production data, run from Claude Code on Raspberry Pi floor displays.

02Walk-through

A live andon board for Line 3

The demo, scene by scene. Sam asks for the board in plain words; Claude writes it, publishes it and keeps the numbers moving.

  1. 01

    The Line 3 board

    Output 412 of a 450 target, 41 days since the last incident, and a red andon tile: “Station 6 — waiting on material 04:12.”

  2. 02

    The old way

    BI dashboards on TVs fall back to a login screen, and the whiteboard is stale by second shift.

  3. 03

    One request

    In Claude Code, Sam writes: “Build a line board from our production data: output versus target, downtime, days since incident. Put it on the Line 3 screens and keep it current.”

  4. 04

    Built, published, verified

    Claude fetches the data, builds the board and publishes it, then returns a screenshot of the board on the floor. The numbers keep moving as Claude refreshes them.

03Applications

Build software, put it on a screen

The Line 3 board is a real application, not a screenshot of a dashboard. Every version your agent ships is its own release.

  1. 05

    A real application

    The board runs as a packaged web application on the floor displays, and each version is an immutable release.

  2. 06

    Roll back in one sentence

    “Roll Line 3 back to yesterday’s board.” The Line 3 screens return to the previous release.

04Features

Factory floor display features

More of what a plant runs from its agent.

  • Raspberry Pi and Linux kiosk install

    Kiosk mode starts the Player at boot and restarts it if it exits.

  • App releases with rollback

    Every version is its own release; moving back is one request.

  • Timed takeovers for shift briefings

    Put the briefing on every floor screen, then return to the boards.

  • Offline and health alerts with remote reboot

    Know when a display drops, and reboot it from the conversation.

  • Screenshots of the whole floor

    Proof from one line or every screen in the plant.

  • Multicast streams

    Stream to floor displays over a network that carries multicast.

Give your agent a screen

Install the official plugin, pair your first screen, and run it from the agent you already use.

Set up your agentGet a Demo →All use cases →