Tank-Floor MFL Scanner Buying Guide: Maps and Follow-Up
A tank-floor scanner purchase includes the ability to build an understandable inspection record. Evaluate how the package connects scans to plates, distinguishes missing coverage and preserves the relationship between screening data, follow-up results and issued reports.
For: U.S. NDT equipment coordinators, quality staff and inspection business owners
Define the tank-floor record the customer needs
Start with the required deliverable, not a daily scanning-rate claim. Ask the technical owner what the inspection record must show about the tank floor, its plate layout, acquired data, limitations and follow-up work. The equipment package must support that record through acquisition, analysis and reporting. A scanner that moves efficiently across a demonstration plate may still require substantial manual work to produce the customer's final evidence package. Include that work in the purchase evaluation rather than treating reporting as an incidental accessory.
This guide concerns equipment and data-workflow selection. It does not establish tank inspection intervals, remaining-life calculations, acceptance limits or scanner operating settings. Those decisions belong to the applicable technical requirements and authorized reviewers. Purchasing should identify the scanner's intended role and the other activities required for the final assessment. A complete tank-floor inspection program may involve more than the scanner and its map. The quote should make those boundaries visible so the customer is promised the actual supported deliverable.
Separate the physical scanner from the software package
Ask for an itemized configuration covering scanner, acquisition device, analysis software, reporting software, licenses, accessories and service evidence. Identify which functions operate on the field device and which require a separate workstation. Eddyfi's FloormapX manual distinguishes acquisition and desktop analysis/reporting software in a documented system configuration. The cited manual is dated July 2022; use it as an example of package structure, and obtain current configuration details for the actual offer.
Do not treat every feature shown in the manufacturer's software family as included in the quote. Ask the supplier to demonstrate the required functions using the proposed license and hardware. If a customer viewer, extra review seat or report module is separate, record its cost. A complete price comparison should include the equipment and software needed to create, review and deliver the required record. Otherwise the lowest initial bid may omit the functions that make the acquired data useful to the customer.
Make plate identity the foundation of the demonstration
A tank-floor map needs a reliable relationship to the actual plate layout. Ask how the software creates or imports the layout and how individual plate identifiers are maintained. Have the technical owner define the required drawing reference, orientation and location convention. Procurement should test whether users can preserve those relationships through acquisition and reporting. A neat diagram with incorrect plate identity can misdirect follow-up work even if the individual scan files are readable and internally consistent.
Use a fictional demonstration layout containing two similarly shaped plates, a patch feature and one deliberately revised plate identifier. Ask a second reviewer to identify the corresponding records without assistance from the person who created the map. Record whether the software preserves the needed context and how corrections are made. Do not assume that a filename or scan order can repair an ambiguous layout. The final report should allow the intended reader to connect the evidence to the physical location using the approved reference system.
Review data placement and coordinate meaning
Ask the supplier to explain how a scan is associated with a plate and how its position is represented. The buyer does not need to set technical acquisition parameters, but does need to know whether the resulting record supports the required location precision and review workflow. Have the technical owner assess the relevant evidence and limitations. If manual placement or alignment is part of the process, demonstrate it explicitly and retain the resulting assumptions in the evaluation record.
Test what happens when a scan is assigned to the wrong fictional plate or placed with an incorrect orientation. Ask how the supported correction preserves the source record and updates the analysis. This is a controlled software demonstration using nonproduction data. It should reveal whether a later reviewer can distinguish original acquisition from subsequent administrative placement. A map that permits convenient editing may need a defined review process to ensure corrections remain explainable. Include that process in the purchasing and handover plan.
Distinguish scanned, evaluated and unexamined areas
Define the coverage categories the final record must communicate. Collected data, data accepted for evaluation, areas requiring another approach and areas not examined should not be represented by the same unexplained blank space. Ask the supplier to show how the proposed workflow records those distinctions. The technical owner determines the applicable categories and review criteria. Procurement ensures the software or supplementary record can express them clearly and that the report recipient can understand them without interpreting the operator's memory.
Build a sample case with one intentional coverage gap and one acquired region with no reportable finding under the demonstration's defined assumptions. Ask a reviewer to tell them apart from the exported report. If the report cannot do so without a manual annotation, include that annotation step in the trial. A manual process can be acceptable when controlled and complete. The purchasing concern is whether the limitation remains visible, not whether every function is automated or represented by a particular color.
Evaluate claims about surface discrimination within their scope
Some tank-floor systems combine several data channels or technologies and offer information intended to help distinguish different indication characteristics. Ask the supplier to identify what the specific configuration provides, what the displayed quantities mean and which limitations apply. Do not convert a marketing description into a universal claim that every indication is classified correctly or that complementary examination is unnecessary. The technical reviewer should evaluate the evidence for the intended material, coating and condition range.
Eddyfi's paperless reporting application note describes combining MFL and its STARS information with reporting and follow-up records. That example supports asking about the relationship among acquired channels, interpreted indications and subsequent evidence. It does not establish performance for your tank population. Request a representative demonstration and a written scope statement for the actual package. Keep unsupported applications open or excluded rather than allowing the availability of a sophisticated display to imply an unrestricted inspection capability.
Connect follow-up results to the original indication
Ask how the workflow identifies a reported indication and links any subsequent examination to it. The record should allow an authorized reviewer to see the originating scan reference, physical location, follow-up evidence and disposition required by the process. A handwritten follow-up value entered without its location or source can become difficult to assess later. Purchasing should determine whether the proposed software supports the link directly or whether an additional controlled worksheet or document system is needed.
Create a fictional demonstration indication, associate a separate follow-up record and then review the final report. Confirm that the follow-up does not simply overwrite the original screening context. The appropriate technical owner decides how the combined evidence is interpreted and what is issued. The administrative requirement is that the relationship remains understandable. If a follow-up item is pending, the report should not make it indistinguishable from a completed review. The quotation should include whatever software or manual work is necessary to represent that state.
Test report regeneration after a meaningful change
Reports are often generated before every review comment or follow-up result is complete. Ask the supplier to demonstrate what happens when the underlying project changes after a report is created. The FloormapX manual describes report-generation and update behavior, illustrating why a saved report and a current project are separate artifacts. Do not assume every software package automatically refreshes an already exported document. Test the actual product version and define how issued revisions are controlled within the organization's reporting process.
Use a sample project with a corrected plate label or added follow-up reference. Regenerate the report and compare it with the earlier version. Check the changed content, revision identification and source-project reference required by your process. Preserve the original issued output when the record rules call for it. A report that looks current but was generated before the final change can be misleading. The buying decision should account for the review steps needed to ensure that the final deliverable reflects the approved project state.
Preserve native data alongside presentation outputs
Ask which files are needed to reopen the inspection project and whether the export includes all linked data. A PDF map communicates results but may not preserve the acquisition or analysis detail needed for later technical review. Determine the required native records and compatible software access before buying. Have the supplier demonstrate the complete package on a second workstation rather than opening it only on the acquisition device where hidden dependencies may still be available.
Record the relationship between raw acquisition, working analysis and issued report in a simple manifest. The terminology should match the actual software rather than implying that every file type contains identical information. If the project references external images, drawings or follow-up documents, test that those references survive handover. A folder that opens correctly on the creator's computer may fail elsewhere because a linked item was never included. The purchase acceptance trial should expose those dependencies while the workflow can still be adjusted.
Examine imports, replacements and repeated scans
A tank project may contain data acquired over several sessions or by more than one crew. Ask how the software handles importing additional plates, replacing a scan and identifying duplicate content. Do not assume the product will automatically merge every dataset in the way your process expects. Demonstrate a small fictional case with an existing plate, an additional plate and a repeated scan. Record the actual outcome and the controls needed to preserve the intended source selection.
Have the technical owner decide how repeated or superseded acquisition is retained and reviewed. Procurement should confirm that the software can support that decision, either directly or through a controlled external record. An apparently tidy final map can conceal ambiguity if nobody can tell which scan was used after a replacement. Keep the original and revised file references available where required. The important purchasing outcome is a reproducible and reviewable dataset, not simply the absence of duplicate plate names in the interface.
Evaluate realistic field and office workloads separately
A representative trial should include field data handling and office analysis, since those tasks can stress different parts of the package. Ask users to evaluate project setup, record transfer, map review, follow-up entry and report creation with a realistic demonstration dataset. Record observed time and difficulties as local trial results, not industry-wide production guarantees. The size and condition of the actual work can differ substantially from the supplier's example, so preserve the assumptions behind any productivity estimate.
Check the intended workstation and storage arrangement using the same files and required functions. Confirm whether the quoted license allows the necessary collaboration and whether the field device remains available while office work continues. If one license or device must move between acquisition and reporting roles, include that scheduling constraint in the comparison. A package with strong individual features may still create a bottleneck when the organization needs two people to perform different stages at the same time.
Work through a fictional report-completeness decision
A hypothetical service company compares two tank-floor packages. Both produce attractive color maps. In the trial, one package easily records the customer's required plate identifiers but needs a separate follow-up worksheet. The other integrates follow-up information but requires additional manual work to preserve the customer's layout convention. The company does not declare either universally superior. It compares the actual required steps, evidence completeness, review burden and included licenses for its intended jobs.
The final decision records the selected package and the controlled supplementary process that closes its gaps. The supplier's sample report remains in the file, but the purchase approval relies on the company's own demonstrated deliverable. This fictional example shows why reporting needs can change the value of a scanner quote without changing the underlying inspection technology. A transparent manual step may be preferable to an assumed automatic function that does not actually satisfy the customer's required record.
Maintain the supported configuration and its evidence
Record the scanner identity, acquisition device, relevant accessories, software versions and approved application scope at handover. Ask the manufacturer what service and review are required after significant repairs or component changes. Preserve the resulting evidence against the affected configuration. Do not assume that a scanner's calibration due date alone establishes suitability for every tank-floor condition or validates the layout and interpretation produced by its software. Those remain separate technical and record-quality responsibilities.
NDT Connect's equipment tracker supports basic asset fields, status, an entered due date and notes. It does not create tank-floor maps, analyze MFL signals or manage indication follow-up. Keep those functions in the selected inspection systems and use an evidence reference in the asset notes where appropriate. A completed purchase should leave the organization able to identify the scanner package, reproduce the required report path and explain how coverage and follow-up are represented. That makes the equipment investment reviewable beyond the first impressive map.
Confirm which records a future customer can receive
Before contracting for customer work, obtain a sample of the exact deliverable package and verify the recipient's reader requirements. A customer who only receives a PDF may not need an analysis license, while a customer requesting the native project may need a compatible viewer or additional entitlement. State what is included in your offer and what access the recipient must provide. Do not promise unrestricted reanalysis based on a file export that has only been tested on the supplier's fully licensed workstation.
Retain that agreed deliverable definition with the purchasing decision. If a later customer requests a different native format, additional metadata or another reporting structure, review it as a new requirement. The scanner may still be suitable, but the existing software package and handover process need evidence for the expanded promise.
Frequently Asked Questions
Does a tank-floor color map prove complete coverage?
No. The record must distinguish the coverage actually evaluated, gaps and limitations under the applicable inspection process.
Should follow-up values replace the original scanner context?
Preserve a clear relationship between the originating indication and the follow-up evidence. The authorized review process determines the issued interpretation.
What should be demonstrated before purchasing the reporting package?
Use representative nonproduction data to test plate identity, coverage categories, follow-up links, report revisions and complete native-file handover.
References & Standards Cited
- Eddyfi: FloormapX user manual, July 2022 View source ↗
- Eddyfi: paperless tank-floor inspection reporting 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.