Labor management systems and computer programs

Abstract

To improve the operational management system of transportation companies. [Solution] A labor management system according to one embodiment includes a master containing records that associate location data with location names, location identification means for identifying the location of a vehicle, work identification means for identifying the type of work performed at the identified location, recording means for recording work information including location data corresponding to the identified location and the type of work identified by the work identification means, and update means for registering a record that associates the location data with the location name of the location indicated by the location data in the master if a record corresponding to the location data of the work information is not registered in the master. Each of the means is realized by the administrator terminal, the driver terminal, and the server, or by the cooperation of the administrator terminal, the driver terminal, and the server.

Description

Technical Field

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

Background Art

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

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

[0004] As the labor management of drivers becomes stricter in this way, the labor required by the managers of transportation companies for labor management may increase. Also, on the shipper side, it is necessary to accurately grasp the actual situation such as the waiting time of drivers entering and leaving their company for loading and unloading.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of the Invention

Problems 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 capable of improving the business management system in the transportation industry. Other objects of the present invention are derived from this specification and the attached drawings. [Means for solving the problem]

[0007] A labor management system according to one embodiment includes an administrator terminal, a driver terminal, and a server that can communicate with each other. Furthermore, the labor management system includes location data and a location name, The type of work to be performed at the facility indicated by the location name and A master containing multiple records associated with each other, and a location identification means for identifying the location of the vehicle, The plurality of records in the master The position identified by the position identification means If there is a record containing location data corresponding to that location, the work type of that record will be set to that location Types of work performed in as identification If no record containing the location data exists, the type of work to be performed at that location is identified based on input from the driver or administrator. A means for identifying work, a recording means for recording work information including location data corresponding to the location identified by the location identification means and the type of work identified by the work identification means, The record corresponding to the location data of the work information recorded by the recording means is If none of the multiple records in the master contain a record corresponding to the location data of the work information, then the location data and 、 The name of the location indicated by the location data and , the type of work entered by the driver or the manager and The system includes an update means for registering a record associated with the master. Each of the location identification means, the work identification means, the recording means, and the update means is implemented by any of the administrator terminal, the driver terminal, and the server, or by the cooperation of the administrator terminal, the driver terminal, and the server.

[0008] A computer program according to one embodiment includes a computer, a location-finding means for determining the location of a vehicle, The master contains multiple records that associate location data, a place name, and the type of work to be performed at the facility indicated by that place name. The position identified by the position identification means If there is a record containing location data corresponding to that location, the work type of that record will be set to that location Types of work performed in as identification If no record containing the location data exists, the type of work to be performed at that location is identified based on input from the driver or administrator. A recording means for recording work information including work identification means, location data corresponding to the location identified by the location identification means, and work type identified by the work identification means, The record corresponding to the location data of the work information recorded by the recording means is Multiple records in the master Nina If not, the location data and the name of the location indicated by the location data , the type of work entered by the driver or the manager and It functions as an update means for registering records associated with the master. [Effects of the Invention]

[0009] According to the present invention, it becomes possible to improve the business management system of a carrier. Other effects of the present invention are derived from this specification and the accompanying drawings.

Brief Description of the Drawings

[0010] [Figure 1] FIG. 1 is a block diagram showing a configuration example of a labor management system according to the first embodiment. [Figure 2] FIG. 2 is a diagram showing an example of the data structure of records constituting a location information master. [Figure 3] FIG. 3 is a diagram showing an example of the data structure of records constituting a work information table. [Figure 4] FIG. 4 is a flowchart showing an example of processing executed when a vehicle stops. [Figure 5] FIG. 5 is a diagram showing an example of an input method for work types. [Figure 6] FIG. 6 is a flowchart showing an example of work record processing A. [Figure 7] FIG. 7 is a flowchart showing an example of work record processing B. [Figure 8] FIG. 8 is a flowchart showing an example of work record processing C. [Figure 9] FIG. 9 is a flowchart showing an example of master update processing. [Figure 10] FIG. 10 is a diagram showing an example of a registration screen. [Figure 11] FIG. 11 is a flowchart showing an example of work start determination processing according to the second embodiment. [Figure 12] FIG. 12 is a flowchart showing an example of work end determination processing according to the second embodiment. [Figure 13] FIG. 13 is a block diagram showing a configuration example of a vehicle management system according to the third embodiment. [Figure 14] FIG. 14 is a diagram showing an example of the data structure of records constituting a facility information master. [Figure 15] FIG. 15 is a diagram showing an example of the data structure of records constituting a carrier mass. [Figure 16] FIG. 16 is a diagram showing an example of the data structure of records constituting a work information table. [Figure 17] FIG. 17 is a flowchart showing a series of processes for generating records of a work information table. [Figure 18] FIG. 18 is a diagram showing an example of an application screen displayed on a driver terminal display. [Figure 19] FIG. 19 is a diagram showing an example of a management screen displayed on a facility terminal. [Figure 20] FIG. 20 is a diagram showing an example of an analysis result screen on which analysis results by an analysis function are displayed.

BEST MODE FOR CARRYING OUT THE INVENTION

[0011] Some embodiments will be described with reference to the drawings. In each of the embodiments described below, a labor management system and a computer program for managing the labor of truck drivers are disclosed. <000​​​​​​​​​​​​The administrator terminal 1 includes a controller 10 containing a processor and memory, a storage device 11, a display 12, an input device 13, a speaker 14, and an interface 15 for external connections. The controller 10 can perform various processes disclosed in this embodiment by having the processor execute a computer program stored in memory.

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

[0016] Interface 15 is connected to a communication device 16, which can communicate with network N, via wired or wireless connection. Interface 15 may also be connected to an attendance terminal 17, which allows drivers to complete attendance and departure procedures at the workplace.

[0017] The driver terminal 2 can be a portable device such as a smartphone or tablet. The driver terminal 2 may also be a device permanently mounted on the vehicle.

[0018] The driver terminal 2 includes a controller 20 containing a processor and memory, a storage device 21, a communication device 22, a display 23, an input device 24, a speaker 25, and a GPS (Global Positioning System) receiver 26. The controller 20 can perform various processes disclosed in this embodiment by having the processor execute a computer program stored in memory.

[0019] The communication device 22 is capable of wireless communication with network N. The communication device 22 may also be capable of direct communication with the digital tachograph 3 using short-range wireless communication or the like. The input device 24 includes a touch panel and buttons for operating the GUI displayed on the display 23. The GPS receiver 26 receives GPS signals from satellites and detects the position of the driver terminal 2 based on those signals.

[0020] The digital tachograph 3 is mounted on the vehicle. The digital tachograph 3 is connected to a communication device 41 capable of communicating with the network N, a display 42, an input device 43, a driving sensor 44, and a GPS receiver 45 via wired or wireless communication. These elements connected to the digital tachograph 3 may be located on the vehicle's console or elsewhere, or they may be part of the digital tachograph 3.

[0021] The input device 43 includes buttons and a touch panel for operating the GUI displayed on the display 42. The input device 43 may also include various buttons for inputting the type of work performed by the driver, such as departure, return to depot, loading, unloading, rest, waiting, overnight stay, refueling, and boarding, as well as the status of the vehicle. The driving sensor 44 detects parameters related to driving, such as the vehicle's speed, acceleration, engine speed, and engine temperature. The GPS receiver 45 receives GPS signals from satellites and detects the vehicle's position based on these signals.

[0022] Although Figure 1 shows only one vehicle, a transportation company may have multiple drivers and multiple vehicles. The labor management system according to this embodiment includes elements such as driver terminals 2 for these multiple drivers and digital tachographs 3 installed in multiple vehicles.

[0023] Server 5 is connected to network N. Server 5 may be located outside the business premises or located within the business premises. Server 5 may also be a server included in a cloud system. In this case, cloud computing in the form of SaaS (Software as a Service) can be used for processing performed by elements of the labor management system such as administrator terminal 1, driver terminal 2, and digital tachograph 3.

[0024] Server 5 stores the management database 50. In this embodiment, the management database 50 includes, as a key element, a location information master 51 and a work information table 52. In addition, the management database 50 may include various other information necessary for labor management and business management, such as the work history of multiple drivers and information regarding each driver's work schedule.

[0025] Administrator terminal 1 can retrieve information from the management database 50 of server 5 and save information to the management database 50 via communication via communication device 16 and network N. Driver terminal 2 can perform similar processing via communication via communication device 22 and network N. In addition, administrator terminal 1, driver terminal 2, and digital tachograph 3 can exchange information with each other via communication devices 16, 22, 41 and network N.

[0026] The digital tachograph 3 records operational information in its internal memory, including the vehicle's start time, end time, the so-called three legally mandated elements (instantaneous vehicle speed, distance traveled, and travel time) at each time point from the start to the end of operation, the type of work performed at each time point (waiting, rest, loading, unloading, refueling, boarding, etc.), and vehicle location data (address), based on parameters such as speed detected by the driving sensor 44, input from the input device 43, signals received by the GPS receiver 45, and information input by the driver terminal 2. Furthermore, the digital tachograph 3 transmits the operational information to the server 5. The server 5 stores the operational information in the management database 50. The administrator terminal 1 and driver terminal 2 can obtain the operational information by accessing the management database 50 and use it for display on the displays 12 and 23 or for other processing. Operational information may also be transmitted directly from the digital tachograph 3 to the administrator terminal 1 and driver terminal 2.

[0027] In a labor management system configured as described above, the administrator terminal 1, driver terminal 2, digital tachograph 3, and server 5 communicate via network N, allowing both the workplace and the vehicles to monitor the driver's work status and the vehicle's driving status in real time.

[0028] For example, the administrator terminal 1 displays a list of driver information on the display 12, showing the working status of each driver belonging to the business site and the driving status of the vehicles, based on information from the management database 50 and other sources. This allows the administrator to easily grasp the working status of each driver and the driving status of the vehicles, and to issue necessary instructions to drivers in remote locations.

[0029] Figure 2 shows an example of the data structure of record R1 that constitutes the location information master 51. Each record R1 of the location information master 51 includes location data, location name, work type, consignor name, set time information, and reservation system flag.

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

[0031] For example, the location name in record R1 is identification information such as a string or code that indicates a specific facility (company name, customer name, store name, etc.) such as a loading point, unloading point, gas station (GS), convenience store, parking area (PA), the transportation company's office, or ferry terminal.

[0032] The work type in record R1 represents the work that the driver should perform at the facility indicated by the location name. Examples of such work types include rest, loading, unloading, refueling, and boarding.

[0033] The shipper name, scheduled time information, and reservation system flag for record R1 are set when the work type is loading or unloading. The shipper name is identification information such as a string or code that indicates the name of the shipper. The shipper recorded as the shipper name may include the consignee at the destination of the goods and the originating shipper at the loading location. The scheduled time information includes the facility's break time, opening time, closing time, and standard working time required for the work that the driver should perform at the facility (the work indicated by the work type). The reservation system flag indicates whether the facility indicated by the location has implemented a loading / unloading reservation system. For example, the reservation system flag is "0" if a reservation system is not implemented and "1" if one has implemented it.

[0034] Figure 3 shows an example of the data structure of record R2 that constitutes the work information table 52. Each record R2 in the work information table 52 includes work date and time, driver ID, location data, location name, work type, work time information, and registration flag.

[0035] The work date and time in record R2 is information indicating the date and time when the work was performed. The work date and time can be, for example, the start or end date and time of the work, but it may also be just the date the work was performed. The driver ID is identification information of the driver who performed the work. Vehicle identification information may be recorded along with the driver ID.

[0036] The location data of record R2 is information indicating the location on a map where the work was performed. This location data, as in the case of location information master 51, may be a string representing an address, for example, or it may be coordinates corresponding to a positioning system such as GPS.

[0037] The location name in record R2 is identification information such as a string or code that indicates the facility where the work was performed. As with location information master 51, this facility could be a loading point, unloading point, gas station, convenience store, parking area, the transportation company's office, ferry terminal, etc.

[0038] The work type in record R2 represents the work that was performed. Possible work types include, for example, rest, loading, unloading, refueling, boarding, and waiting.

[0039] The work time information in record R2 includes, for example, the first time the vehicle began its stay at the facility indicated by the location name, the second time the vehicle ended its stay at the facility, and the actual work time at the facility. For example, if the work type is rest, the actual work time corresponds to the rest time. Similarly, if the work type is loading, the actual work time corresponds to the loading time, and if the work type is unloading, the actual work time corresponds to the unloading time. If the work type is standby, the standby time is recorded instead of the actual work time. Furthermore, if the work type is loading or unloading and standby occurs before these operations are performed, the standby time is recorded in addition to the actual work time.

[0040] The registration flag for record R2 indicates whether or not record R1, which corresponds to the location data of record R2, is registered in the location information master 51. For example, the registration flag is "0" if record R1 containing the same location data as record R2 is registered in the location information master 51, and "1" if it is not registered.

[0041] Furthermore, the data structures of record R1 in the location information master 51 and record R2 in the work information table 52 are not limited to those shown in Figures 2 and 3. Records R1 and R2 can be changed to various forms as long as they can realize at least a part of the various processes disclosed in this embodiment.

[0042] The labor management system according to this embodiment executes the process shown in the flowchart of Figure 4 in response to a vehicle stopping. The process (steps) shown in the flowchart may be realized through the cooperation of the controller 10 of the administrator terminal 1, the controller 20 of the driver terminal 2, and the server 5, etc., or it may be realized by any one of them individually.

[0043] The vehicle stopping that triggers the process shown in the flowchart of Figure 4 is, for example, when the vehicle's engine is stopped, when the vehicle speed detected by the driving sensor 44 is 0 km / s for a certain period of time, or when the vehicle's position, as determined by the signals received by the GPS receivers 26 and 45, does not change for a certain period of time. In addition to these, various other methods, such as the operation of a specific button, can be used as triggers to start the process shown in the flowchart.

[0044] At the start of processing in the flowchart of Figure 4, it is first determined whether the driver has entered the type of work (rest, break, loading, unloading, refueling, boarding, waiting, etc.) (step S101). The driver can enter the type of work, for example, using the driver terminal 2.

[0045] Figure 5 shows an example of how to input the type of work. The driver terminal 2's display 23 shows the illustrated work input screen 60. The work input screen 60 includes a rest button 61 for inputting a rest, a loading button 62 for inputting loading, an unloading button 63 for inputting unloading, a refueling button 64 for inputting refueling, a boarding button 65 for inputting boarding a ferry, a PA button 66 for inputting a rest at a parking area, a waiting button 67 for inputting waiting, etc.

[0046] The driver can input the type of work they are about to perform by operating the buttons on the work input screen 60. Alternatively, the driver may input the type of work by operating the vehicle's input device 43.

[0047] In the flowchart of Figure 4, if the type of work is not entered (NO in step S101), it is determined whether a predetermined time T1 has elapsed since the vehicle stopped (step S102). For example, the predetermined time T1 can be set as appropriate by the transport company, such as 1 minute, 5 minutes, or 10 minutes.

[0048] If the predetermined time T1 has not elapsed (NO in step S102), the process returns to step S101. When the predetermined time T1 has elapsed (YES in step S102), work record processing A is executed.

[0049] On the other hand, if the work type is entered before the predetermined time T1 in step S102 has elapsed (YES in step S101), the driver's priority setting is determined (step S103). The priority setting indicates the priority order for recording the vehicle's stopping time as a work type registered in the location information master 51 or as a work type entered by the driver via the work input screen 60, etc. Hereinafter, the setting that prioritizes the work type registered in the location information master 51 will be called "registered priority," and the setting that prioritizes the work type entered by the driver will be called "input priority." Such priority settings can be switched, for example, by the administrator terminal 1. The priority setting may be set collectively for all drivers belonging to the business office, or it may be set for each driver.

[0050] If the priority setting is registration priority (registration priority in step S103), work record processing B is executed. On the other hand, if the priority setting is input priority (input priority in step S103), work record processing C is executed.

[0051] Figure 6 is a flowchart showing an example of work record processing A. The processing (steps) shown in this flowchart may be implemented through the cooperation of the controller 10 of the administrator terminal 1, the controller 20 of the driver terminal 2, and the server 5, etc., or it may be implemented by any one of them individually.

[0052] In work record processing A, the vehicle's stopping position is first identified (step S201). For example, the stopping position is the vehicle's current position and can be identified based on the signal received by the GPS receiver 26. The vehicle's current position may also be identified based on the signal received by the GPS receiver 45.

[0053] Next, record R1 corresponding to the stopping position identified in step S201 is retrieved from the location information master 51 (step S202). In step S202, record R1 containing location data corresponding to the stopping position identified in step S201 is extracted from the location information master 51. At this time, record R1 containing the location data may be extracted not only when the stopping position identified in step S201 and the position indicated by the location data are exactly the same, but also when the two can be considered substantially identical. Here, substantially identical may include cases where the stopping position identified in step S201 is located within a predetermined radius (for example, within several tens of meters) of the position indicated by the location data of record R1.

[0054] After step S202, it is determined whether the stopping position is registered in the location information master 51, that is, whether or not a record R1 containing location data corresponding to the stopping position has been extracted (step S203).

[0055] If record R1 is extracted (YES in step S203), the first time is obtained (step S204). For example, the first time is the stopping time of the vehicle that triggered the process shown in the flowchart of Figure 5. As another example, the first time may be the time after a predetermined time T1 in step S102 has elapsed from the vehicle's stopping time. As yet another example, the first time may be a time input by input devices 13, 24, 43, etc.

[0056] After step S204, the work type of the extracted record R1 is recorded in the management database 50, etc., as the driver's current work status (step S205). This work status is maintained until the end of the work.

[0057] After step S205, it is determined whether the work at the stopping position has been completed (step S206). For example, if the vehicle is released from its stopped state, it is determined that the work has been completed (YES in step S206). The stopped state is released, for example, when the vehicle's engine is started, when the vehicle speed detected by the driving sensor 44 is no longer 0 km / s, or when the vehicle's position, as determined by the signal received by the GPS receiver 26 or GPS receiver 45, changes. As another example, in step S206, it may be determined that the waiting has ended in response to the operation of the input devices 24 and 43.

[0058] Furthermore, the vehicle may move a short distance within the premises of the facility where the work is to be performed between tasks. Therefore, in step S205, the work may be determined to be completed only if the vehicle remains stationary for a certain period of time or longer.

[0059] If it is determined that the work is completed (YES in step S206), a second time is obtained (step S207). The second time is, for example, the time when the vehicle's stopped state is released, i.e., the current time, and can be obtained from the system clock of the driver terminal 2, etc. Alternatively, the second time may be a time entered by operating the input devices 24, 43, etc. Also, the second time may be the time after a predetermined time has elapsed since the vehicle's stopped state was released.

[0060] After step S207, the actual work time is calculated (step S208). If the work involves loading or unloading and there is a waiting period, that waiting time is also calculated in step S208. Details on how to calculate the actual work time and other information in step S208 will be described later.

[0061] After step S208, record R2 for the work is recorded in the work information table 52 (step S209). Record R2 includes the work date and time, driver ID, location data, location name, work type, work time information, and registration flag, as shown in Figure 3.

[0062] The date and time of the operation recorded in record R2 in step S209 may be, for example, the date and time of execution in step S208. Alternatively, the date and time of the operation may be the first time obtained in step S204 or the second time obtained in step S207.

[0063] The driver ID in record R2 is, for example, the driver ID of the driver logged into the labor management system on driver terminal 2. Furthermore, the location data, location name, and work type in record R2 may be, for example, the location data, location name, and work type recorded in record R1 extracted from the location information master 51 in step S202. However, the location data may also be the one identified in step S201.

[0064] The first and second timestamps included in the work time information of record R2 are the first and second timestamps obtained in steps S204 and S207, respectively. Furthermore, the actual work time and waiting time in the work time information are the actual work time and waiting time calculated in step S208. In record R2, the registration flag is set to "0" (already registered).

[0065] On the other hand, if record R1 is not extracted in step S202 (NO in step S203), the driver's input of the work type is accepted (step S210). This input is accepted, for example, by displaying a message prompting the driver to input the work type on the driver terminal 2's display 23, along with the work input screen 60 shown in Figure 5. The input of the work type may also be performed by the administrator. In this case, for example, the work type input screen is displayed on the administrator terminal 1's display 12.

[0066] When the type of work is entered through button operations on the work input screen 60, the first time is acquired, as in step S204 (step S211). Furthermore, the entered type of work is recorded in the management database 50, etc., as the driver's current working status (step S212). This working status is maintained until the completion of the work.

[0067] After step S212, it is determined whether the work has been completed, as in step S206 (step S213). If the work has been completed (YES in step S213), the second time is obtained, as in step S207 (step S214). Furthermore, the actual work time and other details are calculated (step S215). Details of the calculation method for the actual work time and other details in step S215 will be described later.

[0068] After step S215, record R2 of the work is recorded in the work information table 52 (step S216). The work date and time of record R2 may be, for example, the date and time when step S216 is executed. Alternatively, the work date and time may be the first time obtained in step S211 or the second time obtained in step S214. The driver ID of record R2 is, for example, the driver ID of the driver logged into the labor management system on driver terminal 2.

[0069] The location data for record R2 indicates the vehicle location identified in step S201. The work type for record R2 is the work type entered in step S210.

[0070] The first and second timestamps in the work time information for record R2 are the first and second timestamps obtained in steps S211 and S214, respectively. The actual work time and waiting time in the work time information are the actual work time and waiting time calculated in step S215. In record R2, the registration flag is set to "1" (not registered). Note that no location name is set in record R2.

[0071] As described above, after record R2 is recorded in the work information table 52 in step S209 or step S216, work record processing A is completed.

[0072] Figure 7 is a flowchart showing an example of work record processing B. The processing (steps) shown in this flowchart may be implemented through the cooperation of the controller 10 of the administrator terminal 1, the controller 20 of the driver terminal 2, and the server 5, etc., or it may be implemented by any one of them individually.

[0073] Work record processing B includes steps S301 to S309, which are the same as steps S201 to S209 of work record processing A. Furthermore, work record processing B includes steps S310 to S315, which are the same as steps S211 to S216 of work record processing A. Note that since work record processing B is executed when the type of work has already been entered in step S101, it does not include the processing corresponding to step S210.

[0074] Work record processing B is executed when registration takes priority. Therefore, if record R1 corresponding to the stopping position identified in step S301 is registered in the location information master 51 (YES in step S303), the work type of record R1 is recorded as the driver's current working status (step S305). Furthermore, record R2, which includes the work type of record R1, is recorded in the work information table 52 (step S309).

[0075] On the other hand, if record R1 corresponding to the stopping position identified in step S301 is not registered in the location information master 51 (NO in step S303), the work type entered in step S101 is recorded as the driver's current working status (step S311). Furthermore, record R2, which includes the work type, is recorded in the work information table 52 (step S315).

[0076] Figure 8 is a flowchart showing an example of work record processing C. The processing (steps) shown in this flowchart may be implemented through the cooperation of the controller 10 of the administrator terminal 1, the controller 20 of the driver terminal 2, and the server 5, etc., or it may be implemented by any one of them individually.

[0077] In work record processing C, first, the vehicle's stopping position is identified, similar to step S201 (step S401). Then, the first time is acquired, similar to step S204 (step S402). Subsequently, the work type entered in step S101 is recorded in the management database 50, etc., as the driver's current working status (step S403). This working status is maintained until the completion of the work.

[0078] After step S403, it is determined whether the work at the stopping position is completed, as in step S206 (step S404). If the work is completed (YES in step S404), the second time is acquired, as in step S207 (step S405).

[0079] Next, record R1 corresponding to the stopping position identified in step S401 is retrieved from the location information master 51 (step S406). The details of this search are the same as in step S202. After step S406, it is determined whether or not the stopping position is registered in the location information master 51, that is, whether or not record R1 containing location data corresponding to the stopping position has been extracted (step S407).

[0080] If record R1 is extracted (YES in step S407), the actual work time and other information are calculated as in step S208 (step S408), and record R2, with the registration flag set to "0" (already registered), is recorded in the work information table 52 (step S409).

[0081] On the other hand, if record R1 is not extracted (NO in step S407), the actual work time and other information are calculated as in step S215 (step S410), and record R2 with the registration flag set to "1" (not registered) is recorded in the work information table 52 (step S411).

[0082] The date and time of the operation in record R2 recorded in steps S409 and S411 may be, for example, the date and time when steps S409 and S411 are executed. Alternatively, the date and time of the operation may be the first time obtained in step S402 or the second time obtained in step S405.

[0083] The driver ID in record R2 recorded in steps S409 and S411 is, for example, the driver ID of the driver logged into the labor management system on driver terminal 2. Furthermore, the work type in these records R2 is the work type entered in step S101.

[0084] The location data and location name of record R2 recorded in step S409 may be, for example, the location data and location name recorded in record R1 extracted from the location information master 51 in step S406. However, the location data may also be the one identified in step S401.

[0085] The location data of record R2 recorded in step S411 indicates the vehicle location identified in step S401. Note that no location name is set in record R2.

[0086] The first and second timestamps of the work time information in record R2, recorded in steps S409 and S411, are the first and second timestamps obtained in steps S402 and S405, respectively.

[0087] The actual work time and waiting time in the work time information for record R2 recorded in step S409 are the actual work time and waiting time calculated in step S408. Similarly, the actual work time and waiting time in the work time information for record R2 recorded in step S411 are the actual work time and waiting time calculated in step S410. The work record processing C ends with step S409 or step S411.

[0088] Here, we will explain how to calculate the actual work time, etc., in each of the following steps: S208, S308, S408 (when registered in the location information master 51) and S215, S314, S410 (when not registered in the location information master 51). (1) Calculation method in steps S208, S308, and S408 If the type of work to be recorded is rest, refueling, or boarding, the elapsed time from the first time point to the second time point is calculated as the actual work time (rest time, refueling time, or boarding time). On the other hand, if the type of work to be recorded is loading or unloading, the actual work time (loading time, unloading time) and waiting time are calculated using the facility break time, business start time, business end time, and standard work time of record R1 extracted in steps S202, S302, and S406, in addition to the first and second time. For example, if the standard working time is less than or equal to the elapsed time from the first time point to the second time point, the standard working time becomes the actual working time for loading or unloading. On the other hand, if the standard working time is longer than the elapsed time from the first time point to the second time point, that elapsed time becomes the actual working time for loading or unloading, and the waiting time becomes 0. For example, waiting time is the time from the first time slot to the second time slot minus time that overlaps with facility break time, time before the start of business hours, time after the end of business hours, and standard working hours. However, it is not necessary to use any of these times for deduction. Furthermore, other types of time may be deducted from the time from the first time slot to the second time slot.

[0089] If the type of work to be recorded is loading or unloading, and the reservation system flag of record R1 extracted in steps S202, S302, and S406 is "1" (reservation system implemented), the reservation time for loading or unloading set in the reservation system may be further considered. Specifically, if the reservation time is later than the first time, the reservation time is used in place of the first time, and the actual work time and waiting time are calculated using the method described above. The reservation time may be input by the administrator terminal 1 and the driver terminal 2, or it may be recorded in the management database 50. In addition, the reservation time may be obtainable by the administrator terminal 1, the driver terminal 2, and the server 5 by accessing the reservation system. (2) Calculation method in steps S215, S314, and S410 As with (1) above, if the type of work to be recorded is rest, refueling, or boarding, the elapsed time from the first time to the second time is calculated as the actual work time (rest time, refueling time, or boarding time). Also, if the type of work to be recorded is waiting, the elapsed time from the first time to the second time is calculated as the waiting time. If a location is not registered in the location information master 51, the facility's break time, opening time, closing time, and standard working hours are unknown. Therefore, in steps S215, S314, and S410, even if the type of work to be recorded is loading or unloading, the elapsed time from the first time to the second time is calculated as the actual working time (loading time, unloading time). However, a standard working time common to all shippers may be predetermined. In this case, if the standard working time is less than or equal to the elapsed time from the first time to the second time, the standard working time will be the actual working time for loading or unloading, and the waiting time will be the elapsed time minus the standard working time. On the other hand, if the standard working time is longer than the elapsed time from the first time to the second time, the elapsed time will be the actual working time for loading or unloading, and the waiting time will be 0.

[0090] In addition to the examples in (1) and (2) above, actual working time and waiting time can be calculated using various methods.

[0091] The labor management system according to this embodiment can perform a master update process that updates the location information master 51 using record R2 of the work information table 52. The details of the master update process will be described below.

[0092] Figure 9 is a flowchart showing an example of a master update process. The process (steps) shown in this flowchart may be implemented through the cooperation of the controller 10 of the administrator terminal 1, the controller 20 of the driver terminal 2, and the server 5, etc., or it may be implemented by any one of them individually.

[0093] In the master update process, first, records R2 containing location data not registered in the location information master 51 are extracted from the work information table 52 (step S501). A registration flag can be used for this extraction. That is, records R2 with a registration flag of "1" (not registered) are extracted. Note that the extraction target in step S501 is, for example, records R2 that include work dates and times after the date and time of the previous master update process.

[0094] Next, a registration screen showing the extraction results from step S501 is displayed (step S502), and the registration of a new record R1 to the location information master 51 is accepted (step S503). For example, when an administrator performs the registration of a new record R1, the registration screen is displayed on the display 12 of the administrator terminal 1. The registration operation in step S503 is performed by operating the input device 13.

[0095] Figure 10 shows an example of the registration screen 70. The registration screen 70 includes a list table 71, a registration button 72, and a cancel button 73. The list table 71 displays a list of information corresponding to record R2 extracted in step S501. That is, each row in the list table 71 corresponds to record R2 and includes input fields for location data, location name, work type, client name, facility break time, business start time, business end time, standard work time, and reservation system flag.

[0096] The input fields for location data and work type, marked with a dot pattern, are automatically populated with the location data and work type of the extracted record R2 by default. Administrators can also modify the location data and work type in these input fields. In the example in Figure 10, the address is shown as the location data.

[0097] Input fields other than location data and work type are initially blank when the registration screen 70 is displayed, for example, and are to be filled in by the administrator. As another example, the facility name corresponding to the address indicated by the location data may be searched from the map data, and the identified facility name may be automatically entered by default in the location name input field. Also, if multiple facility names are identified from the map data, these may be displayed as selectable location name candidates.

[0098] The input fields for consignor name, facility break time, business start time, business end time, standard working hours, and reservation system flag can be filled in, for example, when the work type is loading or unloading. However, even when the work type is other than loading or unloading, at least one of these input fields may be filled in.

[0099] If the cancel button 73 is pressed, the master update process using the registration screen 70 is interrupted. If the register button 72 is pressed, it is determined that input to the registration screen 70 is complete (YES in step S504). At this time, a record R1 containing the information entered in each input field is generated and registered in the location information master 51 (step S505). Note that registration to the location information master 51 may be performed row by row in the list table 71. In this case, for example, if the register button 72 is pressed while any row is selected, the record R1 corresponding to that row will be registered in the location information master 51. The master update process is completed at step S505.

[0100] According to this embodiment, it becomes possible to improve the operational management system of a transportation company. Specifically, even if the driver does not input the type of work, if record R1 corresponding to the vehicle's stopping position is registered in the location information master 51, then record R2 of the work type corresponding to record R1 will be recorded in the work information table 52. This suppresses omissions in recording work information and reduces the burden on drivers and managers regarding work information recording.

[0101] Furthermore, in this embodiment, if a driver performs work at a location where location data is not registered in the location information master 51, a record R2 corresponding to that location is registered in the location information master 51 through a master update process. This allows the location information master 51 to be updated to reflect the daily operations of the transportation company, and significantly reduces the burden on managers and drivers involved in the update process.

[0102] Furthermore, in this embodiment, it is possible to set a registration priority, which prioritizes work types registered in the location information master 51, and an input priority, which prioritizes work types entered by the driver. By incorporating such priority settings, it is possible to significantly improve the accuracy of driver labor management. For example, if there are many errors in the input of work types by drivers, setting the priority to registration priority allows work information corresponding to the stopping position to be recorded based on the location information master 51. On the other hand, if there are few errors in the input of work types by drivers, or if there are many cases where work different from the work type registered in the location information master 51 is performed, the priority setting can be set to input priority. In addition to the above, various other desirable effects can be obtained from this embodiment. Furthermore, the configuration disclosed in this embodiment can be modified into various forms.

[0103] For example, the work record processes A, B, and C shown in the flowcharts of Figures 6 to 8 do not necessarily all need to be executed in real time. For instance, the calculation of work time in steps S208, S215, S308, S314, S408, and S410, and the recording of work information in steps S209, S216, S309, S315, S409, and S411 can be executed at appropriate times, such as when compiling the driver's work information.

[0104] As described above, the entity that executes the processes (steps) shown in the flowcharts of Figures 4, 6 to 9 is not particularly limited, but as an example, each process in the flowcharts of Figures 4, 6 to 8 may be executed by the controller 20 of the driver terminal 2, and each process in the flowchart of Figure 9 may be executed by the controller 10 of the administrator terminal 1.

[0105] Furthermore, the computer programs that enable the administrator terminal 1, driver terminal 2, and server 5 to perform the processing for each step do not need to be stored in a single memory location. They may be composed of modules distributed and stored in the memories of multiple computers. In this case, each module can be executed by the respective processor of the multiple computers.

[0106] For example, in this embodiment, the process of identifying the vehicle's position in steps S201, S301, S401, etc. constitutes a position identification means. Furthermore, the process of identifying the type of work performed at a parking position by operating the work input screen 60 shown in Figure 5 or by extracting a record R1 corresponding to the parking position from the location information master 51 constitutes a work identification means. Also, the process of identifying the actual work time and waiting time in steps S208, S215, S308, S314, S408, S410, etc. constitutes a time identification means. Additionally, the process of recording work information (record R2) in steps S209, S216, S309, S315, S409, S411, etc. constitutes a recording means. Finally, the process of updating the location information master 51 in steps S501 to S505 constitutes an update means. Beyond these, various other means constituting the labor management system can be identified from this embodiment and the embodiments described later.

[0107] [Second Embodiment] A second embodiment will now be described. In the first embodiment, the process shown in the flowchart of Figure 4 is started in response to the vehicle stopping, and when the vehicle is released from its stopped state, it is determined in steps S206, S213, S306, S312, and S404 that the work has been completed. In this embodiment, other examples of methods for determining the start and end of such work are disclosed. Configurations not specifically mentioned can be the same as those in the first embodiment.

[0108] Figure 11 is a flowchart showing an example of a process for determining when to start work (work start determination process). Figure 12 is a flowchart showing an example of a process for determining when to finish work (work end determination process). The processes (steps) shown in these flowcharts may be implemented through the cooperation of the controller 10 of the administrator terminal 1, the controller 20 of the driver terminal 2, and the server 5, etc., or they may be implemented by any one of them individually.

[0109] For example, the work start determination process is performed while the vehicle is in motion and the processes shown in the flowcharts of Figures 4 and 6 to 8 have not yet been executed. In the work start determination process, the vehicle's position is first determined (step S601). The current position can be determined based on the signal received by the GPS receiver 26. The vehicle's position may also be determined based on the signal received by the GPS receiver 45.

[0110] Next, it is determined whether the location identified in step S601 is within the area corresponding to the location data of record R1 in the location information master 51 (step S602). This process may be performed on all records R1 in the location information master 51, or it may be performed on a specific record R1, for example, based on the condition that the work type is loading or unloading.

[0111] For example, the area described above is the area assigned the same address as the location indicated by the location data of record R1 in the map data. If the location data is coordinates corresponding to a positioning system such as GPS, the area described above may be the area within a predetermined radius (within 50m, within 100m, within 200m, etc.) of the location indicated by those coordinates. As yet another example, area data defining the area may be recorded in each record R1 of the location information master 51, and the determination in step S602 may be performed based on that area data. In addition to these, the area corresponding to the location data can be defined in various other ways.

[0112] If it is determined that the vehicle's location is not within the area of ​​any record R1 in the location information master 51 (NO in step S602), the process returns to step S601.

[0113] On the other hand, if it is determined that the vehicle is within the area of ​​any record R1 (YES in step S602), it is determined whether the vehicle speed is less than the first speed (step S603). In the following explanation, this area will be referred to as the target area.

[0114] The vehicle speed used for comparison with the first speed is, for example, the vehicle speed detected by the driving sensor 44. Alternatively, the vehicle speed calculated based on the change in position indicated by the signals received by the GPS receivers 26 and 45 may be used for comparison with the first speed.

[0115] The first speed is set to a speed such as 10 km / h, at which point the vehicle can be considered to be moving slowly or stopped. Step S603 may determine whether the vehicle speed is below the first speed for a certain period of time (e.g., 30 seconds, 1 minute, 2 minutes, etc.).

[0116] If it is determined that the vehicle speed is not less than the first speed (NO in step S603), the process returns to step S601. On the other hand, if it is determined that the vehicle speed is less than the first speed (YES in step S603), the process shown in the flowchart of Figure 4 is started. Thereafter, as in the first embodiment, one of the work record processes A, B, or C is executed based on whether or not the driver has entered the type of work and the priority setting.

[0117] Furthermore, if work record processes A, B, and C are executed after the work start determination process shown in Figure 11, then record R1 corresponding to the vehicle's location will be registered in the location information master 51. Therefore, in work record process A, the process proceeds in the order of steps S201 to S209, in work record process B, the process proceeds in the order of steps S301 to S309, and in work record process C, the process proceeds in the order of steps S401 to S409.

[0118] The work completion determination process shown in Figure 12 is executed in steps S206, S306, and S404. In the work completion determination process, the vehicle's position is identified, as in step S601 (step S701). Furthermore, it is determined whether the identified vehicle's position is within the aforementioned target area (step S702).

[0119] If it is determined that the vehicle's position is within the target area (YES in step S702), it is determined whether the vehicle speed is less than or equal to the second speed (step S703). This vehicle speed may be the speed detected by the driving sensor 44, or it may be the vehicle speed calculated based on the change in position indicated by the signals received by the GPS receivers 26 and 45. The second speed may be the same as the first speed, for example, but it may also be different from the first speed.

[0120] If it is determined that the vehicle speed is not equal to or greater than the second speed (NO in step S703), the process returns to step S701.

[0121] On the other hand, if it is determined that the vehicle is not within the target area (NO in step S702), or if it is determined that the vehicle speed is at or above the second speed (YES in step S703), it is determined that the work is complete (YES in steps S206, S306, and S404).

[0122] When using the work start determination process and work end determination process as described above, the first time specified in steps S204, S304, and S402 can be the time when the work start determination process is completed, that is, the time when the vehicle enters the target area and the vehicle speed falls below the first speed. As another example, the first time may be the time when a predetermined amount of time has elapsed since the completion of the work start determination process. Furthermore, the second time specified in steps S207, S307, and S405 can be the time when the work end determination process is completed, that is, the time when the vehicle exits the target area or when the vehicle speed becomes the second speed or higher. As another example, the second time may be the time when a predetermined amount of time has elapsed since the completion of the work end determination process, or the time when the vehicle speed is no longer 0 km / h during the execution of the work end determination process. In steps S209, S309, and S409, using these first and second time points, record R2 is generated based on various information in record R1 corresponding to the target area and recorded in the work information table 52.

[0123] Even when applying the work start determination process and work end determination process of this embodiment, the process shown in the flowchart of Figure 4 is started when the vehicle stops, just as in the first embodiment. This allows work information at locations where record R1 is not registered in the location information master 51 to be recorded in the same way as in the first embodiment. Furthermore, such unregistered locations can be registered in the location information master 51 by the master update process.

[0124] Step S603 may be omitted from the work start determination process. In this case, the work is determined to have started when the vehicle enters the area (target area) corresponding to the location data of any record R1 in the location information master 51. Also, step S703 may be omitted from the work end determination process. In this case, the work is determined to have ended when the vehicle leaves the target area.

[0125] Thus, it is possible to determine the start and end of work even without using vehicle speed. However, using both vehicle position and speed has the advantage of potentially improving the accuracy of the determination.

[0126] As described above, the entity executing the processes (steps) shown in the flowcharts of Figures 11 and 12 is not particularly limited, but as an example, these processes are executed by the controller 20 of the driver terminal 2. Furthermore, the computer program for realizing the processes related to each step does not need to be stored in a single memory, but may consist of modules distributed and stored in the memories of multiple computers. In this case, each module can be executed by the respective processor of the multiple computers.

[0127] The configurations disclosed in the first and second embodiments can be modified in various ways, as described below, for example.

[0128] In the first and second embodiments, the processes shown in Figures 4, 6 to 9, 11, and 12 are implemented by the controller 10 of the administrator terminal 1, the controller 20 of the driver terminal 2, and the server 5. However, at least a portion of these processes can also be implemented by other devices included in the labor management system. For example, at least a portion of the above processes may be performed by the digital tachograph 3. In this case, the digital tachograph 3 may also function as a driver terminal.

[0129] The location information master 51 may contain multiple records R1 with the same location data and location name, but different consignors. In this case, multiple records R1 with the same location data and location name may be extracted in steps S202, S302, S406, etc. If multiple records R1 are extracted, a screen for selecting the one corresponding to the consignor to be worked on may be displayed on the display 12 of the administrator terminal 1 or the display 23 of the driver terminal 2, and work information may be recorded using the record R1 selected by the administrator or driver through this screen.

[0130] For example, in step S409 of the work record processing C, which is executed when the priority setting is input priority, a record R1 containing the same location data and location name is recorded in the location information master 51, but a record R2 with a different work type than record R1 may be recorded in the work information table 52. In this case, in the master update processing, the work type of record R1 may be replaced with the work type of record R2. As another example, the work type of record R2 may be additionally recorded in record R1. When recording a new record R2 using record R1 containing multiple work types generated in this way, the administrator or driver may be able to select one of these work types. The screen related to this selection may be displayed, for example, on the display 12 of the administrator terminal 1 and the display 23 of the driver terminal 2.

[0131] Multiple records R1 with the same location data and location name but different consignors may be registered in the location information master 51. Furthermore, if these records R1 are extracted in steps S202, S302, S406, etc., the administrator or driver may be able to select one of these records R1. The screen related to this selection may be displayed, for example, on the display 12 of the administrator terminal 1 or the display 23 of the driver terminal 2.

[0132] The location name, consignor name, facility rest time, business start time, business end time, standard work time, and reservation system flag shown in the list 71 on the registration screen 70 may be entered by the driver using the driver terminal 2 at appropriate timings during work record processing A, B, and C. The information entered in this way may be recorded, for example, in record R2 of the work information table 52 and displayed by default in the list 71 during the master update process.

[0133] Record R1 in the location information master 51 may further include a shipper flag indicating whether the record relates to a shipper, either in place of the shipper name or together with the shipper name. When such a shipper flag is applied, for example, an input field for the shipper flag may be added to the registration screen 70 in Figure 10. The shipper flag can be used, for example, to select a method for calculating actual working time in steps S208, S308, and S408. That is, if the shipper flag indicates that record R1 relates to a shipper, the actual working time (loading time, unloading time) and waiting time may be calculated using facility break time, business start time, business end time, and standard working time.

[0134] In the first and second embodiments, the administrator may pre-set the locations to be used for recording work information. Such a setting can be achieved, for example, by adding a flag to the location information master 51 that indicates the setting. In this case, in steps S202, S302, and S406 of the first embodiment, a record R1 is extracted from the location information master 51 that includes location data corresponding to the stopping position and indicates that the flag is used for recording work information. In the second embodiment, entry into and exit from the area is determined based on the location data of record R1, which indicates that the flag is used for recording work information.

[0135] As another example, the settings for locations to be recorded for work information may be recorded in a separate file from the location information master 51. This file may record, for example, location data and location names of the locations to be recorded, or the registration number of record R1 in the location information master 51, as information indicating that the locations are to be recorded for work information. In steps S202, S302, and S406 of the first embodiment, record R1, which includes location data corresponding to the stopping position and is indicated in the file as being to be recorded for work information, is extracted from the location information master 51. In the second embodiment, entry into and exit from the area is determined based on the location data of record R1, which is indicated in the file as being to be recorded for work information.

[0136] The type of work to be recorded in record R1 of the location information master 51 and record R2 of the work information table 52 may be automatically determined from the location name. For example, if the location name is the name of a convenience store or parking area, the type of work may be automatically determined as a break (more specifically, a break at a convenience store or a break at a parking area), and if the location name is the name of a gas station, refueling may be automatically determined.

[0137] In the first and second embodiments, a labor management system for managing the work of truck drivers was disclosed. However, the processes in these labor management systems can also be applied to the labor management of drivers of other types of vehicles, such as trains, buses, and taxis. Furthermore, they can also be applied to the labor management of workers other than drivers.

[0138] The computer programs for implementing the processes disclosed in the first and second embodiments may be stored on a storage medium and transferred to the user, or transferred by the user through a network download. Furthermore, the computer that executes such computer programs may be not limited to the administrator terminal 1, driver terminal 2, digital tachograph 3, and server 5 disclosed in each embodiment, but may be other devices.

[0139] [Third Embodiment] A third embodiment will now be described. In this embodiment, a vehicle management system is disclosed that allows a shipper to understand the status and waiting time of vehicles used by carriers that load or unload cargo at their own facilities. This vehicle management system may have the same functions as those in the first or second embodiment.

[0140] Figure 13 is a block diagram showing an example configuration of a vehicle management system according to the third embodiment. Here, we assume that a shipper company has multiple facilities (C1, C2, C3, ...) such as factories and offices, and that vehicles from multiple carriers load or unload cargo at these facilities. Each facility has at least one loading / unloading port for loading or unloading cargo.

[0141] The vehicle management system includes a server 100 connected to a network N. The server 100 stores a management database 110. As a key element of this embodiment, the management database 110 includes a facility information master 120 containing information on each facility, a transporter master 130 containing information on each transporter, and a work information table 140 (work information database) that stores a history of work performed by transporters at each facility.

[0142] Each facility is equipped with at least one facility terminal 200. If there are multiple loading / unloading points within the facility, a facility terminal 200 may be provided for each of these points. As the facility terminal 200, for example, a tablet, smartphone, or personal computer can be used.

[0143] Drivers of vehicles managed by the vehicle management system have a driver terminal 300. The driver terminal 300 is, for example, a tablet or a smartphone. An application for the vehicle management system is installed on each driver terminal 300.

[0144] If the facility terminal 200 and the driver terminal 300 are tablets or smartphones, their hardware configurations can be the same as those of the driver terminal shown in Figure 1 in the first embodiment.

[0145] The server 100, facility terminal 200, and driver terminal 300 can perform various processes disclosed in this embodiment by executing computer programs stored in memory. Network N may include the Internet, LAN, or WAN. Wi-Fi® may be used to connect the facility terminal 200 and driver terminal 300 to network N at each facility.

[0146] Figure 14 shows an example of the data structure of record R120, which constitutes the facility information master 120. Each record R120 in the facility information master 120 includes facility ID, facility name, area data, set time information, and inbound / outbound information, etc.

[0147] The facility ID is an identification piece of information assigned to each facility. The facility name is the name of the facility corresponding to the facility ID. The area data is information indicating the map-based extent of the facility's premises corresponding to the facility ID, and represents a specific area in a coordinate system compatible with a positioning system such as GPS.

[0148] The time information includes, for example, the facility's break time, opening time, and closing time, corresponding to the facility ID. The loading / unloading information is information about the loading / unloading points (loading / unloading locations) of the facility corresponding to the facility ID. For example, if the facility has multiple loading / unloading points, the loading / unloading information may include identification information (name, code, etc.) for these loading / unloading points, such as loading / unloading points A, B, C, ... In addition, identification information of the authorized carrier (such as the carrier ID described later) may be registered for each loading / unloading point.

[0149] Figure 15 shows an example of the data structure of record R130, which constitutes the carrier master 130. Each record R130 in the carrier master 130 includes the carrier ID, carrier name, facility ID, and inbound / outbound port name.

[0150] The carrier ID is an identification piece assigned to each carrier. The carrier name is the name of the carrier corresponding to the carrier ID. The facility ID and inbound / outbound port name in record R130 are set to correspond to the facilities and inbound / outbound ports to which the carrier corresponding to the carrier ID is permitted to enter. If a carrier is permitted to enter multiple facilities or use multiple inbound / outbound ports, multiple facility IDs and multiple inbound / outbound port names may be set in a single record R130. As described above, if the carrier ID of a carrier permitted to use an inbound / outbound port is registered in the facility information master 120, the registration of the inbound / outbound port name in the carrier master 130 may be omitted.

[0151] Figure 16 shows an example of the data structure of record R140, which constitutes the work information table 140. Each record R140 in the work information table 140 includes work ID, work date, facility ID, inbound / outbound port name, carrier ID, vehicle ID, driver name, status information, designated time, entry time, exit time, work start time, waiting time, delay time, and work time.

[0152] The work ID is an identification piece of information assigned to each work performed. The work date is the date (year, month, day) on which the work corresponding to the work ID was performed. The facility ID and inbound / outbound port name in record R140 indicate the facility and inbound / outbound port on which the work corresponding to the work ID was performed.

[0153] The carrier ID, vehicle ID, and driver name in record R140 indicate the carrier, vehicle, and driver (worker) who performed the work corresponding to the work ID. The status information indicates the progress of the work, such as "on standby," "working," and "completed."

[0154] The specified time in record R140 is the disclosure time of the work specified by the shipper company for the work corresponding to the work ID. The specified time may also be the reservation time for loading or unloading set in the reservation system described above in the first embodiment. Alternatively, both the specified time and the reservation time may be recorded in record R140.

[0155] The entry time, exit time, and work start time for record R140 are the time when the vehicle indicated by the vehicle ID in the record entered the facility indicated by the facility ID in the record, the time when the vehicle exited the facility, and the time when the driver began work at the facility, respectively.

[0156] The waiting time in record R140 is the time the driver waited at the facility indicated by the facility ID before starting work. In this embodiment, the waiting time is mainly calculated based on the specified time (or reservation time), entry time, and work start time in the same record.

[0157] For example, if the entry time is earlier than the designated time, the waiting time will be the time from the designated time to the start of work. On the other hand, if the entry time is later than the designated time, or if no designated time is set, the waiting time will be the time from the entry time to the start of work. In addition, the waiting time may be calculated by adding or subtracting a certain amount of time from the time from the designated time or entry time to the start of work.

[0158] For facilities corresponding to the facility ID in record R140, the waiting time may be calculated by further considering the facility break time, opening time, and closing time set in the facility information master 120. That is, the waiting time may be calculated by subtracting the time overlapping with the facility break time, the time before the opening time, or the time after the closing time from the time from the specified time or entry time to the start of work. However, it is not necessary to use any of these times for deduction.

[0159] The delay time for record R140 is the time the entry time was delayed compared to the designated time. The work time is the time required to perform the work corresponding to record R140, and in one example, it is the elapsed time from the start time of the work to the exit time.

[0160] Figure 17 is a flowchart showing a series of processes for generating record R140 in the work information table 140. The processes (steps) shown in this flowchart are implemented, for example, by the server 100, the facility terminal 200, and the driver terminal 300, or by the cooperation of the server 100, the facility terminal 200, and the driver terminal 300, etc.

[0161] For example, when a driver starts their day's operations, they launch the application for the vehicle management system installed on the driver terminal 300. At this time, the application accepts information input (step S801). The information entered here may include, for example, the carrier ID of the carrier to which the driver belongs, the driver's name, the vehicle ID of the vehicle the driver operates, and the designated time (reserved time) for the work the driver is to perform that day. If the driver is to perform work sequentially at multiple facilities, multiple designated times may be entered in that order. Also, if there is work scheduled for which no designated time has been set, it may be possible to register that work as having no designated time.

[0162] Furthermore, at least one of the carrier ID, driver name, and vehicle ID may be displayed on the driver terminal 300's screen by default, based on previously entered information or information pre-configured in the application, and the driver may modify these as needed. In addition, the designated time may not be entered directly by the driver, but rather downloaded from information set in a reservation system or the like. Moreover, the designated time may be entered on the facility terminal 200 or other facility-side terminals and then downloaded to the driver terminal 300.

[0163] Figure 18 shows an example of the application screen 400 displayed on the driver terminal 300 after the input in step S801 is completed. This application screen 400 has display fields 401, 402, and 403 for the carrier ID, vehicle ID, and driver name entered in step S801. In the example in Figure 18, the carrier name corresponding to the carrier ID is also displayed in display field 401.

[0164] Furthermore, the application screen 400 has a display field 404 for one or more specified times (specified time 1, specified time 2, etc.) entered in step S801, and a display field 405 for displaying the status of admission to the facility corresponding to the specified time. As described above, if work without a specified time is entered, a schedule indicating that there is no specified time, such as "No specified time," may be added. It is preferable that the schedule be displayed in order of planned work, including such work without a specified time. For example, in the example in Figure 18, if work without a specified time is scheduled between work at specified time 1 and work at specified time 2, a schedule with "No specified time" displayed in the display field 404 may be added between the lines for specified time 1 and specified time 2. Note that immediately after the input in step S801, nothing is displayed in the display field 405. As will be described in more detail later, when admission to the facility corresponding to the specified time is completed, information indicating completion of admission, such as "Completed," will be displayed in the display field 405. The completion of admission admission may be notified to the driver by changing the display color of the specified time display field 404, etc.

[0165] After the application is launched, the driver drives the vehicle to the facility where loading or unloading is scheduled. During this operation, it is determined whether the vehicle has stopped or not (step S802). This determination can be made based on the signal received by the GPS receiver of the driver terminal 300. For example, if the position of the vehicle identified by the signal does not change for a certain period of time, it is determined that the vehicle has stopped. In addition, the same method as in the first or second embodiment can be applied to determine whether the vehicle has stopped.

[0166] If it is determined that the vehicle has stopped (YES in step S802), the vehicle's stopping position is determined (step S803). The stopping position is the vehicle's current position and can be determined based on the signal received by the GPS receiver of the driver terminal 300.

[0167] Next, record R120 corresponding to the stopping position identified in step S803 is retrieved from the facility information master 120 (step S804). In step S804, an attempt is made to extract record R120 in which area data including the stopping position identified in step S803 is set.

[0168] In one example, the search target in step S804 is limited to record R120 of the facility ID recorded in record R130 of the carrier master 130, which includes the carrier ID entered in step S801. This allows the carrier to record operations only at facilities and loading / unloading points to which they are permitted entry.

[0169] If record R120 containing area data including the stopping position cannot be extracted (NO in step S805), the process returns to step S802, and steps S803 to S805 are executed depending on the subsequent stopping of the vehicle.

[0170] On the other hand, if record R120 containing area data including the stopping position is extracted (YES in step S805), the entry reception process is executed (step S806). In the entry reception process, a new record R140 corresponding to the work to be performed is generated in the work information table 140.

[0171] In step S806, the work ID of record R140 is recorded as, for example, a newly assigned code. The work date of record R140 is recorded as the date of the current day. The facility ID of record R140 is recorded as the facility ID of record R120 extracted in step S804. In addition, the inbound / outbound port name is recorded as, for example, the inbound / outbound port name of the facility recorded in record R130 of the carrier master 130, which includes the carrier ID entered in step S801. As another example, the driver terminal 300 may accept input of the inbound / outbound port name, and the entered inbound / outbound port name may be recorded in record R140. Furthermore, the carrier ID, vehicle ID, and driver name of record R140 are recorded as the carrier ID, vehicle ID, and driver name entered in step S801.

[0172] At step S806, the status information of record R140 is recorded as "Waiting". The specified time is, for example, the earliest time among the specified times entered in step S801 for which the work is incomplete. Alternatively, the specified time set for the carrier's work on that day in the reservation system may be recorded.

[0173] In step S806, the entry time recorded in record R140 may be, for example, the time when the vehicle begins to stop. Alternatively, the entry time may be a predetermined time elapsed from the time the vehicle began to stop. Note that in step S806, the exit time, work start time, waiting time, and work time are not recorded in record R140. On the other hand, if the entry time is later than the specified time, the difference is recorded as the delay time.

[0174] Once entry registration is complete in step S806, information indicating completion, such as "Completed," will be displayed in the display field 405 of the operation schedule corresponding to the task to be performed now (for example, the earliest time in the display field 405 among the incomplete operation schedules). This allows the driver to automatically understand that entry registration has been completed.

[0175] The facility can check information about vehicles whose entry registration has been completed using the facility terminal 200. Figure 19 shows an example of the management screen 500 displayed on the facility terminal 200. The management screen 500 displays the facility name corresponding to the facility terminal 200, such as "Facility C1", the facility's opening time, the current time, and the management table 510.

[0176] Each row in the management table 510 contains information about vehicles that were registered for entry at the facility on that day. Specifically, each row corresponds to record R140 in the work information table 140, where the work date is the current date and the facility ID indicates the facility in question.

[0177] In the example shown in Figure 19, the leftmost column of each row in the management table 510 displays the name of the carrier corresponding to the carrier ID in record R140. Furthermore, each row in the management table 510 displays the vehicle ID, driver name, loading / unloading port name, status information (waiting / working / completed), designated time, entry time, delay time, departure time, waiting time, and working time from record R140.

[0178] A work input field is provided at the far right of the management sheet 510. When the status information is "Waiting," the start button 511 is displayed in the work input field (see the rows for B Transportation and C Transportation). When the status information is "In Progress," the end button 512 is displayed in place of the start button 511 in the work input field (see the row for A Transportation). The start time of the work may be displayed for the end button 512, such as "9:30." When the status information is "Completed," the start time of the work is displayed in the work input field (see the row for D Transportation).

[0179] In the example shown in Figure 19, a toggle button 513 is located at the top of the display field for the inbound / outbound port names. The toggle button 513 is used to switch the inbound / outbound ports to be displayed in the management table 510. For example, when the toggle button 513 is operated, a dialog box is displayed for selecting one or more inbound / outbound ports from the multiple inbound / outbound ports of the facility to be displayed. In the example shown in Figure 19, inbound / outbound port "A" is selected.

[0180] Furthermore, in the example in Figure 19, rows with a status of "completed" are displayed in a different color from the other rows (see row D, "Transport"). This makes it easier to visually distinguish between rows with incomplete (waiting / in progress) tasks and completed rows.

[0181] For example, in management table 510, rows showing the work status as "in progress" may be displayed at the top, rows showing the work status as "completed" may be grouped together at the bottom, and rows showing the work status as "on standby" may be grouped together in between. Furthermore, if there are multiple rows showing "on standby," arranging them so that those with earlier specified times are at the top makes it easy to understand the priority of which vehicles should start work.

[0182] Furthermore, the display style (text color and background color) for the standby and working status indicators in the work status display area may be different. Similarly, if the standby time exceeds a certain period, a warning may be issued by changing the display style (text color and background color) of the standby time to something more conspicuous. The display style of the standby time may change in multiple stages, for example, less than 1 hour, 1 hour or more but less than 2 hours, and 3 hours or more. In Figure 19, the difference in the display style between the work status and standby time is shown as an example using diagonal lines.

[0183] In the flowchart of Figure 17, after entry is accepted in step S806, the system awaits its turn to perform the task (step S807). During this time, the status of the task remains in a waiting state.

[0184] Furthermore, while the work status is in standby mode, the standby time for that work is counted up in management sheet 510 as time passes. This allows facility managers to understand the real-time standby status of each vehicle that enters the facility.

[0185] For example, when the start button 511 is pressed on the management screen 500, the work sequence for the corresponding task arrives (YES in step S807). At this time, the vehicle calling process corresponding to that task is performed (step S808).

[0186] For example, in the call processing, the facility terminal 200 notifies the driver terminal 300 of the arrival of the work turn. Upon receiving this notification, the driver terminal 300 informs the driver of the arrival of the work turn through voice output via a speaker, message display on a screen, etc.

[0187] Furthermore, when it is time for the work, the record R140 in the work information table 140 corresponding to that work is updated (step S809). Specifically, the status information of the record R140 is set during the work, and the work start time is recorded. For example, the time when the start button 511 is operated can be used as the work start time. However, the work start time may be the time after a predetermined period of time has elapsed since the start button 511 was operated, or the time entered by the facility terminal 200 or the driver terminal 300.

[0188] After steps S808 and S809, the completion of the work is awaited (step S810). For example, if the vehicle's position, determined based on the signal received by the GPS receiver of the driver terminal 300, falls outside the range of the area data of record R120 extracted in step S804, the work is determined to be complete.

[0189] When it is determined that the work has been completed (YES in step S810), the exit reception process is executed (step S811). In the exit reception process, the exit time (work completion time), waiting time, and work time are recorded in the record R140 for the work in question. The exit time is, for example, the time when a vehicle that was parked at the loading / unloading area begins to move in order to leave. Such a time can be determined by recording the time-series position of the vehicle within the facility based on the signal received by the GPS receiver of the driver terminal 300.

[0190] As another example, the departure time may be the time when the vehicle left the area data range of record R120 extracted in step S804, or a predetermined time before that time, or a predetermined time after that time.

[0191] As another example, the completion of work may be entered by operating the end button 512 on the management sheet 510. In this case, the work completion time may be the time when the end button 512 is operated, a predetermined time before this time, or a predetermined time after this time. In addition, the work completion and departure times may be entered by the driver terminal 300.

[0192] Waiting time is calculated based on the entry time, work start time, facility break time, business start time, and business end time, as described above. Work time is, for example, the time from the work start time to the departure time. The work start time may be the time obtained by subtracting or adding a predetermined time from the time from the work start time to the departure time.

[0193] Step S811 marks the end of the recording process for one operation. Subsequently, steps S802 to S811 are repeated for the vehicle in question.

[0194] As described above, the execution entity for each step in the flowchart of Figure 17 may be any of the devices included in the vehicle management system according to this embodiment (server 100, facility terminal 200, driver terminal 300, etc.). For example, the execution entity for step S801 is the driver terminal 300, and the execution entities for steps S802 to S811 are the server 100 or the facility terminal 200.

[0195] As the process shown in the flowchart of Figure 17 is executed for multiple vehicles, the work information table 140 accumulates work information for loading and unloading at each facility. By using this work information table 140, shippers can analyze the real-time status and waiting times of vehicles visiting each facility.

[0196] The vehicle management system preferably includes a function to analyze the records R140 stored in the work information table 140. This analysis function can be used, for example, on a facility terminal 200 or other personal computers on the shipper's side. However, at least a part of the analysis function may be available on the carrier's personal computer.

[0197] For example, the analysis screen used to perform the analysis function displays a GUI for specifying the analysis period, the facility ID to be analyzed, the carrier ID to be analyzed, etc. Multiple facility IDs may be specified simultaneously. Similarly, multiple carrier IDs may be specified simultaneously.

[0198] Figure 20 shows an example of the analysis results screen 600, which displays the analysis results obtained by the analysis function. This analysis results screen 600 shows the results of the analysis of the waiting time for work performed by a vehicle of "A Transportation" at "Facility C1" in "October 2024".

[0199] Specifically, the analysis results screen 600 includes a work history table 610. Each row in this work history table 610 corresponds to record R140 in the work information table 140. In the example in Figure 20, the date, vehicle ID, driver name, designated time, entry time, work start time, waiting time due to the transport company, waiting time due to the consignor, and work time of record R140 corresponding to each row are displayed.

[0200] Waiting time due to the shipping company is the waiting time caused by reasons on the shipping company's side. For example, waiting time due to the shipping company is the waiting time that occurs when the entry time is earlier than the designated time, and is equivalent to the time from the entry time to the designated time. Waiting time due to the shipping company may also be the time obtained by adding or subtracting a predetermined time from the time from the entry time to the designated time.

[0201] Shipper-initiated waiting time corresponds to waiting time caused by reasons on the shipper's side. For example, shipper-initiated waiting time corresponds to the time from the designated time to the start of work. Shipper-initiated waiting time may also be the time obtained by adding or subtracting a predetermined time from the time from the designated time to the start of work.

[0202] For example, the waiting time due to the carrier and the waiting time due to the consignor are calculated when the work history table 610 is generated. Alternatively, the waiting time due to the carrier and the waiting time due to the consignor may be calculated in step S809, etc., and recorded in record R140 of the work information table 140.

[0203] Work history table 610 also displays the total waiting time due to the transport company, the waiting time due to the consignor, and the total work time for each row. Furthermore, the bottom of work history table 610 (the area marked with diagonal lines) displays the total waiting time due to the consignor, the number of waiting cases (the number of work cases included in work history table 610), and the average waiting time. The average waiting time is calculated by dividing the total waiting time due to the consignor by the number of waiting cases. Using this average waiting time, it is easy to understand the current waiting time situation at facility C1 of Transport A.

[0204] The analysis results screen 600 disclosed here is merely one example of a waiting time analysis method. As another analysis method, for example, the total or average waiting time due to the carrier and the waiting time due to the shipper may be calculated for each facility without specifying a carrier. In this case, the average waiting time due to the carrier or the waiting time due to the shipper for each facility may be ranked and displayed on the analysis results screen 600. This makes it easy to identify facilities that particularly need improvement in waiting times. Alternatively, the total or average waiting time due to the carrier and the waiting time due to the shipper may be calculated for each carrier without specifying a facility.

[0205] Transportation companies sometimes outsource work requested by client companies to other transportation companies. In such cases, the primary transportation company and the subcontracted transportation company may be linked. This would allow the client company to understand the relationship between the primary and subcontracted transportation companies that visit the facility, and would also lead to improved security measures.

[0206] The association between the prime contractor and the subcontractor can be implemented, for example, by the carrier ID. Specifically, the carrier ID of a subcontractor may be set to include the carrier ID of the prime contractor, such as by adding a sub-number to the carrier ID of the prime contractor. As another example, the prime contractor's carrier ID may be recorded in the subcontractor's record R130 along with the carrier ID of that carrier.

[0207] According to this embodiment, shippers can easily manage the vehicles of transportation companies entering and leaving their facilities. Furthermore, by analyzing the work information table 140, which stores work history, shippers can grasp the actual waiting time and take measures to reduce waiting time.

[0208] Furthermore, in the process shown in the flowchart of Figure 17, work information is recorded without requiring any special operation from the driver or facility manager. Therefore, it is possible to significantly reduce the burden on drivers and managers, and since there is no concern about input omissions, work information can be recorded accurately.

[0209] This embodiment allows us to understand various functions (means). An example of these means is given below. (1) Facility identification means (steps S802 to S805) that identify the facility where the vehicle has stopped based on the vehicle's location information. (2) An entry reception means (step S806) for accepting vehicles to enter the facility. (3) A calling means for calling a vehicle waiting to perform work (step S808). (4) Start identification means for identifying the start time of work for vehicle drivers at the facility (steps S807, S809). (5) Departure identification means (step S811) for identifying the time of departure of a vehicle from the facility. (6) A waiting time calculation means (step S811) that calculates the waiting time of the vehicle based on the entry time and the start time of work. (7) Recording means for recording records including facility identification information, vehicle identification information, identification information of the transporter corresponding to the vehicle, entry time, work start time and exit time, etc. (steps S806, S809, S811). (8) Analysis means for analyzing multiple accumulated records (Figure 20). (9) Result display means for displaying the analysis results obtained by the analysis means (Figure 20).

[0210] In this embodiment, we primarily assume a scenario where the entry and exit of a vehicle into a facility is detected by signals received by the GPS receiver of the driver terminal 300. As another example, vehicle entry may be detected when the driver terminal 300 enters the communication range of a Wi-Fi transceiver installed at the facility's entrance / exit, and vehicle exit may be detected when the driver terminal 300 leaves the communication range.

[0211] Furthermore, in this embodiment, it is assumed that the driver terminal 300 is, for example, a tablet or smartphone, and that the input in step S801 is performed by an application installed on it. As another example, the driver terminal 300 may be an in-vehicle device such as a digital tachograph. In this case, the driver terminal 300 only needs to be able to transmit vehicle information, such as signals received by the vehicle's GPS receiver, to the server 100 etc. via the network N, and the above application is not necessarily required. That is, once the vehicle's location information is transmitted from the in-vehicle device to the server 100 etc., the server 100 etc. can implement the processing shown in the flowchart of Figure 17 based on this location information. As yet another example, the driver's smartphone or tablet and an in-vehicle device such as a digital tachograph may cooperate to realize the functions of the driver terminal 300. [Explanation of symbols]

[0212] 1...Administrator terminal, 2...Driver terminal, 3...Digital tachograph, 5...Server, 10, 20...Controller, 50...Management database, 51...Location information master, 52...Work information table.

Claims

1. A labor management system including an administrator terminal, a driver terminal, and a server that can communicate with each other, A master containing multiple records that associate location data, location names, and the types of work to be performed at the facility indicated by the location name, A means for determining the location of a vehicle, If any of the multiple records in the master contain a record that includes location data corresponding to the location identified by the location identification means, the work type of that record is identified as the work type of the work performed at that location; if there is no record that includes such location data, the work identification means identifies the work type of the work performed at that location based on input from the driver or manager. A recording means for recording location data corresponding to the location identified by the location identification means, and work information including the type of work identified by the work identification means, If there is no record in the master that corresponds to the location data of the work information recorded by the recording means, an update means registers a record in the master that associates the location data, the name of the location indicated by the location data, and the type of work entered by the driver or the manager. Equipped with, Each of the location identification means, the work identification means, the recording means, and the update means is implemented by the administrator terminal, the driver terminal, and the server, or by the cooperation of the administrator terminal, the driver terminal, and the server. Labor management system.

2. If the update means does not have a record in the master that corresponds to the location data of the work information recorded by the recording means, it displays a registration screen on the display of the administrator terminal in which a location name and work type can be entered, and registers a record in the master that associates the location data with the location name and work type entered on the registration screen. The labor management system according to claim 1.

3. If the update means does not have a record in the master that corresponds to the location data of the work information recorded by the recording means, it registers a record in the master that associates the location data with the place name of the location indicated by the location data, the type of work entered by the driver or the manager, and at least one of the rest time, opening time, closing time of business, and standard working hours at the facility indicated by the place name. The labor management system according to claim 1.

4. The system further comprises a time-determining means for determining the actual working time of the work performed at the location determined by the location-determining means, The recording means records the work information, which includes location data corresponding to the location identified by the location identification means, the type of work identified by the work identification means, and the actual work time identified by the time identification means. The time determination means is implemented by any one of the administrator terminal, the driver terminal, and the server, or by the cooperation of the administrator terminal, the driver terminal, and the server. A labor management system according to any one of claims 1 to 3.

5. The time determination means determines the actual work time based on a first time when the vehicle entered an area corresponding to the location data of any record registered in the master, and a second time when the vehicle exited the area. The labor management system according to claim 4.

6. The time determination means determines the actual work time based on a first time when the vehicle enters an area corresponding to the location data of any record registered in the master and the vehicle speed of the vehicle falls below a first speed, and a second time when the vehicle exits the area or the vehicle speed of the vehicle within the area becomes a second speed or greater. The labor management system according to claim 4.

7. Computers, Location identification means for determining the location of a vehicle, The work identification means includes a master containing multiple records that associate location data, a place name, and the type of work to be performed at the facility indicated by the place name, and if there is a record containing location data corresponding to the location identified by the location identification means, the work type of that record is identified as the type of work to be performed at that location; if there is no record containing the location data, the work identification means identifies the type of work to be performed at that location based on input from the driver or manager. A recording means for recording location data corresponding to the location identified by the location identification means, and work information including the type of work identified by the work identification means, If there is no record in the master that corresponds to the location data of the work information recorded by the recording means, an update means registers in the master a record that associates the location data, the name of the location indicated by the location data, and the type of work entered by the driver or the manager. A computer program designed to function as such.

8. If the update means does not have a record in the master that corresponds to the location data of the work information recorded by the recording means, it displays a registration screen on the display where the location name and work type can be entered, and registers a record in the master that associates the location data with the location name and work type entered on the registration screen. The computer program according to claim 7.

9. If the update means does not have a record in the master that corresponds to the location data of the work information recorded by the recording means, it registers a record in the master that associates the location data with the place name of the location indicated by the location data, the type of work entered by the driver or the manager, and at least one of the rest time, opening time, closing time of business, and standard working hours at the facility indicated by the place name. The computer program according to claim 7.

10. The computer is further configured to function as a time determination means for determining the actual working time of the work performed at the location determined by the location determination means. The recording means records the work information, which includes location data corresponding to the location identified by the location identification means, the type of work identified by the work identification means, and the actual work time identified by the time identification means. A computer program according to any one of claims 7 to 9.

11. The time determination means determines the actual work time based on a first time when the vehicle entered an area corresponding to the location data of any record registered in the master, and a second time when the vehicle exited the area. The computer program according to claim 10.

12. The time determination means determines the actual work time based on a first time when the vehicle enters an area corresponding to the location data of any record registered in the master and the vehicle speed of the vehicle falls below a first speed, and a second time when the vehicle exits the area or the vehicle speed of the vehicle within the area becomes a second speed or greater. The computer program according to claim 10.

Images