Lifecycle of a Density Test

Owned by Tracie Karsjens (Unlicensed)
Last updated: Dec 08, 2015 by Joel Smolarek
2 min read

When working in MetaField® in the density area, a user will create a test that has a status associated with it. The test will work through a process from the initial logging, until the test appears on a report. The diagram below describes this process and how it works in the various areas of MetaField. 

Field

A density test is created in the Field module by a field technician. There are two basic scenarios that can occur:

  • If the field tech knows the correct proctor for the test and selects it, they will save the test in status analyzed.
  • If the proctor is not available or, the field tech does not know the correct proctor, they can choose Pending Proctor as the proctor, and this will save the test as pending.

There are two exceptions to the above:

  • A One-Point Density test can never be set to pending. It will always be saved as analyzed in the field.
  • For a Bituminous Nuclear Gauge test, it is the presence of either the Supplied Max Density Value or Lab Max Density Value that determines if it is pending, rather than a proctor.

While a test is in pending status, it can be edited in the Field module and a proctor (or Max Density) can be entered to move it to analyzed. Once it is in analyzed status, the test can still be edited, but the test can not be edited in the Field module once it is in a status of complete..

A field technician may also create a Density Testing Field Report containing one or many test records.


Quality Control

Since project managers use QC to view and manage their project work, a test is viewable in QC as soon as it is saved for the first time. At that initial save, the project manager will see the test as pending or analyzed. The proctor (or max density) for a pending test can be edited in QC as well as Field to make it analyzed.

At any time, a project manager may manually mark a test as pending or review. Both are intended as ways for a project manager to flag a test for some additional attention. In the case where a project manager manually marks a test as pending, it does not necessarily mean that the proctor (or max density) is missing. 

In order to put the test on a report, the project manager must manually change the status to complete to indicate it has been reviewed. This will also remove it from visibility in the project manager’s dashboard.


Dashboard

The project manager’s dashboard will show them the number of tests in pending, analyzed and review status in QC, as well as any failing results for which a passing retest has not been completed. In addition, the not reported feature count makes sure that all test results are reported to the client.