Skip to content 
In custom machine building, production flow is the system that carries a machine that has never existed before from brief to final testing. The stages stay fixed, the rhythm is set by project milestones rather than takt time, and waste is driven out by proving parts before they ever reach the machine. The flow repeats on every project. The product never does.
What does production flow mean when every product is a first?
The same thing it means in any plant: work moving through defined stages at a steady rhythm, with waiting and rework driven out. What changes is the object that flows. In serial production, thousands of parts move through fixed stations. In a machine builder’s workshop, one machine moves through fixed stages, and each stage handles content nobody has handled before.
Lean production flow earned its place as the reference model of manufacturing, and it earned it honestly: a defined sequence, identical cycles, improvement compounding over long runs. That model is not the thing we are correcting here. It is the thing we translate. A first machine runs on a production system of its own, where engineering, build, and test overlap and the flow forms around one product. That article states the principle. This one is about how the flow operates day to day, on the floor, when there is no repeating cycle to lean on.
Which flow principles carry over to a one-off build?
Most of them, translated. The principles behind serial flow do not disappear when the product is a single machine; they change form.
| Flow principle | In serial production | In a one-off build |
|---|---|---|
| Cycle | Thousands of identical cycles | One machine moving through fixed stages: design, workshop, assembly, testing |
| Rhythm | Takt time paces every station | Milestones pace the project: design freeze, mechanical completion, power-on, first cycle |
| Standard work | Defined per station and per part | Defined per stage; the sequence is standard, the content is engineered fresh each time |
| Waste removal | Refined cycle after cycle over the run | Functions proven at the bench before integration, so rework stays off the machine |
| Learning | Incremental, spread across production | Concentrated in weeks of build and test, then carried into the next project |
The last row is the one customers notice least and benefit from most. Products differ from project to project; the way a machine comes together does not. Mounting interfaces, wiring standards, software structure, test procedures: these get better with every machine and belong to the flow, not to any single product. A customer buying a first machine is buying the last machine’s lessons without paying for them again.
How does the flow run on the workshop floor?
One machine, one bay, one team. Each machine gets its own bay and keeps it until final testing, so the work is never shuffled aside to make room for another job. The mechanical fitters, the electrical team, and the software engineer work on the same machine at the same time, not in a relay: while stations are still being fitted at one end, the first commissioned station is already cycling at the other. That overlap is the whole point. It is how a build with no repeating cycle still keeps a rhythm.
Anything in doubt goes on a bench first. A fixture or a subassembly whose behavior is uncertain runs on its own, off the machine, until it does what it is supposed to. A problem caught on the bench costs hours; the same problem caught on the fully assembled machine costs days, because now it hides behind everything mounted around it. Keeping unproven parts off the machine is the one-off version of keeping defects off the line, and it is where most of the schedule is won or lost.
Design sits close to the bays for the same reason. When the fitter mounting a fixture hits an interference, the engineer who drew it walks over, decides at the machine, and updates the model that same day. The correction gets absorbed now, in one conversation, instead of being discovered again downstream. The stages themselves have exit conditions that keep this honest:
| Stage | It is done when |
|---|---|
| Design | The design is frozen and the long-lead parts are on order |
| Workshop | Frames, fixtures, and stations are machined and fitted |
| Assembly and integration | Mechanics, electronics, and software run together as one machine |
| Testing | The machine runs the real part at its target cycle and is documented |
No stage opens the next one until its own exit condition is met. Freezing the design before the workshop cuts metal is not bureaucracy; it is what stops a late drawing change from turning into scrapped hardware.
Does flow thinking reach the delivered machine?
Yes, in how the machine is specified and in how it lands. A machine engineered by people who think in flow is designed around the takt of the line it will join: its cycle time, how operators load and unload it, and how parts arrive and leave, for example on a line with pallet conveyors. Getting those right is much of what makes a manual line worth transforming into an automatic one. A machine that ignores the line’s takt can look finished and still starve the station upstream or flood the one downstream. The same thinking shapes loading and unloading, so an operator’s cycle matches the machine’s rhythm instead of fighting it. That is the difference between a machine that runs and a machine that runs in the line.
The flow keeps running after delivery, too. When the product changes, a machine changeover replaces fixtures, heads, and parameters while the base machine stays in service, so the line’s rhythm survives the product’s evolution instead of ending with its first version.
Is building a one-off machine a production system or craft work?
A production system, run with craft-level care. The parts are machined and fitted by people who take pride in the work, but every project moves through the same engineered sequence: design, workshop, assembly and integration, testing. What varies is the machine. The discipline that builds it does not.
How is lead time kept under control without repeating cycles?
Through the stages and their exit conditions. The design is frozen before the workshop cuts metal, long-lead components are ordered at that freeze, and every function is proven at the bench before it reaches integration. Lead time in a one-off build is lost to rework and waiting, so the flow is built to keep both off the machine.
Does the flow improve if every product is different?
Yes, because improvement attaches to the stages and the standards, not to the product. Every machine leaves something behind in the flow that the next one inherits: a cleaner interface, a better test procedure, a wiring standard that saves a day. The product resets each time; the flow only compounds.