Details: If this is turned on, the following fields also display: Responsibility, Profession, Preferred date, Activity group, as well as fields in which to insert Immediate action, Corrective action and Preventive action. See below for description.
Status: Unhandled, In progress and Executed. Can be set manually. When requisitioning maintenance, the statuses are set automatically, see previous description.
Shutdown required: Will be included in work orders / historical jobs that are created via event log or via requisition.
Priority: Will be included in work orders / historical jobs that are created via event log or via requisition.
Shift: If the desired shift is set as a preselection in the list view for the event log, this shift will be suggested.
Reported to: Desired shift that will be linked to the event log entry.
Stop/From: To calculate downtime, click stop to set time of downtime. Alternatively, insert manually.
Start/To: Click start when the equipment/line is in operation again. Alternatively, insert manually. When the event log entry is saved, downtime is calculated. Alternatively, do not enter a time. Reopen the event log entry in edit mode when the equipment/line starts up again and click start.
Total: Downtime is calculated automatically, see start/stop above. Alternatively, insert total downtime manually.
Project: A specific project can be linked to the event log entry. This will be included in the work order / historical job if this is created from the event log entry.
Asset: Select/find desired asset.
Produced quantity / unit: Free text. This info is in a separate column in the Excel export.
Cause of damage: The drop-down list is divided into two, i.e. the top part shows causes of damage that have previously been selected for assets linked to the same asset group as the asset for which the log entry is being created. Causes of damage are created under the menu ‘System’ → ‘Operations’. Default reports for ‘Incidents by causes’ and ‘Top 10 - Shutdown allocated to causes’ can be found in the event log menu list.
Corrected by: Look up personnel in the employee list.
Copy to @: Notification to specific email addresses. Specific mailing lists are set up in the menu ‘System’ → ‘Messages’. See separate description in ‘System’.
Responsibility: Indicate whether it is ‘Operations’ or ‘Maintenance’ that is responsible.
Profession: Will be included in work orders / historical jobs that are created via event log or via requisition.
Department: Will be inserted automatically if a department is linked to the asset that has been selected or to the superior asset.
Inquire Maintenance: If you need to select maintenance, select the registration address here. The message will be sent to the user linked to this. Registration addresses are defined under the menu ‘System’ → ‘Messages’, see separate description under ‘System’. In the list view you will be able to see information such as whether the message has been read by the recipient or not. If a work order has been created, the requisitioner will automatically receive a message that the job has been executed (approved).
Preferred date: Will be included in work orders / historical jobs that are created via event log or via requisition.
Activity group: Will be included in work orders / historical jobs that are created via event log or via requisition. The default report ‘Incidents allocated to activity groups’ can be found in the event log menu list.
Description: Description of what the log entry applies to. When a work order / historical job is created, this description will come as the default in the ‘Short description’ field (max. 50 characters). Shown as default in the list view, and is searchable.
Immediate action / Corrective action / Preventive action: Free text, is searchable, and can be listed in the list view. When a work order / historical job is created, these will populate the ‘Description’ field.
Pictures: A total of 3 pictures can be uploaded/linked to the log entry. These 3 pictures will be included in the message if maintenance is requisitioned.
Deviation: If the deviation module is activated, and the user is set up as the reporter of the deviation, a deviation can be reported on the basis of this event log entry. Note that this button is hidden when using the 'Inquire maintenance' function.
Work orders: If the user has rights to create work orders, this button will be available to the user. Note that this button is hidden when using the 'Inquire maintenance' function.
History: If the user has rights to create historical jobs, this button will be available to the user. Note that this button is hidden when using the 'Inquire maintenance' function.