How to Add a Private AI Layer to Rockwell FactoryTalk On-Prem
how to add AI to Rockwell FactoryTalk on-prem
Also searched as
- FactoryTalk Historian AI integration
- FactoryTalk ProductionCentre AI assistant without cloud
- local LLM for FactoryTalk alarm and event data
- private AI Rockwell Automation plant data
Short answer
FactoryTalk is a family, so pick the read surface per product: Historian SE through its PI-based interfaces, View SE alarm and event logs through the SQL database, ProductionCentre through its documented interfaces, and VantagePoint where you already consolidate data. Put a read-only tool server in front, serve an open-weight model locally, and respect FactoryTalk Security.
Applies to: FactoryTalk View SE, FactoryTalk Historian SE, FactoryTalk ProductionCentre and FactoryTalk VantagePoint on-prem. Product versions differ; confirm interfaces against your installed release.
Reference build, in order
- 1Inventory which FactoryTalk products you actually run, and for each one name the supported read interface (Historian interfaces, SQL log database, product SDK or web services, VantagePoint models).
- 2Create read-only identities in each system and, where possible, use a reporting copy or replica rather than the production server.
- 3Build a tag and asset catalog from Historian and the HMI project (descriptions, units, areas) for retrieval.
- 4Index plant documents: SOPs, batch and lot records, maintenance notes, alarm philosophy, with source permissions attached.
- 5Write a tool server with named read operations per source and strict time and row caps.
- 6Serve an open-weight model on local GPUs through vLLM or Ollama, connected only to the tool server.
- 7Mirror FactoryTalk Security roles and areas into the tool server's allow lists, and log every call.
- 8Roll out read-only first, then drafted outputs, then approved write-backs in business systems only.
The FactoryTalk read surfaces, product by product
FactoryTalk Historian SE is built on a PI Data Archive, so the same read patterns as the PI System apply: PI Web API where it is available in your release, or the PI-family SQL and SDK interfaces. Check what your installed version ships and whether PI Web API is deployed; do not assume it.
FactoryTalk View SE keeps its runtime in the HMI server and its configuration under the FactoryTalk Directory. Alarm and event history can be logged to a SQL Server database when that logging is configured, which gives you an ordinary, queryable source. The exact table and view names depend on how logging was set up, so inspect your own database rather than trusting a generic script.
FactoryTalk ProductionCentre is Rockwell's MES. Its business objects are best reached through its supported SDK or web interfaces for your version, with direct SQL reserved for read-only reporting if your integrator has documented the views. FactoryTalk VantagePoint is a useful single read surface if you already model plant data there.
# Historian SE (PI-based), if PI Web API is deployed
GET https://ft-hist.plant.local/piwebapi/streams/{webId}/summary?startTime=*-24h&endTime=*&summaryType=Average&summaryDuration=1h
-- Alarm and event log (SQL Server). Object names depend on your logging setup.
SELECT TOP (200) *
FROM <your_alarm_event_log_view>
WHERE <timestamp_column> >= DATEADD(hh, -24, GETDATE())
ORDER BY <timestamp_column> DESC;Reference architecture
Keep the AI stack on the business side of the network, behind the same firewall conventions you use between the plant and enterprise zones. The tool server is the only component allowed to reach the Historian, the log database and the MES interface, and it uses read-only identities.
Retrieval combines metadata (tags, areas, equipment names) with text (SOPs, deviations, lot notes). Questions like 'which lots ran on press 4 during the pressure alarm' need MES lot data, alarm history and Historian values, and the tool server should expose a named operation for each of them.
For an air-gapped site, load models and containers from approved media, run embeddings locally and keep the audit log in the isolated zone.
Permissions through FactoryTalk Security
FactoryTalk Security centralises users, groups and actions through the FactoryTalk Directory, and authenticates against Windows accounts. It controls what a person may do in View SE, not what a SQL login can read, so you must bring the idea of areas and roles into the tool server yourself.
Translate FactoryTalk groups and areas into allow lists of tags, equipment and lots. Apply them when building answers and when filtering the retrieval index, so a document or tag from a restricted area never reaches the model's context.
Test by role, including a contractor identity, and keep the mapping in a reviewed file with an owner.
Write-back, sizing and phases
Controller tags and HMI write paths are out of scope for an assistant. Useful write-backs are in business systems: a maintenance request, a quality hold, a draft downtime reason, each submitted through the target system's API after a person approves the exact payload. If ProductionCentre transactions are involved, use its supported transaction interfaces, never table updates.
As a range, one 24 to 48 GB GPU serves a department of tens of occasional users; a few hundred active users usually need two to four GPUs plus headroom. A document index for tens of thousands of files is a few GB to low tens of GB.
Phase 1: read-only alarm, trend and lot questions for one line. Phase 2: drafted shift and deviation reports. Phase 3: approved requests and holds in downstream systems.
Limits and when the vendor tools are enough
If your goal is dashboards and reports across FactoryTalk data, VantagePoint and the standard reporting tools may already do it, and an AI layer is optional. The assistant earns its place when users must combine alarms, history, lots and documents in plain language, or when people do not know where to look.
Expect integration effort to vary a lot by product and version. Do not promise a unified answer across View SE, Historian and ProductionCentre until each read path is tested individually. Rockwell and its partners also offer their own analytics offerings; they may be sufficient if cloud is acceptable.
Try it here, free
Rockwell FactoryTalk Private AI Layer Blueprint Generator
Fill in your environment and get an architecture plan for a private AI assistant on Rockwell FactoryTalk: components, security controls, rollout phases and open questions for IT.
Common pitfalls
- !Assuming one interface covers all FactoryTalk products. Each has its own supported read path.
- !Copying generic SQL for alarm logs without inspecting the real object names in your logging database.
- !Reading ProductionCentre tables directly when a supported interface exists for the same data.
- !Assuming FactoryTalk Security automatically limits what a SQL login can read.
- !Letting an AI service near controller or HMI write paths.
- !Querying the live HMI server for history instead of a log database or Historian replica.
How an ERP-grounded AI assistant handles this
Netray builds the tool server and retrieval layer against whichever FactoryTalk interfaces you have approved, and links them to ERP data through ERPray so a question can span alarms, lots and purchase orders. Tool calls and sources are shown to the user.
Frequently asked questions
Is FactoryTalk Historian the same as the PI System?
FactoryTalk Historian SE is built on PI technology, so many PI patterns apply. Capabilities and which interfaces ship depend on the release, so confirm against your install before designing around PI Web API or other PI tools.
Can the assistant acknowledge alarms or change setpoints?
It should not. Controller and HMI write paths are outside the safe scope for chat-driven automation. Limit write-backs to business records such as maintenance requests, each approved by a person.
Do we need VantagePoint?
No. It is helpful if you already consolidate FactoryTalk and other data there, because it gives one read surface. Without it, the tool server can read each source directly.
Can all of this run air-gapped?
Yes. Models, embeddings, index, tool server and logs all run on your own servers, loaded from approved media. No outbound connection is required.
Related
How to Connect OPC UA Machine Data to Your ERP
Do not connect OPC UA servers straight to the ERP. Read machine tags through an edge gateway or MES, convert signals into business events (cycle complete, stop, state change, count), attach the work order context, and post summarised confirmations to the ERP through its supported API. The ERP wants quantities, times and reasons per order, not millions of raw tag values.
How-toHow to Calculate OEE from MES Data and ERP Standards
OEE equals Availability times Performance times Quality. Availability comes from MES run and stop events against planned production time, Performance compares actual output to the ideal cycle time (usually the routing standard from the ERP), and Quality is good units divided by total units. The numbers are only trustworthy if planned time, ideal cycle time and the good/scrap split are defined once and used consistently.
AdvancedHow to Add AI to the AVEVA PI System On-Prem, Without Moving Data to a Cloud
Put a read-only tool server in front of PI Web API, index the PI AF asset model plus your SOPs and shift logs, and serve an open-weight model on local GPUs. The model asks tools for bounded summaries instead of raw tag data, and every call runs with the asking user's PI identity and is logged.
AdvancedHow to Add AI to a Self-Hosted Ignition Gateway Without Cloud
Ignition writes history and alarms to a SQL database you own, so a read-only database account plus a few WebDev or Named Query endpoints give an AI tool server clean access. Index the tag tree and your plant documents, serve an open-weight model on local GPUs, and map Ignition roles and tag permissions into the tool layer.
How-toHow to Send Production and Labor Reporting from MES to ERP
Treat the ERP work order as the system of record for cost and quantity, and the MES as the system of record for what physically happened. Send one confirmation message per operation (or per shift or lot) containing work order, operation sequence, good quantity, scrap quantity with reason, and labor start/stop per employee and work center, post it through the ERP's supported transaction API, and make the message idempotent so a retry never double-posts.
AdvancedISA-95 and B2MML: How to Integrate ERP with MES
ISA-95 defines the boundary between business systems (Level 4, the ERP) and manufacturing operations (Level 3, the MES) and the information that crosses it. B2MML is the XML implementation of those models. In practice you exchange a ProductionSchedule from ERP to MES, and ProductionPerformance, plus material and equipment information, back, mapping each element to your ERP's work order and confirmation APIs.
AI for ERPAI for SAP Plant Maintenance: Notifications, Work Orders, and Predictive Signals
AI grounded on SAP PM data that triages notifications, drafts work orders, standardizes failure codes, and flags predictive maintenance signals, on-prem.
AI for ERPAI 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.
Stuck on Rockwell FactoryTalk?
Talk to engineers who work inside Rockwell FactoryTalk every week, and who build private AI that answers these questions from your own ERP data.
Keep exploring
Free tools
- Rockwell FactoryTalk Private AI Layer Blueprint GeneratorFill in your environment and get an architecture plan for a private AI assistant on Rockwell FactoryTalk: components, security controls, rollout phases and open questions for IT.
- Rockwell FactoryTalk AI Assistant Sizing and Value CalculatorEstimate peak concurrency, GPU count, index size, hours saved and payback for a private on-prem AI assistant on Rockwell FactoryTalk.
ERP fixes and how-tos
- AI on AVEVA System Platform and Wonderware Historian, Fully On-PremArchitecture for a private AI assistant on AVEVA System Platform and Wonderware Historian: SQL views, Galaxy areas, read-only access, local GPUs, audit log.
- How to Add AI to a Self-Hosted Ignition Gateway Without CloudPrivate AI for self-hosted Ignition: Tag Historian tables, alarm journal, Named Queries, WebDev, role mapping, local GPUs and an audit trail. No cloud needed.
- How to add AI to GE Proficy (Historian and Plant Applications) on-premHow to add a private AI assistant to GE Proficy Historian and Plant Applications on-prem: read-only access, retrieval, local models, audit and rollout.