Tempus Fugit — and the Knowledge Leaves With It

A Roman mosaic says it in two words: tempus fugit. Time flies. The inscription reads as decoration until you stand in front of it long enough to feel its weight. I work at the unglamorous end of that sentence — capturing and structuring knowledge before it disappears — and I can tell you that two thousand years of human enterprise have been lost not to destruction but to the quiet failure to write things down.

The demographic arithmetic in German Mittelstand manufacturing is not speculative. It is dated and it is moving. An entire generation of engineers, machinists, service technicians, and production planners is retiring across the next decade. What leaves with them is not their titles. It is the pattern behind the fault they could diagnose by sound, the sequence they ran when three variables broke simultaneously, the institutional memory no ERP system ever captured because no one thought to ask. That knowledge was the competitive advantage. It was rarely written down. It lived in people. And people retire.

The error I see most often is to call the solution “scanning the documents.” It is not. Captured documents are raw material, not structured knowledge. The work requires structuring the tacit: the why behind the decision, not just the decision; the pattern behind the fix, not just the fix; the exception that overrides the procedure, and the condition under which it applies. That is what makes knowledge retrievable and teachable. The output is the organisation’s memory — made searchable, surveyable, transferable to the person who was not in the room when the master machinist diagnosed the fault he has heard a hundred times and you are hearing for the first.

At the VDMA Praxistag KI in Frankfurt this month, practitioners from German machine-building named structured knowledge access for fault resolution among the highest-priority first applications for AI in their industry — not because it is technically impressive, but because the business case is immediate and the cost of not doing it is already visible in the service queue.

One more thing, because it bears on sovereignty: the knowledge base this work produces is yours. It resides on your infrastructure, under your governance, not in a vendor’s cloud where it is accessible to anyone whose contract allows it. Knowledge is an asset. An asset you cannot locate — or that quietly leaves the building — is not an asset at all.

Tempus fugit. The mosaic is two thousand years old and it is still right. The question is not whether to capture. It is whether you have started.