IMPORTANT |
It is extremely important that you set up and work within your own site to maintain you data integrity. If you work within any other site, you will compromise your own exercise data as well as the data of other students. Predictable exercise results require that your data be isolated in your own site. |
Purpose: The purpose of this exercise is to create the part to be repaired.
Windows:
Inventory Part
Note: If you have not yet already done so, create the following:
Part No | Description | Part Type |
XX-187-CS | Chain Saw 187 | Manufactured |
General exercise for Manufactured Inventory Part
Purpose: The purpose of this exercise is to set up the customer data for the customer to be used in main exercises below. The repair part is owned by this customer.
Windows:
Customer
Note: If you have not yet already done so, create the following:
Customer | Description |
XX-CMRO | Customer for CMRO |
General exercise for Customer
Purpose: The purpose of this exercise is to enter a coordinator responsible for the coordination of the dispatching customer order for the return of the repair part to the customer.
Windows:
Coordinators
Note: If you have not yet already done so, create the following:
Coordinator ID | Name |
Your ID | Your name |
General exercise for Entering Coordinator
Purpose: A service type is a way of grouping actions possible to perform for a part in order to bring it back to its original fit and/or function for different kinds of faults.
Windows:
Component Repair Order Basic Data/Service Type
Note: If you have not yet already done so, create the following:
Service Type | Service Type Description |
XX-ST01 | 200 h Chain Saw Overhaul |
XX-ST02 | Fuel System Overhaul |
XX-ST03 | 1500 h Complete Chain Saw Overhaul |
General exercise for Service Type
Purpose: The purpose of this exercise is to set up a non-inventory sales part. This part is needed since it will act as the invoicing object for the service types.
Windows:
Non-Inventory Sales Part
Non-Inventory Sales Part No | Description | Base Price |
XX-CS-Service | Chain Saw 187 Service Part | 250 |
General exercise for Non-Inventory Sales Part
Purpose: Repair codes are a way of grouping standard jobs for the work order and material and/or operations for repair shop order. The purpose of this exercise is to define the repair codes which will be connected to the part to be repaired, as well as to the service types connected to that part.
Windows:
Repair Setup Basic Data/Repair Code
Note: If you have not yet already done so, create the following:
Repair Code | Repair Description | Note |
XX-RCCS-1 | Cleaning, Chain Saw 187 | The repair code includes the following actions:
|
XX-RCCS-2 | Fuel System, Chain Saw 187 | The repair code includes the following actions:
|
XX-RCCS-3 | Chain Brake, Chain Saw 187 | The repair code includes the following actions:
|
General exercise for Repair Code
Purpose: The purpose of this lesson is to prepare the inventory part for being processed on a component repair order in Component MRO. Start with connecting service types for the repair part and update the service price.. A service type has two purposes, to define a work scope and to act as price label for the work performed.
Continue with connecting repair codes to service types and to repair part. Repair codes are a way of grouping standard jobs for the work order and material and/or operations for repair shop order. By connecting repair codes to service types you can create a predefined work scope when repair shop order or work order is selected as supply for the component repair order line.
Windows:
Part Service Definition and Pricing
Part Service Definition and Pricing/Service Types
Repair Setup Basic Data/Repair Code Part
Repair Part | Service Type | Service Part No | Service Part Description | Base Price | Service Price |
XX-187-CS | XX-ST01 | XX-CS-Service | Chain Saw 187 Service Part | 250 | 500 |
XX-187-CS | XX-ST02 | XX-CS-Service | Chain Saw 187 Service Part | 250 | 1200 |
XX-187-CS | XX-ST03 | XX-CS-Service | Chain Saw 187 Service Part | 250 | 2000 |
Repair Code | Part No |
XX-RCCS-1 | XX-187-CS |
XX-RCCS-2 | XX-187-CS |
XX-RCCS-3 | XX-187-CS |
Service Type | Repair Code |
XX-ST01 | XX-RCCS-1 |
XX-ST02 | XX-RCCS-2 |
XX-ST03 | XX-RCCS-1, XX-RCCS-2. XX-RCCS-3 |
General exercise for Defining Services and Pricing
Purpose: The purpose of this exercise is to establish a service contract with your customer. The service contract offers a possibility to differentiate how to invoice the customer for service types connected to the part.
Windows:
Service Contract
Note: If you have not yet already done so, create the following:
Important: It is not possible to do the Define Component Repair Order Work Scope, No Existing Service Contract exercise when the part service contract is active.
General exercise for Part Service Contract
Purpose: The purpose of this exercise is to create and process two component repair orders containing a component repair order line each. The first component repair order is not related to any service contract while the second one is related to a service contract.
Windows:
Component Repair Order
Note: If you have not yet already done so, create the following:
Component repair order 1, without service contract
Component repair order 2, with service contract
Component Repair Order | Customer No | Part No | Service Types |
1 | XX-CMRO | XX-187-CS | XX-ST01 and XX-ST02 |
2 | XX-CMRO | XX-187-CS | XX-ST01, XX-ST02 and XX-ST03 |
General exercise for Entering Component Repair Order
Purpose: The purpose of this lesson is to calculate the accumulated transaction costs for each service type, which constitute the work scope for a component repair order line. Furthermore, you will learn how to create sales lines for the performed service types and transfer them to a customer order for processing and invoicing.
Windows:
Component Repair Order
Create Pick List for Customer
Print Pick List for Customer Orders
Report Picking of Customer Orders
Create Customer Invoice
Customer Invoice
Note: In order to get an overview of the costs, as well as monitor how much they have grown compared to the price defined in the Service Price field, you can calculate cost lines at any time during the processing of component repair order lines.
Note: On the Service Type tab, the < Resources Used column, the total cost for performed services can be viewed as soon as you have calculated the cost lines.
No service contract should be established with customer XX-CMRO and the component repair order line should preferably be in Completed or Signed Off status.
Note: A recommendation is to create sales lines when the component repair order line is in Completed or Signed Off status.
Note: If repair shop order or disposition shop order is selected as repair order type for a component repair order line, then no consideration is taken to scraped part when calculating the cost. This means that, when using Resources Used as invoice type for a service type, the transactions for replacement part are included in the cost on which the sales price for the service type is based.
A service contract must be established for Customer XX-CMRO and the component repair order line should preferable be in in Completed or Signed Off status.
Note: The total price for a service type with invoice type Resources Used is displayed in the Resource Based Service Price column on the Service Type tab as soon as the sales lines are calculated.
The customer XX-CMRO is requesting a component repair. A component repair order must exist, with a component repair order line preferably in Completed or Signed Off status. A customer order must also be pegged to the component repair order line.
Note: The supply code for the transferred sales lines is Service Order and all functionality related to this supply code is applied.
Note: The non-inventory sales part connected to the service type in the Part Service Definition and Pricing window is used as invoicing object for the service type. If a service contract is applied for the component repair order line and the executed service type uses Resources Used as invoice type, then the non-inventory sales parts are connected to the cost categories in the CRO Cost Category tab in the Service Contract. There they are used as invoicing object for the cost categories.