Author: admin

For the better part of two decades, the story of industrial disruption had a familiar shape. Nimble entrants ran circles around the incumbents, unburdened by legacy portfolios, tangled supply chains, or installed bases measured in decades. The advantage belonged to whoever carried the least.

AI is inverting the story. The same weight that slowed large manufacturers—the sprawling product histories, the regulatory scar tissue, the decades of hard-won engineering intellectual property (IP)—is precisely the raw material that makes AI valuable.

In discrete manufacturing, the winners of the AI decade will not be the startups with the cleanest slate. They will be the Goliaths who finally turn their bulk into leverage.

The Asset No One Can Buy

Here is the uncomfortable truth for every well-funded newcomer: The one thing they cannot acquire is history. A general AI model can learn everything on the public internet and still know nothing about how your product is designed, built, changed, and certified. That knowledge lives in the engineering systems established manufacturers have run for years—the requirements, designs, bills of materials, and change history that constitute the essential IP of a business, along with the rules governing who may see it and how it gets approved.

That is exactly the context AI needs to reason well: what it is working with, who is allowed to use it, and how similar problems were solved before. Strip that away and even a capable model is reduced to guessing.

Owning It Isn’t the Same Thing as Wielding It

There is no partial credit here: Either a manufacturer’s product data is connected, governed, and curated or it isn’t. And for most, it isn’t. When a manufacturer’s product data sits fragmented across systems that don’t talk, modeled inconsistently across functions, locked in PDFs and the memories of engineers who may be five years from retirement, that is not a company with a slightly weaker AI position. It is a company with no AI position at all, pointing retrieval-augmented generation at a pile of disconnected documents and calling the output intelligence.

Take a routine scenario: A supplier discontinues a component and a replacement has to be qualified.

In one company, an engineer spends weeks tracing where that part lives: which assemblies, which configurations, which customer variants, which open orders, and which regulatory filings reference it. In another, an AI agent reaching the live product record through an open standard like the Model Context Protocol returns the full ripple in minutes, flags the two variants where the substitution breaks a compliance requirement, and surfaces a part already qualified for the same purpose.

Same change, same models, same ambition. But one company absorbs the cost quietly; the other never pays it.

And that is one scenario among dozens that play out every week, such as:

• A field failure comes in from a customer. One company reasons across service records, the as-built configuration, and the change history to find the root cause in an afternoon; the other convenes a task force and waits.
• A new program goes out to bid. One company knows in hours which existing designs, parts, and lessons it can reuse; the other quotes as if starting from scratch and either overbids or wins work it will lose money on.
• An auditor asks for the complete design and approval trail on a shipped product. One company produces it on demand; the other sends people digging through inboxes and shared drives for a week.
• A design engineer starts a new part. One company’s AI surfaces the three interchangeable parts already in the catalog; the other creates a fourth and pays to carry it for its entire lifecycle.

None of these is a dramatic, board-level crisis. Each is a small, ordinary moment of product work. And that is the point. Here, the math tips toward the giant: the larger the portfolio, the deeper the installed base; the longer the history, the more of these moments occur every day and the more a connected foundation compounds across them. The same scale that was a liability for 20 years becomes the multiplier. On disconnected data, that scale only multiplies the drag. Those returns don’t come on a sliding scale. They belong entirely to the manufacturers whose data is ready to be reasoned over, and not at all to the ones whose data isn’t—a divide decided long before the first model is deployed.

A Strategic Decision, Not a Software Purchase

Closing the gap is less about buying new software than about making a decision: to own and govern product data as an enterprise asset, not a by-product of engineering. Three things unlock it:

1. A product data foundation, anchored in the bill of materials, so AI reasons over an authoritative connected model rather than fragments that disagree.
2. Governed AI, where the same access rules that protect the IP constrain the model to limit what each user may see, keeping the model secure and auditable rather than a novel way to leak secrets.
3. AI in the workflow, running within the procedures teams already use, from engineering change to configuration to manufacturing planning, rather than hovering above them as a chatbot.

The executives who win this decade won’t be those who ran the most AI experiments. They’ll be those who asked the harder question early: Are we turning decades of engineering IP into a structural advantage or letting it depreciate in systems that don’t connect, align, or scale?

For 20 years, size was a liability. AI is making size the ultimate advantage—but only for the manufacturers who build the foundation to wield it.

The advantage is already theirs. The only question is whether Goliath picks up the stone—before David convinces him he’s too big to fight.

Turn AI insight into measurable business impact. Discover how AI embedded in product lifecycle management helps manufacturers cut complexity, lower costs, and accelerate decisions—without compromising governance.