Optix Runtime with Base Token Package (M)
The following example shows a system architecture that uses an HMI and two clients.
System Architecture - Base Package M
The example architecture has the following components.
- Single HMI runtime with typical HMI functionality and, one native client and one web client
- Communicates with multipleRockwell Automation®controllers and multiple third-party controllers
- Logs data to an internal 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 | |||
Native HMI client | 1 | - | |
Web HMI Client - 1 connection | 1 | - | |
Features | |||
Alarms | 1 | - | |
Recipe | 1 | - | |
Runtime retentivity | 1 | - | |
Data logger | 1 | - | |
Embedded database | 0 | - | |
Extended database - 1 connection | 1 | - | |
Controller Connections | |||
Rockwell Automation®
EtherNet/IP™ - 2 connections | 2 | - | |
Third-party drivers - 2 connections | 2 | - | |
Total: | 11 | 0 | |
Base token package (M), which includes 11 base tokens, is recommended for this example. There
is no need for an extended package. Use the Device Sizing tool to select the best deployment
option for your application.
For this configuration, you can select one of the following deployment options.
- Optix Runtime base token package (M) + consider bundling with ASEM 6300 Industrial Computers
- OptixPanel™Standard
Provide Feedback