Decision brief

Ask the demo to survive a shift change

Use a work order, an old procedure and an absent operator to see what the agent does when the easy part is over.

Buying guide

Start with the missing supplier reply

An overdue confirmation is a useful place to begin. Define what the agent may read, what it can draft and which decisions stay with the buyer.

Read the article

Implementation plan

Before the next shift takes over

Agree the pass conditions, rehearse a failed update and leave the team a procedure it can use without the original builder.

Read the article

From the archive

The Best Enterprise AI Solutions for Manufacturing Operations

Seven enterprise AI solutions assessed for manufacturing operations, from supplier follow up and order handling to plant knowledge and aftersales support, with the criteria, a buyer's guide and a shortlist checklist.

Read the article

Editorial selection

Full comparison

Nexus

Best for: An operations team that will own the procedure and accept the result, with help to build it.

If your buyer or planner knows the job but needs someone to build the agent, start with Nexus. Its engineer-led offer is relevant to that gap; ask to see it handle the plant’s own procedure.^1,2

Limitations

A required system action, hosting boundary or support period is still unanswered.

Read profile

UiPath

Best for: Automation teams joining software robots, applications and human decisions in an existing process.

UiPath is a strong alternative when a plant already uses software robots and needs work to pause for a document or a person’s decision. Its platform explicitly connects those steps with agents.^3,4,5

Limitations

The chosen deployment has not shown the required agents, connections and recovery steps working together.

Read profile

UiPath orchestration view of a loan process with application intake, credit and identity, underwriting decision and funding steps — Image from UiPath.

Microsoft Copilot Studio

Best for: A Microsoft-centered plant with assigned builders and a way to approve releases.

Copilot Studio deserves a look when plant IT already manages Microsoft environments and has people ready to build and release agents. Its policies and release tools can fit that team’s existing work.^6,7,8

Limitations

You are treating a knowledge answer as proof of an allowed ERP update, or a license as a promise to do the build.

Read profile

Copilot Studio start screen with a prompt box and choices to build an agent, a workflow or an app — Image from Microsoft Copilot Studio.

Full comparison

Compare the shortlist

Choose which providers to keep, then focus the evidence on one buying criterion.

Providers

Focus on

1NexusAn operations team that will own the procedure and accept the result, with help to build it.

If your buyer or planner knows the job but needs someone to build the agent, start with Nexus. Its engineer-led offer is relevant to that gap; ask to see it handle the plant’s own procedure.^1,2

The plant task

Partly documented

Nexus says an engineer builds the first procedure alongside your team and shows it running in your own tools.¹

Your systems

Partly documented

Nexus lists connections to ERP and CRM systems, communications tools and custom APIs. It says information can pass in both directions.^9,10

Unfinished work

Partly documented

Nexus says uncertain cases go to a person with the relevant context.¹¹

Permission to act

Partly documented

Nexus describes access by role and records of actions and decisions. Its blog says data flow, access and audit trails need sign-off before launch.^12,13

Help on every shift

Documented

Nexus says it builds with the customer’s team and stays to improve the first version.^1,2

Read profile

2Microsoft Copilot StudioA Microsoft-centered plant with assigned builders and a way to approve releases.

The plant task

Partly documented

Microsoft says makers can describe an agent in ordinary language and test it before publishing.¹⁴

Your systems

Partly documented

Microsoft lists Power Platform, Dynamics 365 and external knowledge sources, alongside prebuilt connectors and MCP servers.^8,15

Unfinished work

Not established

Can the agent save unfinished work and hand it over when a system fails or the shift changes?

Permission to act

Partly documented

Microsoft documents administrator data policies, knowledge access tied to the signed-in user and approval gates for moving agents into production.^6,16,7

Help on every shift

Partly documented

Microsoft provides tools to build and test agents, with controls for moving them through development, test and production.^14,7

Read profile

3Google Gemini EnterpriseGoogle Cloud teams connecting engineering information or analyzing approved data from production-support work.

Gemini Enterprise is worth considering when the plant’s information already lives in Google Cloud projects or BigQuery. Its search and data connections give that team a place to start.^17,18

The plant task

Partly documented

Google describes search that respects permissions and a workbench for building agents without code. It also offers a Frontline edition for frontline workers.^17,19,20

Your systems

Partly documented

Google documents a federated BigQuery connector. It says data stays in place when Data Cloud connectors use federated mode.^18,21

Unfinished work

Not established

Where does the agent record a failed query, conflicting information or a task waiting for the next shift?

Permission to act

Partly documented

Google documents Cloud IAM and document-level access controls. Its Agent Platform documentation describes tool-use rules written in plain language.^22,23,24

Help on every shift

Partly documented

Google documents buying a subscription, then distributing its licenses across projects and locations. Standard and Plus customers can publish their own agents.^25,26,27

Read profile

4UiPathAutomation teams joining software robots, applications and human decisions in an existing process.

The plant task

Documented

UiPath describes a platform joining AI, people and systems: agents reason, software robots act and people make decisions where needed.^3,4

Your systems

Partly documented

UiPath’s Integration Service includes prebuilt connectors and a Connector Builder.²⁸

Unfinished work

Documented

UiPath says a process can wait for documents or approval and then resume. Low-confidence decisions can go to a person with their context.^5,29

Permission to act

Documented

UiPath describes pauses for approval and tamper-evident logs recording actions, tool calls and human approvers.^5,30

Help on every shift

Partly documented

UiPath offers code-first and low-code development. Its pricing material describes self-hosted installation, including air-gapped deployment.^31,32

Read profile

5WorkatoManufacturers with someone responsible for integrations and a defined sequence across business systems.

Workato is a strong candidate when an integration team wants events in business systems to start and coordinate work. Its triggers and reusable recipes suit that approach.^33,34,35

The plant task

Documented

Workato says its Genies can start from business events, schedules or APIs, and use reusable recipes and skills.^33,34

Your systems

Partly documented

Workato describes ERP and database connections, with a gateway or On-Prem Agent for reaching on-premises applications.^35,36,37

Unfinished work

Partly documented

Workato documents audit logs for workflow runs, configuration changes and user actions.³⁸

Permission to act

Documented

Workato describes human approvals, detailed access controls and roles deciding who can create, build and deploy workflows and agents.^39,40

Help on every shift

Partly documented

Workato offers onboarding and training packages. Standard includes development, test and production environments.^41,42

Read profile

6GleanTeams bringing scattered procedures, tickets and engineering information together before adding actions.

Glean deserves attention when maintenance or engineering staff struggle to find the right information across tools. Its search and source-permission model fit that first job.^43,44,45

The plant task

Documented

Glean describes enterprise search and bringing engineering code, tickets, documents and incident history together.^43,45

Your systems

Partly documented

Glean offers an Indexing SDK for custom data and OpenAPI definitions for custom actions.^46,47

Unfinished work

Partly documented

Glean describes requiring approval before an agent acts and sending audit events to a security monitoring system, or SIEM.^48,49

Permission to act

Partly documented

Glean says source-system permissions apply to reads and writes. The security material checked November 8 marked agent policies and separate agent or user policies as coming soon.^44,50,51

Help on every shift

Not established

Who owns source permissions, connector setup, current content and ongoing support in Glean’s proposal?

Read profile

7Relevance AIOperations teams with named staff ready to take over building, evaluating and supervising agents.

Relevance AI is worth considering if the first project should teach your operations team to build and supervise later agents. It describes workflow mapping, an embedded team and training.^52,53

The plant task

Partly documented

Relevance AI says it helps customers map workflows and identify suitable agent use cases.⁵³

Your systems

Partly documented

Relevance AI says schedules, application events, webhooks and custom signals can start an agent.⁵⁴

Unfinished work

Partly documented

Relevance AI lists conditional approval rules and ways to pass cases on through email and Slack.^55,56

Permission to act

Documented

Relevance AI describes approvals for individual tools, customer-set thresholds for human sign-off and rerunning evaluations before publishing changes.^57,58,59

Help on every shift

Documented

Relevance AI describes an embedded team that gets the customer live and then trains the customer’s staff.⁵²

Read profile

When another provider fits

UiPath

Your plant already uses software robots, and the process needs to wait for documents or decisions.

Put UiPath near the top of that evaluation. It describes agents, software robots and people working in one process, with pauses and resumptions around approvals.^3,4,5

Trade-off: Name who maintains each robot and connection, then show how the chosen installation recovers from a failure. The engineering work still needs an owner.^31,28

Microsoft Copilot Studio

Plant IT already manages Microsoft environments, data policies and releases.

Copilot Studio may fit that team well. Its documented data policies and release approvals give colleagues controls within the environment they already manage.^6,7

Trade-off: Give the builders time and check every plant connection. Access to Dynamics knowledge does not prove the action needed in another ERP or maintenance system.^14,8,15

Glean

A maintenance colleague needs the current approved procedure or a relevant incident record.

Give Glean an early trial. Its search respects source permissions, and its engineering proposition brings documents, tickets and incident history together.^43,44,45

Trade-off: Decide who owns each document and how the correct revision is selected. Permission to read a procedure does not show that it is current for this machine.⁴⁴

Workato

Your integration team maintains recipes and wants business events to start work across systems.

Workato is a direct candidate. Its event, schedule and API triggers and reusable recipes fit that approach.^33,34

Trade-off: Follow the entire network and data path. Workato’s On-Prem Agent reaches private systems; that does not mean all of Workato runs inside the plant.³⁷