Walk through any manufacturing facility and the question almost asks itself: what if we monitored this machine’s temperature, output rate, and status in real time? The question is legitimate. But the one that follows — who will read this data, what decision will it inform, and what will that decision be worth to the business — rarely gets the same attention. The Internet of Things, a term gaining real traction in technology circles, sits at exactly this intersection: genuine opportunity on one side, expensive distraction on the other. What separates the two is asking three questions in the right order: what to connect, why to connect, and how it will generate returns.
The concept itself is straightforward. IoT refers to physical devices — machines, sensors, meters, vehicles — that generate and share data over a network. When that data stream is fed into enterprise systems, ERP modules, or a centralized monitoring platform, it can inform decisions that were previously made on intuition or delayed reporting. In Turkish manufacturing, logistics, and retail, pilot deployments are beginning to appear; but most of them start with technology curiosity rather than a defined business problem. The result is predictable: expensive sensors, unprocessed data, and frustrated project sponsors.
The first question — what to connect — looks deceptively simple. Technically, almost anything can be connected. But the connection decision should begin with an operational inventory, not a product catalogue. Which equipment failure brings production to a halt? Which process generates cost overruns precisely because its status is invisible? Where are managers currently making decisions based on estimates rather than facts? The answers to these questions naturally surface the candidates worth connecting. A connection list built this way has a defensible business rationale; one built from a vendor brochure does not.
The second question — why to connect — is the heart of the business case. There are three credible justifications for connecting a device: improving operational efficiency, reducing a defined risk, or creating a new revenue stream. A cold-chain logistics company that monitors in-vehicle temperature in real time can prevent product spoilage, protecting both margin and customer relationships. A textile factory that tracks energy consumption on dyeing machines gains a lever for optimizing its electricity bill. These justifications are specific and measurable. When the justification is simply ‘to collect more data,’ the project budget becomes indefensible the moment it faces scrutiny.
The third question — how it will generate returns — forces a TCO and ROI calculation. On the cost side: sensor hardware, network infrastructure, data storage, integration development, and ongoing maintenance. On the return side: reduction in unplanned downtime, lower excess inventory, energy savings, or measurable improvement in customer retention. Without this calculation, committing to an IoT project is the equivalent of buying equipment without asking the price. For SMEs where capital is constrained, putting this analysis on paper — even in a basic spreadsheet — is not optional. It is the minimum standard for a responsible investment decision.
In practice, the most consistent obstacle is integration. How does data from sensors flow into the existing ERP or accounting system? Most projects hit an unexpected wall here: legacy software architectures were not designed to receive external data feeds. File-based transfers or custom-built interfaces add both time and cost, often in ways that were not anticipated in the original project scope. Data quality compounds the problem. Raw sensor output requires cleaning and validation before it becomes a reliable input to any report or decision. Projects that do not account for these realities early tend to absorb their surprises at the worst possible moment — during go-live.
The practical test for any manager considering an IoT investment comes down to three written answers: what specific operational problem does this connection solve, what is the annual cost of leaving that problem unsolved, and what is the expected payback period in months? If all three answers are clear and defensible, the project deserves a green light. If the answers rely on ‘value will emerge over time’ assumptions, holding the budget is the more disciplined choice. The Internet of Things offers a genuine competitive edge when it is built on a sound business case — but that edge belongs to the questions, not the technology.
This article was originally written in Turkish by Gökhan MERCANOĞLU on February 18, 2013 and has been automatically translated into English and other languages using machine translation.