Work Order Processing

The main process WO Processing is used in IFS/Maintenance, in other words, internal maintenance. When using internal maintenance, you have your own employees in the business who have the knowledge on maintaining the objects within the company. 

The Work Order Processing contains the following steps: 

• Evaluate the service requests and the fault reports. You can either query for the work order, or receive information on the work order from the event server. Evaluate it and change the status of the work order. 
• Prepare work orders with general information, budget estimates, customer, etc. Estimate the budget as well by looking over the costs and revenues (if IFS/Service Management is used). If the work order is to be scheduled by PSO, set up the scheduling data, e.g., define employees as scheduling resources, register datasets, broadcasts and the scheduled tasks which should be used for transferring data to the Scheduling Engine. Based on dataset and broadcast set up, a scheduled plan will be returned to IFS Applications. If the plan is suitable, assign the work order either to the currently logged on user or to the employee suggested by the Scheduling Engine.
• Create a repair work order on the broken serial object or the non-serial part to be corrected. You have to define the repair workshop where the serial object can be repaired.  With the help of the system, you have control over where the serial part is, the running costs for the serial object, which repair has been done on the object, etc. You always have the possibility to follow the serial object as a component among other components within the establishment. The three possible destinations for the serial object include the facility, the repair workshop, and the inventory. The parts that are not registered in the system, such as traditional serial objects, are called non-serial parts. The reason not to register these parts as serial parts is because they are not in need of detailed information such as serial transaction history and repair costs, and that you want to save the administration of the part. If a non-serial part gets broken, the system can be configured such that it automatically creates a repair work order for this part. Once the broken part is repaired, it will be returned to inventory. The customer then has to scrap the part, or move the part into inventory before the repair work order can be set to "Finished."
• Soon after the reported fault/work request is evaluated or planned, the work order or the work tasks can be transferred to one or many mobile devices owned by technicians who are working for the service organizations belongs to the work order site, if IFS Mobile Application is installed in their devices and if there is a requirement for them to work on field. Technician can process the work assignments while they are on field and report their work. If they have access to internet while on field can update the IFS system while processing the work assignments. 
• Execute the work through the work assignments connected to the work tasks. Create pick lists and issue the parts that are needed for the work tasks. If no parts are included, simply change the status to "Started" and perform the work on the work task.
• Before concluding the work tasks, report in actions, time, tool/equipment, expenses, external costs and unissue or return parts that were not used or replaced. Once the reporting is done, the financial manager creates a voucher. Voucher updates are conducted from a hold table in IFS/Accounting Rules™. All vouchers generated in any of the modules are placed in the hold table and then updated to the general ledger. The item becomes fully traceable from here.Authorize all work task transactions and invoice if required to the customer (if IFS/Service Management  is used). Then conclude the work tasks.
• Once all work tasks are completed and report in actions are performed the work order can be concluded.