Automated Immersion UT: Purchase and Acceptance Checklist
An automated immersion system combines inspection hardware, motion, fixtures and software. A successful purchase defines how those parts work together for the intended part families and how factory evidence becomes an accepted production record at your site.
For: U.S. NDT equipment coordinators, quality staff and inspection business owners
Write the part-family scope before the machine specification
Begin with the parts and required decisions. Identify the materials, geometry range, relevant regions, required inspection output and expected record. Ask the technical owner to define the inspection requirements and the production team to describe the workflow. A request for a large tank and several motion axes does not by itself establish a useful inspection system. Those are design choices that should serve the agreed part-family scope.
Separate present requirements from possible future applications. Give each proposed family a priority and evidence status. The supplier can then identify what is included in the initial design and what requires additional development. This guide concerns purchasing and acceptance records. It does not prescribe ultrasonic settings, scan coverage, water conditions, machine safety controls or defect acceptance rules. Those belong to the responsible technical, engineering and site processes for the delivered installation.
Distinguish tank capacity from inspectable capacity
Ask the supplier to explain the difference between physical tank dimensions and the usable inspection envelope for the proposed configuration. The fixture, part orientation, probe arrangement and motion requirements can affect what the system can actually examine. A part that fits inside the tank is not necessarily within the demonstrated application scope. The buyer should request a configuration drawing or equivalent evidence for each representative family.
Have the relevant owners review loading, positioning and access requirements through their normal engineering process. Purchasing should record the accepted arrangement and its dependencies. If an optional fixture or motion feature is needed to address the largest part, include it explicitly in the offer. Do not combine the maximum dimensions from separate configurations into one assumed capability. The final scope should describe the supported arrangement, not simply repeat the largest number in the product literature.
Identify the complete inspection configuration
Evident's immersion-system description presents a system built around automated scanning and ultrasonic acquisition. Treat that as a reminder to specify the complete package: mechanics, motion control, probe arrangement, instrumentation, acquisition software, analysis and reporting. Ask the supplier to identify what it provides directly and what depends on third-party equipment or customer-supplied infrastructure.
Create a configuration baseline with component models, relevant revisions and interface responsibilities. Not every item needs an individual asset record, but the organization should be able to reconstruct what was accepted. Include custom fixtures, software modules and part programs where they define the application. A system can be physically complete while lacking a required analysis license or production interface. The baseline prevents those less visible dependencies from disappearing between the demonstration, quotation and delivered installation.
Make fixtures part of the application evidence
For each part family, identify the fixture or supported positioning arrangement used in the trial. Ask who owns its design, documentation and replacement responsibility. A fixture can be essential to the repeatability and location context of the record even when it looks like a minor mechanical accessory. The technical and engineering owners should determine how its suitability will be assessed.
Record the relationship between fixture identity, part program and inspection coordinate system. If a substitute fixture is proposed after design approval, route it through the agreed change process. Do not accept an undocumented workshop modification simply because the part can still be loaded. The acceptance file should show which arrangement supported the trial evidence and what review established that a later configuration remains applicable. This is a record-control requirement, not a design instruction for the fixture itself.
Define the factory acceptance purpose
Evident's automated-inspection overview describes project stages including design reviews, factory acceptance, installation, site acceptance and production startup. These are useful distinct milestones. The factory trial should demonstrate agreed requirements using identified configurations and representative parts or artifacts. State which requirements it will establish and which cannot be closed until the system is installed in the customer's environment.
Assign acceptance owners before the trial. Technical performance, mechanical function, data integration and documentation may require different reviewers. Give each requirement a defined evidence artifact and a disposition field. A supplier demonstration can be productive even when an issue is found, provided the issue and corrective action are recorded. Avoid a single broad passed label that obscures an incomplete application trial or a software function awaiting later installation.
Select representative trial items deliberately
Have the technical owner choose the trial items and document why they represent the intended work. Include the relevant variation that drives system selection. A single simple specimen may prove basic function without demonstrating the difficult part family. Keep the identities and supporting information for each item with the trial record so a future reviewer can understand what the result actually established.
Distinguish known reference information from assumptions about a specimen. If another method supplies a comparison result, preserve its scope and limitations. Define how trial results will be evaluated before collecting them. Purchasing should not invent detection thresholds or substitute convenient artifacts for the technical owner's requirements. The buyer's role is to ensure the agreed items, evidence and review are available at the milestone and that any departure from the plan is documented rather than silently accepted.
Trace part identity from loading to report
Ask how the production part is identified and how that identity remains associated with the acquired dataset. Include any barcode, manual entry, manufacturing-system interface or part-program selection involved in the proposed workflow. A motion sequence can run correctly while the record is assigned to the wrong part. The acceptance plan should therefore include identity handling as its own requirement.
Use fictional identifiers with similar names in a controlled software trial. Have the reviewer follow a selected record from assignment through acquisition, analysis and export. Ask what happens when an identifier is corrected or a job is repeated. The technical and data owners determine the required controls; the trial establishes whether the delivered system supports them. Record manual reconciliation steps honestly. An interface that requires human confirmation may be acceptable, but its role should not be hidden in a claim of complete automation.
Verify the meaning of coordinates in exported data
Define the location information needed by the customer or downstream reviewer. Ask how the system relates machine coordinates, part coordinates and report references. The engineering and technical owners should agree the relevant convention. Purchasing should require a demonstration that the convention survives the intended export and remains understandable outside the acquisition screen.
Select a feature in a fictional trial record and ask a second reviewer to identify its location using the delivered package. Include orientation and origin information as required. If an exported map is mirrored, rotated or stripped of context by a receiving application, record the issue and resolve it through the supported workflow. Do not treat a colorful C-scan as sufficient evidence of usable location information. The purpose of the trial is a record another person can correctly relate to the part.
Evaluate interruptions without unsafe improvisation
Ask the supplier and site engineering owners to define controlled acceptance exercises for relevant interruption scenarios. The objectives may include preserving part identity, identifying incomplete records and understanding the supported recovery process. Do not improvise machine faults or bypass controls to create a dramatic test. The agreed plan should be appropriate to the installation and manufacturer instructions.
Inspect the resulting records. A resumed motion sequence does not automatically mean that the inspection record is complete. The technical owner should be able to distinguish completed, repeated and unavailable portions under the approved workflow. Document any manual review needed before a part returns to the normal process. The purchasing requirement is transparent evidence and a supported recovery procedure, with the responsibilities assigned before production depends on the system.
Measure throughput at the agreed completion point
Define whether the business requirement concerns machine cycle time, inspected parts, reviewed results or released customer packages. Those measures can differ. During a representative trial, record the relevant loading, identification, acquisition, analysis and handover activities. Do not compare one supplier's scan-only figure with another supplier's complete workflow time as though they describe the same service.
Preserve assumptions about part mix, staffing, fixtures and simultaneous analysis. If the trial uses an additional workstation or an expert who is not included in the planned operating model, identify that dependency. The production and technical owners can then decide whether the observed result supports the intended capacity. A realistic business case records the conditions under which performance was demonstrated and the unresolved estimates for other part families, rather than turning the fastest trial cycle into an unconditional promise.
Establish site acceptance as a defined second stage
Installation places the system within the actual facility, data environment and production workflow. Agree what evidence must be repeated or newly established at that stage. The relevant owners determine facility readiness, machine integration and technical checks. Purchasing should coordinate the dependencies and retain the acceptance plan without assuming that a successful factory trial automatically closes every site requirement.
Compare the installed configuration with the factory baseline. Record changes to software, fixtures, workstations or interfaces and obtain the agreed review. If a production-system connection was simulated at the factory, test the real supported interface at the site using approved trial data. Keep unresolved items visible and assigned. The goal is a clear transition from delivered machinery to an accepted application workflow, with evidence that the actual installation supports the requirements used to justify the purchase.
Use the downloadable matrix as an evidence index
The accompanying worksheet provides columns for requirement, part family, deliverable, configuration, factory evidence, site evidence, owner, open issue and disposition. Its sample row is fictional. Replace it with the project's approved requirements. The worksheet is an organizational aid; it does not contain universal technical acceptance criteria and is not an import format for NDT Connect.
Use one row for each independently reviewable requirement. For example, preserve part identity and export a readable C-scan are separate outcomes even if demonstrated in the same session. Link to the actual evidence rather than writing only checked. Keep the matrix current when a configuration changes or an issue is retested. A concise index can make a complex acceptance file navigable while the detailed technical reports remain in their controlled locations.
Work through a fictional factory-to-site gap
A hypothetical manufacturer accepts a factory demonstration using representative parts and a simulated production identifier. At installation, the real manufacturing interface uses a different identifier structure. The system still scans correctly, but the exported report cannot be reconciled automatically with the production record. The site team records this as an open interface requirement rather than declaring the entire project complete because the ultrasonic hardware passed its earlier trial.
The data owner and supplier agree a supported mapping, repeat the identity trial and preserve the corrected evidence. The technical acceptance remains tied to the appropriate configuration, while the interface issue receives its own disposition. This fictional example shows why factory and site evidence should be related but distinct. It also explains why an acceptance matrix needs more than a list of instrument specifications: the final output must work inside the customer's actual process.
Retain the delivered system's support package
At handover, collect the agreed configuration baseline, application scope, manuals, software entitlements, fixture records, trial evidence and support responsibilities. Identify the process for reviewing later changes. An automated system may evolve through replacement components and new part programs; the organization should preserve which evidence supports each accepted role instead of treating the original purchase as permanent authorization for every future application.
NDT Connect can coordinate the asset identity, due date, status and notes for relevant equipment. It does not control motion, manage part programs, acquire C-scans or approve automated release decisions. Keep those functions and records in the selected production and inspection systems. The completed purchasing file should allow a new project owner to understand what was accepted at the factory, what was established at the site and where any remaining application boundary lies.
Assign ownership of the final acceptance archive
Name the person responsible for assembling the signed decisions and their supporting evidence after the project closes. Supplier reports, customer trial notes and issue resolutions often arrive through different project channels. Reconcile them against the matrix so an apparently closed requirement does not point to an inaccessible draft or a superseded configuration.
Preserve the final version of each accepted artifact and the relationship to any corrective retest. The archive should explain the disposition without requiring access to a project member's personal inbox. This administrative closure makes the technical acceptance useful to future maintenance, quality and production staff.
Frequently Asked Questions
Does tank size define the inspectable part envelope?
No. Evaluate the complete supported arrangement, including fixtures, probe access and motion requirements.
Why keep factory and site acceptance separate?
They address different evidence. The site stage confirms the delivered configuration and actual facility, data and production interfaces.
Does the worksheet supply UT acceptance limits?
No. It indexes project-specific evidence and responsibilities; qualified technical owners establish the applicable inspection criteria.
References & Standards Cited
- Evident: automated inspection project stages View source ↗
- Evident: immersion tank testing system 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.