I'm reviewing a commissioned UR5e inspection cell while its original integrator is still available. Handover is mostly main-routine screenshots, no revisions, called routines, fixture assumptions or ordinary PLC definitions. What should the maintainer be able to trace before we accept the pack?
Trace an identified coupon through the installed program set, fixture conditions and ordinary request/result exchange. Ask for the complete project and revision record first; screenshots can illustrate the route but cannot supply missing dependencies.
I've requested the installed project and supported backup instructions, with the fixture drawing and PLC interface sheet linked to the same revision. The integrator agrees to a walkthrough.
Include a wait or interrupted inspection in that walkthrough. A completed route can hide who owns an uncertain coupon and which condition stops the next action; that is often the part a maintainer actually needs.
Have another maintainer follow the pack, not only listen to its author. Can they locate the actual called routine and explain the wait from the supplied information? That is different from recognising a screenshot while the integrator narrates it.
Project received and normal route traced. The second maintainer found a fixture-confirmation wait whose PLC meaning differs between the sheet and the explanation. We have marked that discrepancy rather than choosing the version that sounds nicer.
Ask both interface owners to reconcile it against the installed behaviour and identify the corrected revision. Do not edit the process merely to make the paperwork agree while the handover review is in progress.
The owners corrected the sheet: it had described completion where the installed exchange acknowledges receipt. Maintenance can now trace that wait. Approved interruption recovery remains to be explained and checked, so the handover stays open.