An RF test equipment RFQ should state the measurement job before it states the instrument model. In the first 150 words, name the frequency range, required bandwidth, expected signal level, connector and cable path, calibration plane, acceptance evidence, and destination. A useful example is: “Measure conducted emissions from 150 kHz to 30 MHz with a LISN, verify a receiver path to 6 GHz, record 10 MHz analysis bandwidth checks, define a -20 dBm reference signal, and deliver one known-good and one forced-fail report.” That is a buyer brief, not a shopping list.
The RFQ does not need to be long, but it must be specific. RF test systems fail quietly when the requirement only says “spectrum analyzer” or “signal generator” and leaves the cable, adapter, fixture, trigger, calibration, software, and export path to guesswork.
What to include before asking for price
Start with the application. Is the equipment used for EMC pre-compliance, receiver troubleshooting, production RF alignment, VNA measurement, cable qualification, RF power amplifier checks, field interference hunting, or automated test? The answer changes the instrument class, accessory set, and acceptance method.
Next, state the DUT and operating conditions. Include frequency range, power level, modulation type, bandwidth, connector type, expected impedance, cable length, fixture geometry, ambient constraints, and whether the test is manual or automated. If the equipment will be shipped internationally, include the destination country, end user, end use, delivery terms, and documentation requirements.
Do not hide uncertainty. If the exact frequency range or bandwidth is not settled, say so and ask the supplier to propose the decision path. A good RFQ can include open questions; a bad RFQ pretends the missing engineering is already solved.
Engineering Review Matrix
| RFQ field | Minimum detail to provide | Why it matters | Acceptance evidence |
|---|---|---|---|
| Frequency range | Start, stop, harmonics, IF, or sweep needs such as 9 kHz to 6 GHz | Determines analyzer, generator, cable, probe, and fixture suitability | Known signal or sweep result at agreed points |
| Bandwidth and speed | RBW/VBW, real-time bandwidth, sweep time, or capture time | Prevents buying a device that sees the signal but misses the event | Screenshot or data file at target bandwidth |
| Power and dynamic range | Expected input/output level, attenuator, preamp, damage limit | Protects front ends and defines measurement margin | Reference level check and overload behavior |
| Cable and connector path | SMA, N, 3.5 mm, waveguide, cable length, adapter count | RF path loss and repeatability often dominate the result | Cable state, adapter list, or path loss note |
| Calibration plane | Instrument port, cable end, fixture port, or DUT reference plane | Defines where the measurement is trusted | Calibration note or reference device result |
| Automation and data | SCPI/LAN/USB/PXIe, CSV/PDF/database, operator fields | Prevents manual copying and missing traceability | Sample report with DUT ID and measured values |
| Export screening | Destination, end user, end use, technical scope | Prevents late compliance surprises | Export review note before order release |
Use this matrix as the RFQ body if the project is still early. It gives suppliers enough context to ask useful questions and gives procurement a way to compare answers beyond unit price.
Common RFQ mistakes
The first mistake is quoting the maximum frequency but not the lowest useful frequency. EMC and conducted-noise work can care about kHz ranges, while mmWave work may care about waveguide bands, cable phase stability, and fixture access. The second mistake is ignoring the measurement bandwidth. A narrow swept measurement and a real-time capture can produce different answers even when the frequency headline looks similar.
The third mistake is treating RF accessories as minor parts. Cables, adapters, probes, LISNs, attenuators, switches, and fixtures can decide repeatability. A 40 GHz cable with poor handling control can create more uncertainty than the instrument selection. The fourth mistake is leaving reports until the end. If the buyer needs DUT ID, operator, timestamp, limit table, screenshot, raw data, and pass/fail result, those fields belong in the RFQ.
The fifth mistake is assuming export is automatic. For international orders, XGY Tek should screen destination, end use, end user, technical scope, and documentation before order release. The RFQ should not promise universal export availability.
Acceptance evidence to request
For a standalone RF instrument, request a configuration record, datasheet, accessory list, calibration status where applicable, and a representative measurement screenshot or data file. For a system, request a FAT checklist, known-good result, forced-fail result, path description, software version, report sample, exception log, and handover notes.
If the system includes a LISN, probe, VNA cable, RF switch, or fixture, require at least one verification step that exercises the accessory path. A spectrum analyzer screenshot alone does not prove the fixture, cable, or automation path is correct. The evidence should name the signal source, level, frequency, cable path, attenuation, and result.
For automated RF systems, include a negative test. A forced fail at a defined limit proves the report can reject a bad condition. Without that, the system has only demonstrated that it can display a pass.
References Reviewed
This checklist uses CISPR and ANSI EMC instrumentation context for RF measurement discipline, SCPI for instrument-control expectations, and ABF export requirements for international shipment guardrails. The references do not replace project-specific standards review, but they keep the RFQ anchored in verifiable engineering language.
When the application is EMC pre-compliance, do not present the result as accredited compliance unless the correct accredited test path is scoped. When the application is export supply, do not imply every destination or end use is eligible.
Engineering FAQ
What is the shortest useful RF test equipment RFQ?
State the application, frequency range, bandwidth, signal level, connector path, calibration plane, software/report output, destination, end use, and acceptance evidence. If those fields are present, a supplier can start a serious engineering review.
Should I specify a model number or the measurement problem?
Specify both if you already have a preferred model. If you only specify a model number, the supplier may miss cables, fixtures, software, reports, calibration, or acceptance evidence that make the model usable.
What acceptance checks should be mandatory?
Require at least one known-good measurement, one forced-fail or out-of-limit condition, a report sample, the RF path description, software version, and any calibration or reference notes. Systems with fixtures should also validate loading and repeatability.
How does export screening affect RF equipment procurement?
Destination, end user, end use, and technical scope can affect whether and how a product is supplied. The safest RFQ includes those fields early so compliance review happens before order release.
Quote-stage handoff
Send the RF requirement list for quote-stage validation. Include the measurement method, target ranges, report needs, destination, and acceptance criteria so the quote can be checked as a system rather than a loose model comparison.