The component repair order consists of a header and part lines and is used for different types of services: exchanges and repairs. The information entered in the component repair order header is inherited to all component repair order lines. Default values retrieved from the header can be changed later on in the process.
When entering a new component repair order, the following information retrieves default values: site, reported by, coordinator, entry date and start date. You can change the default values.
Specify the customer to whom the repaired part should be sent. The parts to be repaired or exchanged must be owned by the same customer. It is not possible to handle services of components owned by different customers on the same component repair order.
In the fault information area you can describe the detected problems, i.e., the part’s discrepancy from the original form, fit and/or function. This information might be helpful later on when preparing the work, and for troubleshooting and repairs. The fault information codes are entered as basic data and can then be used on the component repair order. The reason for having predefined fault information is to consistently record the fault information, which then can be used for technical and financial follow-ups and analysis of faults and costs.
You can create CRO repairs for processing on any of the repair order types mentioned below:
Furthermore, the CRO allows you to create, view, manage and maintain CRO exchange scenarios consisting of:
As a result of this activity, a component repair order is created and receives Planned status. The component repair order keeps track of the parts and the transactions occurring during the service process. The transactions can be used to calculate the costs for the services and constitute the base for the amount to invoice the customer.