Proficy* Historian I MPORTANT P RODUCT I NFORMATION Version 5.5 June 2013
All rights reserved. No part of this publication may be reproduced in any form or by any electronic or mechanical means, including photocopying and recording, without permission in writing from GE Intelligent Platforms, Inc. Disclaimer of Warranties and Liability The information contained in this manual is believed to be accurate and reliable. However, GE Intelligent Platforms, Inc. assumes no responsibilities for any errors, omissions or inaccuracies whatsoever. Without limiting the foregoing, GE Intelligent Platforms, Inc. disclaims any and all warranties, expressed or implied, including the warranty of merchantability and fitness for a particular purpose, with respect to the information contained in this manual and the equipment or software described herein. The entire risk as to the quality and performance of such information, equipment and software, is upon the buyer or user. GE Intelligent Platforms, Inc. shall not be liable for any damages, including special or consequential damages, arising out of the user of such information, equipment and software, even if GE Intelligent Platforms, Inc. has been advised in advance of the possibility of such damages. The user of the information contained in the manual and the software described herein is subject to the GE Intelligent Platforms, Inc. standard license agreement, which must be executed by the buyer or user before the use of such information, equipment or software. Notice 2013 GE Intelligent Platforms, Inc. All rights reserved. *Trademark of GE Intelligent Platforms, Inc. Microsoft is a registered trademark of Microsoft Corporation, in the United States and/or other countries. All other brands or names are property of their respective holders. We want to hear from you. If you have comments, questions, or suggestions about our documentation, send them to the following email address: doc@ge.com
Table of Contents Proficy Historian 5.5 New Features... 6 User Defined Data Types... 6 Dynamically Sized Array Tags... 6 Enhanced Data Query Filtering... 6 Updated Operating System Support... 6 Permanent Rename and Permanent Delete of Tags... 6 New Calculation Modes... 7 New Query Modifiers... 7 New Comparison Modes... 7 New Sampling Mode... 7 Proficy Historian 5.5 Release Notes... 8 Installation and Upgrade Troubleshooting... 8 Upgrading from Historian 3.1 or greater... 8 Upgrading to Historian 5.5 on a Windows 64-bit Operating System... 9 Installing Proficy Historian 5.5... 9 Archive Backup Behavior... 9 Security Compatibility with Historian Install and Upgrade... 9 Installation Folders for Proficy Historian... 9 On a 32-bit Windows Operating System:... 9 Proficy Historian IHA (Historian Archive) Migration Tool... 10 Proficy Historian and Microsoft Excel... 11 Installing Excel Add-in for Excel 2007, Excel 2010(32-bit/64-bit) or Excel 2013... 11 Support for VMWare Products... 11 Best Practices for VMWare... 11 Suspended Images/Power Metered Images... 12 I/O Devices and Connections and VMware... 12
USB Controllers and VMware... 12 USB Devices, Historian, and VMware... 12 Additional VMware Notes... 12 Proficy Historian Alarm and Events Server with Microsoft SQL Server 2008... 13 Configuring the Proficy Historian OLE DB Provider Properties in a Linked Server... 13 Proficy Historian Alarm and Event Archive Migration... 13 Backing up Alarm and Event Data... 13 Migrating Historical Alarm and Event Data... 14 Enhanced Security by Enforcing Strict Authentication... 14 Adding Multiple Archives... 15 Browsing Tags from Historian Clients... 16 Throttling Store and Forward Buffer Flush... 16 Configuring the BufferFlushMultiplier... 16 Proficy Historian and Antivirus Software... 16 Proficy Historian and Microsoft Windows... 17 Windows Firewall Enabled by Default in Windows XP SP3, Vista, Server 2003, and Server 2008... 17 Optimizing Server Settings for Windows 2003 Server, or Windows 2008 Server... 17 Archiver Obtaining List of Domain Controllers... 17 Proficy Historian General Troubleshooting... 17 Receiving an ihconfigurationgetproperties Error... 18 User API Programs Not Freeing Up Memory... 18 Tag Rename... 18 Maximum Buffer Memory Size... 18 Differences between Proficy Historian and Proficy Historian for SCADA 5.0... 18 Upgrading from Proficy Historian for SCADA to 5.5 Plant Historian... 20 To upgrade Proficy Historian for SCADA to Plant Historian:... 20 Procedure for Updating the Historian License for the Proficy Mobility product to Plant Historian21
To update your Historian to Plant Historian:... 21 Command Line support for Alarm Migration Tool... 21 Command Line Switches (Case does not matter):... 22 EXAMPLES:... 22 Using Arrays and MultiField tag elements in Calculation, Server to Server Collectors.... 24 Using Arrays in the Calculation and Server to Server collectors... 24 Using Multi field Tags in the Calculation and Server to Server collectors... 24 Historian Archive Ingestion Service.... 24 Proficy Historian 5.5 System Requirements... 25 Hardware Requirements... 25 Guidelines for Determining Historian Server Size... 25 Example System for Sustained Event Rate*... 27 Recommended Historian Collector Configurations... 28 Recommended Historian Alarm and Event Archiver Configurations... 28 Hardware Requirements - Proficy Historian on Windows XP Embedded... 29 Software Requirements... 29 Compatibility with Other Proficy Products... 30
Proficy Historian 5.5 New Features User Defined Data Types Proficy Historian now gives you the ability to create user defined data types which include multiple fields of selected data types. You can then create Historian tags of that type. All the tag operations can be performed on this tag such as raw and calculated queries. For more information, refer to the User Defined Type topic in the Using the Historian Administrator e-book in the online help. Dynamically Sized Array Tags Proficy Historian now allows you to store a set of values with a single timestamp and quality and then read the elements back individually or as an array. For more information, refer to the Array tag topic in the Using the Historian Administrator e-book in the online help. Enhanced Data Query Filtering With a Filter Expression you can now enter complex filter conditions that instruct the Data Archiver to examine the collected data and return time ranges that match the condition so that those ranges can be queried further. For more information, refer to the Using Filter Expression topic in the Advanced Topics e-book in the online help. Updated Operating System Support Proficy Historian 5.5 supports running on Windows 8 and Windows Server 2012. Permanent Rename and Permanent Delete of Tags You can now efficiently manage your tags and memory by truly deleting or renaming tags to meet your current needs instead of aliasing them and hiding the tags. Truly renaming or deleting the tags that are no longer needed saves disk space and memory and makes the names available for re-use. If you do a Permanent Rename or Delete, the reference to the previous names are changed or deleted from the Config file, but the previously collected data does not get purged. For more information, refer to the Permanently Rename a Tag and Permanent Delete a Tag topics in the Using the Historian Administrator e-book.
New Calculation Modes Proficy Historian now has the following calculation modes that add more combinations and contexts for data retrieval: FirstRawValue/FirstRawTime retrieves the first good raw sample value or timestamp for a given time interval. LastRawValue/LastRawTime retrieves the last good raw sample value or timestamp for a given time interval. Tagstats returns multiple calculation modes for a tag in a single query. For more information, refer to the Calculation Modes topic in the Advanced Topics e-book. New Query Modifiers Proficy Historian adds three additional Query Modifiers that alter the behavior of Sampling and Calculation Modes to meet your retrieval requirements. INCLUDEBAD directs the Data Archiver to consider raw samples of bad data quality when computing calculation modes. FILTERINCLUDEBAD directs the Data Archiver to consider the values of bad quality data when determining the time ranges that match the filter condition. USEMASTERFIELDTIME returns raw values of all the field elements in a multifield type tag at the timestamp determined by the MasterField. For more information, refer to the Query Modifiers topic in the Advanced Topics e-book. New Comparison Modes Proficy Historian now allows you to do a bitwise comparison for a tag. By using bitwise comparison you can compare the binary values of the given filter tag with the bits specified in the condition. The Bitwise comparison modes are: AllBitSet (^) comparison mode returns True when the binary value of the Filter Tag is equal to all the bits in the condition. AnyBitSet (~) comparison mode returns True when the binary value of the Filter Tag is equal to any of the bits in the condition. AnyBitNotSet (!~) comparison mode returns True when the binary value of the Filter Tag is not equal to any one of the bits in the condition. AllBitNotSet (!^) comparison mode returns True when the binary value of the Filter Tag is not equal to all the bits in the condition. For more information, refer to the Using Filter Expression topic in the Advanced Topics e-book. New Sampling Mode Proficy Historian now gives you a new sampling mode which can be used on retrieval of data that has already
been collected in the arhive. RawByFilterToggle sampling mode is a form of filtered data query. A filtered data query returns data values for a particular time period whereas RawByFilterToggle sampling mode returns the time periods where the condition becomes TRUE or FALSE. For more information, refer to the Sampling Modes topic in the Advanced Topics e-book. Proficy Historian 5.5 Release Notes Installation and Upgrade Troubleshooting IMPORTANT: Historian 5.5 does not support FIX32 and CIMPLICITY native collectors running on the Hitorian server or with 5.5 client tools, but these collectors will still be able to connect and send data to the 5.5 server, provided they have the proper SIMs and configuration. You must un-install Historian 3.0 or 3.1, which contains FIX32 and CIMPLICITY native collectors, and then install Historian 5.5. Upgrading from Historian 3.1 or greater Before upgrading Historian, it is recommended that you follow these steps: 1. Stop the Historian Data Archiver service. 2. Make sure you back up all archive data files (*.iha), configuration files (*.ihc) and backup files. By default, you can find these files in the c:\proficy Historian Data\Archives folder. The upgrade process will update these existing files to the new version. These new files are not backward compatible with the older version of Historian. 3. Optionally, use the Excel Add-In to export your tag configuration for all tags. It is recommended that you export tags associated with each collector to a separate worksheet. 4. If you are using a Microsoft SQL Server Data Engine (MSDE) database, then the Historian installer will install SQL Server Express 2008 and migrate the MSDE data into SQL Server Express 2008 automatically. NOTES: Please stop all Proficy applications (ifix, CIMPLICTY, PlantApps) and any custom applications which read/write data from Historian, before upgrade. If you choose to upgrade Historian, then you must upgrade your Historian license key to the new Proficy Historian license key. For upgrading Proficy Historian from version 3.1 to 5.5, you must uninstall both the Historian 3.1 service packs and/or SIMs and base product manually (from Control Panel -> Add/Remove Programs) and then, run the Historian installer. For upgrading from Historian versions older than 3.1, you must uninstall the old product then install the newer version of Proficy Historian. During maintenance or upgrade on Proficy Historian install with SIM, you may be prompted with a Re-boot dialog after the SIM uninstall. Click 'No' on the Re-boot dialog and continue. Main installer will proceed and ask for reboot at the end.
Upgrading to Historian 5.5 on a Windows 64-bit Operating System If you are using the 32-bit Data Archiver and have created registry keys such as RouteInterfaceStautsMsg under the Data Archiver in a 64 bit WoW registry path "HKEY_LOCAL_MACHINE\SOFTWARE\ Wow64\Intellution, Inc.\iHistorian\Services\DataArchiver\, then you must manually re-create them under native 64-bit registry path "HKEY_LOCAL_MACHINE\SOFTWARE\Intellution, Inc.\iHistorian\Services\DataArchiver\. You can also delete all the Data Archiver related registry entries from the 64 bit WoW registry path. Installing Proficy Historian 5.5 Before installing Proficy Historian, stop all running Proficy Historian services by going to Administrative Tools, and then Services. The installation process for the Proficy Historian 5.5 should automatically uninstall your SIMs. However, the automatic uninstall of your SIMs may fail during the install if files are locked. An error will display indicating the file which is in use. You will be required to stop the services or applications locking the file, and then attempt the installation again. You can choose to manually uninstall your Historian SIMs prior to installing the Historian 5.5. To uninstall SIMs manually, you must first stop all Historian Services, then go into your systems Control Panel, click Add/Remove Programs, and remove those SIMs. It is recommended after any SIM uninstall to restart your system, if prompted. NOTE: When you start Proficy Historian, it may take a longer time to start an archiver depending on number of archives online, number of tags, and number of connections. Archive Backup Behavior If you back up an archive more than once, the backup tool will, by default, attempt to use the same name for the backup file and will detect that an archive with the same name already exists. Rename the backup archive file or move the original backup archive file from the target backup directory. Security Compatibility with Historian Install and Upgrade Proficy Historian offers an enhanced security mode called Strict Client and Strict Collector authentication. Both modes are disabled when upgrading Historian. This option enables you to connect and complete the installation regardless of the version of your clients and collectors. You can enable the feature after upgrade, if desired. Installation Folders for Proficy Historian On a 32-bit Windows Operating System: The default installation folder is: C:\Program Files\Proficy\Proficy Historian\ The archives, log files, and buffer files are installed to these locations: C:\Proficy Historian Data\Archives\ C:\Proficy Historian Data\BufferFiles\
C:\Proficy Historian Data\LogFiles\ The help files are installed to: C:\Program Files\Proficy\ProficyDoc\1033\Historian\ On a 64-bit Windows Operating System: The default destination folder for a 64-bit Historian Server is: C:\Program Files\Proficy\Proficy Historian\x64\Server directory. The default destination folder for all 32-bit components (such as collectors and APIs) is: C:\Program Files\Proficy\Proficy Historian\x86 directory The default archives, log files, and buffer files are and help are same as a 32-bit operating system. Be aware that when upgrading earlier versions of Proficy Historian, the Server, OLEDB, API, NonWebAdmin, Samples, and Online help installs to the new locations described above. IMPORTANT: If you have uninstalled a previous version of Proficy Historian and did not remove the archives, ensure you direct the new Historian to the previous install folder (for example, C:\Program Files\GE Fanuc\Proficy Historian\Archives\ ) so that the Historian install program will find the existing archives and configuration file. If you are rolling back to a previous versions of Historian, it is recommended to backup the Data Archives and Config file. NOTE: On a 64-bit Windows Operating System, all 32-bit components (such as collectors and APIs) related registry keys will be located under HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\\Intellution, Inc.\iHistorian\. For more information, refer to the Installing the Historian Server topic in the online help. Proficy Historian IHA (Historian Archive) Migration Tool Historian now allows you to migrate up to 30 years of old data. The Historian Archive Migration Tool is commonly used for: Merging archives to save space. Migrating archives from one server to another with different server names. Reducing large archives into smaller archives. For more information, refer Migration Tool section in Getting Started Guide e-book.
Proficy Historian and Microsoft Excel Installing Excel Add-in for Excel 2007, Excel 2010(32-bit/64-bit) or Excel 2013 Requirement: Make sure that Visual Basic for Applications is installed before installing the Excel Add-in for Excel 2007, 2010 or 2013. This is typically located under Office Shared Features in the Office 2007, 2010 or 2013 installation process. To install Excel Add-in for Excel 2007, 2010 or 2013, use the following steps: 1. In Excel 2007, click the Office button in the top left corner. o In Excel 2010,2013, click the File tab -> Options. 2. Click Options and then go to Add-Ins. 3. Make sure the drop-down list for Manage is set for Excel Add-ins, and click Go. 4. Select Proficy Historian Add-In for Excel 2003. For Excel 2007 and above select Proficy Historian Add-In and Proficy_Historian_Helper. If the installation is successful a new menu item appears under Add-Ins or as Proficy Historian ribbon. If it does not appear then you may need to shut down and restart Excel. If you receive an error such as: "This workbook has lost its VBA project, ActiveX controls and other programmability-related features " the most probable cause is that Visual Basic for Applications was not installed. Install this application by navigating to Office Shared Features through the Office 2007, 2010 or 2013 installation process. Support for VMWare Products Proficy Historian provides support for VMware ESXi Server version 5.0 and above. The virtualization capability provided by VMware lets you run multiple virtual machines on a single physical machine, with each virtual machine sharing the resources of that one physical computer. Please be aware that while we have tested VMware ESXi 5.0 and above, issues with the VMware software or the virtualized environment are outside the scope of GE Intelligent Platform's responsibility. You must use VMWare Compatibility Hardware and Software before installing Proficy Historian 5.5 Data Archiver on a Virtual Machine. For the current release, the only supported type of Proficy licensing for use with VMware is keyless (software) licensing. NOTE: VMware Player is also not supported. IMPORTANT: Advanced features of ESXi Server (such as VMotion, High Availability, and Clustering support) have not been tested with Proficy Historian. For information regarding VMWare's compatibility and its supported software and hardware environments, please visit: http://www.vmware.com/resources/guides.html Best Practices for VMWare To prevent disk growth during run time, make sure you pre-allocate the hard disk in your VMware image. If the VMware disk needs to grow at runtime because of IHA growth or creation, then the Data Archiver can be slowed. If there is not enough disk space on the host machine to grow the VMware disk, then the archiver may lose data.
Suspended Images/Power Metered Images ESXi servers have power meter functions and options as well as the ability to suspend images to conserve power. We do not recommend or support these functions due to the potential effects on the Guest operating system, specifically in regards to polling I/O and timely updates. I/O Devices and Connections and VMware There are a multitude of devices and methods of communications on the market. These devices may be used if you can successfully connect them from the virtual machine through the physical HOST, but we do not support the setup of that connection. Be aware that device drivers used to write to proprietary cards for the ESXi HOSTS as part of virtual device setup can cause issues. USB Controllers and VMware The USB controller has these limitations when using Historian and VMware: Minimum virtual hardware version 7 is required. Only one USB controller of each type can be added to a virtual machine. The USB arbitrator can monitor a maximum of 15 USB controllers. If your system includes an additional number of controllers and you connect USB devices to these controllers, the devices are not available to be passed through to a virtual machine. You must add a USB controller to a virtual machine before you can add a USB device. You must remove all USB devices from a virtual machine before you can remove the controller. USB Devices, Historian, and VMware USB devices have these limitations when using Historian and VMware: A virtual machine may have up to 20 USB devices attached to it, however each unique USB device can only be attached to one virtual machine at a time. Unsupported USB devices may not interact as expected with other ESXi features. Additional VMware Notes GE Intelligent Platforms cannot guarantee the performance of the Historian software in a virtualized environment due to the wide range of parameters associated with the hardware, configuration, memory settings, third-party software installations, and the number of virtual machines running all of which can affect performance. Therefore, GE Intelligent Platforms cannot provide support related to the performance of the Historian software running on a virtual machine if its determined that the issue is related to the virtual environment. Also, GE Intelligent Platforms does NOT provide support or troubleshoot a customer's virtual machine infrastructure. It is the responsibility of you, the customer, to ensure that the performance of the Historian software and any third-party applications (especially those not recommended by GE Intelligent Platforms) are adequate to meet the needs of your run mode environment. GE Intelligent Platforms does not support issues related to functionality that is not available as a result of running in a virtual machine infrastructure. Examples include the functionality of card level drivers such as those for the Genius family of drivers, the Allen-Bradley DH/DH+ drivers, the Cyberlogic's MBX Driver for the SA85 card, as well as functions requiring direct video access. Check with the vendor of your third-party application for support statements regarding that third-party
product's ability to run in a virtualized environment. For more detailed information regarding VMware specifications and requirements, please visit the VMware web site: http://www.vmware.com/resources/compatibility/search.php Proficy Historian Alarm and Events Server with Microsoft SQL Server 2008 If you choose to install the Alarm and Event Archiver then you may be prompted to restart your computer to complete the SQL Server Express 2008 and Plant Database installations. Configuring the Proficy Historian OLE DB Provider Properties in a Linked Server To configure the Proficy Historian OLE DB provider Properties, perform the following steps: 1. Expand the Providers folder which is located inside the Linked Servers folder in the Object Explorer. 2. Right-click the iholedb.ihistorian provider and select Properties. 3. Enable Supports 'Like' operator Option. NOTES: Select the Level Zero Only option only when older versions of SQL Server are used. For better performance while executing small queries, select the Allow in Process option. Clear the option if larger queries are to be executed. For configuring the Historian 64-bit OLE DB provider as a linked server, the Allow in Process option is mandatory. Proficy Historian Alarm and Event Archive Migration If you are upgrading to the newest version of Historian and you have already collected alarms, you can migrate the Historical Alarm and Event data after upgrading to Proficy Historian 5.5. Alarms are not available for retrieval until they are migrated. New alarms collected with the new version of Proficy Historian will be available immediately. Before migrating alarm and event data, ensure that you have backed up the data. To migrate your alarms into the new alarm database, you must do a backup of the old alarms and restore them into the new database. The backup can be done before upgrade using the Historian Administrator or it can be done after upgrade using the Proficy Alarm Database Migration Tool on the start menu. Backing up Alarm and Event Data To back up the Alarm and Event Data, perform the following steps:
1. Click the Backup Existing Alarms and Events tab. 2. In the Time Range section, in the From and To fields, set the start time and end time. You may need to migrate small time periods if you have many alarms. If you need to migrate the alarms in blocks of time, do the oldest alarms first. 3. In the Database Name field, enter the name of the database from which you have to backup the data. Typically, this will be the same as the SQL Server you are currently using. 4. Select either windows or SQL server authentication by selecting the Use Windows Authentication or Use SQL Authentication options. 5. In the User Id and Password fields, enter the login credentials. Be sure to use a user name with permission to connect and backup alarms. 6. In Backup Folder Path field, give the absolute path, including file name, to store the backed up alarms. For example, c:\temp\march2010.bak. Provide the path to place the backup folder on the local computer and if your SQL server is running on a remote computer, enter a path that exists on the remote computer. 7. Click the Test Connection button to check that the source database is active and the information is accurate. The Begin Backup button is activated. 8. Click the Begin Backup button to backup the alarms and when the backup is complete, you will get a count of rows backed up. Migrating Historical Alarm and Event Data To make the backed up alarms available for retrieval, you have to write them into the current alarm database. To migrate Historical Alarms and Events to the latest version of Proficy Historian, perform the following steps: 1. Click the Migrate Alarms and Events Backup tab. 2. In Backup File Path field, provide the location of the file containing the backup. If your server is running on a remote computer, enter a path that exists on the remote computer. 3. In the Database section, in the SQL Server Instance Name field, enter the server name. In the Database Name field, enter the name of the database to which you have to migrate the data. Click the Test Connection button to check that the database is active and the information is accurate. TIP: You can find this information in the registry under: HKEY_LOCAL_MACHINE\SOFTWARE\Intellution, Inc.\iHistorian\Services\AlarmArchiver. 4. Select either windows or SQL server authentication by selecting Use Windows Authentication or Use SQL Authentication options. 5. In the User Id and Password fields, enter the login credentials. Be sure to enter an account with permission to restore alarms. 6. Click the Test Connection button to check that the database is active and the information is accurate. The Begin Migration button is activated and the alarm data is restored. 7. Click the Begin Migration button to migrate the data. Enhanced Security by Enforcing Strict Authentication Proficy Historian comes with enhanced security features to control access and protect user account credentials. For more information, refer to the Implementing Strict Authentication topic in the online help. SIMs are available for pre- 5.5 versions of Historian that can allow clients and collectors to connect to 5.5 Data Archiver even when the Enforce Strict security options are enabled. For example, an Excel Add-In running on Historian 4.0 will be able to connect to a 5.5 Data Archiver with Enforce Strict Client Authentication set to enabled. Or, a Historian 3.5 OPC collector can connect even when Enforce Strict Collector Authentication is enabled. The ability to connect is subject to the same rules as 5.5 clients and collectors. The account used to
connect must be known at the Data Archiver computer. The following table highlights the SIMs that apply to pre-5.5 versions of Proficy Historian. Historian Version SIM 5.0 IH50_SIM5.exe or newer 4.5 IH45_SIM12.exe or newer 4.0 IH40_SIM23.exe or newer 3.5 IH35_SIM20.exe or newer 3.0 Check the Historian SIM download section of the GlobalCare web site. 3.1 Check the Historian SIM download section of the GlobalCare web site. Installing SIMs may help other Proficy products connect but you should refer to the support site for each product to get the latest information. For more information, refer to the Implementing Strict Authentication topic in the online help. Adding Multiple Archives If you are creating multiple archives on a remote machine, then you must ensure that you have enough hard disk space on that machine. The Allocate Space slider does not display a remote machine's hard disk space. In other words, if you are creating multiple archives on a remote machine, you must ignore the percentage of available disk space will be used message displayed by the Allocate Space slider. If you receive the error message Runtime error 330 Invalid Property Value" while creating multiple archives on a remote machine, it is probably because you do not have enough hard disk space on that machine. When you click OK on the error message, Historian Administrator may disappear. You must now clean up the remote machine's hard disk space and restart the Historian Administrator.
Browsing Tags from Historian Clients By default, the Historian clients can return a maximum of 100K tags at a time. If the Historian clients are capable of retrieving more than 100K tags, then you can configure the maximum tags the search should return by adding the "MaxTagsToRetrieve" registry key. For more information, refer to the Browsing Tags from Historian Clients topic in the online help. Throttling Store and Forward Buffer Flush Store and forward buffering is a key feature of Historian collectors. It prevents data loss during planned or unplanned network outage between a collector and Historian server. If the collector is disconnected from the archiver for several hours or days, many megabytes of data can be buffered and must be delivered by the collector to the Data Archiver upon reconnect. Since all data is sent from the collector to the archiver in time order, the design goal has been to catch up to real time as quickly as possible by sending data as fast as possible. If this is not the desired behavior because you want to limit the network load on a slow, shared Wide Area Network (WAN) or you want to limit the CPU load on the Data Archiver caused by the incoming data, you can configure the collector to throttle the data it is sending. NOTE: Throttling Store and Forward does not affect the alarm and events collector. Configuring the BufferFlushMultiplier Configuring the throttle is easy, but due to modifying a key in the registry, this should be done with caution. A DWORD registry key called BufferFlushMultiplier is present under each collector under: HKey_Local_Machine\Software\Intellution, Inc.\iHistorian\Services\YOUR_COLLECTOR_TYPE. To slow the store and forward throttling, enter a value of 2 in the registry on the BufferFlushMultiplier key. To disable throttling, set the value to 0 or delete the registry value. The 2 means that the collector should never send data at more than 2 times its normal rate. This limits network and CPU load, but because data is sent in time order, you are not able to retrieve near current time historical data until the throttled flush is complete. Proficy Historian and Antivirus Software It is recommended that antivirus software be configured to exclude Historian archive and ihc files from antivirus scans, as this may interfere with server operation.
Proficy Historian and Microsoft Windows Windows Firewall Enabled by Default in Windows XP SP3, Vista, Server 2003, and Server 2008 If you install Proficy Historian on a Windows XP system, you will be prompted to allow Proficy Historian to reconfigure the Windows Firewall. If you answer Yes, Historian will be added to the firewall's exception list and set to Enabled. If you answer No, Historian will be added to the list and set to Disabled. You can change this setting through the Windows Firewall control panel at any time. Optimizing Server Settings for Windows 2003 Server, or Windows 2008 Server If you are running Historian on a Windows 2003 Server or Windows 2008 Server computer, do not set your File and Printer Sharing for the Server optimization options to Maximum Data Throughput for File Sharing. The Maximize Data Throughput for File Sharing setting in File and Printer Sharing for Microsoft Networks Properties controls the system cache size and allows the cache to grow very large. This could cause excessive paging when dealing with large files and might interfere with applications like Historian. It is recommended that you select the Maximum Data Throughput for Network Applications. To view or change your Server Optimization settings on Windows 2003 or Windows 2008 servers: 1. Open the Control Panel. 2. Double-click the Network and Dial-Up Connections icon. The Network and Dial-up Connections dialog box appears. 3. Right-click the Local Area Connection Properties icon and select Properties. 4. Select the File and Printer Sharing for Microsoft Networks component and click the Properties button. 5. Ensure that the Maximize Data Throughput for Network Applications options is selected. 6. Click OK. For more information on changing the Server Service properties, refer to the Microsoft Knowledge Base article Q228766. Archiver Obtaining List of Domain Controllers If the archiver is configured to use domain group security, the data archiver obtains the list of primary and backup domain controllers at archiver startup. If a domain controller is not available at that time or if you add new domain controllers, they are not seen by the archiver until the next time the archiver is restarted.for example, if your backup domain controller was not available on archiver startup, the archiver will not fail over to the backup domain controller for user authentication. For more information, refer "Working with Security" section in Online Help. Proficy Historian General Troubleshooting IMPORTANT: Before you start to troubleshoot any performance-related issue, it is important first to set correct expectations. If you installed Proficy Historian on a computer that only meets the minimum hardware requirements, but the computer does not meet the recommended hardware requirements, you may be unable to make a noticeable improvement to the performance of Proficy Historian unless you upgrade the hardware on the computer.
Receiving an ihconfigurationgetproperties Error If you receive a single ihconfigurationgetproperties[-2] error in the collector.log file, the error most likely occurred as a result of the collector connecting and querying for changes in the tag database immediately, getting a timeout, and then immediately querying again and succeeding. User API Programs Not Freeing Up Memory User API Programs built with anything other than Visual Studio.NET should be modified to call ihufreeptr() to free any memory pointers returned by the User API. Do not free these pointers using free() in your application or you can risk memory corruption. Tag Rename Whenever you rename a tag, only the active tag name (that is, the new tag name) will be visible in the Tags list on the Historian Administrator Tag Maintenance screen. You can rename tags multiple times, but only the latest active tag name will be visible in the Tags list. You can also retrieve the data using any alias (that is, the new or old tag names). However, the Tag Maintenance screen will display only an active tag name (that is, the new tag name). Whenever you change or copy a tag name, the information about the old tag name, new tag name, and time stamps are all recorded in the audit trail. Maximum Buffer Memory Size You can specify the maximum memory buffer size that an archiver queues can take. By default, memory buffer size is 100MB. Differences between Proficy Historian and Proficy Historian for SCADA 5.0 The following table highlights the different components supported by Proficy Historian and Proficy Historian for SCADA 5.0 Compenents Supported Proficy Historian Proficy Historian for SCADA 5.0 Historian Server Yes Yes Historian Administrator Yes Yes Historian Client Tools Yes Yes
Compenents Supported Proficy Historian Proficy Historian for SCADA 5.0 ifix Collector Yes Yes OPC Collector Yes Yes Server to Server Distributor Yes Yes Historian Excel Add-in Yes Yes Client Access API Yes Yes Alarm Event Archiver Yes Not Available Calculation Collector Yes Not Available File Collector Yes Not Available ifix Alarm Collector Yes Not Available OPC Alarm Collector Yes Not Available ServerToServer Collector Yes Not Available Simulation Collector Yes Not Available
Compenents Supported Proficy Historian Proficy Historian for SCADA 5.0 OSI PI Collector and Distributor Yes Not Available Incoming Remote Collector Connection Yes Not Available Collector ToolKit Yes Not Available Windows Performance Collector Yes Not Available Upgrading from Proficy Historian for SCADA to 5.5 Plant Historian If you are converting from Proficy Historian for SCADA to 5.5 Plant Historian, you must change your tags from SCADA data store to Historical data store, if your Plant Historian license does not have any SCADA data stores or tags. This is because, the Data Archiver will shutdown at startup due to licensing and you will not have the opportunity to change the tags in the Historian Administrator. If you change the entire SCADA data store into a Historical Data Store then all the tags will become historical tags that have no time-limit on collection. To upgrade Proficy Historian for SCADA to Plant Historian: 1. Purchase a license for the Plant Historian. 2. Upgrade your software to Proficy Historian. 3. Stop the Data Archiver service. 4. Apply your new Historian license key with the Historical Tags. Make sure the new license has enough historical tags to hold all tags the from SCADA Historian because you have to convert all the tags. You can see the licensed tag counts in the Proficy Common License Viewer. Here, you can view only the tag counts for Proficy Historian product and not for the Proficy SCADA Historian product. 5. In the command prompt, change the directory to the location of the ihdataarchiver.exe. For example: cd C:\Program Files\Proficy\Proficy Historian\Server on 32 bit operating system. 6. In the command prompt run the following command line: ihdataarchiver.exe UpgradeScadaToHistorical [NewDataStoreName] The UpgradeScadaToHistorical keyword tells the Data Archiver to convert the current SCADABuffer to a Historical Data Store.The new name for this historical store is specified following the keyword UpgradeScadaToHistorical. For example: ihdataarchiver.exe UpgradeScadaToHistoricalUserBuffer will convert the scada buffer and name the new DataStore "UserBuffer".
7. Start the Data Archiver service. If the conversion was successful, you can start your Data Archiver and run the Historian Administrator as long as you have enough Historical tags. If there are any errors you can view them from the Data Archiverlogfile. Procedure for Updating the Historian License for the Proficy Mobility product to Plant Historian If you are using Proficy Mobile to display data from Proficy Historian 5.5 or above your Historian license is limited to a certain amount of data. You can purchase a full Proficy Historian license and update your license key. For example, if you had a 30-day buffer for data, you can change this to unlimited data with the Plant Historian, so that the data is not overwritten after the 30-day buffer is reached. When the license is upgraded you will need to convert your rotational (SCADA) data store to a user data store by performing the following steps so that all tags become historical tags that have no time limit on collection. To update your Historian to Plant Historian: 1. Shut down the Data Archiver. 2. Apply your new Historian license key with Historical Tags.Make sure the new license has enough historical tags to hold all tags. You cannot upgrade only some of the tags.you have to upgrade all the tags. You can see the licensed tag counts in the Proficy Common License Viewer. 3. From the command prompt, change the directory to the location of the ihdataarchiver.exe. For example: cd C:\Program Files\Proficy\Proficy Historian\Server 4. From the command prompt run the following command line: ihdataarchiver.exeupgradescadatohistorical [NewDataStoreName] or if you are running a 64 bit operating system, run the 64 bit Data Archiver: ihdataarchiver_x64.exe UpgradeScadaToHistorical [NewDataStoreName] The UpgradeScadaToHistorical keyword tells the Data Archiver to convert the current SCADABuffer to a Historical Data Store.The new name for this historical store is specified following the keyword UpgradeScadaToHistorical. For example: ihdataarchiver.exeupgradescadatohistoricalhistoricalbuffer will convert the SCADA buffer and name the new data store. 5. Start the Data Archiver. If the conversion was successful, you can start your Data Archiver as long as you have enough Historical tags. If there are any errors you can view them from the Data Archiverlogfile. For More information, refer Knowledge Base Articles on the GE Intelligent Platforms support site: http://support.ge-ip.com/. Command Line support for Alarm Migration Tool If you are using Alarm Migration Tool using command line you can use the following switches.
Command Line Switches (Case does not matter): REQUIRED SWITCHES: /TASK = Command to be executed (for example BACKUP 0r RESTORE) /SERVER = SQL Server Name (for example usgb021) /DBNAME = Database Name (for example AEDatabase) /SDATETIME = mm/dd/yyyy HH:MM:ss format (for example "5/21/2012 10:20:30"). Alarms & Events recorded from this time will be considered. This option is mandatory only when used with BACKUP command. /EDATETIME = mm/dd/yyyy HH:MM:ss format (for example "5/25/2012 10:20:30"). Alarms & Events recorded till this time will be considered. This option is mandatory only when used with BACKUP command. /BKPPATH = Fully qualified path of the.dat file where the backup of the Database will be taken.this switch is mandatory only when used with BACKUP command. /RSTPATH = Fully qualified path of the.dat file from where the Database will be restored.this switch is mandatory only when used with RESTORE command. /USERNAME = User Name (for example sa) used to connect to SQL Server using SQL Authentication. If this switch is not provided then Windows Authentication is used to connect to SQL Server. OPTIONAL SWITCHES: /PWD = Password (for example Pr0f1cyhist) Default is empty string (no password is okay, but not recommended for security reasons). If you want the password to be blank, simply skip using this switch. EXAMPLES: BACKUP Operation using SQL Authentication: Proficy.Historian.AandE.Migration.exe /TASK=Backup /SERVER=CPHIST45\PROFICYHIST /DBNAME=CPHIST45_plantdatabase /SDateTime="3/9/2013 21:00:00" /EDateTime="3/9/2013 23:59:59" /BKPPATH=C:\temp\PDB_0309.dat /USERNAME=sa /PWD=Pr0f1cyhist BACKUP Operation using Windows Authentication: Proficy.Historian.AandE.Migration.exe /TASK=Backup /SERVER=Domain\Node /DBNAME=AEDB /SDateTime="5/10/2012 10:20:30" /EDateTime="6/10/2012 10:20:30" /BKPPATH=E:\DBBkpPath\AEDB_1.dat RESTORE Operation using SQL Authentication: Proficy.Historian.AandE.Migration.exe /TASK=Restore
/SERVER=CPHIST45\PROFICYHIST /DBNAME=CPHIST45_AEDatabase /RSTPATH=C:\temp\PDB_0309.dat /USERNAME=sa /PWD=Pr0f1cyhist RESTORE Operation using Windows Authentication: Proficy.Historian.AandE.Migration.exe /TASK=RESTORE /SERVER=Domain\Node /DBNAME=AEDB /RSTPATH=E:\DBBkpPath\AEDB_1.dat Multiple Backups Using a Batch File: cd C:\Program Files\Proficy\Proficy DataBase start /b /wait Proficy.Historian.AandE.Migration.exe /TASK=Backup /SERVER=CPHIST45\PROFICYHIST /DBNAME=CPHIST45_plantdatabase /SDateTime="3/9/2013 21:00:00" /EDateTime="3/9/2013 23:59:59" /BKPPATH=C:\temp\PDB_0309.dat /USERNAME=sa /PWD=Pr0f1cyhist start /b /wait Proficy.Historian.AandE.Migration.exe /TASK=Backup /SERVER=CPHIST45\PROFICYHIST /DBNAME=CPHIST45_plantdatabase /SDateTime="3/10/2013 00:00:00" /EDateTime="3/10/2013 02:00:00" /BKPPATH=C:\temp\PDB_0310_1.dat /USERNAME=sa /PWD=Pr0f1cyhist start /b /wait Proficy.Historian.AandE.Migration.exe /TASK=Backup /SERVER=CPHIST45\PROFICYHIST /DBNAME=CPHIST45_plantdatabase /SDateTime="3/10/2013 02:00:00" /EDateTime="3/10/2013 04:00:00" /BKPPATH=C:\temp\PDB_0310_2.dat /USERNAME=sa /PWD=Pr0f1cyhist Multiple Restores Using a Batch File cd C:\Program Files\Proficy\Proficy DataBase start /b /wait Proficy.Historian.AandE.Migration.exe /TASK=Restore /SERVER=CPHIST45\PROFICYHIST /DBNAME=CPHIST45_AEDatabase /RSTPATH=C:\temp\PDB_0309.dat /USERNAME=sa /PWD=Pr0f1cyhist start /b /wait Proficy.Historian.AandE.Migration.exe /TASK=Restore /SERVER=CPHIST45\PROFICYHIST /DBNAME=CPHIST45_AEDatabase /RSTPATH=C:\temp\PDB_0310_1.dat /USERNAME=sa /PWD=Pr0f1cyhist start /b /wait Proficy.Historian.AandE.Migration.exe /TASK=Restore /SERVER=CPHIST45\PROFICYHIST /DBNAME=CPHIST45_AEDatabase /RSTPATH=C:\temp\PDB_0310_2.dat /USERNAME=sa /PWD=Pr0f1cyhist NOTE: Parameter values with spaces should be enclosed within quotation marks (""). For Example: /BKPPATH="C:\Proficy Historian Data\AEDB_Bkp.dat".
Using Arrays and MultiField tag elements in Calculation, Server to Server Collectors. Using Arrays in the Calculation and Server to Server collectors In Proficy Historian 5.5 you can create tags of Array data type. You can use the array tags with the Calculation Collector or Servre to Server collector as a source of information. You can forward the entire array to the latest version of the Proficy Historian server using the Server to Server collector or distributor like you do for a regular tag. If you are using a Pre 5.5 Data Archiver then, you can only send an individual array element. For example: result = currentvalue("array1[4]") You cannot make calculation tags of array data type, but you can use data from array tags inside your calculations. For example: result = currentvalue("array1[4]")+5 Using Multi field Tags in the Calculation and Server to Server collectors In Proficy Historian 5.5 you can create tags of User Defined data types. You can use these tags with the Calculation Collector or Servre to Server collector as a source of information. You cannot make Server to Server tags of a User Defined data type. The Server to Server collector will not be able to write to them. However, you can use the fields of a multifield tag in your calculation formula. For example: result = currentvalue("tag1.intval")+5 If you want use a MultiField tag as a trigger tag you can use either the tag name "Tag1" or tag name with the field "Tag1.IntVal". When you are sending a multifield tag data to a destination Historian Server using Server to Server collector, the tag will be converted into multiple tags at the destination. Even if you are using the latest Historian version, a tag with 2 fields will become 2 tags on the destination server and will not be a User Defined type. These tags will have the data type of the field. For example: If you have one tag "Tag1" with two fields "FloatVal" and "IntVal" on a source archiver, the Server to Server collector will create 2 tags "Tag1.FloatVal" and "Tag1.IntVal" on the destination. Historian Archive Ingestion Service. This service, created as manual start, is reserved for use with the Proficy Historian HD big data analytics platform. Having this service stopped does not impact the functioning of Proficy Historian. For more information regarding Proficy Historian HD, please visit: http://www.ge-ip.com/products/proficyhistorian-hd/p3714.
Proficy Historian 5.5 System Requirements Hardware Requirements For Historian Servers, the minimum hardware requirements are: A 2.4 GHz clock speed Intel Core i3 or i5 or i7 CPU or equivalent AMD Phenom CPU with 4 GB RAM for a 32-bit Historian Server and 4 GB RAM for a 64-bit Historian Server. A DVD-ROM drive. 100 Mbps TCP/IP-compatible network interface adapter for network communication and certain I/O drivers. 80 GB free hard drive space for the data archives, message files, buffer files, and log files used by the system. For Data Collector nodes, the recommended minimum hardware requirements are: A 2.0 GHz clock speed Intel Core i3 or i5 or i7 CPU or equivalent AMD Phenom CPU with 2 GB RAM. 40 GB of free hard drive space to store buffered data. A DVD-ROM drive. TCP/IP-compatible network interface adapter for network communication and certain I/O drivers. For the Microsoft Cluster service, the minimum hardware requirements are: A 2.6 GHz clock speed Intel Core i3 or i5 or i7 or Xeon or equivalent AMD Opteron CPU with minimum 8 GB RAM. 80 GB of local free hard drive space. 40 GB shared SCSI hard drive (RAID preferred).. Two 100Mbit TCP/IP-compatible network interface adapters for network communication and certain I/O drivers (One for public network, another for private network). NOTE: The configuration of each server added to the cluster must be identical to the other servers in the cluster. Guidelines for Determining Historian Server Size You determine the size of an Historian Server as a function of the number of tags from which data is collected, the rate of alarm and event collection, and how often you intend to collect the data and how much data you want to keep online. The number of tags is an indicator of the number of concurrent users likely to access the system. The primary factor is server memory requirements; CPU load is a secondary factor. If the number of concurrent users is significantly different from the suggested guidelines, adjust server memory size accordingly. Use the following parameters to determine the size of the Historian Server.
Recommended Historian Server Configurations* Tags <10K 10K to 100K 100K to 1 Million 1 Million to 2 Million 2 Million to 10 Million 10 Million to 20 Million RAM (GB) 4 GB 4 GB 32GB 64 GB 128GB 256GB Disk Size required 80 GB 160 GB 1 TB 4 TB 10TB 15TB Processor Type Intel Core-i5, i7 family, or equivalent Intel Xeon (56xx, E5 family or AMD Opteron 42xx/62xx family) Intel Xeon ( 56xx, E5 family or AMD Opteron 42xx/62xx family) Intel Xeon ( 56xx, E5 family or AMD Opteron 42xx/62xx family) CPU Dual/Quad cores 2-Socket 2-socket or 4- socket 2-socket or 4- socket CPU Speed (GHz) 2.8 2.6 2.6 2.6 Recommended CPU clock in Giga Hz 2.8 2.6 2.6 2.9 Operating System Windows 7 (32-bit) or Windows Server 2008 (32-bit) Windows Server 2008 R2/Windows 2012 standard (64-bit) Windows Server 2008 R2 (64- bit)/windows 2012 Standard(64- bit) Windows Server 2008 R2 (64- bit)/windows 2012 Standard (64-bit) Storage Type Internal SATA Drives Direct attached or shared storage with SAS enterprise class drives. Hardware RAID controller with cache High speed shared storage with SAS or SSD drive High speed shared storage with SAS or SSD drive
Recommended Historian Server Configurations* memory. types. Hardware RAID controller with cache memory types. Years of data online 1 year * Above recommended configurations may vary based on years of data online, update rate, data compression setting, and other tag configuration parameters. NOTES: Proficy Historian Server can run on both 32-bit and 64-bit versions of Windows. When possible, for performance reasons, consider using computers with multiple disk drives so that archives and buffers can be given their own drive. Or, multiple data stores can each have their own drive. Sustained event rate is 18 million per minute.* Proficy Historian supports Intel Core i3, i5, i7 Duo based processors as long as they are compatible with the operating system. Proficy Historian does not support Itanium processors. Example System for Sustained Event Rate* Specification Medium Size Server Large Size Server Processor Type Intel Xeon 5540 Intel Xeon E5-2670 or E5-4650 CPU Dual socket Dual socket or quad-socket CPU Speed (GHz) 2.5 2.7
Specification Medium Size Server Large Size Server RAM (GB) 64 256 * Note that System Performance may vary depending on the hardware specifications, operating system, and tuning parameters. The above hardware specifications are provided as a reference only. Recommended Historian Collector Configurations Configuration Item Recommendation RAM (GB) 2 GB* Disk Size required 40 GB Historian 5.5 Collectors 32-bit Operating System Windows 7 (32-bit) or Windows 7 (64-bit)** * Historian 5.5 Collectors may use up to 4 GB RAM in a 64-bit Windows operating system. ** Historian 5.5 Collectors work as 32-bit applications on a 64-bit Windows operating systems using WoW64 mode (Windows-on-Windows 64-bit). However, you can read and write data from a 64-bit Historian Server. NOTES: RAM and Disk Size required may vary based on the collectors available on the system. Recommended number of tags per collector is 20 to 30K. For ifix systems, count each Node.Tag.Field (NTF) as a separate tag when you determine the size of the system. For example, FIX.FIC101.F_CV and FIX.FIC101.B_CUALM (current alarm) both count as tags, even though they are derived from the same ifix tag. Recommended Historian Alarm and Event Archiver Configurations Use the following parameters to determine the size of the Historian Alarm and Event archiver.
Alarm & Event Rate RAM CPU 1 / minute 1 GB Single 1 / second 2 GB Single 10 / second 2 GB Single 100 / second 4 GB Double You must have disk storage capacity in the multi-gb range for the many data archive files (typically 500 MB each) and alarms you will generate, especially if you want to keep old data online. NOTE: As more applications run simultaneously on a server, performance decreases. Whenever possible, run additional applications on separate computers. Hardware Requirements - Proficy Historian on Windows XP Embedded The minimum Historian hardware requirements are: A minimum Atom-based 1.6 GHz computer or equivalent. A minimum of 1 GB RAM. A minimum of 1 GB of free hard drive space (for an upgrade). For a new installation, a minimum of 5 GB of free hard drive space is required. Other GE Intelligent products, such as Proficy ifix, impose additional requirements. Refer to the Important Product Information (IPI) topic in the product's electronic books for specific system requirements. Click the System Req. tab in that product's IPI for details. TCP/IP-compatible network interface adapter for network communication and certain I/O drivers. One free, direct-connect USB port. Some touch screens, pointing devices, and I/O drivers require a serial port. Additional ports for I/O hardware should be ordered with the computer. SVGA or better color graphics monitor and a 100% IBM-compatible, 24-bit graphics card capable of 800x600 resolution and at least 16 million (16,777,216) colors. Two-button mouse or compatible pointing device (such as a touch screen). NOTE: There are risks associated with using a Compact Flash or a similar device as a Primary drive in the Windows XP Embedded environment with the Proficy Historian product and your production data. These types of devices have a lifetime associated with them regarding the number of writes the device is capable of over a lifetime. As such, storing production data on such a device may result in lost data, over the long term. If the system has a physical drive, and not a Compact Flash or a similar device, the production data is affected by this risk. Software Requirements The minimum Historian software requirements are:
One of the following operating systems, with latest service packs or revisions: o o o o o o o o o o NOTES: Microsoft Windows Server 2008 R2 (64-bit) Microsoft Windows Server 2008 (32-bit or 64-bit) Microsoft Windows Server 2003 R2 (64-bit) Microsoft Windows Server 2003 (32-bit or 64-bit) Microsoft Windows 7 Professional (32-bit or 64-bit) Microsoft Windows 8 Professional (32-bit or 64-bit) Microsoft Windows Vista Professional (32-bit or 64-bit) Microsoft Windows XP Professional SP3 (32-bit or 64-bit) Microsoft Windows XP Embedded (32-bit) Microsoft Windows Server 2012 Standard (64-bit) Historian 5.5 32-bit components such as Collectors, Excel Add-in 32-bit, Interactive SQL 32-bit, APIs, and Non-Web Administrator work as 32-bit application on 64-bit Windows operating systems using WoW64 mode (Windows-on-Windows 64-bit). However, you can read and write data from a 64-bit Historian Server. Windows Server 2008 (32-bit or 64-bit) and Windows Server 2008 R2 can be installed as either the Full or Server Core installation. Proficy Historian 5.5 does not support on a Windows Server Core installation. SQL must use mixed mode authentication. Network interface software for network communication. The TCP/IP network protocol is required. One of the following 32-bit or 64-bit SQL Server systems to configure alarm and event archiving: Microsoft SQL Server 2008 Standard, Professional, or Enterprise Edition. Microsoft SQL Server 2008 Express. Microsoft SQL Server 2008 R2. Microsoft SQL Server 2012. One of the following 32-bit or 64-bit versions of SQL Server to use Historian as a linked server: Microsoft SQL Server 2008 Standard, Professional, or Enterprise Edition. Microsoft SQL Server 2008 Express. Microsoft SQL Server 2008 R2. Microsoft SQL Server 2012. The Historian Excel Add-In requires installation of Microsoft Office 2003, or Microsoft Office 2007, or Microsoft Office 2010 (32-bit/64-bit) or Microsoft Office 2013. Compatibility with Other Proficy Products Several GE Intelligent Platform products work with Proficy Historian. The following is a general set of required versions to work with Historian 5.5. IMPORTANT: If you want to enable the new Strict Authentication feature in Proficy Historian 5.5, be aware that you will need to apply the latest SIMs that support this feature for all Proficy clients that connect to the Archiver, including the ones listed in this table. In addition, there may be SIMS to allow pre-5.0 collectors and client applications such as Excel Add-In to connect. Refer to the SIM download page for update for Historian and other Proficy products.
Product Proficy Portal Required Version 3.5, 3.5 SP1 Machine Edition View 7.5, 7.0 CIMPLICITY 8.2, 8.1, 8.0. ifix 5.5, 5.1.* Plant Apps 6.1, 5.0, 4.1** Proficy Workflow 2.1, 2.0 Proficy Smart Signal 5.5 Proficy CSense 5.5 PHA 5.5, 5.0 * For customers using ifix, there was a change in the HKEY_CURRENT_USER registry values for WebSpace and it will no longer work with the existing sim. Ensure that you get the latest ifix sims. The following article provides additional instructions: http://support.ge-ip.com/support/index?page=kbchannel&id=s:kb15129. *For customers using ifix 5.1 and 5.0 with Historian 5.5, there was a change in the registry entry that has to be updated. The following article provides additional instructions: http://support.ge-ip.com/support/index?page=kbchannel&id=s:kb13651. ** For Plant Apps customers using the Historian Type = GE Proficy Historian 3.0 to connect to Proficy Historian 5.5, both the Enabled and Disabled options for Enforce Strict Client Authentication selection are supported. ** For Plant Apps customers using the Historian Type = GE Proficy Historian to connect to Proficy Historian 5.5, only the Disabled option for Enforce Strict Client Authentication selection is supported. In Historian 5.0, the Historian HKEY_CURRENT_USER registry key values were changed. The programs accessing the server collection through the SDK are unaffected. Any program or script that directly accesses the registry keys or any Terminal Server login scripts that try to configure a list of servers by importing registry keys directly will no longer work. Such programs need to access the server collection via SDK calls, not directly.