FactoryTalk Historian Site Edition Design Considerations

Agenda

FactoryTalk Historian Product Family Overview FactoryTalk Historian SE v3.00 – What’s New? FactoryTalk Historian SE v3.00 – Design Considerations FactoryTalk Historian SE v3.00 - Post Installation Activities

Copyright © 2012 Rockwell Automation, Inc. All rights reserved.

2

Strategic Partnership

 Leadership in Automation and Information Solutions  Solution Provider  Automation and Controls Expertise  Solution Platform

 Real-time Performance Management Software Products  Technology Provider  Data Historian and Context Experts  Product Platform

3 Copyright © 2012 Rockwell Automation, Inc. All rights reserved.Copyri

FactoryTalk Historian

MANAGEMENT

SUPERVISOR

OPERATOR

Copyright © 2012 Rockwell Automation, Inc. All rights reserved.

4

Agenda FactoryTalk Historian Product Family Overview FactoryTalk Historian SE v3.00 – Design Considerations FactoryTalk Historian SE v3. Inc.Post Installation Activities Copyright © 2012 Rockwell Automation. 5 .00 – What’s New? FactoryTalk Historian SE v3. All rights reserved.00 .

0 Bundled   Leverages Data Aggregation in Historian for improved performance Historian to Historian Tag Correlation  FactoryTalk Historian to Historian Interface  FactoryTalk Batch EVT Interface Copyright © 2012 Rockwell Automation. Inc. Web Services. OPC. OPC  Advance Computing Engine (ACE)   FTSP CPR9 SR5 & FactoryTalk VantagePoint EMI v4. All rights reserved.0?  New OSI PI Server PI Server 2010 R3 (64-bit)  Windows Integrated Security Model   Requires Asset Framework/SQL Server Express  Advanced Server Option Data Access Components – OLEDB. . JDBC.What’s New in FactoryTalk Historian SE v3.

00 .Post Installation Activities Copyright © 2012 Rockwell Automation.00 – What’s New? FactoryTalk Historian SE v3. All rights reserved.Agenda FactoryTalk Historian Product Family Overview FactoryTalk Historian SE v3. Inc. 7 .00 – Design Considerations FactoryTalk Historian SE v3.

All rights reserved.  The intent of this session (56070) is to make a user aware of the numerous variables that must be considered when designing a Historian SE System.Reference Material  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. 8 . Copyright © 2012 Rockwell Automation. Inc.

Inc.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 (1)  FactoryTalk Asset Framework Server (1)  SQL Server (Express or Standard) (1)  Internet Information Server (IIS) – if using FT ActiveView (1)  FactoryTalk Historian Live Data Interface(s) (1+)  FactoryTalk Live Data Server(s) (1+)  FactoryTalk Historian Client(s) (1+) Can all these roles coexist on a single computer? Copyright © 2012 Rockwell Automation. 9 . All rights reserved.

Inc. 10 .FactoryTalk Historian SE Single Host System A single host FactoryTalk Historian SE system is good (supported).  However.FactoryTalk Historian SE and FactoryTalk VantagePoint on a Single Host Computer Copyright © 2012 Rockwell Automation. All rights reserved. it is not recommend because:  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 .

All rights reserved. its scalability is limited and the potential for resource conflicts still exists on Host 1. Historian Server. Asset Framework Server. Inc. 11 . Copyright © 2012 Rockwell Automation. However. SQL Server  Host 2: Historian Live Data Interface and Data Server (RSLE) A two host system leverages data collection buffering (a/k/a store and forward).FactoryTalk Historian SE Two Host System A two host FactoryTalk Historian SE system (ignoring clients) is better:  Host 1: FTD.

Copyright © 2012 Rockwell Automation. Inc. SQL Server  Host 2: FT Historian Server  Host 3: FT Historian Live Data Interface 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. 12 .FactoryTalk Historian SE Three Host System A three host FactoryTalk Historian SE system (ignoring clients) is best:  Host 1: FT Directory. FT Asset Framework Server. All rights reserved.

DataLink. thenHistorian you need to specify redundant Interfaces Historian servers Data Buffering Services Copyright © 2012 Rockwell Automation. All rights reserved. Portal. Inc. Custom Application… Secondary Historian Configuration Changes Primary Historian If your customer Secondary wants redundancy. Rich Clients: FactoryTalk View. FactoryTalk Applications. then you need toHistorian(s) specify redundant interface nodes Data Buffering Services Historian Interfaces If your customer wants high availability. ProcessBook. 13 .Redundancy and High Availability System Management Tools PI SDK Thin Clients: FactoryTalk VantagePoint.

Inc. .Interface Redundancy Recommendation is to have the Interface node on the same computer as RSLinx Enterprise Copyright © 2012 Rockwell Automation. All rights reserved.

‘Phase 1’ Interface Failover Phase 1 method requires write-back to HMI system or a controller. All rights reserved. Inc. . Copyright © 2012 Rockwell Automation.

. Inc.‘Phase 2’ Interface Failover Phase 2 method uses a file share and is preferred over Phase 1. Copyright © 2012 Rockwell Automation. All rights reserved.

Copyri . Inc.High Availability Architecture 17 Copyright © 2012 Rockwell Automation. All rights reserved.

) FactoryTalk View. VantagePoint. 18 .Historian SE Server Limits  One (1) per FactoryTalk Directory  Or one (1) Collective consisting of 2 members FactoryTalk Historian Server  100. Inc. PLC.000 tags  50. ProcessBook. All rights reserved. etc.000 Events/sec (sum all events on all interfaces)  25 FactoryTalk Live Data Interface (FTLD) nodes maximum  20 Clients maximum  Interface node Data Source (DCS. ActiveView Copyright © 2012 Rockwell Automation. DataLink.

19 . PLC. Inc. All rights reserved.) non-redundant or redundant pairs Copyright © 2012 Rockwell Automation.000 events/sec on one redundant interface pair  Total Interfaces per FactoryTalk Historian Server  25 interfaces per server  Interface node Data Source (DCS.000 events/sec on one Interface FactoryTalk Historian Server  Tags on scan – redundant interface  15.Historian Live Data Interface Limits  Tags on scan  20. etc.

All rights reserved. Inc. 20 .Derived Tags  Performance Equations  Can be very CPU intensive  Make sure your Performance Equations are not too complicated  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 Copyright © 2012 Rockwell Automation.

some of those components are recommended to be installed on a separate server:  Advanced Computation Engine (ACE)  Data Access (OLEDB. 21 .Advance Server Components Depending on the server performance. OPC DA. Copyright © 2012 Rockwell Automation. Inc. OPC HDA) These components typically require more resources than you would want to co-locate on the same server . All rights reserved.

but not recommended  2 guest images: better. 22 . but should be on two physical hosts (three preferred) Host 1: Guest image for Server Host 2: Guest image for Interface Copyright © 2012 Rockwell Automation. Inc.  However.Virtualization Considerations  Virtualization is supported. but should be on two physical hosts  3 guest images: best. For more information. the same architectural considerations apply:  1 guest image: good (supported). All rights reserved. refer to AID 30209 Rockwell Software in Virtual Environments.

Windows XP Pro SP3 (32 bit)   Clients  Operating Systems   Windows 7 Pro SP1 (32 & 64 bit). Windows 2008 SP2 (32 & 64 bit). All rights reserved. Inc. Windows 2008 SP2 (32 & 64 bit).FactoryTalk Historian SE Product Requirements  Server   Operating Systems    Windows 2008 R2 SP1 (64 bit) SQL Server 2008 R2 (32/64 bit) Express or Standard Edition SQL Server 2005 SP4 (32/64 bit) Express or Standard Edition Software  Interfaces  Operating Systems Windows 2008 R2 SP1 (64 bit). Windows 2003 R2 SP2 (32 & 64 bit)  Windows 7 Pro SP1 (32 & 64 bit). Windows XP Pro SP3 (32 bit) Windows 2008 R2 SP1 (64 bit). 23 . Windows 2003 R2 SP2 (32 & 64 bit) Copyright © 2012 Rockwell Automation.

All rights reserved. 24 . The combination of Windows 2008 servers and Windows XP SP3 clients has been problematic with both Rockwell Software and third-party products. Inc.” For example. Windows XP clients should not be used with Windows 2008 servers. Copyright © 2012 Rockwell Automation.Operating System Considerations Interface Node – Server or Client OS   FactoryTalk Historian Live Data interfaces are only supported on Windows XP/2003/2008 family servers and client OS’s Interface Nodes are supported on both client and Server OS’s FactoryTalk Historian Clients are only supported on Windows XP / Win7 family client OS’s FactoryTalk Historian Clients – Client OS  As a general rule. servers and clients should be in the same Windows OS “vintage.

Inc. 25 . All rights reserved.Domain & Workgroup Configurations  Common requirements  Unique IP address  Unique computer names  Proper name resolution  Differences  PC configuration  User name authentication  Security  Connectivity Copyright © 2012 Rockwell Automation.

and  The server is referenced in all the client host files. Interface and Client  Which means you either have to specifically install a DNS server. where:  All clients are referenced in the server host file. Copyright © 2012 Rockwell Automation.Workgroup Considerations  Workgroups:  FactoryTalk Historian requires full name resolution to be working on  Server. 26 . Inc. All rights reserved. or  a manual host file has to be maintained on both FactoryTalk Historian server and FactoryTalk Historian clients.

 One less computer in network to maintain.  Recommended only for small FactoryTalk Historian SE applications where user accounts don’t change often. Copyright © 2012 Rockwell Automation.Decentralized administration  Workgroups Advantages:  No domain controller (Windows Server OS) to purchase. Inc. All rights reserved.  All users participating in the workgroup must be members of the Administrator’s group.Workgroup Workgroup .  Create the same set of user accounts and passwords on every computer in a FactoryTalk Historian SE application.  Workgroup Rules:  All computers participating in a single application must be members of the same Windows workgroup. 27 .

WINS  Recommended for larger FactoryTalk Historian SE applications. 28 . Copyright © 2012 Rockwell Automation. or environments with changing user accounts  Domain Rules:  For applications consisting of more than 10 computers.  The domain controller should be its own independent PC that does not contain any application software installations of any kind. DNS.Centralized administration  Domain Advantages:  Centralized administration  Automated name resolution when used with DHCP.  The FactoryTalk Historian SE Server and FactoryTalk Directory should not be installed on the same computer as the domain controller. All rights reserved. a domain controller is required. Inc.Domain Domain .

microsoft.  A domain controller should NOT refer to itself as the time keeper  3rd-party devices can exist within the domain controller to be the time keeper Copyright © 2012 Rockwell Automation.mspx The key sentence in this TechNote is “…Microsoft does not recommend running applications on computers configured as domain controllers. and certainly not applications that require more than Authenticated User privileges in order to run successfully. All rights reserved.com/technet/prodtechnol/windows2000serv/maintain/security/secdefs.”  Installation of any application software on a domain controller can have adverse affects on the network and system performance.  The following information comes from a Microsoft TechNet article: http://www. Inc. 29 .Domain Controller  Rockwell Software does not support running application software on computers configured as domain controllers.

Directory Limits  One Historian Server per Network FactoryTalk Directory (FTD)  The Local FactoryTalk Directory is not supported  Historian icons are located under:  System | Connections | Historical Data  FactoryTalk Live Data interfaces installed under the Historian they are connected to. Copyright © 2012 Rockwell Automation. All rights reserved. 30 . Inc.

31 . Inc. Value is then “shared” with the application. All rights reserved.  Use proper load balancing of components to keep steady state CPU utilization <40% Copyright © 2012 Rockwell Automation.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.

. All rights reserved.FactoryTalk Historian Client Considerations What are the FactoryTalk Historian clients?  FactoryTalk VantagePoint  Native FT Historian Integration and Trending  FactoryTalk View SE  Native Trending from FactoryTalk Historian  FactoryTalk Historian DataLink  Excel Add-In  FactoryTalk Historian ProcessBook  Advanced Analytics Client  FactoryTalk AlarmView and ProfileView Copyright © 2012 Rockwell Automation. Inc.

. Inc.Historian Client Considerations When are these clients used?  FactoryTalk VantagePoint  Is the client platform for multiple type of applications: Portal  Dashboard  Reports     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 Datalogger Copyright © 2012 Rockwell Automation. All rights reserved.

. Copyright © 2012 Rockwell Automation.Historian Client Considerations (con’t) When are these clients used?  FactoryTalk Historian DataLink  Is used for Excel reporting – mainly when the reporting is only from Historian. Inc.  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. If multiple disparate data sources are required – FactoryTalk VantagePoint should be considered instead. All rights reserved.

interface nodes. then this computer may be the FactoryTalk Historian server. 39618 . IIS is already a requirement for FactoryTalk View and no extra IIS server is required. IIS is not required (and not recommended) for any other FactoryTalk Historian SE computers (e. All rights reserved. 35 .IIS – Internet Information Services  Internet Information Server (IIS) is a required component only for a computer hosting ProcessBook displays using ActiveView.  If using FactoryTalk View SE Clients to host ProcessBook displays. dedicated web server.. or it may be a separate. Inc.g. etc). If ActiveView is being used. FactoryTalk Live Data servers. clients.FactoryTalk View Site Edition IIS Handbook Copyright © 2012 Rockwell Automation.

Thin Clients: No rotating media. Improve data security: Terminal Server allows you to focus your security measures on the server. wireless. Lower cost of ownership: A thin client typically consists only of the operating system and the TSAC client. small footprint. low maintenance for patches and such. Minimize downtime: Upgrade your entire FactoryTalk Historian SE installation with a single server-side operation. or virtual private network (VPN). small memory. Data Server and Interfaces Intranet/Internet Network  Benefits of using Terminal Server with FactoryTalk Historian SE      Increased network flexibility: Users gain access to a Terminal Server over a TCP/IP connection including Remote Access. the Internet. All rights reserved. Ethernet. wide area network (WAN). Copyright © 2012 Rockwell Automation.Using FactoryTalk Historian SE with Terminal Services FT Historian Client FT Historian Clients Zero Install Terminal Service Component with FT Historian Client Sessions inside Internet Explorer ` ` ` ` ` ` Windows 2003 Server Web Server Terminal Server Historian Client(s) Dedicated Process Network ` Factory Talk Directory FT Historian SE Servers. Inc. 36 .

 Since minimal software is needed on the client computer and all the processing is done on the terminal server. For this reason. WAN. VPN. wireless.Using FactoryTalk View SE with Windows 2003 Terminal Server While the focus of this document is FactoryTalk View SE. client computer hardware can be scaled down to reduce cost. No other software (not even a web browser) is required. these clients are known as “Thin” clients. Inc. Copyright © 2012 Rockwell Automation.Using FactoryTalk Historian SE with Terminal Services (con’t)  For a computer to be a Terminal Services client. 29919 . All rights reserved. it is also applicable to FactoryTalk Historian SE. or slow connect rate remote access software is used.  Terminal services is the preferred method for clients to communicate to the servers if a firewall. it only requires an operating system and the Terminal Services client software. 37 .

Inc. All rights reserved. 38 .00 .Post Installation Activities Copyright © 2012 Rockwell Automation.Agenda FactoryTalk Historian Product Family Overview FactoryTalk Historian SE v3.00 – Design Considerations FactoryTalk Historian SE v3.00 – What’s New? FactoryTalk Historian SE v3.

Copyright © 2012 Rockwell Automation. 39 .Post Release Patches  For any post-release product patches that have been made available. Inc. All rights reserved. refer to: 63530 – FactoryTalk Historian Patch TOC.

In a FactoryTalk Historian SE distributed system.microsoft.microsoft.exe) uses the Network Time Protocol (NTP) to synchronize computer clocks on the network.  Windows Time Service Tools and Settings http://technet2.mspx?mfr=true Copyright © 2012 Rockwell Automation. alarms and diagnostic logs.com/WindowsServer/en/library/ac86e77c-0be3-430aba0b-c2225506fc4f1033. time synchronization ensures accurate time stamps on data.com/windowsserver/en/library/b43a025f-cce2-4c82b3ea-3b95d482db3a1033. All rights reserved.mspx?mfr=true http://technet2.Time Synchronization  The Windows Time service (W32tm. Inc. 40 .

Instructions for disabling the Windows Error Reporting feature.Windows Error Reporting  There is an error-reporting feature included with Windows that can be used to report computer and program errors to Microsoft. For additional information refer to: 42651. Inc. Copyright © 2012 Rockwell Automation. and disabling it is recommended. All rights reserved. There is currently no benefit to using this feature in a Rockwell Software environment. 41 .

refer to:  35251 . refer to:  35376 . Inc. All rights reserved.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 additional information on FactoryTalk Activation.FactoryTalk Activation Server User Management Copyright © 2012 Rockwell Automation. 42 .FactoryTalk Activation Frequently Asked Questions  If planning to deploy a FactoryTalk Activation Server.

Questions? .