Factory Talk

FactoryTalk Implementacin de Arquitecturas
Tendencias Tecnolgicas Lima Agosto 2017
Miguel Orihuela
Solution Architect Automation & Software
Rockwell Automation de Per
PUBLIC
Rockwell Automation TechED 2017 @ROKTechED #ROKTechED Copyright 2017 Rockwell Automation, Inc. All Rights Reserved. 1
Agenda
High Level discussion of the main considerations when building a system:
FactoryTalk Services Platform
Data Servers
FactoryTalk View Site Edition (SE)
FactoryTalk Historian
FactoryTalk AssetCentre
FactoryTalk VantagePoint
Basic Microsoft SQL Server Considerations
ThinManager & Remote Desktop Services

PUBLIC Rockwell Automation TechED 2017 @ROKTechED #ROKTechED Copyright 2017 Rockwell Automation, Inc. All Rights Reserved. 2
Factory Talk Suite
EMI - Manufacturing Intelligence Suite
Broad Horizontal Applicability Mfg. Operations
Management
Scalable Solutions
Auto Suite
Tightly coupled with the Automation Systems
Infrastructure for Vertical Application Suites CPG Suite
Applicable across multiple industries
Web Reporting Pharma Suite
Manufacturing ProductionCentre
Intelligence
VantagePoint
Visualization
Metrics Manufacturing Operations
Asset - Industry Application
Management Historian
Suites
Transaction Industry Specific
Manager
Business Objectives Focus
View SE / ME Plant-centric Approach
Control ViewPoint
Quality & Compliance
AssetCentre Supply Chain
Windows Infrastructure
Use a Server Operating System for application servers
Operating System compatibility

charts located on:
Product Compatibility & Download Center
Patch qualification testing recorded on:

Rockwell Software MS Patch Qualifications
Windows Infrastructure
Workgroups vs Domains
Windows Domains recommended in architectures of Workgroup environments:
10 FactoryTalk Computers or more All computers must be in the
same Workgroup.
Common Requirements
Unique IP Address (consider DHCP) Domain environments:
Unique Host Names (consider DNS) All computers must be in the
same Domain / trusted Domain.
Differences
User name authentication Workgroups require
special configuration Domain and Workgroup
environments cannot be mixed.
Security Domains allow for Active Directory user
linking
Sample Architecture:
Domain Controllers
Domain
Controllers
Server O/S
Managed Ethernet Switch for Control System Network (CSN) HMI/Ctrl Communications
Engineering Workstation
RSLogix 5/500/5000
ControlLogix ControlLogix ControlLogix RSLinx Classic
SLC SLC
PLC PLC
PUBLIC
Overview
Local vs Network Directories
Local FactoryTalk Directory: Each computer is FTSP isolated
Network FactoryTalk Directory:
Ties multiple FactoryTalk PCs together
Share services such as FactoryTalk Security and FactoryTalk Live Data
Used for distributed applications and applications with everything installed on one PC
HMI Server Historian Server

Clients
Network FactoryTalk Directory
Data Server AssetCentre Server
Network FTD Architecture Considerations
The role of the Network server should be hosted on a dedicated computer.
System Start-up
Compatibility
Patching/Upgrading
Redundancy
Exception
FTD Server can host other system components:

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
Use a server operating system

A server OS is optimized to service network requests
Not a domain controller
FAQs / Common Errors
FactoryTalk Services Platform not required/recommended on a Domain Controller.
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.)
No redundancy caching instead

AID 66352 - FactoryTalk View SE Behavior when FactoryTalk Directory is Unavailable
FactoryTalk Directory servers do not communicate with each other.

FactoryTalk Directory
Domain Controllers
Server O/S FactoryTalk Directory
For the Ctl Sys Domain Server
Server O/S
FactoryTalk Activation
Server
RSLogix 5/500/5000
SLC SLC
PLC PLC
For more information on
Rockwell Automation TechED 2017
NS19 - Introduction to the Design & Implementation of FactoryTalk Security in a DCS
NS20 - Advanced Design, Management & Implementation of FactoryTalk Security in a DCS
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
Data Servers
Options
For Rockwell Automation Hardware (Controllers, drives, etc):
RSLinx Classic
RSLinx Enterprise
FactoryTalk Gateway
Use OPC for 3rd Parties:

Kepware
Matrikon Data Server
others
Data Client Data Client
Data Servers
RSLinx Enterprise vs RSLinx Classic
RSLinx Enterprise RSLinx Classic
Wherever possible! Only when features are not available
Preferred Data Server in RSLinx Enterprise
for Rockwell Automation Alias Topic Support
Hardware Complex Paths
Performance is greatly increased Ethernet to DH, DH+, DH-485
with Logix family controllers DDE Support

Also supports legacy controllers Specific driver support
(PLC-5, SLC, etc)
Data Servers
Complex Paths
Data Server
EtherNet/IP
ControlLogix ControlLogix
DH+
ControlNet
SLC ControlLogix
SLC
PLC PLC
RSLinx Classic Required RSLinx Enterprise Supported

DH+ protocol = PCCC ControlNet protocol = CIP
Ethernet protocol = CIP Ethernet protocol = CIP
Data Servers
RSLinx Enterprise Example Configurations
Number of Example Configurations
Controllers
(Shortcuts)
Recommended Data Servers

Digital and Tags defined 3
Analog within each
Instruction controller
based Alarms (Namespace) 2
RSLinx 1
Enterprise
Resource 10 Clients & 10 20 Clients & 20 30 Clients & 30
Tag Types Impact FactoryTalk Controllers Controllers Controllers
(Scalar, Array, Live Data
UDT) Clients Assumes: 10K Numeric Tags / Ctrl and 1K Strings Tags / Controller;
Each client requests 2K Numeric tags, 200 Stings, 500 Digital and
500 Analog Alarms.
Number of
Number of
Tags on Scan
Tag
References
Distribute the load across multiple
by Clients
RSLinx Enterprise Data Servers.
Data Servers
Sizing Summary
Application sizing is complex without a single answer for all possibilities
Use the example sizing for new applications

Note: Most applications will not require every client to request all tags from each
controller.
If unsure on sizing, contact the local RA office
64-bit operating systems can take advantage of higher memory limits, allowing for
higher application limits
ViewSE Clients can reduce tags in memory by unchecking Maintain Connections

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.
Data Servers
FactoryTalk Directory Data Server
Server
Server O/S
Server O/S
Domain Controllers
Server O/S
FactoryTalk Directory (1) RSLinx Enterprise
For the Ctl Sys Domain Server (1) RSLinx Classic
OPC Client
(1) FactoryTalk Gateway
RSLogix 5/500/5000
SLC SLC
DH+ PLC PLC
SLC
PLC
Data Servers
SY21 Optimize ControlLogix Performance for FactoryTalk Client Applications
SY24 Optimizing System Communications with RSLinx, FactoryTalk, and OPC
RA Knowledgebase
AID 507425 Rockwell Automation Data Server Decision Guide
AID 685789 - RSLinx Enterprise LogixDP Data Provider Information
FactoryTalk View SE
PUBLIC
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 (1+)
SQL Server (Express or Standard) (1+)
FactoryTalk Live Data Server (1+)
FactoryTalk Alarm Server (0+)
FactoryTalk View SE Client (1+)
FactoryTalk View SE Studio (1+)
FactoryTalk View SE Distributed
Component Recommendations
Production Applications 1 Network Distributed per FactoryTalk Directory
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)
50 per application (total mix of thick & thin clients)

Clients Extend this number using ViewPoint
FactoryTalk View SE Distributed
HMI Server Architecture
Can be co-located with the FactoryTalk Directory, but recommend separate hosts
Recommend independent hosts no clients or Engineering Workstation co-located

One HMI server per host
Except for testing
MSSQL Express instance must be co-located for tag database

Not supported for use with anything outside of the HMI server. e.g., it cannot be used for historical
logging
HMI tag utilization can be used to estimate server loading

Redundant servers do not equate to load-balancing
See AID 732555 FactoryTalk View SE Product Characterization
FactoryTalk View SE
Alarm Limits
Legacy / Classic HMI Alarming
40,000 total alarms per HMI Server
10,000 of which can be Analog
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
FactoryTalk View SE
Data and Alarm Server Architecture
RSLinx Enterprise Can be co-located with HMI server
No more than two different data servers per host
and RSLinx Classic Example: Classic and Enterprise installed on the same host
RSLinx Enterprise used as alarm server

Device-based Often co-located with HMI server
Alarming Some firmware versions not supported
Tag-based Often co-located with HMI and/or Data server

Alarming
FactoryTalk View SE
Server Redundant HMI/Data Server
Server O/S Server O/S
FactoryTalk Directory (1) HMI Server
Domain Controllers
FactoryTalk Activation (1) Tag-based Alarm Server
Server O/S (1) Data Server Data Server
Server
For the Ctl Sys Domain MSSQL Express Server (1) RSLinx Enterprise Server O/S
(1) RSLinx Enterprise
Engineering Workstation 5 Clients

RSLogix 5/500/5000
SLC SLC FactoryTalk View Studio
PLC PLC
FactoryTalk Clients
FactoryTalk View SE Client
FactoryTalk View SE
Extending with FactoryTalk ViewPoint
Using FactoryTalk ViewPoint, displays can be published for browser-based
viewing.
ViewPoint can be used to extend beyond 50 clients if mobile clients meet

the application needs.
Up to 25 extra ViewPoint clients are within the reference architecture guidelines.
Note:
ViewPoint uses only FactoryTalk Alarming, no Legacy/HMI Alarming
ActiveX controls and VBA cannot be used by ViewPoint displays
FactoryTalk View SE
Architecting FactoryTalk ViewPoint
Use a server Operating System
A separate host is recommended for larger applications (>10 clients) and/or

Redundancy
Can be co-located with FactoryTalk View SE HMI server
ViewPoint can service one application at a time

25 clients per 1 ViewPoint server
FactoryTalk ViewPoint Smart Devices and Tablets
Mobile O/S
Mobile Favorites
Redundant HMI/Data Server

FactoryTalk Directory Server O/S
Server (1) HMI Server
Server O/S (1) Tag-based Alarm Server
FactoryTalk Directory (1) Data Server
Domain Controllers FactoryTalk Activation (1) RSLinx Enterprise
Server
Server O/S MSSQL Express Server
For the Ctl Sys Domain
FactoryTalk ViewPoint
Server O/S
FactoryTalk ViewPoint Server

RSLogix 5/500/5000
PLC PLC
FactoryTalk Clients
FactoryTalk View SE
Dont 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 clients at a time.
50 Client recommendation is per application, not per server.

Consider ViewPoint for extending applications.
FactoryTalk View SE
VZ05 Architecting a Distributed HMI System
VZ06 FactoryTalk View Site Edition: Configuration and Maintenance Lab
VZ07 - FactoryTalk View Site Edition: Introductory Lab
VZ09 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 612506 Architecting FactoryTalk View Site Edition Network Distributed Systems
Rockwell Automation Literature Library

FactoryTalk View SE Popular Configuration Drawings
FactoryTalk Historian SE
PUBLIC
Application Options
FactoryTalk Directory Connectivity
FactoryTalk Historian ME can optionally use a Network FactoryTalk Directory.
Native (local to ME module) or FactoryTalk Security (Network FactoryTalk Directory) options.
FactoryTalk Historian SE only supported in the Network FactoryTalk Directory

FactoryTalk Historian SE does not support Local Directory environment.
FactoryTalk Historian EE does not use the FactoryTalk Services Platform.

A FactoryTalk Historian SE server can be configured as an enterprise level aggregator.
FactoryTalk Historian ME
Module Information
1756 Module can communicate across backplane or with
modules outside of its own chassis
Stores data collection on module

Can service up to 4 ControlLogix modules
(1 with high-speed collection)
Up to 2500 events/sec can be collected

Onboard memory storage must be accounted for
HIST1, ~4 hours @ 2500 events/sec
HIST2, ~14 hours @ 2500 events/sec
Long-term storage data can be forwarded to server Server
See AID 63082 FAQ: FactoryTalk Historian Machine Edition

Components
A typical FactoryTalk Historian SE system consists of the following software components
(or roles):
Network FactoryTalk Directory Server (FTD) (1*)
FactoryTalk Historian Server (1-2)
FactoryTalk Asset Framework Server (1)
FactoryTalk Historian Analysis Server (1)
Microsoft SQL Server (Express or Standard) (1)
FactoryTalk Historian Live Data Interface (1+)
FactoryTalk Live Data Server (1+)
FactoryTalk Historian Client (1+)
Component Limits
FactoryTalk Directory FactoryTalk Directory
Two (2) Historian SE Servers per

Or two (2) collectives consisting of 2 members each
FactoryTalk Historian FactoryTalk Historian SE FactoryTalk Historian FactoryTalk Historian SE
100,000 Events/sec SE Server Server SE Collective Collective
Events/sec
20 Clients maximum
Interface
before Compression
10,000 tags/sec
FactoryTalk View, 10,000 tags/sec

FactoryTalk VantagePoint, FactoryTalk Historian SE
Server
Client
Datalink, ProcessBook, ActiveView 10,000 tags/sec
Interface
10,000 tags/sec
See AID 49189 FactoryTalk Historian SE System Design Considerations

Interface Considerations
v5.0 Events/sec
after Exception
75,000 tags/sec
50,000 events/sec (40,000 redundant) Interface
10,000 tags/sec
v4.0 10,000 tags/sec
Server
Client
50,000 tags/sec 10,000 tags/sec
Interface
25,000 events/sec (20,000 redundant) 10,000 tags/sec
Total Interfaces per FactoryTalk Historian Server

50 interfaces / ME modules per server, 25 redundant
See AID 66997 FAQ: FactoryTalk Historian SE FactoryTalk Live Data Interface
Redundancy vs High Availability
System Thin Clients: FactoryTalk VantagePoint, Portal,
Management Rich Clients: FactoryTalk View, ProcessBook, Datalink,
Tools FactoryTalk Applications, Custom Application
PI SDK
Secondary Configuration Primary

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

Services If you require highly available data for
Services
Historian Interfaces reporting, then you need redundant
Historian Interfaces
servers (a Collective).
Component Architecture
Interfaces buffer data when the FactoryTalk Historian Server is absent
Co-locating with Historian Server not recommended
Optimal location with data server
FactoryTalk Historian SE Server
Server O/S
Historian SE Server can host Asset Framework (non-collective)
Asset Framework Server
MSSQL Express instance and Analysis Server included Server O/S
Analysis Server
Larger applications should split to independent server MSSQL Express
Equates to at least 3 server hosts:

FactoryTalk Directory Server (FTD) Server O/S
FactoryTalk Historian SE server

w/ FactoryTalk Historian SE Asset Framework Server (FTAF) FactoryTalk Historian
SE Server
Data Server
Server O/S
Server O/S Data Server
w/ MSSQL Express Asset Framework Server
Analysis Server
SE Interface
MSSQL Express
Data Server/Interface FactoryTalk Historian SE
Server
ME Module vs SE Interface
FactoryTalk Historian ME as an interface: Buffering
Mitigate against loss of communications from data

server to controller
High-speed collection
Historian ME FactoryTalk Historian
Data collection without local data server requirement SE Server
Cannot directly connect to Historian SE collective
Buffering
FactoryTalk Historian SE Live Data interface:

Native redundancy
Direct collective connectivity FactoryTalk Historian
Data Server & Interface
SE Server
Greater events/sec limit (2500 vs 25000-50000)
FAQs / Common Problems
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.)
FactoryTalk Directory Server O/S
Server (1) HMI Server
Server O/S (1) Tag-based Alarm Server
FactoryTalk Directory (1) Data Server
Domain Controllers FactoryTalk Activation (1) RSLinx Enterprise
Server
Server O/S FactoryTalk Historian
MSSQL Express Server Live Data Interface
For the Ctl Sys Domain
SE Server
Server O/S
FactoryTalk Historian Server
Analysis Server
MSSQL Express Server

RSLogix 5/500/5000
PLC PLC FactoryTalk Historian
SE Management Tool
FactoryTalk Clients
FactoryTalk Historian SE Client
IN06 FactoryTalk Historian SE: Architectures and Design Considerations
IN07 FactoryTalk Historian Site Edition: Basic Lab on Data Collection and Reporting
IN08 - FactoryTalk Historian Site Edition: Advanced Lab

AID 49189 FactoryTalk Historian SE System Design Considerations
AID 56070 FactoryTalk Historian SE Tips and Best Practices TOC
AID 60114 FAQ: FactoryTalk Historian SE
AID 66997 FAQ: FactoryTalk Historian SE Live Data Interface
AID 60277 FAQ: FactoryTalk Historian Collectives
AID 1041010 FAQ: FactoryTalk Historian SE Analysis Server
PUBLIC
Components
A typical FactoryTalk AssetCentre system consists of the following software components
(or roles):
Network FactoryTalk Directory Server (FTD) (1)
Microsoft SQL Server (1)
FactoryTalk AssetCentre Server (1)
FactoryTalk AssetCentre Agent (1+)
FactoryTalk AssetCentre Client (1+)
ProCalV5 Server (0-1)
ProCalV5 Client (0-1+)
Component Limits
One FactoryTalk AssetCentre Server
ProCalV5 Server (if using Calibration Management)
Fifteen FactoryTalk AssetCentre Agents

Up to 10 Agent Groups 1
Single agent services ~100 assets/ 12hrs 15
50
Fifty concurrent FactoryTalk AssetCentre
Clients
ProCalV5 Client (if using Calibration Management)
System Considerations
FactoryTalk Directory there can be only one!
A FactoryTalk AssetCentre Server can be linked with one and only one FactoryTalk Network Directory.
Microsoft SQL Server

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

See AID 106118 Determining the Necessary Number of 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.
Agent hosts should not be used as Engineering Workstations due to resource usage.
Client Location Considerations
Any FactoryTalk PC requiring audit/event FactoryTalk AssetCentre Client
functionality requires an AssetCentre Client

RSLogix / Logix Designer
FactoryTalk View Studio
Diagnostics

Client synchronizes with server

every 10 seconds
Diagnostics cached when disconnected from
server FactoryTalk AssetCentre Server
FactoryTalk AssetCentre Smart Devices and Tablets
Mobile O/S
Mobile Favorites

Server O/S
(1) HMI Server
FactoryTalk Directory ControlLogix
(1) Tag-based Alarm Server
Server (1) Data Server
Server O/S (1) RSLinx Enterprise
FactoryTalk Directory FactoryTalk Historian Live Data

Domain Controllers Interface ControlNet
Server FactoryTalk
Server O/S MSSQL Express Server
For the Ctl Sys Domain AssetCentre Client
FactoryTalk Engineering Workstation
AssetCentre Client RSLogix 5000
RSLinx Classic
FactoryTalk
Gateway? AssetCentre
Agent
FactoryTalk Historian FactoryTalk AssetCentre Server
SE Server Server O/S
Server O/S MSSQL Server Standard
Historian SE Server FactoryTalk AssetCentre Server
Asset Framework Server FactoryTalk AssetCentre Agent
Analysis Server FactoryTalk AssetCentre Client
MSSQL Express Server RSLinx Classic (no activation)
FactoryTalk RSLogix 5/500/5000 (no
AssetCentre Client activation)

RSLogix 5/500/5000
PLC PLC FactoryTalk Historian SE
Management Tool
FactoryTalk Clients
FactoryTalk AssetCentre Client
FactoryTalk Historian SE Client
FactoryTalk AssetCentre:
SY13 FactoryTalk AssetCentre: Overview
SY14 FactoryTalk AssetCentre: Introductory Hands-on Lab
SY15 FactoryTalk AssetCentre: Advanced Hands-on Lab

AID 57483 FactoryTalk AssetCentre System Design Considerations
AID 56049 FactoryTalk AssetCentre Tips and Best Practices TOC
AID 60057 Architecting FactoryTalk AssetCentre
RockwellAutomation.com
Introduction to FactoryTalk AssetCentre Architecture (video)
PUBLIC
FactoryTalk Services
FactoryTalk VantagePoint can function independently of a FactoryTalk Directory or
within a Network FactoryTalk Directory
Within a 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 & Events information can also be collected
from outside of the FactoryTalk Directory server.
Components
A typical FactoryTalk VantagePoint system includes the following components (or roles):
Network FactoryTalk Directory Server (FTD) (0-1)
Microsoft SQL Server (1)
MSSQL CLR (0-1)
Microsoft SharePoint Server w/Web Parts (0-1)
FactoryTalk VantagePoint Server (1)
FactoryTalk VantagePoint Mobile Site (1)
Data Source (1+)
FactoryTalk VantagePoint Client (1+)
FactoryTalk VantagePoint KPI App (0+)
System Scaling
SQL Server Express can be used in place of
SQL Server Standard Edition in red-dot systems.
Once there is a requirement for a separate SQL
instance, it is best to use SQL Server Standard SharePoint and
Edition. Excel Services
For large enterprise
Multiple FTVP systems that include
Systems SharePoint
Dedicated systems for Excel Services can be
Separated SQL Eventing, Report used to improve Excel
Server System Generation, rendering performance
Dashboards on the Portal
SQL Server installed on
separate server from
Stand-Alone VantagePoint
Systems
Data Source and
VantagePoint are
installed on separate
Co-Hosted servers
Systems VantagePoint has a
dedicated server (no
Data Source other applications)
installed on same
server as
VantagePoint
Component Architecture
General Best Practice system consists of 3 hosts:
A three host system is the
FactoryTalk VantagePoint Server Best Practice because it is the
(w/Mobile Site & FTD) most scalable and minimizes
Data Source the potential for resource
conflicts.
SQL Server
Smaller system components can be co-located: Generally, smaller systems

FactoryTalk VantagePoint Server and MSSQL combined have less than 10 clients.
(w/Mobile Site & FTD)
Data Source
Where can the FactoryTalk VantagePoint Server be co-located?
Best practice is to locate on an independent host
In small applications, its 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
Refer to Example Software Systems
FactoryTalk VantagePoint Smart Devices and Tablets
Mobile O/S
Mobile Favorites

Server O/S
Server (1) Tag-based Alarm Server
Server O/S (1) Data Server

FactoryTalk Directory (1) RSLinx Enterprise Windows 8 KPI

FactoryTalk Activation FactoryTalk Historian Live
Domain Controllers Windows 8.1
Server Data Interface
Server O/S MSSQL Express Server FactoryTalk AssetCentre Client
For the Ctl Sys Domain FactoryTalk AssetCentre
Client
FactoryTalk Historian FactoryTalk AssetCentre Server MSSQL Server
Server
SE Server Server O/S Server O/S
Server O/S
Server O/S MSSQL Server Standard Microsoft SQL
FactoryTalk Server Standard
Historian SE Server FactoryTalk AssetCentre Server VantagePoint Server
Asset Framework Server FactoryTalk AssetCentre Agent for FactoryTalk
Analysis Server FactoryTalk AssetCentre Client VantagePoint Portal
MSSQL Express Server RSLinx Classic (no activation) FactoryTalk
FactoryTalk AssetCentre RSLogix 5/500/5000 (no activation) VantagePoint Mobile
Client Excel 2010+

RSLogix 5/500/5000
Management Tool
FactoryTalk AssetCentre Client FactoryTalk Clients
FactoryTalk VantagePoint FactoryTalk View SE Client
Manager FactoryTalk Historian SE Client
Dashboard Builder FactoryTalk AssetCentre Client
Excel
IN02 - FactoryTalk VantagePoint EMI: Analytics in 50
IN04 FactoryTalk VantagePoint EMI Lab: Introduction to Analytics

AID 59149 FactoryTalk VantagePoint Tips and Best Practices TOC
AID 61808 - FAQ: FactoryTalk VantagePoint Frequently Asked Questions
AID 493349 FAQ: FactoryTalk Integration with Microsoft SharePoint
AID 520456 FAQ: Using SQL CLR with FactoryTalk VantagePoint EMI
AID 576677 FAQ: FactoryTalk VantagePoint EMI Windows 8 KPI
AID 613768 FAQ: FactoryTalk VantagePoint Mobile Site
Microsoft SQL Server: Briefly
PUBLIC
Microsoft SQL
How many servers are out there?
FactoryTalk View SE HMI Tag Database Server (2) Redundant HMI/Data Server
(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 Directory Server
FactoryTalk Alarms & Events Historical Logging FactoryTalk Directory Server

FactoryTalk Activation Server
FactoryTalk Historian SE Asset Framework Server

Server O/S
FactoryTalk AssetCentre Server

MSSQL Server Standard
FactoryTalk AssetCentre Agent
FactoryTalk VantagePoint Server MSSQL Server
Server FactoryTalk VantagePoint Server

FactoryTalk VantagePoint Portal
Excel
MSSQL
Server Standard
for FactoryTalk VantagePoint
Microsoft SQL
Consolidating Server Instances
Many instances can be consolidated:
FactoryTalk Alarms & Events (FTAE) History Microsoft SQL Server
FTAE Database
FactoryTalk Historian SE Application Framework (FTAF) Server FTAF Database
FTAC Database
FactoryTalk AssetCentre (FTAC) Server FTVP Database
FactoryTalk VantagePoint (FTVP) Server
MSSQL Standard and Express instances can be installed side-by-side on the same host
Consider SQL host resources when consolidating

Separate server recommended
SQL Express instance may not have enough resources to handle multiple applications
Microsoft SQL
Express vs Standard
Many applications requiring SQL now ship with Microsoft SQL Express
Intended for smaller systems and/or historical storage
SQL Express limits

10GB database size
1 CPU socket up to 4 cores
1GB memory per instance
Migrating from SQL Express to SQL Standard is fully supported
Knowledgebase Answer ID 942093

Microsoft SQL Server Smart Devices and Tablets
Mobile O/S
Mobile Favorites

Server O/S
Server (1) Tag-based Alarm Server
Server O/S (1) Data Server

FactoryTalk Directory (1) RSLinx Enterprise Windows 8 KPI
FactoryTalk Activation FactoryTalk Historian Live Data Windows 8.1
Domain Controllers Server Interface
Server O/S MSSQL Express Server FactoryTalk AssetCentre Client
For the Ctl Sys Domain FactoryTalk AssetCentre
Client
Server
Server O/S
Server O/S MSSQL Server Standard Microsoft SQL
Historian SE Server FactoryTalk AssetCentre Server VantagePoint Server
Asset Framework Server FactoryTalk AssetCentre Agent FactoryTalk
Analysis Server FactoryTalk AssetCentre Client MSSQL Server
VantagePoint Portal Express
MSSQL Express Server RSLinx Classic (no activation) FactoryTalk
FactoryTalk AssetCentre RSLogix 5/500/5000 (no activation) VantagePoint Mobile
Client Excel 2010+

RSLogix 5/500/5000
Management Tool
FactoryTalk VantagePoint Manager FactoryTalk View SE Client
Dashboard Builder FactoryTalk Historian SE Client
Excel 2010+ FactoryTalk AssetCentre Client
Microsoft SQL with FactoryTalk
AID 64647 FAQ: Using Microsoft SQL Server with Rockwell Software
FactoryTalk Products
Includes support information, memory best practice links, licensing FAQs
AID 49075 FactoryTalk Metrics MSSQL Backup
AID 59541 FactoryTalk AssetCentre MSSQL Backup & Restore
AID 62884 FactoryTalk VantagePoint MSSQL Backup
ThinManager and
Remote Desktop Services
PUBLIC
Traditional Automation Network
Dedicated PCs for dedicated applications.
Control Room Plant Floor Offices
Plant Floor
HMI HMI MES
ThinManager Solution
Replace PCs with Thin Clients and Manage Deployment Centrally with ThinManager
Control Room Plant Floor Offices
Office Grade
Thin Clients
Terminal to Terminal Shadowing
MultiSession
Tiling
Plant Floor Mobile Users

MultiSession
MultiMonitor
Instant Failover
Redundant
Ethernet
Camera Feeds
HMI / MES HMI / ERP / MES
ThinManager Securely Delivers Content
DELIVER CONNECTED Devices
ENTERPRISE CONTENT IN 3 WAYS Thin/Zero Clients
Mobile Devices
PCs
Content Types Users

HMI Individuals
Windows Based
MES User Groups

CMMS
ERP
Web Content
IP/USB Cameras Locations
Terminal Shadow Facility
PanelView Plus Lines/Areas
VNC
Assets/Devices
Safely and securely deliver Content to any combination of Device, User and Location.
MultiSession and Tiling
MultiSession and Tiling
Delivering more than one content type to a terminal
Example:
2 FactoryTalk View SE client instance
1 FactoryTalk View ME instance
1 PanelView Plus Terminal Shadow
Terminal Content
Terminal Content
MultiMonitor
MultiMonitor
Up to 5 monitors can be connected to a single terminal
1. Left monitor:
2 FactoryTalk View SE client instances
1 FactoryTalk View ME instance
1 PanelView Plus shadow
2. Right monitor
Terminal Content
Terminal Content
1 FactoryTalk VantagePoint instance

1 IP Camera
Virtual Screening
Virtual Screening
Evolution of MultiMonitor
Similar to tiling, but layout is configurable
Each Virtual Screen behaves like a physical display
Tiling is supported within each virtual screen
Can configure virtual screen swapping and full screen
Content overlays fully supported
Terminal Content
Terminal Content
ThinManager & RDS Redundant Remote Desktop Remote Desktop
Redundant
Smart Devices and Tablets
Mobile O/S
Mobile Favorites
Services Servers and ThinManager Servers
Server O/S Server O/S
Redundant HMI/Data Server FactoryTalk View SE Client
ThinManager Server
Server O/S
FactoryTalk Historian SE Client View SE Client
FactoryTalk
(1) HMI Server FactoryTalk AssetCentre Client Historian SE Client
FactoryTalk
FactoryTalk Directory (1) Tag-based Alarm Server RSLogix 5/500/5000
Server (1) Data Server RSLinx Classic RSLogix 5/500/5000
Server O/S (1) RSLinx Enterprise FactoryTalk View Studio
FactoryTalk View Studio Windows 8 KPI
FactoryTalk Directory FactoryTalk Historian Live Data FactoryTalk Historian SE
FactoryTalk Redundant
Historian SE ThinManager Windows 8.1
Domain Controllers FactoryTalk Activation Interface Management Tool Management Tool Servers
Server O/S Server
FactoryTalk AssetCentre Client FactoryTalk VantagePoint Server O/S
For the Ctl Sys Domain FactoryTalk AssetCentre Manager Manager (1) ThinManager Server
Client
Server
Server O/S
Server O/S FactoryTalk AssetCentre Server Microsoft SQL
Historian SE Server FactoryTalk AssetCentre Agent VantagePoint Server
Asset Framework Server FactoryTalk AssetCentre Client FactoryTalk
Analysis Server RSLinx Classic (no activation) VantagePoint Portal
FactoryTalk AssetCentre RSLogix 5/500/5000 (no activation) FactoryTalk
Client VantagePoint Mobile
Excel 2010+

RSLogix 5/500/5000
Management Tool
FactoryTalk VantagePoint Manager FactoryTalk View SE Client
Engineering Workstations Thin Clients
Dashboard Builder FactoryTalk Historian SE Client
Excel 2010+
Questions?
PUBLIC
www.rockwellautomation.com

Factory Talk

Uploaded by

Document Information

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

Factory Talk

Uploaded by

Copyright:

Available Formats

FactoryTalk Implementacin de Arquitecturas

Tendencias Tecnolgicas Lima Agosto 2017

FactoryTalk View Site Edition (SE)

Basic Microsoft SQL Server Considerations

ThinManager & Remote Desktop Services

Operating System compatibility

Patch qualification testing recorded on:

HMI Server Historian Server

FTD Server can host other system components:

Use a server operating system

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

No redundancy caching instead

FactoryTalk Directory servers do not communicate with each other.

Use OPC for 3rd Parties:

with Logix family controllers DDE Support

RSLinx Classic Required RSLinx Enterprise Supported

Recommended Data Servers

Use the example sizing for new applications

ViewSE Clients can reduce tags in memory by unchecking Maintain Connections

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)

50 per application (total mix of thick & thin clients)

Recommend independent hosts no clients or Engineering Workstation co-located

MSSQL Express instance must be co-located for tag database

HMI tag utilization can be used to estimate server loading

FactoryTalk Alarms & Events

RSLinx Enterprise used as alarm server

Tag-based Often co-located with HMI and/or Data server

Engineering Workstation 5 Clients

ViewPoint can be used to extend beyond 50 clients if mobile clients meet

A separate host is recommended for larger applications (>10 clients) and/or

ViewPoint can service one application at a time

Redundant HMI/Data Server

Engineering Workstation 5 Clients

Redundancy is not load balancing.

50 Client recommendation is per application, not per server.

Rockwell Automation Knowledgebase

Rockwell Automation Literature Library

FactoryTalk Historian SE only supported in the Network FactoryTalk Directory

FactoryTalk Historian EE does not use the FactoryTalk Services Platform.

Up to 2500 events/sec can be collected

See AID 63082 FAQ: FactoryTalk Historian Machine Edition

Two (2) Historian SE Servers per

FactoryTalk Historian FactoryTalk Historian SE FactoryTalk Historian FactoryTalk Historian SE

100,000 Events/sec SE Server Server SE Collective Collective

FactoryTalk View, 10,000 tags/sec

Datalink, ProcessBook, ActiveView 10,000 tags/sec

See AID 49189 FactoryTalk Historian SE System Design Considerations

v4.0 10,000 tags/sec

50,000 tags/sec 10,000 tags/sec

25,000 events/sec (20,000 redundant) 10,000 tags/sec

Total Interfaces per FactoryTalk Historian Server

Secondary Configuration Primary

Data Buffering Data Buffering

Equates to at least 3 server hosts:

FactoryTalk Directory Server (FTD) Server O/S

FactoryTalk Historian SE server

Mitigate against loss of communications from data

Cannot directly connect to Historian SE collective

FactoryTalk Historian SE Live Data interface:

Historian Interface buffering is effectively disabled when co-located with

Data Redundancy = Interfaces, Information High Availability = Collective.

Historical data is not natively stored in an open database (e.g., MSSQL.)