UCOS Process Historical Archiver Uses Less Bandwidth

The UCOS Process Historical Archiver (PHA) copies the values of tags and other pertinent associated data, while a project is running, to an ODBC-compliant database.

The values in the database can then be manipulated, examined, queried, used for rule-based decision making, and many other data analysis tasks.

Using exception-based technologies, the UCOS data historian archives more data with less bandwidth.

Details

Uses any ODBC-Compliant Database

The UCOS Data Historian supports run-time archiving of project data to a disk file (database) that is compatible with the Microsoft Open Database Connectivity (ODBC) standard. The system supports any standard ODBC-compliant database (e.g., MS SQL Server, Oracle, etc.) and can be accessed using standard SQL queries. ODBC-compliant database managers, report writers, expert systems, custom software, and other applications can be used to read and manipulate the archived data.

Minimizes Bandwidth & Resource Requirements

Larger Image (6K)

The typical data historian archives either all data or a set of statistically compressed samples. This results in either massive data archives or output that is statistically representative of the data, but not absolutely accurate.

The UCOS Data Historian delivers the best of both approaches. It determines which data to save to the database using a method known as exception-based archiving. The exception-based archiver examines the data values associated with archived tags. If the data has not changed since the last sample, or has not changed more than the user-configured deadband, then there is no archive entry to the database. This approach archives all data, minimizes the amount of space required to store that data, and does not need to rely on statistical compression in order to reproduce that data.

More data, more accuracy, less bandwidth.

The savings in bandwidth is especially helpful if you are accessing archived data from remote nodes.

Of course, pure exception-based archiving can be overridden for all tags or selected tags by configuring a minimum-write-rate variable to be a non-zero value. Tags configured with a minimum-write-rate other than zero will have their tag values archived at regular intervals whether or not the tag value has changed.

Runs Under Windows 2000/XP

Although the UCOS Data Historian can be run on the same node running a UCOS HMI, typically a node is dedicated to archiving in order to ensure maximum availability.

The UCOS Data Historian can run on any PC under Windows 2000/XP. RAM and hard disk requirements are dependant on the amount of data you expect to archive and the amount of time you expect to maintain that data.