EP1262604B1 - Verfahren und system zur verwaltung einer baumaschine und arithmetische verarbeitungseinheit - Google Patents

Verfahren und system zur verwaltung einer baumaschine und arithmetische verarbeitungseinheit Download PDF

Info

Publication number
EP1262604B1
EP1262604B1 EP01921782A EP01921782A EP1262604B1 EP 1262604 B1 EP1262604 B1 EP 1262604B1 EP 01921782 A EP01921782 A EP 01921782A EP 01921782 A EP01921782 A EP 01921782A EP 1262604 B1 EP1262604 B1 EP 1262604B1
Authority
EP
European Patent Office
Prior art keywords
construction machine
machine
data
load
index
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Expired - Lifetime
Application number
EP01921782A
Other languages
English (en)
French (fr)
Other versions
EP1262604A1 (de
EP1262604A4 (de
Inventor
Hiroshi Watanabe
Koichi Shibata
Hiroyuki Adachi
Toichi Hirata
Genroku Sugiyama
Hideki Komatsu
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Hitachi Construction Machinery Co Ltd
Original Assignee
Hitachi Construction Machinery Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Hitachi Construction Machinery Co Ltd filed Critical Hitachi Construction Machinery Co Ltd
Publication of EP1262604A1 publication Critical patent/EP1262604A1/de
Publication of EP1262604A4 publication Critical patent/EP1262604A4/de
Application granted granted Critical
Publication of EP1262604B1 publication Critical patent/EP1262604B1/de
Anticipated expiration legal-status Critical
Expired - Lifetime legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Information and communication technology [ICT] specially adapted for implementation of business processes of specific business sectors, e.g. utilities or tourism
    • G06Q50/08—Construction
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00—Registering or indicating the working of vehicles
    • G07C5/008—Registering or indicating the working of vehicles communicating information to a remotely located station
    • E—FIXED CONSTRUCTIONS
    • E02—HYDRAULIC ENGINEERING; FOUNDATIONS; SOIL SHIFTING
    • E02F—DREDGING; SOIL-SHIFTING
    • E02F9/00—Component parts of dredgers or soil-shifting machines, not restricted to one of the kinds covered by groups E02F3/00 - E02F7/00
    • E02F9/20—Drives; Control devices
    • E02F9/2025—Particular purposes of control systems not otherwise provided for
    • E02F9/2054—Fleet management
    • E—FIXED CONSTRUCTIONS
    • E02—HYDRAULIC ENGINEERING; FOUNDATIONS; SOIL SHIFTING
    • E02F—DREDGING; SOIL-SHIFTING
    • E02F9/00—Component parts of dredgers or soil-shifting machines, not restricted to one of the kinds covered by groups E02F3/00 - E02F7/00
    • E02F9/20—Drives; Control devices
    • E02F9/22—Hydraulic or pneumatic drives
    • E—FIXED CONSTRUCTIONS
    • E02—HYDRAULIC ENGINEERING; FOUNDATIONS; SOIL SHIFTING
    • E02F—DREDGING; SOIL-SHIFTING
    • E02F9/00—Component parts of dredgers or soil-shifting machines, not restricted to one of the kinds covered by groups E02F3/00 - E02F7/00
    • E02F9/20—Drives; Control devices
    • E02F9/22—Hydraulic or pneumatic drives
    • E02F9/2278—Hydraulic circuits
    • E02F9/2292—Systems with two or more pumps
    • E—FIXED CONSTRUCTIONS
    • E02—HYDRAULIC ENGINEERING; FOUNDATIONS; SOIL SHIFTING
    • E02F—DREDGING; SOIL-SHIFTING
    • E02F9/00—Component parts of dredgers or soil-shifting machines, not restricted to one of the kinds covered by groups E02F3/00 - E02F7/00
    • E02F9/20—Drives; Control devices
    • E02F9/22—Hydraulic or pneumatic drives
    • E02F9/2278—Hydraulic circuits
    • E02F9/2296—Systems with a variable displacement pump
    • E—FIXED CONSTRUCTIONS
    • E02—HYDRAULIC ENGINEERING; FOUNDATIONS; SOIL SHIFTING
    • E02F—DREDGING; SOIL-SHIFTING
    • E02F9/00—Component parts of dredgers or soil-shifting machines, not restricted to one of the kinds covered by groups E02F3/00 - E02F7/00
    • E02F9/26—Indicating devices
    • E—FIXED CONSTRUCTIONS
    • E02—HYDRAULIC ENGINEERING; FOUNDATIONS; SOIL SHIFTING
    • E02F—DREDGING; SOIL-SHIFTING
    • E02F9/00—Component parts of dredgers or soil-shifting machines, not restricted to one of the kinds covered by groups E02F3/00 - E02F7/00
    • E02F9/26—Indicating devices
    • E02F9/267—Diagnosing or detecting failure of vehicles
    • G—PHYSICS
    • G07—CHECKING-DEVICES
    • G07C—TIME OR ATTENDANCE REGISTERS; REGISTERING OR INDICATING THE WORKING OF MACHINES; GENERATING RANDOM NUMBERS; VOTING OR LOTTERY APPARATUS; ARRANGEMENTS, SYSTEMS OR APPARATUS FOR CHECKING NOT PROVIDED FOR ELSEWHERE
    • G07C5/00—Registering or indicating the working of vehicles
    • G07C5/08—Registering or indicating performance data other than driving, working, idle, or waiting time, with or without registering driving, working, idle or waiting time
    • G07C5/0841—Registering performance data
    • G07C5/085—Registering performance data using electronic data carriers

Definitions

  • the present invention relates to a method and system for managing a construction machine, with which whether the model used by a customer is an optimum one can be evaluated for a construction machine, such as a hydraulic excavator, having a plurality of sections operated for different periods of time, e.g., a front operating device section, a swing section and a track or travel section.
  • a construction machine such as a hydraulic excavator, having a plurality of sections operated for different periods of time, e.g., a front operating device section, a swing section and a track or travel section.
  • US-A-5 737 215 discloses a method and an apparatus for managing a construction machine by comparing one machine in a fleet of such machines.
  • the operation status for sections of a plurality of these machines of different models will be measured, and the measured operation status data will be transferred to and stored in a base computer.
  • Said base computer is provided for statistically processing and outputting said accumulated operation data.
  • the fleet manager determines, on the basis of the accumulated operation data, a recommended cource of action, for example, onboard faults, needed repairs, maintenance schedule, etc.
  • a hydraulic excavator comprises various sections, i.e., an engine, a front operating device (hereinafter referred to simply as a front ), a swing body, and a track or travel body.
  • the engine is operated upon turning-on of a key switch, whereas the front, the swing body, and the track body are operated upon an operator's manipulation made during the engine operation.
  • the engine running time, the front operating time, the swing time, and the travel time take different values from one another.
  • An object of the present invention is to provide a method and system for managing a construction machine, and a processing apparatus, which make it possible to confirm how a customer employs a machine in practice, and to evaluate whether the machine is an optimum model for the customer.
  • a method for managing a construction machine comprising a first step of measuring an operation or working status for each of sections of each of a plurality of construction machines working in fields and including various models, and transferring the measured operation status to a base station computer and then storing and accumulating it as operation data in a database; and a second step of, in the base station computer, statistically processing the operation data and producing and outputting evaluation data for determining whether a particular one of the plurality of construction machines is an optimum model.
  • the second step includes a third step of calculating, as the evaluation data, a value of at least one index regarding the state of use of the particular one of the plurality of construction machines based on the operation data, and determines based on the calculated index value whether the particular construction machine is an optimum model.
  • the second step further includes a fourth step of calculating, as the evaluation data, a value of the index for each of construction machines of the same model as the particular construction machine based on the operation data, thereby obtaining first correlation between the index and the number of operated construction machines, and compares the index value of the particular construction machine with the first correlation to determine whether the particular construction machine is an optimum model.
  • the second step further includes a fifth step of calculating, as the evaluation data, a value of the index for each of construction machines of at least one of the various models of the plurality of construction machines, which differs from the model of the particular construction machine, based on the operation data, thereby obtaining second correlation between the index and the number of operated construction machines, and compares the index value of the particular construction machine with the first and second correlations to determine whether the particular construction machine is an optimum model.
  • the first step measures a load for each of said sections in addition to the operation status for each section, and stores and accumulates the measured load in the database of the base station computer; and the second step further includes a sixth step (S42A, S430-442) of modifying the measured operation status depending on an amount of the measured load, and produces the evaluation data by using, as the operation data, the load-dependent modified operation status.
  • the operation status is represented by at lease one of an operating time and the number of times of operations.
  • the construction machine is a hydraulic excavator
  • the section is any of a front , a swing body , a track body and an engine of the hydraulic excavator.
  • the operation status for each section i.e., each of the front, the swing body, the track body and the engine of the hydraulic excavator, can be measured, and whether that hydraulic excavator is an optimum model for the customer can be evaluated more appropriately.
  • the construction machine is a hydraulic excavator ;
  • the sections include a front , a swing body , a track body and an engine of the hydraulic excavator; the operation status is represented by an operating time for each of the front, the swing body, the track body and the engine; and the index includes at least one of a ratio of an engine running time to a travel time, a ratio of the engine running time to a time during which a pump pressure is not lower than a predetermined value, the product of a ratio of the engine running time to a swing time and a bucket capacity, and the product of a ratio of the engine running time to an excavation time and an excavator body weight.
  • the construction machine is a hydraulic excavator ;
  • the sections include a front , a swing body and a track body of the hydraulic excavator;
  • the operation status is represented by the number of times of operations for each of the front, the swing body and the track body;
  • the index includes at least one of a ratio of the total number of times of operations to the number of times of track operations, a ratio of the total number of times of operations to the number of times of operations in which a pump pressure is not lower than a predetermined value, the product of a ratio of the total number of times of operations to the number of times of track operations and a bucket capacity, and the product of a ratio of the total number of times of operations to the number of times of front operations and an excavator body weight.
  • a system for managing a construction machine comprising data measuring and collecting means for measuring and collecting an operation status for each section of each of a plurality of construction machines working in fields and including various models; and a base station computer mounted in a base station and having a database in which the operation status measured and collected for each section is stored and accumulated as operation data, the base station computer including computing means for statistically processing the operation data to produce and output evaluation data for determining whether a particular one of the plurality of construction machines is an optimum model, wherein said computing means includes first means for calculating, as the evaluation data, a value of at least one index regarding the state of use of the particular one of the plurality of construction machines based on the operation data, and determines based on the calculated index value whether the particular construction machine is an optimum model.
  • the computing means further includes second means for calculating, as the evaluation data, a value of the index for each of construction machines of the same model as the particular construction machine based on the operation data, thereby obtaining first correlation between the index and the number of operated construction machines, and compares the index value of the particular construction machine with the first correlation to determine whether the particular construction machine is an optimum model.
  • the computing means further includes third means for comparing the index value of the particular construction machine with the first correlation to determine whether the particular construction machine is an optimum model.
  • the computing means further includes fourth means for calculating, as the evaluation data, a value of the index for each of construction machines of at least one of the various models of the plurality of construction machines, which differs from the model of the particular construction machine, based on the operation data, thereby obtaining second correlation between the index and the number of operated construction machines, and compares the index value of the particular construction machine with the first and second correlations to determine whether the particular construction machine is an optimum model.
  • the computing means further includes fifth means for comparing the index value of the particular construction machine with the first and second correlations to determine whether the particular construction machine is an optimum model.
  • the data measuring and collecting means measures and collects, in addition to the operation status for each section, a load for each section; the base station computer stores and accumulates the operation status and the load measured and collected for each section, as the operation data, in the database ; and the computing means further includes sixth means (S42A, S430-442) for modifying the measured operation status depending on an amount of the measured load, and produces the evaluation data by using, as the operation data, the load-dependent modified operation status.
  • sixth means S42A, S430-442
  • a processing apparatus wherein an operation status for each section of each of a plurality of construction machines working in fields and including various models is stored and accumulated as operation data, and the operation data is statistically processed to produce and output evaluation data for determining whether a particular one of the plurality of construction machines is an optimum model.
  • Fig. 1 shows an overall outline of a management system including a system for evaluating an optimum model of a construction machine according to a first embodiment of the present invention.
  • the management system comprises machine side controllers 2 mounted on hydraulic excavators 1, 1a, 1b, 1c, ... (hereinafter represented by numeral 1) working in fields; a base station center server 3 installed in a main office, a branch office, a production factory or the like; an in-house computer 4 installed in the branch office, a service workshop, the production factory or the like; and a user side computer 5.
  • the base station center server 3 may be installed, in addition to the above-mentioned places, in any other desired place, for example, in a rental company possessing several units of hydraulic excavators.
  • the controller 2 in each hydraulic excavator 1 collects operation information of the hydraulic excavator 1.
  • the collected operation information is sent along with machine body information (machine model and number) to a ground station 7 through satellite communication using a communication satellite 6, and then transmitted from the ground station 7 to the base station center server 3.
  • the machine body/operation information may be taken into the base station center server 3 through a personal computer 8 instead of satellite communication.
  • a serviceman downloads the operation information collected by the controller 2 into the personal computer 8 along with the machine body information (machine model and number).
  • the downloaded information is taken into the base station center server 3 from the personal computer 8 using a floppy disk or via a communication line such as a public telephone line or the Internet.
  • check information obtained by the routine inspection and repair information can also be collected through manual inputting by the serviceman. Such manually inputted information is similarly taken into the base station center server 3.
  • Fig. 2 shows details of the configuration of the machine side controller 2.
  • the controller 2 comprises input/output interfaces 2a, 2b, a CPU (Central Processing Unit) 2c, a memory 2d, a timer 2e, and a communication control unit 2f.
  • CPU Central Processing Unit
  • the controller 2 receives, from a sensor group (described later) through the input/output interface 2a, detection signals of pilot pressures associated with the front, swing and track or travel; a detection signal of the operating time of the engine 32 (see Fig. 3 ) (hereinafter referred to as the engine running time ); a detection signal of pump pressure in a hydraulic system; a detection signal of oil temperature in the hydraulic system; and a detection signal of the engine revolution speed.
  • the CPU 2c processes those data of the received information into operation information in the predetermined form by using a timer (including the clocking function) 2e, and then stores the operation information in the memory 2d.
  • the communication control unit 2f routinely transmits the operation information to the base station center server 3 through satellite communication. Also, the operation information is downloaded into the personal computer 8 through the input/output interfaces 2b.
  • the machine side controller 2 includes a ROM for storing control programs, with which the CPU 2c executes the above-described processing, and a RAM for temporarily storing data used during the processing.
  • Fig. 3 shows details of the hydraulic excavator 1 and the sensor group.
  • the hydraulic excavator 1 comprises a track or travel body 12; a swing body 13 rotatably mounted on the track body 12; a cab 14 provided in a front left portion of the swing body 13; and a front operating device (excavation device), i.e., a front 15, mounted to a front central portion of the swing body 13 in a vertically rotatable manner.
  • the front 15 is made up of a boom 16 rotatably provided on the swing body 13; an arm 17 rotatably provided at a fore end of the boom 16; and a bucket 18 rotatably provided at a fore end of the arm 17.
  • a hydraulic system 20 is mounted on the hydraulic excavator 1.
  • the hydraulic system 20 comprises hydraulic pumps 21a, 21b; boom control valves 22a, 22b, an arm control valve 23, a bucket control valve 24, a swing control valve 25, and track or travel control valves 26a, 26b; and a boom cylinder 27, an arm cylinder 28, a bucket cylinder 29, a swing motor 30, and track motors 31a, 31b.
  • the hydraulic pumps 21a, 21b are driven for rotation by a diesel engine (hereinafter referred to simply as an "engine") 32 to deliver a hydraulic fluid (oil).
  • engine diesel engine
  • the control valves 22a, 22b to 26a, 26b control flows (flow rates and flow directions) of the hydraulic fluid supplied from the hydraulic pumps 21a, 21b to the actuators 27 to 31a and 31b.
  • the actuators 27 to 31a and 31b drive the boom 16, the arm 17, the bucket 18, the swing body 13, and the track body 12.
  • the hydraulic pumps 21a, 21b, the control valves 22a, 22b to 26a, 26b, and the engine 32 are installed in an accommodation room formed in a rear portion of the swing body 13.
  • Control lever devices 33, 34, 35 and 36 are provided in association with the control valves 22a, 22b to 26a, 26b.
  • a control lever of the control lever device 33 When a control lever of the control lever device 33 is operated in one direction X1 of two crossing directions (+), an arm-crowding pilot pressure or an arm-dumping pilot pressure is generated and applied to the arm control valve 23.
  • a rightward-swing pilot pressure or a leftward-swing pilot pressure is generated and applied to the swing control valve 25.
  • a boom-raising pilot pressure or a boom-lowering pilot pressure is generated and applied to the boom control valves 22a, 22b.
  • a bucket-crowding pilot pressure or a bucket-dumping pilot pressure is generated and applied to the bucket control valve 24.
  • a left-track pilot pressure and a right-track pilot pressure are generated and applied to the track control valves 26a, 26b, respectively.
  • the control lever devices 33 to 36 are disposed in the cab 14 together with the controller 2.
  • the sensor 40 is a pressure sensor for detecting the arm-crowding pilot pressure as an operation signal for the front 15.
  • the sensor 41 is a pressure sensor for detecting the swing pilot pressure taken out through a shuttle valve 41a
  • the sensor 42 is a pressure sensor for detecting the track or travel pilot pressure taken out through shuttle valves 42a, 42b and 42c.
  • the sensor 43 is a sensor for detecting the on/off state of a key switch of the engine 32
  • the sensor 44 is a pressure sensor for detecting a delivery pressure of the hydraulic pumps 21a, 21b, i.e., a pump pressure, taken out through a shuttle valve 44a
  • the sensor 45 is an oil temperature sensor for detecting a temperature of working oil (oil temperature) in the hydraulic system 1.
  • the revolution speed of the engine 32 is detected by a revolution speed sensor 46. Signals from those sensors 40 to 46 are sent to the controller 2.
  • the base station center server 3 comprises input/output interfaces 3a, 3b, a CPU 3c, and a storage device 3d in which a database 100 is formed.
  • the input/output interface 3a receives the machine body/operation information and the check information from the machine side controller 2, and the input/output interface 3b receives the machine body information for each machine model and a request for evaluating an optimum model from the in-house computer 4.
  • the CPU 3c stores and accumulates those data of the received information in the storage device 3d in the form of the database 100.
  • the CPU 3c processes the information stored in the database 100 to make a daily report, a diagnostic report, an optimum model evaluation result report, etc., and then transmits those reports to either one or both of the in-house computer 4 and the user side computer 5 via the input/output interface 3b.
  • the base station center server 3 includes a ROM for storing control programs, with which the CPU 3c executes the above-described processing, and a RAM for temporarily storing data in the course of the processing.
  • Fig. 4 is a functional block diagram showing an outline of processing functions of the CPU 3c.
  • the CPU 3c has various processing functions executed by a machine body/operation information processing section 50, a machine body information/optimum model evaluation processing section 51, a check information processing section 52, an in-house comparison determination processing section 53, and an external-house comparison determination processing section 54.
  • the machine body/operation information processing section 50 executes predetermined processing by using the operation information inputted from the machine side controller 2.
  • the machine body information/optimum model evaluation processing section 51 executes predetermined processing based on the machine body information for each machine model and a request for evaluating an optimum model both inputted from the in-house computer 4 (as described later).
  • the check information processing section 52 stores and accumulates the check information, inputted from the personal computer 8, in the database 100, and also processes the check information to make a diagnostic report.
  • the in-house comparison determination processing section 53 and the external-house comparison determination processing section 54 select required data among from not only the information prepared by the machine body/operation information processing section 50, the machine body information/optimum model evaluation processing section 51 and the check information processing section 52, but also the information stored and accumulated in the database 100, and transmit the selected data to the in-house computer 4 and the user side computer 5.
  • the processing function of the machine side controller 2 is mainly divided into the function of collecting an operating or working time for each section of the hydraulic excavator and the function of collecting frequency distribution data such as load frequency distribution for each section.
  • the machine body/operation information processing section 50 of the base station center server 3 has the function of processing the operating time and the function of collecting the frequency distribution data.
  • Fig. 5 is a flowchart showing the function of collecting the operating time for each section of the hydraulic excavator executed in the CPU 2c of the controller 2
  • Fig. 6 is a flowchart showing the processing function of the communication control unit 2f in the controller 2 executed when the collected operating time data for each section is transmitted.
  • the CPU 2c first determines whether the engine revolution speed signal from the sensor 46 is of a value not lower than a predetermined revolution speed, and hence whether the engine is being operated (step S9). If it is determined that the engine is not being operated, step S9 is repeated. If it is determined that the engine is being operated, the CPU 2c proceeds to next step S10 and reads data regarding the pilot pressure detection signals associated with the front, swing and track from the sensors 40, 41 and 42 (step S10).
  • the CPU 2c calculates, using time information from the timer 2e, a time during which the pilot pressure exceeds a predetermined pressure, and stores and accumulates the calculated result in the memory 2d in correspondence to the date and the time of day (step S12).
  • the predetermined pressure represents a pilot pressure that can be regarded as indicating that each of the front, swing and track operations has been performed.
  • the CPU 2c calculates an engine running time using time information from the timer 2e, and stores and accumulates the calculated result in the memory 2d in correspondence to the date and the time of day (step S14).
  • the CPU 2c executes the above-described processing at a predetermined cycle during a period of time in which power supplied to the controller 2 is turned on.
  • the operating time calculated in each of steps S12, S14 may be added to the corresponding time calculated in the past and stored in the memory 2d, and may be stored as an accumulative operating time.
  • the communication control unit 2f monitors whether the timer 2e is turned on (step S20).
  • the CPU reads the operating time for each section of the front, swing and track, the engine running time (including the date and the time of day), and the machine body information, which are stored and accumulated in the memory 2d (step S22), and then transmits the read data to the base station center server 3 (step S24).
  • the timer 2e is set to turn on at the fixed time of day, for example, at a.m. 0. By so setting the timer, when it becomes a.m. 0, the operating time data for one preceding day is transmitted to the base station center server 3.
  • the CPU 2c and the communication control unit 2f repeat the above-described processing everyday.
  • the data stored in the CPU 2c is erased when a predetermined number of days, e.g., 365 days (one year), have lased after the transmission to the base station center server 3.
  • Fig. 7 is a flowchart showing the processing function of the machine body/operation information processing section 50 in the center server 3 executed when the machine body/operation information is transmitted from the machine side controller 2.
  • the machine body/operation information processing section 50 monitors whether the machine body/operation information is inputted from the machine side controller 2 (step S30). When the machine body/operation information is inputted, the processing section 50 reads the inputted information, and then stores and accumulates it as operation data (see Fig. 8 ) in the database 100 (step S32).
  • the machine body information contains, as described above, the machine model and number.
  • the processing section 50 reads the operation data for a predetermined number of days, e.g., one month, out of the database 100 and makes a daily report regarding the operating time (step S34). Thereafter, the thus-prepared daily report and a maintenance report are transmitted to the in-house computer 4 and the user side computer 5 (step S40).
  • Fig. 8 shows how the operation data is stored in the database 100.
  • the database 100 contains, as shown in Fig. 8 , a database section (hereinafter referred to as an operation database ) in which the operation data per machine model and number is stored and accumulated.
  • the operation database stores data as given below.
  • the engine running time, the front operation time (hereinafter referred to also as the excavation time), the swing time, and the travel time per machine model and number are stored in the operation database per machine model and number as daily report data in the form of accumulative values in correspondence to the date.
  • T NE (1) and T D (1) represent respectively an accumulative value of the engine running time and an accumulative value of the front operation time for a No. N machine of model A as of January 1, 2000.
  • T NE (K) and T D (K) represent respectively an accumulative value of the engine running time and an accumulative value of the front operation time for the No. N machine of model A as of March 16, 2000.
  • accumulative values T S (1) to T S (K) of the swing time and accumulative values T T (1) to T T (K) of the travel time for the No. N machine of model A are stored in correspondence to the date. Similar data is also stored for a No. N+1 machine, a No. N+2 machine, etc. of model A.
  • the operation database stores the frequency distribution data, although this point will be described below.
  • Figs. 9 and 10 each show one example of the daily report transmitted to the in-house computer 4 and the user side computer 5.
  • Fig. 9 shows each operating time data for one month in the form of graph and numerical value in correspondence to the date.
  • the user can confirm changes in the state of use of the owned hydraulic excavator for the past one month.
  • the left side of Fig. 10 graphically shows the operating time for each section and the engine running time under no load for the past half year, and the right side of Fig. 10 graphically shows transition of a ratio between the engine running time under load and the engine running time under no load for the past half year.
  • the user can confirm changes in the state and efficiency of use of the owned hydraulic excavator for the past half year.
  • Fig. 11 is a flowchart showing the processing function of the CPU 2c in the controller 2.
  • the CPU 2c first determines whether the engine revolution speed signal from the sensor 46 is of a value not lower than a predetermined revolution speed, and hence whether the engine is being operated (step S89). If it is determined that the engine is not being operated, step S89 is repeated. If it is determined that the engine is being operated, the CPU 2c proceeds to next step S90 and reads data regarding the pilot pressure detection signals associated with the front, swing and track from the sensors 40, 41 and 42, the pump pressure detection signal from the sensor 44, the oil temperature detection signal from the sensor 45, and the engine revolution speed detection signal from the sensor 46 (step S90).
  • the pilot pressures associated with the front, swing and track and the pump pressure are stored in the memory 2d as the frequency distribution data of excavation load, swing load, travel load and pump load, respectively (step S92).
  • the read oil temperature and engine revolution speed are also stored in the memory 2d as the frequency distribution data (step S94).
  • steps S90 to S94 are repeated.
  • the frequency distribution data represents data resulting from obtaining a distribution of detected values per predetermined time, e.g., 100 hours, with respect to the pump pressure or the engine revolution speed.
  • the predetermined time (100 hours) is of a value on the basis of engine running time.
  • the predetermined time may be of a value on the basis of the operating time for each section.
  • Fig. 12 is a flowchart showing details of processing procedures for preparing the frequency distribution data of excavation load.
  • the CPU first determines whether the engine running time has exceeded 100 hours after entering this processing (step S100). If it does not yet exceed 100 hours, the CPU then determines, using the signal from the sensor 40, whether the hydraulic excavator is in the state of arm crowding operation (under excavation) (step S108). If the hydraulic excavator is in the state of arm crowding operation (under excavation), the CPU determines, using the signal from the sensor 44, whether the pump pressure is, e.g., 30 MPa or higher (step S110).
  • a unit time (computation cycle time) ⁇ T is added to an accumulative time T D1 for the pressure zone of 30 MPa or higher, and the resulting sum is set to a new accumulative time T D1 (step S112). If the pump pressure is not 30 MPa or higher, the CPU determines whether the pump pressure is 25 MPa or higher (step S114). If the pump pressure is 25 MPa or higher, the unit time (computation cycle time) ⁇ T is added to an accumulative time T D2 for the pressure zone of 25 to 30 MPa, and the resulting sum is set to a new accumulative time T D2 (step S116).
  • the unit time ⁇ T is added to an accumulative time T D3 , ..., T Dn-1 , or T Dn for the corresponding pressure zone, and the resulting sum is set to a new accumulative time T D3 , ..., T Dn-1 , or T Dn (steps S118 to S126).
  • the processing procedures for preparing the frequency distribution data of swing load and travel load are the same as those shown in Fig. 12 except for that, in the process of step S108 in Fig. 12 , the CPU determines using the sensor 44 whether the hydraulic excavator is in the state of swing operation, or determines using the sensor 42 whether the hydraulic excavator is in the state of travel operation, instead of determining, using the signal from the sensor 40, whether the hydraulic excavator is in the state of arm crowding operation (under excavation).
  • the CPU proceeds to the processing, shown in Fig. 13 , for preparing the frequency distribution data of pump load of the hydraulic pumps 21a, 21b.
  • the CPU first determines, using the signal from the sensor 44, whether the pump pressure is, e.g., 30 MPa or higher (step S138). Then, if the pump pressure is 30 MPa or higher, the unit time (computation cycle time) ⁇ T is added to an accumulative time T P1 for the pressure zone of 30 MPa or higher, and the resulting sum is set to a new accumulative time T P1 (step S140). If the pump pressure is not 30 MPa or higher, the CPU determines whether the pump pressure is 25 MPa or higher (step S142).
  • the unit time (computation cycle time) ⁇ T is added to an accumulative time T P2 for the pressure zone of 25 to 30 MPa, and the resulting sum is set to a new accumulative time T P2 (step S144).
  • the unit time ⁇ T is added to an accumulative time T P3 , ..., T Pn-1 , or T Pn for the corresponding pressure zone, and the resulting sum is set to a new accumulative time T P3 , ..., T Pn-1 , or T Pn (steps S146 to S154).
  • the CPU proceeds to the processing, shown in Fig. 14 , for preparing the frequency distribution data of oil temperature.
  • the CPU first determines, using the signal from the sensor 45, whether the oil temperature is, e.g., 120°C or higher (step S168). Then, if the oil temperature is 120°C or higher, the unit time (computation cycle time) ⁇ T is added to an accumulative time T O1 for the temperature zone of 120°C or higher, and the resulting sum is set to a new accumulative time T O1 (step S170). If the oil temperature is not 120°C or higher, the CPU determines whether the oil temperature is 110°C or higher (step S172).
  • the unit time (computation cycle time) ⁇ T is added to an accumulative time T O2 for the temperature zone of 110 to 120°C, and the resulting sum is set to a new accumulative time T O2 (step S174).
  • the unit time ⁇ T is added to an accumulative time T O3 , ..., T On-1 ,or T On for the corresponding temperature zone, and the resulting sum is set to a new accumulative time T O3 , ..., T On-1 , or T On (steps S176 to S184).
  • the CPU proceeds to the processing, shown in Fig. 15 , for preparing the frequency distribution data of engine revolution speed.
  • the CPU first determines, using the signal from the sensor 46, whether the engine revolution speed is, e.g., 2200 rpm or higher (step S208). Then, if the engine revolution speed is 2200 rpm or higher, the unit time (computation cycle time) ⁇ T is added to an accumulative time T N1 for the engine revolution speed of 2200 rpm or higher, and the resulting sum is set to a new accumulative time T N1 (step S210). If the engine revolution speed is not 2200 rpm or higher, the CPU determines whether the engine revolution speed is 2100 rpm or higher (step S212).
  • the unit time (computation cycle time) ⁇ T is added to an accumulative time T N2 for the engine revolution speed zone of 2100 to 2200 rpm, and the resulting sum is set to a new accumulative time T N2 (step S214).
  • the unit time ⁇ T is added to an accumulative time T N3 , ...,T Nn-1 , or T Nn for the corresponding engine revolution speed zone, and the resulting sum is set to a new accumulative time T N3 , ..., T Nn-1 , or T Nn (steps S216 to S224).
  • the CPU After the end of the processing shown in Fig. 15 , the CPU returns to step S100 of Fig. 12 and repeats the processing shown in Figs. 12 to 15 until the engine running time exceeds 100 hours.
  • the frequency distribution data thus collected is transmitted from the communication control unit 2f of the controller 2 to the base station center server 3.
  • the processing function executed by the communication control unit 2f in that occasion is shown in a flowchart of Fig. 16 .
  • the CPU monitors whether the engine running time has exceeded 100 hours (step S230). If the engine running time has exceeded 100 hours, the frequency distribution data and the machine body information, both stored and accumulated in the memory 2d, are read out (step S232) and transmitted to the base station center server 3 (step S234). As a result, the frequency distribution data is transmitted to the base station center server 3 each time the data is accumulated in amount corresponding to 100 hours of the engine running time.
  • the CPU 2c and the communication control unit 2f execute the above-described processing repeatedly per 100 hours on the basis of engine running time.
  • the data stored in the CPU 2c is erased when a predetermined number of days, e.g., 365 days (one year), have lased after the transmission to the base station center server 3.
  • Fig. 17 is a flowchart showing the processing function of the machine body/operation information processing section 50 in the center server 3 executed when the frequency distribution data is transmitted from the machine side controller 2.
  • the machine body/operation information processing section 50 monitors whether the frequency distribution data for each of excavation load, swing load, travel load, pump load, oil temperature and engine revolution speed is inputted from the machine side controller 2 (step S240). When the data is inputted, the processing section 50 reads the inputted data, and then stores it as operation data (see Fig. 8 ) in the database 100 (step S242). Subsequently, the frequency distribution data for each of excavation load, swing load, travel load, pump load, oil temperature and engine revolution speed is processed to make a report in the form of a graphs (step S244), and the report is transmitted to the in-house computer 4 and the user side computer 5 (step S246).
  • the database 100 contains an operation database section per machine model and number, in which the operating time data for each day per machine model and number is stored and accumulated as daily report data.
  • the respective values of the frequency distribution data of excavation load, swing load, travel load, pump load, oil temperature and engine revolution speed per machine model and number are stored and accumulated in the operation database per 100 hours on the basis of engine running time.
  • Fig. 8 shows examples of the frequency distribution of pump load and oil temperature for the No. N machine of model A.
  • the frequency distribution of pump load for first 100 hours is stored in an area of from 0 hr to 100 hr for each pump pressure zone of 5 MPa, e.g., from 0 MPa to 5 MPa: 6 hr, from 5 MPa to 10 MPa: 8 hr, ..., from 25 MPa to 30 MPa: 10 hr, and not less than 30 MPa: 2 hr.
  • the frequency distribution of pump load is similarly stored in each area of from 100 hr to 200 hr, from 200 hr to 300 hr, ..., from 1500 hr to 1600 hr.
  • the above description is likewise applied to the frequency distributions of excavation load, swing load and travel load, the frequency distribution of oil temperature, and the frequency distribution of engine revolution speed.
  • the load is represented by pump load. More specifically, the respective values of the operating time for excavation, swing and travel are collected for each of the pressure zones of from 0 MPa to 5 MPa, from 5 MPa to 10 MPa, ..., from 25 MPa to 30 MPa, and not lower than 30 MPa on the basis of pump pressure, and then stored as the frequency distributions of excavation load, swing load and travel load.
  • Fig. 18 shows one example of a report of the frequency distribution data transmitted to the in-house computer 4 and the user side computer 5.
  • This example shows each load frequency distribution as a rate with respect to each operating time among 100 hours of engine running time.
  • the frequency distribution of excavation load for example, is represented by setting the excavation time (e.g., 60 hours) among 100 hours of engine running time to 100%, and obtaining a percentage (%) of an accumulative time for each pressure zone of pump pressure with respect to 60 hours.
  • the frequency distributions of swing load, travel load and pump load are also represented in a similar manner.
  • the frequency distributions of oil temperature and engine revolution speed are each represented by setting 100 hours of engine running time to 100 % and obtaining a percentage of each accumulative time with respect to 100 %.
  • Fig. 19 is a flowchart showing the processing function of the machine body information per machine model executed in the machine body information/optimum model evaluating processing section 51 of the center server 3.
  • the machine body information/optimum model evaluating processing section 51 monitors whether the machine body information per machine model is inputted from the in-house computer 4 by, e.g., the serviceman (step S500). Each time when the machine body information is inputted, the processing section 51 reads the inputted machine body information, and then stores and accumulates it as machine body data (see Fig. 20 ) in the database 100 (step S502).
  • the machine body information per machine model contains data regarding the specifications of the machine body, such as the machine weight, bucket capacity and crawler shoe width.
  • Fig. 20 shows how the machine body data is stored in the database 100.
  • the database 100 contains, in addition to the operation database shown in Fig. 8 , a machine body database section (hereinafter referred to as a machine body database) in which the machine body data per machine model, shown in Fig. 20 , is stored and accumulated.
  • the machine body database stores data as given below.
  • the machine body database stores, per machine model, data regarding the specifications of the machine body of each model.
  • W A represents the weight (e.g., 6.5 ton) of the machine model A
  • B A represents the bucket capacity (e.g., 0.3 m 3 )
  • S A represents the crawler shoe width (e.g., 500 mm) of the machine model A.
  • the specification data of the machine body is similarly stored.
  • Fig. 21 is a flowchart showing the function of processing a request for evaluating an optimum model executed in the machine body information/optimum model evaluation processing section 51 of the center server 3.
  • the machine body information/optimum model evaluating processing section 51 monitors whether a request for evaluating an optimum model is inputted from the in-house computer 4 by, e.g., the serviceman (step S510). When the request for evaluating an optimum model is inputted, the processing section 51 reads the inputted demand (step S512).
  • inputting of the request for evaluating an optimum model means an entry of the machine body and number of the hydraulic excavator used by the customer.
  • the processing section 51 accesses the database 100 to read the operation data corresponding to the same machine number, to compute an index value of the hydraulic excavator corresponding to the inputted number for each index item regarding the state of use of the hydraulic excavator, and to obtain a distribution of the number of operated machines with respect to index values, thereby plotting a distribution graph (step S514).
  • the index regarding the state of use of the hydraulic excavator implies a parameter indicating the state of use of the hydraulic excavator, such as an excavation ratio, a swing ratio and a travel ratio (described later).
  • the processing section 51 evaluates whether the hydraulic excavator corresponding to the inputted machine number is an optimum model (step S516), and then prepares and outputs a report of the evaluation result (step S518).
  • step S514 Details of the processing executed in step S514 is shown in a flowchart of Fig. 22 .
  • the processing section 51 accesses the database 100 and reads the operating time data for each machine number of the model A from the operation database shown in Fig. 8 (step S520).
  • the machine model A is a model read in step S512 of Fig. 21 .
  • the processing section 51 calculates, per machine number, a travel ratio (%) by dividing the past total travel time (e.g., the latest accumulative value T T (K) of travel time for the No. N machine shown in Fig. 8 ) by the past total engine running time (e.g., the latest accumulative value T NE (K) of engine running time for the No. N machine shown in Fig. 8 ) (step S522).
  • the term travel ratio represents a proportion of the travel time with respect to the total working time, i.e., a value indicating a rate at which the hydraulic excavator is used for travel.
  • the processing section 51 classifies the travel ratios calculated per machine number and obtains a distribution of the number of operated machines with respect to the travel ratio (step S524).
  • the travel ratio is divided into unit-width ranges of, for example, from 1 % to 5 %, from 5 % to 10 %, ..., from 90 % to 95 %, and not less than 95 %.
  • the number of operated machines belonging to each range of the travel ratio is calculated so that the number of operated machines is correlated with each range of the travel ratio.
  • the thus-obtained distribution data is prepared in the form of a distribution graph, and the travel ratio of the machine corresponding to the inputted number is put in the distribution graph (S526).
  • the distribution data is obtained for a pump load ratio as another index, and a distribution graph including the pump load ratio of the machine corresponding to the inputted number is plotted (steps S528 to S532).
  • the term pump load ratio represents a proportion of a time during which the pump load pressure is not lower than a predetermined pressure, with respect to the total working time (engine running time), i.e., a value indicating a rate at which the hydraulic excavator is used for work required for operating the pump.
  • the time during which the pump load pressure is not lower than the predetermined pressure can be obtained as, e.g., a pump operating time.
  • the pump operating time can be obtained as the sum of the front operating time, the swing time and the travel time (e.g., the sum of the latest accumulative value T D (K) of front operating time, the latest accumulative value T S (K) of swing time, and the latest accumulative value T T (K) of travel time for the No. N machine shown in Fig. 8 ).
  • the pump load ratio is given as a value resulting from dividing the above sum by the total engine running time (e.g., the latest accumulative value T NE (K) of engine running time for the No. N machine shown in Fig. 8 ) (step S528).
  • the pump operating time may be obtained by directly calculating the time during which the pump load pressure is not lower than the predetermined pressure, based on the pump load frequency distribution data in the operation frequency distribution data shown in Fig. 8 .
  • the time during which the pump load pressure is not lower than the predetermined pressure is determined by summing up the pump load frequency distribution data per 100 hours of operating time in the operation frequency distribution data shown in Fig. 8 , obtaining a pump load frequency distribution in the total operating time of the hydraulic pump, and totalizing periods of time during which the pump load pressure is not lower than the predetermined pump pressure (e.g., 5 MPa).
  • the pump load ratio is given as a value resulting from dividing the totalized time by the total engine running time (e.g., the latest accumulative value T NE (K) of engine running time for the No. N machine shown in Fig. 8 ).
  • indices such as an excavation load ratio (excavation time/total working time) and a swing load ratio (swing time/total working time), can also be set as required, and a distribution graph for each index can be obtained in a similar manner.
  • Figs. 23 and 24 are flowcharts showing details of the evaluation processing executed in step S516 of the flowchart shown in Fig. 21 .
  • step S540 it is first determined whether the travel ratio of the machine corresponding to the inputted number is larger than a predetermined range including an average value.
  • the travel ratio of the machine corresponding to the inputted number has been obtained by the processing of step S522 in Fig. 22
  • the predetermined range including the average value has been obtained as a travel ratio range in which the number of operated machines is maximum among the distribution data obtained by the processing of step S524 in Fig. 22 .
  • step S542 an advice for selection of a travel-enhanced model is provided.
  • step S550 it is first determined whether the pump load ratio of the machine corresponding to the inputted number is larger than a predetermined range including an average value.
  • the pump load ratio of the machine corresponding to the inputted number has been obtained by the processing of step S528 in Fig. 22
  • the predetermined range including the average value has been obtained as a pump load ratio range in which the number of operated machines is maximum among the distribution data obtained by the processing of step S530 in Fig. 22 .
  • step S552 it is now determined whether the pump load ratio is larger than the predetermined range including the average value
  • step S554 If the pump load ratio is larger than the predetermined range, an advice for selection of a model of a one rank-up level is provided (step S554). If the pump load ratio is not larger than the predetermined range, an advice for selection of a model of a one rank-down level is provided (step S556).
  • Figs. 25 and 26 each show one example of the evaluation result report prepared and outputted in the processing of step S518 in Fig. 21 .
  • Fig. 25 shows one example of the report showing both a distribution graph of the number of operated machines with respect to the travel ratio for the machine model A, and the travel ratio of the machine corresponding to the inputted number.
  • the travel ratio of the machine corresponding to the inputted number is indicated by a vertical line in the distribution graph.
  • the average value i.e., the peak value of the distribution graph
  • Fig. 26 shows one example of the report showing both a distribution graph of the number of operated machines with respect to the pump load ratio for the machine model A, and the pump load ratio of the machine corresponding to the inputted number.
  • the pump load ratio of the machine corresponding to the inputted number is indicated by a vertical line in the distribution graph. Also, in this example, since the pump load ratio of the machine corresponding to the inputted number is lower than the average value (i.e., the peak value of the distribution graph), a message Model of one rank-down level is recommended is added to the evaluation result.
  • the sensors 40 to 46 and the controller 2 are provided as data measuring and collecting means in each of a plurality of hydraulic excavators 1 working in fields to measure an operating time for each of a plurality of sections (the engine 32, the front 15, the swing body 13 and the track body 12), which are operated for different periods of time per hydraulic excavator, and the measured operating time is transferred to the base station computer 3 to be stored and accumulated as operation data therein.
  • the operation data is read out for each hydraulic excavator to obtain an index value, such as a travel ratio, regarding the state of use of a particular hydraulic excavator and a distribution of the number of operated hydraulic excavators of the same model as the particular hydraulic excavator with respect to index values.
  • the index value of the particular hydraulic excavator is compared with that distribution to determine whether the particular hydraulic excavator is an optimum model. Therefore, how the customer employs the owned hydraulic excavator (particular hydraulic excavator) in practice can be confirmed from comparison with other hydraulic excavators of the same model, and whether the particular hydraulic excavator is an optimum model for the customer can be evaluated. It is hence possible to give an advice about the optimum model depending on the state of use.
  • a daily report of operation information, a diagnostic report of maintenance and check results, etc. are provided to the user side as appropriate, the user can confirm the status of operation of the owned hydraulic excavator everyday, and can more easily perform management of the hydraulic excavator on the user side.
  • a second embodiment of the present invention will be described with reference to Figs. 27 to 33 .
  • This embodiment is intended to additionally plot a distribution graph of the number of operated machines of another model having an average value of the index regarding the state of use, which is close to the index value of the machine corresponding to the inputted number, and to evaluate an optimum model with easier understanding.
  • a management system of a construction machine has the same overall arrangement as that of the first embodiment, and has a system arrangement similar to that of the first embodiment shown in Figs. 1 to 3 . Also, the machine side controller 2 and the base station center server 3 have the same processing functions as those described above with reference to Figs. 4 to 26 except for the points described below. The following description is made of the points different from the first embodiment.
  • Fig. 27 is a flowchart showing the function of processing a request for evaluating an optimum model executed in the machine body information/optimum model evaluation processing section 51 of the center server 3 according to this embodiment.
  • processing to monitor whether a request for evaluating an optimum model is inputted (step S510) and processing to read the inputted demand for evaluating an optimum model (step S512) are the same as those in the first embodiment shown in Fig. 21 .
  • the processing section 51 accesses the database 100 to read the machine body data as well as the operation data corresponding to the same machine number, to compute an index value of the hydraulic excavator corresponding to the inputted number for each index item regarding the state of use of the hydraulic excavator, and to obtain a distribution of the number of operated machines with respect to index values, thereby plotting a distribution graph (step S564).
  • the processing section 51 evaluates whether the hydraulic excavator corresponding to the inputted machine number is an optimum model (step S566), and then prepares and outputs a report of the evaluation result (step S568).
  • step S564 Details of the processing executed in step S564 is shown in a flowchart of Fig. 28 .
  • the processing section 51 accesses the database 100 and reads the operating time data and the machine body data for each machine number of the model A (i.e., the model read in step S512 of Fig. 27 ), respectively, from the operation database shown in Fig. 8 and the machine body database shown in Fig. 20 (step S570).
  • the processing section 51 calculates, per machine number, a travel ratio (%) by dividing the past total travel time (e.g., the latest accumulative value T T (K) of travel time for the No. N machine shown in Fig. 8 ) by the past total engine running time (e.g., the latest accumulative value T NE (K) of engine running time for the No. N machine shown in Fig. 8 ) (step S572). Thereafter, the processing section 51 classifies the calculated travel ratios and obtains a distribution of the number of operated machines with respect to the travel ratio (step S574). The thus-obtained distribution data is prepared in the form of a distribution graph, and the travel ratio of the machine corresponding to the inputted number is put in the distribution graph (S576).
  • the processing executed in steps S572 to S576 is the same as that executed in steps S522 to S526 shown in Fig. 22 .
  • the processing section 51 calculates, per machine number, a swing ratio (%) by dividing the past total swing time (e.g., the latest accumulative value T S (K) of swing time for the No. N machine shown in Fig. 8 ) by the past total engine running time (e.g., the latest accumulative value T NE (K) of engine running time for the No. N machine shown in Fig. 8 ), and obtains a value resulting from multiplying the calculated swing ratio by the bucket capacity (e.g., W A shown in Fig. 20 ) of the model A (step S578).
  • a swing ratio % by dividing the past total swing time (e.g., the latest accumulative value T S (K) of swing time for the No. N machine shown in Fig. 8 ) by the past total engine running time (e.g., the latest accumulative value T NE (K) of engine running time for the No. N machine shown in Fig. 8 ), and obtains a value resulting from multiplying the calculated swing
  • the term swing ratio represents a proportion of the swing time with respect to the total working time, i.e., a value indicating a rate at which the hydraulic excavator is used for swing.
  • the amount of work can be understood from a value resulting from multiplying the calculated swing ratio by the bucket capacity.
  • a rate of the amount of work performed by the hydraulic excavator is therefore estimated from the value resulting from multiplying the calculated swing ratio by the bucket capacity. That value is called a work amount index value hereinafter.
  • the processing section 51 classifies the work amount index values thus calculated, and obtains a distribution of the number of operated machines with respect to the work amount index value (step S580).
  • a distribution can be obtained in a similar manner to step S524 in Fig. 22 .
  • the work amount index value is divided into ranges at a unit width and the number of operated machines belonging to each range is calculated so that the number of operated machines is correlated with each range of the work amount index value.
  • the thus-obtained distribution data is prepared in the form of a distribution graph, and the work amount index value of the machine corresponding to the inputted number is put in the distribution graph (S582).
  • the processing section 51 calculates, per machine number, an excavation load ratio with respect to the past total front operating time (e.g., the latest accumulative value T D (K) of front operating time for the No. N machine shown in Fig. 8 ), and obtains a value resulting from multiplying the calculated excavation load ratio by the body weight of the model A (step S584).
  • an excavation load ratio with respect to the past total front operating time (e.g., the latest accumulative value T D (K) of front operating time for the No. N machine shown in Fig. 8 )
  • One method for calculating an excavation load ratio is as follows. Assuming the total front operating time to be, e.g., 1020 hours, a rate of time during which the excavation load is not smaller than a predetermined load, e.g., a pump pressure of 20 MPa, is calculated and set as an excavation load ratio.
  • a rate of time during which the excavation load is not smaller than a predetermined load e.g., a pump pressure of 20 MPa
  • the center of gravity of an integral value of the excavation load frequency distribution may be determined and set as an excavation load ratio.
  • the position of the center of gravity is indicated by a mark ⁇ in Fig. 29 .
  • excavation load ratio is a value representing a rate at which load acts upon the front in the total front operating time.
  • An excavation force of the hydraulic excavator can be obtained as a value resulting from multiplying the excavation load ratio by the body weight. That value is called an excavation force index value hereinafter.
  • the processing section 51 classifies the excavation force index values thus calculated, and obtains a distribution of the number of operated machines with respect to the excavation force index value (step S590). Such a distribution can be obtained in a similar manner to step S524 in Fig. 22 .
  • the thus-obtained distribution data is prepared in the form of a distribution graph, and the excavation force index value of the machine corresponding to the inputted number is put in the distribution graph (S592).
  • Fig. 30 is a flowchart showing details of the processing of evaluation executed in step S566 of the flowchart shown in Fig. 27 .
  • the processing section 51 accesses the database 100 and reads the operating time data and the machine body data for each machine of all models, respectively, from the operation database shown in Fig. 8 and the machine body database shown in Fig. 20 (step S600).
  • step S602 the distribution data of travel ratio is computed for all models.
  • a method for obtaining the distribution data of travel ratio is performed in the same manner as the processing executed in steps S572 and S574 of Fig. 28 except that the machine model A is replaced by all models.
  • the processing section 51 compares the thus-computed distribution data of travel ratio for all models with the travel ratio of the machine corresponding to the inputted number, and selects the distribution data having an average value of the travel ratio (i.e., the travel ratio at which the number of operated machines in the distribution data is maximum), which is closest to the travel ratio of the machine corresponding to the inputted number (step S604).
  • a distribution graph of the selected distribution data is plotted and superimposed on the distribution graph of the machine model A prepared in step S576 in the flowchart of Fig. 28 (step S606).
  • the processing section 51 similarly computes the distribution data for all models, selects the distribution data having an average value that is close to the index value of the machine corresponding to the inputted number, and superimposes a distribution graph of the selected distribution data on the distribution graph of the machine model A prepared in step S582 or S592 in the flowchart of Fig. 28 (steps S608, S610).
  • Figs. 31 to 33 each show one example of the evaluation result report prepared and outputted in the processing of step S568 in Fig. 27 .
  • Fig. 31 shows one example of the report showing, in a superimposed manner, not only a distribution graph of the number of operated machines with respect to the travel ratio for the machine model A and the travel ratio of the machine corresponding to the inputted number, but also a distribution graph for the machine model A TR (travel-enhanced type) having an average value of the travel ratio which is closest to the travel ratio of the machine corresponding to the inputted number.
  • the travel ratio of the machine corresponding to the inputted number is indicated by a vertical line in the distribution graphs.
  • a message Travel-enhanced model is recommended is added to the evaluation result.
  • Fig. 32 shows one example of the report showing, in a superimposed manner, not only a distribution graph of the number of operated machines with respect to the work amount index value (swing ratio x bucket capacity) for the machine model A and the work amount index value of the machine corresponding to the inputted number, but also a distribution graph for the machine model B (model of one rank-up level) having an average value of the work amount index value which is closest to the work amount index value of the machine corresponding to the inputted number.
  • the work amount index value of the machine corresponding to the inputted number is indicated by a vertical line in the distribution graphs.
  • a message Model B is recommended is added to the evaluation result.
  • Fig. 33 shows one example of the report showing, in a superimposed manner, not only a distribution graph of the number of operated machines with respect to the excavation force index value (excavation load ratio x body weight) for the machine model A and the excavation force index value of the machine corresponding to the inputted number, but also a distribution graph for the machine model C (model of one rank-down level) having an average value of the excavation force index value which is closest to the excavation force index value of the machine corresponding to the inputted number.
  • the excavation force index value of the machine corresponding to the inputted number is indicated by a vertical line in the distribution graphs.
  • a message Model C is recommended is added to the evaluation result.
  • an index value such as a travel ratio
  • Those three kinds of data are compared with one another to determine whether the particular hydraulic excavator is an optimum model.
  • a third embodiment of the present invention will be described with reference to Figs. 1 to 4 and 34 to 40 .
  • This embodiment is intended to confirm the state of use by detecting, instead of the operating time, the number of times of operations as a parameter representing the operation status for each section of a construction machine in the first embodiment.
  • a management system of a construction machine has the same overall arrangement as that of the first embodiment, and has a system arrangement similar to that of the first embodiment shown in Figs. 1 to 4 .
  • the machine side controller 2 has the function of collecting the operating time for each section of a hydraulic excavator, and correspondingly the machine body/operation information processing section 50 of the base station center server 3 has the function of processing the operating time. Further, the base station center server 3 includes the machine body information/optimum model evaluation processing section 51.
  • Fig. 34 is a flowchart showing the function of collecting the operating data for each section of the hydraulic excavator executed in the CPU 2c of the controller 2.
  • the CPU 2c first determines whether the engine revolution speed signal from the sensor 46 is of a value not lower than a predetermined revolution speed, and hence whether the engine is being operated (step S9). If it is determined that the engine is being operated, the CPU 2c reads data regarding the pilot pressure detection signals associated with the front, swing and track from the sensors 40, 41 and 42, and the pump pressure detection signal from the sensor 44 (step S10A).
  • the CPU 2c counts the number of times of each of front, swing and track operations, and stores and accumulates the counted result in the memory 2d in correspondence to the date and the time of day (step S12A).
  • the number of times of operations is counted up one when the pilot pressure exceeds a predetermined pressure.
  • the number of times of front operations is counted depending on, e.g., the pilot pressure for arm crowding that is essential in excavation work. The number of times of operations may be counted up one depending on each of the pilot pressures for operating the boom, the arm and the bucket.
  • step S14 an engine running time is stored and accumulated in the memory 2d (step S14).
  • step S16A the pump pressure after the lapse of a predetermined time (e.g., 2 to 3 seconds) is detected and then stored and accumulated in the memory 2d in correspondence to the number of times of operations (step S16A).
  • a predetermined time e.g. 2 to 3 seconds
  • the machine body/operation information thus stored and accumulated is transmitted to the base station center server 3 once a day, as described above in connection with the first embodiment with reference to Fig. 6 .
  • Fig. 35 is a flowchart showing the processing function of the machine body/operation information processing section 50 in the center server 3 executed when the machine body/operation information is transmitted from the machine side controller 2.
  • the machine body/operation information processing section 50 monitors whether the machine body/operation information (the number of times of each of front, swing and track operations, the pump pressure, and the engine running time) is inputted from the machine side controller 2 (step S30A).
  • the processing section 50 reads the inputted information, and then stores and accumulates it as operation data in the database 100 (step S32A).
  • the processing section 50 then reads the operation data for a predetermined number of days, e.g., one month, out of the database 100 and makes a daily report regarding the operating data (step S34A). Thereafter, the thus-prepared daily report and a maintenance report are transmitted to the in-house computer 4 and the user side computer 5 (step S40).
  • Fig. 36 shows how the operation data is stored in the database 100.
  • the engine running time, the number of times of front operations (the number of times of excavations), the number of times of swing operations, and the number of times of track operations are stored as an operation database per machine model and number in the form of accumulative values in correspondence to the date.
  • T NE (1) and S D (1) represent respectively an accumulative value of the engine running time and an accumulative value for the number of times of front operations for a No. N machine of model A as of January 1, 2000.
  • T NE (K) and S D (K) represent respectively an accumulative value of the engine running time and an accumulative value for the number of times of front operations for the No. N machine of model A as of March 16, 2000.
  • accumulative values S S (1) to S S (K) for the number of times of swing operations and accumulative values S T (1) to S T (K) for the number of times of track operations for the No. N machine of model A are stored in correspondence to the date. Similar data is also stored for a No. N+1 machine, a No. N+2 machine, etc. of models A, B, C, etc.
  • the pump load frequency distribution is stored and accumulated for each of the front, swing and track operations in correspondence to the date.
  • the number of times of front operations is stored in an area for the front operation dated January 1, 2000 for each pump pressure zone of 5 MPa; e.g., from 0 MPa to 5 MPa: 12 times, from 5 MPa to 10 MPa: 32 times, ..., from 25 MPa to 30 MPa: 28 times, and not lower than 30 MPa: 9 times.
  • the pump load frequency distribution is also similarly stored in areas for the swing and track operations and areas for the subsequent dates.
  • the machine body information/optimum model evaluation processing section 51 of the base station center server 3 has, as with the first embodiment, the function of processing the machine body information per model and the function of processing a request for evaluating an optimum model.
  • the function of processing the machine body information per model is the same as that in the first embodiment described with reference to Figs. 19 and 20 .
  • Fig. 37 is a flowchart showing the function of processing a request for evaluating an optimum model executed in the machine body information/optimum model evaluation processing section 51 of the center server 3, and Fig. 38 is a flowchart showing details of processing executed in step S514A of Fig. 37 .
  • the processing executed in steps S510 and S512 of Fig. 37 is the same as that in the first embodiment.
  • step S514A of Fig. 37 the processing section 51 computes an index value of a hydraulic excavator corresponding to the inputted number for each index item regarding the state of use of the hydraulic excavator, obtains a distribution of the number of operated machines with respect to index values, and plots a distribution graph through the processing shown in Fig. 38 .
  • the processing section 51 accesses the database 100 and reads the operation data for each machine number of the model A from the operation database shown in Fig. 36 (step S520A). Then, the processing section 51 calculates, per machine number, a travel ratio (%) by calculating the past total number of times of operations, which is resulted from adding the total number of front operations (e.g., the latest accumulative value S D (K) for the number of times of front operations for the No. N machine shown in Fig.
  • a travel ratio % by calculating the past total number of times of operations, which is resulted from adding the total number of front operations (e.g., the latest accumulative value S D (K) for the number of times of front operations for the No. N machine shown in Fig.
  • the processing section 51 classifies the travel ratios calculated per machine number and obtains a distribution of the number of operated machines with respect to the travel ratio (step S524).
  • the thus-obtained distribution data is prepared in the form of a distribution graph, and the travel ratio of the machine corresponding to the inputted number is put in the distribution graph (S526).
  • the distribution data is obtained for a pump load ratio as another index, and a distribution graph including the pump load ratio of the machine corresponding to the inputted number is plotted (steps S528A to S532).
  • the term pump load ratio represents a proportion of the number of times of operations in which the pump load pressure is not lower than a predetermined pressure, with respect to the total number of times of operations per machine number.
  • the number of times of operations in which the pump load pressure is not lower than the predetermined pressure can be obtained, from the pump load frequency distribution for all of the front, swing and track operations shown in Fig. 36 , by totalizing the number of times of each of those operations in which the pump load pressure is not lower than the predetermined pressure.
  • the pump load ratio is a value representing a rate at which the hydraulic excavator is used for works under high load, and the predetermined pump pressure is set to, e.g., about 15 MPa.
  • indices such as an excavation load ratio (number of times of excavations / total number of times of operations) and a swing load ratio (number of times of swing operations / total number of times of operations), can also be set as required, and a distribution graph for each index can be obtained in a similar manner.
  • the processing section 51 evaluates whether the hydraulic excavator corresponding to the inputted machine number is an optimum model, and then prepares and outputs a report of the evaluation result similarly to the first embodiment.
  • Figs. 39 and 40 each show one example of the evaluation result report prepared and outputted in the processing of step S518A in Fig. 37 .
  • a fourth embodiment of the present invention will be described with reference to Figs. 1 to 4 , 20 , 36 , and 41 to 46 .
  • This embodiment is intended to confirm the state of use by detecting, instead of the operating time, the number of times of operations as a parameter representing the operation status for each section of a construction machine in the second embodiment.
  • a management system of a construction machine has the same overall arrangement as that of the first embodiment, and has a system arrangement similar to that of the first embodiment shown in Figs. 1 to 4 .
  • the processing function of the machine side controller 2 and the processing function of the machine body/operation information processing section 50 in the base station center server 3 are the same as those in the third embodiment.
  • the machine body information/optimum model evaluation processing section 51 of the base station center server 3 has the function of processing the machine body information per model, which is similar to that in the first embodiment. Also, the processing section 51 has the function of processing a request for evaluating an optimum model as described below.
  • Fig. 41 is a flowchart showing the function of processing a request for evaluating an optimum model executed in the processing section 51 of the center server 3, and Fig. 42 is a flowchart showing details of processing executed in step S564A of Fig. 41 .
  • the processing executed in steps S510 and S512 of Fig. 41 is the same as that in the first embodiment.
  • step S564A of Fig. 41 through the processing shown in Fig. 42 , the processing section 51 computes an index value of a hydraulic excavator corresponding to the inputted number for each index item regarding the state of use of the hydraulic excavator, obtains a distribution of the number of operated machines with respect to index values, and plots a distribution graph.
  • the processing section 51 accesses the database 100 and reads the operating data and the machine body data for each machine number of the model A (i.e., the model read in step S512 of Fig. 41 ), respectively, from the operation database shown in Fig. 36 and the machine body database shown in Fig. 20 (step S570A).
  • the processing section 51 calculates, per machine number, a travel ratio (%) by calculating the past total number of times of operations, which is resulted from adding the total number of front operations (e.g., the latest accumulative value S D (K) for the number of times of front operations for the No. N machine shown in Fig. 36 ), the total number of times of swing operations (S S (K)) and the total number of times of track operations (T T (K)), and then dividing the total number of times of track operations (T T (K)) by the past total number of times of operations (step S572A).
  • the total number of front operations e.g., the latest accumulative value S D (K) for the number of times of front operations for the No. N machine shown in Fig. 36
  • S S (K) total number of times of swing operations
  • T T (K) total number of times of track operations
  • the processing section 51 classifies the calculated travel ratios and obtains a distribution of the number of operated machines with respect to the travel ratio (step S574).
  • the thus-obtained distribution data is prepared in the form of a distribution graph, and the travel ratio of the machine corresponding to the inputted number is put in the distribution graph (S576).
  • the processing section 51 calculates, per machine number, a swing ratio (%) by dividing the past total number of times of swing operations (S S (K)) by the past total number of times of operations calculated above, and obtains a value resulting from multiplying the calculated swing ratio by the bucket capacity (e.g., W A shown in Fig.
  • step S578A a work amount index value
  • step S580 a distribution of the number of operated machines with respect to the work amount index value is obtained.
  • the thus-obtained distribution data is prepared in the form of a distribution graph, and the work amount index value of the machine corresponding to the inputted number is put in the distribution graph (S582).
  • the processing section 51 calculates, per machine number, an excavation load ratio with respect to the past total number of times of front operations, and obtains a value resulting from multiplying the calculated excavation load ratio by the body weight of the model A, i.e., an excavation force index value (step S584A).
  • a load ratio of the excavation load frequency distribution is computed. For example, a rate of the number of times of front operations, in which the excavation load is not smaller than a predetermined load, e.g., a pump pressure of 20 MPa, with respect to the total number of times of front operations is calculated and set as an excavation load ratio.
  • a predetermined load e.g., a pump pressure of 20 MPa
  • the center of gravity (mark x) of an integral value of the excavation load frequency distribution, shown in Fig. 43 may be determined and set as an excavation load ratio. The position of the center of gravity is indicated by a mark x in Fig. 29 .
  • the processing section 51 classifies the excavation force index values thus calculated, and obtains a distribution of the number of operated machines with respect to the excavation force index value (step S590).
  • the thus-obtained distribution data is prepared in the form of a distribution graph, and the excavation force index value of the machine corresponding to the inputted number is put in the distribution graph (S592).
  • step S566A and S568A the processing section 51 evaluates whether the hydraulic excavator corresponding to the inputted machine number is an optimum model, and then prepares and outputs a report of the evaluation result similarly to the second embodiment.
  • the evaluation processing of step S566A in Fig. 41 is executed by using, instead of the operating time, the number of times of operations in the detailed processing of steps S600, S602, S608 and S610 shown in Fig. 30 in connection with the second embodiment similarly to the processing of Fig. 42 .
  • step S568A of Fig. 41 reports shown in Figs. 44 to 46 are prepared and outputted.
  • a fifth embodiment of the present invention will be described with reference to Figs. 47 to 49 .
  • This embodiment is intended to modify the measured operation status for each section of a construction machine for an improvement in accuracy of an index value regarding the state of use of the construction machine, and to realize more appropriate evaluation of an optimum model.
  • Fig. 47 is a flowchart showing the processing function of the machine body/operation information processing section 50 in the center server 3 executed when the machine body/operation information is transmitted from the machine side controller 2.
  • step S33A the accumulative value for the number of times of each of front, swing and track operations is read out, modified depending on load, and stored in the database again.
  • Fig. 48 is a flowchart showing details of processing to modify the number of times of operations depending on load.
  • the processing section 51 first determines whether the machine number N is not greater than Z (step S600). If N is not greater than Z, the pump load frequency distribution in a front operation area for the No. N machine is read for all working days out of the operation database shown in Fig. 36 , and then classified to obtain an excavation load frequency distribution (step S602). This process is the same as that used to obtain the excavation load frequency distribution for computing the excavation load ratio in step S584A of Fig. 42 in the fourth embodiment, and the obtained excavation load frequency distribution is as shown in Fig. 43 . Then, an average excavation load D M per front operation is computed (step S604).
  • the average excavation load D M is determined, for example, by calculating the products of respective pump pressures and the number of times of front operations based on the excavation load ratio distribution, shown in Fig. 43 , which is obtained in step S602, and then dividing the sum of those products by the number of times of front operations.
  • the average excavation load D M may be determined by obtaining the position of the center of gravity (mark x) of an integral value of the excavation load frequency distribution shown in Fig. 43 , and setting the pump pressure at the position of the center of gravity as D M .
  • a load modifying coefficient ⁇ is derived from the average excavation load D M (step S606). That process is executed using the preset relationship between the average excavation load D M and the load modifying coefficient ⁇ , which is shown, by way of example, in Fig. 49 .
  • step S608 After obtaining the load modifying coefficient ⁇ as described above, the latest accumulative value S D (K) for the number of times of front operations is read out of the operation database shown in Fig. 36 , and the read-out accumulative value S D (K) is modified with the load modifying coefficient ⁇ , thereby obtaining the number S' D (K) of times of operations as given below (step S608):
  • S ⁇ D K S D K ⁇ ⁇
  • the thus-obtained number S' D (K) of times of operations is stored in the database 100 as the number of times of operations modified depending on load.
  • the number of times of operations modified depending on load is similarly obtained and stored in the database 100 (steps S610 and S620). Then, the above-described processing is executed for all of the machine numbers 1 to Z to obtain the number of times of operations modified depending on load for each of all hydraulic excavators of the model A, which is also stored in the database 100. Similarly, the number of times of operations modified depending on load is further obtained for each of all hydraulic excavators of other models such as B, and then stored in the database 100 (step S630).
  • the number of times of operations can be modified depending on load in a like manner.
  • the state of use of the machine varies depending on the amount of load of each section as well.
  • the measured operation status (operating time or number of times of operations) for each section is modified depending on load, and the load-dependent modified operation status (operating time or number of times of operations) is statistically processed to confirm how the customer employs the owned hydraulic excavator in practice. Therefore, whether the owned hydraulic excavator is an optimum model for the customer can be evaluated after compensating for differences in the state of use caused by differences in load. It is hence possible to give an advice about the optimum model more appropriately depending on the state of use.
  • an optimum model evaluation processing section (step S516 in Fig. 21 and step S566 in Fig. 27 ) is provided in an evaluating system so that the evaluating system determines by itself whether the particular hydraulic excavator is an optimum model.
  • whether the particular hydraulic excavator is an optimum model may be determined by any suitable person, such as a serviceman, by directly outputting two kinds of data, i.e., a value of an operation status variable of the particular hydraulic excavator and a distribution of the number of operated hydraulic excavators of the same model as the particular hydraulic excavator with respect to the operation status variable, or three kinds of data, i.e., the above twos and a distribution of the number of operated hydraulic excavators of different model having an average value of the operation status variable, which is close to the value of the operation status variable of the particular hydraulic excavator.
  • the data and graph for a distribution of the number of hydraulic excavators working in fields with respect to the operating time thereof are prepared and transmitted everyday in the center server 3 along with preparation and transmission of a daily report.
  • processing is not necessarily required to be made everyday, and may be executed at different frequencies such that the distribution data is prepared everyday and the distribution graph is plotted and transmitted once a week.
  • the distribution data may be automatically prepared in the center server 3, and the distribution graph may be plotted and transmitted in response to an instruction from the serviceman using the in-house computer.
  • both the distribution data and the distribution graph may be prepared and transmitted in response to an instruction from the serviceman.
  • the machine body information/optimum model evaluation processing section 51 of the center server 3 executes the whole of the processing to evaluate an optimum model whenever data is inputted from the in-house computer.
  • the amount of processing required for evaluating whether the particular hydraulic excavator is an optimum model may be reduced by previously obtaining the distribution data for all machine models and all operation status variables, and storing the obtained distribution data as a database. This enables the customer to know the evaluation result with a faster response.
  • the engine running time is measured using the engine revolution speed sensor 46, it may be measured by a combination of a timer and a signal resulting from detecting turning-on/off of the engine key switch by the sensor 43. As an alternative, the engine running time may be measured by a combination of a timer and turning-on/off of a power generation signal from an alternator associated with the engine, or by rotating an hour meter with power generated by the alternator.
  • center server 3 While the information created by the center server 3 is transmitted to the user-side and in-house computers, it may also be returned to the side of the hydraulic excavator 1.
  • a value of an operation status variable of a particular construction machine and a distribution of the number of operated construction machines of the same model as the particular construction machine with respect to the operation status variable are obtained from operation data including an operating time for each section of the construction machine, and are compared with each other to determine whether the particular construction machine is an optimum model. Therefore, how the customer employs the owned construction machine (particular construction machine) in practice can be confirmed from comparison with other construction machines of the same model. It is hence possible to give an advice about the optimum model depending on the state of work.
  • a value of an operation status variable of a particular construction machine, a distribution of the number of operated construction machines of the same model as the particular construction machine with respect to the operation status variable, and a distribution of the number of operated construction machines of different model with respect to the operation status variable are obtained from operation data including an operating time for each section of the construction machine, and are compared with one another to determine whether the particular construction machine is an optimum model. Therefore, how the customer employs the owned construction machine (particular construction machine) in practice can be confirmed from comparison with other construction machines of the same model and other construction machines of different model. It is hence possible to give an advice about the optimum model more appropriately depending on the state of work.

Landscapes

  • Engineering & Computer Science (AREA)
  • Mining & Mineral Resources (AREA)
  • Civil Engineering (AREA)
  • General Engineering & Computer Science (AREA)
  • Structural Engineering (AREA)
  • Physics & Mathematics (AREA)
  • General Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • Health & Medical Sciences (AREA)
  • Economics (AREA)
  • General Health & Medical Sciences (AREA)
  • Human Resources & Organizations (AREA)
  • Marketing (AREA)
  • Primary Health Care (AREA)
  • Strategic Management (AREA)
  • Tourism & Hospitality (AREA)
  • General Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • Operation Control Of Excavators (AREA)

Claims (14)

  1. Verfahren zum Verwalten einer Baumaschine, das die Schritte umfasst:
    einen ersten Schritt (S9-14, S20-24, S30-32, S89-94, S240-246), bei dem ein Betriebszustand jedes Funktionssegments (12, 13, 15, 32) einer jeden Baumaschine aus einer Mehrzahl von Baumaschinen (1, 1a, 1b, 1c) gemessen wird, wobei die Baumaschinen in verschiedenen Bereichen arbeiten und verschiedene Modelle umfassen, wobei der gemessene Betriebszustand zu einem Basisstationscomputer (3) übertragen wird und dann der gemessene Betriebszustand gespeichert und als Betriebsdaten in einer Datenbank (100) gesammelt wird,
    gekennzeichnet durch einen zweiten Schritt (S500-502, S510-518, S510-568), bei dem in dem Basisstationscomputer die Betriebsdaten statistisch verarbeitet werden und Bewertungsdaten erzeugt und ausgegeben werden zur Bestimmung, ob eine spezielle aus einer Mehrzahl von Baumaschinen ein optimales Modell ist, wobei der zweite Schritt einen dritten Schritt (S514) aufweist, bei dem als Bewertungsdaten ein Wert mindestens eines Indexes betreffend den Benutzungsstatus der speziellen Baumaschine aus einer Mehrzahl von Baumaschinen (1, 1a, 1b, 1c) auf der Grundlage der Betriebsdaten berechnet wird und wobei auf der Grundlage des berechneten Indexwertes entschieden wird, ob die spezielle Baumaschine ein optimales Modell ist.
  2. Verfahren zum Verwalten einer Baumaschine nach Anspruch 1, wobei der zweite Schritt ferner einen vierten Schritt (S514) aufweist,
    bei dem als Bewertungsdaten ein Wert des Indexes für jede Baumaschine vom selben Modell wie die spezielle Baumaschine auf der Grundlage der Betriebsdaten berechnet wird, wobei eine erste Korrelation zwischen dem Index und der Anzahl der betätigten Baumaschinen erhalten wird, wobei der Indexwert der speziellen Baumaschine mit der ersten Korrelation verglichen wird, um zu bestimmen, ob die spezielle Baumaschine ein optimales Modell ist.
  3. Verfahren zum Verwalten einer Baumaschine nach Anspruch 2, wobei der zweite Schritt ferner einen fünften Schritt (S564) aufweist, bei dem als Bewertungsdaten ein Wert des Indexes für jede Baumaschine mindestens eines Modells von verschiedenen Modellen der Mehrzahl von Baumaschinen (1, 1a, 1b, 1c) basierend auf den Betriebsdaten berechnet wird, wobei sich das Modell von dem Modell der speziellen Baumaschine unterscheidet, wodurch eine zweite Korrelation zwischen dem Index und der Anzahl der betriebenen Baumaschinen erhalten wird, und wobei der Indexwert der speziellen Baumaschine mit den ersten und zweiten Korrelationen verglichen wird, um zu bestimmen, ob die spezielle Baumaschine ein optimales Modell ist.
  4. Verfahren zum Verwalten einer Baumaschine nach Anspruch 1, wobei im ersten Schritt (S9-S16A, S30-32A) eine Last für jedes Funktionssegment zusätzlich zu dem Betriebszustand für jedes Funktionssegment gemessen wird, und die gemessene Last in der Datenbank des Basisstationscomputers (3) gespeichert und gesammelt wird, und wobei der zweite Schritt ferner einen sechsten Schritt (S33A) aufweist, bei dem der gemessene Betriebszustand in Abhängigkeit von dem Wert der gemessenen Last geändert wird, und Bewertungsdaten erzeugt werden, indem als Betriebsdaten der lastabhängige geänderte Betriebstatus verwendet wird.
  5. Verfahren zum Verwalten einer Baumaschine nach einem der Ansprüche 1 bis 4, wobei der Betriebsstatus repräsentiert wird durch die Betriebszeit und/oder die Anzahl der Betriebsvorgänge.
  6. Verfahren zum Verwalten einer Baumaschine nach einem der Ansprüche 1 bis 4, wobei die Baumaschine ein Hydraulikbagger (1, 1a, 1b, 1c) ist, und das Funktionssegment entweder die stirnseitige Vorrichtung (15), der Schwenkkörper (13), der Raupenkörper (12) oder der Motor (32) des hydraulischen Baggers ist.
  7. Verfahren zum Verwalten einer Baumaschine nach einem der Ansprüche 1 bis 4, wobei die Baumaschine ein Hydraulikbagger (1, 1a, 1b, 1c) ist und die Funktionssegmente eine stirnseitige Vorrichtung (15), einen Schwenkkörper (13), einen Raupenkörper (12) und einen Motor (32) des Hydraulikbaggers umfassen, und der Betriebsstatus repräsentiert wird durch eine Betriebszeit sowohl der stirnseitigen Vorrichtung, des Schwenkkörpers, des Raupenkörpers als auch des Motors, und wobei der Index mindestens einen der folgenden Werte beinhaltet: das Verhältnis der Motorlaufzeit zu der Fahrzeit, das Verhältnis der Motorlaufzeit zu der Zeit, während der ein Pumpendruck nicht kleiner ist als ein vorbestimmter Wert, das Produkt aus dem Verhältnis der Motorlaufzeit zu einer Schwenkzeit, und einer Schaufelkapazität, und das Produkt aus dem Verhältnis der Motorlaufzeit zu einer Ausgrabzeit und einem Baggerkörpergewicht.
  8. Verfahren zum Verwalten einer Baumaschine nach einem der Ansprüche 1 bis 4, wobei die Baumaschine ein Hydraulikbagger (1, 1a, 1b, 1c) ist, und die Funktionssegmente eine stirnseitige Vorrichtung (15), einen Schwenkkörper (13) und einen Raupenkörper (12) des Hydraulikbaggers umfassen, wobei der Betriebsstatus repräsentiert wird durch die Anzahl der Betriebsvorgänge sowohl der stirnseitigen Vorrichtung, des Schwenkkörpers als auch des Raupenkörpers, und wobei der Index mindestens einen der folgenden Werte umfasst: das Verhältnis der Gesamtzahl der Betriebszeiten zu der Anzahl der Raupenbetätigungen, das Verhältnis der Gesamtzahl der Betätigungen zu der Anzahl der Betätigungen, bei denen ein Pumpendruck nicht kleiner ist als ein vorbestimmter Wert, das Produkt aus dem Verhältnis der Gesamtzahl der Betätigungen zu der Anzahl der Raupenbetätigungen, und einer Schaufelkapazität, und das Produkt aus dem Verhältnis der Gesamtzahl der Betätigungen zu der Anzahl der Betätigungen der stirnseitigen Vorrichtung und dem Baggerkörpergewicht.
  9. System zum Verwalten einer Baumaschine mit:
    Mitteln (2, 40-46, S9-14, S20-24, S89-94) zum Messen und Sammeln von Daten, die für jedes Funktionssegment (12, 13, 15, 32) einer jeden Baumaschine von einer Mehrzahl von Baumaschinen (1, 1a, 1b, 1c), die in verschiedenen Bereichen arbeiten und verschiedene Modelle umfassen, ein Betriebstatus messen und sammeln,
    gekennzeichnet durch einen Basisstationscomputer (3, 50, S30-32, S240-246), der in einer Basisstation installiert ist und eine Datenbank (100) aufweist, in der der für jedes Funktionssegment gemessene und gesammelte Betriebsstatus als Betriebsdaten gespeichert und gesammelt wird,
    wobei der Basisstationscomputer Rechenmittel (51, S500-502, S510-518, S510-568) aufweist zum statistischen Bearbeiten der Betriebsdaten, um Bewertungsdaten zur Bestimmung, ob eine spezielle Baumaschine der Mehrzahl von Baumaschinen ein optimales Modell ist, zu erzeugen und auszugeben,
    wobei die Rechenmittel erste Mittel (51, S514) aufweisen zum Berechnen, als Bewertungsdaten, eines Werts mindestens eines Indexes bezüglich des Benutzungszustands einer speziellen Baumaschine (1, 1a, 1b, 1c) aus einer Mehrzahl von Baumaschinen auf der Grundlage der Betriebsdaten, und wobei auf der Grundlage des berechneten Indexwertes bestimmt wird, ob eine spezielle Baumaschine ein optimales Modell ist.
  10. System zum Verwalten einer Baumaschine nach Anspruch 9, wobei die Rechenmittel ferner zweite Mittel (51, S514) aufweisen zum Berechnen, als Bewertungsdaten, eines Wertes des Index für jede Baumaschine desselben Modells wie die spezielle Baumaschine auf der Grundlage der Betriebsdaten, wodurch eine erste Korrelation zwischen dem Index und der Anzahl betätigten Baumaschinen erhalten wird und wobei der Indexwert der speziellen Baumaschine mit der ersten Korrelation verglichen wird, um zu bestimmen, ob die spezielle Baumaschine ein optimales Modell ist.
  11. System zum Verwalten einer Baumaschine nach Anspruch 10, wobei die Rechenmittel ferner dritte Mittel (51, S516) aufweisen zum Vergleichen des Indexwertes der speziellen Baumaschine mit der ersten Korrelation, um zu bestimmen, ob die spezielle Baumaschine ein optimales Modell ist.
  12. System zum Verwalten einer Baumaschine nach Anspruch 10, wobei die Rechenmittel ferner vierte Mittel (51, S564) aufweisen zum Berechnen, als Bewertungsdaten, eines Indexwertes für jede Baumaschine mindestens eines der verschiedenen Modelle der Mehrzahl von Baumaschinen (1, 1a, 1b, 1c), welches sich von dem Modell der speziellen Baumaschine unterscheidet, auf der Grundlage von Betriebsdaten, wodurch eine zweite Korrelation zwischen dem Index und der Anzahl der betätigten Baumaschinen erhalten wird und wobei der Indexwert der speziellen Baumaschine mit der ersten und der zweiten Korrelation verglichen wird, um zu bestimmen, ob die spezielle Baumaschine ein optimales Modell ist.
  13. System zum Verwalten einer Baumaschine nach Anspruch 12, wobei die Rechenmittel ferner fünfte Mittel (51, S566) aufweisen zum Vergleichen des Indexwertes der speziellen Baumaschine mit den ersten und zweiten Korrelationen, um zu bestimmen, ob die spezielle Baumaschine ein optimales Modell ist.
  14. System zum Verwalten einer Baumaschine nach Anspruch 9, wobei die Mittel (2, 40-46, S9-S16A) zum Messen und Sammeln von Daten zusätzlich zu dem Betriebsstatus für jedes Funktionssegment (12, 13, 15, 32) eine Last für jedes Funktionssegment messen und sammeln, wobei der Basisstationscomputer (3, 50, S30-32A) den Betriebsstatus und die Last, gemessen und gesammelt für jedes Funktionssegment, als Betriebsdaten in der Datenbank (100) speichert und sammelt, und
    wobei die Rechenmittel ferner sechste Mittel (51, S33A) aufweisen zum Verändern des gemessenen Betriebsstatus in Abhängigkeit von dem Wert der gemessenen Last, und wobei diese Mittel Bewertungsdaten erzeugen, indem als Betriebsdaten der lastabhängige geänderte Betriebstatus verwendet wird.
EP01921782A 2000-03-31 2001-04-02 Verfahren und system zur verwaltung einer baumaschine und arithmetische verarbeitungseinheit Expired - Lifetime EP1262604B1 (de)

Applications Claiming Priority (3)

Application Number Priority Date Filing Date Title
JP2000098118 2000-03-31
JP2000098118 2000-03-31
PCT/JP2001/002853 WO2001073226A1 (fr) 2000-03-31 2001-04-02 Procede et systeme de gestion d'une machine de construction et appareil de traitement arithmetique

Publications (3)

Publication Number Publication Date
EP1262604A1 EP1262604A1 (de) 2002-12-04
EP1262604A4 EP1262604A4 (de) 2009-11-11
EP1262604B1 true EP1262604B1 (de) 2011-08-03

Family

ID=18612642

Family Applications (1)

Application Number Title Priority Date Filing Date
EP01921782A Expired - Lifetime EP1262604B1 (de) 2000-03-31 2001-04-02 Verfahren und system zur verwaltung einer baumaschine und arithmetische verarbeitungseinheit

Country Status (6)

Country Link
US (1) US6449884B1 (de)
EP (1) EP1262604B1 (de)
JP (1) JP4170622B2 (de)
KR (1) KR100460483B1 (de)
CN (1) CN1153873C (de)
WO (1) WO2001073226A1 (de)

Families Citing this family (26)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN1221913C (zh) * 2000-03-31 2005-10-05 日立建机株式会社 建筑机械的管理方法,系统以及运算处理装置
DE10057972A1 (de) * 2000-11-22 2002-07-18 Zahnradfabrik Friedrichshafen Ermittlung von Getriebekenngrößen
JPWO2003000997A1 (ja) * 2001-06-20 2004-10-14 日立建機株式会社 建設機械の遠隔制御システム及び遠隔設定システム
US6739078B2 (en) * 2001-08-16 2004-05-25 R. Morley, Inc. Machine control over the web
JP3948286B2 (ja) * 2002-01-15 2007-07-25 日立建機株式会社 建設機械の管理システム及び管理方法
US7607245B2 (en) * 2002-09-26 2009-10-27 Hitachi Construction Machinery Co., Ltd. Construction machine
US7983820B2 (en) 2003-07-02 2011-07-19 Caterpillar Inc. Systems and methods for providing proxy control functions in a work machine
JP4246039B2 (ja) * 2003-11-18 2009-04-02 日立建機株式会社 建設機械の稼働情報管理装置
US20060041845A1 (en) * 2004-05-20 2006-02-23 Caterpillar Inc. Systems and methods for exchanging display data between machines
US7640683B2 (en) * 2005-04-15 2010-01-05 Topcon Positioning Systems, Inc. Method and apparatus for satellite positioning of earth-moving equipment
US7873455B2 (en) * 2006-09-25 2011-01-18 Cnh America Llc Work vehicle access monitoring and control system
US7925439B2 (en) * 2006-10-19 2011-04-12 Topcon Positioning Systems, Inc. Gimbaled satellite positioning system antenna
US7725294B2 (en) * 2007-12-04 2010-05-25 Clark Equipment Company Power machine diagnostic system and method
US20100145865A1 (en) * 2008-05-16 2010-06-10 Berger Thomas R Managing and securing construction and rental equipment
JP5350916B2 (ja) * 2009-07-03 2013-11-27 日立建機株式会社 排気浄化装置の管理システム、排気浄化装置の管理方法
AU2011252966B2 (en) 2010-05-14 2014-10-23 Joy Global Surface Mining Inc Cycle decomposition analysis for remote machine monitoring
US20130190933A1 (en) * 2012-01-20 2013-07-25 International Business Machines Corporation Energy efficient air flow control
AU2012390438B2 (en) * 2012-09-21 2016-04-14 Hitachi Construction Machinery Co., Ltd. Operation management device of self-propelled mining equipment
KR101947188B1 (ko) * 2013-01-11 2019-04-22 현대건설기계 주식회사 건설장비 또는 산업차량의 사용과 관련된 특정시간을 관리하는 아워 미터 및 이에 의한 관리방법
US20140372427A1 (en) * 2013-06-13 2014-12-18 Sap Portals Israel Ltd Real-time analytic report analysis and retrieval framework
EP3210089A1 (de) * 2014-10-23 2017-08-30 Carrier Corporation Wartungsüberwachungsanlage für eine mobile ausrüstung
JP6392101B2 (ja) * 2014-12-05 2018-09-19 日立建機株式会社 建設機械の管理システム
JP7036606B2 (ja) * 2018-01-31 2022-03-15 株式会社小松製作所 積込機械の制御装置および制御方法
KR102564721B1 (ko) * 2019-03-26 2023-08-08 히다찌 겐끼 가부시키가이샤 작업 기계
CN112581155A (zh) * 2019-09-30 2021-03-30 北京国双科技有限公司 一种数据处理方法及装置
WO2023018808A1 (en) * 2021-08-11 2023-02-16 Oshkosh Corporation Work equipment utilization monitoring system and method

Family Cites Families (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JPH0317321A (ja) * 1989-06-15 1991-01-25 Komatsu Ltd メンテナンスモニタ装置
JP2584371B2 (ja) 1991-09-11 1997-02-26 株式会社小糸製作所 自動車用標識灯
JP2584371Y2 (ja) * 1992-10-12 1998-10-30 株式会社小松製作所 パワーショベルの作動状況把握装置
US5737215A (en) * 1995-12-13 1998-04-07 Caterpillar Inc. Method and apparatus for comparing machines in fleet
JP3335106B2 (ja) 1997-07-16 2002-10-15 株式会社小松製作所 機械のメンテナンス時期判定方法および装置
JP2000027236A (ja) * 1998-07-07 2000-01-25 Komatsu Ltd 建設機械のデータ記憶装置およびデータ処理装置

Also Published As

Publication number Publication date
EP1262604A1 (de) 2002-12-04
CN1153873C (zh) 2004-06-16
WO2001073226A1 (fr) 2001-10-04
JP4170622B2 (ja) 2008-10-22
US6449884B1 (en) 2002-09-17
KR20020020703A (ko) 2002-03-15
KR100460483B1 (ko) 2004-12-08
CN1366569A (zh) 2002-08-28
EP1262604A4 (de) 2009-11-11

Similar Documents

Publication Publication Date Title
EP1262604B1 (de) Verfahren und system zur verwaltung einer baumaschine und arithmetische verarbeitungseinheit
EP1286003B1 (de) Verfahren zur verwaltung einer baumaschine und rechnereinheit
EP1273718B1 (de) Verfahren und system zum verwalten einer baumaschine
EP2228493A2 (de) Procédé et système de gestion de machine de construction et appareil de traitement
US8073653B2 (en) Component life indicator
US7333922B2 (en) System and method of monitoring machine performance
JP6298797B2 (ja) 建設機械の交換品管理システム
US9637891B2 (en) Management server for working machine and management method for working machine
US7693633B2 (en) Machine operational data collection and reporting system
JP4689136B2 (ja) 作業現場に配備された作業機械の実稼動時間の検出方法、データ収集・管理システム、および基地局
US20070150295A1 (en) Asset management system
US20090006153A1 (en) Evaluation tool for adjusting resale of machine components
WO2007040822A1 (en) Asset management system
JP2008008144A (ja) 建設機械の情報管理装置

Legal Events

Date Code Title Description
PUAI Public reference made under article 153(3) epc to a published international application that has entered the european phase

Free format text: ORIGINAL CODE: 0009012

17P Request for examination filed

Effective date: 20020325

AK Designated contracting states

Kind code of ref document: A1

Designated state(s): AT BE CH CY DE DK ES FI FR GB GR IE IT LI LU MC NL PT SE TR

RBV Designated contracting states (corrected)

Designated state(s): DE FR GB IT SE

A4 Supplementary search report drawn up and despatched

Effective date: 20090903

17Q First examination report despatched

Effective date: 20100506

GRAP Despatch of communication of intention to grant a patent

Free format text: ORIGINAL CODE: EPIDOSNIGR1

GRAS Grant fee paid

Free format text: ORIGINAL CODE: EPIDOSNIGR3

GRAA (expected) grant

Free format text: ORIGINAL CODE: 0009210

AK Designated contracting states

Kind code of ref document: B1

Designated state(s): DE FR GB IT SE

REG Reference to a national code

Ref country code: GB

Ref legal event code: FG4D

REG Reference to a national code

Ref country code: DE

Ref legal event code: R096

Ref document number: 60145074

Country of ref document: DE

Effective date: 20110929

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: SE

Free format text: LAPSE BECAUSE OF FAILURE TO SUBMIT A TRANSLATION OF THE DESCRIPTION OR TO PAY THE FEE WITHIN THE PRESCRIBED TIME-LIMIT

Effective date: 20110803

PLBE No opposition filed within time limit

Free format text: ORIGINAL CODE: 0009261

STAA Information on the status of an ep patent application or granted ep patent

Free format text: STATUS: NO OPPOSITION FILED WITHIN TIME LIMIT

26N No opposition filed

Effective date: 20120504

REG Reference to a national code

Ref country code: DE

Ref legal event code: R097

Ref document number: 60145074

Country of ref document: DE

Effective date: 20120504

REG Reference to a national code

Ref country code: FR

Ref legal event code: ST

Effective date: 20121228

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: FR

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20120430

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: GB

Payment date: 20140402

Year of fee payment: 14

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: IT

Payment date: 20140415

Year of fee payment: 14

GBPC Gb: european patent ceased through non-payment of renewal fee

Effective date: 20150402

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: GB

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20150402

Ref country code: IT

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20150402

PGFP Annual fee paid to national office [announced via postgrant information from national office to epo]

Ref country code: DE

Payment date: 20180320

Year of fee payment: 18

REG Reference to a national code

Ref country code: DE

Ref legal event code: R119

Ref document number: 60145074

Country of ref document: DE

PG25 Lapsed in a contracting state [announced via postgrant information from national office to epo]

Ref country code: DE

Free format text: LAPSE BECAUSE OF NON-PAYMENT OF DUE FEES

Effective date: 20191101