Consider a mid-sized automotive supplier in Bursa: the company has installed new CNC machines on its production floor and attached temperature and vibration sensors to several workstations. The plant manager wants to monitor this data continuously, but the existing ERP system cannot receive or process it. Machine status is still recorded on paper at the start of each shift and entered manually into the system. The sensors are there, the data exists, but none of it reaches the ERP. This is not a hypothetical — it is the operational reality at many Turkish manufacturing firms right now.
The smart factory concept assumes seamless data flow between machines, sensors, and software systems. In this model, an ERP platform is not merely an accounting and inventory tool; it serves as an operational backbone that processes real-time data from the production floor, dynamically updates capacity plans, and coordinates with the supply chain on a continuous basis. Most Turkish SMEs have not yet built this backbone. Their ERP systems were implemented in the early or mid-2000s, configured for the requirements of that era — adequate for accounting, invoicing, and basic stock management, but structurally insufficient for production intelligence.
Two technical fault lines define the problem. First, most legacy ERP systems operate within a closed architecture: they offer no standard interface for receiving external data streams and require custom development to connect with anything outside their own modules. Second, their underlying data models were designed around periodic batch entry — daily, weekly, or at best hourly updates. Sensor data, by contrast, updates in seconds. When these two architectures are placed side by side, the mismatch becomes structural: sensors are fast, ERP is slow; sensors are continuous, ERP is periodic; sensors are automated, ERP depends on manual input.
The business cost of this gap is concrete. When real-time machine data cannot reach the ERP, capacity planning relies on historical averages rather than actual floor conditions. Predictive maintenance becomes impossible; downtime is recorded only after it occurs. Inventory consumption is not synchronized with production pace, creating simultaneous risks of excess stock and critical material shortages. When total cost of ownership (TCO) is calculated properly, these inefficiencies represent a measurable annual burden — yet in most companies they are classified as operational losses rather than ERP-related costs, which keeps them invisible in technology investment discussions.
Two paths exist for closing this gap. The first is to extend the production module of the current ERP and use a middleware layer to feed sensor data into the system. This approach requires lower initial investment but tends to carry high long-term maintenance costs, and it does not resolve the architectural constraints at the core of the system. The second path is to migrate to a newer ERP platform designed for production data management. This means higher upfront investment and a longer transition period, but when ROI is modeled over a five-year horizon, it frequently outperforms the first option for firms with significant production volume. Which path makes sense depends on the complexity of the production environment, the age of the current system, and the firm’s growth targets for the coming years.
There is a practical constraint that deserves direct attention: sensor integration is not purely a software problem. The industrial network infrastructure on the factory floor, the communication protocols of existing machines, and data security requirements all factor into the equation. In many mid-sized Turkish factories, industrial networking either does not exist or runs entirely separate from the office network. Identifying these infrastructure gaps before beginning an ERP modernization project is essential — without this step, even a well-chosen ERP platform will fail to deliver the expected results, and the project will encounter unexpected costs mid-implementation.
For decision-makers, a clear priority sequence helps. Start by technically evaluating what your current ERP production module can actually receive and process in near-real time — test it, do not assume. Then map the network and sensor infrastructure on your factory floor. Once these two assessments are complete, the scope and timing of a modernization investment can be defined on solid ground. The smart factory is a legitimate strategic direction. But the first step toward it is not buying new equipment — it is taking an honest look at where your ERP infrastructure stands today.
This article was originally written in Turkish by Gökhan MERCANOĞLU on April 23, 2012 and has been automatically translated into English and other languages using machine translation.