Report Details of Work Order Operations with Work Orders

This instruction explains how you report an operation after the work has been completed. When you report an operation, you report the time spent on the operation and the materials that were used.

Outcome

The operation is fully reported. When applicable, additional materials, time and employees are added to the operation.

Depending on the system settings, these results can be expected:

  • The work order operation is closed and, where no approval is required, the work order is automatically closed.
  • The work order operation is closed, but needs further approval. These operations will be given status 89 and can be viewed in 'Work Schedule. Open Toolbox' (MOS195) before final approval.
  • A diagnostics message is issued and the diagnostics structure is automatically created.
  • Materials with issue method 4 or 6 will be reported automatically.
  • The load on the work center will be reduced depending on the selected work center load reduction method in 'Work Center. Open' (PDS010).

Depending on the parameter settings and the results, the following operations may be performed:

  • The work order operation can be approved and closed.
  • The work order operation can be approved and the work order header can be manually closed.
  • The work order operation can be approved automatically and the work order header can be closed manually.
  • If tools have been allocated to the operation, they can be deallocated, either automatically or manually, in 'Allocation. Deallocate Tool' (MMS127) or 'Tool. Allocate' (MOS127).

Information about the transactions is saved in these tables:

  • 'Work order operations' MMOOPE
  • 'Operation transactions' MMOPTR.

Before you start

The starting conditions listed in Reporting Operations and Inspections should be met.

Parameter settings that impact the result:

  • If the process should be completed automatically, the following settings should be defined:

    The work center flag 'Verify operation close' in 'Work Center. Open' (PDS010/F) must be set to 0.

    'Close by (MOS050)' must not be set in 'WO Operation. Report' (MOS070/P). If a record exists in 'WO Type. Connect Facility Parameters' (MOS122), automatic WO closure should be set.

  • If the work order operation should require approval before closing, but the work order header should close automatically, the following settings should be defined:

    The work center flag 'Verify operation close' in 'Work Center. Open' (PDS010/F) must be set to 1.

    'Close by (MOS050)' must not be set in 'WO Operation. Report' (MOS070/P). If a record exists in 'WO Type. Connect Facility Parameters' (MOS122), automatic WO closure should be set.

  • If the work order operation should require approval before closing, and the work order header should be closed manually, the following settings should be defined:

    The work center flag 'Verify operation close' in 'Work Center. Open' (PDS010/F) must be set to 1.

    'Close by (MOS050)' must be set in 'WO Operation. Report' (MOS070/P). If a record exists in 'WO Type. Connect Facility Parameters' (MOS122), automatic WO closure should not be set.

  • If the work order operation should NOT require approval before closing, and the work order header should be manually closed, the following settings should be defined:

    The work center flag 'Verify operation close' in 'Work Center. Open' (PDS010/F) must be set to 0.

    'Close by (MOS050)' must be set in 'WO Operation. Report' (MOS070/P). If a record exists in 'WO Type. Connect Facility Parameters' (MOS122), automatic WO closure should not be set.

Follow these steps

  1. Start 'WO Operation. Report' (MOS070/H).

    The program can be started in the following ways:

    From 'Work Schedule. Open Toolbox' (MOS195), select the operation and then select option 'Report Operation'.

    From 'Work Order. Open' (MOS100), select the work order and then select option 31='Report WO Operation' to display 'WO Operation. Report' (MOS070/B). Then double click the operation to report to display the report panel.

  2. Specify the time used for setting up the operation and the time spent performing the operation.

    The time specified here should be the actual time spent on the operation. Remember to use the unit that is specified for the work center, which is usually hours. The time can be set to be defaulted using an F13 parameter. If so, the estimated time for the operation will be proposed for the actual time. Time already recorded will be displayed next to this field.

    Time can be logged for multiple users with the F14 function. F14 uses 'WO Operation. Report Employee' (MOS075). If this function is to be used, the employees must be defined in 'Employee. Connect Calendar' (CRS510), 'User. Connect Authority' (CRS545), etc. When this function is used, the hours logged against the employee are automatically accumulated on the (MOS070) screen.

  3. Specify the time used to set up and run the machine (optional and not normally used for plant maintenance).
  4. Specify the disturbance code, if applicable, and the setup disturbance code (normally not used within plant maintenance) .

    Disturbance codes are predefined and are used to indicate disturbances that have affected the operation or the operation setup.

  5. Specify the downtime, if required, and specify whether the operation is now completed.

    Downtime is used for statistics.

    The completion flag is defaulted from the service from which the operation originated. This is set on the (MOS301/E) panel.

  6. If applicable, specify the time the operation was delayed because materials were late or machines were not stopped in time.
  7. Specify an employee identity, if applicable.

    Additional employees can be added using F14=Report Employee Number.

  8. Specify error codes, if applicable.

    Error codes are predefined and can be used in different ways. One example is to use error code 1 for a symptom, such as that smoke has been detected. Error code 2 could then be a cause code, such as a loose cable. Error code 3 could be the solution, such as refitting.

    Error codes can be linked directly to the equipment/serialized item. If this is not done, all available error codes will be displayed. Error codes can be made mandatory if the parameter 'Failure effect category' in (MOS300/F) is set to a value between 1 and 3.

    When error codes are displayed in (MOS070), they are displayed according to a hierarchy. M3 initially checks for a record in (MMS238) (the lowest level). If no record is found there, M3 checks in (MOS478) (option 'Diagnostics' from (CRS025)) where error codes are linked to item/equipment types. Finally, if these do not exist, M3 goes to (MOS572) (the highest level).

  9. Specify the work center that actually carried out the work (if it is different from the one on the work order), an overtime costing type (when applicable), and an optional user-defined text.

    The overtime costing type entered here will override the standard rate.

    Two text lines may be added here. More text can be added through the notepad option. The text block ID will be 'MOS070'. This allows the original request text and the report text to be viewed separately.

    • Specifying the position and equipment fields:

      The position will normally default from the original work request and not be changed.

      The equipment number will normally default from the original request. If it does not, the field can be set to be mandatory using the F13 parameters or 'WO Type. Connect Facility Parameters' (MOS122). It is normally good practice to link work orders to equipment. This enables statistics to be analyzed at the correct level. If only a position is specified, the history may not be as useful.

  10. Press Enter to save and finish.

    If the completion flag has been selected, the operation will be closed. If this is the last operation to be closed, then the system will either close the work order header automatically or display 'Work Order. Close' (MOS050) to allow it to be closed manually.

Note: Even if skills are used for the work, capability is not verified when reporting is done using (MOS070) as the job has already been completed.