Vehicle data server for specially-equipped vehicles

Abstract

To enable a user having legitimate authority to view vehicle data of specially-equipped vehicles.SOLUTION: A first server 100 transmits an initial screen (not shown). A user-side manager terminal device 120 transmits a data request to the first server 100 when a "vehicle list" button is selected on the initial screen (S5). The first server 100 reads out registered vehicle data and working operation data of the user and generates vehicle list data (S23). In this case, determination is made as to whether there is a specially-equipped vehicle that includes at least one component having exceeded a recommended number of days of replacement (S25). When processing of step S25 is finished for all components that include alert information with regard to these exceeded components, vehicle list data is generated and then transmitted to the user-side manager terminal device 120 (S29).SELECTED DRAWING: Figure 12

Description

[Technical Field]

[0001] The present invention relates to a specially equipped vehicle data server, and more particularly to access management to specially equipped vehicle data. [Background technology]

[0002] In Patent Document 1, a terminal device 20 collects vehicle data from a control unit 10 of a specially equipped vehicle 5. The vehicle data collected by the terminal device 20 is transmitted to a server 30 via the Internet 2. The server 30, for example, performs a fault diagnosis of the specially equipped vehicle 5 based on the collected vehicle data and transmits the results to the terminal device 20. The user can easily understand the results by looking at a display device 23 of the terminal device 20 (paragraph 0048). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2020-127192 Summary of the Invention [Problem to be solved by the invention]

[0004] However, the maintenance management system of Patent Document 1 has the following problem. The inventors considered using such a maintenance management system (user terminal, server) to provide maintenance services to multiple companies. In this case, vehicle data held by different companies would be stored on the server. Therefore, if left as is, there is a risk that data on vehicles owned by other companies could be viewed.

[0005] SUMMARY OF THE INVENTION An object of the present invention is to solve the above problems and to provide a specially equipped vehicle data server that allows access to specially equipped vehicle data when a user has proper authority. [Means for solving the problem]

[0006] (1) The special purpose vehicle data server of the present invention comprises: A) a special purpose vehicle data storage means for storing special purpose vehicle data in association with a special purpose vehicle identifier; B) a special purpose vehicle data management means for transmitting the special purpose vehicle data upon a data viewing request; C) the special purpose vehicle data is stored in association with a user identifier; D) the special purpose vehicle data includes current maintenance data for mounted equipment; and E) upon a request to view data for a special purpose vehicle managed by the user identifier from a user terminal authenticated with a certain user identifier, the special purpose vehicle data management means transmits the special purpose vehicle data linked to the user identifier to the user terminal.

[0007] Therefore, it is possible to prevent a user with a different user identifier from viewing the current equipment maintenance data of the equipment.

[0008] (2) In the special-purpose vehicle data server according to the present invention, the current maintenance status data for the mounted equipment includes operational data and vehicle maintenance data for the special-purpose vehicle control device that controls the controlled devices mounted on the special-purpose vehicle, and the vehicle maintenance data includes initial vehicle data and maintenance history data at the time of delivery of the special-purpose vehicle. The special-purpose vehicle data server is composed of a first server that stores the operational data and a second server that stores the vehicle maintenance data. When a data viewing request is received, the special-purpose vehicle data management means reads the initial vehicle data and the maintenance history data associated with the user identifier from the second server and transmits the special-purpose vehicle data including these data to the user terminal. Therefore, since the current maintenance status data is not stored in the first server, storage capacity can be reduced accordingly.

[0009] (3) In the specially equipped vehicle data server according to the present invention, the current maintenance status data for the mounted equipment includes 1) initial vehicle data at the time of delivery of the specially equipped vehicle, including predetermined replacement date data indicating the number of days between replacements of parts, and 2) maintenance history data including data indicating the last replacement date, and when a data viewing request is received, the specially equipped vehicle data management means determines whether there are any parts for which the predetermined number of replacement days has elapsed since the last replacement date, and if so, transmits warning information to the user terminal together with the data. Therefore, if there are any parts for which the predetermined number of replacement days has elapsed since the replacement date, warning information can be provided to the user terminal.

[0010] (4) In the special purpose vehicle data server according to the present invention, when a data viewing request specifying a user identifier is received from the user terminal, the special purpose vehicle data management means transmits to the user terminal a maintenance history input screen for inputting a maintenance history or a generation command for generating the maintenance history input screen. Therefore, the maintenance history input screen can be displayed when viewing data.

[0011] (5) In the special purpose vehicle data server according to the present invention, a manufacturer identifier for the manufacturer of the special purpose vehicle to request authentication is stored, and when a data viewing request specifying the manufacturer identifier is received, the special purpose vehicle data management means transmits the current maintenance status data of each special purpose vehicle to the manufacturer computer that has made the data viewing request. Therefore, the manufacturer computer can receive the current maintenance status data of each special purpose vehicle.

[0012] The terms used in the claims and their correspondence in the embodiments will be explained below.

[0013] In the embodiment, the "controlled device" corresponds to the hydraulic pump P, the multi-valve MV, the various cylinders A1 to A4, the lifting body 4, the compression plate 5, etc. In the embodiment, the "controlled device control unit" corresponds to the mounted object side control device UK.

[0014] "Specially equipped vehicle data" is information about specially equipped vehicles, and is a concept that includes "basic vehicle data" and "current maintenance data for mounted objects." "Basic vehicle data" is vehicle attribute data for determining replacement parts, and in the embodiment, corresponds to the data determined at the time of delivery of the specially equipped vehicle shown in Figure 10A.

[0015] The "current maintenance data for mounted equipment" is data necessary for maintenance, and includes the "operational data" and "vehicle maintenance data" of specially equipped vehicles. The operation data of specially equipped vehicles is a prerequisite for maintenance.

[0016] In this embodiment, the "vehicle maintenance data" corresponds to the "initial vehicle data" and the "maintenance history data." In this embodiment, the "operation data" is stored in the first server 100, and the "initial vehicle data" and the "vehicle maintenance data" are stored in the second server 140, but this is not limiting.

[0017] That is, the interrelationships of the data used in this embodiment can be expressed in an easy-to-understand manner as follows:

[0018] "Specially equipped vehicle data" > "Basic vehicle data" & "Current status data of maintenance of bodywork", "Current status data of equipment maintenance" > "Operational operation data" & "Vehicle maintenance data", "Vehicle maintenance data" > "Initial vehicle data" & "Maintenance history data", In addition, the “operation data” is stored in the first server 100, and the “vehicle maintenance data” is stored in the second server 140.

[0019] Note that companies that provide specially equipped vehicles already have a server that stores vehicle identification data that identifies the specially equipped vehicle purchased by each user. In this system, such a server can be used as the second server 140. Therefore, compared to storing all of the data in the first server 100, the storage area of ​​the first server 100 can be used more effectively. [Brief explanation of the drawings]

[0020] [Figure 1] 1 is a partially cutaway overall side view of a refuse collection vehicle V used in a specially equipped vehicle management system 1. FIG. [Figure 2] 1 is a schematic diagram for explaining the control relationships of the various parts in a refuse collection vehicle V. FIG. [Figure 3] FIG. 2 is a functional block diagram of the specially equipped vehicle management system 1. [Figure 4] FIG. 2 is a diagram illustrating a hardware configuration of a first server 100. [Figure 5] 10A and 10B are diagrams illustrating an example of user ID corresponding data and user-specific vehicle data. [Figure 6] FIG. 10 is a diagram showing an example of specially equipped vehicle operation data. [Figure 7] FIG. 2 is a diagram showing the hardware configuration of a user portable device 160. [Figure 8] FIG. 2 is a diagram showing the hardware configuration of a user-side administrator terminal device 120. [Figure 9] FIG. 2 is a diagram showing a hardware configuration of a second server 140. [Figure 10] 3A and 3B are diagrams illustrating data structures of basic vehicle data and regularly replaced part data. [Figure 11] FIG. 10 is a diagram showing the data structure of consumable parts data and part replacement / vehicle repair history data. [Figure 12] 10 is a flowchart for displaying current equipment maintenance data. [Figure 13] 10 is an example of a current equipment maintenance data display screen. [Figure 14] 10 is an example of a current equipment maintenance data display screen. DETAILED DESCRIPTION OF THE INVENTION

[0021] Hereinafter, embodiments of the present invention will be described with reference to the drawings.

[0022] (1. Description of specially equipped vehicles) First, the refuse collection vehicle V, which is a specially equipped vehicle used in the specially equipped vehicle management system 1, will be described.

[0023] The refuse collection vehicle V shown in Figure 1 is composed of a base vehicle Vb and a body F of the base vehicle Vb that is mounted on the vehicle body F for refuse collection work after the base vehicle Vb is fully assembled. The base vehicle Vb is equipped with a vehicle-side control device UV, and the body K is equipped with a body-side control device UK.

[0024] As shown in FIG. 2, a vehicle body F of a base vehicle Vb is equipped with an engine E, a battery B, an electric motor M, a selective power take-off mechanism PS, and a vehicle-side control device UV.

[0025] The engine E applies driving force to the wheels W. The electric motor M is connected to the battery B via an inverter 12 and operates on power from the battery B. The power selection take-off mechanism PS can selectively take off the power of the engine E or the electric motor M from the wheel drive system D, which is a drive system including the engine E and the electric motor M. The vehicle-side control device UV is mainly composed of a microcomputer, and controls the engine E, the electric motor M, the battery B, and the electromagnetic clutch 11. A starter switch S-SW for starting the engine E is also connected to the vehicle-side control device UV.

[0026] In reality, the vehicle-side control device UV is connected to the engine E, the electric motor M, and the battery B by a plurality of power lines and / or signal lines, but these are simply shown in FIG. 2.

[0027] The output side of the power take-off device PTO is interlocked and connected to a hydraulic pump P that is part of the mounted object K. The power take-off device PTO is also connected to the vehicle-side control device UV, and selectively switches and transmits the output of the transmission 10 (see FIG. 1 ) to either the wheels W or the hydraulic pump P in response to an operation input to a power take-off switch P-SW that is also connected to the vehicle-side control device UV. Specifically, when the power take-off switch P-SW is in the off (OFF) state, the output of the transmission 10 is transmitted to the wheels W and used for driving the vehicle. On the other hand, when the switch P-SW is turned on, the output of the transmission 10 is transmitted to the hydraulic pump P and used for driving the pump.

[0028] The mounted object K has a box-shaped garbage collection box 1 with an open rear end as its base body (mounted object main body), and this garbage collection box 1 is mounted and fixed onto the body F of the base vehicle Vb as an after-market attachment. A garbage drop box 3 is attached to the rear end of the garbage collection box 1. The garbage drop box 3 has a garbage drop opening 3a at its rear end for dropping garbage into the garbage collection box 1. An opening / closing door 3t opens and closes the garbage drop opening 3a.

[0029] A garbage loading device 2 serving as a work machine is provided inside the garbage drop box 3. The garbage loading device 2 forcibly loads the garbage in the drop box 3 into the garbage storage box 1 when the drop box 3 is in the loading position.

[0030] The garbage loading device 2 has a conventionally known structure known as a compression plate type, and comprises a lifting body 4, a second cylinder A2, a compression plate 5, and a third cylinder A3. The lifting body 4 is supported on both the left and right side walls of the garbage bin 3 so that it can be raised and lowered, facing the rear end opening 1a of the garbage storage bin 1. The second cylinder A2 forcibly raises and lowers the lifting body 4. The compression plate 5 extends across the full width of the garbage bin 3 and is supported by the second cylinder A2 for raising and lowering the lifting body, and is pivotally supported at the bottom of the lifting body 4 so that it can rotate back and forth. The third cylinder A3 forcibly rotates the compression plate 5.

[0031] In addition, a rear operation panel CR is fixed and supported on the outer surface around the garbage inlet 3a of the garbage bin 3 shown in Figure 1. The rear operation panel CR is provided with operation switches CR-SW1 to CR-SW3, a first power source selection switch M-SW1, and warning lamps L1 to L5. The operation switches CR-SW1 to CR-SW3 select and operate the operating mode of the garbage loading device 2. In particular, the operation switch CR-SW3 is a switch that issues an emergency stop command in the event of a dangerous situation. The first power source selection switch M-SW1 outputs a motor selection signal when turned on. This switches the hydraulic pump P from an engine-driven state driven by the engine E to a motor-driven state driven by the electric motor M.

[0032] As shown in Fig. 1, a cabin control device UF having a control panel CF is provided in the driver's cab of the base vehicle Vb. As shown in Fig. 2, the cabin control device UF has a microcomputer 61, a short-range wireless communication unit 63, an antenna 65, and the control panel CF.

[0033] The control panel CF is provided with operation switches CF-SW1 to CF-SW3, a second power source selection switch M-SW2, and notification lamps L1 to L5. Like the operation switches CR-SW1 to CR-SW3, the operation switches CF-SW1 to CF-SW3 select and operate the operation modes of the garbage loading device 2 and the garbage discharge device 7. Like the first power source selection switch M-SW2, the second power source selection switch M-SW2 outputs a motor selection signal when turned on.

[0034] 1, a camera 53 is provided above the garbage bin 3. Images from the camera 53 are analyzed by an image processing unit 51 provided in the control unit box UKB. The image processing unit 51 is connected to the mounted-item control device UK, and if the image analysis determines that a dangerous condition exists, it outputs an emergency stop signal to the mounted-item control device UK. In other words, this is the same as when the operation switch CR-SW3 is pressed.

[0035] In this embodiment, a refuse collection vehicle has been described as an example of a specially equipped vehicle, but the vehicle is not limited to a refuse collection vehicle.

[0036] 2. Overview of the Special Purpose Vehicle Data Management System1 The specially equipped vehicle management system 1 includes a specially equipped vehicle data server 190, a user portable device 160, a user side administrator terminal device 120, and a specially equipped vehicle 180a.

[0037] The specially equipped vehicle vehicle-side control device 201 of the specially equipped vehicle 180a has short-range wireless transmission / reception means 203, operation data storage means 205, specially equipped vehicle identification data storage means 209, and control means 207. The short-range wireless transmission / reception means 203 is connected to the short-range wireless transmission / reception means 164 of the specially equipped vehicle vehicle-side control device 201 by short-range wireless communication. The operation data storage means 205 stores operation operation data of the control target device 210. The specially equipped vehicle identification data storage means 209 stores the identifier of the specially equipped vehicle. The control means 207 manages the transmission of the operation operation data stored in the operation data storage means 205 by the short-range wireless transmission / reception means 203.

[0038] The specially equipped vehicle data server 190 includes a first server 100 and a second server 140 that manage specially equipped vehicle data.

[0039] The second server 140 has a special purpose vehicle maintenance data storage means 141. The special purpose vehicle maintenance data storage means 141 stores initial vehicle data and maintenance history data at the time of delivery of the special purpose vehicle in association with a user identifier. The second server 140 is a server that stores vehicle identification data that identifies the special purpose vehicle purchased by the user, and is a server originally owned by the special purpose vehicle manufacturer.

[0040] The first server 100 has a special-purpose vehicle data management means 103, a special-purpose vehicle operation data storage means 101, and a server-side authentication means 109. When an authentication request is received from a user terminal (user-side administrator terminal device 120 or user portable device 160), the server-side authentication means 109 determines whether the stored identifier has valid authorization, and if so, grants access authorization. When a data viewing request is received from a user terminal (user-side administrator terminal device 120 or user portable device 160), the special-purpose vehicle data management means 103 reads the initial vehicle data and maintenance history data of the special-purpose vehicle associated with the user identifier of the user terminal from the special-purpose vehicle maintenance data storage means 141, and transmits special-purpose vehicle data including these data to the user terminal. The server-side authentication means 109 also reads the operation data of the special-purpose vehicle associated with the user identifier and transmits it to the user terminal.

[0041] Furthermore, the maintenance history data includes data indicating the last replacement date, and the initial vehicle data includes predetermined replacement date data indicating the number of days since the last replacement of parts. When a data viewing request is received, the specially equipped vehicle data management means 103 determines whether there are any parts for which the predetermined number of days have passed since the last replacement date, and if so, transmits warning information to the user terminal that made the data viewing request.

[0042] The special purpose vehicle data management means 105 may be configured to, when a data viewing request specifying a user identifier is received from a user terminal (user side administrator terminal device 120 or user portable device 160), send a maintenance history input screen or a maintenance history input screen generation command to the user terminal (user side administrator terminal device 120 or user portable device 160).

[0043] In addition, the server-side authentication means 109 may store a manufacturer identifier for the manufacturer of the special-purpose vehicle to request authentication, and determine whether or not the manufacturer has access authority.If the manufacturer has such authority, the special-purpose vehicle data management means 103 may be configured to, upon receiving a data viewing request that identifies the manufacturer identifier, transmit the current maintenance status data of each special-purpose vehicle to the manufacturer computer that made the data viewing request.

[0044] The user portable device 160 includes a short-distance wireless transmission / reception means 164 , an operation data acquisition means 165 , an operation data storage means 166 , an operation data transmission means 162 , and a user portable authentication means 169 .

[0045] The operating operation data acquisition means 165 connects the short-range wireless transmission / reception means 164 to the specially equipped vehicle vehicle-side control device 201 via wireless communication to acquire operating operation data of the mounted object. The operating operation data storage means 166 stores the acquired operating operation data. The operating operation data transmission means 162 transmits the operating operation data to the first server 100 based on determined transmission conditions. The user portable authentication means 169 stores data for authentication, and issues an authentication request to the server-side authentication means 109 of the first server 100.

[0046] The user side administrator terminal device 120 has a management device side authentication means 129 and a data viewing management means 125 .

[0047] The management device side authentication means 129 requests the first server 100 to authenticate the user as the user with the specific user identifier.

[0048] The data browsing management means 125 issues a data browsing request specifying the user identifier to the first server 100, and upon receiving a result from the first server 100, displays it.

[0049] Although the case where the viewing management means 125 is provided in the user-side administrator terminal device 120 has been described with reference to FIG. 3, it may also be provided in the user portable device 160 .

[0050] Furthermore, in this embodiment, the vehicle maintenance data is stored in the second server 140, but it may also be stored in the first server 100.

[0051] In this embodiment, the specially equipped vehicle operation data storage means 101 and the specially equipped vehicle maintenance data storage means 141 constitute a specially equipped vehicle data storage means 191 .

[0052] 3. Hardware Configuration 3.1 Hardware Configuration of the First Server 100 The hardware configuration of the first server 100, which is configured using a CPU, will be described with reference to FIG.

[0053] The first server 100 includes a CPU 23, a memory 27, a hard disk 26, a monitor 30, an optical drive 25, an input device 28, a communication board 31, and a bus line 29. The CPU 23 controls each part via the bus line 29 in accordance with each program stored in the hard disk 26.

[0054] The hard disk 26 has an operating system program 26o (hereinafter abbreviated as OS), a main program 26m, a user-registered vehicle data storage unit 26c, a user ID corresponding data storage unit 26u, and a specially equipped vehicle operation data storage unit 26d.

[0055] As will be described later, the second server 140 is managed by a user ID (in-company user ID) different from that of the first server 100. Therefore, the user ID storage unit 26u stores the user ID correspondence data shown in FIG. 5A.

[0056] The data structure of the user-specific registered vehicle data 26c is shown in Fig. 5B. The user-specific registered vehicle data 26c stores the serial numbers of specially equipped vehicles managed by each service user ID in association with each service user ID.

[0057] The data structure of the operation data stored in the specially equipped vehicle operation data storage unit 26d is shown in Fig. 6. The operation data includes the time, the total number of loadings, the total number of TG lifts, the PTO operation time, and the position data, all associated with the serial number. The operation data is provided via the user portable device 160.

[0058] In this embodiment, Windows 10 (registered trademark or trademark) is used as the operating system program (OS) 26o, but the present invention is not limited to this.

[0059] Each of the above programs is read from the CD-ROM 25a on which the programs are stored via the optical drive 25 and installed on the hard disk 26. The programs may be installed on the hard disk from a computer-readable recording medium other than a CD-ROM, such as a flexible disk (FD) or an IC card. Furthermore, the programs may be downloaded using a communication line.

[0060] In this embodiment, the program stored on the CD-ROM is installed on the hard disk 26 from the CD-ROM, thereby causing the computer to indirectly execute the program. However, the present invention is not limited to this, and the program stored on the CD-ROM may be executed directly from the optical drive 25. Programs that can be executed by a computer include not only those that can be executed directly by simply installing them as they are, but also those that require conversion to another format (for example, decompressing compressed data), and those that can be executed in combination with other modules.

[0061] 3.2 Hardware Configuration of User Portable Device 160 The user portable device 160 will be described with reference to Fig. 7. This figure shows an example of a hardware configuration in which the user terminal device 120 is configured using a CPU.

[0062] The user terminal device 120 has the configuration of a typical smartphone and includes a CPU 123, memory 127, flash memory 126, display unit 130, wireless communication unit 128, operation unit 125, audio input / output unit 124, location information detection unit 122, short-range wireless communication unit 121, and bus line 129. The location information detection unit 122 is a module that detects location information using GNSS (Global Navigation Satellite System). The short-range wireless communication unit 121 communicates according to the Bluetooth (registered trademark) standard. In this embodiment, iOS (trademark) is used as the OS.

[0063] The CPU 123 controls each unit via a bus line 129 in accordance with each program stored in a flash memory 126 .

[0064] The flash memory 126 includes an operating system program 126o (hereinafter abbreviated as OS) and a main program 126m.

[0065] The processing of the main program 126m will be described later.

[0066] In this embodiment, Bluetooth (registered trademark) is used as the short-range wireless communication unit, but the present invention is not limited to this.

[0067] The flash memory 126 has a transmission condition storage unit 126d. The operating operation data is transmitted from the user terminal device 160 to the first server 100 in the following procedure. Based on the main program 126m, the CPU 123 periodically (for example, every 30 seconds) connects to the specially equipped vehicle vehicle-side control device 201 via short-range wireless communication and issues an instruction to acquire the operating operation data. When the specially equipped vehicle vehicle-side control device 201 of the specially equipped vehicle receives the acquisition instruction, it transmits the operating operation data stored in the memory (not shown in FIG. 2) in the mounted object-side control device UK to the user terminal device 160. When the CPU 123 receives the operating operation data, it transmits it to the first server 100.

[0068] (3.3 Hardware Configuration of User-Side Administrator Terminal Device 120) 8 shows the hardware configuration of the user-side administrator terminal device 120. The basic configuration is the same as that shown in FIG.

[0069] The hard disk 226 includes an operating system program 226o and a browser program 226m.

[0070] 3.4 Hardware Configuration of the Second Server 140 9 shows the hardware configuration of the second server 140. The basic configuration is the same as that shown in FIG.

[0071] The hard disk 326 includes an operating system program 326o, a main program 326m, a registered vehicle basic data storage section 326c, and a maintenance data storage section 326m.

[0072] The second server 140 is managed by a user ID (hereinafter referred to as an in-house user ID) that is different from that of the first server 100. Therefore, the user ID storage unit 26u stores data (not shown) that corresponds to an in-house user ID for logging in and its password.

[0073] 10A shows the data structure of the registered vehicle basic data storage unit 326c. For each in-house user ID, initial data such as the serial number, registration number, model, etc. of the specially equipped vehicle being managed is stored.

[0074] Furthermore, the maintenance data storage unit 326m stores the regularly replaced parts data shown in FIG. 10B, the consumable parts data shown in FIGS. 11A and 11B, and the parts replacement and vehicle repair history data. These are data that indicate the maintenance history of each specially equipped vehicle. The regularly replaced parts data shown in FIG. 10B, the consumable parts data shown in FIGS. 11A and 11B, and the parts replacement and vehicle repair history data are maintenance history data for a specially equipped vehicle with serial number "18R830001M."

[0075] In this embodiment, the periodic replacement part information data includes, but is not limited to, the number of days elapsed, the number of days recommended for replacement, the ratio, the date of record of replacement, the date of the last replacement, and the cumulative number of replacements. Similarly, the consumable part data includes, but is not limited to, the name of the consumable part, the number of days elapsed, the date of the last replacement, and the cumulative number of replacements.

[0076] 4. Display and update of current equipment maintenance data (4.1 Maintenance data display processing) The process of displaying the current equipment maintenance status data of the user ID "1001" on the user side administrator terminal device 120 will be described with reference to FIG.

[0077] The following describes a case where an operator of the user-side administrator terminal device 120 accesses the login screen using the browser program 226m, logs in using the user ID "1001," and displays the current maintenance status data for the equipment of a specially equipped vehicle with the serial number "18R830001M."

[0078] The login process to the first server 100 is the same as the normal process, and therefore will not be described here. Upon such login, the first server 100 transmits an initial screen (not shown).

[0079] The CPU 223 of the user-side administrator terminal device 120 displays the received initial screen (step S1 in FIG. 12). The operator selects a "Vehicle List" button (not shown) on the initial screen. The CPU 223 of the user-side administrator terminal device 120 determines whether or not the "Vehicle List" button is selected (step S3 in FIG. 12), and when the "Vehicle List" button is selected, transmits a vehicle list data request to the first server 100 (step S5).

[0080] The first server 100 determines whether to receive a vehicle list data request (step S21), and upon receiving such a request, reads the registered vehicle data and operating operation data of the user and generates vehicle list data (step S23).

[0081] In this embodiment, the list data processing is performed by reading out the following data. The operating operation data used were the accumulated number of loadings, accumulated number of TG lifts, and PTO operating time for each specially equipped vehicle from the operating operation data for user ID "1001" shown in Figure 6. In addition, by referring to the user ID correspondence data shown in Figure 5A, the in-house user ID "U123456789" for user ID "1001" was read out, and the second server 140 was accessed to use the serial number, registration number, vehicle number, model, and latest data registration date and time of the specially equipped vehicle with that serial number.

[0082] The access permission to the second server 140 may be determined by determining whether or not the combination matches a stored combination using a normal ID and PW.

[0083] Furthermore, the latest data registration date and time can be obtained by reading out the date and time of the operation data shown in FIG. 6B.

[0084] The CPU 23 determines whether there is a specially equipped vehicle in the read vehicle list data that includes at least one part that has exceeded the recommended replacement days (step S25). In this case, when the regularly replaced part data for the specially equipped vehicle with serial number "18R830001M" is referenced, the ratio of the number of days elapsed to the recommended replacement days exceeds 1 for the replacement parts "hydraulic oil," "return filter," "hydraulic parts, seals," and "bearing bushings, slide shoes." Therefore, the specially equipped vehicle with serial number "18R830001M" that includes such parts is determined to have parts that have exceeded the recommended replacement days (step S27). This is performed for all specially equipped vehicles managed by the user (step S28).

[0085] When the process of step S25 is completed for all parts containing alert information for the excess parts in step S28, the CPU 23 generates vehicle list data and transmits it to the user-side administrator terminal device 120 (step S29).

[0086] The CPU 223 of the user-side administrator terminal device 120 determines whether to receive vehicle list data (step S7 in FIG. 12), and upon receiving such data, displays a list of vehicle list data for user ID "1001" (step S9). An example of vehicle list data is shown in FIG. 13A. In this case, specially equipped vehicles with serial numbers "17R810008M" and "18R830001M" have been given a parts replacement warning.

[0087] The operator of the user-side administrator terminal device 120 selects a vehicle for which he or she wishes to refer to the current equipment maintenance data from the displayed vehicle list data. In this case, he or she selects the specially equipped vehicle with the serial number "18R830001M" shown in Fig. 13A.

[0088] The CPU 223 of the user-side administrator terminal device 120 determines whether any special-purpose vehicle is selected (step S11 in FIG. 12), and if such a selection is made, sends a vehicle maintenance data request specifying the special-purpose vehicle to the first server 100 (step S13).

[0089] The first server 100 determines whether to accept the vehicle maintenance data request (step S31), and upon receiving such a request, reads out the vehicle maintenance data for the specially equipped vehicle (step S33). In this case, the vehicle maintenance data for the specially equipped vehicle with the serial number "18R830001M" is read out. In this embodiment, the regularly replaced parts data shown in FIG. 10B, the consumable parts data shown in FIGS. 11A and 11B, and the parts replacement and vehicle repair history data are read out.

[0090] The CPU 23 of the first server 100 generates a vehicle maintenance data screen from the read data and transmits it to the user-side administrator terminal device 120 (step S35).

[0091] The CPU 223 of the user-side administrator terminal device 120 determines whether or not to receive the vehicle maintenance data screen (step S15 in FIG. 12), and when such data is received, it displays it (step S17).

[0092] A display screen for periodic replacement part data is shown in FIG. 13B, a display screen for consumable part data is shown in FIG. 13C, and a display screen for part replacement and vehicle repair history data is shown in FIG. 14A.

[0093] The vehicle maintenance data may be displayed all together, or selection buttons may be displayed so that when one of the data is selected, it is displayed.

[0094] In this way, only the user with that user ID can access the vehicle maintenance data for the special purpose vehicle linked to that user ID.

[0095] In this embodiment, the case where the vehicle maintenance data is referred to from the user side administrator terminal device 120 has been described, but the vehicle maintenance data can also be referred to from the user portable device 160.

[0096] (4.2 Maintenance Data Record Processing) The maintenance history data constituting the vehicle maintenance data can be input from the user-side administrator terminal device 120, as will be described below.

[0097] 14A, when the user selects new registration button 410, a new registration request is sent to the first server 100. The first server 100 generates the editing screen shown in FIG. 14B and sends it to the user-side administrator terminal device 120. The user-side administrator terminal device 120 displays this. When the operator of the user-side administrator terminal device 120 inputs the maintenance history data to be registered and selects registration button 420, the maintenance history data is sent to the first server 100. The first server 100 saves this in the maintenance data storage unit 226m of the second server 140.

[0098] The current equipment maintenance data includes not only the vehicle maintenance data stored in the maintenance data storage unit 226m but also the operation data stored in the specially equipped vehicle operation data storage unit 26d (see FIG. 4). Such operation data is updated when it is received from the user portable device 160.

[0099] Also, when a list of vehicles is displayed on the user-side administrator terminal device 120 and one of the specially equipped vehicles is selected, a data display screen such as that shown in Fig. 14C may be displayed. When a maintenance data display button is selected on this screen, the current maintenance status data of the mounted object shown in Fig. 13B and Fig. 14 may be displayed.

[0100] When the current equipment maintenance status data is displayed, map data showing the location of the specially equipped vehicle may also be displayed.

[0101] Furthermore, in the above embodiment, when the user selects the new registration button 410 in FIG. 14A, the editing screen shown in FIG. 14B is displayed. However, this is not limited to this, and when any of the replacement record buttons 430 in FIG. 13B is selected, a screen for editing the maintenance history data of the corresponding special purpose vehicle may be displayed.

[0102] In this embodiment, the first server 100 generates the screen data to be sent to the user-side administrator terminal device 120, but it is also possible to send data for generating the screen data to the user-side administrator terminal device 120 and generate the display screen on the user-side administrator terminal device 120.

[0103] Alternatively, instead of accessing the first server 100 each time, the necessary data may be sent in one exchange, and the necessary screen may be generated in the user-side administrator terminal device 120. Alternatively, multiple screen data may be sent to the user-side administrator terminal device 120, and the display may be switched.

[0104] (5. Other Embodiments) The data update registration date and time shown in FIG. 13 is updated when the operating action data is received from the user portable device 160.

[0105] The number of days elapsed in maintenance history data is updated as follows. For the maintenance history data of any special-purpose vehicle, the number of days from the last replacement date to the current date is calculated by accessing the regularly replaced parts data screen or the consumable parts data screen shown in FIG. 13B, and the obtained number of days is used as the number of elapsed days. For example, if the current date is March 31, 2021, and the last replacement date for a certain consumable part is March 2, 2021, the number of elapsed days is 29 days.

[0106] In this embodiment, the case where the current state of maintenance data for the mounted equipment of the user ID can be accessed from the user-side administrator terminal device 120 or the user portable device 160 has been described, but a maintenance company identifier and password may be issued so that the maintenance company that brings the specially equipped vehicle to the maintenance shop can temporarily access the current state of maintenance data for the mounted equipment of the specific specially equipped vehicle. Furthermore, a manufacturer identifier and password that allows temporary access may be issued to the manufacturer of the specially equipped vehicle instead of the maintenance shop.

[0107] In this embodiment, in Fig. 3, one user terminal 150 is illustrated as one user-side administrator terminal device 120 and one user-ported device 160, but the number of user-ported devices 160 required is equal to the number of specially equipped vehicles that the user will use simultaneously. Generally, one user is configured with multiple user-ported devices 160 and multiple specially equipped vehicles. Note that multiple user-side administrator terminal devices 120 may be provided.

[0108] The operation data acquired by the user portable device 160 may include image data showing the operation status of the mounted object. Such image data may be data captured by the image processing unit 51 from an image of the camera 53 (see FIG. 2). The user portable device 160 may transmit the operation data including such image data to the first server 100.

[0109] In this embodiment, the case where a garbage collection vehicle is used as the special vehicle is described, so the operation data is the cumulative number of loadings, cumulative number of TG ascents, PTO operation time, and position data. However, any data may be used as long as it is the operation data of a special vehicle.

[0110] In this embodiment, an alert indicating whether the number of days since replacement has passed is displayed when the list is displayed, but this is not limited to this and may also be displayed when a specific specially equipped vehicle is selected.

[0111] In this embodiment, the current state of equipment maintenance data is stored separately in the first server 100 and the second server 140, so the operating operation data and vehicle maintenance data are read from the first server and the second server, respectively, and data for screen display is generated each time. However, this is not limited to this, and the data to be used for display may be read from the second server in advance and stored separately in the first server in a format required for display.

[0112] It may also be configured as a single server that collects all of this data.

[0113] A similar authentication means may also be provided for the second server. In this case, the company user ID and its password may be stored in the user ID correspondence data of the first server. [Explanation of symbols]

[0114] 100 First Server 140 Second Server 120 User-side administrator terminal device 160 User terminal device

Claims

1. Specially equipped vehicle data storage means for storing specially equipped vehicle data; a specially equipped vehicle data management means for transmitting the specially equipped vehicle data when a data browsing request is received; A specially equipped vehicle data server comprising: The specially equipped vehicle data includes current maintenance data of the equipment mounted on the specially equipped vehicle, The current maintenance status data of the mounted object includes the history of the repair location and repair content of the specially equipped vehicle as maintenance history data, The specially equipped vehicle data management means When a request to view data on managed special-purpose vehicles is received from a user terminal, the special-purpose vehicle data of the special-purpose vehicles is transmitted to the user terminal; A specially equipped vehicle data server characterized by the above.

2. In the special purpose vehicle data server of claim 1, The specially equipped vehicle data storage means stores specially equipped vehicle data in association with a specially equipped vehicle identifier, The specially equipped vehicle data is stored in association with a user identifier, the special purpose vehicle data management means, when a request to view data on special purpose vehicles managed by a user identifier is received from a user terminal authenticated by a certain user identifier, transmits to the user terminal the special purpose vehicle data on the special purpose vehicle linked to the user identifier; A specially equipped vehicle data server characterized by the above.

3. In the special purpose vehicle data server of claim 1 or 2, The equipment maintenance current status data includes next replacement date specification data that specifies the next replacement date of the part, the specially equipped vehicle data management means, upon receiving the data viewing request, determines whether or not there are any parts whose next replacement date has passed, and if so, transmits warning information to the user terminal together with the parts; A specially equipped vehicle data server characterized by the above.

Images