Skip to content

Tube Inspection Equipment RFQ: ECT, RFT, Arrays and IRIS

A multi-technology tube-inspection platform does not necessarily arrive with every technology shown in its brochure. Build the quotation around your actual tube population, approved methods, installed options and complete probe packages.

For: U.S. NDT equipment coordinators, quality staff and inspection business owners

Turn the exchanger list into an equipment requirement

Begin with the assets the organization expects to inspect and the decisions those examinations must support. Ask the technical owner to identify the tube materials, relevant dimensions, geometry, expected damage concerns, access conditions and governing requirements needed for method selection. Purchasing should preserve that information in an application matrix. A request for a tube tester alone gives a supplier too little basis to define a complete package. It also encourages comparisons between offers that may cover different portions of the intended work.

Keep the technical selection with the authorized person. This guide does not prescribe which method to use on a particular exchanger, probe dimensions, pull speeds, frequencies or interpretation criteria. It explains how to translate an approved scope into a verifiable quotation. Each application row should identify the selected or proposed method, required output, supporting evidence and unresolved questions. If the method is not yet selected, record that as a technical decision still required rather than letting the first available instrument determine the inspection plan.

Distinguish the platform family from the offered configuration

Eddyfi's Ectane 3 product page describes a platform offered in several configurations with multiple technology options. Its user guide explains configuration identifiers associated with capabilities. The purchasing lesson is to obtain the exact offered model and installed options. A list of technologies supported somewhere in the product family does not establish that every individual unit, rental or used instrument has them enabled or includes the required hardware interfaces.

Ask the supplier to map the quoted configuration to each required application. Use separate columns for installed capability, necessary probe, software function and supporting accessory. If an option is available only through a later upgrade, identify its cost, service requirements and lead time. Do not score a future upgrade as a present capability. A deliberately limited configuration can be a sensible purchase when its role is clear; the problem is buying one configuration while assuming the entire family's capability list arrives in the case.

Keep IRIS distinct from electromagnetic tube methods

A single platform can support methods that rely on different physical principles. The Ectane product documentation lists IRIS as ultrasonic testing alongside several electromagnetic technologies. Do not let a broad phrase such as electromagnetic tube tester obscure that distinction. Ask the technical owner which methods are included in the approved work and what supporting equipment each requires. The buyer should be able to explain the complete package for each method without implying that selecting another software label transforms an incomplete configuration into a working inspection system.

Record method names precisely in the application matrix and quotation. ECT, RFT, array variants and IRIS should not be treated as interchangeable abbreviations for the same deliverable. The supplier should identify what each proposed arrangement provides and what limitations apply. If the business case includes complementary methods, show how the work and records will be coordinated. This is a scope question, not a claim that every exchanger needs several methods or that one technology universally replaces another.

Specify probes as identifiable items

A probe family name is not a complete procurement description. Ask for the exact part number, relevant configuration, cable arrangement, connector and evidence required by the approved application. Eddyfi's tubing probe catalog page separates numerous probe families and accessories, illustrating the range of choices within a single supplier's offering. Use the technical owner's approved selection or the supplier's documented recommendation as the basis for the order, rather than inferring suitability from a nominal tube diameter alone.

Preserve the relationship between the probe and the application row it supports. If a supplier proposes an alternative to an existing probe, request a documented comparison and route the differences for technical review. Do not reduce a custom or specialized probe to a generic internal nickname that loses its important configuration. At receipt, the coordinator should be able to match the supplied item to the quoted part and supporting record. An unidentified spare in the case is not yet evidence of a supported replacement capability.

Include the supporting package for each method

Ask the supplier to list the items required to perform the proposed workflow under the approved procedure. Depending on the selected arrangement, this may involve different supporting hardware, handling accessories, reference artifacts or services. Identify which are included, which the customer supplies and which remain to be specified. Do not copy a generic kit list from another technology or assume that every accessory used during a demonstration is bundled with the instrument. The final offer should describe a complete supported arrangement for each agreed application.

Where the supplier identifies a dependency such as a particular ancillary supply or handling system, have the relevant technical and site owners confirm the arrangement. Purchasing should record who provides it and whether its cost is included. This guide does not specify flow, pressure, cleaning conditions or other operating requirements. Its purpose is to prevent omitted dependencies from appearing only when the crew arrives. A package comparison is meaningful only when both bidders have priced the same required scope and disclosed their assumptions.

Review probe handling and automation as a separate option

A manual probe workflow and a mechanized pusher-puller can create different equipment, access and data-handling requirements. Ask what the proposed handling system actually controls and how it integrates with the instrument and software. The Ectane product page identifies integration with a compatible pusher-puller, but that does not mean every quote includes the mechanism or every existing system is compatible. Request the exact configuration and interface requirements for the package you intend to buy.

Have the authorized users evaluate a representative, approved demonstration. Record access needs, cable management, equipment placement and the information retained about each acquisition. If automation is proposed to improve throughput, include setup, record association and recovery from an interrupted sequence in the trial. Do not equate a nominal mechanical speed with guaranteed completed tubes per shift. The actual workflow includes preparation, identification, acquisition quality review and reporting, and those steps should be reflected in the local productivity estimate.

Specify reference artifacts and supporting evidence

Ask the technical owner to define the reference artifacts and evidence needed for the selected methods and tube populations. Purchasing should identify the required artifact, drawing or specification and the documentation supplied. A generic reference tube included with one package may not satisfy every application in the matrix. Do not assume that a certificate for the electronic instrument establishes the suitability of all probes or reference artifacts. Preserve each item's identity and its relationship to the approved configuration.

Resolve custom artifact requirements before committing to the equipment delivery schedule. If the supplier needs customer material, drawings or technical approval to manufacture an artifact, record those dependencies and responsible parties. The business case should not count an application as immediately available when its essential reference arrangement is still undefined. At handover, maintain an index linking instrument, installed options, probe and reference evidence so a coordinator can assemble the intended package without reconstructing the technical selection from memory.

Test tube identity before evaluating report appearance

Tube inspection data need a reliable relationship to the physical tube and the relevant exchanger map. Ask how the proposed workflow assigns identifiers and prevents ambiguity when operators move between rows, sections or assets. The required identity convention comes from the approved project process. Purchasing should test that the instrument and software can preserve it through acquisition, transfer and analysis. A polished report with the wrong tube association is not a successful demonstration of the required deliverable.

Use a small fictional map with similar identifiers, one repeated acquisition and one deliberately corrected entry. Ask an independent reviewer to identify the corresponding files and final status. Record how the software handles the correction and whether the original record remains available as required. If tube-map design is a separate software function, include that product and license in the quote. Do not assume that an acquisition program's file list provides the same mapping and reporting functions as a dedicated tube-management application.

Verify the installed analysis capabilities

Ask the supplier to show which acquisition, analysis and reporting functions are licensed for each selected method. A product family may support many techniques while a particular software seat has a narrower scope. Confirm whether the required analyst can work independently of the acquisition workstation and whether review of historical files requires an additional entitlement. Include those details in the comparison, especially when multiple crews will collect data while office staff analyze results at the same time.

Request representative files for each required method and open them using the proposed analysis configuration. Check that the required data views and context are available. Do not assume that successful opening of one ECT file demonstrates support for an IRIS or array dataset. Record the method, file source and software version for each trial. If a feature is optional or requires a future release, preserve that limitation in the acceptance record instead of relying on a supplier-prepared report generated with a different software package.

Demonstrate transfer, interruption and recovery

A realistic field trial should include the normal data-transfer route and an agreed nonproduction interruption scenario. Ask how users know which tube records are complete, which remain pending and which require review after recovery. The technical process determines what can be accepted; the software should make the state understandable. A file existing in a folder does not necessarily establish that the intended acquisition and review sequence was completed. The buyer needs evidence of the workflow, not only evidence that the device can save something.

Transfer the demonstration package to another workstation and verify identifiers, method context and the required files. If the workflow includes a shared drive or offline collection, test that arrangement specifically. Avoid deleting source data as part of a sales demonstration merely to prove an export exists. Preserve the originals until the required receipt and review checks are complete under your process. The purchasing trial should show how the organization will retain a recoverable record without creating competing unexplained versions of the same tube's data.

Work through a fictional upgrade assumption

A hypothetical company buys a used instrument described as a multi-technology tube platform. Its planned work includes two methods, but the seller's photos show only the family name. The buyer requests the exact configuration, installed options and software entitlements. The manufacturer or authorized supplier confirms that one intended capability requires additional work. The buyer then compares the complete upgrade package with another offer rather than assuming that a suitable connector or a menu item proves the required capability is present.

The final purchase memo lists the delivered scope and the applications that remain unavailable until the upgrade is completed and reviewed. If the organization chooses to rent the missing capability temporarily, that arrangement has its own identity, evidence and software requirements. This fictional example does not imply that used instruments are unsuitable or that a particular product hides its options. It shows why a broad family description needs a configuration-specific verification before it becomes the basis of a customer commitment.

Plan spares around the application matrix

Use the intended workload to identify which probe or accessory failure would interrupt which applications. A spare for one tube family may not support another, and a replacement instrument may lack an installed option the crew needs. Ask the supplier to confirm compatible alternatives and current service arrangements. Record lead times as dated commercial information, not permanent facts. The coordinator should be able to distinguish a physically available spare from a complete supported replacement package for the scheduled work.

Maintain an association record for probes that move between instruments or kits. Preserve original identifiers, condition observations and relevant service evidence. If a damaged probe is replaced, do not overwrite its history with the new part's identity. The technical reviewer determines any necessary review before the new arrangement is used. Purchasing and stores can support that decision by keeping the actual configuration visible. This is especially important where several similar probes are carried for different applications and their differences are not obvious from a quick glance.

Close the quote with a complete capability matrix

The final comparison should show each required application, the approved method, instrument configuration, probe, supporting equipment, reference artifacts, software and evidence. Mark unresolved items with an owner and a defined next action. A capability is ready for commercial acceptance when the required package and documentation have the appropriate disposition, not merely when the instrument is delivered. Retain excluded applications so later schedulers do not interpret an incomplete row as an overlooked opportunity the equipment can automatically handle.

NDT Connect's free equipment tracker can hold instrument and accessory asset details, entered calibration due dates, status and notes. It does not detect installed options, manage tube maps or analyze inspection datasets. Keep the detailed capability matrix and technical records in the selected document and inspection systems. A concise note can point to those records where appropriate. The result of the purchase should be a clearly bounded, identifiable package that supports the intended work and a documented route for future expansion, rather than a case whose family name promises more than its contents can deliver.

Frequently Asked Questions

Does a multi-technology platform include every advertised method?

Not necessarily. Confirm the exact model, installed hardware options, software licenses, probes and supporting equipment included in the offer.

Is IRIS an eddy-current method?

No. IRIS is an ultrasonic technique, even when supported by an instrument family that also includes electromagnetic tube-inspection methods.

Can one successful sample-file test establish all analysis capabilities?

No. Demonstrate the required files and functions for each intended method using the actual quoted software configuration.

References & Standards Cited

  1. Eddyfi: Ectane 3 instrument configuration and technologies View source ↗
  2. Eddyfi: tubing probe families and accessories View source ↗
  3. Eddyfi: Ectane 3 user guide and configuration identifiers 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.