Fit-up is the weld decision nobody logs
Root gap and alignment cause more lack of fusion than any parameter choice, yet almost no shop records them per joint. What changes when you do.
Engineering writing about the parts of welding autonomy that are genuinely hard: measuring fit-up, planning heat, reading indications, and agreeing what a pilot actually proved.
Three pieces on the upstream decisions that determine weld quality.
Root gap and alignment cause more lack of fusion than any parameter choice, yet almost no shop records them per joint. What changes when you do.
Five lines, two arguments, and how to settle attribution before integration week rather than after the review.
Modelling what happens to takt when the constraint station cannot be staffed at all — and why overtime stops working sooner than expected.
Industrial AI is full of claims that cannot be checked. Accuracy figures with no baseline, yield gains with no attribution, autonomy demonstrations on joints chosen for the camera.
Writing is the cheapest available correction. If we describe our method in public — how we baseline, how we attribute a rework hour, how we handle a low-confidence indication — then a welding engineer can tell us where we are wrong before a customer pays for the lesson.
So the journal is technical, specific and occasionally unflattering to us. That is the point of it.
How Weldeon decides whether something worked.
Mix, shift pattern and seasonality — and the four weeks that decide whether your pilot means anything at all.
Rework is booked to the station that repaired it, which systematically hides the station that caused it.
Why model confidence should stop a cell rather than colour a dashboard.
The physics and craft the platform has to respect.
Why holding kJ/mm across a real joint requires continuous control rather than a number entered at shift start.
Treating weld order as something to optimise rather than inherit, and what it saves at block erection.
Sitting with qualified inspectors adjudicating machine calls, and what disagreement taught us about our own thresholds.
Architecture arguments, in public.
Enforcement below the intelligence: where to clamp a qualified range, and why every other location eventually fails.
What a welding control loop's latency budget is actually spent on, line by line.
Traceability compiled afterwards is always incomplete. Traceability produced by the controller cannot be.
“If we describe our method in public, a welding engineer can tell us where we are wrong before a customer pays for the lesson.”
Longer arcs we return to.
Cutting, forming and fit-up — the decisions made before the arc that determine whether the weld can succeed.
Radiography, ultrasonics and vision, and what machine interpretation changes about the inspection bay.
Takt, line balance and the constraint station, in shops that cannot hire their way out.
Baselines, attribution and scorecards — how to prove an industrial AI claim honestly.
4
running series across process, systems, rate and evidence
12
pieces written and queued for individual publication
0
vendor-sponsored posts, now or later
100%
of methodology claims accompanied by their measurement definition
We publish guest pieces from welding and quality engineers, and we pay for them.
One email when something substantial is published. No campaign sequences, no drip.
Book a pilot on one cell or line. We agree the scorecard before we start — first-pass yield, rework hours, defect escapes, takt — and we report against it in the open.