Ride hailing management device, program, ride hailing management system, and ride hailing management method

Abstract

To provide a ride hailing management device, program, ride hailing management system, and ride hailing management method capable of facilitating ride hailing more greatly than before.SOLUTION: A ride hailing management device in accordance with an embodiment includes a display control unit and memory control unit. The display control unit presents a first Gantt chart showing schedules of transportation cases and schedules of moving bodies, presents a second Gantt chart whose time base agrees with that of the first Gantt chart and schedules of drivers, and displays a third Gantt chart whose time base agrees with that of the first Gantt chart and second Gantt chart. The memory control unit associates a case selected from the first Gantt chart, a moving body selected from the second Gantt chart and supposed to be in charge of transportation of the case, and a driver, who is selected from the third Gantt chart and supposed to drive the moving body for transportation, with one another, and stores the associated case, moving body, and driver in a memory unit.SELECTED DRAWING: Figure 4

Description

[Technical field]

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

[0002] There is a system for dispatching freight vehicles for transporting luggage. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] JP 2001-23073 A Summary of the Invention [Problem to be solved by the invention]

[0004] However, conventional vehicle dispatch systems are unable to rationally confirm the information that a dispatcher uses to make decisions about vehicle allocation.

[0005] An object of the present invention is to provide a vehicle dispatch management device, a program, a vehicle dispatch management system, and a vehicle dispatch management method that make it easier to dispatch vehicles than ever before. [Means for solving the problem]

[0006] The vehicle dispatch management device of the embodiment includes a display control unit and a storage control unit. The display control unit displays a first Gantt chart showing a schedule of a case to be transported, a second Gantt chart showing a schedule of a mobile body and having a time axis coinciding with the first Gantt chart, and a third Gantt chart showing a schedule of a driver and having a time axis coinciding with the first Gantt chart and the second Gantt chart. The storage control unit associates the case selected in the first Gantt chart, the mobile body selected in the second Gantt chart to transport the case, and the driver selected in the third Gantt chart to drive the mobile body to transport the case, and stores them in a storage device. [Brief description of the drawings]

[0007] [Figure 1] 1 is a block diagram showing an example of a main configuration of a vehicle dispatch system according to an embodiment and components included in the vehicle dispatch system 1. FIG. [Diagram 2] 2 is a flowchart showing an example of processing by a processor of the terminal device in FIG. 1; [Diagram 3] 2 is a flowchart showing an example of processing by a processor of the server device in FIG. 1; [Figure 4] FIG. 2 is a diagram showing an example of a vehicle dispatch matching screen displayed on the display device in FIG. 1. [Diagram 5] FIG. 2 is a diagram showing an example of a vehicle dispatch matching screen displayed on the display device in FIG. 1. [Figure 6] FIG. 2 is a diagram showing an example of a vehicle dispatch matching screen displayed on the display device in FIG. 1. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0008] The vehicle dispatch system according to the embodiment will be described below with reference to the drawings. Note that the scale of each part in each drawing used in the following description of the embodiment may be changed as appropriate. Also, the configuration of each drawing used in the following description of the embodiment may be omitted for the sake of explanation. Also, in each drawing and in this specification, the same reference numerals indicate similar elements.

[0009] FIG. 1 is a block diagram showing an example of a main configuration of a vehicle dispatch system 1 according to an embodiment and components included in the vehicle dispatch system 1. Each component of the device may be built-in or external. The vehicle dispatch system 1 provides a vehicle dispatch service. Users who use the vehicle dispatch service are mainly transportation companies that transport luggage using trucks and the like, and shippers of the luggage. The vehicle dispatch service is a service that supports dispatching of vehicles for luggage transport cases. Dispatching a vehicle means assigning a truck and a driver that transports luggage for the case to the case. The vehicle dispatch system 1 includes, as an example, a server device 100 and a terminal device 200. The vehicle dispatch system 1 may include some of these. The vehicle dispatch system 1 is an example of a vehicle dispatch management system.

[0010] The server device 100 and the terminal device 200 are connected to a network NW. The network NW is typically a communication network including the Internet. The network NW may be a communication network including a private network such as an intranet. The network NW may be a communication network including a LAN (local area network).

[0011] The server device 100 is a device such as a server that provides a vehicle dispatch service. The server device 100 includes, as an example, a processor 110, a read-only memory (ROM) 120, a random-access memory (RAM) 130, an auxiliary storage device 140, and a communication interface 150. A bus 160 or the like connects these components. The server device 100 is an example of a vehicle dispatch management device.

[0012] The processor 110 is a central part of a computer that performs processes such as calculations and control necessary for the operation of the server device 100, and performs various calculations and processes. The processor 110 is, for example, a central processing unit (CPU), a micro processing unit (MPU), a system on a chip (SoC), a digital signal processor (DSP), a graphics processing unit (GPU), an application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field-programmable gate array (FPGA). Alternatively, the processor 110 is a combination of a plurality of these. The processor 110 may also be a combination of these with a hardware accelerator or the like. The processor 110 controls each part to realize various functions of the server device 100 based on programs such as firmware, system software, and application software stored in the ROM 120 or the auxiliary storage device 140. The processor 110 also executes processes described below based on the programs. A part or all of the programs may be incorporated in the circuitry of the processor 110.

[0013] The ROM 120 and the RAM 130 are main storage devices of the computer with the processor 110 at its core. The ROM 120 is a non-volatile memory used exclusively for reading data. The ROM 120 stores, for example, firmware among the above programs. The ROM 120 also stores data used by the processor 110 when performing various processes.

[0014] The RAM 130 is a memory used for reading and writing data. The RAM 130 is used as a work area for storing data that is temporarily used when the processor 110 performs various processes. The RAM 130 is typically a volatile memory.

[0015] The auxiliary storage device 140 is an auxiliary storage device of a computer with the processor 110 as its core. The auxiliary storage device 140 is, for example, an EEPROM (electric erasable programmable read-only memory), a HDD (hard disk drive), or a flash memory. The auxiliary storage device 140 stores, for example, system software and application software among the above programs. The auxiliary storage device 140 also stores data used by the processor 110 in performing various processes, data generated by the processes in the processor 110, various setting values, and the like. The data stored in the auxiliary storage device 140 includes, for example, a user DB (database) 141, a case DB 142, a vehicle DB 143, and a driver DB 144.

[0016] The user DB 141 is a database that stores and manages information about users who use the vehicle dispatch service. For example, the user DB 141 stores user information in association with a user ID (identifier) ​​for each user. The user ID is identification information that is uniquely assigned to each user. In addition, users who use the vehicle dispatch service have two or more types of attributes. The attributes include a transportation attribute and a shipper attribute. A user with a transportation attribute (hereinafter referred to as a "transportation user") is a user who transports luggage. Therefore, a transportation company, etc. is a transportation user. A transportation company and an office within the transportation company may be different users. A user with a shipper attribute (hereinafter referred to as a "shipper user") is a user who becomes a shipper who requests a transportation company to transport luggage. A shipper includes not only a shipper, but also a prime contractor, a 3PL (third party logistics), and a first-tier subcontracted transportation company entrusted by the shipper. In addition, a user may have both a transportation attribute and a shipper attribute. A user having both attributes is a user who both transports luggage and requests the transport of luggage. The user information includes, for example, information about the company such as the name and address of the company, a list of the offices where the user operates and information about each office, information about business partners, information about each employee, and information about the bank account to be used.

[0017] The case DB 142 is a database that stores and manages information about cases. In this embodiment, a case refers to a case of a request to a transportation company to transport luggage. The case DB 142 stores information about the case (hereinafter referred to as "case information") in association with a case ID for each case. The case ID is identification information that is uniquely assigned to each case. The case information includes, for example, an orderer ID, an order recipient ID, a dispatched vehicle ID, a dispatched driver ID, floor information, transportation condition information, designation information, baggage information, order variables, type information, and other information about the case. The orderer ID is the user ID of the shipper user who is the orderer who placed the case. The dispatched customer ID is the user ID of the transportation user who is the order recipient of the case. The dispatched vehicle ID is the vehicle ID of the freight truck used for the case. The dispatched driver ID is the driver ID of the driver who drives the freight truck in the case. The vehicle ID is identification information that is uniquely assigned to each freight truck. The vehicle ID may be identification information for the vehicle dispatch system 1, or may be existing identification information such as a vehicle registration number, a vehicle number, a wireless call number (WCN), an on-board device management number, or an electronic toll collection (ETC) card number. The driver ID is identification information uniquely assigned to each driver. The transportation condition information is information indicating the transportation conditions. The hierarchical information is information indicating the subcontractor level of the case. The designation information is information indicating the conditions of the vehicle used for the case. The conditions include, for example, the vehicle model, class, shape, size, and equipment of the vehicle. The baggage information is information about the baggage to be transported in the case. The baggage information includes, for example, the name, weight, volume, and number of the baggage. The order variable indicates, by a value, which of a plurality of states the case is in, including three types of states: an unordered state, an ordered state, and a rejected state. The unordered state is a state in which the order for the case has not been accepted or rejected. The ordered state is a state in which the order for the case has been accepted. The rejected state is a state in which an order for a project has been rejected. The type information indicates the type of project. There are two types of projects: own vehicle projects and chartered vehicle projects. Information about other projects includes, for example, the project name, loading point, unloading point, loading date and time, and unloading date and time. The project information may also include a subcontractor project ID.The subcontract case ID is the case ID of the subcontract case that is based on this case.

[0018] As described above, the cases stored and managed by the case DB 142 include own vehicle cases and vehicle hire cases. Own vehicle cases are cases in which a own vehicle is used. Vehicle hire cases are cases in which a chartered vehicle is ordered. Vehicle hire cases are cases in which an order is placed with an outsourced party such as a subcontractor or an in-house sales office.

[0019] In addition, a project with an nth subcontractor includes an original project ID. The original project ID is the project ID of the project (hereinafter referred to as the "original project") that is the source of the order for the chartered vehicle. If the project is a subcontractor project, the project indicated by the original project ID is the project of the prime contractor (first tier contractor). If the project is an nth subcontractor project, the project indicated by the original project ID is the project of the (n-1)th subcontractor. n is an integer greater than or equal to 2.

[0020] At least one of an ordering user and an order recipient user can register an item in the item DB 142 .

[0021] Vehicle DB143 is a database that stores and manages information about each freight vehicle operated by each transportation user. Vehicle DB143 stores, for each freight vehicle, a vehicle ID, a user ID, and information about the freight vehicle (hereinafter referred to as "vehicle information"). The user ID associated with a vehicle ID is the user ID of the user who operates the freight vehicle identified by the vehicle ID. Vehicle information includes, for example, the name of the transportation company (signboard name), the vehicle model, shape, and class, vehicle number, vehicle equipment, information that can identify the driver who uses the vehicle, contact information, vacant dates, vacant times, and vacant locations.

[0022] Driver DB144 is a database that stores and manages information about each driver used by each transportation user. Driver DB144 stores a driver ID, a user ID, and information about the driver (hereinafter referred to as "driver information") for each driver in association with the driver ID. The user ID associated with the driver ID is the user ID of the user who uses the driver identified by the driver ID. Driver information includes the driver's name, license type, phone number, planned / actual information, on-duty time information, remaining working time, operation date, planned operation location, and operation time. Planned / actual information is information about the driver's scheduled work hours and actual working hours. On-duty time information is information indicating the driver's scheduled work hours and actual on-duty time. Remaining working time is the on-duty time subtracted from a predetermined upper limit time. The upper limit time is, for example, a target value for on-duty time for one month.

[0023] The driver DB 144 also stores the driver ID in association with the location information and the date and time, thereby storing the location information of the driver identified by the driver ID for each date and time.

[0024] The communication interface 150 is an interface for the server device 100 to communicate via a network NW or the like.

[0025] The bus 160 includes a control bus, an address bus, a data bus, etc., and transmits signals exchanged among the various components of the server device 100 .

[0026] The terminal device 200 is a device that can use the vehicle dispatch service. The terminal device 200 is used, for example, by a user of the vehicle dispatch service. The terminal device 200 is, for example, a general-purpose computer such as a personal computer (PC), a tablet terminal, or a smartphone. Alternatively, the terminal device 200 may be a dedicated device for using the vehicle dispatch service. The terminal device 200 includes, for example, a processor 210, a ROM 220, a RAM 230, an auxiliary storage device 240, a communication interface 250, an input device 260, and a display device 270. A bus 280 and the like connect these components.

[0027] The processor 210 is a central part of a computer that performs processes such as calculations and control necessary for the operation of the terminal device 200, and performs various calculations and processes. The processor 210 is, for example, a CPU, an MPU, an SoC, a DSP, a GPU, an ASIC, a PLD, or an FPGA. Alternatively, the processor 210 is a combination of a plurality of these. The processor 210 may also be a combination of these with a hardware accelerator. The processor 210 controls each part to realize various functions of the terminal device 200 based on programs such as firmware, system software, and application software stored in the ROM 220 or the auxiliary storage device 240. The processor 210 also executes processes described below based on the programs. A part or all of the programs may be incorporated in the circuitry of the processor 210.

[0028] The ROM 220 and the RAM 230 are main storage devices of the computer with the processor 210 at its core. The ROM 220 is a non-volatile memory used exclusively for reading data. The ROM 220 stores, for example, firmware among the above programs. The ROM 220 also stores data used by the processor 210 when performing various processes.

[0029] The RAM 230 is a memory used for reading and writing data. The RAM 230 is used as a work area for storing data that is temporarily used when the processor 210 performs various processes. The RAM 230 is typically a volatile memory.

[0030] The auxiliary storage device 240 is an auxiliary storage device of a computer with the processor 210 at its core. The auxiliary storage device 240 is, for example, an EEPROM, a HDD, or a flash memory. The auxiliary storage device 240 stores, for example, system software and application software among the above programs. The auxiliary storage device 240 also stores data used by the processor 210 in performing various processes, data generated by the processes in the processor 210, various setting values, and the like.

[0031] The application software stored in the auxiliary storage device 240 includes, for example, application software for using a vehicle dispatch service (hereinafter referred to as a "terminal application"). The terminal application may be software dedicated to the vehicle dispatch service, or may be general-purpose software such as a web browser.

[0032] The communication interface 250 is an interface for the terminal device 200 to communicate via a network NW or the like.

[0033] The input device 260 accepts operations by an operator of the terminal device 200 (hereinafter simply referred to as "operator"). The input device 260 is, for example, a keyboard, a keypad, a touchpad, a mouse, or a controller. The input device 260 may also be a device for voice input.

[0034] The display device 270 displays a screen for notifying an operator or the like of various pieces of information. The display device 270 is, for example, a display such as a liquid crystal display or an organic EL (electro-luminescence) display. A touch panel can also be used as the input device 260 and the display device 270. That is, a display panel provided in the touch panel can be used as the display device 270, and a pointing device provided in the touch panel by touch input can be used as the input device 260.

[0035] The bus 280 includes a control bus, an address bus, a data bus, etc., and transmits signals exchanged among the various parts of the terminal device 200 .

[0036] The operation of the vehicle dispatch system 1 according to the embodiment will be described below with reference to Figs. 2 and 3. Note that the contents of the process in the following operation description are merely examples, and various processes capable of obtaining similar results can be appropriately used. Fig. 2 is a flowchart showing an example of the process by the processor 210 of the terminal device 200. The processor 210 executes the process of Fig. 2 based on a program stored in, for example, the ROM 220 or the auxiliary storage device 240. Fig. 3 is a flowchart showing an example of the process by the processor 110 of the server device 100. The processor 110 executes the process of Fig. 3 based on a program stored in, for example, the ROM 120 or the auxiliary storage device 140. Note that the operation will be described taking as an example a case where a vehicle is dispatched for a job in which neither a freight vehicle nor a driver is specified.

[0037] The processor 210 starts the process shown in FIG. 2 when, for example, a terminal application is started. Alternatively, the processor 210 starts the process shown in FIG. 2 when a web page of a vehicle dispatch service is accessed using the terminal application. Note that it is necessary to log in to the vehicle dispatch service in order to use some or all of the functions of the vehicle dispatch service. The terminal device 200 logs in to the vehicle dispatch service using, for example, a user ID. The login may be automatic or may require an operation by an operator. When the terminal device 200 is logged in to the vehicle dispatch service, it stores at least one of the user ID used for the login and the session ID given in the login. The user ID or the session ID is hereinafter referred to as a "login ID". However, in the following description, for simplicity, a case where the login ID is a user ID will be described as an example. Also, a user identified by a login ID is referred to as a login user.

[0038] 2, the processor 210 of the terminal device 200 generates an image corresponding to the selection screen. Then, the processor 210 instructs the display device 270 to display the generated image. In response to the display instruction, the display device 270 displays the selection screen.

[0039] The selection screen is a screen for selecting which user's trucks are to be displayed on the dispatch screen. On the selection screen, it is possible to select not only the logged-in user but also other users. In addition, it is also possible to select multiple users.

[0040] The selection screen also includes a confirmation button that is operated by the user to confirm a selection.

[0041] In step ST12, processor 210 waits for the decision button to be operated with one or more users selected. If the decision button is operated with one or more users selected, processor 210 determines Yes in step ST12 and proceeds to step ST13.

[0042] In step ST13, the processor 210 generates a vehicle dispatch list request. The vehicle dispatch list request includes, as an example, a login ID and a selection ID. The selection ID is the user ID of the user selected on the selection screen. There may be multiple selection IDs. The vehicle dispatch list request is information requesting a list of cases ordered by the transportation user specified by the login ID and information on each case. The vehicle dispatch list request is information requesting a list of trucks operated by the transportation user specified by the selection ID and information on each truck. The vehicle dispatch list request is information requesting a list of drivers used by the transportation user specified by the login ID and information on each driver. After generating the vehicle dispatch list request, the processor 210 instructs the communication interface 250 to transmit the vehicle dispatch list request to the server device 100. In response to this transmission instruction, the communication interface 250 transmits the vehicle dispatch list request to the server device 100. The transmitted vehicle dispatch list request is received by the communication interface 150 of the server device 100.

[0043] 3, the processor 110 of the server device 100 determines whether or not a vehicle allocation list request has been received by the communication interface 150. If a vehicle allocation list request has not been received, the processor 110 determines No in step ST31 and proceeds to step ST32.

[0044] In step ST32, the processor 110 determines whether or not a dispatch request has been received by the communication interface 150. If a dispatch request has not been received, the processor 110 determines No in step ST32 and returns to step ST31. Thus, the processor 110 enters a standby state in which steps ST31 and ST32 are repeated until a dispatch list request or a dispatch request is received. The dispatch request will be described later.

[0045] If a request for a vehicle dispatch list is received while processor 110 is in a standby state in which steps ST31 and ST32 are repeated, processor 110 determines "Yes" in step ST31 and proceeds to step ST33.

[0046] In step ST33, the processor 110 acquires information requested by the vehicle dispatch list request. That is, the processor 110 refers to the case DB 142 to identify cases in an order-received state among cases whose supplier ID is the same as the login ID included in the vehicle dispatch list request. The processor 110 then acquires the case ID and case information for each identified case. The processor 110 also refers to the vehicle DB 143 to identify a vehicle ID associated with the selection ID included in the vehicle dispatch list request. The processor 110 then acquires associated vehicle information for each identified vehicle ID. The processor 110 also refers to the driver DB 143 to identify a driver ID associated with the login ID. The processor 110 then acquires associated driver information for each identified driver ID.

[0047] In step ST34, the processor 110 generates vehicle allocation list information. The vehicle allocation list information includes the information acquired in step ST33. The vehicle allocation list information is information that instructs displaying a vehicle allocation matching screen SC1 described below. After generating the vehicle allocation list information, the processor 110 instructs the communication interface 150 to transmit the vehicle allocation list information to the terminal device 200. Upon receiving this transmission instruction, the communication interface 150 transmits the vehicle allocation list information to the terminal device 200. The transmitted vehicle allocation list information is received by the communication interface 250 of the terminal device 200. After processing step ST34, the processor 110 returns to step ST31.

[0048] 2, the processor 210 of the terminal device 200 waits for vehicle allocation list information to be received by the communication interface 250. If vehicle allocation list information is received, the processor 210 determines Yes in step ST14 and proceeds to step ST15.

[0049] In step ST15, the processor 210 generates an image corresponding to the vehicle allocation matching screen SC1-1 as shown in Fig. 4. Then, the processor 210 instructs the display device 270 to display the generated image. In response to the display instruction, the display device 270 displays the vehicle allocation matching screen SC1-1. Note that the vehicle allocation matching screens SC1-1 to SC1-3 are collectively referred to as vehicle allocation matching screens SC1.

[0050] 4 is a diagram showing an example of a vehicle allocation matching screen SC1-1 displayed on the display device 270. The vehicle allocation matching screen SC1-1 is a screen for displaying a list of cases. The vehicle allocation matching screen SC1-1 is a screen for selecting a case for which a vehicle is to be allocated from the list. The vehicle allocation matching screen SC1-1 includes, as an example, an area AR11-1 and a save button B11.

[0051] Area AR11-1 is an area that displays a list of cases. Cases displayed in area AR11-1 are cases included in the dispatch list information. Each case displayed in area AR11-1 is selectable. Area AR11-1 displays part of the case information for each case. The part of the case information includes, for example, at least part of the case name, shipper name, loading point, unloading point, loading date and time, unloading date and time, etc. However, area AR11-1 shown in FIG. 4 shows only a part of this. Area AR11-1 also includes a Gantt chart showing the schedule for each case. The Gantt chart has the horizontal axis representing time and the vertical axis representing a list of cases. The Gantt chart displays the planned period for each case by a band (horizontal bar). The Gantt chart displays the loading point location and unloading point location of the case within the band. Note that area AR11-1 shown in FIG. 4 is partially omitted. The Gantt chart in area AR11-1 is an example of a first Gantt chart showing a schedule for a transportation project.

[0052] The save button B11 is a button that can be operated when three items, the job, the truck, and the driver, are selected on the vehicle allocation matching screen SC1. The save button B11 is a button for finalizing the vehicle allocation details. The save button B11 is also a button for the operator to operate when instructing the terminal device 200 to transmit the vehicle allocation details to the server device 100. The details indicate that the job will be transported by the truck and the driver. The vehicle allocation matching screen SC1 is a collective term for the vehicle allocation matching screens SC1-1 to SC1-3.

[0053] The operator performs an operation on the vehicle allocation matching screen SC1-1 to select a job for which he / she wishes to allocate a vehicle from among the jobs displayed in the list.

[0054] In step ST16, the processor 210 waits for an operation to select a job displayed in the list on the vehicle allocation matching screen SC1-1. If an operation to select a job is performed, the processor 210 determines Yes in step ST16 and proceeds to step ST17.

[0055] In step ST17, the processor 210 generates an image corresponding to the vehicle allocation matching screen SC1-2 as shown in Fig. 5. Then, the processor 210 instructs the display device 270 to display the generated image. In response to the display instruction, the display device 270 displays the vehicle allocation matching screen SC1-2.

[0056] 5 is a diagram showing an example of a vehicle allocation matching screen SC1-2 displayed on the display device 270. The vehicle allocation matching screen SC1-2 is a screen that displays a list of freight vehicles. The vehicle allocation matching screen SC1-2 is a screen for selecting a freight vehicle that will transport the job selected on the vehicle allocation matching screen SC1-1 from the list. The vehicle allocation matching screen SC1-2 includes, as an example, an area AR11-2, an area AR12-1, and a save button B11.

[0057] Area AR11-2 is an area that displays the case selected on the vehicle dispatch matching screen SC1-1. Area AR11-2 includes a Gantt chart showing the schedule for the case. The Gantt chart displays the planned period for the case using bands. The Gantt chart displays the location of the loading point and the unloading point for the case within the band. The Gantt chart corresponds to the portion of the case extracted from the Gantt chart in area AR11-1. The Gantt chart in area AR11-2 is an example of a first Gantt chart. Area AR11-2 includes part of the case information, similar to area AR11-1.

[0058] The area AR12-1 is an area that displays a list of freight vehicles. The freight vehicles displayed in the area AR12-1 are freight vehicles included in the dispatch list information. Each freight vehicle displayed in the area AR12-1 is selectable. The area AR12-1 displays part of the vehicle information for each freight vehicle. The part of the vehicle information includes, for example, the vehicle type, shape, and rank, the vehicle number, the vacant vehicle date, the vacant vehicle time, and the vacant vehicle location. However, the area AR12-1 shown in FIG. 5 shows only a part of this information. The area AR12-1 also includes a Gantt chart showing the schedule of each freight vehicle. The Gantt chart has a horizontal axis representing time and a vertical axis representing a list of freight vehicles. The Gantt chart displays, for each freight vehicle, the scheduled period of the case that the freight vehicle will transport, using a band. The Gantt chart displays the location of the loading point and the location of the unloading point of the case within the band. The Gantt chart and the Gantt charts in the areas AR11-1 and AR11-2 have the same time axis. Here, the time axis coincidence indicates that an arbitrary time T of one Gantt chart coincides with a time T of the other Gantt chart. That is, a scale line indicating an arbitrary time T of one Gantt chart coincides with a scale line indicating a time T of the other Gantt chart. The Gantt chart in the area AR12-1 may be capable of displaying a schedule other than the operation of each freight vehicle. The area AR12-1 shown in FIG. 5 is partially omitted. The Gantt chart in the area AR12-1 is an example of a second Gantt chart that shows the schedule of the moving body and has a time axis coincident with that of the first Gantt chart. The area AR12-1 may also display information indicating which user operates each freight vehicle. The freight vehicle operated by the logged-in user is the user's own vehicle. The freight vehicle operated by a user other than the logged-in user is a chartered vehicle.

[0059] The operator performs an operation to select a truck to transport the case selected on the vehicle dispatch matching screen SC1-1 from among the trucks displayed in a list on the vehicle dispatch matching screen SC1-2. At this time, the operator selects a truck that meets the vehicle conditions indicated by the specification information displayed in the area AR11-2 and that can transport the cargo indicated by the cargo information displayed in the area AR11-2.

[0060] In step ST18, the processor 210 waits for an operation to select a truck displayed in the list on the vehicle allocation matching screen SC1-2. If an operation to select a truck is performed, the processor 210 determines Yes in step ST18 and proceeds to step ST19.

[0061] In step ST19, the processor 210 generates an image corresponding to the vehicle allocation matching screen SC1-3 as shown in Fig. 6. Then, the processor 210 instructs the display device 270 to display the generated image. In response to the display instruction, the display device 270 displays the vehicle allocation matching screen SC1-3.

[0062] 6 is a diagram showing an example of a vehicle allocation matching screen SC1-3 displayed on the display device 270. The vehicle allocation matching screen SC1-3 is a screen that displays a list of drivers. The vehicle allocation matching screen SC1-3 is a screen for selecting a driver who will transport the job selected on the vehicle allocation matching screen SC1-1 from the list. The vehicle allocation matching screen SC1-3 includes, as an example, an area AR11-2, an area AR12-2, an area AR13-1, and a save button B11.

[0063] Area AR12-2 is an area that displays a freight truck selected on the dispatch matching screen SC1-2. Area AR12-2 includes a Gantt chart showing the schedule for that freight truck. The Gantt chart uses bands to display the scheduled period for the job that the freight truck will transport. The Gantt chart displays the location of the loading point and the location of the unloading point for that job within the band. The Gantt chart corresponds to the part of the job that is extracted from the Gantt chart in area AR12-1. The Gantt chart in area AR12-2 is an example of a second Gantt chart.

[0064] The area AR13-1 is an area that displays a list of drivers. The drivers displayed in the area AR13-1 are drivers included in the dispatch list information. Each driver displayed in the area AR13-1 is selectable. The area AR13-1 displays part of the driver information for each driver. The part of the driver information includes, for example, the driver's name, the on-duty time and remaining working time in a specified period, the operation date, the planned operation location, and the operation time. However, the area AR13-1 shown in FIG. 6 shows only a part of this information. The specified period is, for example, the current month. The area AR13-1 also includes a Gantt chart showing the schedule of each driver. The Gantt chart has the horizontal axis representing time and the vertical axis representing a list of drivers. The Gantt chart displays, for each driver, the planned period of the cases that the driver will transport by using a band. The Gantt chart displays the location of the loading point and the location of the unloading point of the cases within the band. The time axis of the Gantt chart coincides with that of the Gantt charts in areas AR11-1 and AR11-2. The time axis of the Gantt chart in area AR13-1 coincides with that of the Gantt charts in areas AR12-1 and AR12-2. The Gantt chart in area AR13-1 may be capable of displaying schedules other than driving for each driver. The driver's schedules other than driving include, for example, schedules for holidays. The area AR13-1 shown in FIG. 6 is partially omitted. The Gantt chart in area AR13-1 shows the driver's schedule, and is an example of a third Gantt chart whose time axis coincides with that of the first Gantt chart and the second Gantt chart.

[0065] In addition, the area AR13-1 may be selectable to indicate that a driver has not been determined.

[0066] The operator performs an operation to select a driver who will transport the job selected on the vehicle allocation matching screen SC1-1 from among the drivers displayed in a list on the vehicle allocation matching screen SC1-3.

[0067] As described above, the processor 210 functions as an example of a display unit that displays the first Gantt chart, the second Gantt chart, and the third Gantt chart by performing the processes of steps ST15, ST17, and ST19 in cooperation with the display device 270. Also, the processor 210 functions as an example of a display control unit that displays the first Gantt chart, the second Gantt chart, and the third Gantt chart by performing the processes of steps ST15, ST17, and ST19.

[0068] Furthermore, the terminal device 200 displays the first Gantt chart, the second Gantt chart, and the third Gantt chart based on an instruction from the server device 100. Therefore, the processor 110 cooperates with the communication interface 150 to transmit vehicle allocation list information that instructs the display of the vehicle allocation matching screen SC1, thereby functioning as an example of a display control unit.

[0069] In step ST20, the processor 210 waits for an operation to select a driver displayed in the list on the vehicle allocation matching screen SC1-3. If an operation to select a driver is performed, the processor 210 determines Yes in step ST20 and proceeds to step ST21.

[0070] In step ST21, the processor 210 waits for an operation to confirm the dispatch of a vehicle. That is, the processor 210 waits for a predetermined operation, such as operating the save button B11, to be performed. If an operation to confirm the dispatch of a vehicle is performed, the processor 210 determines Yes in step ST21 and proceeds to step ST22.

[0071] In step ST22, the processor 210 generates a dispatch request. The dispatch request includes a login ID, a case ID of the case selected on the dispatch matching screen SC1-1, a vehicle ID of the truck selected on the dispatch matching screen SC1-2, and a driver ID of the driver selected on the dispatch matching screen SC1-3. In addition, the driver ID in the case where the driver is undecided is a driver ID indicating that the driver is undecided. The dispatch request is information indicating the contents of the dispatch. The contents are that the truck and the driver will transport the case. In addition, the dispatch request is information requesting that the contents be stored. After generating the dispatch request, the processor 210 instructs the communication interface 250 to transmit the dispatch request to the server device 100. In response to this transmission instruction, the communication interface 250 transmits the dispatch request to the server device 100. The transmitted dispatch request is received by the communication interface 150 of the server device 100. After the process of step ST22, processor 210 returns to step ST15.

[0072] The dispatch request is an example of information indicating the case selected in the first Gantt chart, the moving object selected in the second Gantt chart, and the driver selected in the third Gantt chart. Therefore, the processor 210 functions as an example of a transmission unit that transmits the information to the dispatch management device by performing the process of step ST22 in cooperation with the communication interface 250.

[0073] If a vehicle dispatch request is received while processor 110 is in a standby state in which steps ST31 and ST32 are repeated, processor 110 determines "Yes" in step ST32 and proceeds to step ST35.

[0074] In step ST35, the processor 110 updates the case DB 142 based on the dispatch request received in step ST34, and registers the truck and the driver in the case. That is, the processor 110 sets the value of the dispatched vehicle ID for the case information associated with the case ID included in the dispatch request to the vehicle ID included in the dispatch request. Then, the processor 110 sets the value of the dispatched driver ID for the case information to the driver ID included in the dispatch request.

[0075] If the dispatched freight vehicle is a chartered vehicle, the processor 110 updates the type information in the case information to indicate a chartered vehicle case. If the dispatched freight vehicle is the vehicle itself, the processor 110 sets the type information in the case information to indicate a vehicle itself case. The processor 110, for example, refers to the vehicle DB 143 to identify the user ID associated with the vehicle ID included in the received dispatch request. The processor 110 then determines that the vehicle is a chartered vehicle if, for example, the login ID included in the received dispatch request is different from the user ID.

[0076] From the above, the processor 110 functions as an example of a memory control unit that associates and stores in a memory device a case selected in the first Gantt chart, a mobile vehicle that transports the case selected in the second Gantt chart, and a driver that drives the mobile vehicle to transport the case, selected in the third Gantt chart.

[0077] In step ST36, the processor 110 generates notification information. For this purpose, the processor 110 refers to the vehicle DB 143 to acquire vehicle information associated with the vehicle ID included in the dispatch request received in step ST32. The processor 110 also refers to the driver DB 144 to acquire driver information associated with the driver ID included in the dispatch request. The processor 110 then generates notification information using the acquired driver information. The notification information includes the case ID and vehicle ID included in the dispatch request, as well as the acquired vehicle information and driver information. The notification information is information that notifies the shipper of the case identified by the case ID that the truck and driver performing the transportation for the case identified by the case ID have been determined. The notification information is also information that indicates a notification of a vehicle number notification. The determination of the truck performing the transportation for the case means, in other words, that the vehicle number of the case has been determined. The truck performing the transportation for the case is, in other words, a truck assigned to be dispatched to the case. The vehicle number notification is, for example, a notification of information about the truck and information about the driver. The contents of the vehicle number notification include, for example, the vehicle type and vehicle number of the truck, and the driver's name and phone number. After generating the notification information, the processor 110 instructs the communication interface 150 to transmit the notification information to the terminal device 200 used by the user who placed the order for the case. If the case is a prime contractor's case, the processor 110 instructs the communication interface 150 to transmit the notification information to the terminal device 200 used by the shipper user who placed the order for the case. On the other hand, if the case is a subcontracted case that is not a prime contractor but is a subcontracted case of a second or lower level, the processor 110 instructs the communication interface 150 to transmit the notification information to the terminal device 200 used by the shipper user who placed the order for the prime contractor's case that is the origin of the case, and to the terminal device 200 used by the transport user who received the higher-level case of the case. Here, the prime contractor's case that is the origin of the case is a first-tier subcontractor's case that is reached when it is transmitted to the parent case of the parent case of the case.The processor 110 also instructs the communication interface 150 to transmit the notification information to the terminal device 200 used by the recipient of the case. Upon receiving the transmission instruction, the communication interface 150 transmits the notification information to each of the terminal devices 200. The transmitted notification information is received by the communication interface 250 of each of the terminal devices 200.

[0078] The processor 210 of the terminal device 200 that has received the notification information causes the display device 270 to display the content of the notification indicated by the notification information.

[0079] In step ST37, the processor 110 determines whether the dispatched truck is a chartered truck. If the processor 110 determines that the truck is not a chartered truck, the processor 110 determines No in step ST37 and returns to step ST31. On the other hand, if the processor 110 determines that the truck is a chartered truck, the processor 110 determines Yes in step ST37 and proceeds to step ST38.

[0080] In step ST38, the processor 110 performs processing for placing an order for a chartered vehicle with the chartering destination. The chartering destination is the user specified by the user ID specified in step ST37. The processor 110, for example, registers the order in the project DB 142 as a new project. The orderer ID of the project information of the project is the login ID included in the received vehicle dispatch request. The order destination ID of the project information is the user ID of the chartering destination. The dispatched vehicle ID of the project information is the vehicle ID included in the vehicle dispatch request. The dispatched driver ID of the project information is the driver ID included in the vehicle dispatch request. The value of the hierarchical information of the project information is the value obtained by adding 1 to the value of the hierarchical information of the original project. The original project is the project specified by the project ID included in the received vehicle dispatch information. The transportation condition information, the designation information, and the baggage information of the project information are, for example, the same as the original project. The order variable of the project information indicates, for example, an unordered state. The original project ID of the project information is the project ID of the original project.

[0081] Furthermore, the processor 110 may transmit information indicating that an order has been placed to the terminal device 200 used by the charterer. After processing of step ST38, the processor 110 returns to step ST31.

[0082] According to the vehicle dispatch system 1 of the embodiment, the server device 100 displays a Gantt chart showing a list of project schedules, a Gantt chart showing a list of truck schedules, and a Gantt chart showing a list of driver schedules. In addition, these three Gantt charts have the same time axis. This allows the dispatcher to rationally confirm the information needed to make decisions when allocating vehicles. Therefore, the vehicle dispatch system 1 of the embodiment can make vehicle dispatch easier than ever before.

[0083] Furthermore, according to the vehicle dispatch system 1 of the embodiment, the server device 100 displays the location of the loading point and the location of the unloading point within the band of the Gantt chart. This makes it easier for the dispatcher to check the information needed to make a decision when allocating vehicles. Therefore, the vehicle dispatch system 1 of the embodiment can make vehicle dispatching easier than ever before.

[0084] According to the vehicle dispatch system 1 of the embodiment, the server device 100 displays at least a part of the designated information and the baggage information on the vehicle dispatch screen SC1-2. Therefore, when selecting a freight vehicle to be used for dispatch, the dispatcher can check the designated information and the baggage information on the same screen, which makes it easy to dispatch the vehicle.

[0085] The above embodiment can be modified as follows.

[0086] The area AR13-1 may display a driver used by the transportation user specified by the selected ID. In this case, the processor 110 of the server device 100 specifies the driver ID associated with the selected ID instead of the login ID in step ST33 of FIG.

[0087] The vehicle dispatch system 1 in the above embodiment is capable of dispatching vehicles for jobs that have already been ordered. However, the vehicle dispatch system 1 may also be capable of dispatching vehicles for jobs that have not yet been ordered. In this case, provisional dispatching of vehicles for jobs that have not yet been ordered can be used as a basis for deciding whether or not to accept the order.

[0088] In the above embodiment, the project involves transporting luggage by truck. However, the project in the embodiment may involve transporting luggage by using a moving object other than a truck.

[0089] In the above embodiment, the users are transport companies and shippers. However, the users may be other than transport companies and shippers.

[0090] In the above embodiment, the job is a job for transporting luggage, but the job may be a job for transporting people.

[0091] In the Gantt chart in the above embodiment, the horizontal axis represents time, and the vertical axis represents a list of jobs, trucks, and drivers. However, the horizontal and vertical axes may be reversed.

[0092] In the above embodiment, the selection is performed in the order of job, truck, and driver, however, the selection order is not limited to this.

[0093] In the vehicle dispatch matching screen SC1 in the above embodiment, the areas are displayed in the order of area AR11, area AR12, and area AR13 from the top. However, the display order is not limited to this. Area AR11 is a general term for areas AR11-1 and AR11-2. Area AR12 is a general term for areas AR12-1 and AR12-2. Area AR13 is a general term for areas AR13-1 and AR13-2.

[0094] The vehicle allocation matching screen SC1 may include any two or more of the areas AR11-1, AR12-1, and AR13-1.

[0095] Each of the devices in the embodiments may be composed of a plurality of devices. Each of the devices in the embodiments may be realized by using cloud computing.

[0096] The processor 110 and the processor 210 may implement part or all of the processes implemented by the programs in the above-described embodiments by using a hardware circuit configuration.

[0097] The program for implementing the process of the embodiment is transferred in a state in which it is stored in, for example, a non-transitory computer-readable storage medium in the device. However, the device may be transferred in a state in which the program is not stored. The program may then be transferred separately and written to the device. The program may be transferred in this case by, for example, recording it in a removable non-transitory computer-readable storage medium, or by downloading it via a network such as the Internet or a LAN.

[0098] Although the embodiment of the present invention has been described above, it is merely an example and does not limit the scope of the present invention. The embodiment of the present invention can be implemented in various forms without departing from the gist of the present invention. [Explanation of symbols]

[0099] 1. Vehicle dispatch system 100 Server Devices 110,210 processors 120,220 ROM 130,230 RAM 140,240 Auxiliary storage 141 User DB 142 Project DB 143 Vehicle DB 144 Driver DB 150,250 Communication Interface 160,280 Bus 200 Terminal Equipment 260 Input Devices 270 Display Devices

Claims

1. a display control unit that displays a first Gantt chart showing a schedule of a transportation project, a second Gantt chart showing a schedule of a moving object and having a time axis coinciding with the first Gantt chart, and a third Gantt chart showing a schedule of a driver and having a time axis coinciding with the first Gantt chart and the second Gantt chart; A vehicle dispatch management device comprising: a memory control unit that associates the case selected in the first Gantt chart, the mobile body that transports the case selected in the second Gantt chart, and the driver that drives the mobile body and transports the case, selected in the third Gantt chart, and stores them in a memory device.

2. 2. The vehicle dispatch management device according to claim 1, wherein at least one of the first Gantt chart, the second Gantt chart, and the third Gantt chart displays the location of the loading point and the location of the unloading point of the job within a horizontal bar indicating a planned period.

3. The vehicle dispatch management device according to claim 1 , wherein the display control displays, together with the second Gantt chart, information on cargo to be transported in the job and information indicating conditions of a mobile object to be used in the job.

4. The processor in the dispatch management device is a display control unit that displays a first Gantt chart showing a schedule of a transportation project, a second Gantt chart showing a schedule of a moving object and having a time axis coinciding with the first Gantt chart, and a third Gantt chart showing a schedule of a driver and having a time axis coinciding with the first Gantt chart and the second Gantt chart; A program that functions as a memory control unit that associates the case selected in the first Gantt chart, the mobile body that transports the case selected in the second Gantt chart, and the driver that drives the mobile body and performs the transportation, selected in the third Gantt chart, and stores them in a memory device.

5. A terminal device and a vehicle dispatch management device are included, The terminal device a display unit that displays a first Gantt chart showing a schedule of a transportation project, a second Gantt chart showing a schedule of a moving object and having a time axis coinciding with the first Gantt chart, and a third Gantt chart showing a schedule of a driver and having a time axis coinciding with the first Gantt chart and the second Gantt chart; a transmission unit that transmits information indicating the job selected in the first Gantt chart, the moving object selected in the second Gantt chart, and the driver selected in the third Gantt chart to the vehicle dispatch management device, The vehicle dispatch management system includes a memory control unit that associates the case selected in the first Gantt chart, the mobile body that transports the case selected in the second Gantt chart, and the driver that drives the mobile body and performs the transportation, selected in the third Gantt chart, and stores them in a memory device.

6. displaying a first Gantt chart showing a schedule of a transportation project, a second Gantt chart showing a schedule of a moving object and having a time axis coinciding with the first Gantt chart, and a third Gantt chart showing a schedule of a driver and having a time axis coinciding with the first Gantt chart and the second Gantt chart; A vehicle dispatch management method, which associates and stores in a storage device the case selected in the first Gantt chart, the mobile body selected in the second Gantt chart for transporting the case, and the driver selected in the third Gantt chart for driving the mobile body to perform the transportation.

Images