The purchasing question
What does the supplier deliver for each vehicle platform?A vehicle count cannot distinguish a standalone module from electronics integrated into a broader system. The contract boundary determines the revenue unit.
| Compare | Examine | Why it matters |
|---|---|---|
| Hardware | Sound output, electronics and enclosure | Content delivered per vehicle |
| Control and sound | Vehicle-state inputs and sound behaviour | Software, calibration and integration work |
| Programme | Platform variants and production timing | Engineering revenue versus recurring unit supply |
The alert is a vehicle-level function.
Microchip describes AVAS as a system that alerts pedestrians to electric-drive vehicles at low speed and presents electronics for implementing it. [1] The audible result depends on both sound output and the control architecture that determines when and how the sound is produced.
Keep this external pedestrian-alerting function separate from in-cabin sound experiences. Similar audio technology does not make them the same product or purchasing requirement.
The product boundary changes supplier content.
A supplier may deliver a standalone module, a sound-output component or electronics integrated into a wider control unit. Compare the actual contract scope and bill of materials before applying a common revenue-per-vehicle assumption.
Reusing control electronics can change separately purchased hardware content without removing the function. Vehicle growth and module growth can therefore diverge as platforms adopt different architectures.
Development and unit supply have different clocks.
HARMAN’s 2019 HALOsonic discussion describes exterior sound synthesis alongside other active sound-management functions. [2] It provides a dated example of combined sound-system scope, rather than a current deployment count.
Platform engineering, sound design, calibration and validation occur around programme milestones. Recurring module supply follows production. Track engineering contracts separately from units shipped and retain the platform’s variant mix.
Compare delivered content for a fixed platform.
List the hardware, embedded functions, calibration work and ongoing support included in each offer. Then connect the applicable platforms to production timing and supplier awards.
A price movement may reflect a change in content or the removal of a separate module. Reconcile that architecture change before interpreting the movement as a like-for-like reduction in component value.
Sources & scope
The sources establish function and system examples. Contract boundaries and platform revenue implications are APO analysis.
- Microchip — acoustic vehicle alerting system
Function and electronics context; reviewed 3 October 2026.
- HARMAN — the sound of safety
Historical sound-system example, 2019; no current regulatory or deployment claim inferred.
A question about your market?
Discuss the product, application or geography you need the research to cover.
Discuss your research needs