Beruflich Dokumente
Kultur Dokumente
PI ProcessBook 2015
Version 3.5.0
Fixes
This section lists items that were resolved or added in this release of PI
ProcessBook. PI ProcessBook 2015 (v3.5.0)
Enhancements
Future Data
The PI Server 2015 release introduces the new Future Tag that can be used to plot
data into the future. PI ProcessBook 2015 supports this new tag type by polling for
new values at regular intervals when updating the displays.
Please review the white paper Using Future Data and Visualization Clients, for
more information regarding Future Data in the PI System.
Known Issues
This section lists problems and enhancements that have been deferred until a future
release.
On recent operating systems Microsoft .NET 4.5.2 update could fail during
installation of PI ProcessBook 2015. This is an issue with the .NET installer.
Recommend updating outside of the PI ProcessBook setup process and
trying again.
AF Attributes with data references configured to use time ranges will not
update correctly when used as tags on trend symbols.
Future Data tags cannot be used as placeholders for datasets.
Setup
NOTE: Any prior beta of PI ProcessBook or other beta PI System software should be
uninstalled prior to the installation of PI ProcessBook 2015.
To install PI ProcessBook manually, double-click on the PIProcessBook_2015.exe
file. The installation files are unpacked and the setup starts after the file extraction is
acknowledged.
You must have administrator privileges on your machine to successfully install PI
ProcessBook.
In order to benefit from the PI Notifications add-in delivered with this version of PI
ProcessBook, you must have PI Notifications client 1.0.777.0 or later installed.
The OSIsoft pre-requisite kit should be installed on a target system before silently
installing PI ProcessBook. For silent installations with Active Directory Group Policy,
please consult Support Solution 3136OSI8: How to Deploy Products with Active
Directory Group Policy.
To invoke a silent installation, enter the command setup.exe f silent.ini. The
silent.ini file can be customized to provide default a PI Server configuration setting as
follows:
[COMMANDLINE]
7 = /qn REBOOT=Suppress ALLUSERS=1 PI_SERVER= localhost
PI_ALIAS=localhost PI_TYPE=3 PI_PORT=5450 PI_USER=piadmin
INSTALLDIR="C:\Program Files\PIPC"
9 = /qn REBOOT=Suppress ALLUSERS=1 PI_SERVER= localhost
PI_ALIAS=localhost PI_TYPE=3 PI_PORT=5450 PI_USER=piadmin
INSTALLDIR="C:\Program Files\PIPC"
The two lines above are the only lines that should be changed in the silent.ini file
delivered with PI ProcessBook. localhost entries for the PI SDK, components 7 and
9, should be changed to reference the appropriate PI server.
NOTE: This version of PI ProcessBook requires .NET version 4, which requires a
reboot of the system. In order to do a silent installation this version of .NET must
already be present on the target system.
For information on installing PI ProcessBook using Microsofts System Management
Server technology, please see the following documents. A patch for the PI SDK in
this installation kit is a separate DLL the resolves a PI SDKregistry issue (WI65835).
Operating Systems
The following operating system platforms (with minimum Service Pack requirements
noted, where they apply) are supported:
Windows Vista SP2
Windows Server 2008 R2 (non-CORE version)
Windows 7 SP1
Windows 8
Windows Server 2012
Windows 8.1
Windows Server 2012 R2
Windows 10
Note that saving a file in Windows Vista, or later to a restricted area, e.g. Program
Files\PIPC, results in the file being stored in the users Virtual Store folder although PI
ProcessBook continues to report that the file is saved in the restricted area.
The Allow button must be clicked in order to repair or remove PI ProcessBook when
UAC is turned on.
UAC should be disabled to ensure successful deployment using silent installation.
Otherwise, elevated permission dialogs can be displayed by the operating system.
System Prerequisites
OSIsoft products and their installation depend on operating system components such
as Microsoft run time libraries, the Windows Installer engine, .NET Framework, and
other operating system redistributable packages. These operating system
components are available in three prerequisite setup kits. All three setup kits contain
both 32 and 64-bit redistributables.
To ensure that all necessary prerequisite components are installed, OSIsoft product
setup kits check for dependent components. If a dependency is missing, the
installation will exit, and the user will need to install prerequisites.
See the Prerequisite Kits page on the OSIsoft Tech Support Web site for more
information.
Server Platforms
Hardware Requirements
Physical Memory: Minimum 128 MB; Recommended 512 MB. Although 128 MB
provides acceptable performance for many, increasing the available RAM improves
performance, especially when there are multiple applications running simultaneously
on the same machine.
Processor Speed: Pentium III CPU or better. A faster processor may help
performance if displays have complex calculations performed locally, but increasing
the installed RAM is more likely to help with general performance.
Hard Disk Space: 300 MB of empty space on the system drive for application files
and registry entries.
In addition to the drive space required for the application files and registry entries,
there must also be enough space available to keep a backup copy of the pisdk.msi
and ProcessBook.msi files. Even after the product is uninstalled the backup copy still
exists. This copy is deleted only when the system is rebooted.
Only the OSIsoft and Microsoft components previously identified are required to run
PI ProcessBook.
Uninstalling PI ProcessBook
PI ProcessBook can be removed from your system by selecting it for removal in the
Add/Remove Programs utility in Control Panel for Windows 2003, or the Programs
and Features Control Panel for Windows Vista/Windows Server 2008 or later. You
must have administrator privileges on your machine to successfully uninstall PI
ProcessBook.
If PI ProcessBook is uninstalled on a system with PI ActiveView, the PI ActiveView
installation should be repaired to ensure proper functionality. The repair needs to be
done to support non-administrator users.
The following tables list the files installed by the PI ProcessBook 2015 installation
program.
Note: On 64-bit Windows installations, Program Files (x86) is used instead of Program Files and
SysWOW64 is used instead of System32.
\PIPC\Procbook OSIsoft.PB.ToolBars.Browser.Bookmarks.xsd
[CommonFilesFolder]\Microsoft
MSOINTL.DLL 10.0.2609.0
Shared\Office10\1033
[CommonFilesFolder]\Microsoft
link.exe 6.0.8168.0
Shared\VBA\VBA6
[CommonFilesFolder]\Microsoft
mspdb60.dll 6.0.8168.0
Shared\VBA\VBA6
[CommonFilesFolder]\Microsoft
vb6debug.dll 6.0.84.62
Shared\VBA\VBA6
[CommonFilesFolder]\Microsoft
vba6mtrt.dll 6.0.87.72
Shared\VBA\VBA6
x86_Microsoft.VC90.ATL_1fc8b3b9a1e18e3b_9.0.3
\Windows\winsxs\Manifests
0729.6161_x-ww_92453bb7.cat
x86_Microsoft.VC90.ATL_1fc8b3b9a1e18e3b_9.0.3
\Windows\winsxs\Manifests
0729.6161_x-ww_92453bb7.manifest
x86_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.3
\Windows\winsxs\Manifests
0729.6161_x-ww_31a54e43.cat
x86_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.3
\Windows\winsxs\Manifests
0729.6161_x-ww_31a54e43.manifest
x86_Microsoft.VC90.MFC_1fc8b3b9a1e18e3b_9.0.3
\Windows\winsxs\Manifests
0729.6161_x-ww_028bc148.cat
x86_Microsoft.VC90.MFC_1fc8b3b9a1e18e3b_9.0.3
\Windows\winsxs\Manifests
0729.6161_x-ww_028bc148.manifest
x86_Microsoft.VC90.MFCLOC_1fc8b3b9a1e18e3b_
\Windows\winsxs\Manifests
9.0.30729.6161_x-ww_730c3508.cat
x86_Microsoft.VC90.MFCLOC_1fc8b3b9a1e18e3b_
\Windows\winsxs\Manifests
9.0.30729.6161_x-ww_730c3508.manifest
x86_Microsoft.VC90.OpenMP_1fc8b3b9a1e18e3b_
\Windows\winsxs\Manifests
9.0.30729.6161_x-ww_4ddc769f.cat
x86_Microsoft.VC90.OpenMP_1fc8b3b9a1e18e3b_
\Windows\winsxs\Manifests
9.0.30729.6161_x-ww_4ddc769f.manifest
\Windows\winsxs\Policies\x86_policy.9.0.Micros
oft.VC90.ATL_1fc8b3b9a1e18e3b_x- 9.0.30729.6161.cat
ww_9e7eb501
\Windows\winsxs\Policies\x86_policy.9.0.Micros
oft.VC90.ATL_1fc8b3b9a1e18e3b_x- 9.0.30729.6161.policy
ww_9e7eb501
\Windows\winsxs\Policies\x86_policy.9.0.Micros
oft.VC90.CRT_1fc8b3b9a1e18e3b_x- 9.0.30729.6161.cat
ww_b7353f75
\Windows\winsxs\Policies\x86_policy.9.0.Micros
oft.VC90.CRT_1fc8b3b9a1e18e3b_x- 9.0.30729.6161.policy
ww_b7353f75
\Windows\winsxs\Policies\x86_policy.9.0.Micros
oft.VC90.MFC_1fc8b3b9a1e18e3b_x- 9.0.30729.6161.cat
ww_4ee8bb30
\Windows\winsxs\Policies\x86_policy.9.0.Micros
oft.VC90.MFC_1fc8b3b9a1e18e3b_x- 9.0.30729.6161.policy
ww_4ee8bb30
\Windows\winsxs\Policies\x86_policy.9.0.Micros
oft.VC90.MFCLOC_1fc8b3b9a1e18e3b_x- 9.0.30729.6161.cat
ww_b8438ace
\Windows\winsxs\Policies\x86_policy.9.0.Micros
oft.VC90.MFCLOC_1fc8b3b9a1e18e3b_x- 9.0.30729.6161.policy
ww_b8438ace
\Windows\winsxs\Policies\x86_policy.9.0.Micros
oft.VC90.OpenMP_1fc8b3b9a1e18e3b_x- 9.0.30729.6161.cat
ww_6ad67377
\Windows\winsxs\Policies\x86_policy.9.0.Micros
oft.VC90.OpenMP_1fc8b3b9a1e18e3b_x- 9.0.30729.6161.policy
ww_6ad67377
\Windows\winsxs\x86_Microsoft.VC90.ATL_1fc8
atl90.dll 9.0.30729.6161
b3b9a1e18e3b_9.0.30729.6161_x-ww_92453bb7
\Windows\winsxs\x86_Microsoft.VC90.CRT_1fc8
msvcm90.dll 9.0.30729.6161
b3b9a1e18e3b_9.0.30729.6161_x-ww_31a54e43
\Windows\winsxs\x86_Microsoft.VC90.CRT_1fc8
msvcp90.dll 9.0.30729.6161
b3b9a1e18e3b_9.0.30729.6161_x-ww_31a54e43
\Windows\winsxs\x86_Microsoft.VC90.CRT_1fc8
msvcr90.dll 9.0.30729.6161
b3b9a1e18e3b_9.0.30729.6161_x-ww_31a54e43
\Windows\winsxs\x86_Microsoft.VC90.MFC_1fc8
mfc90.dll 9.0.30729.6161
b3b9a1e18e3b_9.0.30729.6161_x-ww_028bc148
\Windows\winsxs\x86_Microsoft.VC90.MFC_1fc8
mfc90u.dll 9.0.30729.6161
b3b9a1e18e3b_9.0.30729.6161_x-ww_028bc148
\Windows\winsxs\x86_Microsoft.VC90.MFC_1fc8
mfcm90.dll 9.0.30729.6161
b3b9a1e18e3b_9.0.30729.6161_x-ww_028bc148
\Windows\winsxs\x86_Microsoft.VC90.MFC_1fc8
mfcm90u.dll 9.0.30729.6161
b3b9a1e18e3b_9.0.30729.6161_x-ww_028bc148
\Windows\winsxs\x86_Microsoft.VC90.MFCLOC_
1fc8b3b9a1e18e3b_9.0.30729.6161_x- mfc90chs.dll 9.0.30729.6161
ww_730c3508
\Windows\winsxs\x86_Microsoft.VC90.MFCLOC_
1fc8b3b9a1e18e3b_9.0.30729.6161_x- mfc90cht.dll 9.0.30729.6161
ww_730c3508
\Windows\winsxs\x86_Microsoft.VC90.MFCLOC_
1fc8b3b9a1e18e3b_9.0.30729.6161_x- mfc90deu.dll 9.0.30729.6161
ww_730c3508
\Windows\winsxs\x86_Microsoft.VC90.MFCLOC_
1fc8b3b9a1e18e3b_9.0.30729.6161_x- mfc90enu.dll 9.0.30729.6161
ww_730c3508
\Windows\winsxs\x86_Microsoft.VC90.MFCLOC_
1fc8b3b9a1e18e3b_9.0.30729.6161_x- mfc90esn.dll 9.0.30729.6161
ww_730c3508
\Windows\winsxs\x86_Microsoft.VC90.MFCLOC_
1fc8b3b9a1e18e3b_9.0.30729.6161_x- mfc90esp.dll 9.0.30729.6161
ww_730c3508
\Windows\winsxs\x86_Microsoft.VC90.MFCLOC_
1fc8b3b9a1e18e3b_9.0.30729.6161_x- mfc90fra.dll 9.0.30729.6161
ww_730c3508
\Windows\winsxs\x86_Microsoft.VC90.MFCLOC_
1fc8b3b9a1e18e3b_9.0.30729.6161_x- mfc90ita.dll 9.0.30729.6161
ww_730c3508
\Windows\winsxs\x86_Microsoft.VC90.MFCLOC_
1fc8b3b9a1e18e3b_9.0.30729.6161_x- mfc90jpn.dll 9.0.30729.6161
ww_730c3508
\Windows\winsxs\x86_Microsoft.VC90.MFCLOC_
1fc8b3b9a1e18e3b_9.0.30729.6161_x- mfc90kor.dll 9.0.30729.6161
ww_730c3508
\Windows\winsxs\x86_Microsoft.VC90.MFCLOC_
1fc8b3b9a1e18e3b_9.0.30729.6161_x- mfc90rus.dll 9.0.30729.6161
ww_730c3508
\Windows\winsxs\x86_Microsoft.VC90.OpenMP_
1fc8b3b9a1e18e3b_9.0.30729.6161_x- vcomp90.dll 9.0.30729.6161
ww_4ddc769f
x86_Microsoft.VC90.ATL_1fc8b3b9a1e18e3b_9.0.3
Global Assembly Cache
0729.6161_x-ww_92453bb7.cat
x86_Microsoft.VC90.ATL_1fc8b3b9a1e18e3b_9.0.3
Global Assembly Cache
0729.6161_x-ww_92453bb7.manifest
x86_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.3
Global Assembly Cache
0729.6161_x-ww_31a54e43.cat
x86_Microsoft.VC90.CRT_1fc8b3b9a1e18e3b_9.0.3
Global Assembly Cache
0729.6161_x-ww_31a54e43.manifest
x86_Microsoft.VC90.MFC_1fc8b3b9a1e18e3b_9.0.3
Global Assembly Cache
0729.6161_x-ww_028bc148.cat
x86_Microsoft.VC90.MFC_1fc8b3b9a1e18e3b_9.0.3
Global Assembly Cache
0729.6161_x-ww_028bc148.manifest
x86_Microsoft.VC90.MFCLOC_1fc8b3b9a1e18e3b_
Global Assembly Cache
9.0.30729.6161_x-ww_730c3508.cat
x86_Microsoft.VC90.MFCLOC_1fc8b3b9a1e18e3b_
Global Assembly Cache
9.0.30729.6161_x-ww_730c3508.manifest
x86_Microsoft.VC90.OpenMP_1fc8b3b9a1e18e3b_
Global Assembly Cache
9.0.30729.6161_x-ww_4ddc769f.cat
x86_Microsoft.VC90.OpenMP_1fc8b3b9a1e18e3b_
Global Assembly Cache
9.0.30729.6161_x-ww_4ddc769f.manifest
\PIPC\Procbook\SVG_Addin annotated12.jpg
\PIPC\Procbook\SVG_Addin annotated12.png
\PIPC\Procbook\SVG_Addin annotated14.jpg
\PIPC\Procbook\SVG_Addin annotated14.png
\PIPC\Procbook\SVG_Addin annotated16.jpg
\PIPC\Procbook\SVG_Addin annotated16.png
\PIPC\Procbook\SVG_Addin annotated32.jpg
\PIPC\Procbook\SVG_Addin annotated32.png
\PIPC\Procbook\SVG_Addin questionable12.jpg
\PIPC\Procbook\SVG_Addin questionable12.png
\PIPC\Procbook\SVG_Addin questionable14.jpg
\PIPC\Procbook\SVG_Addin questionable14.png
\PIPC\Procbook\SVG_Addin questionable16.jpg
\PIPC\Procbook\SVG_Addin questionable16.png
\PIPC\Procbook\SVG_Addin questionable32.jpg
\PIPC\Procbook\SVG_Addin questionable32.png
\PIPC\Procbook\SVG_Addin substituted12.jpg
\PIPC\Procbook\SVG_Addin substituted12.png
\PIPC\Procbook\SVG_Addin substituted14.jpg
\PIPC\Procbook\SVG_Addin substituted14.png
\PIPC\Procbook\SVG_Addin substituted16.jpg
\PIPC\Procbook\SVG_Addin substituted16.png
\PIPC\Procbook\SVG_Addin substituted32.jpg
\PIPC\Procbook\SVG_Addin substituted32.png
\PIPC\Procbook\SVG_Addin svg_addin.dll 3.5.0.284
\PIPC\Procbook\SVG_Addin SVG_ADDIN_DEFAULT.INI
\PIPC\Procbook\SVG_Addin\Export\PB a.xsl
\PIPC\Procbook\SVG_Addin\Export\PB animate.xsl
\PIPC\Procbook\SVG_Addin\Export\PB animatemotion.xsl
\PIPC\Procbook\SVG_Addin\Export\PB animatetransform.xsl
\PIPC\Procbook\SVG_Addin\Export\PB circle.xsl
\PIPC\Procbook\SVG_Addin\Export\PB colornames.xml
\PIPC\Procbook\SVG_Addin\Export\PB dataset.xsl
\PIPC\Procbook\SVG_Addin\Export\PB defs.xsl
\PIPC\Procbook\SVG_Addin\Export\PB desc.xsl
\PIPC\Procbook\SVG_Addin\Export\PB disable_default.xsl
\PIPC\Procbook\SVG_Addin\Export\PB ellipse.xsl
\PIPC\Procbook\SVG_Addin\Export\PB g.xsl
\PIPC\Procbook\SVG_Addin\Export\PB globalsymbols.xsl
\PIPC\Procbook\SVG_Addin\Export\PB hexmath.xsl
\PIPC\Procbook\SVG_Addin\Export\PB image.xsl
\PIPC\Procbook\SVG_Addin\Export\PB line.xsl
\PIPC\Procbook\SVG_Addin\Export\PB lookuptables.xsl
\PIPC\Procbook\SVG_Addin\Export\PB marker.xsl
\PIPC\Procbook\SVG_Addin\Export\PB path.xsl
\PIPC\Procbook\SVG_Addin\Export\PB pattern.xsl
\PIPC\Procbook\SVG_Addin\Export\PB PB_format_x.xsl
\PIPC\Procbook\SVG_Addin\Export\PB PB_layers.xsl
\PIPC\Procbook\SVG_Addin\Export\PB PB_msstate.xsl
\PIPC\Procbook\SVG_Addin\Export\PB PB_multistate.xsl
\PIPC\Procbook\SVG_Addin\Export\PB PB_refreshdata.xsl
\PIPC\Procbook\SVG_Addin\Export\PB PB_traceelem.xsl
\PIPC\Procbook\SVG_Addin\Export\PB PB_trendlogical.xsl
\PIPC\Procbook\SVG_Addin\Export\PB PB_XYPlotElems.xsl
\PIPC\Procbook\SVG_Addin\Export\PB PI_to_SVG.js
\PIPC\Procbook\SVG_Addin\Export\PB PI_to_SVG.xsl
\PIPC\Procbook\SVG_Addin\Export\PB PI_to_SVG_js.xml
\PIPC\Procbook\SVG_Addin\Export\PB polygon.xsl
\PIPC\Procbook\SVG_Addin\Export\PB polyline.xsl
\PIPC\Procbook\SVG_Addin\Export\PB rect.xsl
\PIPC\Procbook\SVG_Addin\Export\PB set.xsl
\PIPC\Procbook\SVG_Addin\Export\PB style_attribs.xsl
\PIPC\Procbook\SVG_Addin\Export\PB text.xsl
\PIPC\Procbook\SVG_Addin\Export\PB title.xsl
\PIPC\Procbook\SVG_Addin\Export\PB tokenize_colors.xsl
\PIPC\Procbook\SVG_Addin\Export\PB tspan.xsl
\PIPC\Procbook\SVG_Addin\Export\PB use.xsl
\PIPC\Procbook\SVG_Addin\Export\PB vbacode.xsl
Documentation Overview
These release notes are part of a documentation set that supports PI ProcessBook.
The set also includes:
PI ProcessBook User Guide: An introduction to PI ProcessBook for the end user.
This user guide provides a product overview, installation procedures, a tutorial to
acquaint you with the user interface, and other topics to allow you to work with and
troubleshoot PI ProcessBook.
Additional information, including the latest release notes, about PI ProcessBook and
other topics of interest can be found in respective documents available on the
OSIsoft Technical Support and Resources Web site.
OSIsoft, LLC
777 Davis St., Suite 250
San Leandro, CA 94577 USA
Tel: (01) 510-297-5800
Fax: (01) 510-357-8136
Web: http://www.osisoft.com
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, PI Coresight and RtWebParts are all
trademarks of OSIsoft, LLC. All other trademarks or trade names used herein are the property of their respective owners.
Published: 29-June-2015