Optix Runtime with Base Token Package (L) and Extended Token
Package (XXS)
The following example shows a system architecture that uses an HMI with high availability
and five web clients.
System Architecture - With High Availability
The example architecture has the following components.
- An HMI application with typical HMI functionality, high availability, and five web clients
- Communicates with multipleRockwell Automation®controllers and multiple third-party controllers
- Acts as a client to other OPC UA servers
- Logs data to an external database
- Requires event logging, alarming, recipe, and basic PDF reporting
The following table shows example runtime sizing for a package that includes the
application components.
Selection | Base Token Value | Extended Token Value | |
|---|---|---|---|
Clients | |||
Web HMI Client - 5 connections | 3 | - | |
Features | |||
Alarms | 1 | - | |
Recipe | 1 | - | |
Event logger | 1 | - | |
Basic reporting | 1 | - | |
Runtime retentivity | 1 | - | |
Data logger | 1 | - | |
External database | 1 | - | |
Controller Connections | |||
Rockwell Automation®
EtherNet/IP™ - 4 connections | 2 | - | |
Third-party drivers - 2 connections | 2 | - | |
Interoperability | |||
OPC UA Client - 1 connection | 1 | - | |
High Availability | |||
Three-node HA cluster | - | 3 | |
Total: | 15 | 3 | |
Base token package (L), which includes 15 base tokens, plus extended token package (XXS),
which includes three extended tokens, are recommended for this example. Use the Device Sizing tool to select the best
deployment option for your application.
For this configuration, you can select the following deployment option.
- Optix Runtime base token package (L) + Optix Runtime extended token package (XXS) + consider bundling with ASEM 6300 Industrial Computers
Provide Feedback