Current-RMS - Inspection Tasks

PATorganiser now supports populating Inspection Tasks in Current-RMS.

Usage of Inspection Tasks is optional but PATorganiser will search out Inspection Tasks (if they exist) and map them to Test Result names. Using this method means that you can set this up according to your own workflows, naming conventions, testing equipment and data.

As an example, within Current-RMS, we have created two Tasks of our Inspection: (one of type String and one of type Boolean)

Note: Create these to match the results that your tester creates. From our data analysis, although a lot of tests are very similar, each user and device can be slightly different, even in the naming of each result.

Then in PATorganiser, we have created a Test which has results with the same names as the Tasks:

When sending the data to Current-RMS, we review each Result Type (or Test Result Name) and see if matches a Task Name. If it does, we will then populate it according to the type:

For Boolean types, the logic is: 1 = Status is not equal to Fail, 0 = Status is equal to Fail

For String types, we output the results in the format of "{status} {result} {unit}, Limit: {limit}" where the values are available