The buyer task and decision boundary
Maintenance information should keep the physical assembly, its permitted configuration and the observation history together. A new harness, feedback revision or tool adapter can change the relevant checks even if the machine still starts. Record what changed, what stayed unchanged and which task was reviewed afterwards. The work is easier to hand over when backup coverage, parameter transfer and inspection are individually visible instead of being compressed into a single completed checkbox.
Technical context: Use a controlled comparison instead of several simultaneous changes
In a hypothetical fault investigation, a harness, drive and parameter set are all changed together and the alarm disappears. The observation supports only the new combination under the observed conditions. It cannot identify which change removed the symptom. Where the equipment procedure permits, record one authorised change at a time and preserve the task conditions. Where isolation is not possible, state the limitation. Never suggest bypassing a safeguard, feedback check or protection limit to make the comparison easier. A diagnostic record should retain unsuccessful and interrupted attempts as well as successes.
A second condition to preserve: Match the observation window to the original condition
Suppose a hypothetical alarm normally occurs after an hour of ordinary operation, while the replacement was observed for ten minutes. The correct statement is that the alarm did not recur during those ten minutes, not that the fault was permanently fixed. Arrange further checks only within the device maker permitted operating conditions. State the tool, load, motion and environmental context. The service documentation used as a reference contains device-specific backup and software restrictions; it is not permission to restore an arbitrary controller image. [S2] An existing backup should be checked for identity and coverage before use.
Establish a usable baseline
For a maintained robot assembly, keep the physical revision and permitted settings together. A baseline is a described configuration and task, not merely the first number in a chart. Record identities, versions, original sources, the method and known limits. Keep raw observations beside summaries. When conditions change, mark the boundary rather than drawing an uninterrupted trend that implies direct comparability. A baseline should help a later reader understand what changed and what the earlier evidence can still support.
Use an impact matrix for every material change
For a maintained robot assembly, keep the physical revision and permitted settings together. For each changed item, list the relationships and decisions it may affect. Mark each as retained, requiring review or not yet determinable, and give a reason. Updating one document does not establish the physical state, and replacing one assembly does not validate every restored setting. The matrix should guide the necessary review, not replace it with a set of reassuring ticks. Keep responsibilities and permitted actions explicit.
Verify restoration coverage rather than file existence
For a maintained robot assembly, keep the physical revision and permitted settings together. Identify exactly what was preserved and what can be reconstructed from it. A file, exported table or backup may cover only part of the configuration. Record the applicable identity and revision, dependencies and the checks required after restoration. Do not use a similarly named file as proof of suitability. Where the relevant maker or publisher imposes restrictions, retain the original instruction and explain its applicability rather than treating it as a universal permission.
Hand maintenance information to the next owner
For a maintained robot assembly, keep the physical revision and permitted settings together. The handover should show the current state, recent changes, unresolved observations and temporary limits. Separate routine observation from authorised intervention and from formal acceptance. Preserve the reasons for data discontinuities and the scope of any follow-up task. Avoid extrapolating remaining life or future performance from a short series without evidence. The practical value is continuity: the next team can use the history without mistaking old conditions for the current configuration.
Apply the worksheet to this domain
Use the change matrix to connect robot serial identity, motor and feedback revision, parameter backup scope and supplier scope. Give each change a reason, an affected relationship and a review status. Keep the previous evidence instead of overwriting it. Separate the existence of a backup or document from its coverage and applicability. After the relevant review, record the task and conditions actually observed. If a condition cannot be recreated, state the limit and the next action. The current record should make clear what can still be relied on and what needs fresh confirmation.
Four routes and their tradeoffs
If using exact part-number replacement, preserve the baseline for suffix, revision, provenance and permitted parameter handling. Review whether its fit still holds: The installed identity and replacement basis are already known. After a change, reassess the consequence: A narrow scope still needs receipt and installed-task checks.
If using documented alternative, preserve the baseline for mechanical, electrical, feedback and controller support separately. Review whether its fit still holds: An applicable maker or responsible party has confirmed the relationship. After a change, reassess the consequence: More sourcing flexibility creates additional evidence to review.
If using diagnosis before purchase, preserve the baseline for original logs, triggering task and authorised diagnostic route. Review whether its fit still holds: The symptom has not established the failed assembly. After a change, reassess the consequence: Upfront investigation can reduce unnecessary component buying.
If using interface and handover review, preserve the baseline for drawings, configuration, receiver inspection and unresolved conditions. Review whether its fit still holds: A proposed component exists but its evidence pack is incomplete. After a change, reassess the consequence: A review clarifies scope but is not a supply or repair commitment.
Prepare the next review with original evidence
For the next maintenance review, attach the current configuration, recent change and impact matrix. Ask which earlier evidence remains applicable, what must be checked again and who confirms the current state. Retain the previous revision with its reason for change. Use the original references below to verify applicable restrictions and definitions. The review should produce a current baseline and a clear action list, rather than an unsupported assurance that every future condition is covered.
[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