Robot or Data Infrastructure: What Comes First on the Path to a Smart Factory

Picture a metal fabrication plant outside Bursa. Management invested in a CNC robot to boost capacity — the machine runs, parts come off the line. But production planning still runs on spreadsheets, inventory is tracked on paper forms in the warehouse, and quality data lives in the operators’ heads. The robot speeds up, yet everything around it stays just as chaotic. Machine downtime goes unrecorded. No one can trace which batch caused which quality problem. The cost impact of the capacity increase cannot be calculated. The investment has been made, automation has started — but the gain is invisible.

As the concept of Industry 4.0 begins to take shape on the Hannover Messe stage, Turkish manufacturing SMEs are starting to hear the phrase ‘smart factory.’ In practice, the response tends to follow the same reflex: buy a robot, set up automation, wait for efficiency. This approach contains a fundamental sequencing error. Automation is a multiplier applied to existing processes. If those processes are disorganized, automation produces that disorganization faster and at greater cost. The question of where to invest first is therefore not a technical preference — it is a strategic decision.

What do we mean by data infrastructure? Making production processes traceable, recordable, and analyzable. This means activating the production module of an ERP system, running material requirements planning (MRP), moving quality management records into the system, and establishing cost tracking at the work order level. None of this is purely a software matter; it is equally a process standardization matter. Which operator performs which step, how does incoming raw material get logged, how is scrap reported — until these questions have standardized answers, no software or machine delivers lasting efficiency gains.

What changes when an ERP production module goes live? The first and most concrete gain is traceability. How long each work order took, when each machine stopped, how much scrap came out of each batch — all of it enters the record. Once this data starts accumulating, managers make decisions based on numbers rather than instinct. The second gain is planning reliability. When MRP runs, purchase orders are shaped by the production plan rather than guesswork; excess inventory shrinks and supply delays become predictable. The third gain is cost transparency. Data collected at the work order level shows what each product actually costs to make. Pricing decisions rest on that foundation.

Now bring the robot back into this picture. When automation is introduced after the data infrastructure is in place, machine downtime feeds into the ERP, reflects in work order durations, and updates capacity planning. Quality data can be linked to batches. The efficiency gains the robot delivers become measurable, and return on investment (ROI) can be calculated. A total cost of ownership (TCO) analysis becomes possible because maintenance, downtime, and quality costs are already recorded in the system. The investment decision is no longer based on intuition — it is based on data. In this sequence, the robot stops being a cost item and becomes a calculable strategic tool.

In practice, this transition faces real obstacles. A significant share of Turkish manufacturing SMEs still track production data on paper or in spreadsheets. The most common problem in ERP projects is not technical but behavioral: operators keep using old habits instead of entering data into the system, and managers continue requesting reports from the accountant rather than pulling them from the ERP. Building a data infrastructure therefore means more than purchasing a software license — it means redefining how work gets done. An ERP deployed without process standardization becomes a hollow shell within months: the system is there, the data is not.

For the manager at the decision point, the right question to ask is this: what share of your production processes are currently recorded and traceable? If the answer is uncertain, build the infrastructure that answers that question first. Activate the ERP’s production and quality modules, start work order tracking, run MRP. Once that foundation is solid, automation investment becomes both less risky and more measurable. A robot on the right foundation is a powerful tool. Without that foundation, it is simply an expensive machine.

This article was originally written in Turkish by Gökhan MERCANOĞLU on July 1, 2013 and has been automatically translated into English and other languages using machine translation.


For master data management, the critical question is not which system to use. The real question is which problem will be solved, which data can be trusted, and which action will be accelerated. Without these answers, solutions look modern but only digitize old habits.


Gökhan Mercanoğlu
ERP ve Kurumsal Yazılım