Same here. Link worked on the integrator's account, nowhere else. Check access before polishing the index.

I like a short index, though. One place telling me which fixture drawing, program export and interface sheet belong together, even if the details live elsewhere.

Rebecca, our maintenance account can open the folder. It contains screenshots and an undated export. Lin, an index would help, but first we need the integrator to identify what is actually installed.

An undated export is a question, not a backup you can rely on. Ask them to establish its relationship to the installed version before anyone tries restoring it.

Include the called routines. Our main file opened beautifully and then asked for something nobody had.

Bruno, did somebody test opening the package from the maintenance account before handover?

No. They demonstrated it on their laptop. We learned the difference during the first support call.

That is a useful handover check in its own right, Rebecca. I would have a second person follow the index and locate a named subroutine without the integrator pointing at it.

And ask that person to explain an ordinary request and its completion from the interface sheet. Finding the right files is necessary, but it will not rescue an undefined signal meaning.

Our integrator has identified the installed export and supplied two omitted routines. The PLC sheet still calls one signal done where the application notes say request received. Both authors need to settle that.

That's a real disagreement. Don't make your training sheet choose a winner for them.

It may help to draw one housing check with the events in order. Not a new interface design from maintenance, just a way for the authors to expose which moment each word describes.

Keep the fixture assumptions nearby too. Software can be correct for a nest that isn't fitted.

Bruno, yes. Especially if an input means the selected fixture is available rather than merely that something is present. The physical meaning needs a drawing reference, not a confident label.

The fixture reference matches the installed nest. I've arranged the joint interface walkthrough and a maintenance-account file check. Thanks, Rebecca, the access question made us include the actual support account from the start.

Can the other shift attend the interrupted-cycle part, or will they only get the notes?

I'd record their unanswered questions if they can't. Our setter once found the missing explanation immediately because he hadn't been in the meeting where everyone silently agreed what a phrase meant.

Other-shift maintenance will join. The files are much more useful now, but I won't call the handover complete while request receipt and completion still mean different things to the two authors.