Rockwell Automation TechED 2017 - In06 - FactoryTalk Historian Site Edition Architectures and Design Considerations

IN06 - FactoryTalk Historian
Site Edition
Architectures and Design Considerations
Rob Entzminger
Senior Commercial Engineer
PUBLIC
Rockwell Automation TechED 2017 @ROKTechED #ROKTechED Copyright 2017 Rockwell Automation, Inc. All Rights Reserved. 1
Agenda
Related Sessions
FactoryTalk Historian Product Family Overview
FactoryTalk Historian SE v5.01 Whats New?
FactoryTalk Historian SE v5.01 Design Considerations
FactoryTalk Historian SE v5.01 Post Installation Activities
PUBLIC Rockwell Automation TechED 2017 @ROKTechED #ROKTechED Copyright 2017 Rockwell Automation, Inc. All Rights Reserved. 2
Enabling the Industrial Internet of Things (IIoT)
The Connected Enterprise

Customer Outcomes Faster Time
$
Lower Total Cost Improved Asset Enterprise
to Market of Ownership Utilization Risk Management
INFORMATION SOLUTIONS CAPABILITIES Cloud | On-Premise | Edge
SCALABLE EXECUTION SYSTEMS SCALABLE ANALYTICS MOBILITY & COLLABORATION CONNECTED SERVICES
AUTO DISCOVERY ZERO CONFIG DASHBOARDS ORCHESTRATION & WORKFLOW PEOPLE IN THE IIOT
ROCKWELL AUTOMATION IIoT INFRASTRUCTURE Integrated Architecture
SMART CONNECTED ASSETS EtherNet/IP Enabled Network
SENSORS & ACTUATORS INTELLIGENT MOTOR CONTROL CONTROLLERS MOBILE / DISPLAYS MACHINES & EQUIPMENT REMOTE ASSETS
PUBLIC Copyright 2017 Rockwell Automation, Inc. All Rights Reserved. 3

Related Sessions
Session Title Type
IN04 FactoryTalk VantagePoint EMI Lab: Introduction Lab
IN05 FactoryTalk VantagePoint EMI Lab: Advanced Analytics Lab
IN06 FactoryTalk Historian Site Edition: Architectures and Design Considerations Discussion
IN07 FactoryTalk Historian SE: Basic Lab on Data Collection and Reporting Lab
IN08 FactoryTalk Historian Site Edition: Advanced Lab Lab
Agenda
Related Sessions
Strategic Partnership
Leadership in Automation and Information Real-time Performance Management Software

Solutions Products
Solution Provider Technology Provider
Automation and Controls Expertise Data Historian and Context Experts
Solution Platform Product Platform
Distributed Historian Strategy
MANAGEMENT
SUPERVISOR
OPERATOR
The Right Information, at the Right Time, with the Right Fidelity
Agenda
Related Sessions
Historian SE 5.01 Release Summary
Design time
New Features Run time Enhancements Mobility
Enhancements
PI Server 2015 R2 SP1 First 5,000 tags can be VantagePoint Wizard for VantagePoint Mobile - new
Introduction of Asset from any data source selecting controller tags widgets
Framework and Event New data buffer sub- and automatically Indicator
Frames system for improved configuring Historian SE
Vertical Gauge
Office 2016 support performance of FTLD Use text filtering or UDT
Interface structure type to reduce Pie Chart
SQL Server 2014 support number of tags to search Map
Buffer Manager to monitor
Express Installation and troubleshoot the PI Builder to replace older
Additional Data Access Interface buffering tag configurator in Excel
Options (ODBC, Web API) AF/EF integration with System Explorer to
Bundled FactoryTalk VantagePoint model manage Asset Framework
VantagePoint 8.0
Updated PI Server Components
Incorporates the following components
Data Archive PI 2015 R2 SP1 (3.4.395.80)
AF2015R2 Server (2.7.5.7166)
AF2016 SP2 Client Install
FactoryTalk Historian Infrastructure
INFRASTRUCTURE
PI Data Link

PI ProcessBook
VISUALIZATION SUITE PI SYSTEM ACCESS
FACTORYTALK HISTORIAN SE SERVER
PI Notifications PI Event Frames PI Analytics PI AF PI Data Archive
PI INTERFACES OPTIMIZES DATA STORAGE
FactoryTalk Historian
System Components
FactoryTalk Historian Asset Framework
Basic Concepts
FactoryTalk Historian AF defines

AF Analytics your assets as Elements
FactoryTalk Historian AF defines

your assets meaningful data with
Asset Framework Database Attributes
An Attribute can be a static value, a
Relational databases
Servers
reference to a dynamic data value,
or a formula (calculated value)
Time series data
FactoryTalk Historian AF
standardizes your asset
definitions using Templates
Improved Interface Performance
Historian SE v5.1 Historian SE v4.0 Improvement
Max Tag Count / Interface 75,000 50,000 50%
Max Events / Interface 50,000 events / sec 25,000 events / sec 100%
Max Events / Redundant Interface 40,000 events / sec 20,000 events / sec 100%
New buffer sub-system increases performance
New Buffering Manager
Dashboard for configuration,

monitoring and
troubleshooting of buffering
interface
Express Installation/Upgrade
Automated installation of:

IIS (for VantagePoint EMI server)
SQL Express 2012 SP3
FactoryTalk Historian SE Server, Asset Framework
FactoryTalk VantagePoint EMI Server
Automated configuration of:

IIS
FactoryTalk Historian SE server and local FTLD Interface
FactoryTalk VantagePoint Connector
For small applications(<5,000 tags)

configured to run on a single computer
FactoryTalk Historian Data
Access Options
FactoryTalk Historian SE v5.01 3 catalog numbers
OLEDB Provider (SQL Access)

ODBC Driver (SQL Access)
OPC DA / HDA
JDBC (Java)
ACE (Advanced Computing Engine)
PI Notification
WEB API (now include REST services for FTH System data access)
Additional Changes FactoryTalk
Historian 5.01 Release
The following catalog items will be removed:
9518-HSE10K3ADD - Historian SE 10,000 points, 3rd Party
9518-HSE20K3ADD - Historian SE 20,000 points, 3rd Party
9518-HSE5003ADD(M) - Historian SE 500 points, 3rd Party
Published List of Third-Party Historian Interfaces will be limited to:

9518-OPCHDA Historian Interface for OPC HDA
9518-HINRELDB Historian Interface for ODBC
9518-HINUNIFILE Historian Interface Universal File Loader
* Additional interface accessible by contacting Product Management
Agenda
Related Sessions
Reference Material
Links to roughly 90% of the information contained in this presentation can be found in the Rockwell Automation
Knowledgebase in one Answer ID:
56070 FactoryTalk Historian SE Tips and Best Practices TOC.
The intent of this session and 56070 is to make a user aware of the numerous variables that must be
considered when designing a FactoryTalk Historian SE System.
FactoryTalk Historian SE Components
A typical FactoryTalk Historian SE system consists of the following software components (or
roles):
Network FactoryTalk Directory Server (FTD) (1)
FactoryTalk Historian Server (FTH Data Archive) (1)
FactoryTalk Asset Framework Server (FTH AF) (1)
SQL Server (Express or Standard) (1)
FactoryTalk Historian Live Data Interface(s) (1+)
FactoryTalk LiveData Server(s) (RSLE) (1+)
FactoryTalk Historian Client(s) (1+)
Internet Information Server (IIS)* (1)
* Only if using FT Security Services, FT ActiveView Client or FactoryTalk VantagePoint
Can all these roles coexist on a single computer?

FactoryTalk Historian SE Single Host
A single-host FactoryTalk Historian SE system is good (supported).
Express Installation option for a single computer solution
However, it is not recommend because:

All eggs in one basket
Potential for resource conflicts
No data collection buffering
No client server autonomy
Challenging to expand or modify
A single-host system that includes FactoryTalk VantagePoint is also supported within limits:
62869 - FactoryTalk Historian SE and FactoryTalk VantagePoint on a Single Host Computer
FactoryTalk Historian SE Two Host
A two-host FactoryTalk Historian SE system (ignoring clients) is better:
Host 1: FTD, Historian Server, Asset Framework Server, SQL Server
Host 2: Historian Live Data Interface and Data Server (RSLE)
A two-host system leverages data collection buffering (aka store and forward). However, its
scalability is limited and the potential for resource conflicts still exists on Host 1.
FactoryTalk Historian SE Three Host
A three-host FactoryTalk Historian SE system (ignoring clients) is best:
Host 1: FT Directory, FT Asset Framework Server, SQL Server (Express or Standard)
Host 2: FT Historian Server
Host 3: FT Historian LiveData Interface (FTLD) and Data Server (RSLE)
A three-host system is the Best Practice because it is the most scalable and minimizes the potential for
resource conflicts.
High Availability
System Thin Clients: FactoryTalk VantagePoint, Portal,
Management Rich Clients: FactoryTalk View, ProcessBook, DataLink,
Tools FactoryTalk Applications, Custom Application
SDK
If you require minimal data loss,

Secondary
then you need redundant interface
Secondary Primary
Historian Configuration Historian Historian(s)
Changes
nodes
Data Buffering Data Buffering

Services IfServices
you require highly available data for
Historian Interfaces reporting, then you need redundant
Historian Interfaces
servers (a Collective).
Interface Redundancy
Starting with a separation Primary Secondary
model FactoryTalk
Live Data Interface
FactoryTalk
Live Data Interface
Interface Node
Redundancy Primary Secondary
2- FTLD Interface RSLinx Enterprise

Data Server
RSLinx Enterprise
Data Server
Data Server
Redundancy
2- RSLinx Enterprise
Rockwell Rockwell Rockwell Rockwell Rockwell

CLX CLX CLX CLX CLX
Recommendation is to
have the Interface node Primary
FactoryTalk
Secondary
FactoryTalk
on the same computer

Live Data Interface Live Data Interface
Primary Secondary
as RSLinx Enterprise
RSLinx Enterprise RSLinx Enterprise
Data Server Data Server
Rockwell Rockwell Rockwell Rockwell Rockwell

CLX CLX CLX CLX CLX
One host should be designated as the Primary Data with the responsibility of the
Primary Interface Node and Primary Data Server. The second host is designated as
Secondary with the responsibility of the Secondary Interface Node Server and
Secondary Data Server.
Good Bad
Server #1 Server #2 Server #1 Server #2

Data Server Primary Data Server Secondary Data Server Primary Data Server Secondary
Interface Node Primary Interface Node Secondary Interface Node Secondary Interface Node Primary
Redundant Redundant
Pair Pair
Phase 1 Interface Failover
In either a Redundant
Phase 1 method
FactoryTalk View SE
requires write-back
Server or a redundant
to HMI system or a
controller
controller.
Phase 1 method requires write-back to HMI system or a controller.

Phase 2 Interface Failover
Phase 2 method uses a file share and is preferred over Phase 1.
FactoryTalk Historian SE Server Limits
Two (2) per FactoryTalk Directory FactoryTalk
Or two (2) Collective consisting of 2 members Historian
500,000 Tags Server
100,000 Events/sec (sum all events on all

interfaces)
50 Inbound Connections - this could be 50 Interface
FactoryTalk LiveData Interface (FTLD) nodes node
maximum or (25 Redundant pair) or 50

FactoryTalk ME modules Data Source
(DCS, PLC,
20 Clients maximum etc.)
FactoryTalk View, VantagePoint, DataLink,

ProcessBook, ActiveView
FactoryTalk Historian LiveData
Interface Limits
Tag Count on Interface FactoryTalk
75,000 Historian Server
Tags on scan
50,000 events/sec on one Interface
Tags on scan redundant interface
40,000 events/sec on one redundant Interface
interface pair node
Total Interfaces per FactoryTalk Historian Server

50 interfaces per server or 25 redundant Data Source
pairs
(DCS, PLC,
etc.)
New buffer sub system increases performance

Derived Tags (Calculations)
Performance Equations
Can be very CPU intensive
Make sure your Performance Equations are not too complicated
Consider the use of Offsets
Uses Archive values and is influenced by Exception and Compression
Consider potentially utilizing ACE for more complex tasks
ACE can be installed on a separate computer
Statistical Totalizers
Has a measurably less impact on resources
Uses Snapshot Values can be more accurate
Asset Framework
Analysis
Advanced Server Components
Depending on the server performance, some of those
components are recommended to be installed on a
separate server:
Advanced Computation Engine (ACE)
Data Access (OLEDB, ODBC, OPC DA, OPC HDA,
OLEDB Enterprise, Web API)
Notifications
These components typically require more

resources than you would want to co-locate on
the same server .
Virtualization Considerations
Virtualization is supported. For more information, refer to AID 30209 - Rockwell Software
in Virtual Environments.
However, the same architectural considerations apply:
1 guest image: good (supported), but not recommended
2 guest images: better, but should be on two physical hosts
3 guest images: best, but should be on two physical hosts (three preferred)
Host 1: Host 2:
Guest image Guest image
for Server for Interface
FactoryTalk Historian SE 5.01
Server
Operating Systems
Windows 2008 R2 SP1 (64 bit)
Windows 2012 R2 Standard (64 bit)
Windows 2012 Standard (64 bit)
Software
SQL Server 2012 (64 bit) SP3 Express or Standard Edition*
SQL Server 2014 (64 bit) Standard*
FactoryTalk Services
FTSP CPR 9 SR8.1 & SR9
FactoryTalk Activation 4.00.02
Microsoft Excel
Office 2013 (32 bit)
Office 2016 (32 bit)
FactoryTalk Historian SE 5.01
Interfaces
Operating Systems
Windows 2012 Standard (64 bit)
Windows 7 Pro SP1 (32 & 64 bit)
Windows 8.1 Pro (32 & 64 bit)

Windows 10 (64 bit)
Clients
Operating Systems
Windows 7 Pro SP1 (32 & 64 bit)
Windows 8.1 Pro (32 & 64 bit)
Windows 10 (64 bit)
Area Best Practices
Any 1 Area contains only 1 Server of any
type (HMI or Data)
Any 1 installation of a server instance is
referenced 1 time. Value is then shared
with the application.
Use proper load balancing of components
to keep steady state CPU utilization <40%
FactoryTalk Historian Scan Types
Advised Mode: Default Polled Mode: Poll from Device Mode:
Standard scan type Optimized Polled scan Highest load on data server (Data server is
Used for most applications Used to force records at a defined interval forced to check tag value every scan cycle)
Less load on data server Higher load on data server (polled every scan Used for triggers to make sure the exact value
Less communication cycle for updates) from the devices are recorded when triggered.
Basic Concept: Basic Concept: Basic Concept:

System subscribes to changes at a defined interval, System subscribes to changes at a defined interval, Tags are defined with triggers
i.e. one second i.e. one second. When triggered the system will read the current
The system will automatically inform system of If the is no change to the value, a record is created value directly from the device
changes to tags based on the defined interval. with the previous value and an new time stamp.
FactoryTalk Historian Client
What are the FactoryTalk Historian
clients?
FactoryTalk VantagePoint FactoryTalk Historian
Native FT Historian Integration
and Trending DataLink
Mobile Access Excel Add-In
Access to SE or ME
FactoryTalk View SE
Native Trending from FactoryTalk ProcessBook
Historian SE Advanced Analytics Client
Native Trending from FactoryTalk PI System Explorer
Historian ME
AF Configuration
TrendPro
FactoryTalk Historian Client
Considerations
When are these clients used?
FactoryTalk Historian DataLink
Is used for Excel reporting mainly when the reporting is only from
Historian. If multiple disparate data sources are required FactoryTalk
VantagePoint should be considered instead.
FactoryTalk Historian ProcessBook
Used typically for ad hoc reporting and especially for quality
investigation and optimization run by like QA personnel and Lean and
Six Sigma professionals.
Client Considerations
When are these clients used?
FactoryTalk VantagePoint
Is the client platform for multiple type of applications:
Portal
Dashboard
Reports
Mobile
Has native access to FactoryTalk Historian
Used for mainly all pre-configured content to the majority of users in a plant
Used with reporting from disparate data sources including FactoryTalk Historian
FactoryTalk View SE
Native integration optimally used with all FactoryTalk View SE installation and should be used instead of the
FactoryTalk View Datalog Models
IIS Internet Information Services
Internet Information Server (IIS) is a required component only for a computer hosting
ProcessBook displays using ActiveView. If ActiveView is being used, then this
computer may be the FactoryTalk Historian server, or it may be a separate, dedicated
web server. IIS is not required (and not recommended) for any other FactoryTalk
Historian SE computers (e.g., FactoryTalk LiveData servers, interface nodes, clients,
etc).
If using FactoryTalk View SE Clients to host ProcessBook displays, IIS is already a
requirement for FactoryTalk View and no extra IIS server would be required.
39618 - FactoryTalk View Site Edition IIS Handbook
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.
This is inherently bad for a distributed system that depends on remote
communications.
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.
898270 TCP/UDP ports used by Rockwell Automation products
Many other components (such as DCOM and MS authentication services)
assign ports at runtime (dynamic).
Architecture Concepts: Firewall 101
Firewalls DO the following:
Separate networks
Block traffic based on user, TCP/UDP
port number (the pipe) and
source/destination
Act with authentications models (for
example, Active Directory)
Firewalls DO NOT do any:
Virus blocking
Intrusion detection OR prevention
Use RDP Services to go through a Firewall
Post Release Patches
For post-release product patches, refer to:
900530 - Patch Roll-up for CPR9 SRx
63530 FactoryTalk Historian Patch TOC
63141 - FAQ: FactoryTalk Historian Site Edition
Default File Locations
Installation Manager files (includes log files):
C:\Program Files\Rockwell Software\FactoryTalk Historian\Installation Manager
Help files and additional documentation:
x86: C:\Program Files (x86)\Common Files\Rockwell\Help
x64: - None
Core program files:
x86: C:\Program Files (x86)\Rockwell Software\FactoryTalk Historian
x64: C:\Program Files\Rockwell Software\FactoryTalk Historian
Database (archive) files:
C:\Program Files\Rockwell Software\FactoryTalk Historian\Server\PI\Dat
Should be changed to a separate partition, RAID array or Storage Area Network (SAN). For more information, refer to 63428 - FactoryTalk
Historian SE: Moving and/or Deleting Archive Files
Disable virus scanning!
For more information refer to: 504345 - FactoryTalk Historian SE: Default Installation Paths and Environment
Variables
Time Synchronization
Time synchronization is vital in a FactoryTalk Historian
distributed system as it ensures accurate time stamps on
data, alarms and diagnostic logs
Using a Windows Domain makes time synchronization
automatic
NTP is not as precise as PTP or IEEE-1588
Using a workgroup requires configuration of the Windows
Time service (W32tm.exe)
Windows Time Service Tools and Settings
Windows 2003 Server Time Tools
Windows Time Service Technical Reference
Activate the Historian Server
Activating FactoryTalk Historian SE is unique in that activation must exist on the FT Activation
Server and be assigned to the Historian Server using the FT Administration Console:
For more information on FT Historian Activation, refer to:

60530 FAQ: FactoryTalk Historian SE Activation
For more information on FactoryTalk Activation, refer to:
516310 - Did You Know? Activations support is free on weekdays for all customers
High Availability Licensing & Activation
Interface
Does not cost extra. Interfaces are either installed non-redundant or redundant. FactoryTalk Historian Site Edition
server and interface node
Interfaces need to support redundancy for a redundant architecture.
redundancy:
You can mix redundant interfaces with non-redundant interface if needed.
Possibility of two redundant
interface nodes connected to one
Server a/k/a Collective either redundant or non
redundant data server
Requires two sets of identical tag licenses one for each server. i.e. the tag price
will double. Possibility of up to two redundant
FactoryTalk Historian servers with
This does not apply to Advance Server Option data coming from either
You cannot share a license between two servers, two separate licenses are redundant or non-redundant
needed. Interfaces
Example: A FactoryTalk Historian collective with 5000 tags, requires: two separate activations for 5000
tags each.
Buffering
Buffering is not enabled by default!
Configure and test buffering on all interface
nodes.
Consider where the buffer files are located
with the Buffer Sub System you can not limit the
size of the buffers
When a Collective is used there are two buffers
one for each Collective Member
For more information refer to:

56721 - FAQ: FactoryTalk Historian Site Edition Buffering
Disconnected Startup
Allows the Interface Node to start without a connection to the FactoryTalk
Historian Server
Disconnected startup is not enabled by default!
Enabling requires deleting 3 high speed scan classes (0.05, 0.1, & 0.25)
Configure and test disconnected startup on all interface nodes.

66883 - FactoryTalk Historian SE: FTLD Interface Disconnected Startup
Backup
Backup is not enabled by default!
Configure and test Backup on the Historian Server.
Test Restore too!
64559 Restoring a Complete FactoryTalk Historian SE Server from Backup

51487 - How to backup FactoryTalk Historian SE Server
PerfMon Interface Considerations
MCN Health Monitor includes the PerfMon Interface
FactoryTalk Historian includes 140 Performance Tags for monitoring the system's performance at no additional
cost. Performance tags provide insights into a number of performance management problems, including memory,
disk, and process management problems.
Unlike other interfaces, the PerfMon interface gets installed automatically
Customers need to modify the interface Batch file, ICU configuration and the Start/Stop batch files in the system to
be able to manage and change the interface configuration

59015 - FactoryTalk Historian SE and the PerfMon Interface.
Performance Monitoring
FactoryTalk Historian ships with performance monitoring components:
The Manufacturing Control Network (MCN) Health Monitor package is a set of data collectors (PI Interfaces) and client tools
that facilitates the collection, organization, and visualization of your IT performance data. The MCN Health Monitor is invaluable
for monitoring and managing devices such as:
Workstations & Servers
Firewalls
Control system applications
Network routers & switches
Communications network itself
Leveraging FactoryTalk Historian SE core technology and investment, MCN Health Monitor both minimizes the required
investment necessary to monitor IT infrastructures and increases the FactoryTalk Historian SE return on investment.

53786 - FactoryTalk Historian SE: Manufacturing Control Network (MCN) Health Monitor.
Windows Problem Reporting
There is a Problem Reporting feature included with Windows that can be used to
report computer and program errors to Microsoft. There is currently no benefit to
using this feature with Rockwell Software and disabling it is recommended.

42651- Instructions for disabling the Windows Error Reporting feature.
Working with
Asset Framework
and
FactoryTalk VantagePoint
Design Considerations
Asset Framework/Event Frame Integration
Overview
FactoryTalk Historian FactoryTalk VantagePoint
Asset Framework
VantagePoint
AF Import Tool
VantagePoint
EF Export Tool
VantagePoint EF Export Tool
Knowledgebase
1034454 - FactoryTalk VantagePoint EMI - Event Frame (EF) Export Tool
Exports Event Frames from the FT Historian into VantagePoint storage. It includes the custom VantagePoint types
for Event Frame definition, tag providers for visualization, EF queries, and EF mapped types.
FTVP
IncuityHistory
EFET
FTH EF
VantagePoint AF Import Tool
Knowledgebase
1034411 - FactoryTalk VantagePoint EMI - Asset Framework (AF) Import Tool
Imports the Element & Event Frame Templates into VantagePoint and builds the
equivalent object in the UPM. The tool will only support PI Points and Constants.
FactoryTalk VantagePoint Manager - Types
System Explorer - Templates
VantagePoint AF Import Tool
Knowledgebase
System Explorer - Elements From Tag
Providers
FactoryTalk VantagePoint Manager - UPM From UPM
Common Architecture Configurations
Design Considerations
Architectures
Microsoft FactoryTalk FactoryTalk AF Databas e

ShareP oint AF Server
VantagePoint Historian SE SQL Server
80 5450 5457
80 5459
Single Machine
FactoryTalk VantagePoint / SharePoint
FactoryTalk Historian Archive Data
FactoryTalk Historian AF Data
Architecture Microsoft
ShareP oint
FactoryTalk
VantagePoint
FactoryTalk
Historian EE
AF Server
AF Databas e
SQL Server
5450 TCP
Business Network
?? TCP
FTH EE
DMZ PI To PI
Interface
5450 TCP
Control Network
?? TCP
FactoryTalk
FactoryTalk Historian SE AF Databas e
VantagePoint AF Server SQL Server
Logix5550
RUN I/O
< > ET HERNET
Originator
POWER
Rs 232
QUALITY
Allen-Bradley
BAT OK
RXD TXD OK
Time Series Data

RUN REM PROG
Rockwell 1756-ME
Architecture
Control Network Business Domain
DMZ
Desktops and
PI Interface PI Server Data Access
Node Servers
Data Only Conduit
Originator
Time Series Data
Application Data
Architecture
Control Network Business Domain
Protected User
Domain DMZ
PI SCADA PI Server PI-to-PI PI Server

Interface
Originator
Time Series Data
Architecture
Complete A Survey
Please take a moment to complete the brief session survey
on our mobile app and let us know how were doing!
Download the ROKTechED app and login:
Username: Last name

Password: Email address used to register
Locate the session in the Schedule icon

Click on the Survey icon in the lower right corner of the session details
Complete survey & submit
Thank you!

Rockwell Automation TechED 2017 - In06 - FactoryTalk Historian Site Edition Architectures and Design Considerations

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Rockwell Automation TechED 2017 - In06 - FactoryTalk Historian Site Edition Architectures and Design Considerations

Hochgeladen von

Copyright:

Verfügbare Formate

IN06 - FactoryTalk Historian

FactoryTalk Historian Product Family Overview

FactoryTalk Historian SE v5.01 Whats New?

FactoryTalk Historian SE v5.01 Design Considerations

FactoryTalk Historian SE v5.01 Post Installation Activities

The Connected Enterprise

INFORMATION SOLUTIONS CAPABILITIES Cloud | On-Premise | Edge

ROCKWELL AUTOMATION IIoT INFRASTRUCTURE Integrated Architecture

SMART CONNECTED ASSETS EtherNet/IP Enabled Network

PUBLIC Copyright 2017 Rockwell Automation, Inc. All Rights Reserved. 3

IN04 FactoryTalk VantagePoint EMI Lab: Introduction Lab

IN05 FactoryTalk VantagePoint EMI Lab: Advanced Analytics Lab

IN08 FactoryTalk Historian Site Edition: Advanced Lab Lab

FactoryTalk Historian Product Family Overview

FactoryTalk Historian SE v5.01 Whats New?

FactoryTalk Historian SE v5.01 Design Considerations

FactoryTalk Historian SE v5.01 Post Installation Activities

Leadership in Automation and Information Real-time Performance Management Software

FactoryTalk Historian Product Family Overview

FactoryTalk Historian SE v5.01 Whats New?

FactoryTalk Historian SE v5.01 Design Considerations

FactoryTalk Historian SE v5.01 Post Installation Activities

VISUALIZATION SUITE PI SYSTEM ACCESS

FACTORYTALK HISTORIAN SE SERVER

PI Notifications PI Event Frames PI Analytics PI AF PI Data Archive

PI INTERFACES OPTIMIZES DATA STORAGE

FactoryTalk Historian AF defines

FactoryTalk Historian AF defines

Historian SE v5.1 Historian SE v4.0 Improvement

Max Tag Count / Interface 75,000 50,000 50%

New buffer sub-system increases performance

Dashboard for configuration,

Automated installation of:

Automated configuration of:

For small applications(<5,000 tags)

OLEDB Provider (SQL Access)

Published List of Third-Party Historian Interfaces will be limited to:

FactoryTalk Historian Product Family Overview

FactoryTalk Historian SE v5.01 Whats New?

FactoryTalk Historian SE v5.01 Design Considerations

FactoryTalk Historian SE v5.01 Post Installation Activities

Can all these roles coexist on a single computer?

However, it is not recommend because:

If you require minimal data loss,

Data Buffering Data Buffering

2- FTLD Interface RSLinx Enterprise

Rockwell Rockwell Rockwell Rockwell Rockwell

on the same computer

Rockwell Rockwell Rockwell Rockwell Rockwell

Server #1 Server #2 Server #1 Server #2

Phase 1 method requires write-back to HMI system or a controller.

Phase 2 method uses a file share and is preferred over Phase 1.

100,000 Events/sec (sum all events on all

FactoryTalk LiveData Interface (FTLD) nodes node

maximum or (25 Redundant pair) or 50

20 Clients maximum etc.)

FactoryTalk View, VantagePoint, DataLink,

Total Interfaces per FactoryTalk Historian Server

New buffer sub system increases performance

These components typically require more

Windows 7 Pro SP1 (32 & 64 bit)

Windows 8.1 Pro (32 & 64 bit)

Windows 8.1 Pro (32 & 64 bit)

Windows 10 (64 bit)