METHOD FOR THE MAINTENANCE OR EXTENSION OF THE FUNCTIONAL RANGE OF A SELF-PROPELLED MACHINE, AND FUNCTIONAL MANAGEMENT SYSTEM OR MAINTENANCE MANAGEMENT SYSTEM

Abstract

A method for the maintenance or extension of the range of functions of a self-propelled machine, in particular a tandem roller, single-drum roller, rubber-wheeled roller, refuse compactor, road finisher, road milling machine, recycler or stabilizer, comprising the steps: generating a code which can be identified at a short distance by a control device of the machine either automatically by the control device after a maintenance interval has expired, or after a request by an operator for an extension of the range of functions, wherein the code contains information about at least one machine state that changes in the course of operation of the machine, identifying the code by a mobile terminal, transmitting the information contained in the code to a central server, transmitting a release code from the server to the mobile terminal, transmitting the release code to the control device of the machine, enabling the maintenance interval or the extension of the range of functions.

Claims

1. A method for the maintenance or extension of the range of functions of a self-propelled machine, in particular a tandem roller, single-drum roller, rubber-wheeled roller, refuse compactor, road finisher, road milling machine, recycler or stabilizer, comprising the steps of: generating a code, which can be identified at a short distance, by a control device of the machine either automatically by the control device after a maintenance interval has expired or after a request by an operator for an extension of the range of functions, wherein the code contains information about at least one machine state which changes in the course of operation of the machine; identifying the code by a mobile terminal; transmitting the information contained in the code to a central server; transmitting a release code from the server to the mobile terminal; transmitting the release code to the control device of the machine; and enabling the maintenance interval or the extension of the range of functions.

2. The method according to claim 1, wherein the code which can be identified at a short distance comprises a signal for wireless transmission of data, in particular an NFC, Bluetooth, WLAN, RFID or infrared signal.

3. The method according to claim 1, wherein the code which can be identified at a short distance is an optoelectronically readable code, and in that the optoelectronically readable code is displayed on a display device of the control device, wherein the identification of the code comprises reading of the optoelectronically readable code by a mobile terminal.

4. The method according to claim 1, wherein transmitting the release code to the control device comprises entering the release code at the control device of the machine by the operator.

5. The method according to claim 1, wherein the code contains at least one of the following pieces of information: the serial number of the machine; the location of the machine, for example as GPS coordinates; a current time at the location of the machine, especially in coordinated universal time (UTC); the operating time of the machine; the operating time of a working device of the machine, in particular a drive motor, a vibration drive, a milling drum, a screed heating system and/or a paving screed; the operating time of a wear part of the machine, in particular an air filter, an oil filter, a scraper, a belt, an ejector, a travel device and/or a wear pad; an identification of the code; the type of maintenance whose maintenance interval has expired; the desired extension of the range of functions; a current oil quality, for example of a hydraulic oil or an engine oil; the status of a counter comprised by the control device, which counts, for example, the number of machine starts; and the current machine configuration, in particular machine hardware and/or machine software.

6. The method according to claim 1, wherein at the central server and/or at the mobile terminal: a hierarchical structure with at least two service levels is stored, wherein the user of the mobile terminal is assigned a service level, and wherein the mobile terminal displays different information to the user after the code has been identified, depending on the user's service level; and/or a verification is carried out as to whether the current machine configuration, in particular machine hardware and/or machine software, permits the desired extension of the range of functions; and/or a verification of the service level of the user of the mobile terminal is carried out, and the further steps, in particular the transmission of the release code from the server to the mobile terminal, are only carried out if the service level of the user is sufficient.

7. The method according to claim 1, wherein an order for an extension of the range of functions is created at the mobile terminal and is transmitted to the central server, wherein the central server performs a transmission of a payment request to the mobile terminal.

8. The method according to claim 1, wherein a verification of a receipt of payment is performed at the central server or at the mobile terminal and the further steps, in particular the transmission of the release code from the server to the mobile terminal, are only performed if a receipt of payment has been detected.

9. The method according to claim 1, wherein the release code is created at the central server or at the mobile terminal, wherein the release code is created in such a way that it is valid only for the relevant machine and/or only for a limited period of time.

10. The method according to claim 1, wherein enabling the extension of the range of functions and/or the release code is valid for an unlimited period of time or for a limited period of time.

11. The method according to claim 1, wherein an information output is displayed to the operator on the mobile terminal in the event of a negative result of a verification, with instructions for solving the problem and/or a contact to a service partner.

12. The method according to claim 1, wherein the operator selects a desired extension of the range of functions from a list of all possible extensions of the range of functions on the control device and/or in that the control device makes suggestions to the operator during operation of the machine regarding available extensions of the range of functions of currently used functions and/or currently enabled extensions of the range of functions of the machine, which can be selected by the operator.

13. The method according to any claim 1, wherein the extension of the range of functions concerns at least one of the following functions: edge cutter right and/or left; faster or slower crab steering; grit spreader; traffic circle grit spreader; interface metrology; obstacle detection; immobilizer; radio remote control; telematics; seat adjustment; key assignment of control lever; activate free-running flow divider; activate automatic flow divider; travel lever ramp adjustment; typing operation; rotating beacon; coming/leaving home; tire pressure control system; ECO stop; compaction monitoring; display modes compaction control; mirror adjustment; rear view camera; bird view; drone camera; virtual reality; asphalt temperature sensor; machine autonomy or partial autonomy; such as automatic control; automatic following; automatic edge pressing; automatic leveling; split scraper blade; AdBlue filling pump; dust extraction; side shield camera; and activation of the milling drum during reverse travel; compressed air system.

14. The method according to claim 1, wherein a machine history is created and stored at the central server from the transmitted information contained in the code, and also the enabled maintenance intervals and/or extensions of the range of functions.

15. The method according to claim 1, wherein performing maintenance work on the machine is required before the release code is transmitted.

16. A function or maintenance management system for carrying out the method according to claim 1, comprising a self-propelled machine, in particular a tandem roller, single-drum roller, rubber-wheeled roller, refuse compactor, road finisher, road milling machine, recycler or stabilizer, with a control device and a display device, a mobile terminal and a central server.

Description

BRIEF DESCRIPTION OF THE DRAWINGS

[0047] The invention is explained in more detail below with reference to the embodiments shown in the figures. They show schematically:

[0048] FIG. 1: a tandem roller;

[0049] FIG. 2: a single-drum roller;

[0050] FIG. 3: a rubber-wheeled roller;

[0051] FIG. 4: a refuse compactor;

[0052] FIG. 5: a road finisher;

[0053] FIG. 6: a road milling machine;

[0054] FIG. 7: a functional or maintenance management system;

[0055] FIG. 8: a control device with a display device;

[0056] FIG. 9: a control device with a display device and the functional relationship with a mobile terminal and a central server;

[0057] FIG. 10: a flowchart of the method for extending the range of functions;

[0058] FIG. 11: a flowchart of the maintenance method; and

[0059] FIG. 12: a flowchart of an alternative maintenance method.

DETAILED DESCRIPTION

[0060] Components that are identical or have the same effect are identified by the same reference signs. Repeating components are not designated separately in each figure.

[0061] FIGS. 1-6 show generic machines 1. All generic machines 1 are self-propelled and comprise a machine frame 3, an operator's cab 2 and a drive engine 4, typically a diesel combustion engine or an electric motor. In working mode, they typically move in working direction a on a ground 8. For this purpose, they have different travel devices related to the respective function or field of application. FIG. 1 shows, for example, a tandem roller that has a roller drum 5 both at the front and at the rear, with which it compacts the ground 8. In the roller drums 5, a vibration exciter can also be provided, for example, by means of which the roller drum 5 can be made to vibrate in order to increase the compaction performance of the machine 1. FIG. 2 shows a single-drum roller that also comprises a roller drum 5 at the front in working direction a. The rear of the single-drum roller, on the other hand, comprises a roller drum 5. At the rear, however, the single-drum roller comprises wheels 6. The rubber-wheeled roller shown in FIG. 3 comprises rubber wheels 6 both at the front and at the rear. FIG. 4 again shows a refuse compactor. This comprises a compactor blade 54 at its front end in working direction a, with which refuse can be distributed to landfills. FIG. 5 shows a road finisher for paving asphalt layers. For this purpose, it comprises a material hopper 55 and a paving screed 7. The road finisher shown includes crawler tracks 9, but could also have wheels 6. Finally, a road milling machine is shown in FIG. 6, which also includes other ground milling machines such as recyclers and stabilizers. The road milling machine comprises a milling drum 11 rotatably mounted in a milling drum box 10 about an axis of rotation 12, which is used to mill off damaged roads, for example. The milled material removed is transferred to a transport vehicle via a conveyor 13 and transported away. These machine types are familiar to those skilled in the art, so their design and function will not be discussed in detail.

[0062] All machines 1 comprise a control device 14 with a display device 15 (see FIGS. 7-9). The control device 14 is, for example, part of the on-board computer of the machines 1. FIG. 7 shows an overview of a function or maintenance management system 51 configured to carry out the method. The system 51 comprises a machine 1, a mobile terminal 44 and a central server 45. The mobile terminal 44 is, at least temporarily, in contact with the central server 45 and can exchange data with it, for example via the Internet, a cloud 52, a satellite 53 or any other variants of, preferably wireless, remote data transmission. The mobile terminal 44 is configured, for example, as a smartphone or tablet and comprises a camera with which optoelectronically readable codes can be read from the display device 15 of the machine 1. While the mobile terminal 44 and, for example, the cloud 52, the satellite 53 and the server 45 are in constant data exchange, for example via an Internet connection, the transmission of data between the machine 1 and the mobile terminal 44 involves only a reading 24 of an optoelectronically readable code displayed on the display device 15 and an input 36 by an operator of a release code displayed on the mobile terminal 44. Any further data transmission between the machine 1 and the mobile terminal 44 is not provided, not necessary and does not take place in this embodiment example.

[0063] FIGS. 8 and 9 show a control device 14 with display device 15 and illustrate how, in one embodiment, an operator can start the process according to the invention. For example, according to FIG. 8, the operator is shown a menu heading 16 on the display device 15, for example “Available options/configurations”. In addition, the operator is shown a selection menu 17 that displays a list of all possible configurations or configuration changes, i.e., extension of the range of functions, which are available for the specific machine 1. In this list, for example, options are also available to undo an extension of the range of functions carried out in the past. Using control elements of the control unit 14 or, if the display device 15 is configured as a touch screen, directly via the display device 15 itself, the operator can now scroll through the list of available extensions of the range of functions and select one. As soon as a function range extension has been selected, the display on the display device 15 changes, for example, as shown in FIG. 9. Now the operator is shown an information output 19 under the menu heading 16, which in particular contains the designation of the selected extension of the range of functions, with various general information on the selected extension of the range of functions being compiled here. For example, information relating to the prerequisites for carrying out the extension of the range of functions which can be detected by the machine 1 may also be displayed here. For example, whether or not a necessary hardware element is already mounted on the machine 1 is displayed here, as long as this is detectable by the machine 1. Furthermore, the display device 15 shows the operator an optoelectronically readable code 18, which the operator can read (arrow 24) with the aid of the mobile terminal 44 and which contains the information already described above. Finally, the display device 15 also shows an input field 20, via which the operator can enter (arrow 36) the release code generated in the further course of the method at the control device 14. In this exemplary embodiment, there is no communication between the control device 14 and the mobile terminal 44, and in particular also the central server 45, beyond reading 24 the code 18 and entering 36 the release code. Further information transmission and processing is performed exclusively by the mobile terminal 44 and/or the central server 45. All the process steps explained in more detail below, from displaying the code 18 on the display device 15 to entering 36 the release code in the input field 20, are therefore carried out outside the control device 14 by the mobile terminal 44 and/or the central server 45, possibly with the assistance of the operator.

[0064] FIG. 10 shows a flow chart of the process 21 for extending the range of functions of the machine 1. In the flow chart according to FIG. 10 and also in the flow charts according to FIGS. 11 and 12, flow paths that are followed after a positive result of a check are indicated by a check mark. In contrast, flow paths that are initiated after a negative result of a check are indicated by a cross. The start of the process 21 is indicated by step 22. Here, for example, as described above, an extension of the range of functions is selected by the operator at the control device 14, either from a corresponding list or according to a suggestion made by the control device 14 during operation of the machine 1. Once the operator has selected a desired extension of the range of functions, an optoelectronically readable code 18 is displayed 23 on the display device 15. With the aid of the mobile terminal 44, the code 18 is then read 24, during which the information stored in the code 18 is received by the mobile terminal 44. The mobile terminal 44 then already displays to the operator information about the current operation, for example, about the further process for carrying out the extension of the range of functions. This information may be compiled differently, for example, depending on the service level of the operator of the mobile terminal 44. Importantly, even if the service level of the operator is not sufficient to perform the further steps himself, he is still offered constructive guidance on how to obtain the desired extension of the range of functions. This is ensured by displaying contact data for a service partner in the operator's vicinity. This is followed by the transmission 25 of the information stored in the code 18 from the mobile terminal 44 to the central server 45, for example via the Internet. At the central server 45, the information is processed and it is ensured, for example also on the basis of the checksum contained in the code 18, that the data transmission from the mobile terminal 44 to the server 45 has functioned sufficiently error-free. In addition, a check 26 of the code 18 is carried out to determine whether the transmitted code 18 belongs to the present method 21 at all. For this purpose, for example, the identification of the code 18 is examined to determine the purpose for which the code 18 was transmitted to the server 45. If the purpose lies in an extension of the range of functions, the method 21 proceeds as described herein. If, on the other hand, the purpose is, for example, an error message or other operation for which codes 18 generated by the control device 14 are transmitted to the server 45, then a transition 47 is made to the corresponding other subroutine of another procedure performed at the server 45, for example, for error reporting.

[0065] If checking 26 of code 18 shows that a function range extension has been requested by the operator, the next step is to check 27 to determine which specific extension of the range of functions is involved and which requirements must be met for this on machine 1. For example, it is possible to determine whether the desired extension of the functional range, or range of functions, can be achieved by modifying the software of machine 1 alone, or whether hardware modifications are also necessary. Once the requirements have been determined, a check 28 is performed to determine whether or not the machine 1 meets the software and/or hardware requirements for the desired extension of the range of functions on the basis of the information contained in the code 18. If it is determined that the machine 1 does not meet the necessary requirements, the server 45 transmits a corresponding message to the mobile terminal 44, at which an information output 48 takes place informing the operator which requirements for the desired extension of the range of functions are not currently met by the machine 1 and how he can meet these requirements. If the operator cannot fulfill these requirements himself, a contact to a service partner in his vicinity is suggested. If the check 28 shows that the machine 1 meets the prerequisites for the desired extension of the range of functions, the server 45 performs a check 29 of the necessary service level required to activate the extension of the range of functions on the machine 1 next. For example, extension of the range of functions that intervene in safety-relevant areas of the machine or whose activation may be safety-relevant on the machine 1 can only be performed by operators with a sufficient service level. These operators have then received appropriate training, for example, which enables and authorizes them to perform the necessary work. Once the necessary service level of the operator has been determined, a verification 30 is performed to determine whether the service level of the operator of the mobile terminal 44 is sufficiently high. For this purpose, the service level of the operator of the mobile terminal 44 may also be transmitted to the server 45 together with the information of the code 18. Alternatively, it is also possible for the mobile terminal 44 to transmit the identity of the operator to the server 45, for example via an individual code that complies with data protection requirements, and for the service levels of all possible operators to be stored on the central server 45. If the verification 30 reveals that the service level of the operator of the mobile terminal 44 is not sufficient to complete the extension of the range of functions on machine 1, the server 45 transmits this information to the mobile terminal 44, at which an information output 49 takes place informing the operator that his service level is not sufficient to fully enable the extension of the range of functions. Again, the operator is advised to contact a service partner with a sufficient service level.

[0066] If the service level of the operator of the mobile terminal 44 is sufficient, the next step is to check 31 whether the desired extension of the range of functions is subject to a charge or not. This is followed by a check 32 to determine whether payment has already been made or not. In the case of an extension of the range of functions that are not subject to a charge, payment is automatically and always considered to have already been made. If the server 45 detects a receipt of payment or an invoicing process, or if the feature enhancement is not subject to a charge, the next step is to specify 33 a time limit for which the feature enhancement is to be activated. The time limit can be infinite, for example, so that there is a permanent extension of the range of functions. This is the case, for example, if the operator buys the function range extension and it is then to be permanently usable on machine 1. Alternatively, the operator may only rent the desired extension of the range of functions for a certain period of time. Different time limits can also be selected at the control unit 14, for example, and are treated in the end like different function range extensions in process 21. Once the temporal limitation has been set 33, this is followed by a creation 34 of a release code by the server 45, in which, for example, both the temporal limitation and the machine 1 and any limited temporal validity of the release code are taken into account. Corresponding algorithms for generating the release code are known to the person skilled in the art and need not be explained in detail here. If the corresponding release code is available at the server 45, the release code is transmitted 35 to the mobile terminal 44, which displays the release code to the operator. The operator then enters 36 the release code at the control device 14, for example in the input field 20 on the display device 15. The control device 14 then checks the release code to ensure that the release code is actually intended for the machine 1 and, in particular, is still valid at the current time. If the control device 14 does not detect any irregularities, the next step is to enable 37 the desired extension of the range of functions, if necessary for the period of a time limit or permanently. The method 21 is then completed and ends in step 38. The function range extension is now available to the operator of the machine 1 and can be used immediately in operation.

[0067] If, when verifying or checking 32 the payment of an extension of the range of functions that is liable to cost, it is determined that a payment has not yet taken place, the corresponding transaction up to this point is counted as an order of the operator who wants to purchase the extension of the range of functions. In this case, the server 45 is used like an online store. Therefore, a creation 39 of an order for the provision of the extension of the range of functions takes place. Since the operator must pay for the chargeable feature enhancement, the next step is to transmit 40 a payment request from the server 45 to the mobile terminal 44. This is displayed to the operator accordingly, so that the operator can process the payment via online payment services, for example. Meanwhile, the server 45 waits 41 for the payment to be received. A check 42 is performed at regular intervals to determine whether the payment has been received. If the verification 42 reveals that the operator has paid for the desired feature enhancement and the payment has been received, the method 21 continues as explained above with the setting 33 of a time limit. In the event that the verification 42 indicates that no payment has been received, an additional verification 43 is performed to determine whether a timeout for the payment has occurred. If there is not yet a timeout, the wait 41 for payment is maintained. If, on the other hand, a maximum time available for making the payment has expired, a corresponding message is generated and transmitted to the mobile terminal 44. A corresponding information output 50 is then provided to the operator at the mobile terminal 44 that the payment has not been made due to a timeout, allowing the operator to correct the problem if necessary. For example, the operator may restart the process 21 and try again.

[0068] FIG. 11 shows a flow chart of the method 21 for maintenance of a self-propelled machine 1. The method 21 starts in step 22. The control device 40 checks at regular intervals whether or when a maintenance interval expires. For this purpose, a verification 57 is made whether the operating time of the machine 1 exceeds the maintenance interval minus a warning buffer. A constant, predefined time is deducted from the maintenance interval as a warning buffer. If verification 57 shows that the operating time of machine 1 does not exceed the maintenance interval minus the warning buffer, method 21 is reset. This means that method 21 starts again from the beginning. Otherwise, the next step is to check 58 whether the operating time of machine 1 exceeds the maintenance interval. Thus, during checking 58, no warning buffer is deducted any more. If checking 58 shows that the operating time of machine 1 does not exceed the maintenance interval, the operating time of machine 1 is in the warning buffer. Therefore, an information 59 is displayed to the operator, informing him that a maintenance interval is about to expire or that maintenance is necessary. The remaining duration of the warning buffer can also be displayed to the operator. If checking 58 shows that the operating time of machine 1 exceeds the maintenance interval, maintenance is due. The operator is therefore prompted 60 to initiate maintenance. For this purpose, a corresponding display is generated at the display device 15, which informs the operator of the need for maintenance. In addition, the operator is free at any time to actively initiate maintenance on his own initiative, as shown by the dashed arrow between steps 22 and 23 in FIG. 11.

[0069] In principle, the next step is to carry out the maintenance itself. This can be done by the operator or a service partner. A dialog box on the display device 15 at the control device 14 prompts 61 whether performance 46 maintenance has been successfully completed. If this is negated by the operator or the service partner, the method 21 is reset. If, on the other hand, the performance 46 of the maintenance is confirmed, the dialog box on the display device 15 next prompts 62 whether the operator or the service partner would like to reset the maintenance interval. If this is answered in the negative, the method 21 is also reset and is restarted with the maintenance interval still open. If, on the other hand, the operator or service partner confirms that the maintenance interval is to be reset, an optoelectronically readable code 18 is displayed 23 on the display device 15. The information contained in the code 18 can then be transmitted to the mobile terminal 44 by reading 24 the code 18. Information about the current operation can then be displayed to the operator by the mobile terminal 44, for example about the further progress until the service interval is acknowledged. This information may also vary depending on the service level of the operator of the mobile terminal 44. By a transmission 25 of the information stored in the code 18 from the mobile terminal 44 to the central server 45, for example via the Internet, this information is also made available to the machine manufacturers. At the central server 45, the information from the code 18 is processed and verified, for example, on the basis of the checksum. By means of a check 26 of the code 18, it is determined whether the transmitted code 18 belongs to the present method 21, i.e. the maintenance or the acknowledgement of maintenance intervals. If the code 18 does not belong to the method 21 for maintenance of the machine 1, a transition 47 is also made here to a corresponding other subroutine. If the code 18 belongs to the method 21, the next step is to check 29 the necessary service level, which is required to reset or acknowledge the maintenance interval. Once the necessary service level of the operator is determined, a checking 30 is performed to determine whether the service level of the operator of the mobile terminal 44 is sufficiently high. If the checking 30 determines that the service level of the operator of the mobile terminal 44 is not sufficient to perform the maintenance on the machine 1, the server 45 transmits this information to the mobile terminal 44, at which an information output 49 occurs informing the operator that his service level is not sufficient to reset the maintenance interval. In this case, a contact to one or more service partners with sufficient service level is indicated to the operator.

[0070] In the case where, after checking 30, it is determined that the service level of the operator of the mobile terminal 44 is sufficient to reset the maintenance interval, the next step is to create 34 the release code at the server 45, which is transmitted to the mobile terminal 44 by transmitting 35 the release code. The mobile terminal 44 displays the release code to the operator so that the operator can perform the entry 36 of the release code at the control device 14, for example in the input field 20 on the display device 15. The entry of the release code represents the last step of the maintenance work. The control device 14 checks the release code in accordance with the foregoing. If everything is in order, the release 37 of the maintenance interval takes place, which essentially corresponds to an acknowledgement of the maintenance request or a resetting of the maintenance interval. The method 21 is then completed and ends in step 38.

[0071] FIG. 12 shows a flow chart of an alternative method 21 for maintenance of a self-propelled machine 1. The method 21 starts in step 22. Here, too, as in the method 21 according to FIG. 11, the control device 14 first either prompts 60 the operator to perform maintenance due to a time lapse, or the operator initiates this on his or her own. To avoid repetition, reference is made to the above explanations for FIG. 11 for this part of the method 21 according to FIG. 12.

[0072] If the operator selects maintenance, either on his or her own initiative or after being prompted 60, an optoelectronically readable code 18 is displayed 23 on the display device 15. Reading 24 of the code 18 by the mobile terminal 44 can then take place, as already described above. In this case, the information stored in the code 18 is read by the mobile terminal 44. The mobile terminal 44 then displays to the operator information about the current operation, for example, about the further process for performing the service. Again, this information may vary depending on the service level of the operator of the mobile terminal 44. For example, the operator is told how to perform the maintenance or who to contact to have the maintenance performed. This is followed by transmitting 25 the information stored in the code 18 from the mobile terminal 44 to the central server 45, for example via the Internet. At the central server 45, the information from the code 18 is processed and verified, for example, using the checksum. Also, a check 26 of the code 18 is performed to determine whether the transmitted code 18 belongs to the present method 21 at all. If the code 18 does not belong to the method 21 for servicing the machine 1, a transition 47 is made to a corresponding other subroutine. If the code 18 belongs to the method 21, the next step is to check 29 the necessary service level, which is required to perform the maintenance on the machine 1 and/or to reset the maintenance interval. Again, this is based on safety aspects to ensure that only sufficiently trained operators perform the respective maintenance on the machine 1. Once the necessary service level of the operator has been determined, a checking 30 is performed to determine whether the service level of the operator of the mobile terminal 44 is sufficiently high. If the checking 30 determines that the service level of the operator of the mobile terminal 44 is not sufficient to perform the maintenance on the machine 1, the server 45 transmits this information to the mobile terminal 44, at which an information output 49 takes place informing the operator that his service level is not sufficient to perform the maintenance and/or to reset the maintenance interval. Again, a contact to a service partner with sufficient service level is indicated to him In the event that, after checking 30, it is determined that the service level of the mobile terminal 44 operator is sufficient to perform the maintenance, the next step is to perform 46 the maintenance itself. This is done, for example, by the operator of the mobile terminal 44, or by a service partner who, however, also has a mobile terminal 44, for example, and who performs the method 21 as part of his service activities. A user with a sufficiently high service level is also shown further, helpful information here, for example instructions for carrying out 46 the maintenance and/or a digital service booklet with a complete machine history, in particular comprising all previous maintenance and/or extension of the range of functions. The warranty status of the machine can also be included in this information.

[0073] The further course of the method 21 depends on whether it is possible to detect the completion of the maintenance work by the machine 1, for example by the control device 14. This can succeed, for example, by wear parts being equipped with identification devices, for example RFID chips, and these being read out, or by other sensors being available which detect successful completion of the maintenance. Whether or not the completion of maintenance can be objectively detected in this way may vary from maintenance to maintenance. If such detection is not possible, the operator or service partner performing the maintenance is simply trusted with a sufficient service level. The name of the operator or service partner then stands for the performance and quality of the maintenance. For example, he can confirm that the maintenance has been performed by making an entry on the mobile terminal 44. This is transmitted to the server 45, which then performs the creation 34 of the release code, whereupon a transmission 35 of the release code to the mobile terminal 44 takes place. The mobile terminal 44 displays the release code to the operator so that the operator can perform the entry 36 of the release code at the control device 14, for example in the input field 20 on the display device 15. The entry of the release code represents the last step of the maintenance work. The control device 14 checks the release code in accordance with the foregoing. If everything is in order, the release 37 of the maintenance interval takes place, which essentially corresponds to an acknowledgement of the maintenance request. The method 21 is then completed and ends at step 38.

[0074] If, on the other hand, it is possible for the machine 1 to objectively detect, for example via the control device 14 and/or sensors connected to it, that the maintenance work has been carried out, then an additional safety level can be retracted. It is then possible, for example, for a new optoelectronically readable code 18 to be generated by the control device 14 after the maintenance work has been carried out 46, which code contains the detected results of the maintenance. This new code 18 is then made available via a display 23 on the display devices 15, whereupon a new reading 24 of the code 18 by the mobile terminal 44 takes place. The information stored in the new code 18 is then transmitted to the server 45 by a retransmission 25. Based on the transmitted information, a check 26 is then performed at the server 45 to determine whether the maintenance work has been completely and successfully performed. If this is the case, the method 21 continues with the creation 34 of the release code as already described above. If, on the other hand, it is determined that the maintenance has either not been performed completely or not successfully, a corresponding message is generated by the server 45 and transmitted to the mobile terminal 44. An information output 56 is then generated at the mobile terminal 44, informing the operator of the failed maintenance and also indicating to the operator exactly where the problem lies and how to correct it. Alternatively, the operator can again be shown, if necessary, who he can contact to have the problem rectified.

[0075] All in all, the method 21 makes it easier, more economical and faster to expand the range of functions or to perform maintenance on a machine 1. This increases the flexibility of the machine 1, since the operator can use all possible machine configurations quickly and easily. At the same time, safe and reliable operation of the machine 1 is ensured by safety mechanisms provided in the process 21.

[0076] Finally, the method for mounting a hardware component according to the invention will be illustrated in more detail using an example. For this purpose, reference is made only to FIG. 1 as an example. The hardware component to be attached is a grit spreader 63. This is indicated in dashed lines in FIG. 1 to illustrate that the grit spreader 63 is not initially present. The operator can now call up the additional option “grit spreader” from the operating menu of the machine 1. The control device 14 can now check whether, if applicable, a grit spreader is already present on the machine 1 or whether the requested hardware component is already available. For this purpose, for example, a suitable sensor, in FIG. 1 sensor 64, can be provided which checks, for example mechanically and/or electronically, whether the hardware component is already available at the attachment point for the hardware component. For this purpose, the sensor 64 is in communication with the control device 14 via the signal transmission line 65, and the control device 14 is in communication with the display device 15 via the signal transmission line 66. These can be wired or wireless. The method according to FIG. 10, for example, can now be carried out. If the grit spreader 63 is already attached, the corresponding machine-side control of the grit spreader can now be enabled in the machine operating software via the method shown in FIG. 10, for example. If, on the other hand, the grit spreader 63 is not detected and/or the machine 1 does not permit such a configuration, this can be indicated to the operator after appropriate testing. However, as a supplement or alternative, the sensor 64 can also be, for example, an oil quality sensor or comprise an oil quality sensor which senses the current quality of an oil of the machine 1, for example a hydraulic oil or an engine oil, and transmits the result to the control device 14. This information may also then be transmitted to the central server 45 via the code 18, as explained above.