OSIsoft Release Notes

Transcription

1 OSIsoft Release Notes PI ACE 2010 R2 SP1 (version /1.2.50) 2011 OSIsoft, LLC. All rights reserved PI ACE 2010 R2 SP1 Release Notes

2 Table of Contents Overview... 1 Fixes and Enhancements... 1 Fixes... 1 Known Issues... 3 Setup... 6 Operating Systems... 6 System Prerequisites... 6 Other System Requirements... 6 PI Server Platforms... 7 Distribution Kit Files... 7 Installation... 8 Upgrading from Previous Versions... 8 Uninstalling PI ACE... 9 List of Files Installed During Setup... 9 Any Feature... 9 ACE Manager ACE 2.x Scheduler ACE 2.x Wizard for VB 2005, 2008 and ACE 1.x Scheduler ACE 1.x Wizard for VB Documentation Overview Technical Support and Resources... 13

3 Overview PI Advanced Computing Engine (PI ACE) provides an environment for developers - novice to professional - to create calculations using data from the PI System. Users have created calculations to aggregate metrics; perform heat and material balances, data reconciliation, real-time cost accounting and batch summaries. PI ACE can be used to integrate with third party systems including data transfer and alarming and for just about any application that does not require user intervention. ACE can be used in either the Microsoft Visual Basic 6 (VB6) or the Microsoft Visual Basic.NET (VB.NET) 2005, 2008, and 2010 development environment. Because of the significant differences in the integrated development environments (IDEs) for VB6 and VB.NET, OSIsoft provides two versions of ACE: ACE for VB6 (ACE 1.x) and ACE for VB.NET (ACE 2.x).This release supports VB6, Visual Basic 2005, 2008 and Visual Basic.NET 2003 is NOT supported. This release fixes several critical issues found in PI ACE 2010 R2 (version /1.2.50). In particular, several issues that could intermittently impact the results of the ACE 2.x calculations have been fixed (see OSIsoft Knowledge Base article #KB for more details). These changes only apply to ACE 2.x and no changes have been made for ACE 1.x. This release does not include any enhancements and is a full install of PI ACE. Fixes and Enhancements Fixes This section lists problems that have been resolved in this release of PI ACE. These fixes only apply to ACE 2.x (unless otherwise specified); no changes have been made for ACE 1.x. Fixes for PI ACE 2010 R2 (version ) The following issues found in the PI ACE 2010 R2 release have been fixed. Punch List Item 24085OSI OSI8 Description ACE calculations with output tags of point type = Int16 throw an error when recalculating or during normal calculations if PIACEPoint.ArcMode is explicitly set to dmreplaceduplicates. As a result, no output is written to the PI Server. The following error is logged: Error number: 438 Location: PIACEPoint.PutValue Description: Public member ReplaceArchieveValue on type PIACEPoint not found. When editing an ACE calculation (using PIACEWizard>Edit menu) with a large number of input/output tags or aliases (around 100 or more), after clicking Finish on Page2, it takes an unreasonably long time to load the VB.NET OSIsoft Release Notes Page 1

4 24093OSI OSI OSI OSI OSI OSI OSI OSI OSI8 project. During this time, the Visual Studio process (devenv.exe) uses excessive CPU. For input tags configured as recalculation tags, deleting archive events does not trigger automatic recalculations. When starting an ACE context which maps to a PIModule and contains PI tags as input or output aliases, ACE fails to resolve the PI tags and as a result fails to initialize the context. The status of the context is set as "Error". Following error is written to the message log: Error number: 5 Location: PIACENetClassModule.InitializeComponent Description: The given key was not present in the dictionary. This issue does not occur for tags specified using full path name \\servername\tagname. When an ACE calculation attempts to access data for output tags or aliases (except PIACEPoint.Value method) using PIACEPoint.PrevEvent, PrevVal, NextEvent, NextVal or summary methods, an object reference error is thrown - "Object reference not set to an instance of an object". This may result in "Calc Failed" event written to output tags for this calculation. The ACE built-in function ParseTime returns a PITime object which can potentially be modified by any other PIACEPoint or PIACEBIFunctions call that requires resolving a string time (e.g. "today", "*-1h" etc.). PIACEPoint summary methods (Avg, Mean, Max, Min, Count, Range, StDev, PctGood and Total) may intermittently return wrong results when same source tag is used in multiple ACE contexts, and these contexts make summary calls at the same time. The issue only occurs when ACE Cache is enabled and relevant data is found in ACE Cache. Many PIACEPoint and PIACEBIFunction methods (e.g. Value, PrevEvent, Avg etc.) have to convert the timestamp specified as absolute or relative pi time strings (e.g. "today", "*-1h" etc.) to UTC Seconds. When an ACE module is configured with multiple contexts and more than one context calls a time conversion routine at exactly the same time supplying a string to represent the timestamp, incorrect timestamp may be used for evaluation. This could intermittently impact the results of the ACE 2.x calculations. For any PIACEPoint or PIACEBIFunctions methods, when timestamp is specified as an ambiguous string (e.g. "17:00" or "5:00 PM" is ambiguous because no date is specified), an "invalid time" error is returned. For versions before PI ACE 2010 R2, ambiguous time strings are resolved relative to the execution time (or current time, depending on the method). For PI ACE 2010 R2, ACE attempts to resolve timestamp strings as VB.NET Date. For example, "17:00" would be interpreted as "1/1/ :00" - which would result in invalid time. ACE contexts mapped to PIModules which do not have all input/output aliases fail to initialize and their status is set to Error. The following message is logged to the message log: "Location: PIACENetClassModule.InitializeComponent Description: The given key was not present in the dictionary." When running ACE calculations on a client machine (with no PI Server installed) with a pre PI Message Subsystem, the PIACEClassLibraryHost process may crash when attempting to log messages from multiple threads. The ACE Manager would still be showing the status of the corresponding calculation as ON (green) but the PIACEClassLibraryHost Page 2

5 24381OSI OSI8 process would not be running (can be verified from the task manager). See PISDK PLI 24337OSI8 for more details. Debug level messages at the scheduler level are ON by default. As a result, each host process (PIACEClassLibraryHost.exe) logs message similar to the following every 5 seconds - "RetrievePIEvents summary: Last retrieval time = ; Snapshot count = 2; Processing time (ms) = 0; Archive count = 0; Processing time (ms) = 0; Cache update time (ms) = 0". If the built-in datetime functions (BONM, BOD, BOM, FONM, Noon etc.) pass the input time argument as a PITime object, the input argument is modified. Fixes for Previous Versions of PI ACE The following issues found in release or before are fixed. Punch List Item 24333OSI8 Description When stopping a context, ACE uses the name of the context as a partial string, and stops all contexts that contain this string. If contexts are nested (e.g. \\mypiserver\unit1, \\mypiserver\unit1\subunit1 etc.), stopping one context may incorrectly stop contexts in the nested sub-items. Even after the contexts pointing to nested sub-items are unintentionally stopped, ACE Manager still displays their status as ON (green). Known Issues This section lists problems and enhancements that have been deferred until a future release. Please consult the technical support Web site for an updated list. Punch List Item 20396OSI OSI OSI OSI8 Description After upgrading PI ACE, users may fail to recompile previously created calculations using Visual Studio 2008, with the error Could not resolve this reference. Could not locate the assembly "OSIsoft.PIACENet, Version=2.1.xx.0, Culture=neutral, PublicKeyToken=38c1410a641dcae4". Check to make sure the assembly exists on disk. This problem can be resolved by selecting the reference OSIsoft.PIACENet in the VB.NET solution and setting its Specific Version property to False. ACE scheduler would be able to successfully run the previously compiled dll, it is the recompiling that would fail. ACE Manager fails to display the complete calculation tree when the total number of nodes in the tree view control exceeds Tree view nodes are created for executables, classes, contexts, as well as module properties such as the tag lists. (Note: Users may be able to use enhancement PLI#23816OSI8 as a workaround for this issue.) Testing calculations compiled as x64 (strictly 64-Bit) is not supported. Testing calculations in Visual Studio 2008 using ACE 2.x Wizard on Windows XP, Windows Server 2003 and Windows Vista may fail with an

6 error - Failed to create ACE Module: Loading this assembly would produce a different grant set from other instances. (Exception from HRESULT: 0x ). When this happens, users would not be able to register calculations from ACE Wizard, as this requires the calculation to be successfully tested. The newly created ACE module would have its status set as New and would not be started by the ACE 2.x scheduler. This issue can be fixed using either of the following two methods: Solution 1 (recommended): Install the Application Compatibility Update for the.net Framework 2.0 SP2 - KB Solution 2: Copy and Paste the following files from the ACE\Wizard directory to the Visual Studio 2008 application base directory where devenv.exe is located (typically, C:\Program Files (x86)\microsoft Visual Studio 9.0\Common7\IDE): - PIACENetWizard.dll - PIACEWizard.AddIn - AxInterop.MSChart20Lib.dll - AxInterop.MSFlexGridLib.dll - Interop.MSChart20Lib.dll - Interop.MSFlexGridLib.dll Add the path to the VS2008 application base directory to the list of Visual Studio 2008 Add-Ins File Paths OSI OSI OSI OSI8 See Knowledge Base article (# KB00424) for more details. After upgrading to PI ACE 2010 R2 SP1, the enable/disable creating performance counters setting may not be persisted. For example, if creating performance counters is disabled, after the upgrade, it is enabled. When upgrading from PI ACE or earlier, on machines where the ACE 2.x scheduler is configured to run against a PI Server other than the default server from the KST, this configuration would not be persisted upon upgrading to PI ACE 2010 R2 SP1. The users would have to specify the TargetPIServer entry in the scheduler configuration file (ACE\Scheduler\PIACENetScheduler.exe.config). When upgrading from PI ACE 2010 R2, the TargetPIServer, TargetScheduler and PIACEHostTargetCPU settings (specified in the scheduler configuration file) are not persisted. Users would have to reset these entries. On Windows XP, Windows Server 2003 and Windows Vista, if ACE 1.x scheduler is installed silently (e.g. msiexec /i piace.msi ADDDEFAULT=Core,ACE1.x_Scheduler /q) it may fail to start calculations with the following error message: Error number: Location: PIACEContextInfo.StartACEContext Description: CreateObject failed for aceexename.acemodulename. The workaround to this problem is to uninstall PI ACE, and reinstall without using the /q switch. PI ACE failover cannot occur while the primary PI Server is down. When a Page 4

7 23843OSI OSI OSI OSI OSI8 standby ACE Scheduler takes over as primary, it must first connect to the primary PI Server, and read/update structural information in the PI MDB. If the scheduler cannot connect to the primary PI Server, it does not start any calculations. In certain situations, calculations created using previous versions of ACE (up to v2.1.32) may fail to work as 64-Bit. The calculations may either fail to initialize or result in error during execution with the error message(s) similar to the following: Method not found: 'PISDK.PIModule OSIsoft.PI.ACE.PIACEBIFunctions.GetPIModuleFromPath(System.String)'. The issue mainly arises for calculations using ACE library functions which return PI SDK objects (for example FindXX, GetPIModuleFromPath, ParseTime etc.), and only applies when running calculations as 64-Bit. There would be no issue in running the calculations as 32-Bit. In order to run the calculation as 64-Bit, users are required to recompile the calculation assembly (dll) using the latest version of OSIsoft.PIACENet.dll (v ). See Knowledge Base article (# KB00428) for more details. Installing ACE 1.x wizard on machines where VB6 is not installed may generate an error Error 1904: Module C:\Program Files\PIPC\ACE\Wizard\PIPE2ACE.dll failed to register. Users can choose to ignore the error message and installation will complete successfully. Alternatively, in the installation program use the selection feature to deselect the ACE 1.x wizard as workaround. Testing an ACE calculation (using PIACEWizard>Test) which sets the value of output tags at timestamp other than the current execution time, does not display the results for the output tags. PI ACE 2010 R2 displays "Calc Failed" while earlier versions (up to v2.1.32) display "Null". This issue does not affect the calculations at runtime and the correct value would be written to the PI Server at the specified timestamp. After upgrading from PI ACE 2010 R2 ( ) to PI ACE 2010 R2 SP1 ( ) F1 help for Visual Studio 2010 may not work. Users can manually install ACE help library. Use the following steps to install the PI ACE Help3 library: 1. Open VS2010 and click Help>Manage Help Settings. This would open Help Library Manager. 2. On the Help Library Manager window, select "Install content from Disk" and browse to $PIPC\ACE\Help directory. Select HelpContentSetup.msha and click Open. Click Next. 3. Click Add next to the "PI Advanced Computing Engine 2010 R2" content for offline help. Click Update. Registering a context from ACE 2.x Wizard (using PIACEWizard>Register) as clock-scheduled with sub-second period (e.g or 0.5) fails with the error - "ACE Context <context name> may not have been registered successfully. Invalid Schedule Information". Users can work around this issue by specifying the schedule for the newly created context using ACE Manager (Context>Edit Schedule and Priority). ACE Manager allows specifying sub-second periods.

8 Setup Operating Systems The following operating system versions (with minimum Service Pack requirements noted, where they apply) are supported on either (32-bit or 64-bit where applicable*): Windows XP SP3** Windows Vista** Windows 7** Windows Server 2003 SP2 Windows Server 2008 Window Server 2008 R2 *On 64-Bit operating systems ACE calculations and scheduler for ACE 2.x can be configured to be run as 64-bit. ACE Manager, ACE 1.x and 2.x Wizard, and ACE 1.x scheduler only run as 32-Bit. ** OSIsoft recommends running ACE Scheduler on server operating systems in production environments. System Prerequisites Installation of an OSIsoft product on Windows relies on the presence of Microsoft operating system components such as the Microsoft.NET Framework and Microsoft run time libraries. OSIsoft Prerequisite Kits are available in three packages that verify and install the needed operating system prerequisites: Online (Recommended): For installation on a computer connected to the internet. This kit connects to Microsoft sites in order to download.net Framework 3.5 for the operating system on which it is run. This is a bootstrapper kit that is much smaller than the Standalone kit. Standalone (Recommended): For installation on a computer that cannot connect to Microsoft sites, or for installations where such connection is not desirable. This is a full redistributable kit that is much larger than the Online kit. Legacy: This kit should only be used for installation on older operating systems where the OSIsoft products do not require.net Framework 3.5. All three Prerequisite Kits contain both 32-bit and 64-bit installation redistributables. See the Prerequisites Product Pages on the OSIsoft Tech Support Web site to determine which MS Operating System prerequisites you need. Other System Requirements ACE consists of three components: Scheduler, Manager, and Wizard. The system requirements for each component differ and are as follows: Page 6

9 ACE 2.x Scheduler (2.1.50) Microsoft.NET Framework 2.0 or above PI SDK or higher for 64-bit and PI SDK or higher for 32-bit PI API a or higher for 64-bit ACE 2.x Wizard (2.1.50) Microsoft Visual Studio 2005, 2008 or 2010 Microsoft.NET Framework 2.0 or higher* PI SDK or higher for 64-bit and PI SDK or higher for 32-bit * ACE 2.x Wizard for Visual Studio 2010 requires.net Framework 3.5 SP1. ACE Manager (1.2.50) PI SDK or higher ACE 1.x Scheduler (1.2.50) Microsoft.NET Framework 2.0 or above PI SDK or higher ACE 1.x Wizard (1.2.50) Visual Basic 6 (Enterprise or Professional edition) PI SDK or higher. PI Server Platforms The three components of ACE can be installed on different computers. In order to develop or run ACE Modules, a PI Server version 3.3 or higher is required to store the structural information of ACE Modules in the PI Module Database. This server is referred to as the PI ACE Data Server. The actual PI tags used in calculations or for archiving results in an ACE Module could come from either the PI ACE Data Server or other PI Servers. Distribution Kit Files The PI ACE setup distribution consists of the following files: Setup Files Description DotNet20Setup.dll Setup module for DotNet 2.0 Framework. MSRunTimesSetup.dll Setup module for Microsoft Runtimes x86. MSRunTimesSetupx64.dll Setup module for Microsoft Runtimes x64. piace.msi Windows installer file for the PI ACE. pisdk.msi Windows installer file for the PI-SDK x86. pisdk_x64.msi Windows installer file for the PI-SDK x64.

10 piapi_x64.msi Windows installer file for the PI-API x64. Setup.exe setup.ini SetupUtils.dll silent.ini Setup wrapper installation program. This program manages delivery of all components. Setup wrapper configuration. Setup wrapper utility module. Setup wrapper silent installation configuration. Installation The installation program is called Setup.exe and consists of both ACE for VB6 (ACE 1.x) and ACE for VB.NET (ACE 2.x). Before running the setup program, verify that the target platform meets the system requirements and prerequisites. The setup program automatically installs PISDK (x86) only on 32-bit operating systems and PISDK (x86), PI SDK (x64) and PI API A (x64) on 64-bit operating systems along with other components if they are not installed already. Because the setup program may write entries to shared portions of the registry, it is necessary to log in as a user with Administrative privileges on the system. It is advisable to close other applications during the setup process. If a PI System is running on the target machine, you need not stop the system. By default, ACE is installed under the PIPC directory (that is PIPC\ACE). Follow the setup program instructions to install appropriate components on the target machine. You may choose to install ACE Wizard, ACE Manager, and/or ACE Scheduler. Upon successful installation, ACE registers its Uninstall, which is then available through the standard control panel Add/Remove Programs applet. To install all features silently, the command is: msiexec /i piace.msi /q To install selected features silently, the command is: msiexec /i piace.msi ADDDEFAULT="FeatureList" /q where FeatureList is a list of features to be installed, separated by commas. piace.msi consists of these features: Core, ACEManager, ACE1.x_Wizard, ACE2.x_Wizard, ACE1.x_Scheduler, and ACE2.x_Scheduler. The Core feature must be installed for any other ACE component to function. For example, the following installs ACE Manager and ACE 2.x Wizard: msiexec /i piace.msi ADDDEFAULT="Core,ACEManager,ACE2.x_Wizard" /q Silently installing piace.msi does not check for component requirements; nor does it install any required components such as.net Framework and PI SDK. To silently install the whole package, one needs to modify the silent.ini file delivered with the setup package. Please see PI Server Installation and Upgrade Guide for details. Upgrading from Previous Versions The setup would automatically upgrade ACE versions /2.0.1 or later. However, upgrading from any version before /2.0.1 or beta release (2.1.40) is not supported. All Page 8

11 versions before /2.0.1 (i.e., 1.0.1, and 2.0.0) and beta release (2.1.40) must be uninstalled first via the Control Panel, Add/Remove Programs applet. If the PI Scheduler is configured to run against a PI Server other than the default PI Server for that machine (KST) refer to the Known Issues section above and Punch List Item 23820OSI8 for information on manually updating the PI Server. Uninstalling PI ACE PI ACE can be removed from your system by selecting it for removal in the Add/Remove Programs utility in Control Panel for Windows XP and 2003 Server, or the Programs and Features Control Panel for Windows Vista, 2008 Server, and Windows 7. The VB6 (located under ACE\Executables) and VB.NET (located under ACE\ClassLibraries) solutions created for ACE 1.x and 2.x calculations, respectively, are not deleted. List of Files Installed During Setup The following tables list the set of files installed by the PI ACE set up kit depending on feature selected for installation. Any Feature Directory File Version $PIPC\ACE PIACE.dll PIACECommon.dll OSIoft.PIACENet.dll OSIsoft.PIACEAssemblyLoader.dll OSIsoft.PIACENet.xml PIACEWebService.asmx PIACEWebService.dll PISteamTableFunctions.dll PI16.ICO $PIPC\ACE\Help PIACEReference.chm PIACEUserGuideVB6.chm PIACEUserGuideVBDotNet.chm

12 PIACESteamTable.chm H2Reg.exe H2Reg.ini piace.hxc piace.hxs piace.hxt piace_a.hxk piace_b.hxk piace_f.hxk piace_k.hxk piace_s.hxk piace_namedurlindex.hxk piace_b.hxk HelpContentSetUp.msha piace.cab $Windows\Symbols\dll OSIsoft.PIACENet.pdb OSIsoft.PIACEAssemblyLoader.pdb $Windows\assembly OSIsoft.PIACEAssemblyLoader.dll OSIsoft.PIACENet.dll policy.2.0.osisoft.piacenet policy.2.1.osisoft.piacenet ACE Manager Directory File Version $PIPC\ACE PIACEManager.exe Page 10

13 ACE 2.x Scheduler Directory File Version $PIPC\ACE\Scheduler PIACENetScheduler.exe PIACENetScheduler64.exe PIACENetScheduler.exe.config PIACEClassLibraryHost.exe (AnyCPU) $PIPC\ACE\Scheduler\x86 PIACEClassLibraryHost.exe (32 bit) $Windows\Symbol\exe PIACENetScheduler.pdb PIACENetScheduler64.pdb ACE 2.x Wizard for VB 2005, 2008 and 2010 Directory File Version $PIPC\ACE\Wizard AxInterop.MSChart20Lib.dll AxInterop.MSFlexGridLib.dll Interop.MSChart20Lib.dll Interop.MSFlexGridLib.dll Mschrt20.ocx MSFLXGRD.OCX PIACENetWizard.dll PIACEWizard.AddIn $PIPC\ACE\Wizard\VS2005 Class1.vb AssemblyInfo.vb PIACENetClassLibraryTemplateVB.vbproj $PIPC\ACE\Wizard\VS2008 Class1.vb AssemblyInfo.vb

14 PIACENetClassLibraryTemplateVB.vbproj $PIPC\ACE\Wizard\VS2010 Class1.vb AssemblyInfo.vb PIACENetClassLibraryTemplateVB.vbproj $PIPC\ACE\Wizard2005 Mschrt.ocx Msflxgrd.ocx $PIPC\ACE\Scheduler PIACEClassLibraryHost.exe (AnyCPU) $PIPC\ACE\Scheduler\x86 PIACEClassLibraryHost.exe (32-Bit) ACE 1.x Scheduler Directory File Version $PIPC\ACE\Scheduler PIACEScheduler.exe OSIsoft.PIACE.dll OSIsoft.PIACECommon.dll $Windows\Symbols\dll PIACEScheduler.pdb ACE 1.x Wizard for VB6 Directory File Version $PIPC\ACE\Wizard ACEClassTemplate.cls ACEExeTemplate.vbp DebugModule.bas PIACE.vbz PIACETestFunction.txt PIACEWizard.dll Page 12

15 PIPE2ACE.dll PEFormulaTemplate.vbp clstemplate.cls $PIPC\ACE\Help PIPE2ACE.doc Documentation Overview The following help files are included with the PI ACE installation and located in the PIPC\ACE\Help directory: PIACEUserGuideVBDotNet.chm: This user guide provides a product overview, installation procedures, and tutorial examples and describes features for various ACE components (ACE Manager, 2.x Wizard and Scheduler) required for developing calculations using Visual Basic.NET development environment. It also lists some common troubleshooting procedures. PIACEReference.chm: Documentation for the PI ACE library functions which are implemented as methods or properties of the PIACEPoint object or as shared routines. PIACEUserGuideVB6.chm: This user guide describes the features for various ACE components (ACE Manager, 1.x Wizard and Scheduler) required for developing calculations using Visual Basic 6 development environment. PIACESteamTable.chm: HTML Help for the PI Steam Table Library. In addition Adobe PDF versions of the User Guides are available on the OSIsoft technical support website and also included on PI ACE distribution media: PI ACE 2010 R2 User Guide for Visual Basic.NET.pdf PI ACE 2010 R2 User Guide for Visual Basic 6.pdf Technical Support and Resources OSIsoft provides dedicated technical support internationally, 24 hours a day, 7 days a week to customers with a current SRP contract. To locate local access numbers and current contact options, please visit our Contact Methods page on the Technical Support web site at The main contact information is also listed below: Telephone: Web Portal: techsupport@osisoft.com My Calls When you open a case using any of the above methods, you will receive a response from a Technical Support Engineer within four hours. Be sure to provide: Product name, version, and/or build numbers

16 Computer platform (CPU type, operating system, and version number) The time that the difficulty started The message log(s) at that time You can also take advantage of the Self-service Search page on our Technical Support Web Site to look for answers to your technical questions and issues. The search tool searches our online library of documentation, knowledge base articles, technical announcements and bulletins, known product issues, and documented product enhancement requests, as well as a collection of resources for system managers. Page 14

17 OSIsoft, LLC 777 Davis St., Suite 250 San Leandro, CA USA Tel: (01) Fax: (01) Web: OSIsoft Australia Perth, Australia OSIsoft Europe GmbH Frankfurt, Germany OSIsoft Asia Pte Ltd. Singapore OSIsoft Canada ULC Montreal & Calgary, Canada OSIsoft, LLC Representative Office Shanghai, People s Republic of China OSIsoft Japan KK Tokyo, Japan OSIsoft Mexico S. De R.L. De C.V. Mexico City, Mexico OSIsoft do Brasil Sistemas Ltda. Sao Paulo, Brazil Copyright: OSIsoft, LLC. All rights reserved. No part of this publication may be reproduced, stored in a retrieval system, or transmitted, in any form or by any means, mechanical, photocopying, recording, or otherwise, without the prior written permission of OSIsoft, LLC. OSIsoft, the OSIsoft logo and logotype, PI Analytics, PI ProcessBook, PI DataLink, ProcessPoint, Analysis Framework, IT Monitor, MCN Health Monitor, PI System, PI ActiveView, PI ACE, PI AlarmView, PI BatchView, PI Data Services, PI Manual Logger, PI ProfileView, PI WebParts, ProTRAQ, RLINK, RtAnalytics, RtBaseline, RtPortal, RtPM, RtReports, PI Event Frames and RtWebParts are all trademarks of OSIsoft, LLC. All other trademarks or trade names used herein are the property of their respective owners. U.S. GOVERNMENT RIGHTS Use, duplication or disclosure by the U.S. Government is subject to restrictions set forth in the OSIsoft, LLC license agreement and as provided in DFARS , DFARS , FAR , FAR , as applicable. OSIsoft, LLC. Published: 05 August 2011