Which FR10 routine supplies the bracket identity missing from our handover pictures?

BenBarnes0544 · 17 Jan 2026, 09:30 UTC

Closed
BE
BenBarnes0544
Our FR10 main-routine pictures omit the bracket-identity lookup. How should we recover its dependencies with the integrator?

21 replies

JA
JasperAbbott0029
Replying to BenBarnes0544

Follow the installed job, not the screenshots. Ask the integrator to show where that identity comes from and which routines or configuration it depends on. Bring whoever will support it after handover.

18 points
TH
ThomasBaker0451
Replying to BenBarnes0544

Does the lookup choose the inspection job, or only put a name on the display? Both need explaining, but I wouldn't assume a misleading label means the wrong inspection was selected.

12 points
BE
BenBarnes0544
Replying to ThomasBaker0451

It selects the inspection job from the fixture identity. Relief maintainer is joining the walkthrough.

11 points
AN
AnikaAdams0160
Replying to BenBarnes0544

Take the actual inserts to that walkthrough too; the storage label can look perfectly convincing while naming a different piece from the one sitting in the cell.

-2 points
SO
SofiaBell0630
Replying to BenBarnes0544

And let the relief maintainer find the answer before the integrator points to it. I sat through a handover where every pause got filled by the person who built the thing. We all nodded, then the first ordinary wait after he left became a group guessing competition. Not because the screen lacked information. Because none of us knew where he had been looking.

9 points
BE
BenBarnes0544
Replying to SofiaBell0630

Yes. Integrator will demonstrate once, then the relief maintainer will use the draft without prompting.

10 points
JA
JasperAbbott0029
Replying to SofiaBell0630

Sofia, that sounds painfully familiar. Our handover improved when the demonstrator finally stopped saying it's just here before anyone had time to look.

10 points
TH
ThomasBaker0451
Replying to BenBarnes0544

Get the routine and configuration revisions with that draft. A clear explanation tied to the wrong lookup table can teach the next person exactly how to make the wrong selection.

17 points
BE
BenBarnes0544
Replying to ThomasBaker0451

Recovered the called routine and lookup configuration with their revisions. One pictured insert belongs to the previous job.

24 points
AN
AnikaAdams0160
Replying to BenBarnes0544

Then use a current physical example, including the insert's installed identity; don't simply replace the caption under the old photo and leave its different geometry teaching the loader.

17 points
SO
SofiaBell0630
Replying to BenBarnes0544

What does the maintainer see if the fixture identity isn't recognised, Ben? I'd want that in the exercise, not only the happy lookup where every name agrees.

8 points
BE
BenBarnes0544
Replying to SofiaBell0630

An unresolved identity message, with no inspection job selected. We'll include that case and its support contact.

0 points
BE
BenBarnes0544
Replying to BenBarnes0544

Walkthrough completed. Relief maintainer found the lookup, but the support contact in the unresolved case was obsolete.

16 points
JA
JasperAbbott0029
Replying to BenBarnes0544

Better to find that while everyone is there. Was it an old person's name or the wrong company? The replacement needs to reach someone who actually owns that lookup.

4 points
BE
BenBarnes0544
Replying to JasperAbbott0029

Old integrator contact. Their current support desk owns the lookup enquiry and has confirmed the route.

14 points
AN
AnikaAdams0160
Replying to BenBarnes0544

Has stores also got the current insert references now, or only the maintenance folder? I'd rather not supply the old pictured insert correctly labelled and recreate this confusion from the cupboard.

8 points
BE
BenBarnes0544
Replying to AnikaAdams0160

Stores has the current references and withdrawn photo marked obsolete. Actual insert identities matched during the walkthrough.

20 points
TH
ThomasBaker0451
Replying to BenBarnes0544

Were the ordinary PLC waits covered as well? Finding the lookup is useful, but a maintainer still needs to know whether the selected job is waiting for something outside that routine.

14 points
SO
SofiaBell0630
Replying to ThomasBaker0451

Thomas, yes, and the support contact should change with the cause. I don't want every ordinary receiver wait turned into a call about fixture identity just because that is the first chapter.

24 points
BE
BenBarnes0544
Replying to SofiaBell0630

Both covered in the repeat exercise: unresolved identity and receiver unavailable. Maintainer found each owner unaided. Handover accepted, thanks.

10 points

Discussion closed

This discussion is closed to new replies after six months without activity. Last activity: .