Share your robot application, servo scope, target specs, drawings, and quantity plan. We will respond with practical engineering and sourcing support.
Inquiry Email
Include drawings, torque/speed, protocol, and prototype quantity.
Use these templates before submitting the form when your team needs a cleaner first quote package.
CSV
A field-by-field checklist for torque-speed-duty targets, drawings, protocol, sample quantity, acceptance tests, and open decisions.
Use before the first supplier email so engineering, sourcing, and procurement are aligned on required inputs.
CSV
A starting validation matrix for torque, current, heat rise, backlash, encoder zero, communication, burn-in, and outgoing inspection.
Use when samples are being scoped and the buyer needs pass/fail evidence before pilot approval.
Markdown
A request brief that lists the drawings, datums, connector exits, cable routes, and acceptance limits needed before project-specific geometry work.
Use before requesting project-specific STEP or STL geometry for a custom motor, drive, or actuator package.
RFQ Form
Use the form for quick routing, or email directly when drawings, attachments, or CC recipients are required.
Step 1 of 5: A. Project Context
| Required Item | Example | Why It Helps |
|---|---|---|
| Servo system scope | Motor-only / drive board / smart servo / integrated actuator | Aligns supplier responsibility before architecture and pricing are discussed. |
| Torque-speed and duty cycle | 15 N·m continuous, 45 N·m peak, 60 rpm output, 30% duty | Prevents selection by peak torque alone and exposes thermal margin early. |
| Mechanical interface | Housing envelope, shaft or bore, PCB outline, connector drawing revision | Avoids sample mismatch across motor, drive, and actuator assembly. |
| Quantity plan | Prototype qty + annual forecast | Improves lead-time and pricing accuracy. |
| Destination and terms | Country, Incoterm, requested ship date | Aligns packaging, documents, and shipping plan early. |
Yes. Send your current assumptions first, then mark pending items clearly so we can return a provisional quote scope.
Use a revision-controlled change request with effective lot and impact scope agreed by both teams.
Yes. Please list required document types in the RFQ stage so they are included in validation and delivery planning.
If your team needs a fast start, use this structure in the first email. It improves quote precision and reduces clarification cycles.
| 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. |
