Time management apparatus, program, terminal apparatus, time management system, and time management method

Abstract

To provide a time management apparatus, a program, a terminal apparatus, a time management system, and a time management method which can measure and manage at least any one of a cargo waiting time of a driver or the like, a cargo handling work time, and a total time of cargo waiting and cargo handling work, much easier than a conventional method.SOLUTION: A time management apparatus of an embodiment includes a communication unit and a storage control unit. The communication unit receives, from a first terminal device used by a driver who performs transportation and delivery in a case where a cargo is transported and delivered, information which clarifies at least any one of a cargo waiting time, a cargo handling work time, and a total time of cargo waiting and cargo handling in at least either of loading and unloading of the cargo in the case. The storage control unit stores, based on the information received by the communication unit, information which clarifies at least any one of the cargo waiting time, the cargo handling work time, and the total time of cargo waiting and cargo handling in at least either of the loading and the unloading, in association with the case.SELECTED DRAWING: Figure 4

Description

[Technical field]

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

[0002] The 2024 problem in logistics is that the waiting time and loading / unloading work time that occurs at the loading / unloading destination of trucks and other freight vehicles is the cause of long working hours. There is a demand from shippers and transportation companies to know this waiting time (standby time) and loading / unloading work time. For this reason, a method is used in which truck drivers record the actual waiting time and loading / unloading work time for each trip and submit the records to a designated submission destination. However, this method is time-consuming. [Prior art documents] [Patent documents]

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

[0004] The problem that the embodiments of the present invention aim to solve is to provide a time management device, program, terminal device, time management system, and time management method that can measure and manage at least one of the waiting time of drivers and others, the loading and unloading work time, and the total waiting and unloading time more easily than ever before. [Means for solving the problem]

[0005] The time management device of the embodiment includes a communication unit and a storage control unit. The communication unit receives information from a first terminal device used by a driver who transports and delivers a cargo for a cargo delivery job, the information indicating at least one of a cargo waiting time, a cargo handling operation time, and a total cargo handling waiting time for at least one of loading and unloading the cargo for the cargo delivery job. The storage control unit stores the information indicating at least one of a cargo waiting time, a cargo handling operation time, and a total cargo handling waiting time for at least one of loading and unloading the cargo in a storage device in association with the cargo job, based on the information received by the communication unit. [Brief description of the drawings]

[0006] [Figure 1] 1 is a block diagram showing an example of a main configuration of a time management system according to an embodiment and components included in the time management system; [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 terminal device in FIG. 1; [Figure 4] 2 is a flowchart showing an example of processing by a processor of the server device in FIG. 1; [Diagram 5] 2 is a flowchart showing an example of processing by a processor of the terminal device in FIG. 1; [Figure 6] FIG. 11 is a diagram showing an example of a schedule screen displayed on a display device. [Figure 7] FIG. 13 is a diagram showing an example of a details screen displayed on a display device. [Figure 8] FIG. 13 is a diagram showing an example of a time input screen displayed on a display device. [Figure 9] FIG. 4 is a diagram showing an example of an operation information screen displayed on a display device. [Figure 10] FIG. 13 is a diagram showing an example of a management screen displayed on a display device. [Figure 11] FIG. 4 is a diagram showing an example of an operation information screen displayed on a display device. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0007] The time management 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, for the purpose of explanation, each drawing used in the following description of the embodiment may be shown with the configuration omitted. Also, in each drawing and in this specification, the same reference numerals indicate similar elements.

[0008] FIG. 1 is a block diagram showing an example of a time management system 1 according to an embodiment and a main configuration of components included in the time management system 1. Each component of the device may be built-in or external. The time management system 1 provides a time management service. The time management service in this embodiment is a service that measures and records the waiting time and loading / unloading work time of a driver who transports and delivers luggage using a truck or the like. Users who use the time management service are mainly transportation companies that transport and deliver luggage using a truck or the like and shippers of the luggage. The time management system 1 includes, as an example, a server device 100, a terminal device 200, and a terminal device 300. The time management system 1 may include some of these.

[0009] The server device 100, the terminal device 200, and the terminal device 300 are connected to a network NW. The network NW is typically a communication network including the Internet. The network NW is typically a communication network including a WAN (wide area network). 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). The network NW may be a wireless line or a wired line, or may be a mixture of wireless lines and wired lines. The network NW may be a communication network including a dedicated line or a public mobile phone network.

[0010] The server device 100 is a server that provides a time management service. The server device 100 includes, for 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 and the like connect these components. The server device 100 is an example of a time management device.

[0011] 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.

[0012] 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.

[0013] 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.

[0014] 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, and various setting values. Examples of the data stored in the auxiliary storage device 140 include a user DB (database) 141, a case DB 142, a vehicle DB 143, a driver DB 144, and an operation DB 145.

[0015] The user DB 141 is a database that stores and manages information about users who use the time management service. For example, the user DB 141 stores user information for each user in association with a user ID (identifier). The user ID is identification information that is uniquely assigned to each user. In addition, users who use the time management 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 and delivers 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 and deliver luggage. The shipper includes not only the shipper, but also the prime contractor, 3PL (third party logistics), and first-tier subcontracted transportation company entrusted by the shipper. The attributes of a user who uses the time management service may also include a consignee attribute. A user with a consignee attribute is a user who is the consignee of a package to be transported or delivered (hereinafter referred to as a "consignee user"). Note that there may be users with multiple attributes. For example, a user with two attributes, a transportation attribute and a shipper attribute, is a user who both transports and delivers packages and requests the transportation and delivery of packages. User information includes, for example, information about the company such as the company name and address, a list of the user's business offices and information about each office, information about business partners, information about each employee, and information about the bank account used.

[0016] 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 and deliver a package. The case DB 142 stores, for each case, a case ID, information about the case (hereinafter referred to as "case information") and an operation ID in association with each other. The case ID is identification information that is uniquely assigned to each case. The case information includes, for example, an orderer ID, an order destination ID, a consignee ID, a dispatched vehicle ID, a dispatched driver ID, floor information, transportation condition information, designation information, baggage information, order variables, and other information about the case. The orderer ID is the user ID of the shipper user who orders the case. The order destination ID is the user ID of the transportation user who orders the case. The consignee ID is the user ID of the consignee. The dispatched vehicle ID is the vehicle ID of the freight vehicle used for the case. The dispatched driver ID is the driver ID of the driver who drives the freight vehicle in the case. The vehicle ID is identification information that is uniquely assigned to each freight vehicle. 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 for 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 the order for the project has been rejected. Other information about the project includes, for example, the project name, the loading location, the unloading location, the loading date and time, and the unloading date and time. The project information may include a subcontract project ID.The subcontract case ID is the case ID of the subcontract case that is based on this case.

[0017] The operation ID associated with the case ID is an operation ID that identifies the operation that carries out the case. The operation ID is unique identification information for each operation.

[0018] Furthermore, there are two types of cases stored and managed by the case DB 142: own vehicle cases and car charter cases. Own vehicle cases are cases in which the own vehicle is used. Car charter cases are cases in which a chartered car is ordered. Car charter cases are cases in which an order is placed with an outsourced party such as a subcontractor or an in-house sales office. Cases that are not car charter cases are direct cases.

[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] 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.

[0021] Driver DB144 is a database that stores and manages information about each driver used by each transportation user. Driver DB144 stores, for each driver, a driver ID, a user ID, and information about the driver (hereinafter referred to as "driver information") in association with each other. The user ID associated with a 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 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.

[0022] 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.

[0023] The driver DB 144 may store information about drivers who are not drivers used by the transportation users registered in the user DB 141. The driver DB 144 stores driver information about such drivers in association with a guest driver ID. The guest driver ID is unique identification information for each such driver.

[0024] The operation DB 145 is a database that stores and manages the planned and actual operation. For each operation, the operation DB 145 associates an operation ID with a driver ID, operation schedule information, real-time information, status information, and prediction information. The operation ID is unique identification information for each operation. The driver identified by the driver ID performs the operation identified by the operation ID. Multiple driver IDs may be associated with an operation ID. The operation schedule information is information indicating the schedule of the operation. The operation schedule information includes a case ID. The case ID identifies the case to be performed in the operation. The operation schedule information may include multiple case IDs. The operation schedule information preferably includes an operation instruction. The operation schedule information includes, for example, the name of the operation, the date and time of the operation, the date and time of starting the operation, the date and time of ending the operation, the scheduled date and time of leaving the warehouse, the scheduled date and time of returning to the warehouse, the date and time of planning to load the luggage, the date and time of planning to unload the luggage, the date and time of taking a break, and other scheduled dates and times. The operation schedule information also includes, for example, information about the location of departure, loading and unloading of luggage, resting, returning to the warehouse, and other planned locations. The information includes, for example, the name, address, contact information, person in charge, and berth number. The operation schedule information also includes, for example, information about the trucks used for operation, information about luggage to be transported, and other information about the operation.

[0025] The real-time information is information indicating the date and time when various events occurred during operation, and the length of various times during operation. The events are, for example, arrival at the loading destination, start of loading, end of loading, departure from the loading destination, arrival at the unloading destination, start of unloading, end of unloading, departure from the unloading destination, start of operation, end of operation, departure from the warehouse, return to the warehouse, start of rest, end of rest, start of various plans, end of various plans, etc. The lengths of various times are, for example, waiting time at the loading destination, loading and unloading work time at the loading destination, total waiting and unloading time at the loading destination, waiting at the unloading destination, loading and unloading work at the unloading destination, total waiting and unloading time at the unloading destination, operation time, rest time, and various plans.

[0026] The status information is information that indicates the current status of the driver who operates the vehicle, and the forecast information is information that indicates the forecast date and time when the driver who operates the vehicle and the truck will arrive at the destination.

[0027] The communication interface 150 is an interface for the server device 100 to communicate via a network NW etc. The communication interface 150 is an example of a communication device.

[0028] 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 .

[0029] The terminal device 200 is a device that can use the time management service. The terminal device 200 is used, for example, by a user of the time management service. The terminal device 200 is, for example, a personal computer (PC), a tablet terminal, a mobile phone such as a smartphone, or other general-purpose computers. Alternatively, the terminal device 200 may be a dedicated device for using the time management 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 or the like connects these components. The terminal device 200 is an example of a second terminal device used by an orderer who places an order for a job. The terminal device 200 is an example of a third terminal device used by a recipient of an order for a job.

[0030] 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.

[0031] 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.

[0032] 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.

[0033] 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.

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

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

[0036] The input device 260 accepts operations by an operator of the terminal device 200. The input device 260 is, for example, a keyboard, a keypad, a touchpad, a mouse, a controller, etc. The input device 260 may also be a device for inputting voice.

[0037] The display device 270 displays a screen for notifying the operator of the terminal device 200 of various kinds 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.

[0038] 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 .

[0039] The terminal device 300 is a device used by a truck driver. The terminal device 300 is, for example, a smartphone or a tablet terminal. The terminal device 300 may be an on-board device of the truck. The terminal device 300 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, a display device 270, and a positioning unit 310. A bus 280 or the like connects these units. Explanation of the same parts as the terminal device 200 will be omitted. The terminal device 300 is an example of a first terminal device used by a driver who transports and delivers luggage for a project to transport and deliver the luggage.

[0040] The application software stored in the auxiliary storage device 240 of the terminal device 300 includes application software for the driver to input various dates and times (hereinafter referred to as the "driver application"). The driver application may be application software dedicated to a time management service, or may be general-purpose application software such as a web browser.

[0041] The truck driver, for example, uses a driver app to input the start date and time and the end date and time of each task.

[0042] The RAM 230 or the auxiliary storage device 240 of the terminal device 300 stores the driver ID of the driver who uses the terminal device 300.

[0043] The positioning unit 310 is an integrated circuit (IC) chip, module, or circuit that uses a global navigation satellite system (GNSS) such as a global positioning system (GPS) to position and output the position of the terminal device 300. The positioning unit 310 includes, for example, an antenna that receives a GNSS signal from a GNSS satellite. The positioning unit 310 also includes a calculation unit that performs calculations for positioning. The positioning unit 310 outputs the positioning result. Note that the terminal device 300 may be configured such that the processor 110 performs calculations for positioning. In this case, the positioning unit 310 may not include a calculation unit. The positioning unit 310 may also locate the position of the terminal device 300 using a method other than the GNSS. The terminal device 300 may also locate the position of the terminal device 300 using a combination of the GNSS and a method other than the GNSS.

[0044] 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 300 .

[0045] The operation of the time management system 1 according to the embodiment will be described below with reference to Figs. 2 to 5. 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. Figs. 2 and 3 are flowcharts showing an example of the process by the processor 210 of the terminal device 300. The processor 210 executes the process of Figs. 2 and 3 based on a program stored in, for example, the ROM 220 or the auxiliary storage device 240. Fig. 4 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. 4 based on a program stored in, for example, the ROM 120 or the auxiliary storage device 140. Fig. 5 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. 5 based on a program stored in, for example, the ROM 220 or the auxiliary storage device 240.

[0046] The processor 210 of the terminal device 300 starts the processing of Fig. 2 and Fig. 3, for example, when a driver application is started. Note that the processor 210 executes the processing of Fig. 2 and Fig. 3 in parallel or in parallel.

[0047] 2, the processor 210 of the terminal device 300 waits for an operation to instruct displaying the operation schedule. If the operation is performed, the processor 210 judges that the result is Yes in step ST11 and proceeds to step ST12.

[0048] Furthermore, the processor 210 may determine Yes in step ST11 in response to input of a uniform resource identifier (URI), such as a uniform resource locator (URL) for accessing a schedule screen described below. For example, the URI may be stored in a barcode. The barcode is, for example, a two-dimensional code. The driver inputs the URI to the terminal device 300 by having the terminal device 300 read the barcode using a camera or the like. The server device 100 has a function of generating the URI and the barcode. The URI may include at least one of an operation ID and a driver ID.

[0049] The processor 110 of the server device 100 receives issuance instruction information including, for example, a driver ID or an operation ID and generates the URI and the barcode. The issuance instruction information is information for instructing to generate the URI and the barcode for displaying a schedule screen SC1 that displays a schedule of a driver identified by the driver ID or a schedule of an operation identified by the operation ID.

[0050] In step ST12, the processor 210 generates a schedule request. The schedule request includes the driver ID stored in the terminal device 300. The schedule request is information requesting transmission of a driving schedule of a driver identified by the driver ID. The schedule request may include the above-mentioned URI instead of the driver ID. After generating the schedule request, the processor 210 instructs the communication interface 250 to transmit the schedule request to the server device 100. Upon receiving this transmission instruction, the communication interface 250 transmits the schedule request to the server device 100. The transmitted schedule request is received by the communication interface 150 of the server device 100.

[0051] 4, the processor 110 of the server device 100 determines whether or not a schedule request has been received by the communication interface 150. If a schedule request has not been received, the processor 110 determines No in step ST41 and proceeds to step ST42.

[0052] In step ST42, processor 110 determines whether or not input time information has been received by communication interface 150. If input time information has not been received, processor 110 determines No in step ST42 and proceeds to step ST43.

[0053] In step ST43, the processor 110 determines whether or not the positioning information has been received by the communication interface 150. If the positioning information has not been received, the processor 110 determines No in step ST43 and proceeds to step ST44.

[0054] In step ST44, the processor 110 determines whether or not an operation list request has been received by the communication interface 150. If an operation list request has not been received, the processor 110 determines No in step ST44 and proceeds to step ST45.

[0055] In step ST45, the processor 110 determines whether or not an operation request has been received by the communication interface 150. If an operation request has not been received, the processor 110 determines No in step ST45 and returns to step ST41. Thus, the processor 110 enters a standby state in which steps ST41 to ST45 are repeated until a schedule request, input time information, positioning information, operation list request, or operation request is received. The input time information, positioning information, operation list request, and operation request will be described later.

[0056] If a schedule request is received while processor 110 is in a standby state in which steps ST41 to ST45 are repeated, processor 110 determines that the result is Yes in step ST41 and proceeds to step ST46.

[0057] In step ST46, the processor 110 refers to the operation DB 145 to acquire an operation ID and operation schedule information associated with the driver ID included in the schedule request received in step ST41. The processor 110 may acquire operation IDs and operation schedule information for multiple operations. The processor 110 may acquire only an operation ID and operation schedule information for an operation that has not yet ended. The processor 110 may acquire only an operation ID and operation schedule information for an operation that is closest to the current date and time among the operations that have not yet ended. The processor 110 may acquire only an operation ID and operation schedule information for an operation whose date of operation coincides with the current date. The processor 110 may acquire only an operation ID and operation schedule information for an operation within a predetermined period. The predetermined period is, for example, a period based on the current date and time. The processor 110 may identify the driver ID from the URI included in the schedule request.

[0058] If the schedule request includes an operation ID, the processor 110 may obtain operation schedule information associated with the operation ID.

[0059] In step ST47, the processor 110 generates schedule information. The schedule information includes the operation ID and operation schedule information acquired in step ST46. After generating the schedule information, the processor 110 instructs the communication interface 150 to transmit the schedule information to the terminal device 300 that is the sender of the schedule request. In response to this transmission instruction, the communication interface 150 transmits the schedule information to the terminal device 300. The transmitted schedule information is received by the communication interface 250 of the terminal device 300. After processing of step ST47, the processor 110 returns to step ST41.

[0060] 2, the processor 210 of the terminal device 300 waits for schedule information to be received by the communication interface 250. If schedule information has been received, the processor 210 determines Yes in step ST13 and proceeds to step ST14.

[0061] In step ST14, the processor 210 generates an image corresponding to the schedule screen SC1 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 schedule screen SC1.

[0062] FIG. 6 is a diagram showing an example of the schedule screen SC1 displayed on the display device 270. The schedule screen SC1 is a screen that displays the contents of operation schedule information included in the schedule information received in step ST13. The processor 210 targets any one of the operations indicated by one or more operation schedule information included in the schedule information. The processor 210 displays the contents of the operation schedule information of the targeted operation on the schedule screen SC1. For example, the processor 210 targets an operation that is closest to the current date and time among the operations that have not yet ended. The processor 210 may target an operation specified by an operation using the input device 260. The schedule screen SC1 includes areas AR11 to AR13.

[0063] Field AR11 contains the date on which the target operation will be performed. Field AR12 contains the name of the target operation.

[0064] The area AR13 is an area that displays at least a part of the contents of the flight schedule information about the target service. The area AR13 includes, for example, an area AR14 and areas AR15a to AR15c.

[0065] Area AR14 is an area that displays the start or end date and time of the operation.

[0066] The area AR15a is an area that displays information related to the plan to load the luggage. The information includes, for example, the date and time of loading the luggage, and the name and address of the place where the luggage will be loaded. The area AR15a is also a button. The area AR15a is a button that the operator of the terminal device 300 operates when instructing the terminal device 300 to display more detailed information related to the plan to load the luggage.

[0067] Area AR15b is an area that displays information related to the schedule for dropping off the luggage. The information includes, for example, the date and time for dropping off the luggage, and the name and address of the place for dropping off the luggage. Area AR15b also serves as a button. Area AR15b is a button that the operator of the terminal device 300 operates to instruct the terminal device 300 to display more detailed information related to the schedule for dropping off the luggage.

[0068] The area AR15c is an area that displays information about a schedule other than loading and unloading of luggage. The information includes, for example, the contents and date and time of the schedule. The area AR15c is also a button. The area AR15c is a button that the operator of the terminal device 300 operates when instructing the terminal device 300 to display more detailed information about the schedule.

[0069] In step ST15, processor 210 waits for an operation on any of areas AR15. Note that area AR15 is a general term for areas AR15a to AR15c. If any of areas AR15 is operated, processor 210 determines Yes in step ST15 and proceeds to step ST16.

[0070] In step ST16, the processor 210 generates an image corresponding to the details screen SC2 as shown in Fig. 7. Then, the processor 210 instructs the display device 270 to display this generated image. Upon receiving the display instruction, the display device 270 displays the details screen SC2.

[0071] FIG. 7 is a diagram showing an example of the detail screen SC2 displayed on the display device 270. The detail screen SC2 is a screen that displays detailed information about a plan corresponding to the operated area AR15. When the area AR15a is operated, the detail screen SC2 is a screen that displays detailed information about a plan to load luggage (hereinafter referred to as a "detail screen SC2a"). When the area AR15b is operated, the detail screen SC2 is a screen that displays detailed information about a plan to unload luggage (hereinafter referred to as a "detail screen SC2b"). When the area AR15a is operated, the detail screen SC2 is a screen that displays detailed information about a plan other than loading and unloading luggage (hereinafter referred to as a "detail screen SC2c"). The detail screen SC2 shown in FIG. 7 is a screen that displays detailed information about a plan to load luggage. The detail screen SC2 includes buttons B21 to B23, as an example. However, the detail screen SC2c does not need to include the button B22.

[0072] The button B21 is a button operated by the operator of the terminal device 300 when instructing the terminal device 300 to display a map showing the location of the location where the schedule is to be performed. The button B21 on the details screen SC2a is a button operated by the operator of the terminal device 300 when instructing the terminal device 300 to display a map showing the location of the location where the luggage is to be loaded. The button B21 on the details screen SC2b is a button operated by the operator of the terminal device 300 when instructing the terminal device 300 to display a map showing the location of the location where the luggage is to be unloaded.

[0073] The button B22 is a button that is operated by the operator of the terminal device 300 when instructing the terminal device 300 to display the time input screen SC3. The time input screen SC3 will be described later.

[0074] The button B23 is a button that is operated by the operator of the terminal device 300 when instructing the terminal device 300 to return to the schedule screen SC1. When the button B23 is operated, the processor 210 returns to step ST14.

[0075] 2, the processor 210 of the terminal device 200 determines whether or not the button B21 has been operated. If the button B21 has not been operated, the processor 210 determines No in step ST17 and proceeds to step ST18.

[0076] In step ST18, the processor 210 determines whether or not the button B22 has been operated. If the button B22 has not been operated, the processor 210 determines No in step ST18 and returns to step ST17. Thus, the processor 210 enters a standby state in which steps ST17 and ST18 are repeated until the button B21 or the button B22 is operated.

[0077] If the button B21 is operated during a standby state in which steps ST17 and ST18 are repeated, the processor 210 determines that the answer is Yes in step ST17, and proceeds to step ST19.

[0078] In step ST19, the processor 210 generates an image corresponding to the map 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 map screen.

[0079] The map screen is a screen including a map showing the location of the place where the plan is to be carried out. When the map screen is to be ended, the processor 210 returns to step ST16.

[0080] If the button B22 is operated during a standby state in which steps ST17 and ST18 are repeated, the processor 210 determines that the answer is Yes in step ST18, and proceeds to step ST20.

[0081] In step ST20, the processor 210 generates an image corresponding to a time input screen SC3 as shown in Fig. 8. Then, the processor 210 instructs the display device 270 to display this generated image. In response to the display instruction, the display device 270 displays the time input screen SC3.

[0082] FIG. 8 is a diagram showing an example of a time input screen SC3 displayed on the display device 270. The time input screen SC3 is a screen for inputting the date and time of each scheduled event corresponding to the operated area AR15 and transmitting the date and time to the server device 100. The time input screen SC3 (hereinafter referred to as "time input screen SC3a") when the button B22 in the details screen SC2a is operated is a screen for inputting the date and time of each event at the loading destination of the luggage. The time input screen SC3a is a screen for inputting information necessary for determining each time at the loading destination out of the real time information. The time input screen SC3b is a screen for inputting information necessary for determining each time at the unloading destination out of the real time information. The time input screen SC3 (hereinafter referred to as "time input screen SC3b") when the button B22 in the details screen SC2b is operated is a screen for inputting the date and time of each event at the unloading destination of the luggage. The time input screen SC3 when the button B22 in the details screen SC2c is operated (hereinafter referred to as the "time input screen SC3c") is a screen for inputting the date and time when each event in the schedule occurred other than loading and unloading of luggage. The time input screen SC3 shown in FIG. 8 is the time input screen SC3a.

[0083] The time input screen SC3 includes, for example, one or more of an area AR31, an area AR32, a send button B31, a cancel button B32, and a cancel button B33.

[0084] Each area AR31 corresponds to an event, and is used to input the date and time when the corresponding event occurred.

[0085] The time input screen SC3a includes four areas AR31, from area AR31-1 to area AR31-4. The event corresponding to area AR31-1 is the start of waiting or arrival at the loading destination. The event corresponding to area AR31-2 is the start of loading. The event corresponding to area AR31-3 is the end of loading. The event corresponding to area AR31-4 is departure from the loading destination. Note that the time input screen SC3a does not have to include area AR31-3 or area AR31-4.

[0086] The time input screen SC3b includes four areas AR31, from area AR31-5 to area AR31-8. The event corresponding to area AR31-5 is the start of waiting or arrival at the unloading destination. The event corresponding to area AR31-6 is the start of unloading. The event corresponding to area AR31-7 is the end of unloading. The event corresponding to area AR31-8 is departure from the unloading destination. Note that the time input screen SC3b does not have to include area AR31-7 or area AR31-8.

[0087] Events corresponding to the area AR31 in the time input screen SC3c include, for example, the start of operation, the end of operation, leaving the depot, returning to the depot, the start of break, the end of break, the start of schedule, and the end of schedule.

[0088] The area AR31 includes, for example, an area AR311 and an input button B34.

[0089] Area AR32 is a button operated by the operator of terminal device 300 when uploading an image related to the schedule corresponding to the operated area AR15. The image is, for example, an image of a receipt for the completion of unloading, evidence of a stamp, the situation of an accident, or the situation of damage to a package, etc. Area AR32 displays the image specified by the operator.

[0090] The input button B34 is a button that is operated by the operator of the terminal device 300 when a corresponding event occurs. When the input button B34 is operated, the processor 210 displays the current date and time in an area AR311 within the same area AR31.

[0091] Area AR311 is an area that displays the date and time when the corresponding event occurred. Note that the date and time may be directly input into area AR311 without using input button B34. Also, the date and time displayed in area AR311 may be changeable. Processor 210 changes the date and time based on an operational input by the operator.

[0092] The send button B31 is a button that the operator operates to instruct the terminal device 300 to send the image displayed in the area AR32 and the date and time displayed in the area AR311. The cancel button B32 is a button that is operated to cancel the operation of the send button B31.

[0093] The cancel button B33 is a button that the operator operates to instruct the terminal device 300 to return to the details screen SC2. When the cancel button B33 is operated, the processor 210 returns to step ST16.

[0094] In step ST21, the processor 210 determines whether or not any of the input buttons B34 has been operated. If any of the input buttons B34 has not been operated, the processor 210 determines No in step ST21 and proceeds to step ST22.

[0095] In step ST22, the processor 210 determines whether or not the send button B31 has been operated. If the send button B31 has not been operated, the processor 210 determines No in step ST22 and returns to step ST21. Thus, the processor 210 enters a standby state in which steps ST21 and ST22 are repeated until the input button B34 or the send button B31 is operated.

[0096] If the input button B34 is operated while in a standby state in which steps ST21 and ST22 are repeated, the processor 210 determines that the answer is Yes in step ST21, and proceeds to step ST23.

[0097] In step ST23, the processor 210 stores the current date and time in the auxiliary storage device 240 as the time when the event corresponding to the operated input button B34 occurred. The processor 210 also displays the current date and time in the area AR311 in the same area AR31 as the operated input button B34. After the process of step ST23, the processor 210 returns to step ST21.

[0098] If the transmission button B31 is operated while in a standby state in which steps ST21 and ST22 are repeated, the processor 210 determines that the result is Yes in step ST22, and proceeds to step ST24.

[0099] In step ST24, the processor 210 generates input time information. The input time information is information for notifying the server device 100 of various times input on the time input screen SC3. The input time information includes the driver ID stored in the terminal device 300, the operation ID of the target operation, the image displayed in the area AR32, and the date and time displayed in the area AR311. In other words, the date and time displayed in the area AR311 is the date and time stored in step ST23. After generating the input time information, the processor 210 instructs the communication interface 250 to transmit the input time information to the server device 100. Upon receiving this transmission instruction, the communication interface 250 transmits the input time information to the server device 100. The transmitted input time information is received by the communication interface 150 of the server device 100. After processing step ST24, the processor 210 returns to step ST16.

[0100] As described above, by processing steps ST21, ST23, and ST24, processor 210 functions as an example of a control unit that controls the storage and transmission to a time management device of information indicating at least one of the waiting time, loading and unloading work time, and total loading and unloading waiting time for at least one of loading and unloading, based on operational input by the driver.

[0101] On the other hand, if the processor 110 of the server apparatus 100 receives input time information while in a standby state in which steps ST41 to ST45 in FIG. 4 are repeated, the processor 110 judges the result to be Yes in step ST42 and proceeds to step ST48.

[0102] As described above, the processor 110 functions as an example of a communication unit that receives information indicating at least one of a waiting time, a loading / unloading operation time, and a total waiting / loading time for at least one of loading and unloading of a cargo from a first terminal device used by a driver who transports and delivers the cargo in a cargo delivery job by cooperating with the communication interface 150 to perform the process of step ST42. Also, the processor 110 functions as an example of a communication control unit that controls the communication device by controlling the communication interface 150 to perform the process of step ST42.

[0103] In step ST48, the processor 110 updates the real-time information of the operation DB 142 based on the input time information received in step ST42. For this purpose, the processor 110 writes each date and time and image included in the input time information into the real-time information. Note that the real-time information is associated with the operation ID included in the input time information.

[0104] In step ST49, if the input time information includes the arrival date and time of the loading destination and the loading start date and time, the processor 110 calculates the loading destination waiting time. The loading destination waiting time is, for example, the length of time from the arrival at the loading destination to the start of loading. Therefore, the processor 110 calculates the loading destination waiting time, for example, by the following formula. (Waiting time at the loading destination) = (Loading start date and time) - (Arrival date and time at the loading destination) (1)

[0105] Alternatively, the waiting time at the loading destination is the length of time from the date and time of instruction to start loading requested by the shipper or the like (hereinafter referred to as the "loading instruction date and time") to the start of loading. In this case, the processor 110 calculates the waiting time at the loading destination, for example, by the following formula. (Waiting time at destination) = (Loading start date and time) - (Loading instruction date and time) (2)

[0106] Furthermore, when the input time information includes the loading start date and time and the loading end date and time, the processor 110 calculates the loading operation time at the loading destination. The loading operation time at the loading destination is the length of time from the loading start to the loading end. Therefore, the processor 110 calculates the loading operation time at the loading destination, for example, by the following formula. (Loading operation time at destination) = (Loading completion date and time) - (Loading start date and time) (3)

[0107] The processor 110 also calculates the total waiting time for cargo handling at the loading destination, for example, by using any of the following formulas. (Total waiting time at the loading destination) = (Waiting time at the loading destination) + (Loading and unloading time at the loading destination) (4) (Total time waiting for cargo at the loading destination) = (Loading completion date and time) - (Arrival date and time at the loading destination) (5) (Total time waiting for cargo at the loading destination) = (Loading completion date and time) - (Loading instruction date and time) (6)

[0108] Furthermore, when the input time information includes the arrival date and time at the unloading destination and the start date and time of unloading, the processor 110 calculates the waiting time at the unloading destination. The waiting time at the unloading destination is the length of time from the arrival at the unloading destination to the start of unloading. Therefore, the processor 110 calculates the waiting time at the unloading destination, for example, by the following formula. (Waiting time at the unloading destination) = (Start date and time of unloading) - (Arrival date and time of unloading destination) (7)

[0109] Alternatively, the waiting time at the unloading destination is the length of time from the date and time of the instruction to start unloading requested by the shipper, etc. (hereinafter referred to as the "unloading instruction date and time") to the start of unloading. In this case, the processor 110 calculates the waiting time at the unloading destination, for example, by the following formula. (Waiting time at unloading destination) = (unloading start date and time) - (unloading instruction date and time) (8)

[0110] Furthermore, when the input time information includes the unloading start date and time and the unloading end date and time, the processor 110 calculates the loading and unloading work time at the unloading destination. The loading and unloading work time at the unloading destination is the length of time from the unloading start to the unloading end. Therefore, the processor 110 calculates the loading and unloading work time at the unloading destination, for example, by the following formula. (Loading and unloading time at the unloading destination) = (Unloading end date and time) - (Unloading start date and time) (9)

[0111] The processor 110 also calculates the total waiting time for cargo handling at the unloading destination by using, for example, any of the following formulas. (Total time spent waiting for cargo at the unloading destination) = (time spent waiting for cargo at the unloading destination) + (time spent handling cargo at the unloading destination) (10) (Total time waiting for cargo at the unloading destination) = (End of unloading date and time) - (Arrival date and time at the unloading destination) (11) (Total time waiting for unloading at the unloading destination) = (End of unloading date and time) - (Date and time of unloading instruction) (12)

[0112] In addition, when the input time information includes a break start date and time and a break end date and time, the processor 110 calculates the break time. The break time is the length of time from the break start to the break end. Therefore, the processor 110 calculates the break time, for example, by the following formula. (Break time) = (Break end date and time) - (Break start date and time) (13)

[0113] The processor 110 may use the departure date and time of the loading destination instead of the loading end date and time. The processor 110 may use the departure date and time of the unloading destination instead of the unloading end date and time.

[0114] From the above, the combination of the loading start date and time and at least one of the loading destination arrival date and time and the loading instruction date and time is information that indicates the loading destination waiting time. In addition, the loading destination waiting time itself is information that indicates the loading destination waiting time.

[0115] In addition, the combination of at least one of the loading end date and time and the loading destination departure date and time with the loading start date and time is information that indicates the loading operation time at the loading destination. The loading operation time at the loading destination itself is also information that indicates the loading operation time at the loading destination.

[0116] Furthermore, a combination of at least one of the loading end date and time and the loading destination departure date and time, and at least one of the loading destination arrival date and time and the loading instruction date and time, is information that indicates the total waiting time for loading at the loading destination. A combination of at least one of the loading end date and time and the loading destination departure date and time, and at least one of the loading start date and time, and at least one of the loading destination arrival date and time and the loading instruction date and time, is information that indicates the total waiting time for loading at the loading destination. The total waiting time for loading at the loading destination itself is information that indicates the total waiting time for loading at the loading destination.

[0117] In addition, a combination of the unloading start date and time and at least one of the unloading destination arrival date and time and the unloading instruction date and time is information that indicates the waiting time at the unloading destination. In addition, the waiting time at the unloading destination itself is information that indicates the waiting time at the unloading destination.

[0118] In addition, the combination of the unloading end date and time, the unloading destination departure date and time, and the unloading start date and time is information that indicates the loading and unloading work time at the unloading destination. The combination of the unloading destination departure date and time, and the unloading start date and time is information that indicates the loading and unloading work time at the unloading destination. The loading and unloading work time at the unloading destination itself is information that indicates the loading and unloading work time at the unloading destination.

[0119] Furthermore, a combination of at least one of the unloading end date and time and the departure date and time from the unloading destination, and at least one of the arrival date and time at the unloading destination, and at least one of the unloading instruction date and time, is information that indicates the total waiting time for loading and unloading at the unloading destination. A combination of at least one of the unloading end date and time and the departure date and time from the unloading destination, and at least one of the unloading start date and time, the arrival date and time at the unloading destination, and at least one of the unloading instruction date and time, is information that indicates the total waiting time for loading and unloading at the unloading destination. The total waiting time for loading and unloading at the unloading destination itself is information that indicates the total waiting time for loading and unloading at the unloading destination.

[0120] As described above, by performing the processing of step ST49, the processor 110 functions as an example of a calculation unit that calculates the cargo waiting time, the cargo handling operation time, and the total cargo waiting and handling time based on the information received by the communication unit.

[0121] In step ST50, the processor 110 writes the calculation result in step ST49 into the real time information. The real time information to be written is the same as the real time information written in the previous step ST48. After the process of step ST50, the processor 110 returns to step ST41.

[0122] As described above, by performing processing of at least one of steps ST48 and ST50, processor 110 functions as an example of a memory control unit that associates with a case and stores in a memory device information indicating at least one of the waiting time, loading and unloading work time, and total waiting and loading and unloading time for at least one of loading and unloading based on information received by the communication unit.

[0123] On the other hand, in step ST31 of FIG. 3, the processor 210 of the terminal device 300 measures the position of the terminal device 300 using the positioning unit 310.

[0124] In step ST32, the processor 210 generates positioning information. The positioning information includes the driver ID stored in the auxiliary storage device 240, the current date and time, and the position information measured in step ST31. The positioning information may also include the driver's moving speed. The processor 210 acquires the moving speed from, for example, a speed sensor. Alternatively, the processor 210 may calculate the speed using the position information. The moving speed of the driver is also the speed of the truck. After generating the positioning information, the processor 210 instructs the communication interface 250 to transmit the positioning information to the server device 100. Upon receiving this transmission instruction, the communication interface 250 transmits the positioning information to the server device 100. The transmitted positioning information is received by the communication interface 150 of the server device 100. After processing in step ST32, the processor 210 returns to step ST31. As described above, the terminal device 300 periodically transmits its own position information to the server device 100. This location information indicates the driver's location information and the truck's location information.

[0125] On the other hand, if the processor 110 of the server apparatus 100 receives positioning information while in a standby state in which steps ST41 to ST45 in FIG. 4 are repeated, the processor 110 determines Yes in step ST43 and proceeds to step ST51.

[0126] In step ST51, the processor 110 associates the driver ID included in the positioning information received in step ST45 with the location information, date and time, and moving speed included in the positioning information, and stores them in the driver DB 144. After the process of step ST51, the processor 110 returns to step ST41.

[0127] When a user wants to check the details of a service, the user operates the input device 260 to input an instruction to the terminal device 200 to display a list of services. The processor 210 of the terminal device 200 starts the process shown in Fig. 5 in response to the input. Here, the details of the service include, for example, the details of the service schedule information, the details of the real-time information, and the location information of the terminal device 300.

[0128] In step ST61 of FIG. 5, the processor 210 of the terminal device 200 generates a traffic list request. The traffic list request includes, as an example, a login ID. The traffic list request is information requesting transmission of a list of cases with confirmed vehicle numbers among cases ordered by a shipper user or a transport user identified by the login ID. After generating the traffic list request, the processor 210 instructs the communication interface 250 to transmit the traffic list request to the server device 100. Upon receiving this transmission instruction, the communication interface 250 transmits the traffic list request to the server device 100. The transmitted traffic list request is received by the communication interface 150 of the server device 100.

[0129] If an operation list request is received while processor 110 is in a standby state in which steps ST41 to ST45 are repeated, processor 110 determines that the answer is Yes in step ST44, and proceeds to step ST52.

[0130] In step ST52, the processor 110 refers to the case DB to identify cases ordered by the user identified by the user ID included in the operation list request received in step ST44. Then, the processor 110 identifies the operation ID associated with the case ID of each identified case.

[0131] In step ST53, the processor 110 generates operation list information. The operation list information includes the operation list and the operation ID identified in step ST52. The operation list is information indicating a list of operations identified by the operation ID identified in step ST52. After generating the operation list information, the processor 110 instructs the communication interface 150 to transmit the operation list information to the terminal device 200 that is the sender of the operation list request. Upon receiving this transmission instruction, the communication interface 150 transmits the operation list information to the terminal device 200. The transmitted operation list information is received by the communication interface 250 of the terminal device 200. After processing step ST53, the processor 110 returns to step ST41.

[0132] 5, the processor 210 of the terminal device 200 waits for operation list information to be received by the communication interface 250. If operation list information is received, the processor 210 determines "Yes" in step ST62 and proceeds to step ST63.

[0133] In step ST63, the processor 210 generates an image corresponding to the operation list screen based on the operation list information received in step ST62. Then, the processor 210 instructs the display device 270 to display the generated image. Upon receiving the display instruction, the display device 270 displays the operation list screen.

[0134] The operation list screen is a screen that displays a list of operations to be performed for cases ordered by a user identified by a login ID. Each operation displayed on the operation list screen can be selected by operating the input device 260. In addition, the operation list screen includes, as an example, a details button. The details button is a button that is operated when instructing the terminal device 200 to display details of a selected case.

[0135] When the user wishes to check detailed information about an event displayed on the operation list screen, the user operates the details button, for example, with the operation in question selected.

[0136] In step ST64, processor 210 waits for the operation of the details button to be operated with any operation selected. If the details button is operated with any operation selected, processor 210 determines Yes in step ST64 and proceeds to step ST65.

[0137] In step ST65, the processor 210 generates an operation request. The operation request includes, as an example, a login ID and an operation ID of the selected operation. The operation request is information requesting transmission of detailed information about the operation specified by the operation ID. After generating the operation request, the processor 210 instructs the communication interface 250 to transmit the operation request to the server device 100. Upon receiving this transmission instruction, the communication interface 250 transmits the operation request to the server device 100. The transmitted operation request is received by the communication interface 150 of the server device 100.

[0138] On the other hand, if an operation request is received while the processor 110 of the server device 100 is in a standby state in which steps ST41 to ST45 in FIG. 4 are repeated, the processor 110 judges the result to be Yes in step ST45 and proceeds to step ST54.

[0139] In step ST54, the processor 110 refers to the operation DB 145 to acquire a driver ID, operation schedule information, and real time information associated with the operation ID included in the operation request received in step ST45. The processor 110 also refers to the driver DB 144 to acquire location information and date and time associated with the driver ID. The processor 110 may also acquire a speed associated with the driver ID.

[0140] In step ST55, the processor 110 uses the real-time information acquired in step ST54 to determine the transportation status of the case identified by the case ID included in the operation request received in step ST45. The transportation status indicates the current status of the operation of the case. The transportation status can be, for example, operation not started, released, running, waiting to be loaded, loading, loading completed, waiting to be unloaded, unloading, unloading completed, and operation completed. As an example, the processor 110 determines the transportation status as follows.

[0141] The processor 110 determines that the vehicle has finished traveling if the real-time information includes the return date and time or the end date and time of traveling. Otherwise, the processor 110 determines that the vehicle is traveling if the real-time information includes the departure date and time of the unloading destination. Otherwise, the processor 110 determines that the vehicle is unloading if the real-time information includes the end date and time of unloading. Otherwise, the processor 110 determines that the vehicle is unloading if the real-time information includes the start date and time of unloading. Otherwise, the processor 110 determines that the vehicle is waiting for unloading if the real-time information includes the arrival date and time of the unloading destination. Otherwise, the processor 110 determines that the vehicle is traveling if the real-time information includes the departure date and time of the loading destination. Otherwise, the processor 110 determines that the vehicle is loading if the real-time information includes the end date and time of loading. Otherwise, the processor 110 determines that the vehicle is loading if the real-time information includes the start date and time of loading. Otherwise, if the real-time information includes the date and time of arrival at the loading destination, processor 110 considers the vehicle to be waiting for loading. Otherwise, if the real-time information includes the date and time of departure or the date and time of operation start, processor 110 considers the vehicle to have been departed. Otherwise, processor 110 considers the vehicle to have not yet started operation. As described above, each date and time functions as a flag that determines the transportation status depending on its presence or absence. For example, the date and time of return to the warehouse and the date and time of operation end function as flags that indicate the end of operation.

[0142] The processor 110 also writes the determined transportation status into the status information associated with the operation ID included in the received input time information.

[0143] In step ST56, the processor 110 uses the latest location information and date and time acquired in step ST56 to calculate the predicted date and time when the driver who operates the vehicle will arrive at the destination (hereinafter referred to as the "predicted arrival date and time"). The date and time when the driver will arrive at the destination is also the date and time when the truck used for the job will arrive at the destination. If the transportation status determined in step ST55 is "unloaded", the processor 110 calculates the predicted arrival date and time with the destination as the loading destination. If the transportation status is "loading completed", the processor 110 calculates the predicted arrival date and time with the destination as the unloading destination. If the transportation status is "unloading completed", the processor 110 calculates the predicted arrival date and time with the destination as the return location. In addition, if the calculated predicted arrival date and time is later than the scheduled date and time, the processor 110 calculates the predicted delay time. The predicted delay time is the difference between the predicted arrival date and time and the scheduled date and time. The processor 110 may calculate the time it will take to arrive (hereinafter referred to as the "predicted arrival time") instead of the predicted arrival date and time or in addition to the predicted arrival date and time. The predicted arrival date and time, the predicted arrival time, and the predicted delay time are collectively referred to as arrival prediction information.

[0144] In addition, the processor 110 writes the calculated predicted arrival date and time into the prediction information associated with the operation ID included in the received input time information.

[0145] The processor 110 may notify a user, such as a consignee user, of the arrival prediction information by transmitting the calculated arrival prediction information to a terminal device 200 used by the user. For this purpose, the processor 110 instructs the communication interface 150 to transmit the arrival prediction information. Upon receiving this transmission instruction, the communication interface 150 transmits the arrival prediction information to the terminal device 200. The transmitted arrival prediction information is received by the communication interface 250 of the terminal device 200. The processor 210 of the terminal device 200 notifies the user of the arrival prediction information by displaying the arrival prediction information on the display device 270, for example.

[0146] In step ST57, the processor 110 generates operation information. The operation information includes the operation schedule information, real time information, position information, and date and time acquired in step ST54. The operation information also includes the transportation status determined in step ST55. The operation information also includes the arrival prediction information calculated in step ST56. The operation information may also include the speed acquired in step ST54. Alternatively, the processor 110 may calculate the driver's speed using the position information acquired in step ST54. The operation information may also include the speed calculated here. After generating the operation information, the processor 110 instructs the communication interface 150 to transmit the operation information to the terminal device 200 that is the source of the operation request. In response to this transmission instruction, the communication interface 150 transmits the operation information to the terminal device 200. The transmitted operation information is received by the communication interface 250 of the terminal device 200. After processing in step ST57, the processor 110 returns to step ST41.

[0147] As described above, the processor 110 functions as an example of a communication unit that transmits at least one of the waiting time, the loading and unloading operation time, and the total waiting and loading / unloading time to at least one of a second terminal device used by the ordering party placing the order for the project and a third terminal device used by the recipient of the project, by working in cooperation with the communication interface 150 to process step ST57.

[0148] In addition, by working in cooperation with the communication interface 150 to process steps ST43 and ST57, the processor 110 functions as an example of a communication unit that receives location information of a first terminal device and transmits the location information to at least one of a second terminal device used by an orderer placing an order for the project and a third terminal device used by a recipient of the project.

[0149] 2, the processor 210 of the terminal device 200 waits for operation information to be received by the communication interface 250. If operation information has been received, the processor 210 determines "Yes" in step ST66 and proceeds to step ST67.

[0150] In step ST67, the processor 210 generates an image corresponding to the operation information screen SC4 as shown in Fig. 9. 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 operation information screen SC4. When the processor 210 ends the display of the operation information screen SC4, the process returns to step ST61.

[0151] FIG. 9 is a diagram showing an example of an operation information screen SC4 displayed on the display device 270. The operation information screen SC4 is a screen that displays at least a part of operation schedule information, real-time information, transportation status, and arrival prediction information included in the operation information received in step ST66 for the operation selected on the operation list screen. When the real-time information includes each time, the operation information screen SC4 displays each time. It is preferable that the real-time information includes cargo waiting time and cargo handling operation time. When the real-time information includes an image, the operation information screen SC4 may display the image. Furthermore, the operation information screen SC4 is a screen that displays operation position information.

[0152] The operational location information is information indicating the location of the driver in charge of the case. The driver's location is also the location of the freight vehicle used for the case. If the case is after the start of the operation and before the end of the operation, the operational location information includes the current location of the driver. If the case is after the start of the operation, the operational location information includes the change in the location of the driver from the start of the operation to before the end of the operation.

[0153] The operation information screen SC4 includes, for example, a detailed area AR41, a detailed area AR42, and a map area AR43. The detailed area AR41 is an area that displays at least a part of the operation details. The detailed area AR40 includes, for example, areas AR411 to AR416. The detailed area AR40 also includes the scheduled start and end dates and times of loading of the luggage at the luggage destination, the location of the luggage destination, the name of the luggage to be loaded at the luggage destination, and other information related to the luggage destination. The detailed area AR40 also includes the scheduled start and end dates and times of unloading of the luggage at the luggage destination, the location of the luggage destination, the name of the luggage to be unloaded at the luggage destination, and other information related to the luggage destination.

[0154] Areas AR411 to AR416 are areas that display real-time information. Therefore, the times displayed in areas AR411 to AR416 are not scheduled times but actual times taken.

[0155] An area AR411 displays the waiting time at the destination of the cargo. An area AR412 displays the loading operation time at the destination of the cargo. An area AR413 displays the total waiting time at the destination of the cargo.

[0156] An area AR414 displays the waiting time at the destination of the cargo. An area AR415 displays the cargo handling time at the destination. An area AR416 displays the total waiting time at the destination.

[0157] The processor 210 changes the display manner for the area AR413, for example, by highlighting the total waiting time for loading the cargo at the loading destination when the total waiting time for loading the cargo exceeds a predetermined time P1. The processor 210 also changes the display manner for the area AR416, for example, by highlighting the total waiting time for loading the cargo at the unloading destination when the total waiting time for loading the cargo exceeds a predetermined time P2. The times P1 and P2 are determined, for example, by the administrator, designer, or user of the time management system 1. The times P1 and P2 may be the same length or different lengths. As an example, the times P1 and P2 are both one hour.

[0158] The processor 210 may change the manner of displaying the areas AR413 and AR416 when the total time of waiting for cargo at the loading destination and the total time of waiting for cargo at the unloading destination exceeds a predetermined time P3. The time P3 is, for example, two hours. The processor 210 may also change the manner of displaying at least one of the areas AR411, AR412, AR414, and AR415 when at least one of the waiting time at the loading destination, the loading operation time at the loading destination, the waiting time at the unloading destination, and the loading operation time at the unloading destination exceeds a predetermined time.

[0159] The details area AR42 displays details of the trip other than the contents displayed in the details area AR41. The display contents of the details area AR42 are omitted in Fig. 9. The details include, for example, information about the transport company that transports and delivers the cargo in the trip, information about the driver who performs the trip, and information about the freight truck that performs the trip. The details also include, for example, detailed information about the loading and unloading destinations and on-site precautions.

[0160] The map area AR43 is an area that displays the operation position information using a map. The map area AR43 displays the driver's position indicated by the operation position information on the map. The map area AR43 also displays the positions of the loading destination, unloading destination, and other destinations on the map. The map area AR43 also displays the distance from the driver's position to the destination position. The distance may be a distance along a route from the driver's position to the destination position or a straight-line distance. The map area AR43 may also display the driver's travel speed. The map area AR140 may also display the estimated date and time when the driver will arrive at the destination, and the estimated time it will take for the driver to arrive at the destination.

[0161] As described above, the terminal device 200 displays the operation information screen SC4 in response to receiving the operation position information. Therefore, the processor 110 of the server device 100 cooperates with the communication interface 150 to transmit the operation position information, thereby functioning as an example of a communication unit that causes at least one of the second terminal device and the third terminal device to display the position indicated by the position information and the distance from the position to the destination.

[0162] The operation information screen SC4 shown in Fig. 9 displays information about one operation. However, the terminal device 200 may be capable of displaying a screen including information about multiple operations or multiple cases. As an example of such a screen, a management screen SC5 is shown in Fig. 10. The processor 210 obtains information necessary for displaying the management screen SC5 from the server device 100.

[0163] FIG. 10 is a diagram showing an example of the management screen SC5 displayed on the display device 270. The management screen SC5 is, for example, a screen for budget / actual management that manages the operation schedule and operation results of the vehicle and the chartered vehicle for all cases on a specified date or during a specified period, and for status management of the vehicle. The management screen SC5 includes, for each of a plurality of cases, whether loading has been completed, the company name of the shipper user who ordered the case, the vehicle number of the truck that will transport the case, whether the vehicle or the chartered vehicle will be used, and the latest location indicated by the operation location information. In addition, the management screen SC5 includes, for each of a plurality of cases, the scheduled start date and time, scheduled end date and time, start date and time, start date and time, and end date and time of waiting for at least one of loading and unloading.

[0164] The management screen SC5 allows the user to select a case or an operation. The processor 210 displays details of the selected case or operation. The processor 210 displays details of the selected case or operation, for example, on an operation information screen SC4 as shown in Fig. 9 or an operation information screen SC6 as shown in Fig. 11.

[0165] 11 is a diagram showing an example of an operation information screen SC6 displayed on the display device 270. As an example, the operation information screen SC6 includes, for the operation selected on the management screen SC5, the vehicle number of the truck performing the transportation and delivery, the name of the driver performing the transportation and delivery, the scheduled date and time of arrival at each point, the date and time of actual arrival at each point, the waiting time at the loading destination, the loading destination loading operation time, the total waiting and loading time at the loading destination, the waiting time at the unloading destination, the loading destination loading operation time, and the total waiting and loading time at the unloading destination. The processor 210 changes the way of displaying the area of ​​the operation information screen SC6 where the time exceeding the predetermined time is displayed, similar to the operation information screen SC4.

[0166] The processor 210 may overlay and display the operation management screen SC6 on the management screen SC5. The processor 210 may use the management screen SC5 as the operation list screen. The processor 210 may display the operation information screen SC6 instead of the operation information screen SC4.

[0167] According to the time management system 1 of the embodiment, the server device 100 receives information from the terminal device 300 that indicates at least one of the waiting time, the loading and unloading work time, and the total loading and unloading time, based on the received information, and stores the information that indicates at least one of the waiting time, the loading and unloading work time, and the total loading and unloading time, in association with the case. Therefore, by using the time management system 1 of the embodiment, the burden on the driver and the user is reduced. As described above, the time management system 1 of the embodiment can measure and manage at least one of the waiting time, the loading and unloading work time, and the total loading and unloading time for a case more easily than in the past. Furthermore, by using the time management system 1 of the embodiment, the user can easily grasp at least one of the waiting time, the loading and unloading work time, and the total loading and unloading time.

[0168] According to the time management system 1 of the embodiment, the server device 100 stores information about the case, information about the operation for performing the case, information about the driver performing the operation, and information about the truck performing the operation in association with each other. This allows the server device 100 of the embodiment to manage the case, the truck, and the driver in association with each other. Furthermore, the server device 100 of the embodiment can measure and manage the waiting time and the loading and unloading work time for each case, which is associated with the case, the vehicle, and the driver, more easily than before. A device conventionally used in operation management, such as a digital tachograph, stores information on operation results, but does not store other information. Therefore, it is impossible to manage information like the server device 100 of the embodiment.

[0169] According to the time management system 1 of the embodiment, the server device 100 stores information that indicates the waiting time, the loading and unloading work time, and the total loading and unloading time in association with the case. Therefore, the time management system 1 of the embodiment makes it easier to know the waiting time, the loading and unloading work time, and the total loading and unloading time for the case than in the past.

[0170] According to the time management system 1 of the embodiment, the server device 100 transmits at least one of the waiting time, the loading and unloading work time, and the total waiting and unloading time to the terminal device 200. This allows the user of the terminal device 200 to grasp the waiting time, the loading and unloading work time, and the total waiting and unloading time.

[0171] Moreover, according to the time management system 1 of the embodiment, the server device 100 transmits the driver's location information to the terminal device 200. Therefore, by using the time management system 1 of the embodiment, the user can know where the driver is or has been.

[0172] According to the time management system 1 of the embodiment, the server device 100 calculates the waiting time, the loading and unloading work time, and the total loading and unloading time. This eliminates the need for the user to calculate the waiting time, the loading and unloading work time, and the total loading and unloading time.

[0173] The driver, for example, uses a driver app to input the loading destination arrival date and time (start date and time of waiting), loading start date and time (end date and time of waiting), loading end date and time, and loading destination departure date and time at the loading destination. The driver, for example, inputs the timing of arrival at the loading destination, the timing of loading start, the timing of loading end, and the timing of departure from the loading destination, thereby inputting the loading destination arrival date and time, loading start date and time, loading end date and time, and loading destination departure date and time. The input is, for example, pressing a button displayed on the terminal device 300. The time management system 1 of the embodiment calculates the loading destination waiting time, loading operation time, and waiting loading total loading time at the loading destination using the date and time input by the driver. Therefore, the time management system 1 of the embodiment makes it easier to calculate these times than before.

[0174] The driver also inputs the arrival date and time at the unloading destination (start date and time of waiting for cargo), the start date and time of unloading (end date and time of waiting for cargo), the end date and time of unloading, and the departure date and time from the unloading destination, for example, by using a driver app. The driver inputs the arrival date and time at the unloading destination, the start date and time of unloading, the end date and time of unloading, and the departure date and time from the unloading destination, for example, by making a predetermined input for each of the timing of arrival at the unloading destination, the timing of start of unloading, the timing of end of unloading, and the timing of departure from the unloading destination. The time management system 1 of the embodiment calculates the waiting time, the loading and unloading work time, and the total loading and unloading time at the unloading destination using the dates and times input by the driver. Therefore, the time management system 1 of the embodiment makes it easier to calculate these times than before.

[0175] The terminal device 300 used by the driver transmits its own position measured by GNSS, i.e., the position of the truck (driver), to the server. According to the time management system 1 of the embodiment, the server device 100 acquires the position from the terminal device 300. Then, the server device 100 of the embodiment displays the location of each truck (each driver) on a map. Therefore, by using the time management system 1 of the embodiment, the user can easily know where each truck (each driver) is.

[0176] Moreover, according to the time management system 1 of the embodiment, the server device 100 displays the distance from the truck (driver) to the destination. Therefore, the user can easily grasp the distance by using the time management system 1 of the embodiment.

[0177] Moreover, according to the time management system 1 of the embodiment, the server device 100 displays the predicted date and time when the truck (driver) will arrive at the destination. Therefore, the user can easily know the date and time by using the time management system 1 of the embodiment.

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

[0179] The time management system 1 of the embodiment may be capable of displaying on a map the position of the freight vehicle (driver) in charge of the case when receiving an input specifying a case. The time management system 1 of the embodiment may be capable of displaying on a map the position of the freight vehicle (driver) in charge of the case where the freighter is the specified shipper when receiving an input specifying a shipper. The time management system 1 of the embodiment may be capable of displaying on a map the position of the freight vehicle (driver) in charge of the case where the freighter is the specified shipper when receiving an input specifying a shipper and a case. In addition, the time management system 1 of the embodiment may be capable of displaying information on the case where the selected freight vehicle or driver is in charge. The freight vehicle and the driver may be selected from the map. The case information includes the start time and end time of each task, etc., input by the driver.

[0180] In the above embodiment, the time input screen SC3 allows the user to input the date and time when various events occurred. The time input screen SC3 may also allow the user to input various lengths of time. In this case, the processor 110 of the server device 100 does not need to calculate the time in step ST49 of FIG. 4.

[0181] In the above embodiment, the time is input based on the operation of the input button B34. However, the terminal device 300 or another device may automatically input the time. The other device may be, for example, a digital tachograph. The time may also be input by another method.

[0182] In the above embodiment, the job involves transporting and delivering luggage by truck. However, the job in the embodiment may involve transporting and delivering luggage by using a moving object other than a truck.

[0183] The time may be used instead of the date and time. Note that the date and time is a type of time.

[0184] In the above embodiment, part of the processing executed by the server device 100 may be executed by the terminal device 200 or the terminal device 300. In the above embodiment, part of the processing executed by the terminal device 200 or the terminal device 300 may be executed by the server device 100.

[0185] 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.

[0186] 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.

[0187] 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 therein. The program may then be transferred separately and written to the device. In this case, the program may be transferred by, for example, recording the program in a removable non-transitory computer-readable storage medium, or by downloading the program via a network such as the Internet or a LAN (local area network).

[0188] 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]

[0189] 1. Time Management 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 145 Operation DB 150,250 Communication Interface 160,280 Bus 200,300 terminal devices 260 Input Devices 270 Display Devices 310 Positioning Unit

Claims

1. a communication unit that receives information indicating at least one of a waiting time, a loading / unloading operation time, and a total waiting / loading time for at least one of loading and unloading of the luggage in the luggage transport / delivery job from a first terminal device used by a driver who transports and delivers the luggage in the luggage transport / delivery job; A time management device comprising: a memory control unit that stores information indicating at least one of the waiting time, the loading and unloading operation time, and the total waiting loading and unloading time in a memory device in association with the case based on the information received by the communication unit.

2. The time management device of claim 1, wherein the memory control unit stores in a memory device the information indicating at least one of the waiting time, the loading and unloading work time, and the total waiting and unloading time, in association with the case, the driver, and the freight truck that transports and delivers the case.

3. The communication unit receives the information indicating the waiting time, the loading and unloading operation time, and the total waiting loading and unloading time in the loading and unloading from the first terminal device, 2. The time management device according to claim 1, wherein the memory control unit stores the information indicating the waiting time, the loading and unloading work time, and the total waiting loading and unloading time in the memory device in association with the case.

4. The time management device described in claim 1, wherein the communication unit transmits at least one of the waiting time, the loading and unloading operation time, and the total waiting loading and unloading time to at least one of a second terminal device used by an ordering party that places an order for the project and a third terminal device used by an order recipient of the project.

5. the communication unit receives location information of the first terminal device, and transmits the location information to at least one of a second terminal device used by an orderer placing an order for the job and a third terminal device used by a recipient of the job; The time management device according to claim 1 , wherein the storage control unit stores the position information in a storage device.

6. The time management device according to claim 5, wherein the communication unit causes at least one of the second terminal device and the third terminal device to display the location indicated by the location information, the distance from the location to a destination, and / or a predicted time at which the driver will arrive at the destination.

7. 2. The time management device according to claim 1, further comprising a calculation unit that calculates the cargo waiting time, the cargo handling operation time, and the cargo waiting total cargo handling time based on the information received by the communication unit.

8. A processor included in a time management device having a communication device, a communication control unit that controls the communication device to receive information indicating at least one of a waiting time, a loading / unloading operation time, and a total waiting / loading time for at least one of loading and unloading of the luggage in the luggage transport / delivery job from a first terminal device used by a driver who transports and delivers the luggage in the luggage transport / delivery job; A program that functions as a memory control unit that stores information indicating at least one of the waiting time, the loading and unloading work time, and the total waiting loading and unloading time in a memory device in association with the case based on the information received by the communication device.

9. A time management system is configured together with a time management device including a communication unit that receives information from a first terminal device used by a driver who transports and delivers a cargo in a cargo delivery job, the information indicating at least one of a cargo waiting time, a cargo handling operation time, and a total cargo handling time for loading and / or unloading the cargo in the cargo delivery job, and a storage control unit that stores, based on the information received by the communication unit, the information indicating at least one of a cargo waiting time, a cargo handling operation time, and a total cargo handling time for loading and / or unloading the cargo in a storage device in association with the cargo delivery job, The first terminal device is equipped with a control unit that controls the storage of information indicating at least one of the waiting time, the loading and unloading work time, and the total waiting loading and unloading time based on operational input by the driver and the transmission of the information to the time management device.

10. a processor provided in the first terminal device which constitutes a time management system together with a time management device including a communication unit which receives information from a first terminal device used by a driver who transports and delivers a cargo in a cargo delivery job, the information indicating at least one of a cargo waiting time, a cargo handling operation time, and a total cargo handling time for loading and / or unloading the cargo in the cargo delivery job, and a storage control unit which stores, based on the information received by the communication unit, the information indicating at least one of a cargo waiting time, a cargo handling operation time, and a total cargo handling time for loading and / or unloading the cargo in a storage device in association with the cargo delivery job; A program that functions as a control unit that controls the storage of information indicating at least one of the waiting time, the loading and unloading time, and the total waiting loading and unloading time for at least one of the loading and unloading based on operational input by the driver, and the transmission of the information to the time management device.

11. A time management device and a terminal device are included. The time management device is a communication unit that receives information from the first terminal device used by a driver who transports and delivers a package for transporting and delivering the package, the information indicating at least one of a waiting time, a loading and unloading operation time, and a total waiting and loading and unloading time for at least one of loading and unloading the package for the package; a storage control unit that stores information indicating at least one of the waiting time, the loading and unloading operation time, and the total waiting time for loading and unloading based on the information received by the communication unit in a storage device in association with the case; A time management system, comprising: a control unit which controls the storage and transmission to the time management device of information indicating at least one of the waiting time for at least one of the loading and unloading, the loading and unloading operation time, and the total waiting and loading and unloading time, based on operational input by the driver.

12. Transmitting information indicating at least one of a waiting time, a loading / unloading operation time, and a total waiting / loading time for at least one of loading and unloading of the luggage in the luggage transport / delivery job based on an operation input by a driver who transports and delivers the luggage in the luggage transport / delivery job, receiving said information; A time management method in which, based on the received information, information indicating at least one of the waiting time for at least one of the loading and unloading, the loading and unloading work time, and the total waiting and loading and unloading time is stored in a storage device in association with the case.

Images