What is FactoryTalk?

FactoryTalk is Rockwell Automationโ€™s family of industrial software products for visualisation, data collection, configuration management and production control, all running on a shared foundation called the FactoryTalk Services Platform. The brand covers, among others, the HMI and SCADA software FactoryTalk View, the newer visualisation platform FactoryTalk Optix, the FactoryTalk Historian historian and the FactoryTalk AssetCentre management tool. FactoryTalk is the software layer above Allen-Bradley controllers and is widespread in North America and in European plants running Rockwell control systems.


๐Ÿง  What is the FactoryTalk Services Platform?

During the 2000s Rockwell gradually consolidated its software onto a single platform. RSView Enterprise, with its Machine Edition and Site Edition variants, has been called FactoryTalk View since version 5.0, and other โ€œRSโ€ products were rebranded too: RSLinx Enterprise, for instance, became FactoryTalk Linx. The RSLogix 5000 programming software, by contrast, continued as Studio 5000. The common foundation is the FactoryTalk Services Platform (FTSP), which every FactoryTalk product installs. It provides shared services:

  • FactoryTalk Directory โ€” a single project structure holding applications, areas and data definitions, either as a local directory (one computer) or a network directory (shared across the network)
  • FactoryTalk Security โ€” users, groups and permissions in one place, optionally linked to Active Directory
  • FactoryTalk Live Data โ€” real-time exchange of tag values between products
  • FactoryTalk Alarms and Events โ€” shared alarming from controllers and servers
  • FactoryTalk Audit โ€” records who changed what and when
  • FactoryTalk Activation โ€” the licensing mechanism for all products

Because every product uses the same directory and security model, you do not have to redefine users and tags for each application.


๐Ÿ”ง Which FactoryTalk products are there?

Product Function Notes
FactoryTalk View SE HMI/SCADA Site Edition, as a local station or a distributed client-server application
FactoryTalk View ME Machine HMI Machine Edition, runtime on PanelView Plus terminals
FactoryTalk Optix Modern HMI Based on ASEM software (acquired in 2020), with OPC UA and browser-based design
FactoryTalk Historian Historian Built on OSIsoft PI technology, now part of AVEVA
FactoryTalk AssetCentre Configuration management Backups, version control and audit log for controller programs
FactoryTalk Linx Communications Data server for Allen-Bradley controllers, formerly RSLinx Enterprise
FactoryTalk Design Studio Cloud engineering Browser-based Logix programming with generative AI (Copilot)
FactoryTalk Hub SaaS portal Design Hub, Operations Hub and Maintenance Hub, hosted on Microsoft Azure
FactoryTalk ProductionCentre / Plex MES Traditional MES and the cloud MES Plex, acquired in 2021 for about USD 2.2 billion

FactoryTalk Optix is the youngest visualisation product. In April 2020 Rockwell acquired the Italian company ASEM, including a flexible HMI platform and remote access software. That became FactoryTalk Optix, announced in 2022 as part of FactoryTalk Design Hub and, since late 2023, also sold with dedicated OptixPanel terminals. Optix supports third-party devices alongside Rockwell controllers.


๐Ÿ”„ How does FactoryTalk relate to Studio 5000 and Logix?

Studio 5000 Logix Designer is the programming environment for the Logix controllers, ControlLogix and CompactLogix. FactoryTalk is the layer above: FactoryTalk Linx reads the tags from the controller over IP and the underlying CIP protocol, after which FactoryTalk View displays them and FactoryTalk Historian stores them. Because FactoryTalk browses tag names directly from the Logix project, you do not need to maintain a separate tag database. Studio 5000 itself also relies on FactoryTalk Activation and FactoryTalk Security, for example to control who may edit a controller online. FactoryTalk Design Studio is the cloud-native engineering environment Rockwell is developing alongside Studio 5000, with built-in version control and browser-based collaboration.


๐Ÿ” How does security work in FactoryTalk?

FactoryTalk Security is built on authentication (who are you?) and authorisation (what may you do?). Permissions are granted to users and groups, ideally synchronised with Windows or Active Directory groups. A key feature is area-based security: you divide an application into areas, and everything in an area (displays, tags, alarms) inherits that areaโ€™s permissions unless you override them for an individual object. An operator on line 1 can then view line 2 without being able to operate it.

FactoryTalk software regularly features in advisories from the US agency CISA:

Advisory Product Vulnerability Remedy
ICSA-24-030-06 (2024) FactoryTalk Services Platform CVE-2024-21917, CVSS 9.8: service tokens reusable without authentication Version 6.40 or later
ICSA-24-226-06 (2024) FactoryTalk View SE 13.0 CVE-2024-7513, CVSS 8.8: overly broad folder permissions, code run with elevated rights Tighten folder permissions (remove the INTERACTIVE group)
ICSA-25-028-04 (2025) FactoryTalk View SE before v15.0 CVE-2025-24481 and -24482: exposed debugger port and DLL execution Version 15.0 or patch
ICSA-25-252-04 (2025) FactoryTalk Optix 1.5.0โ€“1.5.7 CVE-2025-9161, CVSS 7.1: code execution through the MQTT broker Version 1.6.0 or later

Rockwell publishes every advisory in its Trust Center. Track that list in your patch process, because FactoryTalk servers often run unchanged for years.


๐Ÿ› ๏ธ How do you build a FactoryTalk architecture for a plant?

A typical FactoryTalk View SE installation for a medium-sized plant looks like this, step by step:

  1. Plan the network โ€” place controllers, HMI servers and clients in separate zones according to network segmentation and IEC 62443; FactoryTalk servers belong at levels 2โ€“3 of the Purdue model and must never be directly reachable from the office network.
  2. Set up the FactoryTalk Directory โ€” a single network directory server, preferably redundant, as the central source for applications and security.
  3. Configure FactoryTalk Linx โ€” as a data server per area, with a redundant pair for critical lines.
  4. Install HMI servers and clients โ€” FactoryTalk View SE servers hosting alarms and displays, with operator stations as thin clients.
  5. Connect the historian โ€” FactoryTalk Historian SE reads through Live Data and discovers controllers automatically.
  6. Centralise licensing โ€” an activation server with concurrent licences that clients borrow over the network.
  7. Define security โ€” user groups from Active Directory, permissions per area, auditing switched on.
  8. Control changes โ€” FactoryTalk AssetCentre takes scheduled backups of controllers and HMI projects, compares them with the approved version and so supports change management.

For devices from other vendors, add an OPC server such as Kepware, which passes tags from, for example, Siemens or Modbus equipment on to FactoryTalk.


โš–๏ธ How does FactoryTalk compare with WinCC, AVEVA and Ignition?

Feature FactoryTalk View SE WinCC (Siemens) AVEVA System Platform Ignition
Native controller Allen-Bradley Logix Siemens S7 Vendor-neutral Vendor-neutral
Engineering View Studio, Design Studio TIA Portal IDE with object templates Designer (Java)
Licensing model Per server, client and display Per tag package and client Per I/O count and client Per server, unlimited tags and clients
Historian FactoryTalk Historian (PI) WinCC Archive / Process Historian AVEVA Historian / PI Tag Historian (SQL)
Strengths Discrete manufacturing, US market European machine building Process and multi-site industry Fast roll-out, web, MQTT

In practice the choice often follows the controller brand: an Allen-Bradley plant leans towards FactoryTalk, a Siemens plant towards WinCC.


โ“ Frequently asked questions

Is FactoryTalk the same as FactoryTalk View?

No, FactoryTalk is the name of Rockwell Automationโ€™s entire software family, whereas FactoryTalk View is only its HMI and SCADA product. Besides FactoryTalk View, the FactoryTalk brand includes FactoryTalk Historian, FactoryTalk AssetCentre, FactoryTalk Linx and FactoryTalk Optix, among others.

What is the difference between FactoryTalk View SE and ME?

FactoryTalk View ME (Machine Edition) is intended for single-machine HMIs and runs on PanelView Plus terminals. FactoryTalk View SE (Site Edition) is the SCADA variant for a whole site, either as a single station or as a distributed application with multiple servers and clients.

Will FactoryTalk Optix replace FactoryTalk View?

Rockwell positions FactoryTalk Optix as a modern, open, web-based visualisation platform, but FactoryTalk View is still developed and supported. For new projects with multi-vendor equipment or cloud engineering, FactoryTalk Optix is often the logical choice, while existing FactoryTalk View installations usually remain in service.

How does licensing work in FactoryTalk?

FactoryTalk uses FactoryTalk Activation, based on FlexNet technology and managed with FactoryTalk Activation Manager. You choose between node-locked activations, tied to one computer, and concurrent activations that clients borrow over the network from an activation server.

Is FactoryTalk Historian the same as the PI historian?

FactoryTalk Historian is built on licensed PI technology from OSIsoft, which AVEVA acquired in 2021. FactoryTalk Historian adds integration with the FactoryTalk Services Platform and automatic discovery of Allen-Bradley controllers on top of that core.

How do you secure FactoryTalk?

You secure FactoryTalk by placing its servers in a segmented OT network, linking FactoryTalk Security to Active Directory with permissions per area, and actively patching against CISA and Rockwell advisories. You should also tighten Windows permissions on HMI servers and use FactoryTalk AssetCentre for backups and change detection.


๐Ÿ“Œ In summary

FactoryTalk is Rockwell Automationโ€™s software layer above Allen-Bradley controllers: one platform with a shared directory, security and licensing for HMI, SCADA, historian, configuration management and MES. Organisations using FactoryTalk benefit from tight integration with Logix, but must segment, patch and manage the platform as seriously as any other critical OT component.