The complete device
What does turnkey ultrasound development include?
Turnkey describes a coordinated development scope, not a universal off-the-shelf configuration. Start with the intended use and measurable requirements, then agree which layers ALEVA supplies, which the customer supplies, and what evidence is required at each handover.
| Layer | Engineering scope | Deliverables to agree |
|---|---|---|
| Probe and transducer | Custom or adapted probe engineering through iProbe; acoustic and electrical integration. | Geometry, frequency, channel mapping, acoustic tests, connector and manufacturing requirements. |
| Imaging engine | FPGA/GPU acquisition, beamforming and image-processing architecture. | Timing, interfaces, throughput, latency, calibration and the selected imaging configuration. |
| System electronics | Transmit and receive front ends, control, power, protection and host connectivity. | Board design, power and thermal budgets, electrical verification and integration tests. |
| Software | Acquisition control, processing, user interfaces and agreed imaging or research functions. | Supported modes, APIs, RF/IQ or image outputs, software verification and maintenance responsibilities. |
| Industrial and mechanical design | Product enclosure, ergonomics, internal packaging, thermal integration and serviceability. | Mechanical CAD, prototype enclosure, materials, assembly and manufacturability requirements. |
| Verification and regulatory documentation | Engineering records and test evidence supporting the finished-device submission strategy. | Requirements traceability, agreed verification reports, risk-management inputs and the documentation handover. |
| Manufacturing and technology transfer | Production preparation, assembly guidance, test procedures and an agreed supply or transfer model. | Production files, acceptance tests, calibration procedures, ownership and licensing terms. |
Individual capabilities are not promises of every mode, channel count or certification in every product. Performance, scope, acceptance criteria, commercial terms and responsibilities must be specified for the selected device.
Design the interfaces, not just the parts
Why a coordinated program can reduce integration risk
Separately capable subsystems do not necessarily make a verified device. The probe affects transmit drive and receive sensitivity; acquisition timing affects beamforming; data access affects link bandwidth; and the enclosure affects heat, handling and serviceability.
One system specification
Keep probe, electronics, firmware, processing and enclosure requirements aligned. Assign an owner to each interface rather than leaving compatibility implicit.
Evidence at each handover
Define test methods and acceptance limits before evaluation. Carry verification records forward so production and submission teams can trace what was measured.
Manufacturing from the outset
Consider assembly, calibration, production tests and service access during development—not only after the prototype produces an image.
A scope that fits your team
Start with a subsystem or a broader program. Document customer inputs, supply obligations, intellectual-property rights and transfer conditions.
Coordination can reduce interface risk; it does not eliminate technical uncertainty or guarantee a cost, schedule, regulatory outcome or clinical performance.
From requirements to transfer
A staged development process
- Discovery and specification. Define intended use, probe, imaging requirements, host, enclosure, budget and evidence needed. Agree the work packages and responsibilities.
- Architecture, design and simulation. Establish acquisition and processing architecture, probe interfaces, electronics, mechanical packaging and verification methods.
- Prototype and verification. Evaluate imaging, acoustic output, timing, data movement, power, thermal and mechanical behavior against the agreed requirements. Clinical validation, when needed, is a separate planned activity.
- Documentation and production transfer. Deliver the agreed design and test records, production and calibration procedures, and supply or technology-transfer package. Track unresolved risks and remaining finished-device obligations.
Engineering documentation for the regulatory pathway
Regulatory documentation is part of the development plan, not a substitute for finished-device clearance or conformity assessment. The applicable pathway depends on the device, intended use and market. The legal manufacturer and submission responsibilities should be agreed at the beginning of the program.
ALEVA's documentation scope can support that work through agreed design records and verification evidence. It does not, by itself, establish FDA clearance, CE marking, certification or clinical validation. See the FDA's 510(k) overview and the European Commission's medical-device regulatory overview for the relevant regulatory context.
Explore the ultrasound engineering stack
Explore the OEM development guides
Frequently asked questions
Turnkey development questions
What does turnkey ultrasound device development mean?
It means coordinating the probe, imaging engine, electronics, software, enclosure, verification documentation and manufacturing transfer within an agreed device-development program. The scope and responsibilities must be defined for the particular product.
Can the scope include industrial design of the enclosure?
Yes. Industrial and mechanical design can be included alongside the ultrasound electronics and software, covering ergonomics, packaging, thermal integration, assembly and serviceability. Deliverables are agreed for the project.
Does a turnkey program include regulatory approval?
Not automatically. Agreed engineering records and verification evidence can support a finished-device submission. Clearance or conformity assessment, clinical validation and the legal manufacturer's responsibilities must be established for the device, intended use and target market.
Can we begin with a subsystem rather than a complete device?
Yes. A program can begin with probe engineering, an imaging engine or another defined subsystem. Compatibility, interfaces, support, intellectual-property rights and later transfer requirements should be agreed before development.
What should we provide before discussing a program?
Share the intended use, target markets, probe requirements, imaging modes, depth and field of view, host platform, data-access needs, enclosure constraints, schedule and budget. These inputs help define a realistic engineering scope and verification plan.
Define the complete device program.
Bring your application and engineering requirements. Together, we can map the interfaces, work packages, evidence and responsibilities from probe to product.
Discuss your project →Read more engineering articles →