Labor management system and computer program

The labor management system addresses the challenge of tracking driver waiting and rest times by using terminals and servers to automate data collection and recording, improving accuracy and efficiency in labor management.

JP7698367B1Active Publication Date: 2025-06-25HISHIKI TRANSPORT
View PDF 7 Cites 0 Cited by

Patent Information

Application Number
JP2025028549
Authority / Receiving Office
JP · JP
Patent Type
Patents
Current Assignee / Owner
Filing Date
2025-02-26
Publication Date
2025-06-25
Estimated Expiration
2044-04-11

AI Technical Summary

Technical Problem

Existing labor management systems in transportation companies struggle to accurately track and manage driver waiting times and rest periods, especially at loading and unloading points, due to inconsistencies in data entry and lack of real-time monitoring.

Method used

A labor management system comprising a driver terminal, administrator terminal, and server that utilize position specifying, time acquisition, shipper identification, and calculation means to record waiting and rest times based on GPS data and input devices, ensuring accurate tracking and recording of labor activities.

Benefits of technology

The system improves the accuracy of labor management by automatically recording waiting and rest times, correcting inconsistencies, and enabling real-time monitoring of driver activities, thereby enhancing business management efficiency.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure 0007698367000001_ABST
    Figure 0007698367000001_ABST
Patent Text Reader

Abstract

Improve the business management system in the transportation company. 【Solution means】 A labor management system according to an embodiment includes a driver terminal, a manager terminal, and a server that can communicate with each other, and includes a position specifying means for specifying the position where the vehicle has stopped, a first acquisition means for acquiring a first time input by an input device, a second acquisition means for acquiring a second time input by the input device, a shipper specifying means for specifying a shipper corresponding to the specified position, a calculation means for calculating a waiting time at the specified position based on the first time and the second time, and a recording means for recording waiting information including the specified shipper and the calculated waiting time. Each of the position specifying means, the first acquisition means, the second acquisition means, the shipper specifying means, the calculation means, and the recording means is realized by any one of the driver terminal, the manager terminal, and the server, or by the cooperation of the manager terminal, the driver terminal, and the server.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to a labor management system and a computer program.

Background Art

[0002] In recent years, there has been an increasing movement to improve the working environment. In improving the working environment, it is important for both administrators and workers to strive to comply with laws and various regulations. For example, in the case of truck drivers, there are various regulations regarding restricted hours, rest periods, and break times.

[0003] Also, in recent years, in order to correct long working hours of drivers, there has been a strong demand to reduce waiting times at loading and unloading points. To reduce waiting times, it is necessary to grasp the actual situation of waiting times in daily operations and then work on improvements.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] The present invention has been made based on the above circumstances, and one of its objects is to provide a labor management system and a computer program that can improve the business management system in a transportation company. Other objects of the present invention are derived from this specification and the accompanying drawings.

Means for Solving the Problems

[0006] A labor management system according to an embodiment includes a driver terminal, an administrator terminal, and a server that can communicate with each other, and position specifying means for specifying the position where the vehicle has stopped, In the vehicle, the driver terminal, or the administrator terminalA first acquisition means for acquiring a first time input by an input device, a second acquisition means for acquiring a second time input by the input device, a shipper identification means for identifying a shipper corresponding to the position identified by the position identification means, a calculation means for calculating a waiting time of a driver of the vehicle at the position identified by the position identification means based on the first time and the second time, and a recording means for recording waiting information including the shipper identified by the shipper identification means and the waiting time calculated by the calculation means. Each of the position identification means, the first acquisition means, the second acquisition means, the shipper identification means, the calculation means, and the recording means is realized by any one of the driver terminal, the administrator terminal, and the server, or by cooperation of the administrator terminal, the driver terminal, and the server. According to another aspect of the embodiment, the labor management system includes a driver terminal, an administrator terminal, and a server that can communicate with each other, and includes a position identification means for identifying a position where the vehicle has stopped. In the vehicle, the driver terminal, or the administrator terminal A first acquisition means for acquiring a first time input by an input device, a second acquisition means for acquiring a second time input by the input device, a shipper identification means for identifying a shipper corresponding to the position identified by the position identification means, a calculation means for calculating a rest time of a driver of the vehicle based on the first time and the second time when the shipper identification means cannot identify a shipper, and a recording means for recording the rest time calculated by the calculation means. Each of the position identification means, the first acquisition means, the second acquisition means, the shipper identification means, the calculation means, and the recording means is realized by any one of the driver terminal, the administrator terminal, and the server, or by cooperation of the administrator terminal, the driver terminal, and the server, a labor management system.

[0007] A computer program according to an embodiment causes a computer to perform a position identification means for identifying a position where a vehicle has stopped. In the vehicle, driver terminal, or administrator terminalFunction as first acquisition means for acquiring a first time input by an input device, second acquisition means for acquiring a second time input by the input device, shipper identification means for identifying a shipper corresponding to the position identified by the position identification means, calculation means for calculating the waiting time of the driver of the vehicle at the position identified by the position identification means based on the first time and the second time, and recording means for recording waiting information including the shipper identified by the shipper identification means and the waiting time calculated by the calculation means. According to another aspect of the embodiment, the computer program causes a computer to function as position identification means for identifying the position where the vehicle has stopped. In the vehicle, driver terminal, or administrator terminal Function as first acquisition means for acquiring a first time input by an input device, second acquisition means for acquiring a second time input by the input device, shipper identification means for identifying a shipper corresponding to the position identified by the position identification means, calculation means for calculating the waiting time of the driver of the vehicle at the position identified by the position identification means based on the first time and the second time, and recording means for recording waiting information including the shipper identified by the shipper identification means and the waiting time calculated by the calculation means.

Advantages of the Invention

[0008] According to the present invention, it is possible to improve the business management system of a transportation company. Other effects of the present invention are derived from this specification and the accompanying drawings.

Brief Description of the Drawings

[0009]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

Figure 19

Embodiments for Carrying Out the Invention

[0010] Some embodiments will be described with reference to the drawings. In each of the embodiments described below, a labor management system and a computer program for managing the labor of truck drivers are disclosed.

[0011] [First Embodiment] FIG. 1 is a block diagram showing a configuration example of a labor management system according to the first embodiment. The labor management system includes a manager terminal 1 disposed at a workplace, a digital tachograph 2 mounted on a vehicle, and a server 3. The digital tachograph 2 functions as a driver terminal in the present embodiment.

[0012] As the manager terminal 1, for example, a personal computer can be used. The manager terminal 1 may be a portable device that can be carried by a manager, such as a tablet or a smartphone.

[0013] The manager terminal 1 includes a controller 10 including a processor and a memory, a storage device 11, a display 12, an input device 13, a speaker 14, and an interface 15 for external connection. The controller 10 can realize various processes disclosed in the present embodiment by the processor executing a computer program stored in the memory.

[0014] The input device 13 includes, for example, a keyboard, a mouse for operating a GUI (Graphical User Interface) displayed on the display 12, and a touch panel provided on the display 12.

[0015] A communication device 16 capable of communicating with the network N is communicatively connected to the interface 15 by wire or wirelessly. The interface 15 may be further connected to an attendance / leaving terminal 17 for a driver to perform attendance and leaving processes at a workplace.

[0016] The digital tachograph 2 includes a controller 20 including a processor and a memory, a storage device 21, a built-in display 22 and a speaker 23, and an interface 24 for external connection. The controller 20 can realize various processes disclosed in the present embodiment by the processor executing a computer program stored in the memory.

[0017] Connected to the interface 24 are a communication device 41 capable of communicating with the network N, a display 42, an input device 43, a travel sensor 44, and a GPS (Global Positioning System) receiver 45 by wired or wireless communication. These elements connected to the interface 24 may be provided in a vehicle console or the like, or may be part of the digital tachograph 2. Note that the digital tachograph 2 may not include the display 22 and the speaker 23.

[0018] The input device 43 includes buttons and a touch panel for operating the GUI displayed on the display 42. Further, the input device 43 includes various buttons for inputting the work type of the driver and the state of the vehicle, such as departure, return, loading, unloading, break, standby, accommodation, refueling, boarding, etc. The travel sensor 44 detects travel-related parameters such as the speed, acceleration, engine speed, and engine temperature of the vehicle. The GPS receiver 45 receives GPS signals from satellites and detects the position of the vehicle based on the signals.

[0019] The server 3 is communicatively connected to the network N. The server 3 may be disposed outside the business office or may be disposed in the business office. The server 3 may be a server included in a cloud system. In this case, cloud computing in the form of SaaS (Software as a Service) or the like can be used for the processes executed by elements of the labor management system such as the administrator terminal 1 and the digital tachograph 2.

[0020] The server 3 stores a management database 30 and a location information master 31. The management database 30 includes information regarding the work histories of a plurality of drivers, future work schedules, and the like. The location information master 31 may be a part of the management database 30.

[0021] The administrator terminal 1 can acquire information from the management database 30 and the location information master 31 of the server 3 or store information in the management database 30 through communication via the communication device 16 and the network N. The digital tachograph 2 can also execute similar processing through communication via the communication device 41 and the network N. In addition, the administrator terminal 1 and the digital tachograph 2 can exchange information with each other via the communication devices 16, 41 and the network N.

[0022] Based on parameters such as the speed detected by the travel sensor 44, the input from the input device 43, and the signal received by the GPS receiver 45, the controller 20 of the digital tachograph 2 stores operation information including the vehicle's operation start time, operation end time, so-called legal three elements (instantaneous vehicle speed, travel distance, travel time) at each time from the operation start time to the operation end time, the work type (standby, rest, break, loading, unloading, refueling, boarding, etc.) at each time, and the vehicle's position data (address) in the storage device 21. Furthermore, the controller 20 transmits the operation information to the server 3. The server 3 stores the operation information in the management database 30. The controller 10 of the administrator terminal 1 can access the management database 30 to acquire the operation information and use it for display on the display 12 and other processes. The operation information may be directly transmitted from the digital tachograph 2 to the administrator terminal 1.

[0023] In the labor management system configured as described above, by communicating the administrator terminal 1, the digital tachograph 2, and the server 3 via the network N, the labor status of the driver, the running status of the vehicle, etc. can be grasped in real time at both the workplace and the vehicle.

[0024] For example, based on information such as the management database 30, the administrator terminal 1 causes the display 12 to display a list of driver information indicating the working status of each driver belonging to the business office and the driving status of the vehicle. As a result, the administrator can extremely easily grasp the working status of each driver, the driving status of the vehicle, etc., and can also give necessary instructions to drivers in remote locations.

[0025] FIG. 2 is a diagram showing an example of the data structure of the record R constituting the location information master 31. Each record R of the location information master 31 includes position data, location information, and location type.

[0026] The position data of the record R is information indicating a position on the map. The position data may be, for example, a character string indicating an address, or may be coordinates corresponding to a positioning system such as GPS.

[0027] For example, the location information of the record R is identification information such as a character string or a code indicating a unique location name (company name, customer name, etc.) such as a shipper, a gas station (GS), a convenience store, a parking area (PA), the business office of the carrier, a ferry terminal, etc. When the name of the shipper is recorded as the location information, this does not necessarily mean that the shipper is located at the position indicated by the position data. The position data associated with the shipper in the record R may indicate the delivery destination of the goods received the transportation request.

[0028] The location type of the record R is identification information indicating to which type among types such as a shipper, a gas station, a convenience store, a parking area, a business office, a ferry terminal, etc. the name indicated by the location information belongs.

[0029] The labor management system according to the present embodiment executes the process shown in the flowchart of FIG. 3 in response to the vehicle stopping. The process (steps) shown in the flowchart may be realized by the cooperation of the controller 10 of the administrator terminal 1, the controller 20 of the digital tachograph, the server 3, etc., or may be realized by any one of these alone.

[0030] The vehicle stop that triggers the process shown in the flowchart of FIG. 3 is, for example, a state where the vehicle engine has stopped, a state where the vehicle speed detected by the traveling sensor 44 is 0 km / s over a certain period of time, or a state where the position of the vehicle specified by the signal received by the GPS receiver 45 does not change over a certain period of time. In addition to these, various methods such as the operation of a specific button can be adopted as the trigger to start the process shown in the flowchart.

[0031] At the beginning of the process start of the flowchart in FIG. 3, first, it is determined whether or not the driver has input the work type (waiting, rest, break, loading, unloading, refueling, boarding, etc.) (step S101). The driver can input the work type by, for example, the input device 43.

[0032] If the work type has not been input (NO in step S101), it is determined whether or not a predetermined time T1 has elapsed since the vehicle stopped (step S102). For example, the predetermined time T1 can be appropriately set by the carrier, such as 1 minute, 5 minutes, or 10 minutes.

[0033] If the predetermined time T1 has not elapsed (NO in step S102), the process returns to the process of step S101. Eventually, when the predetermined time T1 has elapsed (YES in step S102), it is determined whether the stop setting regarding the handling of the vehicle stop time is either a standby setting that treats the stop time as standby or a rest setting that treats it as rest (step S103). The stop setting can be changed, for example, by the administrator terminal 1.

[0034] If the stop setting is the standby setting (standby in step S103), the stop process A is executed. Also, if the stop setting is the rest setting (rest in step S103), the stop process B is executed.

[0035] On the other hand, if the work type is input before the lapse of the predetermined time T1 in step S102 (YES in step S101), the process corresponding to the input work type is executed. That is, if the input work type is standby (standby in step S104), the stop process A is executed. Also, if the input work type is break (break in step S104), the stop process B is executed. Further, if the input work type is loading or unloading (loading / unloading in step S104), the stop process C is executed. In the present embodiment, these stop processes A, B, and C will be described, but for other input work types, the stop process corresponding to the input is also executed.

[0036] FIG. 4, FIG. 5, and FIG. 6 are flowcharts showing examples of the stop process A, the stop process B, and the stop process C, respectively. The processes (steps) shown in these flowcharts may be realized by the cooperation of the controller 10 of the administrator terminal 1, the controller 20 of the digital tachograph, and the server 3, etc., or may be realized by any one of these alone.

[0037] In the stop process A shown in FIG. 4, first, the stop position of the vehicle is specified (step S201). For example, the stop position is the current position of the vehicle and can be specified based on the signal received by the GPS receiver 45.

[0038] Subsequently, the shipper corresponding to the stop position specified in step S201 is searched from the shipper information master 31 (step S202). In step S202, a record R that includes the position data corresponding to the stop position specified in step S201 and whose location type is shipper is extracted from the shipper information master 31. At this time, not only when the stop position specified in step S201 exactly matches the position indicated by the position data, but also when the two can be regarded as substantially the same, the record R including the position data may be extracted. Here, substantially the same may include the case where the stop position specified in step S201 is located within a predetermined radius (for example, within several tens of meters) of the position indicated by the position data of the record R.

[0039] After step S202, it is determined whether the shipper corresponding to the parking position can be identified (step S203). That is, it is determined whether the shipper corresponding to the parking position identified in step S201 is registered in the location information master 31, more specifically, whether the record R is extracted in step S202.

[0040] If the record R is extracted (YES in step S203), the first time is obtained (step S204). For example, the first time is the parking time of the vehicle that triggered the process shown in the flowchart of FIG. 3. In this case, when the vehicle parks, its parking time is recorded in the storage device 21, the management database DB, etc., and in step S204, the parking time is read out. As another example, the first time may be the time when a predetermined time T1 in step S102 has elapsed since the parking time of the vehicle. As still another example, the first time may be the time input by the input devices 13, 43, etc. Also, when the parking process A is started in response to the input of the standby work type by the input device 43, the first time may be the time of the input.

[0041] After step S204, the first time is recorded in the management database 30, etc. as the standby start time of the driver (step S205). After the standby start time is recorded, until the standby end time is recorded, the labor state of the driver is in the standby for loading or unloading.

[0042] After step S205, it is determined whether a predetermined time T2 (for example, 30 minutes) has elapsed since the first time (step S206). If the predetermined time T2 has not elapsed (NO in step S206), it is determined whether the standby has ended (step S207). If the standby has not ended (NO in step S207), the process returns to the process of step S206.

[0043] If a predetermined time T2 has elapsed before the standby ends (YES in step S206), a warning regarding the standby is executed (step S208). The warning may be a warning display for the driver by the vehicle displays 22, 42, or may be an output of a warning message or a warning sound by the speaker 23. Further, the warning may be a warning display for the administrator by the display 12 of the administrator terminal 1, or may be an output of a warning message or a warning sound by the speaker 14. For example, the warning display using the display 12 may be performed by changing the display color of the area of the driver in the list screen of a plurality of drivers belonging to the business office. The area may include the elapsed time since the start of standby. Such a warning can enable the driver and the administrator to recognize a situation where the elapsed time since the start of standby has reached a predetermined time T2 or more.

[0044] For example, when the parking state of the vehicle is released, it is determined in step S207 that the standby has ended (YES in step S207). Here, the parking state is released, for example, when the vehicle engine starts, when the vehicle speed detected by the traveling sensor 44 becomes not 0 km / s, or when the position of the vehicle specified by the signal received by the GPS receiver 45 changes. As another example, in step S207, it may be determined that the standby has ended in response to an operation of a button such as a loading button or an unloading button of the input device 43.

[0045] After the standby ends, a second time is acquired (step S209). The second time is, for example, the time when the parking state of the vehicle is released, that is, the current time, and can be obtained from the system clock of the digital tachograph 2 or the like. As another example, the second time may be the time input by the input devices 13, 43, etc.

[0046] After step S209, a waiting time is calculated (step S210). The waiting time is, for example, the elapsed time from the first time obtained in step S204 to the second time obtained in step S209. In this case, the waiting time corresponds to the parking time of the vehicle. As another example, the waiting time calculated in step S210 may be the elapsed time or the parking time minus a predetermined fixed time or an arbitrary time.

[0047] After step S210, waiting information is recorded in a management database 30 or the like (step S211). For example, this waiting information includes the driver's identification information, the shipper's identification information indicated by the location information of the record R extracted in step S202, the first time obtained in step S204, the second time obtained in step S209, and further the waiting time calculated in step S210. With step S211, the parking process A ends.

[0048] Here, when the shipper corresponding to the parking position specified in step S201 is not registered in the location information master 31 (NO in step S203), the administrator is notified that the vehicle is parked at an unregistered shipper's location (step S212). For example, this notification is made by displaying a screen on the display 12 of the administrator terminal 1. Note that in step S212, a similar notification may be made to the driver using a display 42 or the like.

[0049] FIG. 7 is a diagram showing an example of a notification screen 50 displayed on the display 12 in step S212. For example, the notification screen 50 includes a message indicating that the vehicle has stopped at an unregistered shipper's location and a message indicating that the location name should be entered. Further, the notification screen 50 includes a date / time box 51, a driver name box 52, a parking position box 53, a location name box 54, a save button 55, and a cancel button 56.

[0050] In the date and time box 51, the parking time of the vehicle that triggered the process shown in the flowchart of FIG. 3, for example, is displayed. In the driver name box 52, the name of the driver is displayed. In the parking position box 53, the address indicating the parking position specified in step S201 is displayed.

[0051] With such a notification screen 50 displayed, modification of the location name is accepted (step S213). The administrator can input the location name (consignor) into the location name box 54 by operating the input device 13 based on, for example, the driving schedule of the driver on that day.

[0052] The notification screen 50 may further include a candidate display button 54a. When the candidate display button 54a is operated, candidates for the consignor are displayed. Such candidates may be all the consignors registered in the location information master 31, or may be consignors associated with location data close to the address displayed in the parking position box 53 among these consignors. When the administrator selects any one from such candidates, the selected consignor is input into the location name box 54.

[0053] When the save button 55 is operated, it is determined whether the consignor input in the location name box 54 at that time is registered in the location information master 31 (step S214). As a result, if it is determined that the consignor is registered (YES in step S214), the processes of steps S204 to S211 are executed.

[0054] On the other hand, when the consignor input in the location name box 54 at the time of operating the save button 55 is not registered in the location information master 31 (NO in step S214), or when the cancel button 56 of the notification screen 50 is operated, a confirmation screen for asking permission to process the parking time as a break time is displayed on the display 12 (step S215).

[0055] In the notification screen 50, it may be possible to correct the parking position (address) in the parking position box 53. Further, in step S214, if the location information master 31 is searched based on the corrected parking position in the parking position box 53, and there is no record R including the position data corresponding to the parking position, or even if such a record R exists but the location type is not the shipper, the processing after step S215 may be executed.

[0056] FIG. 8 is a diagram showing an example of the confirmation screen 60. For example, the confirmation screen 60 includes an OK button 61 and a cancel button 62 together with a message asking whether to process the parking time as a break. When the OK button 61 is operated, that is, when it is permitted to process the parking time as a break time, the processing of steps S216 to S222 is executed. On the other hand, when the cancel button 62 is operated, that is, when it is denied to process the parking time as a break time, the parking process A ends. As another example, when the cancel button 62 is operated, a screen (for example, the selection screen of FIG. 12 described later) for selecting the work type (waiting, loading, unloading, refueling, boarding, etc.) may be displayed, and the parking time may be recorded in the management database 30 as the work type selected on the screen.

[0057] After the confirmation screen 60 is displayed, if a certain period of time elapses without the screen being operated, it may be processed as if the OK button 61 or the cancel button 62 has been operated. In this case, the labor management system may have a function of presetting which of the OK button 61 and the cancel button 62 is to be processed as having been operated. Such a setting function can be provided, for example, on the administrator terminal 1, but is not limited to this example.

[0058] Note that the processing of step S215 may be executed before step S212 or after step S216. Further, the confirmation screen 60 may be displayed on the vehicle display 42 or the like. In this case, the confirmation screen 60 is operated by the driver.

[0059] In step S216, the first time is acquired in the same way as in step S204. After that, the first time is recorded in the management database 30 or the like as the rest start time of the driver (step S217). Until the rest end time is recorded after the rest start time is recorded, the working state of the driver is in a rest state.

[0060] After step S217, it is determined whether the rest has ended (step S218). For example, when the parking state of the vehicle is released, it is determined in step S218 that the rest has ended (YES in step S218), and the second time is acquired in the same way as in step S209 (step S219).

[0061] After step S219, the rest time is calculated (step S220). The rest time is, for example, the elapsed time from the first time acquired in step S216 to the second time acquired in step S219. In this case, the rest time corresponds to the parking time of the vehicle. As another example, the rest time calculated in step S220 may be the elapsed time or the parking time minus a predetermined fixed time or an arbitrary time.

[0062] After step S220, the rest information is recorded in the management database 30 or the like (step S221). For example, this rest information includes the identification information of the driver, the first time acquired in step S216, the second time acquired in step S219, and further the rest time calculated in step S220.

[0063] After step S221, for example, by displaying on the display 12,42, the driver and the administrator are notified that the parking time has been processed as the rest time (step S222). As described above, the parking process A is executed when the parking setting is standby or when standby is input as the work type. Through the notification in step S222, the driver and the administrator can recognize that the parking time has been treated as the rest time even in these cases. Parking process A ends with step S222.

[0064] Note that a third time may be further considered in calculating the waiting time in step S210. For example, the third time is a time serving as a criterion for whether the process can be performed as the waiting time, and the waiting before that time is of a nature to exclude the shipper's responsibility. As an example, the third time may be the business start time of the operation entity such as the loading point or the unloading point, the reservation time for loading or unloading by the carrier, the designated time for loading or unloading from the shipper, etc., or the reception time when waiting is accepted at the loading point or the unloading point.

[0065] When considering the third time in step S210, for example, the following calculation methods (1) to (3) can be applied. (1) When the first time is later than the third time In this case, the elapsed time from the first time to the second time is calculated as the waiting time.

[0066] (2) When the first time is earlier than the third time and the second time is later than the third time In this case, the elapsed time from the third time to the second time is calculated as the waiting time. Note that the elapsed time from the first time to the third time may be recorded in the management database 30 as the rest time.

[0067] (3) When both the first time and the second time are earlier than the third time In this case, the waiting time is calculated as zero. Note that the elapsed time from the first time to the second time may be recorded in the management database 30 as the rest time.

[0068] In calculating the waiting time in step S210, in addition to the third time, time zones such as the lunch break at the loading point or the unloading point may be further considered. That is, when the time from the first time to the second time overlaps with such a time zone, the overlapping part may be deducted from the waiting time. Further, the overlapping part may be recorded in the management database 30 as the driver's rest time.

[0069] In the parking process B shown in the flowchart of FIG. 5, steps S201 to S221 are the same as those in the parking process A. As described above, the parking process B is executed when the parking setting is a break or when the driver inputs a break as the work type. Therefore, in the example of FIG. 5, the notification (step S222 in the parking process A) when recording the parking time as a break is omitted.

[0070] On the other hand, in the parking process B, after recording the waiting information in step S211, for example, the driver and the administrator are notified that the parking time has been processed as the waiting time by displaying on the display 12,42 (step S301). Thereby, the driver and the administrator can recognize that the parking time is treated as the waiting time. A notification similar to step S301 may be executed before step S211. The notification may include a message indicating that the parking time is processed as the waiting time. For example, the notification may be executed before the process of step S204 after it is determined in step S203 or step S214 that the shipper corresponding to the parking position is registered in the location information master 31 (YES in steps S203, S214). Also, the notification may be executed between step S204 and step S205, or between step S205 and step S206.

[0071] In the parking process C shown in the flowchart of FIG. 6, steps S201 to S204, S207, S209, S212 to S222 are the same as those in the parking process A. In the parking process C, after the first time is obtained in step S204, the first time is recorded in the management database 30 etc. as the start time of the driver's loading or unloading (step S401). Until the end time is recorded after the start time of loading or unloading is recorded, the working state of the driver is in the process of loading or unloading.

[0072] Also, in the parking process C, after the second time is acquired in step S209, the loading / unloading information is recorded in the management database 30 or the like (step S402). For example, this loading / unloading information includes the identification information of the driver, the identification information of the shipper indicated by the location information of the record R extracted in step S202, the first time acquired in step S204, and the second time acquired in step S209. The loading / unloading information may include the working time of loading or unloading (for example, the elapsed time from the first time to the second time).

[0073] According to the above-described embodiment, it is possible to improve the business management system of the carrier. Specifically, when the vehicle stops, the parking position of the vehicle is acquired based on GPS or the like, the shipper corresponding to the parking position is specified, and the waiting information regarding the shipper is recorded. Thereby, even when the driver or the administrator does not make any special input, it is possible to obtain the waiting information for the appropriate shipper.

[0074] Also, when the shipper corresponding to the parking position is not registered in the location information master 31, the parking time is recorded as the rest time. Thereby, it is possible to accurately manage the working state of the driver.

[0075] Also, according to the parking processes A and C, even when the driver inputs waiting, loading, or unloading as the work type at the time of parking (waiting or loading / unloading in step S104), if the shipper is not registered in the location information master 31, the parking time is recorded as the rest time. Further, according to the parking process B, even when the driver inputs rest as the work type at the time of parking (rest in step S104), if the shipper is registered in the location information master 31, the parking time is recorded as the waiting time. By these processes, it is possible to correct the driver's input and record appropriate labor information according to the situation.

[0076] In addition, in the parking processes A, B, and C, even if the shipper corresponding to the parking position is not registered in the location information master 31, the shipper can be corrected by the processes of steps S212 to S214. Thereby, it is possible to cope with a situation where the parking position and the position data of the location information master 31 are inconsistent due to GPS position deviation, incorrect registration of the position data of the location information master 31, or the like. In addition to the above, various suitable effects can be obtained from this embodiment.

[0077] The configuration disclosed in this embodiment can be modified in various ways. For example, in this embodiment, it is assumed that the parking setting for standby or rest has been made in advance. If there is no parking setting, it may be set by default so that either parking process A or parking process B is executed. Also, the labor management system may not have the function of parking setting. In this case, parking process A or parking process B may be executed without going through the process of step S103. As a more specific example, in the parking process when there is no parking setting function, first, the processes of steps S201 to S203 are executed. When it is determined in step S203 that there is a shipper registration (YES in step S203), at least one of the administrator and the driver is notified that the parking time is to be processed as standby time, and then the processes of steps S204 to S211 and S301 are executed. Also, when it is determined in step S203 that there is no shipper registration (NO in step S203), at least one of the administrator and the driver is notified that the parking time is to be processed as rest time, and then the processes of steps S216 to S222 are executed. Note that, similar to parking processes A and B, the processes of steps S212 to S214 may be executed.

[0078] For example, the notification to the administrator to process the parking time as waiting time or break time may be made by displaying a message on the display 12 of the administrator terminal 1, or by changing the labor status of the driver to "waiting" or "break" on the driver information list screen showing the labor status of each driver and the driving status of the vehicle displayed on the display 12. Further, the notification to the driver to process the parking time as waiting time or break time may be made by displaying a message on the display 22 of the digital tachograph 2 and the display 42 of the vehicle and by voice output from the speaker 23. The notification methods to the administrator or the driver exemplified here are also applicable to other notifications disclosed in this specification.

[0079] In the parking processes A, B, and C, the processes of steps S212 to S215 may be omitted. That is, in the parking processes A, B, and C, when there is no registration of the shipper corresponding to the parking position in the location information master 31 (NO in step S203), the parking time may be recorded as break time without displaying the notification screen 50 or the like. Note that there may be a case where there is no record R including the position data corresponding to the parking position in the location information master 31, or a case where there is a record R in which the shipper is registered as location information but the position data is not registered. In step S203, it is determined that there is no registration even in such a case (NO in step S203). And when steps S212 to S215 are omitted, when it is determined that there is no registration in step S203, the parking time is recorded as break time without displaying the notification screen 50 or the like.

[0080] The processes shown in the flowcharts of FIGS. 3 to 6 do not necessarily all need to be executed in real time. For example, the calculation and recording of the waiting time in steps S210 and S211, and the calculation and recording of the break time in steps S220 and S221 can be executed at an appropriate timing such as when aggregating the labor information of the driver based on the information such as the first time, the second time, and the third time stored in the management database 30 or the like.

[0081] As described above, the execution entity of the processes (steps) shown in the flowcharts of FIGS. 3 to 6 is not particularly limited. As an example, the processes of steps S101 to S104, S201 to S211, S215 to S221, and S401 to S402 may be executed by the controller 20 of the digital tachograph 2, and the processes of steps S212 to S214, S222, and S301 may be executed by the controller 10 of the administrator terminal 1.

[0082] In addition, the computer programs for causing computers such as the administrator terminal 1, the digital tachograph 2, and the server 3 to realize the processes related to the respective steps do not have to be stored in a single memory, and may be constituted by modules distributed and stored in the memories provided in the plurality of computers respectively. In this case, each module can be executed by the respective processors of the plurality of computers.

[0083] For example, in the present embodiment, the processes such as step S201 constitute position specifying means for specifying the position where the vehicle has stopped. The processes such as steps S202, S203, S214 constitute shipper specifying means for specifying the shipper. The processes such as steps S210, S220 constitute calculating means for calculating the waiting time and rest time. The processes such as steps S211, S221, S402 constitute recording means for recording waiting information, rest information, loading / unloading information, etc. In one aspect of the present embodiment, when the shipper can be specified by the above shipper specifying means, this recording means records the waiting time (for example, the elapsed time from the first time to the second time) calculated by the above calculating means, and when the shipper can be specified by the above shipper specifying means, at least a part of the elapsed time from the first time to the second time is recorded as the rest time. The processes such as step S212 constitute notification means for notifying the administrator or the driver when the shipper cannot be specified. The processes such as steps S204, S209, S216, S219 constitute acquisition means for acquiring the first time and the second time. Note that the term "acquisition" in this specification may include various operations for obtaining information, such as reading information from some storage means, receiving it, calculating it, etc. The processes such as step S215 constitute confirmation means for seeking permission to treat the parking time (the elapsed time from the first time to the second time) as the rest time. In addition to these, various means constituting the labor management system can be specified from the present embodiment and each of the embodiments described later.

[0084] [Second Embodiment] The second embodiment will be described. The same configurations as those in the first embodiment can be applied to the configurations not particularly mentioned.

[0085] FIG. 9 is a diagram showing an example of the data structure of a record R constituting the location information master 31 according to the second embodiment. In the present embodiment, each record R further includes the type of work to be performed by the driver in addition to the position data, location information, and location type. As the type of work, for example, operations such as waiting, resting, loading, unloading, refueling, and boarding can be set.

[0086] The labor management system according to this embodiment executes the processes shown in the flowchart of FIG. 10 in response to the vehicle stopping. The flowchart of FIG. 10 includes the processes of steps S101, S102, and S104, similar to the flowchart of FIG. 3, but does not include the process of step S103. When the work type is not input by operating the input device 43 or the like (NO in step S101) and a predetermined time T1 has elapsed (YES in step S102), the stop process D is executed.

[0087] FIG. 11 is a flowchart showing an example of the stop process D. The processes (steps) shown in the flowchart may be realized by the cooperation of the controller 10 of the administrator terminal 1, the controller 20 of the digital tachograph, and the server 3, etc., or may be realized by any one of them alone.

[0088] In the stop process D, first, the stop position of the vehicle is specified in the same way as step S201 (step S501). Subsequently, the record R corresponding to the stop position specified in step S501 is retrieved from the location information master 31 (step S502). Further, it is determined whether the stop position is registered in the location information master 31, that is, whether the record R including the position data corresponding to the stop position is extracted (step S503).

[0089] When the record R is extracted (YES in step S503), the first time (stop time) is acquired in the same way as step S204 (step S504). Further, the first time is recorded in the management database 30 or the like as the start time of the work corresponding to the work type of the record R (step S505).

[0090] Thereafter, it is determined whether the work has ended (step S506). For example, when the stopped state of the vehicle is released, it is determined in step S506 that the work has ended (YES in step S506). As another example, it may be determined that the work has ended in response to the button of the input device 43 being operated.

[0091] After the operation is completed, a second time is obtained in the same manner as in step S209 (step S507). Further, the working time required for the operation is calculated (step S508). The working time is, for example, the elapsed time from the first time to the second time. In this case, the working time corresponds to the parking time of the vehicle. As another example, the working time may be the time obtained by subtracting a predetermined fixed time or an arbitrary time from the elapsed time or the parking time.

[0092] After calculating the working time, the operation information is recorded in the management database 30 or the like (step S509). For example, this operation information includes the driver's identification information, the location information and operation type included in the record R extracted in step S502, the first time obtained in step S504, the second time obtained in step S507, and further the working time calculated in step S508.

[0093] On the other hand, when the record R is not extracted in step S502 (NO in step S503), the selection of the operation type by the driver is accepted (step S510). This acceptance of the selection is performed, for example, by displaying a selection screen for the operation type on the display 42. Note that the selection of the operation type may be performed by the administrator. In this case, for example, a selection screen for the operation type is displayed on the display 12.

[0094] FIG. 12 is a diagram showing an example of a selection screen 70 for the operation type. For example, the selection screen 70 includes a plurality of operation type buttons 71 indicating the operation type, a cancel button 72, and a message prompting the selection of the operation type. For example, when the cancel button 72 is operated, the parking process D ends.

[0095] In FIG. 12, as a plurality of work type buttons 71, there are exemplified a standby button 71a for selecting standby as a work type, a break button 71b for selecting a break as a work type, a loading button 71c for selecting loading as a work type, an unloading button 71d for selecting unloading as a work type, a refueling button 71e for selecting refueling as a work type, a boarding button 71f for selecting boarding a ferry as a work type, and a PA button 71g for selecting a break in a parking area. A driver or a manager can select a work type by operating these buttons.

[0096] When any one of the work type buttons 71 is operated, the first time is acquired in the same manner as in step S504 (step S511). Then, the first time is recorded in a management database 30 or the like as the start time of the work of the driver corresponding to the operated work type button 71 (step S512).

[0097] After step S512, it is determined whether the work has ended in the same manner as in step S506 (step S513), and the work time required for the work is calculated in the same manner as in step S508 (step S515). After the calculation of the work time, work information is recorded in a management database 30 or the like (step S516). For example, this work information includes the identification information of the driver, the work type selected in step S510, the first time acquired in step S511, the second time acquired in step S514, and further the work time calculated in step S515.

[0098] After step S509 or step S516, a notification to the driver and the administrator is made, for example, by display on the display 12,42 (step S517). When step S517 is carried out after step S509, the notification is made by a screen including a message etc. stating that the parking time has been processed as the work type specified based on the location information master 31. Also, when step S517 is carried out after step S516, the notification is made by a screen including a message etc. stating that the parking time has been processed as the work type selected in step S510. Parking process D ends with step S517.

[0099] A notification similar to step S517 may be executed before step S509. The notification may include a message etc. stating that the parking time has been processed as the work type specified based on the location information master 31. For example, the notification may be executed between step S503 and step S504, between step S504 and step S505, or between step S505 and step S506.

[0100] When the work type of the record R corresponding to the parking position in step S502 is boarding a ferry, or when boarding a ferry is selected as the work type by operating the boarding button 71f in step S510, the parking time may be recorded as any one of a rest, a split rest period, and a rest period according to the length of the parking time. Specifically, when the elapsed time from the first time to the second time is less than the first reference time (for example, 4 hours), it is recorded as a rest time, when the elapsed time is equal to or more than the first reference time and less than the second reference time (for example, 9 hours), it is recorded as a split rest period, and when the elapsed time is equal to or more than the second reference time, it may be recorded as a rest period. Also, when the location type of the record R corresponding to the parking position in step S502 is a parking area, or when taking a rest in the parking area is selected as the work type by operating the PA button 71g in step S510, similar to when boarding a ferry, the parking time may be recorded as a rest time, a split rest period, or a rest period based on the first reference time and the second reference time.

[0101] In addition, when the work type corresponding to the parking position is not registered in the location information master 31, the selection or modification of the work type may be performed afterwards by the administrator or the driver. In this case, for example, work information with an undetermined work type is recorded in step S516, and then a screen such as the selection screen 70 for the administrator or the driver to select or modify the work type in the work information is called, and the work type may be selected or modified through the screen.

[0102] In the above-described present embodiment, even when the driver does not input the work type when the vehicle is parked, the parking time is recorded as work of the work type set according to the parking position. Thereby, even if the driver forgets to input the work type, the labor state can be recorded.

[0103] Also, when the parking position is not registered in the location information master 31, the selection of the work type is accepted in step S510. Thereby, a more accurate record of the labor state can be made.

[0104] Similar to the first embodiment, the computer program for causing computers such as the administrator terminal 1, the digital tachograph 2, and the server 3 to realize the processing according to each step does not need to be stored in a single memory, and may be configured by modules distributed and stored in the memories provided in a plurality of computers respectively. In this case, each module can be executed by the respective processors of a plurality of computers.

[0105] The processing of steps S510 to S517 may be executed instead of steps S212 to S222 in the parking processes A, B, and C of the first embodiment, or instead of steps S215 to S222.

[0106] [Third Embodiment] The third embodiment will be described. The same configurations as those in the first and second embodiments can be applied to the configurations not particularly mentioned.

[0107] The labor management system according to this embodiment executes the processes shown in the flowchart of FIG. 13 in response to the vehicle stopping. The flowchart of FIG. 13 includes the processes of steps S101 and S102, similar to the flowchart of FIG. 3, but does not include the processes of steps S103 and S104. When the work type is not input by operating the input device 43 or the like (NO in step S101) and a predetermined time T1 has elapsed (YES in step S102), the same parking process D as in the second embodiment is executed. On the other hand, when the work type is input by operating the input device 43 or the like (YES in step S101), the parking process E is executed.

[0108] FIG. 14 is a flowchart showing an example of the parking process E. The processes (steps) shown in the flowchart may be realized by the cooperation of the controller 10 of the administrator terminal 1, the controller 20 of the digital tachograph, and the server 3, etc., or may be realized by any one of them alone.

[0109] The parking process E shown in FIG. 14 includes the processes of steps S501 to S509 and S511 to S517, similar to the parking process D shown in FIG. 11, but does not include the process of step S510. That is, since the parking process E is executed when the work type is input by the driver, when the work type corresponding to the parking position is not registered in the location information master 31 (NO in step S503), the processes of steps S511 to S516 are executed without accepting the selection of the work type on the selection screen 70 or the like. Even with the configuration of this embodiment, the same effects as in the second embodiment can be obtained.

[0110] [Fourth Embodiment] The fourth embodiment will be described. The same configurations as those in the first to third embodiments can be applied to the configurations not particularly mentioned.

[0111] In this embodiment, it is assumed that there is a priority setting for whether to record the parking time of the vehicle as the work type registered in the location information master 31 or as the work type input by operating the input device 43 or the like. Hereinafter, the setting that prioritizes the work type registered in the location information master 31 is called "registration priority", and the setting that prioritizes the work type input by operating the input device 43 or the like is called "input priority". Such a priority setting can be switched by, for example, the administrator terminal 1. The priority setting may be set collectively for all drivers belonging to the workplace, or may be set for each driver.

[0112] The labor management system according to this embodiment executes the processing shown in the flowchart of FIG. 15 in response to the vehicle stopping. The flowchart of FIG. 15 includes the processing of steps S101 and S102 as in the flowchart of FIG. 3, but does not include the processing of steps S103 and S104. When the work type is not input by operating the input device 43 or the like (NO in step S101) and a predetermined time T1 has elapsed (YES in step S102), the same parking process D as in the second embodiment is executed.

[0113] Also, in the flowchart of FIG. 15, when the work type is input by operating the input device 43 or the like (YES in step S101), the priority setting of the driver is determined (step S105). When the priority setting is registration priority (registration priority in step S105), the same parking process E as in the third embodiment is executed. On the other hand, when the priority setting is input priority (input priority in step S105), the parking process F is executed.

[0114] FIG. 16 is a flowchart showing an example of the parking process F. The processing (steps) shown in the flowchart may be realized by the cooperation of the controller 10 of the administrator terminal 1, the controller 20 of the digital tachograph, the server 3, etc., or may be realized by any one of these alone.

[0115] In the parking process F, first, similar to step S501, the parking position of the vehicle is specified (step S601). Subsequently, similar to step S504, the first time (parking time) is acquired (step S602). Further, the first time is recorded in the management database 30 or the like as the start time of the work corresponding to the work type input by the driver (step S603).

[0116] Thereafter, similar to step S506, it is determined whether the work has been completed (step S604). When it is determined that the work has been completed (YES in step S604), similar to step S507, the second time is acquired (step S605). Further, similar to step S508, the working time required for the work is calculated (step S606).

[0117] After calculating the working time, the work information is recorded in the management database 30 or the like (step S607). For example, this work information includes the driver's identification information, the work type input by the input device 43 or the like, the first time acquired in step S602, the second time acquired in step S605, and further the working time calculated in step S606. The parking process F ends at step S607.

[0118] Thus, in the present embodiment, when the priority setting is registration priority, in response to the work type being input by the driver, the parking process E shown in the flowchart of FIG. 14 is executed. In the parking process E, if the work type corresponding to the parking position is registered in the location information master 31, the parking time is recorded as the work related to that work type, and if not, the parking time is recorded as the work related to the work type input by the driver. That is, the registration in the location information master 31 takes precedence over the input by the driver.

[0119] On the other hand, when the priority setting is input priority, regardless of the registration in the location information master 31, the parking time is recorded as the work related to the work type input by the driver. That is, the input by the driver takes precedence over the registration in the location information master 31.

[0120] By incorporating such priority settings, it is possible to significantly improve the accuracy of driver labor management. For example, when there are many input errors in the work type entered by the driver, by giving priority to the registered settings, it is possible to record work information corresponding to the parking position based on the location information master 31. On the other hand, when there are few input errors in the work type entered by the driver, or when there are many cases where work different from the work type registered in the location information master 31 is carried out, the priority setting may be set to input priority.

[0121] [Fifth Embodiment] The fifth embodiment will be described. For configurations not specifically mentioned, those similar to the first to fourth embodiments can be applied.

[0122] In the parking processes A and B of the first embodiment, when a record R of the shipper corresponding to the parking position is registered in the location information master 31, an example of the process of recording the waiting time for that shipper was illustrated. In such a process, if a plurality of records R with the same position data but different shippers are registered in the location information master 31, it may be possible for the administrator or the driver to select any of these shippers.

[0123] Such a selection can be received, for example, at an appropriate timing after the process of step S203 in the parking processes A and B. As an example, the selection may be made by displaying a shipper selection screen on the displays 12, 42, etc.

[0124] FIG. 17 is a diagram showing an example of a shipper selection screen 80. This selection screen 80 includes a date and time box 81, a driver name box 82, a parking position box 83, a candidate box 84, an OK button 85, and a cancel button 86.

[0125] In the date and time box 81, the parking time of the vehicle that triggered the process shown in the flowchart of FIG. 3, for example, is displayed. In the driver name box 82, the name of the driver is displayed. In the parking position box 83, the address indicating the parking position specified in step S201 is displayed. In the parking position box 83, any one of the place names indicated by the location information of the plurality of records R specified from the location information master 31 may be displayed.

[0126] In the candidate box 84, the consignors indicated by the location information of the plurality of records R specified from the location information master 31 are listed. In the example of FIG. 17, two candidates, candidate 1 and candidate 2, are displayed. The display order of the consignors is not particularly limited, but in one example, the consignors with a high selection frequency may be displayed as the top candidates.

[0127] When the OK button 85 is operated in a state where any candidate is selected from such a candidate box 84, the consignor of the selected candidate is determined as the target of recording the waiting information. That is, the waiting information recorded in step S211 includes the identification information of the consignor selected on the selection screen 80. When the cancel button 86 is operated, for example, the processes of steps S215 to S222 are executed, and the parking time is recorded as a break time.

[0128] The process related to the selection of such a consignor can also be applied to the parking process C. In this case, the parking time is recorded as the working time for loading or unloading goods for the consignor selected by the selection screen 80.

[0129] In addition, the same processing as the shipper's selection can also be applied to the parking processes D and E. That is, when a plurality of records R including position data corresponding to the parking position are extracted from the location information master 31 in step S502, a screen similar to the selection screen 80 may be displayed on the displays 12, 42, etc. In this case, the location information and work type of each record R are listed in the candidate box 84 as work candidates. Further, the work information including the selected location information and work type is recorded in step S509.

[0130] [Sixth Embodiment] The sixth embodiment will be described. For configurations not particularly mentioned, those similar to the first to fifth embodiments can be applied.

[0131] FIG. 18 is a diagram showing an example of the data structure of the record R constituting the location information master 31 according to the sixth embodiment. In the present embodiment, each record R further includes time information in addition to the position data, location information, and location type. The time information is set, for example, when the location type is a shipper, and corresponds to the scheduled working time for loading or unloading.

[0132] When executing the parking processes A and B using such a location information master 31, when calculating the waiting time in step S210, the time indicated by the time information of the record R is subtracted from the parking time. Thereby, it becomes possible to calculate an accurate waiting time considering the time for loading or unloading during parking. As another example, the waiting time may be calculated in the same manner as in the first embodiment, and the time indicated by the time information of the record R may be added to the waiting information recorded in step S211. Even in this case, when performing aggregation or the like based on the waiting information, the time indicated by the time information included in the waiting information is subtracted from the waiting time included in the waiting information, so that it becomes possible to calculate a waiting time considering the time for loading or unloading.

[0133] The method for preventing the loading and unloading operation time from being included in the waiting time is not limited to the above. For example, as for the movement of the vehicle at the loading or unloading point, it is assumed that the vehicle first stops at the waiting place, then moves to the loading or unloading work place and stops again, and leaves the loading or unloading point after the work is completed. Therefore, for the first stop at the loading or unloading point, parking processes A and B are started. Then, when it is determined in step S207 that the parking state is released by detecting the speed using GPS or the like, and after the waiting information is recorded in step S211 and the parking processes A and B are completed, if the vehicle stops again within a certain time, the parking time may be recorded as the loading or unloading operation time. The above-mentioned certain time is, for example, several minutes and can be arbitrarily set by an administrator or the like. The starting point of the above-mentioned certain time is, for example, the time when it is determined in step S207 that the parking state is released, but it is not limited to this example.

[0134] As yet another example, when the vehicle stops again within the above-mentioned certain time, if the parking time is substantially the same as the time indicated by the time information of the record R including the position data corresponding to the parking position in the location information master 31, the parking time may be recorded as the loading or unloading operation time. Also, when the vehicle does not stop again within the above-mentioned certain time, or even if it stops but the parking time is not substantially the same as the time indicated by the time information of the record R, the waiting time may be corrected by subtracting the time indicated by the time information of the record R from the waiting time recorded in the previous parking processes A and B. Note that "substantially the same" as the time indicated by the time information of the record R for the parking time includes not only the case where the two are the same, but also the case where, for example, the difference between the two is within a predetermined time of about several minutes. This predetermined time can be arbitrarily set by, for example, the administrator terminal 1.

[0135] The processing of the above-described embodiment can be applied not only to the parking processes A and B but also to the parking processes D, E, and F. Also, time information may be set in the record R including location information other than the shipper, and the time indicated by the time information may be subtracted from the parking time when recording work types other than waiting.

[0136] [Embodiment 7] Embodiment 7 will be described. For configurations not particularly mentioned, those similar to the first to sixth embodiments can be applied.

[0137] The processes related to the calculation and recording of the waiting time, rest time, and other working times disclosed in the first to sixth embodiments may be executed retrospectively at an appropriate timing such as when aggregating the driver's labor information.

[0138] When executing these processes retrospectively, for example, the driving information of the vehicle (speed data for each time, position data for each time, work type input by the driver and the input time, etc.) accumulated in the management database 30 can be used. The driving information is transmitted from the digital tachograph 2 to the server 3 as described above. However, the method of recording the driving information is not limited to this example.

[0139] For example, when retrospectively executing the processes shown in the flowcharts of FIGS. 3 to 6, FIGS. 10, 11, and FIGS. 13 to 16 based on the driving information, the identification of the parking position in steps S201, S501, S601, the acquisition of the first time in steps S204, S216, S504, S511, S602, and the acquisition of the second time in steps S209, S219, S507, S514, S605 are performed based on the driving information. The parking position corresponds to the position indicated by the position data of the driving information at the parking time determined based on the speed data in the driving information, for example. The first time corresponds to the above parking time, for example. The second time corresponds to the time of release from parking determined based on the speed data in the driving information, for example.

[0140] Note that when retrospectively executing the processes shown in the above flowcharts, the processes in steps S205 to S207, S217 to S218, S401, S505, S506, S512, S513, S603, S604, etc. may be omitted.

[0141] Also, when the processes shown in the above flowcharts are executed retrospectively, by executing the processes of steps S212 to S214 or by displaying a shipper selection screen 80 as shown in FIG. 17, even when a GPS position deviation occurs or when multiple shippers are registered for a parking position, an appropriate shipper to be targeted for standby or the like can be selected. However, the processes of steps S212 to S214 and the process of displaying the selection screen 80 may be omitted.

[0142] [Eighth Embodiment] The eighth embodiment will be described. The same configurations as those of the first to seventh embodiments can be applied to the configurations not particularly mentioned.

[0143] FIG. 19 is a block diagram showing a configuration example of a labor management system according to the eighth embodiment. The labor management system according to the present embodiment includes a driver terminal 9 in addition to the elements shown in FIG. 1. The driver terminal 9 is a portable device such as a smartphone or a tablet.

[0144] The driver terminal 9 includes a controller 90 including a processor and a memory, a storage device 91, a communication device 92, a display 93, an input device 94, a speaker 95, and a GPS receiver 96. The controller 90 realizes various processes as the driver terminal 9 by the processor executing a computer program stored in the memory.

[0145] The communication device 92 can communicate wirelessly with the network N. The input device 94 includes a touch panel and buttons for operating the GUI displayed on the display 93. The GPS receiver 96 receives GPS signals from satellites and detects the position of the driver terminal 9 based on the signals.

[0146] The driver terminal 9 is capable of executing at least a part of the processes (steps) shown in the flowcharts of FIGS. 3 to 6, FIGS. 10, 11, and FIGS. 13 to 16. As an example, the processes of steps S101 to S105, S201 to S211, S215 to S221, S401 to S402, S501 to S517, and S601 to S607 may be executed by the controller 90 of the driver terminal 9. In this case, the confirmation screen 60 shown in FIG. 8, the selection screen 70 shown in FIG. 12, and the selection screen 80 shown in FIG. 17 may be displayed on the display 93. The various notifications and warnings mentioned in the above-described embodiments may also be implemented by display on the display 93 or voice output from the speaker 95.

[0147] Also, the identification of the parking position in steps S201, S501, and S601 may be performed based on the signals received by the GPS receiver 96. Further, the stopping of the vehicle that triggers the processes shown in the flowcharts of FIGS. 3, 10, 13, and 15, and the detection of the release of the parking state in the processes such as steps S206, S218, S506, S513, and S604 may be performed based on the signals received by the GPS receiver 96.

[0148] In addition to those shown in FIGS. 1 and 19, the labor management system can be configured with various elements. For example, the functions of the server 3 may be integrated into the administrator terminal 1. In this case, the management database 30 and the location information master 31 can be stored in the storage device 11 or other storage devices connected to the administrator terminal 1.

[0149] In each embodiment, a labor management system for managing the labor of truck drivers has been disclosed. However, the processes in these labor management systems can also be applied to the labor management of drivers of other types of vehicles such as railways, buses, and taxis. Further, it can also be applied to the labor management of workers other than drivers.

[0150] A computer program for realizing each process disclosed in each embodiment may be stored in a storage medium and transferred to a user, or may be transferred by the user downloading it via a network. Further, a computer that executes such a computer program may be not only the administrator terminal 1, the digital tachograph 2, the server 3, and the driver terminal 9 disclosed in each embodiment, but also other devices.

[0151] Each of the embodiments described above does not limit the scope of the invention to the configurations disclosed in these embodiments. The present invention can be implemented in various other forms. The configurations and their modifications disclosed in each embodiment are included in the invention described in the claims and the equivalent scope thereof.

Explanation of Reference Numerals

[0152] 1... Administrator terminal, 2... Digital tachograph, 3... Server, 9... Driver terminal, 10, 20, 90... Controllers, 30... Management database, 31... Location information master, 50... Notification screen, 60... Confirmation screen, 70, 80... Selection screens.

Claims

1. A labor management system including a driver terminal, an administrator terminal, and a server that can communicate with each other, A position identifying means for identifying a position where the vehicle is stopped; a first acquisition means for acquiring a first time inputted by an input device of the vehicle, the driver's terminal, or the manager terminal; A second acquisition means for acquiring a second time inputted by the input device; A shipper identification means for identifying a shipper corresponding to the location identified by the location identification means; a calculation means for calculating a waiting time of the driver of the vehicle at the position identified by the position identification means based on the first time and the second time; A recording means for recording waiting information including the shipper identified by the shipper identification means and the waiting time calculated by the calculation means; Equipped with Each of the location identification means, the first acquisition means, the second acquisition means, the shipper identification means, the calculation means and the recording means is realized by any one of the driver terminal, the manager terminal and the server, or by the manager terminal, the driver terminal and the server working together. Labor management system.

2. The recording means records the elapsed time from the first time to the second time as a rest time when the shipper cannot be identified by the shipper identification means. The labor management system according to claim 1.

3. the calculation means, when the first time is earlier than a third time that is a criterion for determining whether or not the process should be performed as a waiting time, calculates an elapsed time from the third time to the second time as the waiting time; The labor management system according to claim 1 or 2.

4. When the first time is earlier than the third time, the recording means records the elapsed time from the first time to the third time as a rest time. The labor management system according to claim 3.

5. A labor management system including a driver terminal, an administrator terminal, and a server that can communicate with each other, A position identifying means for identifying a position where the vehicle is stopped; a first acquisition means for acquiring a first time inputted by an input device of the vehicle, the driver's terminal, or the manager terminal; A second acquisition means for acquiring a second time inputted by the input device; A shipper identification means for identifying a shipper corresponding to the location identified by the location identification means; a calculation means for calculating a rest time of the driver of the vehicle based on the first time and the second time when the shipper identification means cannot identify the shipper; a recording means for recording the rest time calculated by the calculation means; Equipped with A labor management system in which each of the location identification means, the first acquisition means, the second acquisition means, the shipper identification means, the calculation means and the recording means is realized by either the driver terminal, the manager terminal, or the server, or by cooperation between the manager terminal, the driver terminal, and the server.

6. Computer, A location identification means for identifying the location where the vehicle is stopped; a first acquisition means for acquiring a first time inputted by an input device of the vehicle, the driver's terminal, or the manager's terminal; a second acquisition means for acquiring a second time inputted by the input device; A shipper identification means for identifying a shipper corresponding to the location identified by the location identification means; a calculation means for calculating a waiting time of the driver of the vehicle at the position identified by the position identification means based on the first time and the second time; and a recording means for recording waiting information including the shipper identified by the shipper identification means and the waiting time calculated by the calculation means; A computer program that functions as a

7. The recording means records the elapsed time from the first time to the second time as a rest time when the shipper cannot be identified by the shipper identification means.

7. A computer program according to claim 6.

8. the calculation means, when the first time is earlier than a third time that is a criterion for determining whether or not the process should be performed as a waiting time, calculates an elapsed time from the third time to the second time as the waiting time; A computer program according to claim 6 or 7.

9. When the first time is earlier than the third time, the recording means records the elapsed time from the first time to the third time as a rest time.

9. A computer program according to claim 8.

10. Computer, A location identification means for identifying the location where the vehicle is stopped; a first acquisition means for acquiring a first time inputted by an input device of the vehicle, the driver's terminal, or the manager's terminal; a second acquisition means for acquiring a second time inputted by the input device; A shipper identification means for identifying a shipper corresponding to the location identified by the location identification means; A calculation means for calculating a rest time of a driver of the vehicle based on the first time and the second time when the shipper identification means cannot identify a shipper; and a recording means for recording the rest time calculated by the calculation means; A computer program that functions as a

Citation Information

Patent Citations

  • Method and system for determining freight rate and fees

    JP2011108092A

  • Vehicular data collection apparatus

    JP2011128918A

  • Vehicle data collection device

    JP2014035718A

  • Labor management system and computer program

    JP2019101726A

  • Past operation record analysis program, past operation record analysis method and past operation record analysis system

    JP2020181345A