The Plant Does Not Need More Data. It Needs Better Decisions.
An anonymized case study on industrial IoT, prediction, and the quiet battle for control inside process plants
I have spent a good part of my career watching companies discover the internet of things and reach the same conclusion at roughly the same speed. Connect the machines. Collect the data. Put it in the cloud. Build a dashboard. Call it a platform. Wait for the business to transform.
It never quite works that way.
I have been through this cycle in several contexts - with clients, with partners, with companies building the hardware and companies buying the services. The pattern is consistent enough that I have come to think of it as a structural problem rather than an execution problem. The research confirms it. Estimates of IoT project failure rates consistently range from 60 to 80 percent, and a Cisco survey of nearly 2,000 business and IT decision-makers found that only 26 percent could point to at least one IoT project they considered genuinely successful. The technology works. The connection gets made. The data flows. And then, somewhere between the dashboard and the promised business impact, the project stalls. Not because the technology failed. Because nobody stopped to ask which business problem the data was actually supposed to solve, and whether the people collecting it were in any position to solve it.
When IoT and connected things are the answer, what was the question?
This piece is about a company I know from that world. I have worked with them as a hardware partner. They make measurement instruments for process industries: chemical plants, water systems, food and beverage, life sciences, energy assets. Good equipment, solid reputation, long customer relationships. Over the past few years they have started moving upstream, building out a digital ecosystem that connects their instruments to cloud-based backends and frontends, showing data streams from field devices in dashboards, offering diagnostics and asset management. The direction is right. The risk is real.
What a process plant actually looks like
A process plant is not a data-poor environment. It measures pressure, flow, temperature, level, quality, pH, conductivity, density, and dozens of other variables, continuously. The problem is not that the plant is blind. The problem is that most of what the plant knows does not automatically become a better decision.
Operators are trying to keep production stable. Maintenance teams are trying to prevent downtime. Quality teams are trying to avoid deviations. Compliance teams are trying to keep records complete. Plant managers are trying to protect uptime, safety, and margin. Everyone is making decisions under imperfect information, and the information they need is scattered across automation systems, vendor portals, maintenance software, local spreadsheets, PDF manuals, and the head of the technician who has worked on that unit for twenty years.
So plants develop practical substitutes. Fixed maintenance schedules. Alarm response. Manual checks. Conservative spare-parts inventory. Experienced operators carrying institutional knowledge that exists nowhere else. These are not signs of backwardness. According to MaintainX’s State of Industrial Maintenance 2025, 45 percent of maintenance leaders cite staffing and budget constraints as their primary obstacle to better maintenance, and nearly one third of manufacturers struggle to find people with the skills to interpret sensor data and act on what it tells them. In that context, fixed schedules and experienced operators are the rational behavior of organizations managing uncertainty with the tools actually available to them. An estimated 82 percent of companies still rely primarily on reactive maintenance rather than predictive approaches -- not because they prefer it, but because the alternative has not yet been made accessible enough to change behavior at scale.
The result is expensive. Siemens’ True Cost of Downtime 2024 report found that Fortune Global 500 companies lose approximately $1.4 trillion annually to unplanned downtime, equivalent to 11 percent of total revenues, up from 8 percent five years earlier. The average large plant loses 27 hours per month to unplanned incidents. Across manufacturing sectors, Aberdeen Research puts the average hourly cost of an unplanned stoppage at $260,000, reaching $2.3 million per hour in automotive. The buffers are expensive. The uncertainty they are compensating for is more expensive still.
The central question, then, is not what the instrument measures. The central question is which asset, signal, document, inventory position, or maintenance issue actually deserves attention right now. That decision happens dozens of times a day across a plant. It is small enough to look operational, but large enough to affect margin. A wrong call means unnecessary maintenance. A delayed call means downtime. A missed document creates compliance friction. A misread diagnostic sends technicians to the wrong place. A poorly understood installed base leads to excess inventory, obsolete devices, and slow repairs.
This is the problem that genuinely valuable industrial IoT could solve. Not the connectivity. The decision.
Why this company has a real advantage and a real problem
The company I am describing has one thing that most AI-native startups and digital platform vendors lack: it already belongs in the plant. Industrial customers do not hand operational trust to outsiders easily, and for good reasons. Process environments are conservative because safety, uptime, compliance, and liability make conservatism rational. Cybersecurity and integration complexity are consistently cited as the top barriers to industrial IoT adoption, alongside trust in the supplier behind the system. A clever model from a vendor nobody knows is not enough to move the needle in these environments.
An established measurement supplier enters with a completely different kind of credibility. It knows the physical layer. It knows the installed base. It has documentation, service history, calibration context, diagnostics, and relationships built over years of showing up when something breaks. That is a genuine wedge into the decision layer. And the company’s digital ecosystem, if it delivers on its ambition, connects device identity, health status, documentation, maintenance events, inventory signals, and diagnostics into one environment -- which starts to look less like a vendor portal and more like plant-level operational intelligence.
The ambition is real. The gap between that ambition and where most industrial IoT actually lands is also real, and I have watched it play out enough times to recognize the pattern.
Connecting data is not the same as understanding the business it belongs to. A dashboard that shows device health is useful. A system that helps a maintenance planner decide which device to inspect first, given limited technician time and a scheduled production run tomorrow, is something categorically different. The first is a technology output. The second requires understanding what the plant is actually trying to protect, what the cost of different failure modes looks like, and how maintenance decisions interact with production schedules, compliance deadlines, and procurement cycles. Research on predictive maintenance consistently makes the same point: the value is not in transforming sensor streams into a dashboard. It is in transforming sensor streams into actionable maintenance decisions that change what people do. That understanding does not come from the data. It comes from being genuinely embedded in the customer’s operational reality.
The business model problem that technology cannot solve
I have argued for a long time, in various forms and with various clients, that IoT is never really about technology. It is about whether the data enables something that was previously a barrier or a struggle worth paying to remove. The technology is only the means. The question that matters is: what does the customer struggle with today that this data could actually fix, and is the fix worth the investment?
That question sounds simple. It is not, because it requires the supplier to understand the customer’s business at a level most hardware companies never reach. They understand how the instrument works. They understand how to install it, calibrate it, maintain it. They may even understand the process it measures. But do they understand what it costs the customer when a device behaves unexpectedly? Do they know how maintenance planning actually happens inside that plant, who makes the decisions, what information they have access to, and what would genuinely change their behavior? Do they understand the compliance burden well enough to make documentation faster rather than just more connected?
These are not engineering questions. They are business model questions. And the company that can answer them -- credibly, specifically, for the customers it already serves -- will build something that changes behavior. The company that cannot will build a dashboard that sits beside the real workflow rather than inside it. The distinction matters more than it looks from the outside. Data outside the workflow is information. Data inside the workflow changes what people do. The gap between those two states is not a technical integration problem. It is a question of whether the supplier understands the customer’s job well enough to redesign the work around better information.
What the honest test looks like
There are two easy mistakes when looking at a company like this from the outside.
The first is to assume the platform transition is a natural extension of the hardware business. It is not. An installed base is a data acquisition opportunity, but turning that opportunity into recurring decision support requires capabilities that hardware companies rarely develop organically: service design, workflow integration, customer success, and a genuine willingness to be measured on business outcomes rather than technology features.
The second mistake is to assume that because the technology works, the business model follows. It does not. Predictive maintenance is not created by labeling diagnostics as AI. When properly integrated into operational workflows, predictive approaches have reduced monthly downtime incidents by roughly 40 percent compared to five years ago according to Siemens’ own longitudinal data. But the operative phrase is “properly integrated into workflows.” Most deployments stop short of that. They create visibility without changing accountability. They produce analytics that sit beside the real maintenance process rather than inside it.
Vendor neutrality is probably the hardest strategic test. A process plant is a multi-vendor environment. A system that only serves one supplier’s installed base is a vendor tool -- useful but limited. A system that works across the messy multi-brand reality of an actual plant floor becomes something the plant owns rather than something the supplier provides. That transition requires the company to invest in becoming genuinely useful to the plant, even when that usefulness does not directly sell more of its own hardware. That is a harder internal commitment than it sounds.
What I think is actually at stake
The strongest version of this company is not an instrument supplier with a digital layer attached. It is a decision-infrastructure company for process industries - one that uses its installed base and operational credibility to become the trusted home for the asset intelligence that drives maintenance, compliance, procurement, and reliability planning across the plant.
That is a genuinely different business. It has recurring revenue characteristics, customer dependency, and defensibility that hardware sales alone do not. It is also a much harder business to build, because it requires the company to develop a depth of customer understanding that goes far beyond knowing how the instrument works.
The companies that get this right will be the ones that stop asking what their technology can do and start asking what their customers cannot solve without it. That requires sitting in the plant, in the maintenance meeting, in the compliance review, in the procurement discussion, and understanding the decisions those people make every day with incomplete information.
The data is not the product. The better decision is the product. The companies that understand that distinction early enough to build around it will be the ones worth watching.
Everyone else will have connected a lot of instruments to a dashboard that nobody changes their behavior because of.
