EDAS to PI Data Reconciliation Utility



E-DAS to PI

Data Reconciliation Utility

Version 1.0.0.104

How to Contact Us

| |

|OSIsoft, Inc. |Worldwide Offices |

|777 Davis St., Suite 250 |OSIsoft Australia |

|San Leandro, CA 94577 USA |Perth, Australia |

| |Auckland, New Zealand |

|Telephone |OSI Software GmbH |

|(01) 510-297-5800 (main phone) |Altenstadt, Germany |

|(01) 510-357-8136 (fax) |OSI Software Asia Pte Ltd. |

|(01) 510-297-5828 (support phone) |Singapore |

| |OSIsoft Canada ULC |

|techsupport@ |Montreal, Canada  |

| |OSIsoft, Inc. Representative Office |

|Houston, TX |Shanghai, People’s Republic of China  |

|Johnson City, TN |OSIsoft Japan KK |

|Mayfield Heights, OH |Tokyo, Japan  |

|Phoenix, AZ |OSIsoft Mexico S. De R.L. De C.V. |

|Savannah, GA |Mexico City, Mexico  |

|Seattle, WA | |

|Yardley, PA | |

|Sales Outlets and Distributors |

|Brazil |South America/Caribbean |

|Middle East/North Africa |Southeast Asia |

|Republic of South Africa |South Korea |

|Russia/Central Asia |Taiwan |

| |

|WWW. |

|OSIsoft, Inc. is the owner of the following trademarks and registered trademarks: PI System, PI ProcessBook, Sequencia, |

|Sigmafine, gRecipe, sRecipe, and RLINK. All terms mentioned in this book that are known to be trademarks or service marks |

|have been appropriately capitalized. Any trademark that appears in this book that is not owned by OSIsoft, Inc. is the |

|property of its owner and use herein in no way indicates an endorsement, recommendation, or warranty of such party's |

|products or any affiliation with such party of any kind. |

| |

|RESTRICTED RIGHTS LEGEND |

|Use, duplication, or disclosure by the Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of the |

|Rights in Technical Data and Computer Software clause at DFARS 252.227-7013 |

| |

|Unpublished -- rights reserved under the copyright laws of the United States. |

| |

|© 2002-2005 OSIsoft, Inc. PI_ESCEDAS_EPRUtility.doc |

Table of Contents

Introduction 1

Reference Manuals 2

Supported Features 2

Running EPR Interactively 5

Connecting to the Servers 6

Specifying the Tag Criteria 9

Retrieving and Selecting Tags 10

Reconciling Tags 12

Logging Messages 14

Loading a Configuration File 16

Specifying Auto-Load Information 16

Determining Version 18

Running EPR Automatically 19

Setting up a Configuration File 19

Running EPR from the Command Line 19

Editing the PI Trust Table 20

Logging Messages in Automated Mode 21

Using EPR with the Windows Scheduler 22

Other Considerations 25

Appendix A: Using Time Offsets 27

Revision History 29

Introduction

PI-EDAS is the interface between PI and the Environmental Systems Corporation (ESC) E-DAS software application. In the E-DAS system it is common for users to qualify data. For qualification, averaged data is processed with a set of certified calculations and the original data is then replaced with the qualified data for that time period. Then it is usual to send this updated data to PI. The EDAS to PI Data Reconciliation utility (EPR) is the tool with which a user can import edited (qualified) values from the EDAS system into PI after making manual qualification adjustments to the existing data. This action is termed reconciliation. With EPR, the user browses for the PI tags, given certain criteria such as point source, interface ID number, and E-DAS data type, and then updates them for given a time range (reconciliation period).

It is possible to use EPR interactively from a graphical user interface or to run it from the command line. When EPR runs from the command line, the user can schedule reconciliations to run automatically, reducing the need for manual intervention.

The PI-EDAS to PI Reconciliation Utility (EPR) has the following system requirements.

• Windows NT( 4.0 / Windows 2000 or later for Intel( Processors.

• 64 MB RAM (Windows NT systems), or 128 MB RAM (Windows 2000 systems).

• 5 MB available disk space.

• Intel Pentium( Processor.

• PI-API.

• PI-SDK.

• At least one remote E-DAS Expert for UNIX or E-DAS EMR for Windows Server and the E-DAS API. The E-DAS API must be resident on the same computer system that the EPR will run on.

Reference Manuals

OSIsoft

• Environmental System E-DAS interface to the PI System

Environmental Systems Corporation

• E-DAS Expert for UNIX User’s Guide, or E-DAS EMR for Windows User’s Guide

• E-DAS API Installation Instructions

Supported Features

|Feature |Support |

|Platforms |NTI (Windows NT/2000/XP, Windows Server 2003, Intel) |

|PI Point Types |Real / Digital / Integer / float 16 / string |

|Outputs from PI |No |

|Inputs to PI |User Initiated or Scheduled |

|Maximum Point Count |N/A |

|Uses PI-SDK |Yes |

|* Source of Timestamps |E-DAS |

|* Vendor Software Required on PI-API / PINet Node |Yes |

|Vendor Software Required on Foreign Device |No |

|Vendor Hardware Required |No |

* See paragraphs below for further explanation.

Source of Time Stamps

The time stamps used by the EPR Utility are taken from the E-DAS server and converted to UTC (Coordinated Universal Time) before being sent to the PI System. This ensures that all timestamps are unambiguous, even when transporting values and timestamps across time zone boundaries. When values are retrieved from the PI System their time stamps will be relative to the PI System’s local time. For example, if the EPR Utility reads a value from the E-DAS server with a time stamp of 6:00 P.M., and the E-DAS server is in the Eastern Standard Time Zone (UTC – 5), the time stamp will be adjusted to 11:00 P.M. and then sent to the PI System. If the PI System is in the Pacific Standard Time Zone (UTC – 8) it understands UTC and that the time stamp should actually be 3:00 P.M. Because we are using UTC this also handles cases where the E-DAS server and the PI System are observing different daylight savings time settings. Please see Appendix A: Using Time Offsets for more information on how time stamps are handled.

Vendor Software Required

The E-DAS API (provided by ESC) communicates only with the E-DAS Server. You must install the E-DAS API (edasapi.dll and supporting files) on the same PI-API node as the E-DAS to PI Reconciliation Utility (EPR).

Running EPR Interactively

The E-DAS to PI Data Reconciliation Utility (EPR) supports two modes of operation, interactive operation and automated operation.

• For interactive operation the user must start the application and do all required operations manually. This operation is described in this section.

• For Automated operation the user must start EPR from the command line using parameters that specify a configuration file. Automated operation, described in the “Running EPR Automatically” section, requires no further intervention on the part of a user.

To start EPR interactively, follow the steps below.

1. On the Start menu, point to Programs.

2. Point to PI System and click E-DAS to PI Reconciliation Utility. The E-DAS Reconciliation Utility dialog box appears as shown below.

[pic]

Connecting to the Servers

After starting EPR, you need to connect to PI and the EDAS servers. Follow the steps below.

1. Connect to PI by clicking the PI Connections button, as shown below. The Connections dialog box appears.

[pic]

3. If your desired PI Server appears in the Servers field, select it and click Connect. If your desired PI server is not in the list, click Add to define a new connection. After you click Connect and close the Connections dialog box, the PI Server appears in the Active PI Server list with the status Connected, as shown below. This is the PI Server that will be used for reconciliation.

[pic]

Note: To connect automatically to this PI Server each time you start EPR, select the Reconnect each time EPRUtil is started checkbox.

After you connect to the PI Server, connect to the E-DAS server. Follow the steps below.

1. Connect to the EDAS Server by entering the server name in the E-DAS Server field, as shown below.

2. Click Connect. A Connected message appears in the Status field.

[pic]

Note: To connect automatically to this EDAS Server each time you start EPR, select the Reconnect each time EPRUtil is started checkbox.

Specifying the Tag Criteria

After you have connected to the PI and E-DAS servers, you need to display the tags that you want to update in PI. Follow the steps below.

1. Click the Tag Search Criteria tab.

[pic]

2. Select the Point Source or enter the Point Source value manually.

3. Select the Interface Instance ID # or enter the ID # manually.

4. Select the E-DAS data types to search for.

5. Enter a value for the Average value starting system digital state.

6. To retrieve the tags, see the Retrieving and Selecting Tags section.

Retrieving and Selecting Tags

This section assumes that you have already specified the tag search criteria as described in the “Specifying the Tag Criteria” section.

[pic]

1. Click the Reconciliation tab.

2. Enter a search mask in the Tag Mask field to restrict the tag search. If you leave this field blank or enter an asterisk (*), the search returns all tags specified on the Tag Search Criteria tab. If you enter text into the Tag Mask field with no asterisk (*) the search attempts to return a tag with a name matching the text exactly as it is typed. In short, the asterisk (*) is used to specify a “wildcard” character or string.

Examples of using the Tag Mask functionality:

|Tag Mask |Possible Return Values |

|EDASAvgValue |Only a tag named EDASAvgValue |

|EDASAvg* |Any tag that starts with EDASAvgValue such as EDASAvgValue and EDASAvgVal2 |

|*Val |Every tag that ends with the text “Val” |

|*Cal* |Every tag that contains the text “Cal” anywhere in its name |

|* or blank text |Every tag that matches the criteria set in the Tag Search Criteria tab |

3. After entering the Tag Mask, click Get Tags to retrieve the tags from PI. The tag names appear in the Tag Selection field. To stop the tag search, click Stop.

The figure below shows the use of the Tag Mask feature to restrict the tags returned to those that have a name that begins with the text EDAS.

[pic]

7. To select a tag for reconciliation, click its name in the Tag Selection field. A selected tag will be colored blue. You can also click Expanded View and select tags in the dialog box that appears. To select multiple tags press and hold the control (Ctrl) key while clicking each additional tag name. To select tags on multiple adjacent rows, click the uppermost or lowermost row and press and hold the shift key while clicking another row.

Click a heading (Tag Name, Extended Descriptor, etc.) to sort the entire list of tags based on the values within that column.

8. To reconcile the tags, see the Reconciling Tags section.

Reconciling Tags

This section assumes that you have already retrieved and selected the tags as described in the “Retrieving and Selecting Tags” section.

To reconcile the tags (update them in the PI database), follow the steps below.

1. Enter a starting and ending time in the Starting Time and Ending Time fields. The times can each be relative times or absolute times.

[pic]

An absolute time must take the following form: dd-mmm-yy hh:mm:ss where dd represents a 2 digit day, mmm represents a 3 letter English abbreviation for a month such as Jan for January or Feb for February, yy represents a 2 digit year, hh represents a 1 or 2 digit hour, mm represents a 2 digit minute, and ss represents a 2 digit second (seconds may be omitted if desired). If the entire hour, minute, second portion of the timestamp is omitted it will default to midnight (00:00:00) but will not be displayed.

In the use of relative times, note that the asterisk character (*) will resolve to the current local time as defined on the EPR computer system. Therefore *-7d resolves to the time “Now” minus 7 days, or seven days previous to the current time. For example, if the starting time is specified as *-72h and the ending time is specified with an asterisk (*), the reconciliation updates data from the previous 72 hours until “Now”, where “Now” is the current local time for the computer running EPR.

Be sure that the starting time is before the ending time, especially when you are using one relative time and one absolute time, or two relative times.

2. This step involves the Time Offset setting, which is optional, and not recommended for most cases. If you are running EPR in a situation where the EDAS Server is in a different time zone than the PI Server, and/or the PI Server observes daylight savings time (while the E-DAS server does not), and you wish to translate time stamps to be relative to a time zone other than that on the E-DAS server, than you may use the Time Offset feature to accomplish this. To do so, select the Use Time Offset checkbox as shown below. The Time Offset field and its associated Set button become available.

Note: This is a major change from previous versions of the E-DAS to PI Reconciliation Utility. This version of EPR internally converts all timestamps to UTC (Coordinated Universal Time) before sending values from E-DAS to PI. This maintains unique time stamps across time zones and DST settings making the use of the Time Offset undesirable in most cases. More detailed information about using the Time Offset functionality can be found in Appendix A.

[pic]

Enter the time offset. Time offsets should be entered and viewed as being relative to the E-DAS Server. Only hour and minute intervals are recognized, and they must be formatted in the form of a plus or minus, followed by an integer, immediately followed by an h, for hours, or m, for minutes. For example, enter +1h if the E-DAS Server is 1 hour ahead of the PI Server. Enter -5h if the E-DAS Server is 5 hours behind the PI Server.

Click the Set button associated with the Time Offset field. EPR validates the time offset. EPR also validates the time offset prior to each reconcile; that is, when the Reconcile button is clicked or when an automated reconcile is executed.

9. Click Reconcile to update the tags in PI.

[pic]

The Status field displays the progress and any error messages that occur. Messages from the Status field are also sent to the pipc log file. To help with readability EPR messages in the pipc log file are prefaced with “EPR>”.

Logging Messages

EPR logs its messages to an EPR-specific log file in a folder named “Logs”, to the PIPC.log file of the Active PI Server, and to the Status field of EPR when it is running in interactive mode. The EPR-specific log file is named EPRUtil_dd-mm-yyyy.log where dd represents a 1 or 2 digit day, mm represents a 1 or 2 digit month, and yyyy represents a 4 digit year. Each log file contains only the messages for the day which it represents. EPR creates a new log file each day, but only if EPR is run on that day and messages need to be logged.

EPR always writes to the PIPC.log file of the Active PI Server when a connection to a PI server exists. This behavior cannot be altered. However, it is possible to configure how EPR handles its own log files.

To access the logging options, on the Options menu click Logging. The EPRUtil Logging dialog box appears, as shown below:

[pic]

To disable the logging feature, select the Enable EPRUtil Logging checkbox to remove the check.

Specify the lifetime for the log files by entering a value in the Number of Days to Maintain Log Files field. This allows you to control the amount of disk space used for EPR logging and makes it easier to find logs for a specific date. The number of log files maintained in the Logs folder will not exceed the value specified in this field.

Note: When you need to create a new log file, any file in the Logs folder with a name matching the form of EPRUtil_*.Log, and that was created prior to the length of time specified in the Number of Days to Maintain Log Files field will be deleted.

To prevent the deletion of a log file, rename it so that it does not match the form of EPRUtil_*.Log, or remove it from the Logs directory.

EPR-specific log files that are currently in the Logs folder appear in the Current Log Files field. To open a file in Notepad, double-click the name.

[pic]

Loading a Configuration File

It is possible to save an EPR configuration and reload it instead of choosing options manually every time you need to reconcile data. To do this, on the File menu, click Save Configuration and enter a file name for the configuration file. To load the configuration, on the File menu, click Load Configuration and select the configuration file to load.

[pic]

When a configuration file is saved any specified PI tags, along with their configuration, are saved in the configuration file. Then when an EPR reconcile is executed using the saved EPR configuration the specified PI tags, and their configurations, are read from the file so that the utility knows which tags to reconcile. The current PI tag configuration for each specified PI tag is then pulled from the PI Server and compared against the PI tag configuration saved in the EPR Configuration file. If a change is detected a message will be written to the log files and the reconciliation will be marked as failed; that is it will return a status of 0x01. However, the reconciliation will be attempted for each specified PI tag, even those where a change has been detected, using the configuration read from the PI Server. This mechanism is in place to detect changes in tag configuration and report them to the user. It will not prevent the reconciliation from executing. To prevent the messages from being displayed the user should run “Get Tags” to get the latest tag configuration from the PI Server and re-save the EPR configuration file.

Specifying Auto-Load Information

Enable the Auto Load Interface Information feature to have EPR automatically enumerate each Point Source and Interface ID# that exists on a PI Server when the Active PI Server is first connected to and/or changed. Enumerating this information can take a significant amount of time for PI Systems that have a large number of tags.

To enable the Auto Load Interface Information feature, on the Options menu, select Auto Load Interface Info, as shown below.

[pic]

When using the Auto-Load Interface feature the drop down lists for Point Source and Interface ID# parameters on the Tag Search Criteria tab are populated such that as a user you only have to pick from the list.

Determining Version

To determine the version of EPR, on the About menu, click About EPRUtil, as shown below.

[pic]

Running EPR Automatically

Before you can use EPR in an automated mode, you must create a configuration file. An EPR configuration file is a text-based file that contains all the information necessary to reconcile data between an E-DAS system and a PI System.

Note: It is recommended that you not edit an EPR configuration file manually.

Setting up a Configuration File

To create a configuration file, you need to start EPR interactively and configure each option/parameter. To do this, follow the procedures in the “Running EPR Interactively” section. Then save a configuration file as described in the “Loading a Configuration File” section. EPR prompts you to enter a file name; by default the extension is .epr. However, any extension is valid as long as the configuration file is formatted correctly. EPR automatically saves configuration files in a subdirectory named “Configs” that is within the EPR installation directory.

When you install EPR, the .epr file extension is associated with the EPR executable file. If you double-click a valid *.epr file within Windows Explorer, EPR opens with the settings configured in the file.

Running EPR from the Command Line

To run EPR from the command line, set the working folder to the following:

Program Files\PIPC\Interfaces\ESCEDAS

Then enter the following command:

eprutil .epr

This starts EPR in the interactive mode with settings specified in the file. To run a reconciliation automatically include the /s switch.

Eprutil .epr /s

When you specify the configuration file at the command line, use any relative or fully qualified path and filename. However, UNC paths are not supported. If the name of your configuration file contains any spaces, enclose the name in double quotation marks.

Example of using a relative configuration file:

eprutil .\Configs\SampleReconciliation.epr /s

Example of using a fully qualified configuration path and filename with spaces:

eprutil D :\MyConfigFiles\ »Sample Reconciliation.epr »

Before using configuration files to start EPR in automated mode, it is recommended that you load them into EPR manually and test the reconciliation first.

Editing the PI Trust Table

Before EPR can automatically connect to a PI Server, a valid trust table entry must exist on each PI Server to which EPR will be connecting. This requirement is required due to security rules that are part of the PI System architecture. With a trust table entry, no user information or passwords are required to be stored and tracked by EPR.

In order to edit the trust table, use the piconfig utility that ships with every PI Server, shown here, or you may use the PI System Management Tools. An example of how to use piconfig to list the trust table entries for a PI Server is shown below.

[pic]

The following commands show how to add a trust table entry for EPR.

[pic]

The following commands show how to verify that the new entry is correct and to exit piconfig.

[pic]

This trust table entry allows a user to connect to the PI Server through the trust table authentication from any computer using EPR.

Note these additional points:

• This trust table entry only authenticates users who connect to the PI Server from EPR. For a user to connect with another PI Client, the user must explicitly log in with a password, another trust table entry must be used for authentication, or the default access privileges must be accepted.

• The example trust table entries authenticate users as the PI User named PIAdmin. Any other valid PI User can be used as long as the user has read-access to the PI Point Database and read/write-access to the tag data for each tag that is to be reconciled. If strict security is required, it is recommended that a PI User other than PIAdmin be used.

• The example trust table entry allows anyone with a copy of EPR to be authenticated by the PI Server. If stricter security is required, it is recommended that the trust table entry be further restricted to a specific computer, range of computer addresses, or Microsoft Windows user.

The PI Server trust table is very flexible and allows for many different configurations of varying security level. A complete discussion of the PI Server trust table is beyond the scope of this manual. For further information see the PI System manuals.

Logging Messages in Automated Mode

When EPR runs in automated mode, messages are logged to an EPR-specific log file unless otherwise specified. This log file is located in a subdirectory called Logs within the EPR installation directory. See the “Logging Messages” section for detailed information about the logging feature.

To disable writing messages to the EPR-specific log file, either open EPR interactively and disable logging, or include the /NL switch to the command line. If logging has already been disabled while EPR is in interactive mode, the /NL switch has no effect.

Note: EPR messages are always written to the PIPC.log file of the Active PI Server. This operation cannot be altered.

Using EPR with the Windows Scheduler

It is possible to schedule EPR to run automatically with the Microsoft Windows Scheduler. To use the Scheduler with EPR follow the steps below.

1. Open the Control Panel and double-click Scheduled Tasks.

2. Double-click Add Scheduled Task. The Scheduled Task Wizard opens. Click Next to continue.

[pic]

3. The wizard prompts you to select the program to schedule. Locate EPR (E-DAS to PI Reconciliation Utility) as shown below, select it, and click Next. It is recommended that you use the browse button to explicitly browse to the installed EPRUtil.exe file. Otherwise it is possible you may select a link file (a file with an .lnk extension) which likely will not work.

[pic]

4. Enter a task name and select the period at which the Scheduler will run as shown below. Then click Next.

[pic]

5. Enter the scheduling parameters and click Next.

[pic]

6. Enter a user ID under which EPR will run and click Next. If your trust table entry requires a specific Window’s user account for authentication, be sure to enter the correct account here. You may also need to specify a domain as well as an account name by using the backslash character as shown in the example.

[pic]

7. Select the Advanced Properties checkbox and click Finish.

[pic]

8. In the Run field append any additional command line parameters, such as the configuration file, that are needed.

[pic]

Note: You must specify the configuration file you wish to use along with the /s switch in order to schedule the EDAS to PI Reconciliation Utility to start in automated mode. This is the same way you would start the EDAS to PI Reconciliation Utility in automated mode from the command line.

9. Click OK to complete the task scheduling. You will need to re-enter the password for the user ID assigned to the task.

The Last Run Time, Status, and Last Result columns within the Scheduler window, shown below, yield useful information. If the last result is anything other than 0x0, an error occurred the last time EPR was executed by the scheduler for this task. The pipc.log file or the EPR specific log file should be checked to find out what the error was.

[pic]

For more detailed information on the Windows Scheduler consult Microsoft’s documentation.

Other Considerations

Use multiple configuration files to schedule different E-DAS to PI Reconciliations at different periods. Note that the Scheduler does not enforce any EPR specific rules. For example, the Windows scheduler will allow a user to schedule reconciliations that overlap time periods such having a daily reconciliation and a weekly reconciliation run at the same time. This is not recommended.

Appendix A:

Using Time Offsets

This version of the E-DAS to PI Reconciliation Utility marks a significant change in the way time is handled within the application. In all previous versions of EPR time stamps were read from the E-DAS system and transferred directly to the PI System without taking into consideration any differences time zone or daylight savings time (DST).

For example, consider an E-DAS server running in Easter Standard Time and a PI Server running in Pacific Daylight Time. In this case the E-DAS Server is actually 2 hours ahead of the PI Server. Therefore, a value time stamped at 06:00:00 (6:00 AM) in the E-DAS Server should be 04:00:00 (4:00 AM) if considered from the PI Server’s perspective. In previous versions of EPR the time stamp of the event would actually be sent directly to the PI Server as 06:00:00 (6:00 AM) unless a time offset value was supplied to manually account for the difference. Therefore, in previous versions of EPR, a user would need to provide a time offset of +2h to indicate that the E-DAS server as 2 hours ahead of the PI Server. Once daylight savings time would change for the PI Server (it would fall back to Pacific Standard Time) the actual time difference would need to be +3h to indicate that the E-DAS Server was 3 hours ahead of the PI Server. It is the problems encountered with daylight savings time changes on the PI Server and how to reconcile across DST boundaries that prompted a new way of handling time within the EPR utility.

In this version of the EPR Utility all time stamps found in the E-DAS Server are converted to UTC (Coordinated Universal Time) before they are sent to the PI System. The PI System can then take the UTC time stamp and interpret it in an unambiguous way. Therefore, continuing the example case above, the user would not have to make any adjustments to the time offset of the reconciliation to correctly transfer data from the E-DAS Server to the PI Server. This is much simpler than in previous versions of EPR, and as a result it is generally recommended that the Time Offset feature not be used.

There is one case in which a user may wish to use the Time Offset functionality. If the user would like events in the PI Server to be reflected at the same time as which they occurred in the E-DAS Server, that is keep time stamps unchanged regardless of time zone or DST differences, the Time Offset feature can be used to adjust the timestamps back to the original E-DAS time. In essence, the Time Offset feature can be thought of as having an opposite affect as it did in previous versions.

Previous versions of EPR used the Time Offset functionality to account time zone and DST setting differences while the current and future versions of EPR use the Time Offset feature to ignore the differences in time zone and DST settings between a PI Server and an E-DAS Server.

Revision History

|Date |Author |Comments |

|23-Oct-02 |ESB |First Release of this document. |

|19-Nov-02 |Bp |Update of screen capture of the complete epr |

|20-Nov-02 |Bp |Update as per Julie – add reference to pipc log for status |

| | |messages. |

|27-Feb-03 |CLP |Version 1.0.0.78 includes new functionality for automated use via |

| | |the command line and an updated GUI (tabbed control added). |

|21-Apr-03 |ESB |Edited and revised version 1.0.0.78 of the manual. |

|28-Apr-03 |CLP |Updated to reflect TagMask changes and inserted an important note |

| | |about scheduling via the Windows Scheduler. |

|16-Jun-03 |CLP |Updated with changes to Time Offset functionality. |

|26-Aug-03 |CG |Fixed headers & footers, and TOC |

|27-May-04 |CLP |Changed wording in Appendix A |

|15-Dec-04 |CLP |Updated for version 1.0.0.102 of the utility which has significant|

| | |changes to how time is handled and a minor change in detecting tag|

| | |configuration changes with reconciling from configuration files. |

|23-Mar-05 |MPK |Fixed copyright page with current year and changed company name to|

| | |OSIsoft, Inc. Made Final. |

|20-Apr-05 |BP/CLP |Updated version to 1.0.0.103 |

|21-Apr-05 |Chrys |Removed highlighting |

|10-Nov-05 |BP |Updated version to 1.0.0.104 |

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download