Case study · Kocher+Beck Polska
A production panel for Kocher+Beck Polska
Work completed, business panel in use at the company · no before-and-after measurement
I designed and built a panel for Kocher+Beck Polska, a company that produces to order. It combines data from the MES and from SAP, calculates the delivery date from lead-time history and lets you trace every figure to its source document. I describe the rollout as a management process: decisions, roles, consent for reads and changes, and release gates.
This is an English summary of the case study, which is in Polish. No screenshots and no figures from the company's data. The figures I give concern my software and are dated. I show the architecture and the methods in a conversation.
At a glance
The company, the problem, what I did and the result
- Company
- Kocher+Beck Polska, a Polish manufacturing company that belongs to the German Kocher+Beck group. It produces to order.
- Problem
- Sales were in one system and finance in another, and the delivery-date forecast from the production system did not account for queues. Management, sales and production had no shared place for the figures, so arguing over a number replaced making a decision. A salesperson had no date they could justify.
- What I did
- I designed and built a panel that combines data from the MES and from SAP. It calculates the delivery date from lead-time history, shows the shop-floor queue and on-time delivery in two variants, reconciles sales with SAP and gives B2B partners a portal with their own data. For the design department I built an add-in for Autodesk Inventor.
- I do not change the existing tables or the code of the source systems. I read them without locks, and writes to the MES go only through my own procedures in a separate database schema.
- Result
- There is: work completed, the business panel is in use at the company, and the first modules have run on the server since September 2026. The sales report from the panel matches SAP to the grosz in six report settings (checked in October 2026).
- There is not: a before-and-after measurement of the effect. That is why I quote no savings and no improvement in on-time delivery.
- What I will measure: the time it takes to prepare one management report and the number of questions to sales about a delivery date. I am agreeing the method with the company. I have not yet set a date for the first measurement, so I do not give one here. I will add it once it is agreed.
To the groszThe “Sales analysis by customer” report, reproduced in the panel, matches SAP in six report settings. I checked it in four independent ways (October 2026). I do not give the amounts.
Client's voice
You don't lay ten tiles at once, only one, then the next. But you have to know which one to take. The worker also has to know which part to take.
What I built
Modules, roles and status
Each module has three status levels. I give only what is confirmed. “Not confirmed” does not mean “no”. It means I have no confirmation.
- Built work on the module is finished
- On the client's server the module runs on the company's server
- Used daily people at the company use the module every day
| Module | For whom | Built | On the client's server | Used daily |
|---|---|---|---|---|
| The panel as a wholeWhat is confirmed without a breakdown by module. | The whole company | Yes | First modulesSince September 2026. Which ones exactly: not confirmed. | Business panelIn use at the company. Which modules daily: not confirmed. |
| Management dashboardSales, finance and production in one place, pace against the monthly target, “what needs attention” alerts. | Management | Yes | Not confirmed | Not confirmed |
| Sales and order reportsBreakdowns by customer, product, channel and account manager, offer funnel, reconciliation with the finance system. | Management, sales | Yes | Not confirmed | Not confirmed |
| On-time deliveryTwo versions: against the original promise and after rescheduling, with a written method. | Management | Yes | Not confirmed | Not confirmed |
| Delivery date with confidenceA recommended completion date in the order form and in the partner view. | Sales, partner | Yes | Not confirmed | Not confirmed |
| Order target and action listA solver for the monthly target: open offers, each with a reason to go back to it. | Sales, management | YesScope: first stage, with the action list. | Not confirmed | Not confirmed |
| Production analysisShop-floor queue, job sequence, orders with no movement, reorder point, chance of finishing on time and a “slowed down” alert. | Production manager | Yes | Not confirmed | Not confirmed |
| Sales moduleOffers, orders, customers and suppliers, price calculator. A logged-in employee issues the document, and the write goes through procedures. | Sales | Yes | Not confirmed | Not confirmed |
| B2B partner portalOrders, offers, production, calendar, shipments, status calculated from events. A partner sees only their own data. | B2B partners | Yes | Not confirmed | Not confirmed |
| AdministrationPermissions, partner access, targets and thresholds, system status. The process owner controls them without a programmer. | Process owner | Yes | Not confirmed | Not confirmed |
| AI layerCommentary on aggregated figures and an analytical assistant that works on aggregates. | Management | YesSwitched off in the base configuration. | Not confirmed | Not confirmed |
| Mobile accessRead access on a phone, as an app installed from the browser. | Internal users | Yes | Not confirmed | Not confirmed |
The full version
The rest is in Polish
The Polish case study also covers the starting situation, the six mechanisms of the panel, the rollout as a management process, the architecture and the current status. Read the full case study (in Polish).