---
title: "Shop Floor Communication | Use Cases | FlowFuse • FlowFuse"
description: "Andon, alerts and escalations that reach the right people in seconds: from machine events to team channels, displays and phones. Built on Node-RED, managed with FlowFuse."
canonical_url: "https://flowfuse.com/use-cases/shop-floor-communication/"
meta:
  "og:description": "Andon, alerts and escalations that reach the right people in seconds: from machine events to team channels, displays and phones. Built on Node-RED, managed with FlowFuse."
  "og:title": "Shop Floor Communication | Use Cases | FlowFuse • FlowFuse"
---

> Index of every page on this site: [llms.txt](https://flowfuse.com/llms.txt)

**Use case**

# Shop Floor Communication

The line stopped four minutes ago. The person who can fix it will find out when someone walks over.

[**Talk to Us**](https://flowfuse.com/book-demo/)

**01 · Customer pain**

## Events travel at walking speed.

Machines know the moment something needs attention. Getting that moment to a human still relies on stack lights someone must see, radios someone must answer, and walks across the floor.

Escalation is informal: if the first person is busy, the event waits. Response times are unmeasured because nobody records when the call for help actually started.

#### Alarms without an audience

Stack lights and local alarms help only whoever happens to be nearby.

#### Events never reach team channels

The tools people actually watch, phones, Teams, Slack, displays, are disconnected from the machines.

#### No escalation path

If the first responder is occupied, nothing routes the event to the next person.

#### Response time is invisible

Without timestamps from event to acknowledgment, response cannot be measured or improved.

**02 · Outcome first**

## From machine event to the right person, in seconds.

FlowFuse turns machine and operator events into routed notifications: andon displays, team-channel messages, SMS escalation chains, with acknowledgment and timing captured for every event.

**Operational**

#### Events routed, not broadcast

The right role gets the right event on the channel they actually watch, with context attached.

**Organizational**

#### Escalation that runs itself

Unacknowledged events climb the chain automatically; nothing waits on a walk across the floor.

**Financial**

#### Measured, shrinking response times

Event-to-acknowledgment timing becomes a metric you can see and improve.

**03 · Why this is important**

## Downtime is often waiting time in disguise.

A meaningful share of every stop is the gap between the event and the right person knowing about it.

**01**

#### Minutes of waiting hide in every stop

Multiply the notification gap across every stop and shift; the total is a production line's worth of capacity.

**02**

#### Informal escalation fails on bad days

Exactly when the floor is busiest, word-of-mouth routing breaks down.

**03**

#### Communication data improves staffing

Knowing which events, where, at what times, shapes shift coverage and skill placement.

**04 · Why off-the-shelf doesn't work**

## Why the usual approaches stall.

Andon exists in many forms; connected, routed, measured andon rarely does.

**Hardware andon**

#### Lights and towers, no routing

Visual signals with no notion of who should respond or what happens if they do not.

**MES call buttons**

#### Locked to one vendor's screens

Built-in call functions reach only the people logged into that system.

**Group chat chaos**

#### Everything posted to everyone

Unrouted alerts train people to ignore the channel.

**05 · With / without FlowFuse**

### Without FlowFuse

##### Events wait for a passerby

Stack lights and shouts; response depends on proximity.

##### No record of response

Event-to-fix timing unmeasured, unimprovable.

##### Every plant improvises

Each site wires its own ad-hoc notification hacks.

### With FlowFuse

##### Events reach the right person in seconds

Routed notifications with context, on channels people watch.

##### Acknowledgment and timing captured

Response becomes a measured, managed metric.

##### One pattern across sites

The same escalation flows deployed fleet-wide.

**06 · Build it with AI**

## From described to deployed, with the FlowFuse Expert

The FlowFuse Expert works on this use case with you, from routing logic to summarizing what happened overnight.

**Step 01**

#### Describe it, get a starting flow

Tell the Expert your events, roles and channels; it assembles a routing and escalation starting flow. Currently in open beta on FlowFuse Cloud.

**Step 02**

#### Refine with in-editor assistance

Function Builder and completions handle message formatting, shift calendars and escalation timers.

**Step 03**

#### Own and adapt what you built

The flow explainer documents routing rules so supervisors can read and adjust them without a developer.

[Get started with the Expert](https://flowfuse.com/ai/)

AI capabilities noted as beta are in open beta on FlowFuse Cloud at time of writing.

**Common in these industries**

[**Automotive**](https://flowfuse.com/industries/automotive/), [**Food & Beverage**](https://flowfuse.com/industries/food-beverage/), [**Aviation & Aerospace**](https://flowfuse.com/industries/aviation-aerospace/), [**Electronics & Appliances**](https://flowfuse.com/industries/electronics-appliances/), [**Industrial Machinery**](https://flowfuse.com/industries/industrial-machinery/), [**Building Materials**](https://flowfuse.com/industries/building-materials/), [**Energy and Utilities**](https://flowfuse.com/industries/energy-utilities/) · [all industries](https://flowfuse.com/industries/)

### Close the gap between event and action

Talk to an expert about connected andon and escalation, or route your first event today.

[**Talk to Us**](https://flowfuse.com/book-demo/) [**Build With Us**](https://flowfuse.com/build-with-us/)

```json
{"@context":"https://schema.org","@graph":[{"@id":"https://flowfuse.com/#website","@type":"WebSite","description":"FlowFuse builds your first industrial solution with your team, proves it at one plant, then helps you roll it out to every plant, faster each time.","inLanguage":"en","name":"FlowFuse","url":"https://flowfuse.com/","alternateName":["FlowForge","Flow Fuse"],"publisher":{"@id":"https://flowfuse.com/#identity"}},{"@id":"https://flowfuse.com/use-cases/shop-floor-communication/#webpage","@type":"WebPage","description":"Andon, alerts and escalations that reach the right people in seconds: from machine events to team channels, displays and phones. Built on Node-RED, managed with FlowFuse.","name":"Shop Floor Communication | Use Cases | FlowFuse","url":"https://flowfuse.com/use-cases/shop-floor-communication/","isPartOf":{"@id":"https://flowfuse.com/#website"},"potentialAction":[{"@type":"ReadAction","target":["https://flowfuse.com/use-cases/shop-floor-communication/"]}],"primaryImageOfPage":{"@id":"https://flowfuse.com/#logo"}},{"@id":"https://flowfuse.com/#identity","@type":"Organization","legalName":"FlowFuse Inc.","name":"FlowFuse","url":"https://flowfuse.com","alternateName":["FlowForge","Flow Fuse"],"logo":{"@id":"https://flowfuse.com/#logo"},"sameAs":["https://twitter.com/FlowFuseinc","https://github.com/FlowFuse","https://www.linkedin.com/company/flowfuse/","https://www.facebook.com/FlowFuse/","https://www.youtube.com/channel/UCbBzP8NZbv3WDtlt4UouA-g"]},{"@id":"https://flowfuse.com/#logo","@type":"ImageObject","caption":"FlowFuse","contentUrl":"https://flowfuse.com/handbook/images/logos/ff-logo--square--dark.png","inLanguage":"en","url":"https://flowfuse.com/handbook/images/logos/ff-logo--square--dark.png"}]}
```

## Sitemap

See the full [sitemap](https://flowfuse.com/sitemap.md) for all pages.
