[{"data":1,"prerenderedAt":145},["ShallowReactive",2],{"use-case-shop-floor-communication":3},{"id":4,"title":5,"architecture":6,"extension":7,"industries":8,"meta":16,"problem":17,"sections":18,"seoMeta":137,"slug":140,"stem":141,"values":142,"__hash__":144},"useCases\u002Fuse-cases\u002Fshop-floor-communication.yml","Shop Floor Communication","remote-device-management","yml",[9,10,11,12,13,14,15],"automotive","food-beverage","aviation-aerospace","electronics-appliances","industrial-machinery","building-materials","energy-utilities",{},"The line stopped four minutes ago. The person who can fix it will find out when someone walks over.",[19,22,24,47,64,78,95,117,131,133],{"type":20,"layout":21},"hero","centered",{"type":23},"sectionNav",{"type":25,"heading":26,"intro":27,"cards":30},"pain","Events travel at walking speed.",[28,29],"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.",[31,35,39,43],{"icon":32,"title":33,"detail":34},"i-heroicons-bell-alert","Alarms without an audience","Stack lights and local alarms help only whoever happens to be nearby.",{"icon":36,"title":37,"detail":38},"i-heroicons-chat-bubble-left-right","Events never reach team channels","The tools people actually watch, phones, Teams, Slack, displays, are disconnected from the machines.",{"icon":40,"title":41,"detail":42},"i-heroicons-arrow-path","No escalation path","If the first responder is occupied, nothing routes the event to the next person.",{"icon":44,"title":45,"detail":46},"i-heroicons-clock","Response time is invisible","Without timestamps from event to acknowledgment, response cannot be measured or improved.",{"type":48,"heading":49,"intro":50,"dimensions":51},"outcomes","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.",[52,56,60],{"label":53,"title":54,"detail":55},"Operational","Events routed, not broadcast","The right role gets the right event on the channel they actually watch, with context attached.",{"label":57,"title":58,"detail":59},"Organizational","Escalation that runs itself","Unacknowledged events climb the chain automatically; nothing waits on a walk across the floor.",{"label":61,"title":62,"detail":63},"Financial","Measured, shrinking response times","Event-to-acknowledgment timing becomes a metric you can see and improve.",{"type":65,"heading":66,"intro":67,"points":68},"whyItMatters","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.",[69,72,75],{"title":70,"detail":71},"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.",{"title":73,"detail":74},"Informal escalation fails on bad days","Exactly when the floor is busiest, word-of-mouth routing breaks down.",{"title":76,"detail":77},"Communication data improves staffing","Knowing which events, where, at what times, shapes shift coverage and skill placement.",{"type":79,"heading":80,"intro":81,"traps":82},"competition","Why the usual approaches stall.","Andon exists in many forms; connected, routed, measured andon rarely does.",[83,87,91],{"label":84,"title":85,"detail":86},"Hardware andon","Lights and towers, no routing","Visual signals with no notion of who should respond or what happens if they do not.",{"label":88,"title":89,"detail":90},"MES call buttons","Locked to one vendor's screens","Built-in call functions reach only the people logged into that system.",{"label":92,"title":93,"detail":94},"Group chat chaos","Everything posted to everyone","Unrouted alerts train people to ignore the channel.",{"type":96,"without":97,"with":107},"comparison",[98,101,104],{"title":99,"detail":100},"Events wait for a passerby","Stack lights and shouts; response depends on proximity.",{"title":102,"detail":103},"No record of response","Event-to-fix timing unmeasured, unimprovable.",{"title":105,"detail":106},"Every plant improvises","Each site wires its own ad-hoc notification hacks.",[108,111,114],{"title":109,"detail":110},"Events reach the right person in seconds","Routed notifications with context, on channels people watch.",{"title":112,"detail":113},"Acknowledgment and timing captured","Response becomes a measured, managed metric.",{"title":115,"detail":116},"One pattern across sites","The same escalation flows deployed fleet-wide.",{"type":118,"intro":119,"steps":120,"note":130},"aiBuildLayer","The FlowFuse Expert works on this use case with you, from routing logic to summarizing what happened overnight.",[121,124,127],{"title":122,"detail":123},"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.",{"title":125,"detail":126},"Refine with in-editor assistance","Function Builder and completions handle message formatting, shift calendars and escalation timers.",{"title":128,"detail":129},"Own and adapt what you built","The flow explainer documents routing rules so supervisors can read and adjust them without a developer.","AI capabilities noted as beta are in open beta on FlowFuse Cloud at time of writing.",{"type":132},"industries",{"type":134,"heading":135,"description":136},"cta","Close the gap between event and action","Talk to an expert about connected andon and escalation, or route your first event today.",{"title":138,"description":139},"Shop Floor Communication | Use Cases | FlowFuse","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.","shop-floor-communication","use-cases\u002Fshop-floor-communication",[143],"labor-operational-efficiency","BjklnE0icldlNpawQvfa3b3cnWDznwf6ig6D01l5CXA",1790950586201]