Consider a mid-sized metal fabrication firm in Bursa. Machines run on the shop floor, shift supervisors fill out paper forms, and at the end of the day those figures get carried over to the accounting department. The company installed an ERP system five years ago — inventory and finance modules are live, but production is still largely manual. The owner has been reading about ‘smart manufacturing’ and ‘sensor-driven production tracking’ in trade publications and is asking a straightforward question: is the ERP infrastructure already in place compatible with this vision, or does the company need to start from scratch?
Smart manufacturing, at its core, aims to capture machine data, work order flows, and inventory movements in near real time and feed them directly into transaction systems. MRP (material requirements planning) and ERP platforms have managed the planning layer for decades, but the vast majority of these systems still receive data manually or through batch file transfers rather than automatically. The gap between the shop floor and the planning system sits right at the centre of every smart manufacturing conversation.
Looking at the ERP installations across Turkish manufacturing SMEs, the picture is uneven. One segment has never activated the production module at all, using ERP purely as an accounting and inventory tool. A second group has opened the production module but closes work orders by hand. A smaller third group has started collecting production data through barcode readers or simple shop-floor terminals. That third group has taken the first meaningful step toward smart manufacturing infrastructure — not sensor integration, but at least a closed data collection loop.
So can existing ERP infrastructure carry the vision? The answer depends on the platform and the quality of the original implementation. Enterprise platforms such as SAP, Oracle, and Microsoft Dynamics are technically capable of receiving data from external sources through their production modules. The challenge is not the software itself but the middleware layer: capturing data from a machine on the shop floor requires either a terminal connected to that machine or a SCADA system. Getting that data into ERP then depends on a file transfer or a direct database connection — both achievable, but both require technical resources to build and maintain. Most Turkish SMEs lack the in-house capacity to set up and sustain that middle layer.
On the cost side, total cost of ownership (TCO) calculations are frequently incomplete. ERP licence and maintenance fees are visible; adding shop-floor terminals, building a SCADA connection, designing data transfer routines, and testing the whole chain is a separate project budget. Calculating the return on investment (ROI) for a mid-sized manufacturer is not straightforward. That said, if the right measurement points are chosen — scrap rates, machine downtime, planning variance — concrete gains are achievable. The critical step is defining upfront which data will be collected and which decisions that data will support.
In practice, the hardest obstacle is not technical but organisational. Collecting production data means the shift supervisor stops using paper forms. That transition requires process redesign and training. On top of that, ERP production modules that have sat unused for years tend to accumulate configuration gaps. Getting the system ready for real production data can sometimes take more effort than a fresh installation. A pattern that appears repeatedly in consulting engagements: the company focuses on the technical integration while the bill of materials inside ERP is inaccurate or work centres are not defined. Even if the data feed is built correctly, planning outputs remain unreliable.
For an SME manager standing at the decision point, a practical prioritisation looks like this. First, assess how complete the existing ERP production module actually is — if bills of materials, work centres, and capacity definitions are not in place, feeding data from the outside accomplishes nothing. Second, identify which production data carries real decision value; rather than putting a terminal on every machine, starting at the bottleneck reduces cost and accelerates ROI. Third, decide whether the technical capacity to build and maintain the integration will come from inside the company or from an external partner. Smart manufacturing is a compelling vision, but the journey begins with getting the existing system onto solid ground.
This article was originally written in Turkish by Gökhan MERCANOĞLU on July 11, 2011 and has been automatically translated into English and other languages using machine translation.