Patent Application
20050021245
The present invention relates to an information providing system for a construction machine. More particularly, the present invention relates to an information providing system for a machine is used in mining and an information providing method for a machine is used in mining, which can give sufficiently satisfied care to the customer side with careful consideration.
Maintenance of machines are used in mining, such as hydraulic excavators, has conventionally been performed by servicemen who periodically make the round of their assigned areas. The servicemen measure operation data of the hydraulic construction machines and component parts thereof, and predict the life of each component based on design data and experiences. Then, the servicemen manage the timing of maintenance and other information to prevent the occurrence of troubles.
On the other hand, as disclosed in, e.g., JP,A 2000-259729, an information providing system for a construction machine is already known in which, by utilizing the recent information and communication technology, information, such as operation data, of construction machines distributed all over the world is transmitted to one place so that the information of all the construction machines is collected and managed in a centralized manner based on the transmitted data.
With that prior-art system, the operating status of each construction machine is detected as operation data by an operation sensor, and the detected operation data is periodically transmitted by an operation data communicating device to a support center installed in one place. The support center receives the transmitted operation data and records it in a main database. Based on the recorded operation data, the support center predicts a possibility of the occurrence of troubles for each construction machine and automatically outputs a report. The system having such a construction liberates the servicemen from skills otherwise required in prediction of troubles and enables the prediction of troubles to be always made at a certain level of accuracy.
In the field of construction machines, it is general that construction machine makers are engaged only in manufacturing the construction machine and actual marketing of the manufactured construction machine is performed via a plurality of selling companies (so-called dealers), branch offices, etc. Therefore, business for selling parts and customer service business, such as repair, replacement and maintenance, for the construction machines after being sold are handled by not the construction machine makers, but by the selling companies, etc. The selling companies, etc. are, for example, medium- or small-sized firms having close relations to local communities. They are usually in direct contact with customers after the time of purchasing of the machines and are well acquainted with specific situations and environments (such as natural environment, economical environment, legal situation, cultural background, and labor environment) for each local area and each customer. Based on those stances and knowledge, the selling companies, etc. can give sufficiently satisfied and appropriate care to the customers with careful consideration.
With the prior-art system described above, however, the information of all construction machines distributed all over the world is collected to one place, i.e., by one support center installed in a construction machine maker, for example, and is managed in a centralized manner. The occurrence of troubles, etc. is then predicted based on the collected information. Accordingly, a report on prediction as to the occurrence of troubles is outputted in accordance with only the judgment on the side of the maker, who has no direct contact with the customers, while bypassing the selling companies, etc. who are actually engaged in the marketing business and the service business. As a result, there is a fear that, looking from the customer side, sufficiently careful consideration is not paid and care becomes unsatisfied in such points as that questions and demands raised from the customer side regarding the contents of the report are not thoroughly responded, and the information and format of the report are not responsive to the real request from the customer side.
The present invention has been made in view of the state of the art described above, and its object is to provide an information providing system for a construction machine and an information providing method for a construction machine, which can give sufficiently satisfied care to the customer side with careful consideration.
To achieve the above object, the present invention provides an information providing system for a construction machine, the system transmitting and receiving information regarding the construction machine, wherein the system includes a server for obtaining data regarding machine operations of a plurality of construction machines via information communication and storing the obtained data in a database, and for outputting the obtained data regarding the machine operations of the plurality of construction machines via information communication.
Also, to achieve the above object, the present invention provides an information providing system for a construction machine, the system transmitting and receiving information regarding the construction machine, wherein the system includes a server which is provided on the side of a manufacturer of the construction machine or a person commissioned from the manufacturer, which obtains data regarding machine operations of a plurality of construction machines via information communication and stores the obtained data in a database, and which outputs, via information communication, the obtained data regarding the machine operations of the plurality of construction machines, as basic information for services presented to a user or an owner of each construction machine, to an information terminal provided on the side of a serviceman in charge of the services or a supervisor supervising the serviceman.
In the present invention, the data regarding the machine operations of a plurality of construction machines is taken in via information communication by the server provided on the side of the manufacturer, etc. of the construction machine and then stored in the database, and it is also outputted to the side of the serviceman, etc. as basic information for the services. Based on the basic information for the service, the salesman, etc. can make a judgment by themselves and take actions depending on situations and demands of the customer (such as the user) with whom the serviceman, etc. usually keep direct contact. For example, the data can be displayed, as final service information, on the side of the user, etc. in a predetermined form. Further, the serviceman, etc. can go to the customer side to make explanation and analysis with regard to the contents of the information, the display form and so on, as required, in response to questions, demands, etc. from the customer side.
Thus, the functions required on the manufacture side are restricted to those ones of receiving and collecting data from a large number of hydraulic excavators and distributing the data, while a judgment made based on the distributed data regarding, e.g., what kinds of care should be finally presented to the customer, is left to the side of the serviceman, etc. taking charge of services in the closest relation to the customer. As a result, unlike the prior art in which all operations ranging from data reception to services are managed at one place in a centralized manner, sufficiently satisfied and proper care can be given to the customer side with careful consideration.
Further, to achieve the above object, the present invention provides an information providing system for a construction machine, the system transmitting and receiving information regarding the construction machine, wherein the system includes a server which is provided on the side of a manufacturer of the construction machine or a person commissioned from the manufacturer, which obtains, via information communication, data regarding machine operations of a plurality of construction machines from an information terminal provided on the side of a user or an owner of each construction machine, and stores the obtained data in a database, and which outputs, via information communication, the obtained data regarding the machine operations of the plurality of construction machines, as basic information for services presented to the user or the owner, to an information terminal provided on the side of a serviceman in charge of the services or a supervisor supervising the serviceman.
Further, to achieve the above object, the present invention provides an information providing system for a construction machine, the system transmitting and receiving information regarding the construction machine, wherein the system comprises an information terminal provided on the side of a user or an owner of a construction machine and being connectable to a portable terminal for obtaining data regarding machine operation of the construction machine; a first server provided on the side of a manufacturer of the construction machine or a person commissioned from the manufacturer, obtaining data regarding the machine operation of the corresponding construction machine from each information terminal via information communication and storing the obtained data in a database, and outputting the obtained data regarding the machine operations of a plurality of construction machines, as basic information for services presented to the user or the owner, via information communication; and a second server provided on the side of a serviceman in charge of the services or a supervisor supervising the serviceman, receiving the basic information from the first server, and outputting the basic information or information resulting from the basic information, the information terminal receiving the basic information or the information resulting from the basic information from the second server, and displaying the received information, as service information presented to the user or the owner, in a predetermined form.
Still further, to achieve the above object, the present invention provides an information providing system for a construction machine, the system transmitting and receiving information regarding the construction machine, wherein the system comprises a plurality of information terminals provided on the side of users or owners of construction machines, a first server provided on the side of a manufacturer of the construction machines or a person commissioned from the manufacturer, and a plurality of second servers provided in a hierarchical form on the side of a plurality of servicemen in charge of services presented to the users or the owners and on the side of a supervisor supervising the servicemen; wherein the first server obtains data regarding machine operation of each construction machine via information communication and stores the obtained data in a database, and outputs the obtained data regarding the machine operations of the plurality of construction machines, as basic information for services presented to the users or the owners, to the second server provided on the supervisor side via information communication; wherein the second server provided on the supervisor side outputs the basic information received from the first server to a plurality of other second servers provided on the serviceman side; wherein the plurality of second servers provided on the serviceman side receive the basic information from the second server provided on the supervisor side and output, to the plurality of corresponding information terminals, the basic information directly or after optionally selecting the basic information; and wherein the plurality of information terminals each receive the basic information or information resulting from the basic information from the second server provided on the corresponding serviceman side, and display the received information, as service information presented to the user or the owner, in a predetermined form.
Still further, to achieve the above object, the present invention provides an information providing system for a construction machine, the system transmitting and receiving information regarding the construction machine, wherein the system includes a second server which is provided on the side of a serviceman in charge of services presented to a user or an owner of the hydraulic excavator, or on the side of a supervisor supervising the serviceman, which receives, as basic information for the services, data regarding machine operations of a plurality of construction machines via information communication, the data being obtained by a first server provided on the side of a manufacturer of the construction machines or a person commissioned from the manufacturer, and which outputs the basic information or information resulting from the basic information to an information terminal provided on the side of the user or the owner such that the basic information or the information resulting from the basic information is displayed in a predetermined form as service information presented to the user or the owner.
Still further, to achieve the above object, the present invention provides an information providing system for a construction machine, the system transmitting and receiving information regarding the construction machine, wherein the system comprises a supervisor-side second server which is provided on the side of a supervisor supervising a plurality of servicemen in charge of services presented to users or owners of hydraulic excavators, and which receives, as basic information for the services, data regarding machine operations of a plurality of construction machines via information communication, the data being obtained by a first server provided on the side of a manufacturer of the construction machines or a person commissioned from the manufacturer; and a plurality of serviceman-side second servers which are provided on the side of the plurality of salesmen, and each of which receives the basic information from the supervisor-side second server and outputs, to a corresponding information terminal provided on the side of the user or the owner, the basic information directly or after optionally selecting the basic information, such that the basic information or the optionally selected basic information is displayed in a predetermined form as service information to the user or the owner of the hydraulic excavator.
Preferably, in the above information providing system for the construction machine, the information terminal includes display means for displaying the service information in a predetermined graphical format, and the display means rearranges the information from the second server to form a file each time when the information is obtained from each hydraulic excavator, and displays the file in relation to a machine number or a customer management-purposed machine name of the hydraulic excavator from which the file has been obtained, and a model name or a working site name of the relevant hydraulic excavator.
With those features, the customer can easily find out desired data on the customer side, and hence convenience for the customer can be increased.
Still further, to achieve the above object, the present invention provides an information providing system for a construction machine, the system transmitting and receiving information regarding the construction machine, wherein the system includes a server which is provided on the side of a manufacturer of the construction machine or a person commissioned from the manufacturer, which obtains data regarding machine operations of a plurality of construction machines via information communication and stores the obtained data in a database, and which outputs, via information communication, the obtained data regarding the machine operations of the plurality of construction machines, as basic information for sales to a user or an owner of each construction machine, to an information terminal provided on the side of a salesman or a supervisor supervising the serviceman.
In the present invention, the data regarding the machine operations of a plurality of construction machines is taken in via information communication by the server provided on the side of the manufacturer, etc. of the construction machine and then stored in the database, and it is also outputted to the side of the salesman, etc. as basic information for the sales. Based on the basic information for the sales, the salesman, etc. can make a judgment by themselves and take actions depending on situations and demands of the customer (such as the user) with whom the salesman, etc. usually keep direct contact. For example, the data can be displayed, as final sales information, on the side of the user, etc. in a predetermined form. Further, the salesman, etc. can go to the customer side to make explanation and analysis with regard to the contents of the information, the display form and so on, as required, in response to questions, demands, etc. from the customer side.
Thus, the functions required on the manufacture side are restricted to those ones of receiving and collecting data from a large number of hydraulic excavators and distributing the data, while a judgment based on the distributed data regarding, e.g., what kinds of care should be finally presented to the customer, is left to the side of the salesman, etc. taking charge of sales in the closest relation to the customer. As a result, unlike the prior art in which all operations ranging from data reception to services are managed at one place in a centralized manner, sufficiently satisfied and proper care can be given to the customer side with careful consideration.
Still further, to achieve the above object, the present invention provides an information providing system for a construction machine, the system transmitting and receiving information regarding the construction machine, wherein the system includes a server which is provided on the side of a manufacturer of the construction machine or a person commissioned from the manufacturer, which obtains, via information communication, data regarding machine operations of a plurality of construction machines from an information terminal provided on the side of a user or an owner of each construction machine, and stores the obtained data in a database, and which outputs, via information communication, the obtained data regarding the machine operations of the plurality of construction machines, as basic information for sales to the user or the owner, to an information terminal provided on the side of a salesman or a supervisor supervising the salesman.
Still further, to achieve the above object, the present invention provides an information providing system for a construction machine, the system transmitting and receiving information regarding the construction machine, wherein the system comprises an information terminal provided on the side of a user or an owner of a construction machine and being connectable to a portable terminal for obtaining data regarding machine operation of the construction machine; a first server provided on the side of a manufacturer of the construction machine or a person commissioned from the manufacturer, obtaining data regarding the machine operation of the corresponding construction machine from each information terminal via information communication and storing the obtained data in a database, and outputting the obtained data regarding the machine operations of a plurality of construction machines, as basic information for sales to the user or the owner, via information communication; and a second server provided on the side of a salesman or a supervisor supervising the salesman, receiving the basic information from the first server, and outputting the basic information or information resulting from the basic information, the information terminal receiving the basic information or the information resulting from the basic information from the second server, and displaying the received information, as sales information presented to the user or the owner, in a predetermined form.
Still further, to achieve the above object, the present invention provides an information providing system for a construction machine, the system transmitting and receiving information regarding the construction machine, wherein the system comprises a plurality of information terminals provided on the side of users or owners of construction machines, a first server provided on the side of a manufacturer of the construction machines or a person commissioned from the manufacturer, and a plurality of second servers provided in a hierarchical form on the side of a plurality of salesmen in charge of sales to the users or the owners and on the side of a supervisor supervising the salesmen; wherein the first server obtains data regarding machine operation of each construction machine via information communication and stores the obtained data in a database, and outputs the obtained data regarding the machine operations of the plurality of construction machines, as basic information for sales to the users or the owners, to the second server provided on the supervisor side via information communication; wherein the second server provided on the supervisor side outputs the basic information received from the first server to a plurality of other second servers provided on the serviceman side; wherein the plurality of second servers provided on the serviceman side receive the basic information from the second server provided on the supervisor side and output, to the plurality of corresponding information terminals, the basic information directly or after optionally selecting the basic information, and wherein the plurality of information terminals each receive the basic information or information resulting from the basic information from the second server provided on the corresponding serviceman side, and display the received information, as sales information presented to the user or the owner, in a predetermined form.
Still further, to achieve the above object, the present invention provides an information providing system for a construction machine, the system transmitting and receiving information regarding the construction machine, wherein the system includes a second server which is provided on the side of a salesman in charge of sales to a user or an owner of the hydraulic excavator, or on the side of a supervisor supervising the serviceman, which receives, as basic information for the sales, data regarding machine operations of a plurality of construction machines via information communication, the data being obtained by a first server provided on the side of a manufacturer of the construction machines or a person commissioned from the manufacturer, and which outputs the basic information or information resulting from the basic information to an information terminal provided on the side of the user or the owner such that the basic information or the information resulting from the basic information is displayed in a predetermined form as sales information presented to the user or the owner.
Still further, to achieve the above object, the present invention provides an information providing system for a construction machine, the system transmitting and receiving information regarding the construction machine, wherein the system comprises a supervisor-side second server which is provided on the side of a supervisor supervising a plurality of servicemen in charge of sales to users or owners of hydraulic excavators, and which receives, as basic information for the sales, data regarding machine operations of a plurality of construction machines via information communication, the data being obtained by a first server provided on the side of a manufacturer of the construction machines or a person commissioned from the manufacturer; and a plurality of serviceman-side second servers which are provided on the side of the plurality of salesmen, and each of which receives the basic information from the supervisor-side second server and outputs, to a corresponding information terminal provided on the side of the user or the owner, the basic information directly or after optionally selecting the basic information, such that the basic information or the optionally selected basic information is displayed in a predetermined form as sales information presented to the user or the owner of the hydraulic excavator.
Preferably, in the above information providing system for the construction machine, the information terminal includes display means for displaying the sales information in a predetermined graphical format, and the display means rearranges the information from the second server to form a file each time when the information is obtained from each hydraulic excavator, and displays the file in relation to a machine number or a customer management-purposed machine name of the hydraulic excavator from which the file has been obtained, and a model name or a working site name of the relevant hydraulic excavator.
More preferably, in the above information providing system for the construction machine, the display means displays a list of the information from the second server, the list including the model name, the machine number corresponding to the model name, and a name of the file corresponding to the machine number, which are arranged in this order in a tree form.
Preferably, in the above information providing system for the construction machine, the display means displays a list of the information from the second server, the list including the working site name, the customer-management machine name corresponding to the working site name, and a name of the file corresponding to the customer-management machine name, which are arranged in this order in a tree form.
Preferably, in the above information providing system for the construction machine, the display means includes simultaneous display instructing means for simultaneously displaying the contents of the plural files on one screen image.
With those features, it is possible to more easily make comparative analysis of the contents of a plurality of files, and to further improve serviceability.
Furthermore, preferably, in the above information providing system for the construction machine, the display means displays, of the data in the file, change in load factor of an engine equipped in the hydraulic excavator or in pressure frequency of hydraulic actuators associated with a front operating mechanism in a color-coded representation depending on the magnitudes of numerical values of the load factor or the pressure frequency.
With those features, it is possible to recognize the load rate of the engine (i.e., degree of fuel consumption) or the excavation load imposed on the front operating mechanism, for example, at a glance, and hence to easily carry out management and evaluation of operating situations of each construction machine or characteristics of the working site.
Preferably, in the above information providing system for the construction machine, the display means displays, of the data in the file, values of an operation time and a non-operation time within a run time of the hydraulic excavator along with percentages of the values with respect to the run time.
With that feature, a comparison can be more easily made between a plurality of files (including the hydraulic excavators of different machine numbers and different models) in which absolute values of respective run times differ from each other.
Preferably, in the above information providing system for the construction machine, the server or the first server has the functions of obtaining data regarding operation per component section in a plurality of construction machines via information communication, computing, based on the obtained data, the repair/replacement timing of a part belonging to the component section for each of the construction machines, confirming parts having the repair/replacement timings substantially matched with each other among the plurality of construction machines, deciding a planned selling price of the confirmed parts depending on a quantity thereof, and outputting the planned selling price as the basic information via information communication.
In the present invention, the data regarding the operation per component section in a plurality of construction machines is taken in via information communication by the server provided on the side of the manufacturer, etc. of the construction machine and then stored in the database, for example. Further, the part repair/replacement timing is computed for each of the hydraulic excavators. Such processing is executed for all of the hydraulic excavators, and the parts having the repair/replacement timings substantially matched with each other are extracted and confirmed from among the many hydraulic excavators.
On the premise that the relevant parts are collectively repaired or replaced in all of the thus-extracted hydraulic excavators, productivity, distribution efficiency, etc. could be increased and hence the repair/replacement cost estimated for each hydraulic excavator could be greatly reduced. In view of that, the planned selling price of the relevant part is decided while reflecting a cost reduction depending on the number of the parts to be repaired or replaced, and then outputted as the basic information for services or the basic information for sales to the side of the serviceman or the salesman, etc. Furthermore, the serviceman or the salesman, etc. display the basic information, as final services information or final sales information, in a predetermined form to the customer side.
Thus, by advantageously utilizing a scale merit resulting from the capability of predicting the part repair/replacement timings of the many hydraulic excavators and by performing repair or replacement of a particular part for the many hydraulic excavators in a collective manner, it is possible to improve productivity, distribution efficiency, etc., and to greatly reduce the repair/replacement cost estimated for each hydraulic excavator. Consequently, a burden imposed on the customer side can be noticeably reduced.
Preferably, in the above information providing system for the construction machine, the server or the first server has the functions of obtaining data regarding operation per component section in a plurality of construction machines via information communication, computing, based on the obtained data, the repair/replacement timing of a part belonging to the component section for each of the construction machines, confirming parts having the repair/replacement timings substantially matched with each other among the plurality of construction machines, deciding, for the confirmed parts, a discount sales period substantially the same as or prior to the repair/replacement timing thereof and a discount selling price during the discount sales period, and outputting the discount sales period and the discount selling price as the basic information via information communication.
With those features, besides the effect described above, the side of the serviceman, etc. can obtain an effect of positively ensuring a profit and promotion of sales with advanced booking, while the customer side can obtain an effect of further reducing a cost burden based on setting of the discount selling price.
Preferably, in the above information providing system for the construction machine, the information terminal is connectable to the portable terminal for obtaining data regarding operation per component section of the construction machine; the first server obtains the data regarding the operation per component section of the corresponding construction machine from each information terminal via information communication and stores the obtained data in the database, computes, based on the data stored in the database, the repair/replacement timing of a part belonging to the component section for each of the construction machines, confirms parts having the repair/replacement timings substantially matched with each other among the plurality of construction machines, decides a planned selling price of the confirmed parts depending on a quantity thereof, and outputs the planned selling price as the basic information to the second server via information communication; the second server outputs the basic information received from the first server or the information resulting from the basic information to the information terminal; and the information terminal displays the information received from the second server, as the service information or the sales information, in a predetermined form.
Preferably, in the above information providing system for the construction machine, the information terminal is connectable to the portable terminal for obtaining data regarding operation per component section of the construction machine; the first server obtains the data regarding the operation per component section of the corresponding construction machine from each information terminal via information communication and stores the obtained data in the database, computes, based on the data stored in the database, the repair/replacement timing of a part belonging to the component section for each of the construction machines, confirms parts having the repair/replacement timings substantially matched with each other among the plurality of construction machines, decides, for the confirmed parts, a discount sales period substantially the same as or prior to the repair/replacement timing thereof and a discount selling price during the discount sales period, and outputs the discount sales period and the discount selling price, as the basic information, to the second server via information communication; the second server outputs the basic information received from the first server or the information resulting from the basic information to the information terminal, and the information terminal displays the information received from the second server, as the service information or the sales information presented to the user or the owner, in a predetermined form.
Preferably, in the above information providing system for the construction machine, the server or the first server has the functions of obtaining data regarding operation per component section of the construction machine via information communication, computing, based on the obtained data, future change in machine management cost of the construction machine and future change in machine value of the construction machine, as well as the timing at which the machine management cost and the machine value become substantially equal to each other, computing, when a particular part belonging to the component section is to be repaired or replaced before the computed timing, subsequent change in machine management cost of the construction machine and subsequent change in machine value of the construction machine resulting after the repair/replacement of the particular part, and outputting at least the subsequent change in machine management cost and the subsequent change in machine value after the repair/replacement, as the service information or the sales information presented to the user or the owner of the corresponding construction machine, via information communication.
In the present invention, the data regarding the operation per component section in a plurality of construction machines is taken in via information communication by the server provided on the side of the manufacturer, etc. of the construction machine and then stored in the database. Further, future changes in both machine management cost and machine value are computed for each construction machine, and the timing at which the machine management cost and the machine value become substantially equal to each other is also computed.
In the past, it was usual to recommend the customer to purchase a new machine substituted for an old one at that timing. Recently, however, there have increased needs for more effectively employing the currently owned old machines for a longer period through repair/replacement of parts. If the user side takes an action for prolonging the machine life, for example, by repairing or replacing at least one particular part (e.g., several or many parts having the repair/replacement timings close to each other, or a particular part having an effect of prolonging the life of the overall machine), a curve representing the machine management cost (=curve representing the repair/replacement cost estimated for the overall machine) slides toward the longer life side (i.e., the lower cost side), and a curve representing the overall machine value (=curve representing the trade-in cost) also slides toward the longer life side (i.e., the higher value side). With that point in mind, in the present invention, assuming the case that the particular part is repaired or replaced before the timing at which the machine management cost and the machine value become substantially equal to each other, subsequent changes in both machine management cost and machine value after the repair/replacement in such a case are computed. Then, at least those subsequent changes in both machine management cost and machine value after the repair/replacement (i.e., the above-mentioned sliding of the curves toward the longer life side than that estimated for the case before the repair/replacement of the part) are outputted, as the services or sales information (basic information), to the side of the serviceman, etc. The outputted information is displayed, as final services or sales information, in a predetermined form to the customer side by the serviceman or the salesman, for example.
Thus, since the user side can obtain at least the subsequent changes in both machine management cost and machine value after the repair/replacement of the part, i.e., the above-mentioned sliding of the curves toward the longer life side (lower cost side for the machine management cost curve and higher value side for machine value curve) than that estimated for the case before the repair/replacement of the part. It is hence possible to properly determine at the user's own discretion as to, for example, when and how the part is to be repaired or replaced, and how long the machine life can be extended. As a result, the user can effectively utilize the machine possessed by himself at a sufficiently satisfied level.
Preferably, in the above information providing system for a construction machine, the server or the first server has the functions of obtaining data regarding operation per component section of the construction machine via information communication, computing, based on the obtained data, future change in machine management cost of the construction machine and future change in machine value of the construction machine, as well as the timing at which the machine management cost and the machine value become substantially equal to each other, computing, when a particular part belonging to the component section is to be repaired or replaced before the computed timing, subsequent change in machine management cost of the construction machine and subsequent change in machine value of the construction machine resulting after the repair/replacement of the particular part, and outputting the subsequent. change in machine management cost and the subsequent change in machine value after the repair/replacement along with the future change in machine management cost and the future change in machine value of the construction machine, as the service information or the sales information presented to the user or the owner of the corresponding construction machine, via information communication.
Since the user side can obtain not only the subsequent changes in both machine management cost and machine value after the repair/replacement of the particular part, but also the changes in both machine management cost and machine value estimated for the case before the repair/replacement, it is possible to more exactly recognize the sliding of the curves toward the longer life side, and to reliably make an appropriate decision.
Preferably, in the above information providing system for the construction machine, the server or the first server outputs at least the subsequent change in machine management cost and the subsequent change in machine value after the repair/replacement, as data capable of being graphically displayed in the form of curves, via information communication.
Preferably, in the above information providing system for the construction machine, the information terminal is connectable to the portable terminal for obtaining data regarding operation per component section of the construction machine; the first server obtains the data regarding the operation per component section of the construction machine from the information terminal via information communication and stores the obtained data in the database, computes, based on the data stored in the database, future change in machine management cost of the construction machine and future change in machine value of the construction machine, as well as the timing at which the machine management cost and the machine value become substantially equal to each other, computes, when a particular part belonging to the component section is to be repaired or replaced before the computed timing, subsequent change in machine management cost of the construction machine and subsequent change in machine value of the construction machine resulting after the repair/replacement of the particular part, and outputs at least the subsequent change in machine management cost and the subsequent change in machine value after the repair/replacement, as the basic information, to the second server via information communication; the second server outputs, to the information terminal, the basic information received from the first server directly or after processing or optionally selecting the basic information; and the information terminal displays the information received from the second server, as the service information or the sales information, in a predetermined form.
Preferably, in the above information providing system for the construction machine, the information terminal is connectable to the portable terminal for obtaining data regarding operation per component section of the construction machine; the first server obtains the data regarding the operation per component section of the construction machine from the information terminal via information communication and stores the obtained data in the database, computes, based on the data stored in the database, future change in machine management cost of the construction machine and future change in machine value of the construction machine, as well as the timing at which the machine management cost and the machine value become substantially equal to each other, computes, when a particular part belonging to the component section is to be repaired or replaced before the computed timing, subsequent change in machine management cost of the construction machine and subsequent change in machine value of the construction machine resulting after the repair/replacement of the particular part, and outputs at least the subsequent change in machine management cost and the subsequent change in machine value after the repair/replacement along with the future change in machine management cost and the future change in machine value of the construction machine, as the basic information, to the second server via information communication; the second server outputs, to the information terminal, the basic information received from the first server directly or after processing or optionally selecting the basic information; and the information terminal displays the information received from the second server, as the service information or the sales information, in a predetermined form.
More preferably, in the above information providing system for the construction machine, the server or the first server outputs at least the subsequent change in machine management cost and the subsequent change in machine value after the repair/replacement, as data capable of being graphically displayed in the information terminal in the form of curves, to the second server via information communication.
In addition, to achieve the above object, the present invention provides an information providing method for a construction machine, the method comprising the steps of obtaining data regarding machine operations of a plurality of construction machines via information communication, and outputting, via information communication, the obtained data regarding the machine operations of the plurality of construction machines, as basic information for services and/or sales made to a user or an owner of each construction machine, to a serviceman, a salesman or a supervisor supervising the serviceman and/or the salesman.
Also, to achieve the above object, the present invention provides an information providing method for a construction machine, the method comprising the steps of obtaining, via information communication, data regarding machine operations of a plurality of construction machines from an information terminal provided on the side of a user or an owner of each construction machine, and outputting, via information communication, the obtained data regarding the machine operations of the plurality of construction machines, as basic information for services and/or sales made to the user or the owner, to the side of a serviceman, a salesman or a supervisor supervising the serviceman and/or the salesman.
Preferably, in the above information providing method for the construction machine, the method further comprises the steps of computing, based on the data obtained via information communication, the repair/replacement timing of a part belonging to the component section for each of the construction machines, confirming parts having the repair/replacement timings substantially matched with each other among the plurality of construction machines, deciding a planned selling price of the confirmed parts depending on a quantity thereof, and outputting the planned selling price as the service information and/or the sales information via information communication.
Preferably, in the above information providing method for the construction machine, the method further comprises the steps of computing, based on the data obtained via information communication, the repair/replacement timing of a part belonging to the component section for each of the construction machines, confirming parts having the repair/replacement timings substantially matched with each other among the plurality of construction machines, deciding, for the confirmed parts, a discount sales period prior to the repair/replacement timing thereof and a discount selling price during the discount sales period, and outputting the discount sales period and the discount selling price as the service information and/or the sales information via information communication.
Preferably, in the above information providing method for the construction machine, the method further comprises the steps of computing, based on the data obtained via information communication, future change in machine management cost of the construction machine and future change in machine value of the construction machine, as well as the timing at which the machine management cost and the machine value become substantially equal to each other, computing, when a particular part belonging to the component section is to be repaired or replaced before the computed timing, subsequent change in machine management cost of the construction machine and subsequent change in machine value of the construction machine resulting after the repair/replacement of the particular part, and outputting at least the subsequent change in machine management cost and the subsequent change in machine value after the repair/replacement, as the service information and/or the sales information, via information communication.
Preferably, in the above information providing method for the construction machine, the method further comprises the steps of computing, based on the data obtained via information communication, future change in machine management cost of the construction machine and future change in machine value of the construction machine, as well as the timing at which the machine management cost and the machine value become substantially equal to each other, computing, when a particular part belonging to the component section is to be repaired or replaced before the computed timing, subsequent change in machine management cost of the construction machine and subsequent change in machine value of the construction machine resulting after the repair/replacement of the particular part, and outputting the subsequent change in machine management cost and the subsequent change in machine value after the repair/replacement along with the future change in machine management cost and the future change in machine value of the construction machine, as the service information and/or the sales information, via information communication.
One embodiment of an information providing system for a construction machine according to the present invention will be described with reference to the drawings.
The hydraulic excavator 1 comprises a travel body 12, a swing body 13 swingably mounted on the travel body 12, a cab 14 provided in a front left portion of the swing body 13, and a front operating mechanism (excavating device) 15 provided in a front central portion of the swing body 13 in vertically angularly movable manner. The front operating mechanism 15 is made up of a boom 16 rotatably mounted to the swing body 13, an arm 17 rotatably mounted to a fore end of the boom 16, and a bucket 18 rotatably mounted to a fore end of the arm 17.
While the hydraulic excavator 1 is shown in
In
The hydraulic pumps 21a, 21b are driven for rotation by a diesel engine (hereinafter referred to simply as an “engine”) 32 provided with a fuel injecting device (not shown) of the so-called electronic governor type, and deliver a hydraulic fluid (working oil). The control valves (regulation valves) 22a, 22b-26a, 26b control respective flows (flow rates and flowing directions) of the hydraulic fluid supplied from the hydraulic pumps 21a, 21b to the hydraulic actuators 27-31a, 31b, and the hydraulic actuators 27-31a, 31b drive the boom 16, the arm 17, the bucket 18, the swing body 13, and the travel body 12. The hydraulic pumps 12a, 21b, the control valves 22a, 22b-26a, 26b, and the engine 32 are mounted in an accommodation room (engine room) behind the swing body 13.
Control lever devices 33, 34, 35 and 36 are disposed corresponding to the control valves 22a, 22b to 26a, 26b. When a control lever of the control lever device 33 is manipulated in one X1 of two crossed directions, an arm-crowding pilot pressure or an arm-dumping pilot pressure is produced and applied to the arm control valve 23. When the control lever of the control lever device 33 is manipulated in the other X2 of the two crossed directions, a rightward-swing pilot pressure or a leftward-swing pilot pressure is produced and applied to the swing control valve 25.
When a control lever of the control lever device 34 is manipulated in one X3 of two crossed directions, a boom-raising pilot pressure or a boom-lowering pilot pressure is produced and applied to the boom control valves 22a, 22b. When the control lever of the control lever device 34 is manipulated in the other X4 of the two crossed directions, a bucket-crowding pilot pressure or a bucket-dumping pilot pressure is produced and applied to the bucket control valve 24. Further, when control levers of the control lever devices 35, 36 are manipulated, a left-travel pilot pressure and a right-travel pilot pressure are produced and applied to the travel control valves 26a, 26b. The control lever devices 33 to 36 are disposed in the cab 14 along with the controller 2.
Sensors 40 to 49 are disposed in the hydraulic system 20 having the construction described above. The sensor 40 is a pressure sensor for detecting, as an operation signal for the front operating mechanism 15, the arm-crowding pilot pressure in this embodiment, and the sensor 41 is a pressure sensor for detecting, as a swing operation signal, the swing pilot pressure taken out through a shuttle valve 41a. The sensor 42 is a pressure sensor for detecting, as a travel operation signal, the travel pilot pressure taken out through shuttle valves 42a, 42b and 42c.
The sensor 43 is a sensor for detecting an ON/OFF state of a key switch for the engine 32, the sensor 44 is a pressure sensor for detecting the delivery pressure of the hydraulic pumps 21a, 21b, i.e., the pump pressure, taken out through a shuttle valve 44a, and the sensor 45 is an oil temperature sensor for detecting the temperature of the hydraulic oil (i.e., the oil temperature) in the hydraulic system 1. The sensor 46 is a revolution speed sensor for detecting the revolution speed of the engine 32. The sensor 47a is a fuel sensor for detecting the amount of fuel injected by the fuel injecting device of the engine 32 (i.e., the fuel consumption), the sensor 47b is a pressure sensor for detecting the blowby pressure in a cylinder of the engine 32, and the sensor 47c is a temperature sensor for detecting the temperature of a coolant (radiator water) for cooling the engine 32. The sensor 48 is a pressure sensor for detecting, as a digging pressure applied from the front operating mechanism 15, the pressure on the bottom side of the bucket cylinder 29 in this embodiment (or on the bottom side of the arm cylinder 28). The sensor 49a is a pressure sensor for detecting the traveling pressure, i.e., the pressure of the travel motor 31a or 31b (for example, a maximum one of the pressures of the travel motors 31a and 31b may be taken out through a shuttle valve not sown), and the sensor 49b is a pressure sensor for detecting the swing pressure, i.e., the pressure of the swing motor 30. Detected signals of those sensors 40 to 49 are all sent to and collected in the controller 2.
The controller 2 is to collect (as described later in detail) data regarding the machine operation for each part of the hydraulic excavator 1 (hereinafter referred to simply as “operation data”). The most important feature of the present invention resides in a flow of the operation data and manners of presenting services and sales to the customer based on the operation data.
Referring to
The operation data and the machine body data both downloaded to the user-side personal computer 4 are first processed (described later in detail) in the user-side personal computer 4 by using an application program installed therein beforehand, and are then displayed in a predetermined format as service/sales information representing the operation status of the relevant hydraulic excavator.
On the other hand, the operation data and the machine body data both downloaded to the user-side personal computer 4 are subjected to automatic search made from the side of the main server 5 via the intermediate server 6 as to whether new data is stored in the user-side personal computer, for example, when a homepage of the dealer, etc. is accessed from the user-side personal computer. If new data is found, the new data is sucked up from the user-side personal computer 4 upon consent of the user side whenever accessed. On that occasion, in addition to the operation data and the machine body data of the hydraulic excavator 1, check data, repair data, etc. obtained at the time of routine check may also be manually entered for collection by the dispatched serviceman or the serviceman (including the salesman) belonging to the dealer, etc. Then, the entered data may also be taken into the main server 5.
Thereafter, the operation data of the individual hydraulic excavators 1 thus collected is transmitted to the corresponding user-side personal computer 4 (belonging to the user of the relevant hydraulic excavator 1) via the corresponding intermediate server 6 (belonging to the dealer, etc. engaged in service/sales business for the user of the relevant hydraulic excavator 1). More specifically, among the operation data and the machine body data of all the hydraulic excavators 1 collected in the main server 5, at least data of the hydraulic excavators 1 related to the user, for example, possessed, used or managed by the user, is downloaded to the user-side personal computer 4 (including the intermediate server 6) by performing a predetermined operation on the side of the user-side personal computer 4 (e.g., by accessing the homepage of the dealer, etc. and clicking a download button on a predetermined screen). In this respect, at the discretion of the dealer, etc., it is possible to select or restrict users to which the data is to be transmitted, and to actuate a lock or disable display of a downloading screen itself for some users so that they cannot download any data.
Additionally, in
The input/output interface 2a receives, from the above-described sensors 40 to 49, the pilot pressure detected signals for the front operating mechanism 15, swing and travel, the key switch-on detected signal for the engine 32, the pump pressure detected signal for the pumps 21a, 21b, the oil temperature detected signal, the revolution speed detected signal for the engine 32, the coolant temperature detected signal, the digging pressure detected signal, the traveling pressure detected signal, the fuel consumption detected signal, the blowby pressure detected signal, and the swing pressure detected signal.
The CPU 2c processes those detected signals into predetermined operation data by using the timer (including the clock function) 2e and stores the operation data in the memory 2d.
In addition to the components described above, the controller 2 further comprises a ROM serving as a recording medium that stores control programs for causing the CPU 2c to execute the predetermined processing, and a RAM serving as memory means for temporarily storing data produced during the processing.
Referring to
If it is determined that the engine 32 is under the operation, the CPU proceeds to step 2 in which it reads the pilot pressure detected signals for the front operating mechanism, swing and travel from the sensors 40, 41 and 42 (step 2). Then, for each of the thus-read pilot pressure detected signals for the front operating mechanism, swing and travel, the CPU calculates a period of time during which the pilot pressure exceeds a predetermined one (i.e., a pilot pressure at which the front operating mechanism, the swing body or the travel body can be regarded as being operated) by using the clock information of the timer 2e. Subsequently, the CPU stores and accumulates the calculated data in the memory 2d in correspondence with the date and the time of day (step 3).
Thereafter, in step 4, the CPU reads data regarding the pump-delivery-pressure detected signal from the sensor 44, data regarding the hydraulic-oil-temperature detected signal from the sensor 45, data regarding the engine-revolution-speed detected signal from the sensor 46, data regarding the fuel consumption detected signal from the sensor 47a, data regarding the engine-blowby-pressure detected signal from the sensor 47b, data regarding the engine-coolant-temperature detected signal from the sensor 47c, data regarding the digging pressure detected signal from the sensor 48, data regarding the traveling pressure detected signal from the sensor 49a, and data regarding the swing pressure detected signal from the sensor 49b. Subsequently, the CPU stores and accumulates the read data in the memory 2d in correspondence with the date and the time of day by using the clock information of the timer 2e.
Then, during a period in which it is determined in step 1 that the engine 32 is under the operation, the engine run time is calculated by utilizing the clock information of the timer 2e, and is stored and accumulated in the memory 2d in correspondence with the date and the time of day (step 5).
The CPU 2 executes the above-described processing of steps 1 to 5 per predetermined time unit (=cycle) (e.g., per several minutes to several tens minutes) while a source power for the controller 2 is held ON. As a result, the memory 2d accumulates therein the front operation time, the swing operation time and the travel lever operation time during the predetermined cycle in accordance with step 3, an average pump delivery pressure, an average oil temperature, an average engine revolution speed, an average fuel consumption rate, an average engine blowby pressure, an average coolant temperature, an average digging pressure and an average traveling pressure during the predetermined cycle in accordance with step 4, as well as an average engine run time in accordance with step 5 (see
On that occasion, for the time data described above, respective values accumulated whenever each cycle lapses, i.e., an accumulated front operation time, an accumulated swing operation time, an accumulated travel lever operation time, and an accumulated engine run time are separately calculated and stored in the memory 2d while updating the previous values (see
In addition, though not described here in detail, various event data, such as engine on/off data and key switch on/off data, various alarm data, and so on are also time-serially stored in the memory 2d (see
Returning to
Referring to
A main portion of the operation data after the file header is constituted, as a first set of data, by the data accumulated after manufacturing of the relevant hydraulic excavator. More specifically, the accumulated data comprises, for example, the accumulated engine run time, various accumulated operation times (such as the accumulated lever operation (including travel) time, the accumulated swing operation time and the accumulated travel lever operation time), and an accumulated frequency distribution (see a later description on a frequency distribution).
Subsequent to the accumulated data mentioned above, items of data sectioned per cycle are time-serially arranged. More specifically, those items contain the time of day at which the data was obtained, and the accumulated engine run time up to the preceding cycle, followed by the engine run time, the respective operation times (such as the lever operation (including travel) time, the swing operation time and the travel lever operation time), respective frequency distributions (such as an engine revolution speed distribution, a hydraulic oil temperature distribution, a coolant temperature distribution, a pump delivery pressure distribution, a digging pressure distribution, and a traveling pressure distribution), the average engine blowby pressure, the average fuel consumption rate, the average pump delivery pressure, the average oil temperature, the average engine revolution speed, the average coolant temperature, the average digging pressure, the average traveling pressure, and so on. In this connection, for easier understanding of the frequency distributions, the frequency distributions are each represented by previously setting a plurality of frequency areas (e.g., 5 minutes in the engine revolution speed range of 0 to 600 rpm, 2 minutes in the range of 600 to 800 rpm, and 15 minutes in the range of 800 to 1000 rpm), and by indicating time lengths falling in the respective frequency ranges on the basis of unit time (e.g., the engine revolution speed range of 0 to 600 rpm, of 600 to 800 rpm, and of 800 to 1000 rpm).
After the above-mentioned data per cycle unit, there follows the event/alarm and other data. In the illustrated example, the event/alarm and other data contains the date and the time of day at which the event/alarm and other has occurred, and the number of the event/alarm and other. The accumulated engine run time at that time (e.g., the above-mentioned accumulated engine run time) is also indicated as reference data.
The operation data, which has been downloaded from the controller 2 to the portable terminal 3 in the above-mentioned file format, is taken into the user-side personal computer 4 in the same file format. The taken-in data is processed by the application program previously installed (or another one distributed and installed, as required, from the dealer side, for example), as described above, and is then indicated in a predetermined format as information representing the operation status of the relevant excavator.
Referring to
The personal computer body 4A comprises communication interfaces (I/O) 4a, 4b serving respectively as input means and output means, a CPU (Central Processing Unit) 4c serving as processing means, a RAM 4d serving as memory means, a storage device (storing and holding means) 4e including a program storage area (ROM) 4ea and a data storage area 4eb, and a display interface 4f.
The communication interface 4a receives not only operation signals from the keyboard 4D and the mouse 4C, but also the operation data having the file structure, shown in
The CPU 4c processes the stored operation data based on the received operation signals into data in conformity with a predetermined display format by using a data processing program (described later) that has been stored in the program storage area 4ea of the storage device. On that occasion, data produced during the processing is temporarily stored, as required, in the RAM 4d serving as memory means. The processed operation data is displayed on the display unit 4B in the predetermined format via the display interface 4f.
Additionally, the not-yet-processed operation data stored in the data storage area 4eb of the storage device can be outputted to the main server 5 via the communication interface 4b in accordance with operation signals from the keyboard 4D and the mouse 4C. This point will be described later.
As shown in
Further, the information displaying program 110 is made up of a data processing program 120 for processing the operation data stored in the data storage area 4eb of the storage device to be matched with the predetermined display format, and a standard screen program 130 including various functions related to screen display itself.
The data processing program 120 is made up of a life data processing program 121, a daily data processing program 122, an hours data processing program 123, a ratio data processing program 124, a summary data processing program 125, a utilization data processing program 126, a blowby data & fuel-consumption-rate data processing program 127, an event/alarm and other data processing program 128, and a histogram processing program 129 for respectively preparing life data, daily data, hours data, ratio data, summary data, utilization data, blowby data & fuel consumption rate data, event/alarm and other data, and histogram data, which are described later.
The standard screen program 130 contains a mail outputting program 131, a storing program 132, and a printing program 133, which serve to respectively send data displayed on a screen image to any desired address by electronic mail, store it in a predetermined place (e.g., the storage area 4eb of the storage device), and print it. The standard screen program 130 further contains a file information displaying program 134 for displaying the property of each file, and a multi-screen displaying program 135 for displaying data of a plurality of files (other files than one that is now opened) at the same time.
Detailed processing steps and function of each program will be described later.
Examples of display screen images presented on the display unit 4B by the functions of the above-mentioned programs will be described below one by one.
In
Such a division of the screen into the areas A to F enables an operator to look for any desired data with more ease. Also, since the graph display area B for displaying the operation data itself is arranged so as to occupy a most part of the screen, the operator can more easily look at a displayed graph. Further, the second graph selection area C in the form of a menu bar is always displayed, while the first graph selection area A in a tree structure can be selectively displayed or not displayed at the operator's discretion. By selecting the first graph selection area A to be not displayed, the graph display area B is displayed in a larger size so that the operator can more easily look at a graph.
The areas A to F will be described in more detail below in order.
(1) First Graph Selection Area A
As shown in
The tree structure is not limited to the above-described one, but it may be rewritable, as required, to contain, for example, a folder having an operation site name (e.g., “OO prefecture, OO city, xx work site”) for the hydraulic excavator 1, a folder having a specific machine name (e.g., “first loader in xx work site”) for customer management, and a book file name. Such a structure enables the data to be displayed and changed in a more easily understandable manner to the user.
Further, while in the illustrated example the download date and time (e.g., “OO/□/x (year/month/day)” is directly used as the book file name, the range of date and time (e.g., “OO/□/x to OO/Δ/□ (year/month/day)”) covering the data contained in the file may also be employed instead. This modification enables the operator to easily look for any one among plural sets of the downloaded data, which corresponds to the desired period. Alternatively, for example, when the number of files is small, the simple file number or the like (e.g., “No. 5”) may be displayed for simplification of display. Further, in a display state in which only the machine number (e.g., “501” or “504” in the illustrated example) is displayed before opening any file name, the latest download data and time of day, for example, may be displayed on the right side of the machine number so that the operator can recognize the date and the time of day of the latest date without opening a lower-level layer (i.e., any file name). Additionally, where no file is stored for the latest predetermined period (e.g., three months) or more, the relevant machine number name may be displayed in a different color, thereby prompting the operator to download the latest file.
In the illustrated example, each operation data file contains, in a lower level layer, a “life data” file, an “operation data” folder, an “alarm and fault data” folder, an “event data” file, and a “histogram data” folder.
The “operation data” folder contains, in an even lower level layer, a “daily data” file, an “hours data” file, a “ratio data” file, a “summary data” file, a “utilization data” folder, a “blowby data” file, and a “fuel consumption rate data” file. The “utilization data” folder contains, in an even lower level layer, an “hours data” file and a “ratio data” file.
The “alarm and fault data” folder contains, in an even lower level layer, an “alarm data” file and a “fault data” file.
The “histogram data” folder contains an “engine speed data” file, a “hydraulic oil temperature data” file, a “coolant temperature data” file (not shown), a “pump pressure data” file (not shown), a “digging pressure data” file (not shown), and a “traveling pressure data” file (not shown).
The reason why there are a plurality of files having machine model names and machine numbers in the examples shown in
(2) Graph Display Area B
Each of the above-mentioned data files or folders will be described one by one in more detail below.
(2-1) Life Data
The “life data” file is displayed by processing the operation data, which is stored in the data storage area 4ea of the storage device in the user-side personal computer 4, into accumulated operation information since the start of operation of the hydraulic excavator 1 (e.g., the time of machine delivery) after manufacturing thereof.
Referring to
Then, in step 141, by using both the accumulated engine run time Teng contained in the accumulated data and the lever operation (including travel) time Tlever obtained from the various accumulated operation times therein, a non-operation time Tnop is calculated from the following formula:
non-operation time Tnop=accumulated engine run time Teng−lever operation time Tlever
Then, in step 142, by using the non-operation time Tnop determined step 141, a non-operation time rate Tr_nop [%] is calculated from the following formula:
non-operation time rate Tr—nop=(non-operation time Tnop/accumulated engine run time Teng)×100
Thereafter, in step 143, by using the travel lever operation time Ttravel obtained from the various accumulated operation times contained in the accumulated data, an operation time rate Tr_lever_ex_travel [%] of the work lever (except for travel) is calculated from the following formula:
work lever operation time rate Tr_lever—ex_travel={(lever operation time Tlever−travel lever operation time Ttravel)/accumulated engine run time Teng)×100[%]
Then, in step 144, a travel lever operation time rate Tr_travel [%] is calculated from the following formula:
travel lever operation time rate Tr_travel=(travel lever operation time Ttravel/accumulated engine run time Teng)×100[%]
Thereafter, the CPU proceeds to step 145 and displays the non-operation time Tnop, the travel lever operation time Ttravel, the work lever operation time Tlever_ex_travel, and the accumulated engine run time Teng in the form of bar graphs, which have been obtained as described above.
Then, the CPU proceeds to step 146 and displays, as numerals, the respective values of the non-operation time Tnop, the travel lever operation time Ttravel, the work lever operation time Tlever_ex_travel, and the accumulated engine run time Teng on the right side of fore ends of the bar graphs representing the non-operation time Tnop (Non-Operation), the travel lever operation time Ttravel (Travel), the work lever operation time Tlever_ex_travel (Operation), and the accumulated engine run time Teng (Engine Run), respectively. In addition, the CPU also displays, as numerals, the non-operation time rate Tr_nop, the travel lever operation time rate Tr_travel, the work lever operation time rate Tr_lever_ex_travel, and the accumulated engine run time rate (=100[%]).
In a graph illustrated in
Furthermore, assuming the accumulated engine run time Teng to be 100[%], the respective values of the non-operation time rate Tr_nop, the travel lever operation time rate Tr_travel, the work lever operation time rate Tr_lever_ex_travel, and the accumulated engine run time rate are also displayed as numerals. This graphic display makes it easier to compare data among a plurality of hydraulic excavators 1 differing in the engine run time from each other (see also
On the right side of the bar graphs, there is a “memo box” in which the operator is able to enter a memo as required. Accordingly, it is possible to enter, as a memo, the matters that cannot be displayed by graphs.
Moreover, two tags “Graph” and “Report” are selectably displayed in an upper left portion of the area B of the screen, thus enabling the operator to display data of the same contents in the form of a graph or a list including numerical values in a selectable manner (
In
While, in
(2-2) Daily Data
The “daily data” file is displayed by processing the operation data, which is stored in the data storage area 4ea of the storage device in the user-side personal computer 4, into various kinds of general operation information per day over the range of several days to one month or several tens days, for example.
Referring to
Then, in step 151, the CPU sets an operator i=a, which is used for counting the time unit data, followed by proceeding to step 152.
In step 152, the CPU reads the engine run time Teng in the time unit data [i] and determines whether the read time is not shorter than a predetermined time Td1 (e.g., ½ of the time unit). If this determination is satisfied, the CPU proceeds to step 153 in which the relevant box (i.e., the box corresponding to the time unit [i]) is painted all over in a first color (e.g., light blue). Thereafter, the CPU proceeds to step 154.
In step 154, the CPU reads the lever operation (including travel) time Tlever in the time unit data [i] and determines whether the read time is not shorter than a predetermined time Td2 (e.g., ½ of the time unit). If this determination is satisfied, the CPU proceeds to step 155 in which the relevant box (i.e., the box corresponding to the time unit [i]) is painted all over in a second color (e.g., yellowish green). Thereafter, the CPU proceeds to step 156. If the determination is not satisfied in step 152 or step 154, the CPU directly proceeds to step 156. As a result, if both the conditions in steps 152 and 154 are satisfied, the relevant box is painted in a deep green color resulting from mixing of light blue and yellowish green. If the condition in step 152 alone is satisfied, the relevant box is painted just in a light blue color.
In step 156, the operator i is incremented by one, and it is determined in step 157 whether i is larger than b. If this determination is not satisfied, the CPU returns to step 152 and repeats the same sequence of steps as that described above. If that determination is satisfied, the processing flow is brought to an end.
With the processing steps described above, the box of the time unit [i] corresponding to the state in which the engine run time is not less than a certain value and the lever operation time is not less than a certain value (namely the state of the hydraulic excavator 1 being under the operation) is painted in a deep green color, while the box of the time unit [i] corresponding to the state in which the engine run time is not less than the certain value, but the lever operation time is less than the certain value (namely the engine idling state) is painted just in a light blue color.
In a graph illustrated in
In an upper left region of the screen, there are disposed a “month selection pull-down menu” in the form of a menu bar enabling the operator to select year/month of the desired data to be displayed, a “+” button, and a “−” button. The operator can directly and promptly select the month to be displayed by using the “pull-down menu”, and can simply change the month to be displayed by using the “+” and “−” buttons. On the right side of the “+” and “−” buttons, a “time zone pull-down menu” in the form of a menu bar is disposed so that the operator can select the desired time zone to be displayed. In addition to the time zone of “6-18” shown in
Referring to
In step 162, similarly to step 152, the CPU reads the engine run time Teng in the time unit data [i] and determines whether the read time is not shorter than a predetermined time Td1 (e.g., ½ of the time unit). If this determination is satisfied, the CPU proceeds to step 163 in which it reads the average fuel consumption rate Qf in the time unit data [i] and determines whether the read rate is not smaller than a first predetermined value (25% in this example). If this determination is not satisfied, the CPU proceeds to step 169 in which the relevant box (i.e., the box corresponding to the time unit [i]) is painted all over in a first color (e.g., light blue). Thereafter, the CPU proceeds to step 167 described later.
If the determination in step 163 is satisfied, the CPU proceeds to step 164 in which it determines whether the average fuel consumption rate Qf in the time unit data [i] is not smaller than a second predetermined value (50% in this example) which is larger than the first predetermined value. If this determination is not satisfied, the CPU proceeds to step 170 in which the relevant box (i.e., the box corresponding to the time unit [i]) is painted all over in a second color (e.g., yellowish green). Thereafter, the CPU proceeds to step 167 described later.
If the determination in step 164 is satisfied, the CPU proceeds to step 165 in which it determines whether the average fuel consumption rate Qf in the time unit data [i] is not smaller than a third predetermined value (75% in this example) which is larger than the second predetermined value. If this determination is not satisfied, the CPU proceeds to step 171 in which the relevant box (i.e., the box corresponding to the time unit [i]) is painted all over in a third color (e.g., green). Thereafter, the CPU proceeds to step 167 described later.
If the determination in step 165 is satisfied, the relevant box (i.e., the box corresponding to the time unit [i]) is painted all over in a fourth color (e.g., red). Thereafter, the CPU proceeds to step 167.
In step 167, the operator i is incremented by one, and it is determined in step 168 whether i is larger than b. If this determination is not satisfied, the CPU returns to step 162 and repeats the same sequence of steps as that described above. If that determination is satisfied, the processing flow is brought to an end.
With the processing steps described above, when the engine run time is not more than a certain value, the box is not colored. When the engine run time is not less than the certain value, the box is displayed in a color differing in the order of light blue, yellowish green and green as the fuel consumption rate (stated another way, the engine load rate) increases. Further, when the fuel consumption rate is a maximum range, the box is displayed in a red color.
In a graph illustrated in
While the color-coded display is performed depending on the fuel consumption rate in the example described above, the present invention is not limited to such a display way. For example, the color-coded display may be performed depending on the digging pressure (i.e., the bottom side pressure of the bucket cylinder 29 or the arm cylinder 28). The color-coded display can be realized, for example, by determining whether the rate of a time during which a predetermined pressure is reached in the desired time zone is large or small, or whether the number of times of pressure peaks is large or small. This enables the operator to recognize the digging load per time zone at a glance. As a result, it is possible to facilitate structure evaluation of the front operating mechanism 15 of each hydraulic excavator 1 or, in particular, the necessity of a blast (with a dynamite) for assisting the digging carried out by the so-called large-scaled and super-large-scaled hydraulic excavators, evaluation of the blast properties, etc.
(2-3) Hours Data
The “hours data” file is displayed by processing the operation data, which is stored in the data storage area 4ea of the storage device in the user-side personal computer 4, into various kinds of operation information (display per unit interval in time of day; see
Referring to
Then, in step 181, the CPU sets an operator i=a, which is used for counting the time unit data, followed by proceeding to step 182.
In step 182, by using the engine run time Teng and the lever operation (including travel) time Tlever both contained in the time unit data [i], a non-operation time Tnop is calculated from the following formula:
non-operation time Tnop=engine run time Teng−lever operation time Tlever
Thereafter, in step 183, by using the travel lever operation time Ttravel contained in the time unit data [i], a work lever operation (except for travel) time T_lever_ex_travel is calculated from the following formula:
work lever operation time Tlever—ex_travel=lever operation time Tlever−travel lever operation time Ttravel
Thereafter, the CPU proceeds to step 184 and plots the engine run time Teng on the graph. Subsequently, the CPU plots on the graph the work lever operation time Tlever_ex_travel calculated in above step 185, and also plots on the graph the travel lever operation time Ttravel calculated in above step 186.
Then, the CPU proceeds to step 187 in which the operator i is incremented by one, and it determines in step 188 whether i is larger than b. If this determination is not satisfied, the CPU returns to step 182 and repeats the same sequence of steps as that described above. If that determination is satisfied, the processing flow is brought to an end.
In a graph illustrated in
In this respect, two tags “Graph” and “Report” similar to those described above are selectably displayed in an upper left portion of the area B of the screen, thus enabling the operator to display data of the same contents in the form of a graph or a list including numerical values in a selectable manner (
Under the two tags in an upper left portion of the area B of the screen, there are disposed a “daily” button corresponding to the above-mentioned display per unit interval in time of day and a “Monthly” button corresponding to the above-mentioned display per day so that the operator can select the time of day and the day in month.
In addition, at the bottom of the screen, the number of times at which various alarms (described later in detail) occurred per unit interval in time of day (per 30 minutes in this example) is displayed as numerical data as information for reference. On the farther right side of the “daily” button, an “alarm list display pull-down menu” in the form of a menu bar is disposed to allow selection of the alarm type to be displayed at the bottom of the screen from a displayed list. Thus, the operator can directly and promptly select the alarm type for which the number of times of occurrences is to be displayed.
While, in the example described above, legends for the graph, i.e., “Travel”, “Operation (except for travel)”, and “Engine Run” , are displayed in an upper right portion of the area B, the legends may be movable to a place near the vertical axis on the left side with a proper manipulation as required. Such a movement of the legends makes the graph more easily viewed. Further, though not shown, the graph may be designed such that the operator can make a bookmark or a memo in any desired place on the graph. In such a case, the operator can manage, along with the graph, the matters that cannot be expressed by only the graph. Moreover, the background of the graph may be color-coded, for example, such that the time zone in which the engine is not operated (in
Referring to
Then, in step 191, the CPU sets an operator j=1, which is used for counting the time unit data, followed by proceeding to step 193.
In step 193, by using the lever operation (including travel) time Tlever and the travel lever operation time Ttravel both contained in the time unit data [i], a work lever operation (except for travel) time Tlever_ex_travel is calculated from the following formula:
work lever operation time Tlever—ex_travel=lever operation time Tlever−travel lever operation time Ttravel
Thereafter, the CPU proceeds to step 194 in which the operator j is incremented by one, and it determines in step 195 whether j is not smaller than 24. If this determination is not satisfied, the CPU returns to step 191 and repeats the same sequence of steps as that described above. As a result, respective values of the work lever operation time Tlever_ex_travel in the time unit data [1] to [24] (per hour) for 24 hours in the desired day [k] are extracted.
If the determination in step 195 is satisfied, the CPU proceeds to step 197 in which the respective values of the work lever operation time Tlever_ex_travel for 24 hours in the desired day [k], which have been extracted as described above, are totalized to obtain:
daily accumulated work lever operation time Tlever_ex_travel_day [k]=Σ Tlever_ex_travel [j]
Thereafter, in step 198, the respective values of the travel lever operation time Ttravel for 24 hours in the desired day [k], which have been extracted as described above, are totalized to obtain:
daily accumulated travel lever operation time Ttravel_day [k]=Σ Ttravel [j]
Then, in step 199, a daily accumulated engine run time Teng_day is calculated by adding the engine run time Teng in the time unit, which is contained in the last time unit data [24], to the accumulated engine run time Teng contained in the last time unit data [24].
Thereafter, the CPU proceeds to step 200 in which the daily accumulated work lever operation time Tlever_ex_travel_day [k], the daily accumulated travel lever operation time Ttravel_day [k], and the daily accumulated engine run time Teng_day, which have been calculated respectively in above steps 197, 198 and 199, are plotted on a graph.
Then, the CPU proceeds to step 201 in which the operator k indicating the date is incremented by one, and it determines in step 202 whether k is larger than a value representing the date of the time unit data [b]. If this determination is not satisfied, the CPU returns to step 190 and repeats the same sequence of steps as that described above. As a result, for a period spanning from the extracted time unit data [a (e.g., O/x/Δ (month/day/hour))] to the extracted time unit data [b (e.g., x/O/□ (month/day/hour))], the daily accumulated work lever operation time Tlever_ex_travel_day [k], the accumulated travel lever operation time Ttravel_day [k], and the daily accumulated engine run time Teng_day are plotted on the graph.
If the determination in step 202 is satisfied, the processing flow is brought to an end.
In a graph illustrated in
In the illustrated example, the accumulated engine run time Teng (Hour Meter) is also displayed as the life data, and a vertical axis representing the accumulated engine run time is indicated on the right side. This vertical axis is defined, for example, to be fixed to a predetermined time t (e.g., t=1200 hours) from an hour meter value at the beginning of each month (namely, to fix a reduced scale of that vertical axis). Such display makes it possible to easily compare behaviors between the progress (slope) of the hour meter and the time per operation type among a plurality of machine models, and to lay a proper maintenance plan.
The processing flow shown in
non-operation time Tnop=engine run time Teng−lever operation time Tlever
The non-operation time Tnop in each desired day [k] thus calculated is plotted on the graph in step 200. The processing flow shown in
In
In
(2-4) Ratio Data
The “ratio data” file is displayed by converting the unit of the vertical axis of the graph representing the “hours data” file, described in above (2-3), from an absolute value to a rate (e.g., a percentage relative to the engine run time Teng set to 100%). Then, the “ratio data” file is displayed by processing the operation data, which is stored in the data storage area 4ea of the storage device in the user-side personal computer 4, into various kinds of operation information (display per unit interval in time of day) representing detailed behaviors over the range of 24 hours for each day, or into various kinds of behavior information (display per day) representing detailed behaviors over the range of several tens days to one month, for example, similarly to the hours data described above.
Referring to
Then, in step 211, the CPU sets an operator i=a, which is used for counting the time unit data, followed by proceeding to step 212.
In step 212, by using the lever operation (including travel) time Tlever and the travel lever operation time Ttravel both contained in the time unit data [i], an operation time Tlever_ex_travel of the work lever except for travel is calculated from the following formula: work lever operation time Tlever_ex_travel=lever operation time Tlever—travel lever operation time Ttravel Then, in step 213, by using the engine run time Teng contained in the time unit data [i], a work lever operation time rate Trlever_ex_travel is calculated from the following formula:
work lever operation time rate Trlever—ex_travel=(work lever operation time Tlever—ex_travel/engine run time Teng)×100
Thereafter, the CPU proceeds to step 214 in which a travel lever operation time rate Tr_travel is calculated from the following formula:
travel lever operation time rate Tr_travel=(travel lever operation time Ttravel/engine run time Teng)×100
Then, the CPU proceeds to step 215 in which the work lever operation time rate Trlever_ex_travel and the travel lever operation time rate Tr_travel are plotted on a graph along with numerical values.
Then, the CPU proceeds to step 216 in which the operator i is incremented by one, and it determines in step 217 whether i is larger than b. If this determination is not satisfied, the CPU returns to step 212 and repeats the same sequence of steps as that described above. If that determination is satisfied, the processing flow is brought to an end.
In a graph illustrated in
Referring to
Then, in step 221, the CPU sets an operator j=1, which is used for counting the time unit data, followed by proceeding to step 222.
In step 222, by using the lever operation (including travel) time Tlever and the travel lever operation time Ttravel both contained in the time unit data [i], a work lever operation (except for travel) time Tlever_ex_travel is calculated from the following formula:
work lever operation time Tlever—ex_travel=lever operation time Tlever−travel lever operation time Ttravel
Thereafter, the CPU proceeds to step 223 in which the operator j is incremented by one, and it determines in step 224 whether j is not smaller than 24. If this determination is not satisfied, the CPU returns to step 221 and repeats the same sequence of steps as that described above. As a result, respective values of the work lever operation time Tlever_ex_travel in the time unit data [1] to [24] (per hour) for 24 hours in the desired day [k] are extracted.
If the determination in step 224 is satisfied, the CPU proceeds to step 225 in which the respective values of the engine run time Teng for 24 hours in the desired day [k], which have been extracted as described above, are totalized to obtain:
daily accumulated engine run time Teng_day [k]=Σ Teng [j]
Thereafter, in step 226, the respective values of the work lever operation time Tlever_ex_travel for 24 hours in the desired day [k], which have been extracted as described above, are totalized to obtain:
daily accumulated work lever operation time Tlever_ex_travel_day [k]=Σ Tlever_ex_travel [j]
Further, by using Σ Tlever_ex_travel [j] and the daily accumulated engine run time Teng_day [k], a work lever operation time rate Tr_lever_ex_travel_day [k] per day is calculated from the following formula:
work lever operation time rate Tr_lever—ex_travel_day [k]=(Σ Tlever—ex_travel [j]/Teng_day [k])×100
Thereafter, in step 227, the respective values of the travel lever operation time Ttravel for 24 hours in the desired day [k], which have been extracted as described above, are totalized to obtain:
daily accumulated travel lever operation time Ttravel_day [k]=Σ Ttravel [j]
Further, by using Σ Ttravel [j] and the daily accumulated engine run time Teng_day [k], a travel lever operation time rate Tr_travel_day [k] per day is calculated from the following formula:
travel lever operation time rate Tr_travel_day [k]=(Σ Ttravel [j]/Teng_day [k])×100
Thereafter, in step 228, a daily accumulated engine run time Teng_day is calculated by adding the engine run time Teng in the time unit, which is contained in the last time unit data [24], to the accumulated engine run time Teng contained in the last time unit data [24].
Thereafter, the CPU proceeds to step 229 in which the daily work lever operation time rate Tr_lever_ex_travel_day [k], the daily accumulated travel lever operation time rate Tr_travel_day [k], and the daily accumulated engine run time Teng_day [k], which have been calculated respectively in above steps 226, 227 and 228, are plotted on a graph along with numerical values.
Then, the CPU proceeds to step 230 in which the operator k indicating the date is incremented by one, and it determines in step 231 whether k is larger than a value representing the date of the time unit data [b]. If this determination is not satisfied, the CPU returns to step 220 and repeats the same sequence of steps as that described above. As a result, for a period spanning from the extracted time unit data [a (e.g., O/x/Δ (month/day/hour))] to the extracted time unit data [b (e.g., x/O/Δ (month/day/hour))], the daily accumulated work lever operation time rate Tr_lever_ex_travel_day [k], the daily accumulated travel lever operation time rate Tr_travel_day [k], and the daily accumulated engine run time Teng_day [k] are plotted on the graph.
If the determination in step 231 is satisfied, the processing flow is brought to an end.
In a graph illustrated in
In the illustrated example of
Further, in the graphs of
Additionally, it is also possible to prepare, e.g., display of a calendar, “+” and “−” buttons, movable arrangement of the legends, a space for making a bookmark or a memo, and colored display of the engine non-run time zones. Such a modified screen layout can also provide similar advantages to those described above.
(2-5) Summary Data
The “summary data” file is to display data having the same contents as those of the “life data” file, described above in (2-1), by processing the operation data, which is stored in the data storage area 4ea of the storage device in the user-side personal computer 4, into accumulated operation information for a period designated by the operator, instead of accumulated operation information from the start of operation of the hydraulic excavator 1 after manufacturing thereof to the present time.
Referring to
Then, in step 241, the CPU sets an operator i=a, which is used for counting the time unit data, followed by proceeding to step 242.
In step 242, by using both the engine run time Teng contained in each time unit data [i] and the lever operation (including travel) time Tlever obtained from the various operation times therein, a non-operation time Tnop in each time unit is calculated from the following formula:
non-operation time Tnop=engine run time Teng−lever operation time Tlever
Then, in step 243, by using the travel lever operation time Ttravel contained in each time unit data [i], a work lever operation time Tlever_ex_travel in each time unit is calculated from the following formula:
work lever operation time Tlever—ex_travel=lever operation time Tlever−travel lever operation time Ttravel
Thereafter, the CPU proceeds to step 244 in which the operator i is incremented by one, and it determines in step 245 whether i is larger than b. If this determination is not satisfied, the CPU returns to step 242 and repeats the same sequence of steps as that described above. As a result, respective values of the non-operation time Tnop and the travel lever operation time Ttravel in each time unit are obtained for all of the time unit data [a] to [b] in the desired period.
If the determination in step 245 is satisfied, the CPU proceeds to step 246 in which the respective values of the non-operation time Tnop in all of the time units [a] to [b] calculated in above step 242 are totalized to obtain:
accumulated non-operation time Ts—nop in desired period (e.g., certain month)=Σ T—nop [i]
Thereafter, in step 247, the respective values of the work lever operation time Tlever_ex_travel in all of the time units [a] to [b] calculated in above step 243 are totalized to obtain:
accumulated work lever operation time Ts_lever—ex_travel in desired period (e.g., certain month)=Σ Tlever—ex_travel [i]
Then, in step 248, the respective values of the travel lever operation time Ttravel in all of the time units [a] to [b], which have already been extracted, are totalized to obtain:
accumulated travel lever operation time Ts_travel in desired period (e.g., certain month)=Σ Ttravel [i]
Thereafter, in step 249, the respective values of the engine run time Teng in all of the time units [a] to [b], which have already been extracted, are totalized to obtain:
accumulated engine run time Ts—eng in desired period (e.g., certain month)=Σ Teng [i]
Thereafter, in step 250, by using the accumulated non-operation time Ts_nop and the accumulated engine run time Ts_eng which have been obtained respectively in above steps 246 and 249, a non-operation time rate Tr_s_nop in the desired period (e.g., certain month) is calculated from the following formula:
Tr—s—nop=(Ts—nop/Ts—eng)×100
Then, in step 251, by using the accumulated work lever operation time Ts_lever_ex_travel which has been obtained in above step 247, a work lever operation time rate Tr_s_lever_ex_travel in the desired period (e.g., certain month) is calculated from the following formula:
Tr—s_lever—ex_travel=(Ts_lever—ex_travel/Ts—eng)×100
Thereafter, in step 252, by using the accumulated travel lever operation time Ts_travel which has been obtained in above step 248, a travel lever operation time rate Tr_s_travel in the desired period (e.g., certain month) is calculated from the following formula:
Tr—s_travel=(Ts_travel/Ts—eng)×100
Thereafter, the CPU proceeds to step 253 and displays the accumulated non-operation time Ts_nop (Non-Operation), the accumulated travel lever operation time Ts_travel (Travel), the accumulated work lever operation time Ts_lever_ex_travel (Operation), and the accumulated engine run time Ts_eng (Engine Run) in the desired period in the form of bar graphs, which have been obtained in above steps 246, 247 and 248.
Then, in step 254, the respective values of the accumulated non-operation time Ts_nop, the accumulated travel lever operation time Ts_travel, the accumulated work lever operation time Ts_lever_ex_travel, and the accumulated engine run time Ts_eng are displayed, as numerals, on the right side of fore ends of the bar graphs displayed in above step 253. In addition, the non-operation time rate Tr_s_nop, the travel lever operation time rate Tr_s_travel, the work lever operation time rate Tr_s_lever_ex_travel, and the accumulated engine run time rate (=100[%]) in the desired period, which have been obtained respectively in above steps 250, 251 and 252, are also displayed as numerals.
In a graph illustrated in
Furthermore, assuming the accumulated engine run time Ts_eng to be 100[%], the respective values of the non-operation time rate Tr_s_nop, the travel lever operation time rate Tr_s_travel, the work lever operation time rate Tr_s_lever_ex_travel, and the accumulated engine run time rate are also displayed as numerals. This graphic display makes it easier to compare data among a plurality of hydraulic excavators 1 differing in the engine run time from each other (see also
Moreover, as in the display screen images of the life data shown in
In
While, in
(2-6) Utilization Data
The “utilization data” file is displayed by processing the operation data, which is stored in the data storage area 4ea of the storage device in the user-side personal computer 4, into information indicating transition of an operation item ratio per month or week, for example.
Referring to
Then, in step 261, the CPU sets an operator i=a, which is used for counting the time unit data, followed by proceeding to step 262.
In step 262, by using both the engine run time Teng contained in each time unit data [i] and the lever operation (including travel) time Tlever obtained from the various operation times therein, a non-operation time Tnop in each time unit is calculated from the following formula:
non-operation time Tnop=engine run time Teng−lever operation time Tlever
Then, in step 263, by using the travel lever operation time Ttravel contained in each time unit data [i], a work lever operation time Tlever_ex_travel in each time unit is calculated from the following formula:
work lever operation time Tlever—ex_travel=lever operation time Tlever−travel lever operation time Ttravel
Thereafter, the CPU proceeds to step 264 in which the operator i is incremented by one, and it determines in step 245 whether i is larger than b. If this determination is not satisfied, the CPU returns to step 262 and repeats the same sequence of steps as that described above. As a result, respective values of the non-operation time Tnop and the travel lever operation time Ttravel in each time unit are obtained for all of the time unit data [a] to [b] in the desired month.
If the determination in step 265 is satisfied, the CPU proceeds to step 266 in which the respective values of the non-operation time Tnop in the desired month, i.e., in all of the time units [a] to [b], calculated in above step 262 are totalized to obtain:
accumulated non-operation time Tu_nop in desired month=Σ T_nop [i]
Thereafter, in step 267, the respective values of the work lever operation time Tlever_ex_travel in the desired month (all of the time units [a] to [b]) calculated in above step 263 are totalized to obtain:
accumulated work lever operation time Tu_lever_ex_travel in desired month=Σ Tlever_ex_travel [i]
Then, in step 268, the respective values of the travel lever operation time Ttravel in the desired month (all of the time units [a] to [b]), which have already been extracted, are totalized to obtain:
accumulated travel lever operation time Tu_travel in desired month=Σ Ttravel [i]
Thereafter, in step 269, the respective values of the engine run time Teng in the desired month (all of the time units [a] to [b]), which have already been extracted, are totalized to obtain:
accumulated engine run time Tu_eng in desired month=Σ Teng [i]
Thereafter, in step 270, by using the accumulated non-operation time Tu_nop and the accumulated engine run time Tu_eng which have been obtained respectively in above steps 266 and 269, a non-operation time rate Tr_u_nop in the desired month is calculated from the following formula:
Tr—u—nop=(Tr—nop/Tr—eng)×100
Then, in step 271, by using the accumulated work lever operation time Tu_lever_ex_travel which has been obtained in above step 267, a work lever operation time rate Tr_u_lever_ex_travel in the desired month is calculated from the following formula:
Tr—u_lever—ex_travel=(Tu_lever—ex_travel/Tu—eng)×100
Thereafter, in step 272, by using the accumulated travel lever operation time Tu_travel which has been obtained in above step 268, a travel lever operation time rate Tr_u_travel in the desired month is calculated from the following formula:
Tr—u_travel=(Tu_travel/Tu—eng)×100
Then, the CPU proceeds to step 273 and determines, in accordance with a selection input from a separate means (not shown), whether the utilization data is to be indicated as real time display (described in detail later; see
In step 274, the accumulated non-operation time Tu nop (Non-Operation), the accumulated travel lever operation time Tu_travel (Travel), and the accumulated work lever operation time Tu_lever_ex_travel (Operation) in the desired month, which have been obtained respectively in above steps 266, 267 and 268, are displayed in the form of a bar graph. In addition, the respective values of the accumulated non-operation time Tu_nop, the accumulated travel lever operation time Tu_travel, and the accumulated work lever operation time Tu_lever_ex_travel are also displayed as numerals each representing the relevant real time, by way of example, inside the bar graph.
If the ratio display is selected in step 273, the CPU proceeds to step 275. In step 275, the non-operation time rate Tr_u_nop, the travel lever operation time rate Tr_u_travel, and the work lever operation time rate Tr_u_lever_ex_travel in the desired month, which have been obtained respectively in above steps 270, 271 and 272, are displayed in the form of a bar graph. In addition, the respective values of the accumulated non-operation time Tu_nop, the accumulated travel lever operation time Tu_travel, and the accumulated work lever operation time Tu_lever_ex_travel are also displayed as numerals representing ratios (percentages), which are taken by those respective values on an assumption of the accumulated engine run time Tu_eng being set to 100%, by way of example, inside the bar graph (see
In a graph illustrated in
Furthermore, the respective values (absolute amounts) of the accumulated travel lever operation time Tu_travel, the accumulated work lever operation time Tu_lever_ex_travel, and the accumulated non-operation time Tu_nop are also displayed as numerals in the corresponding specific item zones of each bar graph. As a result, it is possible to easily perform work management of the hydraulic excavator 1 in units of a month (or a week).
On the other hand,
In a graph illustrated in
In
Referring to
Then, in step 281, the CPU sets an operator i=a, which is used for counting the time unit data, followed by proceeding to step 282.
In step 282, by using both the engine run time Teng contained in each time unit data [i] and the lever operation (including travel) time Tlever obtained from the various operation times therein, a non-operation time Tnop in each time unit is calculated from the following formula:
non-operation time Tnop=engine run time Teng−lever operation time Tlever
Then, in step 283, by using the travel lever operation time Ttravel contained in each time unit data [i], a work lever operation time Tlever_ex_travel in each time unit is calculated from the following formula:
work lever operation time Tlever—ex_travel=lever operation time Tlever−travel lever operation time Ttravel
Thereafter, the CPU proceeds to step 284 in which the operator i is incremented by one, and it determines in step 285 whether i is larger than b. If this determination is not satisfied, the CPU returns to step 282 and repeats the same sequence of steps as that described above. As a result, respective values of the non-operation time Tnop and the travel lever operation time Ttravel in each time unit are obtained for all of the time unit data [a] to [b] in the desired month.
If the determination in step 285 is satisfied, the CPU proceeds to step 286 in which the respective values of the non-operation time Tnop in the desired month, i.e., in all of the time units [a] to [b], calculated in above step 282 are totalized to obtain:
accumulated non-operation time Tu_nop in desired month=Σ T—nop [i]
Thereafter, in step 287, the respective values of the work lever operation time Tlever_ex_travel in the desired month calculated in above step 283 are totalized to obtain:
accumulated work lever operation time Tu_lever_ex_travel in desired month=Σ Tlever_ex_travel [i]
Then, in step 288, the respective values of the travel lever operation time Ttravel in the desired month, which have already been extracted, are totalized to obtain:
accumulated travel lever operation time Tu_travel in desired month=Σ Ttravel [i]
Thereafter, in step 289, by using the accumulated non-operation time Tu_nop calculated in above step 286 and a target operation time per month (=operation budget, ×hours/month in an example described later with reference to
Tr—u—nop=(Tr—nop/operation budget)×100
Then, in step 290, by using the accumulated work lever operation time Tu_lever_ex_travel which has been obtained in above step 287, an actual-to-target work lever operation time rate Tr_u_lever_ex_travel in the desired month is calculated from the following formula:
Tr—u_lever—ex_travel=(Tu_lever—ex_travel/operation budget)×100
Thereafter, in step 291, by using the accumulated travel lever operation time Tu_travel which has been obtained in above step 288, an actual-to-target travel lever operation time rate Tr_u_travel in the desired month is calculated from the following formula:
Tr—u_travel=(Tu_travel/operation budget)×100
Then, the CPU proceeds to step 292 and determines, in accordance with a selection input from separate means (not shown), whether the utilization data is to be indicated as real time display (described in detail later; see
In step 294, the accumulated non-operation time Tu_nop (Non-Operation), the accumulated travel lever operation time Tu_travel (Travel), and the accumulated work lever operation time Tu_lever_ex_travel (Operation) in the desired month, which have been obtained respectively in above steps 286, 287 and 288, are displayed as specific component zones of one bar graph. In addition, the respective values of the accumulated non-operation time Tu_nop, the accumulated travel lever operation time Tu_travel, and the accumulated work lever operation time Tu_lever_ex_travel are also displayed as numerals each representing the relevant real time inside the specific component zones of the bar graph along with the respective values of the corresponding operation budges displayed as numerals each representing the relevant real time (see
If the ratio display is selected in step 292, the CPU proceeds to step 293. In step 293, the actual-to-target non-operation time rate Tr_u_nop, the actual-to-target travel lever operation time rate Tr_u_travel, and the actual-to-target work lever operation time rate Tr_u_lever_ex_travel in the desired month, which have been obtained respectively in above steps 289, 290 and 291, are displayed as specific component zones of one bar graph. In addition, their respective values are also displayed as numerals representing ratios (percentages), which are taken by those respective values on an assumption of the corresponding target operation time (operation budget) being set to 100%, by way of example, inside the bar graph (see
In a graph illustrated in
An operation budget setting button (which may be replaced by a tag) is disposed in an upper central portion of the area B of the screen at a position slightly offset to the left side. Upon the operation budget setting button being clicked, an operation budget (target operation time) setting list is displayed as an interrupt window, for example, as shown in the right side of
With such a screen layout, it is possible to recognize the operation status with respect to the target operation time (operation budget) and to facilitate production management.
On the other hand,
In a graph illustrated in
As in the screen image of
In
(2-7) Blowby Data and Fuel Consumption Rate Data
The “blowby data” file is displayed by processing engine blowby pressure data detected by the sensor 47b, which is contained in the operation data stored in the data storage area 4ea of the storage device in the user-side personal computer 4, into information indicating behaviors of the engine blowby pressure for a period spanning from several days to one month. Also, the “fuel consumption rate data” file is displayed by processing engine fuel consumption data detected by the sensor 47a, which is contained in the operation data stored in the data storage area 4ea of the storage device in the user-side personal computer 4, into information indicating behaviors of the fuel consumption for a period spanning from several days to one month.
Referring to
Thereafter, in step 301, respective values of the lever operation time Tlever of each time unit data [j] (j=1 to 24) are totalized to obtain a daily accumulated lever operation (including travel) time Tlever_day [k] from the following formula:
Tlever_day [k]=Σ Tlever [j]
Thereafter, in step 302, the average blowby pressure Pblowby [j] in each unit data [j] is multiplied by the number of samplings n[j] in each unit data [j], and the resulting values are totalized for all of the time units j=1 to 24. This total value is divided by the number of samplings Σ n[j] in all of the time units to obtain a daily average blowby pressure Pblowby_day from the following formula:
Pblowby_day [k]=Σ(Pblowby [j]×n[j])/Σ n[j]
Then, in step 303, the daily accumulated lever operation time Tlever_day and the daily average blowby pressure Pblowby_day, which have been calculated respectively in above steps 301 and 302, are plotted on a graph (in the case of displaying those data in the form of a list as well, the respective numerical values are displayed in the list).
Then, the CPU proceeds to step 304 in which the operator k indicating the date is incremented by one, and it determines in step 305 whether k is larger than a value representing the date of the time unit data [b]. If this determination is not satisfied, the CPU returns to step 300 and repeats the same sequence of steps as that described above. As a result, for a period spanning from the extracted time unit data [a (e.g., O/x/Δ (month/day/hour))] to the extracted time unit data [b (e.g., x/O/□ (month/day/hour))], the daily accumulated lever operation time Tlever_day and the daily average blowby pressure Pblowb_day are plotted on the graph.
If the determination in step 305 is satisfied, the processing flow is brought to an end.
In a graph illustrated in
Referring to
Thereafter, in step 311, respective values of the lever operation time Tlever of each time unit data [j] (j=1 to 24) are totalized to obtain a daily accumulated lever operation (including travel) time Tlever_day [k] from the following formula:
Tlever_day [k]=Σ Tlever [j]
Thereafter, in step 312, the average fuel consumption rate Qfuel [j] in each unit data [j] is multiplied by the number of samplings n[j] in each unit data [j], and the resulting values are totalized for all of the time units j=1 to 24. This total value is divided by the number of samplings Σ n[j] in all of the time units to obtain a daily average fuel consumption rate Qfuel_day from the following formula:
Qfuel_day [k]=Σ (Qfuel [j]×n[j])/Σ n[j]
Then, in step 313, the daily accumulated lever operation time Tlever_day and the daily average fuel consumption rate Qfuel_day, which have been calculated respectively in above steps 311 and 312, are plotted on a graph (in the case of displaying those data in the form of a list as well, the respective numerical values are displayed in the list).
Then, the CPU proceeds to step 314 in which the operator k indicating the date is incremented by one, and it determines in step 315 whether k is larger than a value representing the date of the time unit data [b]. If this determination is not satisfied, the CPU returns to step 310 and repeats the same sequence of steps as that described above. As a result, for a period spanning from the extracted time unit data [a (e.g., O/x/Δ (month/day/hour))] to the extracted time unit data [b (e.g., x/O/□ (month/day/hour))], the daily accumulated lever operation time Tlever_day and the daily average fuel consumption rate Qfuel_day are plotted on the graph.
If the determination in step 315 is satisfied, the processing flow is brought to an end.
In a graph illustrated in
In
(2-8) Event/Alarm and Other Data
The “event/alarm and other data” file is displayed by processing various event data detected by the sensors, such as engine on/off and key switch on/off, various alarm data, etc., which are contained in the operation data stored in the data storage area 4ea of the storage device in the user-side personal computer 4, into information indicating behaviors of the event/alarm and other data for a period spanning from several days to one month. The event data is grouped into an “event data” file, and the alarm and other data is grouped into an “alarm and fault data” folder. However, since those two kinds of data are processed in a similar manner, the following description is made below by regarding those two kinds of data together as the event/alarm and other data.
Referring to
Thereafter, the CPU sets in step 321 an operator i=a, which is used for counting the time unit data. In step 322, the CPU clears, to an initial value 0, a count value N1 representing the accumulated number of times at which the event number 1 has occurred, followed by proceeding to step 323.
In step 323, the CPU reads event data [i] of each unit data [i] and determines whether the event number 1 is turned on (in other words, whether the event of the event number 1 has occurred during the relevant unit time. If this determination is satisfied, the CPU proceeds to step 324 in which the count value N1 representing the accumulated number of times of occurrences is incremented by one, followed by proceeding to step 325. If the determination in step 323 is not satisfied, the CPU directly proceeds to step 325.
After incrementing the operator i by one in step 325, the CPU proceeds to step 326. In step 326, the CPU determines whether i is larger than b. If this determination is not satisfied, the CPU returns to step 323 and repeats the same sequence of steps as that described above. As a result, for the desired day (for a period of the time units [a] to [b]), how many times the event of the event number 1 has occurred (i.e., the accumulated number of times N1 of occurrences in the desired day) is calculated.
If the determination in step 326 is satisfied, the CPU proceeds to step 327. In step 327, the CPU determines whether the counted number of times N1 of occurrences is not smaller than 10. If this determination is satisfied, the CPU proceeds to step 329 in which a relevant box (i.e., a box corresponding to the desired day) is painted all over in a first color (for example, red representing an alarm color), followed by bringing this processing flow to an end. If that determination is not satisfied, the CPU proceeds to step 328 in which a relevant box (i.e., a box corresponding to the desired day) is painted all over in a second color (for example, yellow) and the accumulated number of times N1 of occurrences is put in the relevant box, followed by bringing this processing flow to an end.
Note that, while the above description has been made in a simplified way for easier understanding, the sequence of steps 320 to 328 or 329 is executed for each of a plurality of days. Also, while the above description has been made, by way of example, in connection with only the event of the event number 1, similar processing is executed for each event of another number.
As a result, for each event, the box corresponding to the day in which the event has occurred 10 or more times is painted red and the box corresponding to the day in which the event has occurred 9 or less times is painted yellow with the number of times of event occurrences displayed in the yellow box. For the day showing the number of times of event occurrences being zero, i.e., for the day in which the event has not occurred, the corresponding box may be left blank (see
In a graph illustrated in
Additionally, as in the several screen examples described above, a “month selection pull-down menu” in the form of a menu bar, a “+” button and a “−” button, which enable the operator to select year/month of the relevant data to be displayed, are disposed in an upper left portion of the area B of the screen. Further, the data period is displayed in an upper right portion of the area B, as indicated by “OO/□/x-Δ/□ (year/month/day)”. With such a screen layout, similar advantages to those described above can also be obtained.
Moreover, as in the several screen examples described above, two tags “Graph” and “Report” are selectably displayed in an upper left portion of the area B, thus enabling the operator to display data of the same contents in the form of a graph or a list including numerical values in a selectable manner (
Thought not specifically shown in
(2-9) Histogram Data
The “histogram data” file is displayed by processing the operation data, which is stored in the data storage area 4ea of the storage device in the user-side personal computer 4, into behavior transition information at intervals of a predetermined time (e.g., per day or per a predetermined engine run time).
Referring to
Then, for a region number n indicating a plurality of frequency regions (e.g., engine revolution speed regions of 0-600 rpm, 600-800 rpm, 800-1000 rpm, 1000-1200 rpm, 1200-1400 rpm, 1400-1600 rpm, 1600-1800 rpm, 1800-2000 rpm, 2000-2200 rpm, 2200-2400 rpm, 2400-2600 rpm, and 2600 rpm or over) which are set to look at a frequency distribution for a certain item A (e.g., engine revolution speed distribution, hydraulic oil temperature distribution, coolant temperature distribution, pump delivery pressure distribution, digging pressure distribution, or traveling pressure distribution), the CPU sets in step 341 the region number n=1 (corresponding to the region of 0-600 rpm in the above example).
Thereafter, the CPU sets in step 342 an operator i=a, which is used for counting the time unit data, followed by proceeding to step 343.
In step 343, from among the various frequency distribution data in each unit data [i], a value of time for the item A (e.g., the engine revolution speed) corresponding to each region (e.g., 0-600 rpm) indicated by the region number n is extracted and added to a preceding value (described later) to obtain an accumulated value.
After incrementing the operator i by one in step 344, the CPU proceeds to step 345. In step 345, the CPU determines whether i is larger than b. If this determination is not satisfied, the CPU returns to step 343 and repeats the same sequence of steps as that described above. As a result, for the desired day (for a period of the time units [a] to [b]), a total time for the item A (e.g., the engine revolution speed) corresponding to each region (e.g., 0-600 rpm) indicated by the region number n is calculated.
If the determination in step 345 is satisfied, the CPU increments the region number n by one in step 346, followed by proceeding to step 347.
In step 347, the CPU determines whether the region number n reaches the specified number of regions (12 in the example in which frequency regions are given as engine revolution speed regions of 0-600 rpm, 600-800 rpm, 800-1000 rpm, 1000-1200 rpm, 1200-1400 rpm, 1400-1600 rpm, 1600-1800 rpm, 1800-2000 rpm, 2000-2200 rpm, 2200-2400 rpm, 2400-2600 rpm, and 2600 rpm or over). If this determination is not satisfied, the CPU returns to step 342 and repeats the same sequence of steps as that described above. As a result, for the desired day (for a period of the time units [a] to [b]), a total time for the item A (e.g., the engine revolution speed) corresponding to each of the frequency distribution regions (e.g., 12 regions in this example) is calculated.
Thereafter, the CPU proceeds to step 348 in which the calculated results are displayed in the form of a bar graph sectioned into the frequency distribution regions and painted in different colors for each of the frequency distribution regions, followed by bringing this processing flow to an end.
While the description is simplified for easier understanding and is made in connection with, by way of example, only the item A, similar processing to that described above is executed for each of the other items and for each of plural time zones set at intervals of the processing time.
As a result, a plurality of bar graphs representing the respective items sectioned into the predetermined frequency distribution regions, which are painted in different colors from each other, are formed at intervals of the processing time.
In a graph illustrated in
In each of the bar graphs, the frequency distribution regions are arranged successively from the high revolution speed side to the low revolution speed side in the direction from above to below in different colors from each other (though not shown in detail, the colors are preferably selected so as to change from a warm color, e.g., red, toward a cold and dark color, while gradually becoming lighter and then conversely becoming darker via yellow and green, in the direction from above to below for the purpose of presenting a cautious color in the region of excessively high revolutions speeds and providing continuity from a visual point of view), thereby making up individual specific component zones of the bar graph. Further, in the bar graphs adjacent to each other in the left-to-right direction, boundary lines between the specific component zones of each bar graph are interconnected by transition lines so that the operator can recognize at a glance time-dependent transitions of the respective specific components (i.e., the frequency distribution regions).
In addition, under each bar graph, the predetermined accumulated time value (e.g., 200 hours, 300 hours, etc. representing the accumulated engine run time) corresponding to the bar graph data and the date (e.g., the start date, the end date, or the middle date of the data measurement) representing the corresponding data are displayed. This enables the operator to understand at a glance the region (engine revolution speed region in this example) in which the operation is performed at high frequency. Further, since the horizontal axis is graduated to intervals of the predetermined time, it is possible to easily read from which point in time the tendency has changed, and to increase the efficiency of troubleshooting. In particular, by selecting the predetermined time interval to 100 hours of the engine run time, resulting display of the data per 100 hours can be used for evaluation of machine components.
In a graph of
In a graph of
In a graph of
In a graph of
In a graph of
While the frequency distribution regions are displayed all in different colors in FIGS. 50 to 55, the present invention is not limited to the examples described above, and only the regions to be noted (e.g., the regions in excess of a certain threshold) may be colored. Such graphical display enables the operator to understand, for example, the occurrence of an abnormality with more ease. As an alternative, the frequency distribution regions may be displayed with only monochromatic gradations instead of coloring. Such monochromatic display enables the operator to more easily look at the data when printed out by a printer. Further, the histogram range may be adjustable, as required, to a width that is desired for viewing.
Additionally, as in the several screen examples described above, a “base period selection pull-down menu” in the form of a menu bar, a “+” button and a “−” button, which enables the operator to select a base period (hour meter value representing the accumulated engine run time in this example) for the relevant data to be displayed, are disposed in an upper left portion of the area B of the screen. The data period is displayed in an upper right portion of the area B, as indicated by “OO/□/x-Δ/□ (year/month/day)”. Further, as in the several screen examples described above, two tags “Graph” and “Report” are selectably displayed in an upper left portion of the area B, thus enabling the operator to display data of the same contents in the form of a graph or a list including numerical values in a selectable manner (FIGS. 50 to 55 each show the example displayed when the “Graph” tag is selected).
(3) Second Graph Selection Area C
As shown in
As described above in connection with the first graph selection area A, the “machine model name” box and the “machine number” box may be replaced, for example, by an “operation site name” box and a “specific machine name for custom management” box such that the box name is rewritable as required.
Additionally, the “book file name” box may be displayed, for example, in the forward or backward order of the dates each corresponding to file download date (or the range covered by the relevant data).
(4) Menu Button Area D
As shown in
For example, when the “Print” button is clicked, the data (or the whole of the book file) displayed on the screen at that time can be printed out by a printer in accordance with the printing program 133 (not described here in detail) stored in the program storage area 4ea in the user-side personal computer 4. When the “Preview” button is clicked, a print layout which will be printed out as it is upon clicking of the “Print” button can be displayed on the screen beforehand.
Further, when the “Send Mail” button serving as a sending instruction means is clicked, the data (or the whole of the book file) displayed on the screen at that time can be sent by E-mail (e.g., as an attached file) via the communication interface 4b (see
When the “Option” button is clicked, various kinds of settings incorporated as options in the operating program can be changed as required.
The screen image shown in
Further, though not shown, when an initialization file is installed, setting data can optionally be set and changed based on the file. Thus, the graph display method can easily be modified by preparing such an initialization file in advance. Moreover, in the case capable of designating the place where data is to be stored, the data storage place can optionally be changed (by using the storing program 132 stored in the program storage area 4ea in the user-side personal computer 4). Thus, the displayable contents can easily be changed by selecting a data group to be displayed. Additionally, in the case capable of switching over a manner of displaying the date and the time of day, it is possible to change the date and the time of day displayed on the graph to more convenient ones, for example, when the manner of displaying the date and the time of day differs depending on countries and/or districts.
(5) Status Display Area E
As indicated by “OOOOOO” in
(6) Menu Area F
As shown in
For example, when the “Send BookFile by E-Mail” button serving as a sending instruction means is clicked, the data (or the whole of the book file) displayed on the screen at that time can be sent by E-mail via the communication interface 4b (see
Also, when the “BookFile Properties” is clicked, properties of the relevant book file, such as download date and time, time-zone difference data, serial number, and name of the person having downloaded the book file, can be displayed (though not shown) in accordance with the file information displaying program 134 (not described here in detail) stored in the program storage area 4ea in the user-side personal computer 4. Display of the properties facilitates management of each book file.
When the “Go to” menu is clicked, two menus “Back” and “Forward”, and the names of the graphs opened at that time (three graphs in the illustrated example, i.e., life data graph of “YZOOO-103030”, life data graph of “YZOOO-103030”, and life data graph of “YZOOO-103030”) are displayed on the right side as shown. By clicking any one of those menus and names, the corresponding graphical screen image is displayed. In addition to the box for displaying the graphs opened at that time, an option menu “graphical representation (all)”, for example, may be disposed to provide the function of developing all of the registered graphs. In this case, all the graphs can be formed at a time.
The menu for various graphs displays the kinds of graphs, which are viewable for the machine model (“YZOO” in this example) currently selected on the screen. In this example, in addition to the “life data (Life)”, the following data are displayed, i.e., “operation daily data (Operation-Daily)”, “operation hours data (Operation-Hours)”, “operation ratio data (Operation-Ratio)”, “operation summary data (Operation-Summary)”, “alarm, etc. data_(Alarms_Faults-Alarms)”, “alarm, etc. data_(Alarms_Faults-Faults)”, “event data_(Events)”, “engine revolution speed histogram data (Histogram-Engine Speed)”, “hydraulic oil temperature histogram data (Histogram-Hydraulic Oil Temp)”, “coolant temperature histogram data (Histogram-Coolant Temp)”, “pump pressure histogram data (Histogram-Pump Press)”, “digging pressure histogram data (Histogram-Digging Press”, and “traveling pressure histogram data (Histogram-Traveling Press)”. Thus, since a list of graph items different for each machine model is displayed, the operator can recognize the kinds of viewable graphs at a glance. Additionally, the name of the relevant machine model name itself may be displayed in the display box of the menu for various graphs. This enables the operator to recognize at a glance to which machine model the displayed graph items belong.
(7) Others
Any other suitable operating means, e.g., buttons for actuating other functions convenient to users, can also be disposed in any appropriate place on the screen.
As described above, the operation data taken into the user-side personal computer 4 from the controller 2 is processed and displayed as information representing the operation situation of the relevant machine. On the other hand, as described above with reference to
Returning to
Though not shown, the main server 5 further comprises a ROM for storing control programs and a RAM for primarily storing data during the processing in order that the CPU 5c can execute the above-mentioned processing. Further, the ROM stores application programs that are equivalent to or the same as the data taking-in program 100 and the information displaying program 110 both installed in the device program storage area (ROM) 4ea in the user-side personal computer 4. With those programs, similar display screen images for all of the hydraulic excavators 1 to those displayed on the user-side personal computer 4 can be displayed on the display unit 5D in accordance with the operation of, for example, a keyboard 5B and a mouse 5C.
In
Based on not only the information created by the machine-body/operation data processing unit 50 and the product-exchange and part-repair/replacement data processing unit 51, but also the information stored and accumulated in the database 5A, the sales plan scheduling unit 53 confirms particular parts of plural hydraulic excavators 1 which have repair/replacement timings substantially coincident with each other, and decides the planned selling price of each of the confirmed particular parts depending on the number of those parts. Also, for the confirmed particular part, the sales plan scheduling unit 53 decides, as required, a discount sales (campaign) period prior to the repair/replacement timing and a discount selling price (campaign price) during the discount sales period. Then, the planned selling price, the discount sales period, the discount selling price, etc. are outputted to the intermediate server 6 as base information used by the dealers, etc. for promoting sales or services/sales to corresponding customers of the respective hydraulic excavators 1 (as described in detail later).
The processing functions of the machine-body/operation data processing unit 50 and the product-exchange and part-repair/replacement data processing unit 51 will be first described below with reference to flowcharts. The machine-body/operation data processing unit 50 of the main server 5 has the function of processing the operation time corresponding to the above-described function of collecting the operation time for each component section of the hydraulic excavator 1, which is executed by the machine-side controller 2. Also, the product exchange and part repair/replacement data processing unit 51 has the function of processing product exchange information and the function of processing part repair/replacement information.
In
In
Subsequently, the processing unit 51 accesses the database 5A, reads out the operation data for the machine number corresponding to the old hydraulic excavator, and stores the latest engine run time in the read operation data, as operation time until exchange of the hydraulic excavator (hereinafter also referred to as “exchange operation time”), in the database 5A (step 46).
Then, the processing unit 51 reads out the latest exchange operation time, computes distribution data of the number of the exchanged machines with respect to the operation time, and creates a distribution graph for the number of the exchanged machines based on the computed distribution data (step 47) (described later).
In
Subsequently, the processing unit 51 accesses the database 5A, reads out the operation data for the relevant machine model and number and computes a repair/replacement time interval of the part on the basis of the operation time of the component section to which the repaired or replaced part belongs, followed by storing and accumulating the computed time interval, as actual maintenance data, in the database 5A (step 54). Here, the term “part repair/replacement time interval” means a time interval from assembly of one part into the machine body to repair of the part or replacement of thereof by a new one upon the occurrence of a failure or the expiration of the life. The part repair/replacement time interval is computed on the basis of the operation time of the component section to which the relevant part belongs. In the case of a bucket prong, for example, the component section to which the bucket prong belongs is the front. If the front operation time (excavation time) from mounting of one bucket prong to the machine body to repair or replacement of the bucket prong upon breakage is 1500 hours, the repair/replacement time interval of the bucket prong is computed as 1500 hours.
Then, the processing unit 51 reads out the latest actual maintenance data, computes distribution data of the number of the repaired or replaced parts with respect to the operation time, and creates a distribution graph for the number of the repaired or replaced parts based on the computed distribution data (step 56) (described later).
In
The operation database per machine model and number stores therein, as accumulated values, the engine run time, the front operation time (hereinafter also referred to the “excavation time”, the swing time, and the travel time per machine model and number corresponding to the date. In the shown example, TNE(1) and TD(1) represent respectively an accumulated value of the engine run time and an accumulated value of the front operation time of the hydraulic excavator of the machine model A and No. N on Jan. 1, 2000. TNE(K) and TD(K) represent respectively an accumulated value of the engine run time and an accumulated value of the front operation time of the hydraulic excavator of the machine model A and No. N on Mar. 16, 2000. Likewise, accumulated values of TS(1) to TS(K) of the swing time and accumulated values of TT(1) to TT(K) of the travel time of the hydraulic excavator of the machine model A and No. N are also stored corresponding to the dates. Respective accumulated values for the hydraulic excavators of the machine model A and Nos. N+1, N+2, . . . , and of the machine models B, C, . . . are further stored in a similar manner.
The actual maintenance database per machine model and number stores therein the repair/replacement time interval of the part repaired or replaced in the past per machine model and number, as an accumulated value on the basis of the operation time of the component section to which the part belongs. In the shown example, TFB(1) and TFB(L) represent respectively accumulated values (e.g., 3400 hr and 12500 hr on the basis of the front operation time) of the first and L-th repair/replacement time intervals of the bucket prong in the hydraulic excavator of the machine model A and No. N. TTL(1) and TTL(M) represent respectively accumulated values (e.g., 5100 hr and 14900 hr on the basis of the travel time) of the first and M-th repair/replacement time intervals of a travel link in the hydraulic excavator of the machine No. N. Respective accumulated values for the hydraulic excavators of the machine model A and Nos. N+1, N+2, . . . , and of the machine models B, C, . . . are also stored in a similar manner.
The exchange database per machine model and number stores therein, as a value on the basis of the engine run time, the operation time of the old hydraulic excavator per machine model and number, which has been exchanged by the new one. In the shown example, TX(1) represents the operation time (e.g., 32000 hr on the basis of the engine run time) until the exchange of the hydraulic excavator of the machine model A and No. 1, and TX(L) represents the operation time (e.g., 30000 hr on the basis of the engine run time) until the exchange of the hydraulic excavator of the machine model A and No. L. Respective values for the hydraulic excavators of the machine models B, C, . . . are also stored in a similar manner.
In step 36 shown in
The expression “the operation time of the component section to which the part belongs” used in this embodiment means the operation time of the front operating mechanism 15 (i.e., the excavation time) when the component section to which the part belongs is the front operating mechanism 15, such as for the bucket, the bucket prong, and a front pin (e.g., a joint pin between the boom and the arm), means the swing time when the component section to which the part belongs is the swing body 13, such as for a swing wheel and the swing motor, and means the travel time when the component section to which the part belongs is the travel body 12, such as for the travel motor, the travel link and a travel roller. Also, it means the engine run time when the component section to which the part belongs is the engine 32, such as for engine oil and an engine oil filter. Further, when the component section to which the part belongs is a hydraulic source of the hydraulic system, such as for the working oil, a working oil filter, a main pump and a pilot pump, the engine run time is regarded as the operation time of the component section to which the part belongs. As an alternative, the operation time of the hydraulic source may be obtained by detecting an operation time during which the delivery pressure of the hydraulic pumps 21a, 21b exceeds a predetermined level, or by subtracting the non-load time from the engine run time.
In
Likewise, the number of hydraulic excavators having the engine run time in each range per 10000 hours is calculated for the machine models B, C, . . . (step 72). After the distribution data of the number of the currently working hydraulic excavators has been computed for each range of the engine run time in such a manner, a distribution graph of the number of the currently working hydraulic excavators is created through the processing executed in steps 38 and 40 shown in
In
ΔTLFB=TD(K)−TFB(M)
Subsequently, the processing unit 50 executes the above-described process for all the hydraulic excavators of the machine numbers Nos. 1 to Z and calculates the operation time (front operation time) ΔTLFB of the currently used bucket prong for each of all the hydraulic excavators of the model A.
Then, after dividing the front operation time ΔTLFB of each bucket prong into ranges per 500 hours, the processing unit 50 calculates the number of hydraulic excavators having the front operation time in each of the divided ranges. More specifically, it calculates the number of hydraulic excavators having the front operation time in each of the divided ranges of 0-500 hr, 501-1000 hr, 1001-1500 hr, 1501-2000 hr, and 2001 hr or more, thereby obtaining distribution data of the number of the currently working hydraulic excavators (step 85).
Similarly, for the travel link of each of the hydraulic excavators of the model A, the operation time (travel time) of each travel link is calculated, and distribution data of the number of currently working hydraulic excavators having the travel time in each range per 250 hours is obtained (step 86). Then, for each of the other parts, the operation time is calculated and distribution data of the number of currently working hydraulic excavators having the operation time in each predetermined range in a similar manner.
Likewise, the operation time is calculated for each of the parts of the hydraulic excavators of the models B, C, . . . and distribution data of the number of currently working hydraulic excavators having the operation time in each predetermined range (step 87).
After the distribution data of the operation time and the number of the currently working hydraulic excavators has been computed per machine model and part, a distribution graph of the number of the currently working hydraulic excavators is created through the processing executed in steps 38 and 40 shown in
In step 47 shown in
In
Also, in step 56 shown in
In
ΔTFB(i)=TFB(i)−TFB(i−1)
When the data collection of the repair/replacement time interval ΔTFB of the bucket prong is completed for all the hydraulic excavators, distribution data of the number of the repaired or replaced parts with respect to the repair/replacement time interval is computed from the collected data of the repair/replacement time interval, and a distribution graph of the number of the repaired or replaced parts is created based on the computed distribution data (step 106). The distribution data of the number of the repaired or replaced parts can be obtained in a similar manner to the above-described one used for computing the distribution data of the number of the currently working hydraulic excavators. For each of the other parts such as the travel link, distribution data of the number of the repaired or replaced parts is computed and a corresponding distribution graph is created in a similar manner (step 108). Likewise, for the hydraulic excavators of the models B, C, . . . , respective distribution data of the number of the repaired or replaced parts are computed and respective distribution graphs are created (step 110). The created distribution graphs representing the number of the repaired or replaced parts are then outputted to the display unit 5D (or the intra-company computer) (step 114).
Here, one of major features of this embodiment resides in that, by referring to the distribution graph of the number of the hydraulic excavators with respect to the operation time per hydraulic excavator, the distribution graph of the number of the hydraulic excavators with respect to the operation time per part, the distribution graph of the number of the exchanged hydraulic excavators with respect to the operation time per hydraulic excavator, and the distribution graph of the number of the repaired or displaced parts with respect to the operation time per component section, which have been created by the machine-body/operation data processing unit 50 and the product-exchange and part-repair/replacement data processing unit 51, the sales plan scheduling unit 53 predicts the number of parts belonging to, e.g., the front operating mechanism and the travel body (i.e., makes demand prediction), which are to be repaired or replaced if the current situation will continue as it is, and then decides a sales plan for a particular part of the hydraulic excavator based on the demand prediction.
In
(A) Prediction of Number of Parts
(1) The sales plan scheduling unit 53 assumes an average operation time until repair or replacement of the part. The average operation time is given as a value on the basis of the operation time of the component section to which the relevant part belongs.
Taking the bucket prong as an example, the average operation time is assumed to be, e.g., 1000 hours on the basis of the front operation time.
(2) The number of the hydraulic excavators exceeding the average operation time is calculated from the distribution graph representing the number of the currently working hydraulic excavators with respect to the operation time for the relevant part.
For example, in the case of assuming the average operation time of the bucket prong to be 1000 hours on the basis of the front operation time as mentioned above, the number of the hydraulic excavators having the front operation time (excavation time) exceeding the average operation time is 2800 in total from the distribution graph shown in
(3) From the number of the hydraulic excavators exceeding the average operation time, the sales plan scheduling unit 53 estimates the number of the hydraulic excavators having the parts which will be actually repaired or replaced in near future (e.g., in the next term) if the current situation will continue as it is.
For example, in the case shown in
(4) The estimated number of the relevant hydraulic excavators is multiplied by the number of the parts per hydraulic excavator to predict the number of the parts to be repaired or replaced in the near future.
For example, when it is estimated that the number of the hydraulic excavators in which the bucket prongs will be repaired or replaced is 2520, the number (demand) of the bucket prongs which will require to be repaired or replaced in near future (e.g., in the next term) is predicted to be 10080 because the number of the bucket prongs per hydraulic excavator is four.
Likewise, for each of the other types of parts B, C, D, . . . , the number of the parts which will be actually repaired or replaced is predicted successively (step 121). In the case of the travel link, for example, by assuming the average operation time until the travel ink until repair or replacement of the travel link on the basis of travel time to be 500 hours, the number of the travel links which will require to be repaired or replaced in near future (e.g., in the next term) can be predicted in a similar manner from the distribution graph shown in
(B) More Exact Prediction of Number of Parts
In this embodiment, as described above, the main server 5 reads out the actual maintenance data (part repair/replacement data) and the operation data both shown in
Stated another way, in above (A), the average operation time until repair or replacement of the bucket prong is assumed to be 1000 hours, by way of example, on the basis of the front operation time in the above-mentioned step (1). Therefore, the accuracy in predicting the number of the bucket prongs to be repaired or replaced is determined depending on how the assumed operation time is appropriate.
In this embodiment, since the distribution graph of the actual number of the repaired or replaced bucket prongs is obtained as shown in
Thus, the demand for the number of parts to be repaired or replaced in the hydraulic excavators 1 for each type of the parts is predicted in the manner described in above (A) or (B). On that occasion, the number of the hydraulic excavators 1, which will require to be exchanged if the current situation continues as it is, may be additionally predicted as related reference information. This prediction is carried out, for example, as follows.
(C) Prediction of Number of Hydraulic Excavators
(1) The sales plan scheduling unit 53 assumes an average operation time until exchange of the hydraulic excavator. The average operation time is given as a value on the basis of the engine run time.
The average operation time is assumed to be, e.g., 20000 hours on the basis of the engine run time.
(2) The number of the hydraulic excavators exceeding the average operation time is calculated from the distribution graph representing the number of the currently working hydraulic excavators.
For example, in the case of assuming the average operation time to be 20000 hours as mentioned above, the number of the hydraulic excavators having the operation time exceeding the average operation time is 2800 in total from the distribution graph shown in
(3) From the number of the hydraulic excavators exceeding the average operation time, the sales plan scheduling unit 53 estimates the number of the hydraulic excavators which will be exchanged in near future (e.g., in the next term) if the current situation will continue as it is (particularly if a particular part will not be repaired or replaced for the purpose of prolonging the life).
For example, in the case shown in
(D) More Exact Prediction of Number of Hydraulic Excavators
In this embodiment, as described above, the main server 5 reads out the exchange data and the operation data of the hydraulic excavators both shown in
Stated another way, in above (C), the average operation time until exchange of the hydraulic excavator is assumed to be 20000 hours, by way of example, in the above-mentioned step (1). Therefore, the accuracy in predicting the number of the hydraulic excavators to be exchanged is determined depending on how the assumed operation time is appropriate.
In this embodiment, since the distribution graph of the actual number of the exchanged hydraulic excavators is obtained as shown in
After predicting the number of parts to be repaired or replaced for each type of the parts in the manner described in above (A) to (D), the processing flow proceeds to step 122.
In step 122, the planned selling price of the part A is decided based on the demand prediction (sales prospect prediction) in step 120. When deciding the planned selling price, the efficiency of productivity, distribution, etc. can be increased by supplying, solely from the maker side, the parts A for all of the hydraulic excavators 1 in which the parts A are to be repaired or replaced. As a result, the planned selling price can be set to a value relatively lower than the ordinary selling price, and it can be more reduced as the number of the relevant hydraulic excavators 1 increases.
Likewise, for each of the other parts B, C, D, . . . , the number of parts to be repaired or replaced is predicted and the ordinary selling price is decided one by one (step 123).
After deciding the selling price for each type of the parts in above steps 122 and 123, the processing flow proceeds to step 124 in which a part sales list is prepared for each customer.
As shown in
In the above-described case represented by
Returning to
As shown in
Returning to
In the embodiment described above, the average operation time until repair or replacement per component section, for example, is assumed (in consideration of the actual performance in the past as required). Then, based on the assumed average operation time, the number of the parts to be repaired or replaced is predicted and the sales plan is scheduled. Depending on the situation, e.g., in the case of intending to promote sales, however, a sales campaign may be scheduled by the sales plan scheduling unit 53 so as to sell the parts at a cheaper special price than the planned selling price, for example, when the customers purchases the parts earlier than the ordinary repair or replacement timing.
In
After the completion of step 123, the processing flow proceeds to step 127. In this step 127, a potential demand (earlier demand), i.e., a demand for the parts that the customers will probably purchase depending on conditions though before reaching the ordinary timing of repair or replacement, is predicted instead of the ordinary demand prediction for the timing of repair or replacement, which is executed in above steps 120 and 121.
More specifically, in the case of the bucket prongs shown in
Likewise, a potential demand for each of the other types of parts B, C, D, . . . is predicted successively (step 128).
After predicting the potential part demand for each type of the parts in such a manner, the processing flow proceeds to step 129.
In step 129, the campaign price (discount selling price) and the campaign period (discount sales period) for the part A are decided based on the potential demand prediction (sales prospect prediction) made in above step 127. More specifically, how much discount is proper (e.g., 3%-off, 5%-off or 10%-off) and at which timing the campaign period is to take place are decided in step 129 from a comprehensive viewpoint depending the magnitude of the potential demand, taking into account both a decrease of profit resulting from discount selling of the part A to be repaired or replaced and an increase of profit on the customer side resulting from earlier purchasing of the part A. In addition, the point regarding whether a merit is resulted from the campaign may also be taken into consideration. If it is determined that the potential demand will not be so prospected even with the campaign at a certain discount selling price, the campaign for the part A may be itself put off.
Likewise, for each of the other parts B, C, D, . . . , the campaign price (discount selling price) and the campaign period (discount sales period) are decided one by one (step 130).
After deciding the campaign price (discount selling price) for each type of the parts in above steps 129 and 130, the processing flow proceeds to step 124, which is similar to step 124 in the processing flow shown in
As shown in
In the example shown in
Returning to
The above-described campaign is one prompting the customer to purchase the part somewhat earlier timing than the ordinary repair/replacement timing, but the campaign is not limited to the above-described one. More specifically, in above (A)(3) regarding the bucket prongs, for example, on an assumption that, among 2800 hydraulic excavators 1 having the front operation time in excess of the average operation time of 1000 hours, the number of those ones in which the bucket prongs will be continuously used in the next term without being repaired or replaced is about 10%, the number of the hydraulic excavators in which repair/replacement of the bucket prongs will be actually demanded is estimated to be 2520. For the purpose of eliminating or minimizing 10% hydraulic excavators for which the bucket prongs have been estimated to be neither repaired nor replaced (i.e., aiming repair or replacement of all or almost all of the relevant hydraulic excavators 1), a campaign may be carried out with the intention of requesting all the customers to purchase the relevant hydraulic excavators at the ordinary repair/replacement timing without exceptions. In this case, the campaign period is substantially matched with the ordinary repair/replacement timing (scheduled timing).
Returning to
The input/output interface 6a receives, from the main server 5, not only the planned selling price (including the campaign price (discount selling price), the campaign period (discount sales period), etc.), which have been decided by the main server 5 for the particular parts of the hydraulic excavators 1, but also the prepared part sales list per dealer, etc. The input/output interface 6a further receives the above-described operation data and machine body data themselves, which are in state not yet processed, from the main server 5.
The CPU 6c stores and accumulates those input data in the database 6A in the storage 6d, prepares an advice note for part sales, as information presented to each customer, based on the part sales list per dealer, etc., and transmits the advice note to the user-side personal computer 4 of each customer via the input/output interface 5b by E-mail, for example, (alternatively the user-side personal computer 4 may access the homepage set up in the intermediate server 6 (such as the homepage of the dealer, etc.) and may download the advice note with operation made on the side of the user-side personal computer 4). The CPU 6c also has the function of transmitting the above-described operation data and machine body data themselves, which are in state not yet processed (alternatively, as in the above case, the user-side personal computer 4 may access the homepage set up in the intermediate server 6 and download the data regarding the hydraulic excavator owned by the user). On that occasion, a template and a form for displaying the operation data and the machine body data along with an explanation expressed in user's own language may be provided in, e.g., the homepage of the dealer, etc., and the operation data and the machine body data from the main server 5 may be provided to the user-side personal computer 4 through some processing, such as insetting of those data into the template, etc., instead of being in state not yet processed. As an alternative, it is also possible to translate only language parts, which are contained in the operation data and the machine body data from the main server 5, by the intermediate server 6 and to present the translated text to the user-side personal computer 4.
For causing the CPU 6c to execute the processing described above, though not shown, the intermediate server 6 further comprises a ROM storing control programs and a RAM serving as memory means for primarily storing data produced during the processing. As in the main server 5, the ROM stores application programs that are equivalent to or the same as the data taking-in program 100 and the information displaying program 110. With those programs, similar display screen images for those of all the hydraulic excavators 1, which are directly or indirectly serviced or sold by the relevant dealer, etc., to those displayed on the user-side personal computer 4 can be displayed on a display unit 6D in accordance with the operation of, for example, the keyboard 6B and the mouse 6C.
Whether to send the above-mentioned advice note to the customer or not is basically totally left at the discretion of the dealer, etc. In spite of the part sales list per dealer, etc. being transmitted from the main server as described above, the dealer, etc. may take actions of not notifying the customer of such information given from the manufacturer side and supplying parts through another part supply route uniquely developed, for example, when the dealer, etc. make a judgment by themselves that those actions not complying with the information contained in the part sales list are benefit for the customer (because of enabling the part to be supplied at a lower cost) or advantageous for the dealer, etc. from the viewpoint of business, taking into consideration situations and environments (such as natural environment, economical environment, legal environment, cultural background, and labor environment) specific to the local area or the customer. It is also optional to send the advice note to some of the customers, but not to send it to the other customers.
On the other hand, as described above, the CPU 6c transmits, to the user-side personal computer 4, the operation data and machine body data themselves, which are obtained from the main server 5 and are in state not yet processed. Responsively, the user-side personal computer 4 can display, on the display unit 4D, not only the advice note transmitted from the intermediate server 6, but also the above-described display screen images (see FIGS. 9 to 60) for the corresponding hydraulic excavator(s) 1 (not limited to one, and when a plurality of hydraulic excavators are owned or used, the screen images for all of them are displayed). By looking at the various screen images displayed on the display unit 4D, the customer (such as the user) ask the dealer, etc., as required, for explanation and analysis regarding the contents of the displayed information, the display form, etc. Correspondingly, the dealer, etc. go to the customer side to make explanation and analysis in response to questions, demands, etc. from the customer side.
The one embodiment of the present invention described above can provide advantageous effects given below.
1) Effect Resulting from Leaving Details of Services and Sales to Dealer Side
In the one embodiment of the present invention described above, data regarding the machine operations of all the hydraulic excavators 1 is taken in by the main server 5 installed on the manufacturer side via information communication and then stored in the database 5A. At the time, the data is also outputted, as basic information for services and sales, to the intermediate server 6 on the side of the dealer, etc. Based on that basic information for services and sales, the dealer, etc. in charge of services and sales can make a judgment by themselves and take the above-mentioned actions depending on situations and demands of the customer (such as the user) with whom the dealer, etc. usually keep direct contact. For example, the dealer, etc. set up a homepage so that the customer can access the homepage of the dealer, etc., download the relevant data into the user-side personal computer 4 by clicking a download button on a predetermined screen, and display the downloaded data, as final service/sales information, in a predetermined form on the user-side personal computer 4. Also, regarding the contents, the display form, etc. of the service/sales information finally displayed on the user-side personal computer 4, the dealer, etc. go to the customer side to make explanation and analysis, as required, in response to questions, demands, etc. from the customer side. In addition, the dealer, etc., can select or restrict users to which the data is to be transmitted, and can actuate a lock or disable display of a downloading screen itself for some users so that they cannot download any data.
Thus, the functions required on the side of the main server 5 (i.e., on the manufacturer side) are restricted to those ones of receiving and collecting data from a large number of hydraulic excavators 1 and distributing the data, while a judgment made based on the distributed data regarding, e.g., what kinds of services and sales should be finally presented to the customer (user), is left to the side of the intermediate server 6 (i.e., the side of the dealer, etc.) taking charge of services and sales in the closest relation to the customer. As a result, unlike the prior art in which all operations ranging from data reception to services and sales are managed at one place in a centralized manner, more appropriate and satisfactory service/sales information can be presented to the customer side with careful consideration.
2) Reduction of Repair/Replacement Cost with Scale Merit
In the one embodiment of the present invention, as described above, data regarding the operation per component section in many hydraulic excavators 1 is taken in by the main server 5 installed on the manufacturer side via information communication and then stored in the database 5A. Further, the part repair/replacement timing is computed for each of the hydraulic excavators 1. Such processing is executed for all of the hydraulic excavators 1, and the parts having the repair/replacement timings substantially matched with each other are extracted and confirmed from among the many hydraulic excavators 1.
Then, on the premise that the relevant parts are collectively repaired or replaced in almost all or a certain percentage of the thus-extracted hydraulic excavators 1 (i.e., collective repair or replacement of the relevant parts increases productivity, distribution efficiency, etc. and hence greatly reduces the repair/replacement cost estimated for each hydraulic excavator 1), the planned selling price of the relevant part is decided while reflecting a cost reduction depending on the number of the parts to be repaired or replaced, and then outputted as the basic information for services and sales to the side of the intermediate server 6. Further, the intermediate server 6 processes the basic information for services and sales, as appropriate, into the final service/sales information that is displayed on the user-side personal computer 4 in a predetermined form, for example, in the form of the advice note shown in
Thus, by advantageously utilizing a scale merit resulting from the capability of predicting the part repair/replacement timings of the many hydraulic excavators 1 and by performing repair or replacement of a particular part for the many hydraulic excavators in a collective manner, it is possible to improve productivity, distribution efficiency, etc., and to greatly reduce the repair/replacement cost estimated for each hydraulic excavator 1. Consequently, a burden imposed on the customer side can be noticeably reduced.
3) Effect with Campaign
In the one embodiment of the present invention, as described above, in addition to the ordinary selling price, the discount sales (campaign) period prior to the ordinary repair/replacement timing and the discount selling price (campaign price) during the discount sales period are decided for a particular part, and such data is also outputted, as the basic information for services and sales, to the side of the intermediate server 6. Further, the intermediate server 6 processes the basic information for services and sales, as appropriate, into the final service/sales information that is displayed on the user-side personal computer 4 in a predetermined form, for example, in the form of the advice note shown in
Additionally, in the one embodiment of the present invention described above, a practical method has not been particularly described which is executed when the potential demand is predicted in steps 127-128 after the end of step 123 in
Referring to
Recently, on the user side, there have increased needs for more effectively employing the currently owned old construction machines for a longer period through repair/replacement of parts instead of trading those old machines in for new ones successively. With those needs in mind, if an action for prolonging the machine life is taken, for example, by repairing or replacing all together a plurality of particular parts belonging particular equipment (such as an engine, a hydraulic pump, and control valves) which are effective in prolonging the life of the overall machine, an ascent of the machine management cost curve (a) is moderated and slides toward the longer life side (i.e., the lower cost side), while a descent of the machine value curve (b) is moderated and slides toward the longer life side (i.e., the higher value side).
More specifically, by repairing or replacing the plurality of parts all together at the timing TB, the machine management cost increases once by ΔS1 (see
Also, with the effect resulting from repairing or replacing the plurality of parts all together at the timing TB , the slope of the rightward ascending machine value curve (b′) becomes larger than that of the original machine value curve (b). Therefore, the machine value curve (b′) extends above the original machine value curve (b) and, as described above, it slides toward the longer life side (i.e., the higher value side) than the original curve (b′).
The above-mentioned sliding of the curves (a′), (b′) shifts a timing TA′ corresponding to a cross point A′ between the machine management cost curve (a′) and the machine value curve (b′) to the right on the graph by a period ΔT (see
On the other hand, in the case (see a point C) of disposing of the old hydraulic excavator by sale (i.e., trade-in) at the timing TA (=timing corresponding to the cross point A between the original machine management cost curve (a) and the original machine value curve (b)) defined in the case of not performing repair/replacement, the following cost merit can be obtained. When the old hydraulic excavator is disposed of by sale at the timing TA, the machine value is increased by ΔS2 as a result of the above-mentioned sliding from the curve (b) to (b′), and this increase of the machine value becomes a profit on the user side. Also, an increase ΔS3 of the repair/replacement cost, which should have been paid during a period from the part repair/replacement timing TB to the timing TA in the case of not performing the repair/replacement, is reduced to an (initial) investment cost S1 paid at the part repair/replacement timing TB. Therefore, the difference of ΔS3−ΔS1 also becomes a profit on the user side. Consequently, the user side can obtain a cost merit of ΔS2+ΔS3−ΔS1 in total by repairing or replacing the particular parts at the timing TB.
The sales plan scheduling unit 53 prepares a graphic curve, such as shown in
In such a manner, the potential demand is predicted for one customer a. Then, the potential demand is similarly predicted for each of the other customers b, c, d, . . . in turn (step 128′).
After predicting the potential demand for the part per customer as described above, the processing flow proceeds to step 129′.
In step 129′, based on the potential demand prediction (sales prospect prediction) executed in above step 127′, the campaign price (discount selling price) and the campaign period (discount sales period) are decided for a plurality of particular parts (e.g., parts D, E and F, see
Likewise, for each of the other customers b, c, d, . . . , the campaign price (discount selling price) and the campaign period (discount sales period) (including whether the campaign is to be performed or not) are decided one by one (step 130′).
After deciding the campaign price (discount selling price) for each of the customers in above steps 129′ and 130′, the processing flow proceeds to step 124 (subsequent steps 124-126 are substantially similar to corresponding steps in
As shown in
In the above-described case represented by
Also, in the example shown in
Returning to
As shown in
Returning to
Correspondingly, in this modification, the input/output interface 6a of each intermediate server 6 receives, from the main server 5, not only the part sales list per dealer, etc., including the planned selling price, the campaign price (discount selling price), the campaign period (discount sales period), etc., which have been decided by the main server 5 for the particular parts of the hydraulic excavators 1 as described above, but also the price change information regarding the customers as campaign targets.
The CPU 6c prepares an advice note for part sales, as service/sales information presented to each customer, based on the part sales list per dealer, etc. and the price change information, and transmits the advice note to the user-side personal computer 4 of each customer via the input/output interface 5b by E-mail, for example.
As in the one embodiment of the present invention described above, whether to send the above-mentioned advice note to the customer or not is basically totally left at the discretion of the dealer, etc. In spite of the part sales list per dealer, etc. and the price change information being both transmitted from the main server as described above, the dealer, etc. may take actions of not notifying the customer of such information given from the manufacturer side and supplying parts through, e.g., another part supply route uniquely developed. It is also optional to send the advice note to some of the customers, but not to send it to the other customers. Alternatively, if there is a reliance relationship between the customer and the dealer, etc., the list sent from the main server (e.g., the data shown in
With the above-mentioned modification, the following effect can be obtained in addition to the effects obtained with the one embodiment of the present invention.
In the modification, as described above, in response to the recent user's needs for the longer life of the hydraulic excavator, changes of the machine management cost curve (a′) and the machine value curve (b′), i.e., sliding of the curves toward the longer life side, which are resulted in the case of repairing or replacing the particular parts at the timing TB before the timing TA corresponding to the cross point A between the machine management cost curve (a) and the machine value curve (b), are outputted as the basic information for services and sales to the intermediate server 5, and then displayed, as the final service/sales information, on the user-side personal computer 4 in the form in which the price change information is contained in the advice note.
Thus, since the user side can obtain the information indicating the sliding of the curve from (a) to (a′) and the sliding of the curve from (b) to (b′) which occur upon the repair/replacement of the part, it is possible to properly determine at the user's own discretion as to, for example, when and how the part is to be repaired or replaced, and how long the machine life can be extended. As a result, the machine possessed by the user can be effectively utilized at a sufficiently satisfied level.
In the above description, when the number of machines and the number of parts each having the operation state (operation time) in excess of the reference value (average operation time) are calculated, a responsible worker performs the calculation and setting of the reference value by outputting the distribution graphs such as shown in
Further, the above-described steps of creating and transmitting the distribution data and the distribution graphs representing the number of currently working hydraulic excavators with respect to the operation time thereof may be modified such that the step of creating the distribution data is automatically executed by the main server 5, while the steps of creating and transmitting the distribution graphs are executed in accordance with instructions entered by, e.g., a person responsible for the sales plan scheduling through the keyboard 5B (or the intracompany computer).
Also, in the above-described embodiment, the distribution data and the distribution graphs representing the number of exchanged products with respect to the operation time of the old hydraulic excavators that have been exchanged by new ones, and the distribution data and the distribution graphs representing the number of repaired or replaced parts with respect to the operation time are executed each time when the product exchange data and the part repair/replacement data are inputted. However, those steps may be executed at any other suitable timing, e.g., at an appropriate intermittent timing through batch processing.
While the above embodiment has been described in connection with, e.g., a hydraulic excavator as one example of construction machines, the present invention is not limited to the hydraulic excavator, but is also applicable other types of construction machines, such as a crawler crane and a wheel loader. These cases can also provide similar effects to those obtained with the above embodiment.
Moreover, applications of the present invention are not limited to construction machines, and the present invention is further applicable to general digging and loading machines working in mine sites (such as a scraper, a rock drill (drill machine), and large-sized hydraulic excavators, wheel loaders, motor graders, etc. employed in mines). These cases can also provide similar effects to those obtained with the above embodiment.
According to the present invention, the functions required on the manufacture side are restricted to those ones of receiving and collecting data from a large number of hydraulic excavators and distributing the data, while a judgment made based on the distributed data regarding, e.g., what kinds of services and sales should be finally presented to the customer, is left to the side of the dealer, etc. taking charge of services and sales in the closest relation to the customer. As a result, unlike the prior art in which all operations ranging from data reception to services are managed at one place in a centralized manner, sufficiently satisfied and proper care can be given to the customer side with careful consideration.
| Number | Date | Country | Kind |
|---|---|---|---|
| 2002-171132 | Jun 2002 | JP | national |
| 2002-171167 | Jun 2002 | JP | national |
| 2002-203522 | Jul 2002 | JP | national |
| Filing Document | Filing Date | Country | Kind |
|---|---|---|---|
| PCT/JP03/07325 | 6/10/2003 | WO |
