Product-Based Supplier Capability Overview
Capability Bar Chart
Displays the top 2 performing suppliers for each product category, ranked by their capability scores based on VEM level assessments across technical functions.
Scoring Formula (HC Savings):
Scores represent Headcount (HC) savings. Higher scores indicate greater resource efficiency and reduced engagement requirements.
Supplier Legend
Hover over legend items to highlight corresponding bars in the chart
Each bar shows supplier name and score on the right side
Click on product names to jump to Product Function Analysis
Product Function Analysis
Select a product to view each supplier's capability scores across different technical functions. The radar charts show VEM level scores together with average scores.
Supplier Score Comparison: 2024 vs 2025
Interactive Supplier Selection
Click on a supplier below to view their 2024 vs 2025 score comparison
Chart Information:
Shows 2024 (dashed line) vs 2025 (solid line) scores for the selected supplier across 8 technical domains.
Scores are based on the overview page scoring rules: ULE(100), L VEM(80), M VEM(60), H VEM(20)
Supplier Technical Capability Assessment Matrix
| Category | Product | HQ DB2 | HQ DB1 | GTK | CNT | FIH | GGEC | ||||||||||||||||||||||||||||||||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Audio HW | Audio SW | Camera | DOT | Sensor | Wireless | Production Test | SW Infra | Audio HW | Audio SW | Camera | DOT | Sensor | Wireless | Production Test | SW Infra | Audio HW | Audio SW | Camera | DOT | Sensor | Wireless | Production Test | SW Infra | Audio HW | Audio SW | Camera | DOT | Sensor | Wireless | Production Test | SW Infra | Audio HW | Audio SW | Camera | DOT | Sensor | Wireless | Production Test | SW Infra | Audio HW | Audio SW | Camera | DOT | Sensor | Wireless | Production Test | SW Infra | ||
HQ-DB1 (Category: Hearable)
Evaluation Result:
HQ-DB1 does not qualify as an ULE partner for four critical reasons:
- Sensor testing fixtures are mostly manual operating, bench automation and fixture spec can be observed as a gap to Amazon standard
- New sensors like mid-IR proximity sensor with skin detection function and BIO sensors need further study to support
- Lack of wireless systematic risk evaluation
- No experience to do correlation on ARF-OTA performance for running effectively FA on antenna/ARF issue during NPI
ULE Mitigation Plan:
ULE Design Playbook
- Establish a playbook mechanism and conduct daily design review sessions with key stakeholders before EVT RR to ensure all technical requirements and specifications are met.
Suggestion:
JDM (M VEM) before EVT RR
HQ-DB2 (Category: General)
Evaluation Result:
HQ-DB2 is an ULE partner for Echo, eReader, and Tablet products. However, they must provide a robust solution to ensure compliance with BRD standards during their transition to HW Specifications. Additionally, HQ-DB2 needs to implement preventive measures to avoid similar compliance issues in future projects.
ULE Mitigation Plan:
ULE Design Playbook
- Amazon connectivity design team can develop a ULE playbook and scheduled design reviews before the EVT RR.
Suggestion:
JDM (L VEM) before EVT RR
GTK (Category: General)
Evaluation Result:
GTK does not qualify as an ULE partner for six critical reasons:
- Camera does not have IQ advanced feature tuning, subjective & objective tuning, and AIISP tuning methodand
- Current labs are not sufficient to support MTK/Qualcomm ISP tuning, no DNP light source, and the camera labs are not qualified by Amazon yet
- Sensor is missing Accel test bench, P-Sensor Test bench, and TOF Test bench Develop
- GTK wireless design and production capability could not offload NTI loading, such as radar, A2S, and simulation requirements
- No experience on Complex issue Troubleshooting Capability improvement-De-sense
- No DOT qualified Sr. engineers and No pDOT design, testing, and validation experience
ULE Mitigation Plan:
ULE Design Playbook
- Establish a standardized Hardware (HW) specification mechanism and begin implementation with the JDM to ensure alignment on technical requirements and quality standards.
- For Eacho Core and Entry Vnext, we developed a ULE playbook and scheduled design reviews before the EVT RR
Suggestion:
JDM (M VEM) before EVT RR
CNT (Category: General)
Evaluation Result:
CNT, with over 10 years of experience working with Amazon on OEM business models, specializes in SMP-TV Stick projects. To support CNT's transition to an independent ULE model for the SMP-TV Stick, Amazon connectivity design team has developed a ULE playbook and scheduled design reviews before the EVT RR. Based on this preparation, CNT has been awarded the Mercer project (next generation TV stick) under the ULE model.
ULE Mitigation Plan:
ULE Design Playbook
- Amazon connectivity design team can develop a ULE playbook and scheduled design reviews before the EVT RR.
Suggestion:
JDM (L VEM) before EVT RR
FIH (Category: General)
Evaluation Result:
FIH-General does not qualify as an ULE partner for three critical reasons:
- No qualified team involvement in Brioche project design
- Laboratory infrastructure not established prior to Brioche engagement
- Recently hired senior engineers lack Amazon DRIs validation
ULE Mitigation Plan:
ULE Design Playbook
1. Validation Level Adjustment
- Increase Amazon VEM requirement to Mid/High
- Leverage Amazon R&D resources for schedule adherence
2. Laboratory Resource Optimization
- Utilize existing Amazon laboratory facilities
- Require EMS to reduce device MVA
- Eliminate delays from EMS lab setup
3. Engineering Qualification Process
- Verify device simulation expertise of EMS senior engineers
- Complete Amazon DRI qualification before RFQ release
OEM-to-ULE Conversion Plan:
- EMS laboratory must complete setup
- All Sr. engineers must secure capability validation from Amazon DRIs
- Obtain Amazon laboratory certification
Suggestion:
OEM
FIH (Category: Seabright and Stinson)
Evaluation Result:
FIH-Seabright and Stinson do not qualify as an ULE partner for four critical reasons:
- High engagement for camera since it has V0 features (night mode)
- Sensor needs re-architect RGB sensor (inferencing with camera night mode IR LED as well) and supports omnisense
- Wireless has new WiFi radar feature (2T|1R) and use new WiFi Chip IC 7903
- No ability to develop Production HW (Chamber) and SW (WFT)
ULE Mitigation Plan:
Hardware specification mechanism
- Establish a standardized Hardware (HW) specification mechanism and begin implementation with the JDM to ensure alignment on technical requirements and quality standards.
Suggestion:
OEM
GGEC (Category: Hearable)
Evaluation Result:
GGEC does not qualify as an ULE partner for eight critical reasons:
- Sensor has gap in function characterization, device bench testing fixtures, manual or automatic
- GGEC will need AMZ team's support to build sensor lab and related capability
- New sensors like mid-IR proximity sensor with skin detection function and BIO sensors need further study to support
- Lack of wireless systematic risk evaluation
- Minimal SAR testing experience and Not familiar with FCC/CE SAR test waiver conditions for TWS
- No expereience to do corerlation on ARF-OTA performance for running effectively FA on antenna/ARF issue during NPI
- No dedicated sensor validation capabilities, desense validation(Spectrum capture), and cross body effect validation
- Not familiar with Amazon production testing requirement
ULE Mitigation Plan:
Hardware specification mechanism
- Establish a standardized Hardware (HW) specification mechanism and begin implementation with the JDM to ensure alignment on technical requirements and quality standards.
Suggestion:
JDM (M VEM)
Technical Domain Detailed Information
Audio SW Domain
HQ DB1 Assessment
- Anechoic chamber owned by the BU, can share labs from other BUs
- All required equipment available (HATS, ACQUA, 3QUEST, Soundcheck, AudioPrecision)
- Experience in all kinds of earbuds and wearable products
- Experience in tuning ANC, EQ algorithms
- Experience in major earbuds solutions
- Following same procedure as other BUs working with Amazon
- No ETSI room nor Listening room
- Lack of ASR experiences
- Limited experience in ASR (Subjective only) and VoIP
GGEC Assessment
- Certified chamber following multiple international standards
- Extensive experiences in ANC, ENC tuning and algorithm design
- In-house playback algorithm (GSound)
- Strong tuning capability in adaptive ANC ENC and EQ algorithms
- Cross productline software stack experience
- No ETSI room nor Listening room
- No ACQUA nor 3QUEST equipment
- No more than two dedicated audio software engineers
- Lack of ASR VoIP experiences
- Does not follow well defined PDP procedure in software dev/release
Sensor Domain
- Wearable products are High engagement for all EMS due to complexity
- HQ: Tablet is already ULE in sensor domain
- GTK: Turn eReader and Tablet to Mid as they have never touched those models
- CNT: Lacks sensor characterization equipment and Amazon sensor program experience
- FIH: Tablet is Mid as they have never been awarded a tablet program
HQ DB1 Assessment
- Familiar with common sensors in TWS products (hall, capacitive, IR proximity, IMU, resistive pressure)
- EE design team capable of chip selection, architecture design, sensor system level simulation
- Experience in sensor SMT/FATP testing support, calibration, tuning, FA and device bench testing
- Lab fixtures and process cover sensor testing requirements and OBA testing
- Gap in algorithm development and evaluation
- Sensor testing fixtures mostly manual operating
- Bench automation and fixture spec gaps to Amazon standard
- New sensors (mid-IR proximity with skin detection, BIO sensors) need further study
GGEC Assessment
- EE HW design team familiar with common TWS sensors
- Capable of chip selection, architecture design, sensor system level simulation
- Demonstrated in-house and 3rd party algorithm development capability
- Gap in sensor function characterization and device bench testing fixtures
- Need Amazon team support to build sensor lab and related capability
- New sensors (mid-IR proximity with skin detection, BIO sensors) need further study
VEM depends on system requirements case by case. Complex sensor stacks may change VEM from Low to Mid/High.
Wireless Domain
HQ DB1 Assessment
- Antenna design analysis and simulation falling short of Amazon expectations
- No experience evaluating worst case scenarios (human cross body impact, component variations)
- Only used CST default head model, not aligned with P10 model standard
- No human cross body simulation and validation capability
- No CTIA standard antenna OTA chamber in factory/lab (sharing Mini/Micro chambers with BD2)
- No significant experience in ARF-OTA performance correlation for effective FA during NPI
- HQ DB1 team not familiar with Amazon RF&Desense design PDP
- Desense simulation capability rarely used for risk evaluation
- Desense risk assessment relies on experience, lacks systematic evaluation
- No consideration of antenna detune risk in ARF station factory testing
GGEC Assessment
- Lacks experience in worst-case scenario evaluation
- P10 head model parameters not aligned with standard (using default CST settings)
- No human cross-body simulation and validation capabilities
- Limited ARF spec window setting experience and antenna performance correlation
- Minimal SAR testing experience, unfamiliar with FCC/CE SAR test waiver conditions for TWS
- Insufficient ARF-OTA performance correlation experience for NPI FA
- Unable to develop solid high-level validation schedule from Amazon wireless HW specs
- Only one MVG SG24 OTA Chamber in R&D lab, lacks factory-based OTA chambers
- Insufficient knowledge of 3D-printed mockup materials (SLA, PLA, PTEG, PC, ABS)
- Poor CSE/RSE design and failure analysis capability
- No ZigBee signaling equipment and power table experience
- Poor desense validation capability, not following Amazon standards
- Poor coex design capability (best performance: 25dB isolation between 2.4GHz and ZigBee)
- Poor systematic desense design capability
Validation Domain
GGEC Assessment
Basic validation facilities (OTA chamber, shielding room, required instruments)
OTA, antenna performance, conducted testing for RF basic performance and pre-compliance
Test limits problematic (conducted spurious emission limit only -40dBm/MHz, likely causing radiated compliance failure)
No dedicated desense test station, no validation plan for wearable devices, no cross body analysis capability
- No dedicated sensor validation capabilities
- No dedicated sensor engineer for validation
- No validation setup or plan for various sensors
- GGEC has almost all required equipment for HW validation
- Refer to Audio SW assessment for detailed capabilities
- Available: Basic EE validation facilities
- Capabilities: PI/PDN/SI/Ripple simulation and measurement
- Need evaluation: Sophisticated layout and PCB stackup planning integration capability
Production Test Domain
| Supplier | Score | Engagement Level | HC Needed |
|---|---|---|---|
| HQ | 88 | Low Engagement | 0.2 |
| GTK | 88 | Low Engagement | 0.2 |
| CNT | 88 | Low Engagement | 0.2 |
| Ensky (FIH) | 88 | Low Engagement | 0.2 |
| GGEC | 81 | Medium Engagement | 0.5 |
HQ-DB1 Detailed Assessment
- Experience in comprehensive device testing for large-scale manufacturing
- Proficient in implementing Presto testing systems in production environments
- Expertise in standardized quality control procedures
- Efficient engineering resource management for testing operations
- Perfect scores in Equipment, Human Resource, Maintenance, Automation, and Failure Analysis (100%)
- Limited ARF chamber capabilities prevent comprehensive design validation during NPI
- Experience category scored only 52% due to fixture design capability gaps
- Need collaboration with Lab126 Production Engineering team for holder design optimization
GGEC Detailed Assessment
- Experience in comprehensive device testing for large-scale manufacturing
- Proficient in operating RF equipment for troubleshooting and annual calibration
- Expertise in standardized quality control procedures
- Perfect scores in Equipment, Human Resource, Maintenance, Automation, and Failure Analysis (100%)
- Lack of ARF chamber design capabilities prevent comprehensive design validation during NPI
- Experience category scored only 36% due to significant fixture design capability gaps
- Need collaboration with Lab126 Production Engineering team for holder design and antenna placement optimization
- 95-100: Ultra Low Engagement (ULE)
- 86-95: Low Engagement (LE)
- 76-85: Mid Engagement (ME)
- 61-75: High Engagement (HE)
- <60: Disqualified
SW Infra Domain
HQ NC DB1 Assessment
- Comprehensive test station support through I-Far platform
- Multi-chipset compatibility for various TWS solutions
- Lacks RF signaling test software development experience
- I-Far test platform only supports Non-Signaling tests
- Presto RF test instrument not included in current test platform (needs upgrade)
- I-Far platform does not support BT Tx calibration (needs upgrade)
GGEC Assessment
- Lacks resources to support factory line test tool development
- Only one software engineer supports all line test stations' tools and MES integration
- Lacks RF and Audio test tool development experience
- 90% of production line test tools outsourced to third-party vendors
- Heavy reliance on external vendors for critical testing infrastructure
- Limited internal development capability may impact customization and rapid response to testing requirements
- Single point of failure with only one dedicated software engineer
- Vendor dependency may affect cost control and timeline flexibility