PI ProcessTemplates Release Notes
EXELE Information Systems, Inc.
http://www.exele.com

---

Version 1.4.0.0 (February 2008)

Requirements
Minimum version	Template Manager	Template Monitor	Add-in for PI ProcessBook
PI Server 3.4.363.97	X	X	X
PI-SDK 1.3.5.338	X	X	X
PI-BatchView 3.1.1.1 (PR1) or later	X
PI ProcessBook 3.0.15.7 (PR1) OR later			X

Upgrading

• Users of ProcessTemplates version 1.3.x and before should uninstall the previous ProcessTemplates components using Add/Remove programs.  
  The uninstall will not remove your existing templates or settings
  As a precaution, you can make a backup your current ProcessTemplates directory.
• You should install this version to the same path unless you plan to move the local templates to the new installation location
• You should stop all current ProcessTemplate components before installing this version.
• Version 1.4 and later contains a single installation program where the user will select the desired components.
  Previous versions contained a separate installation for the Manager, Monitor and Addin.

Operating Systems

• EXELE recommends running ProcessTemplate products on one the following operating Systems:
  Windows 2000 Professional/Server
  Windows XP Professional
  Windows Server 2003

Version	Type (change/fix)	Application(s)	Description
General
1.4	Change	All	Exclusive use of PISDK and support for PI HA (High Availability) Previous versions used a combination of PIAPI and PISDK routines for PI communications. Version 1.4 is the first ProcessTemplates version to use the PISDK exclusively for all required PI communication. Use of the PISDK allows ProcessTemplates to utilize PI HA (High Availability).
1.4	Change	All	PI Unit Cache and PI Module enumeration at application startup Some of the PI Batch functionality available in the PIAPI and utilized by previous version of ProcessTemplates is not available through the PISDK. In order to provide the previous functionality, the ProcessTemplates applications need to enumerate the PI Modules in the ModuleDB to know which are PI Units. This list can be cached so that application start time is not impacted by this module enumeration.
1.4	Change	All	Support the Units without a unique name Previous versions only supported Units whose name was unique; the PI Module/Unit name used in ProcessTemplates did not include the path to the PI Modules. This prevented the use of Units if the same PI Unit name was used for multiple PI Modules in the Module Database. By default, ProcessTemplates will now use the full path name to the Unit when a Unit name is required. "Name-only" Unit names are still supported for backward compatibility.
1.4	Change	All	Support the integer tags as the measurement tag for a template Previous versions only supported float tags for the measurement tag. Integer tags are now supported.
Manager
1.4	Change	Manager	Configurable location for local template files Previous versions stored the local template files in the installation directory. Now, the Template Manager allows you to select a different location for the template files. This is required if you do not have write permission to the installation path.
1.4	Fix	Manager	Import of XY template may not preserve X-tag settings If an XY Template (tag vs. tag) was imported from the PI Server to the local machine, the local template may not preserve the X-tag settings during the import.  Opening the imported template could incorrectly show the template as "Y vs. time" instead of "Y vs. X"
1.4	Fix	Manager	Runtime error 384  docking maximized preview trend If a maximized preview trend was moved (dragged to a new location), the [Dock] button would appear at the top of the preview trend. Clicking [Dock] would result in "error 384 - a form can't be moved or sized while minimized or maximized".
1.4	Change	Manager	Maximize button removed from Preview Trend The separate maximize/restore button that was previously displayed above the Preview Trend has been replaced with a standard form maximize button in the upper right corner of the Preview Trend.
1.4	Change	Manager	Maximized Preview Chart partially hidden by Windows Task Bar The previous Preview Trend window would maximize to the screen size regardless of a displayed Windows Task Bar at the bottom of the screen. The bottom portion of the Preview Trend could be hidden by the Windows Task Bar. The maximized Preview Trend Window will now maximize with regard to the Windows Task Bar.
1.4	Change/Fix	Add-in	EXPEVALDELAY setting extended to PI UnitBatch Searches The ProcBook Addin contains an INI setting EXPEVALDELAY that was previously used for performing filter calls (used by partial UnitBatch templates) at the current PI Server time. In addition, this delay (default = 5 seconds) is now used as an offset for querying PI UnitBatches at current time to prevent the PISDK from incorrectly telling the Addin that there are no active UnitBatches. Symptom: Template limits from the Add-in DataSet may periodically show "Error" as the current template limit value for an active UnitBatch and Template. Cause and resolution: While refreshing a display, ProcessBook will query the Add-in for the template limit values at  "current time" by passing an absolute time (current time) to the Add-in as the both the start and end time of the time range. If this time is the current time of the PI Server (or very close to the current time of PI Server), the PISDK UnitBatch Search can incorrectly return 0 active UnitBatches even if there is an active UnitBatch at the passed time. Setting the UnitBatch search start time back by a few seconds will correctly return the active UnitBatch. The Add-in will use the EXPEVAL setting in the [Add-in] section of the INI file as the offset amount in seconds.  If missing, the default offset is 5 seconds.
1.4	Fix	Manager	"Subscript out of range" error Could occur if chosen UnitBatches for template creation were less than 1 minute in length
1.4	Fix	Manager	Error after searching for and selecting UnitBatches "Object not defined" Could occur if selecting UnitBatches by Unit name (not full path to unit), Unit name was not unique. and active UnitBatches existed with the same selected Unit name and time frame of selected UnitBatches. Error source: end time of active UnitBatches is not defined.
Monitor
1.4	Change	Monitor	Configurable location for Monitor log file Previous versions stored the ProcessTemplates Monitor log file (ptmon.log) in the installation directory. You may now specify a different path in the ProcessTemplates INI file.
1.4	Change	Monitor	Maximum size for monitor log file: 50MB The Monitor log file (ptmon.log) will not grow larger than 50 MB. If the log file maximum size is reached, new messages will not be added.
1.4	Fix	Monitor	Periodic CPU loading with a large number of Active Monitors (>100) With a large number of Active Monitors containing many template samples, CPU usage by PTMon could periodically spike to near 100% for many minutes. This was caused by the Monitor's memory usage requirements for large installations. Various performance changes along with improved memory usage have fixed this problem.
1.4	Fix	Monitor	New behavior if failure to connect to PI at Monitor startup If PTMON fails to connect to PI when started (e.g. PTMON is located on the PI Server and Services are set to automatically start at boot), it will now wait 5 minutes before attempting another connection. This delay is intended to provide enough time to allow PI to start before anther connection is attempted. Previous versions verified that PIMSGSS was running for 2 minutes before attempting to connect to PI, but Vista prevents PTMON from querying the run time of PIMSGSS.
1.4	Change	Monitor	Updated INI settings for Event Pipe Usage Optional settings allow more control on the use of EventPipes for updates to ModuleDB and PI Units. New setting UseEventPipesUnits. See help file/documentation for details.
1.4	Fix	Monitor	Error -75 getting exceptions Some installations could display this error in the ptmon.log file. The Monitor was unable to retrieve exception values for the measurement tags on the PI Server. PISDK EventPipes are now used to retrieve new measurement values, so this problem is no longer relevant.
1.4	Fix	Monitor	Template limits for Subbatch Templates could be shifted up to 60 seconds If the Monitor was delayed in recognizing the start of a new Subbatch, the template limits for a Subbatch template could be shifted by the amount of the delay. This has been fixed. See next item for cause of delay.
1.4	Change	Monitor	Monitor will force PollInterval of UnitBatch EventPipes The Monitor uses Unit (module) EventPipes in the PISDK to monitor the starting and stopping of UnitBatchs and Subbatches. The Monitor will now force the pollinterval of the Eventpipe to 1/2 the interval at which the Monitor checks for updates  (BatchUpdateInterval).  PISDK problem: The pollinterval of this Unit EventPipe is 60 seconds and not 5 seconds as stated in the PISDK documentation. This could cause an unexpected delay (up to 60 seconds) in recognition of a new UnitBatches and Subbatches

 

 

---

Version 1.3.0.10

Requirements
Minimum version	Template Manager	Template Monitor	Add-in for PI ProcessBook
PI Server 3.4.363.97	X	X	X
PI-SDK 1.3.3.304 (provided)	X	X	X
PI-BatchView 3.0 or later	X	X (Config only)
MS ADO 2.7 (provided)			X
IE5	X	X	X
PI ProcessBook 3.012.3 OR later			X

Upgrading

• Users of ProcessTemplates version 1.0 should uninstall using Add/Remove programs.  
  Users of version 1.1 or later can install this version without separately removing earlier version.
• You should stop all current ProcessTemplate components before installing this version.
• You should upgrade all 3 components (Monitor, Manger, ProcessBook Add) to this version at the same time.

Operating Systems

• ProcessTemplates installation uses Windows Installer 2.0
  If you are using Windows NT, you must have SP6 or later in order for the Windows Installer to work properly
• EXELE recommends running ProcessTemplate products on one the following operating Systems:
  Windows NT Workstation/Server SP6 or greater
  Windows 2000 Professional/Server
  Windows XP Professional
  Windows Server 2003

Installation

• ProcessBook Add-in installation will suppress warning for missing ProcessBook
  ActiveView users would receive an installation warning if ProcessBook was not found on the target machine. This warning is now suppressed unless ProcesBook exists and the version is not compatible with ProcessTemplates.
   

• Monitor installation could hang or display error if Terminal Services installed on target machine
  The ProcessTemplate Monitor installation could hang or display "error 1607" on Windows2000 Server and Windows2003 Server machines with Terminal Services installed. This has been fixed.

Monitor Configurator

• Error restoring Monitor Configuration backup
  Users may get error  "numitems not correct" while restoring a PT Monitor Configuration backup. This has been fixed
   

• "Only alarm on new snapshot values" now "Only alarm on measurement tag snapshot values"
  The last screen on the Active Monitor Configuration lets you suppress time-based comparison of measurement and template values and instead perform the comparison only when new measurement tag values appear. The checkbox text has been changed; the function of this setting has not changed.

Monitor

• Multiple Final RMS values output by Monitor
  It was possible for the Template Monitor to output multiple values to the RMS output tag when configured to output a "final RMS value" at the end of a template period. This situation would occur if (1) final RMS output value configured (2) "Alarm on snapshots" selected (3) a the snapshot timestamp for the measurement tag was the same as the final template timestamp. This has been fixed.

Add-in Registration tool

• Allows user to set "load on startup" behavior
  Previous versionsof the ProcessTemplates ProcessBook Add-in registered the Add-in for use in ProcessBook, but did not set the "load on startup" setting for the Add-in. The user could change the "load on startup" setting from within ProcessBook's Add-in Manager. The Add-in Registration tool now allows the user to configure the "load at startup" behavior of the ProcessTemplates Add-in.

Add-in

• Details Window did not display properly
  The Details Window is available on the ProcessTemplates toolbar in ProcessBook. This Windows appeared clipped and did not allow the user to scroll the detail information.

---

Version 1.3.0.8

Requirements
Minimum version	Template Manager	Template Monitor	Add-in for PI ProcessBook
PI Server 3.4.363.97	X	X	X
PI-SDK 1.3.1.247 (provided)	X	X	X
PI-BatchView 3.0 or later	X	X (Config only)
MS ADO 2.7 (provided)			X
IE5	X	X	X
PI ProcessBook 3.012.3 OR later			X

Upgrading

• Users of ProcessTemplates version 1.0 should uninstall using Add/Remove programs.  
  Users of version 1.1 or later can install this version without separately removing earlier version.
• You should stop all current ProcessTemplate components before installing this version.
• You should upgrade all 3 components (Monitor, Manger, ProcessBook Add) to this version at the same time.

Operating Systems

• ProcessTemplates installation uses Windows Installer 2.0
  If you are using Windows NT, you must have SP6 or later in order for the Windows Installer to work properly
• EXELE recommends running ProcessTemplate products on one the following operating Systems:
  Windows NT Workstation/Server SP6 or greater
  Windows 2000 Professional/Server
  Windows XP Professional
  Windows Server 2003
• The Template Monitor runs as a Service and must run on a Windows OS which supports Services.

Add-in

• Addin did not show active UnitBatch dataset limits if server time  < client time
  If the time zone of the PI Server resulted in a current time less than the current time of the client (ProcessBook), the template dataset column values (UL, CL, LL) did not appear for an active UnitBatch. For example, current time of PI Server is 10am when current time of client is 11am.

Monitor and Monitor Admin

• Template limits and monitored tag values truncated to whole number
  Monitor and Monitor Admin (Details window) truncated the measurement tag values and template limits to whole numbers (fractional portion always 0). This only occurred for users of certain Windows OS  versions (e.g. French Windows) where the regional settings use a comma as the decimal separator.  Problem did not occur in English Windows with regional settings using a comma as the decimal separator.

---

Version 1.3.0.7

Requirements
Minimum version	Template Manager	Template Monitor	Add-in for PI ProcessBook
PI Server 3.4.363.97	X	X	X
PI-SDK 1.3.1.247 (provided)	X	X	X
PI-BatchView 3.0 or later	X	X (Config only)
MS ADO 2.7 (provided)			X
IE5	X	X	X
PI ProcessBook 3.012.3 OR later			X

Upgrading

• Users of ProcessTemplates version 1.0 should uninstall using Add/Remove programs.  
  Users of version 1.1 or later can install this version without separately removing earlier version.
• You should stop all current ProcessTemplate components before installing this version.
• You should upgrade all 3 components (Monitor, Manger, ProcessBook Add) to this version at the same time.

Operating Systems

• ProcessTemplates installation uses Windows Installer 2.0
  If you are using Windows NT, you must have SP6 or later in order for the Windows Installer to work properly
• EXELE recommends running ProcessTemplate products on one the following operating Systems:
  Windows NT Workstation/Server SP6 or greater
  Windows 2000 Professional/Server
  Windows XP Professional
  Windows Server 2003
• The Template Monitor runs as a Service and must run on a Windows OS which supports Services.

Add-in

• Dataset offset if Client not in time zone of PI Server
  If the add-in was used on a client machine which was not in the same time zone as the PI Server, the ProcessTemplate dataset values (UL, CL, LL)were offset from the time of the measurement tag. This was originally fixed as 1.3.0.5 patch.
   
• Add-In Registration tool allows configuration for All Users or Current User
  The Add-in registration tool will now allow Add-in registration for the Current User or All Users (local machine). Previous versions registered the Add-in for the current user only. This was originally fixed as 1.3.0.5 patch.
   
• Add-in will not disconnect from PI Server(s)
  The add-in will not disconnect from any PI Servers when it is unloaded.
   
• Add-in error message "Type mismatch" when loading in ProcessBook
  This error was typically seen on machines using French regional settings. This has been fixed.
   
• Add-in may not display all selected dataset columns after checking for template updates
  If the user entered a non-0 update interval for "Check for template updates every...", the Add-in may only return data for the one dataset colum. This has been fixed.

Manager

• Fix: UnitBatch Search returned local start/end times
  The UnitBatch Search dialog returned the UnitBatch start and end times as local time. If the PI Server was in a different time zone, subsequent calls to retrieve measurement tag values from the PI Server did not correctly retrieve the values for the UnitBatch. Returned and stored UnitBatch times will now use the time of the PI Server. This was originally fixed as 1.3.0.5 patch.
   

---

Version 1.3.0.4

Requirements
Minimum version	Template Manager	Template Monitor	Add-in for PI ProcessBook
PI Server 3.4.363.97	X	X	X
PI-SDK 1.3.1.247 (provided)	X	X	X
PI-BatchView 3.0 or later	X	X (Config only)
MS ADO 2.7 (provided)			X
IE5	X	X	X
PI ProcessBook 3.0 OR later			X

Upgrading

• Users of ProcessTemplates version 1.0 should uninstall using Add/Remove programs.  
  Users of version 1.1 or later can install this version without separately removing earlier version.
• You should stop all current ProcessTemplate components before installing this version.
• You should upgrade all 3 components (Monitor, Manger, ProcessBook Add) to this version at the same time.

Operating Systems

• ProcessTemplates installation uses Windows Installer 2.0
  If you are using Windows NT, you must have SP6 or later in order for the Windows Installer to work properly
• EXELE recommends running ProcessTemplate products on one the following operating Systems:
  Windows NT Workstation/Server SP6 or greater
  Windows 2000 Professional/Server
  Windows XP Professional
  Windows Server 2003
• The Template Monitor runs as a Service and must run on a Windows OS which supports Services.

PI Batch Configuration

• The PI Batch Database (PIBatchDB) is used for all UnitBatch searches.
  To view existing batch data stored in the Batch Subsystem, you must first create copies of the units from the pibaunit table into the Module Database.  This step is described in the document "Batch Database Support of the PI Batch Subsystem" found on the OSI support website.  See the section of the document titled “Accessing Batch Subsystem Batches via the PI-SDK” for a step-by-step procedure. 
  
• Unit Alias usage is limited to Unit-level aliases in the Module Database 
  Aliases defined for submodules of the Unit module will not be visible from ProcessTemplates.

General

• New: XY Template Support
  Traditional templates are "Limit (Y) vs. Time" where Y is the measurement tag to monitor.  The limit value is typically based on the time into the UnitBatch or Subbatch.
  XY Templates are "Limit (Y) vs Value (X)" where X is another tag value. This allows you to create XY templates where the limit values are based on a range of X tag values. For example, you expect the Pressure (Y) to be between 190-210 if the Temperature (X) is 145.
  XY templates lend themselves to processes where the limits cannot be determined by "time into event".
   
• New: Second-level SubBatch filter support
  Previous versions allowed you to define SubBatch as the templates filter (e.g. template valid when stage=startup). The limitation was that this SubBatch must be a first-level SubBatch of the UnitBatch. ProcessTemplates now supports filters for 2 levels of SubBatches (e.g. stage = startup, step=heating).
   
• New: Localized number display
  ProcessTemplates will support the local setting for displaying numbers.
  Note that some date displays in ProcessTemplate applications will always default to English abbreviation for month.
   
• New: Template filter expressions can use PI Aliases
  Previous versions allowed you to create a template filter using PI tags (e.g. 'mytemp101tag' > 100). This filter can now use PI Alias names instead of explicit tag names so that the template can be used against multiple, similar Units. (e.g. 'unittemp' > 100).
   
• New: Template calculation method
  New template calculation method: CL +/- N Units
   
• Fix: Error for SubBatches with no PIHeading
  ProcessTemplates would report errors if a template used a SubBatch filter and the SubBatch did not have a PIHeading. The ProcessTemplate Addin, Manager and Monitor will now properly handle pisubbatch.piheading = nothing.
   
• Fix: Error reading templates if regional settings use a comma for the decimal separator
  ProcessTemplates did not properly read stored local templates if the regional settings of the machine use a comma for the numeric decimal separator. This has been fixed.
  In addition, the Template Manager allows you to perform various exports (template limits and batch samples) and imports (template limits) using a CSV file. Since using the comma as a decimal separator will cause problems parsing these files, the Template Manager will use the semicolon (;) in place of the comma when importing and exporting CSV files in these regions.
   

Manager

• New: Comparison chart added
  The comparison chart allows you visually compare 2 templates by overlaying the template limits on the same chart.
   
• New: Template chart can be undocked from main form.
  The template preview chart is now a floating window which can be resized independently of the main Manager window.
   
• New: Template chart can print chart with or without surrounding form
  The template chart can print the chart or the chart and the surrounding form information (legend, etc.).
   
• Fix: Count error returning UnitBatches
  Manager would give error message when searching for UnitBatches if more than one UnitBatch was returned for a time range expected to return one UnitBatch.
  The search is using the saved start and end time of a UnitBatch and expects one UnitBatch returned. If the start time of the next UnitBatch is the same as the end time of the expected UnitBatch, the search will return both UnitBatches. This error message has been fixed and the correct UnitBatch will be used.
   
• Fix: Time match error
  Message would occur if a UnitBatch used to construct a template contained non-0 millisecond portion for the UnitBatch's start or end time. The start/end time of the
  retrieved UnitBatch (with ms) did not match the start/end time displayed in the listbox (no ms). This has been fixed.
   

Monitor

• New: UnitBatch Eventpipes
  The Monitor will now use UnitBatch Eventpipes for monitoring UnitBatch and Subbatch starts and stops. This results in better Monitor performance since it will no longer need to continuously query PIBatch to look for changes. Note that this feature is only available for Batch DB UnitBatches (e.g. PIBaGen) and not for older Batch Subsystem batches.
   
• New: Final Duration and Final RMS output
  Previous versions of ProcessTemplates allow you to output the template Duration and RMS to PI tags. These are continuous outputs which have good values while the template is valid (UnitBatch, SubBatch, ...). You may now configure these outputs such that a single, final value (final Duration or final RMS) is output at the end of the template's valid period. 
   

Add-in

• Fix: Error on exit if Add-in did not load any datasets
  If the add-in was loaded but did not contain any datasets (no Active Monitors exist or a group filter was used), the user would get an error when exiting ProcessBook. This has been fixed.
   
• Fix: Add-in Groups filter may not read entire list of group names
  If you created Active Monitor Groups to filter the list of Active Monitors loaded into ProcessBook, the list of Active Monitor Groups names could become long enough to exceed the allocated buffer. The total length of the group names in the filter could not exceed 100 characters. This has been fixed.
   
• FinalDuration Column
  New template dataset column: FinalDuration. This dataset will output a single value at the template end time containing the final duration of the template. 

---

Version 1.2.0.7

Requirements
Minimum version	Template Manager	Template Monitor	Add-in for PI ProcessBook
PI Server 3.3.361.43	X	X	X
PI-SDK 1.3.1.247 (provided)	X	X	X
PI-BatchView 3.0 or later	X	X (Config only)
MS ADO 2.7 (provided)			X
IE5	X	X	X
PI ProcessBook 2.3 OR later			X

Upgrading

• Users of ProcessTemplates version 1.0 should uninstall using Add/Remove programs.  
  Users of version 1.1 or later can install this version without separately removing earlier version.
• You should stop all current ProcessTemplate components before installing this version.
• You should upgrade all 3 components (Monitor, Manger, ProcessBook Add) to this version at the same time.

Operating Systems

• ProcessTemplates installation uses Windows Installer 2.0
  If you are using Windows NT, you must have SP6 or later in order for the Windows Installer to work properly
• EXELE recommends running ProcessTemplate products on one the following operating Systems:
  Windows NT Workstation/Server SP6 or greater
  Windows 2000 Professional/Server
  Windows XP Professional
  Windows Server 2003
• The Template Monitor runs as a Service and must run on a Windows OS which supports Services.

PI Batch Configuration

• The PI Batch Database (PIBatchDB) is used for all UnitBatch searches.
  To view existing batch data stored in the Batch Subsystem, you must first create copies of the units from the pibaunit table into the Module Database.  This step is described in the document Batch Database Support of the PI Batch Subsystem found on the OSI support website.  See the section of the document titled “Accessing Batch Subsystem Batches via the PI-SDK” for a step-by-step procedure. 
  
• Unit Alias usage is limited to Unit-level aliases in the Module Database 
  Aliases defined for submodules of the Unit module will not be visible from ProcessTemplates.

Manager

• Count error retrieving UnitBatches 
  If UnitBatches used in a template are contain non=0 milliseconds in the UnitBatch start or end time, the Manager would display "count error getting UnitBatch". This has been fixed.
   
• Error creating SubBatch filter if SubBatch does not contain a PI Heading
  Attempting to create a SubBatch filter expression for a SubBatch which does not contain a PI Heading would result in the error "object variable or with block not set". This has been fixed.

Add-in

• Clipboard error creating ToolBar
  If the current user did not have permission to add items to the clipboard, the message "Error creating ProcessTemplates toolbar" was displayed. This has been fixed.
   

 

---

Version 1.2.0.6

Requirements
Minimum version	Template Manager	Template Monitor	Add-in for PI ProcessBook
PI Server 3.3.361.43	X	X	X
PI-SDK 1.3.1.237 (provided)	X	X	X
PI-BatchView 3.0 or later	X	X (Config only)
MS ADO 2.7 (provided)			X
IE5	X	X	X
PI ProcessBook 2.2 OR later			X

Upgrading

• Users of ProcessTemplates version 1.0 should uninstall using Add/Remove programs.  
  Users of version 1.1 or later can install this version without separately removing earlier version.
• You should stop all current ProcessTemplate components before installing this version.
• You should upgrade all 3 components (Monitor, Manger, ProcessBook Add) to this version at the same time.

Operating Systems

• ProcessTemplates installation uses Windows Installer 2.0
  If you are using Windows NT, you must have SP6 or later in order for the Windows Installer to work properly
• EXELE recommends running ProcessTemplate products on one the following operating Systems:
  Windows NT Workstation/Server SP6 or greater
  Windows 2000 Professional/Server
  Windows XP Professional
  Windows Server 2003
• The Template Monitor runs as a Service and must run on a Windows OS which supports Services.

PI Batch Configuration

• The PI Batch Database (PIBatchDB) is used for all UnitBatch searches.
  To view existing batch data stored in the Batch Subsystem, you must first create copies of the units from the pibaunit table into the Module Database.  This step is described in the document Batch Database Support of the PI Batch Subsystem found on the OSI support website.  See the section of the document titled “Accessing Batch Subsystem Batches via the PI-SDK” for a step-by-step procedure. 
  
• Unit Alias usage is limited to Unit-level aliases in the Module Database 
  Aliases defined for submodules of the Unit module will not be visible from ProcessTemplates.

General

• Templates using offsets
  If user configured a template which used offsets where "offset start = 0" and "offset duration= x", the ProcessTemplates Monitor and ProcessBook Addin incorrectly shifted the template 1 sample rate (based on the template sample rate) into the unit batch. This had been fixed and released as patch 1.2.0.5 and is included in 1.2.0.6

Manager

• Count error retrieving UnitBatches 
  If UnitBatches used in a template are configured to use batch active type "step", the end time of one UnitBatch is the start time of the next UnitBatch. In this case the Manager would display an error that 2 UnitBatches existed during the desired period.  This has been fixed.

---

Version 1.2.0.4

Requirements
Minimum version	Template Manager	Template Monitor	Add-in for PI ProcessBook
PI Server 3.3.361.43	X	X	X
PI-SDK 1.3.0.209 (provided)	X	X	X
PI-BatchView 3.0 or later	X	X (Config only)
MS ADO 2.7 (provided)			X
IE5	X	X	X
PI ProcessBook 2.2 OR later			X

Upgrading

• Users of ProcessTemplates version 1.0 should uninstall using Add/Remove programs.  
  Users of version 1.1 can install this version without separately removing version 1.1.
• You should stop all current ProcessTemplate components before installing this version.
• You should upgrade all 3 components (Monitor, Manger, ProcessBook Add) to this version at the same time.

Operating Systems

• ProcessTemplates installation uses Windows Installer 2.0
  If you are using Windows NT, you must have SP6 or later in order for the Windows Installer to work properly
• EXELE recommends running ProcessTemplate products on one the following operating Systems:
  Windows NT Workstation/Server SP6 or greater
  Windows 2000 Professional/Server
  Windows XP Professional
  Windows Server 2003
• The Template Monitor runs as a Service and must run on a Windows OS which supports Services.

PI Batch Configuration

• The PI Batch Database (PIBatchDB) is used for all UnitBatch searches.
  To view existing batch data stored in the Batch Subsystem, you must first create copies of the units from the pibaunit table into the Module Database.  This step is described in the document Batch Database Support of the PI Batch Subsystem found on the OSI support website.  See the section of the document titled “Accessing Batch Subsystem Batches via the PI-SDK” for a step-by-step procedure. 
  
• Unit Alias usage is limited to Unit-level aliases in the Module Database 
  Aliases defined for submodules of the Unit module will not be visible from ProcessTemplates.

General

• Connection to PI Server containing PI Batch requires PI-SDK connection 
  Previous versions used the PI-API for all PI Batch access. PI-SDK use now required and a connection/login is performed to this PI Server.
  
• Login Dialog would not cache "Automatically connect" setting within current application
  Changing the setting of "Automatically connect" would save the setting but would not show the change if the Login dialog was viewed again in the current application. This has been fixed.
  
• Subbatch Support for Partial UnitBatch templates
  Previous versions supported a "sub-event expression" which allowed creation of templates for a portion of the entire UnitBatch. This expression involved PI tags. 
  While this Event Expression is still supported, a  partial UnitBatch template can also be created using a SubBatch expression. This requires SubBatch configuration in the PIBatchDB for the Unit.
  
• Active Monitor UnitGroup support added
  Previous versions supported Active Monitor Groups to allow the Monitor and ProcessBook Addin access to a subset of the total list of configured Active Monitors.
  UnitGroups allow you to create Active Monitor Groups which contain mutually exclusive Active Monitors for a single Unit (for example, separate phases/steps of different products). The Group’s Active Monitors are then concatenated to create a single, accessible set of data from PI ProcessBook. 
  
• Enable/Disable Active Monitor 
  Active Monitors can now be individually enabled/disabled through a checkbox in the Active Monitor Configuration application. The Monitor and Add-in will disregard Active Monitors which are disabled. 
  

Manager

• Event expression second tag digital states not correct
  When creating an event expression, if the second tag in the expression was a digital PI tag, the drop-down of valid digital states was not correctly filled
  

Monitor Configurator

• Can now edit Active Monitor name on "Choose Template" dialog
  The first of the three dialogs used for Active Monitor configuration now allows you to change the Active Monitor name. 
  
• Delta CL added as optional output tag
  Delta CL has been added as a new optional output tag for an Active Monitor. Delta CL is the difference between the measurement tag being monitored and the template's center line value (CL).  
  
• Enable/Disable Active Monitors
  In previous versions, all Active Monitors were assumed "enabled". There is now a check box at the start of each Active Monitor row allowing the user to enable (check) or disable (uncheck) each Active Monitor.
  

Monitor

• Monitor crash when Service set to AutoStart
  PI-SDK Version 1.3 (distributed with PI BatchView 3.0) introduced an issue with PI-SDK Clients attempting to connect to PI as the PI System is starting. This problem is explained at OSI's support site:
  http://support.osisoft.com/progtools/pisdk/reportedproblems.htm
  The ProcessTemplate Monitor will handle this issue and will successfully start. 
  
• Monitor will run with no Active Monitors or Active Monitors in error
  Previous versions would verify all Active Monitors before successful startup. If one or more Active Monitors were in error, the startup would not succeed. 
  
• Monitor will only watch enabled Active Monitors
  Monitor will read the "Disabled" property of each Active Monitor (set in the Active Monitor Configuration) and disregard those which are disabled. On startup, log file will display a message concerning any disabled Active Monitors. 
  
• EventPipe support added for ModuleDB
  Allows the monitor to look for changes to templates and active monitors only if there has been a change in the ModuleDB. Previously, the monitor was required to re-read the template and active monitor configuration from the ModuleDB to check for changes. Use of EventPipe for ModuleDB changes can be turned off through INI setting UseEventPipes.

Monitor Admin

• Minimize to System tray removed
  When minimized, will not use the System Tray
  

ProcessBook Add-In

• Addin File name changed
  Previous versions used the names pta_22x.dll and pta_21x.dll based on the target PI ProcessBook version. Current Addin file name is PTAddin.dll and works with ProcessBook version 2.2 and later.
  
• Addin supports return of 5000 Data Set values to ProcessBook
  Previous limit was 2000. Requires (3-Mar-2003) ProcessBook 2.3.x Patch - 
  Trend32.dll (v2.3.3) - The patch corrects a visualization problem that has been observed in trends with more than 2000 data points on a trace.
  
• ActiveView problem loading ProcessTemplate Toolbar ProcessBook
  The Addin Load behavior for ActiveView is inherited from ProcessBook. Therefore, a "Load on Startup" setting in ProcessBook will automatically load the Add-in in ActiveView. 
  ProcessTemplates Addin displays a ProcessTemplates toolbar in ProcessBook. Since ActiveView does not have a ToolBar, the attempt to add a ProcessTemplate toolbar would fail and display a message to the user. The toolbar will no longer be loaded if the hosting application is ActiveView.
  
• Add-in will only load enabled Active Monitors
  Add-in will read the "Disabled" property of each Active Monitor (set in the Active Monitor Configuration) and disregard those which are
  
• Add-in may not refresh future dataset values
  If the end time of a trend was set to a future date (e.g. *+10m), the Add-in will display template data set values during this future time. Under certain conditions, this future data would not refresh as time progressed, even if the Add-in was configured to refresh future trends. This has been fixed.
  
  

---

Version 1.1 (1.1.0.7)

Requirements
Minimum version	Template Manager	Template Monitor	Add-in for PI ProcessBook
PI Server 3.3.361.43	X	X	X
PI-SDK 1.2.0.168 (provided with install)	X	X	X
PI-BatchView Client 2.1 or later	X	X (Config only)<