[{"data":1,"prerenderedAt":267},["ShallowReactive",2],{"application-guide-nav":3,"agmd-flowfuse-worked-examples":118},[4,12,16,22,25,31,36,42,47,53,58,64,70,75,81,87,93,98,103,108,112],{"guide":5,"slug":6,"title":7,"navOrder":8,"parent":9,"blurb":10,"path":11},"flowfuse","overview","Overview",1,null,"The map of the FlowFuse guide — apps, architectures, and a worked example.","\u002Fapplication-guide\u002Fflowfuse\u002Foverview\u002F",{"guide":13,"slug":6,"title":7,"navOrder":8,"parent":9,"blurb":14,"path":15},"node-red","The map of the Node-RED guide — the pattern families that turn an app into a clean flow.","\u002Fapplication-guide\u002Fnode-red\u002Foverview\u002F",{"guide":5,"slug":17,"title":18,"navOrder":19,"parent":9,"blurb":20,"path":21},"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":13,"slug":17,"title":18,"navOrder":19,"parent":9,"blurb":23,"path":24},"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":26,"title":27,"navOrder":28,"parent":9,"blurb":29,"path":30},"app-delivery-methods","App delivery methods",3,"Two different units of code, delivered two ways. Ship the whole app — a complete, versioned project promoted through environments — or publish one reusable piece — a package the whole team installs and upgrades in one place. Pick by what you're shipping: the app, or a part of it.","\u002Fapplication-guide\u002Fflowfuse\u002Fapp-delivery-methods\u002F",{"guide":13,"slug":32,"title":33,"navOrder":28,"parent":9,"blurb":34,"path":35},"patterns","Patterns","The moves that turn an architecture into a clean, reusable flow — find the seams and reuse well, then handle data on the right paths.","\u002Fapplication-guide\u002Fnode-red\u002Fpatterns\u002F",{"guide":5,"slug":37,"title":38,"navOrder":39,"parent":26,"blurb":40,"path":41},"hardware-apps","Hardware apps",3.1,"The three shapes a FlowFuse app takes when it runs on a device. Pick by how much varies per site: nothing (Packaged App), a few settings (Configurable App), or you assemble it yourself (Edge Building Block).","\u002Fapplication-guide\u002Fflowfuse\u002Fhardware-apps\u002F",{"guide":13,"slug":43,"title":44,"navOrder":39,"parent":32,"blurb":45,"path":46},"design-patterns","Design patterns","The structural choices you select for a flow: find the seams it breaks into, then reuse each piece at the lightest level that solves it — link in\u002Fout, link call, subflow, or packaged node.","\u002Fapplication-guide\u002Fnode-red\u002Fdesign-patterns\u002F",{"guide":5,"slug":48,"title":49,"navOrder":50,"parent":26,"blurb":51,"path":52},"software-apps","Software apps",3.2,"The three shapes a FlowFuse app takes when it runs on the platform. Pick by what it needs: a headless job (Packaged App), a user-facing app driven by data (Data-Driven App), or a reusable piece other apps embed (Shared Building Block).","\u002Fapplication-guide\u002Fflowfuse\u002Fsoftware-apps\u002F",{"guide":13,"slug":54,"title":55,"navOrder":50,"parent":32,"blurb":56,"path":57},"handling-data","Handling data","Classify each signal by shape, purpose and direction, then pick the methods it needs — separate the paths, pace the flow, hold state in context, and manage config. The methods you select to move a flow's data.","\u002Fapplication-guide\u002Fnode-red\u002Fhandling-data\u002F",{"guide":13,"slug":59,"title":60,"navOrder":61,"parent":32,"blurb":62,"path":63},"good-form","Good form",3.3,"A clean flow isn't luck — it's a handful of habits. Wire for reading, lay it out on a grid, decouple UI from logic, catch errors where you can see them, and keep data on a stable contract. Follow these and a flow stays readable, reusable, and out of spaghetti.","\u002Fapplication-guide\u002Fnode-red\u002Fgood-form\u002F",{"guide":5,"slug":65,"title":66,"navOrder":67,"parent":9,"blurb":68,"path":69},"data-plane","Data plane",4,"Before you pick where things run, decide how data is handled. Two stores come built into every FlowFuse server install — the Team Broker and relational Tables — exposed to every instance with nothing extra to stand up. Everything else you bring your own: run it (a time-series DB, an existing database, a model) and expose it to the fleet over Project Link, no inbound ports. This is the data plane the architectures on the next pages all sit on.","\u002Fapplication-guide\u002Fflowfuse\u002Fdata-plane\u002F",{"guide":13,"slug":71,"title":72,"navOrder":67,"parent":9,"blurb":73,"path":74},"worked-examples","Worked examples","Turn an app concept into a Node-RED flow — or a few — leaning on the design patterns and data handling. The method, then the OEE apps end to end.","\u002Fapplication-guide\u002Fnode-red\u002Fworked-examples\u002F",{"guide":13,"slug":76,"title":77,"navOrder":78,"parent":71,"blurb":79,"path":80},"oee-edge-aggregator","OEE - Edge Aggregator",4.1,"The edge app from the OEE use case as a Node-RED flow — a straight-line flow packaged as a subflow and configured per line (its PLC tags, via a config UI and a get-config node), with the data treated as a stream and its counts held in context.","\u002Fapplication-guide\u002Fnode-red\u002Foee-edge-aggregator\u002F",{"guide":13,"slug":82,"title":83,"navOrder":84,"parent":71,"blurb":85,"path":86},"oee-central-dashboard","OEE - Central Dashboard",4.2,"The cloud app from the OEE use case as a Node-RED flow — one link out fanning to two link ins on separate tabs (dashboard and batched history), so the live and history paths stay separate and easy to read.","\u002Fapplication-guide\u002Fnode-red\u002Foee-central-dashboard\u002F",{"guide":5,"slug":88,"title":89,"navOrder":90,"parent":9,"blurb":91,"path":92},"architectures","Architectures",5,"Every FlowFuse deployment is the same building blocks arranged for where it runs — pick the world you're designing for.","\u002Fapplication-guide\u002Fflowfuse\u002Farchitectures\u002F",{"guide":5,"slug":94,"title":95,"navOrder":96,"parent":88,"blurb":9,"path":97},"it-architectures","IT architectures",5.1,"\u002Fapplication-guide\u002Fflowfuse\u002Fit-architectures\u002F",{"guide":5,"slug":99,"title":100,"navOrder":101,"parent":88,"blurb":9,"path":102},"ot-architectures","OT architectures",5.2,"\u002Fapplication-guide\u002Fflowfuse\u002Fot-architectures\u002F",{"guide":5,"slug":104,"title":105,"navOrder":106,"parent":88,"blurb":9,"path":107},"iiot-architectures","IIoT architectures",5.3,"\u002Fapplication-guide\u002Fflowfuse\u002Fiiot-architectures\u002F",{"guide":5,"slug":71,"title":72,"navOrder":109,"parent":9,"blurb":110,"path":111},6,"Start from a use case, break it into apps, and draw the architecture that ties them together — the same method a FlowFuse Proof of Value runs.","\u002Fapplication-guide\u002Fflowfuse\u002Fworked-examples\u002F",{"guide":5,"slug":113,"title":114,"navOrder":115,"parent":71,"blurb":116,"path":117},"worked-example","OEE, end to end",6.1,"One use case — OEE across three lines — broken into two apps and two shared services, then drawn out end to end.","\u002Fapplication-guide\u002Fflowfuse\u002Fworked-example\u002F",{"id":119,"title":72,"blurb":110,"body":120,"description":259,"extension":260,"guide":5,"meta":261,"navOrder":109,"navTitle":72,"navigation":262,"parent":9,"path":263,"seo":264,"slug":71,"stem":265,"__hash__":266},"applicationGuideDoc\u002Fapplication-guide\u002Fflowfuse\u002Fworked-examples.md",{"type":121,"value":122,"toc":254},"minimark",[123,126,152,159,166,171,174,235,239,251],[124,125,72],"h1",{"id":71},[127,128,129,130,134,135,139,140,143,144,147,148,151],"p",{},"A ",[131,132,133],"strong",{},"use case"," is a problem to solve — a defined pain, stated in plain business terms: ",[136,137,138],"em",{},"\"track OEE across three lines,\""," ",[136,141,142],{},"\"warn the team before a tank runs dry.\""," The ",[131,145,146],{},"solution"," is an app — and a use case is rarely a single one. Most take ",[131,149,150],{},"one or more apps working together",".",[127,153,154,155,158],{},"Each worked example takes a real use case and works it end to end — the same way a FlowFuse ",[131,156,157],{},"Proof of Value"," does: name the use case, break it into the apps that solve it, pin down how each app is delivered and what shape it takes, then draw the whole architecture.",[127,160,161,162,165],{},"A solution can be delivered different ways — ",[131,163,164],{},"built entirely by FlowFuse, built together with your team, or built by you"," from these examples. The breakdown is the same either way.",[167,168,170],"h2",{"id":169},"from-use-case-to-apps","From use case to apps",[127,172,173],{},"Every example runs the same four moves:",[175,176,177,184,190,221],"ol",{},[178,179,180,183],"li",{},[131,181,182],{},"Name the use case"," — the pain in plain business terms, and what \"good\" looks like.",[178,185,186,189],{},[131,187,188],{},"Break it into apps"," — list each app the use case needs and say, in one sentence, what it does. Most use cases are more than one app.",[178,191,192,195,196,199,200,204,205,208,209,212,213,216,217,220],{},[131,193,194],{},"Pin down each app"," — for every app, name its ",[131,197,198],{},"delivery method"," (a ",[201,202,203],"a",{"href":30},"whole app"," or a reusable ",[201,206,207],{"href":30},"piece",") and its ",[131,210,211],{},"app pattern"," (",[201,214,215],{"href":41},"hardware"," or ",[201,218,219],{"href":52},"software"," app), where it runs, and why that shape.",[178,222,223,226,227,230,231,234],{},[131,224,225],{},"Draw the architecture"," — place the apps, the ",[201,228,229],{"href":69},"data plane"," and the broker into one picture that shows how it ties together, and state the whole ",[201,232,233],{"href":92},"architecture"," in a sentence.",[167,236,238],{"id":237},"the-examples","The examples",[240,241,243],"callout",{"icon":242},"i-lucide-arrow-right",[127,244,245,250],{},[131,246,247],{},[201,248,249],{"href":117},"OEE, end to end →"," — one use case, two apps and two shared services, from edge to broker to cloud to history.",[127,252,253],{},"More worked examples will land here — each one a use case, broken into its apps and drawn out end to end.",{"title":255,"searchDepth":67,"depth":67,"links":256},"",[257,258],{"id":169,"depth":19,"text":170},{"id":237,"depth":19,"text":238},"A use case is a problem to solve — a defined pain, stated in plain business terms: \"track OEE across three lines,\" \"warn the team before a tank runs dry.\" The solution is an app — and a use case is rarely a single one. Most take one or more apps working together.","md",{},true,"\u002Fapplication-guide\u002Fflowfuse\u002Fworked-examples",{"title":72,"description":259},"application-guide\u002Fflowfuse\u002Fworked-examples","wg_NUgw8MaBAVgBi-UJQoyBzKofcomcPiiYpUI5hCUw",1787070953609]