For thermal imaging and laser rangefinder (LRF) projects, the quality of your RFQ often decides the quality of the quotations you receive. A clear, structured RFQ for thermal and LRF projects allows suppliers to estimate cost and lead time correctly, propose the right platform, and highlight risks early. A vague RFQ forces everyone to guess, and those guesses usually show up later as delays, redesigns or unexpected costs.
This article outlines what engineering and procurement teams should include in an RFQ when sourcing thermal imaging modules and laser rangefinder modules, or complete devices such as thermal scopes and handheld rangefinders. The focus is practical: what information to provide, how detailed it should be, and why it matters to your OEM/ODM partner.
1. Why RFQ quality matters more for thermal and LRF projects
Thermal and LRF systems are not generic components. Performance depends strongly on target type, background, atmosphere, mechanics and firmware. Two RFQs with the same “640×512, 50 mm lens, 1,000 m range” headline can represent completely different engineering problems.
A good RFQ helps both sides to:
- converge quickly on feasible architectures;
- avoid unnecessary over-specification that inflates cost;
- identify critical risks before the first prototype;
- plan a realistic schedule from sample to mass production.
In practice, a well-prepared RFQ can easily save one design iteration and several weeks in the project timeline.
2. Describe the application and use scenarios
The most valuable part of a thermal or LRF RFQ is often not the numbers but the use context. Suppliers need to know what the system must actually do in the field.
Explain, in plain language, the primary application and typical scenarios. For example:
- handheld thermal monocular for night hunting in mixed forest and open fields;
- fixed online thermal monitoring systems for substation equipment;
- weapon-mounted LRF for ballistic correction on 5.56 mm and 7.62 mm platforms;
- vehicle-mounted obstacle detection for slow-speed industrial vehicles.
For each scenario, describe:
- typical target types and sizes;
- working distances (minimum, typical, maximum);
- background and lighting conditions (urban, desert, snow, maritime);
- operational profiles (continuous monitoring, intermittent use, short bursts).
Two or three concise paragraphs with this information are far more helpful than a long list of isolated parameters.
3. Define performance targets for thermal imaging
After the scenarios, specify what “success” means in measurable terms. For the thermal side, this usually includes:
- detector resolution and preferred pixel pitch, if known;
- required detection, recognition and identification ranges for key targets;
- desired field of view (FOV) or angular coverage;
- minimum frame rate and acceptable latency;
- temperature range of interest if radiometric data is needed.
If you are open to supplier recommendations, state that the ranges and FOV figures are targets, not hard constraints, and invite alternative proposals. This gives the manufacturer room to propose cost-optimised thermal imaging modules that still meet your functional needs.
Whenever possible, describe the performance using combinations of target size and distance instead of only “high resolution” or “long range”. For example, “detect a walking person at 1,200 m in clear weather” is clearer than “long-range detection”.
4. Define performance targets for laser rangefinding
For projects that include an LRF, the RFQ should equally clarify rangefinder expectations. Useful items are:
- maximum and typical ranging distance;
- target reflectivity classes (e.g. 10 %, 20 %, 80 %) and typical targets (trees, buildings, steel plates);
- required accuracy and repeatability;
- minimum and maximum allowable measurement time;
- single-shot vs continuous ranging requirements;
- eye-safety class (for example, IEC 60825-1 Class 1).
If integration with ballistics or navigation is planned, mention needed outputs: for instance, distance only, distance + angle, or full trajectory table integration. This helps the supplier suggest appropriate OEM/ODM solutions rather than a generic off-the-shelf module.
5. Mechanical envelope and mounting constraints
Thermal cores and LRFs are sensitive to mechanical constraints. The RFQ should include:
- maximum allowed module dimensions and weight;
- mounting interface (rail standards, screw patterns, custom brackets);
- expected recoil levels for weapon-mounted devices, including calibre and test standards if known;
- orientation restrictions (for example, optical axis vs gravity, IP rating requirements).
If a mechanical model exists, mention the available design format (STEP, IGES, etc.) and whether the supplier will receive it during the proposal phase. Even a simplified envelope drawing can help avoid impossible layouts and unnecessary design changes later.
6. Electrical, power and interface requirements
Clear interface information is critical for both hardware and firmware planning. The RFQ should summarise:
- input voltage range and typical power budget;
- battery system (for example, 18650, 21700 or proprietary pack);
- allowed inrush current and power-up sequencing constraints;
- required communication interfaces (UART, USB, Ethernet, CAN, SPI, I²C, video outputs);
- bandwidth requirements for video or data streams.
If your system uses an existing platform—such as a specific NVR, vehicle controller or embedded SoC—state the exact model and provide basic interface expectations. This allows the supplier to map their thermal imaging camera modules or LRF cores to your existing architecture instead of proposing a completely new stack.
7. Environmental, reliability and certification requirements
Thermal and LRF equipment often operate in challenging environments. The RFQ should clearly state:
- operating and storage temperature ranges;
- humidity expectations and condensation risk;
- vibration and shock levels, with reference standards if available;
- enclosure protection (IP rating) and corrosion considerations (for example, salt fog for maritime use);
- expected service life and warranty targets.
List required certifications or tests explicitly: CE, FCC, RoHS, REACH, MIL-STD-810 profiles, weapon-recoil tests, or local country approvals. This has a direct impact on design choices, test time and cost.
For example, specifying “IP67, 1 m for 30 minutes” upfront avoids later disagreement about what “waterproof” means.
8. Lifecycle, volumes and logistics
Suppliers need to understand how long the product must live and how volumes may change over time. Include:
- expected sales lifetime (for example, 5–7 years);
- planned annual volume and ramp-up profile;
- minimum batch sizes you can accept;
- critical launch dates (trade shows, contract commitments, hunting seasons).
If you foresee second-generation products—higher resolution sensors or new lens options—mention this. It may influence the choice of platforms that can scale with your future portfolio.
Logistics preferences are also useful:
- preferred Incoterms and shipping locations;
- need for drop-shipment to different regions;
- packaging requirements and labelling standards.
9. Documentation, test methods and acceptance criteria
Disputes in thermal and LRF projects often arise not from bad faith but from different test methods. A good RFQ therefore outlines how you intend to verify performance.
For example:
- How will you measure detection and recognition range—formal test targets, field trials, or internal guidelines?
- Do you require specific NETD measurements under defined conditions?
- How will range accuracy be tested (calibrated ranges, reflective targets, number of shots)?
- What constitutes an acceptable level of defective pixels or cosmetic blemishes?
If you already have internal quality specifications or acceptance test procedures (ATPs), mention whether you are willing to align them with the supplier’s existing methods. A shared approach can significantly reduce ramp-up time once pilot lots are ready.
10. Budget bands and commercial expectations
RFQs that request “best price” without context usually produce noisy responses. Thermal and LRF systems offer many trade-offs between performance and cost. Providing a budget band gives suppliers a realistic target and helps them propose the most appropriate architecture.
You do not need to disclose exact target prices, but statements such as “we are aiming for an end-customer MSRP of X in market Y” or “module cost should be below Y at volume Z” are helpful.
If you expect certain commercial terms—consignment stock, demo units, or long-term fixed-price agreements—state them as preferences, not hard conditions, so that suppliers can factor them into their proposal clearly.
11. Structuring the RFQ document
For most engineering teams, a simple, consistent structure works best. A practical outline is:
- Project overview and application summary.
- Thermal performance requirements.
- LRF performance requirements (if applicable).
- Mechanical and electrical constraints.
- Environment, reliability and certification needs.
- Lifecycle, volumes and logistics.
- Test methods and acceptance criteria.
- Commercial framework and budget band.
- Attachments (drawings, block diagrams, existing product references).
Even a concise RFQ following this structure allows suppliers like Gemin Optics to evaluate whether a standard platform, a customized thermal camera core or a fully bespoke design is most appropriate.
12. Common mistakes in RFQs for thermal and LRF projects
Several patterns appear repeatedly in RFQs that later cause project difficulties:
- mixing marketing claims (“see 3 km”) with engineering requirements without clarifying test conditions;
- specifying many minor features but omitting environmental or certification constraints;
- copying parameters from a competitor’s datasheet without confirming they are all needed;
- changing key requirements (such as resolution or range) after samples have been ordered, because the initial RFQ did not reflect internal alignment.
Avoiding these issues is often a matter of investing a few extra hours in internal coordination before submitting the RFQ.
13. How Gemin Optics uses a well-written RFQ
When Gemin Optics receives a structured RFQ that covers the elements above, the response typically follows a clear path:
- mapping requirements to existing laser rangefinder modules and thermal platforms;
- identifying any gaps and associated engineering work;
- preparing an architecture proposal with performance estimates and risks;
- outlining a project timeline from ES samples to mass production, similar to the stages described in earlier articles.
This approach shortens the quotation cycle, reduces the need for follow-up questions, and allows both sides to focus early discussions on real trade-offs instead of basic clarification.
14. Conclusion
Writing a good RFQ for thermal and LRF projects is not about producing a perfect document; it is about giving your suppliers enough structured, realistic information to propose the right solution and highlight risks early.
By clearly describing use scenarios, performance targets, interfaces, environment, lifecycle, test methods and budget bands, engineering and procurement teams can significantly increase the chances that first prototypes are close to the real need, and that the project roadmap from concept to shipment is predictable.
For OEMs and brand owners planning new thermal or LRF products, that clarity is often the most cost-effective engineering investment in the entire project.
