Home > Products & Solutions > EMI > PI ManualLogger

PI ManualLogger

Used to organize and manually enter data from handheld loggers, computer terminals, scanners, and other input devices into the PI System.

Component Summary

Not all critical data come from automated control systems. Lab or plant log sheets, for example, can be valuable data sources. With the PI ManualLogger, you can easily and reliably record these data through handheld devices or computers. Once they are part of the PI System, those data are available throughout the enterprise for review and analysis.

With PI ManualLogger, you can get rid of paper reports, books, and other forms of recording hand-collected data, without installing an expensive automation system. Even your PDA can be a recording device. Simply enter the data and upload them to PI. If you have a tracking system that does not have an interface to PI, you can export data to your PC as a text file, then convert it to a supported PI ManualLogger format for entry into the PI System.

PI ManualLogger can collect comments as well as data. Comments can be attached to specific tags (individual data points) or an entire tour (a collection of data points). You can even create a predefined list of potentially recurring phrases to select from. (Predefined text is still fully editable.) Additionally, PI ManualLogger provides a normal range check for each entry. An audible and visual alarm is triggered when points, either analog or digital, fall outside predetermined ranges.

Technical Overview

A PC or handheld device can be used as a data-entry terminal for data collection from lab and plant log sheets. A shift supervisor can review and approve all data entered into PI ManualLogger before committing them to PI DataStorage. Users may also input data from a properly formatted text file. This facilitates data conversion from other programs (such as databases or statistical packages) into native PI format.

PI ManualLogger also features an interface for data transfer from certain laboratory systems. Once transferred into PI ManualLogger, the data are validated and then sent to the PI System. Data can also be input using PI ManualLogger's standard entry screens or a handheld terminal (HHT) or by using custom forms designed with VB, C++, or screens based in ActiveX components.

PI ManualLogger supports all point types, including analog, digital, string, and BLOB. In the PI System, manual input points are no different from automated computer/instrument points. PI ManualLogger data points are configured for manual, rather than automatic, data collection. Computer/instrument interfaces automatically configure points. To facilitate data collection, PI ManualLogger configures points based on a tour concept, which is simply a collection of tags. You define this collection by using the "Tag Search" box and other appropriate parameters relevant for manual inputs on the "Tour Definition" screen in PI ManualLogger. Required point attributes are Tagname, PointType, Zero, and Span.

PI ManualLogger provides the capability for entering data through default entry screens or custom-designed forms. Custom data-entry forms can be created within Visual Basic or C++. The ability to tailor the look and functionality of the data-entry screen allows users to remain in a familiar working environment. Custom forms benefit from all the standard PI ManualLogger features, such as data validation and security, while creating an intuitive interface for manual data entry.

The PI ManualLogger also supports data entry via an HHT. Each HHT supports several tours, which are read within one process area. Values for tags in a tour can then be collected using the HHT. The HHT clock timestamps data. After data are collected for a specific tour, operators download the data to a PC, and PI ManualLogger uploads the values into the PI System.

The HHT software includes the following features and functionality.

- String tags up to 80 characters long can be entered directly to the HHT.
- Tag groups can be created that allow the user to take different groups of data in any order during the tour.
- Up to seven previous values can be stored for each tag in a tour for delta limit checking.
- Last archive value (LAV) is displayed on the data-entry screen.
- The order in which the data are taken on the tour is recorded.
- Tours up to 999 tags (depending on tagname length) can be downloaded.

System Requirements

- Windows 95, Windows 98, Windows 2000, or Windows NT (version 3.51 or higher)