A measurement is defensible when it can be shown with which instrument, with which setting up and at which point it was taken. The instruments can build this chain by themselves, if they are set up to do so.
- ✓ Setup files that can be recalled, to repeat the same configuration
- ✓ Grid files that tie every reading to its own point
- ✓ Waveform storage for later review
- ✓ NIST-traceable calibration certificate
When an inspection is challenged, the discussion almost never concerns the figure itself: it concerns how the figure was obtained. With which instrument, with which parameters, at which point, with which valid setting up. If that information was not recorded at the time of the measurement, reconstructing it afterwards is impossible.
The first tool of traceability is the setup file. Saving the measurement configuration and recalling it at every campaign removes the most insidious variable, that is the operator setting the parameters from memory. The same setup used across all campaigns makes the values comparable with each other.
Need help choosing the right product?
The second is the grid file. Every reading is written into the cell corresponding to the point laid down by the inspection plan, with no manual transcription: it is the link between the figure and the position, and it is what lets the client find the same point again at the next campaign.
What makes a measurement defensible
| Element | How it is obtained |
|---|---|
| Measurement configuration | Setup file saved on the instrument and recalled at every campaign |
| Identification of the point | Grid file with cells matching the inspection plan |
| Verification of the reading | A-Scan waveform stored together with the value |
| Validity of the instrument | A valid NIST-traceable calibration certificate |
| Comparison between campaigns | Historical archive kept in DakMaster™ |
From the field to the archive
Transferring the readings from the instrument to the computer closes the chain: from that moment the data is in an archive, no longer on a notepad. It is the step where most information is lost when it is done by hand, and also the easiest one to automate.
On the instrument side, periodic calibration completes the picture. The terms and times of the service, with a NIST-traceable certificate, are described on the Calibration and adjustment page.
Recommended instruments
| Instrument | Contribution to traceability |
|---|---|
| Dakota MX1-DL | Large grid files, 64 user setups and a 4 GB data logger |
| Dakota MX2-DL | Waveform storage for reviewing the readings |
| DakMaster™ | Historical archive and comparison between successive campaigns |
| DakView 4 | Data transfer and management of the setup files |
Frequently asked questions
The identification of the point, the measurement configuration used, the date and the reference of the instrument’s calibration. It is these elements that make the reading verifiable long afterwards.
It allows a doubtful reading to be reviewed afterwards, checking how the echo looked at the time of the measurement, without having to go back to the point.
Yes: the calibration of Dakota NDT instruments is issued with a NIST-traceable certificate. The terms of the service are described on the dedicated page.
Back to Inspection Services and NDT Laboratories, or write to us from the Contact page: we will look together at how to set up setup files and grid files around your procedures.
Further information and contacts
Systems division and sensor integration partner : www.roder.it
More information about RODER SRL : about us
Contact for general information : info@roder.it
Contact for information about these products : info@roder.it
The information contained on this web page is provided for information purposes only. Although it has been compiled with the utmost care, it does not constitute a contractual offer or a binding commitment to supply. It may contain transcription, translation or typographical errors. For precise and up-to-date information, please contact our company directly.
Some images on this website have been intentionally generated using Artificial Intelligence (AI). This is because, for many applications and projects, it is not possible to disclose photographs of the installation or of the actual system due to confidentiality agreements, confidentiality clauses and non-disclosure agreements (NDAs).