Evaluating an X-ray vendor works in both directions. A vendor selling a solution rather than a product needs to understand the application before recommending anything, and the quality of the questions they ask is one of the more reliable signals available during an evaluation.
The ten questions below are what a good vendor should be asking. They are not sales qualification. Each one maps to a specific configuration decision, and a vendor who skips them is proposing a system without knowing what it needs to do. They also work as a self-assessment. An organization that cannot answer them is not yet ready to specify a system.
1. What are you inspecting?
PCBs, populated assemblies, batteries, castings, and discrete components all behave differently under X-ray. Density, thickness, and material composition determine how much energy is required to penetrate the sample and how much contrast will remain in the resulting image.
This answer propagates through the entire imaging train. Tube power, detector type, and geometry all follow from what actually goes in the cabinet.
2. What resolution and defect visibility do you need?
This question aligns expectations with physics before a quote exists. The relevant version is not how small a feature the system can theoretically resolve, but what defects have to be found reliably in production.
Resolution is not free. Higher resolution means higher cost and generally slower throughput, since finer imaging requires greater magnification, longer exposures, or both. A vendor who asks this is trying to avoid specifying a system that either misses the defects that matter or costs considerably more than the application requires.
3. What are your board size, thickness, and density?
These dimensions size the hardware. Overall size determines cabinet dimensions and how much stage travel is required to reach every region of the sample. Thickness and density determine the tube energy needed to penetrate it.
Thicker and denser samples require higher energy systems, and heavy copper or multilayer construction raises the requirement further. Getting this wrong in either direction is expensive, whether it means a system that cannot penetrate the work or one specified well beyond what the work demands.
4. Will inspection be inline or offline?
This answer defines the entire workflow rather than a single specification.
Inline inspection means conveyor handling, automated board transfer, and connectivity to an MES for data flow. It also means the inspection has to keep pace with the line. Offline inspection provides far more flexibility in what can be examined and how, at lower throughput.
Neither is a better answer. They are different operating models, and the choice constrains almost everything downstream.
5. What is your budget and timeline?
Vendors ask this early for practical reasons. Budget establishes which configurations are realistic to discuss, and timeline determines how much can be customized before delivery.
Lead time matters more than buyers often expect. Custom configuration, integration work, and operator training all need scheduling, and a compressed timeline removes options that a longer one would keep open.
6. How often will the system be used?
Occasional failure analysis and continuous production inspection place very different demands on the same hardware.
Duty cycle drives tube selection, cooling requirements, and the appropriate service plan. A system running continuously accumulates tube hours quickly and needs thermal management sized accordingly. A system used a few times a week does not, and paying for that capacity provides nothing.
7. Who will operate it?
Engineers and production technicians need different interfaces. An engineer running failure analysis benefits from direct control over imaging parameters. A production technician running a fixed inspection routine benefits from an interface that removes those decisions entirely and executes a stored program consistently.
This determines how much of the system should be automated versus exposed, and it has direct consequences for training requirements and for how repeatable results will be across operators and shifts.
8. What safety protocols does your facility already follow?
A vendor needs to understand the existing radiation safety environment, including training programs, standard operating procedures, and any registration or licensing already in place.
Facilities with established radiation safety programs integrate a new system differently than facilities bringing X-ray in for the first time. The second case requires more groundwork before the system arrives, and a vendor who does not ask is leaving the buyer to discover those obligations later.
9. Are you inspecting for compliance or for quality control?
These lead to genuinely different system requirements.
Compliance-driven industries such as aerospace and medical devices require full traceability, image storage, and audit trails, because the inspection record itself is a deliverable subject to review. General quality control work tends to prioritize speed and image clarity over documentation depth.
A system specified for one and used for the other creates problems that are difficult to correct after installation, particularly when the missing piece is a data retention capability that an auditor expects to exist.
10. When do you need the system installed?
Installation timing interacts with everything above. A tight deadline limits configuration options, compresses training, and reduces room for site preparation.
A longer window creates flexibility in configuration, allows training to be scheduled properly, and often produces better commercial terms. Stating a realistic date rather than an aspirational one leads to a better outcome than discovering the constraint during installation.
What the answers reveal
These questions tell a vendor what to recommend. They also tell a buyer how prepared the organization actually is.
Difficulty answering several of them is useful information rather than a problem. It usually indicates that the inspection requirement has not been defined precisely enough yet, and that is far cheaper to resolve before a purchase order than after a system is on the floor.