Operation management device, operation management system, operation management method, and operation management program

Abstract

To take care of driver fatigue to contribute to driving safety and work efficiency improvement by assigning drivers to routes in accordance with the levels of fatigue of the drivers.SOLUTION: A server 20 comprises a biological information acquisition unit 23 for acquiring biological information indicating the level of fatigue of a driver during operation of a vehicle V, a delivery plan acquisition unit 25 for acquiring a delivery plan including one or more routes, and an assignment unit 26 configured to determine whether to assign the driver to one of the routes included in the delivery plan or not in accordance with the level of fatigue.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to a traffic management device, a traffic management system, a traffic management method, and a traffic management program. [Background technology]

[0002] A driving management system is known that suggests rest points selected from multiple rest facilities based on the vehicle's operation plan, the driver's biometric information, and congestion information at multiple rest facilities along the driving route (see Patent Document 1). [Prior art documents] [Patent documents]

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

[0004] Although conventional technologies including Patent Document 1 estimate the driver's fatigue level from biometric information, no technology has been proposed that utilizes biometric information in operation management including vehicle dispatch planning.

[0005] The present invention provides a traffic management device, a traffic management system, a traffic management method, and a traffic management program that can take care of driver fatigue by allocating routes based on the driver's fatigue level. [Means for solving the problem]

[0006] In order to achieve the above-mentioned object, the operation management device according to the present invention has the following features. a biometric information acquisition unit that acquires biometric information representing a fatigue level of a driver during operation of the vehicle; a delivery plan acquisition unit that acquires a delivery plan including one or more routes; an allocation unit that determines whether to allocate the driver to any of the routes included in the delivery plan based on the fatigue level, Operation control device.

[0007] In order to achieve the above-mentioned object, the traffic management system according to the present invention has the following features. an in-vehicle device that collects the biometric information; The operation management device, The operation management device transmits a delivery plan in which a driver is assigned to each route to the in-vehicle device. Operation management system.

[0008] In order to achieve the above-mentioned object, the operation control method according to the present invention has the following features. Acquire biometric information that indicates the fatigue level of the driver during vehicle operation, Obtain a delivery plan including one or more routes; determining whether to assign the driver to any of the routes included in the delivery plan based on the fatigue level; Operation management method.

[0009] In order to achieve the above-mentioned object, the operation control program according to the present invention has the following features. acquiring biological information representing a fatigue level of a driver during operation of a vehicle; obtaining a dispatch plan including one or more routes; determining whether to assign the driver to any of the routes included in the delivery plan based on the fatigue level; An operation management program that runs on a computer. [Effects of the Invention]

[0010] According to the present invention, crew fatigue can be taken care of by allocating routes based on the crew's fatigue level.

[0011] The present invention has been briefly described above. The details of the present invention will become clearer by reading the following detailed description of the invention (hereinafter referred to as "embodiments") with reference to the accompanying drawings. [Brief explanation of the drawings]

[0012] [Figure 1] FIG. 1 is a system configuration diagram showing an example of the configuration of an operation control system according to one embodiment of the present invention. [Figure 2] FIG. 2 is a block diagram showing an example of the configuration of an in-vehicle device according to one embodiment of the present invention. [Figure 3] FIG. 3 is a block diagram showing an example of the configuration of a server (operation management device) according to one embodiment of the present invention. [Figure 4] FIG. 4 is a flowchart showing an outline of the procedure of the operation management method performed by the server according to the embodiment. [Figure 5] FIG. 5 is a sub-flowchart showing the content of step S20 in FIG. [Figure 6] FIG. 6 is a graph showing a general change in fatigue level of a crew member. [Figure 7] FIG. 7 is a sub-flowchart showing the content of step S30 in FIG. [Figure 8] FIG. 8(A) is a table showing the correspondence between the total on-duty time over the past week and the estimated level of fatigue, and FIG. 8(B) is a table showing the correspondence between the total driving time over the past two days and the estimated level of fatigue. [Figure 9] FIG. 9 is a table showing the overall estimated fatigue level in the combination of the estimated fatigue level based on the total on-duty time and the estimated fatigue level based on the total driving time. [Figure 10] FIG. 10 is a table showing the rest time over the last two days that should be taken into account in the estimated fatigue level. [Figure 11] FIG. 11 is a table showing accumulated fatigue levels in combinations of estimated fatigue levels based on biological information and estimated fatigue levels based on driving data. [Figure 12]FIG. 12 is a graph showing an example of changes in fatigue level or stress, which is a characteristic of a particular crew member. [Figure 13] FIG. 13 is a table showing the characteristics of each crew member for each delivery route. [Figure 14] FIG. 14 is a sub-flowchart (part 1) showing the content of step S60 in FIG. [Figure 15] FIG. 15 is a sub-flowchart (part 2) showing the content of step S60 in FIG. [Figure 16] FIG. 16 is a table showing the delivery routes assigned to each crew member. DETAILED DESCRIPTION OF THE INVENTION

[0013] Specific embodiments of the present invention will be described below with reference to the accompanying drawings.

[0014] As shown in Fig. 1, the operation management system 1 according to the embodiment is a system for caring for the fatigue of a crew member (driver) who drives a vehicle V, based on the fatigue level of the crew member (driver) and operation data of the vehicle V. The operation management system 1 is operated by a service provider whose clients are businesses (e.g., transportation companies) that manage the operation of vehicles such as trucks. The operation management system 1 includes an on-board device 10 mounted on the vehicle V, a server 20 which is an operation management device capable of communicating with the on-board device 10, and an administrator PC (personal computer) 30 which is a communication terminal capable of communicating with the server 20.

[0015] The vehicle-mounted device 10 is mounted on a vehicle V such as a truck, and collects operational data (so-called digital tachograph data) including the driving conditions of the vehicle V. The collected operational data is used, for example, to create a daily report on one day's operations. Specifically, the vehicle-mounted device 10 is a driving recorder that records the driving speed, driving time, driving distance, etc. of the vehicle V. The vehicle-mounted device 10 also functions as a drive recorder that can capture images of the surroundings of the vehicle V using a camera mounted on the vehicle V. The vehicle-mounted device 10 can be wirelessly connected to a network N such as the Internet, for example, via wireless communication. Furthermore, the vehicle-mounted device 10 can also collect biometric information that indicates the driver's fatigue level.

[0016] The server 20 is a computer device that can communicate with the vehicle-mounted device 10 via the network N, and is a traffic management device that is operated by, for example, a service provider and executes the main functions of the traffic management system 1.

[0017] The administrator PC 30 is a communication terminal used by an administrator of a business operator (e.g., a transport company) that operates the vehicle V, and is capable of communicating with at least the server 20 via the network N. The communication terminal is not limited to a fixed installation type, and may be a portable device such as a tablet, smartphone, or mobile phone. The administrator PC 30 may be capable of communicating with the vehicle-mounted device 10.

[0018] 2 is a block diagram showing an example of the configuration of the vehicle-mounted device 10 according to the embodiment. The vehicle-mounted device 10 includes a control unit 11, a speed information acquisition unit 12, an engine information acquisition unit 13, a biological information acquisition unit 15, and a communication unit 16.

[0019] The control unit 11 is a processing unit (computer) that mainly controls the vehicle-mounted device 10. The control unit 11 reads a program for the vehicle-mounted device stored in a memory (not shown) and causes each unit of the vehicle-mounted device 10 to execute a predetermined process.

[0020] The speed information acquisition unit 12 acquires the traveling speed of the vehicle V from a speedometer or the like of the vehicle V. The engine information acquisition unit 13 acquires engine information including engine on / off information, engine speed, etc. The speed information acquisition unit 12 and the engine information acquisition unit 13 can calculate at least one of the on-duty time and driving time of the driver of the vehicle V from the speedometer, engine values, etc. The biometric information acquisition unit 15 acquires biometric information indicating the driver's fatigue level during operation of the vehicle V from a biometric information sensor.

[0021] The fatigue level of the crew member during operation of the vehicle V may include the fatigue level at the time of roll call (before the day's operation), the fatigue level after the previous operation, the fatigue level continuously acquired during the past operation, the fatigue level continuously acquired during the past week's operation, etc. Furthermore, the biometric information representing the crew member's fatigue level may include the driver's pulse wave, heart rate, drowsiness, stress, attention level, etc., which may be indicators of fatigue level. The biometric information sensor may be any sensor capable of acquiring the above-mentioned biometric information, and may be installed on the steering wheel or the driver's seat held by the driver, or may be directly attached to the driver's arm, etc. The biometric information sensor may be of a non-contact type or a contact type. For example, the biometric information sensor may be composed of a pulse wave sensor or an imaging unit capable of capturing images of the driver's face, eyes, etc. The biometric information acquired by the biometric information acquisition unit 15 is stored in a memory (not shown).

[0022] The communication unit 16 functions as a transmitting unit that transmits operation data of the vehicle V, including the traveling speed, engine information, driver's on-duty time, driver's driving time, etc., and driver's biometric information, to the server 20 via the network N, for example, at every predetermined time interval. The communication unit 16 also functions as a receiving unit that receives information from the server 20, the administrator PC 30, etc.

[0023] 3 is a block diagram showing an example of the configuration of the server 20 according to the embodiment. The server 20 includes a control unit 21, a communication unit 22, a biometric information acquisition unit 23, an operation data acquisition unit 24, a delivery plan acquisition unit 25, an allocation unit 26, a calculation unit 27, and a storage unit 28.

[0024] The control unit 21 is an arithmetic processing unit (computer) that mainly controls the server 20. The control unit 21 reads out a server program stored in a memory (not shown), a storage unit 28, etc., and causes each unit of the server 20 to execute a predetermined process.

[0025] The communication unit 22 functions as a receiving unit that receives operation data of the vehicle V and biometric information of the crew from the server 20 via the network N, and also functions as a transmitting unit that transmits information to the server 20, the administrator PC 30, etc. The communication unit 22 receives the operation data of the vehicle V and the biometric information of the crew, for example, at predetermined time intervals.

[0026] The biometric information acquisition unit 23 acquires the biometric information received by the communication unit 22 from the vehicle-mounted device 10. The operation data acquisition unit 24 acquires the operation data of the vehicle V received by the communication unit 22 from the vehicle-mounted device 10.

[0027] The delivery plan acquisition unit 25 acquires a delivery plan including one or more routes that is created by, for example, a vehicle manager, transmitted from the manager PC 30, and received by the communication unit 22. The allocation unit 26 determines whether to allocate a driver to any of the routes included in the delivery plan based on the fatigue level indicated by the biometric information acquired by the biometric information acquisition unit 23.

[0028] The calculation unit 27 calculates the fatigue level using the biometric information during operation for a certain period of time that was acquired during the past certain period of time by the biometric information acquisition unit 23. The allocation unit 26 can also determine whether to allocate a driver to any of the routes included in the delivery plan based on the fatigue level calculated by the calculation unit 27.

[0029] The calculation unit 27 can also calculate the estimated fatigue level from the operation data acquired by the operation data acquisition unit 24. In this case, the allocation unit 26 can determine whether to assign a driver to any of the routes included in the delivery plan based on the estimated fatigue level.

[0030] The memory unit 28 is a storage device that stores various data and programs. The memory unit 28 may store an operation management program for causing the control unit 21 to execute an operation management method described below. At least one of the biometric information acquisition unit 23, the operation data acquisition unit 24, the delivery plan acquisition unit 25, the allocation unit 26, and the calculation unit 27 may be a function realized by software that is realized by a program stored in the memory unit 28, for example.

[0031] 4 is a flowchart showing an outline of the procedure of the operation management method performed by the server 20 according to the embodiment. The biometric information acquisition unit 23 acquires past biometric information from the vehicle-mounted device 10, the operation data acquisition unit 24 acquires operation data from the vehicle-mounted device 10, and the delivery plan acquisition unit 25 acquires a delivery plan from the manager PC 30 (step S10). The calculation unit 27 calculates a fatigue level using the acquired biometric information (step S20). Next, the calculation unit 27 calculates an estimated fatigue level from the acquired operation data (step S30).

[0032] Furthermore, the calculation unit 27 calculates the accumulated fatigue level from the fatigue level calculated in step S20 and the estimated fatigue level calculated in step S30 (step S40). Furthermore, the calculation unit 27 calculates the characteristics of each crew member (step S50). The allocation unit 26 allocates crew members to any of the routes included in the delivery plan acquired in step S10 based on the accumulated fatigue level calculated in step S40 and the characteristics of each crew member calculated in step S50, and creates a delivery plan with the crew members allocated (step S60). The communication unit 22 transmits the delivery plan with the crew members allocated to the routes to the vehicle-mounted device 10 (step S90).

[0033] FIG. 5 is a sub-flowchart showing the content of step S20 in FIG. 4. That is, the calculation unit 27 processes the biometric information acquired in step S10 according to the procedure in FIG. 5 to calculate the fatigue level. The calculation unit 27 first acquires a fatigue value represented by biometric information acquired by the biometric information acquisition unit 23 during a certain period in the past, for example, the last two days of operation (while the vehicle is in operation) (step S21). The calculation unit 27 calculates the amount of change in this fatigue value (step S22). FIG. 6 is a graph showing a rough outline of the change in the fatigue level of the driver. The amount of change corresponds to the length of the double-headed arrow in this graph, and is calculated as the difference between a predetermined reference value, such as the fatigue level at the time of departure, and the fatigue value obtained every predetermined time (for example, 10 minutes) (amount of change = reference value - fatigue value every predetermined time).

[0034] Next, the calculation unit 27 integrates the amount of change in the fatigue value over a certain period of time (step S23), and calculates the fatigue level based on the integrated value (step S24). The final fatigue level is expressed in three levels, for example, high, medium, and low, depending on the calculated value.

[0035] Fig. 7 is a sub-flowchart showing the content of step S30 in Fig. 4. That is, the calculation unit 27 processes the operation data acquired in step S10 according to the procedure in Fig. 7 to calculate an estimated fatigue level. The calculation unit 27 acquires the on-duty time from the operation data for a certain period in the past, for example, the most recent week (step S31), calculates the total on-duty time for the most recent week (step S32), and calculates the estimated fatigue level based on the calculated total on-duty time (step S33).

[0036] 8(A) is a table showing the correspondence between the total amount of on-duty time over the past week and the estimated level of fatigue, and is stored in, for example, the storage unit 28. In step S33, the calculation unit 27 uses this table to calculate the estimated level of fatigue based on the total amount of on-duty time. It is estimated that the maximum total amount of on-duty time per week is approximately 44 hours. Therefore, this table defines the estimated level of fatigue as follows: if the driving time is 36 hours or more (more than 80% of the on-duty time), the estimated level of fatigue is medium if the driving time is 27 hours or more (more than 60% of the on-duty time), and the estimated level of fatigue is low if the driving time is less than 27 hours.

[0037] Furthermore, the calculation unit 27 acquires driving time from operation data for a certain period in the past, for example, the most recent two days (step S34), calculates the total driving time for the most recent two days (step S35), and calculates an estimated fatigue level based on the calculated total driving time (step S36).

[0038] 8(B) is a table showing the correspondence between the total driving time and the estimated fatigue level over a certain period of time in the past, for example, the most recent two days, and is stored in, for example, the memory unit 28. In step S36, the calculation unit 27 uses this table to calculate the estimated fatigue level based on the total driving time. It is estimated that the maximum driving time is approximately 9 hours per day (18 hours in two days). Therefore, this table defines the estimated fatigue level as high when the driving time is 15 hours or more (more than 80% of the driving time), medium when the driving time is 11 hours or more (more than 60% of the driving time), and low when the driving time is less than 11 hours.

[0039] Finally, the calculation unit 27 calculates a comprehensive estimated fatigue level based on the two estimated fatigue levels calculated in step S33 and step S36 (step S37).

[0040] 9 is a table used by the calculation unit 27 to calculate the overall estimated fatigue level in step S37, and is stored in the storage unit 28, for example. This table shows the overall estimated fatigue level for a combination of an estimated fatigue level based on the total amount of on-duty time over the most recent week and an estimated fatigue level based on the total amount of driving time over the most recent two days. For example, if the estimated fatigue level based on the total amount of on-duty time is medium and the estimated fatigue level based on the total amount of driving time is high, the overall estimated fatigue level is high. If the estimated fatigue level based on the total amount of on-duty time is medium and the estimated fatigue level based on the total amount of driving time is low, the overall estimated fatigue level is low.

[0041] The calculation unit 27 may also take into account the rest time of the crew member when calculating the estimated fatigue level. Fig. 10 is a table showing the contents to be taken into account in the estimated fatigue level regarding the rest time over a certain period in the past, for example, the most recent two days, and is stored, for example, in the storage unit 28. For example, while a guideline is to take rest time of 11 hours or more per day, it is possible to take into account in the estimated fatigue level whether or not the crew member has taken rest for at least 9 hours.

[0042] Next, the calculation unit 27 calculates the accumulated fatigue level from the fatigue level calculated in step S20 and the estimated fatigue level calculated in step S30 (step S40). FIG. 11 shows a table used by the calculation unit 27 to calculate the accumulated fatigue level in step S40, which is stored in, for example, the storage unit 28. This table shows the accumulated fatigue level when the estimated fatigue level based on the biometric information calculated in step S20 is combined with the estimated fatigue level based on the operational data calculated in step S20. For example, if the estimated fatigue level based on the biometric information is high and the estimated fatigue level based on the operational data is also high, the accumulated fatigue level is so high that the crew member needs a day off (day off required). If the estimated fatigue level based on the biometric information is high and the estimated fatigue level based on the operational data is low, the accumulated fatigue level is medium.

[0043] Next, the calculation unit 27 calculates the characteristics of each crew member from the past biometric information acquired in step S10 (step S50). The crew member characteristics here are characteristics that the crew member exhibits in relation to driving, and include fatigue level, stress, recovery level, etc. FIG. 12 is a graph showing an example of changes in fatigue level or stress, which are characteristics of a specific crew member. This graph shows that the fatigue level or stress of this crew member changes for each delivery route.

[0044] Fig. 13 is a table showing the characteristics of each crew member for each delivery route, and is stored, for example, in the memory unit 28. When the calculation unit 27 obtains the data of Fig. 12 for each crew member obtained from each in-vehicle device 10, it calculates the characteristics of the crew member for each delivery route, and the memory unit 28 stores the characteristics in the format of the table of Fig. 13.

[0045] The table in Figure 13 lists five delivery routes, No. 1 to No. 5, and each delivery route is characterized by characteristics such as distance, whether loading and unloading is required, delivery mode, etc. Five crew members, Crew A to Crew E, have characteristics that cause them to feel high, medium, or low levels of fatigue or stress for each delivery route.

[0046] For example, crew member A has low fatigue and stress on delivery route No. 1, but medium fatigue and high stress on delivery route No. 5. Crew member C has medium fatigue and stress on delivery route No. 3, but low fatigue and high stress on delivery route No. 4. Crew member E has no experience of driving any of the delivery routes, so his fatigue and stress characteristics cannot be obtained.

[0047] The table in Figure 13 also includes the desired work style of each crew member. For example, crew member A's work type is a day trip and he / she wants to load and unload cargo (OK). Crew member B's work type is an overnight trip and he / she does not want to load and unload cargo (NG).

[0048] Next, the allocation unit 26 allocates crew members to any of the routes included in the delivery plan acquired in step S10 based on the accumulated fatigue levels calculated in step S40 and the characteristics of each crew member calculated in step S50, and creates a delivery plan with the crew members allocated (step S60). Figure 14 is a sub-flowchart (part 1) showing the content of step S60 in Figure 4, and Figure 15 is a continuation of Figure 14 and is a sub-flowchart (part 2) showing the content of step S60 in Figure 4. That is, the allocation unit 26 allocates crew members to routes in accordance with the procedures in Figures 14 and 15.

[0049] The allocation unit 26 acquires the accumulated fatigue levels of all crew members calculated in step S40 (step S61). The allocation unit 26 determines whether there are any crew members who need to take a day off (step S62), and if there are any crew members who need to take a day off (No in step S62), the allocation unit 26 sets the crew members who need to take a day off to a day off and removes them from the options (step S63).

[0050] If there are no crew members who require a day off (Yes in step S62), or after setting the crew members who require a day off as days off (step S63), the allocation unit 26 creates a delivery plan in descending order of the crew members' accumulated fatigue levels (step S64). The allocation unit 26 determines whether there are multiple crew members with the same accumulated fatigue level (step S65). If there are not multiple crew members with the same accumulated fatigue level (No in step S65), the allocation unit 26 refers to the table in FIG. 13, selects a delivery route with low stress-related characteristics for each crew member, and assigns that crew member to that route. This completes the creation of a delivery plan with crew members assigned (step S67).

[0051] If there are multiple crew members with the same accumulated fatigue level (Yes in step S65), the allocation unit 26 compares the stress-related characteristics of the crew members (step S68). The allocation unit 26 determines whether there are multiple crew members with the same stress-related characteristics (step S69). If there are not multiple crew members with the same stress-related characteristics (No in step S69), the allocation unit 26 refers to the table in FIG. 13, selects a delivery route with a low fatigue-related characteristic for each crew member, and allocates that crew member to the route (step S70). This completes the creation of a delivery plan with assigned crew members (step S67).

[0052] If there are multiple crew members with the same stress-related characteristics (Yes in step S69), the allocation unit 26 compares the fatigue-related characteristics of the crew members (step S71). The allocation unit 26 determines whether there are multiple crew members with the same fatigue-related characteristics (step S72). If there are not multiple crew members with the same fatigue-related characteristics (No in step S72), the allocation unit 26 refers to the table in FIG. 13, selects a delivery route so that the relationship between the crew member's desired work type and the delivery route distance is as follows, and allocates the crew member (step S73). Desired work type: Day trip → Distance: Short Desired work type: Overnight → Distance: Long This completes the creation of a delivery plan with crew members assigned (step S67).

[0053] If there are multiple crew members with the same fatigue-related characteristics (Yes in step S72), the allocation unit 26 compares the crew members' preferences regarding their work types (step S74). The allocation unit 26 determines whether there are multiple crew members with the same preferences regarding their work types (step S75). If there are not multiple crew members with the same preferences regarding their work types (No in step S75), the allocation unit 26 refers to the table in FIG. 13, selects a delivery route based on the crew members' preferences regarding whether or not they will load and unload, and allocates the crew members (step S76). That is, the allocation unit 26 allocates crew members who wish to load and unload (OK) to a delivery route with loading and unloading, and allocates crew members who do not wish to load and unload (NG) to a delivery route without loading and unloading. This completes the creation of a delivery plan with assigned crew members (step S67).

[0054] If there are multiple crew members with the same preference regarding the type of work (Yes in step S75), the allocation unit 26 compares the crew members' preferences regarding loading and unloading (step S77). The allocation unit 26 determines whether there are multiple crew members with the same preference regarding loading and unloading (step S78). If there are not multiple crew members with the same preference regarding loading and unloading (No in step S78), the allocation unit 26 selects a route according to the crew members' preferences regarding loading and unloading and allocates the crew members (step S79). That is, the allocation unit 26 allocates crew members who wish to load and unload (OK) to a delivery route with loading and unloading, and allocates crew members who do not wish to load and unload (NG) to a delivery route without loading and unloading. This completes the creation of a delivery plan with assigned crew members (step S67).

[0055] If there are multiple crew members with the same preferences for loading and unloading (Yes in step S78), the allocation unit 26 allocates the crew members to delivery routes in no particular order (step S80). The allocation unit 26 determines whether there are any delivery routes to which no crew members have been assigned (step S81). If there are no delivery routes to which no crew members have been assigned (No in step S81), the creation of a delivery plan with assigned crew members is completed (step S67).

[0056] If there is a delivery route to which no crew member has been assigned (Yes in step S81), it is assumed that there is a shortage of crew members, and the delivery plan will be reviewed again, taking into consideration measures such as changing the schedule or outsourcing (step S82).

[0057] Figure 16 is a table showing the delivery routes assigned by the allocation unit 26 to each crew member. Crew member A has a high level of accumulated fatigue, so he is assigned to a delivery route with a low load. Crew member B has a medium level of accumulated fatigue, so he is assigned to a delivery route with a medium load among the remaining delivery routes. Crew member C has a high level of accumulated fatigue and needs a day off, so he is on a day off and is not assigned to a delivery route. Crew member D has a low level of accumulated fatigue, so he is assigned to a delivery route with a high load. Crew members E and F have no past records of accumulated fatigue, so they are assigned to routes desired by the crew members or delivery routes with available space.

[0058] Finally, the communication unit 22 transmits the delivery plan to which the crew has been assigned to each vehicle-mounted device 10 (step S90). Note that if the delivery plan is reviewed again in step S82, the communication unit 22 may transmit to the vehicle-mounted device 10 a message indicating that there is no delivery plan to which the crew has been assigned.

[0059] As described above, the server 20 according to the embodiment includes at least a biometric information acquisition unit 23 that acquires biometric information of a driver, a delivery plan acquisition unit 25 that acquires a delivery plan, and an allocation unit 26 that determines whether to assign a driver to one of the delivery routes included in the delivery plan based on the driver's fatigue level. By allocating a driver to one of the delivery routes based on the driver's fatigue level, the driver's fatigue can be addressed, contributing to safe driving and improved work efficiency. Furthermore, the system can promote a reduction in driver turnover, thereby contributing to the profits of transportation businesses and the like.

[0060] Furthermore, the server 20 according to the embodiment may include a calculation unit 27 that can calculate a fatigue level using biometric information acquired during operation for a certain period of time in the past by the biometric information acquisition unit 23 (step S20). In this case, the allocation unit 26 can determine whether to assign a driver to any of the delivery routes included in the delivery plan based on the fatigue level calculated by the calculation unit 27 (step S60). This allows a driver to be assigned to any of the delivery routes depending on the fatigue level during past operation.

[0061] Furthermore, the server 20 according to the embodiment may include an operation data acquisition unit 24 that acquires operation data of the vehicle V during operation for a certain period of time, the operation data including at least one of on-duty time and driving time (step S20). In this case, the calculation unit 27 calculates an estimated fatigue level from the operation data, and the allocation unit 26 can determine whether to assign a crew member to one of the routes included in the delivery plan based on the calculated estimated fatigue level. This allows a crew member to be assigned to one of the routes according to the estimated fatigue level calculated based on operation data including either on-duty time or driving time. This allows for more appropriate allocation of crew members to delivery routes. However, acquisition of operation data by the operation data acquisition unit 24 is not essential, and the server 20 may calculate a fatigue level using only biometric information acquired by the biometric information acquisition unit 23 and assign crew members to delivery routes.

[0062] Furthermore, the calculation unit 27 can calculate the estimated fatigue level by taking into account the on-duty time and driving time in the operation data (step S30). This allows the estimated fatigue level to be calculated based on the on-duty time and driving time, and allows for more appropriate allocation of crew members to delivery routes. However, calculating the estimated fatigue level is not essential, and the calculation unit 27 may calculate only the fatigue level described above.

[0063] Furthermore, the calculation unit 27 may calculate an accumulated fatigue level from the biometric information during operation for a certain period of time and the calculated estimated fatigue level (step S40), and the allocation unit 26 may determine whether to allocate a crew member to any of the routes included in the delivery plan based on the accumulated fatigue level. This allows a crew member to be allocated to any of the routes depending on the accumulated fatigue level, thereby more appropriately allocating crew members to delivery routes. However, calculation of the accumulated fatigue level is not essential. The calculation unit 27 may, for example, calculate only the fatigue level or the estimated fatigue level described above.

[0064] The allocation unit 26 may determine the allocation by taking into account the characteristics of each crew member for each delivery route (steps S50, S60). This allows the crew member to be assigned to one of the routes depending on the crew member's characteristics, and allows for more appropriate allocation of crew members to delivery routes. However, it is not essential to take into account the crew member's characteristics. The allocation unit 26 may also assign crew members to routes based on, for example, the fatigue level, estimated fatigue level, or accumulated fatigue level described above.

[0065] The biometric information acquisition unit 23 can acquire biometric information for each operation performed by each of the multiple crew members on at least one route. In this case, the calculation unit 27 calculates the fatigue level for each route for each crew member, and the allocation unit 26 can determine the allocation for each route taking into account the fatigue level and characteristics of each crew member. This allows crew members to be assigned to one of the routes depending on the fatigue level and characteristics of the crew member for each route, making it possible to more appropriately allocate crew members to delivery routes.

[0066] The allocation unit 26 may allocate crew members in order of the accumulated fatigue level based on the accumulated fatigue level of each of the plurality of crew members (step S64). This allows the allocation of crew members in order of the accumulated fatigue level to any of the routes.

[0067] The operation management system 1 according to the embodiment is constructed from the above-described server 20 and the vehicle-mounted device 10 that collects at least biometric information, and the server 20 transmits a delivery plan in which a crew member is assigned to each route to the vehicle-mounted device 10 (step S90). This makes it possible to utilize the biometric information collected from the vehicle-mounted device 10 and to transmit a delivery plan to which a crew member has already been assigned to the vehicle-mounted device 10.

[0068] Although various embodiments have been described above with reference to the drawings, it goes without saying that the present invention is not limited to such examples. It is clear that a person skilled in the art can conceive of various modifications or alterations within the scope of the claims, and it is understood that these also naturally fall within the technical scope of the present invention. Furthermore, the components of the above-described embodiments may be combined in any manner without departing from the spirit of the invention.

[0069] Here, the features of the embodiments of the traffic management device, traffic management system, traffic management method, and traffic management program according to the present invention will be briefly summarized and listed below in [1] to

[11] .

[0070] [1] A biometric information acquisition unit (23) that acquires biometric information indicating a fatigue level of a driver during operation of a vehicle (V); a delivery plan acquisition unit (25) that acquires a delivery plan including one or more routes; an allocation unit (26) that determines whether to allocate the driver to any of the routes included in the delivery plan based on the fatigue level, Operation management device (server 20).

[0071] According to the traffic management device configured as described above in [1], by assigning a driver to a route based on the driver's fatigue level, it is possible to take care of the driver's fatigue and contribute to safe driving and improved work efficiency. It is also possible to promote a reduction in the driver turnover rate, which contributes to the profits of transportation companies, etc.

[0072] [2] A calculation unit (27) is provided that calculates the fatigue level using the biological information acquired by the biological information acquisition unit during driving during the certain period in the past, the allocation unit determines whether to allocate the driver to any of the routes included in the delivery plan based on the fatigue level calculated by the calculation unit. The traffic management device described in [1] above.

[0073] According to the traffic management device having the configuration described in [2] above, a driver can be assigned to one of the routes depending on the degree of fatigue during past operations.

[0074] [3] A driving data acquisition unit (24) is provided to acquire driving data of the vehicle during driving for the certain period, the driving data including at least one of a driving time and a driving time, the calculation unit calculates an estimated fatigue level from the operation data, the allocation unit determines whether to allocate the driver to any of the routes included in the delivery plan based on the estimated fatigue level. The traffic management device described in [2] above.

[0075] According to the operation management device having the configuration described in [3] above, a driver can be assigned to one of the routes according to the estimated fatigue level calculated based on operation data including either the on-duty time or the driving time.

[0076] [4] The calculation unit calculates the estimated fatigue level taking into account the restraint time and the driving time. The traffic management device described in [3] above.

[0077] According to the operation management device having the configuration described in [4] above, the estimated fatigue level can be calculated based on the on-duty time and driving time.

[0078] [5] The calculation unit calculates an accumulated fatigue level from the biological information during the certain period of operation and the estimated fatigue level, the allocation unit determines whether to allocate the driver to any of the routes included in the delivery plan based on the accumulated fatigue level. The traffic management device described in [3] or [4] above.

[0079] According to the traffic management device having the configuration described above in [5], a driver can be assigned to one of the routes depending on the degree of accumulated fatigue.

[0080] [6] The allocation unit determines allocation taking into account the characteristics of each crew member for each route. An operation management device according to any one of [1] to [5] above.

[0081] According to the traffic management device configured as described above in [6], a driver can be assigned to one of the routes depending on the driver's characteristics.

[0082] [7] The biometric information acquisition unit acquires the biometric information for each operation performed by each of the plurality of crew members on at least one route, the calculation unit calculates the fatigue level for each crew member for each route, the allocation unit determines allocation taking into account the fatigue level and characteristics of each crew member for each route. An operation management device according to any one of [2] to [5] above.

[0083] According to the operation management device having the configuration described above in [7], a driver can be assigned to one of the routes depending on the driver's fatigue level and characteristics for each route.

[0084] [8] The allocation unit allocates the crew members in order of the accumulated fatigue level based on the accumulated fatigue level of each of the plurality of crew members. The traffic management device described in [5] above.

[0085] According to the traffic management device configured as described above in [8], drivers with higher levels of accumulated fatigue are assigned to one of the routes.

[0086] [9] An operation management device according to any one of [1] to [8] above; an on-board device (10) that collects at least the biometric information and the operational data; The operation management device transmits a delivery plan in which a driver is assigned to each route to the in-vehicle device. Traffic management system (1).

[0087] According to the operation management system configured as described above in [9], it is possible to utilize the biometric information and operation data collected from the on-board device, and to transmit a delivery plan with a crew member already assigned to the on-board device.

[0088]

[10] Acquire biometric information indicating the fatigue level of the driver during vehicle operation; Obtain a delivery plan including one or more routes; determining whether to assign the driver to any of the routes included in the delivery plan based on the fatigue level; Operation management method.

[0089] According to the operation management method configured as above

[10] , by assigning a driver to one of the routes based on the driver's fatigue level, it is possible to care for the driver's fatigue and contribute to safe driving and improved work efficiency. It also contributes to reducing the driver turnover rate and contributing to the profits of transportation companies, etc.

[0090]

[11] A step of acquiring biometric information representing a fatigue level of a driver during operation of a vehicle; obtaining a dispatch plan including one or more routes; determining whether to assign the driver to any of the routes included in the delivery plan based on the fatigue level; An operation management program that causes a computer to execute the above.

[0091] According to the operation management program configured as described above in

[11] , by assigning a driver to a route based on the driver's fatigue level, it is possible to care for the driver's fatigue and contribute to safe driving and improved work efficiency. It also contributes to reducing the driver turnover rate and contributing to the profits of transportation companies, etc. [Explanation of symbols]

[0092] 1. Traffic management system 10 Onboard equipment 11 Control section 12 Speed ​​information acquisition section 13 Engine information acquisition unit 15 Biometric information acquisition unit 16 Communications Department 20 Server (operation control device) 21 Control section 22 Communications Department 23 Biometric information acquisition unit 24 Operation data acquisition unit 25 Delivery Plan Acquisition Department 26 Allocation Section 27 Calculation section 28 Memory section 30 Administrator PC V vehicle

Claims

1. a biometric information acquisition unit that acquires biometric information representing a fatigue level of a driver during operation of the vehicle; a delivery plan acquisition unit that acquires a delivery plan including one or more routes; an allocation unit that determines whether to allocate the driver to any of the routes included in the delivery plan based on the fatigue level, Operation control device.

2. a calculation unit that calculates the fatigue level using the biological information acquired by the biological information acquisition unit during driving during a certain period in the past, the allocation unit determines whether to allocate the driver to any of the routes included in the delivery plan based on the fatigue level calculated by the calculation unit. The operation management device according to claim 1.

3. an operation data acquisition unit that acquires operation data of the vehicle during operation for the certain period, the operation data including at least one of a restraining time and a driving time; the calculation unit calculates an estimated fatigue level from the operation data, the allocation unit determines whether to allocate the driver to any of the routes included in the delivery plan based on the estimated fatigue level. The operation management device according to claim 2.

4. the calculation unit calculates the estimated fatigue level taking into account the on-duty time and the driving time. The operation management device according to claim 3.

5. the calculation unit calculates an accumulated fatigue level from the biological information during driving for the certain period and the estimated fatigue level, the allocation unit determines whether to allocate the driver to any of the routes included in the delivery plan based on the accumulated fatigue level. The operation management device according to claim 3.

6. the allocation unit determines allocation taking into account the characteristics of each crew member for each route. The operation management device according to claim 1.

7. the biometric information acquisition unit acquires the biometric information for each operation performed by each of the plurality of crew members on at least one route; the calculation unit calculates the fatigue level for each crew member for each route, the allocation unit determines allocation taking into account the fatigue level and characteristics of each crew member for each route. The operation management device according to claim 2.

8. the allocating unit allocates the crew members in descending order of the accumulated fatigue level based on the accumulated fatigue level of each of the plurality of crew members, The operation management device according to claim 5.

9. The traffic management device according to any one of claims 1 to 8; an in-vehicle device that collects at least the biometric information; The operation management device transmits a delivery plan in which a driver is assigned to each route to the in-vehicle device. Operation management system.

10. Acquire biometric information that indicates the fatigue level of the driver during vehicle operation, obtaining a delivery plan including one or more routes; determining whether to assign the driver to any of the routes included in the delivery plan based on the fatigue level; Operation management method.

11. acquiring biological information representing a fatigue level of a driver during operation of a vehicle; obtaining a dispatch plan including one or more routes; determining whether to assign the driver to any of the routes included in the delivery plan based on the fatigue level; An operation management program that causes a computer to execute the above.

Images