The following are the system requirements for FactoryTalk Historian SE version 7.01.00.

FactoryTalk Historian SE works within the system requirements of all Rockwell Automation software products. For the latest information regarding software platform support, refer to Product Compatibility & Download Center.

The hardware required with FactoryTalk Historian Site Edition depends on the demands an application places on the system. The greater the demand, the more powerful system is required. In any application, faster processors and more memory will result in better performance. In addition, there should always be sufficient disk space to provide virtual memory that is at least twice the size of the physical memory.

Product Compatibility

The table lists the minimum supported versions of Rockwell Automation products with which this version of FactoryTalk Historian SE is compatible:

Note:

• It is always considered best practice to install the latest patch rollups from the Rockwell Knowledgebase.
• For current software compatibility, refer to the Product Compatibility and Download Center (PCDC).

Operating system

Microsoft Excel requirements for PI Builder

PI Builder supports the following versions of Microsoft® Excel:

• Microsoft Excel 2019 (32 bit or 64 bit)
• Microsoft Excel 2016 (32 bit or 64 bit)
• Microsoft Excel 2013 (32 bit or 64 bit)
• Microsoft Excel 2010 SP2

This release of PI Builder supports the volume licensed Office (MSI install) and Office 365 (Click-to-Run install) desktop installations (32-Bit and 64-bit). However, Office 365's Office Online, accessible via a browser, is not supported. Please note that Office 365 is a streaming-based subscription service that will upgrade your version of Office in accordance with the newest releases. Therefore, it’s possible that whenever Microsoft introduces a new version of Office, Office365 may upgrade you to that version, which may have compatibility issues with the current versions of PI Builder.

SQL databases for FactoryTalk Historian Asset Framework

FactoryTalk Historian Asset Framework supports the following versions of Microsoft® SQL databases (64-bit):

• Microsoft SQL Server - Standard & Express
• Microsoft SQL Server 2019 CU3
• Microsoft SQL Server 2017
• Microsoft SQL 2016 (Microsoft KB 3164398 required)
• Microsoft SQL 2014 SP3

Required SQL Server components:

• Database Engine
• Agent (backup and replication)

Database requirements for FactoryTalk Historian Asset Framework

Database storage is consumed depending on the type and quantity of FactoryTalk Historian Asset Framework objects. The table below shows approximate database sizes of some representative Asset Framework systems.

SQL Server requirements

Required memory:

• 1 GB for databases with up to 50,000 elements.
• 4 GB for databases with up to 200,000 elements.

For databases with up to 1,000 elements, Asset Framework may be installed on the FactoryTalk Historian server.

For more information on the Microsoft SQL Server system requirements, refer to the Microsoft Development Network.

FactoryTalk Historian SE version 7.01.00 recognizes all existing activation strings (FHSE.XXX, FHSE3ADD.XXX, FHLD.XXX, and PTY3.XXX) as well as two new additional activation strings called FHIST.XXX and FHISTPY.2K. For more information, refer to the FactoryTalk Historian SE 7.01 Installation and Configuration Guide.

This version of FactoryTalk Historian SE has the following changes:

• .NET Framework 4.8 as FactoryTalk products' installation prerequisite: Installing FactoryTalk Services, and/or FactoryTalk Historian SE now requires that you have Microsoft .NET Framework 4.8 installed. Its presence/absence on the computer on which you are installing the aforementioned products is automatically detected during the installation.

A prerequisite for installing .NET Framework 4.8 on Microsoft Windows Server 2012 R2 and Microsoft  Windows 8.1 is that you have Microsoft April 2014 update rollup installed first. For details, see the Windows RT 8.1, Windows 8.1, and Windows Server 2012 R2 update: April 2014.

• FactoryTalk Services Platform (FTSP): The version of FTSP packaged with Historian 7.01 is FTSP 6.20 (CPR 9 SR 12).

• OSIsoft PI binaries

• PI Data Archive 2018 SP3 Patch1 version 3.4.435.604
• PI Asset Framework 2018 SP3 Patch 2 version 2.10.8.440
• PI Analysis Service 2018 SP3 version 2.10.6.195
• PI Notifications Service 2018 SP2 version 2.10.5.9050

• The versions of the OSIsoft PI binaries address security vulnerabilities listed in KB article PN1502.

• When Historian is upgraded to version 7.00.00, PI components shortcuts may not be located under Windows Start menu > Rockwell Software. First identified in FactoryTalk Historian SE version 7.00.00. [Jira 499306]
There is currently no workaround for this anomaly.

• The Advised type points with static values show persistent Bad Input values after briefly disconnecting the data source or restarting. First reported in version 6.00.00. [Jira 930461]
  

• Refreshing the Point Builder list which contains previously deleted PI point causes PI SMT to display an error and requires SMT to be reopened. First identified in FactoryTalk Historian SE version 7.00.00. [Jira 467639]
There is currently no workaround for this anomaly.
Corrected in FactoryTalk Historian SE version 9.00.00.

• If Historian is being installed on a Windows Server 2012 R2 environment by a user who does not have reboot privileges, .NET Framework will not install properly because it requires a reboot. First identified in FactoryTalk Historian SE version 6.00.00.
Please refer to AID 1075023 for a resolution or workaround for these issues.

• The point source limit shown in PI System Management Tool (SMT) may not be consistent with the Historian license point limit. First identified in FactoryTalk Historian SE version 7.00.00. [Jira 754561]
To solve this problem, restart PI License Manager service or force SMT to reconnect.

• In the Discovery Rule Editor, the user-defined rule does not take precedence over the default rule. First identified in FactoryTalk Historian SE version 7.00.00. [Jira 666256]
There is currently no workaround for this anomaly.

FactoryTalk Historian SE version 7.01.00 has no functional changes.

The followings are application notes for FactoryTalk Historian SE version 7.01.00:

Disk space requirements

• Prior to the installation of this version of FactoryTalk Historian SE, make sure that the machines on which you are going to install the product meet the following disk space requirements:

  Note: Apart from that, there must be at least 1GB of free space available on the default operating system drive (usually drive C) on the computer on which you are installing FactoryTalk Historian SE suites.

  The table lists the minimum disk space required for the temporary installation files of the individual suites of this version of FactoryTalk Historian SE.

  Suite	The minimum disk space required (in MB)
  FactoryTalk Historian Asset Framework Server	260
  FactoryTalk Historian SE Server	2,500
  FactoryTalk Historian Live Data Interface	645
  FactoryTalk Historian SE Management Tools	950
  FactoryTalk Historian Analysis Service	400

  The path to the temporary folder which stores the installation files is indicated by the TEMP system environment variable. The variable default value is C:\Users\<UserName>\AppData\Local\Temp\.

  The table lists the minimum disk space required for the installation and usage of the individual suites of this version of FactoryTalk Historian SE.

  Suite	The minimum disk space required (in MB)
  FactoryTalk Historian Asset Framework Server	230
  FactoryTalk Historian SE Server	21,000
  FactoryTalk Historian Live Data Interface	1,486
  FactoryTalk Historian SE Management Tools	690
  FactoryTalk Historian Analysis Service	400

  Note: If you intend to install any suite of FactoryTalk Historian SE on the same disk on which the temporary folder is located, the minimum disk space requirement for the installation will be the sum of the requirements for the temporary installation files and the suite.

Communication between the FactoryTalk Administration Console and FTLD interfaces

• The improvement in reliability and security introduced in this release of FactoryTalk Historian SE between the FactoryTalk Historian Live Data Interface and FactoryTalk Administration Console or FactoryTalk View Studio only exists when 7.01 components are installed on both computers (the Data Server and the Engineering Workstation).

  The FactoryTalk Historian Live Data Interfaces in versions from 3.0 to 4.01 do not contain the new buffer system and do not leverage the increased throughput that the FactoryTalk Historian SE 7.01.00 Live Data Interface has. The FactoryTalk Historian SE administration (such as creating points or configuring interfaces) should be performed only on either the FactoryTalk Historian SE 7.01.00 Server or the Engineering Workstation with FactoryTalk Historian SE 7.01.00 Management Tools installed.

  If you administer FactoryTalk Historian SE on the computers with the older versions (from 3.0 to 4.01) of FactoryTalk Historian Live Data Interfaces installed, from within the FactoryTalk Administration Console or FactoryTalk View Studio, the applications will crash.

Length limitations of backup and archive file paths

• When you set locations of backup and archive files in the System Management Tools make sure that:
• The total path to a backup / archive file contains no more than 255 characters.

  The total path consists of the path to the folder in which a file is located and the name of the file along with its file extension.

  Note: The system will not inform you that the path is too long.

• The path does not contain any of the following characters:

Character	Character names
&	Ampersand
<>	Angle brackets
*	Asterisk
:	Colon Note: This character is not allowed only in folder names. Using it in paths is correct.
{}	Curly brackets
#	Number sign
%	Percent sign
+	Plus sign
?	Question mark
"	Quotation mark
/	Slash
~	Tilde
|	Vertical bar (pipe)

• Folder names do not end with blank spaces.

• If the backup / archive files do not meet the requirements listed above, the backup / archive process may fail or be incomplete. It may be indicated by the following messages in the backup / archive history:
  • Backup was canceled.
  • The filename or extension is too long.
  • Backup of one or more components failed.

Documentation

• On the Installation media
  • There are the following locations on the FactoryTalk Historian SE installation media with the user documentation and documentation-related resources:
    • The Install FactoryTalk Historian Site Edition > Open Installation Instructions> Installation Instructions page. On this page you will find the following resources:
      • FactoryTalk Historian SE Installation Assistant
      • FactoryTalk Historian SE Installation and Configuration Guide
      • Adobe Reader required to open PDF files.
    • The Install FactoryTalk Historian Site Edition > Read Documentation > Documentation page. On this page you will find the following resources:
      • FactoryTalk Historian SE Installation and Configuration Guide
      • Historian SE Reference Guide
      • FactoryTalk Historian Live Data Interface User Guide
      • Historian SE Introduction to System Management Guide
      • FactoryTalk Historian SE Release Notes
      • Adobe Reader required to open PDF files.
      • A link to the Redist\Docs folder on the installation media that stores all the user documentation.
      • A link to the Rockwell Automation Literature Library.

• On the Local Hard Drive
  • To access the user documentation available on your computer, go to the following locations:
    • On a 32-bit operating system: C:\Program Files\CommonFiles\Rockwell\Help
    • On a 64-bit operating system: C:\Program Files (x86)\CommonFiles\Rockwell\Help
  • The Help folder contains one or more of the following subfolders, representing individual FactoryTalk Historian suites:
    • FactoryTalk Historian SE <version> Analysis Service
    • FactoryTalk Historian SE <version> Asset Framework
    • FactoryTalk Historian SE <version> Live Data Interface
    • FactoryTalk Historian SE <version> Management Tools
    • FactoryTalk Historian SE <version> Server
    • FactoryTalk Historian SE <version> Notifications Service

    Depending on the suite, the subfolders listed above may also contain the Advanced Server Options and/or the MCN Health Monitor folders.

    For details on the division of the user documentation for the individual suites, see the FactoryTalk Historian SE Installation and Configuration Guide, section "User documentation".

• In the Start Menu
  • Depending on which suite you have installed on your computer, the Start menu or the Start screen will contain one or more of the following links:
    • FactoryTalk Historian SE <version> Analysis Service documentation
    • FactoryTalk Historian SE <version> Asset Framework documentation
    • FactoryTalk Historian SE <version> Live Data Interface documentation
    • FactoryTalk Historian SE <version> Management Tools documentation
    • FactoryTalk Historian SE <version> Server documentation
    • FactoryTalk Historian SE <version> Notifications Service documentation
• The links refer to the user documentation folders detailed in the FactoryTalk Historian SE Installation and Configuration Guide, section "User documentation".

Note: If the PDF file does not open properly, disable Protected Mode in Adobe Reader (Edit > Preferences > Security (Enhanced) and uncheck the Enable Protected Mode at startup checkbox).

Adobe reader

• If Adobe Acrobat Reader is not set as the default application to open PDF files, you may not open Historian Documentations from the installation wizard.

  As a workaround, go to Control Panel > Programs and Features, right-click Adobe Reader and select Repair.

SQL upgrade

• When upgrading from FactoryTalk Historian SE version 4.00, 5.01, or 6.00 to version 7.00 or 7.01, the Asset Framework server upgrade may not be able to proceed.

To solve this problem, after upgrading SQL server, change the SQL compatibility level and then proceed Asset Framework server upgrade. To change compatibility level:

Cause:

• FactoryTalk Historian Asset Framework requires Microsoft® SQL 2014 SP3 or newer
• The SQL compatibility level designation must be changed accordingly.

Resolution:

After upgrading SQL server, change the SQL compatibility level and then proceed with the Asset Framework server upgrade. To change compatibility level designation to SQL Server 2014:

Method 1:

1. Open command prompt and type sqlcmd -U <username> -P <password> -S <serverName> -d "PIFD".

Note: If logon method is windows authentication, you can omit username and password.

2. Type ALTER DATABASE PIFD SET COMPATIBILITY_LEVEL=120.
3. Type Go.

To check the compatibility level, use the following command:

1. Type SELECT COMPATIBILITY_LEVEL FROM SYS.DATABASES WHERE NAME = 'PIFD'.
2. Type Go.

Method 2:

You can use SQL Server Management Studio (SSMS) to configure the compatibility level:

1. Open SSMS and connect to the appropriate instance of the SQL Server Database Engine.
2. Expand Databases.
3. Right-click the database PIFD, and then click Properties.
4. The Database Properties dialog box opens. In the Select a page pane, click Options.
5. The current compatibility level is displayed in the Compatibility level list box.

            Note: If the list box is blank, download and update SSMS to the latest version.

6. Change the Compatibility level list box to SQL Server 2014 (120) or newer.

   Note: To change compatibility level designation to SQL Server 2016 or higher, please reference the table below.

   Microsoft® SQL	Database Engine Version	Compatibility Level Designation
   SQL Server 2014	12	120
   SQL Server 2016	13	130
   SQL Server 2017	14	140
   SQL Server 2019	15	150