A GNSS anti-jamming antenna or terminal is part of a larger signal, receiver and platform boundary. The product label alone cannot confirm that a configuration is appropriate for a particular installation. Before an engineering discussion, the project team should make the proposed mounting position, signal path, power arrangement and downstream interface visible in a short, traceable documentation package.
This checklist is written for commercial and industrial platform teams. It explains what to prepare before requesting a technical review. It does not certify an installation, predict field performance or replace receiver, platform and environmental validation.
1. Identify the platform and the navigation role
Start with a concise description of the platform rather than a generic request for the highest specification. Record the platform type, the navigation task, the intended operating context and the organisation responsible for the mechanical drawing, receiver configuration and control-system interface.
The purpose is to give the review team enough context to distinguish documented requirements from information that still needs confirmation. A vehicle, a commercial marine platform, an industrial installation and a mobile mapping workflow can all use GNSS, but the installation boundary and evidence package may be different.
For application context, review the ResiNav Applications hub before choosing a candidate product family.
2. Document the proposed mounting boundary
Provide a drawing or annotated image showing the proposed antenna or terminal location. Include the available mounting surface, orientation assumptions, nearby structures, service access and the relevant physical clearance. If the location is still being selected, show the alternatives rather than presenting an assumption as a final design.
- Platform drawing or clear installation photograph.
- Proposed equipment position and mounting interface.
- Nearby structures, housings, antennas or radio equipment.
- Access needed for installation and service.
- Known environmental or mechanical constraints relevant to the project.
This record does not establish final suitability. It makes the physical boundary reviewable.
3. Map the RF and cable route
The cable route is an engineering input, not a finishing detail. Record the anticipated route from the antenna or terminal to the receiver, including approximate length, connector interfaces, penetrations, protection points and nearby equipment. Keep observed facts separate from assumptions that require confirmation.
Where multiple cable paths are possible, identify the preferred route and the reason it was selected. This helps a review cover the entire path rather than only the end devices.
For a broader signal-environment checklist, see GNSS Interference Environment: What to Document Before Integration.
4. Confirm receiver and interface information
The receiver model, required constellations and bands, documented RF interfaces and relevant navigation/data outputs should be available before a configuration is reviewed. Do not infer receiver compatibility from a product category or from a photograph.
Also document the platform power path, available connector types, grounding approach and the system or team that consumes the navigation data. These inputs help connect the physical installation to the navigation workflow.
For the complete engineering boundary, read the Antenna–Receiver–Platform Integration Guide.
5. Keep product information and project constraints distinct
Product data should come from verified records. Project requirements come from the receiver, the platform, the installation and the intended workflow. Keep those two groups separate in the documentation package. If a product parameter, interface or delivery item is not publicly documented, flag it for engineering confirmation instead of filling the gap with an assumption.
The Product Catalogue is the appropriate starting point for reviewing the published product families. Element count and channel count should be used as part of a larger requirement set, not as standalone proof that a configuration will meet an operational need.
6. Assemble a concise review package
Before sending an enquiry, compile the following material in one place:
- Platform description and navigation role.
- Receiver model, required constellations/bands and documented interfaces.
- Mounting drawing or annotated image.
- Proposed cable route, connector notes and available installation space.
- Power, grounding and downstream data-interface information.
- Quantity, project timing and unresolved questions for the review.
This package creates a more useful starting point than an unqualified request for a product recommendation. It allows the discussion to focus on documented integration constraints and on the evidence still needed for a candidate configuration.
Request an engineering review
When the available drawings, receiver details and installation constraints have been collected, submit them through the Request a Quote form. ResiNav can then review the relevant product information with the receiver and platform inputs provided. Final configuration remains subject to engineering review.
FAQ
Does this checklist approve a GNSS installation?
No. It organises the information required for a technical review; it is not a certification or a performance guarantee.
Should a product be chosen before the installation drawing is available?
A preliminary product family can be discussed, but a documented mounting, receiver and interface boundary is needed before a candidate configuration can be reviewed responsibly.
Are cable length and connector details important at the RFQ stage?
They are useful review inputs. Record known information and identify anything that still needs confirmation.
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.