Fdocuments - in Factorytalk System Design Considerations

FactoryTalk® System Design Considerations
PUBLIC INFORMATION
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.

Agenda
High Level discussion of the main considerations you should make when building a system:
Basic ControlLogixTM Considerations
Basic Network Considerations
Basic Host Considerations
FactoryTalk Services Platform
Data Servers
FactoryTalk View Site Edition (SE)
FactoryTalk Historian SE
FactoryTalk AssetCentre
FactoryTalk VantagePoint
Basic Microsoft SQL Server Considerations
Thin Client Connectivity
Virtualization Basics
Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved. 2
Basic ControlLogix Considerations
PUBLIC INFORMATION

ControlLogix Considerations
ControlLogix in a FactoryTalk System
Retrieving data from a ControlLogix is dependent on the processor’s
resources, as well as the FactoryTalk System configurations.
 Controller • Tasks
– Continuous
 Options – Periodic
 Modules – Priorities
• Scan Time
 Memory – Time Slice
 Available & Used – Its effect on overall software
performance – wire frames
 Tag management (arrays & UDTs)
• Redundancy
 Connections
• Data Server Load Balancing
 Data Servers
 Messages • Physical Limits
Continuous Task vs Periodic Task
 Only one continuous task per controller

 Use is not required
 Operates at the lowest priority
 Shares time with processor overhead, including
communications
 Uses CPUtask
Improper time configuration
only after other tasks
couldexecute
prevent the controller from
communicating with a data server!
 Periodic tasks execute automatically on pre-configured
intervals
 Configurable for 1ms or higher
 After execution, task suspends and waits for trigger
 Not affected by System Overhead Timeslice

For more information on…
 RSTechED 2014
 Studio 5000® and Logix Basics Lab
 Studio 5000 and Logix Advanced Lab
 Collecting Data Efficiently in the Integrated Architecture
 Rockwell Automation Literature Library

 ControlLogix System Selection Guide
 Logix5000 Controllers Design Considerations
Required reading!

Basic Networking Considerations
PUBLIC INFORMATION

Networking Considerations
Components
A network is only as good as the selected hardware!
 What type of networking

components will be used? FactoryTalk Applications
• View
Manufacturing Zone
Level 3
• VantagePoint Layer 3
 Firewalls •
•
Historian
AssetCentre
Router
 Switches Layer 3
Switch Stack
 Routers Network Services
• DNS, DHCP, syslog server
• Network and security management
 Wireless Level 0–2 Cell/Area Zone
 Cable types/lengths
Layer 2 Switch HMI
Controller
Drive HMI
 What type of networking Controller

Drive Drive
services will be used?

HMI Distributed I/O
Controller Distributed I/O
Cell/Area #1 Cell/Area #2 Cell/Area #3 (Bus
(Redundant Star Topology) (Ring Topology) Topology)
 Domain vs Workgroup
 DNS, DHCP

Network Components: Firewalls
 The most important aspect of a firewall is that it is at the entry/exit point of the networked
system it protects – not within it!
 A firewall is designed to ‘block’ network traffic on one segment of a network from reaching
another.
FactoryTalk
 The opening of ports within a firewall may Server
present a security concern, and an IT Security

expert will need to be involved in the configuration. Firewall
FactoryTalk
Client
 Aid 29402 - TCP ports used by Rockwell products

 Many other components (such as DCOM and MS authentication services) assign
ports at runtime (dynamic).
 Use thin client services to go through a Firewall for application connectivity

Wireless & WAN Connections
 Occasionally wireless or 3rd party networks (T1, DSL, etc) are implemented
in a control environment – for instance, to communicate with remote sites.
 Wireless networks are prone to signal interference,

leading to breaks in communications, therefore avoid
use with FactoryTalk thick clients or direct data
server to controller connections.
 FactoryTalk applications require network speeds of >= 10Mbps. (test labs

are 100Mbps)
 Ensure thick FactoryTalk clients are on the same network segment as the server(s).
 Remote clients are possible using thin client services.
 Controllers at remote locations should be configured to use a data concentrator,
which needs to be located on the same network segment as the data server(s).

Sample Architecture:
Networks
Internet
Firewall
Managed Ethernet Switch for Control System Network (CSN) – HMI/Ctrl Communications
CLx CLx Flex Flex

CLx CLx
SLC SLC
PLC PLC
Engineering
Workstation
• RSLogix™ 5/500/5000
• RSLinx® Classic

Windows Networking:
Workgroups vs Domains
 Workgroups are supported in architectures of less than 10 FactoryTalk
Computers, otherwise a Windows domain is required.
 Common Requirements
 Unique IP Address
 Centralized environment can allow for DHCP with server reservations
 Unique Host Names
 Centralized environment can allow for DNS
 Differences
 User name authentication – Workgroups require special configuration
 Security – Domains allow for Active Directory user linking

Domain Controllers
Internet
Firewall
Domain
Controllers
•For the Ctl Sys Domain
•W2K3 Server O/S
•DNS/DHCP/WINS
CLx CLx Flex Flex

CLx CLx
SLC SLC
PLC PLC
Engineering
Workstation
• RSLogix 5/500/5000
PLC
Networking Considerations
 Consider contacting Rockwell Automation Network Services group.
 RSTechED 2014
 Ethernet/IP Layer 3 Networking Capabilities
 Understand and Implement High Availability Methods
 Design Considerations for Robust Ethernet/IP Networks
 Rockwell Automation Knowledgebase

 AID 24380: Ethernet/IP, Switches, and Multicast Frames
 AID 34532: Troubleshooting TCP/IP connectivity using a TCP/IP diagram
 AID 29402: TCP/UDP Ports used by Rockwell Automation products
 Literature Library
 Ethernet Design Considerations Reference Manual

PUBLIC INFORMATION

Sizing
HOST = computer or virtual machine hosting an operating system upon
which applications may be installed.
 “Minimum” hardware is not designed to give the best performance
 Use “recommended” or greater specifications wherever possible
 Server-class hardware is not always required
 40% steady-state processor utilization as a general baseline

 Note Windows OS 2GB process memory cap – more resources are not always the
solution.
 Consider future expansion / support when purchasing hardware

 How easily can hardware be expanded or converted (e.g., to Virtual environments)
 Thin client hardware can simplify hardware costs (both purchase and maintenance)

Basic Host Considerations:
Operating Systems
 Windows Operating Systems
 In general, Windows 8 and Windows Server 2012 support is still forthcoming
 Use a Server OS (e.g., Windows Server 2008) for server applications
 Consider disabling Windows Automatic Updates

 Not required
 Prevents untested changes and/or unplanned reboots to production systems
 Note Patch Qualification page:
http://www.rakb-patchtests.com/data/MS_Patch_Qualification/start.htm
 Windows Firewall will be edited by software installs (Rockwell WFCU)

 Antivirus programs may still restrict access or incorrectly identify threats

FactoryTalk Services
Platform Considerations
PUBLIC INFORMATION

Overview
“Build a suite of common services that can be shared by
many applications”
FactoryTalk® – Production Disciplines
Design & Production Data Quality & Asset Performance

Configuration Management Management Compliance Management & Visibility
Plant Wide
Information
Historical Data
Alarms and
Diagnostics
Activation
Live Data
Directory
Security
Events
Control
Systems
Audit
Process Batch Drives Motion Discrete
Safety
Control Control Systems Control Control
Logix – Control Disciplines

Compatibility
 FactoryTalk Services Platform CPR9 versions are generally compatible
between all Service Releases (SRs.)
 For example, CPR9 SR6 hosts can co-exist with CPR9 SR5 hosts
 Where possible, it is recommended to maintain the same FactoryTalk Services
Platform version and patch level across all hosts.
 Refer to the Product Compatibility site:
http://compatibility.rockwellautomation.com/Pages/ProductReplacement.aspx?crumb
=101
 Where possible, it is recommended to upgrade the FactoryTalk Directory

server to the highest FactoryTalk Services Platform version currently
installed.
 Some products may require an upgrade of the FactoryTalk Directory.

Local Directory vs Network Directory
 Local FactoryTalk Directory:
 A Local FactoryTalk Directory encompasses applications and FactoryTalk products
on the local PC only.
 Utilized for Standalone applications, as only local PC servers can be used in local
FactoryTalk Directory applications.
 Network FactoryTalk Directory:

 Network FactoryTalk Directory ties multiple FactoryTalk PCs together, all utilizing a
central FactoryTalk Directory.
 FactoryTalk Products in a Network FactoryTalk Directory can share services, such
as FactoryTalk Security, FactoryTalk Diagnostics, and FactoryTalk Live Data.
 Can be utilized for widely distributed applications, or applications with everything
installed on one PC.

FactoryTalk Services Platform Network
FactoryTalk Directory: Architecture Considerations
 The role of the Network c should be hosted on a dedicated computer.

 System Start-up – FactoryTalk Directory should be first to start
 Compatibility – Occasionally required versioning
 Patching/Upgrading – Independent patching easy
 Redundancy – Lowest risk option keeps FTD available for failover/failback
 Additionally, a dedicated Network FactoryTalk Directory is also an ideal location

for the following roles that are often present in a FactoryTalk system:
 FactoryTalk Activation Server
 FactoryTalk Alarms and Events Historical Log (SQL Standard/Express)
 Centralized FactoryTalk Diagnostics Server (including SQL Server) in absence of AssetCentre
 FactoryTalk Historian Components, including Phase 2 redundancy shared file
 A server operating system (2008 Server) should be used.

 There areOSexceptions
A server is optimized totoservice
the dedicated PC recommendations,
network requests, such
which is a common function of aas
Network
FactoryTalk Directory. small, non-redundant systems.
 This server should not be a Windows domain controller.
Network FactoryTalk Directory: What about Redundancy?
 Client-side caching allows for operation

independent of FactoryTalk Directory in the
event of downtime. Windows FactoryTalk
Domain Directory RSLinx
Controller Server HMI Server Data Server
 Security and directory cached, only used for
access if FactoryTalk Directory unavailable
 Other objects can be cached, such as HMI
displays
 Detailed testing results on FactoryTalk View

SE system in absence of FactoryTalk cache
Directory :
 AID 66352 - FactoryTalk View SE HMI Client HMI Client
Behavior when FactoryTalk Directory is
Unavailable
CLX CLX

Maintenance Considerations
 The computer hosting the Network FactoryTalk Directory should be highly available.
 All hosts in a FactoryTalk system contact the Network FactoryTalk Directory when they boot
and maintain period communications afterwards.
 If the FactoryTalk system is shut down, the Network FactoryTalk Directory should be the last
host shut down and the first to be restarted.
 Avoid renaming the computer hosting the Network FactoryTalk Directory.

 The hosts in a FactoryTalk system only know the Network FactoryTalk Directory by name (vs.
IP address.)
 The Network FactoryTalk Directory should be periodically backed up to a .BAK file.

 This is currently a manual task performed using the FactoryTalk Administration Console.
 Note option to back up Security Authority Identifier
 Refer to 'Choosing the correct backup and restore options' in the FactoryTalk on-line Help for
additional information.

FAQs / Common Errors
 FactoryTalk Services Platform is not required or recommended on a
Domain Controller.
 In other words, do not co-locate a FactoryTalk Directory server or any other
FactoryTalk software on a Domain Controller.
 A FactoryTalk Directory server should be installed on a Windows Server

operating system (as opposed to a Workstation/Desktop OS.)
 Ensure that any FactoryTalk Services Platform clients are pointing to the
FactoryTalk Directory server prior to install – some installs modify the
directory!
 FactoryTalk Directory servers do not communicate with each other.

FactoryTalk Directory
Internet
Firewall
Domain Controllers
•For the Ctl Sys Domain
•W2K8 Server O/S
•DNS/DHCP/WINS
Server
• FactoryTalk Directory
• FactoryTalk Activation
Server
CLx CLx CLx Flex Flex

CLx
SLC SLC
PLC PLC Engineering
Workstation
• RSLogix 5/500/5000

 RSTechED 2014
 Introduction to the Design and Implementation of FactoryTalk Security in a
Distributed Control System
 Advanced Design, Management, and Implementation of FactoryTalk Security in a
Distributed Control System
 RA Knowledgebase
 AID 58803 – Network FactoryTalk Directory Best Practices
 AID 116811 - CPR9 FactoryTalk Services Platform Compatibility Guidelines
 AID 66352 - FactoryTalk View SE Behavior when FactoryTalk Directory is
Unavailable

Data Server Considerations
PUBLIC INFORMATION

Data Servers
Options
 For Rockwell Automation Hardware (Controllers, drives, etc):
 RSLinx Classic
 RSLinx Enterprise
 FactoryTalk Gateway
 Use OPC for 3rd Parties:

 Kepware
 Matrikon
 others

Data Servers
RSLinx Enterprise vs RSLinx Classic
 RSLinx Enterprise
 Wherever possible!
 RLSE is the preferred Data Server for Rockwell Automation Hardware in FactoryTalk
Applications
 Performance is greatly increased, particularly with Logix family controllers
 Also supports legacy controllers (PLC5, SLC, etc)
 RSLinx Classic
 Only when features are not available in RSLinx Enterprise
 Alias Topic Support
 When Complex paths are needed to talk to a controller
 Ethernet to DH, DH+, DH-485
 DDE Support
 Specific driver support
Data Servers
Alias Topics
Engineering
Workstation
• Workstation
communicating to
ControlLogix via
Ethernet and Controlnet
ENet
Topic CNet
1 Topic
Alias Topic 2
• RSLinx Enterprise
Classic
– Two total shortcuts,
topics, oneone
for
for
eacheach
pathpath (ENet
(ENet &
& CNet)
– CNet)
Alias topic references
CLX both existing topics

Data Servers
Complex Paths
Server #1
ENet
CLx CLx
DH+
CNet
SLC CLx
SLC
PLC PLC
• RSLinx Classic Required • RSLinx Enterprise Supported

– DH+ protocol = PCCC – ControlNet protocol = CIP
– Ethernet protocol = CIP – Ethernet protocol = CIP

Data Servers
What about OPC?
 RSLinx Enterprise is a Live Data server, but RSLinx Classic is not required
for OPC
 FactoryTalk Gateway converts Live Data to OPC, acting as an OPC server

 Converts at an application level, including HMI information
 Not the same as RSLinx Classic Gateway
 FactoryTalk Gateway should be installed as close to the client as possible,

allowing for Live Data communications between the server and Gateway.
RSLinx FactoryTalk OPC

CLX Enterprise Gateway Client
CIP Live Data OPC

Data Servers
RSLinx Enterprise Sizing Considerations
 Recommended maximum of 100,000 tags/sec on a single RSLinx
Enterprise data server.
 Guideline based on general system requirements
 Each application will have a different minimum and maximum
 Not representative of total tags in system, only tags “on-scan” per second
 Maximum number of tags/sec are determined by a number of

application variables:
 Types of servers in application (e.g., FactoryTalk View SE, FactoryTalk Historian SE,
etc.)
 Number of servers in application
 Number of HMI clients in application

Data Servers
RSLinx Enterprise Detailed Sizing
 Recommended Maximum of 2,000,000 Tag References per server.
References can be made by:
 HMI Server processes such as tag server, datalog, derived tags, event tags, etc.
 Live Data clients, such as Historian Interface, FactoryTalk Gateway, etc.
 Worst case Tag References estimation equation = A(6x) + Bx

 A is number of FactoryTalk View SE HMI servers
 x is number of total tags on-scan per second
 B is number of FactoryTalk Live Data clients
 Consider an Example system:

 1 redundant FactoryTalk View SE HMI Server/redundant
 12 FactoryTalk View SE Clients
 20 controllers w/5,000 tags on-scan per second
 1(6*100k)+ 12 *100k = 1,800,000 tag references
Data Servers
ControlLogix Connections
 Each instance of RSLinx Enterprise can use up to 6 connections in a
Logix Controller.
 By default each instance of RSLinx Classic can use 5 connections to a

Logix Controller.
 Though typically unnecessary, can be increased
 Recommend no more than 3 data server connections to a single

ControlLogix controller.

Data Servers
 RSLinx Classic is not required for legacy devices.
RSLinx Enterprise is the preferred data server for Rockwell Automation
Devices.
 There can be only one instance of the same data server type running per
host.
 For example, two instances of RSLinx Enterprise cannot run on the same host.
 Only one service running at a time
 If multiple data servers of the same type are required, multiple hosts are required
 Controllers don’t “talk” OPC

 A controller does not require OPC or Live Data communications

Data Servers
Internet
Firewall
Domain Controllers FactoryTalk Directory
•For the Ctl Sys Domain Server
•W2K8 Server O/S • FactoryTalk Directory
•DNS/DHCP/WINS • FactoryTalk Activation Data Server
Server • (1) RSLinx Enterprise
• (1) RSLinx Classic
OPC Client
• (1) FactoryTalk Gateway

CLx
SLC SLC
PLC PLC
DH+ Engineering
Workstation
• RSLogix 5/500/5000
• RSLinx Classic
SLC
PLC
Data Servers
 RSTechED 2014
 Collecting Data Efficiently in the Integrated Architecture
 Optimize ControlLogix Performance for FactoryTalk Client Applications
 AID 507425 – Rockwell Automation Data Server Decision Guide

FactoryTalk View SE
PUBLIC INFORMATION

FactoryTalk View SE
Application Options
Local Directory Single HMI Station Network Directory Multiple Servers Remote Clients
FactoryTalk View SE
Local Station
FactoryTalk View SE
Network Station
FactoryTalk View SE
Network Distributed

FactoryTalk View SE
Components
 A typical FactoryTalk View SE system consists of the following software components (or
roles):
 Network FactoryTalk Directory Server (FTD) (1)
 FactoryTalk View SE Server(s) (1+)
 SQL Server(s) (Express or Standard) (1+)
 FactoryTalk Live Data Server(s) (1+)
 FactoryTalk Alarm Server(s) (0+)
 FactoryTalk View SE Client(s) (1+)
 FactoryTalk View SE Studio(s) (1+)

FactoryTalk View SE
Network Station Considerations
 Network Directory application
 1 HMI server, 1 HMI client (no remote clients)
 Can share remote data & alarm servers, unlike Local station
 Configuration of alarm & data servers is not shared, only resources
 Can also access other Network Directory servers, such as FactoryTalk

Historian SE
 Maximum of 20 applications per directory

FactoryTalk View SE Distributed
Component Limits (v7.00 and higher)
 HMI Servers: 10 per application (redundant or non-redundant)
 Data Servers: 10 per application (redundant or non-redundant)
 Alarm Servers: 10 per application (redundant or non-redundant)
 Clients
 50 per Application
 Total mix of thick & thin clients
 Recommended 25:1 ratio
 1 Distributed application per FactoryTalk Directory (production)

 Multiple supported in development

HMI Server Architecture
 Can be co-located with the FactoryTalk Directory, but recommend separate
hosts
 Recommend independent hosts – no clients or EWS co-located

 Except for testing
 Redundant servers do not equate to load-balancing

 Load balance at a 25:1 ratio
 MSSQL Express instance must be co-located for tag database

 This instance is not supported for use with anything outside of the FactoryTalk View
SE HMI server. i.e., it cannot be used for historical logging

FactoryTalk View SE
Datalog Models
 Up to 20 datalog models can run simultaneously
 The FactoryTalk View SE Trend/Datalog functionality is meant for recent

operator data, not intensive historical analysis
 Running the datalog functionality at its technical limits will result in an unstable host
and server.
 Large data logging needs should indicate the need for an Historian server,
not necessarily an additional HMI server.

FactoryTalk View SE
Alarm Limits (v7.00 and higher)
 Legacy / Classic HMI Alarming
 40,000 total alarms per HMI Server
 10,000 of which can be Analog
 Alarm Summary will display the 2,000 most recent alarm transactions
 Default Update Rate = 2 seconds
 FactoryTalk Alarms & Events

 100,000 total alarms per Application
 10,000 total alarms per Alarm Server
 FactoryTalk Alarms / controller
 2,000 – non-redundant
 500 / 250 – redundant
 AID 44177 - FactoryTalk Alarms & Events - Special Considerations

Data & Alarm Server Architecture
 RSLinx Enterprise and RSLinx Classic
 Can be co-located with HMI server
 No more than two different data servers per host
 For instance, RSLinx Classic and RSLinx Enterprise installed on the same host
 Device-based Alarming
 RSLinx Enterprise used as alarm server
 Often co-located with HMI server
 v21 does not support device-based
 Tag-based Alarming
 Can be co-located with HMI and/or Data server, or independent

Redundancy
 Only one host should be designated as the “Primary” with the responsibility
of the Primary HMI and Primary Data servers.
 Redundancy is not a mechanism for load balancing.
Good Bad
Server #1 Server #2 Server #1 Server #2
• HMI Server Primary • HMI Server Secondary • HMI Server Primary • HMI Server Secondary
• Data Server Primary • Data Server Secondary • Data Server Secondary • Data Server Primary
Redundant Redundant
Pair Pair
Note: Historical Alarm DB should not be located on a redundant host

FactoryTalk View SE
 Don’t put more than one production HMI server on the same host
 Support multiple HMI servers on a single host for development purposes
 Redundancy is not load balancing – only one

server is actively serving data at a time.
 Hierarchy Terminology:
 FTD
 Application
 Area
 Alarm Server
 Data Server
 HMI Server

FactoryTalk View SE
Internet
Firewall
Domain Controllers FactoryTalk Directory Primary Server
•For the Ctl Sys Domain Server • (1) HMI Server
•W2K8 Server O/S • FactoryTalk Directory • (1) Tag-based Alarm Server Data Server
•DNS/DHCP/WINS • FactoryTalk Activation • (1) Data Servers • (1) RSLinx Enterprise
Server • (1) RSLinx Enterprise
• MSSQL Express Server
5 Clients
CLx
SLC SLC
PLC PLC Engineering Workstation
• RSLogix 5/500/5000
• RSLinx Classic
• FactoryTalk View Studio FactoryTalk View SE Clients

FactoryTalk View SE
 RSTechED 2014
 Architecting a Distributed FactoryTalk View Site Edition System
 FactoryTalk View Site Edition: Building Applications
 FactoryTalk View Site Edition: Implementing FactoryTalk Alarms and Events
 Rockwell Automation Knowledgebase

 AID 32549 – FactoryTalk View SE Distributed System Design Considerations
 AID 37110 – FactoryTalk View SE Tips and Best Practices TOC
 AID 44177 - FactoryTalk Alarms & Events Considerations for the Initial Release
 Rockwell Automation Literature Library

 FactoryTalk View SE Popular Configuration Drawings

FactoryTalk Historian
PUBLIC INFORMATION

Application Types
MANAGEMENT
SUPERVISOR
OPERATOR

FactoryTalk Directory Connectivity
 FactoryTalk Historian ME can function independently of a FactoryTalk
Directory, or within a Network FactoryTalk Directory.
 FactoryTalk Historian ME Modules can use security configurations from the
FactoryTalk Directory, or use a native form of security that does not require the
FTSP.
 FactoryTalk Historian SE is only supported in the Network FactoryTalk

Directory
 FactoryTalk Historian SE does not support Local Directory or Workstation type
environment.
 FactoryTalk Historian EE does not use the FactoryTalk Services Platform.

 A FactoryTalk Historian SE server can be configured as an “enterprise” level
aggregator, which would in turn support only the Network FactoryTalk Directory.
Machine Edition Considerations
 ME Module fits into the ControlLogix chassis
 Up to 2 per chassis supported
 Single module can communicate with up to 4 ControlLogix controllers

 Only one if High Speed is being used (<500ms)
 Maximum of 2500 points per second

 Storage available at maximum logging for 4-14 hours depending upon module
 ME Module sends data up to FactoryTalk Historian SE server
See AID 63082 - FAQ: FactoryTalk Historian Machine Edition

Site Edition Components
 A typical FactoryTalk Historian SE system consists of the following software components
(or roles):
 FactoryTalk Historian Server (1)
 FactoryTalk Asset Framework Server (1)
 SQL Server (Express or Standard) (1)
 FactoryTalk Historian Live Data Interface(s) (1+)
 FactoryTalk Live Data Server(s) (1+)
 FactoryTalk Historian Client(s) (1+)

Component Limits
 Two (2) Historian SE Servers per
FactoryTalk
FactoryTalk Directory Historian
 Or two (2) collectives consisting of 2 members Server
each
 100,000 Events/sec
 50,000 pre-v4.00 Interface
node
 20 Clients maximum
Data Source
 FactoryTalk View, (DCS, PLC,
FactoryTalk VantagePoint, DataLink, etc.)
ProcessBook, ActiveView
See AID 49189 – FactoryTalk Historian SE System Design Considerations

Interface Considerations
 25,000 events/sec on one Interface
FactoryTalk
 Up to 50,000 defined tags Historian
Server
 20,000 pre-v4.00 versions
 20,000 events/sec on one redundant

interface pair Interface
 15,000 pre-v4.00 versions node
 Total Interfaces per FactoryTalk Historian Data Source

(DCS, PLC,
Server etc.)
 50 interfaces per server, 25 redundant
See AID 66997 – FAQ: FactoryTalk Historian SE FactoryTalk Live Data Interface
Component Architecture
 Interfaces buffer data in when the FactoryTalk Historian Server is absent.
Therefore, it is not recommended to co-locate interfaces with Historian
Server host.
 Commonly recommended to locate Interface with Data Server.
 Asset Framework server can be co-located with MSSQL

 Can co-locate with Historian Server, but not recommended
 Equates to at least 3 server hosts:

 FactoryTalk Directory Server (FTD)/ FactoryTalk Historian SE Asset Framework
Server (FTAF) / MSSQL
 Optimally divided between two hosts – FTD & FTAF / MSSQL
FactoryTalk
A three HistorianisSEthe
host system server
Best Practice because it is the most scalable
 Data Server/Interface
and minimizes the potential for resource conflicts.
Redundancy vs High Availability
System Thin Clients: FactoryTalk VantagePoint, Portal,

Management Rich Clients: FactoryTalk View, ProcessBook, DataLink, FactoryTalk
Tools Applications, Custom Application…
PI SDK
Secondary Configuration Primary

If you require minimal data loss,
Secondary
Historian
Changes
Historian then you need redundant
Historian(s)interface
nodes
Data Buffering Data Buffering

Services If you require
Services highly available data for
Historian Interfaces reporting, then you need redundant
Historian Interfaces
servers (a Collective).

 Historian Interface ≠ Data Server
 An Historian Interface is a data client, receiving information from the data server,
then forwarding it on to the Historian Server.
 Historian Interface buffering is effectively disabled when co-located with

Historian Server
 Data Redundancy = Interfaces, Information High Availability = Collective
 Historical data is not natively stored in an open database (e.g., MSSQL.)

Internet
Server
Redundant HMI/Data Server
• FactoryTalk Directory
Server • (1) HMI Server
• (1) Tag-based Alarm Server Firewall
Domain Controllers Server • (1) Data Servers
•For the Ctl Sys Domain • MSSQL Express Server • (1) RSLinx Enterprise
•W2K8 Server O/S • FactoryTalk Historian
• FactoryTalk Asset Live Data Interface
•DNS/DHCP/WINS
Framework Server
SE Server
• FactoryTalk Historian
Server
5 Clients
CLx
SLC SLC
• RSLogix 5/500/5000
• RSLinx Classic
• FactoryTalk View Studio FactoryTalk Clients
• FactoryTalk Historian SE • FactoryTalk View SE Client
Mgmt Tool • FactoryTalk Historian SE Client

 RSTechED 2014
 Architecting a Distributed FactoryTalk View Site Edition System
 FactoryTalk View Site Edition: Building Applications
 FactoryTalk View Site Edition: Implementing FactoryTalk Alarms and Events
 AID 49189 – FactoryTalk Historian SE System Design Considerations
 AID 56070: FactoryTalk Historian SE Tips and Best Practices TOC

PUBLIC INFORMATION

Components
 A typical FactoryTalk AssetCentre system consists of the following software components
(or roles):
 FactoryTalk AssetCentre Server (1)
 SQL Server Standard (1)
 FactoryTalk AssetCentre Agent(s) (1+)
 FactoryTalk AssetCentre Client(s) (1+)
 ProCalV5 Server (0-1)
 ProCalV5 Client(s) (0+)

Component Limits
 One FactoryTalk AssetCentre Server
 ProCalV5 Server (if using Calibration
Management)
1
 Five FactoryTalk AssetCentre Agents
 Single agent services ~100 assets/ 12hrs
5
 Fifty concurrent FactoryTalk AssetCentre
Clients
 ProCalV5 Client (if using Calibration
Management)
50

Calibration Management Components
FactoryTalk
AssetCentre
Server
Ethernet
` `
FactoryTalk ProCalV5
AssetCentre Server
Server
• ProCalV5 Server • ProCalV5 Client

– Recommended to be co-located with – Must be co-located with FactoryTalk
FactoryTalk AssetCentre Server. AssetCentre Client.
– Contains all Calibration Management – Can only be accessed using FactoryTalk
information. AssetCentre Client.
– Links to FactoryTalk AssetCentre Server – Used to configure ProCalV5 server.
process device assets.
– Communicates with own database in
MSSQL Server.
System Considerations
 FactoryTalk Directory – there can be only one!
 Each FactoryTalk AssetCentre Server can be associated with one and only one
FactoryTalk Network Directory.
 FactoryTalk Local Directories are not used by FactoryTalk AssetCentre.
 Microsoft SQL Server 2005/2008

 Each FactoryTalk AssetCentre system can use a single Microsoft SQL (MSSQL.)
 MSSQL Server can be co-located with Server component.
 Multiple FactoryTalk AssetCentre Agents

 One agent per host, Agent component can be co-located with Server component.
 Each agent requires un-activated editor software for applicable assets.
 All agents must be able to access all assets in the system.
 Agent hosts should not be used as Engineering Workstations due to resource usage.
 See AID 106118 – Determining the Necessary Number of AssetCentre Agents
Client Considerations
 Locally on engineering workstations
 Engineer workstation = PC being used with editing software such as RSLogix, View
Studio, etc.
 Installing locally with editing software allows user to check out files for use with
editing application, make changes, then check files back into AssetCentre archive.
 Any FactoryTalk PC requiring audit functionality

 FactoryTalk AssetCentre Client acts as FactoryTalk Audit “listener”

 The FactoryTalk AssetCentre Agent component is required for all
configuration.
 Audits/Events are not collected automatically – an AssetCentre Client must

be installed on the host to send the diagnostic information to the Server.
 Only one AssetCentre Server is supported per FactoryTalk Directory.
 …spelling…

Internet
Server
• FactoryTalk Directory Redundant HMI/Data Server
• FactoryTalk Activation • (1) Tag-based Alarm Server
Server Firewall
• (1) Data Servers
Domain Controllers • MSSQL Express Server
• (1) RSLinx Enterprise
• FactoryTalk Asset
•For the Ctl Sys Domain Framework Server • FactoryTalk Historian Live
•W2K8 Server O/S Data Interface
• FactoryTalk
•DNS/DHCP/WINS AssetCentre Client • FactoryTalk AssetCentre
Client
FactoryTalk Historian FactoryTalk AssetCentre Server

SE Server • MSSQL 2008 Server Standard
• FactoryTalk Historian • FactoryTalk AssetCentre Server
Server • FactoryTalk AssetCentre Agent
• FactoryTalk • FactoryTalk AssetCentre Client
AssetCentre Client • RSLinx Classic (no activation)
• RSLogix 5/500/5000 (no
activation)
5 Clients
CLx
SLC SLC
• RSLogix 5/500/5000
• RSLinx Classic
• FactoryTalk Historian • FactoryTalk View SE Client
Mgmt Tool • FactoryTalk Historian SE Client
• FactoryTalk AssetCentre • FactoryTalk AssetCentre Client
Client

 RSTechED 2014
 FactoryTalk AssetCentre: Introduction and Demonstration
 FactoryTalk AssetCentre Self-Paced Lab
 AID 57483 – FactoryTalk AssetCentre System Design Considerations
 AID 56049 – FactoryTalk AssetCentre Tips and Best Practices TOC
 AID 60057 – Architecting FactoryTalk AssetCentre

PUBLIC INFORMATION

FactoryTalk VantagePoint and the
 FactoryTalk VantagePoint can function independently of a FactoryTalk
Directory, or within a Network FactoryTalk Directory.
 Within an FactoryTalk Directory server, FactoryTalk VantagePoint can connect to:
 FactoryTalk Live Data
 FactoryTalk Historian SE or ME
 FactoryTalk Alarms and Events historical database
 FactoryTalk Historian and FactoryTalk Alarms & Event information can also be
collected from outside of the FactoryTalk Directory server.
 FactoryTalk VantagePoint is only supported in the Network FactoryTalk

Directory

Components
 A typical FactoryTalk AssetCentre system consists of the following software components
(or roles):
 Network FactoryTalk Directory Server (FTD) (0-1)
 FactoryTalk VantagePoint Server (1)
 SQL Server Standard (1)
 Data Source (1+)
 FactoryTalk VantagePoint Client(s) (1+)

Sizing
Note that within this solution, the option to increase memory (RAM)
and increase CPUs always exists as a method to improve system
performance.
SharePoint and
Excel Services
Multiple
• For large enterprise
FactoryTalk systems that include
VantagePoint SharePoint
Separated SQL Systems • Excel Services can
Server System be used to improve
• Dedicated systems for Excel rendering
• SQL Server installed Eventing, Report performance on the
on separate server Generation,
Stand-Alone from VantagePoint Dashboards…
Portal
Systems
• Data Source and
VantagePoint are
installed on
Co-Hosted separate servers
Systems • VantagePoint has
a dedicated server
• Data Source (no other
installed on applications)
same server as
VantagePoint

Component Architecture
 Typical system consists of three hosts:
 FactoryTalk VantagePoint Server
 Data Source
 SQL Server
 For smaller systems, components can be co-located

 General guideline is <10 clients
 Application factors that may cause additional hosts to be required:
 Number and type of data sources
 Number and type of reports
 Frequency of report generation
A three host system is the Best Practice because it is the most scalable
and minimizes the potential for resource conflicts.
Internet
FactoryTalk Directory Redundant HMI/Data Server

• FactoryTalk Directory • (1) Tag-based Alarm Server
Server • (1) Data Servers Firewall
Domain Controllers • FactoryTalk Activation • (1) RSLinx Enterprise
•For the Ctl Sys Domain Server • FactoryTalk Historian Live
•W2K8 Server O/S • MSSQL Express Server Data Interface
•DNS/DHCP/WINS • FactoryTalk Asset • FactoryTalk AssetCentre
Framework Server Client
• FactoryTalk
AssetCentre Client
FactoryTalk Historian FactoryTalk AssetCentre Server FactoryTalk VantagePoint MSSQL Server

SE Server • MSSQL 2008 Server Standard Server • MSSQL 2008
• FactoryTalk Historian • FactoryTalk AssetCentre Server • FactoryTalk VantagePoint Server Standard
Server Server for FactoryTalk VantagePoint
• FactoryTalk AssetCentre Agent
• FactoryTalk AssetCentre • FactoryTalk AssetCentre Client • FactoryTalk VantagePoint
Client • RSLinx Classic (no activation) Portal
• RSLogix 5/500/5000 (no • Excel 2010+
activation)
5 Clients
CLx
SLC SLC Engineering Workstation
PLC PLC • RSLogix 5/500/5000
• RSLinx Classic
• FactoryTalk View Studio
• FactoryTalk Historian
Mgmt Tool FactoryTalk Clients
• FactoryTalk AssetCentre • FactoryTalk View SE Client
Client • FactoryTalk Historian SE Client
• FactoryTalk • FactoryTalk AssetCentre Client
VantagePoint Mgr
• Dashboard Builder
• Excel 2010+
 Where can the FactoryTalk VantagePoint Server be co-located?
 Best practice is to locate on an independent host
 In small applications, it’s possible to locate with other server
components
 MSSQL if no independent instance available
 FactoryTalk Historian SE in very limited circumstances
See AID 62869 – FactoryTalk Historian SE and FactoryTalk VantagePoint on a
Single Host Computer

 RSTechED 2014
 Introduction to FactoryTalk VantagePoint and Enterprise Manufacturing Intelligence
 FactoryTalk VantagePoint EMI: 50 Minutes to Value
 FactoryTalk VantagePoint EMI Basic Lab: Building an Information System
 AID 59904 - FactoryTalk VantagePoint System Design Considerations
 AID 59149 – FactoryTalk VantagePoint Tips and Best Practices TOC
 AID 61808 - FAQ: FactoryTalk VantagePoint Frequently Asked Questions
 AID 63620 - Architecting FactoryTalk VantagePoint

Microsoft SQL Server: Briefly
PUBLIC INFORMATION

Microsoft SQL
How many servers are out there?
Redundant HMI/Data Server
 FactoryTalk View SE HMI Tag Database Server (2) • (1) HMI Server
• (1) Tag-based Alarm Server
• (1) Data Servers
• (1) RSLinx Enterprise
 Express instances – must be co-located with HMI Server • FactoryTalk Historian Live
Data Interface
• FactoryTalk AssetCentre
Client
 FactoryTalk Alarms & Events Historical Logging

Server
• FactoryTalk Directory Server
Server
• MSSQL Express Server
• FactoryTalk Asset
Framework Server
 FactoryTalk Historian SE Asset Framework Server • FactoryTalk AssetCentre

Client
FactoryTalk AssetCentre Server

• MSSQL 2008 Server Standard
 FactoryTalk AssetCentre Server • FactoryTalk AssetCentre Server

• FactoryTalk AssetCentre Agent
• FactoryTalk AssetCentre Client
• RSLinx Classic (no activation)
• RSLogix 5/500/5000 (no
activation)
FactoryTalk VantagePoint MSSQL Server

Server • MSSQL 2008
 FactoryTalk VantagePoint Server • FactoryTalk VantagePoint

Server
• FactoryTalk VantagePoint
Server Standard
for FactoryTalk VantagePoint
Portal
• Excel 2010+

Microsoft SQL
Consolidating Server Instances
 FactoryTalk Alarms & Events (FTAE) History, FactoryTalk Historian SE
Application Framework (FTAF) Server, FactoryTalk AssetCentre (FTAC)
Server, and FactoryTalk VantageaPoint (FTVP) instances can be
consolidated
 Amount of consolidation will depend on MSSQL Licensing

 FTAE & FTHSE are shipped with MSSQL Express (no licensing)
 FTAC & FTVP are shipped with a single processor license
 If no external activation is purchased, all databases can be consolidated to

one host with two MSSQL Instances:
 MSSQL Express Instance: FTAE & FTHSE (FTAF) databases
 MSSQL Standard Instance: FTAC & FTVP databases
Microsoft SQL
Database Management Best Practices
 A system backup plan, including both database and transaction logs, is
highly recommended
 FactoryTalk AssetCentre: AID 59541
 FactoryTalk VantagePoint: AID 62884
 Monitor the size of the transaction logs, particularly in systems with

constant data changes (e.g., FactoryTalk AssetCentre)
 Consider simple recovery mode, allowing for scheduled transaction log shrinking
 Discuss further policies with end user’s database management team

 Indexing and cleanup operations
 Database growth policy expansion

Microsoft SQL Server
Internet

• FTD • (1) Tag-based Alarm Server
• FactoryTalk Activation • (1) Data Servers Firewall
Domain Controllers Server • (1) RSLinx Enterprise
•For the Ctl Sys Domain • MSSQL Express Server • FactoryTalk Historian Live
•W2K8 Server O/S • FactoryTalk Asset Data Interface
•DNS/DHCP/WINS Framework Server • FactoryTalk AssetCentre
• FactoryTalk Client
AssetCentre Client

SE Server • MSSQL 2008 Server Standard Server • MSSQL 2008
• FactoryTalk Historian • FactoryTalk AssetCentre Server • MSSQL 2008 Server Standard Server Standard
Server • FactoryTalk AssetCentre Agent • FactoryTalk VantagePoint • MSSQL 2008
• FactoryTalk AssetCentre • FactoryTalk AssetCentre Client Server Server Express
Client • RSLinx Classic (no activation) • FactoryTalk VantagePoint
• RSLogix 5/500/5000 (no Portal
activation) • Excel 2010+
5 Clients
CLx
SLC SLC
• RSLogix 5/500/5000
• RSLinx Classic
• FactoryTalk Historian Mgmt Tool • FactoryTalk View SE Client
• Factorytalk AssetCentre Client • FactoryTalk Historian SE Client
• FactoryTalk VantagePoint Mgr • FactoryTalk AssetCentre Client
• Excel 2010+
PUBLIC INFORMATION

Options
 Remote Desktop Services
 Formerly Terminal Services
 Instantiate multiple sessions from single host
 As opposed to Workstation/Desktop OS single shared instance
 Each instance activated independently of server
 FactoryTalk ViewPoint Server (FactoryTalk View only)

 Microsoft Silverlight required
 Multiple browser options supported
 Some functionality disabled (ActiveX controls, VBA scripting, etc)
 Locate Server component on independent host

RDS Design Considerations
 Windows Server OS Required
 Server co-location supported, but not recommended

 Known issues & Resource intensive
 Client operation could interfere with server availability
 Recommend multiple servers to avoid

a single point of failure
 Load balanced farm of 2+ RDS servers can
be created using the Connection Broker.
 Nearly impossible to generally specify necessary resources

 Invest in server-class hardware with upgrade availability (CPU, Memory, etc)
 Remote Desktop Session Host Capacity Planning in Windows Server 2008 R2
RDS General Considerations
 FactoryTalk Client and Engineering Workstation components are located
on the Remote Desktop Services server (not Server components.)
 Diagnostic information (e.g., Events in FactoryTalk View Studio) will be

seen from all user instances, not limited to the current instance.
 FactoryTalk Diagnostic information can be configured to show location as the thin
client or the RDS Server to which it is connected.
 When used with FactoryTalk AssetCentre, any editor software should be

co-located on the Remote Desktop Services server host.
 Splitting roles between the “thin” client and RDS instance results in more complex file
storage/forwarding.

Remote Desktop Services Server
RDS Client(s)
Internet

• FTD • (1) Tag-based Alarm Server
• FactoryTalk Activation • (1) Data Servers Firewall
Domain Controllers Server • (1) RSLinx Enterprise
•For the Ctl Sys Domain • FactoryTalk Asset • FactoryTalk Historian Live
•W2K8 Server O/S Framework Server Data Interface
•DNS/DHCP/WINS • FactoryTalk • FactoryTalk AssetCentre
AssetCentre Client Client Remote Desktop
Services Hosts
• FactoryTalk View SE Client
• FactoryTalk Historian SE Client
• Logix 5/500/5000
• RSLinx Classic

SE Server • FactoryTalk AssetCentre Server Server • MSSQL 2008
• FactoryTalk Historian • FactoryTalk AssetCentre Agent • FT VantagePoint Server Standard
Server • FactoryTalk AssetCentre Client Server • MSSQL 2008
• FactoryTalk AssetCentre • FT VantagePoint Server Express
Client • RSLogix 5/500/5000 (no Portal
5 Clients
CLx
SLC SLC
• RSLogix 5/500/5000
• RSLinx Classic
• FactoryTalk AssetCentre Client • FactoryTalk Historian SE Client
• Excel 2010+
FactoryTalk Viewpoint
Architecture Considerations
 Recommended to locate the FactoryTalk ViewPoint server on its own
highly available PC separate.
 Co-location supported in non-redundant applications.
 The total number of clients allowed by FactoryTalk ViewPoint is a

maximum of 50
 Total is sum of traditional View SE thick and thin clients and each open browser
instance of FactoryTalk ViewPoint)
 FactoryTalk ViewPoint can only publish a single application at a time.

 For systems including multiple FactoryTalk applications, a separate FactoryTalk
ViewPoint server will be required for each application

Remote Desktop Services Server
RDS Client(s)
Internet

Server • (1) HMI Server FactoryTalk ViewPoint Client(s)
• FactoryTalk Directory • (1) Tag-based Alarm Server
Server • (1) Data Servers Firewall
Domain Controllers • FactoryTalk Activation • (1) RSLinx Enterprise
•For the Ctl Sys Domain Server • FactoryTalk Historian Live
•W2K8 Server O/S • FactoryTalk Asset Data Interface
•DNS/DHCP/WINS Framework Server • FactoryTalk AssetCentre
• FactoryTalk Client Remote Desktop Services
AssetCentre Client
FactoryTalk Hosts
Viewpoint Server • FactoryTalk View SE Client
• ViewPoint Server • FactoryTalk Historian SE Client
• Logix 5/500/5000
• RSLinx Classic

SE Server • FactoryTalk AssetCentre Server Server • MSSQL 2008
• FactoryTalk Historian • FactoryTalk AssetCentre Agent • FT VantagePoint Server Standard
Server • FactoryTalk AssetCentre Client Server • MSSQL 2008
• FactoryTalk AssetCentre • FT VantagePoint Server Express
Client • RSLogix 5/500/5000 (no Portal
5 Clients
CLx
SLC SLC
• RSLogix 5/500/5000
• RSLinx Classic
• FactoryTalk AssetCentre Client • FactoryTalk Historian SE Client
• Excel 2010+
Local and/or Station Applications
 Full Remote Desktop Services implementations are not supported with
Station applications because remote clients are not possible.
 A Point-to-Point remote viewing mechanism, such as VNC, is possible.

 Point-to-Point allows for the sharing of the client instance, as opposed instantiating
multiple clients.
 FactoryTalk ViewPoint can be used for:

 FactoryTalk View ME (PanelView Plus)
 FactoryTalk View SE Local Station
 FactoryTalk View SE Network Station

 RSTechED 2014
 FactoryTalk View Machine Edition and PanelView Plus: Data Logging, Trending,
Recipe Functionality and Remote Access
 FactoryTalk View Site Edition: Building Applications (Part 1)
 Extending FactoryTalk View Site Edition with Microsoft's Remote Desktop Services
 AID 554813 - Using FactoryTalk with Remote Desktop Services TOC
 AID 57596 - FactoryTalk View Object and Feature Support within FactoryTalk
ViewPoint
 Microsoft References
 Remote Desktop Session Host Capacity Planning in Windows Server 2008 R2

Virtualization
PUBLIC INFORMATION

Virtualization
Architecture Considerations
 “Bare metal” hardware sizing
 Expandable, server-class
 Count determined by number of images,
virtualization features
 Generally, 1 physical CPU = 2 virtual CPU
 Memory is 1:1 ratio
 Virtual machine inventory

 One physical host equates
to one virtual machine
 Generally recommended
to start with 1vCPU and scale up as needed
 Generally recommend >=4GB of memory for servers, >=2GB for EWS/Clients

Virtualization
General Considerations
 Server-based Virtualization should be used in production (e.g., vSphere)
 As opposed to workstation based (e.g., VMware Workstation.)
 Separate redundant virtual machines onto different physical hosts

 For example, Primary HMI Server VM on Host 1, Secondary HMI Server
VM on Host 2
 Prevents single point of failure at physical host.
 Consider virtual LANs for VM to VM communications

 Virtual LANs allow for host-internal communications without having to “go out and
back in” the physical NIC
 Contacting Rockwell Automation Network Services group

 Rockwell Automation offers a custom built virtual solution and/or consultation on
virtual system design.

Virtualization
 RSTechED 2014
 Introduction to VMware Product Suite: Virtualization Solutions
 Virtualization in Manufacturing Industries
 Building a Hardware Infrastructure for a Virtualized Solution
 AID 568026 - Using Rockwell Automation Software with VMware
 Literature Library
 Virtualization for Process Automation Systems

We care what you think!
Please take a couple minutes to complete a quick
session survey to tell us how we’re doing.
1
 On the mobile app:
1. Locate session using
Schedule or Agenda Builder
2. Click on the thumbs up icon on
the lower right corner of the 2
session detail
3. Complete survey
4. Click the Submit Form button
3
Thank you!! 4
Questions?
PUBLIC INFORMATION
The image part with relationship ID rId5 was not found in the file. The image part with relationship ID rId5 was not found in the file.
Follow RSTechED on Facebook & Twitter.

Connect with us on LinkedIn.
www.rsteched.com

Fdocuments - in Factorytalk System Design Considerations

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Fdocuments - in Factorytalk System Design Considerations

Uploaded by

Copyright:

Available Formats

FactoryTalk® System Design Considerations

Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.

Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.

 Only one continuous task per controller

Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved. 5

 Rockwell Automation Literature Library

Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved. 6

Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.

 What type of networking

 Wireless Level 0–2 Cell/Area Zone

 What type of networking Controller

services will be used?

Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved. 8

present a security concern, and an IT Security

 Aid 29402 - TCP ports used by Rockwell products

 Use thin client services to go through a Firewall for application connectivity

Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved. 9

 Wireless networks are prone to signal interference,

 FactoryTalk applications require network speeds of >= 10Mbps. (test labs

Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved. 10

CLx CLx Flex Flex

Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved. 11

Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved. 12

CLx CLx Flex Flex

 Rockwell Automation Knowledgebase

Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved. 14

Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.

 40% steady-state processor utilization as a general baseline

 Consider future expansion / support when purchasing hardware

Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved. 16

 Consider disabling Windows Automatic Updates

 Windows Firewall will be edited by software installs (Rockwell WFCU)

Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved. 17

Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.

Design & Production Data Quality & Asset Performance

FactoryTalk Services Platform

Logix – Control Disciplines

Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved. 19

 Where possible, it is recommended to upgrade the FactoryTalk Directory

Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved. 20

 Network FactoryTalk Directory:

Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved. 21

 The role of the Network c should be hosted on a dedicated computer.

 Additionally, a dedicated Network FactoryTalk Directory is also an ideal location

 A server operating system (2008 Server) should be used.

 Client-side caching allows for operation

 Detailed testing results on FactoryTalk View

Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved. 23

 Avoid renaming the computer hosting the Network FactoryTalk Directory.

 The Network FactoryTalk Directory should be periodically backed up to a .BAK file.

Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved. 24

 A FactoryTalk Directory server should be installed on a Windows Server

 FactoryTalk Directory servers do not communicate with each other.

CLx CLx CLx Flex Flex

Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved. 26

Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved. 27

Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved.

 Use OPC for 3rd Parties:

Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved. 29

Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved. 31

• RSLinx Classic Required • RSLinx Enterprise Supported

Copyright © 2014 Rockwell Automation, Inc. All Rights Reserved. 32

 FactoryTalk Gateway converts Live Data to OPC, acting as an OPC server