Close the event after its work order is closed

When a work order was raised from an event recorded in the diary and you fully close the work order, a suggestion appears on the work order page: close the source event too, with the reason “Handled by work order”. This way the event does not stay open after the work raised from it is done.

A suggestion only, never automatic

The system never closes the event by itself. Closing the work order and closing the event are two separate decisions: you accept the suggestion, or put it off with the Not now button.

Before you start

• Permission: handling events — event:handle. By default this belongs to the shift leader, the plant-group, production and site managers, and the system administrator. Without it you still see the suggestion, but the close button is disabled and states the reason.
• Prerequisite: the work order was raised from an event that is still open (Opening a work order request from an event), and the site’s policy asks for the suggestion (it does by default).

Steps

1. Open the work order (Maintenance → Work orders) and close it with the Full close action.
2. After closing, the “Close the source event too?” card appears at the top of the work order. It shows the event’s identifier and says that the suggestion is closing as “Handled by work order”.
3. If you like, write what happened in the Note for closing field. If the policy requires a written reason the field is required (marked with an asterisk); if it only recommends one, the card says so.
4. If one of the policy’s warning rules is not met (for example closing an accident without an investigation), the card asks for a Justification as well. Enter it — without it the close cannot be carried out.
5. Press Close event: Handled by work order. A confirmation appears at the top of the work order: “Event … closed: Handled by work order.”
6. If you do not want to close it now, press Not now. The event stays open.

If you did it right

The event is closed with the reason Handled by work order, and the change — who, when, with which note — goes into a history row that cannot be rewritten afterwards, and into the audit trail.

Common problems

What you see	Why	What to do
No suggestion appears	The event was already closed; or the work order has no source event; or the suggestion is switched off in the site’s policy.	Nothing to do. The policy can be changed under Settings.
“Closing the event requires the event handling permission.”	You do not have event:handle.	Ask your administrator, or ask someone who has it.
“Cannot be closed now: …”	A blocking (Block) rule of the policy is not met, for example nobody has reviewed an accident yet.	Meet the condition, or ask for the rule to be changed in the policy.
“Closing requires a written note.”	The policy asks for a written reason and the field is empty.	Write the note and press the button again. The card stays.
“The event changed in the meantime — refresh the page.”	Someone else changed the event in the meantime.	Refresh the page and look at the updated suggestion.
“The ‘Handled by work order’ close reason is not available.”	The reason has been archived.	Ask the administrator; a factory reason cannot be archived, so this is rare.

Good to know

• The card appears after the close and stays until the page is reloaded. If you press Not now or leave the page, the card disappears. You can also close the event later: in the side panel of the event in the Reports → Events table (Handle events from the table) — with the same policy rules.
• The rules come from the policy. Whether text is needed and what closing an accident requires is set in the closing policy.
• The event’s status does not appear in the diary or in the shift PDF. The closing goes into the event’s history and does not change the content of the diary or the PDF.

Related

Opening a work order request from an eventHow the work order the suggestion comes from is created.

Rules and reasons for closing eventsThe suggestion switch, the text and HSE rules.