The OT Veto: When Your Plant Floor Has Final Say on Your Digital Strategy

There is an unspoken rule in manufacturing technology that overrides every software license, every boardroom mandate, and every digital transformation roadmap. It is the OT Veto. This isn’t a failure of leadership or vision. It is the logical, inevitable outcome of a system where one group is measured purely on the certainty of production, and another is funded to pursue the uncertainty of innovation.

The conversation about data infrastructure is often framed as a technical challenge. In reality, it is a governance challenge. Your control engineers and plant managers hold a de facto veto power over any initiative that introduces risk to their primary metric: uptime. Understanding this power dynamic and learning to work within it is the first step to making any data strategy real.

The Anatomy of a Rational Veto

To frame OT’s caution as resistance is to misunderstand the game. Their incentives are crystal clear and powerfully aligned with the company’s immediate revenue. As one panelist with deep operational experience noted during IIoT World Manufacturing & Supply Chain Day, “Production environments are cost centers, and they also are the beating heart of a company’s business engine.” For them, a running line is success. Any change is, by definition, a threat to that success.

This creates a fundamental asymmetry. The IT or data science team proposes a project with a future, theoretical return—reduced downtime, predictive insights. The OT team faces an immediate, concrete risk: a line stoppage, missed quotas, and quality issues. When the cost of a failed experiment is a tangible hit to the quarterly numbers, the rational choice is to say no. The veto is not stubbornness; it is risk management.

Why “Buy-In” is the Wrong Ask

The traditional approach is to seek “buy-in.” This implies convincing OT to accept a plan conceived elsewhere. It often fails because it doesn’t change the incentive structure. You’re asking them to endorse a risk without altering the consequences of failure.

The shift must be from seeking approval for a project to sharing ownership of the outcome. This means the data initiative must be designed from the start to make the OT team’s job safer or easier, not just to extract data from them. Does it provide them with a better tool to diagnose faults? Does it automate a tedious manual log? Does it give them a clearer, faster view of a chronic process issue? If the answer is no, the veto will remain, rightly, in place.

Designing Projects That Avoid the Veto

The path forward requires redesigning the proposal itself. It moves from a technology rollout to a joint operational improvement.

1. Lead with an OT Problem, Not a Data Solution. Start the conversation in the control room. Identify a specific, nagging pain point: a component that fails unpredictably, a manual quality check that slows the line, an energy spike no one can explain. Frame the data project as a joint investigation into that specific problem.
2. Create a Zero-Risk Testing Zone. Instead of proposing a plant-wide rollout, identify a single machine, line, or process where a trial can be conducted with minimal operational exposure. The goal is to create a safe space for learning where a failure is contained and does not trigger production penalties.
3. Embed the Value in Their Workflow. The output cannot be a dashboard only the data scientist uses. It must be a tool, alert, or report that integrates directly into the OT team’s daily rhythm. The value must be consumable on their terms, in their environment.

From Governance Obstacle to Strategic Partner

When approached this way, the OT team transforms from a gatekeeper to the most valuable partner in the initiative. Their deep, contextual knowledge of the physical process is the very ingredient that turns raw data into actionable insight. They become co-authors of the solution, not defenders against it.

The OT Veto is not a barrier to be broken. It is the most important quality check a manufacturing data strategy will face. It asks the essential question: “Does this truly understand and respect the reality of production?” A strategy that can pass this test isn’t just approved, it’s equipped with the knowledge and partnership to succeed. The goal is not to override the veto, but to design projects that never trigger it.

Sponsored by InfluxData. 

This article was developed based on the IIoT World Manufacturing Day session, “Building Data Infrastructure for Predictive Operations,” sponsored by InfluxData. Thank you to the moderator, Rick Franzosa, and the speakers Benjamin Corbett of InfluxData, Sam Elsner of Litmus, and Calvin Hamus of SkyIO for their insights.