Method and apparatus, and device management system for operating a plurality of technical devices, in particular a plurality of drive units of a fleet or a farm having the device management system

Abstract

The invention relates to a method for operating (100) a plurality of technical devices (220', 220'', 220'''), in particular a plurality of drive units of a fleet or a farm (210) having a device management system, wherein the method comprises the following steps: - monitoring (110) the technical devices (220', 220'', 220'''), in particular the drive units of the fleet or the farm (210), and acquiring (112) operating information (242) relating to a technical device (220', 220'', 220'''); - creating (114) a maintenance plan (244) with future maintenance dates (246) for the technical device (220', 220'', 220''') using the acquired operating information (242), - specifying (116) preliminary future times for the future maintenance dates (260). According to the invention, in the method - the operating information (242) comprises usage data (254) and / or environmental data (252) and / or service data (256) for the technical device (220', 220'', 220'''), and - a change in the operating information (242) relating to the technical device (220', 220'', 220''') is determined, - the provisional future time (260) is dynamically adapted (122) to a changed future time (262) of the future maintenance date (246) on the basis of the change in the operating information (242) relating to the technical device (220', 220'', 220''').

Description

[0001] DESCRIPTION

[0002] Method and equipment or device management system for operating a large number of technical devices, in particular a large number of drive units of a fleet or a farm with the device management system

[0003] The invention relates to a method for operating a plurality of technical devices, in particular a plurality of drive units of a fleet or a farm, with a device management system according to the preamble of claim 1. The invention also relates to a device for operating a plurality of technical devices, in particular a plurality of drive units of a fleet or a farm, with a device management system.

[0004] Methods for operating technical equipment, in particular for planning its maintenance, are already known. Typically, maintenance dates for individual pieces of technical equipment in a farm or fleet are extrapolated based on the average utilization of the fleet or farm.

[0005] However, the more diverse the use of technical equipment within a fleet, the greater the effort required to plan for upcoming maintenance, both in the short and long term.

[0006] German patent DE 10 2017 004 554 Al discloses a maintenance logistics system in which maintenance is initiated for wear parts of refuse collection vehicles when a wear limit is reached. Operating data is used for this purpose.

[0007] It would be desirable to be able to predict maintenance intervals for technical equipment in an improved way in the future.

[0008] This is where the invention comes in, the object of which is to provide a method and a device by means of which maintenance intervals for technical equipment can be predicted in an improved manner, even with varying usage of the technical equipment. This object is achieved in a first aspect by a method according to claim 1.

[0009] The invention relates to a method for operating a plurality of technical devices, in particular a plurality of drive units of a fleet or a farm with a device management system, comprising:

[0010] - Monitoring the technical equipment, in particular the drive units of the fleet or the farm, and recording operating information of a technical device;

[0011] - Creating a maintenance plan with future maintenance dates for the technical equipment using the recorded operating information.

[0012] - Indication of preliminary future dates for future maintenance appointments.

[0013] According to the invention, the operating information includes usage data and / or environmental data and / or service data for the technical device, and

[0014] - a change in the operating information of the technical device is detected,

[0015] - the provisional future date is dynamically adjusted to a changed future date of the future maintenance appointment based on changes to the operating information of the technical equipment.

[0016] The invention provides for the creation of a maintenance plan with future maintenance dates for a technical device based on operational information, including usage data, environmental data, and / or service data. Changes in the operational information of the technical device dynamically lead to an adjustment of the provisional future maintenance date based on the change in the operational information. In other words, the prediction of maintenance dates for a number of technical devices is intended to be device-specific, in particular based on environmental factors, usage patterns, and / or service data.

[0017] For this purpose, the technical equipment is operated and its operating information is recorded. Operating information includes usage data, environmental data, and / or service data. A maintenance plan with future maintenance dates for the technical equipment is created using the existing operating information from the equipment, particularly the drive units of a large fleet or farm, combined with the recorded operating information. Maintenance appointments can be scheduled or unscheduled. Preliminary future maintenance dates for the technical equipment are indicated, and any changes to the future maintenance date are displayed. A future maintenance date can be announced, for example, via an automated signal. This allows users of the technical equipment to be informed about the next maintenance appointment.Changes in operating information, for example due to wear and tear, should therefore lead to a dynamic adjustment of maintenance dates without having to document the changes in operating information.

[0018] The invention thus recognizes that the wear and tear of technical devices depends on the use, the environment and the service of the technical device.

[0019] The invention offers the advantage of improved prediction of future maintenance intervals for technical equipment. Firstly, maintenance intervals can be predicted more flexibly, meaning the invention's concept allows for a rapid response to the specific situation of a technical device. Secondly, the concept improves the database, as the operational information includes usage data, environmental data, and / or service data for the technical device. This significantly improves the reliability of predicting the future date of a maintenance appointment.

[0020] The invention also has the advantage of enabling highly accurate predictions of the fleet's resource requirements for upcoming tasks. Preventive maintenance can be planned efficiently and maintenance intervals adjusted. This ensures the reliability and availability of the technical equipment.

[0021] According to a second aspect of the invention, the aforementioned problem is solved by a device according to claim 10 for operating a number of monitored technical devices, in particular drive units in a fleet or a farm, with a unit for monitoring the technical devices. The device is particularly configured for operating the plurality of technical devices according to the method according to the invention.

[0022] The facility features:

[0023] - a monitoring module designed to monitor the technical equipment, in particular the drive units of the fleet or farm, and to record operating information of a technical device; - a creation module designed to create a maintenance plan with future maintenance dates for the technical equipment using the recorded operating information in an operating information unit, in particular a data logger or a database,

[0024] - a specification module for specifying preliminary future dates for future maintenance appointments, in particular an output interface designed to output the maintenance date of the technical equipment.

[0025] According to the invention, it is provided that

[0026] - the operational information includes usage data and / or environmental data and / or service data for the technical device, and

[0027] - a change in the operating information of the technical device can be detected in the monitoring module, whereby

[0028] - the provisional future date can be dynamically adjusted to a changed future date of the future maintenance appointment based on changes to the operating information of the technical equipment.

[0029] It is evident that the concept of the invention advantageously enables the evaluation of data from operational information, in particular usage data and / or environmental data and / or service data. This advantageously facilitates predictive information, especially planning, regarding required spare parts for maintenance work. This predictive information and any associated planning can be preventive or reactive in relation to the current state. This or similar measures can have a particularly positive impact on warehousing and delivery logistics. Likewise, predictive information, especially planning, generally and / or specifically regarding required spare parts for maintenance work, also enables predictive information, especially planning, regarding required service capacities. Service capacity can also include infrastructure linked to service personnel.

[0030] Advantageous embodiments of the invention are described in the dependent claims and provide detailed information on advantageous ways to implement the concept explained above within the scope of the problem statement and with regard to further advantages. The dynamic adjustment of the changed future point in time comprises a shift in time, whereby the changed future point in time is shifted earlier or later.

[0031] In a training course, a change in operational information can be identified by examining the operating mode of the technical device based on a significant operational change detectable in the usage data. A detectable significant operational change exists, for example, when usage data and / or environmental data and / or service data differ significantly from previous usage data and / or environmental data and / or service data.

[0032] Either a usage profile can be created from the usage data, in particular operating times, downtimes, and / or load, whereby the significant operational change can be identified with the help of the usage profile; or an environmental profile can be created from the environmental data, in particular ambient temperature and / or environmental topography, whereby a further significant operational change can be identified with the help of the environmental profile. A service profile can also be created from the service data, whereby yet another significant operational change can be identified with the help of the service profile.

[0033] The significant operational change can also be identified by the usage profile, the environmental profile and / or the service profile.

[0034] The usage profile can change, for example, if a regularly used piece of technical equipment with a service interval of 5000 km, which normally has a weekly operating distance of 500 km (meaning a maintenance interval of 10 weeks), is used less frequently, for example 200 km per week, or is not used at all for periods of time. In such a case, reaching the 5000 km mark and thus the revised future maintenance date is automatically postponed.

[0035] The operating profile can change, for example, if a vehicle is regularly used on level roads and now operates on roads with varying gradients. Engine wear is now greater. This leads to an earlier future maintenance date. The operating profile can also change if, for example, an engine previously operated in cold environments is now operated in hot environments. The engine is subjected to significantly higher loads in hot environments. This also leads to an earlier future maintenance date.

[0036] In various training courses, an environmental profile and / or usage profile and / or service profile can be used individually or in relation to each other to adjust the future maintenance date.

[0037] Further training enables each technical device to be equipped with a data logger for recording usage and / or environmental data for creating a maintenance plan. This allows for monitoring of the technical devices and, consequently, a direct response to changes in usage and / or environmental data. Maintenance schedules can thus be adjusted instantly based on changes in usage and / or environmental data.

[0038] In another training course, each technical device can have a database for storing service data to create a maintenance plan, especially maintenance intervals. The database can, for example, contain information on when a technical device needs servicing, based on operating time, distance traveled, and / or mileage.

[0039] A technical device may also include a data logger and a database.

[0040] Advantageously, the upcoming maintenance date for the technical device can be communicated to at least one end device. End devices can include computers, laptops, tablets, smartphones, or vehicle dashboards.

[0041] The system's creation module is trained to generate a maintenance plan with future maintenance dates for a piece of technical equipment from existing operational information stored in an operational information unit, specifically a data logger or database. This operational information for the technical equipment, particularly drive units in a fleet or farm, includes a data input module and an output interface. The data input module is trained to provisionally indicate future maintenance dates for the technical equipment. Directly outputting the maintenance date allows for immediate responses to existing operational information.

[0042] The output interface is configured to output the revised future maintenance date of the technical device. The output interface can be a port, a WLAN interface, or a Bluetooth interface. Generally, a near-field communication (NFC) interface is preferred.

[0043] An NFC interface is generally based on RFID technology, an international transmission standard for contactless data exchange. This exchange typically occurs via electromagnetic induction, particularly using loosely coupled coils, over short distances of a few centimeters and at a limited data transfer rate, for example, a maximum of 424 kbit / s. Depending on the specific design and standard, the upper limit for distance or bandwidth and data transfer rate of an NFC interface can differ significantly from this, and often be much higher.

[0044] The operating information includes, in particular, usage data and / or environmental data and / or service data, and changes to the operating information of the technical device dynamically lead to an adjustment of the maintenance date of the technical device based on the change in the operating information of the technical device.

[0045] Preferably, the device further comprises a change detector designed to detect a change in the operating mode of the technical equipment based on a detectable significant change in operation. Upon detection of such a change in operation, the future maintenance date is adjusted to the changed operating mode.

[0046] The system can include a terminal device configured to receive the upcoming maintenance date and the corresponding time for the technical equipment. These terminal devices can be connected to the unit's output interface for monitoring the technical equipment via cable, cellular network, or Wi-Fi. The technical equipment can also include a data logger configured to collect usage and / or environmental data for creating the maintenance plan and to transmit this data to the creation module.

[0047] The technical device can, in addition or as an alternative, include a database designed to store service data for creating the maintenance plan, particularly maintenance intervals, and to transmit this data to the creation module. The creation module can then use usage and / or environmental data to determine a revised future maintenance appointment and output this date to the end device via the output interface.

[0048] In one modification, the invention advantageously leads to a particularly preferred further development within the framework of an equipment management system for operating a large number of technical devices, preferably a large number of drive units of a fleet or a farm, with the equipment management system. Such an equipment management system is advantageously designed

[0049] - as part of a facility according to the concept of the invention and indicates:

[0050] - the monitoring module, the creation module and the specification module, and wherein

[0051] - the device management system, which is so integrally designed, is formed separately from the technical device.

[0052] In particular, the integrated device management system optionally features:

[0053] - a data logger that is designed to collect usage data and / or environmental data for the creation of the maintenance plan and to transmit the usage data and / or environmental data to the creation module, and / or

[0054] - a database that is designed to store service data for creating the maintenance plan, in particular maintenance intervals, and to pass the service data to the creation module.

[0055] Such a device management system has proven particularly advantageous for owners or lessors of vehicles in a fleet or farm equipment; for example, lessors of cars and / or trucks from one or more fleets. Embodiments of the invention are now described below with reference to the drawings and comparison with the prior art, some of which is also shown. These drawings are not necessarily to scale; rather, where explanatory, they are presented in a schematic and / or slightly distorted form. For further information on the teachings directly apparent from the drawings, reference is made to the relevant prior art. It should be noted that numerous modifications and changes concerning the form and details of an embodiment can be made without deviating from the general idea of ​​the invention.The features of the invention disclosed in the description, the drawing, and the claims can be essential for the further development of the invention, both individually and in any combination. Furthermore, all combinations of at least two of the features disclosed in the description, the drawing, and / or the claims fall within the scope of the invention. The general idea of ​​the invention is not limited to the exact form or detail of the preferred embodiment shown and described below, nor is it limited to an object that would be restricted compared to the object claimed in the claims. Where specified dimensioning ranges are given, values ​​lying within the stated limits are also disclosed as limit values ​​and can be used and claimed as desired.Further advantages, features and details of the invention will become apparent from the following description of the preferred embodiments and from the drawing; this is shown in:.

[0056] FIG. 1A shows a preferred embodiment of a device for operating a number of monitored technical devices with a monitoring unit;

[0057] FIG. 1B shows a modification of the preferred embodiment of a device for operating a number of monitored technical devices with a monitoring unit, wherein an integrally designed device management system is designed separately from and for operating the plurality of technical devices;

[0058] FIG. 2 shows a preferred embodiment of a method for operating a number of technical devices with a device management system. FIG. 1A shows a preferred embodiment of a device 200 for operating a number of monitored technical devices, here in the form of rail vehicles 220', 220", 220" ' in a fleet 210, in particular their drive units.

[0059] In other embodiments, the technical equipment can be ships, heavy land vehicles, or industrial machinery. This list is not exhaustive; the multitude can also include other technical equipment and is not limited to the same type of technical equipment. In particular, the multitude can comprise different technical equipment within an exemplary fleet or farm. Therefore, the explanation of the following exemplary embodiments should be understood as merely illustrative or representative of other possible configurations of technical equipment.

[0060] The rail vehicles 220', 220", 220'" shown here, which are exemplary and symbolic representations of other vehicles, e.g., of a fleet, or installations, e.g., of a farm, each have a monitoring module 288', 288", 288'" with an operating information unit 230', 230", 230'". The operating information unit 230', 230", 230'" includes a data logger 234', 234", 234'" and a database 236', 236", 236'". The data loggers 234', 234", 234"' record usage data 254 and environmental data 252 of the rail vehicles 220', 220", 220'". The usage data 254 records operating times 276, operating breaks 278, and load 280. Operating times 276 and operating breaks 278 are determined via the use of the rail vehicle 220', 220", 220" over time t. The load 280 is measured via the load torque M over the rotational speed n. The environmental data 252 records ambient temperature 282 and environmental topography 284. Service data 256 is stored in the database 236', 236", 236'".The service data 256 stores the maintenance intervals 266. The data loggers 234 and the databases 236 each forward the usage data 254, environmental data 252, and the service data 256 to a creation module 240.

[0061] In other embodiments, the technical devices may include either a data logger or a database.

[0062] The creation module 240 comprises a change detector 264, a specification module 259, and an output interface 258. The creation module 240 generates a maintenance plan 244 with future maintenance dates 246 for the rail vehicles 220', 220", 220'" from existing operational information 242. The existing operational information 242 is the usage data.

[0063] 254 and environmental data 252 and service data 256.

[0064] In other embodiments, the operating information can also be usage data, environmental data, or service data.

[0065] The change detector 264 detects a change in the operating mode of the rail vehicle 220', 220", 220'" due to a detectable significant operational change 268. A detectable significant operational change 268 exists when usage data 254, environmental data 252, or service data 256 change significantly from previous usage data 254, environmental data 252, or service data 256. The significant operational change 268 is detectable when, for the engine of a rail vehicle 220', 220", 220" ', for which the maintenance intervals were initially established based on regular use of the rail vehicle 220', 220", 220" ', regular use ceases.

[0066] The significant operational change 268 is also identifiable through a usage profile 272, environmental profile 274, or service profile 286. If the usage profile 272, environmental profile 274, or service profile 286 exhibits a jump or a change in the decrease or increase, a significant operational change 268 or another significant operational change exists. Alternatively, the significant operational change 268 may only be identifiable through the environmental profile 274.

[0067] The change detector 264 transmits the change in the operating mode of the rail vehicle 220', 220“, 220“ ' to the information module 259.

[0068] By evaluating the data from the operational information 242, in particular the usage data 254, environmental data 252, and service data 256, it becomes advantageously possible to generate predictive information, especially planning, regarding the spare parts required for maintenance work. This predictive information and any associated planning can be preventive or reactive in relation to the current state. This or similar measures can have a particularly positive impact on warehousing and delivery logistics. Likewise, predictive information, especially planning, regarding the spare parts required for maintenance work also allows for predictive information, especially planning, regarding required service capacities. Service capacity can, in principle, encompass the skills of service personnel or be categorized accordingly.

[0069] This type of measure has an overall positive impact on short- and medium-term personnel planning. For example, it allows for a more precise planning of required working hours and / or the number of people, in the sense of "manpower." An example could be a calculated working time requirement of 20 hours, or a service staff requirement of 3 people, or 3 people each for a working time requirement of 10 hours or 5 hours.

[0070] As an illustrative example of planning required service capacities, it should be mentioned that planning for service personnel, for example, requires high-voltage training as a condition.

[0071] Service capacity can also include infrastructure linked to service personnel. As an illustrative example of planning for infrastructure linked to or required by service personnel, consider the requirement of an assembly crane with a predetermined or upper / lower lifting capacity.

[0072] In this case, the data module 259, using the change in the operating mode of the rail vehicle 220', 220", 220'", specifies provisional future dates 260 for maintenance appointments 246 of the rail vehicle 220', 220", 220" '. The provisional future dates 260 for maintenance appointments 246 of the technical equipment 220', 220", 220'" are postponed due to the change in the operating mode of the rail vehicle 220', 220", 220'". If the rail vehicle 220', 220", 220" ' is not used regularly, the maintenance appointment 260 is specified later by the data module 259. The specification module 259 is output interface 258, which outputs the maintenance appointment 246 of the rail vehicle 220', 220", 220" '. Based on the changed future time 262 of the maintenance appointment 246 of the rail vehicle 220', 220", 220" ', a time shift 270 of the provisional future times 260 of the maintenance appointments 246 is initiated.Thus, the changes in the operating mode dynamically lead to an adjustment of the maintenance date 246 of the rail vehicle 220', 220", 220'". Overall, this has the advantage that the planning of an exemplary fleet deployment can be optimized, since, in particular, the timing of the maintenance activities becomes known in advance. In this way, a fleet can be deployed more efficiently; for example, vehicles in a fleet can be deployed in a more "distributed" or "concentrated" manner according to the concept of the invention.

[0073] FIG. 1B shows, in principle, — representing a particular embodiment — an integral device management system 201 for operating a plurality of technical devices 220', 220“, 220'“, preferably a plurality of drive units of a fleet or a farm 210 with the device management system 201. This is with reference to the preceding description, wherein the same reference numerals are used for identical or similar features or features of the same or similar function.

[0074] The integrated device management system 201 is presented here according to the embodiment of the

[0075] FIG. 1B basic

[0076] - designed as part of the facility according to one of the previously described embodiments, and

[0077] - provided separately from the multitude of technical equipment 220', 220", 220'".

[0078] That is, the integrated device management system 201 is implemented as shown in FIG. 1B.

[0079] The device management system 201 according to the embodiment of FIG. 1B has:

[0080] - the monitoring module 288', 288“, 288'“, the creation module 240 and the specification module 259.

[0081] As shown in FIG. 1B, such an integrally formed device management system 201 is implemented with functionality and features analogous to those previously described with reference to FIG. 1A. The device management system 201, as can be seen in FIG. 1B, is provided separately from the technical device 220', 220", 220'" - i.e., it is designed as a spatially separated unit.

[0082] A corresponding bidirectional communication of the operating information 242 between the device management system 201 and the fleet or farm 210 with the device management system 201 is possible via interfaces 231, 232 shown here symbolically, in particular in the form of an air interface. The device management system 201 of FIG. 1B also features:

[0083] - a data logger 234, which is designed to record usage data 254 and / or environmental data 252 for the creation of the maintenance plan 244 and to transmit the usage data 254 and / or environmental data 252 to the creation module 240, and / or

[0084] - a database 236 which is trained to store service data 256 for the creation of the maintenance plan 244, in particular maintenance intervals 266, and to pass the service data 256 to the creation module 240.

[0085] Such a vehicle management system 201 of FIG. 1B has proven particularly advantageous for an owner or lessor of vehicles in a fleet 210; for example, a lessor of cars and / or trucks from one or more fleets. The above concept offers an advantage, for example, to a fleet lessor if it becomes known that—according to a fictitious and non-restrictive example—a vehicle is due for maintenance within the next 1,000 km. Based on this information, the concept could be used to plan that the vehicle may be used five more times for short trips of 200 km each, but should not be used for an upcoming trip of, for example, 1,500 km.

[0086] FIG. 2 shows a preferred embodiment of a method 100 for operating a number of technical devices in the form of rail vehicles 220', 220", 220'", in particular a large fleet or farm 210, with a device management system 201 in the form of a device 200 or as part of a device 201 for operating a number of monitored technical devices 220', 220", 220'" as described in FIG. 1A and FIG. 1B respectively.

[0087] In other embodiments, the technical equipment can be ships, heavy land vehicles or industrial machinery; this includes ships, commercial vehicles or, as previously explained — not limited to reference to FIG. 1B — passenger cars.

[0088] The first step of procedure 100 concerns the monitoring 110 of the rail vehicles 220', 220“, 220'”.

[0089] The second step of procedure 100 involves the acquisition 112 of operational information 242 of a rail vehicle 220', 220", 220" '. The operational information 242 consists of usage data 254, environmental data 252, and service data 256. In a third step 114, a maintenance plan 244 with future maintenance dates 246 for the rail vehicle 220', 220", 220" ' is created from existing operational information 242 of the rail vehicles 220', 220", 220" ' with the operational information 242.

[0090] In a fourth step 116, preliminary future dates 260 for maintenance dates 246 for the rail vehicle 220', 220“, 220“ ' are specified.

[0091] To give just one example, let us assume that operational information 242 is recorded for a technical device such as the rail vehicles 220', 220", 220'" mentioned here. Determined according to the first, second, third and fourth steps of procedure 100, a service interval is set for a predetermined running distance, such as a running distance of 5000km.

[0092] With a weekly variable travel distance of 220', 220", 220'" for the rail vehicles, on average a fraction 1 / n (e.g. 500km) of a total travel distance, a preliminary maintenance appointment is planned after n weeks (in one example every ten weeks (i.e. n=10)).

[0093] If the operating mode of the technical device changes—for example, due to a three-week downtime of one of the rail vehicles 220', 220", 220"—then the amended future maintenance date for one of the rail vehicles 220', 220", 220'" is postponed. An amended future date 262 for the maintenance dates 246 is then output to an end device, e.g., a smartphone 240. In another embodiment, the end device can also be a computer, a laptop, a tablet, or a vehicle control panel.

[0094] If, in a sixth step 120, a change is detected in the usage data 254 and / or environmental data 252 and / or service data 256 of the rail vehicle 220', 220", 220'", then, in a seventh step 122, the provisional future date 260 of the future maintenance date 246 is adjusted to a changed future date 262 of the rail vehicle 220', 220", 220'". The usage data 254 and / or environmental data 252 and / or service data 256 of the rail vehicle 220', 220", 220" can change—as already described with reference to FIG. 1A—due to a change in the operating mode. If no change in the usage data 254 and / or environmental data 252 and / or service data 256 of the rail vehicle 220', 220“, 220“ ' is detected in the sixth step 120, the procedure starts again with the first step 110.

[0095] Overall, using procedure 100, the future maintenance dates 246 of a technical device 220', 220", 220" ' are determined dynamically based on the change in the operating information 242 of the technical device 220', 220", 220" '.

[0096] REFERENCE MARK LIST

[0097] 100 methods for operating technical equipment

[0098] 110 Operating the technical equipment

[0099] 112 Recording operational information

[0100] 114 Creating a maintenance plan

[0101] 116 Specifying times for maintenance appointments

[0102] 120 Changes to the operating information

[0103] 122 Adjusting the future maintenance date

[0104] 200 Equipment for operating a number of monitored technical devices

[0105] 201 Device management system for operating a number of monitored technical devices

[0106] 210 fleet of technical equipment

[0107] 220 ' , 220 “ , 220 “ ' techni see devices

[0108] 230', 230“, 230 Operating Information Unit

[0109] 231, 232 interfaces

[0110] 234', 234“, 234 data logger

[0111] 236', 236“, 236 database

[0112] 240 Creation module

[0113] 242 Operational Information

[0114] 244 Maintenance plan

[0115] 246 future maintenance appointments

[0116] 248 Maintenance signal

[0117] 250 terminal devices

[0118] 252 Environmental data

[0119] 254 usage data

[0120] 256 Service data

[0121] 258 Output interface

[0122] 259 Specification module

[0123] 260 preliminary future date

[0124] 262 amended future date

[0125] 264 Change Detector

[0126] 266 Maintenance interval

[0127] 268 significant operational change 270 time point shift

[0128] 272 Usage profile

[0129] 274 Environmental profile

[0130] 276 Operating hours 278 Operating breaks

[0131] 280 Last

[0132] 282 Ambient temperature

[0133] 284 Environmental topography

[0134] 286 Service profile 288', 288“, 288'“ Monitoring module t Time

[0135] M load torque n speed

Claims

REQUIREMENTS 1. Method for operating (100) a plurality of technical devices (220', 220“, 220'“), in particular a plurality of drive units of a fleet or a farm (210) with a device management system, wherein the method comprises the steps: - Monitoring (110) the technical equipment (220', 220“, 220'“), in particular the drive units of the fleet or the farm (210), and recording (112) operational information (242) of a technical device (220', 220“, 220“ '); - Creating (114) a maintenance plan (244) with future maintenance dates (246) for the technical equipment (220', 220", 220" ') with the recorded operating information (242), - Indication (116) of preliminary future dates for the future maintenance dates (260), characterized in that - the operating information (242), usage data (254) and / or environmental data (252) and / or service data (256) for the technical equipment (220', 220", 220" ') include, and - a change in the operating information (242) of the technical device (220', 220", 220'") is detected, - the provisional future date (260) to a changed future date (262) of the future maintenance date (246) is dynamically adjusted (122) based on the change in the operating information (242) of the technical equipment (220', 220", 220'").

2. Method according to claim 1, characterized in that the dynamic adjustment (122) of the changed future time (262) comprises a time shift (270), wherein the changed future time (262) is shifted earlier or later in time.

3. Method according to claim 1 or 2, characterized in that a change in the operating information (242) is detected by means of an operating mode of the technical device (220', 220“, 220“ ') on the basis of a significant change in operation (268) detectable in the usage data (254).

4. Method according to one of the preceding claims, characterized in that a usage profile (272) is created from the usage data (254), in particular operating times (276), operating breaks (278) and / or load (280), wherein the significant operational change (268) can be identified with the help of the usage profile (272).

5. Method according to one of the preceding claims, characterized in that an environmental profile (274) is created from the environmental data (252), in particular ambient temperature (282) and / or environmental topography (284), wherein a further significant change in operation can be identified with the help of the environmental profile (274).

6. Method according to one of the preceding claims, characterized in that a service profile (286) is created from the service data (256), wherein a further significant operational change can be identified with the help of the service profile (286).

7. Method according to one of the preceding claims, characterized in that each technical device (220', 220“, 220“ ') comprises a data logger (286) for recording usage data (254) and / or environmental data (252) for creating the maintenance plan (244).

8. Method according to one of the preceding claims, characterized in that each technical device (220', 220“, 220'“) has a database (288) for storing service data (256) for creating the maintenance plan (244), in particular maintenance intervals (266).

9. Method according to one of the preceding claims, characterized in that for a technical device (220', 220“, 220'“) the future maintenance date (246) is output to at least one terminal device (250) at the future time.

10. Device (200) for operating a plurality of technical devices (220', 220", 220'"), in particular with a device management system (201) for operating the plurality, preferably a plurality of drive units of a fleet or a farm (210) with the device management system, in particular device (200) configured for operating the plurality of technical devices (220', 220", 220'") according to a method according to any one of claims 1 to 9, wherein the device comprises: - a monitoring module (288', 288“, 288'“), designed to monitor (110) the technical equipment (220', 220“, 220“ '), in particular the drive units of the fleet or the farm (210), and to acquire (112) operational information (242) of a technical device (220', 220“, 220'“), - a creation module (240) trained to create (114) a maintenance plan (244) with future maintenance dates (246) for the technical equipment (220 ', 220“, 220“ ') with the recorded operational information (242) in an operational information unit (230', 230", 230" '), in particular a data logger (234) or a database (236), - a specification module (259) for specifying (116) preliminary future dates (260) for the future maintenance dates (246), in particular an output interface (258) configured to output the maintenance date (246) of the technical device (220', 220", 220'"), characterized in that - the operating information (242), usage data (254) and / or environmental data (252) and / or service data (256) for the technical equipment (220', 220", 220'") include, and - in the monitoring module (288', 288", 288'") a change in the operating information (242) of the technical device (220', 220", 220'") can be detected, wherein - the provisional future date (260) is dynamically adjustable to a changed future date (262) of the future maintenance date (246) based on the change in the operating information (242) of the technical equipment (220', 220“, 220“ ').

11. Device according to claim 10, further comprising a change detector (264) configured to detect a change in an operating mode of the technical device (220', 220", 220" ') due to a detectable significant change in operation (268).

12. Device according to claim 10 or 11, further comprising a terminal device (250) configured to receive the future maintenance date (246) with the future time of the technical device (220', 220", 220" ').

13. Device according to one of claims 10 to 12, characterized in that the technical device (220', 220", 220" ') comprises a data logger (234) which is configured to record usage data (254) and / or environmental data (252) for the creation of the maintenance plan (244) and to transmit the usage data (254) and / or environmental data (252) to the creation module (240).

14. Device according to one of claims 10 to 13, characterized in that the technical device (220', 220“, 220'“) comprises a database (236) which is configured to store service data (256) for the creation of the maintenance plan (244), in particular maintenance intervals (266), and to pass the service data (256) to the creation module (240).

15. Equipment management system (201) for operating a plurality of technical devices (220', 220", 220'"), preferably a plurality of drive units of a fleet or a farm (210) with the equipment management system (201), wherein the equipment management system (201) is configured as part of a device according to any one of claims 10 to 14, and the Device management system (201) features: - the monitoring module (288', 288", 288'"), the creation module (240) and the specification module (259), and wherein - the device management system (201) designed in this integral way is formed separately from the technical device (220', 220", 220" '), and wherein the device management system designed in this integral way Device management system (201) optionally features: - a data logger (234) designed to collect usage data (254) and / or environmental data (252) for the creation of the maintenance plan (244) and to transmit the usage data (254) and / or environmental data (252) to the creation module (240), and / or - a database (236) which is designed to store service data (256) for the creation of the maintenance plan (244), in particular maintenance intervals (266), and to pass the service data (256) to the creation module (240).

Images