Rockwell Automation PlantPAx Reference Manual

Reference Manual

Original Instructions

PlantPAx Distributed Control System

System Release 4.6

IMPORTANT This manual applies to PlantPAx System Release 4.5/4.6.

For PlantPAx System Release 5.0, see PROCES-UM100.

Important User Information

Read this document and the documents listed in the additional resources section about installation, configuration, and operation of this equipment before you install, configure, operate, or maintain this product. Users are required to familiarize themselves with installation and wiring instructions in addition to requirements of all applicable codes, laws, and standards.

Activities including installation, adjustments, putting into service, use, assembly, disassembly, and maintenance are required to be carried out by suitably trained personnel in accordance with applicable code of practice.

If this equipment is used in a manner not specified by the manufacturer, the protection provided by the equipment may be impaired.

In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages resulting from the use or application of this equipment.

The examples and diagrams in this manual are included solely for illustrative purposes. Because of the many variables and requirements associated with any particular installation, Rockwell Automation, Inc. cannot assume responsibility or liability for actual use based on the examples and diagrams.

No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits, equipment, or software described in this manual.

Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell Automation, Inc., is prohibited

Throughout this manual, when necessary, we use notes to make you aware of safety considerations.

WARNING: Identifies information about practices or circumstances that can cause an explosion in a hazardous environment, which may lead to personal injury or death, property damage, or economic loss.

ATTENTION: Identifies information about practices or circumstances that can lead to personal injury or death, property damage, or economic loss. Attentions help you identify a hazard, avoid a hazard, and recognize the consequence.

IMPORTANT Identifies information that is critical for successful application and understanding of the product.

Labels may also be on or inside the equipment to provide specific precautions.

SHOCK HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that dangerous voltage may be present.

BURN HAZARD: Labels may be on or inside the equipment, for example, a drive or motor, to alert people that surfaces may reach dangerous temperatures.

ARC FLASH HAZARD: Labels may be on or inside the equipment, for example, a motor control center, to alert people to potential Arc Flash. Arc Flash will cause severe injury or death. Wear proper Personal Protective Equipment (PPE). Follow ALL Regulatory requirements for safe work practices and for Personal Protective Equipment (PPE).

Table of Contents

Preface

Purpose of the Reference Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

Summary of Changes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

Additional Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8

	Chapter 1
System Architecture Overview	Architecture Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	14
	System Elements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	14
	Critical System Attributes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	15
	System Procurement Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	16
	Chapter 2
System Element	PlantPAx Software Components . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	17
Recommendations	Process Automation System Server (PASS) . . . . . . . . . . . . . . . . . . . . . .	18
	PASS Server Redundancy . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	19
	Configure the FactoryTalk Directory . . . . . . . . . . . . . . . . . . . . . . .	20
	Engineering Workstation (EWS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	20
	Engineering Workstation Application Server (AppServ-EWS) . . . .	21
	Operator Workstation (OWS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	21
	Operator Workstation Application Server (AppServ-OWS) . . . . . .	22
	Independent Workstation (IndWS) . . . . . . . . . . . . . . . . . . . . . . . . . . . .	23
	AppServ-Info (Historian). . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	24
	AppServ-Info (VantagePoint) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	24
	AppServ-Info (SQL) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	25
	Asset Management Server (AppServ-Asset). . . . . . . . . . . . . . . . . . . . . .	25
	Batch Management Server (AppServ-Batch). . . . . . . . . . . . . . . . . . . . .	26
	Domain Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	27
	Controller Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	28
	Simplex Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	28
	Redundant Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	29
	Skid-based Controller. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	30
	Determining I/O Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	31
	Sizing Control Strategies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	32

Rockwell Automation Publication PROCES-RM001M-EN-P - June 2019

3

Table of Contents

System Application

Recommendations

Alarm System

Recommendations

Infrastructure

Recommendations

Chapter 3

Controller Recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

Task Configuration and CPU Utilization . . . . . . . . . . . . . . . . . . . 38

Estimate Controller CPU Utilization . . . . . . . . . . . . . . . . . . . . . . . 40

Use of Program Parameters. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43

Tag and Memory Allocation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44

Controller-to-Controller Communication . . . . . . . . . . . . . . . . . . 47

Controller I/O Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48

Using Add-On Instructions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51

FactoryTalk View Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

Rockwell Automation Library of Process Objects. . . . . . . . . . . . . . . . 53

Additional Application Resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54

Chapter 4

FactoryTalk Alarm and Event Software . . . . . . . . . . . . . . . . . . . . . 55 Using the Library of Process Objects for Alarms. . . . . . . . . . . . . . 59 Alarm State Model . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60 Monitoring Your Alarm System . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

Chapter 5

Physical Access Control. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Infrastructure Types. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Traditional . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Virtual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 66

Virtual PlantPAx Configuration Recommendations . . . . . . . . . . . . . 67

Servers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Storage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Virtual Networks. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

Resource Pool Allocation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

Operating System Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Domains and Workgroups . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Domain Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72

Windows Workgroup Recommendations . . . . . . . . . . . . . . . . . . . 73

Server and Workstation Time Synchronization . . . . . . . . . . . . . . 73

Operating System Optimization . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

Network Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75

Ethernet Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76

4	Rockwell Automation Publication PROCES-RM001M-EN-P - June 2019

Table of Contents

Field Device Integration

Recommendations

Chapter 6

Device Configuration Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

FactoryTalk AssetCentre for Enterprise Solution . . . . . . . . . . . . 78

EtherNet/IP Recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78

EtherNet/IP I/O Communication Options . . . . . . . . . . . . . . . . . 79

ControlNet Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80

ControlNet I/O Communication Options . . . . . . . . . . . . . . . . . . 80

DeviceNet Recommendations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

DeviceNet Communication Options. . . . . . . . . . . . . . . . . . . . . . . . 81

HART Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

HART Communication Options . . . . . . . . . . . . . . . . . . . . . . . . . . . 82

FOUNDATION Fieldbus Recommendations . . . . . . . . . . . . . . . . . . 83

FOUNDATION Fieldbus Communication Options . . . . . . . . 83

PROFIBUS PA Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85

PROFIBUS PA Communication Options. . . . . . . . . . . . . . . . . . . 85

Motor Control Recommendations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87

BatchManagementandControl

Recommendations

Information Management

Recommendations

Chapter 7

FactoryTalk Batch Critical System Attributes . . . . . . . . . . . . . . . . . . . 90 Batch Guidelines for Logix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90 Using a Redundant System with a FactoryTalk Batch Server . . . . . . 91

Chapter 8

FactoryTalk Historian Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93

Tips and Best Practices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Architectural Best Practices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

FactoryTalk VantagePoint Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Tips and Best Practices. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

Rockwell Automation Publication PROCES-RM001M-EN-P - June 2019

5

Table of Contents

Maintenance

Recommendations

Chapter 9

PlantPAx System Backup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Host Machine. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96

Virtual Image Disaster Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96 Hypervisor Management Applications . . . . . . . . . . . . . . . . . . . . . . 97

Application Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 97

Controller Project File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98 FactoryTalk Directory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

PASS Servers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

Network Switches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99 Data Back up and Restore. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100

Historian Configuration and Data . . . . . . . . . . . . . . . . . . . . . . . . . 100

Batch Configuration and Data. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 AssetCentre Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

SQL Server Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101 Backup Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102 Retention Considerations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102

System Storage Rates. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104

Security Audit Logs. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105 Microsoft Updates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

Use Antivirus Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Software Patches and Firmware Updates . . . . . . . . . . . . . . . . . . . . . . . 106 Use Proactive Industrial Security Advisory Index. . . . . . . . . . . . 106

Verify Software Patches . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106

Compare Latest Firmware Updates . . . . . . . . . . . . . . . . . . . . . . . . 107 Considerations for Software and Firmware Upgrades . . . . . . . . 107

Rockwell Automation Services and Support . . . . . . . . . . . . . . . . . . . . 108

	Appendix A
Verify and Monitor Your System	Additional Monitoring Resources. . . . . . . . . . . . . . . . . . . . . . . . . .	109
Health
	Appendix B
System Software Components	. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	111
	Glossary
	. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	115
	Index
	. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .	119

6	Rockwell Automation Publication PROCES-RM001M-EN-P - June 2019

Preface

The PlantPAx® system provides a modern approach to distributed control. The system shares common technology (Integrated Architecture® system) with all other automation disciplines in the plant. This approach creates a seamless information flow across the plant for optimization opportunities and enables a Connected Enterprise.

Our scalable platform provides you with the flexibility to implement a system appropriate for your application. Figure 1 shows the documents (this manual in the highlighted section) that are available to help design and implement your system requirements.

Figure 1 - PlantPAx System Implementation and Documentation Strategy

Define and		Install		Prep		Develop		Operate
Procure

• Selection Guide	• Virtualization User Manual	•	Infrastructure User Manual	•	Application User Manual	•	Verify and Troubleshoot User Manual
PROCES-SG001	9528-UM001		PROCES-UM001		PROCES-UM003		PROCES-UM004
		•	Reference Manual	•	Reference Manual	•	Reference Manual
			PROCES-RM001		PROCES-RM001		PROCES-RM001

• Library of Process Objects PROCES-RM002 PROCES-RM013 PROCES-RM014

•Define and Procure - Helps you understand the elements of the PlantPAx system to make sure that you buy the proper components.

•Install - Provides direction on how to install the PlantPAx system.

•Prep - Provides guidance on how to get started and learn the best practices to follow before you develop your application.

•Develop - Describes the actions and libraries necessary to construct your application that resides on the PlantPAx system.

•Operate – Provides guidance on how to verify and maintain your systems for efficient operation of your plant.

Purpose of the Reference Manual

The PlantPAx Reference Manual builds on the Selection Guide, which specifies system sizing guidelines and catalog numbers for procurement. This manual elaborates on the system sizing and application rules that you need to follow to configure a PlantPAx system.

Rockwell Automation Publication PROCES-RM001M-EN-P - June 2019

7

Preface

Summary of Changes

We strongly recommend that you use the PlantPAx virtual image templates and Rockwell Automation® Library of Process Objects for best system performance and functionality. If you are not able to use the templates or the library, you still must follow the guidelines and rules from the Selection Guide and this Reference Manual. These guide posts make sure that you achieve PlantPAx system performance.

The PlantPAx system utilizes a set of Critical System Attributes (CSAs) as performance metrics. Your system performance can meet the CSA metrics if you follow the sizing guidelines and application rules that are defined in these documents and the PlantPAx System Estimator (PSE).

This manual contains new and updated information as indicated in the following table.

Topic	Page
120 OWS clients available in distributed architecture	14
Updates characterized software releases	17
Adds hard disk size for virtual system elements	19, 20, 21, 22,
	24, 25, 26, 27
Updates software components of system elements	111

Additional Resources

These documents contain additional information concerning related products from Rockwell Automation.

Table 1 - System Core Resources

Resource	Description
PlantPAx Distributed Control System Selection Guide,	Provides basic definitions of system elements and sizing guidelines for procuring a PlantPAx system.
publication PROCES-SG001
PlantPAx Distributed Control System Infrastructure	Provides screen facsimiles and step-by-step procedures to configure infrastructure components for your
Configuration User Manual, publication PROCES-UM001	system requirements.
PlantPAx Distributed Control System Application	Provides the steps necessary to start development of your PlantPAx Distributed Control System.
Configuration User Manual, publication PROCES-UM003
PlantPAx Distributed Control System Verification and	Provides checklist worksheets to verify and document that your system design aligns with PlantPAx
Troubleshooting User Manual, publication PROCES-UM004	system recommendations.
Rockwell Automation Library of Process Objects,	Provides information on how to use the Rockwell Automation Library of Process Objects.
publication PROCES-RM002
Rockwell Automation Library of Logix Diagnostic Objects,	Provides Add-On Instructions for monitoring and diagnostic information of Logix controllers.
publication PROCES-RM003
Rockwell Automation Library of Steam Table Instructions,	Provides Add-On Instructions for calculating temperature and pressure steam tables.
publication PROCES-RM004
Rockwell Automation Library of Process Objects: Logic	Provides controller codes and tags for Rockwell Automation Library objects. The objects are grouped by family and
Instructions Reference Manual,	attached as Microsoft Excel® files to the manual PDF file.
publication PROCES-RM013
Rockwell Automation Library of Process Objects: Display	Provides common display elements for the Rockwell Automation Library. For improved accessibility, the elements are
Elements Reference Manual,	combined into one manual.
publication PROCES-RM014

8	Rockwell Automation Publication PROCES-RM001M-EN-P - June 2019

	Preface
Table 1 - System Core Resources
Resource	Description
PlantPAx Hardware Specifications and Certifications,	Provides information on PlantPAx system hardware specifications and certifications.
publication PROCES-SR027
PlantPAx Sequencer Object Reference Manual,	Provides a flexible controller-based step sequencing solution that reduces engineering time by automating common
publication PROCES-RM006	operator procedures.
FactoryTalk® View SE Edition User Manual,	Provides details on how to use this software package for developing HMI applications that can involve multiple users
publication VIEWSE-UM006	and servers, which are distributed over a network.
FactoryTalk View SE Installation Guide,	Contains procedures for installing FactoryTalk View SE software.
publication VIEWSE-IN003
FactoryTalk Alarms and Events System Configuration Guide,	Provides details on how to install, configure, and use FactoryTalk Alarms and Events services as part of a
publication FTAE-RM001	FactoryTalk-enabled automation system.
ControlLogix® System User Manual,	Explains how to use traditional and extreme environment ControlLogix controllers.
publication 1756-UM001
ControlLogix Enhanced Redundancy System User Manual,	Provides information on the installation and configuration for an enhanced redundancy controller system for
publication 1756-UM535	greater availability.
Logix5000™ Controllers Design Considerations Reference	Details how to design and optimize Logix5000 controller applications.
Manual, publication 1756-RM094
Logix5000 Controllers Common Procedures Programming	Provides links to a collection of programming manuals that describe how you can use procedures that are common to all
Manual, Publication 1756-PM001	Logix5000 controller projects.
Logix5000 Controllers General Instructions Reference	Provides programming controller applications by using relay ladder instructions.
Manual, publication 1756-RM003
Logix5000 Controllers Advanced Process Control and Drives	Provides details on process control and drives instructions.
Instructions Reference Manual, publication 1756-RM006
Logix 5000 Controllers Execution Time and Memory Use	Provides a complete list of instruction execution time and memory usage information for Logix5000 controllers in your
Reference Manual, publication 1756-RM087	Studio 5000 Logix Designer® programming software.
PlantPAx Logix Batch and Sequence Manager Reference	Explains a controller-based batch and sequencing solution that leverages the Logix Control Platform and
Manual, publication PROCES-RM007	FactoryTalk View software for integrated control and visualization.
Table 2 - Infrastructure Resources
Resource	Description
PlantPAx Virtualization User Manual,	Describes how to use the PlantPAx virtual image templates for configuring virtual machines.
publication 9528-UM001
EtherNet/IP Network Configuration,	Explains Logix5000 tools that are used in EtherNet/IP topologies and network operation.
publication ENET-UM001
Ethernet Design Considerations Reference Manual,	Explains the infrastructure components that allow this open network to communicate seamlessly throughout a plant,
publication ENET-RM002	from shop floor to top floor.
Converged Plantwide Ethernet (CPwE) Design and	Provides collaborative design guidelines that are based on the Cisco Ethernet-to-the-Factory solution and the Rockwell
Implementation Guide, publication ENET-TD001	Automation Integration Architecture solution.
Troubleshoot EtherNet/IP Networks,	Provides guidelines for troubleshooting an EtherNet/IP network, such as setting speed and duplex.
publication ENET-AT003
1756 ControlLogix Communication Modules Specifications	Contains specifications for the ControlLogix network communication modules.
Technical Data, publication 1756-TD003
Application Note: Segmentation Methods within the	Provides design considerations of network segmentation methodologies for the ControlLogix and
Cell/Area Zone, publication ENET-AT004	CompactLogix™ 5370 controllers.
Stratix® Managed Switches User Manual,	Describes the embedded software features and tools for configuring and managing the Stratix 5410, Stratix 5400, and
publication 1783-UM007	the Stratix 5700 Ethernet managed switches.
Stratix Ethernet Device Specifications Technical Data,	Provides switch specifications, certifications, and the latest product information.
publication 1783-TD001
Stratix/Infrastructure Product Family Quick Reference	Illustration that shows options for connecting your plant network by using standard Ethernet technology.
Drawing, publication IASIMP-QR029

Rockwell Automation Publication PROCES-RM001M-EN-P - June 2019

9

Preface

Table 2 - Infrastructure Resources

Resource	Description
ControlNet Coax Media Planning and Installation Guide,	Provides procedures for planning, installing, and implementing a ControlNet network.
publication CNET-IN002
ControlNet Fiber Media Planning and Installation Guide,
publication CNET-IN001
ControlNet Modules in Logix5000 Control Systems User
Manual, publication CNET-UM001
Product Compatibility and Download Center at	Website helps you find product-related downloads including firmware, release notes, associated software, drivers, tools
http://www.rockwellautomation.com/	and utilities.
rockwellautomation/support/pcdc.page

Table 3 - Field Device Integration Resources

Resource	Description
FactoryTalk AssetCentre Installation Guide,	Provides installation instructions for monitoring your factory automation system.
publication FTAC-IN005
FactoryTalk AssetCentre Product Profile,	Explains this tool for securing, managing, versioning, tracking, and reporting automation-related asset information
publication FTALK-PP001	across your entire enterprise.
EtherNet/IP and ControlNet to FOUNDATION Fieldbus	Describes the installation and operation of the 1788-EN2FFR and 1788-CN2FFR linking devices.
Linking Device, publication 1788-UM057
1788-EN2PAR User Manual, publication 1788-UM056	Describes the installation and operation of the 1788-EN2PAR linking device.
1788-CN2PAR User Manual, publication 1788-UM055	Describes the installation and operation of the 1788-CN2PAR linking device.
ControlLogix HART Analog I/O Modules User Manual,	Contains information on how to install, configure, and troubleshoot ControlLogix HART
publication 1756-UM533	analog I/O modules.
Promass 83 Flowmeter via PROFIBUS PA to the PlantPAx	Provides procedures for the design and implementation of PROFIBUS PA equipment.
Process Automation System, publication PROCES-AP022
DeviceNet System Quick Reference,	Provides procedures for configuring applications on the DeviceNet® network.
publication DNET-QR001
CENTERLINE® Motor Control Centers with EtherNet/IP,	Describes cable system construction and components that are associated with an EtherNet/IP network that is factory-
publication 2100-TD031	installed in CENTERLINE 2100 and CENTERLINE 2500 and IntelliCENTER® motor control centers (MCCs).
CENTERLINE 2500 Motor Control Centers with EtherNet/IP
Network, publication 2500-TD003
Integrate E+H Instruments in a PlantPAx System	Provides a step-by-step approach to integrating HART devices from Endress+Hauser into the PlantPAx system.
Integration Document, publication PROCES-SG003

Table 4 - Batch Resources

Resource	Description
FactoryTalk Batch User's Guide, publication BATCH-UM011	Provides a complement of FactoryTalk recipe management, component guidelines, and software installation
	procedures.
FactoryTalk Batch Installation Guide,	Provides information and procedures for installing FactoryTalk Batch software.
publication BATCH-IN002
PlantPAx Batch Design Considerations Reference Manual,	Provides guidance on selected batch implementation topics in a PlantPAx system.
publication PROCES-RM008
Batch Application Toolkit Quick Start,	Provides a framework for how to use the tasks to complete the components of the Toolkit.
publication IASIMP-QS042
PhaseManager™ User Manual, publication LOGIX-UM001	Explains how to define a state model for your equipment and develop equipment phases.

10	Rockwell Automation Publication PROCES-RM001M-EN-P - June 2019

Preface

Table 5 - Process Safety Resources

Resource	Description
Using ControlLogix in SIL 2 Applications Safety Reference	ControlLogix components that are supported in SIL 2 configurations.
Manual, publication 1756-RM001
Redundant I/O System User Manual	Describes how to install and configure the 1715 Redundant I/O system with a ControlLogix Enhanced
publication 1715-UM001	Redundancy System.
AADvance Solutions Handbook, publication ICSTT-RM447	Explains the features, performance, and functionality of the AADvance controller and systems. It sets out some
	guidelines on how to specify a system to meet your application requirements.
AADvance System Build Manual, publication ICSTT-RM448	Provides experienced panel builders with information on how to assemble a system, switch on and validate the
	operation of a controller.
AADvance Configuration Guide, publication ICSTT-RM405	Defines how to configure an AADvance controller by using the AADvance Workbench to meet your Safety Instrument
	Function (SIF) application requirements.
AADvance Safety Manual, publication ICSTT-RM446	Defines mandatory standards and makes recommendations to safely apply AADvance controllers for a SIF application.
	Explains how to use traditional and extreme environment ControlLogix controllers.
AADvance Troubleshooting and Repair Manual, publication	Provides plant maintenance personnel with information on how to trace and repair a fault in an AADvance system and
ICSTT-RM406	perform routine maintenance tasks.

You can view or download publications at http://www.rockwellautomation.com/literature. To order paper copies of technical documentation, contact your local Allen-Bradley distributor or Rockwell Automation sales representative.

Rockwell Automation Publication PROCES-RM001M-EN-P - June 2019

11

Preface

Notes:

12	Rockwell Automation Publication PROCES-RM001M-EN-P - June 2019

Chapter 1

System Architecture Overview

The PlantPAx® system uses standard Rockwell Automation® Integrated Architecture® (IA) products to build a distributed control system (DCS). Our modern DCS is scalable, flexible, and open while still providing the reliability, functionality, and performance expected from a DCS.

This section describes the system elements and architectures that you can use to configure a PlantPAx system.

Topic	Page
Architecture Classes	14
System Elements	14
Critical System Attributes	15
System Procurement Tools	16

Rockwell Automation characterizes a DCS based on its size or architecture class. A ‘characterized’ classification yields system performance data and recommended hardware and software configurations.

EWS	PASS	Domain	Application Servers	Multiple OWS
		Controller

Device Level Ring Topology

Rockwell Automation Publication PROCES-RM001M-EN-P - June 2019

13

Chapter 1 System Architecture Overview

Architecture Classes

Architecture classes define reference architectures that are based on the size of the required system.

Architecture	Description
Skid	Skid architecture with a skid controller and PanelView™ for monitoring data.
Station	A single station that acts as a PlantPAx Automation System Server (PASS), Operator Workstation (OWS), and
	Engineering Workstation (EWS).
Distributed - Single server	This architecture has a single PASS server and supports multiple OWSs and EWSs.
Distributed - Multiple servers	This architecture has multiple PASS servers and supports multiple OWSs and EWSs. You can add servers for more capacity or to
	segregate servers by operating areas.

			le
		b
	la
ca
S

Distributed ArchitectureMultiple PASS Servers

Distributed ArchitectureSingle PASS Server

Skid Controller

Station Architecture

System Elements

System elements are the different elements of a PlantPAx DCS. Elements can be deployed on your system depending on the needs of the application.

Table 6 - Architectures and System Elements

System	Skid Architecture	Station Architecture	Distributed Architecture		Distributed Architecture
Element			(single PASS (consolidated))		(single to multiple PASS servers)
PASS	Not applicable.	Single workstation serves as PASS, EWS,	For smaller systems, one PASS		One PASS required and includes one or
		and OWS in an independent workstation	(consolidated) is required that typically		more of the following:
			includes the following:		•	FactoryTalk Directory server
			•	FactoryTalk® Directory server	•	HMI server
			•	HMI server	•	Data server
			•	Data server	• Alarm and Event Server
			• Alarm and Event Server		Additional PASS as needed (up to 10
			The PASS-C supports functions that		servers or redundant server pairs).(1)
			otherwise are hosted on application
			servers. The PASS-C single computer
			includes the following in a single
			workstation:
			•	PASS
			•	FactoryTalk Historian
			• AppServ-Asset Management
			•	AppServ-VantagePoint
			• AppServ-Info (SQL)
			IMPORTANT: An additional PASS-C is
			required for redundancy.
EWS		Included in independent workstation	1 EWS required.		1 EWS required.
					Can have as many as 5 EWSs.

14	Rockwell Automation Publication PROCES-RM001M-EN-P - June 2019

System Architecture Overview Chapter 1

Table 6 - Architectures and System Elements

System	Skid Architecture	Station Architecture	Distributed Architecture	Distributed Architecture
Element			(single PASS (consolidated))	(single to multiple PASS servers)
OWS	Not applicable. Operator	Included in independent workstation	Included in PASS-C.	Can have as many as 120 OWS clients.(1)
	interface typically		An .ISO file is available for any single,
	accomplished with PanelView
			physical computer.
	Plus operator terminal or thin
			IMPORTANT: PASS-C supports up to
	client connected to a
	distributed architecture.		10 clients.
Controllers	CompactLogix controller.	1...5 ControlLogix® controllers.	1...5 ControlLogix controllers.	There is no hard limit for the number of
			IMPORTANT: PASS-C supports up to five	controllers. The number of controllers
				that can be supported per PASS (data
			redundant controllers.
				server) depends on controller selection,
			Use the PlantPAx System Estimator to
				controller loading, and number of OWS.
			verify your design. See page 16.
Application	Not applicable. In chassis	AppServ-Asset Management as needed.	Additional servers can be added as your	AppServ-Asset Management as needed.
servers	historian and in controller	AppServ-Batch as needed.	system scales. For example,	AppServ-Batch as needed.
	batch capabilities are available.	AppServ-Information Management (SQL,	AppServ-Batch, AppServ-Information	AppServ-Information Management (SQL,
	Can also be integrated with a		Management.
		Historian, or VantagePoint®) as needed.		Historian, or VantagePoint) as needed
	distributed architecture.		IMPORTANT: An additional PASS-C is
				AppServ-OWS as needed.
			required for redundancy.

(1)These values are product maximum limits. It’s possible that achieving these limits on your system is not feasible based on your system design. Use the PlantPAx System Estimator to make sure that your system is sized properly (see page 16).

Critical System Attributes	A critical system attribute (CSA) is a visible performance indicator of a
	system-wide characteristic. CSAs are used to define or identify specified levels of
	system operation:
	•	Determine system limits
	•	Establish system rules
	•	Establish system recommendations
	• Measure system element and system infrastructure performance
	The following CSAs are used to verify performance during process
	system characterization.
Table 7 - CSA Performance Indicators
Critical System Attribute(1)	Performance
Display callup (paint time)	A noncached display is called up by the operator and ready for operator use within 2 seconds.
Display update	The display updates control information within 1 second.
Steady state alarm time	Steady state alarms occurring at 20 per second are timestamped within 1 second.
Alarm burst time	All alarms in a burst of 1000 alarms are timestamped within 3 seconds.
Recovery	A system element returns to full operation within 5 minutes of the restoration after a failure or loss.
Operator-initiated control	Operator-initiated actions are loaded into the controller and the feedback for the operator action is within 2 seconds.
Batch server: operator action time	An operator batch command has been acted on by the controller in 1 second.
Batch server: server action time	A server batch command has been acted on by the controller in 1 second.
Batch server: controller action time	Batch status events display on the operator workstation within 1 second.

(1)CSA performance indicators are a nominal performance number. The actual system performance can intermittently deviate from the documented CSA due to system disturbances that can introduce variability in the network or operating system performance.

Rockwell Automation Publication PROCES-RM001M-EN-P - June 2019

15

Chapter 1 System Architecture Overview

System Procurement Tools	The following chapters of this manual contain recommendations and
	considerations for how to implement your system. If you have not selected or
	procured your PlantPAx system architecture and components, see the
	PlantPAx Selection Guide, publication PROCES-SG001, for more information.
	The PlantPAx System Estimator (PSE), which is a part of the Integrated
	Architecture® Builder (IAB) software tool, helps you define a PlantPAx system.
	The PSE wizard lets you specify your system architecture that is based on your
	requirements, and verifies that your process control hardware is sized properly.
	When the verification is complete, you can transfer the output of the PSE wizard
	into the IAB tool to develop a bill-of-material for the system based on
	your inputs.
	See http://www.rockwellautomation.com/en/e-tools/configuration.html to
	access the IAB tool.

16	Rockwell Automation Publication PROCES-RM001M-EN-P - June 2019

Chapter 2

PlantPAx Software

Components

System Element Recommendations

PlantPAx® system elements refer to the individual servers, clients, and controllers that comprise a PlantPAx system. This chapter describes each system element and its components. A base installation of all server and workstation elements is available as virtual appliances.

The following table lists where to find specific information.

Topic	Page
PlantPAx Software Components	17
Process Automation System Server (PASS)	18
Engineering Workstation (EWS) and Application Server (AppServ-EWS)	20
Operator Workstation (OWS) and Application Server (AppServ-OWS)	21
Independent Workstation (IndWS)	23
AppServ-Info (Historian)	24
AppServ-Info (VantagePoint)	24
AppServ-Info (SQL)	25
Asset Management Server (AppServ-Asset)	25
Batch Management Server (AppServ-Batch)	26
Domain Controller	27
Controller Characteristics	28

Integrated Architecture® software components and versions that comprise the PlantPAx system, include the following:

•Studio 5000 Logix Designer® application, version 31.x

•Studio 5000 Architect™ application, version 4.x

•FactoryTalk® View software, version 11.x

•FactoryTalk Batch software, version 13.x

•FactoryTalk AssetCentre software, version 9.x

•FactoryTalk® VantagePoint® software, version 8.x

•FactoryTalk Historian software, version 6.x

Performance guidelines are based on the use of the software versions listed.

For the latest compatible software information and to download associated library tools, see the Product Compatibility and Download Center at http:// www.rockwellautomation.com/rockwellautomation/support/pcdc.page.

Rockwell Automation Publication PROCES-RM001M-EN-P - June 2019

17

Chapter 2 System Element Recommendations

Process Automation System

Server (PASS)

The Process Automation System Server (PASS) is a required system element that hosts essential software components to run the system. The essential software components include the data server, HMI server, and alarm server. The PASS can be used as a data, HMI, and/or alarm server.

Software Components	Description
FactoryTalk Network Directory (FTD) server(1)	Secures information from multiple Rockwell Automation® software components across multiple computers and
	provides central administration throughout the PlantPAx system. Application components, such as display and security
	settings, can be stored in their original environments and made available to the entire PlantPAx system without the
	need for duplication.
FactoryTalk Activation server(1)	The FactoryTalk Activation server is part of the FactoryTalk Services Platform. The server allows FactoryTalk-enabled
	software products to be activated via files generated by Rockwell Automation over the Internet. This server essentially
	manages the files that are required to license Rockwell Automation products on the PlantPAx system.
FactoryTalk View HMI server	The human machine interface (HMI) server is configured within your FactoryTalk View Site Edition (SE) application. The
	HMI server stores HMI project components, such as graphic displays, and serves these components to OWSs upon
	request. The HMI server also can manage tag databases and log historical data. Multiple HMI servers can exist on the
	PlantPAx system. Each HMI server must be on a separate PASS.
FactoryTalk View Data server	The Data server component provides access to information from the process controllers to servers and workstations on
	the PlantPAx system. FactoryTalk View software supports two types of data servers: Rockwell Automation Device
	servers (FactoryTalk Linx software) and OPC Data servers. The Data server that is mentioned in PlantPAx documentation
	generally refers to the Rockwell Automation Device servers. Data servers are configured within your FactoryTalk View
	SE application. Multiple data servers can exist on the PlantPAx system.
FactoryTalk View Alarm and Event server	The Alarm and Event server publishes information from controllers and servers available to all subscribing OWSs. Alarm
	and Event servers are configured within your FactoryTalk View SE application. There are two types of Alarm and Event
	servers: device-based and server-based. Device-based Alarm and Event servers are configured as an option to the data
	server. Server-based Alarm and Event servers are configured as a separate component. Each server-based Alarm and
	Event server must be on a separate PASS.
	The Alarm and Event server that is mentioned in PlantPAx documentation refers to the Alarm and Event server that is
	server-based. See Alarm System Recommendations on page 55 for more information.
Optional
FactoryTalk Batch client software	If a Batch Application server is being used on the system, FactoryTalk Batch client components are required to support
	replication of batch-related objects on the displays to the OWS.

(1) In redundant PASS configurations, this component is included on the primary PASS only.

18	Rockwell Automation Publication PROCES-RM001M-EN-P - June 2019

System Element Recommendations	Chapter 2

PASS Server Redundancy

PASS servers can be configured as redundant for the following software components:

•HMI server

•Data server

•Alarm server

IMPORTANT When you enable redundancy in FactoryTalk View Studio software, select the option to ‘Continue using the secondary server even when the primary server becomes available again’to avoid excessive switchovers. This option lets you manage replication of application changes made before or after the switchover occurs. We recommend that you configure your HMI displays to indicate when the system is running without backup.

The FactoryTalk Directory server information is cached on each computer that is participating in a distributed application. If the FTD server computer is disconnected from the network or fails, the OWS, EWS, and other application servers can continue to access everything within the application. This functionality applies as long as the computer has already accessed the FTD server.

Table 8.1 - PASS Virtual Requirements

Category	Requirement(1)
Virtual infrastructure	Required:
	•	4 vCPU
	• 8 GB vRAM min
	•	60 GB vHardDisk
	Recommended CPU and memory allocation:
	• High priority Resource pool(2)
Operating system	Windows Server 2016 operating system, 64 bit

(1)All numbers and figures are referenced for initial sizing only. The values can be adjusted for system performance if needed.

(2)See Resource Pool Allocation on page 69.

Table 8.2 - PASS Traditional Requirements

Category	Requirement
Traditional infrastructure	The PASS must be installed on server-class hardware. The following are sample specifications that are based on PlantPAx
	system characterization:
	• Intel Xeon Multicore processor (4 cores or greater)
	• 2.40 GHz CPU min
	• 8 GB RAM min
	• Ethernet card that supports redundant media if NIC-teaming is used (If you plan to use a motherboard-NIC make sure
	that it supports redundant media)
PASS - C (for small and medium systems)	For systems with fewer than 2000 I/O points, the PASS - Consolidated contains HMI, data collection, decision-making,
	and asset management servers. These combined tools form a basic PlantPAx system in a single server, referred to|
	as consolidated.
	The PASS must be installed on server-class hardware. The following are sample specifications based on PlantPAx
	system characterization:
	• Intel® Xeon E-31270 v5
	• 3.60 GHz CPU min
	• 32 GB RAM min
	• Ethernet card that supports redundant media if NIC-teaming is used (If you plan to use a motherboard-NIC make sure
	it supports redundant media)
Operating system	Windows Server 2016 operating system, 64 bit

Rockwell Automation Publication PROCES-RM001M-EN-P - June 2019

19

Chapter 2 System Element Recommendations

Configure the FactoryTalk Directory

Before starting a project, you must install FactoryTalk Directory (FTD) services on the computer that is hosting the FTD or the PASS. The FTD server manages applications that can exist on multiple clients and servers on separate computers on the PlantPAx system.

IMPORTANT To configure the FTD, see the PlantPAx Distributed Control System

Infrastructure Configuration User Manual, publication PROCES-UM001.

Engineering Workstation (EWS)

The EWS supports system configuration, application development, and maintenance functions. This workstation is the central location for monitoring and maintaining the system operation.

If a batch application server is used, the FactoryTalk Batch client and editor components are required to configure the FactoryTalk Batch system and configure the FactoryTalk objects on the displays.

Table 9.1 - EWS Virtual Requirements

Category	Requirement(1)
Virtual infrastructure	Required:
	•	2 vCPU
	• 4 GB vRAM min
	•	100 GB vHardDisk
	Recommended CPU and memory allocation:
	• Normal priority Resource pool(2)
Operating system	Windows 10 operating system, 64 bit

(1)All numbers and figures are referenced for initial sizing only. The values can be adjusted for system performance if needed.

(2)See Resource Pool Allocation on page 69

Table 9.2 - EWS Traditional Requirements

Category	Requirement
Traditional infrastructure	The EWS must be installed on workstation-class hardware. The following are sample specifications based on PlantPAx
	system characterization.
	• Intel Core 2 Duo
	• 2.40 GHz CPU min
	• 4 GB RAM min
	• Ethernet card that supports redundant media if NIC-teaming is used (If you plan to use a motherboard-NIC make
	sure that it supports redundant media)
Operating system	Windows 10 operating system, 64 bit

20	Rockwell Automation Publication PROCES-RM001M-EN-P - June 2019

System Element Recommendations	Chapter 2

Engineering Workstation Application Server (AppServ-EWS)

Table 10 - AppServ-EWS Virtual Requirements

The AppServ-EWS uses Microsoft® Remote Desktop Services (RDS) technology to serve multiple instances of the EWS as thin clients from a single server. Thin clients can run applications and process data on a remote computer. The recommended limit is five RDS client connections per AppServ-EWS.

Category	Requirement(1)
Virtual infrastructure	Required:
	•	4 vCPU
	• 8 GB vRAM min
	•	100 GB vHardDisk
	Recommended CPU and memory allocation:
	• Normal priority Resource pool(2)
Thin client	We recommend a maximum of 5 FactoryTalk View SE clients per application server
Operating system	Windows Server 2016 operating system, 64 bit
(1) All numbers and figures are referenced for initial sizing only. The values can be adjusted for system performance if needed.
(2) See Resource Pool Allocation on page 69

Operator Workstation (OWS)		The operator workstation (OWS) provides the graphical view and interface into
		the process. The OWS supports operator interaction and is not meant to support
		development or maintenance activities, although these activities are possible if
		desired.
		FactoryTalk View Site Edition (SE) client software must be installed on the
		OWS. The OWS also can contain clients for non-core application servers, such
		as FactoryTalk Batch, FactoryTalk Historian, or FactoryTalk AssetCentre.
Table 11.1 - OWS Virtual Requirements
Category		Requirement(1)
Virtual infrastructure		Required:
		• 2 vCPU
		• 4 GB vRAM min
		• 40 GB vHardDisk
		Recommended CPU and memory allocation:
		• High priority Resource pool(2)
Operating system		Windows 10 operating system, 64 bit

(1)All numbers and figures are referenced for initial sizing only. The values can be adjusted for system performance if needed.

(2)See Resource Pool Allocation on page 69

Table 11.2 - OWS Traditional Requirements

Category	Requirement
Traditional infrastructure	The OWS must be installed on workstation-class hardware. The following are sample specifications based on PlantPAx
	system characterization:
	• Intel Core 2 Duo
	• 2.40 GHz CPU min
	• 4 GB RAM min
	• Ethernet card that supports redundant media if NIC-teaming is used (If you plan to use a motherboard-NIC make
	sure that it supports redundant media)
Operating system	Windows 10 operating system, 64 bit

Rockwell Automation Publication PROCES-RM001M-EN-P - June 2019

21

Chapter 2 System Element Recommendations

Operator Workstation Application Server (AppServ-OWS)

Table 12 - AppServ-OWS Virtual Requirements

The AppServ-OWS uses Microsoft Remote Desktop Services (RDS) technology to serve multiple instances of the OWS as thin clients from a single server. Thin clients can run applications and process data on a remote computer. The recommended limit is 10 RDS connections per AppServ-OWS.

Category	Requirement(1)
Virtual infrastructure	Required:
	•	8 vCPU
	• 16 GB vRAM min
	•	60 GB vHardDisk
	Recommended CPU and memory allocation:
	• High priority Resource pool(2)
Thin client	We recommend a maximum of 10 FactoryTalk View SE clients per application server
Operating system	Windows Server 2016 operating system, 64 bit

(1) All numbers and figures are referenced for initial sizing only. The values can be adjusted for system performance if needed.

(2) See Resource Pool Allocation on page 69

ThinManager Server Options

Deliver multiple sessions to multiple monitors and customized virtual screens on a single thin client.

Deliver applications based on what is assigned to the terminal or user.

The AppServ-OWS system element virtual image template is pre-configured with Remote Desktop Services (RDS). RDS includes the ThinManager® Server installation file. You can configure the AppServ-OWS as your ThinManager Server and deploy up to 10 OWS sessions to simplify the management of all devices and users.

ThinManager increases your productivity, visualization, mobility, and security from one easy-to-use, centralized, and scalable management platform.

ThinManager

Access feeds from USB and IP cameras.

Remote Desktop Servers

Virtual Resources

Manage and deliver virtual desktops while running PCs

as a thin client.

Deliver content to the right person at the right time and place.

Get mobile access to applications specific to a user’s role.

22	Rockwell Automation Publication PROCES-RM001M-EN-P - June 2019

System Element Recommendations	Chapter 2

Independent Workstation (IndWS)

Table 13 - IndWS Traditional Requirements

Safely and securely deliver your content to any combination of device, user, and location with the following features:

•Boost productivity by reducing the time that is spent to manage computers

•Enhance visualization by delivering your content to where you need it and the way you want the content shown

•Extend security through encrypted communications, active directory, and secure thin clients

•Smart mobility where QR codes, Bluetooth, Wi-Fi, and GPS make sure that devices receive content in authorized areas

For more information, contact your Rockwell Automation representative.

The independent workstation (IndWS) combines the roles of the PASS, EWS, and OWS in one computer. This workstation can be used as a ‘shadow system’ for emergency purposes.

Category	Requirement
Traditional infrastructure	The IndWS must be installed on workstation-class hardware. The following are sample specifications based on
	PlantPAx system characterization:
	• Intel Multicore processor (4 cores or greater)
	• 2.40 GHz CPU min
	• 8 GB RAM min
	• Ethernet card that supports redundant media if NIC-teaming is used (If you plan to use a motherboard-NIC make
	sure that it supports redundant media)
Operating system	Windows 10 operating system, 64 bit

Rockwell Automation Publication PROCES-RM001M-EN-P - June 2019

23

Chapter 2 System Element Recommendations

AppServ-Info (Historian)

The Information Management server can include a historian application to collect, manage, and analyze data.

Table 14.1 - AppServ-Info (Historian) Virtual Requirements

Category	Requirement(1)
Virtual infrastructure	Required:
	•	2 vCPU
	• 4 GB vRAM min
	•	120 GB vHardDisk
	Recommended CPU and memory allocation:
	• Normal priority Resource pool(2)
Operating system	Windows Server 2016 operating system, 64 bit(3)

(1)All numbers and figures are referenced for initial sizing only. The values can be adjusted for system performance if needed.

(2)See Resource Pool Allocation on page 69

(3)To install FactoryTalk View SE Historian software, version 4.6, with Windows Server 2016, you must install a patch from the Product Compatibility and Download Center at http://www.rockwellautomation.com/rockwellautomation/support/pcdc.page.

Table 14.2 - AppServ-Info (Historian) Traditional Requirements

Category	Requirement
Traditional infrastructure	The Information Management server must be installed on server-class hardware:
	• Intel Xeon Multicore processor (4 cores or greater)
	• 2.40 GHz CPU min
	• 4 GB RAM min
	• Ethernet card that supports redundant media if NIC-teaming is used (If you plan to use a motherboard-NIC make
	sure that it supports redundant media)
Operating system	Windows Server 2016 operating system, 64 bit

AppServ-Info (VantagePoint)	The Information Management server can be used as a decision support tool by
	installing VantagePoint software.
Table 15.1 - AppServ-Info (VantagePoint) Virtual Requirements
Category	Requirement(1)
Virtual infrastructure	Required:
	• 2 vCPU
	• 4 GB vRAM min
	• 60 GB vHardDisk
	Recommended CPU and memory allocation:
	• Normal priority Resource pool(2)
Operating system	Windows Server 2016 operating system, 64 bit

(1)All numbers and figures are referenced for initial sizing only. The values can be adjusted for system performance if needed.

(2)See Resource Pool Allocation on page 69.

Table 15.2 - AppServ-Info (VantagePoint) Traditional Requirements

Category	Requirement
Traditional infrastructure	The Information Management server must be installed on server-class hardware:
	• Intel Xeon Multicore processor (4 cores or greater)
	• 2.40 GHz CPU min
	• 4 GB RAM min
	• Ethernet card that supports redundant media if NIC-teaming is used (If you plan to use a motherboard-NIC make
	sure that it supports redundant media)
Operating system	Windows Server 2016 operating system, 64 bit

24	Rockwell Automation Publication PROCES-RM001M-EN-P - June 2019

System Element Recommendations	Chapter 2

AppServ-Info (SQL)

An SQL server can be configured with the Information Management server. Software such as FactoryTalk AssetCentre, FactoryTalk VantagePoint, and FactoryTalk Batch use an SQL database to store and access process data. Additionally, the FactoryTalk Alarm and Event server uses an SQL database to store information.

Table 16.1 - AppServ-Info (SQL) Virtual Requirements

Category	Requirement(1)
Virtual infrastructure	Required:
	•	2 vCPU
	• 4 GB vRAM min
	•	120 GB vHardDisk
	Recommended CPU and memory allocation:
	• Normal priority Resource pool(2)
Operating system	Windows Server 2016 operating system, 64 bit

(1)All numbers and figures are referenced for initial sizing only. The values can be adjusted for system performance if needed.

(2)See Resource Pool Allocation on page 69.

Table 16.2 - AppServ-Info (SQL) Traditional Requirements

Category	Requirement
Traditional infrastructure	The Information Management server must be installed on server-class hardware:
	• Intel Xeon Multicore processor (4 cores or greater)
	• 2.40 GHz CPU min
	• 4 GB RAM min
	• Ethernet card that supports redundant media if NIC-teaming is used (If you plan to use a motherboard-NIC make
	sure that it supports redundant media)
Operating system	Windows Server 2016 operating system, 64 bit

Asset Management Server (AppServ-Asset)

An asset management server (AppServ-Asset) is an extension to the PlantPAx system that adds maintenance and plant operations to the system. This server provides the following to improve resource availability:

•Disaster recovery controller data

•Diagnostics

•Calibration

•Real-time monitoring

•Auditing equipment

•Network health

Table 17.1 - AppServ-Asset Virtual Requirements

Category	Requirement(1)
Virtual infrastructure	Required:
	•	2 vCPU
	• 4 GB vRAM min
	•	60 GB vHardDisk
	Recommended CPU and memory allocation:
	• Normal priority Resource pool(2)
Operating system	Windows Server 2016 operating system, 64 bit

(1)All numbers and figures are referenced for initial sizing only. The values can be adjusted for system performance if needed.

(2)See Resource Pool Allocation on page 69

Rockwell Automation Publication PROCES-RM001M-EN-P - June 2019

25

Chapter 2 System Element Recommendations

Table 17.2 - AppServ-Asset Traditional Requirements

Category	Requirement
Traditional infrastructure	The Information Management server must be installed on server-class hardware:
	• Intel Xeon Multicore processor (4 cores or greater)
	• 2.40 GHz CPU min
	• 4 GB RAM min
	• Ethernet card that supports redundant media if NIC-teaming is used (If you plan to use a motherboard-NIC make
	sure that it supports redundant media)
Operating system	Windows Server 2016 operating system, 64 bit

Batch Management Server (AppServ-Batch)

The batch management server (AppServ-Batch) offers comprehensive batch management, including recipe management, procedural control of automated and manual processes, and material management.

Table 18.1 - AppServ-Batch Virtual Requirements

Category	Requirement(1)
Virtual infrastructure	Required:
	•	2 vCPU
	• 4 GB vRAM min
	•	60 GB vHardDisk
	Recommended CPU and memory allocation:
	• Normal priority Resource pool(2)
Operating system	Windows Server 2016 operating system, 64 bit

(1)All numbers and figures are referenced for initial sizing only. The values can be adjusted for system performance if needed.

(2)See Resource Pool Allocation on page 69

Table 18.2 - AppServ-Batch Traditional Requirements

Category	Requirement
Traditional infrastructure	The Information Management server must be installed on server-class hardware:
	• Intel Xeon Multicore processor (4 cores or greater)
	• 2.40 GHz CPU min
	• 4 GB RAM min
	• Ethernet card that supports redundant media if NIC-teaming is used (If you plan to use a motherboard-NIC make
	sure that it supports redundant media)
Operating system	Windows Server 2016 operating system, 64 bit

26	Rockwell Automation Publication PROCES-RM001M-EN-P - June 2019

System Element Recommendations	Chapter 2

Domain Controller

A domain controller is a server that responds to security authentication requests (log in, verify permissions, and so forth) within the Windows server domain. A domain grants you access to a number of network resources (such as applications and printers) with the use of a single user name and password combination. PlantPAx uses a domain controller to store user account information, authenticate users, and enforce security policies.

Domain authentication is recommended, whether it’s an existing domain or a new one. Follow these guidelines for the domain controller:

•Domain controllers are required if there are 10 or more workstations or servers.

•The domain controllers are separate computers. Do not load any application software on a domain controller. Load all system application software on the other computers, such as the PASS, application server, OWS, and EWS.

•Microsoft support does not recommend applications to be run on a domain controller, and certainly not applications that require more than Authenticated User privileges to run.

•The domain controllers must be local to the system workstations and servers (within the local firewall) and not remote to the system.

Table 19.1 - Domain Virtual Requirements

Category	Requirement(1)
Virtual infrastructure	Required:
	•	1 vCPU
	• 4 GB vRAM min
	•	40 GB vHardDisk
	Recommended CPU and memory allocation:
	• Low priority Resource pool(2)
Operating system	Windows Server 2016 operating system, 64 bit

(1)All numbers and figures are referenced for initial sizing only. The values can be adjusted for system performance if needed.

(2)See Resource Pool Allocation on page 69.

Table 20 - Domain Traditional Requirements

Category	Requirement
Traditional infrastructure(1)	The Information Management server must be installed on server-class hardware:
	• Intel Xeon Multicore processor (4 cores or greater)
	• 2.40 GHz CPU min
	• 4 GB RAM min
	• Ethernet card that supports redundant media if NIC-teaming is used (If you plan to use a motherboard-NIC make
	sure that it supports redundant media)
Operating system	Windows Server 2016 operating system, 64 bit

(1) A Microsoft Excel software license is required.

For redundancy purposes, we recommend that you use at least two domain controllers in the domain. These domain controllers replicate automatically to provide high availability and an online configuration backup.

Rockwell Automation Publication PROCES-RM001M-EN-P - June 2019

27

Chapter 2 System Element Recommendations

Controller Characteristics	This section describes the components and sizing attributes for simplex,
	skid-based, and redundant controllers.
	Simplex Controller
	Non-redundant controllers are referred to as simplex controllers.
Table 21 - Simplex Controller Hardware Requirements(1)
Category	Cat. No.
Process controller (2)	ControlLogix® 1756-L71, 1756-L72, 1756-L73, or 1756-L74, or 1756-L75 controller
EtherNet/IP interface	• For direct DLR connection: 1756-EN2TR
	• For direct PRP connection: 1756-EN2TP
	• For secure connections: 1756-EN2TSC
	• Otherwise: 1756-EN2T, 1756-EN2F (no DLR support)
	• For converting topology or media: 1783-ETAP, 1783-ETAP1F, 1783-ETAP2F (supports DLR topology)
ControlNet interface (if applicable)	• 1756-CN2, 1756-CN2R

•1756-CNB, 1756-CNBR

(1)If environmental conditions warrant, you can use an extreme temperature controller, for example, the 1756-L74XT. Conformal coated options are also available for protection from harsh environments that can contain moisture and or chemical contaminants.

(2)As the PlantPAx system release 4.6 uses controller firmware revision 31, implementation requires use of the 1756-L7x controller family. PlantPAx system release 4.6 can co-exist with older generation controllers.

Table 22 - Simplex ControlLogix Controller Sizing

Category(1)	1756-L71	1756-L72	1756-L73	1756-L74	1756-L75(2)
User memory	2 MB	4 MB	8 MB	16 MB	32 MB
Total I/O recommended, max	375	750	1500	2250	2250
Recommended control strategies, max(3)	60	125	250	450	450
Total control strategies @ 250 ms, max	60	125	250	250	250
Total control strategies @ 500 ms, max	60	125	250	450	450
Tags/sec delivered to data server, max	10,000	20,000	20,000	20,000	20,000

(1)These values are recommended maximum limits. It’s possible that achieving all of these values in a single controller is not doable. For more detailed sizing, you can use the PSE (see page 16).

(2)The advantages to using the 1756-L75 controller is to maintain common spare parts with redundant systems or if you are doing some memory intensive storage not accounted for in the sizing model.

(3)Recommended maximum control strategies are based on all controller strategies being simple regulatory control. See Controller I/O Considerations on page 48.

28	Rockwell Automation Publication PROCES-RM001M-EN-P - June 2019

System Element Recommendations	Chapter 2

Redundant Controllers

ControlLogix controllers support redundancy on ControlNet and EtherNet/IP networks. In a redundant controller system on PlantPAx, you need these components:

•Two 1756 chassis each set up the same with the following:

–Number of slots

–Modules in the same slots

–Redundancy firmware revisions in each module

–Two additional ControlNet or Ethernet nodes outside the redundant chassis pair

•One 1756-RM2 module per chassis with fiber media

Table 23 - Redundant Controller Hardware Requirements(1)

Category	Cat. No.
Process controller	ControlLogix 1756-L73, 1756-L74, or 1756-L75 controller
Redundancy module	1756-RM2(2)
Ethernet interface	• For direct DLR connection: 1756-EN2TR
	• For direct PRP connection: 1756-EN2TP
	• For secure connections: 1756-EN2TSC
	• Otherwise: 1756-EN2T, 1756-EN2F (no DLR support)
	• For converting topology or media: 1783-ETAP, 1783-ETAP1F, 1783-ETAP2F (supports DLR topology)
ControlNet interface (if applicable)	• 1756-CN2, 1756-CN2R

•1756-CNB, 1756-CNBR

(1)If environmental conditions warrant, you can use an extreme temperature controller, for example, the 1756-L74XT. Conformal coated options are also available for protection from harsh environments that can contain moisture and or chemical contaminants.

(2)The PlantPAx system recommendation is to use only one redundant controller in a chassis with a 1756-RM2 redundancy module. While a 1756-RM2 module can support two controllers, the resulting performance of each controller is not easily predicted.

Make sure that each redundant controller has enough memory to store twice the amount of controller data and I/O memory to support program modifications. The increased memory usage in a redundant controller provides for a bumpless transfer during a switchover and makes sure the secondary Logix controller has the same values in its output image as the primary Logix controller. The extra memory helps prevent a switchover to a secondary controller with a mixture of old and new data memory.

When using the PlantPAx System Estimator, the PSE accounts for additional memory requirements required for redundancy as memory used.

Table 24 - Redundant ControlLogix Controller Sizing

Category(1)	1756-L73	1756-L74	1756-L75(3)
User memory	8 MB	16 MB	32 MB
Total I/O recommended, max	750	1500	2250
Recommended control strategies, max(2)	125	250	450
Total control strategies @ 250 ms, max	120	120	120
Total control strategies @ 500 ms, max	125	220	220
Tags/sec delivered to data server, max	20,000	20,000	20,000

(1)These values are recommended maximum limits. It’s possible that achieving all of these values in a single controller is not doable. For more detailed sizing, you can use the PSE (see page 16).

(2)Recommended maximum control strategies are based on all controller strategies being simple regulatory control. See Controller I/O Considerations on page 48.

(3)The advantages to using the 1756-L75 controller is to maintain common spare parts with redundant systems or if you are doing some memory intensive storage not accounted for in the sizing model.

Rockwell Automation Publication PROCES-RM001M-EN-P - June 2019

29

Chapter 2 System Element Recommendations

Skid-based Controller

The PlantPAx process automation system is a complete, scalable system, from single controller to a fully distributed set of equipment. You can easily integrate skid-based equipment into the overall system.

The CompactLogix™ controller platform offers a solution for skid-based equipment to be part of the overall PlantPAx system if the application requires the following:

•Control of multiple loops for temperature, pressure, flow, or level

•Operating as a subsystem with sequencing and automation

•Controlled as part of the overall process, accepting reference inputs, and delivering process variables to a supervisory controller

IMPORTANT

.

Table 25 - Skid-based Controller Sizing

Be aware of memory usage within the CompactLogix family when using Library objects. See the PlantPAx Distributed Control System Application Configuration User Manual, publication PROCES-UM003, for guidance of how to configure controllers with the Library of Process Objects.

Category(1)	CompactLogix	CompactLogix	CompactLogix	CompactLogix
	1769 -L24ER-QBFC1B	1769-L19ER-BB1	1769-L33ER	1769-L36ERM
User memory	0.75 MB	1.0 MB	2.0 MB	3.0 MB
Total I/O recommended, max	80	125	250	350
Recommended control strategies, max(2)	10	15	30	45
Total control strategies @ 250 ms, max	10	15	30	45
Total control strategies @ 500 ms, max	10	3000	30	45
Tags/sec delivered to data server, max	3000	3000	3000	3000

(1)These values are recommended maximum limits. To achieve all of these values in a single controller is likely not feasible. For more detailed sizing, you can use the PSE (see page 16).

(2)Maximum controller strategy is based on all controller strategies being simple regulatory control. See Controller I/O Considerations on page 48.

30	Rockwell Automation Publication PROCES-RM001M-EN-P - June 2019