Digital Radiography Detectors: Compare the Complete Package
An industrial digital detector is one part of a radiography system. Compare its documented characteristics, physical arrangement, acquisition software and retained-image workflow against the approved application before treating a panel specification as a complete purchasing answer.
For: U.S. NDT equipment coordinators, quality staff and inspection business owners
Define the application and equipment boundary
Ask the responsible radiography authority to define the approved application and the evidence the imaging system must provide. Purchasing needs a clear statement of the component families, practical access constraints, required image deliverables and applicable technical requirements. It should not infer an exposure technique or image acceptance criterion from a detector brochure. This guide addresses procurement and records, not source operation, exposure settings or radiation protection arrangements.
State whether the purchase concerns a detector alone, a detector and acquisition workstation, or a broader system. Identify existing equipment proposed for reuse and the supplier responsible for confirming the complete arrangement. A standalone detector price can be useful, but it does not establish the total cost or readiness of the inspection workflow. The quotation should make the package boundary explicit enough for another reviewer to understand what remains outside it.
Separate current work from hoped-for future applications. A detector selected for an established task may not suit every geometry, material range or operating arrangement the business later considers. The technical authority should identify the relevant capability for each intended use. Purchasing can then compare demonstrated requirements and optional future capacity without turning a general industrial product description into a claim of universal suitability.
Distinguish direct detectors, computed radiography and digitized film
Digital radiography is used broadly enough that a quotation should identify the actual acquisition technology. Waygate's product overview distinguishes direct radiography detectors, computed radiography systems and film digitization. These categories involve different equipment and record workflows. A buyer should not compare a detector panel with an imaging plate scanner or film digitizer as though each line item performs the same role.
Write the source-to-image workflow in plain language and identify each required device. For a proposed detector arrangement, confirm which hardware acquires the image and which software receives it. For an alternative technology, identify the corresponding processing and handling stages. The technical team decides which approaches are acceptable for the application; purchasing uses the workflow map to compare complete packages on a common basis.
Keep the deliverable requirement consistent when comparing alternatives. If the customer needs a particular reviewed image package or archive relationship, every proposal should explain how it supplies that result. A shorter acquisition workflow does not automatically satisfy the same downstream requirements. Conversely, an additional handling stage is not necessarily disqualifying if the complete approved process meets the organization's needs and its costs are understood.
Look beyond a single pixel specification
A pixel pitch figure is one detector characteristic, not a complete description of image performance. ASTM's public E2597/E2597M-22 scope describes manufacturing characterization intended to provide quantitative information for users and purchasers. Its public significance section identifies several characteristics, including spatial resolution, efficiency, contrast-related performance, lag and pixel behavior. That public material supports a broader evidence request; this guide does not reproduce the standard's test procedures or prescribe their application.
Ask the supplier for the characterization evidence relevant to the proposed detector model and the technical team's requirements. Record what the evidence represents and any conditions or limitations attached to it. A brochure's headline value should not replace the underlying context needed by the reviewer. If two suppliers report different metrics, ask for clarification rather than ranking them as though the numbers measure the same thing.
Do not convert a detector specification directly into a guaranteed smallest detectable flaw or a universal exposure reduction. The complete imaging arrangement and application affect the result. The responsible technical authority should determine what demonstration or evidence is required for the intended use. Purchasing can insist that claims are clearly defined and supported without supplying operational techniques or making technical acceptance decisions itself.
Review characterization evidence at the right level
Distinguish information about a detector model from evidence for the specific unit delivered. ASTM's public scope explains that its manufacturing characterization is intended for manufacturers or integrators and is not simply a routine user stability procedure. Ask the supplier and technical reviewer which model-level information and unit-specific records are needed for the purchase. Avoid requesting a document by standard number without understanding what decision it is meant to support.
Create an evidence index that identifies each document, the item or model it concerns, its date and the reviewer responsible. The index should make it possible to distinguish a general data sheet, a characterization report, a supplied-unit record and the organization's acceptance result. These objects may complement one another, but they are not interchangeable merely because they all contain detector performance language.
Record unresolved differences between the quotation and evidence. If the offered variant differs from the one described in a report, ask the supplier to explain the relationship. Do not assume that a shared product family name makes every result applicable. The technical authority decides whether the available evidence is sufficient or whether additional confirmation is required before the package can be accepted for its intended use.
Assess physical fit as an assembled package
Obtain dimensions and handling information for the exact detector configuration, including any protective arrangement, cable or other accessory required by the proposed workflow. The available space may constrain the package differently from the active imaging area. Ask the technical team to define the relevant access conditions and the supplier to provide the appropriate drawings or controlled demonstration evidence.
Waygate's portable detector page describes detector thickness and wired or wireless options as practical product considerations. Use such information to frame configuration questions, not to assume that one detector fits every location or operating arrangement. A claimed portability benefit should be evaluated with the actual protective items and connections included in the approved package.
Keep physical access and imaging suitability separate in the decision record. A detector can fit a space while still needing further technical evidence for the required image, and a suitable imaging capability can be impractical in the intended geometry. The purchasing evaluation should identify which question each demonstration addresses. Neither result should silently be generalized to the other.
Treat flexible and rigid designs as different configurations
If a supplier proposes a flexible detector, ask for the exact manufacturer's permitted configuration and limitations and have the technical authority review them for the application. Do not infer that a flexible product behaves like film or an imaging plate in every respect. Likewise, do not assume a rigid panel can be substituted without affecting the approved arrangement. The detector form is a configuration choice that belongs in the technical and purchasing record.
Ask whether the proposed package includes the accessories and protective components used in the demonstration. A product photograph may show an arrangement that is optional or supplied separately. Record the part identities and quantities so receiving staff can compare delivery with the accepted configuration. If a required accessory is omitted to reduce the price, retain the resulting condition rather than allowing the quotation to appear complete.
Avoid treating a new design or recent announcement as evidence of application acceptance. A product can offer a useful capability while still requiring the organization's normal technical review and customer agreement. The buyer should focus on the evidence for the intended task and the support available for the specific package, rather than assuming that novelty itself improves the purchasing decision.
Include acquisition and review software in the comparison
Identify the software functions needed to acquire, review, annotate, report and archive the images. A detector package may include an acquisition application without every analysis or reporting function the organization expects. Waygate's Rhythm suite description distinguishes acquisition, review and optional functions. This illustrates why the quotation should identify the edition and entitlement rather than relying on a software family name.
Ask the intended users to demonstrate the required tasks under the proposed license. Record any additional application, workstation or viewer dependency. A sales demonstration using a full-featured license does not establish that the purchased edition provides the same workflow. Confirm the relevant access and support terms with the supplier, including what happens to required functions when a subscription or support period changes.
Include the organization's approved review environment in the acceptance plan. The technical authority determines the requirements for image interpretation and review; purchasing should not substitute a convenient laptop display based solely on screen size or resolution. The analysis workstation guide explains how to organize a software and file trial while keeping application-specific technical acceptance with the responsible reviewer.
Verify what images and context are retained
Ask the technical and records owners to define the objects that must be retained and delivered. These may include source images, relevant processing context, annotations, reviewed outputs and the issued report, depending on the approved requirements. Do not assume that a screenshot or compressed image export is equivalent to the native evidence needed for later review. Specify the intended use before selecting the export format.
Demonstrate the retained package after the acquisition session has ended. The recipient should be able to identify the component, examination record and relevant image relationship without relying on the demonstrator's memory. Ask which processing or annotation changes can be revisited and how issued results are distinguished from working changes. The software's capabilities should be described accurately without inventing a complete audit trail or immutable archive.
If DICONDE exchange is part of the requirement, test the intended receiving system and workflow rather than accepting the label alone. A supported format can help exchange, but the actual file contents, metadata and receiving functions still need appropriate review. Keep the acceptance claim tied to the tested configuration and task. The package should state what the customer can do with the delivered images, not merely which extension appears in the filename.
Plan service and condition evidence over the ownership period
Ask the supplier how it handles technical support, service, repair and configuration identification for the detector and related equipment. Obtain the relevant terms rather than assuming a local turnaround or loan unit. The organization's technical process should determine what evidence is required after a repair or replacement before returning the package to its approved use. A functioning connection alone does not establish that all required performance evidence is current.
Retain the unit's identity and service history separately from the general model information. If a detector is replaced, create a clear relationship between the old and new records instead of changing the serial number on a single historical entry. Earlier inspection records should remain connected to the equipment used at the time. The new unit's acceptance evidence should be identifiable without erasing the previous history.
Do not invent a universal calibration or performance-check interval for every digital detector. The responsible authority should apply the relevant requirements, manufacturer information and organizational process. Purchasing can ask about service availability and documentation, but the final interval and readiness decisions need the appropriate technical basis. Record the source of the decision so an administrator does not later mistake a default date for an established requirement.
Compare costs with the same acceptance boundary
Build a total package comparison that includes the detector, required accessories, software, workstation needs, training, acceptance evidence and documented support arrangements. Keep optional future features separate. If a supplier leaves a necessary item unpriced, show it as unresolved rather than assigning zero. This prevents a low panel price from being compared unfairly with another supplier's complete working package.
Use the organization's actual workload when evaluating expected benefits. A manufacturer's demonstration or case study may illustrate an opportunity without predicting the result for your application. Avoid universal claims about exposure reductions, throughput or cost savings. The technical and commercial teams should identify the assumptions that would need to hold for the purchase to deliver the expected value.
Consider continuity when a single detector or application is unavailable. The appropriate answer may be service support, rental, another approved arrangement or a scheduling change. Obtain the relevant commitments and record what remains the organization's responsibility. The purchase decision should explain the practical consequences of downtime rather than treating a warranty statement as a complete continuity plan.
Apply the review to a hypothetical detector offer
A fictional radiography provider compares two detector packages. One advertises a smaller pixel pitch, while the other includes a review application and characterization evidence directly relevant to the provider's approved task. The provider does not choose a winner from those facts alone. Its technical reviewer assesses the required imaging evidence, and purchasing maps both quotations to the same complete workflow before comparing cost.
During the hypothetical review, the lower-priced quotation omits a software entitlement needed for the customer's agreed image handover. The supplier adds that option and the team repeats the receiving-system demonstration. This example illustrates package completeness rather than a performance claim about a named detector. The resulting comparison is more useful because it exposes the actual deliverable and dependency instead of ranking isolated brochure specifications.
The accepted record identifies the detector configuration, supporting evidence, software environment, retained images and responsibilities for future changes. NDT Connect can hold equipment identity, due date, status and notes referencing that external record. It does not acquire radiographs, evaluate image quality, store DICONDE studies or authorize radiographic work. The equipment register supports administration of the accepted package while the technical and radiation protection processes remain with the responsible organization.
Frequently Asked Questions
Is smaller detector pixel pitch always the best purchasing choice?
No. Evaluate the complete application and documented detector characteristics with the responsible technical reviewer rather than ranking a single specification.
Does a detector characterization report approve every inspection application?
No. Model characterization, supplied-unit evidence and application acceptance answer different questions and need an appropriate review.
Is a DICONDE label enough to guarantee the customer can review the images?
No. Test the agreed file package and functions in the intended receiving environment and record any limitations.
References & Standards Cited
- ASTM International: E2597/E2597M-22 public scope and significance for DDA manufacturing characterization View source ↗
- Waygate Technologies: digital radiography product categories View source ↗
- Waygate Technologies: portable digital X-ray detector information View source ↗
- Waygate Technologies: Rhythm acquisition, review and archive software functions 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.