The OEM ultrasound partner checklist
- Imaging performance you can verify. Request images and test data from a comparable configuration. Specify penetration, resolution, field of view, frame rate and required modes under stated conditions. Define evaluation criteria before reviewing the results; a favorable demonstration is not clinical validation.
- Probe and transducer fit. Record probe geometry, frequency and bandwidth, active channels, multiplexing, transmit limits, connector mapping and receive sensitivity. Ask who verifies the probe-to-engine interface and who owns calibration.
- Processing architecture and data access. Ask where acquisition, beamforming and reconstruction run, and measure latency, throughput, power and transfer costs. FPGA/GPU is one architecture choice, not a universal requirement. Raw channel RF, channel IQ, beamformed IQ and displayed images are different deliverables; specify which you need.
- Documentation and regulatory responsibilities. Agree design records, requirements traceability, risk-management inputs and verification evidence. Establish the legal manufacturer, submission owner and applicable pathway. A supplier's documentation or certification does not automatically clear the finished product.
- A realistic roadmap. Test future requirements against processing, power, thermal, data-link and probe limits. Do not assume a handheld architecture scales to a cart, or that a new mode requires only a software update.
- IP, licensing and transfer. Clarify background IP, new design ownership, source-code access, third-party dependencies and permitted uses. Board supply and technology transfer are different engagements; define what is transferable, with which support and rights.
- Support and supply. Agree engineering contacts, response expectations, lead times, component lifecycle, replacement policy, production tests and maintenance. Put service levels in the contract rather than assuming a response-time promise.
Component supplier or integrated engineering partner?
| Question | Component supply | Integrated program |
|---|---|---|
| Scope | A defined part, board, probe or software module | Multiple device layers with an agreed system specification |
| Integration | The customer coordinates interfaces outside the supplied scope | Interface ownership is assigned within the program |
| Evidence | Component evidence may need additional system-level tests | The program can coordinate component and system verification |
| Transfer | Depends on the supply contract and IP rights | Depends on the agreed transfer package and IP rights |
Either model can work. An integrated program can reduce coordination gaps, but the benefit depends on clear scope, expertise and measured delivery. It does not remove the customer's finished-device obligations.
Where ALEVA fits
ALEVA's engineering scope connects custom probe design, FPGA/GPU beamforming, electronics, imaging software, industrial and mechanical design, documentation support and manufacturing transfer. The turnkey development guide explains the seven layers. Agree available configurations and deliverables for your particular product.
Evaluate before committing
- Write the same brief for each candidate. Include application, probe, modes, host, data outputs and constraints.
- Agree an evaluation plan. Use comparable conditions and predeclared acceptance criteria.
- Review evidence and responsibilities. Distinguish demonstrated performance from roadmap items and proposed work.
- Close the commercial scope. Define milestones, documentation, IP, supply, support and transfer terms.
Explore the OEM development guides
Frequently asked questions
Questions and answers
What should I look for in an OEM ultrasound partner?
Look for verifiable imaging performance, probe-to-engine compatibility, appropriate architecture and data interfaces, agreed documentation, realistic supply and support, and clear IP terms. Define acceptance criteria and interface responsibilities before evaluation.
Is one integrated partner always better than multiple suppliers?
No. Both models can work. An integrated partner can coordinate more interfaces, while specialist suppliers may suit a narrower scope. Compare evidence, responsibilities, expertise and commercial terms rather than assuming either model eliminates risk.
Can we start with board supply and later transfer the design?
Potentially, if the agreed design, licensing and support terms permit it. Define transfer deliverables, source access, background IP and manufacturing responsibilities before choosing the supply model.
Does an OEM partner provide regulatory approval?
Not automatically. Engineering documentation can support a submission, but finished-device clearance or conformity assessment and clinical validation remain specific to the product, intended use and market. Agree those responsibilities explicitly.
How should we evaluate imaging quality?
Use a configuration comparable to your intended product and a test plan with stated conditions and acceptance limits. Review images alongside measured performance, metadata and limitations; plan any required clinical validation separately.
Discuss your ultrasound requirements.
Define the engineering scope, evidence and responsibilities for your product.
Discuss your project →