YiRadarOEM / ODM · Reviewed resource
Reviewed by Mr. Wang, YiRadar Engineering · · Review standard
How to Prepare a Radar Module RFQ: An Engineering Brief Template
A useful radar module RFQ is not a request for a frequency band and a unit price alone. It is a concise description of the behaviour the host product must achieve, the environment in which it must achieve it, and the constraints that will shape the final configuration. The better this starting brief is, the faster an engineering team can identify an appropriate candidate, identify unknowns, and give a commercial response that can be relied upon.
Start with the response, not the part number
Describe what the product must do after the radar detects something. “Detect a person” is too broad. State whether the system needs to react to motion, stationary presence, a position in a zone, a distance change, a gesture, a moving target, or a warning condition. Then state the desired system action: wake a display, control lighting, update HVAC logic, report a target location, or send an event to a host controller.
This separates a module-level sensing question from the control logic that belongs in the larger product. It also helps avoid choosing a motion-oriented configuration for an application that actually requires stationary presence, or treating a sensing event as a complete safety or care workflow.
Define the physical scene
An RFQ should include a simple drawing or photographs whenever possible. Mark the proposed mounting position, the target zone, the approximate target distance, the enclosure material, nearby moving objects, and likely obstructions. The same module can behave differently when placed behind a plastic front panel, near metal, under a high ceiling, or beside a fan, door, water fixture, or vibration source.
Include the expected number of people or objects in the scene and whether a defined zone is more important than total coverage. If the host product moves, record the vehicle or appliance motion that will be present while sensing occurs.
State electrical and integration constraints early
Give the available supply voltage, target current budget, preferred host interface, mechanical envelope, and any firmware-update expectation. The interface should name the host platform and the event or data format the host needs, rather than only naming a connector. For example, a project may need a UART event stream, a defined GPIO response, or application-level messages handled by host firmware.
If a product enclosure already exists, provide its material stack-up and the allowed module location. If it does not, state the available area and whether antenna orientation, connector location, or a surface-mounting method is constrained. This information determines whether an existing configuration is a sensible starting point or whether an OEM / ODM review is more efficient.
Make validation part of the RFQ
State how success will be judged. Useful acceptance inputs include target behaviours, distances, mounting heights, response-time expectations, false-trigger conditions, environmental conditions, and the number of units or installations to be tested. The final test plan belongs to the project parties, but naming the test conditions early prevents a nominal catalog value from being mistaken for an installed-system commitment.
Also identify any safety, medical, privacy, radio, environmental, or country-specific compliance obligations. A radar module configuration does not by itself establish the compliance or suitability of the finished product.
Include commercial context
An RFQ should state sample quantity, target production volume, target market, project timing, and whether the requirement concerns an existing YiRadar configuration or a custom development program. A forecast does not need to be exact; a credible volume range and timing window are enough for an initial manufacturing and engineering conversation.
For the next step, send the brief through the YiRadar RFQ form or start with the custom radar module development hub. If the application is already clear, include the closest YR product configuration as a reference point.
Ready to apply this?
Bring the project conditions to an engineer.
Module selection, final integration, and commercial terms are reviewed against the actual installation and host system.
