It provides a way of transferring and storing test result data between systems that is platform independent e.g. S500 – PinPoint – 3rd party. The diagram shows a typical implementation.

The Test Result Server (TRS) provides an interface that third party systems can communicate such that test data and diagnostic information can be freely available and transferred bi-directionally between systems.

TRS is effectively a repository for client-generated Result Data Blocks (RDB). TRLClient manages all communication to the TRS, compilation of the RDB and handles Tag records created by the Test Executive during a test run. Functions are provided for 3rd party software to interact with RDB for recording and extraction of data.

Each record, called a Tag, consists of two parts. The first part is the header that contains a unique Tag ID code and payload size data. The second part consists of the payload zone that can contain user-supplied data up to 2Gb in length.

TRS comes with some predefined Tag ID codes (Operator name, Test Time, Serial number, etc.) which can be extended by creating your own codes so that the RDB can be used to store literally any data needed, for example process tracking information.