I'm preparing the handover for our commissioned FR10 coupon-inspection cell while the integrator is still available. The notes show the main routine as pendant pictures, with no revision detail, subprograms, fixture assumptions or ordinary PLC signal expectations. What should I ask them to supply and explain?
Book their time before perfecting the document outline. Get the installed program identified and a supported export of it, including dependencies. Otherwise you can spend the available meeting discussing screenshots that belong to a different revision.
Who will use this during an outage? Have that person attend the walkthrough, because the integrator's idea of an obvious step may not survive their departure.
I would organise the explanation around an ordinary inspection cycle. For each stage, show the expected fixture condition, job signals and call into the next routine. Keep the signal meanings with the sequence rather than as an unexplained list of names.
Our maintenance lead will attend. I've requested the installed revision and export before the meeting, Rachel. Sarah's cycle structure looks useful for finding which assumptions are currently only in the integrator's head.
Include where approved backups live and who can update them. We had a fine handover once, then three equally plausible copies by the next outage. The folder name working did more damage than the missing paragraph.
The integrator has supplied an identified export with the called routines. Some screenshot names do not match, so I've marked them as unverified illustrations pending the walkthrough. I haven't treated the export as proof that the explanation is complete.
Good time to ask them to explain one wait in plain language. What has been requested, what confirmation is expected and what the operator should do if it never arrives? That often finds more missing context than another page of screenshots.
Thanks, Sarah. The wait question exposed an undocumented fixture assumption during the walkthrough. We now have it assigned for clarification, with the program reference established. Recovery instructions and backup ownership still need agreement.
Get dates against those two items while the integrator is available. They're exactly the bits people discover missing after the friendly handover meeting is over.