Metrel aPAT Intregration - Useful Information

Metrel aPAT Intregration - Useful Information

Metrel aPAT Integration

PATorganiser and Metrel have worked together to develop an integration whereby testing data from the Metrel Android aPAT application can be uploaded to PATorganiser at the press of a button - no more transferring or uploading of files manually. A further advantage is that aPAT can operate without internet access and the data then sent to PATorganiser once connected back to the internet.

Getting Started

Please follow article Metrel aPAT Intregration - Export to PATorganiser to get setup in PATorganiser and send data from aPAT.

Overview

aPAT and PATorganiser each have their own ways of managing the data, so the following information will help explain how the data from aPAT ends up in PATorganiser

The following screenshot shows the two platforms side by side with the data uploaded from aPAT presented in PATorganiser:


Fields

The following fields are mapped from aPAT to PATorganiser.

Client

The top of the hierarchy in PATorganiser can be mapped in aPAT by setting a comment on the Root node. This does not have to be set to work with PATorganiser and the data will appear in Unknown Client. But if set, it will populate the client field. In the example, the client is called "Example Client Level".

1. Highlight the Node and select the pencil to edit the comment.



2. Create the comment (Client).



In aPAT:


In PATorganiser:


Site

The second level of the hierarchy in PATorganiser (called Site) is mapped to either the Location or Project element in aPAT. aPAT allows Locations or Projects to be added to the Root node. The name of this element will be the Site in PATorganiser. In the example seen below, the Site is called "Umina". This can be edited under Parameters >> NAME (DESIGNATION) OF LOCATION.

In aPAT:


In PATorganiser:


Location

The third level of the hierarchy in PATorganiser - Location, is mapped to the Asset's LOCATION (Room) attribute in aPAT. By default, when you create an Asset in aPAT, its Location will appear as the name of the Location or Project. The actual Location can only be edited in the APPLIANCE ID values under Parameters in aPAT. In this example, the Location of Asset 004 has been edited to "Warehouse". 
Useful Tip: 

When adding assets in the field, we recommend editing aPAT's Location/Project name prior to adding; this ensures that you do not have to create the Asset and keep typing in the Location (Room) attribute over and over. Once all the assets are added, rename the Location/Project to be the correct Site name. The result will be that each Asset has the correct location and site without having to manually type in repetitive information.
In aPAT:


In PATorganiser:


Examples of setting up your tree in aPAT

Test and Tag professionals:

Utilise the Node field in aPAT to configure your customer's name, in the Location field input the address of the customer. Once you have entered the asset details enter the actual location of the asset within your customers site - see below for an example of this layout.

In aPAT:


In PATorganiser:


In-house Test and Tag:

Utilise the Node field in aPAT as the name of the premises, in the Location field input the section or department. Once you have entered the asset details enter the actual location of the asset within the premises - see below for an example of this layout.

In aPAT:



In PATorganiser:


Tests and Results

Tests and results are imported as per standard data import functionality which is detailed in this link.