Generating apparatus, program, and generating method

Abstract

To provide a generating apparatus, a program, and a generating method which can reduce the time and effort in a transportation contract.SOLUTION: A generating apparatus according to an embodiment includes an acquiring unit and a generating unit. The acquiring unit is used for generating a transportation application for placing an order in a case of transporting a cargo, and acquires, from a storage device storing previously created contract master data, the previously created contract master data. The generating unit generates data indicating the transportation application for placing an order for the case by using the contract master data, and stores the data indicating the transportation application in the storage device.SELECTED DRAWING: Figure 2

Description

[Technical field]

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

[0002] To enter into a transportation contract for a case of transporting goods, it is necessary to exchange documents related to the request for transportation, such as a basic contract or transportation application form, and a transportation acceptance letter. However, the exchange of such documents is time-consuming. [Prior art documents] [Patent documents]

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

[0004] The problem to be solved by the embodiments of the present invention is to provide a generation device, a program, and a generation method that can reduce the effort required for transportation contracts. [Means for solving the problem]

[0005] The generating device of the embodiment includes an acquiring unit and a generating unit. The acquiring unit acquires contract master data from a storage device that stores pre-created contract master data used for generating a transportation application form for placing an order for a case to transport luggage. The generating unit generates data representing the transportation application form for placing an order for the case using the contract master data, and stores the data representing the transportation application form in the storage device. [Brief description of the drawings]

[0006] [Figure 1] 1 is a block diagram showing an example of a main configuration of a vehicle dispatch system according to an embodiment and components included in the vehicle dispatch system 1. FIG. [Diagram 2] 2 is a flowchart showing an example of processing by a processor of the server device in FIG. 1; [Diagram 3] 2 is a flowchart showing an example of processing by a processor of the server device in FIG. 1; [Figure 4] 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] 2 is a flowchart showing an example of processing by a processor of the terminal device in FIG. 1; [Figure 7] 2 is a flowchart showing an example of processing by a processor of the terminal device in FIG. 1; [Figure 8] 2 is a flowchart showing an example of processing by a processor of the terminal device in FIG. 1; [Figure 9] 2 is a flowchart showing an example of processing by a processor of the terminal device in FIG. 1; [Figure 10] 2 is a flowchart showing an example of processing by a processor of the terminal device in FIG. 1; [Figure 11] 2 is a flowchart showing an example of processing by a processor of the server device in FIG. 1; [Figure 12] 2 is a flowchart showing an example of processing by a processor of the terminal device in FIG. 1; [Figure 13] 2 is a flowchart showing an example of processing by a processor of the terminal device in FIG. 1; [Figure 14] FIG. 2 is a diagram showing an example of an order input screen displayed on the display device in FIG. 1. [Figure 15] FIG. 2 is a diagram showing an example of a detailed area displayed on the display device in FIG. 1. [Figure 16] FIG. 2 is a diagram showing an example of an amount area displayed on the display device in FIG. 1. [Figure 17] FIG. 2 is a diagram showing an example of an operation information screen displayed on the display device in FIG. 1. [Figure 18] FIG. 2 is a diagram showing an example of a management screen displayed on the display device in FIG. 1. [Figure 19] FIG. 2 is a diagram showing an example of an operation information screen displayed on the display device in FIG. 1. [Figure 20] FIG. 2 is a diagram showing an example of a time input screen displayed on the display device in FIG. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0007] Hereinafter, a vehicle dispatch system according to an embodiment will be described with reference to the drawings. Note that, for the sake of explanation, the drawings used in the following description of the embodiment may omit configurations. In addition, in each drawing and in this specification, the same reference numerals denote similar elements.

[0008] FIG. 1 is a block diagram showing an example of a main configuration of a vehicle dispatch system 1 according to an embodiment and components included in the vehicle dispatch system 1. Each component of each device may be built-in or external. The vehicle dispatch system 1 is a system that provides a vehicle dispatch service. Users who use the vehicle dispatch service are mainly transportation companies that transport luggage using trucks and the like, and shippers of the luggage. The vehicle dispatch service is a service that supports vehicle dispatch and billing for luggage transportation projects. The vehicle dispatch system 1 includes, as an example, a server device 100, a terminal device 200, and a terminal device 300. Note that FIG. 1 shows only one server device 100, one terminal device 200, and one terminal device 300, but the number of each device is not limited. Furthermore, the vehicle dispatch system 1 typically includes multiple terminal devices 200 and multiple terminal devices 300.

[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 device such as a server that provides a vehicle dispatch service. The server device 100 includes, as an example, a processor 110, a read-only memory (ROM) 120, a random-access memory (RAM) 130, an auxiliary storage device 140, and a communication interface 150. A bus 160 or the like connects these components. The server device 100 is an example of a generating 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, various setting values, and the like. The data stored in the auxiliary storage device 140 includes, for example, a user DB (database) 141, a case DB 142, a vehicle DB 143, a driver DB 144, an operation DB 145, and a billing DB 146.

[0015] The user DB 141 is a database that stores and manages information about users who use the vehicle dispatch service. For example, the user DB 141 stores user information 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 vehicle dispatch service have multiple types of attributes. The attributes include a transportation attribute, a shipper attribute, a consignee attribute, a loading destination attribute, and an unloading destination attribute. A user with a transportation attribute (hereinafter referred to as a "transportation user") is a user who transports luggage. Therefore, a transportation company, etc. is a transportation user. A transportation company and an office within the transportation company may be different users. A user with a shipper attribute (hereinafter referred to as a "shipper user") is a user who becomes a shipper who requests a transportation company to transport luggage. A shipper includes not only a shipper but also a prime contractor, a 3PL (third party logistics), and a first-tier subcontracted transportation company entrusted by the shipper. A user with the consignee attribute is a user who is the consignee of the cargo to be transported (hereinafter referred to as the "consignee user"). A user with the destination attribute is a user who operates and manages the location where the cargo is loaded (hereinafter referred to as the "destination user"). A user with the unloading destination attribute is a user who operates and manages the location where the cargo is unloaded (hereinafter referred to as the "destination user"). There may be users with multiple attributes. For example, a user who has both a transportation attribute and a shipper attribute is a user who both transports cargo and requests the transportation of cargo. 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] Furthermore, the user DB 141 stores the contract master in association with the user ID of the shipper user. The number of contract masters associated with one user ID is not limited. Each contract master is assigned a contract ID. The contract ID is identification information unique to each contract master. The contract ID is included in the contract master. The contract master indicates, for example, the agreed contract contents or the contents set based on the reference data. The reference data is, for example, the case information of the case stored in the case DB. The case information will be described later. The contents include, for example, various conditions, freight charges, and fees. The contract master is information used to automatically generate a transportation application form. The transportation application form is a document indicating an application for a contract for a transportation case. The contract master may include information included in an order other than the information included in the transportation application form. The contract master is also used for automatically inputting information required for an order. The contract master includes, for example, information on the orderer, information on the cargo, information on the loading destination, information on the unloading destination, information on the designated vehicle type and mileage / time, and information on the consideration. The contract master may also include freight calculation rules, mileage from the loading destination to the unloading destination, waiting fees at the loading destination and the unloading destination, handling fees at the loading destination and the unloading destination, fees for the total waiting time at the loading destination and the unloading destination, and incidental fees at the loading destination and the unloading destination, as well as payment methods. The freight calculation rules indicate whether the freight is calculated based on distance, time, individual, or other freight calculation methods. The payment methods include, for example, the closing date, the site, and the payment method. In addition to the above, the contract master may also include information included in the case information described below.

[0017] The information about the orderer includes, for example, the orderer's name, the orderer's office name, the project name, and the flight name.

[0018] The information about the cargo includes, for example, the name, quality, packing style, weight, volume, number of pieces, total weight, total volume, type of high-value cargo, value of cargo, information about transportation insurance, and special provisions.

[0019] Information about the destination includes, for example, the name of the destination, the address of the destination, the expected waiting time, the address of the waiting location, notes about the waiting location, waiting time fee at the destination, whether or not independent loading and unloading will be performed, the expected loading and unloading time, loading fee (loading and unloading work fee at the destination), notes about loading and unloading, information about ancillary work, the expected work time for ancillary work, and the fee for ancillary work.

[0020] Information about the drop-off destination includes, for example, the name of the drop-off destination, the address of the drop-off destination, the expected waiting time, the address of the waiting location, notes about the waiting location, waiting time fee at the drop-off destination, whether or not independent loading and unloading is required, expected loading and unloading time, unloading fee (loading and unloading work fee at the drop-off destination), loading and unloading notes, information about ancillary work, expected work time for ancillary work, and fees for ancillary work.

[0021] The information on the designated vehicle type and mileage / travel time includes, for example, the vehicle type, class, shape, size, and equipment of the vehicle used in the case. The information on the designated vehicle type and mileage / travel time also includes, for example, information on the jurisdiction of the transport bureau, the type of transportation handled, fuel surcharge, expected mileage, expected travel time, and other surcharges.

[0022] The information on the consideration includes, for example, freight, expected toll, other surcharge, fuel surcharge, waiting charge at the loading destination, handling charge at the loading destination, ancillary charge at the loading destination, waiting charge at the unloading destination, handling charge at the unloading destination, ancillary charge at the unloading destination, total freight, total fee, total freight and fee, and a utilization transportation fee. The utilization transportation fee is a fee when a project is subcontracted.

[0023] The user DB141 also stores a tariff master in association with the user ID of the transportation user. The tariff master is information used to automatically generate a transportation acceptance. The tariff master is also information used to automatically generate a transportation application. The tariff master includes information related to the price such as the freight and fee for transporting the luggage. The transportation acceptance is a document indicating the acceptance of the contract applied for by the transportation application. The tariff master includes the freight calculation rule, the fuel consumption by vehicle or by type of vehicle, the unit price by vehicle or by type of vehicle, the fee for waiting at the loading destination and the unloading destination, the cargo handling fee at the loading destination and the unloading destination, the fee for the total time for waiting and handling at the loading destination and the unloading destination, and the incidental fee at the loading destination and the unloading destination. The freight calculation rule indicates whether the freight is calculated based on a distance freight, a time freight, an individual freight, or another freight calculation method. The freight calculation rule also includes the calculation method when another freight calculation method is used. The charge for waiting includes, for example, a charge up to a predetermined time P11, and a charge for each predetermined time P12 after the time P11. The handling charge at the loading destination includes, for example, a charge up to a predetermined time P13. The handling charge at the unloading destination includes, for example, a charge up to the time P13. The charge for the total waiting handling time includes, for example, an amount up to each predetermined time P15 after the time P14. The time P11 is, for example, 30 minutes. The time P12 is, for example, 30 minutes. The time P13 is, for example, 30 minutes. The time P14 is, for example, 2 hours. The time P15 is, for example, 30 minutes.

[0024] Note that default values ​​may be set in the newly created tariff master, which may, for example, follow the standard fare announcement.

[0025] The case DB 142 is a database that stores and manages information about cases. In this embodiment, a case refers to a case of a request to a transportation company to transport luggage. The case DB 142 stores, for each case, a case ID, information about the case (hereinafter referred to as "case information") and an operation ID in association with the case ID. The case ID is identification information that is uniquely assigned to each case. The case information includes, for example, an orderer ID, a supplier ID, a consignee ID, a loading destination ID, an unloading destination ID, a dispatched vehicle ID, a dispatched driver ID, a subcontractor case ID, hierarchical information, transportation condition information, real time information, designation information, luggage information, an order variable, a confirmed variable, case change information, a registered contract ID, and other information about the case. The orderer ID is the user ID of the shipper user of the orderer who placed the case. The supplier ID is the user ID of the transportation user of the order recipient of the case. The consignee ID is the user ID of the consignee. The loading destination ID is the user ID of the loading destination. The drop-off destination ID is the user ID of the drop-off destination. 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 for the case. The vehicle ID is identification information uniquely assigned to each freight vehicle. The vehicle ID may be identification information for the dispatch system 1, or may be existing identification information such as the vehicle registration number, the vehicle number, the WCN (wireless call number), the vehicle-mounted device management number, or the ETC (electronic toll collection) card number. The driver ID is identification information uniquely assigned to each driver. The subcontracted case ID is the case ID of the subcontracted case based on this case. The hierarchical information is information indicating which subcontracting level this case is. The transportation condition information is information indicating the transportation condition. The designation information is information indicating the conditions of the vehicle used for the case. The conditions include, for example, the vehicle model, the vehicle rank, the shape, the size, and the equipment of the vehicle. The baggage information is information about the baggage to be transported in the case. The parcel information includes, for example, the name, weight, volume, and number of parcels. The order variable is information that indicates the order status of the case. The order variable indicates, by its value, which of a number of states the case is in, including three types of states: not yet ordered, ordered, and rejected.The unordered state is a state in which the order for the case has not been accepted or rejected. The accepted 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 case has been rejected. The confirmed variable is information indicating whether the truck that will transport the case has been confirmed. The confirmed variable indicates, by its value, one of two types of states, an unconfirmed state or a confirmed state. The unconfirmed state indicates that the truck that will transport the case has not been confirmed. The confirmed state indicates that the truck that will transport the case has been confirmed. Other information about the case includes, for example, the case name, the loading place, the unloading place, the loading date and time, the unloading date and time, and the payment method. The case change information indicates whether the contents of the case have been changed. In addition, the case change information includes the changes to the case. The registered contract ID is the contract ID of the contract master registered in the case. In addition, the case information includes a transportation application form and a transportation acceptance. In other words, the case information includes data indicating a transportation application form and data indicating a transportation acceptance. In addition to the above, the case information may also include information included in the contract master. In addition to the above, the case information may also include information included in the fee schedule master. It can be said that each piece of information in the case information is related to each other.

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

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

[0028] Furthermore, an nth-tier subcontractor's project includes a master project ID. The master project ID is the project ID of the project (hereinafter referred to as the "master project") that is the basis for the order for the chartered vehicle. If the project is a subcontractor's project, the project indicated by the master project ID is the project of the master contractor (first tier subcontractor). If the project is an nth-tier subcontractor's project, the project indicated by the master project ID is the project of the (n-1)th tier subcontractor. n is an integer of 2 or greater. Note that a subcontractor of a master contractor may also be referred to as a first tier subcontractor, but in this specification, a master contractor is referred to as a first tier subcontractor and a subcontractor of a master contractor is referred to as a second tier subcontractor.

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

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

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

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

[0033] 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 the operation, information about the luggage to be transported, and other information about the operation.

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

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

[0036] The billing DB 146 is a database that stores and manages billing information for cases. The billing DB 146 stores information about a bill (hereinafter referred to as "billing information") in association with a billing ID for each bill. The billing ID is identification information that is uniquely assigned to each bill. The billing information includes a billing case ID, a billing source ID, a billing destination ID, amount information, an approval variable, and other information about the bill. The billing case ID is a case ID that indicates which case the bill is for. The billing source ID is the user ID of the transport user of the billing source. The billing destination ID is the user ID of the user of the billing destination. The amount information includes information about the amount of the bill, such as the billed amount and its breakdown. The approval variable is a variable that indicates whether the bill has been approved. The approval variable indicates, depending on the value, which of the three types of states the associated bill is in: an unapproved state, an approved state, or an approval refusal state. The unapproved state is a state in which the bill is neither approved nor rejected. The approved state is a state in which the bill is approved. The approved state also indicates that the amount of the bill has been determined. The approval denied state is a state in which approval of the claim has been denied.

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

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

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

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

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

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

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

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

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

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

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

[0048] The printing device 280 prints images of invoices and the like onto paper, etc. The printing device 280 may be any of a variety of printers, such as a dot matrix printer, an inkjet printer, a thermal printer, a laser printer, or any other type of printer.

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

[0050] 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 290 or the like connects these units. Descriptions of the same parts of the terminal device 300 as those of the terminal device 200 will be omitted.

[0051] 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 billing service, or may be general-purpose application software such as a web browser.

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

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

[0054] The operation of the vehicle dispatch system 1 according to the embodiment will be described below with reference to Figs. 2 to 13 and the like. 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 to 4 and 11 are flowcharts showing an example of the process by the processor 110 of the server device 100. The processor 110 executes the processes of Figs. 2 to 4 and 11 based on a program stored in, for example, the ROM 120 or the auxiliary storage device 140. Figs. 5 to 10 are flowcharts showing an example of the process by the processor 210 of the terminal device 200. The processor 210 executes the processes of Figs. 5 to 10 based on a program stored in, for example, the ROM 220 or the auxiliary storage device 240. Note that Figs. 5, 9 and 10 show the processes executed by the terminal device 200 used by the shipper user. Figs. 6, 8 and 10 show the processes executed by the terminal device 200 used by the transport user. Fig. 10 shows the processes executed by the terminal devices 200 used by the loading destination user and the unloading destination user. 12 and 13 are flowcharts showing an example of processing by the processor 210 of the terminal device 300. The processor 210 executes the processing of FIGS. 12 and 13 based on a program stored in the ROM 220 or the auxiliary storage device 240, for example.

[0055] The processor 210 of the terminal device 200 starts the process shown in FIG. 5 in response to, for example, an input instructing to display a menu related to ordering an item.

[0056] When a shipper user wishes to change or create a new contract master, the shipper user inputs an instruction to the terminal device 200 to display a screen for inputting information contained in the contract master (hereinafter referred to as the "contract input screen").

[0057] 5, the processor 210 of the terminal device 200 judges whether or not an input instructing to display a contract input screen has been received. If the processor 210 has not received an input instructing to display a contract input screen, the processor 210 judges No in step ST61 and proceeds to step ST62.

[0058] Furthermore, when the shipper user wishes to place an order for a project, he or she operates the input device 260 to input to the terminal device 200 the contract master to be used for the order.

[0059] In step ST62, the processor 210 judges whether or not an input specifying the contract master to be used for ordering has been received. If the processor 210 has not received an input specifying the contract master to be used for ordering, the processor 210 judges No in step ST62 and returns to step ST61.

[0060] In step ST63, the processor 210 judges whether or not an input has been received instructing to display a list of orders whose contents have been changed. If the processor 210 has not received an input instructing to display a list of orders whose contents have been changed, the processor 210 judges No in step ST63 and returns to step ST61. Thus, the processor 210 enters a standby state in which steps ST61 to ST63 are repeated until an input is received instructing to display a contract input screen, an input is received specifying a contract master to be used for ordering, or an input is received instructing to display a list of orders whose contents have been changed.

[0061] If the processor 210 receives an input instructing to display the contract input screen while in a standby state in which steps ST61 to ST63 are repeated, the processor 210 judges Yes in step ST61 and proceeds to step ST64. The shipper user also performs an operational input indicating whether to create a new contract master or to change an existing contract master. If the shipper user changes an existing contract master, the shipper user performs an operational input specifying which contract master to change. Furthermore, when creating a new contract master, the vehicle dispatch system 1 can create the contract master using existing case information. If the shipper user uses existing case information, the shipper user performs an operational input specifying which case's case information to use.

[0062] In step ST64, the processor 210 generates a contract request. The contract request includes, as an example, a login ID. When an input indicating that an existing contract master is to be changed is made, the contract request also includes a contract ID. The contract ID is the contract ID of the contract master to be changed, designated by the shipper user. When a contract master is created using existing case information, the contract request includes a case ID indicating the case information. The contract request is information requesting the transmission of the contract master used by the shipper user identified by the login ID. After generating the contract request, the processor 210 instructs the communication interface 250 to transmit the contract request to the server device 100. Upon receiving this transmission instruction, the communication interface 250 transmits the contract request to the server device 100. The transmitted contract request is received by the communication interface 150 of the server device 100.

[0063] 2, the processor 110 of the server device 100 determines whether or not a contract request has been received by the communication interface 150. If a contract request has not been received, the processor 110 determines No in step ST1 and proceeds to step ST2.

[0064] In step ST2, the processor 110 determines whether or not the contract information has been received by the communication interface 150. If the contract information has not been received, the processor 110 determines No in step ST2 and proceeds to step ST3.

[0065] In step ST3, processor 110 determines whether or not an application form generation request has been received by communication interface 150. If an application form generation request has not been received, processor 110 determines No in step ST3 and proceeds to step ST5.

[0066] In step ST4, the processor 110 determines whether or not an automatic input request has been received by the communication interface 150. If an automatic input request has not been received, the processor 110 determines No in step ST4 and proceeds to step ST5.

[0067] In step ST5, the processor 110 determines whether or not a tariff request has been received by the communication interface 150. If a tariff request has not been received, the processor 110 determines No in step ST5 and proceeds to step ST6.

[0068] In step ST6, the processor 110 determines whether or not the fee table information has been received by the communication interface 150. If the fee table information has not been received, the processor 110 determines No in step ST6 and proceeds to step ST7.

[0069] In step ST7, the processor 110 determines whether or not an acceptance letter generation request has been received by the communication interface 150. If an acceptance letter generation request has not been received, the processor 110 determines No in step ST7 and proceeds to step ST8 in FIG.

[0070] In step ST8, the processor 110 of the server device 100 determines whether or not the order information has been received by the communication interface 150. If the order information has not been received, the processor 110 determines No in step ST8 and proceeds to step ST9.

[0071] In step ST9, the processor 110 determines whether or not an order list request has been received by the communication interface 150. If an order list request has not been received, the processor 110 determines No in step ST9 and proceeds to step ST10.

[0072] In step ST10, the processor 110 determines whether or not approval information has been received by the communication interface 150. If approval information has not been received, the processor 110 determines No in step ST10 and proceeds to step ST11.

[0073] In step ST11, the processor 110 determines whether or not change information has been received by the communication interface 150. If change information has not been received, the processor 110 determines No in step ST11 and proceeds to step ST12.

[0074] In step ST12, the processor 110 determines whether or not rejection information has been received by the communication interface 150. If rejection information has not been received, the processor 110 determines No in step ST12 and proceeds to step ST13.

[0075] In step ST13, processor 110 determines whether or not the host vehicle information has been received by communication interface 150. If the host vehicle information has not been received, processor 110 determines No in step ST13 and proceeds to step ST14 in FIG.

[0076] In step ST14, the processor 110 determines whether or not vehicle chartering order information has been received by the communication interface 150. If vehicle chartering order information has not been received, the processor 110 determines No in step ST14 and proceeds to step ST16.

[0077] In step ST16, the processor 110 determines whether or not a case list request has been received by the communication interface 150. If a case list request has not been received, the processor 110 determines No in step ST16 and proceeds to step ST17.

[0078] In step ST17, the processor 110 determines whether or not request information has been received by the communication interface 150. If request information has not been received, the processor 110 determines No in step ST17 and proceeds to step ST18.

[0079] In step ST18, processor 110 determines whether or not a bill list request has been received by communication interface 150. If a bill list request has not been received, processor 110 determines No in step ST18 and proceeds to step ST19.

[0080] In step ST19, the processor 110 determines whether or not billing approval information has been received by the communication interface 150. If the processor 110 has not received billing approval information, the processor 110 determines No in step ST19 and returns to step ST1 in Fig. 2. Thus, the processor 110 enters a standby state in which steps ST1 to ST19 in Figs. 2 to 4 are repeated until a contract request, contract information, application form creation request, automatic input request, rate table request, rate table information, acceptance document creation request, order information, order list request, approval information, change information, rejection information, own vehicle information, chartered vehicle order information, case list request, request information, billing list request, or billing approval information is received. The order list request, approval information, rejection information, own vehicle information, chartered vehicle order information, case list request, request information, billing list request, and billing approval information will be described later.

[0081] If a contract request is received while processor 110 is in a standby state in which steps ST1 to ST19 in FIGS. 2 to 4 are repeated, processor 110 determines Yes in step ST1 in FIG. 2 and proceeds to step ST20.

[0082] In step ST20, if the contract request includes a contract ID, the processor 110 refers to the user DB 141 to acquire a contract master identified by the contract ID. On the other hand, if the contract request does not include a contract ID, the processor 110 acquires a newly created contract master. To this end, the processor 110 refers to the user DB 141 to acquire user information associated with the user ID. The processor 110 then automatically inputs information that can be input from the information included in the user information into the newly created contract master. Furthermore, the processor 110 assigns a contract ID to the newly created contract. Furthermore, if the contract request includes a matter ID, the processor 110 refers to the matter DB 142 to acquire matter information identified by the matter ID. The processor 110 then automatically inputs information that can be input from the information included in the matter information into the newly created contract master.

[0083] Note that items that can be entered from information included in user information refer to items that are common between the user information items and the contract master items. Items that can be entered from information included in case information refer to items that are common between the case information items and the contract master items.

[0084] In step ST21, the processor 110 instructs the communication interface 150 to transmit the contract master acquired in step ST20 to the terminal device 200. Upon receiving this transmission instruction, the communication interface 150 transmits the contract master to the terminal device 200. The transmitted contract master is received by the communication interface 250 of the terminal device 200. After processing step ST21, the processor 110 returns to step ST1.

[0085] 5, the processor 210 of the terminal device 200 waits for the contract master to be received by the communication interface 250. If the contract master is received, the processor 210 judges "Yes" in step ST65 and proceeds to step ST66.

[0086] In step ST66, the processor 210 generates an image corresponding to the contract input 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 contract input screen.

[0087] The contract input screen displays the contents of the contract master received in step ST65. The operator of the terminal device 200 can change the contents of the contract master displayed on the contract input screen by inputting changes to the contract master. Note that inputting new content into a field where no content has been input is also considered a change to the content. The contract input screen also includes a send button. The send button is a button that the operator operates when instructing the terminal device 200 to send the changes to the server device 100 and reflect the changes.

[0088] In step ST67, the processor 210 waits for the operation of the send button on the contract input screen. If the send button is operated, the processor 210 determines Yes in step ST67 and proceeds to step ST68.

[0089] In step ST68, the processor 210 generates contract information. The contract information includes the login ID, the contract ID, and the changes input on the contract input screen. The contract information is information that instructs the contract master identified by the contract ID to reflect the changes. The contract ID is the contract ID of the contract master received in step ST65. After generating the contract information, the processor 210 instructs the communication interface 250 to transmit the contract information to the server device 100. Upon receiving this transmission instruction, the communication interface 250 transmits the contract information to the server device 100. The transmitted contract information is received by the communication interface 150 of the server device 100. After processing in step ST68, the processor 210 returns to step ST61.

[0090] On the other hand, if contract information is received while the processor 110 of the server device 100 is in a standby state in which steps ST1 to ST19 in Figures 2 to 4 are repeated, it determines Yes in step ST2 in Figure 2 and proceeds to step ST22.

[0091] Meanwhile, in step ST22 of Fig. 2, the processor 110 of the server device 100 updates the contract master stored in the user DB 141. The contract master is the contract master identified by the contract ID included in the received contract information. The update contents are indicated by the changes included in the contract information. After processing step ST22, the processor 110 returns to step ST1.

[0092] If processor 210 receives an input specifying a contract master to be used for ordering while in a standby state in which steps ST61 to ST63 are repeated, processor 210 judges the result to be Yes in step ST62 and proceeds to step ST69.

[0093] In step ST69, the processor 210 instructs the communication interface 250 to send an application form generation request to the server device 100. The application form generation request includes a contract ID. The application form generation request is information that instructs the generation of a transportation application form using a contract master identified by the contract ID. The contract ID is the contract ID of the contract master specified to be used for the order. Upon receiving this instruction to send, the communication interface 250 sends the application form generation request to the server device 100. The sent application form generation request is received by the communication interface 150 of the server device 100.

[0094] On the other hand, if an application form generation request is received while the processor 110 of the server device 100 is in a standby state in which steps ST1 to ST19 in FIGS. 2 to 4 are repeated, the processor 110 judges the result to be Yes in step ST3 in FIG. 2 and proceeds to step ST23.

[0095] In step ST23, if the contract ID is included in the application form generation request, the processor 110 refers to the user DB 141 and acquires the contract master identified by the contract ID included in the received application form generation request. The processor 110 then generates a transportation application form using the contract master. At this time, the processor 110 automatically inputs into each item of the transportation application form what information can be input from the information included in the transportation contract master. The transportation application form includes, for example, applicant information, payment method, and cargo information. Applicant information is information about the applicant. The applicant is the person who orders the project. Applicant information includes the company name, the name of the person in charge, an address, and contact information. Contact information is, for example, a telephone number, a fax number, and an email address. Cargo information includes loading destination information, unloading destination information, the condition of the luggage (cargo), and date and time information.

[0096] The information on the loading destination includes, for example, the address, name, and contact information of the loading destination. The information on the destination includes, for example, the address, name, and contact information of the destination.

[0097] The status of the luggage includes, for example, the name, quality, weight or volume, number of pieces, packing style, and total weight or total volume of the luggage.

[0098] The date and time information includes, for example, a desired collection or shipping date and time, and a desired delivery or arrival date and time.

[0099] The transportation application form may include, for example, supplier information, project name, vehicle condition information, number of trips per day, other information on the loading destination, other information on the unloading destination, consignee information, other information on the cargo to be transported, scheduled operation date and time, scheduled start date and time of waiting for loading, scheduled start date and time of loading (scheduled end date and time of waiting for loading), scheduled end date and time of loading, scheduled start date and time of waiting for unloading, scheduled start date and time of unloading (scheduled end date and time of waiting for unloading), scheduled end date and time of unloading, freight information, charges for invoiced freight and paid freight, charges for loading and unloading before operation, freight charges used, contract contents such as transportation conditions, contents of the transportation contract, matters agreed upon before operation, instructions regarding transportation, items related to logistics transaction operations, other conditions, comments on the project, matters to be communicated to the driver, and attached documents. Each scheduled date and time may be a range or a specific date and time.

[0100] The supplier information is information about the supplier, and includes information that can identify which transport user the supplier is. Information that can identify which transport user the supplier is, for example, is the user ID of the transport user. The vehicle condition information is information that indicates the conditions of the freight vehicle used to transport the goods. The vehicle condition information includes, for example, the vehicle type, shape, loading capacity, loading platform size, vehicle equipment, vehicle options, and the number of vehicles. Other information about the loading destination includes, for example, information about the facility of the unloading destination, information about the surrounding roads, information about the waiting place, the loading and unloading conditions of the loading destination, the berth number, and other information about the loading destination. Other information about the unloading destination includes, for example, information about the facility of the unloading destination, information about the surrounding roads, information about the waiting place, the loading and unloading conditions of the loading destination, the berth number, and other information about the unloading destination. The consignee information is information about the consignee, and includes information that can identify which user the consignee is. Information that can identify which user the consignee is, for example, is the user ID of the consignee user. Other information on the cargo to be transported includes, for example, an image of the cargo, information indicating the item, dimensions, number, weight, quantity, product identification code, and control number, as well as notes regarding the cargo. Freight information is information regarding the freight, which is the price for transportation, various fees, and their billing. Freight information includes, for example, freight, tolls, incidental fees, loading and unloading fees, waiting fees, fuel surcharges, whether or not tolls can be billed, and accounting classification. The accounting classification indicates the accounting date of the case. The accounting date is, for example, the departure or arrival date of the cargo transportation.

[0101] As described above, by acquiring the contract master in the processing of step ST23, processor 110 functions as an example of an acquisition unit that acquires contract master data from a storage device that stores pre-created contract master data to be used for generating a transportation application form for placing an order for transporting cargo.

[0102] In step ST24, the processor 110 instructs the communication interface 150 to transmit the transportation application form generated in step ST23 to the terminal device 200. Upon receiving this instruction to transmit, the communication interface 150 transmits the transportation application form to the terminal device 200. The transmitted transportation application form is received by the communication interface 250 of the terminal device 200. After processing step ST24, the processor 110 returns to step ST1.

[0103] In step ST70, the processor 210 waits for a transportation application to be received by the communication interface 250. If a transportation application has been received, the processor 210 determines "Yes" in step ST70 and proceeds to step ST71.

[0104] In step ST71, the processor 210 generates an image corresponding to the order input screen SC1 as shown in Fig. 14. 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 order input screen SC1.

[0105] The processor 210 may obtain from the server device 100 a part or all of the data required to display the order input screen SC1.

[0106] FIG. 14 is a diagram showing an example of an order input screen displayed on the display device 270. The order input screen SC1 is a screen for inputting information required for ordering. The order input screen SC1 includes an order control and an order button. The order control is a control (widget) for inputting each piece of information used for ordering. The order control is, for example, a check box, list box, combo box, text box, and other controls. The order button is a button for instructing the vehicle dispatch system 1 to execute an order. The order button is a button that is operated after each piece of information used for ordering is input.

[0107] The information used for ordering that can be entered into the order input screen SC1 includes the contents of the transportation application form. The processor 210 displays the received contents of the transportation application form on the order input screen SC1. The operator can change the contents of the transportation application form and input new contents into the transportation application form.

[0108] The order input screen SC1 may also be capable of inputting information other than the contents of the transportation application. Such information includes, for example, supplier information, case name, vehicle condition information, business office, number of trips per day, loading destination information, unloading destination information, consignee information, information on the cargo to be transported, scheduled operation date and time, scheduled loading waiting start date and time, scheduled loading start date and time (scheduled loading waiting end date and time), scheduled loading end date and time, scheduled unloading waiting start date and time, scheduled unloading start date and time (scheduled unloading waiting end date and time), scheduled unloading end date and time, freight information, charges for billed freight and paid freight, charges for loading and unloading before operation, transportation charges, contract contents such as transportation conditions, contents of the transportation contract, matters agreed upon before operation, instructions regarding transportation, items related to logistics transaction operations, other conditions, comments on the case, matters to be communicated to the driver, and attached documents.

[0109] It is not necessary to input all the information used for ordering, but only the necessary information may be input. Also, among the information used for ordering, information that must be input may be set.

[0110] Furthermore, the order input screen SC1 can automatically input prices such as freight and fees using a price list master. The price list master is the price list master of the supplier. The price list master is the price list master associated with the user ID of the supplier in the user DB 141. The order input screen SC1 includes an automatic input button B11 for automatically inputting the price.

[0111] When supplier information and information required for calculating the fee (hereinafter referred to as "fee calculation information") have been input, the operator can operate the automatic input button B11 to instruct the terminal device 200 to automatically input the fee. The fee calculation information is, for example, the loading address and the unloading address. The fee calculation information may include other information. The fee calculation information may be other information.

[0112] In step ST72, processor 210 determines whether or not an input instructing automatic input of the consideration has been received. If an input instructing automatic input of the consideration has not been received, processor 210 determines No in step ST72 and proceeds to step ST73.

[0113] In step ST73, the processor 210 determines whether or not an operation to execute an order has been performed. That is, the processor 210 determines whether or not a predetermined operation, such as operating an order button after inputting each piece of information used for an order, has been performed. If an operation to execute an order has not been performed, the processor 210 determines No in step ST73 and returns to step ST72. Thus, the processor 210 enters a standby state in which steps ST72 and ST73 are repeated until an input instructing automatic input of the price is received or an operation to execute an order is performed.

[0114] If processor 210 receives an input instructing automatic input of the consideration while in a standby state in which steps ST72 and ST73 are repeated, it determines Yes in step ST72 and proceeds to step ST74.

[0115] In step ST74, the processor 210 generates an automatic input request. Here, the automatic input request includes, for example, a login ID, a user ID of the supplier, price designation information, and price calculation information. The user ID of the supplier is the user ID of the user indicated by the supplier information entered on the order input screen. The price designation information is information that designates which price to automatically calculate. Here, the price designation information is, for example, a price that has not been entered on the order input screen SC1. The automatic input request is information that requests the price designated by the price designation information to be calculated. After generating the automatic input request, the processor 210 instructs the communication interface 250 to transmit the automatic input request to the server device 100. Upon receiving this instruction to transmit, the communication interface 250 transmits the automatic input request to the server device 100. The transmitted automatic input request is received by the communication interface 150 of the server device 100.

[0116] On the other hand, if the processor 110 of the server device 100 receives an automatic input request while in a standby state in which steps ST1 to ST19 in FIGS. 2 to 4 are repeated, the processor 110 judges the result to be Yes in step ST5 in FIG. 2 and proceeds to step ST25.

[0117] In step ST25, if a planned price is specified in the price specification information, the processor 110 refers to the user DB 141 and acquires the fee table master associated with the user ID of the user identified by the supplier information included in the received automatic input request. The processor 110 then calculates the price specified in the automatic input request using the price calculation information included in the automatic input request. The case where the actual price is specified in the price specification information will be described later.

[0118] When a scheduled freight rate is specified in the automatic input request, the processor 110 calculates the freight rate using the price calculation information. For this purpose, the processor 110 estimates the travel distance and travel time from the loading destination to the unloading destination using the loading destination address and the unloading destination address. The processor 110 estimates the travel distance and travel time from the loading destination to the unloading destination using, for example, the loading destination address and the unloading destination address. The processor 110 estimates the travel distance and the travel time using, for example, map information including road information. The processor 110 calculates the freight rate based on, for example, at least one of the travel distance and the travel time and the fare calculation rule in the tariff master. When the fare calculation rule is a distance-based fare, the processor 110 calculates the fare by multiplying the distance unit price by the travel distance. When the fare calculation rule is an hourly fare, the processor 110 calculates the fare by multiplying the hourly unit price by the travel time. When the fare calculation rule is an individual fare, the processor 110 calculates the fare using the formula, for example, (either a distance-based fare according to the distance traveled by vehicle type or an hourly fare according to vehicle type, and any fees associated with these fares) ÷ {(maximum number of items or weight) × standard loading rate (○○%)}. When the fare calculation rule is another fare calculation method, the processor 110 calculates the fare using that method. It is preferable that the processor 110 calculates the fare using the distance rate and hourly rate for the vehicle type specified in the case information. The processor 110 also estimates the tolls for toll roads from the loading destination to the unloading destination. The processor 110 estimates the tolls using, for example, map information that includes road information.

[0119] When a scheduled fee other than the freight is specified in the automatic input request, the processor 110 calculates the scheduled amount of each fee using the fee calculation information. The processor 110 calculates the fee for waiting for cargo according to the fee calculation method defined in the fee table master, for example, using the scheduled length of time for cargo waiting. The processor 110 calculates the fee for loading according to the fee calculation method defined in the fee table master, for example, using the scheduled length of time for loading. The processor 110 calculates the fee for loading according to the fee calculation method defined in the fee table master, for example, using the scheduled length of time for unloading.

[0120] As described above, the processor 110 functions as an example of an acquisition unit that acquires a price list indicating the amount of the transportation fee by the transporter transporting the luggage from a storage device by acquiring the price list master in the processing of step ST25. Also, the processor 110 functions as an example of a calculation unit that calculates the amount of the fee for the case by using the price list, by calculating the amount of the fee in the processing of step ST25.

[0121] In step ST26, the processor 110 generates compensation information. The compensation information includes the compensation calculated in step ST25. After generating the compensation information, the processor 110 instructs the communication interface 150 to transmit the compensation information to the terminal device 200. In response to this transmission instruction, the communication interface 150 transmits the compensation information to the terminal device 200. The transmitted compensation information is received by the communication interface 250 of the terminal device 200.

[0122] 5, the processor 210 of the terminal device 200 waits for the consideration information to be received by the communication interface 250. If the consideration information is received, the processor 210 judges "Yes" in step ST75 and proceeds to step ST76.

[0123] In step ST76, the processor 210 inputs the price included in the price information into the order input screen displayed on the display device 270. After processing in step ST76, the processor 210 returns to step ST73.

[0124] If an operation to execute an order is performed while the processor 210 is in a standby state in which steps ST72 and ST73 are repeated, the processor 210 judges "Yes" in step ST73 and proceeds to step ST77. If the price is not entered in the transportation application form, the order is, for example, a request for a price estimate or an order for a spot job. The price in the transportation application form includes, for example, freight, tolls, incidental charges, loading and unloading fees, waiting fees, fuel surcharges, fees for the invoiced freight and the paid freight, fees for loading and unloading before the operation, and transportation fees.

[0125] In step ST77, the processor 210 generates order information. The order information includes, for example, a transportation application form, information other than the transportation application form input on the order input screen (hereinafter referred to as "input information"), a contract ID of the contract master designated to be used for ordering, and a login ID. The transportation application form is based on the contents input on the order input screen. The order information is information indicating that an order is to be placed from the orderer indicated by the login ID to the supplier indicated by the supplier information. After generating the order information, the processor 210 instructs the communication interface 250 to transmit the order information to the server device 100. Upon receiving this transmission instruction, the communication interface 250 transmits the order information to the server device 100. The transmitted order information is received by the communication interface 150 of the server device 100. After processing step ST77, the processor 210 returns to step ST61.

[0126] If processor 110 receives order information while in a standby state in which steps ST1 to ST19 in FIGS. 2 to 4 are repeated, it determines Yes in step ST8 in FIG. 3 and proceeds to step ST34.

[0127] In step ST34, the processor 110 registers the order indicated by the order information received in step ST8 as a case in the case DB 142. That is, the processor 110 stores the case information in association with the newly issued case ID. The orderer ID in the case information is the login ID included in the order information. The supplier ID in the case information is the user ID of the transportation user indicated by the supplier information included in the order information. The consignee ID in the case information is the user ID of the user indicated by the consignee information included in the order information. The loading destination ID in the case information is the user ID of the loading destination indicated by the order information. The unloading destination ID in the case information is the user ID of the unloading destination indicated by the order information. The dispatch vehicle ID and dispatch driver ID in the case information are initial values ​​indicating that a vehicle or driver is not registered. The initial value of the dispatch vehicle ID is a value other than the vehicle ID of a specific freight vehicle. The initial value of the dispatch driver ID is a value other than the driver ID of a specific driver. The initial value may be, for example, 0, Null, nothing, blank, a specific value determined in advance, or a dummy ID determined in advance. The subcontractor case ID in the case information is an initial value indicating that there is no subcontractor case based on this case. The initial value of the subcontractor case ID is a value other than the case ID indicating a specific case. The value of the hierarchical information in the case information is 1. The value of the real time information in the case information is an initial value indicating that the actual time taken is unknown or unconfirmed. The value of the order variable in the case information is a value indicating an unordered state. The value of the confirmation variable in the case information is a value indicating an unconfirmed state. The case change information in the case information indicates that the contents of the case have not been changed. The registered contract ID in the case information is the contract ID included in the order information. The case information also includes the contents of the transportation application and input information included in the order information. The case information also includes the transportation application included in the order information. After processing step ST34, the processor 110 returns to step ST1 in FIG. 2.

[0128] As described above, by processing steps ST23 and ST34, processor 110 functions as an example of a generation unit that generates data indicating a transportation application form for ordering a project using the contract master data, and stores the data indicating the transportation application form in a storage device.

[0129] The processor 210 of the terminal device 200 starts the process shown in FIG. 6 in response to, for example, an input instructing to display a menu for receiving an order.

[0130] When the transportation user wishes to change the price list master, the transportation user inputs an instruction to the terminal device 200 to display a screen for inputting information included in the price list master (hereinafter referred to as a "price list input screen").

[0131] 6, the processor 210 of the terminal device 200 judges whether or not an input instructing to display a fee table input screen has been received. If the processor 210 has not received an input instructing to display a fee table input screen, the processor 210 judges No in step ST91 and proceeds to step ST92.

[0132] Furthermore, when the transportation user wishes to display orders for which the transportation user is the order recipient, the transportation user operates the input device 260 to input an instruction to the terminal device 200 to display a list of such orders.

[0133] In step ST92, the processor 210 judges whether or not it has received an input instructing it to display a list of orders for which the processor 210 is the order recipient. If the processor 210 has not received an input instructing it to display a list of orders for which the processor 210 is the order recipient, it judges it as No in step ST92 and returns to step ST91. Thus, the processor 210 enters a standby state in which it repeats steps ST91 and ST92 until it receives an input instructing it to display a price list input screen or an input instructing it to display a list of orders for which the processor 210 is the order recipient.

[0134] If the processor 210 receives an input instructing to display the fee table input screen while in a standby state in which steps ST91 and ST92 are repeated, the processor 210 judges the result to be Yes in step ST91 and proceeds to step ST93.

[0135] In step ST93, the processor 210 generates a rate table request. The rate table request includes, for example, a login ID. The rate table request is information requesting transmission of a rate table master used by the transportation user identified by the login ID. After generating the rate table request, the processor 210 instructs the communication interface 250 to transmit the rate table request to the server device 100. Upon receiving this transmission instruction, the communication interface 250 transmits the rate table request to the server device 100. The transmitted rate table request is received by the communication interface 150 of the server device 100.

[0136] On the other hand, if the processor 110 of the server device 100 receives a fee table request while in a standby state in which steps ST1 to ST19 in FIGS. 2 to 4 are repeated, the processor 110 judges the result to be Yes in step ST5 in FIG. 2 and proceeds to step ST27.

[0137] In step ST27, the processor 110 refers to the user DB 141 to obtain the rate table master associated with the login ID included in the received rate table request.

[0138] In step ST28, the processor 110 instructs the communication interface 150 to transmit the fee table master acquired in step ST27 to the terminal device 200. Upon receiving this instruction to transmit, the communication interface 150 transmits the fee table master to the terminal device 200. The transmitted fee table master is received by the communication interface 250 of the terminal device 200. After processing step ST28, the processor 110 returns to step ST1.

[0139] In step ST94, the processor 210 waits for the fee table master to be received by the communication interface 250. If the fee table master is received, the processor 210 determines "Yes" in step ST94 and proceeds to step ST95.

[0140] In step ST95, the processor 210 generates an image corresponding to the fee table input screen. 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 fee table input screen.

[0141] The fee table input screen displays the contents of the fee master received in step ST94. The operator of the terminal device 200 can change the contents of the fee master displayed on the fee table input screen by inputting the changes to the fee master. The fee table input screen also includes a send button. The send button is a button that the operator operates when instructing the terminal device 200 to send the changes to the server device 100 and reflect the changes.

[0142] In step ST96, the processor 210 waits for the send button on the fee table input screen to be operated. If the send button is operated, the processor 210 determines Yes in step ST96 and proceeds to step ST97.

[0143] In step ST97, the processor 210 generates fee table information. The fee table information includes the login ID and the changes entered on the fee table input screen. The fee table information is information that instructs the fee table master associated with the login to reflect the changes. After generating the fee table information, the processor 210 instructs the communication interface 250 to transmit the fee table information to the server device 100. Upon receiving this transmission instruction, the communication interface 250 transmits the fee table information to the server device 100. The transmitted fee table information is received by the communication interface 150 of the server device 100. After processing step ST97, the processor 210 returns to step ST91.

[0144] On the other hand, if the processor 110 of the server device 100 receives tariff information while in a standby state in which steps ST1 to ST19 in FIGS. 2 to 4 are repeated, the processor 110 judges the result to be Yes in step ST6 in FIG. 2 and proceeds to step ST29.

[0145] In step ST29, the processor 110 updates the fee table master stored in the user DB 141. The fee table master is associated with the login ID included in the received fee table information. The update contents are indicated by the changes included in the fee table information. After processing step ST29, the processor 110 returns to step ST1.

[0146] On the other hand, if the processor 210 of the terminal device 200 receives an input instructing it to display a list of orders for which the processor 210 is the order recipient while in a standby state in which it repeats steps ST91 and ST92 in FIG. 6, it judges the answer to be Yes in step ST92 and proceeds to step ST98.

[0147] In step ST98, the processor 210 generates an order list request. The order list request includes, as an example, a login ID. The order list request is information requesting the transmission of a list of pending cases in which the transport user identified by the login ID is the order recipient, and information on each of the cases. After generating the order list request, the processor 210 instructs the communication interface 250 to transmit the order list request to the server device 100. Upon receiving this transmission instruction, the communication interface 250 transmits the order list request to the server device 100. The transmitted order list request is received by the communication interface 150 of the server device 100.

[0148] On the other hand, if the processor 110 of the server device 100 receives an order list request while in a standby state in which steps ST1 to ST19 in FIGS. 2 to 4 are repeated, the processor 110 judges the result to be Yes in step ST9 in FIG. 3 and proceeds to step ST35.

[0149] In step ST35, the processor 110 refers to the job DB 142 to identify jobs that are not yet received from among jobs whose supplier ID is the same as the login ID included in the order list request received in step ST9. Then, the processor 110 acquires the job ID and job information for each identified job.

[0150] In step ST36, the processor 110 generates order list information. The order list information includes a list of the cases identified in step ST35, and the case ID and case information acquired in step ST35. After generating the order list information, the processor 110 instructs the communication interface 150 to transmit the order list information to the terminal device 200 that is the sender of the order list request. In response to this transmission instruction, the communication interface 150 transmits the order list information to the terminal device 200. The transmitted order list information is received by the communication interface 250 of the terminal device 200. After processing step ST36, the processor 110 returns to step ST1 in FIG. 2.

[0151] 6, the processor 210 of the terminal device 200 waits for the order list information to be received by the communication interface 250. If the order list information is received, the processor 210 judges "Yes" in step ST99 and proceeds to step ST100.

[0152] In step ST100, the processor 210 generates an image corresponding to the order list 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 order list screen.

[0153] The order list screen is a screen that displays a list of pending orders for which the shipping user specified by the login ID is the order recipient. This list is a list included in the order list information received in step ST99. Each of the orders displayed as a list on the order list screen can be selected by operating the input device 260.

[0154] In step ST101, the processor 210 waits for an operation to select an item displayed as a list on the order list screen. If an operation to select an item displayed as a list on the order list screen is performed, the processor 210 determines Yes in step ST101 and proceeds to step ST102.

[0155] In step ST102, the processor 210 generates an acceptance note generation request. The acceptance note generation request includes, for example, a login ID and a case ID. The case ID is the case ID of the case selected on the order list screen. The acceptance note generation request is information requesting that a transportation acceptance note for the case be generated using the rate table master of the user identified by the login ID. After generating the acceptance note generation request, the processor 210 instructs the communication interface 250 to transmit the acceptance note generation request to the server device 100. Upon receiving this transmission instruction, the communication interface 250 transmits the acceptance note generation request to the server device 100. The transmitted acceptance note generation request is received by the communication interface 150 of the server device 100.

[0156] On the other hand, if the processor 110 of the server device 100 receives an acceptance letter generation request while in a standby state in which steps ST1 to ST19 in FIGS. 2 to 4 are repeated, the processor 110 judges the result to be Yes in step ST7 in FIG. 2 and proceeds to step ST30.

[0157] In step ST30, processor 110 refers to user DB 141 to obtain a tariff master associated with the login ID included in the received acceptance form generation request. Processor 110 also obtains case information for the case identified by the case ID included in the received acceptance form generation request. In other words, processor 110 refers to user DB 141 to obtain a transportation application form in the case information associated with the case ID. Processor 110 also refers to user DB 141 to obtain user information associated with the login ID.

[0158] In step ST31, if there is any fee not entered in the transportation application form for the case identified by the case ID, the processor 110 calculates the fee for the missing item. The processor calculates the fee in the same manner as in step ST25.

[0159] In step ST32, the processor 110 generates a transportation acceptance by using the price list master, the case information, and the user information acquired in step ST30, and the consideration calculated in step ST31.

[0160] The transportation acceptance includes, for example, underwriter information, distance and time information, waiting time information, ancillary business information, special provisions, transportation insurance premiums, and total billing amount.

[0161] Underwriter information is information about the underwriter. The underwriter is a person who undertakes transportation or a person who has been entrusted with transportation through forwarding. Thus, underwriter information includes information about the person who undertakes transportation or information about the person who has been entrusted with transportation through forwarding. The person who undertakes transportation indicates a shipper / user who uses his / her own vehicle for the received order. The person who has been entrusted with transportation through forwarding indicates a shipper / user who uses a chartered vehicle for the received order. Information about the underwriter includes, for example, the underwriter's company name, the name of the person in charge, address, contact information, the name of the underwriting office, the address of the underwriting office, contact information for the underwriting office, the date the business license was obtained, the business license number, and the vehicle number. The processor 110, for example, uses the acquired user information to enter the underwriter information into the transportation acceptance document.

[0162] The distance-time information includes, for example, a total travel distance from the loading destination to the unloading destination, an actual vehicle travel distance, a total travel time, and an actual vehicle travel time. The processor 110 inputs, for example, the travel distance and travel time estimated in step ST31 into the transportation acceptance document as the total travel distance and the total travel time.

[0163] The waiting time information includes an expected waiting time and a waiting fee. The processor 110 inputs the expected waiting time into the transportation acceptance slip using the acquired case information. The processor 110 inputs the waiting fee into the transportation acceptance slip using, for example, the acquired fee schedule master.

[0164] The ancillary work information includes the details of the loading operation at the loading destination, the scheduled time for loading operation at the loading destination, the scheduled fee for loading operation at the loading destination, the details of the loading operation at the unloading destination, the scheduled time for loading operation at the unloading destination, the scheduled fee for loading operation at the unloading destination, the details of other operations, the scheduled time for other operations, and the scheduled fee for other operations. The processor 110, for example, inputs the details of each operation and each scheduled time into the transportation acceptance slip using the acquired case information. The processor 110 also inputs each scheduled fee into the transportation acceptance slip using, for example, the loading operation fee in the acquired fee table master.

[0165] The processor 110 calculates the total billing amount by adding up the fares and tolls calculated in step ST31, the estimated charges included in the ancillary service information, the fuel surcharge, and other charges, and subtracting the transportation fee. The processor 110 then inputs the total billing amount into the transportation acceptance document.

[0166] In step ST33, the processor 110 instructs the communication interface 150 to transmit the transportation acceptance generated in step ST162 to the terminal device 200. Upon receiving this instruction to transmit, the communication interface 150 transmits the transportation acceptance to the terminal device 200. The transmitted transportation acceptance is received by the communication interface 250 of the terminal device 200. After processing step ST33, the processor 110 returns to step ST1.

[0167] 6, the processor 210 of the terminal device 200 waits for a transportation acceptance to be received by the communication interface 250. If the transportation acceptance is received, the processor 210 judges "Yes" in step ST103 and proceeds to step ST104.

[0168] In step ST104, the processor 210 generates an image corresponding to the order 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 order screen.

[0169] The order reception screen includes an area for displaying details of the case selected on the order list screen (hereinafter referred to as the "selected order case"), an order reception button, a reject button, and a change button. The details include the case information included in the order list information received in step ST99. The details include the transportation acceptance document received in step ST103.

[0170] The operator of the terminal device 200 can change the contents of the transportation acceptance slip displayed on the order receipt screen by inputting changes to the transportation acceptance slip.

[0171] The "Accept Order" button is a button that the operator operates when accepting (contracting) the selected order. If the contents of the transportation acceptance slip have been changed, the "Accept Order" button cannot be operated.

[0172] The reject button is a button that the operator operates when he or she wishes to reject the selected order and not accept the order.

[0173] The change button is a button that the operator operates when finalizing changes to the contents of the transportation acceptance document.

[0174] In step ST105, processor 210 determines whether or not an operation to change the selected order item has been performed. That is, processor 210 determines whether or not a predetermined operation, such as operating a change button after inputting the change contents, has been performed. If no operation to change the selected order item has been performed, processor 210 determines No in step ST105 and proceeds to step ST106.

[0175] In step ST106, processor 210 determines whether or not an operation to reject the acceptance of the selected order item has been performed. That is, processor 210 determines whether or not a predetermined operation, such as operating a reject button, has been performed. If an operation to reject the acceptance of the selected order item has not been performed, processor 210 determines No in step ST106 and proceeds to step ST107.

[0176] In step ST107, processor 210 determines whether or not an operation to accept the selected order case has been performed. That is, processor 210 determines whether or not a predetermined operation, such as operating an order button, has been performed. If an operation to accept the selected order case has not been performed, processor 210 determines No in step ST107 and returns to step ST105. Thus, processor 210 enters a standby state in which steps ST105 to ST107 are repeated until an operation to change the selected order case is performed, an operation to refuse to accept the selected order case is performed, or an operation to accept the selected order case is performed.

[0177] If an operation for accepting the selected order is performed while in a standby state in which steps ST105 to ST107 are repeated, processor 210 determines "Yes" in step ST107 and proceeds to step ST108.

[0178] In step ST108, the processor 210 generates approval information. The approval information includes, for example, a login ID, a case ID of the selected order case, and a transportation acceptance. The approval information is information indicating that the selected order case is accepted by the transportation user identified by the login ID. The transportation acceptance is the transportation acceptance received in step ST103. After generating the approval information, the processor 210 instructs the communication interface 250 to transmit the approval information to the server device 100. Upon receiving this transmission instruction, the communication interface 250 transmits the approval information to the server device 100. The transmitted approval information is received by the communication interface 150 of the server device 100.

[0179] On the other hand, if the processor 110 of the server device 100 receives approval information while in a standby state in which steps ST1 to ST19 in FIGS. 2 to 4 are repeated, the processor 110 judges the result to be Yes in step ST10 in FIG. 3 and proceeds to step ST37.

[0180] In step ST37, the processor 110 sets the case identified by the case ID included in the approval information received in step ST10 to an accepted state. That is, the processor 110 updates the case DB 142 to set the value of the order variable associated with the case ID to a value indicating the accepted state. The processor 110 also writes the transportation acceptance note included in the approval information into the case information associated with the case ID. After processing step ST37, the processor 110 returns to step ST1 in FIG. 2.

[0181] As described above, by processing steps ST32 and ST37, processor 110 functions as an example of a generation unit that generates data indicating a transportation acceptance indicating that the project has been accepted, and stores the data in association with the transportation application form in a storage device.

[0182] Furthermore, if an operation to change the selected order item is performed while in a standby state in which steps ST105 to ST107 in FIG. 7 are repeated, the processor 210 of the terminal device 200 judges the result to be Yes in step ST105 and proceeds to step ST109.

[0183] In step ST109, the processor 210 instructs the communication interface 250 to send change information to the server device 100. The change information includes the login ID, the case ID of the selected order case, and the change contents of the transportation acceptance. The change information is information indicating that the contents of the transportation acceptance for the selected order case will be changed by the transportation user identified by the login ID. Upon receiving this instruction to send, the communication interface 250 sends the change information to the server device 100. The sent change information is received by the communication interface 150 of the server device 100. After processing step ST109, the processor 210 returns to step ST91 in FIG. 6.

[0184] On the other hand, if the processor 110 of the server device 100 receives change information while in a standby state in which steps ST1 to ST19 in FIGS. 2 to 4 are repeated, the processor 110 judges the result to be Yes in step ST10 in FIG. 3 and proceeds to step ST38.

[0185] In step ST38, the processor 110 sets the case change information associated with the case ID in the received change information to a state indicating that the case has been changed. The processor 110 also writes the change contents in the change information to the case change information. After processing step ST38, the processor 110 returns to step ST1.

[0186] In addition, if an operation to reject acceptance of the selected order item is performed while in a standby state in which steps ST105 to ST107 in FIG. 7 are repeated, the processor 210 of the terminal device 200 judges the result to be Yes in step ST106 and proceeds to step ST110.

[0187] In step ST110, the processor 210 generates rejection information. The rejection information includes, for example, a login ID and a case ID of the selected order case. The rejection information is information indicating that the transportation user identified by the login ID rejects the order for the selected order case. After generating the rejection information, the processor 210 instructs the communication interface 250 to transmit the rejection information to the server device 100. Upon receiving this transmission instruction, the communication interface 250 transmits the rejection information to the server device 100. The transmitted rejection information is received by the communication interface 150 of the server device 100. After processing step ST110, the processor 210 returns to step ST91 in FIG. 6.

[0188] If rejection information is received while in a standby state in which steps ST1 to ST19 in FIGS. 2 to 4 are repeated, processor 110 determines Yes in step ST12 in FIG. 3 and proceeds to step ST39.

[0189] In step ST39, the processor 110 sets the case identified by the case ID included in the rejection information received in step ST39 to a rejected state. That is, the processor 110 updates the case DB 142 to set the value of the order variable associated with the case ID to a value indicating the rejected state. After processing in step ST39, the processor 110 returns to step ST1 in FIG. 2.

[0190] On the other hand, after the process of step ST108 in FIG. 7, the processor 210 of the terminal device 200 proceeds to step ST111.

[0191] In step ST111, the processor 210 generates an image corresponding to the vehicle dispatch 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 vehicle dispatch screen.

[0192] The vehicle dispatch screen includes, for example, a vehicle dispatch control and a confirmation button. The vehicle dispatch control is a control for inputting information related to vehicle dispatch for the selected order item (hereinafter referred to as "vehicle dispatch information"). The vehicle dispatch control is, for example, a check box, a list box, a combo box, a text box, and other controls.

[0193] The vehicle dispatch control includes, for example, selection control, vehicle control, driver control, vehicle chartering destination control, and vehicle chartering content control. Selection control is a control for inputting whether to use the own vehicle or a chartered vehicle for transporting cargo in the selected order item. The own vehicle is the company's own freight vehicle. The chartered vehicle is a freight vehicle of an outsourced party.

[0194] The vehicle control is a control for specifying a truck to be used for transporting cargo in the selected order. Note that the vehicle control can specify multiple trucks.

[0195] The driver control is a control for designating a driver of the company who will drive the freight vehicle for transporting luggage for the selected order item. The input for designating the driver is required when the company's own vehicle is selected in the selection control. Designation of the driver is optional. When a chartered vehicle is selected in the selection control and a driver is not designated in the selection control, it indicates that the driver of the chartered vehicle company will drive the freight vehicle for transporting luggage for the selected order item. The chartered vehicle company refers to the party to which the chartered vehicle is requested. The driver control can also designate multiple drivers.

[0196] The car hire destination control is a control for specifying a transportation user to hire the car to. The input for specifying the transportation user is required when a car hire is selected in the selection control. The car hire destination may be a user registered in the user DB141, or may be a company other than the user registered in the user DB141.

[0197] The vehicle chartering details control is a control for inputting order details to the vehicle chartering party. Contents that can be input using the vehicle chartering details control include, for example, freight information, contract details such as transportation conditions, etc.

[0198] The Confirm button is a button that the operator operates after inputting the necessary vehicle dispatch information using the vehicle dispatch control. The Confirm button is a button that the operator operates when instructing the terminal device 200 to transmit the information inputted using the vehicle dispatch control to the server device 100.

[0199] In step ST112, processor 210 determines whether or not an operation has been performed to confirm that the vehicle will be used for the selected order item. That is, processor 210 determines whether or not a predetermined operation has been performed, such as operating a confirmation button with the vehicle selected in the selection control. If no operation has been performed to confirm that the vehicle will be used for the selected order item, processor 210 determines No in step ST112 and proceeds to step ST113.

[0200] In step ST113, the processor 210 determines whether or not an operation has been performed to confirm the use of a chartered vehicle for the selected order case. That is, the processor 210 determines whether or not a predetermined operation has been performed, such as operating the Confirm button with a chartered vehicle selected in the selection control. If an operation to confirm the use of a chartered vehicle for the selected order case has not been performed, the processor 210 determines No in step ST113 and returns to step ST112. Thus, the processor 210 enters a standby state in which steps ST112 and ST113 are repeated until an operation to confirm the use of the own vehicle for the selected order case is performed or an operation to confirm the use of a chartered vehicle for the selected order case is performed.

[0201] If an operation is performed to confirm the use of the vehicle for the selected order item while in a standby state in which steps ST112 and ST113 are repeated, the processor 210 judges "Yes" in step ST112 and proceeds to step ST114.

[0202] In step ST114, the processor 210 generates the vehicle information. The vehicle information is information indicating that the vehicle is used for the selected order item. The vehicle information is information instructing to register the information input using the vehicle dispatch control. The vehicle information includes, for example, a login ID, a case ID of the selected order item, vehicle information, and dispatch driver information. The vehicle information is information indicating a freight vehicle specified in the vehicle control. The vehicle information indicates the freight vehicle by, for example, the vehicle ID of the freight vehicle. Note that, when a freight vehicle is not specified on the dispatch screen, the vehicle information indicates an unspecified vehicle ID. The unspecified vehicle ID is a vehicle ID indicating that a freight vehicle is not specified, and is information indicating that a freight vehicle is not specified. The dispatch driver information includes information indicating a specified driver. The dispatch driver information indicates the driver by, for example, the driver ID of the driver. Note that, when a driver is not specified in the driver control, the dispatch driver information indicates an unspecified driver ID. The unspecified driver ID is a driver ID indicating that a driver is not specified, and is information indicating that a driver is not specified.

[0203] After generating the own vehicle information, the processor 210 instructs the communication interface 250 to transmit the own vehicle information to the server device 100. Upon receiving this transmission instruction, the communication interface 250 transmits the own vehicle information to the server device 100. The transmitted own vehicle information is received by the communication interface 150 of the server device 100. After processing step ST114, the processor 210 returns to step ST100.

[0204] On the other hand, if the processor 110 of the server device 100 receives vehicle information while in a standby state in which steps ST1 to ST19 in FIGS. 2 to 4 are repeated, the processor 110 determines Yes in step ST13 in FIG. 3 and proceeds to step ST40.

[0205] In step ST40, the processor 110 updates the case DB 142 based on the vehicle information received in step ST8 to register the truck and the driver in the case. That is, the processor 110 sets the value of the dispatched vehicle ID for the case information associated with the case ID included in the vehicle information to the vehicle ID included in the vehicle information. Then, the processor 110 sets the value of the dispatched driver ID for the case information to the driver ID included in the vehicle information. In addition, when the vehicle information included in the vehicle information is not an unspecified vehicle ID and the dispatched driver information included in the vehicle information is not an unspecified driver ID, the processor 110 sets the value of the confirmed variable in the case information to a value indicating a confirmed state. Furthermore, the processor 110 sets the value of the confirmed variable in the case information for each of the upper cases of the case identified by the case ID to a value indicating a confirmed state. Here, the upper case of the case is each case that can be reached when going along the original case of the original case of the case. In addition, processor 110 converts the information about the underwriter contained in the transportation acceptance in the case information into information about the person undertaking the transportation.

[0206] In step ST41, the processor 110 notifies a user, such as an orderer of the case, that the case has been accepted, the transportation acceptance for the case, that the case has been confirmed, and information on the truck and driver who will operate the case. For this purpose, the processor 110 instructs the communication interface 150 to send confirmation notification information to the terminal device 200 used by the user. The confirmation notification information includes the transportation acceptance for the case, and information on the truck and driver who will operate the case. The confirmation notification information also indicates that the case has been accepted and that the case has been confirmed. In response to this transmission instruction, the communication interface 150 transmits the confirmation notification information to the terminal device 200. The transmitted confirmation notification information is received by the communication interface 250 of the terminal device 200. The processor 210 of the terminal device 200 notifies the user by displaying the contents of the confirmation notification information on the display device 270, for example. This notification is deemed to be a written delivery of the transportation acceptance. The notification destination users may include the user who placed the order for the original job. After the process of step ST41, the processor 110 returns to step ST1 in FIG.

[0207] As described above, the processor 110 functions as an example of a contract transmission unit that transmits data indicating a transportation acceptance to the client of the project by performing the process of step ST41 in cooperation with the communication interface 150. The processor 110 also functions as an example of a contract transmission unit that transmits information indicating that the truck and driver performing the transportation in the project have been determined to the client of the project by performing the process of step ST41 in cooperation with the communication interface 150.

[0208] In addition, if an operation is performed to confirm the use of a chartered vehicle for the selected order item while the processor 210 of the terminal device 200 is in a standby state in which steps ST112 and ST113 in Figure 7 are repeated, the processor 210 judges Yes in step ST113 and proceeds to step ST115.

[0209] In step ST115, the processor 210 generates chartering order information. The chartering order information includes, for example, a login ID, a case ID of the selected order case, chartering destination information, and chartering content information. If a driver is specified in the driver control, the chartering order information further includes dispatch driver information. The chartering destination information is, for example, information indicating the chartering destination specified using the chartering destination control. If the chartering destination is a user registered in the user DB141, the chartering destination information includes the user ID of the chartering destination user. If the chartering destination is not a user registered in the user DB141, the chartering destination information includes non-registration information. The non-registration information is information indicating that the chartering destination is not a user registered in the user DB141. The chartering content information includes content input using the chartering content control. The chartering order information is information indicating that a chartering order is to be placed from the ordering source indicated by the login ID to the ordering destination indicated by the chartering destination information. After generating the chartering order information, the processor 210 instructs the communication interface 250 to transmit the chartering order information to the server device 100. Upon receiving this instruction to transmit, the communication interface 250 transmits the vehicle chartering order information to the server device 100. The transmitted vehicle chartering order information is received by the communication interface 150 of the server device 100. After processing step ST115, the processor 210 returns to step ST100.

[0210] On the other hand, if the processor 110 of the server device 100 receives vehicle charter order information while in a standby state in which steps ST1 to ST19 in Figures 2 to 4 are repeated, the processor 110 judges the answer to be Yes in step ST14 in Figure 4 and proceeds to step ST42.

[0211] In step ST42, if the vehicle chartering order information received in step ST14 includes the assigned driver information, the processor 110 updates the job DB 142 to register the driver in the job. That is, the processor 110 sets the value of the assigned vehicle ID for the job information associated with the job ID included in the vehicle chartering order information to the vehicle ID included in the vehicle chartering order information.

[0212] In step ST43, the processor 110 registers the order for the chartered vehicle indicated by the chartered vehicle ordering information received in step ST14 as a case in the case DB 142. The processor 110 stores the case information in association with the newly issued case ID. The case ID issued here is hereinafter referred to as a "new ID." The ordering source ID in the case information is the login ID included in the chartered vehicle ordering information. The contractor ID in the case information is the user ID of the transportation user indicated by the chartered vehicle information included in the chartered vehicle ordering information. The dispatched vehicle ID in the case information is an initial value. The dispatched driver ID is, for example, an initial value. The original case ID in the case information is the case ID included in the chartered vehicle ordering information. The subcontractor case ID in the case information is an initial value. The value of the hierarchical information in the case information is a value obtained by adding 1 to the value of the hierarchical information of the case identified by the original case ID. The value of the real time information in the case information is an initial value. The value of the order variable in the case information is a value indicating an unreceived order state. The processor 110 copies the case information of the case specified by the original case ID, for example, for information in the case information other than the orderer ID, the supplier ID, the dispatched vehicle ID, the dispatched driver ID, the original case ID, and the order variable. However, the processor 110 overwrites the contents of the copied case information with the contents indicated by the vehicle chartering content information included in the vehicle chartering order information. The processor 110 also sets the value of the subcontract case ID for the case information of the case specified by the original case ID to the new ID issued in step ST43. The processor 110 also sets the information about the underwriter included in the transportation acceptance in the case information to information about the person who has accepted the transportation by using the transportation service. After processing step ST43, the processor 110 returns to step ST1 in FIG. 2.

[0213] An order for an n-th subcontractor case is received by the process shown in FIG. 6 and FIG. 7 in the same manner as for a normal case (a first-tier subcontractor case). A chartered vehicle may be ordered for an n-th subcontractor case. That is, a chartered vehicle may be ordered for an n-th subcontractor case as a selective order case. This order becomes a (n+1)th subcontractor case. When the processor 110 of the server device 100 registers a freight vehicle and a driver for an n-th subcontractor case in the process of step ST40 in FIG. 3, the processor 110 also registers the same freight vehicle and driver for the original case of the case. At this time, the processor 110 identifies the original case by the original case ID. When the original case is not a prime contractor case, the processor 110 identifies a further original case by the original case ID of the original case, and by repeating this process, identifies the original case, i.e., the prime contractor case. The processor 110 then registers the same freight vehicle and driver for all identified cases. Through the above process, trucks and drivers are registered for all jobs from the nth subcontractor to the first subcontractor. Also, in the process of step ST42 in Fig. 4, when the processor 110 registers a driver for a job of the nth subcontractor, the processor 110 registers the driver for each of the original jobs. In other words, the processor 110 registers the same driver for jobs from the nth subcontractor to the first subcontractor.

[0214] On the other hand, when the processor 210 of the terminal device 200 is in a standby state in which steps ST61 to ST63 of FIG. 5 are repeated, if the processor 210 receives an input instructing it to display a list of orders whose contents have been changed, the processor 210 judges the answer to be Yes in step ST63 and proceeds to step ST78.

[0215] In step ST78, the processor 210 generates a change list request. The change list request includes, as an example, a login ID. The change list request is information requesting the transmission of a list of cases whose contents have been changed among cases ordered by the transportation user identified by the login ID, and information about each of the cases. After generating the change list request, the processor 210 instructs the communication interface 250 to transmit the change list request to the server device 100. Upon receiving this transmission instruction, the communication interface 250 transmits the change list request to the server device 100. The transmitted change list request is received by the communication interface 150 of the server device 100.

[0216] On the other hand, if the processor 110 of the server device 100 receives a change list request while in a standby state in which steps ST1 to ST19 in FIGS. 2 to 4 are repeated, the processor 110 judges the result to be Yes in step ST15 in FIG. 4 and proceeds to step ST44.

[0217] In step ST44, the processor 110 identifies cases whose change information indicates that the contents of the case have been changed among cases whose orderer ID is the same as the login ID included in the received change list request. Then, the processor 110 acquires the case ID and case information for each identified case.

[0218] In step ST45, the processor 110 generates change list information. The change list information includes a list of the cases identified in step ST44, and the case ID and case information acquired in step ST44. After generating the change list information, the processor 110 instructs the communication interface 150 to transmit the change list information to the terminal device 200. Upon receiving this transmission instruction, the communication interface 150 transmits the change list information to the terminal device 200. The transmitted change list information is received by the communication interface 250 of the terminal device 200. After processing of step ST45, the processor 110 returns to step ST1 in FIG. 2.

[0219] 6, the processor 210 of the terminal device 200 waits for the change list information to be received by the communication interface 250. If the change list information is received, the processor 210 judges "Yes" in step ST79 and proceeds to step ST80.

[0220] In step ST80, the processor 210 generates an image corresponding to the change list screen. 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 change list screen.

[0221] The change list screen is a screen that displays a list of cases whose contents have been changed. This list is a list included in the received order list information. In addition, each case displayed as a list on the change list screen can be selected by operating the input device 260.

[0222] The operator selects from the list the job for which he or she wishes to reorder with the changed contents.

[0223] In step ST81, the processor 210 waits for an operation to select a case displayed as a list on the change list screen. If an operation to select a case displayed as a list on the change list screen is performed, the processor 210 determines Yes in step ST81 and proceeds to step ST82.

[0224] In step ST82, the processor 210 generates an application form generation request. The application form generation request includes the case ID of the selected case and the change contents. The change contents are contents indicated by the case change information of the selected case. The application form generation request in step ST82 is information requesting the generation of a transportation application form that reflects the change contents. After generating the application form generation request, the processor 210 instructs the communication interface 250 to send the application form generation request to the server device 100. Upon receiving this instruction to send, the communication interface 250 sends the application form generation request to the server device 100. The sent application form generation request is received by the communication interface 150 of the server device 100. After processing step ST82, the processor 210 returns to step ST70.

[0225] In step ST23, if the application form creation request includes changes, the processor 110 refers to the case DB 142 to identify a transportation application form associated with the case ID included in the application form creation request. The processor 110 then rewrites the transportation application form to reflect the changes.

[0226] When the transportation user wishes to request payment such as freight for the received job, when he / she wishes to output various forms, when he / she wishes to confirm the contents of the job, etc., he / she operates the input device 260 to input an instruction to the terminal device 200 to display a list of the jobs. In response to the input, the processor 210 of the terminal device 200 starts the process shown in FIG. 8, for example.

[0227] In step ST121 of FIG. 8, the processor 210 of the terminal device 200 generates a case list request. The case list request includes, as an example, a login ID. The case list request is information requesting the transmission of a list of cases ordered by the transport user identified by the login ID and information on each case. After generating the case list request, the processor 210 instructs the communication interface 250 to transmit the case list request to the server device 100. Upon receiving this transmission instruction, the communication interface 250 transmits the case list request to the server device 100. The transmitted case list request is received by the communication interface 150 of the server device 100.

[0228] On the other hand, if the processor 110 of the server device 100 receives a request for a list of cases while in a standby state in which steps ST1 to ST19 in FIGS. 2 to 4 are repeated, the processor 110 judges the result to be Yes in step ST16 in FIG. 4 and proceeds to step ST46.

[0229] In step ST46, processor 110 refers to case DB 142 to identify cases in an accepted state among cases whose supplier ID is the same as the login ID included in the order list request received in step ST9. Processor 110 then acquires the case ID and case information for each identified case. Processor 110 also refers to billing DB 145 to identify bills associated with the case ID of each identified case. Processor 110 then acquires the billing ID and billing information for each identified bill. Processor 110 may also acquire case IDs and case information for cases other than those in an accepted state.

[0230] In step ST47, the processor 110 generates case list information. The case list information includes, for example, a list of cases identified in step ST46, the case ID and case information acquired in step ST46, and the billing ID and billing information acquired in step ST46. After generating the case list information, the processor 110 instructs the communication interface 150 to transmit the case list information to the terminal device 200 that is the sender of the case list request. In response to this transmission instruction, the communication interface 150 transmits the case list information to the terminal device 200. The transmitted case list information is received by the communication interface 250 of the terminal device 200. After processing step ST47, the processor 110 returns to step ST1 in FIG. 2.

[0231] 8, the processor 210 of the terminal device 200 waits for the case list information to be received by the communication interface 250. If the case list information is received, the processor 210 judges "Yes" in step ST122 and proceeds to step ST123.

[0232] In step ST123, the processor 210 generates an image corresponding to the received order list 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 received order list screen.

[0233] The order list screen is a screen that displays a list of cases in which an order has been placed and the shipping user identified by the login ID is the order recipient. This list is a list included in the case list information received in step ST122. Each case displayed as a list on the order list screen can be selected by operating the input device 260. Multiple cases may be selectable. The order list screen also displays case information for each case.

[0234] In step ST124, the processor 210 waits for an operation to select an item displayed as a list on the received order list screen. If an operation to select an item displayed as a list on the received order list screen is performed, the processor 210 determines Yes in step ST124 and proceeds to step ST125.

[0235] In step ST125, the processor 210 generates an automatic input request. The automatic input request here includes, for example, a login ID, a case ID of the selected case, and payment specification information. The payment specification information specifies the actual payment. After generating the automatic input request, the processor 210 instructs the communication interface 250 to transmit the automatic input request to the server device 100. Upon receiving this transmission instruction, the communication interface 250 transmits the automatic input request to the server device 100. The transmitted automatic input request is received by the communication interface 150 of the server device 100.

[0236] On the other hand, when an actual price is specified in the price specification information in step ST25 of Fig. 2, the processor 110 of the server device 100 refers to the user DB 141 and acquires the fee table master associated with the user ID of the user identified by the supplier information included in the received automatic input request. Then, the processor 110 refers to the case DB 142 and acquires real time information in the case information associated with the case ID included in the received automatic input request. Furthermore, the processor 110 uses the length of time indicated by the acquired real time information to calculate the actual amount of each fee according to the fee calculation method defined in the fee table master.

[0237] However, if the actual price has already been entered into the invoice, processor 110 retrieves that amount instead of calculating it. Processor 110 refers to invoice DB 146 to check whether a billing case ID is registered whose case ID is the same as the case ID included in the automatic input request. If such a billing case is registered, processor 110 retrieves amount information for that billing case. Processor 110 then retrieves the actual price amount from the amount information. As a result, the amount revised by the client is sent to the supplier.

[0238] As described above, in the processing of step ST25, processor 110 functions as an example of a calculation unit that calculates the actual waiting fee and handling fee by using the time spent waiting and the time spent handling the cargo in transporting the cargo, and a tariff that indicates the amount of transportation fee paid by the transporter transporting the cargo.

[0239] 8, the processor 210 of the terminal device 200 waits for the consideration information to be received by the communication interface 250. If the consideration information is received, the processor 210 judges "Yes" in step ST126 and proceeds to step ST127.

[0240] In step ST127, the processor 210 generates an image corresponding to the case 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 case screen.

[0241] The case screen is a screen that displays information about the case selected on the case list screen (hereinafter referred to as the "selected case"). The case screen includes a details area, an amount area, an approval area, a billing button, an output button, a billing control, and an output control. The details area is an area that displays the details of the selected case. The details include the case information included in the order list information received in step ST122. The case screen may be divided into multiple screens. For example, the details area and approval area may be different screens from the amount area. The details area in the case screen is, as an example, a details area AR110 as shown in FIG. 15.

[0242] FIG. 15 is a diagram showing an example of the details area AR110 displayed on the display device 270. The details area AR110 is an area that displays some of the details of the case. The details area AR110 includes areas AR111 to AR116, as an example. The details area AR110 also includes the scheduled date and time when loading of the luggage will start and end 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 details area AR110 also includes the scheduled date and time when unloading of the luggage will start and end 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.

[0243] Areas AR111 to AR116 are areas that display real-time information, so the times displayed in areas AR111 to AR116 are not scheduled times but actual times taken.

[0244] An area AR111 displays the waiting time at the loading destination of the cargo. An area AR112 displays the loading operation time at the loading destination. An area AR113 displays the total waiting loading operation time at the loading destination.

[0245] Area AR114 is an area for displaying the waiting time at the unloading destination of the cargo. Area AR115 is an area for displaying the loading and unloading work time at the unloading destination. Area AR116 is an area for displaying the total loading and unloading time at the unloading destination.

[0246] The processor 210 changes the display manner for the area AR113, 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 AR116, 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 billing 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.

[0247] The processor 210 may change the manner of displaying the areas AR113 and AR116 when the total time of waiting for loading at the loading destination and the total time of waiting for loading 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 AR111, AR112, AR114, and AR115 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.

[0248] Moreover, the amount area in the case screen is, for example, the amount area AR120 as shown in FIG. 16. The amount area AR120 is an area that displays the billing amount, etc. The amount area AR120 also includes an input field where the billing amount can be input and changed. The shipper user can determine the billing amount while looking at each time displayed in the details area AR110. The billing amount may vary depending on each time. The amount area AR120 shown in FIG. 16 is the amount area AR120 when multiple cases are selected. The amount area AR120 includes, for example, areas AR121 to AR126.

[0249] Area AR121 is an area that displays information about the item. Area AR122 is an area that displays the charge at the loading destination, out of the planned price. Area AR123 is an area that displays the charge at the unloading destination, out of the planned price. Processor 210 changes the way each time period in areas AR122 and AR123 is displayed if it exceeds a predetermined time period, similar to areas AR111 to AR116 in FIG. 15.

[0250] Area AR124 is an area that displays the fare, which is part of the planned price. The fare is usually unchanged from the planned amount. Therefore, the planned amount and the actual amount are equal. However, the amount displayed in area AR124 may be changeable by operating input using input device 260. The amount after the change is the actual fare amount.

[0251] Area AR125 is an area for displaying the actual fee. The amount displayed here is included in the consideration information received in step ST126. Therefore, the automatically calculated amount is displayed in fee AR125. The amount displayed in area AR125 can be changed by operating input using input device 260.

[0252] Area AR126 is an area that displays the total amount of the actual consideration.

[0253] The approval area displays whether the claim for the selected case is in an unapproved state, an approved state, or an approval denied state, if there is a claim for the selected case. Note that a claim for a case is a claim whose claim case ID is the case ID of the case.

[0254] The billing button is a button for registering a new bill for the selected item and for requesting approval of the bill from the purchaser. The billing button is also a button for finalizing the billing amount for the bill.

[0255] The output button is a button that is operated when outputting various forms regarding the selected case.

[0256] The billing control is a control for inputting information related to the billing amount for the selected case, such as the billing amount and its breakdown. If a bill exists for the selected case, the billing control displays the amount indicated by the amount information of the billing.

[0257] The output control is a control for specifying the type of document to be output. Examples of documents that can be output include transportation instructions, purchase orders, invoices, payment statements, offset notices, waybills, guidance instructions, vehicle number contact slips, operation instructions, transportation applications, transportation acceptances, actual transportation system management books, and various slips.

[0258] A transportation instruction is also called a dispatch instruction. A transportation instruction is a document in which an orderer provides a customer with details of the operation conditions, mainly the work content, with the aim of having the customer fulfill the operation conditions. The operation conditions include, for example, the loading date, unloading date, and loading place.

[0259] A purchase order is a document that an ordering party sends to a customer. A purchase order is a document that describes the details of a transaction, including payment terms, in order to comply with the Subcontract Act.

[0260] An invoice is a document sent by the receiving party (customer) to the ordering party. An invoice is a document that lists the amount to be charged for operations etc.

[0261] A payment statement is a document sent by an ordering party to a customer. The payment statement is a document that lists the payment amount for operations, etc. for which payment was incurred, for the purpose of confirming the payment amount.

[0262] An offset notice is a document sent to a business partner with which accounts receivable and payable occur simultaneously, for the purpose of streamlining transfers and payments for freight, etc. An offset notice is a document that clearly states the amount that has been offset.

[0263] The processor 210 may be able to update the case screen by reacquiring, from the server device 100, information required for displaying the case screen.

[0264] In step ST128, processor 210 determines whether an operation has been performed to confirm the billing amount for the selected job and to request the client to approve the billing amount. That is, processor 210 determines whether a predetermined operation, such as operating the billing button, has been performed. Processor 210 determines No in step ST128 and proceeds to step ST129 if an operation has not been performed to confirm the billing amount for the selected job and to request the client to approve the billing amount.

[0265] In step ST129, the processor 210 determines whether or not an operation to output a form has been performed. That is, the processor 210 determines whether or not a predetermined operation has been performed, such as operating an output button after specifying the type of form using the output control. If an operation to output a form has not been performed, the processor 210 determines No in step ST129 and returns to step ST128. Thus, the processor 210 enters a standby state in which it repeats steps ST128 and ST129 until an operation to confirm the billing amount for the selected job and request the orderer to approve the billing amount is performed or an operation to output a form is performed.

[0266] When processor 210 is in a standby state in which it repeats steps ST128 and ST129, it determines the billing amount for the selected case, and if an operation is performed to request approval of the billing amount from the client, it judges the result to be Yes in step ST128 and proceeds to step ST130.

[0267] In step ST130, the processor 210 generates request information. The request information is information instructing to newly register a bill for the selected case and to request the orderer for approval of the bill. The request information also indicates that an operation has been performed indicating that the orderer of the case has confirmed the billing amount. The request information includes, for example, a login ID, a case ID of the selected case, an orderer ID of the selected case, and amount input information. The amount input information includes information input in the billing control. After generating the request information, the processor 210 instructs the communication interface 250 to transmit the request information to the server device 100. Upon receiving this transmission instruction, the communication interface 250 transmits the request information to the server device 100. The transmitted request information is received by the communication interface 150 of the server device 100. After processing step ST130, the processor 210 returns to step ST127.

[0268] On the other hand, if the processor 110 of the server device 100 receives request information while in a standby state in which steps ST1 to ST19 in FIGS. 2 to 4 are repeated, the processor 110 judges "Yes" in step ST17 in FIG. 4 and proceeds to step ST48.

[0269] In step ST48, the processor 110 registers the billing indicated by the request information received in step ST17 in the billing DB 145. That is, the processor 110 associates the billing information with a newly issued billing ID and stores it. The billing matter ID in the billing information is the matter ID included in the request information. The billing source ID in the billing information is the login ID included in the request information. The billing destination ID in the billing information is the orderer ID included in the request information. The amount information in the billing information includes the amount input information included in the request information. The value of the approval variable in the billing information is a value indicating an unapproved state. After processing step ST48, the processor 110 returns to step ST1 in FIG. 2.

[0270] From the above, when the amount displayed on the case screen has been changed, processor 110 works in cooperation with communication interface 150 to process steps ST17 and ST48, thereby functioning as an example of a change unit that receives input from the case contractor instructing a change to the amount of the consideration, and changes the amount of the consideration based on the instruction.

[0271] When a shipper user wishes to display an order that he / she has placed and a list of invoices for the order, the shipper user operates the input device 260 to input an instruction to the terminal device 200 to display the list of invoices. In response to the input, the processor 210 of the terminal device 200 starts the process shown in FIG. 9, for example.

[0272] In step ST141 of FIG. 9, the processor 210 of the terminal device 200 generates a billing list request. The billing list request includes, as an example, a login ID. The billing list request is information requesting transmission of a list of cases in which the shipper user identified by the login ID is the orderer and information on each case. The billing list request is also information requesting transmission of a list of bills for each case in which the shipper user identified by the login ID is the orderer and information on each bill. After generating the billing list request, the processor 210 instructs the communication interface 250 to transmit the billing list request to the server device 100. Upon receiving this transmission instruction, the communication interface 250 transmits the billing list request to the server device 100. The transmitted billing list request is received by the communication interface 150 of the server device 100.

[0273] On the other hand, if the processor 110 of the server device 100 receives a billing list request while in a standby state in which steps ST1 to ST19 in FIGS. 2 to 4 are repeated, the processor 110 judges the result to be Yes in step ST18 in FIG. 4 and proceeds to step ST49.

[0274] In step ST49, the processor 110 refers to the case DB 142 and identifies cases in an order-received state among cases whose orderer ID is the same as the login ID included in the invoice list request. The processor 110 then acquires a case ID and case information for each identified case. The processor 110 may also acquire case IDs and case information for cases other than those in an order-received state. The processor 110 also refers to the invoice DB 145 and identifies invoices whose invoice destination ID is the login ID included in the invoice list request received in step ST18. The processor 110 then acquires a invoice ID and invoice information for each identified invoice. Alternatively, the processor 110 may refer to the invoice DB 145 and identify invoices associated with the case ID of each identified case. The processor 110 may then acquire a invoice ID and invoice information for each identified invoice.

[0275] In step ST50, the processor 110 generates billing list information. The billing list information includes, for example, a list of cases identified in step ST49, case IDs and case information acquired in step ST49, a list of cases identified in step ST49, and billing IDs and billing information acquired in step ST49. After generating the billing list information, the processor 110 instructs the communication interface 150 to transmit the billing list information to the terminal device 200 that is the sender of the billing list request. In response to this transmission instruction, the communication interface 150 transmits the billing list information to the terminal device 200. The transmitted billing list information is received by the communication interface 250 of the terminal device 200. After processing step ST50, the processor 110 returns to step ST1 in FIG. 2.

[0276] As described above, the processor 110 functions as an example of a billing transmission unit that cooperates with the communication interface 150 to transmit an invoice indicating the cost of transportation, including the loading and unloading fee, to the client of the project. The processor 110 also cooperates with the communication interface 150 to perform the process of step ST50 for the invoice whose amount has been changed by the change unit, thereby functioning as an example of a billing transmission unit that transmits an invoice reflecting the change.

[0277] 9, the processor 210 of the terminal device 200 waits for the bill list information to be received by the communication interface 250. If the bill list information is received, the processor 210 judges "Yes" in step ST142 and proceeds to step ST143.

[0278] In step ST143, the processor 210 generates an image corresponding to the bill list 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 bill list screen.

[0279] The billing list screen is a screen that displays a list of cases ordered by a user identified by a login ID, and a list of bills to which the user is the billing recipient. This list is a list included in the billing list information received in step ST142. Each case and bill displayed as a list on the billing list screen can be selected by operating the input device 260.

[0280] In step ST144, the processor 210 determines whether or not an operation to select a bill displayed as a list on the bill list screen has been performed. If an operation to select a bill displayed as a list on the bill list screen has not been performed, the processor 210 determines No in step ST144 and proceeds to step ST145.

[0281] In step ST145, the processor 210 determines whether or not an operation has been performed to select an item displayed as a list on the billing list screen. If an operation has not been performed to select an item displayed as a list on the billing list screen, the processor 210 determines No in step ST145 and returns to step ST144. Thus, the processor 210 enters a standby state in which steps ST144 and ST145 are repeated until an operation is performed to select an item displayed as a list on the billing list screen or an operation is performed to select an item displayed as a list on the billing list screen.

[0282] If an operation is performed to select a bill displayed as a list on the bill list screen while in a standby state in which steps ST144 and ST145 are repeated, processor 210 judges the result to be Yes in step ST144 and proceeds to step ST146.

[0283] In step ST146, the processor 210 generates an image corresponding to the billing 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 billing screen.

[0284] The billing screen includes a billing details area that displays details of the bill selected on the billing list screen (hereinafter referred to as the "selected billing"), an approve billing button, and a reject billing button. The details include the billing information included in the billing list information received in step ST142.

[0285] The billing details area includes, as an example, a details area AR110 as shown in FIG. 15. The details area AR110 in the billing screen is similar to the details area AR110 in the case screen. The billing details area also includes the billing amount. The billing amount is the same as that displayed in the amount area in the case screen for the same case. Each amount in the billing details area may be changeable by operational input using the input device 260.

[0286] The "Approve Bill" button is a button for approving the selected bill. If the amount in the billing details area has been changed, the "Approve Bill" button cannot be operated.

[0287] The request rejection button is a button that is operated when approval of the selected request is rejected.

[0288] In step ST147, the processor 210 waits for an operation to approve or reject the selected claim. That is, the processor 210 waits for a predetermined operation, such as pressing a claim approval button or a claim rejection button. If an operation to approve or reject the selected claim is performed, the processor 210 determines "Yes" in step ST147 and proceeds to step ST148.

[0289] In step ST148, the processor 210 generates billing approval information. The billing approval information includes the login ID, the billing ID of the selected billing, and approval / rejection information. If the amount in the billing details area has been changed, the billing approval information also includes billing change information. The approval / rejection information indicates whether the selected billing is approved or rejected. If the billing approval button is operated, the approval / rejection information indicates that the billing is approved. Furthermore, the approval / rejection information indicating that the billing is approved indicates that an operation has been performed indicating that the billing amount has been confirmed by the orderer of the project. If the billing rejection button is operated, it indicates that approval of the billing is rejected. The billing change information indicates the changes made to the amounts in the billing details area. After generating the billing approval information, the processor 210 instructs the communication interface 250 to transmit the billing approval information to the server device 100. Upon receiving this transmission instruction, the communication interface 250 transmits the billing approval information to the server device 100. The transmitted billing approval information is received by the communication interface 150 of the server device 100. After the process of step ST148, the processor 210 returns to step ST143.

[0290] On the other hand, if the processor 110 of the server device 100 receives billing approval information while in a standby state in which steps ST1 to ST19 in FIGS. 2 to 4 are repeated, the processor 110 judges the result to be Yes in step ST19 in FIG. 4 and proceeds to step ST51.

[0291] In step ST51, the processor 110 sets the case identified by the billing ID included in the billing approval information received in step ST19 to an approved state or an approval denial state. That is, the processor 110 updates the billing DB 145 to set the value of the approval variable associated with the billing ID to a value indicating an approved state or an approval denial state. If the approval propriety information included in the billing approval information indicates approval, the processor 110 sets the value of the approval variable to a value indicating an approval state. If the approval propriety information indicates denial of approval, the processor 110 sets the value of the approval variable to a value indicating an approval denial state. In addition, if the billing approval information includes billing change information, the processor 110 updates the billing DB 145 to change each amount in the amount information associated with the billing ID according to the billing change information. After processing step ST51, the processor 110 returns to step ST1 in FIG. 2.

[0292] From the above, when the billing approval information includes billing change information, the processor 110 works in cooperation with the communication interface 150 to process steps ST19 and ST51, thereby functioning as an example of a change section that receives an input from the client of the project instructing a change to the amount of the fee, and changes the amount of the fee based on the instruction.

[0293] In addition, processor 110 works in cooperation with communication interface 150 to receive request information and billing approval information including approval / denial information indicating that the billing is approved, and performs processing of step ST51, thereby functioning as an example of a determination section that determines the amount of the fee in response to input indicating the determination of the amount of the fee from both the project client and the project recipient.

[0294] Furthermore, if an operation to output a form is performed while in a standby state in which steps ST128 and ST129 in FIG. 8 are repeated, the processor 210 of the terminal device 200 judges "Yes" in step ST129 and proceeds to step ST131.

[0295] In step ST131, the processor 210 generates a form specified by the output control using the case information of the selected case. Then, the processor 210 outputs the generated form. For example, the processor 210 controls the printing device 280 to output the form as a printout. Alternatively, the processor 210 outputs the form as document data such as PDF (Portable Document Format) or XML (Extensible Markup Language), vector image data such as EPS (Encapsulated PostScript), raster image data such as PNG (Portable Network Graphics), text data such as CSV (comma-separated values), binary data, or other electronic data. The processor 210 may obtain information required for generating the form from the server device 100 as necessary. The processor 210 may obtain the form from the server device 100 instead of generating the form. In this case, the server device 100 generates the form in response to a request from the terminal device 200. Then, the server apparatus 100 transmits the generated form to the terminal apparatus 200. After the process of step ST131, the processor 210 returns to step ST127.

[0296] In addition, if an operation is performed to select a case displayed as a list on the billing list screen while in a standby state in which steps ST144 and ST145 in FIG. 9 are repeated, the processor 210 of the terminal device 200 judges the result to be Yes in step ST145 and proceeds to step ST149.

[0297] In step ST149, the processor 210 generates an image corresponding to the order item 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 order item screen.

[0298] The order item screen is a screen that displays information about an item on the billing list screen. The order item screen includes a details area, an output button, and an output control. The details area is an area that displays details of the item selected on the order item screen. The details include item information included in the billing list information received in step ST142. The details area includes, as an example, a details area AR110 as shown in FIG. 15. The output button is a button that is operated when outputting various forms for the item.

[0299] The output control is a control for specifying the type of document to be output. Examples of documents that can be output include transportation instructions, purchase orders, invoices, payment statements, offset notices, waybills, guidance instructions, vehicle number contact slips, operation instructions, transportation applications, transportation acceptances, actual transportation system management books, and various slips.

[0300] In step ST150, processor 210 waits for an operation to output a form to be performed. If an operation to output a form has been performed, processor 210 determines "Yes" in step ST150 and proceeds to step ST151.

[0301] In step ST151, the processor 210 generates a form specified by the output control using the case information of the case selected on the order case screen. Then, the processor 210 outputs the generated form in the same manner as in step ST131 of Fig. 8. After processing in step ST151, the processor 210 returns to step ST143.

[0302] When a shipper user, a transport user, a consignee user, a loading destination user, or an unloading destination user wishes to perform operation management or the like, they operate the input device 260 to input an instruction to the terminal device 200 to display a list of cases with confirmed vehicle numbers. In response to the input, the processor 210 of the terminal device 200 starts the process shown in FIG. 10, for example.

[0303] In step ST161 of FIG. 10, 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 or received by the shipper user or transport user identified by the login ID. Alternatively, the traffic list request is information requesting transmission of a list of cases with confirmed vehicle numbers among cases in which the loading destination user or unloading destination user identified by the login ID is the loading destination or unloading destination. 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.

[0304] 11, the processor 110 of the server device 100 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 ST171 and proceeds to step ST172.

[0305] In step ST172, the processor 110 determines whether or not an instruction request has been received by the communication interface 150. If an instruction request has not been received, the processor 110 determines No in step ST172 and proceeds to step ST173.

[0306] In step ST173, the processor 110 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 ST173 and proceeds to step ST174.

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

[0308] In step ST175, 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 ST175 and proceeds to step ST176.

[0309] In step ST176, the processor 110 judges 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 judges No in step ST176 and returns to step ST171. Thus, the processor 110 enters a standby state in which steps ST171 to ST176 are repeated until an operation list request, an instruction request, a schedule request, input time information, positioning information, or an operation request is received. The instruction request, schedule request, input time information, positioning information, and operation request will be described later.

[0310] If an operation list request is received while processor 110 is in a standby state in which steps ST171 to ST176 are repeated, processor 110 determines that the result is Yes in step ST171 and proceeds to step ST177.

[0311] In step ST177, processor 110 refers to the case DB to identify cases with confirmed vehicle numbers among cases ordered or accepted by the user identified by the user ID included in the operation list request received in step ST171. Such cases are, for example, cases in which the ordering source ID or supplier ID is the user ID and the value of the confirmation variable indicates a confirmed state. Alternatively, processor 110 refers to the case DB to identify cases in which the vehicle numbers are confirmed among cases in which the user identified by the user ID included in the operation list request is the loading destination or unloading destination. Such cases are, for example, cases in which the loading destination ID or unloading destination ID is the user ID and the value of the confirmation variable indicates a confirmed state.

[0312] In step ST178, the processor 110 generates operation list information. The operation list information includes a list of the cases identified in step ST177, and the case ID and case information of each of the cases. 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 ST178, the processor 110 returns to step ST171.

[0313] 10, 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 ST162 and proceeds to step ST163.

[0314] In step ST163, the processor 210 generates an image corresponding to the operation list 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 operation list screen.

[0315] The operation list screen is a screen that displays a list of cases with confirmed vehicle numbers among the cases ordered by the user identified by the login ID. Each case displayed on the operation list screen can be selected by operating the input device 260. The operation list screen also includes, as an example, a Create button and a Details button. The Create button is a button that is operated when instructing the terminal device 200 to create an operation instruction sheet for the selected case and send it to the driver. The Details button is a button that is operated when instructing the terminal device 200 to display details of the selected case.

[0316] In step ST164, processor 210 determines whether or not the Create button is operated with a case selected. If the Create button is not operated with a case selected, processor 210 determines No in step ST164 and proceeds to step ST165.

[0317] In step ST165, processor 210 determines whether or not the Details button has been operated with a case selected. If the Details button has not been operated with a case selected, processor 210 determines No in step ST165 and returns to step ST164. Thus, processor 210 enters a standby state in which steps ST164 and ST165 are repeated until the Create button or Details button is operated with a case selected.

[0318] If the create button is operated with a case selected while in a standby state in which steps ST164 and ST165 are repeated, the processor 210 determines Yes in step ST164 and proceeds to step ST166.

[0319] In step ST166, the processor 210 generates an instruction request. The instruction request includes, as an example, a login ID and a case ID of the selected case. The instruction request is information requesting that a driving instruction sheet for the case identified by the case ID be created and transmitted to the driver in charge of the case. After generating the instruction request, the processor 210 instructs the communication interface 250 to transmit the instruction request to the server device 100. Upon receiving this transmission instruction, the communication interface 250 transmits the instruction request to the server device 100. The transmitted instruction request is received by the communication interface 150 of the server device 100. After processing step ST166, the processor 210 returns to step ST164.

[0320] On the other hand, if an instruction request is received while the processor 110 of the server apparatus 100 is in a standby state in which steps ST171 to ST176 in FIG. 11 are repeated, the processor 110 judges the result to be Yes in step ST172 and proceeds to step ST179.

[0321] In step ST179, the processor 110 generates a driving instruction specified by the case ID included in the instruction request received in step ST172. The processor 110 generates the driving instruction by using, for example, the case information associated with the case ID. The driving instruction is a document for transmitting each piece of information in the operation to the driver in charge of the case. The driving instruction is notified to the driver by using the driver app. The driving instruction includes, as each piece of information, for example, the name of the client, the name of the case, the type and shape of the freight vehicle used in the operation, the scheduled time and duration of the operation, the route of the operation, the positions of each point such as waypoints and rest points, the name of the operation manager, the loading destination information, the unloading destination information, the rest point information, the fare, the toll, the cargo handling fee, and the cargo handling conditions. The processor 110 stores the generated driving instruction in the case DB 142, for example, in association with the case ID and the driver ID. The driver ID is the same as the dispatch driver ID in the case information. In addition, the processor 110 stores the generated instruction document in the operation DB 145 in association with the operation ID associated with the case ID.

[0322] In step ST180, the processor 110 generates schedule notification information. As an example, the schedule notification information includes the case ID included in the instruction request received in step ST172. The schedule notification information is information notifying that a driving instruction for the case identified by the case ID has been generated and that the driving instruction exists. The schedule notification information is information notifying the driver to whom the schedule notification information is to be sent that the driver has been decided to be in charge of the case. The schedule notification information is information notifying information such as the operation schedule and transportation conditions. The schedule notification information may include the driving instruction generated in step ST179. After generating the schedule notification information, the processor 110 instructs the communication interface 150 to transmit the schedule notification information to the terminal device 300 used by the driver in charge of the case. The driver is identified by the dispatch driver ID associated with the case ID. In response to this transmission instruction, the communication interface 150 transmits the schedule notification information to the terminal device 300. The transmitted schedule notification information is received by the terminal device 300. After the process of step ST180, processor 110 returns to step ST171.

[0323] On the other hand, in step ST201 of Fig. 12, the processor 210 of the terminal device 300 judges whether or not an operation to instruct to display the service schedule has been performed. If an operation to instruct to display the service schedule has not been performed, the processor 210 judges No in step ST201 and proceeds to step ST202.

[0324] In step ST202, the processor 210 determines whether or not the schedule notification information has been received by the communication interface 250. If the schedule notification information has not been received, the processor 210 determines No in step ST202 and returns to step ST201. Thus, the processor 210 enters a standby state in which steps ST201 and ST202 are repeated until an operation is performed to instruct the display of the operation schedule or until the schedule notification information is received.

[0325] If the schedule notice information is received while in a standby state in which steps ST201 and ST202 are repeated, the processor 210 determines that the result is Yes in step ST202 and proceeds to step ST203.

[0326] In step ST203, the processor 210 generates an image corresponding to the schedule notification 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 schedule notification screen. After the process of step ST203, the processor 210 returns to step ST201.

[0327] The schedule notification screen is a screen that displays the contents of the notification indicated by the schedule notification information. Note that the processor 210 may perform notification in a manner other than by displaying the screen.

[0328] When the driver wishes to check the operation instructions, he or she operates the input device 260 to input an instruction to the terminal device 200 to display the operation schedule.

[0329] If an operation to instruct displaying the operation schedule is performed while in a standby state in which steps ST201 and ST202 are repeated, the processor 210 judges the result to be Yes in step ST201 and proceeds to step ST204.

[0330] Furthermore, the processor 210 may determine Yes in step ST201 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.

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

[0332] In step ST204, 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 schedule of operations of a driver identified by the driver ID. The schedule request may include the above-mentioned URI instead of the driver ID. The schedule request is information requesting transmission of a list of operation schedules of cases handled by the driver. 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.

[0333] On the other hand, if the processor 110 of the server apparatus 100 receives a schedule request while in a standby state in which steps ST171 to ST176 in FIG. 11 are repeated, the processor 110 judges the result to be Yes in step ST173 and proceeds to step ST181.

[0334] In step ST181, the processor 110 refers to the case DB 142 and acquires the operation ID and operation schedule information associated with the driver ID included in the schedule request received in step ST173. The processor 110 may acquire operation IDs and operation schedule information for multiple operations. The processor 110 may acquire only the operation ID and operation schedule information for an operation that has not yet ended. The processor 110 may acquire only the 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 the operation ID and operation schedule information for an operation whose date of operation coincides with the current date. The processor 110 may acquire only the 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.

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

[0336] In step ST182, the processor 110 generates schedule information. The schedule information includes the operation ID and operation schedule information acquired in step ST181. 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 in step ST182, the processor 110 returns to step ST171.

[0337] As described above, the processor 110 works in cooperation with the communication interface 150 to process step ST182, thereby functioning as an example of a driver transmission unit that transmits the transportation conditions indicated in the transportation application form to the driver who will transport the luggage.

[0338] 12, the processor 210 of the terminal device 300 waits for the schedule information to be received by the communication interface 250. If the schedule information is received, the processor 210 judges "Yes" in step ST205 and proceeds to step ST206.

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

[0340] The schedule screen is a screen that displays the contents of the operation schedule information included in the schedule information received in step ST205. The processor 210 targets 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 target operation on the schedule screen. The processor 210 targets, for example, the operation that is closest to the current date and time among the operations that have not yet ended. The processor 210 may target the operation specified by the operation using the input device 260. The schedule screen may be capable of displaying a list of only operation schedule information that matches a condition, such as a date, by specifying the condition. In addition, the schedule screen includes the date on which the target operation will be performed and at least a part of the contents of the operation schedule information for the target operation. The schedule screen includes, as an example, a loading schedule area, an unloading schedule area, and other schedule areas.

[0341] The loading schedule area is an area that displays information related to the plan to load luggage. The information includes, for example, the date and time of loading luggage, and the name and address of the place where the luggage will be loaded. The loading schedule area is also a button. The loading schedule area 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 luggage.

[0342] The unloading schedule area is an area that displays information related to the schedule for unloading the luggage. The information includes, for example, the date and time for unloading the luggage, and the name and address of the place for unloading the luggage. The unloading schedule area is also a button. The unloading schedule area 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 schedule for unloading the luggage.

[0343] The other schedule area is an area that displays information about schedules other than loading and unloading of luggage. The information includes, for example, the contents and date and time of the schedule. The other schedule area is also a button. The other schedule area 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.

[0344] In step ST207, the processor 210 waits for any of the scheduled regions to be operated. If any of the scheduled regions has been operated, the processor 210 determines "Yes" in step ST207 and proceeds to step ST208.

[0345] In step ST208, the processor 210 generates an image corresponding to the details 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 details screen.

[0346] The details screen is a screen that displays detailed information about the plan corresponding to the operated plan area. If the loading plan area has been operated, the details screen is a screen that displays detailed information about the plan to load luggage (hereinafter referred to as "details screen a"). If the unloading plan area has been operated, the details screen is a screen that displays detailed information about the plan to unload luggage (hereinafter referred to as "details screen b"). If the loading plan area has been operated, the details screen is a screen that displays detailed information about plans other than loading and unloading luggage (hereinafter referred to as "details screen c"). The details screen shown in FIG. 7 is a screen that displays detailed information about the plan to load luggage. The details screen includes, as an example, a start input button. However, the details screen c does not have to include the start input button.

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

[0348] In step ST209, processor 210 waits for the input start button to be operated. If the input start button is operated, processor 210 determines "Yes" in step ST209 and proceeds to step ST210.

[0349] In step ST210, the processor 210 generates an image corresponding to the time input screen SC21 as shown in Fig. 20. 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 SC21.

[0350] FIG. 20 is a diagram showing an example of a time input screen SC21 displayed on the display device 270. The time input screen SC21 is a screen for inputting the date and time of each event in the schedule corresponding to the operated schedule area and transmitting the date and time to the server device 100. The time input screen SC21 (hereinafter referred to as "time input screen SC21a") when the button B22 in the detail screen a 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 SC21a 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 SC21b 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 SC21 (hereinafter referred to as "time input screen SC21b") when the button B22 in the detail screen b 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 SC21 when the button B22 in the detail screen c is operated (hereinafter referred to as "time input screen SC21c") 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 SC21 shown in FIG. 20 is the time input screen SC21a.

[0351] The time input screen SC21 includes, for example, one or more of an area AR211, an area AR212, a send button B211, a cancel button B212, and a cancel button B213.

[0352] Each area AR211 corresponds to an event. Area AR211 is an area for inputting the date and time when the corresponding event occurred.

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

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

[0355] Events corresponding to the area AR211 in the time input screen SC21c 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.

[0356] The area AR211 includes, for example, an area AR2111 and an input button B214.

[0357] The area AR212 is a button operated by the operator of the terminal device 300 when uploading an image related to the schedule corresponding to the operated schedule area. 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. The area AR212 displays the image specified by the operator.

[0358] The input button B214 is a button that is operated by the operator of the terminal device 300 when a corresponding event occurs. When the input button B214 is operated, the processor 210 displays the current date and time in an area AR2111 in the same area AR211.

[0359] Area AR2111 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 AR2111 without using input button B214. Also, the date and time displayed in area AR2111 may be changeable. Processor 210 changes the date and time based on an operational input by the operator.

[0360] The send button B211 is a button that the operator operates to instruct the terminal device 300 to send the image displayed in the area AR212 and the date and time displayed in the area AR2111. The cancel button B212 is a button that is operated to cancel the operation of the send button B211.

[0361] The cancel button B213 is a button that the operator operates to instruct the terminal device 300 to return to the details screen. When the cancel button B213 is operated, the processor 210 returns to step ST6.

[0362] In step ST211, the processor 210 determines whether or not any of the input buttons B214 has been operated. If the input button B214 has not been operated, the processor 210 determines No in step ST211 and proceeds to step ST212.

[0363] In step ST212, the processor 210 determines whether or not the send button B211 has been operated. If the send button B211 has not been operated, the processor 210 determines No in step ST212 and returns to step ST211. Thus, the processor 210 enters a standby state in which steps ST211 and ST212 are repeated until the input button B214 or the send button B211 is operated.

[0364] If the input button B214 is operated while in a standby state in which steps ST211 and ST212 are being repeated, the processor 210 determines that the answer is Yes in step ST211, and proceeds to step ST213.

[0365] In step ST213, 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 B214 occurred. The processor 210 also displays the current date and time in an area AR2111 in the same area AR211 as the operated input button B214. After the process of step ST213, the processor 210 returns to step ST211.

[0366] If the transmission button B211 is operated while in a standby state in which steps ST211 and ST212 are repeated, the processor 210 judges the result to be Yes in step ST212 and proceeds to step ST214.

[0367] In step ST214, 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 SC21. The input time information includes, for example, the case ID of the case selected in the case selection area, the driver ID stored in the terminal device 300, the operation ID of the target operation, the image displayed in the area AR212, and the date and time displayed in the area AR2111. In other words, the date and time displayed in the area AR2111 is the date and time stored in step ST213. 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 in step ST214, the processor 210 returns to step ST211. Alternatively, when the time input screen SC21a is being displayed, the processor 210 may return to step ST210. Then, in step ST210, the processor 210 determines that the unloading planned area has been operated, and displays the time input screen SC21b.

[0368] 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 ST171 to ST176 in FIG. 11 are repeated, the processor 110 judges the result to be Yes in step ST174 and proceeds to step ST183.

[0369] In step ST183, the processor 110 updates the real-time information in the case DB 142 and the operation DB 145 based on the input time information received in step ST174. To this end, the processor 110 writes each time included in the input time information into the real-time information. The real-time information is included in the case information of the case identified by the case ID included in the input time information. The real-time information is also associated with the operation ID included in the input time information.

[0370] In step ST184, 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)

[0371] 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)

[0372] 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)

[0373] 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)

[0374] 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)

[0375] 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)

[0376] 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)

[0377] 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 of 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)

[0378] 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)

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

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

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

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

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

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

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

[0386] In step ST185, the processor 110 writes the calculation result in step ST184 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 ST183.

[0387] In step ST186, when the processor 110 inputs the actual time for the unloading destination into the real time information, the processor 110 inputs the actual vehicle mileage and the actual vehicle mileage into the transportation acceptance. The transportation acceptance is stored in the case DB 142 in association with the case ID included in the input time information received in step ST174. The actual vehicle mileage is, for example, the time from the departure date and time of the loading destination to the arrival date and time of the unloading destination. The actual vehicle mileage is the actual mileage from the loading destination to the unloading destination. The processor 210 calculates the actual vehicle mileage using, for example, the driver's location information. The processor 210 refers to the driver DB 144 and acquires the location information associated with the driver ID included in the input time information received in step ST174. After processing in step ST186, the processor 110 returns to step ST171.

[0388] 13, the processor 210 of the terminal device 300 measures the position of the terminal device 300 using the positioning unit 310. In step ST221 of FIG.

[0389] In step ST222, 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 ST221. 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 instruction to transmit, 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 the process of step ST222, the processor 210 returns to step ST221. 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.

[0390] On the other hand, if the processor 110 of the server apparatus 100 receives positioning information while in a standby state in which steps ST171 to ST176 in FIG. 11 are repeated, the processor 110 judges the result to be Yes in step ST175 and proceeds to step ST187.

[0391] In step ST187, the processor 110 associates the driver ID included in the positioning information received in step ST176 with the location information and date and time included in the positioning information, and stores them in the driver DB 144. After the process of step ST187, the processor 110 returns to step ST171.

[0392] When the shipper user and the transport user wish to check detailed information about an item displayed on the operation list screen, for example, the shipper user and the transport user select the item and then operate the details button.

[0393] On the other hand, when the processor 210 of the terminal device 200 is in a standby state in which steps ST164 and ST165 are repeated, if the details button is operated with a case selected, the processor 210 judges the result to be Yes in step ST165 and proceeds to step ST167.

[0394] In step ST167, the processor 210 generates an operation request. The operation request includes, as an example, a login ID and a case ID of the selected case. The operation request is information requesting transmission of detailed information about the case identified by the case 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.

[0395] On the other hand, if an operation request is received while the processor 110 of the server apparatus 100 is in a standby state in which steps ST171 to ST176 in FIG. 11 are repeated, the processor 110 judges the result to be Yes in step ST176 and proceeds to step ST188.

[0396] In step ST188, the processor 110 refers to the case DB 142 to acquire case information of the case identified by the case ID included in the operation request received in step ST176. The processor 110 also refers to the driver DB 144 to acquire location information and date and time associated with the dispatch driver ID included in the case information. The processor 110 also refers to the operation DB 145 to acquire operation schedule information associated with the operation ID. The operation ID is the operation ID associated with the case ID included in the operation request.

[0397] In step ST189, the processor 110 uses the real-time information acquired in step ST188 to determine the transportation status of the case identified by the case ID included in the operation request received in step ST176. The transportation status indicates the current status of the operation of the case. The transportation status can be, for example, operation not started, already shipped out, traveling, waiting to be loaded, loading, loading completed, waiting to be unloaded, unloading, unloading completed, and operation completed. The processor 110 determines the transportation status as follows, for example. Note that the completion of loading and unloading means the end of operation from the viewpoint of the shipper user.

[0398] If the real-time information includes the return date and time or the end date and time of operation, the processor 110 determines that operation has ended. Otherwise, if the real-time information includes the departure date and time of the unloading destination, the processor 110 determines that the vehicle is traveling. Otherwise, if the real-time information includes the end date and time of loading / unloading, the processor 110 determines that unloading has ended. Otherwise, if the real-time information includes the start date and time of loading / unloading, the processor 110 determines that unloading is in progress. Otherwise, if the real-time information includes the start date and time of loading / unloading, the processor 110 determines that the vehicle is waiting to be unloaded. Otherwise, if the real-time information includes the departure date and time of the loading destination, the processor 110 determines that the vehicle is traveling. Otherwise, if the real-time information includes the end date and time of loading, the processor 110 determines that loading has ended. Otherwise, if the real-time information includes the start date and time of loading, the processor 110 determines that loading is in progress. Otherwise, if the real-time information includes the date and time when waiting at the loading destination started, processor 110 considers the item to be waiting for loading. Otherwise, if the real-time information includes the date and time when the item leaves the warehouse or the date and time when operation started, processor 110 considers the item to have been left the warehouse. Otherwise, processor 110 considers the operation to have not yet started. 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 when the item returns to the warehouse and the date and time when operation ended function as flags that indicate the end of operation.

[0399] In step ST190, the processor 110 uses the latest location information and date and time acquired in step ST190 to calculate the estimated date and time of arrival of the driver in charge of the job at the destination (hereinafter referred to as the "estimated arrival date and time"). At this time, the processor 110 calculates the estimated arrival date and time using, for example, the most recent location information and date and time. The date and time of arrival of the driver at the destination is also the date and time of arrival of the truck used for the job at the destination. If the transportation status determined in step ST189 is "unloaded", the processor 110 calculates the estimated arrival date and time with the destination as the loading destination. If the transportation status is "loading completed", the processor 110 calculates the estimated arrival date and time with the destination as the unloading destination. If the transportation status is "unloading completed", the processor 110 calculates the estimated arrival date and time with the destination as the return location. In addition, if the calculated estimated arrival date and time is later than the scheduled date and time, the processor 110 calculates the estimated delay time. The scheduled date and time is, for example, the date and time of instruction for loading or unloading requested by the shipper, or the scheduled date and time of waiting to start. The predicted delay time is the difference between the predicted arrival date and time and the scheduled date and time. Note that processor 110 may calculate the time it will take to arrive (hereinafter referred to as the "predicted arrival time") instead of or in addition to the predicted arrival date and time. The time it will take to arrive is the time from the current date and time to the predicted arrival date and time. The predicted arrival date and time and the predicted arrival time are collectively referred to as arrival prediction information.

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

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

[0402] In step ST191, the processor 110 generates operation information. The operation information includes the case information, location information, date and time, and operation schedule information acquired in step ST188. The operation information also includes the transportation status determined in step ST189. The operation information also includes the predicted arrival date and time and predicted delay time calculated in step ST190. After generating the operation information, the processor 110 instructs the communication interface 150 to transmit the operation information to the terminal device 200. Upon receiving 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 step ST191, the processor 110 returns to step ST171.

[0403] As described above, the processor 110 works in cooperation with the communication interface 150 to transmit operation information to the terminal device 200 used by the loading destination user or the unloading destination user, and thereby functions as an example of a loading / unloading transmission unit that transmits the transportation conditions indicated in the transportation application form to at least one of the user who operates and manages the loading destination of the cargo and the user who operates and manages the unloading destination of the cargo.

[0404] 12, 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 ST168 and proceeds to step ST169.

[0405] In step ST169, the processor 210 generates an image corresponding to the operation information screen SC11 as shown in Fig. 17. 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 SC11. When the processor 210 ends the display of the operation information screen SC11, the process returns to step ST161.

[0406] FIG. 17 is a diagram showing an example of an operation information screen SC11 displayed on the display device 270. The operation information screen SC11 is a screen that displays at least a part of the case information, operation schedule information, transportation status, predicted arrival date and time, predicted delay time, and operation position information for the case selected on the operation list screen. The case information is the case information included in the operation information received in step ST168. The transportation status is the transportation status included in the operation information. The predicted arrival date and time and the predicted delay time are the predicted arrival date and time and the predicted delay time included in the operation information. When the real-time information included in the case information includes each time, the operation information screen SC11 displays each time. The real-time information preferably includes a cargo waiting time and a cargo handling operation time. When an image is included in the real-time information, the operation information screen SC11 may display the image. In addition, the operation information screen SC11 is a screen that displays operation position information.

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

[0408] The operation information screen SC11 includes, for example, a detail area AR110, a detail area AR130, and a map area AR140. The detail area AR110 is an area that displays at least a part of the details of the case. The detail area AR110 in FIG. 17 is the same as that in FIG. 15, so a description thereof will be omitted.

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

[0410] The map area AR140 is an area that displays the operation position information using a map. The map area AR140 displays the driver's position indicated by the operation position information on the map. The map area AR140 also displays the positions of the loading destination, unloading destination, and other destinations on the map. The map area AR140 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 may be a straight-line distance. The map area AR140 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.

[0411] According to the vehicle dispatch system 1 of the embodiment, the server device 100 obtains the contract master stored in the auxiliary storage device 140. Then, the server device 100 of the embodiment generates a transportation application form using the contract master. In this way, at least a portion of the data indicating the transportation application form is automatically generated, so the effort of creating the transportation application form is reduced. Furthermore, since the effort of creating the transportation application form is reduced, the effort of the transportation contract is reduced. Furthermore, since it is not necessary to send written documents for the transportation contract, the effort of sending written documents is reduced.

[0412] According to the vehicle dispatch system 1 of the embodiment, the server device 100 acquires the fee master stored in the auxiliary storage device 140. Then, the server device 100 of the embodiment calculates the amount of the transportation fee using the contract master. It reduces the hassle.

[0413] Moreover, according to the vehicle dispatch system 1 of the embodiment, the server device 100 generates data indicative of a transportation acceptance. In this way, at least a portion of the data indicative of the transportation acceptance is automatically generated, so the effort of creating the transportation acceptance is reduced. Also, since the effort of creating the transportation acceptance is reduced, the effort of the transportation contract is reduced. Furthermore, since it is not necessary to send written documents for the transportation contract, the effort of sending written documents is reduced.

[0414] Furthermore, according to the vehicle dispatch system 1 of the embodiment, the server device 100 transmits data indicating a transportation application form to the recipient of the order. Furthermore, the server device 100 of the embodiment transmits a transportation acceptance to the recipient of the order. This reduces the effort required for a transportation contract, as a transportation contract is deemed to have been concluded without the need for a written document. The transportation acceptance includes the scheduled dates and times of collection and delivery, or dispatch and arrival, and the amount of consideration such as freight and fees. This determines that a transportation contract is concluded.

[0415] According to the vehicle dispatch system 1 of the embodiment, the server device 100 transmits the transportation conditions to the driver, thereby reducing the driver's effort to understand the transportation conditions.

[0416] According to the vehicle dispatch system 1 of the embodiment, the server device 100 transmits the transportation conditions to the loading and unloading destinations, thereby reducing the effort required to grasp the transportation conditions of the loading and unloading destinations.

[0417] Furthermore, according to the vehicle dispatch system 1 of the embodiment, the server device 100 automatically calculates the cargo handling fee using the real-time information and the fare table master, thereby reducing the effort required for calculating the cargo handling fee.

[0418] Furthermore, according to the vehicle dispatch system 1 of the embodiment, the server device 100 allows both the ordering party and the ordering party to change the amount of the consideration. This allows the creation of an invoice and the change and confirmation of the amount on the invoice to be performed only on the vehicle dispatch system 1. This reduces the effort required for the adjustment and confirmation of the amount between the ordering party and the ordering party regarding the invoice payment. It also reduces the effort required for invoice creation and invoice processing.

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

[0420] The shipper may be able to register the price list master. In this case, the dispatch system 1 may use the price list master of the ordering source instead of the price list master of the ordering destination. The shipper registers the price list master, for example, based on the case information of the case registered by the shipper. By using such a price list master to display the charges such as freight and fees, even an employee with little experience at the company can easily set the charges when placing an order.

[0421] There may be multiple loading destinations for one order. There may be multiple unloading destinations for one order.

[0422] The operation information screen SC11 shown in Fig. 17 displays information about one case. However, the terminal device 200 may be able to display a screen including information about multiple cases. As an example of such a screen, a management screen SC12 is shown in Fig. 18. The processor 210 obtains information necessary for displaying the management screen SC12 from the server device 100.

[0423] 18 is a diagram showing an example of the management screen SC12 displayed on the display device 270. The management screen SC12 includes, for each of a plurality of cases, information on whether loading has been completed, whether the truck performing the transport for the case has arrived and started waiting, whether loading and unloading work has started, the company name of the shipper user who ordered the case, the vehicle number of the truck performing the transport for the case, whether the own vehicle or a chartered vehicle is used, and the latest location indicated by the operation location information. In addition, the management screen SC12 includes, for each of a plurality of cases, the scheduled start date and time, scheduled end date and time, start date and time of waiting, start date and time, and end date and time of at least one of loading and unloading. Each date and time in the management screen SC12 may be modifiable.

[0424] The management screen SC12 allows the user to select a case. The processor 210 displays details of the selected case. The processor 210 displays details of the selected case on, for example, an operation information screen SC11 as shown in Fig. 17 or an operation information screen SC13 as shown in Fig. 19.

[0425] 19 is a diagram showing an example of an operation information screen SC13 displayed on the display device 270. As an example, the operation information screen SC13 includes, for the case selected on the management screen SC12, the vehicle number of the truck performing the transport, the name of the driver performing the transport, 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. As with the operation information screen SC11, the processor 210 changes the way of displaying an area on the operation information screen SC13 where a time exceeding a predetermined time is displayed.

[0426] The processor 210 may overlay and display the operation management screen SC3 on the management screen SC12. The processor 210 may use the management screen SC12 as the operation list screen. The processor 210 may display the operation information screen SC13 instead of the operation information screen SC11.

[0427] In the above embodiment, the time is input based on the operation of the input button B214. 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.

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

[0429] The vehicle transporting the luggage may be unmanned. In this case, it is not necessary to specify a driver on the vehicle dispatch screen.

[0430] In the above embodiment, the users are transport companies and shippers, and the cases are cases of transporting luggage. However, the billing system of the embodiment may be adapted to users other than transport companies and shippers and cases other than cases of transporting luggage.

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

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

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

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

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

[0436] 1. Vehicle dispatch system 100 Server Devices 110,210 processors 120,220 ROM 130,230 RAM 140,240 Auxiliary storage 141 User DB 142 Project DB 143 Vehicle DB 144 Driver DB 145 Operation DB 146 Billing DB 150,250 Communication Interface 160,290 Bus 200,300 terminal devices 260 Input Devices 270 Display Devices 280 Printing Device 310 Positioning Unit

Claims

1. an acquisition unit that acquires pre-created contract master data from a storage device that stores the contract master data, the contract master data being used for generating a transportation application form for placing an order for transporting a package; A generation device comprising: a generation unit that generates data indicating the transportation application form for ordering the project using the contract master data, and stores the data indicating the transportation application form in a storage device.

2. The acquisition unit acquires from a storage device a tariff indicating a price for transportation by a transporter transporting the luggage, The generating device according to claim 1 , further comprising a calculation unit that calculates an amount of the consideration for the case using the fee schedule.

3. The generating device according to claim 1 , wherein the generating unit generates data indicating a transportation acceptance indicating that the job has been accepted, and stores the data in the storage device in association with the transportation application form.

4. The generating device according to claim 3 , further comprising a contract sending unit configured to send data indicating the transportation acceptance to an orderer of the project.

5. The generating device according to claim 1 , further comprising a contract sending unit that sends information indicating that a truck and a driver for transporting the project have been determined to a client of the project.

6. The generation device according to claim 1 , further comprising a driver sending unit that sends the transportation conditions indicated in the transportation application form to a driver who will transport the luggage.

7. The generating device according to claim 1, further comprising a loading / unloading transmission unit that transmits the transportation conditions indicated in the transportation application form to at least one of a user who operates and manages the loading destination of the cargo and a user who operates and manages the unloading destination of the cargo.

8. a calculation unit that calculates a waiting fee and a handling fee using a time required for waiting and a time required for handling in the transportation of the luggage and a fee table that indicates the amount of the transportation fee by the transporter that transports the luggage; The generating device according to claim 1 , further comprising an invoice sending unit that sends an invoice indicating a price for the transportation, including the loading and unloading fee, to an orderer of the project.

9. a change unit that changes the amount of the consideration based on at least one of an input from an orderer of the project instructing a change to the amount of the consideration and an input from a recipient of the project instructing a change to the amount of the consideration, and The generating device according to claim 8 , wherein the invoice sending unit sends the invoice in which the changes are reflected.

10. The generating device according to claim 8 , further comprising a confirmation unit that confirms an amount of the consideration upon receiving an input indicating confirmation of the amount of the consideration from both an orderer of the job and a recipient of the job.

11. A processor included in the generating device, an acquisition unit that acquires pre-created contract master data from a storage device that stores the contract master data, the contract master data being used for generating a transportation application form for placing an order for transporting a package; A program that functions as a generation unit that generates data indicating the transportation application form for ordering the project using the contract master data, and stores the data indicating the transportation application form in a storage device.

12. Acquire pre-created contract master data from a storage device that stores the contract master data, which is used for generating a transportation application form for placing an order for transporting luggage; A generation method, which uses the contract master data to generate data representing the transportation application form for ordering the project, and stores the data representing the transportation application form in a storage device.

Images