UTL: Universal Tag Locator
The Universal Tag Locator (UTL) is an all-encompassing tag monitoring and reporting system with extensive search and reporting features. Its users can locate real-time instrument information from multiple data sources. UTL is expandable and customizable to connect with all of your plant’s current instrument data sources.
Your operators and supervisors can create customizable end-of-shift reports that can be emailed to selected individuals to manage job tasks and improve continuity. Operating targets can be identified and tracked against established benchmarks. Alarms can be monitored and managed to identify at-risk process conditions.
- End-Of-Shift Reporting
- Operating/Business Planning Targets
- Alarm & Event Reporting
- Instrumentation Portal
- Lab & Handheld Data
- Flexible Configurations
HARDWARE & SOFTWARE
The Universal Tag Locator runs on Microsoft Server software. The system requires Windows 2000 Server (or higher) with IIS and SMTP services installed, SQL Server 2000 (or higher) and the file system space to house the data historian and system support folders. This configuration can be hosted on one server or distributed across multiple interconnected network servers.
No special user workstation software or hardware is required for UTL. The IE 8.0 web browser (or later ) is required. UTL runs on all current browser software and handheld devices.
UTL requires Microsoft SQL Server 2000 or higher. The UTL database can run on the same machine as the application or on a remote machine. By having the SQL server on the same machine, the system does not have to rely on connections to a remote SQL server machine to run. But the load on the server may compromise the performance of the web server. If the server has enough memory and processor capacity, then this configuration should work well.
Placing the SQL server on a different machine or on multiple interconnected servers frees up more resources on the web server for the UTL application. However, response times may be slower due to the remote querying of the databases, and the overall reliability of the system would depend on the stability of the servers running SQL Server, the stability of the web server and the network stability. The UTL database generates approximately 2GB of data per year.
FILE SYSTEM DISK SPACE
The current instances of UTL require about 2GB of disk space per year to store the PDF outputs. The UTL can be configured to store the outputs locally on the server or send them to a network directory. The distribution option is configurable for each instance of the program. For a 5-year projection, a minimum of 10GB of disk space is required.
The network bandwidth must be able to process the requests going to and coming from the web server. If the SQL servers are all remote, then every database driven request will need to query the data source and return its results for processing as quickly as possible. The network connection must have the capacity to handle the potential data load of 200-400 users per site.
FUNCTIONAL USER ACCOUNTS
UTL requires a functional user account that will be the “Run-As” user. This account will have full control of the code pages on the web server as well as access to the various input/output directories that will be required to run the program.
ADDITIONAL SOFTWARE REQUIREMENTS
UTL may require additional software to connect to the data sources:
- ActivePDF – 3rd party PDF converter that generates outputs from the system in PDF format
- PHD API – this allows for connections to PHD data sources
- PI-SDK – this allows for connections to PI data sources
- @aGlance/AGG – this allows for connections to InfoPlusX data sources
- Oracle 9.i Client – this allows for connection to data stored on Oracle Servers (ACM, Sample Manager, LIMS)