Coffey Geotechnics - QESTLab User Guide: Difference between revisions
No edit summary |
No edit summary |
||
| Line 33: | Line 33: | ||
==GETTING STARTED WITH QESTLAB== | ==GETTING STARTED WITH QESTLAB== | ||
=== Connecting to the Server === | === Connecting to the Server === | ||
The QESTLab application runs on servers in the Coffey Sydney office. | The QESTLab application runs on servers in the Coffey Sydney office. See the document '''Installing QESTLab shortcuts''' for instructions on installing the shortcuts to connect to these machines. | ||
Once you have connected and logged on to these machines, start QESTLab by double clicking on the '''QESTLab Client''' icon. | Once you have connected and logged on to these machines, start QESTLab by double clicking on the '''QESTLab Client''' icon. | ||
| Line 462: | Line 462: | ||
<DIV CLASS="pageBreak"/> | <DIV CLASS="pageBreak"/> | ||
== | ==MANAGEMENT REPORTING== | ||
QESTLab contains a number of pre-defined | QESTLab contains a number of pre-defined reports. User are able to modify these or create new reports as required. This module explains the process of running management reports. | ||
{{QESTLab:Reports - running reports/charts|tier===}} | {{QESTLab:Reports - running reports/charts|tier===}} | ||
===Useful reports=== | |||
====Billing==== | |||
#WIP reports - display WIP at the time the report is run. This means the report will look different every time you run it. To save the WIP figure on a particular date, run the report and save it. | |||
#Concrete billing summary - detailed reports of all concrete billing for use on large projects, when a summary invoice is created with items "rolled up". | |||
#Equipment reports - display calibration imformation. | |||
Revision as of 07:58, 27 October 2006
Course Structure
This training guide covers seven modules:
- Getting Started with QESTLab
- Concrete Testing
- Soil Field Testing
- Other Soil/Aggregate Testing
- Billing and Invoicing
- Managing Projects, Fee Schedules, Equipment & Other Lists
- Running Reports
More user information for the QESTLab product can be found at http://online.spectraqest.com
All content and images (c) 2000-2006 Spectra Quality Engineering Software Tools. The information contained herein can not be reproduced, copied, altered or distributed to a third party without the explicit written consent of Spectra Quality Engineering Software Tools Pty Ltd.
GETTING STARTED WITH QESTLAB
Connecting to the Server
The QESTLab application runs on servers in the Coffey Sydney office. See the document Installing QESTLab shortcuts for instructions on installing the shortcuts to connect to these machines.
Once you have connected and logged on to these machines, start QESTLab by double clicking on the QESTLab Client icon.
Logging in to QESTLab
Step 1. To start QESTLab double click the QESTLab Client icon
on the desktop.
Step 2. When QESTLab has loaded the QESTLab log in screen will appear. Enter your QESTLab login name and password provided to you by your QESTLab administrator.
The first-time password that is generated by the system by default is "QEST_password" (minus the quotes). You will be prompted to change this when you access QESTLab for the first time.

Changing your password
The first time you log in to QESTLab change your password to something known only to you.
Step 1. With QESTLab running click the Security menu then select Change Password.
Step 2. In the Old Password field type your current password.
In the New Password field type your new password. Re-enter your new password in the Confirm Password field.

Step 3. Click OK to save your new password.
Logging out
Logout and change user
It is possible to log a different user in to QESTLab without shutting down QESTLab and restarting.
Step 1. With QESTLab running click the Security menu then click Logout.
Step 2. To login another QESTLab user, click the Security menu then click Login.
The new user can then enter their username and password as normal.
NOTE:
1. If you are logged on and the computer that you are running QESTLab on is unattended then there is the possibilty that another person may use the computer to carry out work under your name. When not using QESTLab it is recommended that you either Logout off QESTLab or lock the computer.
2. While you are logged in the Audit Trail keeps a log of every action you make in QESTLab. This is a security feature that enables the tracking of every change made to every field in QESTLab. For this reason you must only work in QESTLab when logged on using your own account.
Close QESTLab
To close QESTLab down on your computer click the File menu then click Exit, or click on the X button in the top right corner of the QESTLab screen
QESTLab operates like Windows Explorer. There is a left hand and a right hand window. Navigation in QESTLab is done using the tree in the left hand window.
The QESTLab tree
Notice the names of the nodes in the tree. Each node allows the user to manage a different area in QESTLab. For example, the Samples node is used to register samples in QESTLab.
The QESTLab tree will look different for users with different levels of permissions in QESTLab. If a user does not have access to a particular area in QESTLab, that node will not be displayed in the tree. For example, if you do not have rights to modify clients in QESTLab you will not see the clients node in the tree. The image below shows all the possible nodes in the QESTLab tree.

Below is a brief description of the different areas in the tree.
| Clients | Users with sufficient rights may add, remove and maintain details for all your customers in this area. |
| Projects | Add, remove and maintain the list of projects your organisation is working on. |
| Work Orders | Work orders are a convenient way to register a group of samples. They are similar to a test request. Select the work orders node to register and search for work orders. |
| Samples | Individual samples are registered and displayed under the samples node. Select the samples node to register or search for samples. |
| Tests/Documents | Select the tests/documents node to search for tests, test reports, or documents other than work orders or samples. Expand this node to see the filters that can be used to search for various documents in QESTLab. |
| Billing | When invoices are raised they are displayed under the billing node. |
| Equipment | Equipment is registered in QESTLab and displayed under the equipment node. Expand the equipment node to see the different types of equipment that can be registered in QESTLab. |
| Lists | QESTLab lists allow you to maintain lists of commonly used items, such as concrete plants, aggregate/soil materials, tester names, and many others. This makes data entry faster and simpler. Lists are displayed and maintained under the lists node. |
| Reports and Charts | This area is used to create and run reports and charts for quality control or other management functions. |
| Specification | Specifications are used to set acceptable limits for test results. They are created and maintained under the specifications node. |
The QESTLab tree can be hidden by clicking on the Show/Hide Tree button
in the toolbar.
Laboratories
The Lab dropdown box above the tree shows the labs to which you have access.

The global lab
Most users will have access to only one laboratory. In this case you will see this lab plus the (global) lab. The global lab contains data (generally clients, plus other data) that needs to be available to all labs.
Note that if you change the lab selected in the Lab dropdown box the tree will change. If you notice that the tree looks unfamiliar or nodes are missing check that you have your lab selected and not the (global) lab.
Accessing more than one lab
If you have been granted rights to more than one laboratory you will see these labs in the Lab dropdown box. Select a laboratory to restrict the data shown in QESTLab to that lab. (all) will also be shown in the laboratory list. Selecting a lab of (all) simply displays information for all laboratories that the user has access to.
Notice that if all laboratories is chosen, then the tree will group items by laboratory, as shown below for the Lists.

This functionality can be turned off by clicking the Show/hide lab nodes button
on the toolbar. If this is de-selected then information is not grouped by laboratory.
Filters
Filters are a way of searching for documents in QESTLab, such as samples, test reports, or invoices. Filters are displayed in the left hand window underneath the QESTLab tree. Filters are included with QESTLab and new ones may be created as required by your QESTLab administrator.

Since different filters are used to search for different things, notice that a different filter appears in the filters area depending on which node is selected in the QESTLab tree.
CONCRETE TESTING
Registering concrete samples
Overview
Concrete samples are added and displayed in the QESTLab tree under the Samples node. There are two main documents (screens) for concrete testing in QESTLab - the concrete sample group document and the concrete sample document.
- The concrete sample group level contains, as the name suggests, information that is applicable to a group of concrete samples taken from the same project on a particular day. This includes the client, project and date cast, as well as other information.
- The concrete sample document stores the actual fieldsheet data for that sample, and the test data for each of the specimens in that sample.
In the QESTLab tree the concrete sample group is displayed with the concrete sample(s) 'hanging' off. In the example the concrete sample group is highlighted and shows the client, project and date cast. There is only one concrete sample in the example, but there may be many concrete samples, one for each fieldsheet for that project for that day. It is shown with the fieldsheet number, mix code, time sampled, and number of specimens i.e. cylinders.
The format of the sample codes is [Lab Code][Year][Report Type]-[number] e.g. ALBU06C-0072.
Notice the two other documents displayed at the same level as the concrete sample document. These document are the concrete test report document, and the QESTLab billing document. These are normally added whenever a concrete sample group is registered. The concrete test report is used to report concrete test results, and the billing document is used to store charges associated with the sample, for inclusion on an invoice at the end of the month.
The advantage of having two documents is that the concrete sample group allows information common to all samples to be entered once, billed once, and reported on the same test report.
Registering a concrete sample group
To register a concrete sample group follow the steps below:
Step 1. Select the Samples node in the tree, and click the New sample button
.
Step 2. The Add Sample(s) and Document(s) window is displayed. Ensure the correct laboratory is chosen, then select Concrete Sample Group from the Type of Sample to be added.
Step 3. In the Select group(s) area, select Concrete Testing group as shown above, or select individually the documents to be added to the sample. In order to generate charges for the sample a billing document must be added when registering a concrete sample group.
Step 4. Ensure that the Sample ID field is left blank. The sample ID will be automatically generated. It has the format LABCODE YEAR REPORTTYPE - NUMBER. eg. ALBU06C-0231.
Step 5. Click OK to add the new sample. The selected documents will appear in the QESTLab tree below the concrete sample group as shown below.
Note the hierachical arrangement of the concrete sample. The concrete sample group document (highlighted) appears first and the concrete sample, billing, and test report documents all 'hang' off the concrete sample group.
The concrete sample group document
The next step in the registration is to complete the fields in the concrete sample group document. The concrete sample group document provides a means of entering information that applies to many concrete samples (fieldsheets).
Completing the concrete sample group document
Step 1. Select the concrete sample group document in the tree.
Step 2. The concrete sample group document is displayed in the right hand window. Some customers have requested their own customised version of this document which may look slightly different to the example below.

Any field with a
button can be selected from a list. For fields with two boxes, either select the item from the list or enter the code in the first box and press Enter on the keyboard.

Select a client and project and enter the date cast, date received, and moisture cure time. The remaining fields can be completed if required. Remarks appear on the concrete test report in the remarks box at the bottom of the report as shown below.

The concrete sample document
The last step in the registration process is to complete each concrete sample document in the concrete sample group. The concrete sample document contains the fieldsheet data and the details of each specimen.
Completing the fieldsheet data
Step 1. Click on the concrete sample document in the tree.

Step 2. The concrete sample document in displayed in the right hand window. Again, this document may look slightly different to the example below.
Step 2. Enter the following data:
- The unique fieldsheet number.
- The grade, this will automatically populate the F'c field.
- Select the name of the person who did the sampling in the Sampled By drop down box.
The remaining data on this screen is optional. Each field is described in the table below.
| Fieldsheet | The unique fieldsheet number. The fieldsheet number must be unique and can be the number from a pre-printed fieldsheet or simply a sequential number managed by the laboratory. |
| Time Batched | Time, in 24 hour format, that the batch of concrete was batched. Any format is acceptable. eg 1200, 12.00, 12:00, 12, 12a, 12 pm, etc. |
| Time Sampled | Time, in 24 hour format as above, that this sample was taken. |
| On Site | |
| Sampled By | Select the name, or enter the code, of the person who took the sample. Populated from the QESTLab Sampled by list. |
| Grade | Grade of the concrete in this sample. eg N32. The grade is used to populate the F'c. |
| F'c | Design strength of the concrete. Automatically populated from the grade. eg 32. The F'c is used to calculate which specimens have failed strength testing. |
| Plant | Select the name, or enter the code, of the plant that batched the concrete. Populated from the QESTLab Concrete plant list. |
| Mix | The mix code of the mix in the batch. |
| Max Agg | The size of the maximum aggregate in the mix. |
| Supplier | The concrete supplier for the plant selected in the Plant field. The supplier field is populated with the supplier name entered in the concrete plant list for this plant. |
| Design Slump | The design slump of the mix. |
| Meas. Slump (initial) | The measured slump before additives. |
| Meas. Slump (final) | The measured slump after additives. |
| Truck | The reference number of the truck that delivered the batch of concrete associated with this docket number. |
| Docket No. | Docket (ticket) number for the batch. |
| Batch No. | Batch number for the batch. |
| Water Added Before/After Test (WABT/WAAT) | Check the relevant box to display the litres field, and enter the amount in litres. |
| Weather | The weather at sampling time. Populated from the QESTLab Weather list. |
| Temperature Air/Concrete | Air/concrete temprature at time of sampling. |
| Compaction | Select the concrete compaction method. Populated from the QESTLab Concrete compaction method list. |
| Sampling Method | The sampling test method number used for this sample. |
| Conditioning | |
| Load | The size of the concrete load in the batch. |
| Prog Load | |
| Sampling Location | Select the sampling location. |
| Location | Enter details of the location if required. |
| Remarks | Enter remarks regarding the sample if required. |
Step 3. Slump only tests
If the sample was taken for slump testing only, and no specimens are to be added, tick the Slump Only box to identify the sample as a slump only sample.

Note that this will only register as one slump test when charges are generated later. If you wish to charge for more than one slump test you can manually alter this in the billing document later.
Step 4. Registering concrete specimens
To register and display the specimens for this sample select a test group from the Test Group drop down box. Test groups are setup by a QESTLab administrator in the concrete test groups list. They contain commonly added groups of specimens and are used to save time during sample registration. Note that once a test group is selected and the sample is saved, the test group field is hidden and no longer available for selection.

Alternately specimens may be added manually, without selecting a test group, by simply entering the number of specimens in the No. field. Also, note that even if specimens are added using a test group, extra specimens may be added by increasing the number in the No. box.
Step 5. The concrete specimens are shown below the fieldsheet information. Notice that much of the data has been completed for each specimen. This is contained in the concrete test group.
If this is correct then the process of sample registration is complete.
The concrete specimen grid
Each field in the concrete specimen area is explained below. Note that the test data and results fields are only shown when the relevant checkbox is ticked.
You may make changes to the data that was entered as part of the concrete test group in this area. Test data can also be entered here, although it is generally entered elsewhere using an electronic version of the daily worksheet to enter data for all specimens tested that day.
The important fields are highlighted in bold.
The specimen details fields

| Specimen ID | Consists of the fieldsheet number and the ID of the specimen (A,B,C etc). Identifies the specimen on the concrete test report. |
| Type | The test to be performed on the specimen. eg COMP100, FLEX150, etc. Note that the type selected determines the measurement columns that are displayed. Different columns will be displayed for different test types. |
| ID | A letter used to identify each specimen in a sample (A,B,C etc). |
| Client ID | The client specimen ID if required. |
| Age | The age of the specimen, in days, at which the test must be conducted. The age may be changed by typing a different age in this field. Note this will change the test date. |
| Test Date | The test date for the specimen. This is automatically calculated from the date cast on the concrete sample group screen, and the specimen age. |
| Std Cure | The standard cure. Leave blank or enter one of the three following options: number of days, A for air cured, or S for site cured. Reported on the concrete test report. |
| Mould | The identifying number of the mould used for this specimen. |
| Spec Locn | The location of the specimen in the curing room or water tank. |
| Cap | Type of cap used in testing. The cap is reported on the concrete test report. |
| Fc | The F'c of the mix. |
| Marks | Record significant marks on the specimen. The marks are reported on the concrete test report. |
| Select Yes or No to determine whether the test results for this specimen will appear on the test report. | |
| Charge | Select Yes or No to determine whether the charge for this specimen will be included in the automatic generation of charges for this sample. |
| Charge to Plant | Select Yes or No to determine whether this specimen will be charged to the plant instead of the client for this sample group. This requires that the plant have an entry in the QESTLab client list. |
| Extern Samp | Select Yes if the specimen was sampled externally. |
The test data fields

Enure the Show Test\Raw Data box is ticked to display the test data columns.

The test data columns appear between the Cap and Density columns, and also include the Test Time and Age Hours columns. Note that the measurement columns that appear depend on the type of specimen selected in the Type column.
| Measurement columns | The measurements for the relevant dimensions of each specimen type (ie. Dia1, Dia2, Dia3, Len, Len1, Len2, Wid, Wid1, Wid2, Dep, Dep1, Dep2, Spn, Height). Note that only the relevant dimension fields will be shown, for each specimen type. Also not that the average of the two measurements (eg Dia1 and Dia2) is reported on the concrete test report along with the other measurement (eg Height). |
| Weight | The weight of the specimen in kgs. |
| Load | The load on the test machine in kNs. The density and strength results that are reported on the concrete test reports are calculated using the measurement, weight and load results above. |
| Extern Crush | Select Yes if the specimen was crushed externally. |
| Test Time | The test time in 24 hour format. |
| Age Hours | The specimen age in hours, calculated from the test time. |
The results fields

Tick Show Results to display the result columns.

| Dens | The density calculated from the test data and reported on the concrete test report. |
| Strgth | The strength calculated from the test data and reported on the concrete test report. The type of strength reported on the test report varies for diferent test types (eg compressive strength for COMP tests, modulus of rupture for FLEX tests, etc). |
| Prd Str | Predicted strength. If the QESTLab is integrated with QESTMix then the system can predict the acceptance age strength of an earlier age specimen. Note that this field is not visible for some specimen types. |
| Wet Dens | Optional entry of Wet density result. |
| Failure Mode | the failure mode for each specimen. A list of possible failure modes is maintained by a QESTLab administrator in the QESTLab concrete failure mode list. There are two important implications of choosing a failure mode. The first is that some failure modes will result in the exclusion of this result from sample average calculations. The second is that for some failure modes the specimen is considered complete. The failure mode is reported on the concrete test report. |
| Measured By | The name of the person who measured this specimen. |
| Crushed By | The name of the person who crushed this specimen. |
| Checked By | The name of the person who checked the results for this specimen. |
Billing
In QESTLab 'billing' refers to the generation of charges for work done (as opposed to invoicing).
After the sample is registered, charges may be generated immediately. For instructions on generating the charges associated with this sample see section 5.2 - Billing.
Finding work to be done
This section covers the process of finding concrete specimens due for testing. This includes:
- Printing a daily worksheet of specimens due for testing.
- Bringing up an electronic version of the daily worksheet for data entry
- Searching for concrete samples using the sample ID or fieldsheet number.
Printing a daily worksheet
Follow the steps below to print a daily worksheet for all specimens due for testing on a particular date. Note that the daily worksheet report can be modified by your QESTLab admininstrator, so the name and layout of the report may be slightly different to that presented here.
Step 1. Expand the Reports node in the QESTLab tree. All reports are displayed in this area. Select the daily worksheet report. In the example it is called Concrete Compression Worksheet and found in a group called Concrete Testing. This may be different in your laboratory.

Step 2. The filter is displayed in the QESTLab filter area below the tree. Enter the required test date, or select the date using the calender. Click the Refresh button to run the report.

Step 3. The worksheet is displayed in the right hand window. An example is shown below.

Click the Print button
in the toolbar to print the worksheet.
Using the electronic worksheet
QESTLab provides an electronic worksheet for entering test data for all specimens for a particular date, regardless of project. The electronic worksheet may be used to enter data directly into QESTLab during testing or to enter data written on a printed daily worksheet.
Step 1. Expand the Tests/Documents node in the tree and select the filter Concrete Compression Tests. Note that this is not the daily worksheet discussed earlier, which is found under the Reports area in the tree.

Step 2. The Concrete Compression Tests filter is displayed in the data filter area.

Notice that the date defaults to Today. If a different date is required enter the date or use the calendar to select the date. You may also limit the search further by entering a sample ID or a fieldsheet ID. Run the filter by clicking the Refresh button .
Step 3. The specimens are displayed in the tree, grouped by test type. Note that this grouping may be slightly different for your organisation.

Step 4. Click on the test type node in the tree (eg. click on COMP100). The specimens are displayed in the right hand window ready for data entry.
Searching for concrete samples using the sample or fieldsheet ID
You may also want to search for particular concrete samples rather than displaying the electronic worksheet for specimen data entry. To do this follow the steps below:
Step 1. Select the Samples node in the tree.
Step 2. In the filter area, select either Concrete Samples or the Concrete Sample Groups filter.
Step 3. Enter a sample ID, fieldsheet ID or other search criteria and run the filter by clicking the Refresh button . The samples will be displayed in the tree
Entering raw test data
This section covers the process of entering the raw test data for concrete testing.
For a full description of each specimen field, see the previous section on The Concrete Specimens. Note that many of the specimen fields have already been entered for the specimens. This was done during sample registration. Enter the test data as follows:
Step 1. Tick the Show Raw Data box
to display the test data columns in the worksheet.
Step 2. Enter the measurements, weight and load results for each specimen. Press ENTER on your keyboard to move from one cell to the next. There is no need to click in each cell using the mouse.
The strength and density results for each specimen will be calculated and displayed in the grid. If a strength result is less than the F'c the result is highlighed in red.
Step 3. Enter the test time for each specimen. The age in hours will be calculated and automatically populated.
Step 4. By default the failure mode will typically be set to 'N' (Normal). If the failure was not normal then you can use an alternative letter designation as per the 'Failure Mode List'. For example 'S' for Shear, 'A' for Abnormal, etc.
Step 5. Optionally you may select the QESTLab user who measured and crushed the specimen in the Measured By and Crushed By fields.
Test results calculated by QESTLab
When raw test data is entered QESTLab calculates the following results:
- The density and strength result for each specimen.
- Sample average strength/densty - The average strength and density results for specimens of a certain type and age are calculated and stored in the database (eg. the average 28 day strength for COMP100 specimens). This is done for each sample.
- Pair difference - The difference in strength and density results between two specimens of the same type and age is calculated and stored for each sample.
The sample average and pair difference calculations are done for predetermined ages present in a sample. (Typically, 7,28,56 and 90 day). If these differences exceed tolerances (as per AS1379 for Australia) then the results are highlighted in red.
It is important to realise that data entered for specimens on the electronic worksheet is stored with that sample and reported on the concrete test report. The worksheet is simply a convenient way to enter data for multiple samples.
Checking test results and signing reports
Checking concrete test results
Overview
Most authorities require that the test results are checked, often by a different technician than the one who performed the work. In QESTLab, checked documents can only be changed by users with QESTLab laboratory supervisor rights.
Checking results
Step 1. Use a filter, such as Concrete Compressive Testing to bring up the electronic worksheet with the days testing. Note that this filter may be named differently in your organisation.
Step 2. Click on the Checked By button to mark all the completed specimens displayed as checked. Alternately mark specimens individually using the Checked By drop down list for each specimen.

Note that any incomplete specimens will not be marked as checked. A specimen is considered complete when it has a strength result or a Mark or Failure Mode with a corresponding entry in the Concrete specimen marks or Concrete failure mode lists that has been flagged to be considered Complete. For example a specimen that is destroyed on site may be marked with an X and should be considered complete, even though a strength result can not be determined.
Also note that if you have just checked later day specimen results (eg. 28day), and the concrete test report has already been issued for earlier results, then the test report will need to be un-signed and re-signed for the newly checked results to appear.
Signing and distributing concrete test reports
Overview
Once test results have been checked they are ready to be signed. In order to sign a report a user requries QESTLab signatory rights for all the test results shown on the test report.
When a test report has been signed any document with results appearing on that test report is read only.
Sign test reports
Step 1. Display the required test reports using a filter to display test reports, such as the Concrete test reports filter. Note that this filter may by named differently in your organisation.

Step 2. Enter a test date or a sample ID and click the Refresh button.

Step 3. All the test reports returned by the filter will be displayed in the tree.

Step 4. To display a test report click on it in the tree. The test report will be displayed in the right hand window.

The concrete test report is described in detail below. Each test report can be displayed and checked before being signed and issued.
Step 5. When test reports have been reviewed sign them all by selecting the Tests/Documents node, then clicking on the button on the toolbar. Note that this button is only available when the Tests/Documents node is selected, and not when one of the test reports is selected.
Alternately each test report may be signed individually. To sign an individual test report select it in the tree, then click on the checkbox at the bottom left of the document.
To sign a test report but leave it non-endorsed tick the Non-endorsed box at the bottom right of the test report before signing. The accreditation logo is not shown on non-endorsed reports.

Once a test report has been signed the sample and all related data is read only for all users regardless of Lab Supervisor or other rights. If a change needs to be made then a signatory needs to un-sign the test report by clearing the check box. The change can then be made and the report re-signed.
The only exception to this rule is that, even after the test report has been signed, concrete specimen tests that have not yet been checked can be entered/modified. This exception allows for the recording of later age results (eg. 28 days) where a test report has already been issued for an earlier age (eg. 7 days). However, even once the later age result is entered and checked it will not appear on the test report until the repot has been un-signed and re-signed.
Distribute test reports
Test reports may be distibuted by:
- Printing.
- Emailing as an Adobe Acrobat (*.PDF). file.
- Saving as an Adobe Acrobat (*.PDF) file to be emailed later.
Printing test reports
Step 1. Use a filter, such as Concrete Test Reports, to search for concrete test reports by date or sample, as described above.
Step 2. When all test reports have been signed, click the Print button
to print all test reports. Alternately select an individual test report, and click the print button to print that report only.
Emailing test reports
Step 1. Use a filter, such as Concrete Test Reports, to search for concrete test reports by date or sample, as described above.
Step 2. When all test reports have been signed, select the Tests/Documents node in the tree and click the Publish button
. This will prompt QESTLab to email all the displayed test reports. If an individual test report is selected then only that report will be emailed.
Step 3. The Batch Email window is displayed. Click OK.

Step 4. The Email Details window is displayed. Ensure the PDF Format button is selected, and enter the email address(s) for this project.
Saving a test report as a .PDF file
This option only applies to individual test reports.
Step 1. Click on an individual test report in the tree.
Step 2. Click the Export to File button [Image:buttons pdf button.png]].
Step 3. Browse to the location to save the file, enter a file name.
Step 4. Select Save as type Adobe Acrobat (*.PDF).
Step 5. Click Save to save the report. The file can be emailed or printed when required.
The concrete test report
The test report header
All test reports in QESTLab share the same header. Note that many of the fields shown below are only visible once the test report is signed.

The following fields can be customised using the QEST Administrator Console if required.
- Laboratory Logo - The logo for each laboratory is set in the QEST Administrator Console, under Laboratories > Internal.
- Accreditation Logo - The default is the NATA logo. This may be changed for users in countries other than Australia.
- Accreditation Text - The default text is shown. This can be replaced by entering your preferred text in the Accreditation Text option in the QEST Administrator Console.
- Endorsment Text - The default text is shown. This can be replaced by entering your preferred text in the NATA Endorsement Text option. If the test report is marked as Non-endorsed prior to signing then no text will display. The user must specify their preferred text in the Non Endorsed Text option.
- Approved Signatory - By default the text "Approved Signatory" precedes the name and title of the user who has signed the test report. This text can be replaced by entering your preferred text in the Approved Signatory option.
- Laboratory Details - These are set in the QEST licence file and can only be modified by Spectra QEST.
- Client and Project Details - Check the Specify client and project checkbox to display a different client and project on the test report to the one set in the sample.

The concrete test results
- Results are grouped by test type (eg. cylinders, grout cubes).
- The Details of sampled concrete section contains fieldsheet data.
- The Concrete specimens and results section contains specimen data and results.

SOILS FIELD TESTING
Registering work orders
Overview
Field soil samples are registered in QESTLab using a work order. A work order is simply a group of field soil samples taken for a particular client and project on a particular date. It is equivalent to a "test request" or a "work request".
The advantage of registering samples using a work order is that it simplifies the process of registering, reporting, certifying and billing samples:
- All the samples in a work request can be registered at once, and information common to all samples entered only once, at the work order level.
- All samples in the work request can be billed at once.
- All test results can be checked on the same screen, and reported on the same test report.
Work orders are added and displayed under the Work Orders node in the QESTLab tree.

Registering soil field samples using a work order
Adding the work order
Step 1. Select the Work Orders node in the QESTLab tree, and click on the New work order button
.

The Add Work Order window is displayed.

Step 2. Complete the fields in the add work order screen as follows.
| Laboratory | Ensure the correct laboratory is selected. If you have rights to only one laboratory the laboratory field will be automatically populated and locked. |
| Work Order ID | This MUST be left blank. A work order ID will then be created automatically |
| View | Leave the default view, or you may choose a different view to display the work order |
| Document Group | You may leave this blank. Note the documents listed in the lower window of the 'Add Work Order' screen. A document group is simply a way of adding one or more of these documents without having to select each document individually. If your system administrator has created document groups select one here, otherwise leave this blank. |
| Documents | If a document group was not selected above, tick each document to add along with this work order. eg. for a Hilf test select the Field Density:Hilf Density Ratio - Test Report and the $Billing document, for a dry density select the Dry Density Ratio test report and the Billing document. |
Step 3. Click OK to register the work order. Notice the two different views of the new workorder:
- The new work order is displayed under the work order node in the tree, with the associated documents are displayed underneath the work order.
- The work order screen is displayed in the right hand window. This work order screen will be used for bulk entry of sample and test data.
Populating the work order
Step 1. Complete the details of the work order as shown below.

| Client Request ID | Enter the customer's test request number. |
| Lot No. | Enter the road project lot number. |
| TRN | Enter the test request number. |
| Sampled By | Select the name, or type the code, of the techician who took the samples. These names are stored in the QESTLab sampled by list. |
| Customer Requirements | Optional. Select a text description of the requirements that the tests need to meet. Typically the compaction requirements according to a standard or modified density. These are stored in the the QESTLab customer requirements list. |
| Location | The location details for the project you selected above. This is stored in the QESTLab project list. |
Step 2. Select the sample type - production, roadworks or general. The type selected here will determine the fields shown on the report. For roadworks testing choose 'Roadworks'. This is discussed in more detail below.
Step 3. Select a test group from the Test Group drop down list. This will add the tests to be done on the samples in this work order. Test groups are similar to the document groups mentioned earlier, and contain commonly added groups of tests. They are created by a QESTLab administrator. Select an appropriate group for this workorder.
The example below shows a typical hilf work order. To register a dry density work order simply select an the equivalent Dry Density test group.

Step 4. The sample and tests are displayed underneath the work order details.
Click the
button to minimise the sample details in order to see all the tests.

Step 5. In the Number of Samples box enter the number of samples in the work order and press ENTER on the keyboard.

Step 6. The samples are added as columns on the work order screen. Notice that some sample data is populated from the work order data entered earlier.
To complete the sample registration process expand the Aggregate/Soil Sample section of the work order screen and enter the sample data.

There are several things to note:
Field sample ID: this is auto incremented. It may be overtyped.
Client Sample ID: if this is entered it replaces the field sample ID on the report.
GPS data not obtainable: must be set to true if you do not have GPS data for this sample. Otherwise you cannot leave this screen.
Sample type: note the roadworks details in the bottom section of the sample area. The fields shown here are determined by the type of sample selected in the work order section. If a sample type of 'General' or 'Production' was chosen the fields here would be different.
Entering field density data
Now that the work order is registered, field data may be entered.
For some tests the test data can be entered, for all samples, on the work order screen. The Nuclear Field Density test is one of these. Expand this test by clicking on the
button next to the Nuclear Field Density test. Enter the field data for each sample. Note that inital fields (down to Probe Depth A) only need to be entered on the first sample and will be replicated on the remaining samples by just pressing Enter.
The process of entering initial moisture content data is the same for both hilf and dry density tests.

Entering moisture content data
Initial moisture content data can then be entered. This is the same for both hilf and dry density work orders.

Entering oversize data
Hilf
Oversize data is entered on the work order screen , in the Hilf ratio sectionas shown below.

Dry Density
Enter oversize data on the work order screen under the Relative compaction section as shown.

Note that the Mass of wet soil, rock, container field MUST have a value greater than zero entered in order to make the final results calculate later. If there is no oversize material you can simply enter any non-zero number in this field.
Entering compaction data
If your compaction data is ready at this time you can enter this now. Compaction data must be entered on the relevant compaction worksheet for each sample.
Hilf
To enter hilf compaction data follow the steps below.
Step 1. Select the Hilf Ratio worksheet in the tree.

Step 2. The worksheet is displayed in the right hand window. Enter the data as shown in the example.

Note:
- The mould mass and volume can be stored with each piece of equipment and brought in to this screen when the equipment is selected. If you wish to store the mould mass ensure that you set a calibration schedule to check the mass as this may change.
- Out of specification equipment is highlighted in red.
- The Chart tab shows the graph for this sample.
Step 3. Repeat this process to enter compaction data for each sample in the work order.
Dry Density
Again, compaction data must be entered in the worksheet. The work order screen only shows the final results. To enter MDD data follow the steps below.
Step 1. By default the MDD is applied to each sample. If this is not the case then first expand the Maximum Dry Density section of the work order, and untick the samples that will not have an MDD performed on them.

Step 2. To enter MDD data in the MDD worksheet select the MDD node in the tree for the sample above.

Step 3. Enter available MDD data in the worksheet.

Step 4. On the work order screen import these results into each sample by selecting the MDD sample as shown below.

Note that if the MDD comes from another work order the sample number may be manually typed in here.
At this point the remaining test data will normally have to wait until the next day to be entered.
Billing
In QESTLab 'billing' refers to the generation of charges for work done (as opposed to invoicing).
After the sample is registered, charges may be generated immediately. For instructions on generating the charges associated with this sample see section 5.2 - Billing.
Entering final test data
After moisture content tests are complete the final data can be entered. This section covers the process of finding work orders and tests, and entering final data.
Overview
Technicians searching for testing work to be done have several options. They can search for:
- Work orders - you can search for all work orders for a particular project, date range or other criteria. You can also use the work order ID to bring up a particular work order. Test data may then be entered for all the samples in this work order.
- Specific Tests - instead of searching for each work order, you can search for all instances of a particular test, such as all incomplete moisture contents, that are waiting to be done. This will display all these tests, regardless of which job they belong to.
The method for searching is optional and may vary between laboratories.
Searching for work orders
To search for work orders for a particular job, or using the work order ID, follow the steps below:
Step 1. Click on the Work Orders node in the tree.
Step 2. If you have access to more than one laboratory then ensure the correct laboratory is selected in the lab node above the QESTLab tree.

Step 3. The default filter is displayed in the filter area. You can use this filter or select another one from the list.

Enter as many criteria as required. For example you may just enter the client and project, work order ID, or date range. You have to enter information in at least one field.
To search by project:
- To select a client or project click the
button and select the item(s) from the list.
- If a date field exists, then a date can be selected from the calendar by clicking on the
button.
To search by work order ID simply enter the ID in the work order ID field.
Step 4. To run the filter click the Refresh button
. The work orders returned by the filter are displayed in the tree under the Work Orders node. Results are grouped by project. Expand the project to see the work orders.

Entering final test data
When final moisture content data is available this should be entered as follows.
Entering final moisture content values
Expand the Moisture Content section of the work order screen and enter the final moisture content data.

Updating compaction data
Hilf
To update your hilf data with the final moisture content data, simply click on the Hilf Ratio worksheet in the tree. It is updated automatically.

Dry Density
To update maximum dry density data with the final moisture content data, follow the steps below.
Step 1. Click on the MDD node in the tree.

Step 2. Enter the final moisture content data on the MDD worksheet.
Step 3. On each of the other samples, click on the Relative Compaction node in the tree and import the MDD sample by clicking the Import button as shown.

Remember the 'Mass of wet soild, rock, container' field must have a non-zero entry to calculate final results.
Searching for test documents
QESTLab comes with several useful filters that allow you to search for all instances of specific test documents (eg. Moisture Content documents). These filters are found under the Tests/Documents node in the tree.

Useful filters here include:
- Moisture completion - returns incomplete moisture tests.
- Hilf density tests - returns incomplete hilf density tests.
- Maximum dry density tests - returns incomplete MDD tests.
Note that these filters will run immediately they are clicked and do not required any search criteria. Other filters require you to enter specific search criteria. If you do need to enter search criteria remember that Complete = 0 will find all incomplete tests.
More filters are available in the normal filter area underneath the tree.
Checking test results
Overview
Most authorities require that the test results are checked, often by a different technician than the one who performed the work. In QESTLab, checked documents can only be changed by users with QESTLab laboratory supervisor rights
Checking soils field testing results
Step 1. Use the work order filter to display the workorders you need to check.

You can search by any combination of client, project, work order ID, sample ID and Date. To find completed work orders use the criteria Complete = 1
Step 2. All work orders returned by the filter will be displayed in the tree.
Step 3. Click on a work order to display it and check the results. When you are satisfied, click the Checked By button on the top right of the work order screen to mark all tests in that work order as checked.
Alternately, each test can be marked as checked by clicking the T in the top right hand corner of the test document.
Signing and distributing soil field test reports
Overview
Once test results have been checked they are ready to be signed. In order to sign a report a user requries QESTLab signatory rights for all the test results shown on the test report.
When a test report has been signed any document with results appearing on that test report is read only.
There are currently three field density test reports in QESTLab for reporting the results of all the samples in a work order.
- Field density: Hilf density ratio.
- Field density: Dry density ratio.
- RTA field density: Dry density ratio.
As well as this, there is the material test report which reports the results of one individual soil sample.
The process for signing and distributing each test report is the same. They differ only in the data presented on the report.
Signing individual test reports
There are two ways to sign test reports. You can sign each report after you check that work order. To do this simple click on the report, then click on the checkbox at the bottom left of the report.
To sign a test report but leave it non-endorsed tick the Non-endorsed box at the bottom right of the test report before signing. This changes the appearance of the test report. Specifically the NATA (or other accreditation authority) logo and statement, is not displayed. For more details see the Test report header section below.

Once a test report at the work order level has been signed, the work order, samples, and all related data is read only for all users regardless of Lab Supervisor or other rights. If a change needs to be made then a signatory needs to un-sign the test report by clearing the check box. The change can then be made and the report re-signed.
</noinclude>
Bulk signing test reports
Alternately you can bulk sign many test reports.
Step 1. Display the required test reports awaiting signing, using an appropriate filter such as Field Test Reports for Signing.

Step 2. All test reports returned by the filter will be displayed in the tree.

Step 4. To display a test report click on it in the tree. The test report will be displayed in the right hand window.

The field density report is described in detail below.
Step 5. When test reports have been reviewed, sign them all by selecting the Tests/Documents node, then clicking on the button on the toolbar. Note that this button is only available when the Tests/Documents node is selected, and not when one of the test reports is selected.
The density test report
The test report header
All test reports in QESTLab share the same header. Note that some of the fields in the accreditation area can be modified by your system administrator. Laboratory details can only be changed by Spectra QEST.
You can change the client and project details shown on the report by selecting an alternate client or project.

The test results
The field density: hilf density ratio test report is shown below. Note that there are minor differences in the data reported on the RTA version of this report. The data reported on the field density: dry density ratio report is also slightly different, although the layout is the same for all three reports as follows:
- The work order data is shown first.
- Each column contains the data for a sample. There is enough room on each page of the test report for six samples. The exact number shown on the report depends on the sample type selected in the work order. For roadworks samples six samples are displayed, for general type samples four are displayed. If there are more than six samples a second page will be produced.
- The Sample details area contains data from the sample screen. The Field and laboratory data area contains test results.

Distribute test reports
Test reports may be:
- Printed - either individually or in bulk.
- Emailed - either individually or in bulk.
- Saved as an Adobe Acrobat (*.PDF) file to be emailed later.
Printing test reports
To print a test report simply click the Print button
on the toolbar while the test report is displayed.
To bulk print many reports use a filter, such as Field Test Reports, as described above, to return the required test reports.

Then select the Tests/Documents node, and click the Print button
on the toolbar to print all test reports.
Emailing test reports
The process for emailing reports is the same as that for printing. To email an individual report select the report and click the Publish button
on the toolbar.
To bulk email reports display the reports using a filter such as Field Test Reports, then click the Publish button. At the Batch Email Test Reports window, click OK to email all test reports displayed.

For further information, please refer to QESTLab:Test Report Publish Functionality.
Saving a test report as a .PDF file
Individual test reports may be saved as a .PDF file, and emailed later. This option only applies to individual test reports.
Step 1. Click on an individual test report in the tree.

Step 2. Click the Export to File button
on the toolbar.
Step 3. Browse to the location to save the file, enter a file name, and select Save as type Adobe Acrobat (*.PDF).
Step 4. Click Save to save the report. The file can then be emailed or printed when required.

OTHER AGGREGATE/SOIL TESTING
Registering samples
Overview
This section describes the situation where a lab needs to register one sample for a few laboratory tests, such as CBRs, gradings, and PIs. In this situation, you may prefer to just register the one sample rather than using the workorder functionality described in the section on soils field testing. Nonetheless if you have many samples that require testing you may still use a workorder to register and manage these samples. To register samples using a workorder just follow the steps outlined in the soils field testing section. To register a single aggregate/soil sample follow the steps below.
Registering a sample
Step 1. Select the Samples node in the tree, and click the New sample button
in the toolbar. The Add Sample(s) and Documents(s) window is displayed.
Step 2. Ensure the correct laboratory is selected. Then in the Type of Sample drop down list, select Aggregate/Soil Sample to register an aggregate/soil sample, or Asphalt Sample to register an asphalt sample.

Step 3. Select the documents to register with this sample, either by selecting a group in the Select groups window, or by selecting the individual documents in the Select documents window. Note that QESTLab contains a huge number of other documents and test methods. If a document appears but is greyed out then your user account does not have rights to view or edit that document. See your system administrator for access.
- To add charges for this sample you must add a Billing Document.
- To report the test results you must add an Aggregate/Soil Test Report.
Step 4. Click OK to add the new sample. The new sample is displayed in the tree. Note the sample ID has been automatically generated, and the documents are shown underneath the sample in the tree.

Step 5. The blank sample document is shown in the right hand window. Complete the fields in the sample document.
The aggregate/soil sample document is described in detail below.
The sample screen
Aggregate/Soil Sample Screen
NOTE: This documentation applies to the Asphalt Sample screen as well.
The aggregate/soil sample document is used to store sample details for an aggregate or soil sample.

GPS details
Enter the GPS details or select Not Obtainable. There is a document-level option "Enforce GPS Data Entry" that when set, will make all GPS data mandatory, however it is not mandatory by default. All GPS data should be formatted in decimal degrees. e.g. Spectra QEST's offices are located at latitude -34.904797, longitude 138.595742. Ensure that elevation is recorded in consistent units. Do not mix feet, yards and meters. On the sample screen, click the button shown below to display the location in Google Earth.

Google Earth will open and display the location of sample. Click on the location to learn more about the sample. The Client, Project, Date Sampled and Location details will be displayed.

Sample identification
| Lab Sample ID | The automatically generated sample ID using the aggregate/soil sample counter. |
| Field Sample ID | To report the field sample ID, enter it here and leave the client sample ID field empty. |
| Client Sample ID | To report the client's sample ID enter it here. It will then overwrite the field sample ID on the report. This means either the field sample ID or the client sample ID can be reported, not both. |
| TRN | Enter the test request number. |
| Submitted on the | Use the calendar to select the date that the sample is being submitted on. |
| at | Enter the submission time in 24 hour format. |
Client/project details
| Client | Populated from the QESTLab Client list. Select the client from the list, or enter the first few characters of the client code or client name and hit Enter. |
| Project | Populated from the QESTLab Project list. Only those projects for the client chosen above will be listed. |
| Owner | Automatically populated with the name of the project owner for the project selected above. |
Material details
| Supplier List | Select the supplier of the material in this sample. Populated from the QESTLab Aggsoil supplier list. |
| Material Source | Select the source of the material in this sample. Populated from the QESTLab Aggsoil material source list. |
| Material | Select the type of material in this sample. Populated from the QESTLab Aggsoil material list. Only those materials for the material source chosen above will be listed. |
| Specification Group | Select the specification group that contains the specification you wish to apply to this sample. |
| Specification Name | Select the required specification for this sample. This is used to highlight out of spec results. If a default specification has been set for the material chosen above, then this specification will be chosen. |
Disposition after test
Select Hold, specify how many days to hold the sample, how the sample should be held and what action should take place when the holding time expires. Alternately select Discard
Sample details
| Sampled On | Use the calendar to select the date that the sample is being submitted on. |
| at | Enter the submission time in 24 hour format. |
| Sampled By | Select the person who took the sample. Populated from the QESTLab Sampled by list. |
| Lot No. | Enter the number of the lot the specimen was sampled. |
| Method | Select the sampling method for this sample. Populated from the QESTLab Agg/soil sampling method list. |
Sample Suitability
Select Sample Not Suitable if the data recorded at the sample-level does not meet requirements.
Sample type
Different fields are displayed depending on the Sample type chosen.
General

| General Location | Enter relevant information about the sampling location. |
| Location Description | Enter more extensive details about the sampling location. |
| Prog Tonnes | The progressive tonnage removed from this location. |
Roadwork

| General Location | Enter relevant information about the sampling location. |
| Road Name | The name of the road the sample is from. |
| Chainage | The distance to sampling location along the road. |
| Offset Distance | The perpendicular distance from the point along the chainage set in the From field. |
| From | Where the offset is calculated from. The are four possible values: Left, Right, Left of Centre and Right of Centre. |
| Depth/Level | Whether the sample is from the base or subbase. |
| Boring Number | The reference number of the sample bore. |
| Depth | The depth of the sample bore. |
Sitework

| Location Description | Enter relevant information about the sampling location. |
| Prog Tonnes | The progressive tonnage removed from this location. |
| Bed Level | The bed level the sample was taken from. |
| Tonnes/hr | Tonnes per hour. |
| Water/hr | Water per hour. |
| Coarse Yield | Yield of coarse material. |
| Fine Yield | Yield of fine material. |
When you have entered the sample data you wish to enter, sample registration is complete.
Billing
For instructions on generating the charges associated with this work order see section 5.2 - Billing.
Finding work to be done
Searching for samples
To search for samples follow the steps below:
Step 1. Click on the Samples node in the tree.
Step 2. If you have access to more than one laboratory then ensure the correct laboratory is selected in the lab node above the QESTLab tree.

Step 3. The default filter is displayed in the filter area. You can use this filter or select another one from the list.

Enter as many search criteria as required. You have to type information in at least one field but you do not have to enter all criteria. For example you may just enter the sample ID, or just the date range.
Note:
- Some fields have lists associated with them (In this case Client ID, Project ID and Date Between). Click the
button to display the list items.
- If a date field exists, then a date can be selected from the calendar by clicking on the
button.
Step 4. To run the filter click the Refresh button
. The results of the filter are displayed in the tree under the Samples node.

Note that for this filter the samples are grouped together under the project. Expand the project to see the samples. Then expand the sample to see the test documents. Incomplete tests are shown in bold. In the example above all the tests are incomplete.
Step 5. To enter test data, select the test document for the test you are interested in. The test document for this test will be displayed in the right hand window ready for data input.
Entering raw test data
QESTLab electronic worksheets
QESTLab provides a custom electronic worksheet for each test method. Data is entered into the worksheet during testing, and QESTLab calculates the test results according to the relevant standard.
The tests to be conducted on a sample are displayed in the tree under the sample. To display the worksheet for a particular test click on that test in the tree.
- In the Equipment area, select the equipment used for this test.
- In the Details area enter the test data.
- The results will be calculated and displayed in the grey result fields.
Some worksheets such as the PSD worksheet contain more complex calculations.

The PSD worksheet is described in detail below.
The particle size distribution document
QESTLab catered for different test methods for performing a particle size distribution. This functionality is provided from a single code base with a dynamic user interface that changes depending on the test methods requirements.
This document covers all the possible functionality. The features mentioned will not be available to all test methods.
Options
The options displays up to 4 drop down boxes that effect the raw data that can be entered and how the calculations are performed.
| Drop Down Combo | Values | Function |
| Percentages | Passing (Total) | The final calculated values will be percentages passing the sieves. |
| Retained (Individual) | The final calculated values will be percentage retained on the individual sieve. | |
| Weights | Individual | Weights entered are for the individual sieve. The balance is cleared between each sieve weighed. |
| Cumulative | Weights entered are cumulative and include the current and all previously weighed sieves. | |
| Washing | None | The sample is not washed over a fine sieve. |
| Total | The entire sample has been washed over a fine sieve (usually 75um / No. 200) | |
| Split | The split sample has been washed over a fine sieve (usually 75um / No. 200) | |
| Drying | Total | The entire sample has been dried. |
| After Split | The sample down to the split was not dried. The sub sample resulting from splitting was dried. |
Equipment
Select the equipment used in performing the test. This includes the Balance, Sieve Set, Sieve Shaker and equipment used for drying the sample.
In the case of a sample that has been split select a second set of equipment that was used on the sub sample. If a sieve set is selected that has its diameter specified in the equipment schedule then the overload mass for this sieve will be displayed in the data entry grid.
Chart
The chart shows the sieve analysis represented on a semi-logarithmic chart. Also shown are specification limits which will be highlighted in red if the test results do not conform. This chart is updated in real time.
Raw data and results
Enter the raw data (masses). Final test results are calcuated and displayed. The columns in this grid are always the same, they are:
| Sieve Size | The sieve size that is being tested. |
| Cumulative/Non Cumulative Mass | Either the mass retained on the sieve, or the cumulative mass from the current and all previous sieves. |
| Max Mass | The maximum mass allowed on this sieve before it is overloaded. |
| % Pass (Total) / % Retained | The calculated result. |
| Limits | The specification limit for the sieve. |
The rows in the grid vary depending on the options set and the sieves selected in the specification limit.
How is? / How do I?
How is the Total Dry Mass determined?
The figure for the total dry mass can be reached several different ways depending on the test method.
The entire sample could be dry / have been dried before commencing the test and the dry sample weighed. In this case the user can directly enter the Total Dry Mass.
The entire sample could be dried as part of the test procedure. In this case the user could still enter the Total Dry Mass or they may choose to, also enter the Wet Mass and possibly the Tare Mass (weight of the tray) and Tare Mass + Wet Sample.
The moisture content of the test could have been determined in a separate test on a sub sample. In this case register the moisture content as a test on the same sample (a sibling test to the PSD) and enter the details. By default this moisture content will then be used to determine the Total Dry Mass when you enter the Wet Mass on the PSD screen. This behaviour can be disabled via the document option ‘Do Not Use Sibling Moisture’. See the document IQ0018 QESTLab System and Document Options.htm for more details.
For some test methods the ‘Total Dry Mass’ is calculated based on the moisture content of the sample after the first split. In this case the option ‘Drying After Split’ is selected. The wet mass of the material passing the split sieve is recorded, as is the ‘Split Wet Mass’ and ‘Split Mass’. The moisture content is determined from the ‘Split Wet Mass’ and ‘Split Mass’. The dry mass of the material passing the split sieve is then calculated and added to the material retained on sieves prior to splitting. This value is the ‘Total Dry Mass’. This assumes that the material already retained are large particles that do not retain any moisture.
How do I split a sample?
When you are required to split a sample and use a smaller portion for the remainder of the test you double click in the cell that contains the last sieve tested before splitting. The system will prompt asking if you want to split after this sieve. You can split a grading twice in this way, to allow for a coarse, intermediate and fine fraction. Double clicking on an existing split will give you the option of removing it. The calculation of percentages passing for the split material will be automatically determined taking into consideration what portion of the entire sample is represented by the material.
Where do I enter details about washing the sample and the Finer 75um (No. 200)?
When washing material over a fine sieve (75um) you need to record the mass retained after washing and drying. This figure is entered in different places on the grid depending on when the washing is performed. If the washing took place for the entire sample then an ‘After Wash’ row appears below the ‘Total Dry Mass’. If washing after a split the ‘After Wash’ appears below the ‘Split Mass’. Remember the value entered is for the dry mass after washing. If you weigh this material in the tray (and have provided the weight of the tray in the first row of the grid) then you will need to set the document option to ensure the mass of the tray is removed from the figure entered before the Finer 75um figure is calculated. See the document IQ0018 QESTLab System and Document Options.htm for more details.
This figure will in turn be used to calculate the Finer 75 um (No. 200) which appears at the bottom of the grid. Some test methods allow for the determination of the Finer 13.5um sieve. This functionality is activated via a document option. See the document IQ0018 QESTLab System and Document Options.htm for more details.
Does the electronic worksheet check for material loss?
For most test methods the electronic worksheet will check to see if material loss has exceed 1%, or a figure provided by the method. This is displayed in red along side the ‘Total Dry Mass’ and the ‘Split Mass’. If after splitting you weigh the material in the pan and it includes all the split material then you will need to set a document option so the material loss check takes this into consideration. See the document IQ0018 QESTLab System and Document Options.htm for more details.
I separated the sample and sieve in two or more lots to avoid overloading sieves, can this be recorded?
Sieves have a maximum acceptable amount of material that can be tested in a single operation. Where the sieve diameter has been entered in the equipment schedule, this maximum mass is displayed in the data entry grid. When a tested mass is entered that exceeds this value the user is warned about the overloading of the sieve and the problem is highlighted. If the sample was tested in two or more lost then enter the mass retained on the sieve as the individual values separated with commas. When you move of the cell the combined mass will be displayed. When moving back on the cell the original breakdown as entered will be shown.
Summary Data for Individual Screens
Particle Size Analysis of Soils - Hydrometer [Q103C]*
Minimum Data Requirements
Example
Completion Requirements
Example
Formulae
Example
Rounding
Example
Dependant Tests
- Test 1
- Test 2
Test-specific Options
Example
Checking test results
Overview
Most authorities require that test results are checked, often by a different technician than the one who performed the work. If you have just registered a single sample then each test will need to be marked as checked individually. If you have registered a work order then the work order screen has a button to mark all tests as checked. When a test is marked as checked it can only be changed by users with QESTLab laboratory supervisor rights. When all tests are checked for a sample then the report be signed.
Checking test results
Step 1. To mark a test document as checked, first click on the test to display the test.

Step 2. Then click on the T icon in the top right of the test document header.

Step 3. At the Laboratory/tester details window tick the box to indicate who tested and who checked the data. Note that data entry users (with QESTLab Data entry rights) will be able to select a name from the drop down list. If you do not have these rights your name will be automatically selected and locked in.

Once data has been checked, the ability to change information on this document is restricted to users with Laboratory Supervisor rights only. The document is read only for all other users. Once all tests for a sample are checked then the sample is also ready only.

Signing and distributing test reports
Overview
Once test results have been checked the test report can be signed. QESTLab signatory rights are required in order to sign test reports. Signatory rights are managed by your systems administrator. A signatory can only sign a test report where they have signatory rights for all the test results shown on the test report.
When a test report has been signed, any document with results appearing on that test report is read only.
Note that some tests, such as the CBR, that require specialised data and graphs, have their own test report. Other aggregate/soil tests, such as gradings, atterbergs and most other tests, are reported on the standard aggregate/soil test report.
Finding test reports to sign
To find test reports to sign you can either:
- Search for the required samples, then go through and check and sign each report,
- Search for the reports, then review the reports as required, and sign them all at once.
Obviously signing all reports in bulk is quicker but the choice will depend on the specific jobs you have on at the time, and the process you are most comfortable with.
Signing each sample individually
To search for samples click on the Samples node as normal. Then use the filter to display the required samples. Click on the report in the tree and sign by clicking the checkbox at the bottom.
As for any test report, tick the Non Endorsed box to leave the NATA logo and statement off the report header.

Bulk signing
To search for specific documents (other than samples and workorders), click on the Tests/Documents node in the tree.
Step 1. Select an appropriate filter to return aggregate/soil test reports. There is one called Aggsoil Test Reports.

Step 2. Enter a search criteria of Complete = 0 to return all incomplete test reports, ie. reports that have not yet been signed. Enter additional search criteria if required.
Step 3. To run the report click the Refresh button
. Test reports returned by the filter will be displayed in the tree, grouped by project. To display a test report click on it in the tree. The test report will be displayed in the right hand window.

Step 4. When test reports have been reviewed, you can sign them all at once. To do this click on the Tests/Documents node, then click on the button on the toolbar. Note that this button is only available when the Tests/Documents node is selected, and not when one of the test reports is selected. If you can't see this button check the Tests/Documents node is selected.
Alternately you may still sign each test report individually as shown above.
Once a test report has been signed, the sample and all related data is read only for all users regardless of Lab Supervisor or other rights. If a change needs to be made then a signatory needs to un-sign the test report by clearing the check box. The change can then be made and the report re-signed.
Distribute test reports
The process of distributing these reports is identical to that for field density reports. They may be:
- Printed - either individually or in bulk.
- Emailed - either individually or in bulk.
- Saved as an Adobe Acrobat (*.PDF) file.
Printing aggregate/soil test reports
To print an individual report, select the report in the tree and click the print button
on the toolbar.
To bulk print reports, use a Tests/Documents filter to display the required reports as described above. Then click on the print button. All displayed reports will be printed.
Emailing aggregate/soil test reports
To email an individual report select the report in the tree and click the Publish button
on the toolbar.
To email multiple reports from one work order, select the work order in the tree and click the Publish button
on the toolbar.
NOTE: Emailing multiple reports from one work order is only available in QESTLab 4.1 and onwards.
For further information, please refer to QESTLab:Test Report Publish Functionality.
Saving a test report as a .PDF file
To save a report select the report in the tree and click the Export to File button
on the toolbar.
Browse to the location to save the file, enter a file name, and select Save as type Adobe Acrobat (*.PDF).

The aggregate soil test report
The test report header
All aggregate/soil test report shares the same header as all test reports in QESTLab. It also has the following additional features.
Tests
Not all of the tests for the sample need to be reported. The Tests... allows the user to select which tests to report. To not report the results of a test simply untick that test.

Test report layout
The Test Report View dropdown box contains a list of possible layouts for the report

The PSD predominant view emphasises the grading results. Note that in this view there is only room for one other test result.
Specification
The Use an alternate specification checkbox allows the user to display limits on the test report according to a specification other than that set in the sample.

The test results
The aggregate/soil test report is shown below.
- The Sample details section displays data from the sample screen. #The Particle size distribution section contains the results and graph of any grading test performed on the sample.
- The Other test results section reports the test results of all other tests performed on the sample.

Test report options
The test report can be configured in the QEST Administrator Console via the Document-Level Options section by selecting the option from the list of documents that corresponds to the report at hand.
PSD Non Classified AS 1289.3.6.1 Chart
**Available from QESTLab 3.3 onwards only.
When the Document-Level Option "PSD Non Classified AS 1289.3.6.1 Chart" is set to True, the Standard Aggregate/Soil Test Report displays the Particle Size Distribution graph in conformance with AS 1289.3.6.1 Section 8.
BILLING AND INVOICING
In QESTLab, billing refers to the process of generating the charges associated with each sample. The term invoicing is used to describe the process of generating invoices. QESTLab provides a complete billing and invoicing package. It is important to emphasise that no matter what type of testing you do, ALL your laboratory's charges can be captured and invoiced in QESTLab.
Setting up your fees
The first step to using the billing and invoicing functionality is to enter into QESTLab all work items that are chargeable, and the amount to charge for each item.
This information is stored in 3 lists:
- The Billable Items list contains each test and work item that can be charged for. This list is maintained centrally and cannot be modified by laboratories.
- The Fee Schedule list contains specific unit charges for each of the billable items above. Each laboratory can define their particular charge for each billable item, including specific fees based on the client or project.
- The Price Lists represent collections of Fee Schedules. Each Price List has an upcharge/discount percentage that applies to all Fee Schedules in the list. Each laboratory, or individual client or project can define its own Price List.
Once the lists are set up, changes will only need to be made when new clients and projects are added to the system, or when prices change.
Billing
Billing Document
Billing documents can be created automatically in QESTLab. The process of autocreation is as follows:
- Register a QESTLab billing document for the work order, concrete sample group, or aggregate/soil sample.
- Generate the charge for the sample or work order - this involves telling QESTLab to automatically calculate the charges for each test on that sample, and then manually adding any extra charges such as mileage, hourly charges, freight, etc.
Register a billing document
Please see the section in billing documents.
Generate charges in the billing document
The charges appearing in the billed items section of the billing document can be automatically generated. The steps are outlined below.
Step 1. Click on the billing document in the tree. The billing document is displayed.

Step 2. Click the Auto Create button to automatically generate the charges associated with this sample.
To generate the charges QESTLab examines the fees in the Fee Schedule list for the tests you have added with this sample (TBD: link here). When searching for the relevant fee for a particular test, QESTLab first checks to see if there is a (generally cheaper) project fee for this project. If no project fee is found for this project, QESTLab checks for customer fees for this customer. If no customer fees are found laboratory fees are checked and finally global fees. If two or more matching fees are found on the same level (eg. two different fees for the same client), then the first one set as Default in the fee schedule list is chosen (TBD: link to the fee schedule document).
Step 3. Add additional charges if required.
Certain charges will not be added by the auto-create process, and must be added manually. These include;
- Charges that are not associated with a test, such as mileage charges, freight, or hourly charges.
- Charges for tests that are not included in QESTLab. If you perform a test that does not have a test screen in QESTLab you must manually add a charge for this test. You only need to have a billable item and an associated fee setup in QESTLab and you can charge for anything you like. To manually add a charge record:
- Click the Add button.
- Select the fee schedule item for that item using the drop down box in either the Item Code or Detail field (whichever field is not selected will be populated). By default only the project level fees for the specified project are available for selection. If there are are no project level fees for the selected project, the Show Global, Lab and Customer Level Fee Schedules checkbox is automatically checked and all fee schedules become available for selection. If you want to see client and laboratory fee schedules even when project fee schedules are available, manually check this box.
- Enter the number of units.
Charge records can be deleted by selecting them in the grid and clicking the Delete button.
Step 4. Add additional information you wish to display on the invoice.
The Identification area is fully editable and can be used to store any extra information you want to display on the invoice. If you want the project (job) number to appear on the invoice type it in here, since this is currently not automatically displayed on the invoice. The client, project, date, identification and source fields on the billing document are populated from the sample and may be changed here if required. Another known issue with this area is that the last line of this area may be truncated on the invoice. To overcome this add an extra (blank) line in the identification area. Note that the identification fields can be customised to display certain fields from the sample screen. This is done by a system administrator. However if you delete these fields the default fields will be displayed instead.
Batch generation of charges for many samples
QESTLab also allows you to automatically generate charges for many samples at a time. However this only creates the automatically added charges, and does not add the manually added charges such as mileage, hourly charges, etc. For this reason it is commonly used update charges for samples where the charges have previously been generated but additional chargeable work has been performed on the sample, such as in concrete testing.
To generate the charges for all samples for a particular job follow the steps below.
Step 1. From the Tools menu select Charges/Invoices > Update Billing. The Update Billing window is displayed.

Step 2. Select the laboratory and date range required and click Update. For large amounts of sample this may take several minutes.
As stated above, this process will also update charges for samples with existing charges. Also note that any charges that have been manually added to a billing document will not be removed when the billing is automatically updated.
Invoicing
MANAGING PROJECTS, FEE SCHEDULES, EQUIPMENT AND OTHER LOCAL DATA
Managing projects
This section covers the process of maintaining projects in QESTLab. At Coffey Geotechnics clients are managed centrally by corporate staff in head office. However each laboratory will maintain its own list of projects.
The project list
Step 1. To manage projects firstly ensure your laboratory is selected in the Lab dropdown box above the tree.

Then click on the Projects node in the tree.

If the projects node is not visible in the tree, ensure your laboratory is selected in the Lab dropdown box.
Step 2. All the projects for the selected laboratory are displayed in the right hand window. To see only the projects
for a particular client select that client in the filter area (ensure the
button is selected to see only the clients for your laboratory), then click the Refresh button
.

Add projects
Step 1. To add a project click the Add list item button
on the toolbar.
Step 2. The Add List Item: Projects window is displayed. Ensure the correct laboratory is selected (if you have access to only one lab this will be locked), and select the client for which the project is being added.
Project code - all new job numbers MUST have the standard format LABTXXXX#####XX. This consists of a four letter division code (LABT), a four letter laboratory code (eg. ALBU), a five digit sequential number (eg. 09523), and a two letter phase (eg. AA). For example LABTALBU09523AA. If you leave the project code field blank a code will automatically be created for you. The only time you will need to override this is to use a previous project code and specify the next phase (AB, AC, etc). To do this simply overtype the project code with the required number and phase.

Step 3. The new project is shown at the bottom of the list. Enter the details of the project in the details area above the list. Note: If you leave the address fields blank then QESTLab will use the client address for reports. If you enter an address for the project QESTLab will use the project address on reports. Invoices will always have the client address details.
Other useful fields are the 'Principal' appears on reports, and the 'Email address' which is used when emailing reports.

Modify projects
You may modify project details at any time.
Step 1. Click on the project in the project list. The details are shown in the details area.

Step 2. Modify the details. The contents of each field is saved as soon as the user clicks into another field.
Delete projects
To delete a project, select the project in the grid and click the Delete button
on the toolbar
Managing fee schedules
This section covers the process of maintaining fee schedules in QESTLab. A complete list of billable items will be maintained centrally so each laboratory will only need to maintain the actual fee schedules for their laboratory, clients and projects.
Billable items cannot be created or modified by laboratory staff. New items must be requested by email from Herb Kaiserseder at Albury Office
The first step to using the billing and invoicing functionality is to enter into QESTLab all work items that are chargeable, and the amount to charge for each item.
This information is stored in 3 lists:
- The Billable Items list contains each test and work item that can be charged for. This list is maintained centrally and cannot be modified by laboratories.
- The Fee Schedule list contains specific unit charges for each of the billable items above. Each laboratory can define their particular charge for each billable item, including specific fees based on the client or project.
- The Price Lists represent collections of Fee Schedules. Each Price List has an upcharge/discount percentage that applies to all Fee Schedules in the list. Each laboratory, or individual client or project can define its own Price List.
Once the lists are set up, changes will only need to be made when new clients and projects are added to the system, or when prices change.
The Fee Schedule list
The fee schedule list links billable items to an actual unit charge for each laboratory, and optionally for a client and project. When QESTLab generates the charge for work done on a sample in a billing document, it does so by examining the relevant fees in the 'Fee Schedule' list. The 'billable items list' lists what can be charge, while the fee schedules list determines how much to charge.
Fees can apply at any of three levels:
1. Laboratory level: Laboratory level fees are the fees set by each laboratory. In contrast to client or project level fees, laboratory level fees are used to enter typical charges for each billable item.
2. Client level: When a particular client gets a special (typically cheaper) rate for a particular billable item, a client level fee would be created to store this lower rate for this client.
3. Project Level: When a project (belonging to a client) gets a special (and typically even cheaper) rate, a project level fee would be created.
When QESTLab automatically generates the billing documents, the most restrictive fee schedule item is used. If a project level fee can be found for the unit of work done on a sample, this fee schedule item will be used. If a project level fee can not be found, QESTLab will then check for client level fees, then finally laboratory level fees. If two entries exist for a specific level (for example, two fees may be entered for client level fee), then QESTLab will use the fee that has 'Default' set to 'Yes'.
Fees are typically entered for specific tests, as well as for labour and other hourly or mileage based activities. Some examples are shown below.

Description of Fee Schedule list fields
The image below shows the fields that are associated with a fee schedule list.

The following list describes these fields
- Code: Any unique code to identify the fee schedule item.
- Name: A name to describe the fee schedule item.
- ItemUnit: The units of the item. For example, if the item is for travel expenses, the unit might me 'kms'. The entry in this field appears in the billing document and consequently in the invoice, as shown below.


- ItemUnit2: Some situations may require that two units be specified for a billable item. This field is only used when 'Multiply Units' is set to true. Please refer to the 'Multiply Units' entry below for more information. The entry in this field appears in the billing document and consequently in the invoice, similar to the 'ItemUnit' field.
- MultiplyUnits: In some situations the final charge is calculated by first multiplying the number of ItemUnit and ItemUnit2 together, then further multiplying by the item charge. For example, ItemUnit may represent the number of Maximum Dry Density Tests, ItemUnit2 may represent the number of hours spent on each report, and the item charge may be entered as cost per hour spent doing MDD tests. The final cost would be ItemUnit x ItemUnit2 x Item Charge, requiring 'Multiply Units' to be set to 'True'.
- UnitCharge: The charge per unit of work associated with this item.
- MinCharge: The minimum charge for this item. If this item is included in a billing document, then the charge will be at least the amount indicated in this field. For example, if the UnitCharge is 5.00, the number of units in the billing document set at 3, and the MinCharge for the item set at $20.00, the client will be charged the minimum of $20.00, instead of 15.00, which is the UnitCharge x number of units.
- Default: If two charges exist on the same level when the billing document is being automatically generated, the item in the fee schedule list that has 'Default' set to 'Yes' is chosen to generate the charges. Please refer to the section on levels for more information about fee levels.
- LabName: The laboratory for which this charge applies. As charges must be associated with a particular laboratory, this field must be set.
- CustomerName: This must be set to a customer's name if you are creating a charge at the client level.
- Project Name: This must be set to a project's name, in addition to setting the customer name, if you are creating a charge at the project level.
- Business Unit 1(%): TBD
- Business Unit 2(%): TBD
- Business Unit 3(%): TBD
- RecordCharge:
Add a new fee schedule item
Step 1. Ensure your laboratory is selected in the Lab dropdown box above the tree.

Then select the fee schedule list under the Lists node in the tree.

Step 2. Click the Add List Item button
to add a new list item.
Step 3. In the Item Name drop down box select the billable item that this fee relates to. To create a fee for a particular client (a client level fee) select the relevant client from the Client drop down box. If a project level fee is required select the relevant project. Note that the Laboratory will be auto populated (and locked) with the laboratory currently chosen in the the QESTLab tree. If you have access to more than one laboratory and you wish to choose a different laboratory click Cancel and choose the required laboratory in the tree.

Step 4. The new fee will be added to the bottom of the list. Enter the Unit Charge for this fee. The following fields can be entered as required:
Minimum charge - enter a minimum charge for this item if requried. Default - if more than one fee schedule is applicable to a particular laboratory, client or project then one fee schedule must be set as the default. When charges are auto-created by QESTLab, the default fee schedule will be used to calculate the charge.
Record charge - this is used normally used to distinguish different types of concrete tests. In this case the RecordCharge field is populated with the 'Item' from the Billable Items list.
The new fee schedule item is now ready to use.
NOTE: If the mapping on a Billable Item is changed (after the corresponding Fee Schedule has been created) then the Fee Schedule will need to be deleted and re-added. Hence it is advisable to ensure that the Billable Items list is mapped correctly before proceeding with Fee Schedule creation.
Searching the Fee Schedule list
When the list is populated use the filter to display laboratory, client or project fee schedules as required. Note that selecting a client or project of (none) will display only laboratory level fee schedules, whereas selecting a client or project of (all) will include all fee schedules regardless whether they are laboratory level fees, or apply to specific clients or projects.

Delete a Fee Schedule item
To delete a fee schedule item, select the item in the list and click the Delete button
on the toolbar.
Managing equipment
This module explains the process of maintaining equipment in QESTLab. By the end of this module users should be able to maintain the equipment register, and record calibration schedules for equipment.
NOTE: The documentation on this page applies to QESTLab 3.2 (and earlier) and is no longer applicable in QESTLab 3.3.
Overview
The QESTLab equipment register allows the user to:
- Manage four calibration schedules for each piece of equipment.
- Record the specific item of equipment used for each test. This allows values associated with that item of equipment to be used in test calculations, and flags tests where out of calibration equipment was used.
- (Where available), configure the direct connection between equipment and computers running QESTLab.
Adding equipment
Each item of testing equipment should be entered into QESTLab.
Step 1. Select the Equipment node in the QESTLab tree and click the New equipment toolbar button
.
Step 2. Ensure the correct laboratory is selected, then select the equipment type, and enter a group if required. Groups are used to break equipment types into more defined categories.

Step 3. Click OK and the new piece of equipment will be displayed in the QESTLab tree under the nominated laboratory, equipment type and group.
Step 4. Complete the equipment code, serial number and other details as required. If an item of equipment is set as default then, on test screens where this type of equipment is used, this particular item will be selected by default. Otherwise none will be selected by default as in the example below.

The equipment code is simply a sequential number (eg. 1, 2,.. 100, 101, etc) This is a global number across the whole organistion. To get the next sequential number available contact the business system manager.
How to Calibrate
NOTE: The documentation on this page applies to QESTLab 3.2 (and earlier) and is no longer applicable in QESTLab 3.3.
Calibration
Each equipment item can have up to four calibration cycles specified. Typically, each cycle will have a different duration and be performed by a different body. Enter the different calibration cycles on the tabs Calibration 1 to Calibration 4.

The balance above has three calibration cycles specified:
- A monthly in-house user check (shown).
- A half-yearly external repeatability calibration.
- An external NATA calibration every 3 years.
The Last Date records the date the equipment was last calibrated.
The Frequency records the required calibration frequency of that cycle.
The Advise field sets a reminder for that cycle.
Recording a Calibration
1. For the appropriate cycle enter the name of the body performing the calibration, then click Record Calibration.
2. Enter any relevant remarks on the Equipment Calibration form, set the date of calibration, and click Calibrate. The remarks will be added to the Calibration History field, and the due date for the next calibration of that cycle will be updated.
Calibration Values
Some equipment types have an additional grid to store the calibration values. Enter the calibration values. These values can then be used on test screens where this item of equipment is selected.
Maximum Dry Density Mould
A typical calibration for an maximum dry density mould is shown below. The mould type should be specified as A or B if used for Australian tests or as 4 or 6 (indicating 4 or 6 inch) if used for American tests.

Proving Ring
Calibration values for proving rings are entered in the format pictured below.

The gauge/load values should be entered in the 'values' tab of the screen in successive pairs. The values in each pair should be separated by a comma. The pairs of values should also be ordered upon being entered, generally in ascending order.
Due for Calibration
QESTLab has several methods by which it advises the user when an equipment item is due for calibration.
1. The equipment screen - the calibration tabs for overdue calibration are highlighted in blue and the due date highlighted in red.

2. The equipment register - the equipment item will be highlighted in red in the QESTLab tree.

3. The test screen - any item of equipment due for calibration will be highlighted in red.

4. Reminder prompts at logon - when a user logs on to QESTLab who has both QESTLab Calibrate equipment rights, and rights to the laboratory containing equipment due for calibration, they will be prompted for each equipment item due for calibration.

Equipment reports
There are several reports available under the Equipment report group that display the calibration status of equipment.
Managing other local data
There are a number of other lists maintained in QESTLab. Some of these are mantained centrally by the Business System Manager. The items in these lists are available to all laboratories. New items must be requested centrally. They include:
- Concrete Failure Mode
- Concrete Compaction Method
Other lists can be modified by each laboratory. These include:
- Additional remarks
- Agg/soil material source (quarry)
- Agg/soil materials
- Agg/soil sampling method
- Agg/soil specimen marks
- Concrete location
- Concrete plant
- Concrete specimen marks
- Concrete supplier list
- Concrete test groups
- Customer requirements
- Reason non standard
- Sample remarks
- Sampled by (list of field testers)
- Weather conditions
QESTLab contains a large number of lists. The lists available to your organistion will depend on your QESTLab license. To edit a list follow the steps below.
Step 1. To add a new list item expand the Lists node in the tree, click on the relevant list, then click the new list item button in the toolbar
.
Step 2. At the Add list item window, select a laboratory and complete the requested details. The required details will obviously be different for each list.

Remember that for QESTLab users with multiple laboratiries, each item in a list may be:
- Global - available to all laboratories.
- Local - available to one laboratory only.
To make an item global assign it to the global laboratory. This item will then be available to all laboratories. To restrict an item to a particular laboratory assign the item to that laboratory.
Step 3. To save the new list item click the verify and save changes button
.
To delete a list item select the item and click the delete button
.
Lists in detail
The fields in each locally maintained list are described below. Some fields are completely optional, or were created specifically for other users of QESTLab, and are not relevant for Coffey Geotechnics.
Agg/Soil Material Source
CODE: A unique code for the agg/soil material source
NAME: The name of the agg/soil material source
SUPPLIER CODE: The code of the supplier of this material, from the agg/soil supplier list.
CUSTOMER: optional
COSTCENTRE: optional
Agg/Soil Materials
CODE: A unique code for the material
NAME: The name of the material
SOURCE CODE: The agg/soil material source code from the agg/soil material source list
SPECIFICATION: Choose a default specification for samples of this type. This specification will be selected by default on the aggregate/soil sample screen when this material is selected.
TYPE: The agg/soil material type from the agg/soil material type list
Agg/Soil Sampling Method
SAMPLING METHOD: Describes the type of sampling done. E.g:- AS1141.3.1 Clause 6.9.5a, AS1141.3.1 Clause 6.9.6 or Tested as Received etc...
Agg/Soil Specimen Marks
MARK: A Mark given to the specimen by the tester
DESCRIPTION: A description of the above mark
EXCLUDE: A YES or NO field that determines whether to exclude a specimen with this mark
COMPLETE: A YES or NO field that determines whether to consider a specimen with this mark complete
Concrete Location
LOCATION:' A text field to store location details.
Concrete Plant
CODE: A unique code for the concrete plant
NAME: The name of the plant
SUPPLIER: Supplier code and supplier name from the concrete supplier list
CUSTOMER CODE: optional
BATCH MATERIAL MAPPING: Used for interfacing with the concrete mix system, QESTMix.
BUSINESS: Used for interfacing with QESTMix
REGION: Used for interfacing with QESTMix
AREA: Used for interfacing with QESTMix
EMAIL: Email address of a contact at the plant
COST CENTRE: optional
Concrete Specimen Marks
MARK: A Mark given to the specimen by the tester
DESCRIPTION: A description of the above mark
EXCLUDE: A YES or NO field that determines whether to exclude a specimen with this mark
COMPLETE: A YES or NO field that determines whether to consider a specimen with this mark complete
Concrete Supplier
CODE: A unique code for the supplier
NAME: The name of the supplier
Concrete Test Groups
The fields below are simply repeated for each specimen in the test group.
CODE: A unique code to identify the group
NAME: The name of the group
PRODUCT CODE: Enter a product code. This group will be chosen by default for samples with this product code.
TYPE: Type of this specimen (COMP100, FLEX100, etc)
AGE: Age of this specimen in days
xSP: Externally sampled
xCR: Externally crushed
CAP: Type of cap used for this specimen (R, S, etc)
CORREC: Correction applied
MARK: Mark on this specimen
CRT: (Certificate). Whether to report the results of this specimen
CHG: (Charge). Whether to charge for this specimen
Customer Requirements
REQUIREMENT: A test requirement for a particular customer
Reason Non Standard
REASONCODE: Code identifying the reason
REASON: Reason for non standard specimen. 50 characters allowed
Sample Remarks
CODE: Code for this remark
REMARK: Remark. 50 characters.
Sampled By
CODE: A unique code for each technician
NAME: The name of the technician
NOTE CODE: optional
Weather Conditions
WEATHER: Weather condition
MANAGEMENT REPORTING
QESTLab contains a number of pre-defined reports. User are able to modify these or create new reports as required. This module explains the process of running management reports.
Running a report
Step 1. Select the report in the tree. Reports are found under the Reports node. They are grouped into functional groups. Expand the tree and select the report to run.

Step 2. Enter the criteria for the report. Some reports will only require a date. Others allow more detailed criteria. The more criteria entered the narrower the search.

Step 3. Enter the desired criteria and click the Refresh button
to run the report.
Step 4. The report is displayed in the right hand window. An example is shown below.

Saving a report
Click the Export to File button
to save the report as a .PDF file.
Click the Export to CSV button
to save the report as a .CSV file.
Emailing a report
Click the Publish Report button
to save the report as a .PDF file. Enter the email address and add notes if desired.
Useful reports
Billing
- WIP reports - display WIP at the time the report is run. This means the report will look different every time you run it. To save the WIP figure on a particular date, run the report and save it.
- Concrete billing summary - detailed reports of all concrete billing for use on large projects, when a summary invoice is created with items "rolled up".
- Equipment reports - display calibration imformation.







