Labor management system and computer program
The labor management system accurately manages truck driver working hours and rest periods, ensuring compliance with regulations by using a database to track labor history and real-time monitoring, addressing challenges in remote areas and optimizing schedules.
Patent Information
- Application Number
- JP2024085276
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2024-05-27
- Publication Date
- 2024-11-19
- Estimated Expiration
- 2037-12-01
AI Technical Summary
Existing labor management systems struggle to accurately manage the working hours and rest periods of truck drivers, especially in remote areas where drivers do not return to the office, leading to challenges in calculating detention time, conducting roll calls, and reducing waiting times at loading and unloading points.
A labor management system and computer program that includes a database to store driver labor history, calculates restraint time, and determines if detention time exceeds limits, with features for roll call management and waiting time tracking, using devices like digital tachographs and administrator terminals to monitor and manage driver labor in real-time.
Enables accurate management of driver labor, ensuring compliance with labor regulations, reducing detention time, and optimizing work schedules to prevent exceeding work hour limits, while facilitating efficient roll call processes and reducing waiting times.
Smart Images

Figure 0007586562000001 
Figure 0007586562000002 
Figure 0007586562000003
Abstract
Description
[Technical field]
[0001] The present invention relates to a work management system and a computer program for managing the work of drivers. [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 and rest periods after work. In addition, drivers are required to take roll calls each working day.
[0003] Calculating working hours and rest periods is complicated, and accurately managing daily roll calls is time-consuming. In addition, truck drivers may drive overnight, meaning that they do not stop by the workplace when they leave work or when they return to work the next day. Therefore, labor management for drivers who are located far from the workplace requires further ingenuity.
[0004] In addition, in order to rectify the long working hours of drivers, there is a demand to reduce waiting times at loading and unloading points. 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]
[0005] [Patent Document 1] JP 2015-127960 A Summary of the Invention [Problem to be solved by the invention]
[0006] 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 accurately manage the labor of drivers, etc. Another object of the present invention can be derived from this specification and the accompanying drawings. [Means for solving the problem]
[0007] The labor management system according to one embodiment includes a database that stores a work history including a driver's daily arrival time and departure time, and a working time record that is a total of the working hours of the driver in the current month that are identified from the work history stored in the database. of The number of days the driver attended work in the current month The first average restraint time divided by , The value obtained by subtracting the actual on-duty hours of the driver from the upper limit of the on-duty hours of the driver for the current month is The number of days the driver is scheduled to work in the current month If it is greater than the second average working hours divided by the value obtained by subtracting the number of days the driver actually worked in the month from The driver of the current month total The time constraint The driver's working hours for the current month The upper limit can be exceeded and The apparatus includes a determination means for making a determination, and an output means for outputting a result of the determination by the determination means.
[0008] The computer program according to one embodiment controls the computer to determine whether a driver is driving a vehicle that is determined from a work history including a driver's daily arrival time and departure time stored in a database. Before The actual working hours of the above drivers for the current month of The number of days the driver attended work in the current month The first average on-duty time divided by the value obtained by subtracting the actual on-duty time of the driver from the upper limit of the on-duty time of the driver for that month The number of days the driver is scheduled to work in the current month If it is greater than the second average working hours divided by the value obtained by subtracting the number of days the driver actually worked in the month from The driver of the current month total The time constraint The driver's working hours for the current month The upper limit can be exceeded and The device functions as a determining means for making a determination and an output means for outputting a result of the determination by the determining means. Effect of the Invention
[0009] According to the present invention, it is possible to accurately manage the work of the driver. Other advantages of the present invention can be derived from the present specification and the accompanying drawings. [Brief description of the drawings]
[0010] [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 the configuration of the driver information list. [Diagram 3] FIG. 3 is a diagram showing an example of the configuration of the driver information list after switching. [Figure 4] FIG. 4 is a diagram showing an example of the configuration of a holiday setting screen. [Diagram 5] FIG. 5 is a diagram showing an example of the configuration of the detailed driver information. [Figure 6] FIG. 6 is a flowchart showing an example of the holiday acquisition warning process. [Figure 7] FIG. 7 is a diagram illustrating an example of the configuration of the roll call information. [Figure 8] FIG. 8 is a flowchart of a roll call process carried out in person. [Figure 9] FIG. 9 is a flowchart showing an example of a task assignment recording process. [Figure 10] FIG. 10 is a flowchart showing an example of the operation process. [Figure 11] FIG. 11 is a diagram showing an example of the accommodation confirmation screen. [Figure 12] FIG. 12 is a diagram showing an example of the roll call schedule confirmation screen. [Figure 13] FIG. 13 is a diagram showing an example of the schedule change screen. [Figure 14] FIG. 14 is a diagram showing an example of the roll call schedule notification screen. [Figure 15] FIG. 15 is a flow chart showing an example of a roll call process performed remotely. [Figure 16] FIG. 16 is a diagram showing an example of a completion waiting screen in the intermediate call. [Figure 17] FIG. 17 is a diagram showing an example of a completion screen in the intermediate roll call. [Figure 18] FIG. 18 is a block diagram showing an example of the configuration of a labor management system according to the second embodiment. [Figure 19]FIG. 19 is a block diagram showing an example of the configuration of a labor management system according to the third embodiment. [Figure 20] FIG. 20 is a flowchart showing an example of the roll call necessity determination process in the fourth embodiment. [Figure 21] FIG. 21 is a diagram showing an example of an intermediate roll call image. [Figure 22] FIG. 22 is a flowchart showing an example of the standby process in the fifth embodiment. [Diagram 23] FIG. 23 is a diagram illustrating an example of a data structure of the waiting information stored in the waiting process. [Figure 24] FIG. 24 is a flowchart showing an example of the returning process in the sixth embodiment. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0011] 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.
[0012] In Japan, the Minister of Labor has established the "Standards for Improvement of Working Hours of Motor Vehicle Drivers (Improvement Standards Notice)" to improve the working conditions of truck drivers. The Improvement Standards Notice stipulates standards for working hours, rest periods, holidays, driving hours, continuous driving hours, overtime work, and holiday work. In addition, the Improvement Standards Notice stipulates special provisions for splitting rest periods, two-person crews, alternate-day work, and ferry rides.
[0013] As an example, the outline of on-duty hours, rest periods, holidays, and continuous driving hours in the Improvement Standards Notification is shown below. [Time commitment] The working hours are the time from the start of work to the finish of work, and refer to the total of working hours and break times. The working hours per month must be within 293 hours in principle. The working hours per day are within 13 hours in principle, with a maximum of 16 hours. The number of times that the working hours exceed 15 hours is limited to two times per week. [Rest period] A rest period is the time between work shifts, during which a worker has complete freedom to live his / her daily life, including sleep time. A daily rest period must be at least eight consecutive hours. Drivers must endeavor to ensure that the rest period in the driver's location is longer than the rest period in other locations. [holiday] A day off is the rest period plus 24 hours. It must not be less than 30 hours under any circumstances. Basically, a day off is at least 32 hours, calculated by adding 24 hours to an 8-hour rest period. [Continuous operation time] Continuous driving time must be within 4 hours. In order to be recognized as a break from driving, a break of at least 10 minutes consecutively and at least 30 minutes in total is required.
[0014] In addition, the manager is required to conduct a roll call on the driver before and after driving. During this roll call, the driver must undergo an alcohol check, etc. In this disclosure, a roll call conducted before driving is called a pre-drivage roll call, and a roll call conducted after driving is called a post-drivage roll call.
[0015] In addition to regular driving, where the driver returns to the office during one working day, drivers may also work overnight, where the driver makes deliveries to distant locations over multiple working days and does not return to the office during that time. In overnight driving, there may be working days when the driver is unable to clock out from the office and working days when the driver is unable to clock in from the office, making it difficult to accurately manage the driver's working conditions.
[0016] In overnight trips of 2 nights or 3 days or more, there will be days when the driver does not stop by the business when leaving or returning to the depot. On these days, an intermediate roll call must be conducted between the pre-drive roll call and the post-drive roll call.
[0017] In each embodiment, it is assumed that the labor standards that drivers and employers must observe are the conditions set forth in the Improvement Standards Notification. However, the labor standards may be standards set forth by other laws and regulations in Japan or other countries, or original standards set forth by employers, etc. In addition, when the Improvement Standards Notification is revised, it goes without saying that the revised conditions may be adopted as the labor standards.
[0018] [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.
[0019] For example, a desktop computer can be used as the administrator terminal 1. The administrator terminal 1 may also be a portable device that can be carried by the administrator, such as a notebook computer, a tablet terminal, or a smartphone.
[0020] The administrator terminal 1 includes a controller 10 including a processor and a memory, a storage device 11, and an interface 12 for external connection. The controller 10 realizes various processes disclosed in the present embodiment by the processor executing a computer program stored in the memory. The interface 12 is communicatively connected to a communication device 13 capable of communicating with a network N, a display 14, an input device 15, a speaker 16, and a breathalyzer 17 via wired or wireless communication. These elements connected to the interface 12 may be part of the administrator terminal 1.
[0021] The input device 15 includes, for example, a keyboard for operating a GUI (Graphical User Interface) displayed on the display 14, a mouse, and a touch panel provided on the display 14. The breathalyzer 17 measures, for example, the concentration of alcohol contained in the breath of the driver.
[0022] The digital tachograph 2 includes a controller 20 including a processor and a memory, a storage device 21, a built-in display 22 and speaker 23, and an interface 24 for external connection. The controller 20 realizes various processes disclosed in the present embodiment by the processor executing a computer program stored in the memory. The interface 24 is connected to a communication device 41 capable of communicating with a network N, a display 42, an input device 43, a driving sensor 44, an alcohol detector 45, and a GPS (Global Positioning System) receiver 46 by 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 need to include the display 22 and the speaker 23.
[0023] 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 driver's work category and the vehicle status, such as leaving, returning to the warehouse, loading, unloading, resting, waiting, and staying overnight. The breathalyzer 45 measures the alcohol concentration in the driver's breath, for example. The driving sensor 44 detects driving-related parameters such as the vehicle speed, acceleration, engine RPM, and engine temperature. The GPS receiver 46 receives GPS signals from satellites and detects the vehicle's position based on the signals.
[0024] The server 3 is communicatively connected to the network N. The server 3 may be located outside the business premises or may be located within the business premises. The server 3 may be a server included in a cloud system. In this case, cloud computing in the form of, for example, SaaS (Software as a Service) or the like may be used.
[0025] The server 3 stores a labor management database 30 and an address table 31. The labor management database 30 includes information on the work history and future work schedules of multiple drivers. In the address table 31, the names of business establishments and clients are associated with their addresses.
[0026] The manager terminal 1 can obtain information from the labor management database 30 and address table 31 of the server 3 and store information in the labor management database 30 by communicating via the communication device 13 and the network N. The digital tachograph 2 can also execute similar processes by communicating via the communication device 13 and the network N. In addition, the manager terminal 1 and the digital tachograph 2 can send and receive information to each other via the communication devices 13, 41 and the network N.
[0027] 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 category at each time (waiting, rest, rest, loading, unloading, etc.), the vehicle position (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 46. Furthermore, the controller 20 transmits the operation information to the server 3. The server 3 stores the operation information in the labor management database 30. The controller 10 of the manager terminal 1 accesses the labor management database 30 to obtain the operation information, and can use it for display on the display 14 or for other processing. The operation information may be transmitted directly from the digital tachograph 2 to the manager terminal 1.
[0028] When a driver arrives at a workplace, the controller 10 executes clock-in processing for the driver based on the operation of the input device 15 or other device for clocking in and out. The clock-in processing includes at least a process for confirming the arrival time. When a driver leaves work, the controller 10 executes clock-out processing for the driver based on the operation of the input device 15 or other device for clocking in and out. The clock-out processing includes at least a process for confirming the clock-out time. The controller 10 stores, for example, the arrival time and clock-out time in the storage device 11, and also stores them in the labor management database 30 via the network N.
[0029] In overnight driving, except for the first day, the driver cannot perform clock-in processing at the business office. In this case, the clock-in time is, for example, the departure time when departure is input by the vehicle's input device 43, or the completion time of a predetermined process that starts when departure is input. In addition, in overnight driving, except for the last day, the driver cannot perform clock-out processing at the business office. In this case, the clock-out time is, for example, the return time when return is input by the vehicle's input device 43, or the completion time of a predetermined process that starts when return is input. The controller 20 of the digital tachograph 2 stores these clock-in times (departure times) and clock-out times (return times) in the labor management database 30 via the network N. These clock-in times and clock-out times may be directly transmitted from the digital tachograph 2 to the manager's terminal 1 and stored in the storage device 11 of the manager's terminal 1.
[0030] 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 and the vehicle's driving status in real time both at the workplace and in the vehicle.
[0031] 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 14 based on information such as the labor management database 30. This allows the manager to very easily grasp the working conditions of each driver and the driving conditions of the vehicle, and can also issue necessary instructions to drivers in remote locations.
[0032] 2 is a diagram showing an example of the configuration of the driver information list. The driver information list includes items such as driver ID, driver name, status (driver), vehicle number, status (vehicle), current vehicle location, map button 101, details button 102, remaining on-duty time, remaining rest period, remaining continuous driving time, remaining rest time, daily inspection, pre-duty roll call, mid-duty roll call, post-duty roll call, daily warning count, monthly error count, and monthly compliance rate. The basis time displayed in the upper right corner indicates the current time that is the basis for the calculation of each item. The basis time is updated periodically, for example, and each item is recalculated accordingly.
[0033] Driver ID is identification information for each driver. Status (driver) indicates the driver's status, such as driving, loading, leaving work, etc. Vehicle number is identification information for each vehicle. Status (vehicle) indicates the vehicle status, such as engine ON / OFF. Current location indicates the address where the vehicle is located, identified by a GPS signal.
[0034] The remaining on-duty time indicates the remaining on-duty time that the driver can work on the current working day. For example, if the maximum on-duty time per day is 13 hours, the remaining on-duty time can be the time obtained by subtracting the on-duty time from the start time to the base time on the current working day from 13 hours.
[0035] The remaining rest period indicates the remaining rest period that the driver should take on the current working day. In other words, the remaining rest period corresponds to the remaining time until the next available time to work. For example, if the minimum daily rest period is 8 hours, the remaining rest period can be calculated by subtracting the rest period taken on the current working day from 8 hours.
[0036] The remaining continuous driving time indicates the remaining time that the driver can drive the vehicle continuously. For example, if the maximum continuous driving time in one session is 4 hours and the driver's current state is driving, the remaining continuous driving time can be the time obtained by subtracting the time from the start of driving to the base time from 4 hours.
[0037] The remaining rest time indicates the remaining rest time that the driver should take on the current working day. For example, if the rest time that the driver should take on a day is 60 minutes, the remaining rest time can be the time obtained by subtracting the rest time taken on the current working day from 60 minutes.
[0038] The controller 10 can calculate the remaining working time, remaining rest period, remaining continuous driving time, and remaining break time based on information such as the arrival time at work, the departure time at work, the start time of driving, the end time of driving, the start time of break, and the end time of break obtained from the labor management database 30, for example.
[0039] The daily inspection indicates whether the driver has completed the inspection of the vehicle on the current working day. The pre-duty roll call, mid-duty roll call, and post-duty roll call indicate whether the driver has been called on the current working day.
[0040] For example, when a daily inspection, a pre-duty roll call, an intermediate roll call, and a post-duty roll call are performed, the controller 10 stores these histories in the labor management database 30. Based on the histories thus stored in the labor management database 30, the controller 10 can display in the driver information list whether a daily inspection, a pre-duty roll call, an intermediate roll call, and a post-duty roll call have been performed.
[0041] The number of daily warnings indicates the number of times the labor management system issued a warning to the driver on the current working day. The number of monthly errors indicates the number of times the driver failed to comply with various work-related rules during the month. For example, the above errors include exceeding the upper limit of working hours in one day (working hours error described below), coming to work without taking the required rest period in one day (not taking rest period described below), driving continuously for more than the upper limit of continuous driving time in one session (continuous driving error described below), not taking the required rest period in one day (not taking rest period described below), not performing daily inspection (not performing daily inspection described below), coming to work on a scheduled day off without taking the required holiday time, not performing a pre-shift roll call, mid-shift roll call, or post-shift roll call. The monthly compliance rate indicates the percentage obtained by dividing the number of monthly errors by the total number of the above errors that should be checked on each working day of the month, for example. For example, the lines of drivers whose daily warning numbers, monthly error numbers, or monthly compliance rates are higher than a predetermined threshold may be colored in a manner that makes them distinguishable from the other lines, as in the top row in the figure.
[0042] For example, when the above warnings and errors occur, the controller 10 stores these histories in the labor management database 30. Based on the histories thus stored in the labor management database 30, the controller 10 can calculate the number of daily warnings, the number of monthly errors, and the monthly compliance rate, and display them in a driver information list.
[0043] In the driver information list, for each driver's line, a map button 101 and a details button 102 are provided. Furthermore, in the driver information list, a switch button 103 is provided in the rest period remaining column.
[0044] When the map button 101 is operated, the controller 10 displays a map of the vicinity of the address shown in the current location item on the display 14, and also places a marker on the address.
[0045] When the switching button 103 is operated, the controller 10 switches the item of the rest period remaining to the holiday time remaining. 3 is a diagram showing an example of the configuration of the driver information list after this switching. When the switch button 103 is operated in the driver information list of FIG. 3, the controller 10 displays the driver information list of FIG.
[0046] In Figure 3, the remaining holiday time indicates the remaining time until the next available time to work, taking into account the holidays set for each driver. For example, if a driver takes a one-day holiday, the next available time to work can be the time 32 hours after the previous time of leaving work, which is the sum of the 8 hours of rest period and the 24 hours of holiday. If a driver takes two or more consecutive days of holiday, the time to be added to the 8 hours is 24 hours multiplied by the number of consecutive days of holiday.
[0047] The field in which the remaining holiday time is displayed is provided with a setting button 104. When the setting button 104 is operated, the controller 10 displays a holiday setting screen on the display 14.
[0048] 4 is a diagram showing an example of the configuration of a holiday setting screen 200. The holiday setting screen 200 includes a display field 201, a plus button 202, a minus button 203, an enter button 204, and a cancel button 205.
[0049] The display field 201 displays, by default, the number of holidays for the driver, which is set in the labor management database 30, for example. When the plus button 202 is operated, the number in the display field 201 increases, and when the minus button 203 is operated, the number in the display field 201 decreases. When the cancel button 205 is operated, the controller 10 erases the holiday setting screen 200. When the enter button 204 is operated, the controller 10 updates the holidays for the driver stored in the labor management database 30 with the number of days displayed in the display field 201, and erases the holiday setting screen 200. When the number of holidays is changed on the holiday setting screen 200, the controller 10 recalculates the remaining holiday time in the driver information list and updates the display.
[0050] When the details button 102 is operated in the driver information list, the controller 10 displays the details of the driver information of the driver corresponding to the details button 102 . 5 is a diagram showing an example of the configuration of the driver information details. For example, the driver information details include, in addition to the items included in the driver information list, the arrival time of the current working day, the number of days of holiday taken in the current month, the night work hours in the current month, the actual number of days of attendance in the current month, the planned number of days of attendance in the current month, the actual working hours in the current month, the upper limit of working hours in the current month, the actual number of overnight stays in the current month, the possible number of overnight stays in the current month, the number of working hours errors in the current month, the number of rest days not taken in the current month, the number of continuous driving errors in the current month, the number of breaks not taken in the current month, the number of daily inspections not performed in the current month, the remaining working hours in the current month, the working hours per remaining attendance in the current month, the working hours per actual attendance in the current month, the remaining number of days of attendance in the current month, and the possible number of overnight stays in the current month. Information required to display these items is stored in, for example, the labor management database 30.
[0051] In the area of individual performance, the upper limit of working hours is the upper limit of working hours for one month, for example 320 hours. The actual working hours is the total working hours of the driver from the start of the month to the current working day. The planned number of days of attendance is the number of days the driver is scheduled to work in the month that is set in advance. The actual number of days of attendance is the number of days that the driver has worked up to the current working day in the month. The possible number of overnight stays is the number of times that overnight trips can be performed in the month, for example 14 days. The actual number of overnight stays is the number of times that the driver has performed overnight trips in the month.
[0052] Here, the upper limit of working hours is A, the actual working hours is B, the number of planned working days is C, the actual number of working days is D, the possible number of overnight stays is E, and the actual number of overnight stays is F. In the monthly confirmation area, the remaining working hours can be calculated using AB. The remaining number of working days can be calculated using CD. The remaining number of available overnight stays can be calculated using EF.
[0053] The working hours per attendance record can be calculated by B / D. In other words, the working hours per attendance record is equivalent to the first average working hours calculated by dividing the total working hours of the driver from the start date of the current month to the current working day by the number of working days of the driver from the start date of the current month to the current working day.
[0054] The duty hours per attendance remaining can be calculated as (AB) / (CD). In other words, the duty hours per attendance remaining is equivalent to the second average duty hours calculated by subtracting the total duty hours from the upper limit of duty hours in the current month, and dividing the result by the number of remaining working days of the driver from the current working day to the end of the current month.
[0055] By looking at the driver information details as above, the manager can easily and accurately grasp the driver's working status. In particular, the monthly confirmation area is an important clue for the manager to supervise the driver's work for the current month. For example, if the remaining working hours are too low compared to the remaining number of days of attendance, the manager can change the operation schedule so that the driver can take holidays or reduce working hours, or instruct the driver to reduce working hours.
[0056] The need for schedule changes or guidance can be judged very easily by comparing the commitment time per attendance record with the commitment time per remaining attendance record. In other words, if the commitment time per attendance record is longer than the commitment time per remaining attendance record, it is estimated that the total commitment time for the month will exceed the commitment time upper limit if things continue as they are, so a change in the schedule or guidance is necessary.
[0057] All or part of the information included in the detailed driver information may be displayed on the vehicle's display 42 or the display 22 built into the digital tachograph 2. In this case, the controller 20 of the digital tachograph 2 can obtain the information required for display by reading it from the labor management database 30 or receiving it from the manager terminal 1.
[0058] In this embodiment, the controller 10 of the manager terminal 1 executes holiday acquisition warning processing based on the working time per actual attendance record and the working time per remaining attendance record. 6 is a flowchart showing an example of a holiday acquisition warning process. The holiday acquisition warning process may be executed for a driver when, for example, an attendance process or a departure process is executed, or may be executed for a driver when a driver is specified in a driver information list. The holiday acquisition warning process may also be executed for a specific driver or all drivers when, for example, a predetermined time arrives or an execution instruction is input via the input device 15.
[0059] First, the controller 10 determines whether the remaining attendance time (P) of the driver to be processed is equal to or greater than the attendance time (Q) (step S101). If P≧Q (YES in S101), the controller 10 ends the holiday acquisition warning process.
[0060] If P≧Q is not satisfied (NO in step S101), the controller 10 judges whether QP is equal to or smaller than the threshold value SH (step S102). The threshold value SH may be, for example, about 30 minutes. If (QP)≦SH (YES in step S102), the controller 10 executes a commitment time warning (step S103). The commitment time warning can be executed, for example, by displaying a message on the display 14 or outputting a voice message from the speaker 16 to inform the manager or the driver that the commitment time per attendance record exceeds the commitment time per remaining attendance, that the commitment time for the month may exceed the upper limit if the situation continues, and that the commitment time needs to be reduced for the remaining working days of the month. The commitment time warning may also be executed by coloring the line of the driver in question in yellow, for example, or by attaching some kind of identifier to the line in the driving information list.
[0061] On the other hand, if (QP)≦SH is not satisfied (NO in step S102), the controller 10 issues an additional holiday acquisition warning (step S104). The additional holiday acquisition warning can be issued, for example, by displaying a message on the display 14 or by outputting an audio message from the speaker 16 informing the manager or driver that an additional holiday should be acquired in the current month. The additional holiday acquisition warning may also be issued by coloring the driver's line in the driving information list in red, for example, or by attaching some kind of identifier.
[0062] The additional holiday acquisition warning may notify the number of additional holidays to be taken. The number of additional holidays to be taken may be, for example, the value obtained by multiplying QP by the remaining number of working days in the current month, and dividing the result by the upper limit of working hours per day or Q. The value may be rounded down or up to the nearest whole number.
[0063] The holiday acquisition warning process ends with steps S103 and S104. The warning in steps S103 and S104 can reliably make the driver or manager aware that the on-duty hours for the current month may exceed the upper limit.
[0064] It should be noted that other judgment methods may be adopted in step S102. For example, step S102 may be to judge whether the value obtained by multiplying QP by the remaining number of working days in the current month and dividing the result by the upper limit of working hours per day or Q is less than 1. In this case, if it is less than 1, a working hours warning is issued, and if it is 1 or more, an additional holiday acquisition warning is issued.
[0065] The warnings in steps S103 and S104 may be executed using the display 22, the speaker 23 or the display 42 of the digital tachograph 2 through communication via the network N.
[0066] Moreover, the holiday acquisition warning process may be executed by the digital tachograph 2 or the server 3. In these cases, the warning in steps S103 and S104 can be executed using at least one of the displays 14, 22, and 42 and the speakers 16 and 23.
[0067] Next, the above-mentioned pre-duty roll call, intermediate roll call, and post-duty roll call will be described. The labor management system according to this embodiment has a function to assist each roll call. Information about each roll call (roll call information) is required to be stored for a certain period of time. In this embodiment, the roll call information is stored in the labor management database 30, for example. The roll call information may be stored in the storage device 11, etc.
[0068] 7 is a diagram showing an example of the configuration of roll call information. This roll call information is created, for example, for each working day. The roll call information includes items such as vehicle number, driver name, work assignment, pre-drivage roll call, intermediate roll call, and post-drivage roll call. Furthermore, the pre-drivage roll call, intermediate roll call, and post-drivage roll call items include roll call method, breathalyzer (whether or not it was used, and the measurement result), confirmation items, roll call time, and executor.
[0069] The work allocation indicates the location where the driver will first perform work on that work day. The roll call method indicates, for example, whether it was conducted in person or over the phone. Whether or not a breathalyzer was used indicates whether an alcohol check was conducted using a breathalyzer. The measurement result indicates the measurement value of the breathalyzer. The items to be confirmed indicate whether or not the manager confirmed with the driver predetermined items at each roll call, such as whether or not the driver was under the influence of alcohol, the driver's illness or fatigue status, the status of daily inspections, and the status of operation. The roll call time indicates the time the roll call was conducted (for example, the time the roll call was completed). The executor indicates the manager who conducted the roll call.
[0070] When a driver clocks in at a workplace, a pre-shift roll call is generally conducted face-to-face at the workplace. When a driver clocks out at a workplace, a post-shift roll call is generally conducted face-to-face at the workplace.
[0071] On the middle and last days of overnight trips, drivers do not clock in at the office. Therefore, pre-shift roll calls are generally conducted by telephone. Also, on the first and middle days of overnight trips, drivers do not clock out at the office. Therefore, post-shift roll calls are generally conducted by telephone. Also, on the middle days of overnight trips, intermediate roll calls are generally conducted by telephone.
[0072] 8 is a flowchart of a roll call process A executed by the controller 10 in a face-to-face roll call at a business establishment. This roll call process A is started, for example, when a manager (executor) inputs a request to execute a roll call via the input device 15. First, the controller 10 displays an input screen for roll call information on the display 14 and accepts input of the driver to be called and the person who will be called (step S201). After the driver and the person who will be called have been input, the controller 10 accepts input of the measurement result by the breathalyzer 17 (step S202). The measurement result may be automatically input after being transmitted from the breathalyzer 17 to the manager terminal 1, or may be input by the person who will be called via the input device 15.
[0073] The controller 10 displays the alcohol measurement result and the driver's work information on the display 14 (step S203). The work information includes, for example, the items shown in the driver information details in Fig. 5 and the remaining holiday time. In step S203, the above-mentioned holiday acquisition warning process may be executed.
[0074] For example, in a pre-shift roll call, by checking the remaining rest period and remaining holiday time included in the work information, it is possible to know whether the driver has taken the necessary rest period or holiday time. In a pre-shift roll call, if the remaining rest period or remaining holiday time of the driver at the time of arrival at work on the current working day is not zero, a warning may be issued by displaying on the display 14 or outputting a sound from the speaker 16.
[0075] In the post-drive roll call, the remaining working time included in the work information can be checked to see if the driver's working time exceeds the upper limit. If the remaining working time of the driver is already zero in the post-drive roll call, a warning may be issued by displaying on the display 14 or outputting a voice from the speaker 16.
[0076] Furthermore, the controller 10 receives an input of the check result of the confirmation items (step S204). Specifically, the controller 10 displays on the display 14 a first button indicating that there is no problem with the confirmation items and a second button indicating that there is a problem, and waits for these buttons to be operated.
[0077] When the check results of the confirmation items are input, the controller 10 judges whether there is a problem with the confirmation items (step S205). For example, if the first button is operated, the controller 10 judges that there is no problem with the confirmation items (YES in step S204), and updates (records) the roll call information in the driver's labor management database 30 input in step S201 (step S206). In this roll call information, the roll call method is "face-to-face", the use or non-use of the breathalyzer is "conducted", the measurement result is the numerical value displayed in step S203, the confirmation items are "OK", the roll call time is, for example, the current time, and the executor is the executor input in step S201.
[0078] After step S206, or when it is determined in step S205 that there is a problem due to the operation of the second button (NO in step S205), the controller 10 ends the roll call process A.
[0079] Next, a process for recording work assignments in the roll call information of FIG. 7 will be described. 9 is a flowchart showing an example of the work assignment recording process. This process is executed, for example, when a driver who has completed a pre-drive roll call inputs a work such as loading or unloading for the first time after inputting a departure from the vehicle through the input device 43 of the vehicle with the vehicle number shown in the roll call information.
[0080] First, the controller 10 acquires the address of the current location of the vehicle (step S301). This address is, for example, the current location of the vehicle (driver) in the labor management database 30. Alternatively, the manager terminal 1 may acquire a GPS signal received by the GPS receiver 46 of the vehicle, and acquire the address based on the GPS signal. Alternatively, the address may be input by the input device 15.
[0081] Next, the controller 10 searches the address table 31 for the address acquired in step S301 (step S302). Furthermore, the controller 10 determines whether or not a corresponding address has been found in the address table 31 (step S303).
[0082] When a corresponding address is found (YES in step S303), the controller 10 saves (records) the name registered for the corresponding address in the address table 31 in the roll call information as the task assignment of the driver (step S304). On the other hand, when a corresponding address is not found (NO in step S303), the controller 10 saves (records) the address acquired in step S301 in the roll call information as the task assignment of the driver (step S305). After step S304 or S305, the task assignment recording process ends.
[0083] Next, an intermediate call will be described. In this embodiment, the intermediate call is performed by the digital tachograph 2 and the manager terminal 1 in cooperation with each other. 10 is a flowchart showing an example of a driving process executed by the digital tachograph 2. This driving process is started when, for example, a departure command is input via the input device 43.
[0084] First, the controller 20 of the digital tachograph 2 judges whether the current working day is the day after an overnight stay, that is, the second day or later of the overnight operation (step S401). For example, the controller 20 judges that the current working day is the day after an overnight stay if the return process for the previous working day is executed with the operation of the return button of the input device 43 as a trigger. On the other hand, the controller 20 judges that the current working day is not the day after an overnight stay if the return process for the previous working day is executed with the operation of the return button of the input device 43 as a trigger. The method of judging whether the current working day is the day after an overnight stay is not limited to this, and for example, a button for selecting whether the current working day is the day after an overnight stay or not may be displayed on the display 42, and the judgment may be made based on the operation result of this button. Also, if the clock-out process was not executed on the manager terminal 1 on the previous working day, the current working day may be judged to be the day after an overnight stay.
[0085] If it is determined that it is the day after the stay (YES in step S401), the controller 20 displays the stay confirmation screen 300 on the display 42 (step S402). 11 is a diagram showing an example of an accommodation confirmation screen 300. The accommodation confirmation screen 300 includes a message such as "Are you staying tonight?", as well as a Yes button 301, a No button 302, and an I don't know button 303.
[0086] When any of the buttons 301 to 303 is operated, the controller 20 closes the accommodation confirmation screen 300 and determines whether the current working day is the last day of the overnight operation (step S403). When the button 302 is operated on the accommodation confirmation screen 300, the controller 20 determines that the current working day is the last day of the overnight operation, and when the button 301 or button 303 is operated, the controller 20 determines that the current working day is not the last day of the overnight operation.
[0087] If it is determined that it is not the last day of the stay (NO in step S403), the controller 20 displays the roll call schedule confirmation screen 400 on the display 42 (step S404). 12 is a diagram showing an example of a roll call schedule confirmation screen 400. The roll call schedule confirmation screen 400 includes a change button 401 and a do not change button 402 along with a message such as "Please conduct the intermediate roll call between 11:00 and 14:00. Would you like to change the scheduled time of the intermediate roll call?". "11:00 to 14:00" in the message is, for example, a default time (time period) that has been set in advance. The default time is not limited to this example and may be another time (time period).
[0088] When either of the buttons 401, 402 is operated, the controller 20 closes the roll call schedule confirmation screen 400 and determines whether or not the scheduled time has changed (step S405). When the button 401 is operated on the roll call schedule confirmation screen 400, the controller 20 determines that the scheduled time has changed, and when the button 402 is operated, the controller 20 determines that the scheduled time has not changed.
[0089] When it is determined that the scheduled time has been changed (YES in step S405), the controller 20 determines whether the driver has changed the scheduled time of the intermediate roll call in the past (for example, after the start date of the current month) (step S406). When there is a change (YES in step S406), the controller 20 displays the schedule change screen 500 reflecting the settings at the time of the previous change on the display 42 (step S407).
[0090] 13 is a diagram showing an example of a schedule change screen 500. The schedule change screen 500 includes display fields 501, 502 that respectively display hours and minutes, a plus button 503 and a minus button 504 that increment or decrement the value in the display field 501, a plus button 505 and a minus button 506 that increment or decrement the value in the display field 502, a confirm button 507, and a cancel button 508. The display fields 501, 502 display the time (15:00 in this example) that was set in the previous scheduled time change. The driver can adjust the scheduled time by operating buttons 503-506.
[0091] On the other hand, if it is determined in step S406 that there has been no change history (NO in step S406), the controller 20 displays on the display 42 the schedule change screen 500 in which the above-mentioned default times are input in the display fields 501 and 502 (step S408).
[0092] When the decision button 507 is operated on the schedule change screen 500, the controller 20 closes the schedule change screen 500. Furthermore, the controller 20 sets the time entered in the display fields 501 and 502 as the scheduled time of the intermediate roll call by, for example, storing it in the storage device 21 (step S409). When the cancel button 508 is operated on the schedule change screen 500, and when it is determined in step S405 that the schedule will not be changed (NO in step S405), the controller 20 sets the default time as the scheduled time of the intermediate roll call (step S409).
[0093] The scheduled time set on schedule change screen 500 may be a time slot such as from xx:xx to xx:xx. In this case, for example, a GUI for setting such a time slot may be provided on schedule change screen 500. Also, in step S409, a time slot from the time entered on schedule change screen 500 in Fig. 13 to a time a predetermined time has elapsed, or a time slot with a predetermined time width before and after the time entered on schedule change screen 500 may be set as the scheduled time.
[0094] The controller 20 also stores the scheduled time of the intermediate roll call thus set in the labor management database 30. The scheduled time may be transmitted to the manager terminal 1 and stored in the storage device 11 of the manager terminal 1.
[0095] After step S409, if it is determined in step S401 that it is not the day after the stay (NO in step S401), or if it is determined in step S403 that it is the last day of the stay (YES in step S403), the controller 20 executes in-travel processing (step S410).
[0096] During operation processing, the controller 20 performs various processes such as generating and storing the above-mentioned operation information, storing the work category and vehicle status inputted via the input device 43, and displaying the driver information of the driver stored in the labor management database 30.
[0097] Furthermore, the controller 20 determines whether an intermediate roll call is necessary (step S411). If an intermediate roll call has already been conducted or if the current working day is not the middle day of an operation involving at least two nights of lodging, the controller 20 determines that an intermediate roll call is unnecessary (NO in step S411). For example, if the above-mentioned lodging confirmation screen 300 is displayed in the operation process and the button 302 is operated, it can be determined that the current working day is not the middle day of an operation involving at least two nights of lodging. The controller 20 may determine that an intermediate roll call is unnecessary if the scheduled time for the intermediate roll call has not been set in step S409.
[0098] On the other hand, if the current working day is the middle day of an operation involving at least two nights of lodging and the intermediate call has not been performed, the controller 20 determines that an intermediate call is necessary (YES in step S411). For example, if the above-mentioned lodging confirmation screen 300 is displayed in the operation process and the button 301 or button 303 is operated, it can be determined that the current working day is the middle day of an operation involving at least two nights of lodging. The controller 20 may determine that an intermediate call is necessary when the scheduled time for the intermediate call is set in step S409 and the intermediate call has not been performed. Thereafter, the controller 20 determines whether the scheduled time for the intermediate call has arrived (step S412).
[0099] During the processing of steps S410 to S412, the controller 20 monitors the occurrence of a return-to-warehouse event (step S413). The return-to-warehouse event is input by operating a return-to-warehouse button or an overnight stay button on the input device 43. For example, the driver operates the return-to-warehouse button when returning to the business establishment to return to the business establishment, and operates the overnight stay button when returning to the business establishment outside the business establishment on the first day or the middle day of an overnight trip.
[0100] While a return-to-warehouse event has not occurred, the controller 20 repeats the processes of steps S410 to S412 (NO in step S413). If a return-to-warehouse event has occurred (YES in step S413), the controller 20 executes a return-to-warehouse process (step S414). In the return-to-warehouse process, a return-to-warehouse time is determined and stored in the labor management database 30. The return-to-warehouse time may be stored in the storage devices 11 and 21.
[0101] When a return event occurs by pressing the lodging button, the return time becomes the driver's finishing time. In this case, the return process may display the next available time to work (leave the warehouse) and the work history for that work day on the display 42. The next available time to work may be, for example, the time when the minimum rest period has elapsed since the return time. The above-mentioned holiday acquisition warning process may be executed in the return process. The operation process ends at step S414.
[0102] When it is determined in step S412 that the scheduled time for the intermediate roll call has arrived (YES in step S412), the controller 20 displays the roll call schedule notification screen 600 on the display 42 (step S415).
[0103] 14 is a diagram showing an example of a roll call schedule notification screen 600. The roll call schedule notification screen 600 includes a scheduled date and time for the intermediate roll call, which is the scheduled time of the intermediate roll call set in step S409 plus the current date, a message for encouraging the intermediate roll call to be performed, such as "Please contact the operations manager and perform an intermediate roll call," and an execution button 601. Together with the roll call schedule notification screen 600, the speaker 23 may output a voice message indicating the arrival of the scheduled time for the intermediate roll call.
[0104] When the implementation button 601 is operated, the controller 20 executes roll call process B. The driver calls the manager (executor) and requests the initiation of an intermediate roll call. The intermediate roll call may be implemented by voice communication via the network N. At the time of the intermediate roll call, roll call process C is executed in the manager terminal 1. The roll call process C may be started, for example, in conjunction with the roll call process B, or may be started when the manager inputs the implementation of a roll call via the input device 15.
[0105] In addition, the pre-duty roll call except on the first day of the overnight operation and the post-duty roll call except on the last day of the overnight operation cannot be conducted at the business establishment. Even in these cases, the roll call processing B and C are executed in response to, for example, input of the start of the roll call by the input device 43.
[0106] FIG. 15 is a flowchart showing an example of the roll call processes B and C. First, the controller 20 accepts the input of the measurement result by the breathalyzer 45 (step S501). The measurement result may be transmitted from the breathalyzer 45 to the digital tachograph 2 and automatically input, or may be input by the driver via the input device 43.
[0107] The controller 20 displays the alcohol measurement result on the display 42 (step S502). Furthermore, the controller 20 transmits various information including the driver ID and the alcohol measurement result to the administrator terminal 1 via the network N (step S503). After transmitting the various information, the controller 20 displays a completion waiting screen 700 on the display 42 (step S504) and waits to receive a completion notification from the administrator terminal 1 (step S505).
[0108] 16 is a diagram showing an example of a completion waiting screen 700 for an intermediate roll call. The completion waiting screen 700 includes a cancel button 701 along with a message such as "Currently waiting for the operations manager to register the roll call. If it will take some time, please check with the operations manager." When the cancel button 701 is operated, the roll call process B ends. A similar completion waiting screen 700 is also displayed for a pre-duty roll call and a post-duty roll call.
[0109] The controller 10 of the manager terminal 1 receives the information transmitted in step S502 (step S601). Furthermore, the controller 10 displays a roll call information input screen on the display 14 and accepts input of the driver to be called and the person who will conduct the roll call (step S602).
[0110] After the driver and the person responsible have been input, the controller 10 displays the alcohol test results and the driver's work information contained in the information received in step S601 on the display 14 (step S603). The work information includes, for example, the items shown in the driver information details in FIG. 5 and remaining holiday time. In step S603, the above-mentioned holiday acquisition warning process may be executed. As in step S203, warnings regarding the remaining rest period, remaining holiday time, and remaining on-duty time may be displayed on the display 14 or issued as audio output by the speaker 16. The display of these warnings and work information may also be executed in the vehicle using the display 42 and speaker 23.
[0111] Furthermore, the controller 10 accepts input of the check results of the confirmation items (step S604), judges whether there is a problem (step S605), and updates the roll call information of the driver if there is no problem (step S606). The processing of these steps S604 to S606 is the same as steps S204 to S206. Note that the roll call method is "telephone".
[0112] After that, the controller 10 transmits a notification of completion of the roll call information recording to the digital tachograph 2 via the network N (step S607). This notification includes the roll call time, which is the time when the roll call was performed. With step S607, the roll call process C ends.
[0113] When the completion notification transmitted in step S607 is received (YES in step S505), the controller 20 of the digital tachograph 2 erases the completion wait screen 700 and displays the completion screen 800 on the display 42 (step S506).
[0114] FIG. 17 is a diagram showing an example of a completion screen 800 in an intermediate roll call. The completion screen 800 includes a message such as "The intermediate roll call is completed. Please continue driving safely.", the intermediate roll call implementation date and time obtained by adding the date to the roll call time included in the completion notice, and a completion button 801. When the completion button 801 is operated, the controller 20 erases the completion screen 800 and ends the roll call process B. A similar completion screen 800 is also displayed in the pre-duty roll call and the post-duty roll call. If it is determined in step S605 that there is a problem (NO in step S605), identification information to that effect may be included in the completion notice. For example, when this completion notice is received, the controller 20 displays a message indicating that there is a problem on the display 42 and ends the roll call process B.
[0115] In the above embodiment, if it is determined in step S401 that it is the day after an overnight stay, and if it is determined in step S403 that the current working day is not the last day of an overnight stay, this means that the current working day is the middle day of an overnight trip of two nights or more. In this embodiment, it is determined that an intermediate roll call is necessary on this middle day, and when the scheduled time for the intermediate roll call arrives, the roll call schedule notification screen 600 notifies the driver or manager that an intermediate roll call should be conducted. This process allows the driver or manager to reliably conduct an intermediate roll call. In addition, the driver or manager can be saved from the trouble of managing the schedule for the intermediate roll call, and can concentrate on other tasks.
[0116] In the roll call processes B and C, even if the driver is in a remote location of the business premises, the alcohol measurement result by the in-vehicle breathalyzer 45 and the like can be easily confirmed on the manager terminal 1. In addition, the driver can grasp the progress of the roll call on the completion waiting screen 700 and the completion screen 800.
[0117] The roll call information in the labor management database 30 updated by the roll call processes A to C can also be printed out, for example, in the format of Fig. 7. Such roll call information can also be used for purposes such as business audits.
[0118] The work assignments in the roll call information can be automatically recorded by the work assignment recording process in Fig. 9. This saves the manager the trouble of checking the work assignments of the drivers and inputting the results.
[0119] In addition, in this embodiment, driver labor management can be performed extremely easily and accurately using the driver information lists shown in Figures 2 and 3 and the driver information details shown in Figure 5. Furthermore, the remaining rest period can be switched to the remaining holiday time using the switch button 103, and the planned number of holidays to be taken can also be changed using the holiday setting screen 200 shown in Figure 4, so holiday management can also be performed appropriately.
[0120] In addition, the holiday acquisition warning process shown in Fig. 6 can notify managers and drivers themselves of drivers whose working hours may exceed the upper limit for the current month. Furthermore, by notifying managers and drivers that they should take additional holidays and the number of holidays they should take, it is possible to increase the effectiveness of compliance with the monthly working hours upper limit. In addition to the above, various other advantageous effects can be obtained from this embodiment.
[0121] In the present embodiment, the working hours and rest periods are mainly managed on a monthly basis, but the working hours and rest periods may be managed on a weekly basis, a yearly basis, or an arbitrarily set number of days or months, or other predetermined period.
[0122] [Second embodiment] Fig. 18 is a block diagram showing an example of the configuration of a labor management system according to the second embodiment. This labor management system includes a driver terminal 5 separate from the digital tachograph 2. The driver terminal 5 may be a mobile device such as a tablet or smartphone. The driver terminal 5 may be a device fixedly mounted in the vehicle.
[0123] The driver's terminal 5 includes a controller 50 including a processor and a memory, a storage device 51, a built-in display 52 and a speaker 53, and an interface 54 for external connection. The controller 50 realizes various processes by the processor executing computer programs stored in the memory.
[0124] The driver's terminal 5 includes, for example, a touch panel that detects an operation of the display 52, but may further include other input devices. The interface 54 is communicatively connectable to, for example, the communication device 41, the display 42, the input device 43, the driving sensor 44, the breathalyzer 45, the GPS receiver 46, and the interface 24 of the digital tachograph 2. The communication connections between these may be wired or wireless. The driver's terminal 5 may have a built-in wireless communication device for communicating with the network N.
[0125] The controller 50 of the driver's terminal 5 executes part or all of the processes that are to be executed by the controller 20 of the digital tachograph 2 in other embodiments. For example, when the controller 50 executes the driving process of FIG. 10 or the roll call process B of FIG. 15, the screens shown in FIGS. 11 to 14, 16, and 17 may be displayed on the display 52. In addition, various screens that are to be displayed on the display 42 in the present disclosure may be displayed on the display 52. Furthermore, information and instructions that are to be input by the input device 43 in the present disclosure may be input by operating a GUI displayed on the display 52 using a touch panel. In other words, the input device operated by the driver does not necessarily need to be a device separate from the driver's terminal 5, and may be included in the driver's terminal 5.
[0126] At least a part of the labor management database 30 may be stored in the storage device 51 of the driver terminal 5, such as detailed driver information and roll call information of the driver who owns the driver terminal 5.
[0127] The labor management system does not need to include the digital tachograph 2. In this case, for example, the controller 50 of the driver's terminal 5 may execute some or all of the processing that is executed by the controller 20 of the digital tachograph 2 in other embodiments.
[0128] [Third embodiment] Fig. 19 is a block diagram showing an example of the configuration of a labor management system according to the third embodiment. This labor management system includes three business establishments O1 to O3. A manager terminal 1 is disposed in the business establishment O1. Business establishments O2 and O3 each have a business establishment terminal 6.
[0129] The configurations of the administrator terminal 1 and the establishment terminal 6 are similar to those of the administrator terminal 1 in other embodiments. For example, the administrator terminal 1 and the establishment terminal 6 can execute at least a part of the processes that are executed by the administrator terminal 1 in other embodiments. As in the above-mentioned embodiments, the establishments O1 to O3 are provided with a communication device 13, a display 14, an input device 15, a speaker 16, and an alcohol detector 17. Furthermore, the establishments O1 to O3 are provided with a camera 18 and a microphone 19 connected to the administrator terminal 1.
[0130] The number of establishments O1 to O3 included in the labor management system is not limited to three. Although not shown in FIG. 19, the labor management system includes vehicle-related components such as a driver's terminal, as in each of the above-mentioned embodiments. The driver's terminal may be a digital tachograph as in the first embodiment, or may be a device separate from the digital tachograph as in the second embodiment. Each of the establishments O1 to O3 has multiple vehicles and drivers.
[0131] In this embodiment, the manager who will be the person in charge of the roll call is located at the business establishment O1. For example, the manager terminal 1 at the business establishment O1 stores the labor management database 30. As in each of the above-mentioned embodiments, the labor management database 30 may be stored in a server communicatively connected to the network N.
[0132] A pre-shift roll call of a driver leaving the establishment O1 and a post-shift roll call of a driver returning to the establishment O1 are carried out by the above-mentioned roll call process A executed by the manager terminal 1 of the establishment O1.
[0133] A pre-shift roll call of a driver leaving business establishment O2 and a post-shift roll call of a driver returning to business establishment O2 are carried out by communication between the business establishment terminal 6 of business establishment O2 and the manager terminal 1 of business establishment O1 via the network N. In this roll call, the business establishment terminal 6 of business establishment O2 executes the above-mentioned roll call process B, and the manager terminal 1 executes the above-mentioned roll call process C.
[0134] In these roll call processes B and C, warnings regarding the remaining rest period, remaining holiday time, and remaining working time may be issued, similar to the above-mentioned step S203. These warnings may be issued by the manager terminal 1 using the display 14 and speaker 16 of the business establishment O1, or by the business establishment terminal 6 using the display 14 and speaker 16 of the business establishment O2. In addition, in these roll call processes B and C, the above-mentioned holiday acquisition warning process may be executed.
[0135] In addition, at a predetermined timing in the roll call processing B, C, for example, immediately after steps S503, S601, a video call between the establishment terminal 6 and the manager terminal 6 is started. That is, the camera 18 of the establishment O2 captures the face of the driver to be called and the microphone 19 collects the driver's voice, and these video data and audio data are sent to the manager terminal 1 of the establishment O1 via the network N. In the establishment O1, for example, an image based on the video data is displayed on the display 14, and audio based on the audio data is output from the speaker 16. In addition, the camera 18 of the establishment O1 captures the face of the executioner and the microphone 19 collects the executioner's voice, and these video data and audio data are sent to the establishment terminal 6 of the establishment O2 via the network N. In the establishment O2, for example, an image based on the video data is displayed on the display 14, and audio based on the audio data is output from the speaker 16.
[0136] In such a video call, the enforcer can see the face and voice of the driver, so it is possible to grasp the driver's health condition to the same extent as in the case of a face-to-face roll call. The video call is disconnected, for example, when the roll call process B or C ends.
[0137] Although the roll call processing between the establishment terminal 6 of the establishment O2 and the manager terminal 1 has been explained above, the roll call processing between the establishment terminal 6 of the establishment O3 and the manager terminal 1 is similar. The intermediate roll call is performed, for example, between the driver terminal of each driver and the manager terminal 1 of the business establishment O1. The flow of the intermediate roll call is the same as that of each of the above-mentioned embodiments. The vehicle and the driver terminal may be provided with a camera, microphone, and speaker for video calling, and the intermediate roll call similar to the above may be performed by video calling between the driver terminal and the manager terminal 1.
[0138] [Fourth embodiment] In the operation process shown in the flowchart of Fig. 10, an example is shown in which the roll call schedule notification screen 600 notifies the user that an intermediate roll call should be performed when the scheduled roll call time arrives. However, the timing and method of the notification that an intermediate roll call should be performed can be modified in various ways. In this embodiment, an example is shown of processing in which the scheduled roll call time is not used.
[0139] FIG. 20 is a flowchart showing an example of the roll call necessity determination process in this embodiment. Here, an example will be described in which the controller 20 of the digital tachograph 2 executes the process in the configuration of the labor management system of the first embodiment. The controller 20 executes the process at any timing between the departure and return of the vehicle. For example, the controller 20 may execute the process at a predetermined time interval (10 minutes, 30 minutes, 1 hour, etc.). The controller 20 may also execute the process when a predetermined time or time period arrives, when a certain time has passed since the departure time, when the vehicle stops traveling, when a specific button on the input device 43 is operated, etc.
[0140] First, the controller 20 judges whether the current working day is the middle day of the overnight operation (step S701). For example, in this embodiment, if the above-mentioned accommodation confirmation screen 300 is displayed at the start of the operation and the operation of the buttons 301 to 303 is accepted, it is possible to judge whether the current working day is the middle day in step S701. Also, if the driver's operation schedule is set in advance in the labor management database 30, it is possible to judge whether the current working day is the middle day based on this operation schedule.
[0141] When it is determined that the current work day is an intermediate day (YES in step S701), the controller 20 determines whether an intermediate roll call has been conducted on the current work day based on, for example, the driver's roll call information in the labor management database 30 (step S702). If an intermediate roll call has not been conducted (step S703), the controller 20 displays an intermediate roll call image 900 on the display 42 (step S703).
[0142] FIG. 21 is a diagram showing an example of an intermediate roll call image 900 displayed on the display 42. The intermediate roll call image 900 includes, for example, the character string "intermediate roll call" and is displayed superimposed on the screen currently being displayed on the display 42. If the intermediate roll call image 900 is placed in a corner of the display 42 as shown in the figure, the visibility of the information on the currently being displayed screen is not hindered. Conversely, if the intermediate roll call image 900 is placed in the center of the display 42, for example, the intermediate roll call image 900 can be made to stand out. The intermediate roll call image 900 may be a message such as "Please conduct an intermediate roll call."
[0143] If it is determined that the current working day is not a mid-day (NO in step S701), if it is determined that an intermediate roll call has already been conducted (YES in step S702), or after step S703 has been executed, the roll call necessity determination process ends.
[0144] After that, the intermediate roll call image 900 continues to be displayed on the display 42. For example, when the driver operates the input device 43 to start the roll call process B shown in the flowchart of Fig. 15 and a completion notice transmitted from the manager terminal 1 is received, the controller 20 erases the intermediate roll call image 900. The intermediate roll call image 900 itself may be a button for starting the roll call process B.
[0145] The above-described intermediate roll call necessity determination process may be executed not only by the digital tachograph 2 but also by the controller 10 of the manager terminal 1. In this case, the intermediate roll call image 900 is displayed, for example, on the display 14. The intermediate roll call image 900 may include a driver ID or a driver name so that it is possible to identify which driver the intermediate roll call image 900 pertains to. The intermediate roll call image 900 may also display drivers who require an intermediate roll call in a list format.
[0146] In the configuration of the labor management system of the second embodiment, the intermediate roll call necessity determination process may be executed by the controller 20 of the digital tachograph 2 or by the controller 50 of the driver terminal 5. In addition, in the configuration of the labor management system of the third embodiment, the intermediate roll call necessity determination process may be executed by the business terminal 6.
[0147] In step S703, not only the intermediate call image 900 is displayed, but also the speaker 16, 23 may output audio to inform the user that an intermediate call is required.
[0148] [Fifth embodiment] In the fifth embodiment, a labor management system is disclosed that can further manage the waiting time (luggage waiting time) of a driver at a loading point or an unloading point of luggage transported by a vehicle. Here, it is assumed that the labor management system has the same configuration as the first embodiment, but the labor management system may have the same configuration as the other embodiments.
[0149] The labor management system has the following functions for managing waiting time: [F1] A function for inputting the start and end of waiting of the vehicle driver at the loading or unloading point of the cargo. [F2] Function to enter the shipper of the cargo handled in loading or unloading. [F3] Function to input designated arrival time. [F4] Function to calculate waiting time at loading or unloading points. [F5] Function to calculate waiting fees for waiting time. [F6] A function to record waiting information including waiting time and waiting fees. [F7] A function to set whether the input of the shipper's information (F2) and the designated arrival time (F3) will be performed on the administrator terminal 1 or the digital tachograph 2 (driver's terminal).
[0150] The driver can start waiting by, for example, operating the standby button on the input device 43. The driver can end waiting by, for example, operating the standby button again after operating the standby button, or by operating another button such as the loading button or unloading button. The designated arrival time is, for example, an arrival time designated in advance by the shipper. The designated arrival time may also be an arrival time designated by an entity other than the shipper, such as an entity operating the loading or unloading point.
[0151] Below, the details of each function will be explained with reference to Fig. 22, taking as an example a case where function F7 is set to input the shipper and the designated arrival time into the digital tachograph 2, and the waiting time and waiting fee are calculated and recorded by the manager terminal 1. However, the shipper and the designated arrival time may be input into the manager terminal 1, or one of these may be input into the manager terminal 1 and the other into the digital tachograph 2. Furthermore, calculation and recording of at least one of the waiting time and waiting fee may be performed by the digital tachograph 2 or the server 3.
[0152] When the driver arrives at a loading or unloading point and needs to wait for work such as loading or unloading, the driver operates the standby button of the input device 43. This causes the digital tachograph 2 to execute standby processing A shown in the flowchart of Fig. 22. Furthermore, the manager terminal 1 executes standby processing B shown in the flowchart.
[0153] First, the controller 20 of the digital tachograph 2 determines whether 30 minutes have passed since the standby start time, which is the time when the standby start was input (step S801). This 30 minutes is just an example, and other appropriate times such as 10 minutes, 15 minutes, or 1 hour can be set.
[0154] If 30 minutes have not elapsed, the controller 20 does not proceed to the next process (NO in step S801). If the command to end standby is input before 30 minutes have elapsed, the controller 20 ends standby process A.
[0155] If 30 minutes have passed (YES in step S801), the controller 20 accepts input from the shipper (step S802). Furthermore, the controller 20 accepts input from the type of work to be performed, such as loading or unloading (step S803), and accepts input from the designated arrival time (step S804). In steps S802 to S804, the controller 20 displays an input screen for the shipper, type of work, and designated arrival time on the display 42, for example, and issues a message from the speaker 23 to prompt the driver to enter this information. The driver can enter the shipper, type of work, and designated arrival time, for example, through the input device 43. If the arrival time is not specified by the shipper, etc., "no designated arrival time" may be entered.
[0156] Thereafter, the controller 20 transmits various information including the inputted shipper, type of business, designated arrival time, driver ID, vehicle number, waiting start time, etc. to the manager terminal 1 via the network N (step S805). Furthermore, the controller 20 waits for the waiting to end (step S806).
[0157] When the driver starts work such as loading or unloading, he inputs the end of waiting. At this time, the controller 20 transmits the waiting end time, which is the time when the waiting end was input, to the manager terminal 1 via the network N (step S807). With step S807, the waiting process A ends.
[0158] In standby process B, the controller 10 of the manager terminal 1 receives the information transmitted from the digital tachograph 2 in step S805 (step S901). The controller 10 displays a confirmation screen on the display 14 based on the received information and accepts corrections (step S902). The confirmation screen includes, for example, the shipper, the type of work, the designated arrival time, the driver ID, the vehicle number, and the standby start time. The confirmation screen may display the current location corresponding to the driver ID in the driver information list described above. If this current location is displayed, the operations manager can easily determine whether the shipper entered by the driver is correct. If the information displayed on the confirmation screen is inaccurate, the operations manager corrects it by operating the input device 15, for example.
[0159] When the confirmation of the information displayed on the confirmation screen is completed, the operations manager inputs confirmation completion, for example, via the input device 15. After that, the controller 10 waits to receive the waiting end time transmitted by the digital tachograph 2 in step S807 (step S903).
[0160] When the waiting end time is received (YES in step S903), the controller 10 calculates the waiting time and displays the calculated waiting time on the display 14 (step S904). Furthermore, the controller 10 calculates the waiting fee and displays the calculated waiting fee on the display 14 (step S905).
[0161] The controller 20 saves (records) the standby information including the information received in step S901 and the standby time and standby fee calculated in steps S904 and S905 (step S906). The standby information may be saved in the labor management database 30 of the server 3, for example, or in the storage device 11. With step S906, the standby process B ends.
[0162] The waiting time calculated in step S904 is, for example, the time from the waiting start time to the waiting end time when the waiting start time is later than the designated arrival time. Also, the waiting time is, for example, the time from the designated arrival time to the waiting end time when the waiting start time is earlier than the designated arrival time. If the time from the designated arrival time to the waiting end time is less than 30 minutes, the waiting information may not be recorded in step S906.
[0163] The waiting time may be calculated by further considering the business start time of the shipper or the operator of the loading or unloading point. In other words, if there is no designated arrival time and the waiting start time is earlier than the business start time, the waiting time may be the time from the business start time to the waiting end time. The business start time of each operator may be preset and stored in the server 3 or the storage device 11, or may be input by the operation manager by operating the input device 15, or may be input by the driver by operating the input device 43 and transmitted to the manager terminal 1 in step S805.
[0164] The calculation of the waiting time may further take into consideration the reception time at which the start of the waiting is received at the loading or unloading point. This reception time may be, for example, the time at which the driver enters necessary information such as the company name, driver name, and vehicle number in a list provided at the loading or unloading point, or the time at which similar information is registered by a terminal installed at the loading or unloading point. The calculation of the waiting time may further take into consideration the instruction time at which the driver is instructed to wait by a person in charge at the loading or unloading point. If the waiting start time is earlier than these times, the time from these times to the waiting end time can be considered as the waiting time.
[0165] The above-mentioned waiting start time is an example of the first time in this embodiment. The above-mentioned waiting end time is an example of the second time in this embodiment. The above-mentioned designated arrival time, business start time, reception time, or instruction time is an example of the third time in this embodiment. These first to third times can be times defined in various ways in addition to those disclosed in this embodiment. For example, the first and second times may be times directly inputted instead of the time when the driver operates the waiting button or other buttons. In addition, when the time when the waiting button or the like is operated includes a fraction in the unit of several minutes, the first and second times may be times rounded down or rounded up.
[0166] The waiting fee calculated in step S905 is, for example, the amount obtained by multiplying the waiting time calculated in step S904 by the amount per unit time predetermined for the shipper. However, the waiting fee is not limited to this example, and may be calculated using other calculation formulas.
[0167] 23 is a diagram showing an example of the data structure of the waiting information stored in step S906. For example, the waiting information includes a driver ID, a vehicle number, a shipper, a type of work, a designated arrival time, waiting time information, a waiting time, and a waiting fee. The waiting time information includes a waiting start time and a waiting end time. The waiting information may further include the business start time, the acceptance time, and the instruction time described above.
[0168] Note that there may be cases where multiple discontinuous waiting times occur at a loading or unloading point. Waiting start time 1 and waiting end time 1, and waiting start time 2 and waiting end time 2 shown in the lower part of Fig. 23, represent the start and end times of two discontinuous waiting times that occur at the same loading or unloading point. In this case, the waiting time recorded in the waiting information is the total time taking into account the two waiting start and end times.
[0169] For example, when the standby button is operated to confirm standby start time 1 and start the processing of the flowchart in Fig. 22, if the time from standby start time 1 to standby end time 1 is less than 30 minutes, the processing from step S802 onwards is not executed. In this case, when the processing of the flowchart in Fig. 22 is executed again by operating the standby button corresponding to standby start time 2, it is determined in step S801 whether the total time of the time from standby start time 1 to standby end time 1 and the time from standby start time 2 to the present has passed 30 minutes. Then, in step S805, standby start time 1, standby end time 1 and standby start time 2 are transmitted to the manager terminal 1, and in step S902 these times are displayed and corrections are accepted, and in steps S904 to S906, the standby time and standby fee are calculated, displayed and recorded using these times as well as the standby end time 2 received in step S903.
[0170] Also, even if the time from the standby start time 1 to the standby end time 1 exceeds 30 minutes and the standby information is recorded, when the process of the flowchart of FIG. 22 is executed again by operating the standby button corresponding to the standby start time 2, the total time from the standby start time 1 to the standby end time 1 and the time from the standby start time 2 to the present time can be used for comparison with 30 minutes in step S801. In this case, since the elapsed time has already exceeded 30 minutes, the subsequent process is executed even if the time from the standby start time 2 to the standby end time 2 is less than 30 minutes. The standby start time 1, the standby end time 1, the standby start time 2, and the standby end time 2 are used to calculate the standby time and the standby fee as in the above example, and the already recorded standby information is updated in step S906. Note that, in the above example, it is assumed that there are two discontinuous standby times, but the same process can be applied even if there are three or more discontinuous standby times.
[0171] Sometimes, cargo belonging to different shippers is transported to the same unloading point. In this case, the waiting time for each cargo must be recorded separately for each shipper. For example, when cargo belonging to shipper 1 and shipper 2 is unloaded at the same unloading point, according to the above-mentioned waiting processes A and B, if the waiting time for each of the cargo belonging to shippers 1 and 2 exceeds 30 minutes, the waiting information can be recorded for each of shippers 1 and 2.
[0172] However, in consideration of the case where there are two discontinuous waiting times for the cargo of shipper 1 or shipper 2, in order to calculate the waiting time more accurately, input of the shipper (step S802) may be requested regardless of whether 30 minutes have passed since the start of the waiting time. Similarly, input of the business type and the designated arrival time may be requested regardless of whether 30 minutes have passed since the start of the waiting time.
[0173] As an example, assume that there are two discontinuous waiting times 2 (waiting start time 2:waiting end time 2) and 3 (waiting start time 3:waiting end time 3) for unloading the cargo of the consignor 2 after waiting time 1 (waiting start time 1:waiting end time 1) for unloading the cargo of the consignor 1. In this case, the consignor input in the waiting process for waiting time 2 is different from the consignor input in the previous waiting process for waiting time 1. Therefore, in the waiting process for waiting time 2, the elapsed time from waiting start time 2 is compared with 30 minutes without considering waiting time 1. On the other hand, the consignor input in the waiting process for waiting time 3 is the same as the consignor input in the waiting process for waiting time 2. In this case, in the waiting process for waiting time 3, the time obtained by adding the elapsed time from waiting start time 3 to waiting time 2 is used for comparison with 30 minutes. Then, in the waiting process for waiting time 3, the waiting information of the consignor 2 including the waiting time considering both waiting times 2 and 3 is recorded. In this way, the waiting time can be recorded more accurately.
[0174] As another example, assuming a case where shipper 1 unloads its cargo while waiting for shipper 2 to unload its cargo, the waiting time for shipper 2 may be calculated starting from waiting start time 1. In this case, in the waiting process for waiting times 2 and 3, the elapsed time from waiting start time 1 is used for comparison with, for example, 30 minutes. If waiting time 1 does not exist because the vehicle unloads shipper 1's cargo immediately after arriving at the unloading point, another time, such as the arrival time of the vehicle at the unloading point, may be set as the starting point of waiting time 2.
[0175] In the flowchart of FIG. 22, a case where the driver ID, the standby start time, and the like are transmitted to the manager terminal 1 after 30 minutes have elapsed since the start of standby is illustrated. However, the driver ID and the standby start time may be transmitted to the manager terminal 1 at the start of standby. In this case, the manager terminal 1 may display a driver information list on the display 14 in which the status of the driver indicated by the driver ID is set to "on standby". Furthermore, when the elapsed time from the standby start time exceeds 30 minutes, the manager terminal 1 may accept input of the shipper, the type of work, the designated arrival time, and the like, and transmit the input information to the digital tachograph 2. The digital tachograph 2 displays the received information on the display 42, for example. In this case, the processes of steps S802 to S804 may be omitted, or instead of these processes, a process of accepting corrections to the information received from the manager terminal 1 may be added.
[0176] When a predetermined time (e.g., 1 hour, 2 hours) has elapsed since the start of standby, a warning may be issued to at least one of the operations manager and the driver, such as by displaying a message on the display 14, 42. In addition, the warning to the operations manager may be issued, for example, by coloring the line of the driver in the driver information list in a manner that makes it possible to distinguish it from other lines.
[0177] The standby information accumulated during daily operations can be displayed or printed in list form, for example, on the manager terminal 1, using the shipper or driver ID as a key. For example, if a list of standby times for specific shippers is created for each month, the workload required for processing standby fee claims can be significantly reduced. In addition, the standby information can be used to improve labor, such as by paving the way for reducing drivers' working hours.
[0178] The subject and the execution order of each process (steps S801 to S807, S901 to S906, etc.) disclosed in this embodiment can be changed as appropriate. When the labor management system includes a driver terminal 5 other than the digital tachograph 2 as shown in FIG. 18, at least a part of each process may be executed by the driver terminal 5. When the labor management system includes a plurality of business terminals 6 as shown in FIG. 19, at least a part of each process may be executed by the business terminal 6. As described above in the second embodiment, the labor management system may not include the digital tachograph 2. All or a part of the processes executed by the manager terminal 1 in this embodiment may be executed by the digital tachograph 2 or the driver terminal 5. All or a part of the processes executed by the digital tachograph 2 in this embodiment may be executed by the manager terminal 1 or the business terminal 6.
[0179] [Sixth embodiment] In the sixth embodiment, a work status management system capable of more appropriately managing the arrival time of a driver is disclosed. Here, it is assumed that the work management system has the same configuration as the first embodiment, but the work management system may have the same configuration as the other embodiments.
[0180] 24 is a flowchart showing an example of a return process A executed by the digital tachograph 2 and a return process B executed by the manager terminal 1. The return process A is started when a return event occurs, for example, by operating the return button or the lodging button of the input device 43.
[0181] First, the controller 20 of the digital tachograph 2 judges whether the current working day is a working day other than the last day of the overnight operation, in other words, whether the next workday is a workday that does not stop at the business premises (step S1001). For example, when the return process A is executed with the operation of the return button as a trigger, the controller 20 judges that the current working day is a working day other than the last day of the overnight operation. On the other hand, when the return process A is executed with the operation of the return button as a trigger, the controller 20 judges that the current working day is not a working day other than the last day of the overnight operation. The judgment method of step S1001 is not limited to this, and it may be judged whether the current working day is a working day other than the last day of the overnight operation, for example, based on the operation result of the button displayed on the display 42.
[0182] If the current work day is a work day other than the last day of the overnight operation (YES in step S1001), the controller 20 records the driver's return time (end time of operation) (step S1002). This return time corresponds to the time when the driver leaves work on that work day, and may be, for example, the time when return process A is started, or may be the time input by the driver through the input device 43. The return time may be recorded by saving it in the storage device 21, or by writing it in the labor management database 30 of the server 3.
[0183] Next, the controller 20 calculates the next possible time to come to work (leave the depot) (step S1003), and notifies the driver of the next possible time to come to work, for example, by displaying the time on the display 42 or outputting the time by voice from the speaker 23 (step S1004). The next possible time to come to work is the earliest time at which the driver can come to work on the work day following the current work day while still complying with the labor standards, and can be, for example, the time when the minimum value of the rest period has elapsed since the driver's return time to the depot (leave work time).
[0184] Furthermore, the controller 20 displays an input field on the display 42, for example, to accept input of the scheduled start time for the next work day (step S1005). The driver can input the scheduled start time using the input device 43, for example, with reference to the next available start time notified in step S1004. Thereafter, the controller 20 transmits the next available start time calculated in step S1003, the scheduled start time input in step S1005, the driver ID, etc., to the manager terminal 1 via the network N (step S1006).
[0185] If the current work day is not a work day other than the last day of the overnight operation (NO in step S1001), the controller 20 records the driver's return time to the depot as in step S1002 (step S1007). In this case, the driver will later clock out at the office, and the clock out time will be determined at that time. In other words, the return time recorded in step S1007 is different from the clock out time.
[0186] After step S1006 or step S1007, the returning process A ends. In the return process B, the controller 10 of the manager terminal 1 receives the scheduled start time and other information transmitted from the digital tachograph 2 in step S1006 (step S1101). The controller 10 displays the received scheduled start time, next available start time, driver ID, and other information on the display 14 (step S1102). Furthermore, the controller 10 accepts corrections to the scheduled start time (step S1103). The operations manager can correct the scheduled start time by operating the input device 15, for example.
[0187] The operation manager checks the displayed scheduled start time, the next available time to start work, the driver's driver information, the driver's operation schedule for the next day, etc., and if the scheduled start time to start work is inappropriate, informs the driver via a communication means such as a telephone that the scheduled start time should be changed. Examples of cases in which the scheduled start time to start work is inappropriate include when the scheduled start time to start work is earlier than the next available time to start work, or when the scheduled start time to start work is too early compared to the start time of the first task on the next day. Note that in step S1005, it may be possible to prevent the driver from inputting a scheduled start time that is earlier than the next available time to start work, or to issue a warning when such a scheduled start time is input.
[0188] If there is no problem with the scheduled start time or if the correction of the scheduled start time is completed, the operations manager confirms the scheduled start time, for example, by operating the input device 15. At this time, the controller 10 records the scheduled start time, for example, in the labor management database 30 (step S1104). This ends the return process B.
[0189] As in this embodiment, if the operations manager is able to check the scheduled arrival time of the driver during overnight trips, the working conditions of drivers in remote locations can be more appropriately managed.
[0190] In addition, on the last day of overnight operation or on normal operation without overnight stays, the calculation and display of the next available time to work and the input and display of the scheduled time to work may be executed as in the present embodiment. In this case, the calculation and display of the next available time to work may be executed by the manager terminal 1 or may be executed by a device for clocking in and out. Furthermore, calculation and display of the next available time to start work and input and display of the scheduled time to start work may be performed in the above-mentioned roll call processes A to C.
[0191] Also, the configuration may be such that the operations manager inputs the planned arrival time to the manager terminal 1 by the input device 15 or the like. In this case, the input planned arrival time may be transmitted to the digital tachograph 2 and notified to the driver by displaying it on the display 42 or the like. In this way, the function in which the operations manager inputs the planned arrival time and the function in which the driver inputs the planned arrival time as in the above-mentioned return-to-depot processes A and B may be switchable by settings.
[0192] It may be possible to prevent the driver from coming to work earlier than the scheduled attendance time recorded in step S1104. For example, if the attendance time determined in the attendance process for the next day's attendance (next day's departure from the depot) is earlier than the scheduled attendance time, a message to the effect that attendance is not possible is displayed on display 14 in the case of attendance process at the business office, or on display 42 in the case of attendance process by vehicle (depot departure process), and the attendance process ends without confirming the attendance time. As another example, it may be possible to prohibit coming to work earlier than the scheduled attendance time by a predetermined amount (for example, one hour) or more.
[0193] The subject of each process (steps S1001 to S1007, S1101 to S1104, etc.) disclosed in this embodiment can be changed as appropriate. When the labor management system includes a driver terminal 5 separate from the digital tachograph 2 as shown in FIG. 18, at least a part of each process may be performed by the driver terminal 5. When the labor management system includes a plurality of business terminals 6 as shown in FIG. 19, at least a part of each process may be performed by the business terminal 6. All or a part of the processes that are to be executed by the manager terminal 1 in this embodiment may be executed by the digital tachograph 2 or the driver terminal 5. All or a part of the processes that are to be executed by the digital tachograph 2 in this embodiment may be executed by the manager terminal 1 or the business terminal 6.
[0194] In addition to the configurations disclosed in the first to sixth embodiments, the labor management system can be realized in various forms. That is, the execution entity of each process disclosed in each embodiment may be any of the manager terminal 1, the digital tachograph 2, the driver terminal 5, and the business terminal 6. In addition, at least a part of these processes may be executed by the server 3.
[0195] Furthermore, the functions of the server 3 may be integrated into the manager terminal 1. In this case, the labor management database 30 and the address table 31 can be stored in the storage device 11 or another storage device connected to the manager terminal 1.
[0196] At least a part of the data exchanged between the administrator terminal 1 and the digital tachograph 2 or the driver terminal 5 may be performed via a storage medium such as a memory card.
[0197] 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.
[0198] 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. A process shown in one flowchart in each embodiment may be realized by one computer program, or may be realized by multiple computer programs. In addition, a computer that executes such a computer program may be not only the administrator terminal 1, the digital tachograph 2, the server 3, the driver terminal 5, or the business terminal 6 disclosed in each embodiment, but also other devices.
[0199] 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]
[0200] 1...Administrator terminal, 2...Digital tachograph (driver terminal), 3...Server, 10, 20...Controller, 17, 45...Alcohol detector, 30...Labor management database, 31...Address table, 200...Holiday setting screen, 300...Accommodation confirmation screen, 400...Roll call schedule confirmation screen, 500...Schedule change screen, 600...Roll call schedule notification screen, 700...Completion waiting screen, 800...Completion screen.
Claims
1. A database that stores the driver's work history including the driver's daily arrival and departure times; a determination means for determining that the driver's total working hours for the current month may exceed the driver's upper limit of working hours for the current month when a first average working time obtained by dividing an actual working time result, which is the total working hours of the driver for the current month specified from the work history stored in the database, by the number of days the driver has actually attended work for the current month, is greater than a second average working time obtained by subtracting the actual working time result from the driver's upper limit of working hours for the current month, by dividing the value obtained by subtracting the number of days the driver has actually attended work for the current month from the number of days the driver is scheduled to attend work for the current month; an output means for outputting a result of the determination by the determination means; A labor management system equipped with
2. When the first average binding time is longer than the second average binding time, the output means issues one of a first warning and a second warning different from the first warning, depending on a difference between the first average binding time and the second average binding time. The labor management system according to claim 1.
3. The first warning includes at least one of displaying a message indicating that the first average on-duty time exceeds the second average on-duty time, displaying a message indicating that the on-duty time for the current month will exceed an upper limit if the current situation continues, displaying a message indicating that the on-duty time needs to be reduced for the remaining working days of the current month, coloring information about the driver in a driver information list including the working states of multiple drivers, and assigning an identifier to information about the driver in the driver information list. The labor management system according to claim 2.
4. The second warning includes at least one of displaying a message to the effect that an additional day off should be taken in the current month, coloring information on the driver in a driver information list including the working statuses of multiple drivers, and assigning an identifier to information on the driver in the driver information list. The labor management system according to claim 2 or 3.
5. Computer, a determination means for determining that the driver's total working hours for the current month may exceed the driver's upper limit of working hours for the current month when a first average working time obtained by dividing the actual working time result, which is the total working hours of the driver for the current month specified from the work history including the driver's daily arrival and departure times stored in a database, by the number of days the driver has actually attended work for the current month, is greater than a second average working time obtained by subtracting the actual working time result from the driver's upper limit of working hours for the current month, by dividing the value obtained by subtracting the number of days the driver has actually attended work for the current month from the number of days the driver is scheduled to attend work for the current month; an output means for outputting a result of the determination by the determination means; A computer program that functions as a
6. When the first average binding time is longer than the second average binding time, the output means issues one of a first warning and a second warning different from the first warning, depending on a difference between the first average binding time and the second average binding time.
6. A computer program according to claim 5.
7. The first warning includes at least one of displaying a message indicating that the first average on-duty time exceeds the second average on-duty time, displaying a message indicating that the on-duty time for the current month will exceed an upper limit if the current situation continues, displaying a message indicating that the on-duty time needs to be reduced for the remaining working days of the current month, coloring information about the driver in a driver information list including the working states of multiple drivers, and assigning an identifier to information about the driver in the driver information list.
7. A computer program according to claim 6.
8. The second warning includes at least one of displaying a message to the effect that an additional day off should be taken in the current month, coloring information on the driver in a driver information list including the working statuses of multiple drivers, and assigning an identifier to information on the driver in the driver information list. A computer program according to claim 6 or 7.
Citation Information
Patent Citations
Entry / departure managing apparatus
JP1988008891A
Time managing device
JP1991041591A
Labor state management device and labor state management system
JP2015127960A
