factorytalk system design considerations

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

PUBLIC INFORMATION

FactoryTalk® System Design Considerations

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

Agenda

Basic ControlLogixTM ConsiderationsBasic Network ConsiderationsBasic Host ConsiderationsFactoryTalk Services PlatformData ServersFactoryTalk View Site Edition (SE)FactoryTalk Historian SEFactoryTalk AssetCentreFactoryTalk VantagePoint

High Level discussion of the main considerations you should make when building a system:

Basic Microsoft SQL Server ConsiderationsThin Client ConnectivityVirtualization Basics


PUBLIC INFORMATION

Basic ControlLogix Considerations


ControlLogix ConsiderationsControlLogix in a FactoryTalk System

4

Retrieving data from a ControlLogix is dependent on the processor’s resources, as well as the FactoryTalk System configurations.

Controller Options Modules

Memory Available & Used Tag management (arrays & UDTs)

Connections Data Servers Messages

• Tasks– Continuous– Periodic– Priorities

• Scan Time– Time Slice– Its effect on overall software

performance – wire frames

• Redundancy

• Data Server Load Balancing

• Physical Limits


ControlLogix ConsiderationsContinuous 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 CPU time only after other tasks execute

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

Improper task configuration could prevent the controller from communicating with a data server!

5


For more information on… ControlLogix Considerations

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

6

Required reading!


PUBLIC INFORMATION

Basic Networking Considerations


Networking ConsiderationsComponents

What type of networking components will be used? Firewalls Switches Routers Wireless Cable types/lengths

What type of networking services will be used? Domain vs Workgroup DNS, DHCP

8

Layer 3 Router

Layer 3 Switch Stack

Layer 2 Switch

Drive

Controller

Controller

DriveHMI

Controller

Drive

HMI

Distributed I/ODistributed I/O

Level 0–2

HMI

Cell/Area #1(Redundant Star Topology)

Cell/Area #2(Ring Topology)

Cell/Area #3 (Bus Topology)

Cell/Area Zone

Manufacturing Zone Level 3

FactoryTalk Applications• View• VantagePoint• Historian• AssetCentre

Network Services• DNS, DHCP, syslog server• Network and security management

A network is only as good as the selected hardware!


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. The opening of ports within a firewall may

present a security concern, and an IT Security expert will need to be involved in the configuration.

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

9

Firewall

FactoryTalkClient

FactoryTalkServer


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 avoiduse 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).

10


Sample Architecture: Networks

CLx CLx CLxCLx

PLCSLC

Flex

PLCSLC

Flex

Firewall

Managed Ethernet Switch for Control System Network (CSN) – HMI/Ctrl Communications


Engineering Workstation

• RSLogix™ 5/500/5000• RSLinx® Classic

Internet


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

12


Firewall

CLx CLx CLxCLx

PLCSLC

Flex

PLCSLC

Flex



Internet


• RSLogix 5/500/5000

Domain Controllers•For the Ctl Sys Domain•W2K3 Server O/S•DNS/DHCP/WINS

PLC

Sample Architecture: Domain Controllers

13


For more information on…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

14


PUBLIC INFORMATION

Basic Host Considerations


Basic Host ConsiderationsSizing

“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)

16

HOST = computer or virtual machine hosting an operating system upon which applications may be installed.


Basic Host Considerations: Operating Systems

17

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


PUBLIC INFORMATION

FactoryTalk Services Platform Considerations


FactoryTalk Services PlatformOverview

19

Design & Configuration

Design & Configuration

Production ManagementProduction

ManagementData

ManagementData

ManagementQuality &

ComplianceQuality &

ComplianceAsset

ManagementAsset

ManagementPerformance

& VisibilityPerformance

& Visibility

Plant Wide Information

ProcessControlProcessControl

BatchControlBatch

ControlDrives

SystemsDrives

SystemsMotionControlMotionControl

DiscreteControlDiscreteControl SafetySafety

FactoryTalk® – Production DisciplinesFactoryTalk® – Production Disciplines

Control Systems

Logix – Control Disciplines

Dire

ctory

Secu

rity

Live D

ata

Diag

nosti

cs

Audit

Activ

ation

Histo

rical

Data

Ala

rms

and

Eve

nts

FactoryTalk Services Platform

“Build a suite of common services that can be shared by many applications”


FactoryTalk Services Platform 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.

20


FactoryTalk Services PlatformLocal 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.

21


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. A server OS is optimized to service network requests, which is a common function of a Network

FactoryTalk Directory. This server should not be a Windows domain controller.

22

There are exceptions to the dedicated PC recommendations, such as small, non-redundant systems.


FactoryTalk Services PlatformNetwork FactoryTalk Directory: What about Redundancy?

Client-side caching allows for operation independent of FactoryTalk Directory in the event of downtime.

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 Directory : AID 66352 - FactoryTalk View SE

Behavior when FactoryTalk Directory is Unavailable

23

HMI Client

CLX

HMI Server

FactoryTalk Directory Server

RSLinx Data Server

Windows Domain

Controller

HMI Client

CLX

cache


FactoryTalk Services PlatformMaintenance 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.

24


FactoryTalk Services PlatformFAQs / 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.25


Domain Controllers•For the Ctl Sys Domain•W2K8 Server O/S•DNS/DHCP/WINS FactoryTalk Directory

Server• FactoryTalk Directory• FactoryTalk Activation

Server

CLx CLx CLxCLx

PLCSLC

Flex

PLCSLC

Flex




• RSLogix 5/500/5000

Firewall

Sample Architecture: FactoryTalk Directory

26

Internet


For more information on…FactoryTalk Services Platform

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

27


PUBLIC INFORMATION

Data Server Considerations


Data ServersOptions

For Rockwell Automation Hardware (Controllers, drives, etc): RSLinx Classic RSLinx Enterprise FactoryTalk Gateway

Use OPC for 3rd Parties: Kepware Matrikon others

29


Data ServersRSLinx 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

30


• RSLinx Classic– Two total topics, one for

each path (ENet & CNet)– Alias topic references

both existing topics

Data ServersAlias Topics

31

EngineeringWorkstation

CNetENet

CLX

Topic 2Topic 1Alias Topic• RSLinx Enterprise

– Two total shortcuts, one for each path (ENet & CNet)

• Workstation communicating to ControlLogix via Ethernet and Controlnet


Data ServersComplex Paths

32

• RSLinx Classic Required– DH+ protocol = PCCC– Ethernet protocol = CIP

• RSLinx Enterprise Supported– ControlNet protocol = CIP– Ethernet protocol = CIP

Server #1

CLx CLx

DH+

PLC

SLC

CNet

ENet

PLC

SLC CLx


Data ServersWhat 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.

33

RSLinx Enterprise

FactoryTalk Gateway

OPCClient

Live Data OPC

CLX

CIP


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 ServersRSLinx Enterprise Sizing Considerations

34


Data ServersRSLinx 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

35


Data ServersControlLogix 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.

36


Data ServersFAQs / Common Errors

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

37


FirewallFactoryTalk DirectoryServer• FactoryTalk Directory• FactoryTalk Activation

Server


OPC Client

38

CLx CLx CLxCLx

PLCSLC

Flex

PLCSLC

Flex



Internet


• RSLogix 5/500/5000• RSLinx Classic

Data Server• (1) RSLinx Enterprise

DH+

PLC

SLC

• (1) RSLinx Classic

• (1) FactoryTalk Gateway

Sample Architecture: Data Servers


For more information on…Data Servers

RSTechED 2014 Collecting Data Efficiently in the Integrated Architecture Optimize ControlLogix Performance for FactoryTalk Client Applications

RA Knowledgebase AID 507425 – Rockwell Automation Data Server Decision Guide

39


PUBLIC INFORMATION

FactoryTalk View SE


FactoryTalk View SEApplication Options

Local Directory

41

Single HMI Station Network Directory Multiple Servers Remote Clients

FactoryTalk View SELocal Station

FactoryTalk View SENetwork Station

FactoryTalk View SENetwork Distributed


FactoryTalk View SEComponents

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+)

42


FactoryTalk View SENetwork 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

43


FactoryTalk View SE DistributedComponent 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

44


FactoryTalk View SE DistributedHMI 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

45


FactoryTalk View SEDatalog 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.

46


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

47


FactoryTalk View SE Distributed 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

48


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.

49

FactoryTalk View SE DistributedRedundancy

Server #1• HMI Server Primary• Data Server Primary

Server #2• HMI Server Secondary• Data Server Secondary

RedundantPair

Good Bad

Server #1• HMI Server Primary• Data Server Secondary

Server #2• HMI Server Secondary• Data Server Primary

RedundantPair

Note: Historical Alarm DB should not be located on a redundant host


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 SEFAQs / Common Errors

50


FactoryTalk DirectoryServer• FactoryTalk Directory• FactoryTalk Activation

Server


51

Sample Architecture: FactoryTalk View SE

CLx CLx CLxCLx

PLCSLC

Flex

PLCSLC

Flex

Firewall

Data Server• (1) RSLinx Enterprise

5 Clients

FactoryTalk View SE Clients

Primary Server• (1) HMI Server• (1) Tag-based Alarm Server • (1) Data Servers

• (1) RSLinx Enterprise



• MSSQL Express Server

Internet

• FactoryTalk View Studio

Engineering Workstation• RSLogix 5/500/5000• RSLinx Classic


For more information on…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

52


PUBLIC INFORMATION

FactoryTalk Historian


FactoryTalk HistorianApplication Types

54

MANAGEMENT

OPERATOR

SUPERVISOR


FactoryTalk Historian 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.55


FactoryTalk HistorianMachine 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

56

See AID 63082 - FAQ: FactoryTalk Historian Machine Edition


FactoryTalk Historian Site 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) 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+)

57


FactoryTalk Historian SEComponent Limits

Two (2) Historian SE Servers per FactoryTalk Directory Or two (2) collectives consisting of 2 members

each

100,000 Events/sec 50,000 pre-v4.00

20 Clients maximum FactoryTalk View,

FactoryTalk VantagePoint, DataLink, ProcessBook, ActiveView

58

Data Source(DCS, PLC,

etc.)

FactoryTalk Historian Server

Interface node

See AID 49189 – FactoryTalk Historian SE System Design Considerations


FactoryTalk Historian SEInterface Considerations

25,000 events/sec on one Interface Up to 50,000 defined tags 20,000 pre-v4.00 versions

20,000 events/sec on one redundant interface pair 15,000 pre-v4.00 versions

Total Interfaces per FactoryTalk Historian Server 50 interfaces per server, 25 redundant

59

Data Source(DCS, PLC,

etc.)

FactoryTalk Historian Server

Interface node

See AID 66997 – FAQ: FactoryTalk Historian SE FactoryTalk Live Data Interface


FactoryTalk Historian SE 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 Historian SE server Data Server/Interface

60

A three host system is the Best Practice because it is the most scalable and minimizes the potential for resource conflicts.


FactoryTalk Historian SERedundancy vs High Availability

61

System Management

Tools

Thin Clients: FactoryTalk VantagePoint, Portal, Rich Clients: FactoryTalk View, ProcessBook, DataLink, FactoryTalk

Applications, Custom Application…

PI SDK

SecondaryHistorian

ConfigurationChanges

Data BufferingServices

Historian Interfaces

Data BufferingServices

Historian Interfaces

SecondaryHistorian(s)

PrimaryHistorian

If you require highly available data for reporting, then you need redundant

servers (a Collective).

If you require minimal data loss, then you need redundant interface

nodes


FactoryTalk HistorianFAQs / Common Errors

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.)

62


Sample Architecture: FactoryTalk Historian

FactoryTalk DirectoryServer• FactoryTalk Directory

Server• FactoryTalk Activation

Server• MSSQL Express Server


CLx CLx CLxCLx

PLCSLC

Flex

PLCSLC

Flex

Firewall

5 Clients

Internet

Redundant HMI/Data Server• (1) HMI Server• (1) Tag-based Alarm Server • (1) Data Servers

• (1) RSLinx Enterprise

FactoryTalk HistorianSE Server• FactoryTalk Historian

Server

FactoryTalk Clients• FactoryTalk View SE Client• FactoryTalk Historian SE Client

• FactoryTalk Historian Live Data Interface• FactoryTalk Asset

Framework Server

• FactoryTalk Historian SEMgmt Tool

Engineering Workstation• RSLogix 5/500/5000• RSLinx Classic• FactoryTalk View Studio




For more information on…FactoryTalk Historian

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

RA Knowledgebase AID 49189 – FactoryTalk Historian SE System Design Considerations AID 56070: FactoryTalk Historian SE Tips and Best Practices TOC

64


PUBLIC INFORMATION

FactoryTalk AssetCentre


FactoryTalk AssetCentreComponents

A typical FactoryTalk AssetCentre system consists of the following software components (or roles): Network FactoryTalk Directory Server (FTD) (1) 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+)

66


FactoryTalk AssetCentreComponent Limits

67

One FactoryTalk AssetCentre Server ProCalV5 Server (if using Calibration

Management)

Five FactoryTalk AssetCentre Agents Single agent services ~100 assets/ 12hrs

Fifty concurrent FactoryTalk AssetCentre Clients

ProCalV5 Client (if using Calibration Management)

1

5

50


FactoryTalk AssetCentreCalibration Management Components

68


ServerEthernet

`

ProCalV5 Server

`


Server

• ProCalV5 Server – Recommended to be co-located with

FactoryTalk AssetCentre Server.– Contains all Calibration Management

information.– Links to FactoryTalk AssetCentre Server

process device assets.– Communicates with own database in

MSSQL Server.

• ProCalV5 Client– Must be co-located with FactoryTalk

AssetCentre Client.– Can only be accessed using FactoryTalk

AssetCentre Client.– Used to configure ProCalV5 server.


FactoryTalk AssetCentreSystem 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

69


FactoryTalk AssetCentreClient 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”

70


FactoryTalk AssetCentreFAQs / Common Errors

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…

71



Server

FactoryTalk Clients• FactoryTalk View SE Client• FactoryTalk Historian SE Client

72

Sample Architecture: FactoryTalk AssetCentre



Server• MSSQL Express Server• FactoryTalk Asset

Framework Server


CLx CLx CLxCLx

PLCSLC

Flex

PLCSLC

Flex

Firewall

5 Clients

Internet


• (1) RSLinx Enterprise• FactoryTalk Historian Live

Data Interface

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

activation)

• FactoryTalk AssetCentre Client



• FactoryTalk AssetCentre Client• FactoryTalk AssetCentre Client

Engineering Workstation• RSLogix 5/500/5000• RSLinx Classic• FactoryTalk View Studio• FactoryTalk Historian

Mgmt Tool




For more information on…FactoryTalk AssetCentre

RSTechED 2014 FactoryTalk AssetCentre: Introduction and Demonstration FactoryTalk AssetCentre Self-Paced Lab

RA Knowledgebase AID 57483 – FactoryTalk AssetCentre System Design Considerations AID 56049 – FactoryTalk AssetCentre Tips and Best Practices TOC AID 60057 – Architecting FactoryTalk AssetCentre

73


PUBLIC INFORMATION

FactoryTalk VantagePoint


FactoryTalk VantagePoint and the FactoryTalk Directory

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

75


FactoryTalk VantagePointComponents

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+)

76


FactoryTalk VantagePointSizing

77

Co-Hosted Systems• Data Source

installed on same server as VantagePoint

Stand-Alone Systems• Data Source and

VantagePoint are installed on separate servers

• VantagePoint has a dedicated server (no other applications)

Separated SQL Server System• SQL Server installed

on separate server from VantagePoint

Multiple FactoryTalk VantagePointSystems• Dedicated systems for

Eventing, Report Generation, Dashboards…

SharePoint and Excel Services• For large enterprise

systems that include SharePoint

• Excel Services can be used to improve Excel rendering performance on the Portal

Note that within this solution, the option to increase memory (RAM) and increase CPUs always exists as a method to improve system

performance.


FactoryTalk 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

78

A three host system is the Best Practice because it is the most scalable and minimizes the potential for resource conflicts.


MSSQL Server• MSSQL 2008

Server Standardfor FactoryTalk VantagePoint


activation)


Server• FactoryTalk AssetCentre

Client

FactoryTalk Clients• FactoryTalk View SE Client• FactoryTalk Historian SE Client • FactoryTalk AssetCentre Client

79

Sample Architecture: FactoryTalk VantagePoint




Framework Server• FactoryTalk

AssetCentre Client


CLx CLx CLxCLx

PLCSLC

Flex

PLCSLC

Flex

Firewall

5 Clients

Internet



Data Interface• FactoryTalk AssetCentre

Client

Engineering Workstation• RSLogix 5/500/5000• RSLinx Classic• FactoryTalk View Studio• FactoryTalk Historian

Mgmt Tool• FactoryTalk AssetCentre

Client

FactoryTalk VantagePoint Server• FactoryTalk VantagePoint

Server• FactoryTalk VantagePoint

Portal• Excel 2010+

• FactoryTalk VantagePoint Mgr

• Dashboard Builder• Excel 2010+




FactoryTalk VantagePointFAQs / Common Errors

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

80


For more information on…FactoryTalk VantagePoint

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

RA Knowledgebase 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

81


PUBLIC INFORMATION

Microsoft SQL Server: Briefly


Microsoft SQLHow many servers are out there?

FactoryTalk View SE HMI Tag Database Server (2) Express instances – must be co-located with HMI Server

FactoryTalk Alarms & Events Historical Logging

FactoryTalk Historian SE Asset Framework Server

FactoryTalk AssetCentre Server

FactoryTalk VantagePoint Server

83

FactoryTalk VantagePoint Server• FactoryTalk VantagePoint




activation)

FactoryTalk DirectoryServer• FactoryTalk Directory Server• FactoryTalk Activation


Framework Server• FactoryTalk AssetCentre

Client




Client


Server Standardfor FactoryTalk VantagePoint


Microsoft SQLConsolidating 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

84


Microsoft SQLDatabase 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

85



activation)



Client


86

Sample Architecture: Microsoft SQL Server

FactoryTalk DirectoryServer• FTD• FactoryTalk Activation



AssetCentre Client


CLx CLx CLxCLx

PLCSLC

Flex

PLCSLC

Flex

Firewall

5 Clients

Internet




Client

Engineering Workstation• RSLogix 5/500/5000• RSLinx Classic• FactoryTalk View Studio• FactoryTalk Historian Mgmt Tool• Factorytalk AssetCentre Client• FactoryTalk VantagePoint Mgr• Dashboard Builder• Excel 2010+

FactoryTalk VantagePoint Server• MSSQL 2008 Server Standard• FactoryTalk VantagePoint



• MSSQL 2008 Server Standard

• MSSQL 2008 Server Express

• MSSQL Express Server


Server Standard




PUBLIC INFORMATION

Thin Client Connectivity


Thin Client ConnectivityOptions

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

88


Thin Client ConnectivityRDS 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

89


Thin Client ConnectivityRDS 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.

90



Server Standard• MSSQL 2008

Server Express

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

activation)



Client


91

Sample Architecture: Remote Desktop Services Server

FactoryTalk DirectoryServer• FTD• FactoryTalk Activation

Server• FactoryTalk Asset


AssetCentre Client


CLx CLx CLxCLx

PLCSLC

Flex

PLCSLC

Flex

Firewall

5 Clients

Internet




Client

FactoryTalk VantagePoint Server• FT VantagePoint

Server• FT VantagePoint


Remote DesktopServices Hosts• FactoryTalk View SE Client• FactoryTalk Historian SE Client• FactoryTalk AssetCentre Client• Logix 5/500/5000• RSLinx Classic

RDS Client(s)



Engineering Workstation• RSLogix 5/500/5000• RSLinx Classic• FactoryTalk View Studio• FactoryTalk Historian Mgmt Tool• FactoryTalk AssetCentre Client• FactoryTalk VantagePoint Mgr• Dashboard Builder• 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

92



Server Standard• MSSQL 2008

Server Express

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

activation)



Client


93

Sample Architecture: Remote Desktop Services Server



Server• FactoryTalk Asset


AssetCentre Client


CLx CLx CLxCLx

PLCSLC

Flex

PLCSLC

Flex

Firewall

5 Clients

Internet




Client

FactoryTalk VantagePoint Server• FT VantagePoint

Server• FT VantagePoint


Remote Desktop Services Hosts• FactoryTalk View SE Client• FactoryTalk Historian SE Client• FactoryTalk AssetCentre Client• Logix 5/500/5000• RSLinx Classic

RDS Client(s)

Engineering Workstation• RSLogix 5/500/5000• RSLinx Classic• FactoryTalk View Studio• FactoryTalk Historian Mgmt Tool• FactoryTalk AssetCentre Client• FactoryTalk VantagePoint Mgr• Dashboard Builder• Excel 2010+

FactoryTalk Viewpoint Server• ViewPoint Server

FactoryTalk ViewPoint Client(s)




Thin Client ConnectivityLocal 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

94


For more information on…Thin Client Connectivity

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

RA Knowledgebase 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

95


PUBLIC INFORMATION

Virtualization


VirtualizationArchitecture 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

97


VirtualizationGeneral 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.

98


For more information on…Virtualization

RSTechED 2014 Introduction to VMware Product Suite: Virtualization Solutions Virtualization in Manufacturing Industries Building a Hardware Infrastructure for a Virtualized Solution

RA Knowledgebase AID 568026 - Using Rockwell Automation Software with VMware

Literature Library Virtualization for Process Automation Systems

99


We care what you think!

On the mobile app:1. Locate session using

Schedule or Agenda Builder2. Click on the thumbs up icon on

the lower right corner of the session detail

3. Complete survey4. Click the Submit Form button

100

Please take a couple minutes to complete a quick session survey to tell us how we’re doing.

2

3

4

1

Thank you!!


www.rsteched.com

Follow RSTechED on Facebook & Twitter.Connect with us on LinkedIn.

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.

PUBLIC INFORMATION

Questions?

factorytalk system design considerations

Technology

network components

network segment

rockwell products

main considerations

network speeds

network traffic

factorytalk thick clients

thick factorytalk clients