Learning last month's numbers on the fifteenth means the chance to intervene has long since passed. We build a dashboard where you see production, stock, orders, delivery dates and collections every morning from the same place, with the same definitions, on your phone. The data comes from your facility in Başpınar; the definitions are agreed at your own desk in your Şehitkamil office.
The hard part is not drawing charts; it is tying each figure to a single definition of what it counts. That is why we start every dashboard with definition work. We have previously built an eleven-module management panel on the factory side; the headings below come from that work and from the integration layers we have built alongside ERPs.
Data from the ERP, production tracking, weighbridge, warehouse and shop-floor entries is gathered into a single reporting layer. Figures no longer change depending on whose Excel they came from. This layer does not replace your ERP; it is a separate structure that reads on top of it and keeps heavy queries from loading the core system.
Quantity produced per shift, running time, downtime and waste — broken down by line, loom or machine. It can be checked during the day, without waiting for the end of shift and the paperwork. Where we pull the data from depends on the site: terminal entry, weighing, counters or your existing production software.
What is on hand, how much is reserved against orders, which order ships on which date and which has slipped — all on one screen. For export orders, a countdown against container and loading dates is shown; the slippage appears before the date passes, not after.
Receivables due and overdue, ageing by customer and the collection trend all sit in the dashboard. You spot the customer whose payment is late by looking at the screen, not by relying on whoever remembers. Who can see which figures is restricted by role.
So you are not forced to check the dashboard every day, thresholds are defined: downtime beyond a set duration, critical stock levels, balances over their limit, delivery slippage. When a rule fires, a notification arrives. The dashboard stops being a screen you watch and becomes a system that tells you.
The main screen is not a shrunken desktop report; it is designed for the phone from the start. The day's summary is visible at a glance, with the detail one tap below. A dashboard you can check at the factory, on the road or in front of a customer is the only kind that actually gets used.
Before any charts, we define the question. Which five figures do you want to see first thing in the morning; which figure keeps you awake at night. This list stays short, and it is what shapes the dashboard; a crowd of gauges helps nobody.
We come to your facility in Başpınar and trace where each figure is actually born: who enters what on which terminal, where the weighbridge is read, where the shift sheet goes, when it lands in the ERP. A figure whose source has not been seen cannot be trusted on a dashboard either.
We put concepts such as waste, yield, open orders and available stock into a single written definition. We then compare the figures the dashboard produces against accounting's and production's own numbers. The dashboard does not go live until those figures agree.
We start with a single topic, usually daily production or collections. It stays in real use for a few weeks; the indicators nobody looks at become obvious and the board is simplified. It improves by removing, not by adding.
Other topics are added in turn, and each role gets the screen it is meant to see. We continue under a maintenance and support agreement. Source code and data stay with you; you are never locked into us for the next report.
That is where most factories start. Our approach is to build the first board from data that is already solid in the system, and queue the paper-based areas as separate work. To bring paper data into the board, we set up either a simple entry screen or shop-floor data capture. We never fill missing data with estimates and present it as real; where data is missing, the dashboard shows it as missing.
No. The dashboard does not replace your ERP; it reads on top of it. Your Logo, Mikro, Netsis or SAP backbone stays in place; we build a separate reporting layer and pull the data from there. This has a further benefit: heavy reports do not strain the core system, because the queries run in the separate layer.
This happens at the start of almost every rollout, and it is actually useful, because it exposes differences in definitions. That is why we run a reconciliation step before going live: we compare the dashboard's figures against accounting's and production's own numbers, and where they differ we document which definition caused it. The dashboard does not open until the figures are reconciled; nobody looks twice at a dashboard that does not add up.
Sometimes it is, and we will tell you so openly. Off-the-shelf tools deliver quickly for companies whose data is already tidy and in one place. The difficulty usually lies not in the tool but in the data beneath it: if the sources are scattered, the definitions differ and shop-floor data is missing, the picture stays the same whichever tool you buy. The bulk of our work is in that lower layer; the visualisation on top is the easiest part.
The main screen is built with few enough indicators to be read at a glance; the rest sits in the detail layer. We define role-based screens: what management sees is not what the production supervisor or finance sees. Once real use shows which indicators nobody ever looks at, we simplify the board.
Access is set up per user and per permission, sessions are logged, and access can be shut off from one place if a device is lost. Who can see which figures is restricted by role definition; sensitive items such as revenue or costs are not opened to everyone. On screens containing personal data, we recommend keeping access rights as narrow as possible.
Yes. On the factory side we built an eleven-module management panel, set up a production layer that runs alongside an ERP without touching it, and delivered systems that take data straight from the shop floor, such as a weighing and labelling station. We have also carried out reverse-engineering work extracting the calculation logic inside enterprise applications on an evidence basis; that work makes questioning where every figure comes from a habit. We do not name clients, and we do not invent result percentages.
The duration depends on the state of your data sources, not on the number of indicators, so we do not quote a day count up front. We pick a single topic to start with, usually daily production or collections. This first board is useful in itself and it also reveals the true state of your data quality; the plan for the next steps is made by looking at it.
Let's discuss that question at your facility, at your own desk. We trace together where the data is born today and put in writing what the first board should show. We visit factories in Başpınar OSB and Şehitkamil and do the discovery on site.
