What should be included in the first RFQ email?

Include joint position, candidate RFQ class or torque window, torque at speed, duty cycle, bus voltage, protocol, encoder and brake needs, interface drawing revision, sample validation priority, requested documents, quantity plan, and destination.

How quickly can we get an actionable response?

Complete RFQs are easier to route for first-round engineering feedback and quote direction within one business day; incomplete inputs usually receive clarification questions first.

Can we discuss custom OEM requirements before PO?

Yes. We encourage pre-PO engineering clarification to reduce prototype and mass-production risk.

OEM capability RFQ

Prepare RFQ for Actuator BOM Integration

This inquiry started from an OEM capability page. Keep the request anchored to customization scope, document release boundaries, and repeat-order controls. Source context: Actuator BOM Integration.

OEM capability

RFQ Context: Actuator BOM Integration

This inquiry started from an OEM capability page. Keep the request anchored to customization scope, document release boundaries, and repeat-order controls. Source context: Actuator BOM Integration.

Review source page

Source Page

/oem/actuator-bom-integration

First Action

Describe the program stage and customization boundary first, then include interface ownership, NDA status, validation records needed, sample gate, and pilot or repeat-order assumptions.

Document Focus

RFQ-qualified engineering packet, NDA-controlled CAD path, customization notes, quality records, and repeat-order revision controls.

Include These Fields in the First Email

Target actuator stack or selected product family
Required subcomponents and any preferred brands or benchmark models
Control architecture, bus voltage, protocol, and software environment
Sample quantity, spare requirement, pilot forecast, and destination

Inquiry Email

[email protected]

Subject: OEM Inquiry - Actuator BOM Integration

Email app

Use this route for the first email: Describe the program stage and customization boundary first, then include interface ownership, NDA status, validation records needed, sample gate, and pilot or repeat-order assumptions.

Instant Chat

+8618857971991

Chat on WhatsApp

Best for quick model-fit questions before a full RFQ email.

RFQ Form

Send a structured inquiry

Use the form for quick routing, or email directly when drawings, attachments, or CC recipients are required.

RFQ Checklist Before You Send

Application and joint map

Example: Robot type, axis list, joint position, payload, and duty notes.
Why It Helps: Separates hand, arm, leg, drive, and prototype sourcing so the first shortlist is not too broad.
Status: required

Candidate RFQ class or torque window

Example: HRA-R70-KNEE, 50-150 Nm, compact QDD, hollow-shaft module, or linear actuator force class.
Why It Helps: Connects the inquiry to the catalog matrix and avoids comparing unrelated actuator architectures.
Status: recommended

Torque, speed, force, or stroke target

Example: Continuous torque, peak torque, peak duration, output speed, linear force, stroke, and cycle rate.
Why It Helps: Lets engineering check thermal load, gearing, rotor size, actuator length, and sample feasibility.
Status: required

Electrical and control stack

Example: Bus voltage, current limit, CAN / EtherCAT / UART, encoder, brake, feedback, and safety limits.
Why It Helps: Prevents late mismatch between motor, driver, firmware, connector, and robot controller.
Status: required

Mechanical envelope and interface

Example: OD, axial length, flange, bore, cable exit, connector, drawing revision, and CAD interface notes.
Why It Helps: Confirms whether a catalog module can fit or whether an OEM interface discussion is needed.
Status: required

Validation plan and sample gate

Example: Backdrivability, thermal rise, shock load, force-control stability, noise, or end-stop behavior.
Why It Helps: Defines the test that should pass before scaling from lab samples to prototype batches.
Status: recommended

Commercial and logistics baseline

Example: Prototype quantity, annual forecast, destination, Incoterm, target ship date, and packaging limits.
Why It Helps: Keeps sample, pilot, and production quotes aligned with the buyer timeline.
Status: required

Documents to request

Example: Datasheet, dimensional drawing, CAD / STEP, wiring pinout, inspection report, and test record.
Why It Helps: Makes the first response package actionable without implying that every controlled file is public.
Status: conditional

Required Item	Example	Why It Helps	Status
Application and joint map	Robot type, axis list, joint position, payload, and duty notes.	Separates hand, arm, leg, drive, and prototype sourcing so the first shortlist is not too broad.	required
Candidate RFQ class or torque window	HRA-R70-KNEE, 50-150 Nm, compact QDD, hollow-shaft module, or linear actuator force class.	Connects the inquiry to the catalog matrix and avoids comparing unrelated actuator architectures.	recommended
Torque, speed, force, or stroke target	Continuous torque, peak torque, peak duration, output speed, linear force, stroke, and cycle rate.	Lets engineering check thermal load, gearing, rotor size, actuator length, and sample feasibility.	required
Electrical and control stack	Bus voltage, current limit, CAN / EtherCAT / UART, encoder, brake, feedback, and safety limits.	Prevents late mismatch between motor, driver, firmware, connector, and robot controller.	required
Mechanical envelope and interface	OD, axial length, flange, bore, cable exit, connector, drawing revision, and CAD interface notes.	Confirms whether a catalog module can fit or whether an OEM interface discussion is needed.	required
Validation plan and sample gate	Backdrivability, thermal rise, shock load, force-control stability, noise, or end-stop behavior.	Defines the test that should pass before scaling from lab samples to prototype batches.	recommended
Commercial and logistics baseline	Prototype quantity, annual forecast, destination, Incoterm, target ship date, and packaging limits.	Keeps sample, pilot, and production quotes aligned with the buyer timeline.	required
Documents to request	Datasheet, dimensional drawing, CAD / STEP, wiring pinout, inspection report, and test record.	Makes the first response package actionable without implying that every controlled file is public.	conditional

Choose the Right RFQ Starting Point

Start from the application that most closely matches your robot axis. It gives engineering a clear path from use case to actuator architecture, first validation risk, and sample decision.

Hands, wrists, neck, and light ankle axes

Finger, wrist pitch/yaw, neck, light ankle, compact lab axes

Torque / Force Window: <50 Nm output class
First Architecture: Compact QDD, compact harmonic, or controller-matched module
RFQ Priority: Envelope, mass budget, low-speed smoothness, encoder resolution, and cable exit
Sample Gate: Backdrivability and current-limit behavior before interface customization
Start From: Product path Solution path

Shoulder, elbow, waist, and cable-through upper body

Shoulder, elbow, waist, torso, hollow-shaft wrist routing

Torque / Force Window: <50 to 150 Nm output class
First Architecture: Integrated rotary module or hollow-shaft joint actuator
RFQ Priority: Backlash, bore size, flange, cable bundle, protocol, and brake requirement
Sample Gate: Cable-through routing and repeated-position accuracy under load
Start From: Product path Solution path

Knee, ankle, hip, and bipedal load-bearing joints

Knee, ankle pitch/roll, hip pitch/roll/yaw, heavy leg test rigs

Torque / Force Window: 50-150 Nm and >150 Nm output classes
First Architecture: High-torque integrated rotary module, reducer module, or frameless motor stack
RFQ Priority: Continuous torque, overload duration, thermal path, brake behavior, impact load, and output bearing support
Sample Gate: Thermal rise and shock-load validation before pilot batch planning
Start From: Product path Solution path

Backdrivable force-control and QDD experiments

Force-control ankle, wrist, compliant shoulder, interaction and fall-response tests

Torque / Force Window: <50 to 150 Nm output class
First Architecture: QDD actuator, frameless outrunner, or low-ratio reducer stack
RFQ Priority: Reflected inertia, torque feedback, current bandwidth, protocol latency, and safety limits
Sample Gate: Force-control stability and low-speed torque ripple checks
Start From: Product path Solution path

Finger, linkage, and compact linear axes

Finger, thumb, compact end-effector linkage, roller-screw test fixture

Torque / Force Window: 40 N to 5 kN force / stroke-dependent
First Architecture: Micro linear actuator or compact roller-screw actuator
RFQ Priority: Stroke, force at speed, side load, backlash, noise, and holding behavior
Sample Gate: Mechanism fit and end-stop behavior before multi-axis kit ordering
Start From: Product path Solution path

Axial-flux and SMC motor-core R&D

Hip-light, knee R&D, compact high-torque demonstrator, 3D magnetic core trials

Torque / Force Window: Project-specific torque-density target
First Architecture: Axial-flux prototype path, SMC stator segment, or 3D magnetic core
RFQ Priority: OD, axial length, SMC grade, loss model, cooling path, tooling DFM, and validation method
Sample Gate: Material and concept validation before tooling commitment
Start From: Product path Solution path

Application	Torque / Force Window	First Architecture	RFQ Priority	Sample Gate	Start From
Hands, wrists, neck, and light ankle axesFinger, wrist pitch/yaw, neck, light ankle, compact lab axes	<50 Nm output class	Compact QDD, compact harmonic, or controller-matched module	Envelope, mass budget, low-speed smoothness, encoder resolution, and cable exit	Backdrivability and current-limit behavior before interface customization	Product path Solution path
Shoulder, elbow, waist, and cable-through upper bodyShoulder, elbow, waist, torso, hollow-shaft wrist routing	<50 to 150 Nm output class	Integrated rotary module or hollow-shaft joint actuator	Backlash, bore size, flange, cable bundle, protocol, and brake requirement	Cable-through routing and repeated-position accuracy under load	Product path Solution path
Knee, ankle, hip, and bipedal load-bearing jointsKnee, ankle pitch/roll, hip pitch/roll/yaw, heavy leg test rigs	50-150 Nm and >150 Nm output classes	High-torque integrated rotary module, reducer module, or frameless motor stack	Continuous torque, overload duration, thermal path, brake behavior, impact load, and output bearing support	Thermal rise and shock-load validation before pilot batch planning	Product path Solution path
Backdrivable force-control and QDD experimentsForce-control ankle, wrist, compliant shoulder, interaction and fall-response tests	<50 to 150 Nm output class	QDD actuator, frameless outrunner, or low-ratio reducer stack	Reflected inertia, torque feedback, current bandwidth, protocol latency, and safety limits	Force-control stability and low-speed torque ripple checks	Product path Solution path
Finger, linkage, and compact linear axesFinger, thumb, compact end-effector linkage, roller-screw test fixture	40 N to 5 kN force / stroke-dependent	Micro linear actuator or compact roller-screw actuator	Stroke, force at speed, side load, backlash, noise, and holding behavior	Mechanism fit and end-stop behavior before multi-axis kit ordering	Product path Solution path
Axial-flux and SMC motor-core R&DHip-light, knee R&D, compact high-torque demonstrator, 3D magnetic core trials	Project-specific torque-density target	Axial-flux prototype path, SMC stator segment, or 3D magnetic core	OD, axial length, SMC grade, loss model, cooling path, tooling DFM, and validation method	Material and concept validation before tooling commitment	Product path Solution path

Common RFQ Class Shortlist

If you do not know the exact model yet, use one of these RFQ classes as a starting reference. The class is not a final part number; it is a practical way to align torque, packaging, controls, and validation scope before quotation.

HRA-C40-QDD

Compact QDD joint class

Best Starting Use: Wrist, neck, light ankle, compact lab axis
Output Window: <50 Nm class2-4 Nm continuous; 8-14 Nm peak
Control Baseline: 24-48 V DCCAN / CAN FD / PWM options
Key Validation Question: Backdrivability, low-speed smoothness, current limit, and cable exit.

HRA-R55-ARM

Compact harmonic arm joint class

Best Starting Use: Elbow, shoulder-light, wrist pitch/yaw
Output Window: <50 Nm class6-15 Nm continuous; 25-45 Nm peak
Control Baseline: 24-48 V DCCAN / EtherCAT options
Key Validation Question: Backlash, cable-through routing, arm mass budget, and mirrored joint consistency.

HRA-R70-KNEE

Mid-load knee and ankle rotary class

Best Starting Use: Knee-light, ankle pitch/roll, waist, shoulder-heavy
Output Window: 50-150 Nm class18-45 Nm continuous; 80-150 Nm peak
Control Baseline: 48-60 V DCCAN FD / EtherCAT options
Key Validation Question: Thermal rise, overload duration, backlash, brake behavior, and shock load.

HRA-R95-HIP

Heavy hip actuator class

Best Starting Use: Hip pitch/roll/yaw, heavy knee, impact test rig
Output Window: >150 Nm class60-120 Nm continuous; 220-450 Nm peak
Control Baseline: 48-72 V DCCAN FD / EtherCAT options
Key Validation Question: Continuous torque envelope, housing heat path, impact load, and bearing support.

HRA-HS80-CBL

Hollow-shaft cable-through joint class

Best Starting Use: Shoulder, elbow, waist, wrist cable-through axes
Output Window: 50-150 Nm class20-55 Nm continuous; 80-160 Nm peak
Control Baseline: 48-60 V DCCAN FD / EtherCAT options
Key Validation Question: Bore size, cable fatigue, connector placement, backlash, and output bearing load.

HRA-LA16-FINGER

Micro linear finger actuator class

Best Starting Use: Finger, thumb, small linkage, lab end-effector
Output Window: <50 Nm class40-120 N force; 180-300 N short duration
Control Baseline: 12-24 V DCDriver dependent
Key Validation Question: Stroke, side load, backlash, noise, heat, and end-stop behavior.

HRA-DRV48-CANFD

48 V controller and encoder kit class

Best Starting Use: Bench bring-up, multi-axis prototype, matched actuator kit
Output Window: <50 Nm classCurrent rating by actuator; Peak current duration by thermal design
Control Baseline: 24-60 V DCCAN FD / EtherCAT / RS485 options
Key Validation Question: Current limit, firmware, protocol latency, encoder resolution, and harness pinout.

HRA-AF80-SMC

Axial-flux SMC prototype class

Best Starting Use: Hip-light, knee R&D, compact high-torque demonstrator
Output Window: 50-150 Nm classProject-specific torque target; Project-specific overload target
Control Baseline: 48-72 V DC target rangeMatched by inverter and test plan
Key Validation Question: SMC grade, loss model, cooling path, torque density, and manufacturable core geometry.

RFQ Class	Best Starting Use	Output Window	Control Baseline	Key Validation Question
HRA-C40-QDDCompact QDD joint class	Wrist, neck, light ankle, compact lab axis	<50 Nm class2-4 Nm continuous; 8-14 Nm peak	24-48 V DCCAN / CAN FD / PWM options	Backdrivability, low-speed smoothness, current limit, and cable exit.
HRA-R55-ARMCompact harmonic arm joint class	Elbow, shoulder-light, wrist pitch/yaw	<50 Nm class6-15 Nm continuous; 25-45 Nm peak	24-48 V DCCAN / EtherCAT options	Backlash, cable-through routing, arm mass budget, and mirrored joint consistency.
HRA-R70-KNEEMid-load knee and ankle rotary class	Knee-light, ankle pitch/roll, waist, shoulder-heavy	50-150 Nm class18-45 Nm continuous; 80-150 Nm peak	48-60 V DCCAN FD / EtherCAT options	Thermal rise, overload duration, backlash, brake behavior, and shock load.
HRA-R95-HIPHeavy hip actuator class	Hip pitch/roll/yaw, heavy knee, impact test rig	>150 Nm class60-120 Nm continuous; 220-450 Nm peak	48-72 V DCCAN FD / EtherCAT options	Continuous torque envelope, housing heat path, impact load, and bearing support.
HRA-HS80-CBLHollow-shaft cable-through joint class	Shoulder, elbow, waist, wrist cable-through axes	50-150 Nm class20-55 Nm continuous; 80-160 Nm peak	48-60 V DCCAN FD / EtherCAT options	Bore size, cable fatigue, connector placement, backlash, and output bearing load.
HRA-LA16-FINGERMicro linear finger actuator class	Finger, thumb, small linkage, lab end-effector	<50 Nm class40-120 N force; 180-300 N short duration	12-24 V DCDriver dependent	Stroke, side load, backlash, noise, heat, and end-stop behavior.
HRA-DRV48-CANFD48 V controller and encoder kit class	Bench bring-up, multi-axis prototype, matched actuator kit	<50 Nm classCurrent rating by actuator; Peak current duration by thermal design	24-60 V DCCAN FD / EtherCAT / RS485 options	Current limit, firmware, protocol latency, encoder resolution, and harness pinout.
HRA-AF80-SMCAxial-flux SMC prototype class	Hip-light, knee R&D, compact high-torque demonstrator	50-150 Nm classProject-specific torque target; Project-specific overload target	48-72 V DC target rangeMatched by inverter and test plan	SMC grade, loss model, cooling path, torque density, and manufacturable core geometry.

What Happens After Inquiry

Data completeness check

Output: We confirm the missing mechanical, electrical, duty-cycle, and commercial fields before model selection.
Buyer Action: Send the latest drawing revision, torque-speed target, sample quantity, and delivery baseline.

Application-to-class shortlist

Output: We map the use case to a candidate RFQ class, comparable architecture, and first validation risk.
Buyer Action: Confirm whether the shortlist matches the target joint, robot size, and integration constraints.

Sample and document plan

Output: We identify which datasheets, drawings, CAD files, wiring notes, or test records are appropriate to request.
Buyer Action: Tell us which documents are needed for internal design review, supplier approval, or prototype release.

Quotation and next decision

Output: We provide the practical quote path: sample scope, lead-time assumptions, OEM boundary, and scale-up notes.
Buyer Action: Approve sample direction, adjust scope, or send additional constraints for a revised shortlist.

Stage	Output	Buyer Action
01Data completeness check	We confirm the missing mechanical, electrical, duty-cycle, and commercial fields before model selection.	Send the latest drawing revision, torque-speed target, sample quantity, and delivery baseline.
02Application-to-class shortlist	We map the use case to a candidate RFQ class, comparable architecture, and first validation risk.	Confirm whether the shortlist matches the target joint, robot size, and integration constraints.
03Sample and document plan	We identify which datasheets, drawings, CAD files, wiring notes, or test records are appropriate to request.	Tell us which documents are needed for internal design review, supplier approval, or prototype release.
04Quotation and next decision	We provide the practical quote path: sample scope, lead-time assumptions, OEM boundary, and scale-up notes.	Approve sample direction, adjust scope, or send additional constraints for a revised shortlist.

Common Clarification Questions

Can I send a rough requirement before final drawings are ready?

Yes. Send your current assumptions first, then mark pending items clearly so we can return a provisional quote scope.

How should we handle engineering changes after sample approval?

Use a revision-controlled change request with effective lot and impact scope agreed by both teams.

Can we request CAD files or sample test records?

Yes. Please list the exact files needed for internal design review. Controlled files such as CAD / STEP and test records depend on model family, OEM scope, and NDA status.

Document Requests and Boundaries

Ask for the documents that match your current buying stage. Public marketing claims are not enough for humanoid joint selection, but controlled engineering files also need the right model context and permission path.

Datasheet / model summary

When to Ask: When comparing candidate actuator classes.
Boundary: Use it to confirm rated output, peak window, voltage, feedback, mass, and operating limits.

2D drawing or envelope sketch

When to Ask: Before checking frame packaging or joint interface fit.
Boundary: Clarify OD, length, flange, bore, mounting holes, cable exit, and connector orientation.

3D CAD / STEP file

When to Ask: After the model family fit is confirmed.
Boundary: Availability depends on model, OEM scope, and NDA status; it should not be treated as an automatic download.

Wiring, protocol, and pinout note

When to Ask: When the actuator must connect directly to an existing controller.
Boundary: Use it to reduce late driver, brake, encoder, connector, or firmware mismatch.

Inspection or sample test record

When to Ask: Before approving samples for lab validation or pilot builds.
Boundary: Ask for the specific test that matters most: torque, backlash, temperature rise, noise, or force response.

Packaging and export documents

When to Ask: When planning international sample shipment or pilot lots.
Boundary: Confirm destination, Incoterm, declared description, packaging limit, and target ship date.

Document	When to Ask	Boundary
Datasheet / model summary	When comparing candidate actuator classes.	Use it to confirm rated output, peak window, voltage, feedback, mass, and operating limits.
2D drawing or envelope sketch	Before checking frame packaging or joint interface fit.	Clarify OD, length, flange, bore, mounting holes, cable exit, and connector orientation.
3D CAD / STEP file	After the model family fit is confirmed.	Availability depends on model, OEM scope, and NDA status; it should not be treated as an automatic download.
Wiring, protocol, and pinout note	When the actuator must connect directly to an existing controller.	Use it to reduce late driver, brake, encoder, connector, or firmware mismatch.
Inspection or sample test record	Before approving samples for lab validation or pilot builds.	Ask for the specific test that matters most: torque, backlash, temperature rise, noise, or force response.
Packaging and export documents	When planning international sample shipment or pilot lots.	Confirm destination, Incoterm, declared description, packaging limit, and target ship date.

Controlled Document Request Path

Use this matrix to request the right document packet without overstating what should be public. The deeper the request, the more important it is to include model context, project stage, and permission status in the first email.

Public selection packet

Buyer Stage: Early shortlist
Documents: Datasheet, model summary, basic envelope image, and application fit notes.
Input to Include: Target joint, output window, voltage / protocol assumption, and quantity direction.
Boundary: Used for selection only; it is not a controlled drawing or final project guarantee.
Primary Use: Decide whether the actuator family deserves engineering RFQ effort.

RFQ-qualified engineering packet

Buyer Stage: Before sample quote
Documents: 2D envelope, interface notes, wiring / protocol note, accessory list, and sample gate.
Input to Include: Drawing revision, mechanical envelope, controller stack, and validation priority.
Boundary: Provided after the model path is clear; it may still exclude editable CAD or supplier-controlled internals.
Primary Use: Check whether a sample can be integrated and tested.

NDA-controlled CAD packet

Buyer Stage: Before mechanical freeze
Documents: STEP / CAD path, pinout details, revision-controlled drawings, and customization notes.
Input to Include: Confirmed candidate model, buyer entity, project scope, and NDA path if needed.
Boundary: Not an automatic website download; controlled files depend on model, OEM scope, and permission.
Primary Use: Let mechanical and electrical teams freeze interface assumptions.

Sample validation packet

Buyer Stage: Before pilot decision
Documents: Inspection note, focused test result, revision record, and packing / shipment baseline.
Input to Include: Accepted sample scope, test fixture context, pass / fail priority, and pilot quantity.
Boundary: Generic records may not answer the application risk; request the exact test that matters.
Primary Use: Decide whether accepted samples can move into pilot planning.

Pilot / repeat-order packet

Buyer Stage: Before repeat PO
Documents: Outgoing inspection scope, revision baseline, packaging plan, and change-control route.
Input to Include: Approved revision, forecast cadence, shipment terms, and quality record expectation.
Boundary: Final content depends on commercial scope and agreed QC terms.
Primary Use: Prevent silent revision drift between sample, pilot, and repeat orders.

Packet	Buyer Stage	Documents	Input to Include	Boundary	Primary Use
Public selection packet	Early shortlist	Datasheet, model summary, basic envelope image, and application fit notes.	Target joint, output window, voltage / protocol assumption, and quantity direction.	Used for selection only; it is not a controlled drawing or final project guarantee.	Decide whether the actuator family deserves engineering RFQ effort.
RFQ-qualified engineering packet	Before sample quote	2D envelope, interface notes, wiring / protocol note, accessory list, and sample gate.	Drawing revision, mechanical envelope, controller stack, and validation priority.	Provided after the model path is clear; it may still exclude editable CAD or supplier-controlled internals.	Check whether a sample can be integrated and tested.
NDA-controlled CAD packet	Before mechanical freeze	STEP / CAD path, pinout details, revision-controlled drawings, and customization notes.	Confirmed candidate model, buyer entity, project scope, and NDA path if needed.	Not an automatic website download; controlled files depend on model, OEM scope, and permission.	Let mechanical and electrical teams freeze interface assumptions.
Sample validation packet	Before pilot decision	Inspection note, focused test result, revision record, and packing / shipment baseline.	Accepted sample scope, test fixture context, pass / fail priority, and pilot quantity.	Generic records may not answer the application risk; request the exact test that matters.	Decide whether accepted samples can move into pilot planning.
Pilot / repeat-order packet	Before repeat PO	Outgoing inspection scope, revision baseline, packaging plan, and change-control route.	Approved revision, forecast cadence, shipment terms, and quality record expectation.	Final content depends on commercial scope and agreed QC terms.	Prevent silent revision drift between sample, pilot, and repeat orders.

What to Include Before Asking for Controlled Files

Candidate model or RFQ class

Why It Matters: Controlled documents are useful only after the actuator family and output window are clear.
Example: HRA-R70-KNEE, 50-150 Nm knee joint, or compact QDD module.

Project review stage

Why It Matters: The right packet differs between early sourcing, sample release, mechanical freeze, and pilot approval.
Example: Internal shortlist, first sample quote, prototype CAD review, or pilot build.

Interface revision and owner

Why It Matters: Drawings, CAD, pinout notes, and test records need a revision baseline to avoid mismatched files.
Example: Robot knee frame rev B, controller rev A, and named mechanical / electrical owner.

NDA or permission status

Why It Matters: Editable CAD, supplier-specific pinout details, and project test records may require controlled release.
Example: NDA ready, NDA under legal review, or public selection packet only.

Input	Why It Matters	Example
Candidate model or RFQ class	Controlled documents are useful only after the actuator family and output window are clear.	HRA-R70-KNEE, 50-150 Nm knee joint, or compact QDD module.
Project review stage	The right packet differs between early sourcing, sample release, mechanical freeze, and pilot approval.	Internal shortlist, first sample quote, prototype CAD review, or pilot build.
Interface revision and owner	Drawings, CAD, pinout notes, and test records need a revision baseline to avoid mismatched files.	Robot knee frame rev B, controller rev A, and named mechanical / electrical owner.
NDA or permission status	Editable CAD, supplier-specific pinout details, and project test records may require controlled release.	NDA ready, NDA under legal review, or public selection packet only.

Suggested First RFQ Email Format

If your team needs a fast start, use this structure in the first email. It improves quote precision and reduces clarification cycles.

Project background and application scenario.
Target joint map and candidate RFQ class.
Torque / speed / force / stroke and duty cycle.
Electrical and control stack.
Mechanical envelope and interface revision.
Validation gate and sample quantity.
Requested documents and delivery baseline.

What You Should Review Before Sending RFQ

Products for architecture-level selection and model-family fit.
Solutions / Applications for scenario-specific constraints and validation priorities.
OEM Capabilities for design collaboration, quality controls, and delivery process.
Engineering Blog for practical checklists you can copy into buyer workflows.
Share benchmark actuator models or CAD envelopes if your team is replacing an existing humanoid joint design.

Typical First Response Package

Model and architecture direction

Purpose: Narrow viable options against torque-speed and interface assumptions.
Buyer Action: Confirm baseline model path before cost-detail discussion.

RFQ clarification list

Purpose: Close data gaps that affect pricing and lead-time accuracy.
Buyer Action: Return missing values and drawing references in one reply.

Validation recommendation

Purpose: Define sample test scope and acceptance evidence for technical sign-off.
Buyer Action: Align internal engineering and procurement gates before PO.

Output	Purpose	Buyer Action
Model and architecture direction	Narrow viable options against torque-speed and interface assumptions.	Confirm baseline model path before cost-detail discussion.
RFQ clarification list	Close data gaps that affect pricing and lead-time accuracy.	Return missing values and drawing references in one reply.
Validation recommendation	Define sample test scope and acceptance evidence for technical sign-off.	Align internal engineering and procurement gates before PO.