Unknown. The screenshot folder has dates, but no project identifier or link to the installed version.

Ask the integrator to identify the installed project, its dependencies and applicable fixture configuration. Keep the pictures as unverified illustrations until matched. A folder date tells you when a file was saved, not necessarily which program was running.

And which fixture-mounted coupon arrangement does the program expect? Include its tooling reference.

Sarah Bennett, both readers. Aisha, fixture reference missing too. I've asked for one identified source pack with separate operator and maintenance sections.

Make each section point back to that source revision. Otherwise you'll create two drifting handovers.

Will, let the regular cover operator try the short section. I mean use it to find the agreed information during a walkthrough, not improvise a recovery because the documentation is incomplete.

Integrator has identified the export and fixture. One called subprogram is missing from the supplied pack; I've logged that explicitly.

Keep that dependency outstanding. Also ask for the ordinary PLC agreement: request, receipt, result, clearing and interrupted-work responsibilities. The routine can call a meaningful-looking signal without explaining what the other side promises when it changes.

Can your maintainer open the supplied export from their own account?

Not tested. Integrator opened it on their laptop. I'll include access from our normal maintenance account in the walkthrough.

That is worth checking before the integrator leaves. A demonstration of their access isn't yours.

Nora, would you put the signal table in the operator section? I'd keep the normal state names and escalation there, with the full table available to maintenance rather than making the operator decode bits.

Sarah Bennett, I agree. Both sections need consistent meanings, not identical detail. The operator should recognise an unanswered request or uncertain result, while maintenance needs the named signals and owners behind those states.

Missing subprogram supplied. Our maintenance account opens the identified pack. Ordinary signal meanings are still being reconciled between the integrator and PLC contractor.

Who owns the combined explanation while those two reconcile it?

Our controls lead. Thanks Aisha; that name was missing. Operator walkthrough stays pending until the disputed meanings are settled.

Keep the disputed states visible in the draft meanwhile. A blank marked awaiting agreement is less likely to teach the wrong answer than a polished screenshot with yesterday's guessed caption.

Done. Archive access and missing dependency are closed findings; interface meanings and operator walkthrough remain open. No complete handover sign-off yet.