简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。

Cannot choose which stop details belong in our FR5 housing ticket

LuisBaker0521 · 2025年10月1日 05:38 UTC

已关闭
LU
LuisBaker0521
My FR5 housing-loader report has a phone video and a screen photograph. Different occurrences. The seller has treated them as one event. I need to untangle that before another shift sends a third version.

12 条回复

AD
AdaAbbott0042

Tell the seller explicitly that the photograph is unmatched. Leave it available as a separate occurrence rather than deleting it. Which useful details can you recover for the video itself?

23
LU
LuisBaker0521

Tray identity is visible. Occurrence time came from the operator's shift note. The message is too small to read.

-2
SA
SamBell0681

Can maintenance use that time to find the matching log? I mean the actual shift-note time, not the time someone forwarded the video. We mixed those up once and searched the wrong end of a shift.

8
LU
LuisBaker0521

They found a log entry near it, but cannot yet confirm it is the same stop. Several pauses happened around then.

14
AD
AdaAbbott0042

Then do not attach that entry as a match yet. Tell support exactly what remains uncertain and ask what they need captured together at the next occurrence.

20
BE
BethBrooks0846

We had a tray-loading investigation where three similar pauses became one story on the support desk. The useful change was an event note the shift could actually fill in: what had just happened, which fixture, what the screen said. Not a form demanding ten things nobody could see.

0
SA
SamBell0681

Beth, did one person collect the logs afterwards? Our operators can note the screen and tray, but asking them for a software export would make the report wait until I arrive.

9
BE
BethBrooks0846

Maintenance collected ours, Sam. Operator's time and setup details gave them somewhere to start. They still marked a log unmatched if it was uncertain; a filled box was not worth sending the investigation the wrong way.

23
AD
AdaAbbott0042

That split sounds sensible. Luis, can your maintenance cover retrieve the required details on each shift, or does the support plan still depend on you being there?

11
LU
LuisBaker0521

Each shift has maintenance cover. We agreed who captures the log and who makes the operator note. New occurrence has both, with a readable waiting-for-fixture message. Controls is checking the matching input state.

14
BE
BethBrooks0846

That's a better starting point. Which fixture confirmation is it waiting for, Luis? Visible hardware in position doesn't necessarily tell controls which part of the signal path failed.

9
SA
SamBell0681

And keep that occurrence in the existing ticket. Thanks Beth for explaining the shift split; I'm taking that part back to our team, not the particular message from Luis's job.

6

讨论已关闭

此讨论已连续六个月没有活动,现已关闭新回复。 最后活动: .