Manufacturing software development: from job ticket to reporting.
Manufacturing software development starts where the paper sits: the job ticket at the machine, the inspection record at the test bench, the shift book in the office. Beside it, a grown spreadsheet holds a core process together.
Understand first, then build
A grown quoting file holds more domain knowledge than any specification. We read it before we replace it.
Paper leaves the shop floor
Job tickets, shift handovers, inspection records and fault reports belong on a device, captured where they arise.
Internal becomes customer-facing
Some spreadsheet is a customer portal that nobody has built yet.
Paperless manufacturing: what we build.
-
Digital job tickets and production data capture
The work step is confirmed at the station and the order status is live. Nobody walks the shop floor to find out any more.
More on this
Large buttons, few fields, readable under shop lighting and operable with work gloves. Capture runs offline and syncs on its own. On terminals, tablets and handhelds, as a web application or a native app.
-
Inspection records and fault reports
Capture readings at the test bench with plausibility checks and a photo. Report faults in a structure that makes frequency, duration and cause reportable.
More on this
The shout across the hall turns into a figure that justifies an investment. The same structure under regulatory pressure: Pharma & Life Sciences.
-
Replace the grown Excel quoting file
Complex quotes get built in Excel, because the matching ERP change was never commissioned. We read the file before we replace it.
More on this
We separate domain knowledge, historic ballast and detours that only exist because Excel forced them. Your own people maintain the pricing rules afterwards. The approach: Excel and VBA modernization.
-
The quoting file becomes a customer portal
If the quote goes to the customer as a PDF anyway: configure variants, see the price, send the enquiry.
-
The ERP stays in charge
SAP or Business Central keep master data and posting. We capture in front of them and hand over through the existing interfaces.
More on this
With SAP through OData or REST services, with Business Central through its API. The core system stays untouched, which keeps sign-offs and upgrades simple. Steering: ERP Project Management.
How many spreadsheets hold your production together?
Tell us where notes, shouts and spreadsheets carry the process. We say what an app solves and where your MES is enough.
Common questions from manufacturing and industry.
Why not buy an MES?
If a standard product covers your case, do that: it is cheaper than anything we build. Manufacturers come to us for two reasons. Either the case is too specific, such as quoting logic no standard knows. Or it is a single process for which an MES rollout would be oversized.
Our quoting sits in a huge Excel file. Can that be replaced?
Yes, and the effort rarely sits where people expect. Rebuilding the formulas is craft work. The work sits in the analysis: which calculation paths still hold, and which special cases are ballast?
What happens to the knowledge of the person who built the file?
That is the most important question in the project, and we ask it first. That person is our main counterpart. We document the logic while we translate it, so the knowledge ends up in the system.
Does capture in production need works council approval?
For systems capable of monitoring behaviour or performance, co-determination is almost always required where a works council exists. We raise it early and build with data minimisation. The employment law assessment stays with you.
How do we start small?
With one process, one station, one shift. What holds up gets rolled out, what does not has cost little. The most common mistake is starting with the largest process.
Does the digital product passport affect us?
Possibly. The first ESPR work plan prioritizes iron and steel, aluminium, textiles, tyres, and furniture and mattresses, among others. Batteries run under their own regulation with a deadline from February 2027. Details: digital product passport.
Read on.
Which file would you miss?
If the answer is a name and not a system, a conversation is worth it.
From job ticket to reporting.
Name the process: the Excel quoting file, the note on the shop floor or the report nobody can pull.
We usually reply within 24 hours.
Remote and on site in Germany, Austria and Switzerland. International projects on request.