Dispatch system and dispatch program
Patent Information
- Application Number
- JP2024104430
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Priority Date
- 2023-08-04
- Filing Date
- 2024-06-27
- Publication Date
- 2026-08-27
- Estimated Expiration
- 2044-06-27
AI Technical Summary
【0016】 本発明によれば、突発的な変更による負担を最小限に抑えつつ、乗務員への円滑な意思伝達を可能にした配車システム及び配車プログラムを提供することが可能になる。
Smart Images

Figure 0007911724000001 
Figure 0007911724000002 
Figure 0007911724000003
Abstract
Description
Technical Field
[0001] The present invention relates to a vehicle allocation system and a vehicle allocation program that provide information related to vehicle allocation plans in the transportation industry to crew members.
Background Art
[0002] In the transportation industry, vehicle allocation plans are often completely analog even now. As an example of a completely analog type, there is the use of a whiteboard commonly called a vehicle allocation board, and magnets indicating vehicles and business contents are attached to rectangular areas corresponding to crew members to be assigned.
[0003] However, with this method, the physical size of the whiteboard becomes a constraint, and the displayable vehicle allocation plan is limited. Specifically, it is difficult to create vehicle allocation plans for multiple days simultaneously or reuse past vehicle allocation plans. Also, mistakes such as lack of communication between multiple vehicle allocation staff are likely to occur. In addition, from the perspective of communication with drivers, it is necessary to print out shift schedules, roll call books, etc. on paper, but in a completely analog vehicle allocation plan using a whiteboard, there is an operation of directly transcribing the contents posted on the whiteboard, which requires a great deal of labor for such printing.
[0004] From the perspective of improving the problems of the completely analog type, an automatic vehicle allocation system in which AI formulates a vehicle allocation plan has been proposed. For example, in Patent Document 1, in order for drivers of transportation companies such as taxis, buses, and trucks, for which the installation of a tachograph is mandatory, to execute an operation plan while complying with the Labor Standards Law, a terminal, by executing software, has a function for an operation manager or a driver to create an operation plan from an operation schedule, and a function for calculating the required time of the operation plan created in the operation plan creation process from past operation information recorded in the terminal and determining whether the operation plan complies with the Labor Standards Law. By having AI formulate a vehicle allocation plan, it becomes possible to reduce the burden on vehicle allocation staff.
Prior Art Documents
[0005] [Patent Document 1] Patent No. 4708500 [Overview of the project] [Problems that the invention aims to solve]
[0006] However, in recent years, the logistics industry has been required to adapt to the Kanban system, which delivers what is needed, when it is needed, and in the required quantity. Examples of adapting to the Kanban system include just-in-time (JST) deliveries from wholesalers and other transport sources to retail stores of major chains such as supermarkets, convenience stores, and drugstores. JST deliveries include large-volume deliveries requested several days in advance to coincide with regular or irregular sales, as well as last-minute deliveries requested the day before due to mismatches between expected demand and actual supply caused by factors such as weather changes.
[0007] Unlike inter-hub deliveries connecting large collection points or courier services following fixed routes within a defined area, the transportation industry primarily involves irregular transport from a base to numerous small delivery destinations without regularly scheduled routes. In such cases, changes to the vehicle dispatch plan due to requests for temporary deliveries occur frequently. Therefore, even after a vehicle dispatch plan is thought to be finalized, unexpected changes often occur afterward.
[0008] The AI-powered automated dispatch system exemplified in Patent Document 1 typically requires increasing computational and time resources as the number of destinations increases. Therefore, in such business operations, there is a concern that the AI-powered automated dispatch system may be unable to cope with requests for temporary deliveries because the required computational load exceeds the system's capacity and requires an enormous amount of time. In addition, the AI-powered automated dispatch system has a user interface that is significantly different from a traditional dispatch board, making it difficult for dispatchers who use conventional dispatch schedules to become proficient in it.
[0009] On the other hand, with traditional analog dispatch systems using whiteboards, even if there are sudden changes, the dispatcher can simply change the tags on the whiteboard or attach sticky notes, making it easier to respond flexibly to sudden changes compared to AI-driven automated dispatch. However, as mentioned above, the burden on the dispatcher remains significant with analog dispatch systems.
[0010] The present invention aims to provide a dispatch system and dispatch program that minimize the burden on dispatchers due to sudden changes in dispatch plans, while enabling smooth communication with drivers. [Means for solving the problem]
[0011] To achieve the above objective, the present invention comprises the following configuration.
[0012] (1) At least one terminal capable of displaying the dispatch plan (for example, electronic board 10, operation management terminal 101, logistics office in-vehicle terminal 102, driver terminal 103, in-vehicle terminal 104), The system includes a management device (for example, management device 20) that performs various processes in response to input operations on at least one of the terminals, The aforementioned control device is A placement operation receiving unit (for example, a placement operation receiving unit 208) receives information on the operation in which a dispatcher operates one of the at least one terminals to move at least one type of tag image selected from a first tag image provided for each of the names of the drivers included in the dispatch plan, a second tag image provided for each of the vehicles the drivers are riding in, and a third tag image provided for each of the delivery destinations, and places the tag images in the fields for inputting the driver, the vehicle, and the delivery destination. A dispatch plan creation unit (for example, a dispatch plan creation support unit 204) creates the dispatch plan based on the information received by the dispatch operation receiving unit, An information display control unit (e.g., driver information display control unit 206) displays dispatch information, including the dispatch plan created by the dispatch plan creation unit, on an electronic board (e.g., electronic board 10) among the at least one terminal that allows input by touch operation, and It has, The management device further includes an individual information receiving unit (for example, an individual information receiving unit 209) that receives individual information addressed to one or more of the multiple crew members entered by the dispatcher, The information display control unit displays the individual information on the electronic board at a predetermined timing along with the dispatch plan for the corresponding crew member. Vehicle dispatch system.
[0013] According to (1), since the dispatch plan is created by moving the tag images and placing them in the dispatch plan items, it is possible to retain the feel of creating a dispatch plan using a traditional whiteboard, and the dispatcher can change the dispatch plan early by operating it, allowing for flexible response to sudden changes. Moreover, since the information addressed to each driver entered by the dispatcher is displayed on the display unit, it becomes possible to communicate smoothly between the dispatcher and the driver.
[0014] (2) In (1), The management device is a dispatch system further comprising a clock-in time stamping unit (for example, a clock-in time stamping unit 207) that stamps the clock-in time when the driver performs a predetermined operation via the electronic board when clocking in.
[0015] According to (2), since the crew members will always look at the display on the screen when they arrive at work, it will be possible to reliably transmit information addressed to the crew members when they arrive at work. This will enable smooth communication between dispatchers and crew members. [Effects of the Invention]
[0016] According to the present invention, it becomes possible to provide a vehicle dispatching system and a vehicle dispatching program that enable smooth communication of information to the crew while minimizing the burden caused by sudden changes.
Brief Description of the Drawings
[0017] [Figure 1] FIG. 1 is an explanatory diagram showing the configuration of a vehicle dispatching system 1 in an embodiment of the present invention. [Figure 2] FIG. 2 is a block diagram showing the electrical configuration of the vehicle dispatching system 1. [Figure 3] FIG. 3 is an example of a crew database 211. [Figure 4] FIG. 4 is an example of a vehicle information database 212. [Figure 5] FIG. 5 is an example of a delivery destination information registration unit 213. [Figure 6] FIG. 6 is an example of a work information registration unit 214. [Figure 7] FIG. 7 is an example of a dynamic information storage unit 215. [Figure 8] FIG. 8 is an example of a vehicle dispatching information storage unit 216. [Figure 9] FIG. 9 is a main flowchart showing an example of a preferred flow of management processing executed by the management device 20. [Figure 10] FIG. 10 is a continuation of FIG. 9. [Figure 11] FIG. 11 is a flowchart showing an example of a preferred flow of vehicle dispatching processing executed by a terminal that executes a vehicle dispatching program. <00001 [Figure 17] Figure 17 is a flowchart showing an example of a preferred flow of the residual calculation process performed by the management device 20. [Figure 18] Figure 18 is a flowchart that continues from the previous figure. [Modes for carrying out the invention]
[0018] Embodiments of the present invention will be described in detail below with reference to the drawings.
[0019] Figure 1 is an explanatory diagram showing the configuration of the dispatch system 1 in one embodiment of the present invention.
[0020] [Configuration of Dispatch System 1] The dispatch system 1 comprises an electronic board 10 and a management device 20. The management device 20 is communicated via a network 100 with the operation management terminal 101, the logistics office terminal 102, the driver terminal 103, the in-vehicle terminal 104, and the electronic board display control device 105, etc. The type of network 100 is not particularly limited as long as it enables the management device 20 to communicate with the operation management terminal 101, the logistics office terminal 102, the driver terminal 103, the in-vehicle terminal 104, and the electronic board display control device 105, etc. Examples of the type of network 100 include the internet, a mobile phone network, a wireless LAN, etc.
[0021] The electronic board 10 is a large display of 50 inches or more, also known as a digital whiteboard or electronic blackboard. The electronic board 10 electrically displays dispatch information to be communicated to the crew. The electronic board 10 replaces the whiteboards that were conventionally used to display dispatch information and is capable of large-screen display.
[0022] Electronic boards are known to include touch display type, projector type, and unit type. In this embodiment, they are not particularly limited as long as they are touch panel type that can be operated by the dispatcher. In that respect, the electronic board 10 may be a touch display type or a unit type in which a touch panel is retrofitted to an existing display. The projector type is undesirable because it does not have a touch panel function.
[0023] The management device 20 corresponds to the server that controls the dispatch system 1 and performs various processes in response to input operations on the electronic board 10.
[0024] The management device 20 corresponds to the server that manages the dispatch system 1 and executes various processes in response to input operations on the electronic board 10. The management device 20 may be a physical server built by the logistics company itself, or a cloud server built by the provider that provides the dispatch system 1. However, considering the convenience for the logistics company, management costs, and the degree to which it can handle increases in scale and usage load (scalability), it is preferable for the management device 20 to be a cloud server.
[0025] In the following explanation, the management device 20 is assumed to be a cloud server, but it is not limited to this. The management device 20 may be any device that has the functionality to perform various processes in response to input operations on terminals such as the electronic board 10, the operation management terminal 101, the logistics office terminal 102, the crew terminal 103, the in-vehicle terminal 104, and the electronic board display control device 105.
[0026] The management device 20 generates dispatch information based on information transmitted from the operation management terminal 101, the logistics office terminal 102, the crew terminal 103, the in-vehicle terminal 104, and the electronic board display control device 105, and displays this dispatch information on the electronic board 10. The management device 20 also stores various data necessary for generating the dispatch information.
[0027] The operation management terminal 101 is a terminal operated by the operations manager. Preferably, the operation management terminal 101 is placed in a location that is visible from the electronic board 10 and is configured to communicate with the electronic board 10 via a network used for relatively short-distance communication, such as a local area network, intranet, or wireless LAN, using wiring without cascading connections via multiple switching hubs. With the above arrangement, the dispatch system 1 enables close communication between the crew and the operations manager. Furthermore, with the above arrangement and communication means, the dispatch system 1 can reduce the risk of communication between the operation management terminal 101 and the electronic board 10 being leaked via an external source. In particular, a local area network using wiring without cascading connections offers excellent cost-effectiveness in terms of establishing communication and communication speed, as well as superior confidentiality in preventing information leakage due to radio wave interception, and enables high-speed communication via the local area network without the speed reduction caused by cascading connections. Furthermore, wireless LAN and Bluetooth are easy to install retrofit, reducing the risk of drivers, dispatchers, etc., tripping over cables such as local area network cables, and eliminating the need for construction work such as raising the floor to avoid overhead wiring in order to prevent the aforementioned risks.
[0028] The logistics office terminal 102 is operated by the person in charge of the logistics office. When the person in charge of the logistics office operates the logistics office terminal 102, the logistics office terminal 102 transmits vehicle information associated with the vehicle that delivered the goods, delivery destination information such as the delivery address, and package information such as the contents of the package to the management device 20.
[0029] The crew terminal 103 is a terminal operated by the vehicle's crew. When a crew member operates the crew terminal 103, the crew terminal 103 transmits things like leave requests.
[0030] The types of the operation management terminal 101, the logistics office terminal 102, and the crew terminal 103 are not particularly limited. These terminals 101, 102, and 103 may take any form, such as a desktop computer, a laptop computer, a tablet computer, or a smartphone. The operation management terminal 101 is preferably a desktop computer or a laptop computer, prioritizing ease of operation, while the logistics office terminal 102 and the crew terminal 103 are preferably tablet computers or smartphones, prioritizing portability.
[0031] The in-vehicle terminal 104 is a so-called digital tachograph that is installed in the vehicle and transmits vehicle operation data to the management device 20 in real time. The operation data includes information such as the vehicle's location, status (driving, working, resting, etc.), and sudden braking and steering. The vehicle operation data transmitted from the in-vehicle terminal 104 may be stored in an internal or external cloud of the management device 20, allowing the management device 20 to retrieve the vehicle operation data from the cloud.
[0032] The electronic board display control device 105 has the function of controlling the display on the electronic board 10 in response to commands from the management device 20, and also has the function of transmitting operation information to the management device 20 in response to touch panel operation on the electronic board 10. The type of electronic board display control device 105 is not particularly limited, but as long as the electronic board display control device 105 has these functions, it is sufficient, and considering the installation area, introduction cost and maintenance cost, the electronic board display control device 105 is preferably a small desktop computer (also called a small PC or mini PC).
[0033] Figure 2 is a block diagram showing the electrical configuration of the dispatch system 1. The electronic board 10 comprises a control unit 11, a display unit 12, and a touch panel unit 13.
[0034] The control unit 11 drives and controls the display unit 12 based on dispatch information received from the management device 20 via the electronic board display control device 105. The control unit 11 also transmits input signals from the operation of the touch panel unit 13 to the management device 20 via the electronic board display control device 105.
[0035] The size of the display unit 12 is not particularly limited, but it is preferable to have a size of 75 inches or larger from the viewpoint of minimizing the burden on dispatchers due to sudden changes in the dispatch schedule. The resolution of the display unit 12 is also not particularly limited, but from the viewpoint of being able to display relatively small characters and retaining as much of the convenience of the conventional analog type of dispatch schedule as possible, the resolution of the display unit 12 is preferably 2K (1920dpi x 1080dpi, also called Full HD, etc.) or higher, more preferably WQHD (Wide Quad-HD, 2560dpi x 1,440dpi) or higher, and particularly preferably 4K (3840dpi x 2160dpi) or higher.
[0036] The touch panel unit 13 is positioned on top of the surface of the display unit 12, and coordinate information of the touch operation performed by the crew on the touch panel unit 13 is transmitted from the control unit 11 to the management device 20. The touch panel unit 13 may be pre-installed, as in a touch display type electronic board, or it may be added later, as in a unit type electronic board.
[0037] The electronic board 10 displays the dispatch board screen and the dispatch plan screen, starting from the top screen.
[0038] The top screen displays a menu screen for switching between screens such as the dispatch board screen and the dispatch planning screen. Furthermore, the electronic board 10 displays various alerts and to-do lists. The dispatch board screen displays the dispatch schedule, which includes the assigned tasks and delivery routes for the drivers. The dispatch planning screen is for creating the dispatch schedule, and displays a format with various items for creating the dispatch schedule, as well as a menu screen to assist in creating the dispatch schedule.
[0039] The management device 20 includes a control unit 200 that controls the entire management device 20, and a storage unit 210 that stores programs and data necessary for operating the control unit 200.
[0040] The control unit 200 is equipped with a processor (PU, Processing Unit, arithmetic processing unit) that performs various processes. By executing programs stored in the memory unit 210, the control unit 200 enables the management device 20 to function as a dynamic management unit 201, a vehicle management unit 202, a working hours management unit 203, a dispatch plan creation support unit 204, a roll call record creation unit 205, a crew information display control unit 206, and a clock-in time stamping unit 207.
[0041] Furthermore, the storage unit 210 includes a crew database 211 for registering crew information, a vehicle information database 212 for registering vehicle information, a delivery destination information registration unit 213 for registering delivery destination information, a work information registration unit 214 for registering work information, a dynamic information storage unit 215 for storing vehicle location information and status information transmitted from the in-vehicle terminal 104, a dispatch information storage unit 216 for storing dispatch board data, including past data, and a display information storage unit 217 for storing display information corresponding to various items in the dispatch information displayed on the electronic board 10, and display information to be displayed when the display information is touched.
[0042] The crew database 211 stores information such as the crew member's employee number, name, driver's license expiration date, date of birth, photograph, length of service, and accident-free period. The length of service and accident-free period are automatically updated at the start of each new day or year.
[0043] Figure 3 shows an example of the crew database 211. In the example shown in Figure 3, the crew name "Yamada Taro", driver's license expiration date "August 31, 2024", date of birth "August 31, 19△△", facial photograph, years of service "△ years", accident-free period "△ years", etc., are associated with employee number "0010". As a result, the management device 20 can display this information on the dispatch board screen. Furthermore, the management device 20 can perform tasks such as sending driver's license renewal notices and calculating bonuses based on years of service and accident-free periods.
[0044] The vehicle information database 212 stores vehicle type, weight, vehicle contract information, and vehicle repair information. Vehicle contract information includes, for example, the vehicle inspection expiration date. Vehicle repair information includes, for example, the date of battery replacement or oil change.
[0045] Figure 4 shows an example of the vehicle information database 212. In the example shown in Figure 4, the vehicle type "4t truck", weight "△△t", vehicle contract information "vehicle inspection expiration date △△△△ / △△ / △△", vehicle repair information "battery replaced on △ / △, oil changed on △ / △", etc. are stored, associated with the vehicle number "1210 8...". As a result, the management device 20 can display this information on the dispatch board screen. Furthermore, this allows the management device 20 to send notifications regarding vehicle inspections, battery replacements, oil changes, etc.
[0046] The delivery destination information registered in the delivery destination information registration unit 213 is stored based on vehicle and cargo information from the logistics office terminal 102. The vehicle and cargo information includes the identification number assigned to the vehicle carrying the cargo, the contents of the cargo, the delivery destination, and the delivery route.
[0047] Figure 5 shows an example of the delivery destination information registration unit 213. In the example shown in Figure 5, the contents of the package, "Fruits and Vegetables," the delivery destination, "△△ Mart," and the delivery route, "I102," are stored, associated with the identification number "△△△." As a result, the management device 20 can display this information on the dispatch board screen.
[0048] The work information registered in the work information registration unit 214 is stored based on the work information from the logistics sales office terminal 102. Examples of work information include loading goods into vehicles.
[0049] Figure 6 shows an example of the work information registration unit 214. In the example shown in Figure 6, the work details "Loading cargo into the vehicle" and precautions for the work are stored, associated with the work number "Work 5". This allows the management device 20 to display this information on the dispatch board screen.
[0050] The dynamic information storage unit 215 stores vehicle operation data transmitted from the in-vehicle terminal 104, and in particular stores vehicle location information and status information from the start to the end of each driver's delivery work.
[0051] Figure 7 shows an example of the dynamic information storage unit 215. In the example shown in Figure 7, the vehicle location information "Month Day, Day Hours, Minutes, Seconds, GPS Coordinates (...)" and status information "No Abnormalities" are stored, associated with the vehicle identification number "△△△". As a result, the management device 20 can display this information on the dispatch board screen. Furthermore, as a result, the management device 20 can send notifications related to this information.
[0052] The dispatch information storage unit 216 stores dispatch board data. The dispatch board data includes information about the crew, information about the vehicle, information about delivery and other tasks, and information addressed to the crew.
[0053] Preferably, the dispatch board data stored in the dispatch information storage unit 216 includes information about the crew, such as arrival time, working hours, and information that can identify the crew member in the crew member database 211 (crew member information). This allows the management device 20 to display the above-mentioned information about the crew member, as well as information about the crew member stored in the crew member database 211, on the dispatch board. Furthermore, this allows the management device 20 to display information addressed to the crew member on the dispatch board at predetermined timings, such as when the crew member clocks in (arrival time).
[0054] Preferably, the dispatch board data stored in the dispatch information storage unit 216 includes vehicle-related information, such as information that can identify the vehicle in the vehicle information database 212 (vehicle information). This allows the management device 20 to display the vehicle-related information stored in the vehicle information database 212 on the dispatch board.
[0055] Preferably, the dispatch board data stored in the dispatch information storage unit 216 includes information related to delivery and other operations, such as information that can identify a delivery destination (delivery destination information) stored in the delivery destination information registration unit 213, and information that can identify an operation (operation information) stored in the operation information registration unit 214. This allows the management device 20 to display the delivery destinations stored in the delivery destination information registration unit 213 and the operations stored in the operation information registration unit 214 on the dispatch board.
[0056] Preferably, the dispatch board data stored in the dispatch information storage unit 216 includes information addressed to the crew (individual information), such as information on road conditions (road information), information on special services (special service information), and information on the work status of other crew members (work information). Information on work status includes, for example, information related to the crew member's working hours, break times, and leave. By including road information as individual information in the dispatch board data, the management device 20 can display road information on the dispatch board at a predetermined timing. This allows crew members to carry out deliveries in a reasonable manner based on road information. By including special service information as individual information in the dispatch board data, the management device 20 can display special service information on the dispatch board at a predetermined timing. This allows crew members to carry out deliveries not only corresponding to regular services already reflected on the dispatch board, but also based on information on special services that have not yet been reflected on the dispatch board. Regarding information on special services, the dynamic management unit 201 can display vehicles that are currently making deliveries or returning to the depot on the dispatch board screen. This allows delivery personnel to prevent disruptions to subsequent dispatches by replacing a scheduled vehicle with a similar vehicle that has returned to the depot earlier, if they anticipate that the scheduled vehicle will not return as planned and will affect the next dispatch. Since the dispatch board data includes work information as individual information, the management device 20 can display work information on the dispatch board at a predetermined time. This allows drivers to make adjustments while taking into account the work status of other drivers (e.g., working hours, break times, holidays, etc.) when making deliveries.
[0057] Figure 8 shows an example of the dispatch information storage unit 216. The example shown in Figure 8 includes dispatch board data for "crew member 9," such as crew member information including arrival time "7:30" and working hours "8:00," vehicle information such as vehicle "1210 8...", work information such as delivery destination information indicating that the first delivery (service 1) is "I01 course," and individual information such as a memo "Traffic jam near the entrance to Soka Station. An emergency delivery request is expected from Mr. / Ms. △△ in the early afternoon. Mr. / Ms. △△ is unable to respond due to sudden illness." As a result, the management device 20 can display the above-mentioned vehicle information and work information on the dispatch board, and also display the above-mentioned memo on the dispatch board at the time the arrival time is stamped, and communicate it to the crew member. Therefore, the crew member can confirm that there is traffic congestion, that they are expected to respond to an emergency delivery, and that there are crew members who are unable to respond, and based on this, they can proceed with the delivery work for "I01 course."
[0058] Furthermore, the example shown in Figure 8 includes data on the dispatch board for "Crew Member 26," such as crew member information including arrival time "8:00" and working hours "8:30," vehicle information such as vehicle "1188 3...", delivery destination information indicating that the first delivery (delivery 1) is "D02 course," work information indicating that the next work to be performed after delivery 1 is "work 05," and individual information such as a memo "Traffic congestion near Hachijo Shiratori and Asahimachi 2." As a result, the management device 20 can display the vehicle information and work information on the dispatch board, and also display the memo on the dispatch board at the time the arrival time is stamped, and communicate this to the crew member. Therefore, the crew member can confirm that there is congestion and proceed with the delivery related to "D02 course" based on this information.
[0059] Regarding the individual information stored in the dispatch information storage unit 216, in the example shown in Figure 8, the memo included in the dispatch board data for "crew member 9" contains the information, "Currently experiencing traffic congestion near the entrance to Soka Station. An emergency delivery request is expected from Mr. / Ms. △△ in the early afternoon. Mr. / Ms. △△ is unable to respond due to sudden illness." On the other hand, the memo included in the dispatch board data for "crew member 26" does not contain the above information, but instead contains different information, "Currently experiencing traffic congestion near Hachijo-Shiratori and Asahi-cho 2." In other words, the management device 20 can display different memos, created based on the differences in each crew member's delivery destination, work schedule, vehicle, etc., as individual information to each crew member.
[0060] Individual information may include not only information entered by dispatchers, etc., but also analysis results based on manually entered information, analysis results based on information obtained from vehicle radio communications, analysis results based on information obtained from the Fleet Management Unit 201, and information obtained from external traffic congestion information services, weather information services, etc.
[0061] The generation of individual information, including analysis results based on manually entered information, is achieved, for example, by a procedure that generates individual information including information such as traffic congestion and accidents manually entered by dispatchers or drivers, when such information is related to the driver's dispatch plan.
[0062] The generation of individual information, including analysis results based on information obtained from vehicle radio communications, can be achieved, for example, by obtaining the presence or absence of traffic congestion and the location of each vehicle from the voice recognition results and associated location information of the vehicle radio communications, and if traffic congestion is determined to be present, generating individual information that includes information indicating that traffic congestion is occurring in the place name corresponding to that location.
[0063] The generation of individual information, including analysis results based on information obtained from the Dynamic Management Unit 201, is achieved, for example, by obtaining the speed and location of each vehicle from the Dynamic Management Unit 201, determining that congestion is occurring at the location of any vehicle whose speed falls below a given threshold, and then generating individual information, including information that congestion is occurring at the place name corresponding to that location, if congestion is determined to be occurring.
[0064] The generation of individual information based on information obtained from external traffic congestion information services can be achieved, for example, by obtaining traffic congestion information (road information) from various traffic congestion information services such as public or private services, extracting traffic congestion information related to the delivery destination information and the course, and generating individual information that includes said traffic congestion information.
[0065] The generation of individual information based on information obtained from external weather information services can be achieved, for example, by obtaining weather information from various weather information services such as public or private services, extracting weather information related to the course of delivery destination information, and generating individual information that includes such weather information.
[0066] Returning to the explanation of the control unit 200, the dynamic management unit 201 manages vehicle location, work progress, etc. in real time based on the operation data stored in the dynamic information storage unit 215. This enables coordination between the dynamic management service, which manages vehicle location and work progress, etc. in real time based on operation data, and the dispatch plan.
[0067] The vehicle management unit 202 manages vehicle contract information and vehicle repair information based on the vehicle information database 212. For example, when the vehicle inspection expiration date is approaching, it notifies the vehicle maintenance personnel. Vehicle contract information is updated, for example, when a vehicle inspection is performed, and vehicle repair information is updated, for example, when a battery is replaced or an oil change is performed. This enables coordination between the vehicle management service, which manages vehicle contract information and vehicle repair information, and the vehicle dispatch plan.
[0068] The time management unit 203 calculates the time a driver is on duty based on the status information stored in the dynamic information storage unit 215 after the driver has completed their delivery duties, and manages the time on duty for each driver. This enables coordination between the time management service, which manages the time on duty for each driver, and the dispatch plan.
[0069] The dispatch plan creation support unit 204 assists dispatchers in creating dispatch plans, and dispatchers create dispatch plans by operating the dispatch plan screen.
[0070] This section describes the procedure for creating a dispatch plan using the dispatch plan creation support unit 204. Before creating a dispatch plan, the following steps must be performed in advance: registering crew information in the crew database 211, registering vehicle information in the vehicle information database 212, registering delivery destination information in the delivery destination information registration unit 213, registering work information in the work information registration unit 214, and creating an email template. The creation of the email template is done to send the dispatch plan to each crew member via email, and can be done by the dispatch manager by operating the email template settings screen. In addition, a shift schedule that reflects the crew members' leave requests should be created in advance. The shift schedule can be created by the operations manager by operating the crew shift editing screen.
[0071] Preferably, the dispatch plan creation support unit 204 performs checks on labor-related laws and regulations and notifies the dispatch plan creator if the check results indicate a suspected violation of labor-related laws and regulations. This allows the management device 20 to reduce the workload of dispatchers and other personnel involved in checking labor-related laws and regulations. The check includes, for example, a procedure to determine whether the standard delivery time and working hours in the dispatch plan meet given constraints regarding working hours and rest times, based on the driver's leave application, monthly working hours, weekly working hours, and daily working hours. The standard delivery time is provided by a procedure using a given delivery time, a procedure using a given conditional delivery time determined according to various conditions such as traffic information (congestion information, accident information) and time of day, a procedure using a delivery time (calculated delivery time) calculated by a neural network or the like that has undergone machine learning based on actual delivery time, a procedure using an estimated required time obtained from an external traffic information service, and a procedure combining these procedures.
[0072] The dispatch plan creation support unit 204 displays a dispatch plan creation format and a menu screen on the electronic board 10 as a dispatch plan screen. Details of the dispatch plan will be described later, but the dispatch plan is a table where multiple dispatch plans are listed side by side, associated with reference numbers, and each dispatch plan has fields for entering the driver's name, vehicle name, delivery route or work name, etc. The menu screen displays images of tags with the driver's name written on them side by side.
[0073] The dispatch plan creation support unit 204 creates tag images of driver names, vehicle names, delivery routes, and work names based on the registered information in the driver database 211, vehicle information database 212, delivery destination information registration unit 213, and work information registration unit 214. The dispatch plan creation support unit 204 then places the created tag images of vehicle names, delivery routes, and work names into the vehicle name, delivery route, and work name fields in the dispatch plan table, and also places tag images with driver names listed on them in a menu screen. At this point, the dispatch plan creation support unit 204 analyzes the information in the dispatch information storage unit 216 to determine the most efficient delivery route, creates a tag image for the delivery route, and places that tag image into the dispatch plan table creation format.
[0074] The dispatch manager operates the dispatch planning screen, selects the tags of drivers deemed suitable considering vacations and other factors, moves them to the format, and rearranges or moves tags such as vehicle name, delivery route, and work name to create a dispatch plan.
[0075] The dispatch plan creation support unit 204 then creates a contact email for the crew members listed on the dispatch plan and sends the email to the crew member's terminal 103 via the operation of the operations manager. The crew member who sent the contact email then checks the dispatch plan. The contact email contains a URL to be specified upon confirmation, and when the crew member specifies this URL, information indicating that the crew member has approved the dispatch plan is sent from the crew member terminal 103 to the management device 20. When the management device 20 receives the information that the crew member has approved the dispatch plan, the dispatch plan creation support unit 204 reflects the crew member's approval in the dispatch plan. The operations manager requests confirmation from the operations manager once approval has been obtained from all crew members listed on the dispatch plan. The operations manager can view the dispatch plan before finalization and operates the dispatch plan screen to input instructions indicating that the dispatch has been finalized. Based on this instruction input, the dispatch plan creation support unit 204 creates a dispatch board for the crew to see. The data of the created dispatch board is stored in the dispatch information storage unit 216.
[0076] The roll call log creation unit 205 creates a roll call log based on the dispatch board information stored in the dispatch information storage unit 216. For details such as the names of the crew members and the vehicles they are riding in, it refers to the information stored in the crew database 211 and the vehicle information database 212. The roll call log creation unit 205 creates data in the roll call log format, including the names of the crew members on the day of work, the vehicle numbers they are riding in, and the details of their journey, and stores the roll call log reflecting this data in a designated area of the storage unit 210. This allows the person in charge of roll calls to download the roll call log from the management device 20 by operating their terminal. The person in charge of roll calls then fills in various confirmation items in the roll call log during the roll call. As a result, the person in charge of roll calls no longer needs to handwrite the names of the crew members and details of their journey in the roll call log, thus reducing the workload for the person in charge of conducting roll calls with crew members before and after their shifts.
[0077] The crew information display control unit 206 controls the display unit 12 to display information addressed to crew members that has been entered by operating the touch panel unit 13, or information addressed to crew members that has been transmitted to the management device 20 via the network. The information is displayed when the crew member to whom the information is addressed touches the display item for arrival time or work time. In addition, if timing information such as a date that specifies the display timing is associated with the information addressed to the crew member, the information is displayed when the crew member touches the display item for arrival time or work time after the time specified in the timing information has elapsed. Information addressed to crew members may be, for example, traffic information entered by dispatchers, office staff, other crew members, etc. Since the time that a single crew member spends looking at the display is at most a few tens of seconds, the information addressed to crew members may be displayed in a large size that covers the schedule of other crew members for the day. Furthermore, if a facial recognition device or fingerprint recognition device is connected to the management device 20, and the crew member's identity is verified by facial recognition or fingerprint recognition, information addressed to the crew member may be displayed on the display unit 12.
[0078] The clock-in time stamping unit 207 controls the clock 21c at the time the driver touches the clock-in time item displayed on the dispatch board screen when the driver reports to work, and displays the clock-in time in the clock-in time item.
[0079] The placement operation receiving unit 208 controls the dispatching officer to operate one of at least one terminals (e.g., electronic board 10, operation management terminal 101, etc.) to move at least one type of tag image selected from the first tag image provided for each of the crew names included in the dispatch plan, the second tag image provided for each of the vehicles the crew members are riding in, and the third tag image provided for each of the delivery destinations, and to receive information about the operation to place the tag image in the fields for inputting crew members, vehicles, and delivery destinations.
[0080] The individual information receiving unit 209 controls the reception of individual information addressed to one or more crew members from among multiple crew members entered by the dispatcher using at least one terminal (e.g., electronic board 10, operation management terminal 101, etc.).
[0081] [Main flowchart of management process] Figure 9 is a main flowchart showing an example of a preferred flow of management processing performed by the management device 20. Figure 10 is a continuation of Figure 9. The following is an example of a preferred flow of management processing performed by the management device 20, using Figures 9 to 10.
[0082] [Step S1: Display the dispatch plan] The control unit 200, in cooperation with the storage unit 210 and the like, executes the crew information display control unit 206 (information display control unit 206). The control unit 200 then uses the information display control unit 206 to display the dispatch plan, indicated by the dispatch board data stored in the dispatch information storage unit 216, on the electronic board 10 or the like (step S1, dispatch plan display step). The control unit 200 then moves the process to step S2.
[0083] The dispatch plan display step includes a procedure for displaying a first tag image for each of the driver names included in the dispatch plan, a second tag image for each of the vehicles the driver is riding in, and a third tag image for each of the delivery destinations in a predetermined area. The first, second, and third tag images are displayed in such a way that they can be moved by operation via various input devices such as a mouse or touch panel.
[0084] In the dispatch plan display step, the targets for which display commands are issued include the electronic board 10, the operation management terminal 101, the logistics office terminal 102, the driver terminal 103, etc. Commands for display on the electronic board 10 are issued, for example, via the electronic board display control device 105, which controls the display on the electronic board 10.
[0085] [Step S2: Determine if operation information has been received] The control unit 200, in cooperation with the storage unit 210 and the like, executes the placement operation receiving unit 208. The control unit 200 then performs a process to determine whether it has received operation information from the placement operation receiving unit 208 (step S2, placement operation receiving step). If it determines that it has received the information, the control unit 200 moves the process to step S3. If it does not determine that it has received the information, the control unit 200 moves the process to step S6.
[0086] The operation information received in step S2 includes information on an operation to move at least one tag image selected from a first tag image provided for each driver name included in the dispatch plan, a second tag image provided for each vehicle the driver is riding in, and a third tag image provided for each delivery destination, and to place the tag image in the fields for inputting the driver, vehicle, and delivery destination. The operation to move the tag image is not particularly limited and may, for example, involve touching the starting and ending points of the movement, or it may involve dragging and dropping from the starting point to the ending point.
[0087] [Step S3: Update the dispatch board data] The control unit 200, in cooperation with the memory unit 210 and the like, executes the dispatch plan creation support unit 204 (dispatch plan creation unit). The control unit 200 then performs a process to update the dispatch board data stored in the dispatch information storage unit 216 based on the information received in the placement operation reception step (step S3, dispatch plan creation step). The control unit 200 then moves the process to step S4.
[0088] In the dispatch plan creation step, if information is received in the assignment operation reception step for an operation to place a first tag image in the field for inputting a crew member, the dispatch plan creation step updates the dispatch board data stored in the dispatch information storage unit 216 so that the crew member corresponding to the field for inputting a crew member becomes the crew member corresponding to the first tag image. In the dispatch plan creation step, if information is received in the assignment operation reception step for an operation to place a second tag image in the field for inputting a vehicle, the dispatch plan creation step updates the dispatch board data stored in the dispatch information storage unit 216 so that the vehicle corresponding to the field for inputting a vehicle becomes the vehicle corresponding to the second tag image. In the dispatch plan creation step, if information is received in the assignment operation reception step for an operation to place a third tag image in the field for inputting a delivery destination, the dispatch plan creation step updates the dispatch board data stored in the dispatch information storage unit 216 so that the delivery destination corresponding to the field for inputting a delivery destination becomes the delivery destination corresponding to the third tag image. If the type of tag image and the type of field do not match, the dispatch plan creation step does not update the dispatch board data stored in the dispatch information storage unit 216.
[0089] [Step S4: Determine if individual information has been received] The control unit 200, in cooperation with the storage unit 210 and the like, executes the individual information receiving unit 209. The control unit 200 then performs a process to determine whether it has received individual information addressed to one or more of the multiple crew members via the individual information receiving unit 209 (step S4, individual information receiving step). If it determines that it has received the information, the control unit 200 moves the process to step S5. If it does not determine that it has received the information, the control unit 200 moves the process to step S6.
[0090] [Step S5: Update individual information] The control unit 200, in cooperation with the memory unit 210 and the like, executes the dispatch plan creation support unit 204 (dispatch plan creation unit). The control unit 200 then performs a process to update the individual information stored in the dispatch information storage unit 216 based on the individual information received in the individual information reception step by the dispatch plan creation support unit 204 (step S5, individual information update step). The control unit 200 then moves the process to step S6.
[0091] [Step S6: Display the dispatch plan] The control unit 200, in cooperation with the storage unit 210 and the like, executes the information display control unit 206. The control unit 200 then executes a process to display the dispatch plan, which is shown by the dispatch board data updated by the above process, on the electronic board 10 or the like (step S6, dispatch plan redisplay step). The control unit 200 then moves the process to step S7.
[0092] In the dispatch plan redisplay step, the electronic board 10 that displays the completed dispatch information may be the same as or different from the terminal operated by the dispatcher. That is, the terminal that transmitted the operation information received in the deployment operation reception step may be the electronic board 10, or another terminal (such as the operation management terminal 101). However, it is generally assumed that this terminal is a different terminal from the electronic board 10 (such as the operation management terminal 101).
[0093] [Step S7: Determine if it is the predetermined timing] The control unit 200, in cooperation with the storage unit 210 and the like, executes the information display control unit 206. The control unit 200 then performs a process to determine whether it is the predetermined timing to display individual information using the information display control unit 206 (step S7, predetermined timing determination step). If it is determined that it is the predetermined timing, the control unit 200 moves the process to step S8. If it is not determined that it is the predetermined timing, the control unit 200 returns the process to step S1 and repeats the process from step S1 to step S11.
[0094] The "predetermined timing for displaying individual information" in the predetermined timing determination step is not particularly limited. For example, the predetermined timing may be the timing when the crew member to whom the information is intended touches the display item for arrival time or attendance time, or the timing when the crew member touches the display item for arrival time or attendance time after the time specified in the timing information has elapsed, in cases where timing information such as a date specifying the display timing is associated with the individual information.
[0095] [Step S8: Display individual information] The control unit 200, in cooperation with the storage unit 210 and the like, executes the information display control unit 206. The control unit 200 then uses the information display control unit 206 to perform a process that displays individual information corresponding to a predetermined timing related to a predetermined timing determination step on the electronic board 10 or the like (step S8, individual information display step). The control unit 200 then moves the process to step S9.
[0096] The manner in which individual information is displayed in the individual information display step is not particularly limited. For example, the display manner may include displaying the individual information in a large size that covers the schedule of other crew members for the day in order to make it easier to see, or displaying the individual information with a confirmation button.
[0097] [Step S9: Determine if the prescribed operation was performed] The control unit 200, in cooperation with the memory unit 210 and the like, executes the clock-in time stamping unit 207. The control unit 200 then uses the clock-in time stamping unit 207 to determine whether a specific operation related to the individual information displayed in the individual information display step occurred when the crew member clocks in (step S9, specific operation determination step). If it is determined that a specific operation occurred, the control unit 200 moves the process to step S10. If it is not determined that a specific operation occurred, the control unit 200 returns the process to step S1 and repeats the process from step S1 to step S11.
[0098] The specific operation determination step preferably includes a procedure for determining that a specific operation has occurred when information relating to a predetermined operation performed by a crew member upon arrival at work via the electronic board 10 or the like, related to the individual information displayed in the individual information display step, is received. Such operations include, for example, touching the arrival time item displayed on the dispatch board screen, or touching the confirmation button attached to the individual information displayed on the dispatch board screen. The predetermined operation determination step may also include a procedure for determining that a specific operation has occurred when a breath alcohol detector is used, or when an operation is performed to update the crew member attendance management information stored in the crew member database 211.
[0099] [Step S10: Clock in at work] The control unit 200 uses the attendance time stamping unit 207 to perform the process of stamping the attendance time for the crew member who performed a specific operation in the specific operation determination step (step S10, attendance time stamping step). The control unit 200 then moves the process to step S11.
[0100] The clock-in time stamping step includes a procedure for updating the clock-in time stored in the dispatch information storage unit 216. Preferably, the clock-in time stamping step also includes a procedure for attaching information to the individual information to indicate that it has been confirmed, so that dispatchers and others can determine whether the individual information displayed in the individual information display step has been confirmed.
[0101] [Step S11: End of displaying individual information] The control unit 200, in cooperation with the storage unit 210 and the like, executes the information display control unit 206. The control unit 200 then executes a process to terminate the display of the individual information displayed in the individual information display step by the information display control unit 206 (step S11, individual information display termination step). The control unit 200 returns the process to step S1 and repeats the process from step S1 to step S11.
[0102] The individual information display termination step prevents confirmed individual information from occupying the dispatch board screen for extended periods, making the screen difficult to view. In particular, if the display of personal information is such that it enlarges and covers the daily schedules of other drivers, the individual information display termination step will redisplay the schedules of the other drivers that were covered, making the dispatch board screen easier to view.
[0103] [Transmission step for dispatch program] The management device 20 executes a dispatch program transmission step, which transmits a program (dispatch program) to at least one terminal (e.g., electronic board 10, operation management terminal 101, etc.) capable of displaying the dispatch plan, causing it to execute a series of processes including at least the dispatch operation command step, the dispatch operation transmission step, and the individual information transmission step described later.
[0104] Figure 11 is a flowchart illustrating an example of a preferred workflow for dispatching a vehicle on a terminal running a dispatching program. The following is an example of a preferred workflow for dispatching a vehicle on a terminal running a dispatching program, using Figure 11.
[0105] (Step S101: Display dispatch plan) The terminal executing the predetermined program performs a process to display the dispatch plan based on the dispatch plan received from the management device 20 (step S101, dispatch plan display step). The terminal then moves the process to step S102.
[0106] (Step S102: Command the placement operation) The terminal executing the predetermined program performs a process in which the dispatcher operates at least one of the terminals to move at least one tag image selected from the first tag image provided for each of the driver names included in the dispatch plan, the second tag image provided for each of the vehicles the driver is riding in, and the third tag image provided for each of the delivery destinations, and places the tag images in the fields for inputting the driver, vehicle, and delivery destination (step S102, placement operation command step). The terminal then moves the process to step S103.
[0107] (Step S103: Send placement operation) The terminal executing the predetermined program performs a process to send the placement operation of the tag image, which was placed in step S102, to the management device 20 (step S103, placement operation transmission step). The terminal then moves the process to step S104.
[0108] (Step S104: Send individual information) The terminal executing the predetermined program performs a process to send individual information addressed to one or more crew members from among the multiple crew members entered by the dispatcher in step S102 to the management device 20 (step S104, individual information transmission step). The terminal then moves the process to step S105.
[0109] (Step S105: Determine if it is an electronic board) A terminal executing a predetermined program performs a process to determine whether the terminal is either an electronic board 10 or an electronic board display control device 105 that controls the display of the electronic board 10, that is, whether it is substantially an electronic board 10 (step S105, electronic board determination step). If it is determined to be an electronic board 10, the terminal moves the process to step S106. If it is not determined to be an electronic board 10, the terminal returns the process to step S101 and repeats the process from step S101 to step S106.
[0110] (Step S106: Control information display) The terminal executing the predetermined program performs a process to display dispatch information, including the dispatch plan created by the management device 20 based on the information transmitted in the dispatch operation transmission step, on the electronic board 10 of the at least one terminal described above that is capable of input by touch operation (step S106, information display control step). The terminal returns to step S101 and repeats the process from step S101 to step S106.
[0111] The information display control step is transmitted in the individual information transmission step and displays the individual information provided by the management device 20 on the electronic board 10 at a predetermined timing, along with the dispatch plan for the corresponding crew member.
[0112] Therefore, according to the dispatch program transmission step, the management device 20 can have at least one terminal execute a series of processes that provide the management device 20 with the dispatch operations related to the management process described above, and a series of processes that display the dispatch plan and individual information on the electronic board 10 related to the management process described above. Through these processes, the dispatch program enables smooth communication to the crew while minimizing the burden caused by sudden changes. Therefore, the management device 20 can work in cooperation with at least one terminal to realize a dispatch system 1 that enables smooth communication to the crew while minimizing the burden caused by sudden changes.
[0113] [Example of a dispatch board display] Next, we will explain an example of a dispatch board display, referring to Figures 12 and 13. Figures 12 and 13 are explanatory diagrams showing the dispatch board screen; Figure 12 shows an example of a vertical display, and Figure 13 shows an example of a horizontal display.
[0114] As shown in Figure 12, the vertically displayed dispatch board screen has items for each driver arranged horizontally, and each driver's item is associated with items indicating the driver's start time, the vehicle the driver is riding in (vehicle number), and the delivery destinations the driver will be traveling to using that vehicle. A table is then displayed with these items arranged vertically.
[0115] The section displaying each crew member shows the crew member's name and, if necessary, a photo of their face or an icon created by the crew member. The section for clock-in time displays the crew member's clock-in time. When a crew member clocks in and touches the clock-in time section, the time at that moment is displayed in the clock-in time section. In other words, the crew member's clock-in time is stamped on the electronic board 10.
[0116] The "Vehicle (Vehicle Number)" field displays the vehicle number assigned to the driver. The "Delivery Destination" field displays the order of the routes the driver will travel. In Figure 12, there are routes from "1ROUTE" to "6ROUTE," and the driver travels in the order of "1ROUTE" to "6ROUTE." For example, driver 48 would first travel the "J01 route" listed in 1ROUTE, and then the "C04 route" listed in 2ROUTE.
[0117] Furthermore, if there is any information (individual information) addressed to the crew member in question, that information is displayed on the electronic board 10. In the example shown in Figure 12, individual information for crew member 40, "7 / 7 10:00~12:00 Traffic restrictions on part of course D6 due to a relay race," is displayed so as to cover part of the information for crew members 21 and 26. This allows crew member 40 to easily check the individual information. In the example shown in Figure 12, crew member 40 touches the clock-in time displayed in their column to end the display of the individual information that was covering part of the information for crew members 21 and 26, and to clock in. Each driver spends only a few tens of seconds looking at the display, and the display of individual information ends as soon as the clock is punched in. Therefore, even if the information addressed to driver 40 is displayed so prominently that it covers the schedules of other drivers (drivers 21 and 26), drivers 21 and 26 can still easily check their respective schedules for the day after the display of individual information ends.
[0118] As shown in Figure 13, in the horizontal display screen, items for displaying each crew member are arranged vertically, and items for displaying arrival time, arrival time, vehicle number, delivery route, and memos are associated with the crew member items, and a table is displayed with these items arranged horizontally.
[0119] On the horizontally displayed dispatch board screen, instead of the "Work Time" and "Service 1" to "Service 6" items that were displayed on the horizontally displayed top screen, the following items are displayed: arrival time, arrival time, "Service 1" to "Service 3", and memo.
[0120] The "Arrival Time" field displays the time the crew member must arrive at work, the "Arrival Time" field displays the time the crew member must arrive at their assigned vehicle, and the "Notes" field displays any messages for the crew member.
[0121] Furthermore, the items displayed on the dispatch board screen can be freely customized. For example, in the vertically displayed dispatch board shown in Figure 12, it is possible to increase or decrease the number of deliveries displayed as a delivery route item, or to add items such as arrival time, arrival time, and memo.
[0122] [Example of a dispatch schedule display] Figure 14 is an explanatory diagram showing the display screen of the dispatch schedule. As shown in Figure 14, the display items of the dispatch schedule are the same as those of the dispatch board screen shown in Figure 13, but an item labeled "Confirmed" is set to the left of the arrival time item. This item is filled in when the driver has confirmed and approved the dispatch schedule via email. In addition, the right-hand area of the display unit 12 displays images of tags bearing the names of each driver.
[0123] In the dispatch schedule, the items for arrival time, arrival time, vehicle number, and route to the delivery destination are automatically entered based on the information registered in the delivery destination information registration unit 213 and the work information registration unit 214. The driver name is entered by the dispatcher. Specifically, the dispatcher touches a driver tag deemed appropriate for the job from the right-hand area of the display unit 12, drags it to the position of the driver name field, and then releases their finger (drag and drop), thereby entering the driver name specified by the dispatcher into the field. It is also possible to swap a designated driver tag with another driver tag by dragging and dropping it onto an already placed designated driver tag. In this case, the designated driver tag moves to the location where the other driver tag was. In addition, the vehicle number and delivery route are also written on the tag image, and the vehicle number and route tags can also be moved and swapped. In this way, the dispatch schedule displayed on the electronic board 10 mimics a conventional whiteboard dispatch board, allowing dispatchers to create the dispatch schedule in a similar manner to attaching magnetic tags with driver names and other information to a whiteboard.
[0124] The vehicle number display items are color-coded based on factors such as vehicle weight and inspection expiration date. Additionally, in the right-hand area where driver identification tags are displayed, the tags of the selected driver for the day are color-coded. Driver tags of those on leave may also be color-coded or excluded from the right-hand area. Delivery routes are also color-coded by route. This makes it easier for drivers to read the delivery schedule.
[0125] [Example of roll call log output] Figure 15 is an explanatory diagram showing the entire roll call log, and Figure 16 is a magnified view of the area enclosed by the dashed line in Figure 15. The roll call log (roll call record book) includes sections for recording pre-trip roll calls and post-trip roll calls.
[0126] The pre-trip roll call form includes fields for entry of reference number, number of days since the holiday, crew information, vehicle number, operation details, designated departure time, date, roll call time, roll call method, confirmation items, and the seal of the person conducting the roll call.
[0127] The crew information includes employee number, crew name, driver's license expiration date, accident-free period, years of service, and date of birth.
[0128] The flight details form allows you to list up to three flights.
[0129] The section for filling in confirmation items includes fields for alcohol test, body temperature, clothing, driver's license, forklift license status, safety helmet, personal belongings, safety slogan card, check for illness / fatigue and sleep deprivation, results of daily inspections, and other necessary information.
[0130] The alcohol test section includes fields for indicating whether a detector was used and for recording the test results. The fatigue section has general and special categories.
[0131] The post-shift roll call form includes fields for date, roll call time, roll call method, confirmation items, and the roll caller's seal.
[0132] The section for filling in confirmation items includes fields for alcohol testing, vehicle / road and operating conditions, personal belongings, whether there were any problems with pallet handling, other necessary information, and final delivery inspection. The alcohol testing section includes fields for whether a detector was used and for the test results. The final delivery inspection section includes fields for delivery completion and receipt confirmation.
[0133] The roll call log is created by the management device 20, based on the finalized dispatch schedule, by automatically inputting information from the crew database 211, the delivery destination information registration unit 213, and the work information registration unit 214 into the fields for the roll call log format, namely the reference number, crew information, vehicle number, operation details, dispatch time designation, and date, as shown in Figure 16.
[0134] [Functions of Dispatch System 1] As mentioned above, the electronic board 10 displays the top screen, dispatch board screen, and dispatch plan screen, but it also displays the following screens: driver shift output screen, driver shift editing screen, dispatch board switching group screen, driver master screen, vehicle master screen, shipper master screen, delivery destination master screen, route master screen, work master screen, classification master screen, display settings master screen, leave information settings screen, and email template settings screen.
[0135] Next, we will explain the various functions related to each display screen of the electronic board 10.
[0136] <Features related to the top screen> License Expiration 30 Days Before Expiration Alert Function: The top screen displays an alert showing the number of drivers whose licenses are expiring in less than 30 days. Clicking (or touching) the display label for this alert will take you to the driver master screen, which will initially display a list of drivers whose licenses are expiring in 30 days.
[0137] Vehicle Inspection Expiration Date 40 Days Before Alert Function: The top screen displays an alert showing the number of vehicles whose vehicle inspection expiration date is less than 40 days away. Clicking (or touching) the display label of this alert will take you to the vehicle master screen, which will initially display a list of vehicles whose vehicle inspection is 40 days away from expiration.
[0138] To-Do List Registration Function: By operating the touch panel unit 13 or the management device 20, a To-Do list with a specified date can be created, and the contents of the registered To-Dos can be viewed when creating a plan for the corresponding date on the dispatch plan screen. In addition, a PDF file (up to 1MB) can be uploaded to the management device 20 when registering, and the file can also be downloaded from the management device 20 on the dispatch plan screen.
[0139] News Release Function: This function is displayed on the top screen to notify users of system release information.
[0140] <Functions related to the dispatch planning screen> Screen display selection function: This function allows users to select the display layout of the dispatch schedule on the dispatch schedule screen from the following options: vertical display, 3 columns with 1 course, 3 columns with 3 courses, 2 columns with 5 courses, 3 columns with 3 courses (without vehicle class display), and 4 columns with 3 courses.
[0141] Plan Addition (New Creation) Function: This function allows you to create a new dispatch plan by specifying a date on the dispatch plan screen.
[0142] History Search (Duplicate Function): This function allows users to set a date or number of vehicles as a condition on the dispatch planning screen, display a list of past dispatch plans, and duplicate a selected past plan from this list. This function duplicates the arrival time, arrival time, vehicle, and route from past plans. Furthermore, this function is configured to allow users to choose whether or not to duplicate the drivers from past plans. This allows dispatchers to choose between two procedures for duplicating past dispatch plans: one that reduces the effort involved in dispatch planning by duplicating drivers excluding those on leave and leaving the corresponding fields blank, and another that does not duplicate drivers and leaves the corresponding fields blank, making it easier to match with work shift schedules.
[0143] Plan Save Function: This function allows you to save the dispatch plan you have created on the dispatch plan screen.
[0144] Batch Confirmation Function: This function allows you to confirm all created plans at once on the dispatch planning screen. However, if even one piece of data (such as arrival time, vehicle, driver, or route) is not set during the planning process, an alert will be displayed and batch confirmation will not be possible. If confirmed successfully, and if an email address is set in the driver master, the driver will be notified of the plan information via email.
[0145] Plan Deletion Function: This function deletes the dispatch plan data created for a specified date on the dispatch plan screen. Please note that this is a physical deletion and cannot be recovered.
[0146] Undo function: This function allows you to revert to the previous state if you have made a mistake in the settings of your dispatch plan on the dispatch plan screen.
[0147] Roll call log output function: This function allows users to output and download the dispatch plan for the relevant day, in accordance with the roll call log spreadsheet template specified for each user, from the dispatch planning screen.
[0148] Dispatch Board Output Function: This function allows users to output and download the dispatch plan for the relevant day, based on the dispatch board spreadsheet template specified for each user, from the dispatch planning screen.
[0149] Weather display function: This function stores the user's base code on the dispatch planning screen, retrieves weather information for the relevant day from the Japan Meteorological Agency, and displays it.
[0150] Selected Delete Function: On the dispatch plan screen, this function allows you to select one cell in the displayed dispatch plan and then press a button to discard the contents of the selected cell.
[0151] Drag-and-drop function: On the dispatch planning screen, vehicle and crew tags (data) can be moved or swapped between their respective columns or rows using drag-and-drop operations. For routes and tasks, tags can be moved or swapped between the route columns or rows using drag-and-drop operations. Movement or swapping can be done using a mouse on the management device 20 or by touching the electronic board 10 with a finger or other means. Tags can be selected from the schedule or from the crew, vehicle, route, and task menus on the right side of the screen, and then moved or swapped. When moving from the right side of the screen to the schedule, the corresponding tag in the menu on the right will be grayed out.
[0152] Plan Details Setting Function: This function allows you to enter plan details by double-clicking or double-tapping any cell in the relevant column or row on the vehicle dispatch plan screen.
[0153] Confirmation (Individual Confirmation) Function: This function allows you to confirm each individual plan (one row in horizontal display, one column in vertical display) within a plan on the dispatch plan screen. If there are any unset details such as arrival time, vehicle, driver, or route during the planning process, an alert will be displayed and confirmation will not be possible. If confirmation is successful, and an email address is set in the driver master, the driver will be notified of the plan information via email.
[0154] Confirmation function: By clicking the URL in the email sent to the driver to display the mobile site, and after confirming the arrival time, vehicle, route, etc., pressing the confirmation button, the arrival time for the corresponding plan on the dispatch plan screen will change from red to black, and the dispatch manager will know that the driver has confirmed the information.
[0155] Duplicate Alert Function in the Dispatch Planning Screen: If vehicle, driver, flight (route), or work tag (data) is duplicated when set via drag-and-drop or through the detailed settings dialog within the dispatch planning table, this function displays an alert indicating the duplication and allows the user to confirm if there is a problem. If there is no problem, the setting can be left as is.
[0156] 7-Day Consecutive Work Alert Function: On the dispatch planning screen, when setting driver tags (data) by drag-and-drop within the dispatch plan table or through the detailed settings dialog, this function displays an alert if the driver has worked for 7 consecutive days, allowing the user to confirm if there are any issues. If there are no issues, the setting can be proceeded with.
[0157] Vacation Schedule Driver Setting Alert Function: In the dispatch planning screen, when setting driver tags (data) by drag-and-drop within the dispatch plan table or through the detailed settings dialog, this function displays an alert if the driver is scheduled to take vacation on the relevant day, allowing the user to confirm if there are any issues. If there are no issues, the setting can be proceeded with. Driver shift information is registered from the shift editing section in driver management.
[0158] Driver License Setting Alert Function: In the dispatch planning screen, when setting driver tags (data) by dragging and dropping within the dispatch plan table or through the detailed settings dialog, this function displays an alert and prevents the setting if the qualifications held by the relevant driver do not match the type of license and transmission required for the vehicle.
[0159] License Expiration Date Alert Function: In the dispatch planning screen, when setting driver tags (data) by drag-and-drop within the dispatch plan table or through the detailed settings dialog, this function displays an alert if the driver's license expires on the specified date, preventing the setting from being completed. Note that the alert will still be displayed for up to one month after the driver's birthday, but dispatching will still be possible.
[0160] Maintenance Vehicle Setting Alert Function: In the dispatch planning screen, when setting vehicle tags (data) by dragging and dropping within the dispatch plan table or through the detailed settings dialog, this function displays an alert if the vehicle is scheduled for maintenance on the specified day, allowing the user to confirm if there are any issues. If there are no issues, the setting can be completed as is.
[0161] Vehicle Inspection Expiry Alert Function: In the dispatch planning screen, when setting vehicle tags (data) by dragging and dropping within the dispatch plan table or through the detailed settings dialog, this function displays an alert if the vehicle's inspection expires on the specified date, preventing the setting from being completed.
[0162] Exclusive Control Function: In the dispatch planning screen, if the date selected in the dispatch plan is already in use by another dispatcher, the screen will be displayed in a special mode, and the plan cannot be changed.
[0163] Display Group-Based Setting Function: This function allows you to switch between display groups in the menu on the right side of the dispatch plan screen, enabling you to create dispatch plans for each group. The maximum number of groups that can be switched is five, and the group settings are configured in the Dispatch Board Switching Group section of Master Maintenance.
[0164] <Functions related to the dispatch board screen> Dispatch Board Screen Display Selection Function: On the dispatch board screen, similar to the dispatch plan, you can select the display layout from vertical display, 3 columns with 1 course, 3 columns with 3 courses, 2 columns with 5 courses, 3 columns with 3 courses (without vehicle class display), and 4 columns with 3 courses, and display the plan created on the dispatch plan screen. Only plans that have been finalized for the current day will be displayed. Initially, the plan for the current day will be displayed. The date can be changed by operating the arrows displayed on either side of the date. It is also possible to set a switch time from the current day to the next day's dispatch plan for each usage location, and the system will automatically switch to the next day's plan when that time arrives.
[0165] Driver attendance setting function: On the dispatch board screen, when a driver taps their own cell in the displayed dispatch plan, the background color changes from pink to white, indicating that they have arrived at work.
[0166] Crew Member Icon Display Function: On the dispatch board screen, only for locations where vertical display is selected, it is possible to display icons registered for each crew member in the crew member master on the dispatch board.
[0167] Sticky note display function: This function allows users to access the sticky note editing screen on the dispatch board screen, write information on a sticky note, and then place the sticky note at any desired location on the dispatch board screen.
[0168] Spreadsheet Output Function: This function outputs the shift information of drivers for the specified month and year to a spreadsheet file on the driver shift output screen. A blank row is output when the dispatch group changes.
[0169] Template Download Function: This function allows you to download a spreadsheet template for bulk registration of shift information on the crew shift editing screen. If the target year and month, crew information, and shift information are already registered, you can download the template with the shift information already set.
[0170] Shift Upload Function: This function allows users to upload crew shift information to a downloaded spreadsheet template and then register it all at once on the crew shift editing screen.
[0171] Approval Function: This function allows administrators to approve shift information submitted by crew members via mobile devices on the crew shift editing screen. Approval can be done individually or in bulk.
[0172] Group Registration Function: This function allows you to register master data that enables switching screens in groups set in the dispatch plan and dispatch board settings within the dispatch board switching group. Up to 5 groups can be registered per location.
[0173] Driver ID Registration Function: This function allows you to register driver IDs (data) used in dispatch planning on the driver master screen, and also allows you to check delivery destinations for which the relevant driver is unavailable.
[0174] Vehicle Tag Registration Function: This function allows you to register vehicle tags (data) to be used in dispatch planning on the vehicle master screen, and you can specify the text color, background color, and frame color of the tags.
[0175] Shipper Registration Function: This function allows you to register shippers who will be the parent of the freight (course) master on the shipper master screen.
[0176] Delivery Destination Information Registration Function: This function allows you to register delivery destination information on the delivery destination master screen. From this screen, you can also set drivers who are not allowed to deliver to a particular destination, or vehicles that are not suitable due to their size or other factors.
[0177] Delivery Tag Registration Function: This function allows you to register delivery tags (data) to be used in dispatch planning on the delivery (course) master screen. From this screen, you can specify the text color, background color, and frame color of the tags, and you can also set the parent shipper and the delivery destinations included in the course.
[0178] Work Tag Registration Function: This function allows you to register work tags (data) used in dispatch planning on the work master screen. From this screen, you can specify the text color, background color, and frame color of the tags.
[0179] Category Management Registration Function: This function allows users to register master data for managing categories used for each screen or function on the Category Master screen.
[0180] Display settings function: This function, available on the display settings master screen, allows users to register settings such as announcements to be displayed in the dispatch plan, the switching time for the dispatch board, and whether or not to send email notifications upon confirmation.
[0181] Individual Leave Information Setting Function: While the shift editing screen allows for overall shift editing, individual leave information settings can be used to register and edit leave information for specific employees.
[0182] The email template setting function allows users to register and edit the sender, copy, and email body of emails sent for confirmation notifications or leave requests, all within the email template setting screen.
[0183] Breath alcohol detector linkage function: The system receives detection results from the breath alcohol detector and issues a warning on the dispatch board screen, etc., if alcohol is detected. Preferably, this function also includes a function that determines that it is a predetermined time to display personal information when a detection result indicating that no alcohol was detected is received. This allows drivers to check their individual information when they use the breath alcohol detector before their shift, without having to perform any additional operations related to the display of individual information. Preferably, the breath alcohol detector is placed in a location that is visible from the electronic board 10 and is configured to communicate with the electronic board 10 via a local area network, intranet, wireless LAN, Bluetooth, USB cable, or other communication means used for relatively short-range communication, without cascading connections via multiple switching hubs. With the above arrangement, the dispatch system 1 makes it easier for drivers using the breath alcohol detector to check the individual information displayed on the electronic board 10, and enables close communication between the driver and the operations manager. Furthermore, with the above-described arrangement and communication means, the dispatch system 1 can ensure confidentiality and cost-effectiveness in communication between the digital time card and the electronic board 10. In particular, a local area network with wiring that does not involve cascading connections offers excellent cost-effectiveness in terms of establishing communication and communication speed, as well as excellent confidentiality in preventing information leakage due to radio wave interception, and enables high-speed communication via the local area network without the speed reduction caused by cascading connections. In addition, wireless LAN and Bluetooth are easy to install retrofit, reduce the risk of drivers, dispatchers, etc., tripping over cables such as local area network cables, and eliminate the need for construction work such as raising the floor to avoid wiring above the floor in order to prevent the aforementioned risks.
[0184] Digital time card linkage function: Receives time stamps from the digital time card and reflects them in the attendance time. Preferably, this function also includes a function to determine when a time stamp is received that it is a predetermined time to display personal information. This allows drivers to check their individual information at the time they stamp the digital time card without having to perform any additional operations related to the display of individual information. Preferably, the digital time card is placed in a location that is visible from the electronic board 10 and is configured to communicate with the electronic board 10 via a local area network, intranet, wireless LAN, Bluetooth, USB cable, or other communication means used for relatively short-distance communication, without cascading connections via multiple switching hubs. With the above arrangement, the dispatch system 1 makes it easier for drivers using the digital time card to check the individual information displayed on the electronic board 10, and enables close communication between the driver and the operations manager. Furthermore, with the above arrangement and communication means, the dispatch system 1 can make communication between the digital time card and the electronic board 10 highly confidential and cost-effective. In particular, local area networks using wiring without cascading connections offer excellent cost-effectiveness in terms of establishing and maintaining communication speed, as well as superior confidentiality by preventing information leakage through radio wave interception. Furthermore, they enable high-speed communication via the local area network without the speed reduction associated with cascading connections. Wireless LAN and Bluetooth are also advantageous because they are easy to install retrofit, reduce the risk of drivers, dispatchers, etc., tripping over local area network cables, and eliminate the need for construction work such as raising the floor to avoid overhead wiring to prevent the aforementioned risks.
[0185] Digital tachograph linkage function: This function receives dynamic information from the digital tachograph and reflects it in the dynamic information storage unit 215. Preferably, this function also includes a function that determines when the digital tachograph starts operating, which is a predetermined time to display personal information. This allows the crew to check the individual information at the time the digital tachograph starts operating, i.e., at the time the crew starts operating the vehicle, without having to perform any additional operations related to the display of individual information.
[0186] Dispatch plan reuse function: This function relates to the dispatch plan creation support unit 204 and the dispatch information storage unit 216, and allows for the reuse of dispatch plans stored in the dispatch information storage unit 216 in the above-mentioned plan saving function. This allows the management device 20 to reduce the burden on dispatch personnel involved in creating dispatch plans by making the saved dispatch plans available.
[0187] Working Hours Management Linkage Function: This function relates to the working hours management service of the working hours management unit 203 and the dynamic information storage unit 215, and manages the working hours of drivers based on information such as arrival and departure times provided from the dispatch board screen, digital time card, etc., and work status information provided from the digital tachograph, etc. This allows the management device 20 to reduce the burden on dispatchers in managing the working hours of drivers.
[0188] Attendance / Payroll Management Integration Function: This function relates to the working hours management unit 203, the attendance time stamping unit 207, and the crew database 211, and is a function of the attendance / payroll management service that manages the attendance and payroll of crew members based on information such as arrival and departure times provided from the dispatch board screen, digital time cards, etc., and work status information provided from digital tachographs, etc. This allows the management device 20 to reduce the burden on dispatchers regarding the management of crew members' attendance and payroll.
[0189] Operation plan management function: This function is linked to the operation plan management service related to the dispatch plan creation support unit 204 and the dispatch information storage unit 216, and manages the operation plan related to the dispatch plan based on the information provided by the operation plan management service.
[0190] According to the embodiment described above, since the dispatch plan is created by moving the tag image, it retains the user experience of using a whiteboard, which was conventionally used to create dispatch plans. Therefore, sudden changes can be minimized. In addition, since information addressed to the driver entered by operating the touch panel unit 13, or information addressed to the driver transmitted to the management device 20 via the network, is displayed on the display unit 12, smooth communication can be achieved between the dispatch manager and the driver.
[0191] Furthermore, the information displayed to the crew on the display unit 12 is not limited to road information; it can be anything, such as notes regarding the work. Also, in this embodiment, a large touch panel display is used as the user interface that mimics a dispatch board, but a combination of a regular large display and an input device such as a mouse may also be used.
[0192] Furthermore, information for the crew displayed on the display unit 12 via touching the touch panel may be erased by touching it again. Also, information from a breath alcohol detector may be acquired and displayed on the display unit 12 as information for the crew, enabling warnings to be issued to the crew. Additionally, it may be linked to a digital time card, and the time recorded on the digital time card may be displayed on the display unit 12 as information for the operations manager. This allows the operations manager to be notified that the crew has reported to work. Furthermore, a digital tachograph may be used, and the operating status may be displayed on the display unit 12 as information for the operations manager. This allows the operations manager to understand the crew's operating status.
[0193] Furthermore, since manual transcription is no longer required, the workload can be reduced. Information can also be shared among crew members, making error checking easier and eliminating careless mistakes. Additionally, vehicle inspection information and other data are automatically updated, simplifying vehicle management.
[0194] Furthermore, because dispatch system 1 analyzes past data to determine dispatches, it becomes possible to make efficient dispatch decisions, and it will be easier to increase the number of personnel capable of planning dispatches in the future. In addition, the burden on dispatchers will be reduced, allowing them to use that time for other planning tasks.
[0195] Furthermore, for drivers, the system significantly reduces the amount of communication and confirmation work required between the dispatch manager and the drivers, thus reducing the workload associated with communication and confirmation. Additionally, the system adjusts drivers' attendance, reducing the burden on drivers regarding their commute. Finally, the system adjusts delivery routes, eliminating route imbalances and reducing the burden on drivers related to driving.
[0196] Although embodiments of the present invention have been described above, the present invention is not limited to the embodiments described above. For example, in this embodiment, the management device 20 and the electronic board 10 are separate, but they may be integrated. In addition, in this embodiment, various inputs can be made by touching the touch panel section 13 of the electronic board 10, but an input device such as a mouse may be connected to the electronic board 10 and the dispatch schedule may be created using the mouse, or input operations on each screen may be performed by operating a mouse connected to the management device 20.
[0197] Furthermore, according to this embodiment, the crew member clocks in by touching the clock-in time tag, but the crew member may also clock in by clicking the clock-in time tag on the dispatch board screen using a mouse. In addition, the crew member may clock in when they use an alcohol breath detection device, or the time the crew member clocks in on a digital time card may be reflected on the dispatch board.
[0198] It is preferable that the system has a function to link with a crew terminal 103, such as a tablet device carried by each crew member. For example, a crew member may operate the crew terminal 103 to send text information to the management device 20, and the management device 20 may use a sticky note function to write the text information from the crew terminal 103 on a sticky note and attach it to the dispatch board. This makes it possible to respond to changes in the day's schedule that occur after the crew member has looked at the display unit 12 (for example, changes in the schedule to respond to various circumstances such as temporary delivery requests due to changes in demand due to weather changes, or compensation for delays in delivery / return due to accidents, traffic jams, etc.).
[0199] Additionally, event information can be extracted from the websites of municipalities included in the delivery routes, and information on events involving traffic restrictions can be obtained. If traffic restrictions are scheduled on the delivery day, drivers may be provided with alternative routes and times to avoid them. This allows drivers to avoid getting caught in traffic jams when traffic restrictions are planned on national or prefectural roads for a limited time due to events such as marathons or ekiden races, or when traffic congestion is expected, such as at fireworks displays.
[0200] <Display regarding clocking in / out times> In the transportation industry, there are legal limits on the annual, monthly, and daily working hours of drivers, the average daily driving time over two days, the average weekly driving time over two weeks, and continuous driving time. There are also minimum limits on the rest periods drivers take after their shifts. However, in the busy transportation industry, where there are many factors to consider and sudden changes to dispatch plans are common, it is difficult for drivers and dispatchers to constantly monitor the remaining available working hours for each driver in relation to these limits.
[0201] To minimize the burden on dispatchers due to sudden changes in dispatch plans, etc., and to support the smooth communication of the remaining available working hours of the crew members in relation to the various upper and lower limits mentioned above, it is preferable that the information display control unit 206 of the management device 20, upon receiving a predetermined operation related to a crew member, executes a process to display an estimate of the remaining available working hours of the crew member for a predetermined period on the electronic board 10. The predetermined operation referred to here is an operation performed by the crew member via the electronic board 10 when they report to work.
[0202] The process includes, for example, a procedure in which the time management unit 203 stores and updates information related to the attendance of crew members, exemplified by working hours, arrival time, departure time, driving time, start time of driving, end time of driving, break time, leave, etc., in the crew member database 211 of the storage unit 210, and the information display control unit 206 calculates various times related to the remaining available working time by referring to the attendance information stored in the storage unit 210, and calculates an estimate of the remaining available working time for the crew member in a predetermined period by subtracting the calculated time from the available working time in a predetermined period set in accordance with the law.
[0203] Various types of time related to the remaining working hours include, for example, the annual working hours, monthly working hours, daily working hours, average daily driving hours over two days, average weekly driving hours over two weeks, or continuous driving hours. Working hours within a specified period include, for example, the annual limit on working hours, the monthly limit on working hours, the daily limit on working hours, the average daily driving hours over two days, the average weekly driving hours over two weeks, or the maximum continuous driving hours. Examples of each limit are as follows: annual limit on working hours = 3,300 hours, monthly limit on working hours = 284 hours, daily limit on working hours = 13 hours, average daily driving hours over two days = 9 hours, average weekly driving hours over two weeks = 44 hours, and maximum continuous driving hours = 4 hours.
[0204] [Flowchart for calculating the remaining amount] Figure 17 is a flowchart showing an example of a preferred flow of the residual calculation process performed by the management device 20. Figure 18 is a flowchart continuing from the previous figure. The following is an example of a process (residual calculation process) for calculating an estimate of the remaining available working hours for the crew member in question during a predetermined period, using Figures 17 and 18.
[0205] [Step S201: Determine whether to update working hours] The control unit 200, in cooperation with the memory unit 210 and the like, executes the working hours management unit 203. The control unit 200 then performs a process to determine whether to update the working hours based on the working hours management unit 203 (working hours update determination step). If it is determined that the hours should be updated, the control unit 200 moves the process to step S202. If it is not determined that the hours should be updated, the control unit 200 moves the process to step S203.
[0206] The procedure for determining whether to update working hours includes, for example, a procedure for determining whether to update working hours when the time of departure is recorded or when manually entered working hours data is provided.
[0207] [Step S202: Update working hours] The control unit 200 executes a process to update working hours using the time management unit 203 (working hours update step). The control unit 200 then moves the process to step S203.
[0208] [Step S203: Determine whether to update the driving time] The control unit 200, in cooperation with the memory unit 210 and the like, executes the working time management unit 203. The control unit 200 then uses the attendance time stamping unit 207 to determine whether to update the working time (working time update determination step). If it determines that an update is necessary, the control unit 200 moves the process to step S204. If it does not determine that an update is necessary, the control unit 200 moves the process to step S205.
[0209] The procedure for determining whether to update the driving time includes, for example, a procedure for determining whether to update the driving time when dynamic information from a digital tachograph, or information related to driving time from a digital time card, crew terminal 103, or in-vehicle terminal 104 is provided.
[0210] [Step S204: Update driving time] The control unit 200 performs a process to update the operating time using the time management unit 203 (operating time update step). The control unit 200 then moves the process to step S205.
[0211] [Step S205: Determine whether to update the break time] The control unit 200, in cooperation with the memory unit 210 and the like, executes the time management unit 203. The control unit 200 then uses the attendance time stamping unit 207 to determine whether to update the break time (break time update determination step). If it determines that an update is necessary, the control unit 200 moves the process to step S204. If it does not determine that an update is necessary, the control unit 200 moves the process to step S205.
[0212] The procedure for determining whether to update the break time includes, for example, a procedure for determining whether to update the break time when dynamic information from a digital tachograph, or information related to break time from a digital time card, crew terminal 103, or in-vehicle terminal 104 is provided.
[0213] [Step S206: Update break time] The control unit 200 performs a process to update the break time using the rest time management unit 203 (break time update step). The control unit 200 then moves the process to step S207.
[0214] [Step S207: Determine if the specified operation has been received] The control unit 200, in cooperation with the memory unit 210 and the like, executes the clock-in time stamping unit 207. The control unit 200 then performs a process to determine whether it has received a predetermined operation that the crew member will perform when clocking in (predetermined operation reception determination step). If it determines that it has received the operation, the control unit 200 moves the process to step S208. If it does not determine that it has received the operation, the control unit 200 returns the process to step S201 and repeats the process from step S201 to step S210. The predetermined operation reception determination step may be the same as the specific operation determination step.
[0215] [Step S208: Total working hours for the specified period] The control unit 200, in cooperation with the storage unit 210 and the like, executes the information display control unit 206. Then, the control unit 200, using the information display control unit 206, executes a process to total the working hours, etc., for a predetermined period for the crew member related to the predetermined operation reception determination step (working hours total step). The control unit 200 then moves the process to step S209.
[0216] (Based on the average weekly operating time over two weeks) In the working hours totaling step, the information display control unit 206, in cooperation with the working hours management unit 203, refers to the working hours for each of the two weeks prior to the day the totaling process is performed, and calculates the total. For example, if the most recent starting date is the previous Sunday and the current day is a Wednesday, the information display control unit 206 totals the working hours from the previous Sunday to this Wednesday. Then, the information display control unit 206 calculates the average weekly working hours over the two weeks by dividing the obtained total working hours by two.
[0217] [Step S209: Calculate the remainder] The control unit 200, using the information display control unit 206, executes a process to calculate the remaining available working hours of the crew member in the predetermined period for the crew member related to the predetermined operation reception determination step (remaining hours calculation step). The control unit 200 then moves the process to step S210.
[0218] (Based on the average weekly operating time over two weeks) In the remaining calculation step, the information display control unit 206 calculates the remaining available working time for the crew member during a predetermined period (two weeks from the most recent starting date) by subtracting the average weekly driving time calculated in the total working time step from the upper limit of the average weekly driving time calculated over two weeks.
[0219] [Step S210: Display the remainder] The control unit 200, using the information display control unit 206, executes a process to display the remaining amount calculated in the remaining amount calculation step along with a predetermined period of time (remaining amount display step). The control unit 200 returns the process to step S201 and repeats the process from step S201 to step S210.
[0220] To improve the visibility of remaining time for crew members, in the remaining time display step, it is preferable that the information display control unit 206 displays an estimate of the remaining time on the electronic board 10 in place of, or in addition to, the remaining time of the crew member's available working hours for a predetermined period. That is, in the remaining time display step, it is preferable that the information display control unit 206 displays an estimate of the remaining time of the crew member's available working hours for a predetermined period on the electronic board 10. The estimate of remaining time may be, for example, a display that color-codes the user interface element where the crew member's name is displayed based on the remaining time calculated in the remaining time calculation step. This color coding system displays, for example, a first color such as light blue when the remaining capacity is equal to or greater than the first threshold (e.g., 11 hours or more in average weekly driving time over two weeks), a second color such as yellow when it is less than the first threshold but equal to or greater than the second threshold (e.g., less than 11 hours but 3 hours or more in average weekly driving time over two weeks), and a third color such as red when it is less than the second threshold (e.g., less than 3 hours in average weekly driving time over two weeks). This color coding system allows crew members to easily determine whether they can drive full-time as usual on a given day, whether they can drive for a short period even if they cannot drive as usual, or whether they are effectively unable to drive at all.
[0221] In the above, as an example, the remaining working time per week based on the average of two weeks was explained in particular detail. However, a person skilled in the art would easily be able to conceive of the process for calculating the estimated remaining working time for other upper limits, etc., based on the above explanation.
[0222] [Effect of residual calculation processing] According to the residual calculation process described above, the management device 20 can support the smooth communication of the remaining working hours in accordance with the law to the crew by displaying an estimate of the remaining working hours for the crew during a predetermined period on the electronic board 10. This relieves the dispatcher of the burden of having to recalculate the residual hours each time they change due to sudden changes in the dispatch plan, etc. Furthermore, this allows the crew to understand their remaining working hours during a predetermined period without having the dispatcher calculate them each time, or without having to calculate them themselves each time, and to plan and execute a work schedule that effectively utilizes their working hours.
[0223] <Display of estimated return time> In order to communicate the scheduled return time to the crew while minimizing the burden on the dispatch manager, it is preferable that the information display control unit 206 of the management device 20 calculates the scheduled return time by adding the time the crew member is on duty based on the delivery plan to the time the crew member clocks in, and displays the calculated scheduled return time on the electronic board 10.
[0224] <Warning displayed regarding the time of instruction to report to work> Due to the considerable effort and time required to create dispatch plans, dispatchers often create daily dispatch plans the day before. In creating dispatch plans, the transportation industry is obligated to ensure that drivers have a given interval period (e.g., 9 hours) or more of rest after their shift ends. Therefore, in creating such dispatch plans, the dispatch plan for a driver is created in advance, either manually by the dispatcher or automatically by the management device 20 of this embodiment, without waiting for the driver to return to the depot, so that the driver's scheduled arrival time is the time when the given interval period is added to or later than the driver's scheduled return time.
[0225] However, as described above, if a driver returns to the depot later than scheduled due to various factors such as traffic conditions, delivery content, or circumstances at the delivery destination, the dispatch plan may require a revision of the scheduled arrival time. Determining whether or not a revision of the scheduled arrival time is necessary for each driver individually is a significant burden for busy dispatchers. Therefore, there is a need for technology that reduces the burden on dispatchers in determining whether or not a revision of the scheduled arrival time is necessary when a driver returns to the depot later than scheduled.
[0226] In order to minimize the burden on dispatchers while enabling them to understand the need to change the instructed arrival time, it is preferable that the information display control unit 206 of the management device 20 calculates the possible arrival time by adding a given interval time (for example, the time obtained by adding the round-trip commuting time to the time stipulated by law) to the departure time when a driver has clocked out, and if the possible arrival time is later than the scheduled arrival time, it executes an arrival schedule warning display step that displays a warning regarding the scheduled arrival time on the electronic board 10, the operation management terminal 101, etc. This allows dispatchers to respond to situations requiring such revisions as described above, for example, when swapping the schedules of a driver whose possible arrival time is later than the scheduled arrival time with another driver who can handle the work assigned to that driver, and to quickly inform these two drivers of the schedule change.
[0227] Warnings related to the scheduled time of arrival at work include, for example, a warning indicating that the time when one can arrive at work is later than the scheduled time, a warning accompanied by the time when one can arrive at work, or a warning accompanied by the time when one can arrive at work and the time when one is instructed to arrive at work at that time.
[0228] This allows dispatchers to identify when they cannot provide the necessary interval time for each driver without having to calculate the available arrival time for each driver individually, and to revise the dispatch plan accordingly. To enable dispatchers to quickly identify drivers who need to adjust their arrival time, it is preferable that the display of available arrival time includes information that identifies the driver in question.
[0229] To further reduce the burden on dispatchers, it is preferable that the information display control unit 206 of the management device 20 calculates the maximum return time by subtracting a given interval time for the driver from the scheduled arrival time for the next day in the scheduled arrival warning display step, and displays a warning on the electronic board 10, operation management terminal 101, etc. if the driver does not return to the depot at or before the maximum return time.
[0230] As a result, the management device 20 enables the dispatcher to quickly recognize that the dispatch plan needs to be revised as soon as they determine that the dispatch plan needs to be revised, without waiting for the driver to return to the depot, and to begin the revision work as soon as possible. This allows the dispatcher to respond to situations requiring revision, such as the one described above, by swapping the schedules of a driver whose arrival time is later than the scheduled arrival time with another driver who can handle the work assigned to that driver, and to communicate the schedule change to both drivers more quickly.
[0231] <Layout Settings> In order to provide a user experience similar to that of the physical dispatch board used before the system S of this embodiment was put into use, it is preferable that the information display control unit 206 of the management device 20 perform a process to customize the layout of the dispatch schedule and the like displayed on the electronic board 10. Such customization may involve, for example, switching between a horizontal layout in which the dispatch plans for each crew member and vehicle are arranged horizontally and the crew members and vehicles are arranged vertically, and a vertical layout in which the dispatch plans for each crew member and vehicle are arranged vertically and the crew members and vehicles are arranged horizontally.
[0232] <Data Output> To provide a user experience similar to that of the physical forms used before commencing use of the system S of this embodiment, it is preferable that the management device 20 executes a process to output a form that summarizes a specified part or all of the dispatch data displayed on the electronic board 10 in a specified format. The format of the form is not particularly limited. The format may be, for example, an Excel® spreadsheet format or a Portable Document Format (PDF) format.
[0233] Furthermore, in order to cooperate with external systems, it is preferable that the management device 20 performs a process to output data that combines a specified part or all of the data managed by the management device 20. In order to enable cooperation with various external systems, it is preferable that the management device 20 performs a process to customize the output items related to the data output in relation to this process. Furthermore, in order to enable cooperation with various external systems, it is preferable that the management device 20 outputs the data in a format specified from various formats presented as options (for example, comma-separated number (CSV) format, JavaScript Object Notation (JSON) format, etc.).
[0234] Within the scope of the concept of this invention, those skilled in the art can conceive of various modifications and alterations. Therefore, such modifications and alterations are understood to fall within the scope of this invention. For example, any addition, deletion, or design change of components, or addition, omission, or modification of processes, made by a person skilled in the art to the above-described embodiments, is also included within the scope of this invention, as long as it retains the essence of this invention. [Explanation of Symbols]
[0235] 1. Dispatch System 10 Electronic boards 11 Control Unit 12 Display section 13 Touch panel section 20 Management device 21 Control Unit 21a CPU 21b Memory 21c clock 22 Input / output section 100 Networks 101 Operation Management Terminal 102 Logistics Sales Office Terminal 103 Crew Terminal 104 In-vehicle terminals 105 Electronic board display control device 200 Control Unit 201 Dynamics Management Department 202 Vehicle Management Department 203 Restraint Time Management Department 204 Dispatch Planning Support Department 205 Roll Call Record Creation Department 206 Crew Information Display Control Unit 207 Time clocking-in section 208 Placement Operation Receiving Unit 209 Individual Information Receiving Unit 210 Storage section 211 Crew Database 212 Vehicle Information Database 213 Delivery Address Information Registration Section 214 Work Information Registration Department 215 Dynamic Information Storage Unit 216 Dispatch Information Storage Unit 217 Display Information Storage Unit
Claims
1. At least one terminal capable of displaying the dispatch schedule, The system includes a management device that performs various processes in response to input operations on at least one of the terminals, The aforementioned control device is A placement operation receiving unit receives information on the operation in which a dispatcher operates one of the at least one terminal to move at least one type of tag image selected from a first tag image provided for each of the names of the drivers included in the dispatch plan, a second tag image provided for each of the vehicles the drivers are riding in, and a third tag image provided for each of the delivery destinations, and places the tag images in the fields for inputting the driver, the vehicle, and the delivery destination. A dispatch plan creation unit which creates the dispatch plan based on the information received by the dispatch operation receiving unit, An information display control unit that displays dispatch information, including the dispatch plan created by the dispatch plan creation unit, on an electronic board among the at least one terminal that is capable of input by touch operation, When the aforementioned crew member performs a predetermined operation via the electronic board upon arrival at work, the attendance time stamping unit stamps the attendance time, It has, The management device further includes an individual information receiving unit that receives individual information addressed to one or more of the multiple crew members entered by the dispatcher, The information display control unit displays the first tag image, the second tag image, and the third tag image, and displays the individual information on the electronic board at a predetermined timing along with the dispatch plan for the corresponding crew member. Vehicle dispatch system.
2. The dispatch system according to claim 1, wherein the information display control unit displays the first tag image, the second tag image, and the third tag image so that they can be moved by touch operation.
3. The dispatch system according to claim 1 or 2, wherein the information display control unit of the management device, upon receiving the predetermined operation relating to the crew member, displays an estimate of the remaining available working hours of the crew member during a predetermined period on the electronic board.
4. On at least one terminal capable of displaying the dispatch schedule, A placement operation command step involves having the dispatcher operate one of the at least one terminals to move at least one tag image selected from the first tag image provided for each of the driver names included in the dispatch plan, the second tag image provided for each of the vehicles the driver is riding in, and the third tag image provided for each of the delivery destinations, and to place the tag images in the fields for inputting the driver, the vehicle, and the delivery destination. A placement operation transmission step that causes the placement operation of the aforementioned tag image to be transmitted to the management device, A step of transmitting individual information to a management device, which transmits individual information addressed to one or more of the multiple crew members entered by the dispatcher, Make it run, Of the at least one of the aforementioned terminals, an electronic board capable of touch input, An information display control step which displays dispatch information, including a dispatch plan, created by the management device based on the information transmitted in the dispatch operation transmission step, A clock-in time stamping transmission step that receives a predetermined operation performed by the crew member via the electronic board when they arrive at work, and transmits information related to said operation to the management device, Make it run, The information display control step involves displaying the first tag image, the second tag image, and the third tag image, and displaying the individual information on the electronic board at a predetermined timing along with the dispatch plan for the corresponding crew member. Ride-hailing program.
Citation Information
Patent Citations
Vehicle operation schedule creation apparatus
JP2012128593A
Vehicle allocation plan editing method, vehicle allocation plan editing device and vehicle allocation plan editing program
JP2017123127A
Vehicle allocation system
JP2019057008A
Information processor
JP2020129348A
Operation Management Methods
JP4708500B1