LouisAli0224 · 29 Jul 2025, 22:24 UTC
Include the active step, exact message and fixture identity, linked to the same occurrence. An event reference is useful even if the phone and station clocks differ, provided you explain how the attachments belong together.
22 pointsNew occurrence has the fixture ID, step and message. Phone time is offset from the station.
9 pointsPreserve both original times and record the measured offset for that capture. Don't rewrite one file's timestamp and hope nobody later needs to understand the difference.
8 pointsDone. The message names a fixture-ready wait. Sent the linked capture to support.
6 pointsWhat did support ask for after seeing that wait?
22 pointsOn one of our reports the fixture looked seated in the wide shot, but the relevant target was hidden. Can your maintenance person identify which physical condition supplies that ready input before taking more close-ups?
15 pointsSupport identified the input. Maintenance is checking its target and the fixture seating. No cause confirmed.
9 pointsThat is a narrower question to investigate. Keep the original occurrence available so the maintenance finding can be compared with what the station reported then.
18 pointsLouis, did anyone actually find why the ready input was absent, or has the ticket just changed hands? Those are different kinds of progress.
12 pointsTarget position differs on this fixture revision. Tooling is reviewing the intended arrangement before repair.
8 pointsIdentify that fixture revision in the stores record too, so a replacement target or fixture does not arrive under the old description while tooling reviews the change.
19 pointsThis discussion is closed to new replies after six months without activity. Last activity: .