Integrated logistics systems, integrated logistics methods, and programs

The collaborative logistics system addresses independent operations in different zones by using a server and operator devices for coordinated resource allocation and data distribution, enhancing efficiency and confidentiality in inter-zone logistics planning.

JP2026087338APending Publication Date: 2026-05-27ナカノ商会 +1

Patent Information

Authority / Receiving Office
JP · JP
Patent Type
Applications
Current Assignee / Owner
ナカノ商会
Filing Date
2024-11-15
Publication Date
2026-05-27

Smart Images

  • Figure 2026087338000001_ABST
    Figure 2026087338000001_ABST
Patent Text Reader

Abstract

We propose a collaborative logistics system suitable for enabling logistics to be realized through cooperation among businesses belonging to different logistics economic zones. [Solution] The collaborative logistics system 1 enables logistics through the collaboration of multiple logistics economic zones. The collaborative planning processing unit 17 on server 3 creates a collaborative operation plan by assigning resources responsible for transportation based on requests in one logistics economic zone to also handle transportation based on requests in a different logistics economic zone. The confidentiality management unit 18 on server 3 distributes the portion of the collaborative operation plan and resource identification data related to the request to the business device corresponding to the logistics economic zone that received the request, distributes the portion related to the transportation that the business device is responsible for to the business device corresponding to the logistics economic zone that did not receive the request but is responsible for transportation, and does not distribute the portion related to the request to the business device corresponding to the logistics economic zone that did not receive the request and is not responsible for transportation.
Need to check novelty before this filing date? Find Prior Art

Description

[Technical Field]

[0001] The present invention relates to a collaborative logistics system, a collaborative logistics method, and a program, and more particularly to a collaborative logistics system, etc., for which multiple businesses cooperate to realize logistics. [Background technology]

[0002] Logistics involving the consolidation of goods from multiple shippers are known, for example, as joint delivery (see Patent Document 1, etc.). [Prior art documents] [Patent Documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2024-049463 [Overview of the Initiative] [Problems that the invention aims to solve]

[0004] However, multiple logistics economic zones exist within the logistics industry. Businesses within the same economic zone can share data. Conversely, businesses in different economic zones do not share data. Thus, businesses either share all data or not. Therefore, operational plans are created independently in different logistics economic zones.

[0005] Therefore, the present invention aims to propose a collaborative logistics system, etc., that is suitable for realizing logistics through cooperation among businesses belonging to different logistics economic zones. [Means for solving the problem]

[0006] The first aspect of the present invention is a collaborative logistics system for realizing logistics through the cooperation of multiple logistics economic zones, comprising a server and multiple operator devices, each operator device corresponding to a different logistics economic zone, the server comprising a collaborative planning processing unit and a confidentiality management unit, the collaborative planning processing unit managing collaborative operation plans and data identifying resources, the collaborative planning processing unit creating the collaborative operation plan by assigning resources responsible for transportation based on requests in a certain logistics economic zone to also be responsible for transportation based on requests in a different logistics economic zone, and the confidentiality management unit distributing the portion of the collaborative operation plan and data identifying resources related to the request to the operator device corresponding to the logistics economic zone that received the request, distributing the portion of the transportation that the operator device is responsible for to the operator device corresponding to the logistics economic zone that did not receive the request but is responsible for transportation, and not distributing at least a portion of the data related to the request to the operator device corresponding to the logistics economic zone that did not receive the request but is not responsible for transportation.

[0007] A second aspect of the present invention is the collaborative logistics system of the first aspect, wherein the collaborative planning processing unit coordinates delivery requests related to the transportation in a given logistics economic zone with resources responsible for transportation in a given logistics economic zone, and assigns them to handle transportation in requests in different logistics economic zones.

[0008] A third aspect of the present invention is a collaborative logistics system of the first or second aspect, wherein the collaborative logistics system includes a worker device that reports transportation work related to the collaborative operation plan to the business operator device, the server includes a collaborative management processing unit, the business operator device includes an individual management processing unit, the individual management processing unit notifies the server of the report, the collaborative management processing unit uses the report to manage the operation of the collaborative operation plan, and the confidentiality management unit, with respect to the request for which the report has been received, distributes operation management related to the report to the business operator device corresponding to the logistics economic zone that received the request, distributes operation management related to the report to the business operator device corresponding to the logistics economic zone that is responsible for transportation but has not received the request, and does not distribute operation management related to the report to the business operator device corresponding to the logistics economic zone that is responsible for transportation but has not received the request.

[0009] A fourth aspect of the present invention is a collaborative logistics method in a collaborative logistics system for realizing logistics through the cooperation of multiple logistics economic zones, wherein the collaborative logistics system comprises a server and multiple operator devices, each operator device corresponding to a different logistics economic zone, the server comprises a collaborative planning processing unit and a confidentiality management unit, the collaborative planning processing unit manages data identifying collaborative operation plans and resources, the collaborative planning processing unit creates a collaborative operation plan by assigning resources responsible for transportation at the request of a certain logistics economic zone to also be responsible for transportation at the request of a different logistics economic zone, and the confidentiality management unit distributes the portion of the data identifying the collaborative operation plan and resources to the operator device corresponding to the logistics economic zone that received the request, distributes the portion of the transportation it is responsible for to the operator device corresponding to the logistics economic zone that did not receive the request but is responsible for transportation, and does not distribute at least a portion of the data related to the request to the operator device corresponding to the logistics economic zone that did not receive the request but is not responsible for transportation.

[0010] A fifth aspect of the present invention is a collaborative logistics method of the fourth aspect, wherein the collaborative planning processing unit coordinates delivery requests related to the transportation in a given logistics economic zone with resources responsible for transportation in a given logistics economic zone, and assigns them to handle transportation in requests in different logistics economic zones.

[0011] A sixth aspect of the present invention is a collaborative logistics method according to the fourth or fifth aspect, wherein the collaborative logistics system includes a worker device that reports transportation work related to the collaborative operation plan to the business operator device, the server includes a collaborative management processing unit, the business operator device includes an individual management processing unit, the individual management processing unit notifies the server of the report, the collaborative management processing unit uses the report to manage the operation of the collaborative operation plan, the confidentiality management unit distributes operation management related to the report to the business operator device corresponding to the logistics economic zone that received the request, distributes operation management related to the report to the business operator device corresponding to the logistics economic zone that received the request but is responsible for transportation but has not received the request, and does not distribute operation management related to the report to the business operator device corresponding to the logistics economic zone that has not received the request but is not responsible for transportation.

[0012] The seventh aspect of the present invention is a program for causing a computer to function as a confidentiality management unit for any of the first to third aspects. Alternatively, the present invention may be considered as a computer-readable recording medium for recording the program of the seventh aspect. [Effects of the Invention]

[0013] According to each aspect of the present invention, a server can create a collaborative operation plan, enabling multiple businesses to cooperate in realizing logistics, and the server's confidentiality management unit can ensure mutual confidentiality in the collaborative operation plan distributed to each business. [Brief explanation of the drawing]

[0014] [Figure 1] This is a block diagram showing an example of the configuration of the collaborative logistics system 1 according to an embodiment of the present invention. [Figure 2] This block diagram shows an example of the configuration of the worker device 7, the business operator device 5, and the server 3 in Figure 1. [Figure 3] This is a flowchart showing an example of the processing of the individual planning processing unit 31 of the operator's device 5. [Figure 4] This flowchart illustrates an example of the process for determining a coordinated operation plan to realize integrated logistics across multiple logistics economic zones. [Figure 5] Figure 1 illustrates a specific example of the process for creating a transportation plan in the integrated logistics system 1. [Figure 6] Figure 2 illustrates a specific example of the process for creating a transportation plan in the integrated logistics system 1. [Figure 7] Figure 3 illustrates a specific example of the process for creating a transportation plan in the integrated logistics system 1. [Figure 8] Figure 4 illustrates a specific example of the process for creating a transportation plan in the integrated logistics system 1. [Figure 9] Figure 5 illustrates a specific example of the process for creating a transportation plan in the integrated logistics system 1. [Figure 10] This flowchart shows an example of how the collaborative management processing unit 19 processes a report regarding work from the operator's device 5. [Figure 11] This flowchart shows an example of processing in the collaborative management processing unit 19 when a work-related report is received from the operator's device 5. [Figure 12] This flowchart shows an example of how the individual management processing unit 33 processes a report regarding collaborative logistics from server 3. [Figure 13] Figure 1 illustrates a specific example of the operation management process in the integrated logistics system 1. [Figure 14] Figure 2 illustrates a specific example of the operation management process in the integrated logistics system 1. [Modes for carrying out the invention]

[0015] The following describes embodiments of the present invention with reference to the drawings. However, the present invention is not limited to these embodiments. [Examples]

[0016] Figures 1 and 2 are block diagrams showing an example of the configuration of the collaborative logistics system 1 according to an embodiment of the present invention.

[0017] In this example, in response to requests from multiple shippers, N (where N is a natural number greater than or equal to 2) transportation companies belonging to logistics economic zones collaborate to fulfill the logistics needs. Each transportation company is, for example, a logistics company or a transportation company, and possesses the resources necessary to fulfill the logistics needs. These resources include physical items such as trucks and ships, and human resources such as workers (drivers, etc.).

[0018] In this example, in each logistics economic zone, the operator device 5 manages the work performed by the transportation companies belonging to that zone. In addition, each worker possesses a worker device 7, which allows them to understand the work they are responsible for based on instructions from the operator device 5, and to report to the operator device 5 when the work is completed.

[0019] Referring to Figure 1, the collaborative logistics system 1 consists of a server 3 and N operator devices 5. n (where n is a natural number from 1 to N) It ​​includes N operators' devices 5 n This corresponds to each logistics economic zone. The operator equipment 5 may be implemented by a single device or by multiple devices.

[0020] Each operator equipment 5 n Corresponding to this, there are one or more worker devices 7. For example, corresponding to the operator device 51, there are p worker devices 7 (where p is a natural number) 11 ,…,7 1p It exists. Operator equipment 5 N Correspondingly, there are q (where q is a natural number) worker devices 7 N1 ,…,7 NqSuch equipment exists. The worker device 7 is provided, for example, according to the worker, vehicle, etc.

[0021] Figures 2(a), (b), and (c) are block diagrams showing examples of the configurations of the worker device 7, business operator device 5, and server 3 in Figure 1, respectively.

[0022] Referring to Figure 2(a), the operator device 7 comprises an input / output device 37, a communication device 39, and a processing device 41.

[0023] The input / output device 37 is an input / output device such as a keyboard, mouse, or touch panel, used for inputting and outputting data between the operator and the system.

[0024] The communication device 39 is a communication device for communicating with the operator's device 5. The communication may be wired or wireless.

[0025] The processing unit 41 is a processor or the like, and is a processing unit for realizing information processing. The processing unit 41 includes a work management unit 43. The work management unit 43 can be implemented, for example, by a processor that operates under the control of a program.

[0026] Referring to Figure 2(b), the operator's device 5 includes an input / output device 23, a communication device 25, a processing device 27, and a storage device 29.

[0027] The input / output device 23 is an input / output device such as a keyboard, mouse, or touch panel, and is used for data input / output processing with personnel at the transportation company.

[0028] The communication device 25 is a communication device for communicating with the server 3 and the operator device 7. The communication may be wired or wireless.

[0029] The processing unit 27 is a processor or the like, and is a processing unit for realizing data processing. The processing unit 27 comprises an individual planning processing unit 31 and an individual management processing unit 33. The individual planning processing unit 31 and the individual management processing unit 33 can be realized, for example, by a processor that operates under the control of a program.

[0030] The storage device 29 is a memory device or the like, and is a storage device that stores data. The storage device 29 includes an individual operation planning unit 35.

[0031] A Transport Management System (TMS) is a system that comprehensively manages the transportation and delivery of goods from the time they are shipped from the logistics center until they reach their destination. The TMS primarily consists of systems that support dispatch planning and operation management. In the operator device 5, the individual planning processing unit 31 is mainly responsible for dispatch planning, and the individual management processing unit 33 is responsible for operation management. The individual planning processing unit 31, the individual management processing unit 33, and the individual operation planning unit 35 can be implemented in the same way as a typical TMS. However, the operator device 5 prioritizes the processing performed by the server 3 in parts where the server 3 is responsible for processing. For example, it prioritizes operation planning and operation management performed by the server 3 and does not make any changes on the operator device 5 side.

[0032] The individual planning processing unit 31 notifies the server 3 of the resources belonging to the logistics economic zone to which it belongs that the server 3 can allocate in cooperation with to realize the operation plan.

[0033] In the transportation business, workers input data corresponding to requests from shippers using the input / output device 37. For each request, the worker inputs whether or not to perform coordinated logistics via server 3. Coordinated logistics is a type of logistics realized through the collaboration of multiple logistics economic zones via operation planning and management on server 3. For simplicity, in this embodiment, it is assumed that workers only input requests for coordinated logistics.

[0034] For requests that cannot be fulfilled through coordinated logistics, the individual planning processing unit 31 can fulfill them in the same way as a typical TMS, for example, by coordinating vehicles for delivery or coordinating drivers responsible for each task.

[0035] Referring to Figure 2(c), the server 3 comprises a communication device 11, a processing unit 13, and a storage device 15.

[0036] Communication device 11 is a communication device for communicating with the operator's device 5. Communication may be wired or wireless.

[0037] The processing unit 13 is a processor or the like, and is a processing unit for realizing information processing. The processing unit 13 comprises a cooperation planning processing unit 17, a confidentiality management unit 18, and a cooperation management processing unit 19. The cooperation planning processing unit 17, the confidentiality management unit 18, and the cooperation management processing unit 19 can be realized, for example, by a processor that operates under the control of a program.

[0038] The storage device 15 is a memory device or the like, and is a storage device that stores data. The storage device 15 is equipped with a coordinated operation planning unit 21.

[0039] Each operator's device 5 manages a database of operational plans for requests involving coordinated logistics. Server 3 shares the database of operational plans for requests involving coordinated logistics from each operator's device 5 in its coordinated operational planning unit 21. The coordinated operational planning unit 21 also stores data that identifies the resources that can be used to realize coordinated logistics.

[0040] The coordination planning processing unit 17 creates a train operation plan by referring to the coordination operation planning unit 21. The train operation plan created by the coordination planning processing unit 17 is called the "coordination operation plan." Resources are also allocated to the coordination operation plan. This process can be implemented in the same way as in a typical TMS (Transportation Management System).

[0041] The confidentiality management unit 18 performs confidentiality processing on data that identifies the coordinated operation plan and the resources necessary to realize the said coordinated operation plan. The confidentiality processing is, for example, as follows:

[0042] The administrator of Server 3 can view all data that identifies the coordinated operation plan and resources.

[0043] The operator device 5, which corresponds to the logistics economic zone that received the request, can obtain data that identifies the coordinated operation plan and resources related to the requested cargo.

[0044] In the logistics economic zone where a request has not been made but the operator is responsible for transportation, the operator device 5 can grasp the portion of the data related to the transportation it is responsible for, which includes the coordinated operation plan and resource identification data for the request.

[0045] In the case of operator device 5, which is responsible for a logistics economic zone that has not received a request and does not handle transportation, it is not possible to obtain the data that identifies the coordinated operation plan and resources related to the request.

[0046] The confidentiality management unit 18 performs confidentiality processing on data identifying the coordinated operation plan and resources according to the requirements of each operator, and then distributes it to each operator's device 5.

[0047] Refer to Figures 3 through 9 to explain the coordinated operation plan in coordinated logistics.

[0048] Figure 3 is a flowchart showing an example of the processing of the individual planning processing unit 31 of the operator's device 5.

[0049] The individual planning processing unit 31 determines whether or not server 3 has sent a coordinated operation plan to the operator's device 5 (step STA1). If server 3 has sent a coordinated operation plan, the process proceeds to step STA8. If server 3 has not sent a coordinated operation plan, the process proceeds to step STA2.

[0050] In step STA2, the individual planning processing unit 31 determines whether an operator of the contractor device 5 has entered a request. If a request has been entered, the process proceeds to step STA3. If no request has been entered, the process returns to step STA1.

[0051] In step STA3, the individual planning processing unit 31 makes the data entered by the operator of the contractor device 5 processable as a database.

[0052] The individual planning processing unit 31 determines whether to realize the request by coordinated logistics (step STA4). For example, if the operator has not instructed coordinated logistics, the individual planning processing unit 31 determines that it will not be realized by coordinated logistics. On the other hand, if the operator has instructed coordinated logistics, in principle, the individual planning processing unit 31 determines that it will be realized by coordinated logistics. However, for example, if collection and delivery are performed without using the main line for the request, the individual planning processing unit 31 determines that it will not be realized by coordinated logistics even if the operator has instructed coordinated logistics. If the individual planning processing unit 31 determines that the request will not be realized by coordinated logistics, it creates an operation plan individually and performs operation management in the same manner as a normal TMS (step STA5), and returns to step STA1. If the individual planning processing unit 31 determines that the request will be realized by coordinated logistics, the process proceeds to step STA6.

[0053] In step STA6, the individual planning processing unit 31 refers to the input data and prepares to create a coordinated operation plan. In this example, for simplicity, it is assumed that four shipping requests are managed in the coordinated operation plan.

[0054] The first delivery request is to deliver the collected goods to the shipping main line base. The shipping main line base is the base that becomes the departure point on the main line in the transportation route of the goods. The individual planning processing unit 31 determines the time t α to deliver the goods to the shipping main line base, referring to, for example, the working hours of the business office.

[0055] The second shipping request is to depart from the shipping main line base on the main line.

[0056] The third dispatch request is for the shipment to arrive at the destination trunk line hub on the trunk line.

[0057] The fourth dispatch request is to deliver the package from the arrival trunk hub to a sales office or similar location. The individual planning processing unit 31, for example, refers to the business hours of the sales office and determines the time t when the package will depart from the arrival trunk hub. δ To decide.

[0058] In this example, coordinated logistics enable the delivery of goods from the outbound trunk line to the receiving trunk line and then to sales offices and other locations. The individual planning processing unit 31 notifies the server 3 (step STA7) and returns to step STA1.

[0059] In step STA8, the individual planning processing unit 31 receives the coordinated operation plan from the server 3. The individual planning unit 35 stores the received coordinated operation plan and resources in a format that can be processed as a database. The individual planning processing unit 31 determines whether the received coordinated operation plan is provisional or not (step STA9). If the received coordinated operation plan is provisional, the individual planning processing unit 31 returns to step STA1. If the received coordinated operation plan is not provisional (i.e., it is official), the individual planning processing unit 31 terminates processing.

[0060] Figure 4 is a flowchart illustrating an example of the process for determining a coordinated operation plan to realize coordinated logistics involving multiple logistics economic zones.

[0061] The coordination planning processing unit 17 determines whether or not to decide on a coordination operation plan (step STB1). For example, the coordination planning processing unit 17 may decide not to decide on an operation plan until the reference time of the previous day (e.g., 18:00), and decide to decide on a coordination operation plan after the reference time. If the coordination planning processing unit 17 decides not to decide on a coordination operation plan, it proceeds to step STB2. If the coordination planning processing unit 17 decides to decide on a coordination operation plan, it proceeds to step STB7.

[0062] In step STB2, the coordination planning processing unit 17 determines whether or not it has received a notification regarding coordinated logistics from the operator's device 5 (see step STA7 in Figure 3). If a notification regarding an individual operation plan for coordinated logistics has been received, the process proceeds to step STB3. If no notification has been received, the process returns to step STB1.

[0063] In step STB3, the collaborative planning processing unit 17 shares the individual operation plans from the collaborative logistics system with the database of the individual operation planning unit 35, and manages them as a database in the collaborative operation planning unit 21.

[0064] The coordination planning processing unit 17 refers to the coordination operation planning unit 21 and adjusts a provisional coordination operation plan and provisional resources to realize the said coordination operation plan (step STB4). This can be implemented in the same way as processing in a normal TMS.

[0065] For example, in the operator's device 5, in relation to the first and fourth delivery requests, the time t of delivering the package to the dispatch trunk hub α and the departure time of the package from the arrival trunk hub. δ Determine (see step STA6). Server 3 determines the time t in relation to the second and third delivery requests. α and time t δ Between these times, the departure time from the main shipping hub β and the time of arrival at the arrival trunk hub t γ We will adjust the schedule and decide on a provisional coordinated operation plan.

[0066] Furthermore, the coordination planning processing unit 17 allocates provisional resources to realize the coordination operation plan. For the task of delivering packages to the outbound trunk line base, the coordination planning processing unit 17 allocates resources from the logistics economic zone that received the package request. For the task of delivering packages from the outbound trunk line base to the arrival trunk line base and for the task of departing packages from the arrival trunk line base, the coordination planning processing unit 17 allocates resources from any logistics economic zone, regardless of whether or not it received a package request.

[0067] The confidentiality management unit 18 performs confidentiality processing on the provisional coordinated operation plan and resource identification data (step STB5). The confidentiality management unit 18 distributes the provisional coordinated operation plan and resource identification data, after confidentiality processing, to each operator device 5 according to the operator (step STB6). Specifically, the confidentiality management unit 18 distributes the portion related to the request to the operator device 5 corresponding to the requested logistics economic zone. To operator device 5 corresponding to a logistics economic zone that has not received a request but is responsible for transportation, the portion related to the transportation is distributed. To operator device 5 corresponding to a logistics economic zone that has not received a request and is not responsible for transportation, the portion related to the request is not distributed. The process returns to step STB1.

[0068] In step STB7, the coordination planning processing unit 17 determines that the last provisional coordination operation plan and resources created at that time are the official coordination operation plan and resources.

[0069] The confidentiality management unit 18 performs confidentiality processing on the formal coordinated operation plan and resource identification data (step STB8). The confidentiality management unit 18 distributes the formal coordinated operation plan and resource identification data, after confidentiality processing, to each operator's equipment 5, according to the operator (step STB9). These processes are the same as in steps STB5 and STB6. The process shown in Figure 4 is then completed.

[0070] Upon receiving data identifying the coordinated operation plan and resources, the operator's device 5 can, for example, make adjustments to individually managed operation plans and resources.

[0071] Referring to Figures 5 to 9, a specific example of the process for creating an operation plan in the collaborative logistics system 1 will be explained. In this example, there are three logistics economic zones: A, B, and C.

[0072] Referring to Figure 5(a), first, Party A inputs the request via the collaborative logistics system. Party A's business device 5 甲 Individual planning processing unit 31 甲 Let S be the outbound trunk hub and T be the arrival trunk hub.

[0073] Delivery request A is to deliver the collected packages to the main shipping hub S. Individual planning processing unit 31 甲 This specifies the time when the package will be delivered to the main shipping hub S. 甲A This is the decision.

[0074] Delivery request B is to depart the package from the main shipping hub S. The coordination planning processing unit 17 determines the departure time from the main shipping hub S. 甲B This is the decision.

[0075] Delivery request C is to have the package arrive at the destination trunk hub T. The coordination planning processing unit 17 determines the time of arrival at the destination trunk hub T. 甲C This is the decision.

[0076] Delivery request D is to deliver a package from arrival trunk hub T. Individual planning processing unit 31 甲 The departure time from arrival trunk hub T is t 甲D This is the decision.

[0077] Figure 5(b) shows a provisional coordinated operation plan and resources managed by the coordinated operation planning unit 21. The coordinated operation planning processing unit 17 assigns driver A1, who belongs to A, as a resource to delivery requests A, B, C, and D. Figure 5(b) shows that driver A1 is in charge of delivery requests A, B, C, and D.

[0078] Figure 5(c) shows the operator's equipment 5 甲 This shows the provisional coordinated operation plan and resources to be distributed. Confidential Management Unit 18 is a logistics economic zone for which Party A has been requested, therefore, operator equipment 5 甲 To that end, a provisional coordinated operation plan and resources related to the request will be distributed.

[0079] Next, referring to Figure 6(a), let's assume that Party B has entered a request via the collaborative logistics system. Party B's business device 5 乙 Individual planning processing unit 31 乙 Let U be the outbound trunk hub and V be the arrival trunk hub.

[0080] Delivery request E is to deliver the collected packages to the main shipping hub U. Individual planning processing unit 31 乙 This refers to the time when the package will be delivered to the main shipping hub U. 乙E This is the decision.

[0081] Delivery request F is to send a package from the main shipping hub U. The coordination planning processing unit 17 sets the departure time from the main shipping hub U. 乙F This is the decision.

[0082] Delivery request G is to have the package arrive at the destination trunk hub V. The coordination planning processing unit 17 determines the time of arrival at the destination trunk hub V. 乙G This is the decision.

[0083] Delivery request H is to deliver a package from arrival trunk hub V. Individual planning processing unit 31 乙 The departure time from arrival trunk hub V is t 乙H This is the decision.

[0084] Figure 6(b) shows the relationship between delivery requests A-D related to Party A's request and delivery requests E-H related to Party B's request. Traditionally, since Party A and Party B belong to different logistics economic zones, they did not share data regarding cargo. Therefore, each logistics economic zone created its own operational plan. Thus, operations were conducted in the state shown in Figure 6(b). Even if joint transportation were to be carried out, it was only for adjusting the volume. Therefore, the time for joint transportation had to be determined in advance, a space for a freight car that could be used for that joint transportation had to be secured, the cargo had to arrive in time for the departure time, and the cargo had to be received after the arrival time.

[0085] There are two delivery requests that travel along the main line: delivery requests B and C, and delivery requests F and G. As shown in Figure 6(c), the coordination planning processing unit 17 assigns delivery request D to another resource instead of having A1 handle it. This allows A1 to handle another delivery request after handling delivery requests B and C.

[0086] As shown in Figure 7(a), the coordination planning processing unit 17 assigns delivery requests F, G, and H to Party A1. Specifically, Party A1 delivers the collected packages to the outbound trunk hub S (delivery request A), and then uses the trunk line to transport them from the outbound trunk hub S to the arrival trunk hub T (delivery requests B and C). Furthermore, Party A1 moves to the outbound trunk hub U and uses the trunk line to transport Party B's packages from the outbound trunk hub U to the arrival trunk hub V (delivery requests F and G), and then delivers them from the arrival trunk hub V (delivery request H).

[0087] Furthermore, the coordination planning processing unit 17 assigns driver A2 as a resource to delivery request D. The coordination planning processing unit 17 also assigns driver B1 as a resource to delivery request E.

[0088] Figure 7(b) shows the operator's equipment 5 甲 This shows the provisional coordinated operation plan and resources to be distributed. The confidentiality management department 18 will handle the request received by Party A, and the operator equipment 5 甲 To that end, a provisional coordinated operation plan and resource allocation for the request will be distributed. In addition, the confidentiality management unit 18 will distribute the request received by Party B to the operator equipment 5 甲 In response to the request, a provisional coordinated operation plan and resource allocation for the transportation to be handled will be distributed. The confidentiality department 18 will not distribute information regarding the work to be handled by Party B1, as this pertains to a request received by Party B, and Party A is not responsible for the transportation.

[0089] Figure 7(c) shows the operator's equipment 5 乙 This shows the provisional coordinated operation plan and resources to be distributed. The confidentiality management department 18 will handle the request received by Party B, and the operator equipment 5 乙 To that end, a provisional coordinated operation plan and resource allocation for the request will be distributed. Here, it will be distributed that delivery request E will be handled by Party B1, and delivery requests F, G, and H will be handled by Party A1. However, Party B will not be responsible for the work for which Party A has received the request. Therefore, for the work that Party A1 is responsible for, the Confidentiality Management Department 18 will perform confidentiality processing and distribute the information for the requests received by Party A. Also, the Confidentiality Management Department 18 will not distribute the information for the work that Party A2 is responsible for, as it pertains to requests received by Party A and Party B is not responsible for transportation.

[0090] Note that in Figure 7(c), the data is distributed with some parts blacked out, but it may also be distributed with the data deleted, for example. In this way, the confidentiality management unit 18 may perform confidentiality processing on some parts (for example, the work content) and distribute the rest (for example, the time). Alternatively, the confidentiality management unit 18 may perform confidentiality processing on all parts.

[0091] Next, referring to Figure 8(a), let's assume that Party C has entered a request via collaborative logistics. Party C's business device 5 丙 Individual planning processing unit 31 丙 Let T be the outbound trunk hub and U be the arrival trunk hub.

[0092] Delivery request I is to deliver the collected packages to the main shipping hub T. Individual planning processing unit 31 丙 This refers to the time when the package will be delivered to the main shipping hub T. 丙I This is the decision.

[0093] Delivery request J is to send a package from the main shipping hub T. The coordination planning processing unit 17 sets the departure time from the main shipping hub T to t 丙J This is the decision.

[0094] Delivery request K is to have the package arrive at the destination trunk hub U. The coordination planning processing unit 17 determines the time of arrival at the destination trunk hub U. 丙K This is the decision.

[0095] Delivery request L is to deliver a package from the arrival trunk line hub U. Individual planning processing unit 31 丙 The departure time from arrival trunk hub U is t 丙L This is the decision.

[0096] Figure 8(b) shows the relationship between delivery requests A-H (see Figure 7(a)) related to requests from Party A and Party B, and delivery requests I-L related to requests from Party C. Traditionally, Party C was in a different logistics economic zone from Party A and Party B, and therefore did not share data regarding cargo. For this reason, Party C created its operational plans independently of Party A and Party B.

[0097] There are delivery requests B and C, delivery requests F and G, and delivery requests J and K, which are delivery requests that travel along the main line. However, at present, delivery requests F and G (time t 乙F Departing from base U by time t 乙G (Arrive at base V by [time]) and delivery requests J and K (time t 丙J Departing from base T by time t 丙K The timing of arriving at base U by a certain date overlaps, and the same driver cannot be assigned to each location.

[0098] Based on the relative locations of the bases, it is desirable to handle delivery requests B and C (arriving at base T), delivery requests J and K (departing from base T and arriving at base U), and delivery requests F and G (arriving at base V) in that order. Therefore, the coordination planning processing unit 17 will handle delivery requests J and K at time t 丙J and t 丙K Shifting the time forward (i.e., planning for an earlier time), and / or the time t of delivery requests F and G. 乙F and t 乙G We try to shift it later (i.e., plan it for a later time). In this example, the time t of delivery requests J and K 丙J and t 丙K It cannot be shifted forward in relation to delivery requests A, B, and C, but the time t of delivery requests F and G 乙F and t 乙G It can be shifted to a later date in relation to delivery request H.

[0099] Figure 8(c) shows that the coordination planning processing unit 17 processes the time t of delivery requests F and G. 乙F and t 乙G Shift it to the later time t 乙F改 and t 乙G改 This shows that in Figure 8(b), delivery requests F and G are shifted to the later time t. 乙F改 and t 乙G改 This indicates a state of affairs.

[0100] Referring to Figure 9(a), the coordination planning processing unit 17 assigns delivery requests J and K to Party A1. Specifically, Party A1 delivers the collected packages to the outbound trunk line hub S (delivery request A) and uses the trunk line to transport them from the outbound trunk line hub S to the arrival trunk line hub T (delivery requests B and C). Party A1 also uses the trunk line to transport Party C's packages from the outbound trunk line hub T to the arrival trunk line hub U (delivery requests J and K). Furthermore, Party A1 uses the trunk line to transport Party B's packages from the outbound trunk line hub U to the arrival trunk line hub V (delivery requests F and G) and delivers them from the arrival trunk line hub V (delivery request H).

[0101] Furthermore, driver B1 delivers B's package to base U before A1 arrives at base U. Therefore, the coordination planning processing unit 17 assigns delivery request L to driver B1. B1 delivers B's collected package to the outbound trunk base U (delivery request E) and delivers C's package from the arrival trunk base U (delivery request L).

[0102] Furthermore, the coordination planning processing unit 17 assigns driver C1 to delivery request I. Driver C1 will deliver C's package to base T before A1 arrives at base T. Therefore, the coordination planning processing unit 17 assigns delivery request D to driver C1. C1 delivers C's collected package to the dispatch trunk base T (delivery request I) and delivers A's package from the arrival trunk base T (delivery request D).

[0103] Figure 9(b) shows the operator's equipment 5 甲 This shows the provisional coordinated operation plan and resources to be distributed. The confidentiality management department 18 will handle the request received by Party A, and the operator equipment 5 甲 To that end, data regarding the delivery request related to the said request will be distributed. In addition, regarding the requests received by Party B and Party C, the business device 5 甲 To that end, data regarding delivery requests for the transportation services they are responsible for will be distributed.

[0104] The confidentiality management unit 18 is the operator's equipment 5 甲To this end, the Confidentiality Department 18 will distribute delivery requests A, B, C, F, G, J, K, and H (delivery requests F and G are the adjusted versions) for the work that Party A1 is in charge of. The Confidentiality Department 18 will not distribute delivery requests E and L for the work that Party B1 is in charge of, as these are requests received by Party B and Party C. The Confidentiality Department 18 will distribute delivery request D for the work that Party C1 is in charge of, as it is a request received by Party A, and will distribute other delivery requests (delivery request I) after performing confidentiality processing.

[0105] Figure 9(c) shows the operator's equipment 5 乙 This shows the provisional coordinated operation plan and resources to be distributed. The confidentiality management department 18 will handle the request received by Party B, and the operator equipment 5 乙 To that end, data regarding the delivery request related to the said request will be distributed. In addition, regarding the requests received by A and C, the business device 5 乙 To that end, data regarding delivery requests for the transportation services they are responsible for will be distributed.

[0106] The confidentiality management unit 18 is the operator's equipment 5 乙 Regarding the work to be handled by Party B1, delivery requests E and L will be distributed. The Confidentiality Management Department 18 will distribute delivery requests F, G, and H (delivery requests F and G are the adjusted versions) related to the request received by Party B for the work to be handled by Party A1, and will distribute other delivery requests (delivery requests A, B, C, J, and K) after confidentiality processing. The Confidentiality Management Department 18 will not distribute delivery requests I and D for the work to be handled by Party C1, as these are requests received by Party A and Party C.

[0107] Figure 9(d) shows the operator's equipment 5 丙 This shows the provisional coordinated operation plan and resources to be distributed. The confidentiality management unit 18 will handle the request received by C, and the operator equipment 5 丙 To that end, data regarding the delivery request related to the said request will be distributed. In addition, regarding the requests received by Party A and Party B, the business device 5 丙 To that end, data regarding delivery requests for the transportation services they are responsible for will be distributed.

[0108] The confidentiality management unit 18 is the operator's equipment 5 丙Regarding the work that C1 is in charge of, delivery requests I and D will be distributed. The Confidentiality Management Department 18 will distribute delivery requests J and K related to the request received by C for the work that A1 is in charge of, and will distribute other delivery requests after confidentiality processing. The Confidentiality Management Department 18 will distribute delivery request L related to the request received by C for the work that B1 is in charge of, and will distribute other delivery requests (delivery request E) after confidentiality processing.

[0109] As shown in Figures 8(d) and 9(a), the coordination planning processing unit 17 can assign drivers who are responsible for trunk line transportation based on requests from one logistics economic zone to also handle trunk line transportation based on requests from a different logistics economic zone during times when they have space to transport goods. In this example, for simplicity, a case without consolidation is shown, but goods from requests in multiple logistics economic zones may be transported together.

[0110] Furthermore, as shown in Figures 8(b) and 8(d), the coordination planning processing unit 17 can coordinate delivery requests for a driver who is responsible for trunk line transportation based on a request from a certain logistics economic zone, and assign them to handle trunk line transportation based on requests from different logistics economic zones.

[0111] Subsequently, when it is time to create a formal collaborative operation plan, the collaborative operation planning unit 17 determines that the last provisional collaborative operation plan and resources created at that time will be the formal collaborative operation plan and resources. The confidentiality management unit 18 performs confidentiality processing on the formal collaborative operation plan and resources and distributes them to Party A, Party B, and Party C, who are in charge of collaborative logistics.

[0112] Refer to Figures 10 to 14 to explain the operation management in collaborative logistics.

[0113] The operator device 5 manages operations based on work reports from the worker device 7. Figure 10 is a flowchart showing an example of the processing performed by the individual management processing unit 33 when a work report is received from the worker device 7.

[0114] The individual management processing unit 33 determines whether or not a report has been received from the operator device 7 (step STC1). The individual management processing unit 33 waits until a report is entered, and if a report is received, proceeds to step STC2.

[0115] In step STC2, the individual management processing unit 33 determines whether the report relates to coordinated logistics.

[0116] If the report is not related to collaborative logistics, the individual management processing unit 33 performs operational management related to the operational plan for its own logistics economic zone (step STC4). Operational management for this operational plan can be performed in the same way as in normal TMS processing. Return to step STC1.

[0117] If the report concerns coordinated logistics, the individual management processing unit 33 notifies the server 3 (step STC3). Return to step STC1.

[0118] Figure 11 is a flowchart showing an example of processing in the collaborative management processing unit 19 when a report regarding work is received from the operator's device 5. The collaborative management processing unit 19 receives reports from the worker devices 7 via the individual management processing unit 33 of each operator's device 5 regarding the collaborative operation plan, and performs operation management by referring to the collaborative operation plan unit 21. Operation management of the collaborative operation plan in the collaborative management processing unit 19 is called "collaborative operation management." This can be implemented in the same way as processing in a normal TMS.

[0119] The linkage management processing unit 19 determines whether or not a report has been received from the operator's device 5 (see step STC3 in Figure 10) (step STD1). The linkage management processing unit 19 waits until a report is received, and if a report is received, proceeds to step STD2.

[0120] In step STD2, the collaborative management processing unit 19 performs operational management related to the collaborative operation plan. Operational management for this operation plan can be performed in the same way as in a normal TMS.

[0121] The confidentiality management unit 18 performs confidentiality processing on reports concerning the collaborative operation plan (step STD3) and distributes them (step STD4). The confidentiality processing is, for example, as follows: The administrator of server 3 can view all reports concerning the collaborative operation plan. The confidentiality management unit 18 distributes operational management reports relating to the requested portion to the operator equipment 5 corresponding to the requested logistics economic zone. It also distributes operational management reports relating to the portion of transportation that it is responsible for to operator equipment 5 corresponding to a logistics economic zone that has not received a request but is responsible for transportation. Here, prerequisite work for transportation is distributed as needed. Operational management reports relating to the requested portion are not distributed to operator equipment 5 corresponding to a logistics economic zone that has not received a request and is not responsible for trunk line transportation.

[0122] The coordination management processing unit 19 determines whether or not this is the final report regarding the coordination operation plan (step STD5). If it is not the final report, it returns to step STD1. If it is the final report, it terminates the process.

[0123] Figure 12 is a flowchart showing an example of the processing performed by the individual management processing unit 33 when it receives a report regarding collaborative logistics from the server 3.

[0124] The individual management processing unit 33 determines whether or not a report regarding linked logistics has been received from the server 3 (step STE1). The individual management processing unit 33 waits until a report is entered, and if a report is received, proceeds to step STE2.

[0125] In step STE2, the individual management processing unit 33 grasps the coordinated operation management based on reports regarding coordinated logistics. Return to step STE1.

[0126] Referring to Figures 13 and 14, a specific example of the operation management process in the collaborative logistics system 1 will be explained. In this example, the collaborative operation management of the collaborative operation plan in Figure 9 will be explained.

[0127] Figures 13 and 14 show examples of the display of the input / output device 37 of the operator device 7 operated by drivers A1, B1, and C1. The display content of each operator device 7 is distributed by the corresponding business operator device 5.

[0128] Referring to FIG. 13(a), for driver A1, regarding the work of delivery request A, it is displayed that the goods collected by A should be delivered to the shipping trunk base S by time t. 甲A If driver A1 delivers the goods collected by A to the shipping trunk base S, he touches the "completed" button display to report to the business operator device 5 甲 that the work of delivery request A has been completed. The individual management processing unit 33 甲 of the business operator device 5 甲 notifies the server 3 because it is a report regarding the coordinated operation plan. The coordinated management processing unit 19 manages the completion of delivery request A. Since delivery request A only relates to A, the coordinated management processing unit 19 distributes it to the business operator device 5 甲 and does not distribute it to the business operator device 5 乙 and the business operator device 5 丙 . The business operator device 5 甲 grasps the update of the coordinated operation management of delivery request A.

[0129] Referring to FIG. 13(b), for driver A1, regarding the work of delivery request B, it is displayed that the goods of A should depart from the shipping trunk base S by time t. 甲B If driver A1 loads the goods of A and departs from the shipping trunk base S, he touches the "completed" button display to report to the business operator device 5 甲 that the work of delivery request B has been completed. The individual management processing unit 33 甲 of the business operator device 5 甲 notifies the server 3 because it is a report regarding the coordinated operation plan. The coordinated management processing unit 19 manages the completion of delivery request B. Since delivery request B only relates to A, the coordinated management processing unit 19 distributes it to the business operator device 5 甲 and does not distribute it to the business operator device 5 乙 and the business operator device 5 丙 . The business operator device 5 甲 ​grasps the update of the coordinated operation management of the delivery request B.

[0130] Referring to FIG. 13(c), for the driver Bing 1, regarding the work of the delivery request I, it is shown that the collected Bing's goods should be delivered to the shipping trunk base T by time t. 丙I If driver Bing 1 delivers the collected Bing's goods to the shipping trunk base T, he touches the "completed" button display and reports to the business operator device 5 丙 that the work of the delivery request I has been completed. The individual management processing unit 33 丙 of the business operator device 5 丙 notifies the server 3 because it is a report on the coordinated operation plan. The coordinated management processing unit 19 manages the completion of the delivery request I. Since the delivery request I is only related to Bing, the coordinated management processing unit 19 distributes it to the business operator device 5 丙 and does not distribute it to the business operator device 5 甲 ]>and the business operator device 5 乙 . The business operator device 5 丙 grasps the update of the coordinated operation management of the delivery request I.

[0131] Referring to FIG. 13(d), for the driver Jia 1, regarding the work of the delivery request C, it is shown that the Jia's goods should be arrived at the arrival trunk base T and handed over to Bing 1 by time t. 甲C If driver Jia 1 loads the Jia's goods, arrives at the arrival trunk base T and hands them over to Bing 1, he touches the "completed" button display and reports to the business operator device 5 甲 that the work of the delivery request C has been completed. The individual management processing unit 33 甲 of the business operator device 5 甲 notifies the server 3 because it is a report on the coordinated operation plan. The coordinated management processing unit 19 manages the completion of the delivery request C. Although the delivery request C is only related to Jia, since the subsequent delivery request D is assigned to Bing 1, the coordinated management processing unit 19 distributes it to the business operator device 5 甲 and the business operator device 5 丙 and does not distribute it to the business operator device 5 乙 . The business operator device 5 甲 and the business operator device 5 丙 grasps the update of the coordinated operation management of the delivery request C.

[0132] Referring to Figure 13(e), driver A1 is instructed to receive C's package from C1, load C's package, and complete the task for delivery request J at time t 丙J It is indicated that the vehicle will depart from the main shipping hub T by [date]. Once driver A1 has loaded C's cargo and departed from the main shipping hub T, touch the "Complete" button displayed on the operator's device 5. 甲 Report to the recipient that the work for delivery request J has been completed. (Business Equipment 5) 甲 Individual management processing unit 33 甲 Since this is a report concerning the coordinated operation plan, it will be notified to server 3. The coordinated management processing unit 19 manages the completion of delivery request J. Since delivery request J relates to A and C, the coordinated management processing unit 19 will notify operator device 5 甲 and operator equipment 5 丙 Distributed to, business device 5 乙 It will not be distributed to. Operator equipment 5 甲 and operator equipment 5 丙 This will track updates to the coordinated operation management for delivery request J.

[0133] Referring to Figure 13(f), driver C1 is instructed to load A's package and perform the task of delivery request D at time t 甲D It is indicated that the vehicle will depart from arrival trunk hub T by [time]. Once driver C1 has loaded A's cargo and departed from arrival trunk hub T, touch the "Complete" button displayed on the operator device 5. 丙 Report to the recipient that the work for delivery request D has been completed. (Business Equipment 5) 丙 Individual management processing unit 33 丙 Since this is a report concerning the coordinated operation plan, it will be notified to server 3. The coordinated management processing unit 19 manages the completion of delivery request D. Since delivery request D relates to A and C, the coordinated management processing unit 19 will notify operator device 5 甲 and operator equipment 5 丙 Distributed to, business device 5 乙 It will not be distributed to. Operator equipment 5 甲 and operator equipment 5 丙 This will track updates to the coordinated operation management for delivery request D.

[0134] Referring to Figure 14(a), driver B1 is instructed to deliver B's collected package at time t for the delivery request E. 乙E It is indicated that the package must be delivered to the main shipping hub U by [date]. Once driver B1 has delivered B's package to the main shipping hub U, touch the "Complete" button and send it to the operator's device 5. 乙 Report to the recipient that the work for delivery request E has been completed. (Business Equipment 5) 乙 Individual management processing unit 33 乙 Since this is a report regarding the coordinated operation plan, it will be notified to server 3. The coordinated management processing unit 19 manages the completion of delivery request E. Since delivery request E is only relevant to party B, the coordinated management processing unit 19 will notify operator device 5. 乙 Distributed to, business device 5 甲 and operator equipment 5 丙 It will not be distributed to. Operator equipment 5 乙 This will track updates to the coordinated operation management for delivery request E.

[0135] Referring to Figure 14(b), driver A1 is instructed to perform the work for delivery request K at time t 丙K It is indicated that the cargo of party C should arrive at the arrival trunk hub U by a certain time and be handed over to party B1. Once driver A1 has loaded the cargo of party C, arrived at the arrival trunk hub U and handed it over to party B1, touch the "Complete" button displayed on the operator's device 5. 甲 Report to the recipient that the work for delivery request K has been completed. (Business Equipment 5) 甲 Individual management processing unit 33 甲 This is a report regarding the coordinated operation plan, so it is notified to server 3. The coordinated management processing unit 19 manages the completion of delivery request K. Delivery request K is related to A and C, but the subsequent delivery request L is handled by B1, so the coordinated management processing unit 19 is notified to operator device 5 甲 , operator equipment 5 丙 and operator equipment 5 乙 Distributed to: Operator equipment 5 甲 , operator equipment 5 丙 and operator equipment 5 乙 This involves monitoring updates to the coordinated operation management for delivery request K.

[0136] Referring to Figure 14(c), driver A1 is instructed to receive B's package from B1, load B's package, and complete the work for delivery request F at time t 乙F改 It is indicated that the vehicle will depart from the main shipping hub U by [date]. Once driver A1 has loaded B's cargo and departed from the main shipping hub U, touch the "Complete" button displayed on the operator's device 5. 甲 Report to the recipient that the work for delivery request F has been completed. (Business Equipment 5) 甲 Individual management processing unit 33 甲 Since this is a report concerning the coordinated operation plan, it will be notified to server 3. The coordinated management processing unit 19 manages the completion of delivery request F. Since delivery request F relates to both A and B, the coordinated management processing unit 19 will notify operator device 5 甲 and operator equipment 5 乙 Distributed to, business device 5 丙 It will not be distributed to. Operator equipment 5 甲 and operator equipment 5 乙 This will track updates to the coordinated operation management for delivery request F.

[0137] Referring to Figure 14(d), driver B1 is instructed to load C's package and perform the delivery request L at time t 丙L It is indicated that the vehicle will depart from arrival trunk hub U by [time]. Once driver B1 has loaded C's cargo and departed from arrival trunk hub U, touch the "Complete" button displayed on the operator device 5. 乙 Report to the delivery request L that the work has been completed. (Business Equipment 5) 乙 Individual management processing unit 33 乙 Since this is a report concerning the coordinated operation plan, it will be notified to server 3. The coordinated operation processing unit 19 manages the completion of delivery request L. Since delivery request L relates to B and C, the coordinated operation processing unit 19 will notify operator device 5 乙 and operator equipment 5 丙 Distributed to, business device 5 甲 It will not be distributed to. Operator equipment 5 乙 and operator equipment 5 丙 This involves monitoring updates to the coordinated operation management for delivery request L.

[0138] Referring to Figure 14(e), driver A1 is instructed to perform the work for delivery request G at time t 乙G改 It is indicated that the cargo of Party B should arrive at the arrival trunk hub V by [time]. When driver A1 arrives at the arrival trunk hub V with Party B's cargo on board, touch the "Complete" button displayed on the operator's device 5 甲 Report to the delivery request G that the work has been completed. (Business Equipment 5) 甲 Individual management processing unit 33 甲 Since this is a report concerning the coordinated operation plan, it will be notified to server 3. The coordinated management processing unit 19 manages the completion of delivery request G. Since delivery request G relates to both A and B, the coordinated management processing unit 19 will notify operator device 5 甲 and operator equipment 5 乙 Distributed to, business device 5 丙 It will not be distributed to. Operator equipment 5 甲 and operator equipment 5 乙 This will track updates to the coordinated operation management for delivery request group.

[0139] Referring to Figure 14(f), driver A1 is instructed to load B's cargo for delivery request H at time t 乙H It is indicated that the vehicle will depart from arrival trunk hub V by [time]. Once driver A1 has loaded B's cargo and departed from arrival trunk hub V, touch the "Complete" button displayed on the operator device 5. 甲 Report to the recipient that the work for delivery request H has been completed. (Business Equipment 5) 甲 Individual management processing unit 33 甲 Since this is a report concerning the coordinated operation plan, it will be notified to server 3. The coordinated management processing unit 19 manages the completion of delivery request H. Since delivery request H relates to both A and B, the coordinated management processing unit 19 will notify operator device 5 甲 and operator equipment 5 乙 Distributed to, business device 5 丙 It will not be distributed to. Operator equipment 5 甲 and operator equipment 5 乙 This involves monitoring updates to the coordinated operation management for delivery request H.

[0140] Furthermore, when a worker of a transportation company inputs that they will perform coordinated logistics for a request, they may instruct whether or not to disclose the data related to the request to other logistics economic zones. Server 3 processes requests that it has instructed not to disclose in the same manner as described above, and for requests that it has instructed to disclose, it also discloses the data related to the request to the operator devices 5 of other logistics economic zones. [Explanation of Symbols]

[0141] 1. Integrated Logistics System 3 servers 5 Operator equipment 7 Operator equipment 11. Communication equipment 13 Processing Unit 15 Storage device 17. Collaboration Planning Processing Unit 18 Secret Management Department 19. Collaboration Management Processing Unit 21. Coordinated Operations Planning Department 23 Input / Output Devices 25 Communication equipment 27 Processing Unit 29 Storage device 31 Individual Planning Processing Unit 33 Individual Management Processing Unit 35 Individual Operation Planning Department 37 Input / Output Devices 39 Communication equipment 41 Processing Unit 43 Work Management Department

Claims

1. A collaborative logistics system for realizing logistics through the cooperation of multiple logistics economic zones, Equipped with a server and multiple operator devices, Each of the aforementioned operators' equipment is designed to accommodate different logistics economic zones. The aforementioned server comprises a coordination planning processing unit and a confidentiality management unit. The aforementioned collaboration planning processing unit manages data that identifies the collaboration operation plan and resources. The aforementioned collaborative planning processing unit creates the collaborative operation plan by assigning resources that are responsible for transportation based on requests in one logistics economic zone to also be responsible for transportation based on requests in a different logistics economic zone. The aforementioned confidentiality management department shall, with respect to the data identifying the aforementioned coordinated operation plan and resources, For the business equipment corresponding to the logistics economic zone that received the request, the portion related to the request will be distributed. For business devices in the logistics economic zone that are responsible for transportation but have not received the request, the transportation portion of the request will be distributed. A collaborative logistics system that does not distribute at least a portion of the data related to the request to operators and equipment in logistics economic zones that have not received the request and are not responsible for transportation.

2. The collaborative logistics system according to claim 1, wherein the collaborative planning processing unit coordinates delivery requests related to transportation in a given logistics economic zone with resources that are responsible for transportation in a given logistics economic zone, and has them handle transportation requests in a different logistics economic zone.

3. The collaborative logistics system includes an operator device that reports transportation operations related to the collaborative operation plan to the operator device. The aforementioned server is equipped with a collaborative management processing unit, The aforementioned operator's device includes an individual management processing unit, The individual management processing unit notifies the server of the report, The aforementioned collaborative management processing unit uses the aforementioned report to manage the operation of the collaborative operation plan. The aforementioned confidentiality department, with respect to the request for which it received the aforementioned report, The operational management information regarding the aforementioned report will be distributed to the operator's equipment corresponding to the logistics economic zone that received the request. Although they have not received the request, they will distribute the operational management information regarding the aforementioned report to the business equipment of the logistics economic zone that is responsible for transportation. The collaborative logistics system according to claim 1, wherein operation management related to the aforementioned report is not distributed to business operators' equipment corresponding to logistics economic zones that have not received the request and are not responsible for transportation.

4. A collaborative logistics method in a collaborative logistics system for realizing logistics through the cooperation of multiple logistics economic zones, The aforementioned collaborative logistics system includes a server and multiple operator devices. Each of the aforementioned operators' equipment is designed to accommodate different logistics economic zones. The aforementioned server comprises a coordination planning processing unit and a confidentiality management unit. The aforementioned collaboration planning processing unit manages data that identifies the collaboration operation plan and resources. The aforementioned collaborative planning processing unit creates a collaborative operation plan by assigning resources that are responsible for transportation based on requests in one logistics economic zone to also be responsible for transportation based on requests in a different logistics economic zone. The aforementioned confidentiality management department shall, with respect to the data identifying the aforementioned coordinated operation plan and resources, For the business equipment corresponding to the logistics economic zone that received the request, the portion related to the request will be distributed. For business devices in the logistics economic zone that are responsible for transportation but have not received the request, the transportation portion of the request will be distributed. A collaborative logistics method that includes a step of not distributing at least a portion of the data related to the request to business operators and equipment in logistics economic zones that have not received the request and are not responsible for transportation.

5. A program for causing a computer to function as the confidential information management unit described in claim 1.