The buyer task and decision boundary
A buyer should commission a supported replacement decision rather than a part that merely looks similar. Start with the installed identity, the symptom and the required return-to-service task. Ask a quotation to distinguish the item, compatibility confirmation, parameter work, inspection and post-replacement observation. Those are separate deliverables. A low item price is not a lower total cost when the unresolved interface and restoration work has silently been left with the buyer.
Technical context: Servo drives: match a supported combination
A drive belongs to a combination of motor, feedback device, controller, firmware and parameters. A matching enclosure or connector establishes little about that combination. Keep the original part number and revision exactly as printed, including suffixes, then ask which official document permits the proposed replacement. Distinguish the alarm that triggered the investigation from the component eventually judged faulty. An intermittent feedback or supply problem can be reported at a drive without proving that the drive itself has failed. Restoring a parameter file also requires an applicable device and software version, not merely a file with the right name. [S2]
A second condition to preserve: Reducers: distinguish clearance from loaded deflection
A reducer comparison should identify the torque condition, the measured end and the definition of the published number. Backlash, hysteresis and torsional stiffness are related to motion behaviour but are not interchangeable labels. A stiffness value describes a load-deflection relationship under specified conditions; it is not a promise of zero displacement. The Harmonic Drive engineering catalogue illustrates terminology for its own product families. Its values must not be assigned to an unknown gearbox. Mounting dimensions, bearing loads, lubrication and the manufacturer service procedure remain separate questions even when a ratio matches. [S1]
Define the deliverable before requesting a price
For a component enquiry, the installed assembly and its required return-to-service task are the anchor. The brief should state the decision, the current evidence and the result expected from the engagement. List what the buyer will supply and what the other party must establish. Distinguish an item or document delivered from an installed task completed and from a result independently verified. Ask for the included work, dependencies, excluded work and change process in writing. That separation makes it possible to compare scope without filling the page with an invented price or an unearned performance promise.
Prepare one shared input revision
For a component enquiry, the installed assembly and its required return-to-service task are the anchor. Collect the identities and original documents into a single input list with a date and revision. Preserve suffixes, source wording and unknown fields. If a candidate uses a different assumption, place that difference beside the affected conclusion rather than in a detached footnote. A quotation should identify which input revision it uses. A later change can then be assessed against the original scope instead of creating a dispute about which configuration or question was actually discussed.
Make missing evidence a decision branch
For a component enquiry, the installed assembly and its required return-to-service task are the anchor. For each unresolved entry, identify why it matters, who can confirm it and what next action would close it. Some missing information blocks selection; other information may be deferred with an explicit consequence. Do not treat all blanks as zero, normal or included. If a preliminary investigation is needed, specify its inputs and artefacts separately. The buyer can then authorise a useful bounded step rather than being asked to accept an apparently complete answer built on unsupported assumptions.
Use the quotation meeting to close specific questions
For a component enquiry, the installed assembly and its required return-to-service task are the anchor. Review scope, evidence, practical preparation and handover in that order. Record accepted inputs, differences between options and remaining conditions. Keep commercial terms distinct from technical confirmation: willingness to quote does not establish compatibility, measurement quality or task success. The meeting output should be a written scope and an action list that both sides can inspect, not merely a verbal expression of confidence. Keep earlier revisions so later changes can be explained.
Apply the worksheet to this domain
Use the input sheet to freeze robot serial identity, installed part number, controller and firmware and motor and feedback revision before the quotation. Ask which evidence confirms each relationship and whether the quoted scope includes that work. Put preparation, supply or analysis, implementation and follow-up in separate lines. A missing confirmation becomes a named dependency, not a hidden assumption. Keep the input revision beside every proposal so a later change can be priced and reviewed against the same task rather than against a different recollection of the enquiry.
Four routes and their tradeoffs
Exact part-number replacement: ask the quotation to cover suffix, revision, provenance and permitted parameter handling. Its fit is this: The installed identity and replacement basis are already known. Make the scope consequence explicit: A narrow scope still needs receipt and installed-task checks.
Documented alternative: ask the quotation to cover mechanical, electrical, feedback and controller support separately. Its fit is this: An applicable maker or responsible party has confirmed the relationship. Make the scope consequence explicit: More sourcing flexibility creates additional evidence to review.
Diagnosis before purchase: ask the quotation to cover original logs, triggering task and authorised diagnostic route. Its fit is this: The symptom has not established the failed assembly. Make the scope consequence explicit: Upfront investigation can reduce unnecessary component buying.
Interface and handover review: ask the quotation to cover drawings, configuration, receiver inspection and unresolved conditions. Its fit is this: A proposed component exists but its evidence pack is incomplete. Make the scope consequence explicit: A review clarifies scope but is not a supply or repair commitment.
Prepare the next review with original evidence
For the next enquiry, attach the frozen input list and name the decision that needs support. Ask the candidate to state included work, excluded work, dependencies and the evidence they will return. Keep the commercial response separate from technical confirmation. Use the original references below to check definitions, while retaining the scope of the actual equipment, document or task. A quotation meeting should leave a bounded action and an inspectable written scope.
[S1] Harmonic Drive Engineering Data; [S2] UR-Series Service Manual.
Primary-source reading
Harmonic Drive Engineering Data
https://www.harmonicdrive.net/_hd/content/documents1/FBB_DifferentialGear.pdf
UR-Series Service Manual
https://www.universal-robots.com/manuals/EN/PDF/Shared/service-manual_ur-series/Service_Manual_UR-Series_en.pdf