Feedback in the same moment
Whoever books sees the effect at once: stock, redox, cost. Not the next morning during reconciliation.
Jan Wagner · software for industrial processes
Production software for flows that cannot afford to break.
I help production companies turn side calculations, quiet corrections and uncertain shift handovers into dependable digital flows. My starting point is container-glass production — where recipe, material, booking and the next shift need one shared truth.
FEEDER · 1150 °CGOB · 1050 °CBLANK MOULD · 900 °C
For whom
When the flow matters more than the demo.
I work where domain knowledge, data and operations meet — from the first process map to a stable application.
What we are after
Software that widens the view.
Industrial software is rarely opened willingly. Most of the time it is a mandatory field between the hall and the office. I build it so that it gives something back: feedback in the same moment, a readable day, and connections that never sat side by side on paper. A tool people like using gets used — and only software that gets used improves operations.
The day becomes readable
A shift sees where it stands and what is missing before handover. That is not a progress bar, that is the state of the hall.
See more than before
Recipe version, consumption and cost sit in one place. Seeing them together leads to different decisions than a stack of lists.
Working together
Four ways of working together.
Process analysis
We walk the flow that currently ends in copies, side calculations or quiet corrections. You get a map of the breaks and an order in which the work is worth doing. The walk through the hall comes first. A workshop or a tool comparison does not replace it.
Start a conversationProduct and backend
I build or steady the application where the data model, domain logic and operations meet. Typical work is booking chains, versioned master data, calculations bound to the recipe version, and a close a shift can repeat.
Start a conversationApplications on request
When a process today consists of forms, mail attachments and one spreadsheet, I build the application that turns it into a single case. For Android, Windows, Linux or the browser, depending on where the work happens. Documents, administration, approvals: the cut follows the process, not the platform.
Start a conversationWork inside a team
I sit where operations and engineering otherwise miss each other: integrations, accumulated code, decisions that get expensive after go-live. I do not deliver a second architecture on the side.
Start a conversationWhat shapes the work
Industry experience, product responsibility and an approach you can inspect.
Batchmaker family · Vanilla operations
01W-Make Batch · Vanilla
The domain reference. Bookings, stock and shift handover stay in one model.
The complete operations version for container glass: from batch ticket through silo and batch book to the daily log.
- 01
Recipe
Composition, version, temperature and cost stay tied to later consumption.
- 02
Ticket
The ticket is the order to the scale, not a printout of a table.
- 03
Silo
Consumption leaves the stock. After that the booking is part of the hall.
- 04
Batch book
What was weighed stays bound to the batch and the recipe version.
- 05
Log
The day closes as a state the next shift will find, not as an exported list.
One flow, one model
From recipe to shift close.
Recipe
Version and composition define the domain starting point.
Batch sheet
The weighing instruction stays bound to the recipe.
Silo
Consumption and stock move as one shared state.
Shift close
The day ends with a record people can inspect.
30-min analysis · free
Describe the process that's breaking today.
Describe the flow that currently ends in copies, side calculations or quiet corrections. I reply within two working days and will honestly tell you whether I can take the case.
Start a conversation