Quality Management
Quality Management is a module within Vinpoint that caters for the management of product testing and test results. Any number of tests can be set up and configured to represent laboratory, quality or other types of testing.
A Test Request can be raised against the content of a specific vessel (tank or barrel), a batch of bulk wine, a vineyard, block or sub-block, or against an inventory item, and the tests to be performed against the entity are listed with their default values automatically populated based on the test and group configurations.
Test Codes
Test Codes can be setup for the various attributes of the grapes or wine. During setup, the following can be specified:
- Result Type – Text, Decimal or Date
- Default Test Method – if Test Methods are setup they can be assigned as a default here
- Sample Volume – define the volume quantity used for samples
- Default UOM Code – the user can define their own units of measure
- Def. Minimum Result – record the Def. Minimum Result for the test code
- Def. Maximum Result – record the Def. Maximum Result for the test code
Test Groups
Test groups can be used to group multiple test codes into a group. First define the various test groups.
Test Group Code Setup
You use the Test Group Code Setup to define the list of test codes per Test Group. In the example below, a Test Group called BULK WINE RECEIPT has been setup and contains the following Test Codes:
At any stage in the receipt or cellar process a Test Request can be issued. By using Test Groups, the user would not have to specify the 3 codes above, but could just specify the Test Group Code which includes the 3 codes.
Quality Management Setup
The Quality Management Setup card must be setup before any test requests can be created and processed.
You can define the following information from this card.
| Field | Description |
|---|---|
| Test Request Nos. | Enter the No. Series to be used in creating test requests. |
| Winery Test Request Document ID | Enter the Report ID to be used in printing the Winery Test Request. |
| Vineyard Test Request Document ID | Enter the Report ID to be used in printing the Vineyard Test Request. |
| Print W. Test No. Confirmation | If enabled, the Report Request page of the Test Request Report will not be prompted and go straight to printing the report when accessed from the Test Request Card. |
| Item Test Request Document ID | Enter the Report ID for printing the Test Request Report for Item Test Requests. |
| Default Test Request Status | This is the initial Status assigned to a created Test Request. |
| Printed Test Request Status | The system will validate that the status of the Test Request against this setting before the Test Request Report can be run. |
| Sample Reference No. Series | Enter the No. Series to be used for the Sample Reference field on the Test Request. |
| Default Test Configuration on Receipt Print | Tick this to automatically create a Test Request based on the Default Test Configuration table when a Receipt is printed. |
| ALC Test Group | Enter the Test Group code for Alcohol |
| ALC Test Code | Enter the Test Code for Alcohol |
| RS Test Group | Enter the Test Group code for RS |
| RS Test Code | Enter the Test Code for RS (Residual Sugar) |
| Density Test Group | Enter the Test Group Code for Density |
| Density Test Code | Ente[r] the Test Code for Density |
| pH Test Code | Enter the Test Code for pH |
| TA Test Code | Enter the Test Code for TA |
| VA Test Code | Enter the Test Code for VA |
| Free SO2 Test Code | Enter the Test Code for SO2 |
| Brix Test Code | Enter the Test Code for Brix |
| Duty Tariff Code Alc. Check | Tick this field if the system should check the Alcohol value from the Duty Tariff table. |
| Declared Batch Alc. Check | Prohibit Alcohol result entered against a Declared Batch of Bulk Wine. |
Test Methods
The Test Method is an optional information that can be specified with the Test Codes. This will flow through into the Test Request Lines but can be overwritten if required.
Default Test Configurations
You can use the Default Test Configuration to automatically generate test requests for certain item category or cellar operation.
Each Test Code under the selected Test Group Code must be entered separately to indicate what test codes will be automatically inserted to the test request automatically created when the respective fruit receipt, bulk wine receipt or work order is “Released”.
Along with the above setup, you must also tick the Auto-Generate column on the Item Categories table to enable the automatic creation of the test requests.
Moreover, it is also possible to enable copying the test results of a Bulk Wine Batch from to wherever it ends up in the Winery Module. To enable this feature, simply select on the Copy Lab Test Group Results column and select the appropriate Test Group Codes that will be copied.
Test Requests
A Test Request can be created from different places in the system. It can be created from:
- Vineyard Card
- Vineyard Block Card
- Vineyard Sub-Block Card
- Fruit Receipt Card
- Bulk Wine Receipt Card
- Work Order Card
- Vessel List and Vessel Card
- Batch Card
- Item Card
- Item Ledger Entries
- Purchase Order Card (Line menu bar)
Depending on which place the Test Request is created from, either a Vineyard Test Request Card, Winery Test Request Card or Item Test Request Card will open.
| Test Request Card | Source |
|---|---|
| Vineyard Test Request | Vineyard, Block and Sub-Block |
| Winery Test Request | Fruit Receipt, Bulk Wine Receipt, Vessel, Batch, Work Order |
| Item Test Request | Purchase Order, Item, Item Ledger Entries |
A Test Request can be easily created from the different pages listed above by selecting the Generate Test Request on the Actions tab of the relevant cards. If a Test Request is created from a Fruit Receipt, this will display the Winery Test Request page as shown below:
The highlighted fields below and the factbox default in from the source of the test request. In this example, Fruit Receipt “WR00009”.
Use the Insert Tests function on the Actions tab to select a Test Group Code:
If a Test Group Code is not being used, the Test Codes can be manually entered on the Lines section of the Test Request.
A print out is also available for the Test Request and can be printed from the ribbon.
A created Test Request first status is “Open”, this can be manually changed as it progresses through the different stages of the process. For example, after the test request is created, you can then change the status to Release to indicate that it is ready to be actioned on. Once the test request is selected and test results ready to be entered, the status can be changed to In Progress.
Once the test results have been logged, the test request should be marked as Complete.
Test Request Line Lists
This lists all the Test Requests that have been created. The user can filter to narrow down the list.
Test Results
When the results are in, the user should record the results and mark it as Complete on the Test Request page:
If the results are not all known at the same time individual line(s) can be marked as complete. Otherwise, you can use the Update Line Status button to update the status of all lines.
Once the test results are recorded for all the test codes the record should be marked complete on the ribbon. Marking a test as Complete also prevents further changes to the test results.
The Test Results can be viewed from the Vessel or source of the Test Request:
Archiving Test Results
Over time, the list of test requests will continue to grow. To reduce the amount of active test requests, particularly those of completed test requests, you can archive these tests so they can be transferred to another set of table – the Archived Test Req. The archived data can be accessed through the Archived Test Req. Header and Archived Test Req. Lines.
