You do not need every connector or test result before contacting a supplier. You do need to distinguish a requirement from a guess. A model name without receiver, signal, mounting, interface and project context may lead to an answer that cannot be evaluated. Mark an unknown explicitly so the supplier knows what to clarify.
Start with the decision the quotation must support
State whether you are screening a published product, requesting a sample for engineering evaluation or discussing an unresolved OEM integration condition. An evaluation-unit quotation is not approval for a production installation. Tell the supplier what the next decision requires.
Review the published product catalogue before naming a model. It separates anti-jamming terminals from independent anti-jamming and anti-spoofing versions. For example, RN-S65-4CH-SNB is in the terminal family, while RN2501-AJS-4CH-DPA is a separate anti-jamming and anti-spoofing version. These are catalogue examples, not platform recommendations. If you do not yet have a model, describe the requirement instead.
Copyable GNSS project-input brief
Select and copy the text below into your project note, then put the relevant details in the optional message field on the RFQ form. The form separately collects business contact, country and quantity. Mark unknown items “to be confirmed”; do not put personal information in a URL.
PROJECT AND DECISION Platform / application: [type and operating role] Project stage: [screening / sample evaluation / production review] Decision this request must support: [shortlist / interface review / quotation / other] Target quantity and timing: [prototype quantity, expected volume, decision date] Destination market and project-required standards: [state requirements; do not assume certification] RECEIVER AND SIGNALS Receiver manufacturer, exact model and firmware: [known / to be confirmed] Required constellations and frequency bands: [list exact signals] Receiver antenna-input and RF expectations: [documented values / to be confirmed] Anti-jamming requirement: [project objective and proposed evaluation] Separate anti-spoofing requirement: [behaviour and evidence / not in scope] INSTALLATION AND INTERFACES Mounting envelope and orientation: [drawing or dimensions] Sky view, nearby structures, cable route and service access: [known constraints] RF connector, cable type/length and loss budget: [known / to be confirmed] Supply, grounding, power budget and data/control interface: [known / to be confirmed] Environmental conditions and required evidence: [project inputs] SUPPLIER RESPONSE REQUESTED Exact proposed model and configuration identity: [supplier to state] Applicable document title and revision: [supplier to state] Published facts versus project-dependent items: [supplier to separate] Open interface, installation or compatibility questions: [supplier to list] Evaluation method, acceptance evidence and next decision: [agree before approval]
This brief is a working aid, not a technical specification or an automatic compatibility test. Use an approved channel for drawings or sensitive project files.
What to know now, and what to ask next
A missing production quantity may prevent a firm commercial quote; an unknown receiver RF boundary may prevent an engineering fit assessment. Keep these gaps separate.
| Input | Buyer should provide | Supplier should confirm | If unresolved |
|---|---|---|---|
| Receiver and signals | Exact receiver where known; required constellations and bands | Configuration and interface scope for that boundary | Limit the discussion to conditional screening |
| Physical installation | Envelope, orientation, cable route and access | Applicable drawing and mounting assumptions | Do not treat headline dimensions as installation approval |
| Electrical and data path | Power, grounding and RF/data/control boundary | Connector, electrical and interface documents for the exact item | List the missing definition before sample evaluation |
| Environment and acceptance | Project conditions and required evidence | Applicable documented limits, tests and revisions | Do not claim an unlisted rating or guaranteed outcome |
| Commercial scope | Quantity, schedule, destination and quotation stage | Quoted item identity, exclusions and dependencies | Request a qualified rather than unconditional price |
Ask for a traceable supplier answer
A useful response identifies the proposed item and separates current published facts, data for the exact proposed configuration and open project assumptions. If a drawing, revision or interface definition determines the decision, request that item by name. The data-sheet guide helps distinguish published fields from questions for the supplier. For the subsequent approval decision, use the GNSS integration documentation package review. This page prepares the buyer’s request before document review.
Before you send
- Name the decision: shortlist, sample evaluation or production discussion.
- Identify the receiver and signals, or mark them unknown.
- Define the antenna or terminal boundary with the receiver and platform.
- Separate installation and environmental requirements from published product values.
- Ask for configuration identity, document revision, open items and next-step evidence.
For an unresolved architecture, see the Custom OEM integration guide. If a published record appears relevant, include its exact model URL and the facts you want confirmed. Use the existing RFQ form to send the request.
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
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.