Everything I write orbits one belief: you can own your factory again, from the data to the software to the decisions. This page is the map, with the six shifts that move a metal shop from buying blind to choosing clearly and from averages to real-time steering.
I rebuilt this site and got something wrong in a way that applies to your shop. I had built every piece by hand, and it ate the hours that belonged to client work. So I moved to a tool I host myself, kept control of the data, and gave the plumbing less of my time.
I run my own shop on open-source software, and these are the seven tools I reach for first. The list covers a Unified Namespace, an MES, an ERP, and the rest of the stack you can self-host for free. I explain what each one does and where it fits.
I see the same story in metalworking shops: the ERP arrives, the MES follows, and the dashboards still are not trusted. Three building blocks separate digitalization that works from digitalization that frustrates: paperless, connected, and real-time.
I spent years connecting ERP systems to real shop floors, and I watched custom work turn a strong system into a bottleneck. Here is the architecture that scales instead: a central source of real-time truth, with ERP handling orders and accounting while operations run on a lighter layer.
Denis Gontcharov and I talk about the bad data that quietly erodes trust in every dashboard. I ask him where quality checks belong in the pipeline, and which open-source tools catch problems before they reach the ERP.
The monolithic ERP is finished, even though ERP itself is not. I explain why accounting-first systems break under the speed and volume of shop floor data, and how ERP fits as one node in a distributed ecosystem built on a Unified Namespace.
Denis Gontcharov and I share a real deployment of a Unified Namespace at a Dutch welding shop, finished in a single day. I explain why the point-to-point link between ERP and MES kept breaking, and what the shop saw once the data ran live.
I pick the free 3D CAD viewers I would install in a metal shop today. One question sorts the list: whether your customer's file stays on your machine or quietly goes to someone else's cloud. You get the everyday viewer, the shop-floor option, and the browser tool.
Denis Gontcharov and I take on the idea that the cloud is only for big enterprises. I ask him how a smaller metals shop moves shop floor data to the cloud, and how predictive maintenance pays off first.
Russ Waddell joins me to unpack what factory connectivity actually means, because every side of the industry defines it differently. I ask him how to start a first project, and why clean, accessible data decides what AI can do later.
I treat an MES as a function rather than a product, and that changes how you shop for one. I lay out the four jobs it must do, the five routes a metal shop can take, and how to choose for high-mix work. Building your own is one of them.
Digital transformation keeps disappointing because tools get bought before the data architecture exists to connect them. I explain the Unified Namespace in plain words: one live place where all factory data comes together, organized the way the business is organized.
Brian Pribe of MACH Controls joins me to make the Unified Namespace practical for smaller manufacturers. I ask him how MQTT and Kafka fit together, and how open source keeps the first step within reach.
Todd Abraham of InnoVaas joins me to compare how the Unified Namespace is spreading in Asia and Europe. I ask him how small shops can start with one problem, and why structured data decides what machine learning can do.
Wim Dijkgraaf of QuotationFactory joins me to explain why real-time events beat the ERP for understanding a high-mix shop. I ask him how event-driven architecture and a Unified Namespace make manufacturers more agile and reliable.
Standing under a cathedral, I wondered how its builders stayed motivated for a project that outlived them. Metalworking has the same long horizon: the parts you make for renewable energy and efficient machines become the foundation of a sustainable future.
Angelo Hulshout joins me to look at why Unified Namespace adoption in European metals is a culture question before a technology one. I ask where a manufacturer can start small, and which low-risk wins prove the value first.
Digitalisation goes wrong in predictable ways, and I hear the same four traps again and again. This piece names them: the urgency trap, the attention trap, the moving train trap, and the IT/OT silo trap. For each one I give you the way out.
Denis Gontcharov and I talk about why domain knowledge still decides what AI can do in a metals plant. I ask where expertise gets lost in the rush to automate, and what the factory of the future keeps in human hands.