Getting started with converting data (UUT/UUR)

Intro

UUT: Unit Under Test reports 
UUR: Unit Under Repair reports
WATS offers different methods to input test and repair data. There are two main methods for interfacing WATS:

  1. Direct Interfacing through an add-on to NI TestStand, LabVIEW or the WATS API (.NET)
  2. Indirect Interfacing using WATS Standard formats or custom flat files or databases.

WATS Reports

WATS consists of two basic report types – UUT and UUR. The UUT report contains all the test result details. The UUR report contains all the repair and rework details executed on a unit. WATS can consume these reports in numerous formats and methods, but the details and quality of these reports are important for the analyzing functionality of WATS.

Interface through the WATS Client or WATS API

The WATS Client is an application that runs on windows (service) and provides both Direct and Indirect Interfacing. The WATS Client has several functions:

  • Offline functionality (buffer reports)
  • Secure transfer to the Master Server
  • Operator Yield monitor
  • Automatic SW update and Online/Offline/Health reporting to the Master Server

 Direct:

Indirect:

Interface through Client Converters

Using direct interfacing is a preferred option, but making converters to read other data sources will also add value to your WATS set-up.  

  • Converters allow you to interface with existing test equipment that is already producing reports generating additional cost savings. This can give faster Return on Investment
  • Converters allow you to enter historical data into WATS
  • Converters allow you to gather data from other installations with “fixed” reporting from sources such as AOI (Automatic Optical Inspector) and FPT (Flying Probe Tester), among others
  • Converters can read reports in a range of formats (report layouts) and with various data types (text, xml, database, excel) 

 

Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.