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