Joint delivery support device, joint delivery support method, and program

Abstract

Conventionally, it has been difficult to realize appropriate joint delivery to improve the efficiency of package delivery. [Solution] The above problem can be solved by a joint delivery support device 1 which includes a project management unit 114 in which project information for joint delivery of parcels is stored, a delivery task management unit 113 in which one or more delivery task information each corresponding to a delivery task identifier and each having an organization identifier, receiving base information, shipping base information, and running time zone information is stored, a condition receiving unit 122 which receives project conditions for configuring a project, a project registration unit 132 which associates project information including the project conditions with the project identifier and stores the project information in the project management unit 114, a delivery task selection unit 133 which, based on delivery task information from one organization, selects delivery task information from another organization that satisfies the project conditions and joint delivery conditions, and a joint delivery transmission unit 141 which transmits the selected delivery task information.

Description

[Technical Field]

[0001] The present invention relates to a joint delivery support device that supports joint delivery of packages. [Background technology]

[0002] Conventionally, there has been a delivery plan support system that allows easy selection of a joint delivery service that enables efficient delivery (see Patent Document 1). [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2024-49463 Summary of the Invention [Problem to be solved by the invention]

[0004] However, it has been difficult to easily realize appropriate joint delivery to improve the efficiency of package delivery.

[0005] In particular, in the past, projects for joint deliveries were not configured, and users were unable to easily carry out joint deliveries of two or more delivery tasks that met the joint delivery conditions while meeting the appropriate project conditions for the project in which the user's organization participates. [Means for solving the problem]

[0006] The first invention of the joint delivery support device is a joint delivery support device comprising: a project management unit that stores project information, which is information corresponding to the project identifier that identifies the project and has project conditions that are conditions for a joint delivery of goods and have two or more organization identifiers; a delivery task management unit that stores two or more delivery task information that is corresponding to a delivery task identifier that identifies a delivery task and has an organization identifier that identifies the organization of the delivery task, receiving base information, shipping base information, and running time zone information; a condition receiving unit that receives project conditions that have an organization identifier of an organization other than the organization identified by the one organization identifier; a project registration unit that associates the project information including the project conditions received by the condition receiving unit with the project identifier and stores it in the project management unit; a delivery task selection unit that selects from the delivery task management unit delivery task information that satisfies the project conditions contained in the project information stored by the project registration unit and the joint delivery conditions that are conditions for joint delivery, for delivery task information that corresponds to the delivery task identifier paired with the one organization identifier, and that includes the organization identifier of an organization other than the organization identified by the one organization identifier; and a joint delivery transmission unit that transmits all or part of the delivery task information selected by the delivery task selection unit.

[0007] With this configuration, a project for joint delivery is created, and by selecting delivery tasks that satisfy the project conditions in the project and the joint delivery conditions for joint delivery, the joint delivery desired by the user can be efficiently realized.

[0008] In addition, the joint delivery support device of the second invention, compared to the first invention, further includes a proposal instruction receiving unit that receives a proposal instruction for joint delivery, which is a proposal instruction corresponding to a delivery task identifier, and the delivery task selection unit is a joint delivery support device that selects from the delivery task management unit delivery task information that satisfies the project conditions contained in the project information and the joint delivery conditions for the delivery task information identified by the delivery task identifier corresponding to the proposal instruction received by the proposal instruction receiving unit.

[0009] With this configuration, it is possible to propose a joint delivery in accordance with the proposal instruction.

[0010] Furthermore, the joint delivery support device of the third invention is a joint delivery support device according to the first or second invention, further comprising a project approval receiving unit that receives project approval information indicating approval for the project conditions received by the condition receiving unit from an organization identified by an organization identifier included in the project conditions, and the project registration unit is a joint delivery support device that, when the project approval receiving unit receives project approval information for the project conditions from organizations identified by one or more organization identifiers among two or more organization identifiers included in the project conditions excluding at least the organization identifier of the organization that transmitted the project conditions received by the condition receiving unit, stores the project information in the project management unit in association with the project identifier, assuming that the project has been established.

[0011] This arrangement allows for joint delivery projects that are approved by all parties involved.

[0012] In addition, the joint delivery support device of the fourth invention is the joint delivery support device of any one of the first to third inventions, further comprising a joint delivery management unit in which one or more joint delivery information indicating that two or more delivery tasks will be carried out by joint delivery is stored, the joint delivery sending unit sends all or part of the delivery task information selected by the delivery task selection unit to an organization identified by the organization identifier contained in the delivery task information, and receives joint delivery consent information from the organization to the effect that the delivery task specified by the delivery task information is permitted to be carried out by joint delivery, and a joint delivery registration unit that, when the joint delivery consent receiving unit receives the joint delivery consent information, stores in the joint delivery management unit joint delivery information indicating that the delivery task specified by the delivery task information corresponding to the delivery task identifier paired with one organization identifier and the delivery task specified by the delivery task information selected by the delivery task selection unit will be carried out by joint delivery.

[0013] With this arrangement, only joint deliveries authorized by all parties can be accomplished.

[0014] Furthermore, the joint delivery support device of the fifth invention is a joint delivery support device in which, compared to any one of the first to fourth inventions, the project conditions include organizational conditions of the proposing organization proposing the joint delivery and organizational conditions of the proposed organization to which the joint delivery is proposed, and the organizational conditions include an organizational identifier having a company identifier, or an organizational identifier having a company identifier and a department identifier, and period information specifying a period.

[0015] With this configuration, a project for joint delivery is created, and by selecting delivery tasks that satisfy appropriate project conditions and joint delivery conditions, the joint delivery desired by the user can be efficiently realized.

[0016] In addition, the joint delivery support device of the sixth invention is a joint delivery support device according to any one of the first to fifth inventions, further comprising a delivery task receiving unit that receives delivery task information of two or more organizations, and a delivery task storage unit that stores the delivery task information received by the delivery task receiving unit in the delivery task management unit in association with a delivery task identifier.

[0017] This configuration makes it possible to manage information on delivery tasks for candidates for joint delivery.

[0018] In addition, the joint delivery support device of the seventh invention is a joint delivery support device according to any one of the first to sixth inventions, further comprising a baggage rule management unit in which delivery task information has baggage attribute values ​​and baggage rules, which are rules regarding baggage that cannot be mixed, are stored, and the delivery task selection unit uses the baggage rules to select delivery task information that includes baggage attribute values ​​of baggage that cannot be mixed, for the baggage attribute values ​​of delivery task information that corresponds to a delivery task identifier paired with an organization identifier.

[0019] This configuration allows for efficient joint delivery, taking into consideration appropriate cargo consolidation.

[0020] Furthermore, the joint delivery support device of the eighth invention is a joint delivery support device according to any one of the first to seventh inventions, further comprising an organization relationship management unit in which one or more relationship information specifying the relationship between two or more organizations is stored, and the joint delivery transmission unit transmits different information contained in the delivery task information depending on the relationship information specifying the relationship between an organization identified by one organization identifier and another organization.

[0021] With this configuration, it is possible to efficiently realize joint delivery while presenting appropriate information to each organization according to the relationship between the organizations.

[0022] Furthermore, the joint delivery support device of the ninth invention is a joint delivery support device according to any one of the first to eighth inventions, in which the joint delivery conditions are one or two of mixed loading conditions for determining whether mixed loading is possible, or return flight conditions for determining whether joint delivery using a return flight is possible.

[0023] With this configuration, a project for joint delivery can be created and joint delivery that satisfies the joint delivery conditions of the project can be carried out, thereby efficiently realizing the joint delivery desired by the user. [Effects of the Invention]

[0024] According to the joint delivery support device of the present invention, a project for joint delivery can be created and joint delivery that satisfies the joint delivery conditions of the project can be carried out, thereby efficiently realizing the joint delivery desired by the user. [Brief explanation of the drawings]

[0025] [Figure 1] Conceptual diagram of information system A in embodiment 1 [Figure 2] Block diagram of Information System A [Figure 3] Block diagram of the joint delivery support device 1 [Figure 4] A flowchart illustrating an example of the operation of the joint delivery support device 1. [Figure 5]A flowchart illustrating an example of the operation of the joint delivery support device 1. [Figure 6] A flowchart illustrating an example of the joint delivery proposal process [Figure 7] A flowchart illustrating an example of the single-task joint proposal process. [Figure 8] A flowchart illustrating an example of the operation of the terminal device 2 [Figure 9] A flowchart illustrating an example of the operation of the terminal device 2 [Figure 10] An example of the organization management table [Figure 11] An example of a cargo rule management table [Figure 12] Figure showing an example of the delivery task management table [Figure 13] An example of the project management table [Figure 14] An example of the joint delivery management table is shown below. [Figure 15] A diagram showing an example of the project registration screen [Figure 16] Figure showing an example of the output [Figure 17] Figure showing an example of the output [Figure 18] Figure showing an example of the output [Figure 19] Figure showing an example of the output [Figure 20] Block diagram of the computer system DETAILED DESCRIPTION OF THE INVENTION

[0026] Hereinafter, embodiments of the joint delivery support device and the like will be described with reference to the drawings. Note that, in the embodiments, components with the same reference numerals perform similar operations, and therefore, repeated description may be omitted.

[0027] (Embodiment 1) In this embodiment, we will explain a joint delivery support device that accepts project conditions, configures a project based on the project conditions, selects delivery tasks that correspond to the project and satisfy the joint delivery conditions, and serves as a platform to support the realization of joint delivery. Note that it is preferable that the project is a project composed of two or more organizations (for example, two or more different companies).

[0028] In this embodiment, a joint delivery support device that proposes candidate delivery tasks for joint delivery for a delivery task corresponding to a received proposed instruction will be described.

[0029] In this embodiment, a joint delivery support device that forms a project only when the parties agree to the project conditions will be described.

[0030] In this embodiment, a joint delivery support device will be described which notifies the parties concerned of delivery task information candidates for joint delivery, and performs processing to carry out joint delivery only when consent is received from the parties concerned.

[0031] In this embodiment, a joint delivery support device that receives and stores delivery task information from one or more organizations will be described.

[0032] In this embodiment, a joint delivery support device will be described that performs processing for carrying out joint delivery to realize appropriate mixed loading of cargo using cargo rules that prohibit mixed loading.

[0033] In this embodiment, a cooperative delivery support device capable of changing the output contents of delivery task information in accordance with organizational relationship information will be described.

[0034] In this specification, information X being associated with information Y means that information Y can be obtained from information X, or information X can be obtained from information Y, and the method of association is not important. Information X and information Y may be linked, may exist in the same buffer, information X may be included in information Y, or information Y may be included in information X, etc.

[0035] Furthermore, in this specification, selecting or determining information Z means obtaining information Z, obtaining a pointer to information Z, obtaining the ID of information Z, setting a flag on information Z, etc., and it is sufficient if information Z can be accessed.

[0036] 1 is a conceptual diagram of an information system A according to this embodiment. The information system A includes a joint delivery support device 1 and one or more terminal devices 2.

[0037] The joint delivery support device 1 is a device that serves as a platform that accepts project conditions, configures a project based on the project conditions, selects delivery tasks that correspond to the project and satisfy the joint delivery conditions, and supports the realization of joint delivery. The joint delivery support device 1 is, for example, a cloud server or an ASP server, but the type is not important.

[0038] The terminal device 2 is a terminal used by a user. The user is, for example, a member of an organization that performs a delivery task. The user is, for example, a member of an organization that benefits from joint delivery. The user is, for example, a person who has been entrusted with the operation of the joint delivery support device 1 by an organization that performs a delivery task. Note that a delivery task is the task of delivering packages using a moving object (for example, a vehicle such as a truck). The terminal device 2 is, for example, a so-called personal computer, a tablet terminal, or a smartphone, but the type is not important.

[0039] The joint delivery support device 1 and one or more terminal devices 2 can communicate with each other via a network such as the Internet.

[0040] Fig. 2 is a block diagram of the information system A in this embodiment. Fig. 3 is a block diagram of the joint delivery support device 1.

[0041] The joint delivery support device 1 includes a storage unit 11, a receiving unit 12, a processing unit 13, and a transmitting unit 14. The storage unit 11 includes an organization management unit 110, a package rule management unit 111, an organization relationship management unit 112, a delivery task management unit 113, a project management unit 114, and a joint delivery management unit 115. The receiving unit 12 includes a delivery task receiving unit 121, a condition receiving unit 122, a project approval receiving unit 123, a proposal instruction receiving unit 124, a joint delivery instruction receiving unit 125, and a joint delivery approval receiving unit 126. The processing unit 13 includes a delivery task accumulation unit 131, a project registration unit 132, a delivery task selection unit 133, and a joint delivery registration unit 134. The transmitting unit 14 includes a joint delivery transmission unit 141. Note that each management unit constituting the storage unit 11 may exist in an external device (not shown).

[0042] The terminal device 2 includes a terminal storage unit 21, a terminal reception unit 22, a terminal processing unit 23, a terminal transmission unit 24, a terminal reception unit 25, and a terminal output unit 26.

[0043] Various types of information are stored in the storage unit 11 constituting the joint delivery support device 1. The various types of information include, for example, organizational information (described later), cargo rules (described later), relationship information (described later), delivery task information (described later), project information (described later), joint delivery information (described later), and joint delivery conditions. It goes without saying that the various conditions in the storage unit 11 may be embedded in a program.

[0044] Joint delivery conditions are conditions for joint delivery of cargo. Joint delivery conditions are consolidated conditions, or return flight conditions, or consolidated conditions and return flight conditions. Consolidated conditions and return flight conditions are consolidated conditions OR return flight conditions. In other words, joint delivery conditions are one or both of consolidated conditions or return flight conditions.

[0045] Consolidation conditions are conditions for transporting cargo scheduled to be transported by two or more delivery tasks together. Consolidation conditions include, for example, that the shipping bases of the two or more delivery tasks are the same or the distance between them is within a threshold, that the receiving bases of the two or more delivery tasks are the same or the distance between them is within a threshold, that the total amount of cargo for the two or more delivery tasks is less than the maximum load capacity of the vehicle for one delivery task, that the difference in the scheduled shipping times for the two or more delivery tasks is within a threshold, and that the difference in the scheduled arrival times for the two or more delivery tasks is within a threshold. Note that consolidation conditions may include other conditions. Consolidation conditions may also be other conditions.

[0046] The return trip conditions are conditions for loading cargo for other delivery tasks on the return trip after the cargo has been unloaded on the outbound trip. Examples of the return trip conditions include: the receiving point for one delivery task is the same as the shipping point for the other delivery task, or the distance between them is within a threshold; the point (e.g., the shipping point) to which the vehicle for one delivery task returns is the same as the receiving point for the other delivery task, or the distance between them is within a threshold; the difference between the scheduled arrival time for one delivery task and the scheduled departure time for the other delivery task is within a threshold; and the attribute values ​​(e.g., vehicle type, maximum load capacity) of the vehicle for one delivery task are the same as the attribute values ​​(e.g., vehicle type, maximum load capacity) of the vehicle for the other delivery task. The return trip conditions may include other conditions. The return trip conditions may also be other conditions.

[0047] The organization management unit 110 stores one or more pieces of organization information. Organization information is information about organizations that will benefit from joint delivery. Organization information is usually associated with an organization identifier. Organization information usually has one or more organization attribute values. Organization information includes, for example, user information. Organization information includes, for example, a project approval flag, a joint delivery approval flag, and an immediate proposal flag.

[0048] An organization identifier is information that identifies an organization. For example, an organization is an organization that performs a delivery task, an organization that outsources a delivery task to another company, or an organization that is responsible for a delivery task. An organization identifier is, for example, a company identifier, or a company identifier and a department identifier. An organization identifier is, for example, an organization ID. A company identifier is information that identifies a company. For example, a company identifier is a company name or a company ID. A department identifier is information that identifies a department. For example, a department identifier is a department name or a department ID.

[0049] The one or more organization attribute values ​​included in the organization information are, for example, an address and a telephone number.

[0050] User information is information about a user. A user is usually a person who belongs to an organization, but may also be a person who has been entrusted by the organization to use the joint delivery support device 1. User information includes, for example, a user identifier and contact information. The user identifier is, for example, the user's ID and the user's name. Contact information is information that indicates how to contact the user. Contact information is, for example, an email address, a phone number, and an ID for an SNS (e.g., Line (registered trademark), Slack (registered trademark)) for contact.

[0051] The project permission flag is information indicating whether permission is required to configure a project. The project permission flag can be, for example, "ON (e.g., "1")," which indicates that permission is required to configure a project, or "OFF (e.g., "0")," which indicates that permission is not required to configure a project.

[0052] The joint delivery permission flag is information indicating whether permission is required when deciding on joint delivery. The joint delivery permission flag can be, for example, "ON (e.g., "1")," which indicates that permission is required when deciding on joint delivery, or "OFF (e.g., "0")," which indicates that permission is not required when deciding on joint delivery.

[0053] The immediate proposal flag is information indicating whether or not a proposal for joint delivery is desired once the project is finalized. The immediate proposal flag can be, for example, "ON (e.g., "1")," indicating that a proposal for joint delivery is desired once the project is finalized, or "OFF (e.g., "0")," indicating that a proposal for joint delivery is not desired once the project is finalized.

[0054] The luggage rule management unit 111 stores one or more luggage rules. A luggage rule is a rule regarding luggage that cannot be mixed. A luggage rule has, for example, a luggage identifier for each of two or more luggage that cannot be mixed. A luggage rule has, for example, a type identifier for each of two or more luggage that cannot be mixed. A type identifier is information that specifies the type of luggage. Examples of luggage rules are (frozen food, drink) and (medicine, food). (Frozen food, drink) is a rule that indicates that the luggage type "frozen food" cannot be mixed with the luggage type "drink". (Medicine, food) is a rule that indicates that the luggage type "medicine" cannot be mixed with the luggage type "food".

[0055] The organizational relationship management unit 112 stores one or more pieces of relationship information. Relationship information is information that specifies the relationship between two or more organizations. The relationship information is, for example, a flag that indicates whether or not two or more organizations are affiliated companies. The relationship information includes, for example, the organizational identifiers of two organizations that do not perform joint delivery.

[0056] The delivery task management unit 113 stores one or more pieces of delivery task information. Delivery task information is information related to delivery tasks. The delivery task information in the delivery task management unit 113 corresponds to a delivery task identifier. The delivery task information has an organization identifier. The delivery task information has, for example, one or more pieces of shipping location information, one or more pieces of receiving location information, and travel time zone information. The delivery task information has, for example, travel time. The delivery task information has, for example, the number of trips. The delivery task information has, for example, one or more package attribute values ​​and one or more vehicle attribute values.

[0057] The delivery task identifier is information for identifying a delivery task, such as the ID or name of the delivery task.

[0058] The shipping base information is information that identifies the base that receives the package. The shipping base information is, for example, one or more pieces of information from the base name, address, and (latitude, longitude).

[0059] The receiving base information is information that identifies the base from which the package is shipped. The receiving base information is, for example, one or more pieces of information from the base name, address, and (latitude, longitude).

[0060] The time period information is information that specifies the time period during which the package is delivered. The time period information includes, for example, a start time and an end time. The time period information includes, for example, a start time and duration information. The duration information is information that specifies the length of time.

[0061] The number of trips is the number of times a delivery van has made deliveries along a similar route. For example, the number of trips is the number of times a delivery van has made deliveries along a similar route within a predetermined period of time.

[0062] The travel time is information that indicates the time it takes to travel for delivery. For example, the travel time is "2 hours" or "10 hours."

[0063] The package attribute value is an attribute value of the package to be delivered, such as package type information that identifies the type of package and the package weight.

[0064] The vehicle attribute value is an attribute value of a delivery vehicle, such as the type of delivery vehicle (e.g., "large vehicle" or "small vehicle") or the maximum load capacity of the delivery vehicle (e.g., "10 tons" or "2 tons").

[0065] The project management unit 114 stores one or more pieces of project information. The project information in the project management unit 114 is usually associated with a project identifier. A project identifier is information that identifies a project. The project identifier is, for example, a project ID or project name.

[0066] The project information is information about a project. Here, the project is a joint delivery project. The project information includes project conditions.

[0067] Project conditions are the conditions for a project that is being constructed. A project specifies the scope in which joint delivery of cargo can be carried out. The project conditions include the organizational identifiers of the two or more organizations that make up the project. The project conditions include, for example, the organizational conditions of the proposing organization proposing joint delivery and the organizational conditions of one or more proposed organizations to which joint delivery is being proposed.

[0068] Organizational conditions are conditions for organizations participating in a project. Organizational conditions include an organizational identifier. The organizational identifier is an organizational identifier that includes a company identifier, or an organizational identifier that includes a company identifier and a department identifier. Organizational conditions include, for example, period information that specifies a period. Organizational conditions include, for example, shipping base information, receiving base information, and traveling time zone information. Organizational conditions include, for example, one or more pieces of condition attribute information. The one or more pieces of condition attribute information are, for example, type information indicating whether it is a return trip or a mixed load, delivery distance information, vehicle rank information, and vehicle attribute information.

[0069] The joint delivery management unit 115 stores one or more pieces of joint delivery information. The joint delivery information is associated with, for example, a joint delivery identifier. The joint delivery identifier is information that identifies the joint delivery information. The joint delivery identifier is, for example, an ID of the joint delivery information.

[0070] Joint delivery information is information that identifies a joint delivery. Joint delivery information is information that indicates that two or more delivery tasks are to be performed by joint delivery. Joint delivery information, for example, has a delivery task identifier for each of the two or more delivery tasks that are to be jointly delivered. Joint delivery information is, for example, link information to each of the two or more delivery tasks that are to be jointly delivered. Note that link information may also be considered to be a delivery task identifier.

[0071] The receiving unit 12 receives various information and instructions from the terminal device 2. The various information and instructions include, for example, delivery task information, project conditions, project approval information, proposal instructions, joint delivery approval information, and joint delivery instructions.

[0072] The delivery task receiving unit 121 receives delivery task information from each of two or more organizations. The delivery task receiving unit 121 receives delivery task information from the terminal device 2.

[0073] The condition receiving unit 122 receives project conditions having an organization identifier of an organization different from the organization identified by the one organization identifier. The condition receiving unit 122 receives project conditions from the terminal device 2. Note that the organization identified by the one organization identifier here is usually the organization proposing the project.

[0074] The project permission receiving unit 123 receives project permission information for the project conditions received by the condition receiving unit 122 from the organization identified by the organization identifier of the project conditions. Note that receiving from an organization means receiving from a terminal device 2 used by a user of the organization. This terminal device 2 is preferably a terminal of a user who belongs to the organization, but may also be a terminal of a user who has received a request from the organization.

[0075] The project permission information is information that indicates whether the construction of a project is permitted. The project permission information is, for example, "1" that indicates permission, or "0" that indicates no permission.

[0076] The proposal instruction receiving unit 124 receives a proposal instruction from the terminal device 2. A proposal instruction is an instruction to request a proposal for joint delivery. The proposal instruction corresponds to a delivery task identifier. The proposal instruction is an instruction to propose other delivery tasks that may be used for joint delivery for the delivery task identified by the delivery task identifier corresponding to the proposal instruction. The proposal instruction is usually also associated with a project identifier.

[0077] The joint delivery instruction receiving unit 125 receives a joint delivery instruction from the terminal device 2. A joint delivery instruction is an instruction for determining a task for performing joint delivery. A joint delivery instruction has, for example, two or more delivery task identifiers.

[0078] The joint delivery permission receiving unit 126 receives joint delivery permission information from the organization, which indicates permission to carry out the delivery task specified by the delivery task information by joint delivery. Receiving from the organization means receiving from the terminal device 2. This terminal device 2 is preferably a terminal of a user who belongs to the organization, but it may also be a terminal of a user who has received a request from the organization.

[0079] The processing unit 13 performs various processes, such as processes performed by a delivery task storage unit 131, a project registration unit 132, a delivery task selection unit 133, or a joint delivery registration unit 134.

[0080] The delivery task storage unit 131 stores the delivery task information received by the delivery task receiving unit 121 in the delivery task management unit 113 in association with a unique delivery task identifier.

[0081] The project registration unit 132 stores the project information including the project conditions received by the condition receiving unit 122 in the project management unit 114 in association with the unique project identifier.

[0082] When the project approval receiving unit 123 receives project approval information for the project conditions from organizations identified by one or more organization identifiers, excluding at least the organization identifier of the organization that transmitted the project conditions received by the condition receiving unit 122, among the two or more organization identifiers included in the project conditions, the project registration unit 132 determines that the project has been established, and stores the project information in the project management unit 114 in association with the project identifier. Note that storing the project information in the project management unit 114 in association with the project identifier as a determined project may also mean storing the project information of the established project in the project management unit 114. Storing the project information in the project management unit 114 in association with the project identifier as a determined project may also mean, for example, adding a project confirmation flag that is temporarily paired with the project information stored in the project management unit 114. Note that the project confirmation flag here is information that determines that the project has been established.

[0083] The delivery task selection unit 133 selects one or more pieces of delivery task information from the delivery task management unit 113 .

[0084] The delivery task selection unit 133 selects, from the delivery task management unit 113, delivery task information that satisfies the project conditions and joint delivery conditions of the project information accumulated by the project registration unit 132 and includes the organization identifier of an organization different from the organization identified by the one organization identifier, for delivery task information corresponding to a delivery task identifier paired with a single organization identifier. The delivery task selection unit 133 may select two or more delivery task information from the delivery task management unit 113. The joint delivery conditions are, for example, one or two of a consolidated loading condition or a return flight condition.

[0085] The delivery task selection unit 133 selects, for example, delivery task information identified by a delivery task identifier corresponding to the proposed instruction received by the proposed instruction receiving unit 124, from the delivery task management unit 113, delivery task information that satisfies the project conditions and joint delivery conditions contained in the project information.

[0086] It is preferable that the delivery task selection unit 133 does not select delivery task information that includes a luggage attribute value of luggage that cannot be mixed using luggage rules for the luggage attribute values ​​of delivery task information that corresponds to a delivery task identifier that pairs with an organization identifier.

[0087] The joint delivery registration unit 134 stores the joint delivery information in the joint delivery management unit 115. When joint delivery is confirmed, the joint delivery registration unit 134 stores the joint delivery information in the joint delivery management unit 115. The joint delivery information is information indicating that the delivery will be performed by joint delivery. The joint delivery information includes, for example, a delivery task identifier for each of two or more delivery tasks to be delivered jointly.

[0088] For example, when the joint delivery permission receiving unit 126 receives joint delivery permission information, the joint delivery registration unit 134 stores joint delivery information in the joint delivery management unit 115, which indicates that the delivery task specified by the delivery task information corresponding to the delivery task identifier paired with one organization identifier and the delivery task specified by the delivery task information selected by the delivery task selection unit 133 will be carried out by joint delivery.

[0089] The transmission unit 14 transmits various types of information to the terminal device 2. The various types of information are, for example, delivery task information.

[0090] The joint delivery transmission unit 141 transmits all or part of the delivery task information selected by the delivery task selection unit 133 to the terminal device 2.

[0091] The joint delivery sending unit 141 sends all or part of the delivery task information selected by the delivery task selecting unit 133 to an organization identified by the organization identifier included in the delivery task information. Sending to an organization means, for example, sending to a terminal device 2 of a user of the organization, or sending to a terminal device 2 of a user entrusted by the organization.

[0092] The joint delivery sending unit 141 preferably sends different information from the information contained in the delivery task information according to the relationship information that specifies the relationship between an organization identified by one organization identifier and another organization. Note that, for example, if the relationship between the two companies indicated by the relationship information is not a special relationship (for example, a group of companies), the joint delivery sending unit 141 will only send information up to the city, town, or village when sending the receiving base information and shipping base information of other companies to the terminal device 2 of each user of the two companies. On the other hand, if the relationship between the two companies indicated by the relationship information is a special relationship (for example, a group of companies), the joint delivery sending unit 141 will send all of the receiving base information and shipping base information (all of the address information) when sending the receiving base information and shipping base information of other companies to the terminal device 2 of each user of the two companies.

[0093] Various types of information are stored in the terminal storage unit 21 included in the terminal device 2. The various types of information include, for example, a user identifier and an organization identifier.

[0094] The terminal reception unit 22 receives various information and instructions, such as delivery task information, project conditions, project permission information, proposal instructions, and joint delivery permission information.

[0095] Here, reception is a concept that includes reception of information input from input devices such as a keyboard, mouse, or touch panel, reception of information transmitted via a wired or wireless communication line, and reception of information read from recording media such as an optical disk, magnetic disk, or semiconductor memory.

[0096] The means for inputting various information and instructions may be any means, such as a touch panel, keyboard, mouse, or menu screen.

[0097] The terminal processing unit 23 performs various types of processing. For example, the various types of processing are processing to convert received information, instructions, etc. into information, instructions, etc. with a structure to be transmitted. For example, the various types of processing are processing to convert received information into information with a structure to be output.

[0098] The terminal transmitting unit 24 transmits various information, instructions, etc. to the joint delivery support device 1. The various information, instructions, etc. are, for example, delivery task information, project conditions, project approval information, proposal instructions, and joint delivery approval information.

[0099] The terminal receiving unit 25 receives various types of information from the terminal 25. The various types of information include, for example, all or part of project information and all or part of delivery task information.

[0100] The terminal output unit 26 outputs various types of information. The various types of information include, for example, all or part of project information and all or part of delivery task information. Here, all or part of the delivery task information is, for example, all or part of the delivery task information for a delivery task to be jointly delivered.

[0101] In addition, output is a concept that includes displaying on a display, projection using a projector, printing on a printer, sound output, transmission to an external device, storage on a recording medium, and delivery of processing results to other processing devices or other programs.

[0102] The storage unit 11, the cargo rule management unit 111, the organizational relationship management unit 112, the delivery task management unit 113, the project management unit 114, the joint delivery management unit 115, and the terminal storage unit 21 are preferably non-volatile recording media, but can also be realized with volatile recording media.

[0103] There is no restriction on the process by which information is stored in the storage unit 11 etc. For example, information may be stored in the storage unit 11 etc. via a recording medium, information transmitted via a communication line etc. may be stored in the storage unit 11 etc., or information input via an input device may be stored in the storage unit 11 etc.

[0104] The receiving unit 12, delivery task receiving unit 121, condition receiving unit 122, project approval receiving unit 123, proposal instruction receiving unit 124, joint delivery approval receiving unit 126, and terminal receiving unit 25 are usually realized by wireless or wired communication means, but may also be realized by means of receiving broadcasts.

[0105] The processing unit 13, delivery task storage unit 131, project registration unit 132, delivery task selection unit 133, joint delivery registration unit 134, and terminal processing unit 23 can usually be realized by a processor, memory, etc. The processing procedures of the processing unit 13, etc. are usually realized by software, and the software is recorded on a recording medium such as a ROM. However, they may also be realized by hardware (dedicated circuit). The processor may be a CPU, MPU, GPU, etc., and the type is not important.

[0106] The transmitting unit 14, the joint delivery transmitting unit 141, and the terminal transmitting unit 24 are usually realized by wireless or wired communication means, but may also be realized by broadcasting means.

[0107] The terminal reception unit 22 can be realized by a device driver for an input means such as a touch panel or a keyboard, or control software for a menu screen.

[0108] The terminal output unit 26 may or may not include an output device such as a display, a speaker, etc. The terminal output unit 26 may be realized by driver software for an output device, or by a combination of driver software for an output device and the output device, etc.

[0109] Next, an example of the operation of the joint delivery support device 1 will be described with reference to the flowcharts of FIGS.

[0110] (Step S401) The delivery task receiving unit 121 determines whether or not delivery task information has been received from the terminal device 2. If delivery task information has been received, the process proceeds to step S402, and if not, the process proceeds to step S403. The received delivery task information is associated with an organization identifier.

[0111] (Step S402) The delivery task storage unit 131 stores the delivery task information received in step S401 in the delivery task management unit 113 in association with the organization identifier.

[0112] (Step S403) The condition receiving unit 122 determines whether or not the project conditions have been received from the terminal device 2. If the project conditions have been received, the process proceeds to step S404, and if not, the process proceeds to step S414.

[0113] (Step S404) The project registration unit 132 acquires a unique project identifier. The processing unit 13 composes project information having the project conditions received in step S403. The processing unit 13 stores the project information in the project management unit 114 in association with the acquired project identifier.

[0114] (Step S405) The processing unit 13 judges whether or not the project permission conditions are satisfied. If the project permission conditions are satisfied, the process proceeds to step S406, and if not, the process proceeds to step S408.

[0115] The project permission conditions are the conditions for obtaining permission to configure the project from the organizations participating in the project. The permission conditions are, for example, the organization identifiers that make up the project information, and the project permission flags that are paired with all organization identifiers except for the organization identifier that identifies the organization of the user who sent the project conditions must be "ON."

[0116] (Step S406) The processing unit 13 acquires, from the project information, one or more organization identifiers that constitute the project information, excluding the organization identifier that identifies the organization of the user who transmitted the project conditions. Here, it is preferable that the processing unit 13 acquires only the organization identifier that is paired with the project permission flag "ON."

[0117] (Step S407) The transmission unit 14 acquires a user identifier paired with each of the one or more organization identifiers acquired in step S406. Next, the transmission unit 14 transmits a project configuration consent instruction including project information to the user identified by the user identifier. Return to step S401. Sending to the user identified by the user identifier means, for example, sending to the contact indicated in the contact information paired with the user identifier.

[0118] (Step S408) The project registration unit 132 stores a project confirmation flag in association with the project information.

[0119] (Step S409) When the project is finalized, the processing unit 13 determines whether or not to propose joint delivery. If joint delivery is proposed, the processing unit 13 proceeds to step S410, and if joint delivery is not proposed, the processing unit 13 returns to step S401.

[0120] For example, whether or not to propose joint delivery is determined in advance when the project is finalized. Also, for example, the processing unit 13 determines to propose joint delivery when the immediate proposal flag of the received project conditions is "ON."

[0121] (Step S410) The delivery task selection unit 133 and the like perform a joint delivery proposal process. An example of the joint delivery proposal process will be described with reference to the flowchart in FIG.

[0122] (Step S411) The project permission receiving unit 123 determines whether or not project permission information has been received from the terminal device 2. If project permission information has been received, the process proceeds to step S412; if not, the process proceeds to step S414. The project permission information is associated with a project identifier and an organization identifier.

[0123] (Step S412) The processing unit 13 stores the project permission information in association with the project identifier and the organization identifier.

[0124] (Step S413) The processing unit 13 determines whether or not the project identified by the project identifier has been established. If the project has been established, the processing unit 13 proceeds to step S408, and if the project has not been established, the processing unit 13 returns to step S401.

[0125] In addition, the processing unit 13 determines that the project has been established when, for example, the project approval information is stored in pair with one or more organization identifiers that are paired with the project identifier, and is one or more organization identifiers of all organizations to which the project configuration approval instruction was sent.

[0126] (Step S414) The receiving unit 12 determines whether or not a delivery task output instruction has been received from the terminal device 2. If a delivery task output instruction has been received, the process proceeds to step S415; if not, the process proceeds to step S420. The delivery task output instruction may include search conditions for narrowing down the delivery tasks. The search conditions are, for example, conditions related to one or more of the following information: shipping base information, receiving base information, travel time zone information, type information indicating whether the delivery is a return delivery or a consolidated delivery, delivery distance information, vehicle class information, and vehicle attribute information.

[0127] (Step S415) The processing unit 13 acquires the project identifier included in the delivery task output instruction.

[0128] (Step S416) The processing unit 13 acquires from the project management unit 114 the project conditions that are paired with the project identifier included in the delivery task output instruction.

[0129] (Step S417) The processing unit 13 acquires the organization identifier included in the delivery task output instruction.

[0130] (Step S418) The processing unit 13 obtains one or more pieces of delivery task information that are paired with the organization identifier and satisfy the project conditions from the delivery task management unit 113. Note that here, the processing unit 13 may obtain only a portion of the information that constitutes the delivery task information. The portion of the information may also be called delivery task information.

[0131] (Step S419) The transmitting unit 14 transmits the one or more pieces of delivery task information acquired in step S418 to the terminal device 2 that has transmitted the delivery task output instruction. Return to step S401.

[0132] (Step S420) The proposal instruction receiving unit 124 determines whether or not a proposal instruction has been received from the terminal device 2. If a proposal instruction has been received, the process proceeds to step S421, and if not, the process proceeds to step S425.

[0133] (Step S421) The delivery task selection unit 133 acquires the project identifier included in the proposed instruction.

[0134] (Step S422) The delivery task selection unit 133 acquires from the project management unit 114 the project conditions that are paired with the project identifier.

[0135] (Step S423) The delivery task selection unit 133 acquires the delivery task identifier included in the proposed instruction.

[0136] (Step S424) The delivery task selection unit 133 acquires delivery task information of other organizations that satisfies the project conditions and joint delivery conditions for the delivery task information identified by the delivery task identifier acquired in step S423 from the delivery task management unit 113. An example of such single-task joint proposal processing will be described using the flowchart in FIG.

[0137] (Step S425) The joint delivery instruction receiving unit 125 determines whether or not a joint delivery instruction has been received from the terminal device 2. If a joint delivery instruction has been received, the process proceeds to step S426, and if not, the process proceeds to step S431.

[0138] (Step S426) The processing unit 13 acquires from the delivery task management unit 113 delivery task information identified by each of two or more delivery task identifiers included in the joint delivery instruction.

[0139] (Step S427) The processing unit 13 judges whether or not the joint delivery permission conditions are satisfied. If the joint delivery permission conditions are satisfied, the process proceeds to step S428, and if not, the process proceeds to step S430.

[0140] The joint delivery permission conditions are conditions for obtaining permission for joint delivery from an organization other than the organization of the user who sent the joint delivery instruction. For example, the joint delivery permission conditions are that the joint delivery permission flag paired with the organization identifier of the organization other than the organization of the user who sent the proposal instruction is "ON."

[0141] (Step S428) The processing unit 13 acquires the organization identifiers of one or more organizations other than the organization of the user who has sent the joint delivery instruction.

[0142] (Step S429) The sending unit 14 acquires a user identifier paired with one or more organization identifiers from the organization management unit 110. The sending unit 14 sends a joint delivery permission instruction to the users identified by the one or more user identifiers. Return to step S401. The joint delivery permission instruction includes, for example, two or more pieces of delivery task information acquired in step S426.

[0143] (Step S430) The joint delivery registration unit 134 stores the joint delivery information in the joint delivery management unit 115. The process returns to step S401.

[0144] The joint delivery information includes, for example, delivery task identifiers of two or more pieces of delivery task information, or two or more pieces of delivery task information.

[0145] (Step S431) The joint delivery permission receiving unit 126 determines whether or not joint delivery permission information has been received from the terminal device 2. If joint delivery permission information has been received, the process proceeds to step S432, and if not, the process returns to step S401.

[0146] (Step S432) The joint delivery registration unit 134 stores the joint delivery permission information.

[0147] (Step S433) The joint delivery registration unit 134 determines whether or not the joint delivery has been established. If the joint delivery has been established, the process proceeds to step S430, and if the joint delivery has not been established, the process returns to step S401.

[0148] The joint delivery registration unit 134 determines that the joint delivery has been established, for example, when the joint delivery permission information has been received and stored from all users of one or more organizations that have sent joint delivery permission instructions. The establishment of the joint delivery also means that the joint delivery information has been stored in the joint delivery management unit 115, and that the joint delivery will be realized in the future. Furthermore, if the delivery task output instruction has a search condition for narrowing down the delivery tasks, the processing unit 13 acquires from the delivery task management unit 113 one or more pieces of delivery task information that also satisfy the search condition.

[0149] Furthermore, in the flowcharts of FIGS. 4 and 5, the processing ends when the power is turned off or an interrupt occurs to end the processing.

[0150] Next, an example of the joint delivery proposal process in step S410 will be described with reference to the flowchart in FIG.

[0151] (Step S601) The delivery task selection unit 133 acquires the received project conditions.

[0152] (Step S602) The delivery task selection unit 133 acquires an organization identifier included in the project conditions acquired in step S601. This organization identifier is the organization identifier of the organization to which the user who has transmitted the project conditions belongs.

[0153] (Step S603) The delivery task selection unit 133 obtains from the delivery task management unit 113 one or more pieces of delivery task information that are paired with the organization identifier obtained in step S602 and that satisfy the project conditions obtained in step S601.

[0154] (Step S604) The delivery task selection unit 133 assigns 1 to the counter i.

[0155] (Step S605) The delivery task selection unit 133 determines whether or not the i-th delivery task information exists among the delivery task information acquired in step S603. If the i-th delivery task information exists, the process proceeds to step S606; if not, the process returns to the upper level process.

[0156] (Step S606) The delivery task selection unit 133 acquires one or more pieces of delivery task information of other organizations, which are one or more pieces of delivery task information corresponding to the i-th delivery task information. An example of such a single-task joint proposal process will be described using the flowchart in FIG. 7. The other organizations here are organizations other than the organization identified by the organization identifier in the i-th delivery task information. The other organizations are also organizations identified by the organization identifier in the project conditions.

[0157] (Step S607) The delivery task selection unit 133 increments the counter i by 1. The process returns to step S605.

[0158] Next, an example of the single-task joint proposal process in step S424 will be described with reference to the flowchart of FIG.

[0159] (Step S701) The delivery task selection unit 133 acquires first delivery task information. The first delivery task information is the i-th delivery task information in step S605 or the delivery task information identified by the delivery task identifier in step S523.

[0160] (Step S702) The delivery task selection unit 133 assigns 1 to the counter i.

[0161] (Step S703) The delivery task selection unit 133 acquires the project conditions of the target project. The delivery task selection unit 133 determines whether or not there is an i-th organization identifier included in the project conditions, other than the organization identifier included in the first delivery task information. If the i-th organization identifier exists, the process proceeds to step S704; if not, the process proceeds to step S713.

[0162] (Step S704) The delivery task selection unit 133 acquires another i-th organization identifier from the project conditions.

[0163] (Step S705) The delivery task selection unit 133 acquires, from the delivery task management unit 113, one or more pieces of delivery task information paired with the i-th organization identifier.

[0164] (Step S706) The delivery task selection unit 133 assigns 1 to the counter j.

[0165] (Step S707) The delivery task selection unit 133 determines whether the j-th delivery task information exists in the one or more pieces of delivery task information acquired in step S705. If the j-th delivery task information exists, the process proceeds to step S708; if not, the process proceeds to step S712.

[0166] (Step S708) The delivery task selection unit 133 acquires second delivery task information, which is the j-th delivery task information.

[0167] (Step S709) The delivery task selection unit 133 determines whether the first delivery task information and the second delivery task information satisfy the joint delivery conditions. If the joint delivery conditions are satisfied, the process proceeds to step S710; if not, the process proceeds to step S711. Here, the joint delivery conditions are, for example, the consolidated loading conditions or return flight conditions included in the project conditions. Also, here, if the project conditions do not have consolidated loading conditions or return flight conditions, the joint delivery conditions here are, for example, "consolidated loading conditions OR return flight conditions."

[0168] (Step S710) The joint delivery registration unit 134 associates the first delivery task information with the second delivery task information. That is, the joint delivery registration unit 134 composes the joint delivery information and stores it in a buffer (not shown). The joint delivery information is, for example, first delivery task information and second delivery task information. The joint delivery information is, for example, a first delivery task identifier and a second delivery task identifier.

[0169] (Step S711) The delivery task selection unit 133 increments the counter j by 1. The process returns to step S707.

[0170] (Step S712) The delivery task selection unit 133 increments the counter i by 1. The process returns to step S703.

[0171] (Step S713) The joint delivery sending unit 141 sends one or more pieces of joint delivery information stored in a buffer (not shown) to the terminal device 2. The process returns to the upper level processing. The joint delivery information is information indicating the correspondence between the delivery task information of each of two or more delivery tasks to be jointly delivered.

[0172] Next, an example of the operation of the terminal device 2 will be described with reference to the flowcharts of FIGS.

[0173] (Step S801) The terminal reception unit 22 determines whether or not delivery task information has been received from the user. If delivery task information has been received, the process proceeds to step S802, and if not, the process proceeds to step S803.

[0174] (Step S802) The terminal processing unit 23 acquires an organization identifier or a user identifier from the terminal storage unit 21. The terminal transmission unit 24 associates the delivery task information with the organization identifier or the user identifier and transmits the delivery task information to the joint delivery support device 1. Return to step S801.

[0175] (Step S803) The terminal reception unit 22 determines whether or not the project conditions have been received from the user. If the project conditions have been received, the process proceeds to step S804, and if not, the process proceeds to step S805.

[0176] (Step S804) The terminal processing unit 23 acquires the organization identifier or the user identifier from the terminal storage unit 21. The terminal transmission unit 24 associates the project conditions with the organization identifier or the user identifier and transmits them to the joint delivery support device 1. Return to step S801.

[0177] (Step S805) The terminal receiving unit 25 determines whether or not a project configuration permission instruction has been received from the joint delivery support device 1. If a project configuration permission instruction has been received, the process proceeds to step S821; if not, the process returns to step S801.

[0178] (Step S806) The terminal processing unit 23 composes a project configuration permission instruction to be output. The terminal output unit 26 outputs the project configuration permission instruction. The project configuration permission instruction includes, for example, the project configuration of the project to be permitted.

[0179] (Step S807) The terminal acceptance unit 22 determines whether or not project permission information has been accepted from the user. If project permission information has been accepted, the process proceeds to step S808; if not, the process proceeds to step S809.

[0180] Here, the terminal receiving unit 22 may receive project non-permission information from the user. The project non-permission information is information indicating that the project is not permitted. When the project non-permission information is received, the terminal transmitting unit 24 transmits the project non-permission information to the joint delivery support device 1. As a result, the project is not constructed.

[0181] (Step S808) The terminal processing unit 23 acquires the organization identifier or the user identifier from the terminal storage unit 21. The terminal transmission unit 24 associates the project permission information with the organization identifier or the user identifier and transmits the project permission information to the joint delivery support device 1. Return to step S801.

[0182] (Step S809) The terminal processing unit 23 determines whether or not a timeout has occurred. If a timeout has occurred, the process returns to step S801, and if not, the process returns to step S807.

[0183] (Step S810) The terminal reception unit 22 determines whether or not a delivery task output instruction has been received from the user. If a delivery task output instruction has been received, the process proceeds to step S811, and if not, the process proceeds to step S814.

[0184] (Step S811) The terminal processing unit 23 acquires an organization identifier or a user identifier from the terminal storage unit 21. The terminal transmission unit 24 transmits a delivery task output instruction to the joint delivery support device 1 in association with the organization identifier or the user identifier.

[0185] (Step S812) The terminal receiving unit 25 determines whether or not one or more pieces of delivery task information have been received from the joint delivery support device 1. If delivery task information has been received, the process proceeds to step S813; if not, the process returns to step S812.

[0186] (Step S813) The terminal processing unit 23 composes one or more pieces of delivery task information to be output. The terminal output unit 26 outputs the delivery task information. Return to step S801.

[0187] (Step S814) The terminal reception unit 22 determines whether or not a proposal instruction has been received from the user. If a proposal instruction has been received, the process proceeds to step S815; if not, the process proceeds to step S818. The proposal instruction includes, for example, a delivery task identifier.

[0188] (Step S815) The terminal processing unit 23 acquires the organization identifier or the user identifier from the terminal storage unit 21. The terminal transmission unit 24 transmits a proposal instruction to the joint delivery support device 1 in association with the organization identifier or the user identifier.

[0189] (Step S816) The terminal receiving unit 25 determines whether or not one or more pieces of joint delivery information have been received from the joint delivery support device 1. If joint delivery information has been received, the process proceeds to step S817; if not, the process returns to step S816.

[0190] (Step S817) The terminal processing unit 23 composes one or more pieces of joint delivery information to be output. The terminal output unit 26 outputs the joint delivery information. Return to step S801. The joint delivery information here is delivery task information for each of two or more delivery tasks that are the subject of joint delivery.

[0191] (Step S818) The terminal reception unit 22 determines whether or not a joint delivery instruction has been received from the user. If a joint delivery instruction has been received, the process proceeds to step S815; if not, the process proceeds to step S818.

[0192] The joint delivery instruction includes, for example, delivery task identifiers for two or more delivery tasks that are the subject of the joint delivery.

[0193] (Step S819) The terminal processing unit 23 acquires the organization identifier or the user identifier from the terminal storage unit 21. The terminal transmission unit 24 associates the organization identifier or the user identifier with the joint delivery instruction and transmits it to the joint delivery support device 1. Return to step S801.

[0194] (Step S820) The terminal receiving unit 25 determines whether or not a joint delivery permission instruction has been received from the joint delivery support device 1. If a joint delivery permission instruction has been received, the process proceeds to step S821, and if not, the process returns to step S801.

[0195] (Step S821) The terminal processing unit 23 composes a joint delivery permission instruction to be output, and the terminal output unit 26 outputs the joint delivery permission instruction.

[0196] (Step S822) The terminal reception unit 22 determines whether or not joint delivery permission information has been received from the user. If joint delivery permission information has been received, the process proceeds to step S823; if not, the process proceeds to step S824. The joint delivery permission information includes, for example, a project identifier and two or more delivery task identifiers that are the subject of joint delivery.

[0197] Here, the terminal receiving unit 22 may receive joint delivery non-permission information from the user. Joint delivery non-permission information is information indicating that the joint delivery is not permitted. When joint delivery non-permission information is received, the terminal transmitting unit 24 transmits the joint delivery non-permission information to the joint delivery support device 1. As a result, the joint delivery information for the joint delivery is not registered, and the joint delivery is not realized.

[0198] (Step S823) The terminal processing unit 23 acquires the organization identifier or the user identifier from the terminal storage unit 21. The terminal transmission unit 24 associates the joint delivery consent information with the organization identifier or the user identifier and transmits it to the joint delivery support device 1. Return to step S801.

[0199] (Step S824) The terminal processing unit 23 determines whether or not a timeout has occurred. If a timeout has occurred, the process returns to step S801, and if not, the process returns to step S822.

[0200] In the flowcharts of FIGS. 8 and 9, the processing ends when the power is turned off or an interrupt occurs to end the processing.

[0201] A specific example of the operation of the information system A in this embodiment will be described below.

[0202] The organization management unit 110 of the joint delivery support device 1 stores the organization management table shown in FIG. 10. The organization management table is a table that manages information about one or more organizations. The organization management table manages one or more records that have "ID" and "organization information." The "organization information" has an "organization identifier," "organization attribute value," "user information," "project permission flag," "joint delivery permission flag," and "immediate proposal flag." The "organization identifier" has a "company name" and a "department name." The "organization attribute value" has an "address." The "user information" has a "user identifier" and a "contact information."

[0203] The cargo rule management unit 111 stores a cargo rule management table shown in FIG. 11. The cargo rule management table is a table for managing one or more cargo rules. The cargo rules here are conditions for two or more cargo items that cannot be mixed (non-mixing rules). The non-mixing rule for "ID=1" indicates that beverages and frozen foods cannot be mixed. The non-mixing rule for "ID=2" indicates that product A and product B cannot be mixed. The non-mixing rule for "ID=3" indicates that medicines and product C cannot be mixed.

[0204] Also, assume that the organizational relationship management unit 112 stores the organizational relationship "Test1 Co., Ltd., Test3 Co., Ltd." Here, it is assumed that the organizational relationship management unit 112 stores two or more organizational identifiers (here, company names) for which all information may be made public. In other words, the organizational relationship information "Test1 Co., Ltd., Test3 Co., Ltd." indicates that "Test1 Co., Ltd." and "Test3 Co., Ltd." are group companies and can mutually view all information contained in the delivery task information. On the other hand, since "Test1 Co., Ltd., Test2 Co., Ltd." are not stored in the organizational relationship management unit 112, when a user of "Test1 Co., Ltd." views the delivery task information of "Test2 Co., Ltd.", only a portion of the information can be seen, and when a user of "Test2 Co., Ltd." views the delivery task information of "Test1 Co., Ltd.", only a portion of the information can be seen. Here, the portion of information is, for example, a portion of the shipping base information (address) (including prefecture and city / town / village) contained in the delivery task information, and a portion of the receiving base information (address) (including prefecture and city / town / village) contained in the delivery task information.

[0205] The delivery task management unit 113 stores a delivery task management table having the structure shown in Figure 12. The delivery task management table is a table that manages one or more pieces of delivery task information. The delivery task management table is a table that manages one or more records that have an "ID," "delivery task identifier," "organization identifier," "shipping base information," "receiving base information," "time period information," "baggage attributes," "vehicle attributes," and "number of trips." The "organization identifier" has a "company name" and a "department name." The "time period information" has a "shipping time" and a "receiving time." The "baggage attributes" have a "baggage type" and a "baggage amount." The "vehicle attributes" have a "vehicle type" and a "vehicle load capacity."

[0206] The project management unit 114 stores a project management table having the structure shown in FIG. 13. A project management table is a table that manages information on one or more projects. The project management table includes an "ID," a "project identifier," a "project name," and "project conditions." The "project conditions" include an "organization condition" and a "period condition." The "organization condition" includes an "organization name" and a "department name." The "period condition" is a condition that specifies the period of the project.

[0207] The joint delivery management unit 115 stores a joint delivery management table having the structure shown in Fig. 14. The joint delivery management table has an "ID," a "joint delivery identifier," and "joint delivery information." The "joint delivery information" is the delivery task identifier of each of two or more delivery tasks that are to be jointly delivered.

[0208] In the above situation, the following three specific examples will be described. Specific Example 1 is an example of registering a project. Specific Example 2 is an example of using project information to determine delivery tasks of other companies to perform joint delivery for one delivery task. Specific Example 3 is an example of using project information to determine, for each of two or more delivery tasks of one company participating in the project indicated by the project information, delivery tasks that satisfy project conditions and joint delivery conditions for selecting them as possible joint delivery tasks from among the delivery tasks of other companies, and to determine delivery tasks to perform joint delivery from among the delivery tasks that satisfy the project conditions and the joint delivery conditions.

[0209] (Example 1) It is assumed that the user displays the project registration screen (FIG. 15) on the terminal device 2, inputs project information, and selects the “Register” button 1501. The terminal device 2 then accepts the project information and transmits the project information including the project conditions to the joint delivery support device 1.

[0210] Next, the condition receiving unit 122 of the joint delivery support device 1 receives project information including the project conditions from the terminal device 2. The project registration unit 132 generates a unique project identifier "P01." Note that the project identifier here is "P" + a "unique numeric value." The project registration unit 132 also composes project information including the received project conditions. The project registration unit 132 associates the composed project information with the project identifier "P01" and stores it in the project management unit 114. This project information is the record with "ID=1" in the project management table (FIG. 13).

[0211] According to the organization management table (FIG. 10), the project permission flag paired with "Test2 Co., Ltd." is "0," so the project information was registered without obtaining permission from "Test2 Co., Ltd."

[0212] (Example 2) It is assumed that a user with an organization identifier "Test 1 Co., Ltd." inputs a delivery task output instruction having a project name "Project A" into the terminal device 2. Next, the terminal device 2 accepts the delivery task output instruction including the organization identifier "Test 1 Co., Ltd." and the project name "Project A," and transmits the delivery task output instruction to the joint delivery support device 1.

[0213] Next, the receiving unit 12 of the joint delivery support device 1 receives the delivery task output instruction from the terminal device 2. Then, the processing unit 13 acquires the project identifier "P01" that pairs with the project name "Project A" included in the delivery task output instruction from the project management table (FIG. 13). Next, the processing unit 13 acquires the project conditions that pair with the project identifier "P01" from the project management table (FIG. 13). The processing unit 13 also acquires the organization identifier "Test 1 Co., Ltd." included in the delivery task output instruction. Next, the processing unit 13 acquires one or more pieces of delivery task information (delivery task information of Test 1 Co., Ltd.) that pairs with the organization identifier "Test 1 Co., Ltd." and satisfies the acquired project conditions from the delivery task management table (FIG. 12). Next, the transmitting unit 14 transmits the one or more pieces of delivery task information to the terminal device 2 that has transmitted the delivery task output instruction. Note that the one or more pieces of delivery task information are transmitted in association with the project identifier "P01."

[0214] Next, the terminal device 2 receives and outputs the delivery task information. An example of such output is shown in FIG. 16. In FIG. 16, the records (rows) in the range 1601 are the transmitted delivery task information. Also, each transmitted delivery task information is associated with a delivery task identifier. Also, the screen information for configuring the screen of FIG. 16 has a project identifier "P01".

[0215] Next, suppose that the user instructs delivery task 1602 on the screen of Fig. 16. Then, the terminal device 2 acquires a delivery task identifier "T13" that identifies delivery task 1602 on the screen. Next, the terminal device 2 composes a proposed instruction having a project identifier "P01" and a delivery task identifier "T13" and transmits it to the joint delivery support device 1.

[0216] Next, the proposed instruction receiving unit 124 of the joint delivery support device 1 receives the proposed instruction from the terminal device 2. Next, the delivery task selecting unit 133 acquires the project identifier "P01" included in the proposed instruction. Next, the delivery task selecting unit 133 acquires the project conditions paired with the project identifier "P01" from the project management table (FIG. 13). The delivery task selecting unit 133 also acquires the delivery task identifier "T13" included in the proposed instruction. Next, the delivery task selecting unit 133 acquires delivery task information that satisfies the project conditions for the delivery task information identified by the delivery task identifier "T13" and that corresponds to the organization identifier "<Company Name> Test 2 <Department Name> Q Factory" of another organization from the delivery task management table (FIG. 12). Furthermore, the task selecting unit 133 selects delivery task information that satisfies the joint delivery conditions (here, return trip conditions) for the delivery task information with the delivery task identifier "T13" from the acquired delivery task information. It is assumed here that the delivery task selection unit 133 selects and acquires delivery task information including the delivery task identifier “T21” of the record with “ID=87” in the delivery task management table (FIG. 12). Next, the transmission unit 14 transmits the delivery task information including the delivery task identifier “T21” to the terminal device 2.

[0217] The joint delivery registration unit 134 also acquires a unique joint delivery identifier "JD01." The joint delivery registration unit 134 also creates joint delivery information having a delivery task identifier "T13" and a delivery task identifier "T21," and stores this joint delivery information in the joint delivery management table (FIG. 14) in pairs with the joint delivery identifier "JD01." This record is the record with "ID=1" in the joint delivery management table (FIG. 14).

[0218] Next, the terminal device 2 receives delivery task information including the delivery task identifier "T21" from the joint delivery support device 1. Then, the terminal device 2 outputs second delivery task information including the delivery task identifier "T21". An output example of delivery task information including the delivery task identifier "T21" is shown in 1701 in FIG. 17. In FIG. 17, the terminal device 2 outputs first delivery task information identified by the delivery task identifier "T13" included in the proposed instruction, in a format aligned with the delivery task information of 1701 (1702). In addition, a line connecting the shipping base and the receiving base is obtained from the shipping base information (address) and the receiving base information (address) of each of the first delivery task information and the second delivery task information, and the line is displayed on a map (1703, 1704).

[0219] (Example 3) It is assumed that a user "U41" of a company named "Company X" inputs project conditions into the terminal device 2. Next, the terminal device 2 receives the project information and transmits it to the joint delivery support device 1.

[0220] Next, the condition receiving unit 122 of the joint delivery support device 1 receives the project conditions from the terminal device 2. The project registration unit 132 generates a unique project identifier "P02." The project registration unit 132 creates project information having the received project conditions. The project registration unit 132 associates the project information with the acquired project identifier "P02" and stores it in the project management unit 114. This project information is the record with "ID=2" in the project management table (FIG. 13).

[0221] Next, the processing unit 13 acquires the organization identifier "Company X,XXX..." contained in the received project information. Next, the processing unit 13 acquires the immediate proposal flag "1" that pairs with the organization identifier. Then, the processing unit 13 determines that joint delivery will be proposed once the project is finalized. Note that the immediate proposal condition here is that the immediate proposal flag of the organization is "ON (1)".

[0222] Next, the delivery task selection unit 133 etc. performs the joint delivery proposal process described using the flowchart in Fig. 6. As a result, for each of two or more pieces of delivery task information with organization identifiers "Company X,XXX...", which are delivery task information that satisfies the project conditions paired with the project identifier "P02", the delivery task information of other companies' delivery tasks that can be jointly delivered for the delivery task specified by the delivery task information is selected from the delivery task management table (Fig. 12).

[0223] Next, the delivery task selection unit 133 acquires the number of candidates for joint delivery for each of two or more pieces of delivery task information with the organization identifier "Company X, XXX...".

[0224] Then, the processing unit 13 creates a screen including two or more pieces of delivery task information with the organization identifier "Company X, XXX..." and the number of candidates for joint delivery associated with the delivery task information. Next, the transmission unit 14 transmits the screen to the terminal device 2.

[0225] The terminal device 2 receives the screen information, composes the screen, and outputs it. An example of such a screen is shown in Figure 18. In Figure 18, 1801, 1802, etc. indicate the number of candidate delivery tasks for joint delivery by other companies for each delivery task of the organization identified by the organization identifier "Company X,XXX...".

[0226] Here, let us say that the user selects 1803, for example. Then, delivery task information of candidate delivery tasks from other companies for the delivery task of 1803 is output. An example of output of such delivery task information is shown in FIG. 19. In FIG. 19, 1901 is a delivery task with the organization identifier "Company X,XXX...", and 1902 and 1903 are two delivery tasks from other companies, which are candidate delivery tasks for joint delivery.

[0227] 19, the user then enters a check mark 1904 and selects the register button 1905. The terminal device 2 then receives a joint delivery instruction to jointly deliver the delivery tasks 1901 and 1902. The joint delivery instruction here has a delivery task identifier "T89" that identifies the delivery task 1901, and a delivery task identifier "T201" that identifies the delivery task 1902. The terminal transmitting unit 24 then transmits the joint delivery instruction "T89, T201" to the joint delivery support device 1.

[0228] Next, the joint delivery instruction receiving unit 125 of the joint delivery support device 1 receives the joint delivery instruction from the terminal device 2. Next, the joint delivery registration unit 134 generates a unique joint delivery identifier "JD03". Next, the joint delivery registration unit 134 pairs the joint delivery information with the joint delivery identifier "JD03" and stores it in the joint delivery management unit 115. This joint delivery information is the record "ID=3" in the joint delivery management table (FIG. 14).

[0229] As described above, according to this embodiment, by configuring a project for joint delivery and selecting delivery tasks that satisfy the project conditions and joint delivery conditions of the project, the joint delivery desired by the user can be efficiently realized.

[0230] Furthermore, according to this embodiment, it is possible to propose a joint delivery in response to a proposal instruction from the user.

[0231] Furthermore, according to this embodiment, a joint delivery project that is approved by all parties involved can be realized.

[0232] Furthermore, according to this embodiment, only joint deliveries that are approved by all parties involved can be carried out.

[0233] Furthermore, according to this embodiment, it is possible to manage information on delivery tasks for candidates for joint delivery.

[0234] Furthermore, according to this embodiment, joint delivery can be efficiently realized by taking into consideration appropriate mixed loading of cargo.

[0235] Furthermore, according to this embodiment, appropriate information according to the relationship between the organizations can be presented to each organization, and joint delivery can be efficiently realized.

[0236] The processing in this embodiment may be realized by software. This software may be distributed by software download or the like. This software may also be recorded on a recording medium such as a CD-ROM and distributed. This also applies to other embodiments in this specification. The software that realizes the joint delivery support device 1 in this embodiment is the following program. That is, this program includes a computer that can access a project management unit that has project conditions, which are conditions for a joint delivery of parcels and have two or more organization identifiers, and that stores project information, which is information corresponding to the project identifier that identifies the project, and a delivery task management unit that stores two or more delivery task information, which is corresponding to a delivery task identifier that identifies a delivery task and has an organization identifier that identifies the organization of the delivery task, receiving base information, shipping base information, and running time zone information, a condition receiving unit that receives project conditions having an organization identifier of an organization different from the organization identified by one organization identifier, and a program that receives the project conditions received by the condition receiving unit. a delivery task selection unit that selects, from the delivery task management unit, delivery task information that satisfies the project conditions of the project information stored by the project registration unit and joint delivery conditions that are conditions for joint delivery, for delivery task information corresponding to a delivery task identifier paired with the one organization identifier, and that includes an organization identifier of an organization different from the organization identified by the one organization identifier; and a joint delivery transmission unit that transmits all or a part of the delivery task information selected by the delivery task selection unit.

[0237] FIG. 20 is a block diagram of a computer system 300 that executes the programs described in this specification to realize the combined delivery support device 1 and the like according to the various embodiments described above.

[0238] In FIG. 20, a computer system 300 includes a computer 301 including a CD-ROM drive, a keyboard 302, a mouse 303, and a monitor 304.

[0239] 20, computer 301 includes, in addition to CD-ROM drive 3012, MPU 3013, bus 3014 connected to CD-ROM drive 3012 etc., ROM 3015 for storing programs such as a boot-up program, RAM 3016 connected to MPU 3013 for temporarily storing instructions of application programs and providing temporary storage space, and hard disk 3017 for storing application programs, system programs, and data. Although not shown here, computer 301 may further include a network card for providing connection to a LAN.

[0240] A program that causes the computer system 300 to execute the functions of the combined delivery support device 1 and the like of the above-described embodiment may be stored on a CD-ROM 3101, inserted into the CD-ROM drive 3012, and then transferred to the hard disk 3017. Alternatively, the program may be transmitted to the computer 301 via a network (not shown) and stored on the hard disk 3017. The program is loaded into the RAM 3016 when executed. The program may also be loaded directly from the CD-ROM 3101 or the network.

[0241] The program does not necessarily include an operating system (OS) or a third-party program that causes the computer 301 to execute the functions of the combined delivery support device 1 of the above-described embodiment. The program need only include instructions that call appropriate functions (modules) in a controlled manner to achieve the desired results. How the computer system 300 operates is well known, and a detailed description thereof will be omitted.

[0242] In addition, in the above program, the steps of transmitting information and receiving information do not include processing performed by hardware, such as processing performed by a modem or interface card in the transmission step (processing that can only be performed by hardware).

[0243] The computer that executes the program may be a single computer or a plurality of computers, that is, it may perform centralized processing or distributed processing.

[0244] Furthermore, in each of the above embodiments, it goes without saying that two or more communication means present in one device may be physically realized by one medium.

[0245] Furthermore, in each of the above embodiments, each process may be realized by centralized processing in a single device, or may be realized by distributed processing in a plurality of devices.

[0246] The present invention is not limited to the above-described embodiment, and various modifications are possible, and it goes without saying that these modifications are also included within the scope of the present invention. [Industrial Applicability]

[0247] As described above, the joint delivery support device 1 of the present invention can configure a project for joint delivery and carry out joint delivery that satisfies the project conditions and joint delivery conditions of the project, thereby having the effect of efficiently realizing the joint delivery desired by the user, and is useful as a server, etc. that supports joint delivery. [Explanation of symbols]

[0248] A. Information Systems 1 Joint delivery support device 2. Terminal Device 11 Storage area 12 Receiving unit 13 Processing section 14 Transmitter 21 Terminal storage section 22 Terminal Reception 23 Terminal processing section 24 Terminal transmitter 25 Terminal receiving section 26 Terminal Output Unit 110 Organization Management Department 111 Luggage Rules Management Department 112 Organizational Relations Management Department 113 Delivery Task Management Department 114 Project Management Department 115 Joint Delivery Management Department 121 Delivery task receiving unit 122 Condition Receiving Unit 123 Project Permission Receiving Department 124 Proposal Instruction Receiving Unit 125 Joint Delivery Instruction Receiving Department 126 Joint Delivery Permission Receiving Department 131 Delivery task storage unit 132 Project Registration Department 133 Delivery task selection section 133 Task Selection Section 134 Joint Delivery Registration Department 141 Joint Delivery Transmission Department

Claims

1. a condition receiving unit that receives project conditions having an organization identifier of an organization different from the organization identified by the one organization identifier; a project registration unit that stores project information, which is information associated with a project identifier that identifies a project, in a project management unit that stores project conditions, which are conditions for a joint delivery of goods and have two or more organization identifiers, and the project information includes the project conditions received by the condition receiving unit, in association with the project identifier; a delivery task selection unit that selects, from a delivery task management unit that stores two or more delivery task information items that correspond to delivery task identifiers and have an organization identifier that identifies the organization of the delivery task, receiving base information, shipping base information, and running time zone information, delivery task information that satisfies the project conditions of the project information stored by the project registration unit and joint delivery conditions that are conditions for joint delivery, for delivery task information that corresponds to a delivery task identifier that pairs with the one organization identifier, and that includes an organization identifier of an organization other than the organization identified by the one organization identifier; a joint delivery transmitting unit that transmits all or part of the delivery task information selected by the delivery task selecting unit.

2. a proposal instruction receiving unit for receiving a proposal instruction for joint delivery, the proposal instruction being associated with a delivery task identifier; The delivery task selection unit 2. The joint delivery support device according to claim 1, wherein the delivery task management unit selects, from the delivery task information identified by the delivery task identifier corresponding to the proposed instruction received by the proposed instruction receiving unit, delivery task information that satisfies the project conditions contained in the project information and the joint delivery conditions.

3. a project permission receiving unit that receives project permission information indicating permission for the project conditions received by the condition receiving unit from an organization identified by the organization identifier included in the project conditions; The project registration unit 2. The joint delivery support device according to claim 1, wherein when the project approval receiving unit receives project approval information for the project conditions from organizations identified by one or more organization identifiers, excluding at least the organization identifier of the organization that transmitted the project conditions received by the condition receiving unit, out of the two or more organization identifiers included in the project conditions, the project is deemed to have been established, and the project information is stored in the project management unit in association with the project identifier.

4. The joint delivery sending unit Transmitting all or part of the delivery task information selected by the delivery task selection unit to an organization identified by an organization identifier included in the delivery task information; a joint delivery consent receiving unit that receives joint delivery consent information from the organization, the joint delivery consent information indicating consent to carry out the delivery task identified by the delivery task information by joint delivery; 2. The joint delivery support device according to claim 1, further comprising a joint delivery registration unit that, when the joint delivery approval receiving unit receives the joint delivery approval information, accumulates joint delivery information in a joint delivery management unit in which one or more pieces of joint delivery information are stored, indicating that the delivery task specified by the delivery task information corresponding to the delivery task identifier paired with the one organization identifier and the delivery task specified by the delivery task information selected by the delivery task selection unit will be performed by joint delivery.

5. The project conditions include organizational conditions of a proposing organization proposing joint delivery and organizational conditions of a proposed organization to which joint delivery is proposed; 2. The joint delivery support device according to claim 1, wherein the organizational conditions include an organization identifier having a company identifier or an organization identifier having a company identifier and a department identifier, and period information specifying a period.

6. a delivery task receiving unit that receives delivery task information of two or more organizations; 2. The cooperative delivery support device according to claim 1, further comprising a delivery task storage unit that stores the delivery task information received by the delivery task receiving unit in the delivery task management unit in association with a delivery task identifier.

7. The delivery task information has a package attribute value, The delivery task selection unit 2. The joint delivery support device according to claim 1, wherein a luggage rule, which is a rule regarding luggage that cannot be mixed, is used for luggage attribute values ​​of the delivery task information corresponding to the delivery task identifier that pairs with the one organization identifier, and delivery task information including luggage attribute values ​​of luggage that cannot be mixed is not selected.

8. The joint delivery sending unit 2. The joint delivery support device according to claim 1, wherein the device refers to an organization relationship management unit in which one or more pieces of relationship information specifying the relationship between two or more organizations are stored, and transmits different information among the pieces of information contained in the delivery task information depending on the relationship information specifying the relationship between the organization identified by the one organization identifier and the other organization.

9. The joint delivery support device according to claim 1, wherein the joint delivery conditions are one or two of a mixed loading condition for determining whether mixed loading is possible, or a return flight condition for determining whether joint delivery using a return flight is possible.

10. A joint delivery support method executed in a joint delivery support device including a condition receiving unit, a project registration unit, a project management unit, a delivery task management unit, a delivery task selection unit, and a joint delivery transmission unit, comprising: a step in which the condition receiving unit receives project conditions having an organization identifier of an organization different from the organization identified by the one organization identifier; a step in which the project registration unit stores project conditions, which are conditions for a joint delivery project of a package and have two or more organization identifiers, and the project information, which is information associated with a project identifier for identifying a project, in the project management unit where the project registration unit stores project information including the project conditions received in the receiving step, in association with the project identifier; The delivery task selection unit selects, from the delivery task management unit storing two or more pieces of delivery task information, the delivery task information corresponding to the delivery task identifier paired with the one organization identifier, which satisfies the project conditions of the project information stored in the project management unit and the joint delivery conditions that are conditions for joint delivery, and which includes an organization identifier of an organization other than the organization identified by the one organization identifier, and which corresponds to the delivery task identifier and has an organization identifier that identifies the organization of the delivery task, receiving base information, shipping base information, and running time zone information; a step in which the joint delivery transmitting unit transmits all or part of the delivery task information selected in the selecting step.

11. Computer, A program for causing the joint delivery support device according to any one of claims 1 to 9 to function.

Images