A useful GNSS anti-jamming RFQ is more than a product-model request. It gives the engineering team enough verified context to review receiver compatibility, platform integration, installation constraints and the documentation required before a recommendation is made.
The checklist below is intended for commercial vehicle, marine, industrial automation and OEM integration projects. It does not replace an engineering review, and it does not assume performance that has not been documented for the selected configuration.
1. Define the platform and operating context
Start with the platform type and the role of GNSS in the system. State whether the equipment will be installed on a vehicle, vessel, fixed site, industrial machine or another commercial platform. Describe the installation location, available mounting area and any restrictions that affect antenna placement or cable routing.
- Platform type and intended commercial application
- Operating environment and installation location
- Available mounting area, orientation and clearance
- Known sources of blockage, vibration or electromagnetic interference
- Expected quantity and project schedule
2. Identify the receiver and required GNSS signals
Provide the receiver manufacturer and exact model whenever possible. The engineering review should confirm the signals, bands and interfaces used by the receiver rather than infer them from a general platform description.
- Receiver manufacturer, model and firmware context
- GNSS constellations and frequency bands required by the project
- Number of antenna inputs or channels expected by the receiver architecture
- Connector type, impedance and any documented receiver-side requirements
- Required output, control or monitoring interfaces
Do not translate or shorten receiver models, product models, frequency designations or interface names in the RFQ. Exact identifiers reduce the risk of reviewing the wrong configuration.
3. Document mechanical, cable and power constraints
Installation details can determine whether a technically relevant product can be integrated safely into the platform. Include dimensional limits and cable information at the beginning of the review.
- Maximum allowable dimensions and weight
- Cable type, length, routing path and loss information if known
- Connector orientation and service-access constraints
- Available supply voltage, power budget and grounding approach
- Environmental or enclosure requirements that must be verified
If an ingress rating, temperature range, vibration level or other environmental requirement is mandatory, state the required value and ask ResiNav to confirm it against the applicable documentation. Do not assume certification or test coverage from a similar-looking product.
4. Clarify anti-jamming and anti-spoofing scope
State whether the project is reviewing GNSS anti-jamming only or an independent anti-jamming and anti-spoofing product version. Describe the system objective in engineering terms and list the evidence or test documentation required by the project. Avoid using an RFQ to claim an unverified detection range, suppression value or field result.
5. Specify the required documentation
List the documents needed for internal review, integration and purchasing. Depending on the available product documentation, this may include a datasheet, mechanical drawing, connector definition, interface description, installation guidance or a documented configuration summary.
- Datasheet or documented product configuration
- Mechanical drawing and mounting information
- Connector and cable definition
- Electrical and interface information
- Installation and commissioning guidance
- Any project-specific acceptance or review checklist
RFQ information checklist
| Area | Information to provide | Why it matters |
|---|---|---|
| Platform | Type, use case, installation location | Defines the integration context |
| Receiver | Manufacturer, model, required signals and bands | Supports compatibility review |
| Mechanical | Dimensions, mounting, clearance and orientation | Identifies installation constraints |
| Cabling | Connector, cable type, length and routing | Supports interface and loss review |
| Power | Supply, budget and grounding information | Supports electrical integration |
| Documentation | Drawings, interfaces, tests and acceptance needs | Defines the evidence required before selection |
| Commercial | Quantity, schedule and destination | Supports a complete quotation response |
Frequently asked questions
Should an RFQ start with a ResiNav product model?
A product model is useful when already known, but the platform, receiver, signal, mounting, cable and interface information should still be supplied so the configuration can be reviewed.
Can the engineering team recommend a product without the receiver model?
A preliminary discussion is possible, but receiver identification and documented interface requirements are important inputs before confirming compatibility.
Should requested environmental ratings be treated as confirmed?
No. State the required rating or test condition and request confirmation against the documentation for the exact product configuration.
Where should the completed checklist be sent?
Use the Request a Quote page or contact the ResiNav team through the Contact page. Product information can be reviewed in the Products catalogue.
Next step
Prepare the checklist with exact models, units and interfaces, then submit it through the ResiNav RFQ page. The resulting discussion should confirm what is documented for the selected configuration before a purchasing or integration decision is made.
NEXT STEP
Turn available platform information into an engineering review.
Use the Technology centre to frame the discussion, review relevant application scenarios, then send the available platform and receiver details for confirmation.