Run the tool first for an immediate sourcing-fit signal, then use the report layers to validate evidence, boundaries, and risk tradeoffs before RFQ lock. If you are evaluating a 100 1 gearbox manufacturer in china, this page is built as a decision-first route rather than a generic overview.
Published: 2026-05-16 · Last updated: 2026-05-16
Score whether your 100:1 sourcing constraints are RFQ-ready, which supplier path to prioritize, and what to do next.
No result yet.
Run the checker to get supplier path recommendation, readiness score, and RFQ next action.
Users want an immediate shortlist signal first, then evidence on supplier quality, lead-time realism, and boundary risks before RFQ commitment.
This page uses 90:1 to 110:1 for strict go decisions and 40:1 to 220:1 for directional screening to prevent false certainty when requirement drift appears.
ICC Incoterms 2020 rules define delivery obligations, but they do not define title transfer, payment, tariffs, sanctions, or force majeure. Quotes with mixed trade-term assumptions are not directly comparable.
ISO 6336-1:2019 (confirmed in 2025) provides rating-method boundaries and explicit non-applicable cases. It should be treated as a gate input, not as complete assembled-system assurance.
IATF 16949 first edition was published in October 2016, and customer-specific requirements continue to update (for example, Ford CSR update on 2025-02-06). Static certificate PDFs alone are insufficient for final supplier lock.
World Bank LPI 2023 reports an average maritime shipment journey of 44 days with 10.5-day standard deviation, so single-point lead-time promises should be treated as probabilistic, not deterministic.
Values below are decision anchors for pre-RFQ screening. Heuristic values are explicitly labeled and must be verified with supplier evidence before final commitment.
| Metric | Value / Context | Why It Matters | Source Family |
|---|---|---|---|
| Strict 100:1 decision band | 90:1 to 110:1 for go/no-go decisions on this page | Prevents drifted ratios from being treated as exact 100:1 sourcing decisions. | Page methodology rule |
| Broad screening corridor | 40:1 to 220:1 for directional screening only | Keeps the checker usable for adjacent requests while preserving strict intent boundaries. | Page methodology rule |
| Catalog-OEM default lead-time baseline | 4 to 10 weeks mass-production window in this model | Useful for fast-turn catalog programs, but often weak on advanced documentation requirements. | Internal heuristic model (explicitly non-universal) |
| Precision-OEM default lead-time baseline | 6 to 14 weeks mass-production window in this model | Represents additional process and quality controls for tighter backlash and validation needs. | Internal heuristic model (explicitly non-universal) |
| Program-OEM default lead-time baseline | 8 to 18 weeks mass-production window in this model | Captures longer ramp for full-custom and trace-heavy programs. | Internal heuristic model (explicitly non-universal) |
| Suggested shortlist size | Go=3 suppliers, Review=4, No-go=5 | Higher uncertainty requires broader supplier coverage before lock. | Page decision policy |
| Backlash path split (model baseline) | Catalog >=8 arcmin, Precision >=3 arcmin, Program >=1.5 arcmin | Tighter precision targets can force supplier-path escalation before pricing comparison. | Internal heuristic model + public catalog class pattern |
| Incoterms governance version | Incoterms 2020 (11 rules total: 7 any mode + 4 sea/inland waterway), effective 2020-01-01 | Quote comparison should keep shipping responsibility terms explicit and uniform. | ICC Incoterms rules page + ICC Q&A |
| Incoterms scope exclusion (decision-critical) | Incoterms rules do not settle transfer of title, payment terms, tariffs, sanctions, or force majeure | A low headline unit price can be non-comparable if commercial/legal terms are not normalized first. | ICC Q&A: matters not covered by Incoterms |
| ISO 6336 scope reminder | ISO 6336-1:2019 is confirmed in 2025; abstract scope includes alpha_n=15°-25°, beta=0°-30°, epsilon_alpha=1.0-2.5 | Rating-method references must be applied only within scope and then handed off to integration validation. | ISO 6336-1:2019 standard page |
| ISO 6336 non-applicable counterexamples | Standard notes non-applicability for cases such as zero backlash and significant root-fillet interference | Projects at these boundaries should not use catalog rating shortcuts as final acceptance evidence. | ISO 6336-1:2019 abstract notes |
| Automotive quality signal | IATF 16949 first edition published in Oct 2016, replacing ISO/TS 16949 | Automotive-grade programs should treat certification status and current customer-specific requirements as hard gates. | IATF official pages + 2025 CSR update notice |
| Certificate verification data pipeline | ISO Survey states that from 2025 onwards, data are compiled from IAF CertSearch | Use live certificate verification instead of relying only on static certificate screenshots in RFQ packs. | ISO Survey + ISO certification guidance |
| Global logistics variance context | World Bank LPI 2023 covers 139 countries; average maritime shipment journey is 44 days with 10.5-day standard deviation | Procurement lead-time plans should include buffer and scenario handling rather than one fixed transit assumption. | World Bank LPI 2023 release + LPI methodology page |
Audit tracks weak points found during hybrid-page review and the direct fixes completed in this implementation.
| Gap | Why It Was Weak | Enhancement | Status |
|---|---|---|---|
| Evidence labels were too generic for external review | Several rows used source-family wording (e.g., "official page") without clause-level, date-stamped facts. | Upgraded key facts with direct standard boundaries, effective dates, and explicit source URLs. | Closed in this round (2026-05-16 refresh) |
| Incoterms guidance lacked negative scope boundaries | Previous copy did not clearly state what Incoterms does not govern, causing false quote comparability assumptions. | Added explicit non-covered items (title/payment/tariff/sanctions/force majeure) and trade-term normalization gates. | Closed in this round (2026-05-16 refresh) |
| Standard applicability and counterexample boundaries were thin | Scope constraints from ISO 6336 were not translated into practical no-overreach rules for buyer decisions. | Added numeric applicability ranges and non-applicable counterexamples to prevent misuse. | Closed in this round (2026-05-16 refresh) |
| Certificate checks were not operationally executable | Page advised certification awareness but did not define a verification path for active/suspended/withdrawn states. | Added ISO/IAF verification pipeline references and a certificate-status execution gate in risk logic. | Closed in this round (2026-05-16 refresh) |
| Commercial comparability evidence remains partial | Public pages still do not provide normalized transaction datasets under one identical duty template. | Kept explicit uncertainty records and a minimum executable RFQ normalization path. | Open (待确认/暂无可靠公开数据) |
Only evidence-backed additions are listed here. Items without reproducible public support remain in uncertainty records.
| New Finding | Evidence Added | Decision Impact | Source Check |
|---|---|---|---|
| Incoterms comparability rules now anchored to direct ICC facts | ICC states Incoterms 2020 entered into force on 2020-01-01 with 11 rules, and ICC Q&A clarifies non-covered items such as title transfer, payment, tariffs, sanctions, and force majeure. | RFQ comparison now requires explicit trade-term normalization before any price-based ranking. | ICC rules page + ICC Q&A (checked 2026-05-16) |
| ISO 6336 scope boundaries translated into executable limits | ISO 6336-1:2019 abstract provides scope ranges (pressure/helix/contact-ratio) and includes explicit non-applicable examples; record shows confirmation in 2025. | Checker guidance now treats these references as gate inputs only and blocks overreach into full release assurance claims. | ISO 6336-1 page (checked 2026-05-16) |
| IATF governance is dynamic, not static | IATF 16949 first edition (October 2016) replaced ISO/TS 16949, and IATF news records ongoing customer-specific requirement updates (e.g., Ford CSR effective 2025-02-06). | Added explicit gate to revalidate certificate scope and current CSR alignment before final supplier lock. | IATF about/news pages (checked 2026-05-16) |
| Certificate verification path upgraded from static proof to live lookup | ISO certification guidance points to IAF CertSearch for validating certificates, and ISO Survey indicates 2025+ aggregation from IAF CertSearch. | Procurement checklist now requires certificate-status verification as part of go/review transition. | ISO certification + ISO Survey pages (checked 2026-05-16) |
| Lead-time planning now has explicit macro-volatility context | World Bank LPI 2023 reports 139-country coverage and a 44-day average maritime shipment journey with 10.5-day standard deviation. | Schedule decisions now include buffer logic and stronger caution against single-point transit assumptions. | World Bank LPI 2023 release (checked 2026-05-16) |
These boundaries determine when this page output is a practical decision aid and when escalation is mandatory.
| Boundary Topic | Condition | Implication | Source |
|---|---|---|---|
| Strict 100:1 intent boundary | Use 90:1 to 110:1 for go/no-go decisions. 40:1 to 220:1 is directional screening only. | Outside strict band, keep review status and confirm true architecture target before procurement lock. | Page methodology rule |
| Quality evidence boundary | Basic docs, PPAP, and full-trace requirements are treated as separate sourcing levels. | If evidence pack depth is mismatched, do not treat nominal pricing as a valid selection signal. | Tool decision policy |
| Certification boundary | When IATF-level quality governance is mandatory, non-program sourcing assumptions are incompatible without verified current scope and CSR alignment. | Escalate supplier path before comparing lead-time and unit price. | IATF official pages + page policy |
| Incoterms scope boundary | Incoterms rules do not govern title transfer, payment terms, tariffs, sanctions, or force majeure handling. | Do not compare supplier total cost on Incoterms labels alone; normalize commercial/legal assumptions first. | ICC Q&A scope statement |
| Lead-time pressure boundary | Sample and mass lead-time targets are scored jointly against path baseline windows. | Aggressive schedule compression can invalidate otherwise feasible technical paths. | Tool scoring model |
| Standards-scope boundary | ISO 6336 references are valid only inside documented scope ranges and include explicit non-applicable cases (such as zero backlash in noted examples). | Keep thermal, bearing, lubrication, and integration checks in release gate. | ISO 6336-1:2019 abstract and confirmation record |
| Commercial comparability boundary | Public source sets are rarely transaction-normalized for identical duty and evidence requirements. | Use one RFQ template before supplier ranking; do not rank by mixed-context catalog snippets. | Open-data limitation (explicit uncertainty) |
| Scenario | Good Fit Signal | Not-Fit Warning | Decision Note |
|---|---|---|---|
| Industrial line needs 100:1 with moderate precision and PPAP-lite evidence | Precision-OEM path with balanced assumptions | Catalog-only shortlist based on unit price first | Confirm document package and metrology condition in sample round. |
| Project demands <=2 arcmin and full traceability | Program-OEM path with conservative assumptions | Treating low-price fast-quote offers as equivalent | Quality evidence depth dominates path choice before cost optimization. |
| Ratio requirement drifts to 130:1 during RFQ prep | Review state + architecture clarification before ranking | Locking suppliers under strict 100:1 assumptions | Ratio drift should reopen path and stage assumptions. |
| Automotive-grade quality governance required | Program path with certification verification at pre-quote stage | Comparing non-IATF and IATF offers in one bucket | Certification mismatch is a hard gating condition, not a minor adjustment. |
These counterexamples prevent false certainty and define minimum corrective actions before supplier lock.
| Assumption | Counterexample | Decision Impact | Minimum Action | Source |
|---|---|---|---|---|
| “100:1 quotes are comparable if nominal ratio matches” | Two quotes can both say 100:1 but use different Incoterms and leave tariffs/duties outside scope. | Price ranking becomes distorted and can hide true landed-cost risk. | Force one RFQ template with fixed Incoterms, duty assumptions, payment, and acceptance terms. | ICC Incoterms rules + ICC Q&A |
| “ISO 6336 rating values are enough for final release” | ISO 6336-1 states scope boundaries and non-applicable examples, so rating references alone can overstate assurance. | Late integration failures can still occur despite acceptable catalog ratings. | Treat ISO 6336 as gate input only, then require system-level thermal/life/integration validation. | ISO 6336-1:2019 standard page |
| “A certificate PDF is sufficient certification proof” | IATF customer-specific requirements continue to update, and certificate status may change over time. | Projects can pass quote review but fail governance checks before award. | Verify current status in IAF CertSearch and confirm latest applicable CSR revision before lock. | IATF news + ISO/IAF verification guidance |
| “Published lead time can be treated as deterministic” | World Bank LPI 2023 highlights sizable transit variance (44-day average with 10.5-day standard deviation). | Single-date commitments can be overly optimistic under logistics volatility. | Apply schedule buffers and review/no-go gates when sample or launch windows are compressed. | World Bank LPI 2023 release |
The checker links input validation, supplier-path branching, readiness scoring, and boundary-triggered sourcing actions.
Strict-band enforcement keeps 100:1 intent coherent and blocks ambiguous architecture decisions from being treated as final.
| Step | Logic | Output |
|---|---|---|
| Input normalization | Validate ratio, torque, backlash, annual volume, lead time, sample deadline, and sourcing constraints. | Clean inputs or recoverable boundary/error state |
| Supplier path resolution | Map customization depth, quality-pack level, certification demand, and risk profile to catalog / precision / program path. | Primary supplier path baseline |
| Readiness scoring | Blend ratio-fit, precision-fit, lead pressure, volume-fit, certification-fit, and evidence-pack compatibility into one score. | Readiness score + risk level |
| Boundary + action mapping | Apply strict-band rules, mismatch triggers, and conservative penalties to assign go/review/no-go with next actions. | Executable RFQ path with supplier-count guidance |
| Commercial and certificate verification gate | Normalize Incoterms/commercial terms and verify certificate status before price-led ranking. | Comparable quote set and lower compliance-reversal risk |
If result status is review/no-go, lock a normalized RFQ template before supplier ranking to avoid mixed-context decisions.
Unknown or partial evidence is explicitly marked instead of forcing fake certainty.
| Option | Strength | Tradeoff | Data Confidence | Typical Fit |
|---|---|---|---|---|
| Catalog OEM path | Fast quote cycle and simple commercial onboarding | Limited evidence depth for tight precision or trace-heavy programs | Public catalogs often expose broad specs but less process detail under strict evidence requirements | Cost-sensitive projects with moderate precision and basic documentation |
| Precision OEM path | Better fit for tighter backlash and engineering-review workflows | Longer delivery and higher qualification overhead versus catalog-only path | Public references typically provide more structured technical disclosures than economy catalogs | Mainstream industrial 100:1 projects needing stronger evidence quality |
| Program OEM path | Best compatibility with full-custom requirements, traceability depth, and strict quality governance | Longest ramp and highest process overhead | Open pages often confirm capability themes but not normalized transaction metrics | Safety-critical or audit-heavy sourcing programs |
| Broker/distributor shortcut path | Can accelerate communication and initial vendor access | Often weakens direct process visibility and evidence traceability | Data continuity may be partial across multi-layer sourcing chains | Exploration phase only, not final lock without direct evidence chain |
| Option | Numeric Signal | Limit / Counterexample | Decision Use | Source Family |
|---|---|---|---|---|
| Ratio-intent coherence | Strict band 90-110 vs broad 40-220 screening corridor | Outside strict band, go decisions are blocked to avoid ambiguous architecture commitments. | Protects keyword intent from scope drift during RFQ. | Page model rule |
| Lead-time pressure model | Path windows: catalog 4-10w, precision 6-14w, program 8-18w; tighter targets incur readiness penalties. | These values are heuristic and must be confirmed by actual supplier evidence packs. | Turns schedule assumptions into explicit risk signals. | Internal model (explicitly marked) |
| Quality evidence ladder | Basic / PPAP / full-trace map to increasing process-control expectations. | Missing evidence should block direct ranking even when nominal specs look similar. | Prevents false equivalence across supplier quote packages. | Page decision framework |
| Certification gate signal | IATF 16949 first edition published in Oct 2016; CSR updates continue (example: Ford CSR effective 2025-02-06). | Static certificate artifacts can lag current status or CSR revision requirements. | Adds a hard compliance gate before cost-based ranking. | IATF official pages + page rule |
| Standards context gate | ISO 6336-1:2019 confirmed in 2025; scope includes explicit applicability ranges and non-applicable examples. | Do not over-interpret catalog capacity references as complete project assurance. | Keeps gate-0 tool output aligned with downstream validation needs. | ISO 6336-1 page |
| Logistics variance context | World Bank LPI 2023 reports 44-day mean maritime journey and 10.5-day standard deviation across 139 countries. | Macro transport variability cannot predict one supplier exactly, but it is a valid buffer signal for planning. | Adds schedule-risk calibration when comparing aggressive lead-time promises. | World Bank LPI 2023 release |
Risks are grouped by misuse, cost, and scenario mismatch so each has an executable mitigation path.
| Risk | Trigger | Impact | Mitigation |
|---|---|---|---|
| Intent drift risk | Using non-100 ratios while treating output as strict 100:1 go decision | Wrong supplier path lock and avoidable redesign loop | Keep strict-band enforcement and reopen architecture assumptions when ratio drifts. |
| Evidence mismatch risk | Comparing suppliers with different quality-pack depth as if equivalent | Audit failure or launch delay after sample stage | Normalize RFQ evidence checklist before quote ranking. |
| Schedule compression risk | Lead-time targets below path baseline without process concessions | Late sample delivery and unstable launch timing | Use conservative mode and escalate path or timeline before commitment. |
| Certification mismatch risk | IATF-required project sourced under generic ISO assumptions | Compliance rejection and program restarts | Treat certification as hard gate and verify current certificate scope early. |
| Commercial scope mismatch risk | FOB/CIF/DDP and payment/tariff assumptions are mixed during quote comparison | Hidden landed-cost variance and false price advantage | Normalize Incoterms and non-Incoterms commercial assumptions before ranking. |
| Commercial comparability risk | Ranking by raw unit price from mixed quote contexts | Incorrect supplier selection and hidden lifecycle cost | Force one template for duty, evidence, Incoterms, and acceptance criteria. |
| Integration-overconfidence risk | Using quick checker output as final release approval | Late-stage integration failures | Keep thermal, life, controls, and integration validation as mandatory release gates. |
Missing evidence is kept explicit so decisions can move forward with controlled uncertainty instead of hidden assumptions.
| Topic | Current Status | Why Uncertain | Minimum Next Step |
|---|---|---|---|
| Cross-supplier normalized lifecycle cost at 100:1 under one duty profile | 待确认 / 暂无可靠公开数据（截至 2026-05-16） | Public pages rarely disclose complete lifecycle assumptions and transaction-normalized cost structure in comparable format. | Collect at least 3 to 5 supplier RFQs using one unified lifecycle-cost worksheet. |
| Open-data parity for sample pass-rate by quality-pack level | 待确认 / 暂无可靠公开数据（截至 2026-05-16） | Published marketing and catalog data usually omit statistically comparable sample-yield records. | Require sample-acceptance criteria and historical yield disclosures in RFQ annex. |
| Public, machine-readable mapping between gearbox-scope cert validity and process-level CSR conformance | 待确认 / 暂无可靠公开数据（截至 2026-05-16） | Public verification services confirm certificate existence/status, but process-scope-to-project-fit mapping is usually not transaction-ready. | Add supplier self-declaration plus third-party audit evidence aligned to project-specific process scope. |
| Scenario | Premise | Process | Outcome |
|---|---|---|---|
| Automation integrator with 100:1, <=8 arcmin, PPAP-lite requirement | Mid-volume industrial project, moderate schedule pressure, quality evidence required before release. | Tool selects precision-OEM path and returns review due evidence + schedule pressure intersection. | Team expands shortlist to 4 suppliers and prevents premature price-only lock. |
| Safety-critical deployment with full-trace requirement | Program needs strict quality governance and deeper documentation chain. | Tool routes to program-OEM path and raises no-go if certification assumptions mismatch. | Project avoids non-compliant shortlist and reduces late audit rework risk. |
| Legacy RFQ with ratio drift to 130:1 | Original keyword intent 100:1, but requirement shifted during detail design. | Tool enforces boundary review and blocks strict-go interpretation. | Procurement re-aligns architecture before issuing supplier ranking request. |
These snapshots show how the checker output maps to an executable sourcing decision path. Values are anonymized and reproducible from the stated constraints.
| Case | Input Snapshot | Tool Output | Decision Follow-up |
|---|---|---|---|
| Case A: 100:1 integrator with PPAP-lite requirement | Ratio 100:1, 420 Nm, backlash 8 arcmin, 1,200 units/year, lead time 8 weeks, sample 5 weeks, PPAP-lite, ISO 9001, semi-custom, precision-servo risk. | Go status, precision-OEM path, readiness score 83.6, suggested shortlist size 3. | Team can move to normalized RFQ with one shared evidence template before final award. |
| Case B: ratio drift to 130:1 during RFQ prep | Same baseline constraints, but target ratio moved from 100:1 to 130:1. | Review boundary triggered because 130:1 is outside strict 90-110 decision band. | Procurement must reopen architecture assumptions before locking supplier ranking. |
Why does this page put the tool before long-form explanation?
Because the query has immediate action intent. You should get a shortlist signal first, then read evidence and boundaries before RFQ lock.
Can I use this checker for any gearbox ratio?
No. It is calibrated for 100:1-centered sourcing decisions with a strict 90-110 decision band and a broader 40-220 screening corridor.
What does review status usually mean?
It means one or more constraints are feasible but not yet evidence-complete. You should gather additional quality and delivery proof before ranking suppliers.
What does no-go mean in this tool?
It signals high mismatch between constraints and current supplier path assumptions. Change path or constraints before issuing final RFQ ranking.
When should I escalate from catalog path to precision/program path?
Escalate when backlash target tightens, quality evidence depth increases, or certification/compliance constraints become strict.
Why is quality-pack depth treated as a separate decision axis?
Two suppliers can quote similar specs but deliver very different evidence quality. Without normalized evidence depth, comparison quality is weak.
If I need IATF-level governance, can I still treat catalog-only quotes as go?
No. This page treats that as a hard mismatch and returns no-go until sourcing path and certification assumptions are aligned.
Does a higher readiness score guarantee success?
No. It improves early decision quality but does not replace integration, life, thermal, and compliance validation.
How many suppliers should I include in shortlist?
Use 3 for go, 4 for review, and 5 for no-go states to reduce single-source bias and evidence gaps.
What should I normalize in RFQ templates?
Normalize duty profile, backlash target, acceptance criteria, quality evidence package, Incoterms, and timeline assumptions across all suppliers.
Can this page replace full procurement engineering review?
No. It is a gate-0 and gate-1 decision aid. Final release still requires full engineering and quality sign-off.
What if I already have one preferred manufacturer?
Run at least one benchmark comparison round anyway. Even strong incumbents should be validated under the same normalized checklist.
Source-backed fields are listed with checkpoint dates. Heuristic rules are explicitly labeled in the tables above.
| Source | Checkpoint Date | Data Used | Link |
|---|---|---|---|
| International Chamber of Commerce: Incoterms Rules | Snapshot checked: 2026-05-16 | Incoterms 2020 effective date and 11-rule structure used for RFQ term normalization | https://iccwbo.org/resources-for-business/incoterms-rules/ |
| ICC Incoterms Q&A (scope boundaries) | Snapshot checked: 2026-05-16 | Defines what Incoterms rules do not cover (title, payment, tariffs, sanctions, force majeure) | https://library.iccwbo.org/clp/clp-incoterms-qa-2020.htm?AGENT=ICC_UK |
| ISO 6336-1:2019 standard page | Snapshot checked: 2026-05-16 | Scope ranges, non-applicable examples, and 2025 confirmation status used for boundary rules | https://www.iso.org/standard/63819.html |
| IATF 16949 official about page | Snapshot checked: 2026-05-16 | First-edition context (Oct 2016) and relationship to automotive quality governance | https://www.iatfglobaloversight.org/iatf-169492016/about/ |
| IATF 16949 customer-specific requirement update notice | Snapshot checked: 2026-05-16 | Shows CSR updates continue (Ford CSR example effective 2025-02-06) | https://www.iatfglobaloversight.org/news/12-february-2025-ford-csr-update-iatf-16949-ppap/ |
| ISO certification guidance | Snapshot checked: 2026-05-16 | Provides certificate-verification entry point and verification workflow guidance | https://www.iso.org/certification.html |
| ISO Survey methodology page | Snapshot checked: 2026-05-16 | States that from 2025 onwards data are compiled from IAF CertSearch | https://www.iso.org/the-iso-survey.html |
| IAF CertSearch certification-status guide | Snapshot checked: 2026-05-16 | Operational status definitions used for certificate gate design | https://support.iafcertsearch.org/verifiers/getting-started/certificate-verification-guide/understand-the-certification-status |
| World Bank Logistics Performance Index 2023 release | Snapshot checked: 2026-05-16 | Provides 139-country coverage and maritime journey mean/variance statistics | https://www.worldbank.org/en/news/press-release/2023/04/21/world-bank-releases-logistics-performance-index-2023 |
| World Bank LPI methodology page | Snapshot checked: 2026-05-16 | Defines indicator and methodology context used for logistics-risk interpretation | https://lpi.worldbank.org/en/about/methodology |
Continue with adjacent modules after finishing this 100:1 manufacturer screening and evidence review flow.
Inquiry Email