Waygate–Varex Partnership: 2026 Field Radiography Buyer Brief

The October announcement, separated from the buying decision

On October 7, 2026, Waygate Technologies and Varex Imaging announced a partnership covering Varex industrial detectors for field radiography. The release identifies Waygate as the exclusive distributor for that scope and says it will assume global after-sales service and training responsibilities. It also introduces Weldpack Pro, a weld-inspection package using bendable and small flat-panel detector options. These are supplier announcements, not independently verified performance results. Read the official announcement.

This article was published on October 31. The announcement date is October 7; the two dates describe different events. We have not independently tested the package, confirmed every regional delivery date or obtained a customer-specific quotation. The following sections are NDT Connect's original purchasing and transition questions for U.S. inspection businesses and asset owners. They are not statements that either supplier has agreed to a particular customer's terms.

Start with the decision that is actually pending

An existing detector owner, a film-based inspection company and an asset owner buying an inspection service have different decisions. An existing owner may primarily need continuity of support. A company considering a new system needs evidence for the intended application and a workable operating model. A service buyer needs an agreed examination scope and usable records, even when another company owns the equipment.

Write the decision at the top of the review document. For example, “Confirm the support route for our installed detector before the next scheduled project” is narrower and more actionable than “Move to digital.” It identifies an owner, a deadline and the evidence needed to close the question. A broader transformation project can then be divided into several such decisions.

Avoid allowing a product presentation to redefine the need halfway through procurement. If the project requires a particular examination, access arrangement or reporting deliverable, preserve that requirement in the comparison. Record attractive additional capabilities separately. They may be valuable later, but they should not obscure an unresolved requirement in the work already promised to a customer.

Existing owners should build a support continuity record

List each installed detector, associated software, accessories and the serial or license identifiers needed to obtain support. Add the current service agreement, warranty evidence, open support cases and any equipment already in transit for repair. This is an administrative inventory, not a new technical approval or an assumption that contract terms have changed.

Ask the current and proposed support contacts to confirm who handles each open item. Record the answer, its date and the affected equipment. A service-channel transition can create uncertainty when one team assumes a case has transferred and another has not received it. A short written record is more useful than relying on a familiar salesperson's name in an old email thread.

Keep a separate list of questions that remain unanswered. Typical examples include the correct repair destination, who issues a return authorization, how an existing service commitment will be handled and whether any customer action is needed for software access. Do not ship an instrument or disclose customer inspection data solely because a message uses a recognizable brand. Verify the communication through an established supplier contact.

New buyers need a complete package definition

Ask for a bill of supply that identifies the detector configuration, acquisition software, review software, power arrangements, transport protection and relevant accessories. Have the supplier distinguish included items from optional items and customer-provided equipment. A package name can make a quotation easier to discuss while leaving important implementation details unspecified.

Then connect each item to a task in the intended workflow. Who acquires the image, who reviews it, where are the records stored and how does the customer receive them? A second workstation or a receiving organization's viewer may matter as much to delivery as the acquisition hardware. The buyer should be able to explain the complete path from examination to accepted record.

Record dependencies that can interrupt that path. These might include an account administrator, an internet connection at a particular step, a license renewal or access to a supported computer environment. Request the actual supplier requirements rather than assuming every field workflow works offline. An equipment purchase should leave the organization with a usable process and known dependencies, not just an inventory of delivered boxes.

Define a representative trial with the technical owner

The responsible technical authority should define the application and the evidence needed from a trial. Procurement staff can organize the schedule and record the results, but they should not invent image-quality limits, exposure settings or inspection acceptance criteria. This article supplies none of those parameters. The approved requirements for the actual work remain the controlling reference.

Choose examples that reflect the important characteristics of the proposed work rather than only the easiest demonstration item. The review may need to consider geometry, access, material, handling and the intended reporting arrangement. Ask the technical owner which differences between the trial and production are acceptable and which leave an important question unresolved.

Capture the exact configuration used during the demonstration. If the offered package later changes, the reviewer needs to know whether the original evidence still supports the decision. Record limitations and unsuccessful tasks alongside successful results. A trial that identifies an exclusion before purchase has produced useful information even if it does not support an immediate unrestricted deployment.

Measure the whole delivery workflow

A buyer often wants to know whether digital equipment will make a project faster. Define the start and finish of that comparison before collecting timings. An acquisition step, an interpreted examination and a released customer record are different milestones. A shorter time at one milestone does not establish the same saving across the entire assignment.

For an original trial worksheet, record preparation, acquisition, review, correction, export and customer handover as separate stages. Use the same scope and completion definition for the options being compared. Keep the number of repeat examinations and the reason for each repeat visible. Do not turn one smooth demonstration into a guaranteed production rate.

Include the people who receive the output. If a client's reviewer cannot locate the component, open the supplied files or distinguish a revised image from the original, the work is not complete merely because acquisition finished. The practical question is whether the proposed workflow produces a record that the intended recipient can understand and use within the agreed review process.

Make data handover a purchasing requirement

Agree the required file types, identifiers, review information and transfer method before the order is placed. Ask the supplier to demonstrate an export and the recipient to open that export in its intended environment. Keep the demonstration record with the purchase decision, including any software dependency or information that does not survive the transfer.

DICONDE is relevant to this conversation, but a label alone does not finish the review. ASTM publishes E3147 for evaluating DICONDE interoperability and E3463 for image and presentation-state display interoperability. Consult the applicable documents and competent reviewers for the actual requirements; the public descriptions are not the full standards. ASTM E3147 and ASTM E3463.

An original acceptance exercise can ask a recipient to retrieve a nominated examination, identify its component, find its review status and distinguish a corrected record from a superseded one. Record the outcome rather than accepting a general compatibility claim. Our digital radiography data-handover guide develops that records question in more detail.

Separate product instruction from personnel authorization

Ask what supplier training covers and what evidence the participant receives. Product operation, software administration, data review and troubleshooting are different learning objectives. The organization should know which tasks a course addresses, what prior knowledge is assumed and which responsibilities remain with the employer or customer.

Create a role-based learning plan for the people who will acquire, review, administer and receive the records. Someone who only manages software access does not need to be described as qualified to interpret an examination. Equally, an experienced reviewer may still need an introduction to the specific record workflow before working independently in the new environment.

Course attendance should be recorded accurately without being converted into an unsupported personnel certification or project authorization. Ask the responsible qualification authority what additional evidence and approval are required for each proposed role. The qualification-record library offers administrative worksheets for organizing those documents without treating a reminder or a course certificate as an approval decision.

Keep radiation protection within the established controls

A detector purchasing discussion does not replace the organization's radiation-protection arrangements. The U.S. NRC's industrial radiography toolkit points to licensing and safety requirements for the activities within its scope. Applicability must be established for the actual source, operation and jurisdiction by the responsible people. NRC industrial radiography toolkit.

Include the radiation-safety and technical owners in change planning early enough to identify the relevant reviews. Procurement should obtain their requirements rather than infer them from a statement about improved detector performance. No exposure, boundary, staffing or monitoring instruction is provided here, and no supplier partnership is treated as an authorization to alter a controlled operating method.

The useful purchasing record is a responsibility map: who evaluates the proposed equipment, who reviews the procedure implications and who authorizes the eventual deployment. Unanswered questions should have named owners and remain open until resolved. This helps a commercial decision move forward without silently transferring technical decisions to a purchasing coordinator.

Compare written commercial terms without invented savings

Request a quotation for the defined package and distinguish purchase, rental, subscription, service and usage charges where applicable. Ask which items are recurring, which depend on the scope and which are optional. This article does not publish a market price, a payback period or a guaranteed cost reduction for the new package.

Prepare a comparison using the same period, workload and responsibilities for every proposal. Include actual quoted support and software terms, proposed training, required accessories and the organization's own implementation effort. If an input is unknown, mark it unknown and show which decision depends on it. A blank cell should not quietly become a zero-cost assumption.

Use scenarios to test the decision, not to manufacture precision. For example, examine what happens if workload is lower than expected, a review workstation needs replacement or a support event occurs during a project. The buyer can then identify the contract provisions and contingency arrangements that matter most before signing. Our inspection cost guide explains how to keep scope and quotation assumptions visible.

Plan a limited first deployment and a fallback

Once the responsible reviewers have approved the intended use, define the first deployment's boundaries. Identify the work population, responsible personnel, record-delivery process and the conditions that require escalation. A limited introduction gives the team a manageable way to observe the full workflow; it is not a substitute for the required technical demonstration or approvals.

Write down how an interrupted workflow will be handled. Who contacts support, what information may be shared and who decides whether the examination can continue? A fallback should be an authorized option under the actual project requirements, not an improvised change made because a device or software account is unavailable.

After the deployment, compare what happened with the original decision brief. Review unresolved support issues, repeat work, data-transfer problems and customer questions. Separate a training need from a configuration problem or a scope mismatch. That distinction helps the next action address the cause instead of producing a vague conclusion that the whole technology succeeded or failed.

Use a transition checklist that remains useful after the announcement

The following checklist is an original editorial aid. It is not a manufacturer form, a contractual commitment or a technical acceptance standard. Assign each item to the person who can obtain the relevant evidence, and retain the answer with the purchase or support record.

Keep the checklist connected to the equipment register. It should be possible to locate the support record for a particular detector and identify which software configuration the purchase review covered. NDT Connect's free equipment tracker can hold current equipment information; it is not a replacement for the full contract, inspection archive or technical approval record.

If you are buying an inspection service rather than a detector, use the same questions to clarify the deliverable with the provider. State the asset, location, work window, governing requirements and expected records in your service request. Confirm the actual provider's capability and availability directly. A well-defined request gives the supplier a useful starting point and gives the buyer a clearer basis for comparing responses.

Sources and editorial scope

The dated news in this feature comes from the October 7, 2026 supplier announcement linked above. The commercial and workflow checklists are NDT Connect editorial proposals, not instructions issued by Waygate or Varex. We have not reported an independent field trial, customer performance result or confirmed universal product availability.

NDT Connect is operated by Atlantis NDT. This article is source-based industry coverage; it does not claim an affiliation with the companies discussed. For corrections, provide the affected passage and supporting primary evidence through our contact page. Our editorial policy explains AI assistance, source use, dates and related-company disclosures.