FactoryTalk and Plex MES + AI
AI for Rockwell FactoryTalk ProductionCentre and Plex MES, Without Exposing Plant Data
Short answer
AI for Rockwell MES puts a private language model over FactoryTalk ProductionCentre's relational data and web services, or over Plex MES through its REST APIs, so supervisors and quality staff can ask plain-English questions about orders, downtime, genealogy and quality. The model is grounded in your records, shows its query, and does not write back without human approval.
- ERP
- Rockwell FactoryTalk ProductionCentre, Plex MES, FactoryTalk Historian
- Industries
- Automotive, Aerospace, Food and Beverage, Industrial Machinery
- Written for
- Plant Operations Manager
Rockwell Automation's MES story has two different engines. FactoryTalk ProductionCentre, which has its roots in the Datasweep product, is a configurable on-premises execution system built on a relational database and a business object layer. Plex, acquired by Rockwell in 2021, is a cloud-native manufacturing platform where MES, quality and ERP functions share one multi-tenant data model and are reached through APIs. Plants often run one, the other, or both after acquisitions.
The two engines present very different integration problems for AI. ProductionCentre is typically on-site, customized by an integrator, and wired to Allen-Bradley PLCs, FactoryTalk Historian and an ERP such as SAP or Oracle. Plex is hosted, so the question becomes which APIs and extracts are available, what the vendor's own analytics already cover, and whether a customer's data policy permits piping production records to a separate AI service.
Rockwell and Plex are both building AI features, and for routine analytics they may be enough. The gap tends to appear when a plant wants cross-system answers: why did a line miss its rate, combining PLC downtime from the historian, quality results from the MES, and material availability from the ERP, in one grounded response that a supervisor can read in the shift meeting.
This page explains how a private AI layer connects to each engine, what it should and should not do, and which questions to ask any vendor before they touch production or quality data.
What usually gets in the way
The problems we hear most from plant operations manager teams running Rockwell FactoryTalk ProductionCentre.
Two MES engines, one plant floor
After acquisitions, a company may run ProductionCentre at one site and Plex at another. Reporting is rebuilt per site, and corporate asks for cross-site comparisons that nobody can produce without a spreadsheet exercise.
Downtime reasons do not match reality
Operators select a coded reason in a hurry, and the real cause sits in PLC fault history or free-text notes. Pareto charts built on codes alone tell an incomplete story.
Historian data and MES data live apart
Time-series from FactoryTalk Historian and transactional MES records join poorly. Answering why a batch failed means correlating tag trends with lot and order data by hand.
Customized business logic is poorly documented
ProductionCentre sites often depend on an integrator's custom business objects and reports. When that person leaves, the knowledge of how a status is derived leaves with them.
Cloud analytics limits and data policy
Plex data is hosted, and some customers cannot send extracts to third-party AI services under customer contracts or export controls, yet still want natural-language access.
Where AI earns its place in Rockwell FactoryTalk ProductionCentre
Each use case names the ERP objects it reads or writes, so your ERP team can judge the integration effort before anyone commits budget.
Shift handover summaries
Generates a grounded summary of the last shift: orders completed, scrap, top downtime events and open quality holds, with each figure linked to its source record.
Touches: Production orders, downtime events, scrap transactions, holds, shift calendars
Outcome: Replaces manual handover compilation; supervisors still review before the meeting.
Downtime root-cause assistant
Combines coded downtime with PLC alarm history and operator notes to propose likely causes for a long stop, with evidence from each source.
Touches: Downtime reasons, FactoryTalk Historian tags and alarms, maintenance work orders
Outcome: Faster triage of repeat stops; the model proposes, the maintenance lead decides.
Lot genealogy and containment
Answers forward and backward trace questions across work orders, lots and shipments, joined to ERP supplier receipts.
Touches: Lot genealogy, component consumption, shipments, supplier lots
Outcome: Cuts initial containment scoping from hours toward minutes.
Quality results and SPC narrative
Explains why a characteristic is trending toward a limit in plain language, citing recent samples, tooling changes and material lots.
Touches: Inspection results, control charts, tool changes, material lots
Outcome: Earlier attention to drift; control limits and responses stay with quality engineers.
Cross-site OEE comparison
Normalizes availability, performance and quality across ProductionCentre and Plex sites and explains the largest gaps.
Touches: Run time, downtime, ideal cycle time, good and total counts
Outcome: A defensible comparison once definitions are aligned; most effort is agreeing on OEE rules.
Work order status Q&A for customer service
Customer service asks whether an order will ship on time and gets an answer that combines MES progress with ERP promise date.
Touches: Production order progress, sales order promise dates, shipment records
Outcome: Fewer calls to the floor; answers show their basis and confidence.
Maintenance and changeover insights
Looks at changeover durations and maintenance work orders to identify sequences that consistently run long and the resources involved.
Touches: Changeover events, work orders, resource calendars, SKU sequences
Outcome: Input to scheduling and SMED efforts; benefit depends on event data quality.
Reference architecture
A private AI layer reads from the MES through the interface appropriate to each engine: curated read-only views and web services for ProductionCentre, and the Plex REST APIs or governed data extracts for Plex. It adds a Historian connector for time-series, joins ERP keys, and serves open-weight models on infrastructure you control.
- 1
Engine-specific connectors
A read-only SQL path and service calls for ProductionCentre; REST API clients with scoped credentials for Plex; an OPC UA or Historian query path for time-series.
- 2
Unified plant model
A mapping that normalizes orders, resources, downtime reasons and quality characteristics across engines and sites so queries mean the same thing everywhere.
- 3
Grounded query and retrieval
Validated, parameterized queries and document retrieval with sources cited; the underlying query is shown with each answer.
- 4
Private model serving
Open-weight models on local GPUs, with no outbound inference calls. For Plex, only the minimum extract needed is brought on-prem.
- 5
Governance
Role-based access mirroring MES and ERP roles, full logging, and human approval on any write-back or notification.
Integration notes for your ERP team
- For ProductionCentre, prefer read-only views over its relational store and avoid querying its internal tables directly, which are subject to change between releases.
- For Plex, use the Plex developer APIs with a scoped integration credential and respect API rate limits; pull incrementally rather than bulk scanning.
- Connect FactoryTalk Historian through its supported query interfaces, and decide up front which tags are in scope; tag naming is rarely consistent across lines.
- Align downtime reason codes and OEE definitions across sites before attempting cross-site comparisons.
- Join MES to ERP on production order, part number and lot, and confirm that backflush timing matches what MES reports.
- Allen-Bradley PLC context (fault codes, recipes) is best consumed through the Historian or OPC UA, not directly from controllers.
Deployment options
On-prem at the plant
ProductionCentre sites with segmented OT networks
GPU server in the plant or regional data center, reaching the MES database and Historian over approved network paths.
Private cloud with governed Plex extracts
Plex customers whose policy allows data in their own tenant
Extracts via Plex APIs land in a private environment you control, where the model runs.
Air-gapped
Defense and export-controlled production
Isolated deployment with scheduled one-way data transfer and offline updates.
Compliance and data control
How the architecture supports your obligations. Certification and accountability stay with your organisation; the design keeps the evidence straightforward.
IATF 16949
Traceability, containment and process-control answers cite source records to support your own audit evidence.
AS9100 and customer flow-down
Customer-controlled data stays inside your boundary; the layer logs who asked what and what was returned.
FSMA 204 and lot traceability (food)
Forward and backward trace queries can support your traceability plan; your records remain the system of record.
ISA/IEC 62443 and OT segmentation
The AI layer connects from the IT side through defined conduits, with read-only access and no path back into control networks.
ITAR / CMMC
On-prem or air-gapped options let you meet your own controls. Compliance is determined on your environment.
Where Netray fits
Custom build
Engine-specific connectors and a unified plant model across ProductionCentre and Plex are bespoke work.
ERPray
Answers the ERP half of shift and order questions, such as promise dates, material availability and costs.
DataRay
Queries quality documents and file-share records alongside MES tables, on-prem.
How an engagement runs
Phase 1 . 2-3 weeks
Assessment
- -Map of MES engines, sites, Historian and ERP
- -Top supervisor and quality questions
- -Data policy and access review
Phase 2 . 3-6 weeks
Connectors and plant model
- -Read-only connectors per engine
- -Normalized downtime and OEE definitions
- -Evaluation set of real questions
Phase 3 . 4-6 weeks
Pilot on one area
- -Shift summary and downtime assistant
- -Accuracy report
- -Logging and approval workflow
Phase 4 . 4-8 weeks
Rollout
- -Additional sites and use cases
- -Operational runbook
- -Training for supervisors and quality
- -Support plan
Questions to ask any vendor, including us
A short list that separates real Rockwell FactoryTalk ProductionCentre AI work from a chatbot demo.
- Which interface do you use for ProductionCentre and which for Plex, and who owns credentials?
- Does production or quality data from Plex leave our tenant, and where is it stored?
- How do you reconcile downtime codes and OEE definitions across sites?
- What access do you need to the Historian, and is it read-only?
- How are answers verified against source records?
- What does Rockwell or Plex already provide natively that overlaps?
- How do you prevent a path from the AI layer into control networks?
Frequently asked questions
Is AI for Plex different from AI for FactoryTalk ProductionCentre?
Yes, in the connection method. ProductionCentre is usually on-prem with a relational store, so read-only views are typical. Plex is a hosted platform, so the AI layer uses its REST APIs or governed extracts. The semantic layer and the governance model are shared, but the data paths and limits differ.
Can I use AI on Plex data without leaving the Plex tenant?
That depends on what Plex offers for your subscription and on your data policy. If the vendor's built-in analytics meets your need, use it. If you need cross-system answers with your own models, you pull governed extracts through the APIs into an environment you control.
Does the assistant control equipment or change schedules?
No. It reads data and drafts explanations or suggestions. Any change to orders, schedules or notifications is approved by a person and executed in the MES or ERP. There is no write path into PLCs or control networks.
How does it use FactoryTalk Historian?
Through a read-only query path for selected tags, usually alarms, states and key process variables around a downtime or quality event. We agree the tag list up front, since broad ingestion of every tag is costly and rarely useful.
What about sites running both engines?
A normalization layer maps orders, resources and reasons into a common plant model. Most of the effort is aligning definitions such as what counts as planned downtime, not the technology. Cross-site comparisons are only as good as those definitions.
Which models are used?
Open-weight models in the Llama, Qwen, Mistral, Gemma or gpt-oss class, served with vLLM or Ollama on your GPUs. The choice depends on language needs, hardware, and an evaluation on your own questions, not on benchmark claims.
What does a pilot cost in effort?
Expect a focused pilot over roughly 8 to 14 weeks with a small joint team: one MES administrator, one quality or operations lead, and IT security. The main variables are access approvals, the number of customizations, and how consistent downtime coding is.
Related guides
AI for Plex Manufacturing Cloud, Grounded in Your Production Data
Put AI on Plex production, quality, and genealogy data without a public model. On-prem or private-cloud LLMs, RAG, and agents built for Plex shops.
Shop floor + on-prem AIAI shop floor assistant for operators working inside your ERP
An on-prem AI copilot answers operator questions against your ERP work instructions, travelers, and routings in plain language, at the machine, without a screen full of menus.
Faster paperwork, same standardAI for NCR, CAPA, and 8D Drafting in AS9100 and ISO 9001 Quality Systems
AI drafts NCR, CAPA, and 8D reports from ERP quality data for engineer review, cutting drafting time under AS9100 and ISO 9001 without changing sign-off.
Digital thread + AIAI Across PLM and ERP: Teamcenter, Windchill, and Your ERP
AI that reads Teamcenter or Windchill alongside your ERP to trace engineering change impact, BOM sync gaps, and where-used questions, on-prem.
EMS / PCBA + on-prem AIAI for EMS and PCBA Manufacturers Running SyteLine, Epicor, or NetSuite
AI for EMS and PCBA manufacturers on SyteLine, Epicor, or NetSuite: automate BOM scrubbing, AVL checks, and obsolescence alerts, grounded in your own ERP data on-prem.
Opcenter Execution + private AIAI for Siemens Opcenter Execution MES, Running Inside Your Own Network
Add private, grounded AI to Siemens Opcenter Execution MES: ask questions over lots, work orders, nonconformances and genealogy without leaving your network.
Plan it with numbers
OEE Calculator (Overall Equipment Effectiveness)
Break your Overall Equipment Effectiveness into availability, performance, and quality, and see how far you sit from the 85% world-class benchmark.
Free ToolMES Implementation Cost Calculator
Estimate total MES implementation cost across licensing, shop-floor terminal hardware, configuration labor, and ERP integration complexity.
Free ToolScrap Rate Cost Calculator
Turn your scrap percentage into an annual dollar figure - including labor and overhead absorbed by scrapped units - and see what each point of improvement is worth.
GuideSmart Factory ERP Integration: Industry 4.0 Connectivity Guide
Connect your smart factory systems to ERP with this Industry 4.0 integration guide covering MES, SCADA, IoT platforms, and real-time production data pipelines.
GuideAI Predictive Maintenance with ERP Integration
Integrate AI predictive maintenance with your ERP system. Reduce unplanned downtime by 45% using sensor data, ML models, and automated work order generation.
GuideOn-Prem AI for Defense Contractors: The Complete Guide
On-prem AI for defense contractors: deploy LLMs and AI agents inside your CMMC and ITAR boundary. Architecture, hardware costs, timelines, and vendor options.
Talk it through with an engineer who knows Rockwell FactoryTalk ProductionCentre
Bring one real question your team cannot answer from the ERP today. We will map the data path, the model, and where it runs, and tell you honestly if AI is the wrong tool for it.