Electrical terminal fitting mating-thread RFQ inputs should show how the fitting meets the controlled assembly interface before a supplier interprets a photo or familiar shape. Record the current revision, mating side A, mating side B, view direction, explicit-unit observations, quantity range, and approval owner.
Start with the assembly view that makes both sides of the interface visible. Name the drawing revision, mating component on each side, installation direction, view source, and person who owns technical approval. A product image cannot define a released thread requirement by itself.
Record the assembly identifier, location reference, quantity range, and any missing view. This keeps a quotation from silently converting an unclear mating condition into a supplier assumption.
Separate side A from side B in the RFQ and keep thread evidence distinct from commercial scope. The following fields let every respondent answer against the same interface record.
| RFQ field | What to send with quote | Review purpose |
|---|---|---|
| Assembly drawing | Current view and revision | Names the governing source |
| Mating side A | Component, direction, and visible feature | Identifies one interface |
| Mating side B | Opposite component and direction | Prevents an assumed reversal |
| Thread evidence | Drawing callout, gauge note, or observed value with unit | Separates evidence from guesswork |
| Quantity scope | Quantity breaks and packaging | Aligns commercial replies |
| Acceptance owner | Named deviation reviewer | Separates quote from approval |
That table organizes an inquiry only. It does not establish thread size, pitch, tolerance, torque, material equivalence, or compatibility.
A removed fitting may reveal a thread view, but it may belong to a different revision or mating component. Label each photo with source, date, direction, and drawing relationship. Keep caliper or gauge notes marked as observations until the technical owner accepts them into the released record.
If the opposite side is hidden, state that fact and request the missing view before comparing offers. Explicit units prevent a numeric note from being mistaken for a complete thread callout.
Require each respondent to cite the revision used, restate both mating sides, and identify whether a value came from a drawing, gauge, sample, or assumption. Keep any alternative in its own field so commercial comparisons remain aligned.
| Response item | Supplier response requested | Buyer action |
|---|---|---|
| Source used | Revision and referenced view | Stop if sources differ |
| Side A reading | Component and direction understood | Check against record |
| Side B reading | Opposite interface understood | Escalate mismatch |
| Thread basis | Drawing, gauge, sample, or open point | Mark evidence status |
| Alternative | Changed feature and basis | Keep separate |
| Commercial scope | Quantity, packaging, timing | Compare aligned replies |
Store clarifications with the controlled revision. A quotation comparison is not an engineering release or a fit approval.
This article does not establish thread size, pitch, tolerance, engagement, torque, load, conductivity, material behavior, corrosion resistance, certification, compliance, or suitability for a particular assembly. Final acceptance needs product-specific evidence and an owner-selected validation plan.
Important: Pause the RFQ if either mating side, the revision, thread evidence, or approval owner is missing. Record observed dimensions with explicit units so a sample note cannot be mistaken for a released requirement. NIST RFQ unit reference
Use the TNHO electrical terminal fittings route to begin a category discussion after the mating record is complete. The route does not replace the controlled drawing or promise a specific thread, fit, performance, certification, or delivery.
For an inquiry, send the mating-thread record through contact, including revision, both interface views, evidence status, quantity range, and unresolved items.
Include the drawing callout or observed value with explicit units, source, revision, view direction, and evidence status.
No. A sample records an observation; the controlled drawing and approved validation define the released requirement.
State both components, directions, visible features, hidden conditions, drawing revision, and open questions.
Mark them open, identify who must confirm them, and keep any supplier alternative separate from the original request.
No. It is a navigation route and does not prove thread size, pitch, tolerance, compatibility, or compliance.
Send the controlled revision, both interface views, evidence status, quantity range, approval owner, and unresolved items.
TNHO 
