[{"data":1,"prerenderedAt":216},["ShallowReactive",2],{"application-guide-nav":3,"application-guide-flowfuse-iiot-architectures":101},[4,11,15,21,24,30,35,41,46,52,57,63,68,74,79,85,91,97],{"guide":5,"slug":6,"title":7,"navOrder":8,"blurb":9,"path":10},"flowfuse","overview","Overview",1,"Turn an app idea into FlowFuse pieces you can name and say in one sentence.","\u002Fapplication-guide\u002Fflowfuse\u002Foverview\u002F",{"guide":12,"slug":6,"title":7,"navOrder":8,"blurb":13,"path":14},"node-red","Turn an architecture sentence into a clean flow shape you can read at a glance.","\u002Fapplication-guide\u002Fnode-red\u002Foverview\u002F",{"guide":5,"slug":16,"title":17,"navOrder":18,"blurb":19,"path":20},"foundations","Foundations",2,"The foundation to build on: what FlowFuse is, its core pieces, and how code is shared across teams.","\u002Fapplication-guide\u002Fflowfuse\u002Ffoundations\u002F",{"guide":12,"slug":16,"title":17,"navOrder":18,"blurb":22,"path":23},"The handful of concepts you need to build with Node-RED, and how they fit together.","\u002Fapplication-guide\u002Fnode-red\u002Ffoundations\u002F",{"guide":5,"slug":25,"title":26,"navOrder":27,"blurb":28,"path":29},"app-delivery-methods","App delivery methods",3,"Two different units of code, delivered two ways: ship the whole app, or publish one reusable piece.","\u002Fapplication-guide\u002Fflowfuse\u002Fapp-delivery-methods\u002F",{"guide":12,"slug":31,"title":32,"navOrder":27,"blurb":33,"path":34},"flow-shape","Flow shape","Turn an architecture sentence into a flow you can read at a glance.","\u002Fapplication-guide\u002Fnode-red\u002Fflow-shape\u002F",{"guide":5,"slug":36,"title":37,"navOrder":38,"blurb":39,"path":40},"hardware-apps","Hardware apps",4,"The three shapes a FlowFuse app takes when it runs on a device.","\u002Fapplication-guide\u002Fflowfuse\u002Fhardware-apps\u002F",{"guide":12,"slug":42,"title":43,"navOrder":38,"blurb":44,"path":45},"design-patterns","Design patterns","The moves that turn a flow into something you can reuse, test and hand off.","\u002Fapplication-guide\u002Fnode-red\u002Fdesign-patterns\u002F",{"guide":5,"slug":47,"title":48,"navOrder":49,"blurb":50,"path":51},"software-apps","Software apps",5,"The three shapes a FlowFuse app takes when it runs on the platform.","\u002Fapplication-guide\u002Fflowfuse\u002Fsoftware-apps\u002F",{"guide":12,"slug":53,"title":54,"navOrder":49,"blurb":55,"path":56},"handling-data","Handling data","Sort data by what it is for before you tune anything.","\u002Fapplication-guide\u002Fnode-red\u002Fhandling-data\u002F",{"guide":5,"slug":58,"title":59,"navOrder":60,"blurb":61,"path":62},"data-plane","Data plane",6,"Before you pick where things run, decide how data is handled.","\u002Fapplication-guide\u002Fflowfuse\u002Fdata-plane\u002F",{"guide":12,"slug":64,"title":65,"navOrder":60,"blurb":66,"path":67},"operating-flows","Operating flows","Four operational habits that keep a flow running when the real world pushes back.","\u002Fapplication-guide\u002Fnode-red\u002Foperating-flows\u002F",{"guide":5,"slug":69,"title":70,"navOrder":71,"blurb":72,"path":73},"architectures","Architectures",7,"The same building blocks, arranged for where they run.","\u002Fapplication-guide\u002Fflowfuse\u002Farchitectures\u002F",{"guide":12,"slug":75,"title":76,"navOrder":71,"blurb":77,"path":78},"worked-example","Worked example","The shape rules and patterns applied end to end.","\u002Fapplication-guide\u002Fnode-red\u002Fworked-example\u002F",{"guide":5,"slug":80,"title":81,"navOrder":82,"blurb":83,"path":84},"it-architectures","IT architectures",8,"Hosting the platform and serving the wider organisation.","\u002Fapplication-guide\u002Fflowfuse\u002Fit-architectures\u002F",{"guide":5,"slug":86,"title":87,"navOrder":88,"blurb":89,"path":90},"ot-architectures","OT architectures",9,"How FlowFuse deploys in operational-technology environments, near the equipment.","\u002Fapplication-guide\u002Fflowfuse\u002Fot-architectures\u002F",{"guide":5,"slug":92,"title":93,"navOrder":94,"blurb":95,"path":96},"iiot-architectures","IIoT architectures",10,"Distributed edge nodes, each doing one small job, feeding one central system.","\u002Fapplication-guide\u002Fflowfuse\u002Fiiot-architectures\u002F",{"guide":5,"slug":75,"title":76,"navOrder":98,"blurb":99,"path":100},11,"OEE, end to end — two packages, two connections.","\u002Fapplication-guide\u002Fflowfuse\u002Fworked-example\u002F",{"id":102,"title":93,"blocks":103,"blurb":95,"extension":212,"guide":5,"meta":213,"navOrder":94,"slug":92,"stem":214,"__hash__":215},"applicationGuide\u002Fapplication-guide\u002Fflowfuse\u002F10-iiot-architectures.yml",[104,107,204],{"type":105,"kicker":93,"body":106},"prose","Distributed edge nodes, each reading a few sensors and doing one small job, feeding one central system. The value is the large-scale live picture that many small nodes add up to.",{"type":108,"panels":109},"tabs",[110,164],{"label":111,"kicker":112,"diagram":113,"summary":162,"useWhen":163},"Distributed edge","Central system · one live view of every node",{"lanes":114,"legend":153},[115,121,123,129,131,142,144],{"label":112,"tone":116,"nodes":117},"cloud",[118],{"title":119,"sub":120,"tone":116},"Central app","one live view of every node",{"link":122},"subscribe",{"label":124,"tone":125,"nodes":126},"Team Broker","broker",[127],{"title":124,"sub":128,"tone":125},"MQTT · UNS",{"link":130},"publish",{"label":132,"tone":133,"nodes":134},"Distributed sites · a Remote Instance + a few sensors, each a small job","ot",[135,138,140],{"title":136,"sub":137,"tone":133},"Remote Instance","Site A",{"title":136,"sub":139,"tone":133},"Site B",{"title":136,"sub":141,"tone":133},"Site C",{"link":143},"reads",{"label":145,"tone":146,"nodes":147},"Sensors","neutral",[148,151,152],{"title":145,"sub":149,"tone":150},"pH · flow · level","muted",{"title":145,"sub":149,"tone":150},{"title":145,"sub":149,"tone":150},[154,156,158,160],{"label":155,"tone":116},"Central",{"label":157,"tone":133},"Edge sites",{"label":159,"tone":125},"MQTT \u002F UNS",{"label":161,"tone":150},"sensor wire","The IIoT shape: many distributed Remote Instances, each reading just a few sensors and doing one small job, publish to a central Team Broker. One central app subscribes and sees every node at once. Each node is small — the value is the large-scale live picture they add up to. Think water-quality monitoring across dozens of pump stations.","Lots of small, spread-out measurement points that only pay off when aggregated into one live view.",{"label":165,"kicker":166,"diagram":167,"summary":202,"useWhen":203},"Across many sites","Enterprise · one namespace, every site rolls up",{"lanes":168,"legend":193},[169,179,180,184,186],{"label":170,"tone":116,"nodes":171},"Enterprise consumers",[172,175,177],{"title":173,"sub":174,"tone":116},"Dashboards","enterprise",{"title":176,"sub":174,"tone":116},"Historian",{"title":178,"sub":174,"tone":116},"Analytics",{"link":122},{"label":166,"tone":125,"nodes":181},[182],{"title":124,"sub":183,"tone":125},"enterprise UNS",{"link":185},"publish · Project Link",{"label":187,"tone":133,"nodes":188},"Sites · each already a cluster of edge nodes",[189,191,192],{"title":137,"sub":190,"tone":133},"a cluster of nodes",{"title":139,"sub":190,"tone":133},{"title":141,"sub":190,"tone":133},[194,196,198,201],{"label":195,"tone":116},"Enterprise",{"label":197,"tone":133},"Sites",{"label":199,"tone":200},"Project Link","it",{"label":159,"tone":125},"Scale the same pattern across sites. Each site — itself a cluster of edge nodes — publishes into one enterprise namespace over Project Link, with no inbound ports. A single Team Broker carries every site's live data, and enterprise dashboards, historians and analytics subscribe across all of them.","The distributed-edge pattern spans multiple plants or geographies that must roll up to one enterprise view.",{"type":205,"columns":8,"items":206},"linkCards",[207],{"title":208,"body":209,"link":210},"Where does the data live?","Every architecture here sits on the same data plane — built-in Tables & Broker, or bring your own over Project Link.",{"label":211,"to":62},"Data plane →","yml",{},"application-guide\u002Fflowfuse\u002F10-iiot-architectures","wSIifhfdGIl4NQdGnZVydGwP1KqDBdkI76llyyK0w5Y",1786134120511]