Labor management system and computer program

Abstract

Improve business management systems within transportation companies. [Solution] A labor management system according to one embodiment includes a driver terminal, a manager terminal, and a server capable of communicating with each other, and is equipped with a master that associates position data with location information, a location identification means that identifies the position of a vehicle, a task identification means that identifies a task type of a task to be performed at a location identified by the location identification means, and a recording means that records task information including location information associated in the master with position data corresponding to the position identified by the location identification means, and the task type identified by the task identification means. Each of the location identification means, the task identification means, and the recording means is realized by any one of the driver terminal, the manager terminal, and the server, or by cooperation between the manager terminal, the driver terminal, and the server.

Description

[Technical field]

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

[0002] In recent years, there has been a growing trend to improve the working environment. To improve the working environment, it is important that both managers and workers make an effort to comply with the law and various rules. For example, there are various rules for truck drivers regarding working hours, rest periods, and rest times.

[0003] In addition, in recent years, there has been a strong demand to reduce waiting times at loading and unloading points in order to rectify the long working hours of drivers. In order to reduce waiting times, it is necessary to understand the actual waiting times during daily operations and then work to make improvements. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Patent No. 6984883 Summary of the Invention [Problem 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. Another object of the present invention can be derived from this specification and the attached drawings. [Means for solving the problem]

[0006] The labor management system according to one embodiment includes a driver terminal, a manager terminal, and a server that are capable of communicating with each other, and associates position data, location information, and work types. Has multiple recordsA master, a position identification means for identifying a position of a vehicle, and the master From the plurality of records, Position data corresponding to the position identified by the position identification means If a corresponding record is found, the position data is The work type associated with As a task type of the task performed by the driver of the vehicle, A task identification means for identifying the task; The relevant record and task information including location information associated with location data corresponding to the location identified by the location identification means and a task type identified by the task identification means. , separately from the master Each of the position identification means, the task identification means, and the recording means is realized by any one of the driver terminal, the manager terminal, and the server, or by cooperation between the manager terminal, the driver terminal, and the server.

[0007] A computer program according to an embodiment includes a computer that includes a position identification unit that identifies a position of a vehicle, a position data, a location information, and a task type associated with each other. Has multiple records To the master From the plurality of records in Position data corresponding to the position identified by the position identification means If a corresponding record is found, the position data is The work type associated with As a task type of the task performed by the driver of the vehicle, A task identification means for identifying the task; and The relevant record and task information including location information associated with location data corresponding to the location identified by the location identification means and a task type identified by the task identification means. , separately from the master It functions as a means of recording. Effect of the Invention

[0008] According to the present invention, it is possible to improve the business management system in a transport company. Other advantages of the present invention can be derived from the present specification and the accompanying drawings. [Brief description of the drawings]

[0009] [Figure 1] FIG. 1 is a block diagram showing an example of the configuration of a labor management system according to a first embodiment. [Diagram 2] FIG. 2 is a diagram showing an example of a data structure of a record constituting the point information master according to the first embodiment. [Diagram 3] FIG. 3 is a flowchart showing an example of processing performed when the vehicle is stopped according to the first embodiment. [Figure 4] FIG. 4 is a flowchart showing an example of the vehicle stopping process A in FIG. [Diagram 5] FIG. 5 is a flowchart showing an example of the vehicle stopping process B in FIG. [Figure 6] FIG. 6 is a flowchart showing an example of the vehicle stopping process C in FIG. [Figure 7] FIG. 7 is a diagram showing an example of the notification screen. [Figure 8] FIG. 8 is a diagram showing an example of the confirmation screen. [Figure 9] FIG. 9 is a diagram showing an example of a data structure of a record constituting the point information master according to the second embodiment. [Figure 10] FIG. 10 is a flowchart showing an example of processing performed when the vehicle is stopped according to the second embodiment. [Figure 11] FIG. 11 is a flowchart showing an example of the vehicle stopping process D in FIG. [Figure 12] FIG. 12 is a diagram showing an example of the selection screen. [Figure 13] FIG. 13 is a flowchart showing an example of processing performed when the vehicle is stopped according to the third embodiment. [Figure 14] FIG. 14 is a flowchart showing an example of the vehicle stopping process E in FIG. [Figure 15] FIG. 15 is a flowchart showing an example of processing performed when the vehicle is stopped according to the fourth embodiment. [Figure 16] FIG. 16 is a flowchart showing an example of the vehicle stopping process F in FIG. [Figure 17] FIG. 17 is a diagram showing an example of a shipper selection screen according to the fifth embodiment. [Figure 18] FIG. 18 is a diagram illustrating an example of a data structure of a record constituting the point information master according to the sixth embodiment. [Figure 19]FIG. 19 is a block diagram showing an example of the configuration of a labor management system according to the eighth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0010] Several embodiments will now be described with reference to the drawings. In each embodiment 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 an example of the configuration of a labor management system according to the first embodiment. The labor management system includes a manager terminal 1 arranged at a business establishment, a digital tachograph 2 mounted on a vehicle, and a server 3. The digital tachograph 2 functions as a driver's terminal in this embodiment.

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

[0013] The administrator terminal 1 comprises a controller 10 including a processor and 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 this embodiment by the processor executing a computer program stored in the memory.

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

[0015] A communication device 16 capable of communicating with the network N is connected to the interface 15 by wire or wireless communication. The interface 15 may further be connected to a time clock terminal 17 for the driver to perform clock-in and clock-out processing at the business premises.

[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 external connection interface 24. The controller 20 can realize various processes disclosed in this embodiment by the processor executing a computer program stored in the memory.

[0017] 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 are communicatively connected to the interface 24 via wired or wireless communication. These elements connected to the interface 24 may be provided in a console of the vehicle, or may be part of the digital tachograph 2. The digital tachograph 2 does not necessarily have to 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. Furthermore, the input device 43 includes various buttons for inputting the type of work performed by the driver and the state of the vehicle, such as leaving the warehouse, returning to the warehouse, loading, unloading, resting, waiting, lodging, refueling, and boarding. The driving sensor 44 detects parameters related to driving, such as the vehicle speed, acceleration, engine RPM, and engine temperature. 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 located outside the business establishment or may be located within the business establishment. 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 the elements of the labor management system such as the manager 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 on the work history and future work schedule of a plurality of drivers. 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 and store information in the management database 30 by communication via the communication device 16 and the network N. The digital tachograph 2 can also execute similar processes by 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] The controller 20 of the digital tachograph 2 stores operation information including the vehicle operation start time, operation end time, the so-called legal three elements (instantaneous speed of the vehicle, traveling distance, traveling time) at each time from the operation start time to the operation end time, the work type at each time (waiting, rest, rest, loading, unloading, refueling, boarding, etc.), vehicle position data (address), etc., in the storage device 21 based on parameters such as speed detected by the travel sensor 44, input from the input device 43, and signals received by the GPS receiver 45. 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 manager terminal 1 accesses the management database 30 to obtain the operation information, and can use it for display on the display 12 or for other processing. The operation information may be transmitted directly from the digital tachograph 2 to the manager terminal 1.

[0023] In the labor management system configured as described above, the administrator terminal 1, digital tachograph 2 and server 3 communicate via network N, making it possible to grasp the driver's working status, the vehicle's driving status, etc. in real time both at the workplace and in the vehicle.

[0024] For example, the manager terminal 1 displays a list of driver information indicating the working conditions of each driver belonging to the establishment and the driving conditions of the vehicle on the display 12 based on information in the management database 30, etc. This allows the manager to very easily grasp the working conditions of each driver and the driving conditions of the vehicle, etc., and can also issue necessary instructions to drivers in remote locations.

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

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

[0027] For example, the location information of record R is identification information such as a character string or code indicating a specific 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. If the name of a shipper is recorded as location information, it does not necessarily mean that the shipper is located at the location indicated by the location data. The location data associated with the shipper in record R may indicate the delivery destination of the package for which a transportation request has been received.

[0028] The location type of record R is identification information that indicates whether the name indicated by the location information belongs to a type such as a shipper, a gas station, a convenience store, a parking area, a business establishment, or a ferry terminal.

[0029] In response to a vehicle being stopped, the labor management system according to this embodiment executes the process shown in the flowchart of Fig. 3. The process (steps) shown in the flowchart may be realized by the controller 10 of the manager terminal 1, the controller 20 of the digital tachograph, the server 3, etc. working together, or may be realized by any one of them alone.

[0030] 3 is triggered by a state in which the vehicle engine is stopped, a state in which the vehicle speed detected by the travel sensor 44 is 0 km / s for a certain period of time, or a state in which the vehicle position identified by the signal received by the GPS receiver 45 does not change for a certain period of time. In addition to these, various other methods such as the operation of a specific button can be used as a trigger for starting the process shown in the flowchart.

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

[0032] If the work type has not been input (NO in step S101), it is determined whether a predetermined time T1 has elapsed since the vehicle stopped (step S102). For example, the predetermined time T1 can be set appropriately 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 step S101. If the predetermined time T1 has elapsed (YES in step S102), it is determined whether the vehicle stop setting regarding the treatment of the vehicle stop time is a standby setting that treats the vehicle stop time as standby or a rest setting that treats the vehicle stop time as rest (step S103). The vehicle stop setting can be changed by, for example, the manager terminal 1.

[0034] When the vehicle stop setting is the standby setting (standby in step S103), vehicle stop processing A is executed. When the vehicle stop setting is the rest setting (rest in step S103), vehicle stop processing B is executed.

[0035] On the other hand, if a work type is input before the predetermined time T1 in step S102 has elapsed (YES in step S101), a process corresponding to the work type is executed. That is, if the input work type is waiting (waiting in step S104), stopping process A is executed. If the input work type is rest (rest in step S104), stopping process B is executed. If the input work type is loading or unloading (loading / unloading in step S104), stopping process C is executed. In this embodiment, these stopping processes A, B, and C are described, but if other work types are input, stopping processes corresponding to the input are also executed.

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

[0037] 4, first, the stopping position of the vehicle is identified (step S201). For example, the stopping position is the current position of the vehicle, and can be identified based on a signal received by the GPS receiver 45.

[0038] Next, the location information master 31 is searched for a shipper corresponding to the stop location identified in step S201 (step S202). In step S202, a record R including location data corresponding to the stop location identified in step S201 and having a location type of shipper is extracted from the location information master 31. At this time, the record R including the location data may be extracted not only when the stop location identified in step S201 and the location indicated by the location data match perfectly, but also when the two are considered to be substantially the same. Here, "substantially the same" may include a case where the stop location identified in step S201 is located within a predetermined radius (e.g., within several tens of meters) of the location indicated by the location data of record R.

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

[0040] When record R is extracted (YES in step S203), the first time is acquired (step S204). For example, the first time is the vehicle stop time that triggered the process shown in the flowchart of FIG. 3. In this case, when the vehicle stops, the stop time is recorded in the storage device 21, the management database DB, or the like, and the stop time is read out in step S204. As another example, the first time may be the time when the predetermined time T1 in step S102 has elapsed from the vehicle stop time. As yet another example, the first time may be the time input by the input device 13, 43, or the like. In addition, when the stop process A is started in response to input of a waiting 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 or the like as the standby start time of the driver (step S205). After the standby start time is recorded, the working status of the driver is waiting for loading or unloading until the standby end time is recorded.

[0042] After step S205, it is determined whether a predetermined time T2 (e.g., 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 step S206.

[0043] If the predetermined time T2 has elapsed before the end of the waiting (YES in step S206), a warning regarding the waiting is issued (step S208). The warning may be a warning display for the driver on the display 22, 42 of the vehicle, or a warning message or warning sound output by the speaker 23. The warning may be a warning display for the manager on the display 12 of the manager terminal 1, or a warning message or warning sound output 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 on a list screen of multiple drivers belonging to the establishment. The area may include the elapsed time from the start of the waiting. Such a warning can make the driver or the manager aware of a situation in which the elapsed time from the start of the waiting period is longer than the predetermined time T2.

[0044] For example, when the vehicle is released from a stopped state, it is determined in step S207 that the waiting has ended (YES in step S207). Here, the stopped state is released, for example, when the engine of the vehicle is started, when the vehicle speed detected by the travel sensor 44 is no longer 0 km / s, or when the position of the vehicle identified by the signal received by the GPS receiver 45 has changed. As another example, in step S207, it may be determined that the waiting has ended in response to the operation of a button such as a loading button or an unloading button of the input device 43.

[0045] After the standby is completed, the second time is acquired (step S209). The second time is, for example, the time when the vehicle is released from the stopped state, that is, the current time, and can be obtained from the system clock of the digital tachograph 2. As another example, the second time may be a time inputted by the input device 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 acquired in step S204 to the second time acquired in step S209. In this case, the waiting time corresponds to the stopping time of the vehicle. As another example, the waiting time calculated in step S210 may be a time obtained by subtracting a predetermined fixed time or an arbitrary time from the elapsed time or the stopping time.

[0047] After step S210, the waiting information is recorded in the 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 acquired in step S204, the second time acquired in step S209, and the waiting time calculated in step S210. Step S211 ends the stopping process A.

[0048] Here, if the shipper corresponding to the stopping position identified in step S201 is not registered in the location information master 31 (NO in step S203), the manager is notified that the vehicle is stopped at a position where the shipper is not registered (step S212). For example, this notification is made by a screen display on the display 12 of the manager terminal 1. Note that in step S212, a similar notification may be made to the driver using the display 42 or the like.

[0049] 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 that the vehicle stopped at a location where the shipper is not registered, and a message that the location name should be input. Furthermore, the notification screen 50 includes a date and time box 51, a driver's name box 52, a stopping location box 53, a location name box 54, a save button 55, and a cancel button 56.

[0050] The date and time box 51 displays the vehicle stop time that triggered the process shown in the flowchart of Fig. 3. The driver's name box 52 displays the name of the driver. The stop position box 53 displays the address indicating the stop position identified in step S201.

[0051] With such a notification screen 50 displayed, a correction to the location name is accepted (step S213). The manager can input the location name (shipper) into the location name box 54 by operating the input device 13, for example, based on the driver's operation schedule for the day.

[0052] The notification screen 50 may further include a candidate display button 54a. When the candidate display button 54a is operated, candidate shippers are displayed. Such candidates may be all shippers registered in the location information master 31, or may be a shipper associated with location data close to the address displayed in the stop location box 53 among these shippers. When the administrator selects one of such candidates, the selected shipper is entered in the location name box 54.

[0053] When the save button 55 is operated, it is determined whether or not the shipper 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 shipper is registered (YES in step S214), the processing of steps S204 to S211 is executed.

[0054] On the other hand, if the shipper entered in the location name box 54 when the save button 55 is operated is not registered in the location information master 31 (NO in step S214), or if the cancel button 56 on the notification screen 50 is operated, a confirmation screen requesting permission to treat the stop time as rest time will be displayed on the display 12 (step S215).

[0055] The stop position (address) in the stop position box 53 may be modifiable on the notification screen 50. Furthermore, in step S214, the location information master 31 is searched based on the modified stop position in the stop position box 53, and if there is no record R including location data corresponding to the stop position, or if such a record R exists but its location type is not a shipper, the processes in and 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 stopping time as a rest period. When the OK button 61 is operated, that is, when processing the stopping time as a rest period is permitted, the processing of steps S216 to S222 is executed. On the other hand, when the cancel button 62 is operated, that is, when processing the stopping time as a rest period is denied, the stopping process A ends. As another example, when the cancel button 62 is operated, a screen for selecting a work type (waiting, loading, unloading, refueling, boarding, etc.) (for example, a selection screen in FIG. 12 described later) is displayed, and the stopping time may be recorded in the management database 30 as the work type selected on the screen.

[0057] If a certain period of time has passed since the confirmation screen 60 was displayed without any operation on the screen, it may be processed as if the OK button 61 or the cancel button 62 had been operated. In this case, the labor management system may have a function for setting in advance whether the OK button 61 or the cancel button 62 should be operated. Such a setting function may be provided in, for example, the manager terminal 1, but is not limited to this example.

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

[0059] In step S216, the first time is acquired as in step S204. After that, the first time is recorded in the management database 30 or the like as the break start time of the driver (step S217). After the break start time is recorded, the working status of the driver is on break until the break end time is recorded.

[0060] After step S217, it is determined whether the rest period has ended (step S218). For example, if the vehicle is released from its stopped state, it is determined in step S218 that the rest period has ended (YES in step S218), and the second time is acquired (step S219) in the same manner as in step S209.

[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 stopping time of the vehicle. As another example, the rest time calculated in step S220 may be the time obtained by subtracting a predetermined fixed time or an arbitrary time from the elapsed time or the stopping time.

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

[0063] After step S221, the driver and manager are notified that the stopping time has been treated as a rest time, for example by displaying on the display 12, 42 (step S222). As described above, stopping process A is executed when the stopping time setting is standby or when standby is input as the work type. The notification in step S222 allows the driver and manager to recognize that the stopping time has been treated as a rest time regardless of these cases. Stopping process A ends with step S222.

[0064] The third time may be further taken into consideration in the calculation of the waiting time in step S210. For example, the third time is a time that is a criterion for determining whether or not to process the waiting time, and is of a nature that excludes waiting before that time from the responsibility of the shipper. As an example, the third time may be the opening time of the operator of the loading or unloading point, the reservation time for loading or unloading by the carrier, the designated time for loading or unloading by the shipper, or the acceptance time when the waiting is accepted at the loading or unloading point.

[0065] When the third time is taken into consideration 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 standby time.

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

[0067] (3) When the first time and the second time are both earlier than the third time In this case, the waiting time is calculated as 0. 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, a time period such as a lunch break at the loading or unloading point may be taken into consideration. That is, if the time from the first time to the second time overlaps with such a time period, the overlapping portion may be deducted from the waiting time. Furthermore, the overlapping portion may be recorded in the management database 30 as the driver's rest time.

[0069] In the vehicle stop process B shown in the flowchart of Fig. 5, steps S201 to S221 are the same as in the vehicle stop process A. As described above, the vehicle stop process B is executed when the vehicle stop setting is a rest period or when the driver inputs a rest period as the task type. Therefore, in the example of Fig. 5, the notification when the vehicle stop time is recorded as a rest period (step S222 in the vehicle stop process A) is omitted.

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

[0071] In the stopping process C shown in the flowchart of Fig. 6, steps S201 to S204, S207, S209, and S212 to S222 are the same as in the stopping process A. In the stopping process C, after the first time is acquired in step S204, the first time is recorded in the management database 30 or the like as the start time of the driver's loading or unloading (step S401). After the start time of loading or unloading is recorded, the working status of the driver is loading or unloading until the end time is recorded.

[0072] In the vehicle stop processing 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 operation time of loading or unloading (for example, the elapsed time from the first time to the second time).

[0073] According to the above embodiment, the business management system of the transport company can be improved. Specifically, when the vehicle stops, the vehicle's stopping position is acquired based on the GPS or the like, the shipper corresponding to the stopping position is identified, and waiting information for the shipper is recorded. This makes it possible to obtain appropriate waiting information for the shipper even if the driver or manager does not make any special input.

[0074] In addition, if the shipper corresponding to the stop position is not registered in the location information master 31, the stop time is recorded as a rest time. This makes it possible to accurately manage the working status of the driver.

[0075] Furthermore, according to stop processing A and C, even if the driver inputs "waiting," "loading," or "unloading" as the type of work during a stop (waiting or loading / unloading in step S104), the stop time is recorded as rest time if the shipper is not registered in the location information master 31. Furthermore, according to stop processing B, even if the driver inputs "rest" as the type of work during a stop (rest in step S104), the stop time is recorded as waiting time if the shipper is registered in the location information master 31. These processes make it possible to correct the driver's input and record work information appropriate to the situation.

[0076] In the stop processing A, B, and C, even if the shipper corresponding to the stop position is not registered in the location information master 31, the shipper can be corrected by the processing of steps S212 to S214. This makes it possible to deal with a situation in which the stop position and the location data of the location information master 31 are inconsistent due to a GPS position shift or erroneous registration of the location data of the location information master 31. In addition to the above, various other advantageous effects can be obtained from this embodiment.

[0077] The configuration disclosed in this embodiment may be modified in various ways. For example, in this embodiment, it is assumed that the waiting or resting time is set in advance. If the stopping time is not set, the stopping process A or the stopping process B may be set as a default. In addition, the labor management system may not have a stopping time setting function. In this case, the stopping process A or the stopping process B may be executed without going through the process of step S103. As a more specific example, in the stopping process when the stopping time setting function is not included, the processes of steps S201 to S203 are executed first. If it is determined in step S203 that the shipper is registered (YES in step S203), at least one of the manager and the driver is notified that the stopping time will be treated as waiting time, and then the processes of steps S204 to S211 and S301 are executed. If it is determined in step S203 that the shipper is not registered (NO in step S203), at least one of the manager and the driver is notified that the stop time will be treated as a rest time, and the processes in steps S216 to S222 are then executed. Note that, like the stop processing A and B, the processes in steps S212 to S214 may be executed.

[0078] For example, the notification to the manager that the stop time will be treated as waiting time or rest time may be made by displaying a message on the display 12 of the manager terminal 1, or by changing the working status of the driver to "waiting" or "rest" on a driver information list screen showing the working status of each driver and the driving status of the vehicle displayed on the display 12. In addition, the notification to the driver that the stop time will be treated as waiting time or rest time may be made by displaying a message on the display 22 of the digital tachograph 2 and the display 42 of the vehicle, or by audio output from the speaker 23. The notification method to the manager or driver exemplified here can also be applied to other notifications disclosed in this specification.

[0079] In the stop processing A, B, C, the processing of steps S212 to S215 may be omitted. That is, in the stop processing A, B, C, if the shipper corresponding to the stop position is not registered in the location information master 31 (NO in step S203), the stop time may be recorded as a rest time without displaying the notification screen 50 or the like. It is possible that the location information master 31 does not have a record R including location data corresponding to the stop position, or that a record R in which a shipper is registered as location information but the location data is not registered exists. In step S203, it is also determined that there is no registration in such a case (NO in step S203). And, if steps S212 to S215 are omitted, if it is determined that there is no registration in step S203, the stop time will be recorded as a rest time without displaying the notification screen 50 or the like.

[0080] The processes shown in the flowcharts of Figures 3 to 6 do not necessarily have 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 rest time in steps S220 and S221 can be executed at an appropriate timing such as when the driver's work information is compiled based on the information such as the first time, the second time, and the third time stored in the management database 30.

[0081] As described above, the entities that execute the processes (steps) shown in the flowcharts of Figures 3 to 6 are not particularly limited, but 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] Furthermore, 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 each step do not need to be stored in a single memory, but may be configured by modules stored in a distributed manner in memories provided in multiple computers. In this case, each module can be executed by a processor of each of the multiple computers.

[0083] For example, in this embodiment, the process of step S201 and the like constitutes a position identification means for identifying the position where the vehicle is stopped. The process of steps S202, S203, S214 and the like constitutes a shipper identification means for identifying the shipper. The process of steps S210, S220 and the like constitutes a calculation means for calculating the waiting time and the rest time. The process of steps S211, S221, S402 and the like constitutes a recording means for recording the waiting information, the rest information, the loading / unloading information and the like. In one aspect of this embodiment, this recording means records the waiting time calculated by the calculation means (e.g., the elapsed time from the first time to the second time) when the shipper can be identified by the shipper identification means, and records at least a part of the elapsed time from the first time to the second time as the rest time when the shipper can be identified by the shipper identification means. The process of step S212 and the like constitutes a notification means for notifying the manager or the driver when the shipper cannot be identified. The processes of steps S204, S209, S216, S219, etc. constitute an acquisition means for acquiring the first time and the second time. In this specification, the term "acquire" may include various operations for acquiring information, such as reading information from some storage means, receiving information, and calculating and acquiring information. The processes of step S215, etc. constitute a confirmation means for requesting permission or denial for processing the stop time (the elapsed time from the first time to the second time) as a rest time. In addition to these, various means constituting a labor management system can be identified from this embodiment and each embodiment described later.

[0084] [Second embodiment] A second embodiment will now be described. Configurations that are not specifically mentioned can be the same as those in the first embodiment.

[0085] 9 is a diagram showing an example of the data structure of record R constituting the location information master 31 according to the second embodiment. In this 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, it is possible to set, for example, work such as waiting, resting, loading, unloading, refueling, and boarding.

[0086] The labor management system according to this embodiment executes the processing shown in the flowchart of Fig. 10 in response to a vehicle being stopped. The flowchart of Fig. 10 includes the processing of steps S101, S102, and S104, like the flowchart of Fig. 3, but does not include the processing of step S103. If a 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), a vehicle stopping processing D is executed.

[0087] 11 is a flowchart showing an example of the vehicle stop processing D. The processing (steps) shown in the flowchart may be realized by the controller 10 of the manager terminal 1, the controller 20 of the digital tachograph, the server 3, etc. working together, or may be realized by any one of them alone.

[0088] In the vehicle stop process D, first, the vehicle stop position is identified as in step S201 (step S501). Next, a record R corresponding to the stop position identified in step S501 is searched for in the location information master 31 (step S502). Furthermore, it is determined whether the stop position is registered in the location information master 31, that is, whether a record R including location data corresponding to the stop position is extracted (step S503).

[0089] If record R is extracted (YES in step S503), the first time (stop time) is acquired (step S504) as in step S204. Furthermore, 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 record R (step S505).

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

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

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

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

[0094] 12 is a diagram showing an example of a work type selection screen 70. For example, the selection screen 70 includes a message prompting the user to select a work type, a plurality of work type buttons 71 indicating the work types, and a cancel button 72. For example, when the cancel button 72 is operated, the vehicle stopping process D ends.

[0095] 12, the multiple work type buttons 71 are exemplified by a standby button 71a for selecting standby as the work type, a rest button 71b for selecting rest as the work type, a loading button 71c for selecting loading as the work type, an unloading button 71d for selecting unloading as the work type, a refueling button 71e for selecting refueling as the work type, a boarding button 71f for selecting boarding a ferry as the work type, and a PA button 71g for selecting resting at a parking area. The driver or manager can select a work type by operating these buttons.

[0096] When any of the work type buttons 71 is operated, the first time is acquired (step S511) as in step S504. After that, the first time is recorded in the 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 been completed (step S513), as in step S506, and the work time required for the work is calculated (step S515), as in step S508. After the work time is calculated, the work information is recorded in the management database 30 or the like (step S516). For example, this work information includes the driver's identification information, the work type selected in step S510, the first time acquired in step S511, the second time acquired in step S514, and the work time calculated in step S515.

[0098] After step S509 or step S516, the driver and the manager are notified, for example, by display on the display 12, 42 (step S517). When step S517 is performed after step S509, the notification is made by a screen including a message or the like to the effect that the stopping time has been processed as the work type identified based on the point information master 31. When step S517 is performed after step S516, the notification is made by a screen including a message or the like to the effect that the stopping time has been processed as the work type selected in step S510. Step S517 ends the stopping process D.

[0099] A notification similar to that in step S517 may be executed before step S509. The notification may include a message indicating that the stop time is processed as a work type identified based on the point information master 31. For example, the notification may be executed between steps S503 and S504, between steps S504 and S505, or between steps S505 and S506.

[0100] When the task type of the record R corresponding to the stopping position in step S502 is boarding a ferry, or when boarding a ferry is selected as the task type by operating the boarding button 71f in step S510, the stopping time may be recorded as any one of a break, a divided rest period, and a rest period depending on the length of the stopping time. Specifically, when the elapsed time from the first time to the second time is less than a first reference time (e.g., 4 hours), the stopping time may be recorded as a break time, when the elapsed time is equal to or greater than the first reference time and less than a second reference time (e.g., 9 hours), the stopping time may be recorded as a divided rest period, and when the elapsed time is equal to or greater than the second reference time, the stopping time may be recorded as a rest period. When the location type of the record R corresponding to the stopping position in step S502 is a parking area, or when resting at a parking area is selected as the task type by operating the PA button 71g in step S510, the stopping time may be recorded as a break time, a divided rest period, or a rest period based on the first reference time and the second reference time, similar to when boarding a ferry.

[0101] Note that the selection or modification of the work type may be performed afterwards by the manager or the driver when a work type corresponding to the stopping position is not registered in the point information master 31. In this case, for example, work information with an undetermined work type is recorded in step S516, and then the manager or the driver may call up a screen such as selection screen 70 for selecting or modifying the work type in the work information, and select or modify the work type through that screen.

[0102] In the above embodiment, even if the driver does not input the task type when the vehicle is stopped, the stop time is recorded as work of the task type set according to the stopping position. This makes it possible to record the working status even if the driver forgets to input the task type.

[0103] Moreover, in the case where the stop position is not registered in the point information master 31, the selection of the work type is accepted in step S510. This enables more accurate recording of the work status.

[0104] As in the first embodiment, the computer programs for causing computers such as the administrator terminal 1, the digital tachograph 2, and the server 3 to execute the processes related to each step do not need to be stored in a single memory, but may be configured by modules stored in a distributed manner in memories provided in multiple computers. In this case, each module can be executed by a processor of each of the multiple computers.

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

[0106] [Third embodiment] The third embodiment will be described. Configurations that are not specifically mentioned can be the same as those in the first and second embodiments.

[0107] The labor management system according to this embodiment executes the processing shown in the flowchart of Fig. 13 in response to a vehicle being stopped. The flowchart of Fig. 13 includes the processing of steps S101 and S102, like the flowchart of Fig. 3, but does not include the processing of steps S103 and S104. If a 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), a stopping process D similar to that of the second embodiment is executed. On the other hand, if a work type is input by operating the input device 43 or the like (YES in step S101), a stopping process E is executed.

[0108] 14 is a flowchart showing an example of a vehicle stop process E. The process (steps) shown in the flowchart may be realized by the controller 10 of the manager terminal 1, the controller 20 of the digital tachograph, the server 3, etc. working together, or may be realized by any one of them alone.

[0109] Vehicle stopping process E shown in Fig. 14 includes the same processes as steps S501 to S509 and S511 to S517 as vehicle stopping process D shown in Fig. 11, but does not include the process of step S510. In other words, vehicle stopping process E is executed when an operation type is input by the driver, and therefore if an operation type corresponding to the stopping position is not registered in the point information master 31 (NO in step S503), the processes of steps S511 to S516 are executed without accepting selection of an operation type on the selection screen 70 or the like. Even with the configuration of this embodiment, it is possible to obtain the same effects as those of the second embodiment.

[0110] [Fourth embodiment] The fourth embodiment will be described. Configurations that are not specifically mentioned can be the same as those in the first to third embodiments.

[0111] In this embodiment, it is assumed that a priority order is set as to whether the vehicle stop time is to be recorded as a work type registered in the location information master 31 or as a work type input by operating the input device 43 or the like. Hereinafter, a setting that gives priority to a work type registered in the location information master 31 is referred to as "registration priority," and a setting that gives priority to a work type input by operating the input device 43 or the like is referred to as "input priority." Such priority settings can be switched by, for example, the manager terminal 1. The priority settings may be set collectively for all drivers belonging to the establishment, 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 a vehicle being stopped. The flowchart of Fig. 15 includes the processing of steps S101 and S102, like the flowchart of Fig. 3, but does not include the processing of steps S103 and S104. If a 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), a vehicle stopping processing D similar to that of the second embodiment is executed.

[0113] 15, when a work type is input by operating the input device 43 or the like (YES in step S101), the driver's priority setting is determined (step S105). When the priority setting is registration priority (registration priority in step S105), a stopping process E similar to that in the third embodiment is executed. On the other hand, when the priority setting is input priority (input priority in step S105), a stopping process F is executed.

[0114] 16 is a flowchart showing an example of the vehicle stop processing F. The processing (steps) shown in the flowchart may be realized by the controller 10 of the manager terminal 1, the controller 20 of the digital tachograph, the server 3, etc. working together, or may be realized by any one of them alone.

[0115] In the stopping process F, first, the stopping position of the vehicle is identified as in step S501 (step S601). Then, as in step S504, the first time (stopping time) is acquired (step S602). Furthermore, 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, it is determined whether the work has been completed (step S604) in the same manner as in step S506. If it is determined that the work has been completed (YES in step S604), the second time is acquired (step S605) in the same manner as in step S507. Furthermore, the work time required for the work is calculated (step S606) in the same manner as in step S508.

[0117] After the calculation of the task time, the task information is recorded in the management database 30 or the like (step S607). For example, this task information includes the driver's identification information, the task 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 the task time calculated in step S606. Step S607 ends the vehicle stopping process F.

[0118] Thus, in this embodiment, when the priority setting is registration priority, stopping process E shown in the flowchart of Fig. 14 is executed in response to the input of a work type by the driver. In stopping process E, if a work type corresponding to the stopping position is registered in point information master 31, the stopping time is recorded as work related to that work type, and if not registered, the stopping time is recorded as work related to the work type input by the driver. In other words, registration in point information master 31 is given priority over input by the driver.

[0119] On the other hand, when the priority setting is input priority, the stop time is recorded as work related to the work type input by the driver, regardless of registration in the point information master 31. In other words, input by the driver is given priority over registration in the point information master 31.

[0120] By adopting such a priority setting, it is possible to significantly improve the accuracy of driver labor management. For example, when the driver makes many input errors in the work type, the priority setting can be set to registration priority, so that work information corresponding to the stopping position can be recorded based on the location information master 31. On the other hand, when the driver makes few input errors in the work type or when the driver often performs work different from the work type registered in the location information master 31, the priority setting can be set to input priority.

[0121] [Fifth embodiment] The fifth embodiment will be described. Configurations that are not specifically mentioned can be the same as those of the first to fourth embodiments.

[0122] In the first embodiment, the stopping processes A and B are exemplified by a process of recording the waiting time for a shipper when a record R of the shipper corresponding to the stopping position is registered in the location information master 31. In such a process, if multiple records R having the same location data but different shippers are registered in the location information master 31, the manager or the driver may be able to select one of these shippers.

[0123] Such a selection can be accepted at an appropriate timing, for example, after the processing of step S203 in the stopping processing A and B. As one example, the selection may be made by displaying a selection screen for the shipper on the display 12, 42, etc.

[0124] 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 stop location box 83, a candidate box 84, an OK button 85, and a cancel button 86.

[0125] The date and time box 81 displays the vehicle stop time that triggered the process shown in the flowchart of Fig. 3, for example. The driver name box 82 displays the name of the driver. The stop location box 83 displays the address indicating the stop location identified in step S201. The stop location box 83 may display any of the location names indicated by the location information of the multiple records R identified from the location information master 31.

[0126] The candidate box 84 displays a list of shippers indicated by the location information of each of the multiple records R identified from the location information master 31. In the example of Fig. 17, two candidates 1 and 2 are displayed. The order in which the shippers are displayed is not particularly limited, but in one example, shippers with a high selection frequency may be displayed as top candidates.

[0127] When the OK button 85 is operated with any candidate selected from such candidate box 84, the selected candidate shipper is determined as the target for recording waiting information. That is, the waiting information recorded in step S211 includes the identification information of the shipper selected on the selection screen 80. When the cancel button 86 is operated, for example, the processing of steps S215 to S222 is executed, and the stop time is recorded as rest time.

[0128] Such processing related to the selection of a shipper can also be applied to the stopping processing C. In this case, the stopping time is recorded as the work time for loading or unloading the cargo for the shipper selected on the selection screen 80.

[0129] Furthermore, processing similar to that for the shipper's selection can also be applied to the stop processing D and E. That is, when multiple records R including location data corresponding to the stop locations are extracted from the location information master 31 in step S502, a screen similar to the selection screen 80 may be displayed on the display 12, 42, etc. In this case, the location information and work type of each record R are displayed as a list in the candidate box 84 as work candidates. Furthermore, work information including the selected location information and work type is recorded in step S509.

[0130] [Sixth embodiment] The sixth embodiment will be described. Configurations that are not specifically mentioned can be the same as those of the first to fifth embodiments.

[0131] 18 is a diagram showing an example of the data structure of record R constituting the location information master 31 according to the sixth embodiment. In this 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 work time for loading or unloading.

[0132] When the stop processing A and B are performed using such a location information master 31, the time indicated by the time information of record R is subtracted from the stop time when calculating the waiting time in step S210. This makes it possible to calculate an accurate waiting time taking into account the time for loading and unloading carried out during the stop. 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 record R may be added to the waiting information recorded in step S211. Even in this case, when performing a calculation 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, making it possible to calculate a waiting time taking into account the time for loading and unloading.

[0133] The method for preventing the loading or unloading work time from being included in the waiting time is not limited to the above. For example, the movement of the vehicle at the loading or unloading point is assumed to be a flow in which the vehicle first stops at a waiting place, then moves to a loading or unloading work place and stops again, and leaves the loading or unloading point when the work is completed. Therefore, when the vehicle stops again within a certain time after the stopping process A or B is started for the first stop at the loading or unloading point, and then it is determined that the stopped state has been released in step S207 by detecting the speed using GPS, etc., and the waiting information is recorded in step S211 and the stopping process A or B is completed, the stopping time may be recorded as the loading or unloading work time. The certain time is, for example, several minutes and can be arbitrarily set by the manager, etc. The start time of the certain time is, for example, the time when it is determined that the stopped state has been released in step S207, but is not limited to this example.

[0134] As another example, if the vehicle stops again within the above-mentioned certain time, and the stopping time is substantially the same as the time indicated by the time information of record R including the position data corresponding to the stopping position in the location information master 31, the stopping time may be recorded as the loading or unloading work time. If the vehicle does not stop again within the above-mentioned certain time, or if the vehicle stops but the stopping time is not substantially the same as the time indicated by the time information of record R, the waiting time may be corrected by subtracting the time indicated by the time information of record R from the waiting time recorded in the immediately preceding stopping process A, B. Note that the stopping time being "substantially the same" as the time indicated by the time information of record R includes not only the case where the two are the same, but also the case where the difference between the two is within a predetermined time, such as a few minutes. This predetermined time can be arbitrarily set by, for example, the administrator terminal 1.

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

[0136] [Seventh embodiment] The seventh embodiment will be described. Configurations that are not specifically mentioned can be the same as those of the first to sixth embodiments.

[0137] The processes relating to the calculation and recording of the waiting time, rest time, and other work time disclosed in the first to sixth embodiments may be executed after the fact at an appropriate timing such as when the work information of the driver is compiled.

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

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

[0140] When the processes shown in the above flowcharts are executed afterwards, the processes in steps S205 to S207, S217 to S218, S401, S505, S506, S512, S513, S603, S604, etc. may be omitted.

[0141] Furthermore, even when the processing shown in each of the above flowcharts is executed after the fact, by executing the processing of steps S212 to S214 and displaying the consignor selection screen 80 as shown in Fig. 17, it is possible to select an appropriate consignor to be the target of waiting, etc., even if a GPS position shift occurs or multiple consignors are registered for the stopping position. However, the processing of steps S212 to S214 and the processing of displaying the selection screen 80 may be omitted.

[0142] [Eighth embodiment] The eighth embodiment will be described. Configurations that are not specifically mentioned can be the same as those of the first to seventh embodiments.

[0143] Fig. 19 is a block diagram showing an example of the configuration of a labor management system according to an eighth embodiment. In addition to the elements shown in Fig. 1, the labor management system according to this embodiment includes a driver terminal 9 separate from the digital tachograph 2. The driver terminal 9 is a portable device such as a smartphone or 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 is capable of wireless communication 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 a GPS signal from a satellite and detects the position of the driver terminal 9 based on the signal.

[0146] The driver's terminal 9 can execute at least a part of the processes (steps) shown in the flowcharts of Figures 3 to 6, 10, 11, and 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's terminal 9. In this case, the confirmation screen 60 shown in Figure 8, the selection screen 70 shown in Figure 12, and the selection screen 80 shown in Figure 17 may be displayed on the display 93. The various notifications and warnings mentioned in the above embodiments may also be implemented by displaying on the display 93 or outputting audio from the speaker 95.

[0147] The identification of the vehicle stop position in steps S201, S501, and S601 may be performed based on a signal received by the GPS receiver 96. Furthermore, the detection of the vehicle stopping, which is a trigger for the processes shown in the flowcharts of Figures 3, 10, 13, and 15, and the release of the stopped state in the processes of steps S206, S218, S506, S513, S604, etc. may be performed based on a signal received by the GPS receiver 96.

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

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

[0150] The computer program for implementing each process disclosed in each embodiment may be stored in a storage medium and transferred to the user, or may be transferred by the user downloading it via a network. Furthermore, the 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] The above-described embodiments do not limit the scope of the invention to the configurations disclosed in these embodiments. The present invention can be embodied in various other forms. The configurations disclosed in the embodiments and their modifications are included in the scope of the invention described in the claims and their equivalents. [Explanation of symbols]

[0152] 1...administrator terminal, 2...digital tachograph, 3...server, 9...driver terminal, 10, 20, 90...controller, 30...management database, 31...location information master, 50...notification screen, 60...confirmation screen, 70, 80...selection screen.

Claims

1. A labor management system including a driver terminal, an administrator terminal, and a server that can communicate with each other, A master having a plurality of records associating location data, point information, and work types; A location determination means for determining a location of a vehicle; a task identification means for searching the plurality of records in the master for a record including position data corresponding to the position identified by the position identification means, and if a corresponding record is found, for identifying a task type associated with the position data in the record as a task type of a task to be performed by a driver of the vehicle; a recording means for recording, separately from the master, task information including location information associated with location data corresponding to the location identified by the location identifying means in the corresponding record and a task type identified by the task identifying means; Equipped with Each of the position identification means, the work identification 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. When the plurality of records does not contain a record including location data corresponding to the location identified by the location identification means, the recording means records work information including a work type selected by a driver or manager of the vehicle. The labor management system according to claim 1.

3. A first acquisition means for acquiring a first time when the vehicle is stopped; A second acquisition means for acquiring a second time when the stopped state of the vehicle is released; a calculation means for calculating an operation time of a driver of the vehicle at a position identified by the position identification means based on the first time and the second time; Further equipped with The recording means records the work information further including the calculated work time, Each of the first acquisition means, the second acquisition means, and the calculation means is realized by any one of the manager terminal, the driver terminal, and the server, or by the manager terminal, the driver terminal, and the server working together. The labor management system according to claim 1 or 2.

4. Computer, A location determination means for determining the location of the vehicle; a task identification means for searching for a record including position data corresponding to the position identified by the position identification means from a plurality of records in a master having the plurality of records associated with position data, point information, and task types, and, if a corresponding record is found, identifying the task type associated with the position data in the record as the task type of the task to be performed by the driver of the vehicle; and a recording means for recording task information including location information associated with location data corresponding to the location identified by the location identifying means in the corresponding record, and a task type identified by the task identifying means, separately from the master; A computer program that functions as a

5. When the plurality of records does not contain a record including location data corresponding to the location identified by the location identification means, the recording means records work information including a work type selected by a driver or manager of the vehicle.

5. A computer program according to claim 4.

6. The computer, a first acquisition means for acquiring a first time when the vehicle is stopped; a second acquisition means for acquiring a second time when the stopped state of the vehicle is released; and a calculation means for calculating an operation 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; It also functions as The recording means records the work information further including the calculated work time.

6. A computer program according to claim 4 or 5.

Images