Home / Ultrasound OEM / Engineering guide

OEM · Partner selection

How to choose an OEM ultrasound partner

Choose an ultrasound partner by evidence and fit, not a list of advertised modes. The probe, acquisition electronics, beamformer, software and enclosure must work together—and each interface needs an owner. Use this checklist to define a comparable evaluation before you commit.

The OEM ultrasound partner checklist

  1. 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.
  2. 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.
  3. 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.
  4. 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.
  5. 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.
  6. 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.
  7. 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?

Responsibility models to compare—not a ranking of suppliers.
QuestionComponent supplyIntegrated program
ScopeA defined part, board, probe or software moduleMultiple device layers with an agreed system specification
IntegrationThe customer coordinates interfaces outside the supplied scopeInterface ownership is assigned within the program
EvidenceComponent evidence may need additional system-level testsThe program can coordinate component and system verification
TransferDepends on the supply contract and IP rightsDepends 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 supports project-specific development across probe design, FPGA/GPU beamforming, electronics, embedded imaging software, enclosure design and manufacturing transfer. Review the ALEVA OEM engineering scope against your brief, then use the turnkey development guide to plan the interfaces and handovers. Agree the supplied configuration, evidence, responsibilities and usage rights for your project.

Evaluate before committing

  1. Request a scope and interface record. List each customer-supplied and supplier-supplied subsystem, its inputs and outputs, the owner of integration, and unresolved assumptions. Compare candidates against the same product brief.
  2. Request a configuration-specific evaluation record. Identify the probe, active channels, acquisition mode, output format, host and software revision. Record the test method, acceptance limit and measured result together; label simulated or proposed results separately.
  3. Request a handover and rights list. Identify the design files, interface documents, software access, test procedures and manufacturing information included in the offer. State licensing limits, third-party dependencies and responsibilities for future changes.
  4. Request a production-readiness plan. Distinguish prototype acceptance, pilot-build work and repeat supply. Identify the remaining calibration, inspection, traceability and component-lifecycle decisions, with an owner for each open item.

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 →