Category: Technology

NeuralWired’s Technology section covers the developments reshaping how the world builds, deploys, and regulates digital innovation. We report daily on the stories driving global conversation in artificial intelligence, big technology companies, startups and venture funding, cybersecurity, consumer gadgets and devices, and blockchain and cryptocurrency.

Our technology coverage goes beyond product announcements. When a major AI model launches, we explain what it can actually do and where its claims are overstated. When a startup raises a large funding round, we look at whether the business behind it can sustain that valuation. When a cybersecurity breach hits the news, we explain who is affected and what comes next, not just what happened. Each article is built from original research into primary sources, including company statements, technical documentation, regulatory filings, and verified data, and is written by our editorial team rather than generated automatically.

Readers come to this section for daily updates on the technology stories that matter globally, from shifts inside major technology companies to emerging tools changing how people work, communicate, and build. Whether you are a founder, an investor, an engineer, or simply someone trying to understand where technology is heading next, NeuralWired’s Technology coverage is built to keep you informed without wasting your time on hype.

  • JPMorgan’s Quantum Computing Leap: 98-Qubit Data

    JPMorgan’s Quantum Computing Leap: 98-Qubit Data

    Pfizer and JPMorgan Prove Quantum Computing Works in 2026
    Enterprise Technology

    Pfizer and JPMorgan Prove Quantum Computing Works in 2026

  • Google’s DORA Metrics Are Failing Engineering Teams

    Google’s DORA Metrics Are Failing Engineering Teams

    Engineering Metrics

    Your Team Ships 40 Times a Day. Goals Still Miss.

    Deployment frequency is up. Lead time is down. Every dashboard is green. And your VP of Engineering still can’t explain why the roadmap slipped a quarter behind. If that sounds familiar, you’re not measuring the wrong things badly. You’re measuring the wrong things well.

    DORA metrics, the deployment frequency, lead time, change failure rate, and recovery time framework born out of Google Cloud’s DevOps Research and Assessment program, have become the default scoreboard for engineering performance. In 2024, only 19% of teams surveyed hit “elite” status on that scoreboard. Yet DORA’s own research team has publicly warned against using these numbers to judge team performance at all. So what are engineering leaders supposed to trust instead?

    What DORA Metrics Actually Measure

    DORA started as a research program, not a dashboard. Dr. Nicole Forsgren, Jez Humble, and Gene Kim built it, and their 2018 book Accelerate introduced what became known as the Four Keys: deployment frequency, lead time for changes, change failure rate, and time to restore service. Google Cloud has run the program since acquiring the founding team’s research in 2018.

    In 2024, DORA added a fifth metric: rework rate, which tracks how many deployments are actually emergency fixes for problems the last deployment caused. That addition alone tells you something. The original four measure how fast you move. Rework rate exists because moving fast and moving in circles started to look identical on the old dashboard.

    Quick definition: An “elite” DORA performer deploys on demand, has a lead time under one day, keeps change failure rate near 5%, and restores service in under an hour. In 2024, roughly one in five surveyed teams qualified. Source: DORA 2024 State of DevOps Report

    The “Elite Performer” Number Nobody Questions

    Here’s the stat that gets stapled to every engineering leadership deck: elite performers deploy 182 times more frequently than low performers, and they restore service 2,293 times faster. Those numbers are real, pulled from a survey of more than 39,000 professionals for the 2024 State of DevOps Report. They’re also the least useful numbers in the report if you’re trying to explain a missed quarter.

    Look at what happened to the middle of the distribution instead. Between 2023 and 2024, the share of low-performing teams grew from 17% to 25%. The share of high performers shrank from 31% to 22%. The industry didn’t get better at DevOps last year. It got worse, on average, while adopting more DevOps tooling than ever.

    Metric20232024
    Low-performing teams17%25%
    High-performing teams31%22%
    Elite-performing teamsnot tracked19%
    That’s the gap the headline is pointing at. A team can hit every DORA benchmark and still be part of a shrinking pool of teams whose actual delivery outcomes are stagnant or backsliding.

    Why Speed and Goals Keep Diverging

    DORA’s own research team saw this coming. In October 2023, according to reporting cited on DORA’s Wikipedia entry, the team explicitly warned against using the Four Keys to evaluate individual teams’ performance. That’s an unusual thing for a research program to say about its own flagship metrics. It’s also exactly what you’d expect once a research tool turns into a KPI baked into Jira, GitLab, and every engineering-analytics dashboard on the market.

    This is Goodhart’s Law showing up in production code. Once deployment frequency becomes the target, it stops measuring what it used to measure. Teams under pressure to hit a number will split pull requests into smaller, more frequent deploys without changing what actually ships. They’ll quietly under-report incidents to protect their change failure rate. None of that improves the product. All of it improves the chart.

    Teams pressured to raise their deployment rate by a fixed percentage can hit that target simply by shipping smaller changes more often, without touching the bugs or incidents that actually determine whether users are happy. Laura Tacho, CTO, DX · getdx.com/podcast
    DORA even flags this tension inside its own 2024 data. Teams that adopted internal developer platforms saw individual productivity and overall organizational performance improve, but the report also found decreased change stability and throughput as a side effect. Speed up one lever, and another one moves without anyone touching it.

    What AI Adoption Did to the Data

    If DORA metrics were shaky before, AI made the cracks visible. The 2024 report found that a 25% increase in AI adoption correlated with a 1.5% decrease in throughput and a 7.2% decrease in stability, DORA’s own team flagged this as correlational rather than causal, but the direction is notable.

    By the time the 2025 State of AI-assisted Software Development Report came out, AI use had reached 90% of surveyed professionals, with more than 80% reporting productivity gains. But 30% still said they had little or no trust in the code AI generated for them. The report’s core finding, drawn from nearly 5,000 professionals and over 100 hours of qualitative interviews, was blunt: AI doesn’t fix a broken team. It amplifies whatever was already there. Strong teams get stronger. Struggling teams get their existing dysfunction on fast-forward.

    That’s the mechanism behind the headline. A team with process debt that starts using AI coding tools doesn’t quietly improve. It ships more, faster, with the same underlying gaps, and those gaps show up downstream as missed goals rather than upstream as slow commits.

    The Case Against DORA Entirely

    Not everyone thinks DORA metrics deserve the reverence they get. Dr. Junade Ali, a software engineering manager who ran independent polling with Survation and J.L. Partners, published a pointed critique on HackerNoon in January 2024 arguing the entire premise is backwards.

    His research found that both software engineers and the general public rank data security, data accuracy, and bug prevention well above deployment speed when asked what matters in software delivery. That directly contradicts what the Four Keys are built to optimize for. Ali also points out that DORA’s team doesn’t publish raw survey data, unlike polling organizations bound by disclosure rules such as the British Polling Council, which require full data tables within two working days of publication.

    It’s hard to find a hypothesis connecting the Four Key Metrics to the outcomes that developers and the public actually say they care about most. Dr. Junade Ali, Software Engineering Manager · HackerNoon, January 2024
    His research also found something worth sitting with: 98% of UK business decision-makers and 96% of their US counterparts agreed that the actual goal of an engineering team is delivering high-quality software on time, not shipping the highest possible number of deploys. Nobody polled thinks speed is the goal. Yet speed is what gets measured, reported, and rewarded.

    What Replaces DORA in 2026

    The clearest answer to “what should we measure instead” so far is DX Core 4, a framework announced in December 2024 by DX co-founder and CEO Abi Noda and DX CTO Laura Tacho, built with input from DORA co-creator Dr. Nicole Forsgren and Dr. Margaret-Anne Storey. It’s worth being upfront here: DX sells the platform that implements this framework, so its published outcomes come from the vendor itself, not an independent auditor.

    With that disclosed, the numbers are still notable. Tested across more than 300 organizations, DX Core 4 has been associated with 3 to 12% increases in engineering efficiency and a 14% increase in R&D time spent on new feature development. The framework’s structure is the real change: it pairs DORA’s speed metrics with effectiveness, quality, and business impact measures, so a team can’t improve one number by quietly breaking another.

    The big question is, what should we actually be measuring? DORA’s throughput numbers alone were never built to capture developer experience or business impact. Abi Noda, Co-founder & CEO, DX · LeadDev, December 2024

    The market is already voting with its budget

    Platform engineering investment backs this shift up. Gartner projections cited in industry compilations put platform engineering team adoption at 80% of large software organizations by 2026, up from 45% in 2022 (worth verifying directly against a current Gartner release before you cite the figure yourself). The broader DevOps software market itself is priced anywhere from roughly $15 billion to nearly $19 billion for 2026 depending on which research firm you ask, a wide enough range that any single number should be treated as directional, not precise.

    Our read: this signals engineering leadership is done treating DORA as a finished answer. The direction for 2026 is DORA plus a counterbalancing quality or business-impact metric, not DORA replaced outright.

    Frequently Asked Questions

    What are the DORA metrics?

    DORA metrics are five software delivery measurements, deployment frequency, lead time for changes, change failure rate, failed deployment recovery time, and rework rate (added in 2024), developed by Google Cloud’s DORA research program to evaluate delivery speed and stability.

    What is an elite DORA performer?

    In DORA’s 2024 report, elite performers deploy on demand, have lead times under a day, keep change failure rates near 5%, and recover from failures in under an hour. Only about 19% of surveyed teams qualified as elite that year.

    Are DORA metrics enough to measure engineering success?

    No. DORA’s own team warned in October 2023 against using the Four Keys to evaluate individual teams. Newer frameworks like DX Core 4 pair DORA with developer experience and business impact metrics to avoid a narrow, gameable view of performance.

    What is Goodhart’s Law and how does it apply to DORA metrics?

    Goodhart’s Law holds that once a measure becomes a target, it stops being a good measure. Applied to DORA, teams pressured to hit deployment-frequency targets can split pull requests artificially or under-report incidents to protect their numbers, without improving actual delivery outcomes.

    What is DX Core 4?

    DX Core 4 is a 2024 framework combining DORA, SPACE, and DevEx research into four dimensions: speed, effectiveness, quality, and business impact. It was built by DX’s Abi Noda and Laura Tacho with input from DORA co-creator Dr. Nicole Forsgren.


    Where This Goes Next

    Here’s what the data actually tells you, once you stop reading the headline numbers in isolation: DORA metrics were never designed to be a scoreboard for individual teams, and the program’s own researchers said so in writing back in 2023. What they measure well is delivery speed and stability at an aggregate level. What they can’t tell you is whether that speed is producing anything your business actually wanted.

    Over the next 6 to 18 months, expect three things to play out. First, more engineering orgs will pair DORA with a second framework, DX Core 4 or something built in-house, rather than reporting DORA numbers alone in board decks. Second, AI’s split effect (individual productivity up, organizational stability shaky) will keep showing up in DORA’s own annual reports until teams fix underlying process debt instead of layering AI on top of it. Third, watch for tooling vendors to start marketing “beyond DORA” dashboards as a category, the same way “shift-left security” became a category once perimeter security stopped being enough on its own.

    Three things worth watching yourself over the next few quarters: whether your org’s change failure rate moves in the same direction as your deployment frequency, whether anyone above you is asking about rework rate at all, and whether a platform engineering investment is quietly trading stability for speed without anyone naming the tradeoff out loud.

    Want the next report before your competitors do? Subscribe to The Neural Loop at neuralwired.com/newsletter.

  • Apple Vision Pro 2026: Dead to Apple, Alive in ORs

    Apple Vision Pro 2026: Dead to Apple, Alive in ORs

    Apple Gave Up on Vision Pro. Hospitals Didn’t.
    Spatial Computing / Enterprise Tech

    Apple Gave Up on Vision Pro. Hospitals Didn’t Get the Memo.

  • Gartner’s Edge Computing Data: The Real 2026 Numbers

    Gartner’s Edge Computing Data: The Real 2026 Numbers

    Enterprise Architecture

    IoT Data Overload: Why Most of It Never Gets Analyzed

    Published July 8, 2026 · NeuralWired.com

    GE Digital’s monitoring center processes more than 200 billion data tags a day from a million sensors across 5,000 power plant assets in 60-plus countries. Most companies running IoT fleets never get close to that ratio of data collected to data used. The gap between what your sensors capture and what your systems actually act on is now the defining bottleneck in enterprise IoT, and closing it has become the real argument for edge computing.

    If you’re building or budgeting for an IoT data architecture in 2026, this is the article for you: enterprise architects, CTOs, and platform engineering leads who need to know what’s real in the edge computing narrative, and what’s still marketing.

    The real numbers behind the “unused data” claim

    IDC’s Global DataSphere research puts total IoT-generated data at roughly 79.4 zettabytes annually, a figure the firm hasn’t publicly refreshed for 2026 as of this writing. That’s about 79.4 trillion gigabytes, produced by a device population IoT Analytics counted at 21.1 billion active connections at the end of 2025, up 14% year over year.

    You’ve probably seen a version of the claim that “99% of IoT data is never analyzed.” Here’s the problem: no primary 2026 source actually supports that exact number.

    Fact-check note: The “only a sliver of your data gets used” claim traces back to IDC’s 2014 Digital Universe study, sponsored by EMC, which found less than 5% of the 2013 global data supply was analyzed, and just 1.5% was what IDC called “target rich,” meaning easily accessible, real-time, and high-impact. That’s the real ancestor of today’s “1%” headline framing. It’s directionally accurate but not a fresh 2026 statistic, and any article that presents it as one is passing along a decade-old number with a new coat of paint.
    The underlying point still holds. As sensor costs have fallen from over $200 per unit five years ago to under $50 today, the volume of raw data generated has scaled far faster than most organizations’ capacity to analyze it. The bottleneck isn’t collection anymore. It’s filtering.

    As AI’s focus shifts from training to inference, edge computing becomes necessary to address latency and privacy needs, opening business models that centralized infrastructure couldn’t support. Paraphrased from Dave McCarthy, Research Vice President, Cloud and Edge Services, IDC · R&D World, December 2025

    Why edge computing, not more cloud storage

    Gartner has projected that 75% of enterprise-generated data would be processed outside a traditional centralized data center or cloud, up from under 10% in 2019. That figure has been circulating for several years now without a fresh confirmation, so treat it as directional rather than a current 2026 data point. But the architectural logic behind it hasn’t gone away: if you’re waiting for a round trip to a centralized cloud region before a factory floor sensor can trigger a shutoff valve, you’ve already lost.

    AI increasingly lives closer to where data and users actually are, at the edge, on-device, in the real world, rather than centralized in the cloud. Paraphrased from John Roese, Chief Technology Officer, Dell Technologies · R&D World, December 2025. Dell sells edge hardware, worth noting as context for this view.
    Here’s where it gets messy for anyone trying to size a budget: research firms can’t agree on how big the edge computing market actually is.

    Source2025/2026 estimateScope
    Global Market Insights~$21.4 billionNarrow, infrastructure-only
    MarketsandMarkets~$658.1 billionBroad, includes adjacent AI/hardware spend
    IDC (spending, not market size)~$261 billion (2025), $380B by 2028Enterprise edge spending, 13.8% CAGR
    That’s a roughly 30x spread between the low and high estimates, entirely a function of what each firm counts as “edge computing.” If a vendor hands you a single market-size number without a methodology footnote, ask for one before it goes anywhere near a board deck.

    The pilot purgatory problem

    Here’s the number that should worry you more than any data-volume statistic: a widely cited McKinsey finding puts 84% of industrial IoT initiatives stuck in pilot mode, with more than a quarter stalled for over two years. Cisco’s older count put pilot survival at just 26%. Adoption isn’t the hard part. Scaling is.

    Most IIoT programs collapse under vague mandates rather than specific, measurable KPIs tied to a real downtime-cost baseline. Paraphrased from Stephan Liozu, Chief Value Officer, Zilliant; adjunct professor, Case Western Reserve University · IndustryWeek
    Liozu has relayed a manufacturing CEO’s description of pilot-stage IIoT projects as stuck somewhere worse than purgatory. And the trend line isn’t improving on its own: MaintainX’s 2025 State of Industrial Maintenance survey found predictive maintenance adoption among maintenance teams actually fell, from 30% in 2024 to 27% in 2025. That’s the opposite of the smooth upward curve most vendor decks imply.

    What actually works: GE and Shell’s real numbers

    Skip the vendor slide decks. Here are two cases with attributable, on-record numbers.

    GE Digital’s Global Electricity Monitoring and Diagnostics Center processes over 200 billion data tags daily from a million sensors across 5,000 power plant assets. Our deeper look at GE and Shell’s real IIoT ROI numbers found GE’s actual documented downtime reduction sits at 5%, notably smaller than the rounder 20% figure that circulates in secondhand retellings. That gap matters: it’s a useful reminder that even legitimate case studies get inflated as they pass through marketing copy.

    Shell’s 2019 oilfield vibration and pressure-sensor deployment cost $87,000 and returned over $1 million in avoided downtime and deferred maintenance, according to IoT World Today’s reporting. It remains one of the few IIoT ROI cases with sourcing that holds up to scrutiny, which says something about how rare well-documented ROI actually is in this space.

    For a sense of what this looks like outside heavy industry, our recent piece on Amazon’s smart building ROI numbers is worth a look. Same underlying discipline, different vertical.

    What ties these together: Both Shell and GE’s real numbers came from narrow, specific use cases with a measurable baseline, not a company-wide “digital transformation” mandate. That’s the pattern that separates the 84% stuck in pilot mode from the ones that scale.

    The accuracy gap nobody talks about

    Consumer AI applications tolerate roughly 95% accuracy. Nobody’s harmed if a recommendation engine gets it wrong occasionally. Industrial systems don’t get that margin.

    Consumer AI applications tolerate roughly 95% accuracy, while industrial models require near-zero error margins, 99.5% or higher, a far higher bar than most AI and edge hype accounts for. Paraphrased from Jeff Winter, VP of Business Strategy, Critical Manufacturing · remarks at IIoT World Days 2025
    That gap is why edge AI’s clearest wins so far cluster in more forgiving domains: retail checkout, consumer cameras, building automation. The highest-stakes industrial control loops, the ones the “operational intelligence” narrative loves to reference, are still catching up. If your architecture roadmap assumes consumer-grade edge AI accuracy translates directly to a chemical plant or a power turbine, that assumption needs a second look before it reaches production.

    Related to this: NVIDIA GR00T and the broader physical AI robotics push are running into the same accuracy ceiling in real-world deployments.

    What this means for your 2026 roadmap

    Unplanned downtime already costs U.S. industrial manufacturers around $50 billion a year, with large plants losing an average of $253 million annually. That’s the cost of inaction, and it’s the number that should anchor any edge computing business case instead of a disputed market-size figure.

    Three things worth watching over the next 6 to 18 months:

    • The EU Cyber Resilience Act. Incident-reporting obligations begin September 11, 2026, with full obligations from December 11, 2027. Edge deployments decentralize where sensitive operational data lives, which directly expands compliance scope for manufacturers and IoT vendors.
    • Inference, not training, drives edge budget. The strongest current argument for edge investment isn’t raw IoT data volume anymore. It’s the shift from centralized model training to real-time inference at the point of use.
    • Narrow pilots with a real KPI, not company-wide mandates. Every documented ROI case in this piece started with a specific, measurable problem and a cost baseline, not a broad “digital transformation” initiative.
    Our take: the data-volume framing that dominates IoT marketing (zettabytes, “you’re only using 1% of your data”) makes for a good headline but a weak business case. The number that actually gets budget approved is the cost of the downtime you’re not preventing.


    FAQ

    What is IoT edge processing?

    IoT edge processing means analyzing or acting on sensor data close to where it’s generated, on the device or a nearby gateway, instead of sending everything to a centralized cloud data center. It reduces latency, cuts bandwidth costs, and enables real-time decisions even with limited connectivity.

    How much data do IoT devices generate?

    IDC estimates connected IoT devices generate roughly 79.4 zettabytes of data annually in its most recent published forecast, equivalent to about 79.4 trillion gigabytes. IDC hasn’t publicly updated this figure for 2026 as of this writing.

    Why do most IoT projects fail to scale?

    A widely cited McKinsey finding shows 84% of industrial IoT initiatives get stuck in pilot mode, often because they launch with vague goals like “improve efficiency” instead of a specific, measurable KPI tied to a real cost baseline.

    What percentage of enterprise data is processed at the edge?

    Gartner projected 75% of enterprise-generated data would be processed outside a centralized data center or cloud, up from under 10% in 2019. The figure is several years old now and should be treated as directional rather than a current data point.

    How big is the edge computing market?

    Estimates vary enormously: 2025 to 2026 figures range from roughly $21 billion (Global Market Insights) to over $650 billion (MarketsandMarkets), depending entirely on what’s counted as “edge computing.” Treat any single figure with caution unless the methodology is disclosed.


    Want more analysis like this?
    Subscribe to The Neural Loop for weekly enterprise AI and infrastructure coverage.

  • Deloitte AI Hallucination Report: FINRA’s 2026 Warning

    Deloitte AI Hallucination Report: FINRA’s 2026 Warning

    Deloitte’s AI Hallucination Cost $290K. FINRA Is Watching Enterprise AI / Compliance

    Deloitte’s AI Hallucination Cost $290K. FINRA Is Watching

  • GE and Shell’s Real Industrial IoT ROI Numbers 2026

    GE and Shell’s Real Industrial IoT ROI Numbers 2026

    Manufacturing & Industrial AI

    The Real IIoT ROI Numbers Plant Managers Need

    Shell turned an $87,000 sensor bet into more than $1 million in returns. Most industrial IoT projects never get that far. Here’s the actual math behind the ones that do.

    In 2019, Shell wired up an aging oilfield with $87,000 worth of vibration and pressure sensors. The payout: over $1 million in avoided downtime and deferred maintenance, a return that would make any CFO sit up. That story gets quoted constantly in industrial IoT (IIoT) marketing decks. What doesn’t get quoted nearly as often: 84% of IoT projects never make it past the pilot stage, and more than a quarter of those stay stuck there for over two years.

    If you’re a plant manager weighing a predictive maintenance rollout, both of those facts matter. This piece walks through what unplanned downtime actually costs, why so many IIoT projects stall before they scale, and how to build an ROI case that survives contact with a skeptical board.

    What Unplanned Downtime Actually Costs You

    Start with the number that justifies everything else: unplanned downtime costs U.S. industrial manufacturers roughly $50 billion a year. The average large plant loses about $253 million annually to breakdowns. For Fortune 500 manufacturers, that works out to $2.8 billion a year, close to 11% of revenue, vanishing into machines that stopped when they weren’t supposed to.

    It’s not a rare event, either. 82% of manufacturers reported unplanned downtime in the past three years, and the average factory loses roughly 800 hours a year to breakdowns that, in theory, sensors could have flagged in advance.

    Here’s where the hardware math has flipped in the plant manager’s favor. Basic industrial IoT sensors now run under $50 a unit, down from over $200 five years ago. A North American plant runs an average of 365 IIoT devices today. Cost is no longer the bottleneck it was in 2019. That changes the calculus: a small, targeted pilot on two or three critical machines is now cheap enough to fund out of an existing maintenance budget, which means you don’t need to wait for a capex approval cycle to test the idea.

    Why Most IIoT Projects Never Scale

    So if the hardware is cheap and the downtime math is brutal, why isn’t every plant running on sensors already?

    Because most projects stall. A McKinsey study, still widely cited years later, found 84% of industrial IoT initiatives get stuck in what the industry now calls “pilot purgatory,” and 28% of those stay there for more than two years. More recent tallies put the failure-to-scale rate above 60%, and Cisco’s older but still-referenced figure puts pilot survival at just 26%.

    “It is not purgatory, it is hell!” Manufacturing CEO, quoted by Stephan Liozu, Chief Value Officer at Zilliant and adjunct professor at Case Western Reserve University’s Weatherhead School of Management, via IndustryWeek
    Liozu isn’t a fringe voice here. His point, backed by McKinsey’s own data, is that most IIoT programs collapse under the weight of vague mandates like “improve efficiency” instead of a specific, measurable KPI tied to a named line and a real downtime-cost baseline.

    Adoption data backs up the stall-out pattern. According to MaintainX’s 2025 State of Industrial Maintenance survey, predictive maintenance adoption among maintenance teams actually dropped, from 30% in 2024 to 27% in 2025. That’s not the smooth upward curve you’d expect from the marketing. Only 46% of manufacturers have deployed IIoT at the facility level at all, and per McKinsey’s more recent numbers, just 25 to 30% of large manufacturers have scaled beyond a pilot to an enterprise-wide rollout.

    Watch this number: Global IIoT market-size estimates for 2026 range from roughly $190 billion (Mordor Intelligence) to over $500 billion (Precedence Research), depending entirely on how each firm defines the market’s scope. When a vendor pitches you urgency based on “the $500 billion IIoT market,” ask which definition they’re using. The spread alone should make you skeptical of any single headline figure used to justify a purchase decision.

    Jeff Winter, VP of Business Strategy at Critical Manufacturing, put the technical side of the problem bluntly at IIoT World Days 2025: consumer AI succeeds at around 95% accuracy, but industrial models need a near-zero margin for error, 99.5% or higher. That’s a much higher bar than most of the AI hype cycle accounts for, and it’s a big part of why pilots that look great in a demo fall apart on a real production line.

    What Actually Works: Two Real Cases

    Strip away the invented statistics you’ll find floating around IIoT marketing content (there’s no verified source for some of the dollar figures companies get credited with online, so treat any suspiciously precise claim with caution) and two real, attributable cases hold up.

    Shell: $87,000 In, $1 Million Out

    Shell’s oilfield asset-monitoring project is the cleanest real-world proof point available. An $87,000 sensor investment on aging equipment generated over $1 million in returns through avoided downtime and deferred maintenance, according to IoT World Today’s reporting. It’s not a hypothetical ROI model. It’s a documented result from a company that had every incentive to keep quiet if the numbers hadn’t worked out.

    GE: The Real Numbers Behind the Headline

    GE Digital’s Global Electricity Monitoring and Diagnostics Center processes over 200 billion data tags daily from a million sensors across 5,000 assets in power plants in more than 60 countries. Bill Ruh, then-CEO of GE Digital, put the actual, on-record result this way when the platform launched:

    “These analytics provide GE Digital with the unique ability to reduce unplanned downtime by up to 5 percent, reduce false alarms by up to 75 percent, and reduce operations and maintenance costs by up to 25 percent.” Bill Ruh, then-CEO, GE Digital, GE News press release, October 2017
    Notice that’s 5%, not the round 20% figure that circulates in some secondhand summaries. It’s a smaller number, but it’s GE’s own, and it comes with a false-alarm reduction and O&M cost figure attached that most retellings leave out entirely.

    Predictive Maintenance: The Realistic Range

    Zooming out from single-company cases, here’s where independent research firms land on predictive maintenance’s actual impact:

    MetricRangeSource
    Maintenance cost reductionUp to 25%Deloitte
    Uptime increase10% to 20%Deloitte
    Downtime reduction (upper bound)Up to 50%McKinsey & Co.
    Asset lifespan extension (upper bound)Up to 40%McKinsey & Co.
    Treat the upper-bound figures as ceiling cases, not defaults. A well-scoped, single-line pilot is far more likely to land near the lower end of these ranges in its first year.

    Building an ROI Case That Survives the Board

    Here’s the actual formula, stripped of vendor gloss: ROI equals annual savings minus annual program cost, divided by annual program cost, times 100. Annual savings breaks down into avoided downtime cost plus avoided emergency maintenance spend, measured against a pre-deployment baseline you establish before you install a single sensor.

    A few things the data says you need to get right:

    • Use your own downtime-cost-per-hour, not an industry average. The $50 billion industry figure is a scale-setter, not an input for your specific calculator.
    • Stress-test your assumptions by plus or minus 30% before presenting to a board. This is standard practice recommended in IoT World’s own project-scoping framework, and it heads off the “your numbers were too optimistic” objection before it happens.
    • Budget for realistic retrofit costs. End-to-end IIoT retrofits run anywhere from $1 million to over $10 million depending on facility size and complexity, per Emergen Research. A sub-$50,000 sensor pilot is a very different financial commitment than a plant-wide rollout, and conflating the two in a pitch deck is a fast way to lose credibility.
    • Set a payback-period expectation that matches your scope. Well-scoped single-line predictive maintenance pilots often show payback in 6 to 18 months. Enterprise-wide rollouts typically take two years or more, and that’s exactly the scope where the pilot-purgatory failure rate climbs.
    Our read: the smartest move for most plant managers right now isn’t the big enterprise-wide business case. It’s the small, self-funded pilot on one or two lines, with a hard KPI and a real downtime-cost baseline attached, that proves the model before anyone has to ask a board for millions.


    Frequently Asked Questions

    How do you calculate ROI for an IIoT project?

    ROI equals annual savings minus annual program cost, divided by annual program cost, times 100. Savings combine avoided downtime cost and avoided emergency maintenance spend, measured against a pre-deployment baseline established before installation begins.

    How much does unplanned downtime cost manufacturers?

    Unplanned downtime costs U.S. industrial manufacturers roughly $50 billion annually. The average large plant loses about $253 million a year, and Fortune 500 manufacturers lose around $2.8 billion annually, close to 11% of revenue.

    What percentage of IoT projects fail to scale?

    Estimates vary, but a widely cited McKinsey finding shows 84% of industrial IoT projects remain stuck in pilot mode, with more than a quarter stalled for over two years, a pattern the industry calls “pilot purgatory.”

    How much can predictive maintenance reduce downtime?

    Deloitte and McKinsey benchmarks put predictive-maintenance-driven downtime reduction between 25% and 50%, with maintenance cost savings of 10% to 25%. Results vary heavily by industry, equipment type, and deployment maturity.

    What’s a realistic payback period for an industrial IoT project?

    Well-scoped, single-line predictive maintenance pilots often show payback within 6 to 18 months. Enterprise-wide rollouts typically take two years or longer, and a meaningful share stall out indefinitely before reaching that point.

    What to Watch Next

    Three things worth tracking over the next 6 to 18 months: whether predictive maintenance adoption recovers from its 2025 dip or keeps sliding, whether sub-$50 sensor pricing pulls more mid-size manufacturers past the 46% facility-level adoption mark, and whether the gap between market-size hype and the 25 to 30% enterprise-scaling rate starts to close.

    None of that changes the math you need today. Get your own downtime-cost baseline, run the small pilot, stress-test the assumptions, and let the numbers, not the vendor slide deck, make the case.

    Want the next breakdown like this one delivered straight to you? Subscribe to The Neural Loop for weekly analysis on industrial AI, robotics, and the infrastructure behind it.

  • Anthropic Copyright Case: 6 Countries Disagree (2026)

    Anthropic Copyright Case: 6 Countries Disagree (2026)

    AI Copyright Rulings Diverge Across 6 Countries in 2026
    GLOBAL AI POLICY

    Your AI Content Runs on Copyrighted Data. Six Countries Now Disagree on What That Means.