diff --git a/src/_includes/layouts/use-case.njk b/src/_includes/layouts/use-case.njk
index d3a0372a73..edcb7c0171 100644
--- a/src/_includes/layouts/use-case.njk
+++ b/src/_includes/layouts/use-case.njk
@@ -9,10 +9,33 @@ sitemapPriority: 0.7
problem hero sub-headline (the pain in one line)
customerPain { heading, intro[], cards[ {icon,title,detail} ] }
outcomeFirst { heading, intro, dimensions[ {label,title,detail} ] }
+ howItWorks { heading, intro, designPattern{}, diagram{}, pieces[], architecture, docsCta{} }
whyItMatters { heading, intro, points[ {title,detail} ] }
competition { heading, intro, traps[ {label,title,detail} ] }
comparison { without[ {title,detail} ], with[ {title,detail} ] }
+ howItWorks answers "how does FlowFuse build this", which the pain, outcome
+ and comparison blocks deliberately do not. It is the bridge from the
+ marketing narrative into the product docs, so keep it high level here and
+ push every detail into a docs link.
+
+ designPattern { kind, name, detail, docsUrl }
+ kind is the pattern family, e.g. "Hardware pattern" or
+ "Software pattern". name is the specific pattern chosen
+ for this use case.
+ diagram { src, alt, caption, width, height, placeholder }
+ End-to-end architecture drawing. src may be a placeholder
+ while the real diagram is commissioned; set
+ diagram.placeholder to true to render the placeholder
+ treatment and keep it visibly unfinished. width/height
+ default to 1200x630 and only exist to reserve the box, so
+ override them when the real asset is a different shape.
+ pieces [ {icon, title, detail, docsUrl} ]
+ The problem broken into the individual components that get
+ built. Order them the way you would build them.
+ architecture slug of a /use-cases/ architecture page this sits on
+ docsCta { label, url }
+
Legacy fall-back front-matter (simple skeleton, still supported):
gap[], workflow[], outcomes[]
@@ -23,11 +46,17 @@ sitemapPriority: 0.7
{% set nav = [] %}
{% if customerPain %}{% set nav = nav.concat([{ id: "customer-pain", label: "Customer Pain" }]) %}{% endif %}
{% if outcomeFirst %}{% set nav = nav.concat([{ id: "outcome-first", label: "Outcome First" }]) %}{% endif %}
+{% if howItWorks %}{% set nav = nav.concat([{ id: "how-it-works", label: "How It Works" }]) %}{% endif %}
{% if whyItMatters %}{% set nav = nav.concat([{ id: "why-it-matters", label: "Why It Matters" }]) %}{% endif %}
{% if competition %}{% set nav = nav.concat([{ id: "competition", label: "Why Off-the-Shelf Fails" }]) %}{% endif %}
{% if comparison %}{% set nav = nav.concat([{ id: "with-without", label: "With / Without FlowFuse" }]) %}{% endif %}
{% if aiBuildLayer %}{% set nav = nav.concat([{ id: "ai-build-layer", label: "Build It With AI" }]) %}{% endif %}
+{# --- section eyebrow numbers, derived from nav so they cannot drift ---
+ Pages omit blocks freely, so a hardcoded "03" desyncs from the nav as soon
+ as an earlier block is missing. Look the number up instead. #}
+{% macro secNum(id) %}{%- for item in nav -%}{%- if item.id == id -%}{%- if loop.index < 10 -%}0{%- endif -%}{{ loop.index }}{%- endif -%}{%- endfor -%}{% endmacro %}
+
-
01 · Customer pain
+
{{ secNum("customer-pain") }} · Customer pain
{{ customerPain.heading }}
{% for paragraph in customerPain.intro %}
@@ -94,11 +123,11 @@ sitemapPriority: 0.7
{% if outcomeFirst %}
-
02 · Outcome first
+
{{ secNum("outcome-first") }} · Outcome first
{{ outcomeFirst.heading }}
{{ outcomeFirst.intro }}
@@ -114,13 +143,103 @@ sitemapPriority: 0.7
{% endif %}
+ {% if howItWorks %}
+
+
+
+
{{ secNum("how-it-works") }} · How it works
+
{{ howItWorks.heading or "How FlowFuse builds this" }}
+ {# width/height are here to reserve the box before the image
+ arrives; without them "h-auto" collapses the figure to
+ zero and the whole section below it jumps on load. #}
+
+
+ {% if howItWorks.diagram.caption or howItWorks.diagram.placeholder %}
+ {% if howItWorks.diagram.placeholder %}Placeholder diagram, pending art request. {% endif %}{{ howItWorks.diagram.caption }}
+ {% endif %}
+
+ {% endif %}
+
+ {% if howItWorks.pieces %}
+
{{ howItWorks.piecesHeading or "The individual pieces" }}
+
+ {% for piece in howItWorks.pieces %}
+
+
+
+ {% include "components/icons/" + piece.icon + ".svg" %}
+
{{ secNum("why-it-matters") }} · Why this is important
{{ whyItMatters.heading }}
{{ whyItMatters.intro }}
@@ -140,11 +259,11 @@ sitemapPriority: 0.7
{% if competition %}
-
04 · Why off-the-shelf doesn't work
+
{{ secNum("competition") }} · Why off-the-shelf doesn't work
{{ competition.heading }}
{{ competition.intro }}
@@ -165,11 +284,11 @@ sitemapPriority: 0.7
{% if comparison %}
-
05 · With / without FlowFuse
+
{{ secNum("with-without") }} · With / without FlowFuse
Without FlowFuse
@@ -206,11 +325,11 @@ sitemapPriority: 0.7
{% if aiBuildLayer %}
-
06 · Build it with AI
+
{{ secNum("ai-build-layer") }} · Build it with AI
{{ aiBuildLayer.heading or "From described to deployed, with the FlowFuse Expert" }}
{{ aiBuildLayer.intro }}
diff --git a/src/index.njk b/src/index.njk
index b7f03ee6c6..102bf8b4ca 100644
--- a/src/index.njk
+++ b/src/index.njk
@@ -67,6 +67,7 @@ operationalSystem:
url: "/use-cases/production-monitoring/"
description: "OEE tracking across lines, shifts, and plants."
- name: "Continuous Improvement"
+ url: "/use-cases/continuous-improvement/"
description: "Digital CI workflow from suggestion to closure."
- title: "OPERATIONAL WORKFLOWS"
items:
diff --git a/src/use-cases/continuous-improvement.njk b/src/use-cases/continuous-improvement.njk
new file mode 100644
index 0000000000..876dddb96b
--- /dev/null
+++ b/src/use-cases/continuous-improvement.njk
@@ -0,0 +1,137 @@
+---
+title: "Continuous Improvement"
+meta:
+ title: "Continuous Improvement | Use Cases | FlowFuse"
+ description: "Close the loop on improvement work: capture problems at the source, track actions, and prove effect with the same data that surfaced the problem. Built on Node-RED, managed with FlowFuse."
+problem: "Improvement ideas are captured on sticky notes, actioned in meetings, and never measured against the line they came from."
+industries: ["automotive", "aviation-aerospace", "aerospace-components"]
+values: ["production-performance", "labor-operational-efficiency"]
+
+howItWorks:
+ heading: "How FlowFuse builds a continuous improvement workflow."
+ intro: "An improvement loop is a record that moves through states, joined to the line data that proves whether it worked. This is how the problem breaks down and which FlowFuse pattern carries it."
+ designPattern:
+ kind: "Software pattern"
+ name: "Data-driven application"
+ detail: "The workflow lives in data, not in the flows. Stages, owners and categories are rows a process engineer can change, so the same application serves a new improvement programme without a redeploy."
+ docsUrl: "/docs/user/ff-tables/"
+ diagram:
+ placeholder: true
+ src: "https://placehold.co/1200x630/eef2ff/4338ca?text=Continuous+Improvement+Architecture"
+ alt: "End-to-end architecture for a continuous improvement workflow: capture on the floor, an improvement record in a database, routing to owners, and line data joined back in to measure the result."
+ caption: "Capture on the floor into one improvement record, routed to an owner, with line data joined back in so the effect is measured rather than asserted."
+ pieces:
+ - icon: "clip-list"
+ title: "Capture where the idea happens"
+ detail: "An operator-facing form on the line rather than a portal nobody opens. FlowFuse Dashboard puts it on the same screen the shift already uses."
+ - icon: "circle-stack"
+ title: "Hold the improvement as a record"
+ detail: "One row per idea with its area, category, owner and state. This is the piece that makes the loop measurable instead of anecdotal."
+ docsUrl: "/docs/user/ff-tables/"
+ - icon: "funnel"
+ title: "Route and triage"
+ detail: "Flows assign each idea to an owner by area and category, and escalate anything sitting too long in one state."
+ - icon: "arrows-right-left"
+ title: "Join to the line it came from"
+ detail: "Pull the relevant production data for the affected line so before and after are the same measurement, taken the same way."
+ - icon: "document-chart-bar"
+ title: "Report the loop, not the backlog"
+ detail: "Closure rate, time in state and realised effect per area, visible to the people running the programme."
+ - icon: "rectangle-stack"
+ title: "Reuse across sites"
+ detail: "The same application serves every plant; each one supplies its own areas, categories and owners as data."
+ architecture: "data-integration"
+ docsCta:
+ label: "Read the tables docs"
+ url: "/docs/user/ff-tables/"
+
+customerPain:
+ heading: "The improvement loop never closes."
+ intro:
+ - "Problems get noticed on the floor, raised in huddles, written on boards, and then decay: no owner, no data before, no data after, no way to know if the fix worked."
+ - "The operational data that could prove or disprove every improvement already exists in the machines. It just never meets the improvement process."
+ cards:
+ - icon: "light-bulb"
+ title: "Ideas die in capture"
+ detail: "Sticky notes and verbal reports lose the context needed to act: which machine, which condition, which frequency."
+ - icon: "clip-list"
+ title: "Actions without baselines"
+ detail: "Fixes are implemented without a measured before, so the after proves nothing."
+ - icon: "arrow-path"
+ title: "Recurring problems recur"
+ detail: "Without frequency data, the same issue is 'solved' quarterly by different people."
+ - icon: "chart"
+ title: "Effect is anecdotal"
+ detail: "Whether an improvement held is a matter of opinion three months later."
+ #placeholder: template copy for review, refine per Showcase
+
+outcomeFirst:
+ heading: "Improvement work with evidence attached."
+ intro: "FlowFuse connects the improvement loop to the machines: problems raised with live context, baselines captured automatically, and effects measured on the same signals that surfaced the issue."
+ dimensions:
+ - label: "Operational"
+ title: "Problems captured with machine context"
+ detail: "A raise-issue action on the floor attaches the machine, state and recent history automatically."
+ - label: "Organizational"
+ title: "A loop that closes itself"
+ detail: "Actions carry owners and baselines; effect checks run automatically after implementation."
+ - label: "Strategic"
+ title: "Improvement becomes cumulative"
+ detail: "Measured wins persist; the same problem stops being rediscovered every quarter."
+
+whyItMatters:
+ heading: "Unmeasured improvement is just activity."
+ intro: "CI programs live or die on whether effects are provable."
+ points:
+ - title: "Credibility compounds or collapses"
+ detail: "Teams engage with improvement programs that demonstrably work; proof requires data on both sides of the change."
+ - title: "The frequency picture changes priorities"
+ detail: "Measured recurrence often reveals the small daily problem outweighing the big monthly one."
+ - title: "Evidence survives reorganizations"
+ detail: "When improvements are recorded with data, the knowledge outlasts the people who made them."
+
+competition:
+ heading: "Why the usual approaches stall."
+ intro: "CI tooling manages the workflow; almost none of it touches the data."
+ traps:
+ - label: "CI/CAPA software"
+ title: "Workflow without measurement"
+ detail: "Actions are tracked to closure, not to effect. The loop closes administratively, not operationally."
+ - label: "Whiteboards and huddles"
+ title: "Capture without context"
+ detail: "What gets written down lacks the machine data that makes it actionable."
+ - label: "BI after the fact"
+ title: "Analysis disconnected from action"
+ detail: "Dashboards show trends, but nothing links a specific fix to a specific effect."
+
+comparison:
+ without:
+ - title: "Fixes without baselines"
+ detail: "Nobody can say what the situation was before the change."
+ - title: "Effects claimed, not shown"
+ detail: "Improvement reporting runs on anecdotes."
+ - title: "Same problems, new sticky notes"
+ detail: "Recurrence is invisible, so it repeats."
+ with:
+ - title: "Baselines captured automatically"
+ detail: "Raising an issue snapshots the relevant signals."
+ - title: "Effect checks run on schedule"
+ detail: "The same signals are compared after the fix, automatically."
+ - title: "A measured improvement record"
+ detail: "What worked, where, and how much, permanently."
+
+aiBuildLayer:
+ intro: "The FlowFuse Expert works on this use case with you, from capture flows to effect reports."
+ steps:
+ - title: "Describe it, get a starting flow"
+ detail: "Tell the Expert how issues should be raised and which signals matter; it assembles a capture-and-baseline starting flow. Currently in open beta on FlowFuse Cloud."
+ - title: "Refine with in-editor assistance"
+ detail: "Function Builder and completions handle baseline snapshots, comparisons and report generation."
+ - title: "Own and adapt what you built"
+ detail: "The flow explainer keeps the measurement logic transparent, which is exactly what an improvement culture needs."
+ note: "AI capabilities noted as beta are in open beta on FlowFuse Cloud at time of writing. Placeholder template copy for internal review."
+
+closingCta:
+ heading: "Close the loop with data"
+ description: "Talk to an expert about evidence-backed continuous improvement, or capture your first baseline today."
+---
diff --git a/src/use-cases/production-monitoring.njk b/src/use-cases/production-monitoring.njk
index 5086a4a875..8dfbc56b0e 100644
--- a/src/use-cases/production-monitoring.njk
+++ b/src/use-cases/production-monitoring.njk
@@ -7,6 +7,44 @@ problem: "Your operation is running. You just can't see it clearly enough, until
industries: ["automotive", "food-beverage", "life-sciences", "aviation-aerospace", "aerospace-components", "renewables", "semiconductors", "electronics-appliances"]
values: ["production-performance"]
+howItWorks:
+ heading: "How FlowFuse builds production monitoring."
+ intro: "Production monitoring is not one app you install. It is a handful of pieces you define once and then replicate. This is how the problem breaks down, and which FlowFuse pattern carries it across every line and site."
+ designPattern:
+ kind: "Hardware pattern"
+ name: "Pipeline plus environment variables"
+ detail: "The monitoring application is built once and distributed to every line by a DevOps pipeline. Everything site-specific, tag addresses, line names, shift boundaries, lives in environment variables instead of inside the flows, so the same snapshot runs everywhere without an edit."
+ docsUrl: "/docs/user/devops-pipelines/"
+ diagram:
+ placeholder: true
+ src: "https://placehold.co/1200x630/eef2ff/4338ca?text=Production+Monitoring+Architecture"
+ alt: "End-to-end architecture for production monitoring: PLCs and machines feeding edge instances, publishing to a broker and historian, with role-specific dashboards on top and a pipeline distributing the application across sites."
+ caption: "Machines and PLCs into edge instances, out over MQTT into your historian, role-specific dashboards on top, and one pipeline distributing the whole application across every line."
+ pieces:
+ - icon: "queue-list"
+ title: "Define the data model"
+ detail: "Name the equipment hierarchy and tag structure first: site, line, cell, signal. Every later piece depends on it, and this is exactly the part an off-the-shelf tool decides for you."
+ - icon: "chart"
+ title: "Derive the metrics"
+ detail: "Counts, cycle times, downtime reasons and OEE are calculated from the model rather than read off a machine. The logic sits in Node-RED flows your own team can read and change."
+ - icon: "device-agent"
+ title: "Collect at the edge"
+ detail: "The Device Agent runs an instance on existing edge hardware and speaks OPC-UA, Modbus, S7 or MQTT to whatever is already on the floor."
+ docsUrl: "/docs/device-agent/introduction/"
+ - icon: "arrows-right-left"
+ title: "Publish and store"
+ detail: "Contextualized data leaves the edge on a stable topic structure and lands in your historian or database. The schema and the storage stay yours."
+ - icon: "dashboard"
+ title: "Visualize per role"
+ detail: "A line view for the supervisor, trend detail for the maintenance engineer, a roll-up for the plant manager. FlowFuse Dashboard builds all three from the same data."
+ - icon: "rectangle-stack"
+ title: "Replicate across sites"
+ detail: "Snapshot the working application and let the pipeline push it to every other line, with each site's specifics supplied by environment variables."
+ docsUrl: "/docs/user/envvar/"
+ docsCta:
+ label: "Read the pipeline docs"
+ url: "/docs/user/devops-pipelines/"
+
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:
diff --git a/src/use-cases/shop-floor-communication.njk b/src/use-cases/shop-floor-communication.njk
index 070eede175..a1a8645826 100644
--- a/src/use-cases/shop-floor-communication.njk
+++ b/src/use-cases/shop-floor-communication.njk
@@ -6,7 +6,44 @@ meta:
problem: "The line stopped four minutes ago. The person who can fix it will find out when someone walks over."
industries: ["automotive", "food-beverage", "aviation-aerospace", "electronics-appliances"]
values: ["labor-operational-efficiency"]
-architecture: "edge-connectivity"
+howItWorks:
+ heading: "How FlowFuse builds connected andon."
+ intro: "Getting an event to the right person is a small number of pieces, not a product. The routing logic is identical at every site; only the people, channels and shift patterns differ, and that is what decides the pattern."
+ designPattern:
+ kind: "Hardware pattern"
+ name: "Pipeline plus external configuration"
+ detail: "The routing and escalation flows are built once and distributed by pipeline. Who responds, on which channel, during which shift is read at runtime from a central configuration source, so a rota change or a new contact never requires a redeploy."
+ docsUrl: "/docs/user/devops-pipelines/"
+ diagram:
+ placeholder: true
+ src: "https://placehold.co/1200x630/eef2ff/4338ca?text=Shop+Floor+Communication+Architecture"
+ alt: "End-to-end architecture for connected andon: machine signals and operator call buttons into edge instances, routed against a central directory of roles and shifts, delivered to displays, team channels and phones, with acknowledgment timing recorded."
+ caption: "Machine signals and call buttons into edge instances, routed against a central directory of roles and shifts, out to displays, team channels and phones, with every acknowledgment timed."
+ pieces:
+ - icon: "bell-alert"
+ title: "Capture the event"
+ detail: "Machine signals, alarm bits and operator call buttons all become the same kind of event, collected by an edge instance next to the equipment."
+ docsUrl: "/docs/device-agent/introduction/"
+ - icon: "queue-list"
+ title: "Model the event"
+ detail: "Each event carries type, area, severity and the role that should respond. Routing decisions are made against that shape, not against a machine address."
+ - icon: "users"
+ title: "Keep the directory outside the flow"
+ detail: "Roles, contacts, channels and the shift calendar live in configuration rather than inside the flows, so the floor can change who responds without touching the application."
+ docsUrl: "/docs/user/envvar/"
+ - icon: "share"
+ title: "Deliver where people look"
+ detail: "The same event fans out to andon displays, team channels and phones, each with the context the recipient needs to act on it."
+ - icon: "clock"
+ title: "Acknowledge and escalate"
+ detail: "An unacknowledged event climbs the chain on a timer. Nothing waits on someone happening to be free."
+ - icon: "circle-stack"
+ title: "Record the timing"
+ detail: "Event, notification and acknowledgment timestamps land in your database, which is what turns response time into a metric you can manage."
+ architecture: "edge-connectivity"
+ docsCta:
+ label: "Read the pipeline docs"
+ url: "/docs/user/devops-pipelines/"
customerPain:
heading: "Events travel at walking speed."
+