Tests Module - Introduction and Layout of Tests
Tests - An Introduction
'Tests' are what Safefood360° refers to as 'Building Blocks' which are used in 'Monitoring' & 'Receiving' Programmes and Records. Tests are part of Master Data in Safefood360°.
There are two types of 'Tests' and 7 types of 'Open Data' that can be used and treated as tests in the Programmes. Although 'Open Data' are not necessarily considered as 'Tests' as they do not carry any 'Pass' or 'Fail' values, they are extremely useful in the Monitoring and Receiving modules as they allow to personalise the Programmes, and in turn the Records, to a great extent.
This article outlines the different types of Tests and Open Data and an indication of where they are best used.
Tests as Building Blocks
Image: Tests as Building Blocks - an Overview
Image: Breakdown of the Usage of 'Tests' in Different Modules
Note: 'Receiving & Inspection' is our newest module added to the 'Monitoring' center and is made available on specific requests only. Talk to your PO about more information regarding the 'Receiving & Inspection' module.
Adding Tests to the 'Tests' Module
To access the 'Tests' module and add your required Tests that will be used in 'Monitoring' and 'Receiving' Programmes and Records, navigate to 'Master Data>Tests'.
Image: Accessing 'Master Data>Tests' Module
Test Types
In Safefood360° we have different types of 'Tests' that can be built to be used in your 'Monitoring' and 'Receiving' modules, however, only Variable and Attribute Tests will have a result associated with the tests' specifications. The Results can be 'Pass', 'Fail' or 'Pass, Warning':
1. Variable: These are quantitative tests and will require a numerical value to be entered in the 'Monitoring' and 'Batching' Records. The result can be 'Target' (Pass), 'Warning' (Pass, Warning), or 'Fail' (Fail), with upper and lower warning limits.
2. Attribute: These are qualitative tests that will require the selection of one single option from a dropdown list in the 'Monitoring' and 'Batching' Records. The result can be 'Target' (Pass), 'Warning' (Pass, Warning) or 'Out of Spec' (Fail).
3. Open Data: These tests don't require any specifications and they do not provide any Pass or Fail results in your 'Monitoring' and 'Batching' Records.
Tests are easily differentiated when robust naming conventions and folder systems are used. Each of the different types of Tests described above are housed in their own separate tabs in the system and the folder structure is displayed within those tabs in the 'Folder' column. A strong naming convention ensures that the correct Tests are easily sourced when building 'Monitoring' and 'Receiving' Programmes.
Tests can be re-used for different Programmes. You can use the same Test in multiple different Programmes, both 'Monitoring' and 'Receiving'. For example, if you have a Test with specifications that can be applied to multiple different Programmes, you can build the Test once, place it in a generic folder, and re-use it in the different Programmes as required. In the case of Open Data 'Tests', we recommend building just one test for generic fields such as Comments (Open Text), add Attachment (File Upload), etc., and use the same Test in all of your Programmes. This will ensure that you don't overload your Test tabs and, as a result, will source the required Tests easier when using the system.
Test usage history can be easily viewed. If you want to know which 'Monitoring' and 'Receiving' Programmes and Records use this specific Test, navigate to the required Test tab in the 'Tests' module in 'Master Data' and click on the name of the Test. This will open the main Test page where you can then click on the required row to expand the Programme or Record section.
Image: Accessing Test History - Click on the Test Name
Image: Accessing Test History - Click on the Required Dropdown to View Test Usage History
Image: Accessing Test History - View Test History - Click on the Blue 'Name' to Access the Related Programme or Record
Changes made to Test names will be automatically reflected in existing (Open and Closed) as well as new Records in which the Test is used. If you rename an Attribute or Variable Test, this will automatically be reflected in all of the Records where the Tests were already used in, as well as all new Records. For Open Data, these changes will only be reflected in newly created Records after the name change - changes will not be applied to existing Records. Any other changes made to any other test specification details will be reflected in newly created Records only.
[Anything else to note for this statement?]
1. Variable Tests
A Variable Test is a quality control Test that measures specific, quantitative characteristics of a Product or Process. Unlike Attribute Tests, Variable Tests provide continuous data that can be measured on a numerical scale, allowing for more precise assessments. This allows food manufacturers to monitor variations in the production process making it easier to identify trends and take Corrective Actions. They are essential for controlling Product consistency, meeting regulatory standards, and ensuring the products are both safe and high-quality. Variable Tests are generally used to assess characteristics such as weight, temperature, pH, concentration, dimensions, moisture content, etc.
Image: Add Variable Test
Image: Blank Variable Test
2. Attribute Tests
An Attribute Test is a quality control Test that evaluates whether specific characteristics (attributes) of a Product or Process meet defined standards or criteria. Instead of measuring specific quantities, Attribute Tests are 'Pass' or 'Fail' assessments based on the presence or absence of particular attributes.
Image: Add Attribute Test
Image: Blank Attribute Test
3. Open Data
Open Data fields are considered as 'Tests' for ease of naming, but they do not carry any limitations for 'Pass' or 'Fail' results. This allows the Users to type in specific details and other observations without affecting the overall Record results. Open Data fields provide flexibility for the User and allow inspectors to input real-time, accurate observations or measurements, which is crucial for effective monitoring and documentation of the food safety processes.
Open Data includes: Text Field, Date Field, Numerical Field, Timestamp, File Upload, Dropdown List and Barcode Field.
Image: Add Open Data
Multiple Open Data fields will appear to be the same when setting them up - the difference will become evident when completing the Records.
Image: Blank Open Data 'Text' Field
Image: Blank Open Data 'Date' Field
Image: Blank Open Data 'Numerical' Field
Image: Blank Open Data 'Timestamp' Field
Image: Blank Open Data 'File Upload' Field
Image: Blank Open Data 'Dropdown List' Field
Image: Add Open Data 'Barcode Field'
Image: Blank Open Data Fields as They Appear in a Monitoring Record (Barcode Field N/A in Monitoring)
Image: Completed Open Data Fields as They Appear in a Monitoring Record (Barcode Field N/A in Monitoring)
