1: Fleet HMI rollout across similar machines
Scenario: You have multiple similar assets, like lines, skids, cells or sites, and want a consistent human-machine interface (HMI) operator experience and a predictable update model.
A container-based approach offers consistency by launching the runtime application in a standardized container context, and repeatability by using documented container launch parameters such as port publishing, container naming and optional restart behavior. If you need the runtime application to keep files or settings it creates, connect the container to a real folder on the computer. That way the data stays even if the container is restarted or replaced.
2: Side-by-side modular edge services
Scenario: You want visualization at the edge and may also want adjacent capabilities deployed alongside it (for example, FactoryTalk® Remote Access™ Runtime).
Containers make it possible to deploy multiple components side by side on a host while keeping them packaged independently. And the FactoryTalk Optix container run guidance provides the concrete mechanism for running the Optix runtime application in Docker as the visualization component within the deployments.
In a composable edge architecture, it’s also advantageous to run remote connectivity services alongside the visualization runtime. For example, FactoryTalk® Remote Access™ Runtime is available as a Docker image, enabling it to be deployed as a separate container next to a FactoryTalk Optix runtime container (or alongside another complementary containerized service on the same host). This is a natural fit for container hosts because containers are designed to run adjacent to each other on the same machine while maintaining process isolation.
3: Cloud deployments
Scenario: Some organizations also extend this container approach into cloud-hosted environments when they want a centrally managed runtime footprint, standardized rollout mechanics or easier alignment with cloud-essential operations.
In these scenarios, the same core containerized software principle applies. An Optix runtime can be packaged and operated as a containerized workload, while the underlying compute is provided by the customer’s cloud infrastructure and governed by their IT policies and security posture.
This fits naturally alongside the Optix cloud-enabled workflows: FactoryTalk® Optix Studio™ Pro supports cloud-hosted collaboration and repository-based development. And Rockwell Automation describes remote deployment patterns that leverage FactoryTalk Remote Access, reducing the need to be physically on-site to deliver updates.
FactoryTalk Optix containerized deployment considerations
Third‑party boundary
For those just starting with containerized software, please refer to the third‑party provider, such as Docker or Portainer, for assistance and licensing terms.
Licensing behavior
If you do not provide an entitlement license key, the FactoryTalk Optix application stops running after 120 minutes. More information can be found in the FactoryTalk Optix help.
Port publishing ties back to application configuration
When Optix runs in a container, choose a port on the host PC and “forward” it to the port Optix uses for its web client. That inside port is the Web Presentation Engine port you set in FactoryTalk® Optix Studio™.
Persistence should be intentional
Decide up front what should be saved versus what can be temporary. The volume binding option exists to persist changes made at runtime by writing runtime changes to a local folder on the host machine, so changes aren’t lost when the container restarts or is replaced.
Repeatability is first, everything else is second
The practical value of deploying FactoryTalk Optix with containerized software is repeatability.
Software containers offer a consistent, documented way to run the same runtime application across environments using standard container launch concepts like port publishing, restart behavior and (when needed) volume mapping for persistence. This supports the broader containerization goal of reducing environment drift and improving consistency from development to production across information technology and operation technology.
Want to take the next step? Explore how ThinManager® software and FactoryTalk Optix relate in the broader containerization conversation, without changing the fundamentals described. And you can dig deeper into the entire portfolio of FactoryTalk Optix portfolio cloud-based software and hardware devices here.
