Operational workflow patterns teams in this industry build and own with FlowFuse.
+{{ uc.data.problem }}
+ + View use case + {% include "components/icons/arrow-right.svg" %} + + + {% endif %} + {% endfor %} ++ {% for slug in industries %}{{ industryLabels[slug] or slug }}{% if not loop.last %}, {% endif %}{% endfor %} + · all industries +
+ {% endif %} +{{ uc.data.problem }}
+ View use case {% include "components/icons/arrow-right.svg" %} + + {% endif %} + {% endfor %} + {% endfor %} +06 · Build it with AI
+{{ aiBuildLayer.intro }}
+{{ step.detail }}
+{{ aiBuildLayer.note }}
+ {% endif %} +Problems operations teams own, and how they are solved with FlowFuse. Each use case is also reachable by industry.
+{{ uc.data.problem }}
- + View use case {% include "components/icons/arrow-right.svg" %} + {% endif %} + {% endfor %} +How FlowFuse is deployed and where it sits in your stack. Architectures are the technical evaluator's entry point; the use cases above are what gets built on them.
+{{ uc.data.problem }}
+ + View architecture + {% include "components/icons/arrow-right.svg" %} + + + {% endif %} {% endfor %}diff --git a/src/use-cases/production-monitoring.njk b/src/use-cases/production-monitoring.njk index 2d9476c006..5086a4a875 100644 --- a/src/use-cases/production-monitoring.njk +++ b/src/use-cases/production-monitoring.njk @@ -4,6 +4,19 @@ meta: title: "Production Monitoring | Use Cases | FlowFuse" description: "Real-time visibility into what your production lines are actually doing. Build the monitoring app your operation needs with FlowFuse and Node-RED: connect any protocol, deploy at the edge or in the cloud, and roll out across sites." problem: "Your operation is running. You just can't see it clearly enough, until something breaks." +industries: ["automotive", "food-beverage", "life-sciences", "aviation-aerospace", "aerospace-components", "renewables", "semiconductors", "electronics-appliances"] +values: ["production-performance"] + +aiBuildLayer: + intro: "The FlowFuse Expert works on this use case with you: describe the monitoring you need and get a working starting flow, then query what it captures in plain language." + steps: + - title: "Describe it, get a starting flow" + detail: "Tell the Expert which lines and KPIs to watch; it assembles tabs, nodes and wiring for a monitoring starting point. Currently in open beta on FlowFuse Cloud." + - title: "Refine with in-editor assistance" + detail: "Function Builder and inline completions handle counters, shift logic and dashboard bindings; the flow explainer documents the result." + - title: "Ask your plant anything" + detail: "Expose captured production data through MCP tools and query it with Expert's Insights mode (beta): 'which line lost the most output this shift?'" + note: "AI capabilities noted as beta are in open beta on FlowFuse Cloud at time of writing." customerPain: heading: "Visibility gaps are expensive." diff --git a/src/use-cases/uns.njk b/src/use-cases/uns.njk index 5110a691c2..cf660121f9 100644 --- a/src/use-cases/uns.njk +++ b/src/use-cases/uns.njk @@ -1,6 +1,7 @@ --- layout: page title: "FlowFuse for UNS" +image: /images/solutions/flowfuse-uns.png problem: "Adopt a Unified Namespace without ripping out existing infrastructure. FlowFuse connects producers and consumers through MQTT with low-code flows." nohero: true meta: @@ -31,15 +32,15 @@ meta:
IT and data professionals are often challenged by the complexities of accessing and analyzing data scattered across disparate systems in manufacturing environments. UNS offers a solution to these challenges by providing a standardized way to access and utilize real-time data across your entire manufacturing operation.
-