I am collecting notes for a training cell and noticed our stop messages are written as if the person already knows the sequence. 'Waiting for confirmation' is not much help when there are several confirmations in the same job.
What is the smallest amount of context you would put beside a stopped cycle so the next person knows what to look at, without turning the screen into a manual?
Name the current state, the expected confirmation, and who or what supplies it. That is enough to distinguish a normal wait from a missing response. The screen does not need to diagnose why the confirmation has not arrived.
That is clearer than our current wording. I can put 'waiting for fixture confirmation from PLC' beside the state, then teach that it is a prompt to check the agreed sequence rather than a diagnosis. Much less mysterious.