See also:
REKA is a tool provide by Daimler to the markets to pinpoint and to focus on performances, on processes with room for optimizing on:
Note: It is possible to collect and export, or view data for all business units per point-of-sale company depending on the parameter settings via the REKA Tool (Workshop Analysis) form or automatically in Timed Operations using the option MSMBWSA in the MS module.
It is also possible to collect and export stock value data depending on the parameter settings via the Collect Stock Value For REKA form or automatically in Timed Operations using the option MSMBCSV in the MS module.
For both Timed Operations options the company number must be set to MB and for the MSMBCSV option the Enter SM Company code parameters must be set to **.
Note: For the export function of the REKA Tool (Workshop Analysis) you need to set up the Communication type called REKA.
This form is displayed when you click Manufacturer systems (Module) and MB. Mercedes-Benz (Company) > Menu - Utilities > Mercedes-Benz parameters and you browse to + Service > + REKA Tool (Workshop Analysis) > [Company] on the Project parameters browser.
Tabs:
The data collection tool determines a business unit based on the Point-of-Sale department type that is specified on the POS department record and the vehicle franchise as specified on the WIP.
Departments without a department type or with a department type not specified in the Department Mapping table are not considered within the analysis tool. This also applies for workshop orders having a department type / franchise combination that is not available in the Department Mapping table.
All data will be separated into a maximum of seven departments:
Grid:
REKA: Displays the seven departments.
Department type: Select the Point of sale department type.
Vehicle Franchise: Enter the single letter franchise codes applicable for this department to determine the correct business unit.
Note: A maximum number of five vehicle franchises can be defined per department. The Vehicle franchises fields are not applicable for the bodyshop and paintshop departments.
Note: It is possible to define the mapping of department types to bodyshop and paintshop departments with the Department codes in Point of Sales.
On this tab it is possible to map the non-productive time information collected from Autoline to codes used in the REKA tool.
Grid:
REKA ID: Displays the REKA ID.
Description: Displays the description of the REKA ID.
Idle code: Enter the Workshop loading Idle time codes.
Note: It is possible to define up to ten different idle codes per REKA ID.
Adjustment code: Enter the Workshop loading adjustment availability codes.
Tip: It will be possible to define up to ten different adjust availability codes per REKA ID.
Warning:
The following idle time code does not exist (yet): Displays idle codes entered in the idle codes column in case they do not exist in the Workshop Loading Idle times form.
The following adjustment codes do not exist (yet): Displays adjustment codes entered in the idle codes column in case they do not exist in the Workshop Loading Adjusted availability reasons form.
Note: If and Idle time codes or Adjustment codes are displayed in this section the user has to either correct the mapped code or create the code in Workshop Loading.
When mapping an Autoline idle time code or adjustment code to a REKA ID the parameter program checks if no duplicate codes are entered. If a duplicate code is detected a message is displayed.
The breakdown of the mechanic‘s non productive time by department, is based on Analysis code in the Resources form to define the mechanic’s department. The first digit of the analysis code refers to the department code of the resource as specified in the Point-of-sales departments table. From the department type on the Department codes in Point of Sales it is possible to define the corresponding department:
The extraction of productive hours, hours sold and turnover is only done for actual labour lines. Actual labour lines will be those lines with an RTS code starting with a character before the one specified in the Non labour code offset parameter on the Labour tab of the POS parameters - 2 form.
When considering non-productive hours, system will include workshop calendar, adjusted resources availability, resources shift allocation and shift settings; to determine the start hours and end hours for a particular mechanic on a particular day. If the mechanic comes to work earlier and start clock-in to idle time, then the clocked idle time before shift start will not be included into the idle time calculation. Similarly, if the mechanic clock to idle time before shift end, and forgot to clock-out from work, then the idle time clock after shift end will also be excluded from idle time calculation.
For parts turnover the system is based on the third digit of the marketing code (Sales code) of parts in Stock Card or analysis code on parts line to determine parts category. It will include also some labour lines into parts turnover calculation based on the first digit of the labour type code on labour lines.
For Daimler parts the system is based on marketing code of parts in the Stock Card. For local supplier parts the user is able define whether to use marketing code or analysis code to categorize the parts. The categorization can be setup in a new table to map spare parts categories required in REKA with parts marketing code/analysis code and labour type code.
Fields:
Parts franchise: Select a franchise from the list.
Buttons:
Add: Adds the selected Parts franchise to the grid.
Remove: Removes the franchise which is selected in the grid.
Note: Upon confirming to delete the franchise changes will be made permanent.
Grid:
The user is allowed to add multiple records for the same REKA id as long the franchise is different. Per record it is possible to fill either the analysis code or the parts category (third digit of the parts marketing code).
REKA ID: Displays the REKA ID.
Description: Displays the description of the REKA ID.
Franchise: Displays the added franchises.
Analysis code: Enter the analysis codes required.
Parts category: Enter the parts categories required.
Note: When entering analysis codes or parts categories a check will be performed if the codes entered are unique for the franchise. If a duplicate code is found a message is displayed and the user is required to correct the codes entered.
Non labour rate mapping Grid:
REKA ID: Displays the REKA ID.
Description: Displays the description of the REKA ID.
Labour type: Enter up to ten non labour type codes.
Note: Validation checks are added which prevent that the same labour type codes are used on different REKA ID’s. The entered labour type codes are validated against the SO.rates table to ensure that the entered codes are known labour type codes.
The user can define how the REKA interface should determine warranty, internal or external invoices.
Account type mapping:
Define account type by: Select how you want to define the account type. The current logic to determine a warranty account based on the VEGA warranty parameters will remain active when this parameter is not setup.
A Account type: When selected the [description] in the fields below displays account types. The REKA interface will in this case use the Account type parameter on the SL account record to determine the type of invoice.
C Category code: When selected the [description] in the fields below displays category codes. The REKA interface will in this case use the Category code parameter on the SL account record to determine the type of invoice.
Warranty [description]: Enter up to ten account types for warranty accounts based on the Account type. Or, enter up to ten category codes for warranty accounts based on Category code.
Payment codes: Enter up to ten payment codes to determine the differentiation between the warranty, internal and external work for invoiced as well as non-invoiced WIP lines. The payment codes entered here are defined for warranty work.
Internal [description]: Enter up to ten account types for internal accounts based on the Account type. Or, enter up to ten category codes for internal accounts based on Category code.
Payment codes: Enter up to ten payment codes to determine the differentiation between the warranty, internal and external work for invoiced as well as non-invoiced WIP lines. The payment codes entered here are defined for internal work.
Note: Non-mapped payment codes will be reported as external hours.
The default setting for these parameters are:
Define account type by: A
Warranty account types: W
Internal account types: I
Related REKA-ID’s:
| Productive hours | REKA ID | |
|---|---|---|
| Warranty account types | 4.1.1.2 | |
| Internal account types | 4.1.1.3 | |
| Non internal and warranty types | 4.1.1.1 | |
| Gross turnover labour | REKA ID | |
| Warranty account types | 10.2 | |
| Internal account types | 10.3 | |
| Non internal and warranty types | 10.1 | |
| Gross turnover labour | REKA ID | |
| Warranty account types | 6.1.2 | |
| Internal account types | 6.1.3 | |
| Non internal and warranty types | 6.1.1 | |
| Labour rate | REKA ID | |
| Labour rate warranty and goodwill | 7.2 | |
| Labour rate internal | 7.3 | |
| Labour rate external | 7.1 | |
The user can map nominal ledger accounts to a REKA ID and business unit. The mapped records are displayed in the grid and can be filtered based on the REKA ID and/or the business unit code.
Cost consideration:
Activate the NL cost: Select to activate the extraction of the costs as defined in the grid.
REKA ID: Select to filter the grid for the REKA ID.
Business unit: Select to filter the grid for the Business unit.
Grid:
The Nominal Ledger company code is based on the Point-of-Sale -> Nominal Ledger company mapping. You cannot map the NL account more than once but you can map more than one NL account to the same REKA ID / business unit.
Cost center: Select the Cost center. The cost center plus description are displayed.
Expense code: Select the Expense code. The expense code plus description are displayed.
REKA ID: Select the REKA ID which is available for mapping to an NL account.
Business unit: Select the Business unit.
Grid Shortcut Menu:
Add line: Adds a new row to the grid.
Tip: Right-click the grid header to add a line.
Delete line: Deletes the selected grid row and refreshes the grid.
Extraction of parts stock value and dead stock value:
Mark parts as dead stock after: Enter the number of month when parts which are not moved are considered as dead stock.
Stock locations: Enter up to ten stock locations which are considered in the stock value collection. By default all nine locations are considered by the collection process.
Generate CSV verification files: Select to generate CSV verification files, when the Collect Stock Value For REKA function is used.
Collection data:
Data collection period: Enter the number of months (value between 0 and 17) for which the REKA tool should collect data in timed operations. Setting the value to 0 will disable the data collection in timed operations, and will use by default a period of 17 month if the export is run manually. Any other value will specify the number of months checked for the REKA information.
Note: The number of months specified in the Data collection period parameter is also used as the default Collection period in the REKA Tool (Workshop Analysis) form.
Convert data:
Convert the data for REKA: Select to activate the conversation of the data for REKA ID’s 6.1, 6.2 and 6.3 to 6.1.1, 6.1.2 and 6.1.3 when collected the first time in the REKA interface.