01
Vision-based quality inspection
In-line defect detection and classification on surfaces, welds, assemblies and print. Runs at line rate on edge hardware, with a review loop that keeps producing labelled data.
- Moves
- Scrap and escape rate
03 Industrial practice
Not a portal, not a dashboard programme. Systems that change what a line does, engineered for brownfield reality, segmented networks and people who will judge them on a night shift.
01 Where the value sits
Chosen because the decision is frequent, the ground truth is obtainable, and the improvement is measurable on a P&L rather than in a slide.
01
In-line defect detection and classification on surfaces, welds, assemblies and print. Runs at line rate on edge hardware, with a review loop that keeps producing labelled data.
02
Asset health from vibration, current, thermal and process telemetry. Ranked by remaining useful life and by what a failure actually costs, not by anomaly score.
03
Constraint identification across the line, then closed-loop or advisory set-point recommendation. Usually the highest-return work and the least glamorous.
04
The unglamorous prerequisite: OPC UA / MQTT collection, contextualisation against asset hierarchy, historian and lakehouse landing, quality monitoring.
05
Calibrated models used to evaluate a change before committing the line to it — scheduling, energy, changeover and capacity scenarios.
06
Retrieval and agentic assistance over SOPs, maintenance history, drawings and tribal knowledge, delivered where the work happens. Cited, sandboxed, and safe to be wrong out loud.
02 Reference architecture
A shape, not a product list. Every engagement adapts it — but the layering, the contracts between layers and the direction of dependency stay fixed.
L5
L4
L3
L2
L1
L0
Data and context flow upward · control and intent flow down · contracts at every boundary
03 Design constraints
These are not caveats. They are the design inputs that separate systems which get adopted from systems which get bypassed.
Equipment from four decades, three protocols and two acquisitions. We design for what is on the floor, not for a reference architecture diagram.
Integration work is planned around production windows and validated in a way that does not require faith. Rollback is rehearsed before rollout.
Purdue-model boundaries, one-way data diodes and sites with no cloud egress at all. Edge-first designs, offline capable, with sync as an optimisation.
Nothing we build sits in a safety-instrumented loop without an explicit, reviewed hazard analysis. Change control records are produced as we go.
A system that gets routed around has failed regardless of its metrics. We design with the shift, not for a stakeholder in a different building.
Your maintenance and automation engineers are the long-term owners. Enablement is part of the plan, not a closing workshop.
04 First engagement
The shape of a first engagement with a manufacturer. Deliberately narrow — one cell, one constraint, one measurable outcome your own people can verify.
Stage one
Stage two
Stage three
"An honest stop" is a real outcome. A meaningful share of diagnostics conclude that the economics do not support the project yet — usually because the ground truth is not obtainable at acceptable cost. Establishing that before a programme is committed is the cheapest finding available.
Manufacturing brief
Tell us about the line, the data you have, and the number you are trying to move. We will come back with an honest read on tractability and a costed option set — or a recommendation to fix something else first.
or write directly — hello@bluestreaklabs.com