A promising GNSS configuration is not yet an integration decision. Before a supplier and an OEM can review the same build, they need to agree which interface facts are published, which project inputs the OEM controls, and which evidence will close each open item.
Make the handoff a decision record, not another request list
The OEM defines the platform, receiver, operating context and acceptance criteria. The supplier confirms what its proposed product record and available project documents actually cover. Neither party should treat an unanswered interface field as an agreed design. Use one revision-controlled record so that an update to the receiver, enclosure or required signals reopens only the affected decisions.
Start with the existing custom OEM integration overview for the application boundary. This page addresses the next decision: who supplies each input and what would count as a reviewable answer. For a detailed receiver timing and serial-port handoff, use the separate receiver interface-control guide.
| Boundary | OEM-controlled input | Supplier question | Evidence to close the decision |
|---|---|---|---|
| Required GNSS signals | Receiver model, bands and constellations required by the application. | Which signals are documented for the exact proposed configuration? | Model-specific product record, document revision and written resolution of any difference. |
| RF and receiver boundary | Receiver input architecture, cable route, RF loss budget and any existing front-end constraints. | What outputs, connectors and interface details can be confirmed for this configuration? | Agreed connection drawing or interface record, plus identified open values. |
| Mechanical and environment | Mounting surface, available envelope, service access, vibration and exposure requirements. | Which published dimensions and project-specific installation information apply? | Approved fit check and installation drawing; environmental evidence only if actually supplied. |
| Power and control | Available input power, protection, startup sequence and controller fault response. | Which electrical and status behaviors are documented for the proposed unit? | Reviewed power/interface limits and a controller response or test plan. |
| Acceptance and change control | Operating scenarios, acceptance criteria, test owner and configuration revision. | What test conditions and deliverables can be agreed before approval? | Signed review disposition naming the responsible party and unresolved conditions. |
Use three release gates
1. Screen the published record
Identify the exact model, available product datasheet and revision. Check the listed signals, dimensions and electrical limits against the OEM’s must-have requirements. A missing field means not yet confirmed; it does not mean either supported or unsupported. The public datasheet directory is a starting point, not an assurance that every project-specific drawing or test report exists.
2. Resolve interface ownership
For every connector, cable, power rail and data consumer, name the party who supplies the input and the party who confirms the proposed output. Record the expected file or drawing, its revision and the date needed for the design gate. If the interface is not published, ask whether it can be supplied for the exact configuration before treating the mechanical or electrical design as released.
3. Approve the configuration to be tested
Freeze the receiver version, product configuration, mounting arrangement and test conditions for the evaluation. Specify what evidence will support acceptance, who will interpret it and which change would require a retest. This is an engineering agreement to evaluate a defined build, not a claim that an OEM deployment, certification or performance target has already been achieved. The separate documentation-package guide helps assess whether supplied documents are complete enough for that gate.
What to send for an initial engineering review
Send the platform and receiver identification, required bands, available installation envelope, RF and power interface constraints, required evidence, intended quantity and decision schedule. Mark each item as documented, OEM-provided, supplier-to-confirm or open. This short status is more useful than an unqualified request for “full compatibility.”
Discuss an OEM GNSS configuration with the existing platform and interface information. The supplier can then identify which published product record is relevant and what still needs project-specific confirmation.
Frequently asked questions
Can an OEM project be assigned a model from a webpage alone?
No. Platform interfaces, receiver architecture, installation and verified product documentation require engineering confirmation.
What makes a documentation handoff useful?
Clear platform, receiver, interface, mounting, power, quantity and schedule information lets the team identify the open review items quickly.
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.