Analyst(s): Keith Kirkpatrick
Publication Date: October 16, 2026

The news coming out of IFS Unleashed 2026 illustrates a vendor pairing governance claims with its first wave of quantified, if still small-scale, customer results, and a continued focus on frontline workers.

What Is Covered in This Article:

• A platform launch paired with a governance pitch. IFS launched IFS Intelligence alongside the Industrial AI Harness on the same day, positioning governance as the feature separating it from general-purpose AI tools rather than raw model capability.
• Adoption is already outrunning oversight. IFS’s own Industrial Index 2026 shows 43% of frontline workers have introduced agentic digital workers into daily operations, while only 4% of organizations require human sign-off on AI-supported decisions.
• A customer put a number on the Harness’s payoff. Eight Group’s CIO told the keynote audience its digital workers, governed by the Harness, delivered a 60% efficiency gain, a figure the written release did not include.
• The pricing logic is now public; the actual price is not. Moffat told analysts IFS Intelligence is priced as a percentage of a customer’s existing IFS contract, scaled by business size, plants, and assets, and that exceeding the usage entitlement triggers a conversation rather than a charge, but IFS has not published the percentage or the entitlement itself.
• Most of the differentiation claims are now category standard. Governance, guardrails, and data-sovereignty language closely track what Salesforce, SAP, and ServiceNow already say about their own agent platforms. The clearest structural advantage is IFS’s existing base of industrial operational data, an edge it shares with other ERP and EAM incumbents, not with horizontal AI platforms.

The Event—Major Themes & Vendor Moves: IFS used its Unleashed 2026 conference to pair a new conversational AI platform with a governance layer built to contain it, after its own research found 43% of frontline industrial workers already run agentic AI with almost no formal oversight in place. CEO Mark Moffat opened the conference by tying that urgency to supply constraints already hitting customers. He cited 2034 as the earliest delivery date for a gas turbine ordered today, the end of 2028 for a backup diesel generator, and a $2 billion increase in General Motors’ costs from memory-chip scarcity, alongside Boeing’s estimate that aviation will need 700,000 more engineers over the next 20 years as two-thirds of the current workforce retires. That scarcity, Moffat argued, is what makes the 40% of operating potential IFS says sits untapped inside existing systems and workers worth capturing now rather than later.

Those figures come from IFS’s own Industrial Index 2026, which surveyed 2,275 executives and frontline workers across 14 countries at companies with more than 500 employees and $250 million or more in annual revenue, fielded by Censuswide between August 17 and September 3. The numbers are self-reported and commissioned by the vendor now selling the product built to close the oversight gap they describe, worth keeping in mind given how directly the keynote’s urgency depends on them.

The event also highlighted a confirmed platform partnership with Siemens Digital Industries Software, whose software Moffat said is used by 92% of Fortune 500 industrial companies, and the continuing use of Nexus Black, an internal applied-AI unit that is built to deploy agentic tools directly with frontline workers.

IFS Ties Its Industrial AI Platform to a Governance Layer Built to Contain It

Analyst Take: IFS’s Unleashed 2026 news cycle is best read as two announcements stacked on top of each other: a new way for frontline and office workers to talk to IFS data, and a governance architecture built specifically because IFS’s own research shows that kind of AI use is already happening without it.

A Conversational Platform Built Around Governance

IFS Intelligence puts a single conversational interface over the data that a customer’s IFS and third-party systems already hold: assets, work orders, schedules, and history. A user asks a question in plain language, and the system reasons across live operational data to explain what is happening and recommend what to do next, showing its sources before any action runs.
IFS Intelligence has three modes defining how people use it.

• Cowork turns a question into an investigation and action. A person asks, reviews the recommendation, and approves before anything is executed. A saved answer becomes a Lens, a live view that keeps updating as the operation moves, and a workflow that succeeds once can be saved as a Skill for others to repeat.
• Loops hands recurring workflows to digital workers that run in the background and escalate only when a decision needs judgment or approval.
• Runway uses plain-language requirements to speed configuration and migration work on the underlying IFS platform.

Loops already draws on roughly 150 built-in skills spanning procurement, field service, and other industrial workflows, each encoding specific implementation experience, down to how a particular region’s rules require splitting a supplier invoice, according to Ravi Bulusu, CTO with IFS Loops. It is likely that IFS will monetize that skill library on its own terms, even if a different company’s model eventually wins the broader orchestration layer around it.

IFS licenses IFS Intelligence as an addition to a customer’s existing IFS contract, not a flat fee. Moffat told the press and analyst audience the price is set as a percentage of what a customer already pays IFS, scaled by business size, plant count, and asset count, replacing the per-user pricing model IFS retired in an April 2026 overhaul. Inside that scaled license, access itself is not gated or tiered by feature, and it comes with an entitlement of AI Executions IFS describes as a fair usage cap rather than a credit model. Speaking from the Unleashed main stage, IFS added detail the written release left out: a customer who exceeds the entitlement is not charged an overage or cut off, and IFS says it will instead have a conversation with the customer about adjusting the plan. IFS has still not published the percentage, the entitlement’s size, or a worked example, leaving the actual bill impossible for a prospective buyer to estimate, even though the pricing logic is now public.

Governing all three modes is the Industrial AI Harness, introduced the same day as the architecture, meant to keep agentic AI inside a customer’s existing identity, permissions, and audit controls. IFS built it from six components, each aimed at a specific failure.

• Planning and orchestration break goals into steps and coordinate agents and tools.
• Skills and connectors define and validate which systems an agent can touch.
• Memory and context carry progress forward and assemble only the information a task needs.
• Guardrails and permissions enforce identity, approvals, and limits on risky actions.
• Verification and escalation checks work for correctness and policy compliance, escalating when needed.
• Observability and auditability log every decision and action so they can be traced after the fact.

IFS said every write-back to a customer’s system of record requires explicit approval, pointing to releasing a shop order or posting a ledger entry as the kind of action that cannot simply be undone. IFS also said it is extending its IFS Cloud services perimeter so customer data never reaches a frontier AI lab. That is more specific than “no raw data to external providers,” but it still describes an architectural intent rather than a contractual guarantee. IFS has not defined, in terms an enterprise can rely on, whether prompts, embeddings, or other context derived from a customer’s records ever leave that perimeter. Companies with strict data-sovereignty requirements, in defense, energy, and other regulated sectors, should get that distinction in writing rather than inferring it from a keynote or a launch release.

Where the Differentiation Case Holds Up, and Where It Doesn’t

Across four releases and the keynote, IFS makes a specific competitive argument only once. Most of what it calls differentiation describes capabilities that the rest of the enterprise AI market now claims as standard. Governance and guardrails language mirrors what Salesforce calls its Agentforce Trust Layer, what SAP calls Joule’s governance framework, and what ServiceNow calls its AI Control Tower: permissions, audit trails, and human escalation have become baseline vendor messaging, not a point of difference. The promise that customer data never reaches an external AI provider matches claims Salesforce and SAP already make about their own agent platforms. Working across multiple AI models rather than one is also increasingly common among agent platforms, not a feature unique to IFS.

The ecosystem-orchestration argument undercuts itself. Mark Moffat described IFS as sitting “at the center” of a partner network spanning Siemens, Microsoft, Anthropic, and OpenAI, but Siemens’ own president described a near-identical partnership with Microsoft from the same stage two years earlier. When several vendors can each claim to sit at the center of the same partner list, the claim stops describing a structural advantage and starts describing a roster of integrations.

Moffat said as much himself at the press and analyst session: the draw of allying with Siemens and Schneider Electric is reaching more than exclusivity. The two companies’ combined install base covers, in his words, “literally 100% of all utilities,” giving IFS access to customers it would otherwise find expensive to acquire on its own, a distribution argument rather than a claim that the technical integration itself is unique.

That said, IFS does have a defensible moat consisting of a combination of hard-to-replicate advantages, including industry depth and customer relationships. Furthermore, IFS fine-tunes its own proprietary models but reserves them for air-gapped, defense-grade deployments where no partner cloud is acceptable to the customer, deferring to partner models such as Microsoft’s everywhere else so it does not compete with Microsoft’s own sovereign-cloud and model business.

IFS’s argument that it already holds decades of asset, maintenance, and service history for a large base of industrial customers, and that IFS Intelligence reasons over that operational context rather than a general model’s training data, is a genuine structural advantage over horizontal platforms like Microsoft Copilot or Salesforce Agentforce, which lack that embedded industrial data by design. It is a weaker advantage against other industrial ERP and EAM incumbents, including SAP, Oracle, Infor, and IBM Maximo, which often make similar claims about their own installed base of customers.

The scaled, feature-unrestricted license is a real go-to-market difference from the credit- or consumption-based pricing common among rival agent platforms, though an unpublished percentage and an unpublished usage entitlement limit how much credit that difference deserves until IFS lets a buyer run the numbers.

CEO Mark Moffat said that IFS is building for the asset and service lifecycle specifically, expects two or three competing intelligence layers to coexist inside most large enterprises, and said it is designing IFS Intelligence so data can flow out to those other layers rather than stay contained inside it. Both answers describe a company betting more on domain depth than a platform moat.

What to Watch:

IFS has built a coherent story, reinforced by Nexus Black, the internal unit it says can move from signed contract to deployed tool in weeks. Whether it holds up at the scale IFS needs depends on evidence it has not yet published or validated by a third party.

• The price is an approach, not a fixed percentage. Moffat described IFS Intelligence pricing as a percentage of a customer’s existing IFS contract, scaled by business size, plant count, and asset count, and said exceeding the usage entitlement triggers a conversation rather than an automatic charge. IFS has published neither the percentage nor the entitlement’s size, so no prospective buyer can estimate a bill from public information alone.
• Regulatory engagement is still young by the company’s own account. Moffat said IFS built a dedicated regulatory affairs capability only in the past 18 months and called the company “many orders of magnitude smaller” than SAP or Salesforce in that function, relying on larger customers to engage regulators on its behalf in the meantime.
• The named proof points still skew small and mid-market. Sims Crane and Equipment is the only customer IFS has named for IFS Intelligence itself, and the two customer wins Nexus Black showcased onstage, a distillery and a growing building-services company, are real deployments with real numbers. But none approaches the scale or regulatory complexity of a multi-site aerospace, energy, or defense operation, the sectors where IFS pitches the Harness hardest.
• “Extending the IFS Cloud perimeter” is a description, not a guarantee. IFS said customer data never reaches a frontier AI lab and that writing back to the system of record always requires approval, but it has not defined, in terms an enterprise can rely on, whether prompts, embeddings, or other derived context ever leave that perimeter.
• Agent-to-agent governance across vendors is an industry-wide blank, not just an IFS one. IFS’s own product leadership says no contractual or billing standard yet exists for when its agents call agents running on another vendor’s platform, a gap that Oracle, Salesforce, and a startup called Paid AI are each approaching differently. Buyers running mixed-vendor environments should ask how IFS handles liability and data boundaries at that hand-off rather than assume the Harness already covers it.

You can read the full press releases at IFS’s website.

Disclosure: Futurum is a research and advisory firm that engages or has engaged in research, analysis, and advisory services with many technology companies, including those mentioned in this article. The author does not hold any equity positions with any company mentioned in this article.

Analysis and opinions expressed herein are specific to the analyst individually and data and other information that might have been provided for validation, not those of Futurum as a whole.

Other Insights From Futurum:

IFS Bets on Saudi Arabia’s Industrial AI Opportunity

Does the New ERP Platform “Signal” Get the Market Right?

IFS’s 25% Growth: A Sign of Industrial AI’s Rising Strength?

Author Information

Keith Kirkpatrick

Keith Kirkpatrick is VP & Research Director, Enterprise Software & Digital Workflows for The Futurum Group. Keith has over 25 years of experience in research, marketing, and consulting-based fields.

He has authored in-depth reports and market forecast studies covering artificial intelligence, biometrics, data analytics, robotics, high performance computing, and quantum computing, with a specific focus on the use of these technologies within large enterprise organizations and SMBs. He has also established strong working relationships with the international technology vendor community and is a frequent speaker at industry conferences and events.

In his career as a financial and technology journalist he has written for national and trade publications, including BusinessWeek, CNBC.com, Investment Dealers’ Digest, The Red Herring, The Communications of the ACM, and Mobile Computing & Communications, among others.

He is a member of the Association of Independent Information Professionals (AIIP).

Keith holds dual Bachelor of Arts degrees in Magazine Journalism and Sociology from Syracuse University.