Quality Tests

In this Field, you should enter a brief description for the Quality Test.

The Version No will auto-populate to '1'. New Versions are mentioned further down on this article. 

In this Field, select from the dropdown the Quality Team that will be responsible for that Quality Test.  

If required, you can then assign a specific user from that Team in the Default Quality Team Member Field if necessary.

As described in the Quality Team Responsible Field, you can define a specific member of the selected Quality Team if required.

This Field should be Enabled if you want your users entering results on Quality Orders  based on this Test without being able to see required Target Result value.

If this Field is Disabled, then the Target Result will remain visible. 

Where this Field is Enabled, a signature FastTab appears on a Quality Order and cannot be posted until a signature is entered.

Where this is Disabled, then this FastTab is hidden and does not require a signature prior to posting a Quality Order.

This Field will default to Open when the record is created but can be changed to either Certified or Closed.

Open - This Status allows the Test to be editable.

Certified - Changing this to this Status will allow the Test to be used and selected on the Test Automation Page.

Closed - Using this Status will signify the Test is no longer active and should not be used. 

The Tracking Code Status can be assigned and will be the status stored against the Quality Order and Serial No or Lot No where used prior to being posted. 

The Date Created field will auto-populate once the Test is created. This is pulled from the Work date.

The Created By field is not editable and shows who created the Quality Test. 

These are also displayed within the Factbox on the Quality Test as well as the List Page. 

Firstly, the Quality Check Codes can be populated manually per line, or multiple can be added at one time by using the Select Quality Checks option on the Lines FastTab ribbon which will open up a list of the Quality Check Codes where multiple ones can be selected and confirmed.  You can have as many checks here as you wish.

Once these are added, many of the other fields will auto-populate, such as the Description, Unit of Measure, Result Type and Rounding Precision which are all pulled from the Quality Check Code Table but are all editable if required.

If you want to change the order of the Quality Check Codes, you can use the Sequence option in the Lines ribbon to move the highlighted line up or down. 

The Test Iterations is used to specify the criteria that will determine the number of results per Check Code.

This defaults to Sample Size but other options are available to choose from.  These are all explained below:

Single Result - This option will default the No of Results to blank and will require just 1 result to be input on the Quality Order. 

Fixed No of Results - This option allows you to enter how many results you want to record on the Quality Order for the Check Code in the No of Results field.

Sample Size -  This option will use the sample size determined in the Automation Rules Page for the Transaction Type.  This means that the No of Results do not need to be populated here. 

This Field may need to be populated, based on the option selected in the Test Iterations Field.

This Field is only editable where Result Type is Numeric or Text but include options Value, Min, Max, Average and Sum which will look at all of the results logged on the "Quality Order" and calculate the Overall Result by this value. 

The Target Result is dependant on what Result Type is being used. The below summary confirms what can and cannot be done based on the Result Type in use. 

Numeric - Will not use pre-defined Values from a Quality Check on the Tests so Target Result requires manual population.  Allows for Result Calculation options of: 'Value', 'Min', 'Max', 'Average' & 'Sum'.  Can utilise the Lower Limit/Upper Limit fields. 

Lookup - Will allow for pre-defined fields to be selected from the Values of the "Quality Check Code" for the Target Result. Result Calculation cannot be changed from 'Value'. Lower Limit/Upper Limit fields cannot be used. 

Text - Will not use pre-defined Values from a Quality Check on Tests so Target Result requires manual population. Result Calculation cannot be changed from 'Value'. Lower Limit/Upper Limit fields cannot be used. 

Once your Target Result is populated with the pass rate (that is, the result you want your Check Code to achieve for the Quality Order to result in a 'Pass'), providing your check code has a Result Type of 'Numeric', you can utilise the Lower and Upper limit fields. 

The Lower and Upper Limit fields can be used where the result doesn't need to be a specific value but it can fall in between the lower and upper limits specified.

This Field can be used to just record a result on the Quality Order which does not effect the overall result and can just be used to record a value for information purposes.

For example, if the Item comes in various different sizes, you might want to record the measurement size of the items you are testing but this would not need to influence the overall result.

Where you are only wanting the Quality Order to pass if these are met (or the Target Result is achieved if Lower and Upper Limits are not in use), leave the Optional field as No.

Where this is Yes, the Quality Order will not log as a fail if a result is entered outside of these parameters.  It also means that where Optional is Yes, the Quality Check Code does not need to be completed on the Quality Order.