When scheduling work order a log is now created. This enables getting information as to how many times a work order has been scheduled. Also remarks can be given explaining why the work order was scheduled.
When work orders are scheduled, logs are created. This is done to capture how many times a work order has been rescheduled. A log is created when a work order is scheduled from:
Schedule logs can be seen from:
When a log is created the following information is currently being captured.
At the bottom of the schedule log form, the total number of times a selected work order has been scheduled is shown.
Schedule log entries cannot be deleted. No set up is required, if Advanced asset management is active the functionality and menu items is available.
A new security privilege has been added 'View work order schedule logs'. The privilege has been added to the security duties Work order maintain and Work order view.
When scheduling work order, a remark can be added to the schedule log, so that users may capture the reason as to why the work order is scheduled.
The remark is added to the schedule log.
The Remark field has been added to 'Schedule work orders', Dispatch, and 'Delete schedule'. It has not been added to Schedule on Work order maintenance jobs.
There is no setup for Remarks on schedule logs. The field will always be available if Advanced Asset Management is enabled.
It is possible to set up a fixed set of remarks for easy selection when scheduling.
On the work order lifecycle states, described in the mandatory remarks section, users can add remarks. If set up the lookup button in the field will be visible. Note, users can select a remark, but they can still alter it and change it any way they want. The remarks set up is not fixed.
It is possible to set up that remarks are mandatory when scheduling. On a work order lifecycle state, it is possible to set up that a remark is mandatory.
For 'Schedule work orders' and Dispatch we use the work order lifecycle state set up on the work order lifecycle model for 'Schedule state'.
For 'Delete schedule' we use the lifecycle state set up on the work order lifecycle model for 'Unscheduled lifecycle state'.
For a fixed remark it is possible to set up reason codes. The intention with the reason code field is to display the reason code associated with the selected remark. When set up, the field for Reason Code is shown. Users cannot edit the reason code.
By selecting a remark, it is possible to update the reason code field.