Thickness Gauge Data Logger: A Buyer’s Workflow Checklist
A thickness gauge can save a number without preserving everything your inspection record needs. Before buying a data logger, demonstrate how your own location names, missing points, repeated readings and exports survive the complete workflow.
For: U.S. NDT equipment coordinators, quality staff and inspection business owners
Start with the record your customer actually needs
Write down the record that must exist when the job is complete. It may be a table of approved thickness readings tied to named locations, a set of stored waveforms for review, a structured survey file, or a combination. The responsible technical reviewer determines which evidence is appropriate to the inspection. The equipment buyer then asks whether the proposed gauge and associated software can create, retain and transfer that evidence without an improvised retyping step that nobody has evaluated.
Separate measurement suitability from record handling. A gauge with convenient logging may still be unsuitable for the material, geometry, surface condition or required examination. Conversely, a technically suitable gauge may create a difficult administrative workflow. Keep both decisions visible in the purchase review. This guide addresses record handling and procurement evidence; it does not select a transducer, prescribe a measurement technique or establish acceptance criteria for a component.
Create a short use statement before reading feature tables. For example, a fictional inspection company needs to repeat an owner's existing location list, preserve the original identifiers, record inaccessible points explicitly and deliver a file that the owner's software can ingest. That statement makes file structure and exception handling central to the demonstration. The largest advertised memory or most elaborate display is not automatically the best answer to that particular need.
Compare display-only, onboard logging and connected workflows
A display-only workflow relies on another record, such as a controlled form or application, to associate each observation with its location. Onboard logging places some of that association inside the instrument. A connected workflow transfers information to another device or system during or after collection. None of these descriptions alone establishes record quality. Ask where the authoritative record is created, who checks it, and what happens if the secondary device or connection is unavailable.
A named product can illustrate the distinctions without serving as a universal recommendation. Evident's 39DL PLUS product page describes onboard storage of readings and waveforms, several file structures and multiple transfer options. These are manufacturer stated capabilities for that product. Use the published data logger description to formulate questions, then confirm the exact configuration, software and regional availability offered in your quotation.
Compare the complete workflow rather than the gauge in isolation. A wireless feature may require an application, supported operating system, account or optional software. A wired workflow may require a particular cable, driver or interface program. Ask the supplier to list these dependencies and demonstrate them on a receiving computer representative of your own environment. The fact that a port exists does not establish that the desired records reach your reporting system intact.
Bring a realistic location list to the demonstration
Prepare a small, fictional location list that resembles your actual naming conventions without exposing a customer's confidential information. Include long identifiers, similar identifiers, leading zeros and any punctuation your system uses. Add a few locations belonging to different components so the demonstration tests the hierarchy as well as the individual point name. Agree beforehand which fields must survive exactly and which may be represented through an approved mapping.
Ask the demonstrator to load or create the list using the proposed workflow, then export it and compare the identifiers. Watch for truncation, automatic renaming, loss of leading zeros or a spreadsheet interpreting identifiers as numbers. These are test questions, not claims that any particular instrument has those faults. A successful demonstration should show the receiving record and the source relationship, rather than stopping when the name looks correct on the gauge screen.
If an identifier must be shortened, retain a controlled crosswalk and evaluate the added work. A locally convenient label such as A12 may become ambiguous when several assets are combined. The buyer should understand who creates and checks the crosswalk, how it is retained, and whether the customer accepts it. Do not silently substitute a short instrument identifier for the owner's permanent location reference and leave the relationship to someone's memory.
Test the file structure against the way work is organized
A sequential list can suit one workflow while a grid better represents another. The useful question is whether the selected structure preserves your intended relationships and supports the order in which authorized work will occur. Ask the technical team to provide the approved location structure; the purchasing demonstration should use that structure without inventing a survey pattern. File organization does not establish that the physical inspection coverage is adequate.
The 39DL PLUS manual documents different data file structures and their management. Its examples are product specific, so use the relevant manual revision to understand the proposed instrument rather than applying its menu behavior to another gauge. A useful acceptance task is to reopen a partly completed demonstration file and show how the operator identifies the next authorized record without confusing the previous reading with a new one. Consult the manufacturer manual for actual operation.
Include an ordinary interruption in the administrative demonstration. The operator may need to leave the file, review another component and return later. Observe whether the active file and location are clear and whether the receiving export preserves the intended association. Do not use an unsafe field interruption to test this behavior. A controlled demonstration with sample data is enough to reveal whether the record workflow requires additional checks or training.
Decide what missing points and repeated observations mean
Agree the meaning of an unfilled location before choosing the logger. It could mean not yet examined, inaccessible, outside scope, a failed transfer or another condition defined by the inspection procedure. A blank alone may not distinguish those cases. Ask how the proposed workflow records the appropriate reason and how that reason reaches the final record. If the gauge cannot hold the needed context, identify the separate controlled record that will carry it.
Test a repeated observation at a fictional location. Determine whether the workflow replaces a value, retains multiple observations, creates a new identifier or asks for a decision. The buyer needs to understand this behavior before it affects a real record. The responsible technical person determines which reading or set of readings belongs in the issued result; the purchasing exercise should establish what evidence remains available to support that decision.
Avoid designing a workflow that equates every stored number with an approved result. A logger may contain demonstration values, incomplete work or readings awaiting review. Make the review boundary explicit in the reporting process. If the connected application offers a status or approval mechanism, demonstrate it and verify its limits. If it does not, document how the organization distinguishes collected data from the reviewed record without inventing a feature that the software lacks.
Evaluate waveform retention and memory in context
Ask whether the intended workflow requires a stored waveform, a thickness value, configuration information or another record for each relevant observation. The answer comes from the technical and contractual requirements. Then demonstrate which objects the quoted system actually saves and exports together. A screenshot of a waveform on the display does not establish that the waveform is retained in the downloadable record or linked to the same location after transfer.
Memory comparisons should use the objects you intend to retain. A headline capacity for scalar readings cannot be assumed to equal capacity when larger records are saved. Rather than calculating a universal job size from brochure numbers, ask the supplier to demonstrate a representative file and explain storage limits, overflow behavior and the process for managing completed files. Record the applicable software version because behavior and supported objects may differ between configurations.
Include retrieval in the test. Select an earlier demonstration location and ask the reviewer to find its retained evidence after the file has been exported and reopened. The result should be understandable without relying on the original demonstrator's memory. If waveform retention is outside the purchased capability, say so in the decision record. A buyer can accept a limited workflow when it satisfies the actual need, but should not describe that workflow as retaining evidence it does not store.
Verify transfer with the actual receiving application
Use a controlled receiving environment that resembles the organization's normal reporting setup. Import the sample, compare location names and units, and verify the relationship between readings, notes and supporting objects. Check whether the transfer creates a new file, updates an existing one or appends records. These choices affect how duplicate transfers are recognized. Record the behavior rather than relying on a generic statement that the instrument exports to a spreadsheet.
Demonstrate a second transfer of the same sample. The intended result may be a rejected duplicate, an explicit replacement or an additional version, depending on the chosen system. What matters is that the behavior is known and manageable. A duplicated row can distort later summaries even when every individual number was transferred accurately. The receiving application's owner should participate because a correct gauge export can still be mishandled by downstream import settings.
Compare a wired option with the proposed connected option if continuity matters to the business. Ask what happens when the network, mobile device or account is unavailable, and whether any fallback retains the required information. Do not assume that a manufacturer advertised offline capability applies to every linked application. Test the specific fallback before making it part of your operational plan and describe any reduced functionality openly.
Include corrections, deletion and access in the purchase review
A record workflow needs an understandable way to handle mistakes. Ask how a user identifies the wrong active location, corrects an administrative label or records that an observation was superseded. Distinguish a field that can be edited from a result that must be reviewed under the organization's procedure. The equipment buyer should capture the system behavior; the organization decides who is authorized to make each kind of change.
Review available protections without overstating them. A feature that prevents accidental deletion does not necessarily provide a full audit trail, individual user attribution or approved record retention. Ask for a demonstration of the exact protection being claimed. If the instrument allows shared access, explain how the surrounding process will identify responsible users and preserve issued records. Avoid describing a password or file lock as proof that the complete workflow meets a particular quality standard.
Use disposable demonstration files for deletion and recovery checks. Keep the accepted sample package unchanged so the evidence remains available. Record whether recovery depends on a prior export, backup or vendor support, and determine who owns that task after purchase. The objective is to discover the real recovery boundary early, not to promise that deleted records can always be restored.
Turn the demonstration into a balanced purchase decision
Create an evaluation sheet with requirements, evidence, unresolved limits and the person accepting each decision. Separate essential requirements from conveniences. Exact location identity may be essential for an existing owner database, while a preferred display arrangement may be optional. This prevents a long feature list from hiding a failure on the one capability that determines whether the purchased workflow can be used.
Include the cost of supporting the workflow. Count required applications, cables, training, configuration work, license terms and any ongoing mapping or manual review. Do not invent a universal cost saving from digital logging. A small team with a simple controlled record may have different needs from a contractor transferring large structured surveys into an owner's system. The purchase decision should explain the specific work reduced or added in your own context.
Before accepting delivery, repeat the essential checks on the delivered configuration or obtain appropriate evidence that the demonstrated configuration is the one supplied. Record model, serial number, relevant options and software version. If a substitution changes the logger or transfer capability, route it back to the responsible reviewer. A delivery receipt confirms that a box arrived; it does not by itself close the data workflow acceptance questions.
Use a hypothetical comparison to expose the deciding issue
Imagine a fictional contractor choosing between two technically suitable gauges for a recurring location list. Gauge A has the larger advertised memory, while Gauge B's demonstration preserves the owner's identifiers and exports the required exception notes. The buyer should not select either from that description alone. It should first establish whether Gauge A can meet the same record requirements and whether Gauge B retains the required evidence for the expected job size.
Suppose the controlled test shows that one proposed application removes leading zeros from location identifiers. The team records a failed mapping check, identifies the receiving import setting responsible, and repeats the affected case after correction. This hypothetical result illustrates why testing the complete chain matters. It is not a claim that a named product has this defect, and it says nothing about the accuracy of a thickness measurement.
Keep the final acceptance sheet with the equipment purchase and training records. NDT Connect's free equipment tracker can hold the gauge's name, type, serial number, manufacturer, model, due date, status and a note referring to that evidence. It does not collect thickness readings, upload waveforms or import logger files. Use the tracker for equipment administration and the selected inspection record system for the measurement evidence that the purchasing exercise has evaluated.
Frequently Asked Questions
Is a larger memory always better for a thickness survey?
No. Compare capacity for the actual objects you need to retain and test location identity, notes, retrieval and transfer. A large reading count does not establish a complete record workflow.
Does a B-scan display prove distance is recorded?
No. The manufacturer manual distinguishes time based and encoded B-scan capabilities. Verify the exact option and evidence required; do not infer distance recording from the display name alone.
Can NDT Connect import gauge readings?
No. The equipment tracker is an equipment administration tool. Measurement data belongs in the chosen inspection data workflow.
References & Standards Cited
- Evident: 39DL PLUS thickness gauge, data logger and transfer features View source ↗
- Evident: 39DL PLUS User Manual, revision 3, November 2024 View source ↗
Related on NDT Connect
Join NDT Connect — free
The free marketplace for the NDT industry — connect inspectors and the companies that need them.
Free to join · Compare provider qualifications and confirm availability directly · Browse providers
By NDT Connect Editorial · Updated
Source-based editorial guidance. Read our editorial policy and disclosures.