Business support device, business support method, and business support program

Abstract

The system automatically associates the shipper with the transportation provider booked by the shipper. [Solution] The transport entity data generation unit generates transport entity data for each cargo transport entity, including transport entity information, receiving location, stopover locations, final destination, delivery deadline, and transport entity data identification number. The shipper data generation unit generates shipper data for each shipper, including transport entity information, receiving location, stopover locations, final destination, delivery deadline for the reserved transport entity, and a unique shipper data identification number for the transport entity reserved by the shipper. The detection unit detects transport entity data that matches the transport entity information, receiving location, stopover locations, final destination, and delivery deadline contained in each shipper data, respectively. The association data generation unit generates association data between shippers and transport entities, including the shipper data identification number of the shipper data and the transport entity data identification number of the transport entity data for which a match was detected.

Description

Technical Field

[0001] The present invention relates to a business support device, a business support method, and a business support program.

Background Art

[0002] Patent Document 1 (Japanese Patent Application Laid-Open No. 2024-103558) discloses a labor management system capable of accurately managing the labor of drivers and the like.

[0003] In paragraph 0150 of this Patent Document 1, a technique related to an input operation of an arrival time designated in advance by a shipper is disclosed, and it is also described that the designated arrival time may be an arrival time designated by an operator of a loading point or an unloading point. Further, in paragraph 0171 of Patent Document 1, it is described that when transporting the goods of different shippers to the same unloading point, the waiting time of each piece of goods is separated for each shipper.

[0004] Here, today, there are known freight forwarders who perform forwarding operations from the receipt of goods from shippers to the delivery to consignees through arrangements of transportation entities such as ships, airplanes, railways, or trucks that transport the goods.

[0005] Due to the business characteristics of this forwarding operation, charges for billing and costs are incurred in terms of transportation entities (Master units), and charges for billing and costs are also incurred in terms of shippers (House units). Therefore, in order to identify the transportation entities used by each shipper, it is necessary to associate and grasp each shipper and each transportation entity.

Prior Art Documents

Patent Documents

[0006]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0007] Previously, the association between each shipper and each transport entity was done manually, which led to problems such as input errors or omissions.

[0008] This invention has been made in view of the above-mentioned problems, and aims to provide a business support device, a business support method, and a business support program that enable the automatic association of each shipper with each transport entity. [Means for solving the problem]

[0009] To solve the above-mentioned problems and achieve the objectives, the business support device according to the present invention includes a transport entity data generation unit that generates transport entity data for each transport entity, including transport entity information uniquely assigned to the transport entity, receiving location, stopover locations, final destination, delivery deadline, and a unique transport entity data identification number, based on the operation schedule information of the transport entity that transports the goods, and shipper data reserved by the shipper requesting the transport of goods, including transport entity information of the transport entity that transports the goods, receiving location, stopover locations, final destination, delivery deadline of the reserved transport entity, and a unique shipper data identification number, for each shipper. The system includes: a shipper data generation unit that generates data; a detection unit equipped with a first detection pattern that detects transport entity data that matches the transport entity information, receiving location, stopover location, final destination, and delivery deadline included in each shipper data; an association data generation unit that generates association data indicating transport entity data related to the shipper data, including at least the shipper data identification number of the shipper data and the transport entity data identification number of the transport entity data for which a match has been detected; and an output control unit that outputs the association data to an output target device.

[0010] Furthermore, in order to solve the above-mentioned problems and achieve the objectives, the business support method according to the present invention comprises a transport entity data generation step in which a transport entity data generation unit generates transport entity data for each transport entity, including transport entity information uniquely assigned to the transport entity, receiving location, stopover locations, final destination, delivery deadline, and a unique transport entity data identification number, based on the operation schedule information of the transport entity that transports the goods; and a shipper data generation unit generates shipper data for each shipper, including transport entity information of the transport entity that transports the goods, receiving location, stopover locations, final destination, delivery deadline of the reserved transport entity, and a unique shipper data identification number, as reserved by the shipper requesting the transport of the goods. The system includes: a shipper data generation step; a detection step comprising a detection unit having a first detection pattern that detects transport entity data including transport entity information,

[0011] Furthermore, in order to solve the above-mentioned problems and achieve the objectives, the business support program according to the present invention comprises a transport entity data generation unit that generates transport entity data for each transport entity, including transport entity information uniquely assigned to the transport entity, receiving location, stopover locations, final destination, delivery deadline, and a unique transport entity data identification number, based on the operation schedule information of the transport entity that transports the goods, and shipper data reserved by the shipper requesting the transport of goods, including transport entity information of the transport entity that transports the goods, receiving location, stopover locations, final destination, delivery deadline of the reserved transport entity, and a unique shipper data identification number. The system includes a shipper data generation unit that generates data for each shipper, a detection unit equipped with a first detection pattern that detects transport entity data that matches the transport entity information, receiving location, stopover location, final destination, and delivery deadline included in each shipper data, respectively, an association data generation unit that generates association data indicating transport entity data related to the shipper data, including at least the shipper data identification number of the shipper data and the transport entity data identification number of the transport entity data for which a match has been detected, and an output control unit that outputs the association data to an output target device. [Effects of the Invention]

[0012] This invention can automatically associate a shipper with a transportation entity that has been booked by the shipper. [Brief explanation of the drawing]

[0013] [Figure 1] Figure 1 is a diagram showing the overall configuration of the system including the business support device of the embodiment. [Figure 2] Figure 2 is a block diagram showing the hardware configuration of the business support device according to the embodiment. [Figure 3] Figure 3 shows an example of a port master table. [Figure 4] Figure 4 shows an example of a ship master table. [Figure 5] Figure 5 shows an example of a customer master table. [Figure 6]FIG. 6 is a schematic diagram showing the operation flow from the import of the mother ship schedule information to the profit and loss confirmation of the business support device according to the embodiment. [Figure 7] FIG. 7 is a diagram showing an example of the mother ship schedule information import screen. [Figure 8] FIG. 8 is a diagram showing an example of the mother ship schedule information obtained by the MBL data generation unit. [Figure 9] FIG. 9 is a diagram showing an example of the MBL data generated by the MBL data generation unit. [Figure 10] FIG. 10 is a diagram showing an example of the web booking information import screen. [Figure 11] FIG. 11 is a diagram showing an example of the web booking information that is the source of the HBL data. [Figure 12] FIG. 12 is a diagram showing the coincidence detection result in the first detection pattern by the detection unit. [Figure 13] FIG. 13 is a diagram showing the coincidence detection result in the second detection pattern by the detection unit. [Figure 14] FIG. 14 is a diagram showing the coincidence detection result in the third detection pattern by the detection unit. [Figure 15] FIG. 15 is a diagram showing the coincidence detection result in the fourth detection pattern by the detection unit. [Figure 16] FIG. 16 is a diagram showing an example of the association data indicating the association between the shipper and the ship. [Figure 17] FIG. 17 is a diagram showing an example of the billing data generated by the billing data generation unit and indicating the amount to be billed to each shipper. [Figure 18] FIG. 18 is a diagram showing an example of the cost data generated by the cost data generation unit and indicating the amount (cost) to be paid to each transporter. [Figure 19] FIG. 19 is a diagram showing an example of the HBL profit and loss confirmation data for each shipper. [Figure 20] FIG. 20 is a diagram showing an example of the MBL profit and loss confirmation data for the shippers and each ship that incurred costs. [Figure 21]Figure 21 shows an example of the income and expense confirmation screen, which displays gross profit and gross profit margin. [Modes for carrying out the invention]

[0014] The following describes in detail, with reference to the drawings, an embodiment of the present invention applied to a terminal device of a transportation intermediary that performs forwarding operations (transportation intermediary operations) in which it receives requests from shippers to transport cargo by ship, reserves ships, and transports the shippers' cargo.

[0015] The present invention is not limited to the following embodiments. For example, in this example, the transport entity is described as a ship, but other transport entities such as aircraft, rail, or trucks can also be used. In any case, the same effects as described later can be obtained. For details, please refer to the following description.

[0016] (Overall structure) As shown in Figure 1, the business support device 1 of this embodiment is connected to a network 50, such as a wide-area network like the Internet or a private network like a LAN (Local Area Network), together with the shipper's terminal device 51, the transporter's terminal device 52 that transports goods by ship, and the web booking system server device 53.

[0017] The carrier accesses the web booking system server 53 via the carrier's terminal device 52 and registers the ship's operational information (date, port of pickup, port of loading, port of unloading, etc.). The shipper accesses the web booking system server 53 via the terminal device 51 and reserves the desired ship for transporting the cargo based on the operational information registered by the carrier.

[0018] The transportation intermediary obtains operational information from the web booking system server 53 or the transportation company's terminal 52 via the business support device 1, as well as the shipper's reservation information (web booking information). Then, it accesses the transportation company's terminal 52 and makes a reservation for the shipper's desired vessel on their behalf. As a result, the shipper's cargo is picked up from the receiving point and transported to the destination (discharge port) by the vessel reserved by the shipper.

[0019] The transportation intermediary calculates and bills the shipper for ocean freight and terminal handling charges, which are the costs of handling containers at the container terminal or during loading onto the vessel. The transportation intermediary also makes payments to the transportation company and the web booking system management company, etc., based on the amount paid by the shipper.

[0020] (Hardware configuration) Figure 2 shows the hardware configuration of the business support device 1 for a transportation intermediary. This embodiment of the business support device 1 includes a storage unit 2, a control unit 3, a communication interface unit 4, and an input / output interface unit 5. An input device 6 and an output device 7 are connected to the input / output interface unit 5. The output device 7 can be a display unit such as a monitor device (including a household television), a printing device, or a speaker device.

[0021] The input device 6 can include a keyboard, mouse, and microphone, as well as a monitor device that works in conjunction with the mouse to provide a pointing device function. The communication interface unit 4 is connected to the network 50 described above.

[0022] For the memory unit 2, a storage device such as ROM (Read Only Memory), RAM (Random Access Memory), HDD (Hard Disk Drive), or SSD (Solid State Drive) can be used.

[0023] The memory unit 2 stores a business support program that assists the operations of transportation intermediaries by automatically associating each shipper with each transportation entity. The memory unit 2 also includes the following storage areas: port master table 11, ship master table 12, trading partner master table 13, ship schedule information storage unit 14, web booking information storage unit 15, MBL data storage unit 16, and HBL data storage unit 17. The memory unit 2 also includes the following storage areas: association data storage unit 18, billing data storage unit 19, cost data storage unit 20, MBL revenue and expenditure confirmation data storage unit 21, HBL revenue and expenditure confirmation data storage unit 22, and revenue and expenditure confirmation screen data storage unit 23.

[0024] As shown in Figure 3, the port master table 11 stores the port code and port name for each port. In the example in Figure 3, the port code "JPOSA" is the port code for Osaka Port in Japan. The port code "JPUKB" is the port code for Kobe Port in Japan, and the port code "JPTYO" is the port code for Tokyo Port in Japan. The port code "JPYOK" is the port code for Yokohama Port in Japan, the port code "CNSHA" is the port code for Shanghai Port in the People's Republic of China, and the port code "INBOM" is the port code for Mumbai (formerly Bombay) in the Republic of India.

[0025] As shown in Figure 4, the ship master table 12 stores the unique ship code and ship name for each vessel. The codes shown in Figure 4, such as "XUKK6", "3FEE2", and "V3LS2", are the ship codes uniquely assigned to each vessel. The ship names for each vessel are "JI XIANG", "GLOBAL AQUA", and "HONG QIAO", etc.

[0026] As shown in Figure 5, the customer master table 13 stores the customer code and customer name uniquely assigned to each customer of the transportation intermediary. This example in Figure 5 shows that the transportation intermediary has business dealings with "○○ Co., Ltd." in Shanghai, whose customer code is "AGENTCNSHA," and also with "○○ Co., Ltd." in Hong Kong, whose customer code is "AGENTHKHKG."

[0027] (Functional configuration of business support equipment) Next, the control unit 3 executes the business support program stored in the storage unit 2, and functions as a data generation unit 31, a detection unit 32, and a display control unit 33 (an example of an output control unit), as shown in Figure 1. The data generation unit 31 includes the functions of an MBL data generation unit 34, an HBL data generation unit 35, an association data generation unit 36, a billing data generation unit 37, a cost data generation unit 38, an HBL income and expenditure confirmation data generation unit 39, an MBL income and expenditure confirmation data generation unit 40, and an income and expenditure confirmation screen data generation unit 41.

[0028] In this example, the data generation unit 31 to the income and expenditure confirmation screen data generation unit 41 are described as being implemented in software based on the business support program. However, all or part of the data generation unit 31 to the income and expenditure confirmation screen data generation unit 41 may be implemented in hardware. In either case, the same effects as described later can be obtained.

[0029] The MBL data generation unit 34 is an example of a transport entity data generation unit, and based on the operation schedule information of the transport entity (ship) that transports the cargo (see Figure 8), it generates transport entity data (MBL data) for each transport entity, which includes transport entity information uniquely assigned to the transport entity (ship code and navigation number shown in Figure 9), the place of receiving cargo, the port of call (loading port), the final destination (unloading port), the deadline for loading, and a unique transport entity data identification number (MBL No. in Figure 8) (see Figure 9).

[0030] The HBL data generation unit 35 is an example of a shipper data generation unit, and generates shipper data (HBL data) for each shipper, which includes the transporter information of the transporting entity that will transport the goods (ship code and navigation number in Figure 16), the receiving place, the port of call (loading port in Figure 16), the final destination (unloading port in Figure 16), the deadline for delivery by the transporting entity that has been reserved by the shipper requesting the transport of the goods, and a unique shipper data identification number (HBL No in Figure 16) (see Figure 16 in part).

[0031] The detection unit 32 detects transport entity data (MBL data) that includes transport entity information,

[0032] The association data generation unit 36 ​​generates association data indicating the transport entity data related to the shipper data, including at least the shipper data identification number (HBLNo shown in Figure 16) of the shipper data (HBL data) for which a match was detected and the transport entity data identification number (MBLNo shown in Figure 16) of the transport entity data (MBL data) (see Figure 16).

[0033] The output control unit outputs the associated data to the output target device. The output target device corresponds to, for example, the output device 7, and can be a display device, a printing device, or a speaker device. The output control unit converts the associated data into display information, print information, or audio information and supplies it to the corresponding device. This makes it possible to obtain display output, print output, or audio output of the associated data. In addition, the output target device can be the storage unit 2, an external storage device, or a server device on a network, and the associated data may be output to or transmitted to these devices for storage.

[0034] Next, in addition to the first detection pattern described above, the detection unit 32 includes, as an example, second to fourth detection patterns. Specifically, the detection unit 32 considers the stopover locations included in each shipper data (HBL data) to be the same land as the receiving location, and includes a second detection pattern that detects transport entity data that matches the transport entity information, receiving location, stopover locations, final destination, and delivery deadline included in each shipper data (see Figure 13).

[0035] Furthermore, the detection unit 32 includes a third detection pattern that detects transport entity data containing transport entity information, receiving location, stopping location, and delivery deadline that match the transport entity information, receiving location, stopping location, and delivery deadline included in each shipper data, excluding the final destination of the shipper data (HBL data) and transport entity data (MBL data) (see Figure 14).

[0036] Furthermore, the detection unit 32 includes a fourth detection pattern that, excluding the final destination of the shipper data (HBL data) and transporter data (MBL data), considers the stopover locations included in each shipper data to be the same land as the receiving location, and then detects transporter data that includes transporter information, receiving location, stopover locations, and delivery deadlines that match the transporter information, receiving location, stopover locations, and delivery deadlines included in each shipper data (see Figure 15).

[0037] Next, the billing data generation unit 37 generates billing data that includes the shipper data identification number and the billing amount for the transportation of each shipper's goods, which has been entered by the operator for each shipper data identification number (see Figure 17).

[0038] Furthermore, the cost data generation unit 38 generates cost data that includes the transport entity data identification number or shipper data identification number, the cost amount for each transport entity entered by the operator for each transport entity data identification number, and the cost amount for each shipper for which a cost was incurred, entered by the operator for each shipper data identification number (see Figure 18).

[0039] The shipper income and expenditure confirmation data generation unit (HBL income and expenditure confirmation data generation unit 39) is an example of a shipper income and expenditure confirmation data generation unit, and it generates shipper income and expenditure confirmation data (HBL income and expenditure confirmation data) by adding billing data and cost data with the same shipper data identification number to the associated data (see Figure 19).

[0040] Furthermore, the transportation entity profit and loss confirmation data generation unit (MBL profit and loss confirmation data generation unit 40) generates transportation entity profit and loss confirmation data (MBL profit and loss confirmation data) by adding billing data and cost data with the same transportation entity data identification number to the aforementioned association data (see Figure 16) (see Figure 20). The output control unit outputs the shipper profit and loss confirmation data and the transportation entity profit and loss confirmation data to the output target equipment.

[0041] Next, the revenue and expenditure confirmation data generation unit (revenue and expenditure confirmation screen data generation unit 41) generates revenue and expenditure confirmation data (revenue and expenditure confirmation screen data shown in Figure 21) that includes the gross profit amount obtained by subtracting the cost amount shown in the cost data from the invoice amount shown in the invoice data, and the gross profit margin which is the ratio of the invoice amount to the gross profit amount, along with the association data (see Figure 16), invoice data (see Figure 17), and cost data (see Figure 18) mentioned above. The output control unit outputs the revenue and expenditure confirmation data (revenue and expenditure confirmation screen data shown in Figure 21) to the output target device.

[0042] (Operation of business support equipment) Next, the operation of the business support device 1 of the embodiment will be described. Figure 6 shows the flow of operations of the business support device 1 of the embodiment from the acquisition of vessel schedule information to the confirmation of revenue and expenses. As shown in Figure 6, in step S1, the business support device 1 of the embodiment acquires vessel schedule information, and in step S2, it acquires web booking information and automatically generates association data that associates the shipper data (HBL data) of each shipper and the transport entity data (MBL data) of the vessels that transport the cargo of each shipper.

[0043] Then, in step S3, billing data and payment data related to this transportation are generated, as well as HBL (Housing Bank Balance) and MBL (Mobile Bank Balance) balance confirmation data. Furthermore, in step S4, gross profit and gross profit margin are calculated based on the billing data and cost data, and balance confirmation data with these added is generated.

[0044] (Step S1) The operation of each step will be explained in detail below. First, in step S1, the operator of the business support device 1 specifies the display of the ship schedule information acquisition screen. As a result, the display control unit 33 displays the ship schedule information acquisition screen shown in Figure 7 via the output device 7.

[0045] The vessel schedule information is information that shows the operating schedule of the vessels of the carriers that are business partners of the intermediary carrier (see the customer master table 13 in Figure 5). The control unit 3 may obtain this vessel schedule information from the carrier's terminal device 52, or the carrier may obtain the vessel schedule information registered in the web booking system server device 53 via the terminal device 52. Alternatively, the operator of the intermediary carrier may manually input the vessel schedule information.

[0046] Thus, the ship schedule information obtained from the transporter's terminal device 52 or the web booking system server device 53, or manually entered by the transporter's operator, is stored in the ship schedule information storage unit 14 by the control unit 3.

[0047] The operator of the transportation intermediary specifies the desired vessel schedule information via the vessel schedule information acquisition screen shown in Figure 7 and operates the execution button provided on the vessel schedule information acquisition screen. The MBL data generation unit 34 acquires the vessel schedule information specified by the transportation intermediary operator from the vessel schedule information storage unit 14.

[0048] Figure 8 shows an example of the acquired vessel schedule information. As shown in Figure 8, the vessel schedule information is acquired, including the port of receipt, port of loading, port of unloading, vessel code, voyage number, delivery deadline, port of arrival, port of departure, date of arrival at destination, and agent code (customer code).

[0049] In this case, cargo is not transported on the same vessel from the port of receipt to the port of unloading (the port of discharge), but is sometimes transshipped at an intermediate port. The "port of loading" is the intermediate port where this transshipment takes place.

[0050] Based on the acquired vessel schedule information, the MBL data generation unit 34 generates MBL data (vessel BL data) by adding a unique MBL number (MBLNo: transport entity data identification number) to each piece of vessel schedule information, including the port of receipt, port of loading, port of unloading, ship code, navigation number, loading deadline, port of arrival, departure date, destination arrival date, and agent code (customer code), as shown in Figure 9, and stores it in the MBL data storage unit 16.

[0051] (Step S2) Next, in step S2, the operator of the business support device 1 specifies the display of the web booking information import screen, which contains reservation information for the vessel that will transport the cargo made by the shipper. As a result, the display control unit 33 displays the web booking information import screen shown in Figure 10 via the output device 7.

[0052] The control unit 3 may obtain this web booking information from the web booking system's server device 53. Alternatively, an operator of a transportation intermediary may manually enter the web booking information by referring to the server device 53.

[0053] Thus, web booking information obtained from the web booking system server device 53, or manually entered by an operator of a transportation intermediary, is stored in the web booking information storage unit 15 by the control unit 3.

[0054] The operator of the transportation intermediary specifies the desired web booking information via the web booking information import screen shown in Figure 10 and operates the execution button provided on the web booking information import screen. The HBL data generation unit 35 acquires the web booking information specified by the operator of the transportation intermediary from the web booking information storage unit 15.

[0055] Figure 11 shows an example of acquired web booking information. As shown in Figure 11, web booking information is acquired that includes a web booking number generated for each shipper's reservation, the shipper's port of arrival, loading port, unloading port, ship code, voyage number, delivery deadline, and the agent code (customer code) of the shipper's agent.

[0056] The HBL data generation unit 35 generates HBL data (shipper data) for each shipper, including the web booking number, the receiving port, loading port, unloading port, ship code, voyage number, delivery deadline date, and agent code (customer code) of the vessel reserved by the shipper, based on the acquired web booking information, and stores it in the HBL data storage unit 17.

[0057] (Processing of linking shippers and vessels) Next, in step S2, the association data generation unit generates association data by associating HBL data (shipper data) for each shipper with MBL data (vessel BL data) of the vessel reserved by the shipper.

[0058] In this case, the detection unit 32 compares the HBL data (shipper data) for each shipper with the MBL data (vessel BL data) of the vessel reserved by the shipper, according to the first to fourth detection patterns, and detects a match between the two.

[0059] (First detection pattern) First, the detection unit 32 compares the "receiving location, loading port, unloading port, ship code, voyage number, delivery deadline, and agent code of the MBL data" shown in Figure 9 with the "receiving location, loading port, unloading port, ship code, voyage number, delivery deadline, and agent code of the HBL data" generated from the web booking information shown in Figure 11, as a first detection pattern. Then, it detects HBL data that perfectly matches this comparison.

[0060] In this example, as shown in Figure 12, the detection unit 32 detects the MBL data with the MBL number "TKMB24100001" as MBL data that matches the HBL data with web booking number "Booking001" as HBL data that perfectly matches the "place of receipt, loading port, unloading port, ship code, voyage number, delivery deadline date, and agent code of the MBL data".

[0061] Furthermore, the detection unit 32 detects the MBL data with the MBL number "TKMB24100002" as MBL data that matches the HBL data with web booking number "Booking002". The detection unit 32 also detects the MBL data with the MBL numbers "OSMB24100001" to "OSMB24100003" as MBL data that matches the HBL data with web booking numbers "Booking004" to "Booking006". Furthermore, the detection unit 32 detects the MBL data with the MBL number "OSMB24100004" as MBL data that matches the HBL data with web booking number "Booking009".

[0062] When MBL data matching HBL data is detected in this manner, the association data generation unit 36 ​​generates association data, as shown in Figure 16, which includes the HBL number and MBL number (see Figure 9) of the HBL data for which a match was detected, as well as the receiving port, loading port, unloading port, ship code, voyage number, delivery deadline, arrival date, departure date, local arrival date, agent code, and web booking number indicated in the MBL data, and stores this association data in the association data storage unit 18.

[0063] This allows for the automatic generation of association data between shippers and vessels, indicating the vessels reserved by the shippers. This association data can be displayed by the display control unit 33 via the output device 7 at a timing specified by the operator.

[0064] (Second detection pattern) Next, as shown in Figure 12, the results of detecting a match between the HBL data and MBL data using the first detection pattern show that the HBL data for "Booking003", "Booking007", "Booking008", and "BookingE01" do not match the MBL data.

[0065] In this case, the detection unit 32 detects a match between the mismatched HBL data and the MBL data using a second detection pattern that considers the receiving location to be the same land as the loading port. Since the shipper's request is from receiving location to delivery location, when there are multiple receiving locations, this second detection pattern can be used to detect MBL data that matches the HBL data. Figure 13 shows the detection results using this second detection pattern.

[0066] In this case, the detection unit 32 considers the receiving location to be the same place as the loading port, and compares the "receiving location, loading port, unloading port, ship code, voyage number, delivery deadline date, and agent code of the HBL data" with the "receiving location, loading port, unloading port, ship code, voyage number, delivery deadline date, and agent code of the MBL data" to detect a match between the two.

[0067] In the example in Figure 13, the HBL data for "Booking003" matches the MBL data for the MBL number "TKMB24100002" as a result of considering the receiving location as the same land as the loading port.

[0068] Therefore, as shown in Figure 16, the association data generation unit 36 ​​generates association data that includes the HBL number "TKHB24100003" and the MBL number "TKMB24100002" (see Figure 9) of the HBL data for "Booking003" in which a match was detected, as well as the receiving location, loading port, unloading port, ship code, voyage number, delivery deadline, arrival date, departure date, local arrival date, agent code, and web booking number indicated in the MBL data, and stores it in the association data storage unit 18.

[0069] (Third detection pattern) Next, as shown in Figure 13, the results of detecting the match between HBL data and MBL data using the second detection pattern show that the HBL data for "Booking007", "Booking008", and "BookingE01" do not match the MBL data.

[0070] In this case, the detection unit 32 detects a match between the mismatched HBL data and the MBL data using a third detection pattern that excludes "port of unloading". Since the shipper's request is from the receiving location to the delivery location, when there are multiple delivery locations due to transshipment, etc., this third detection pattern can be used to detect MBL data that matches the HBL data. Figure 14 shows the detection results using this third detection pattern.

[0071] In this case, the detection unit 32 compares the "place of receipt, port of loading, ship code, voyage number, delivery deadline date, and agent code of the HBL data" with the "place of receipt, port of loading, ship code, voyage number, delivery deadline date, and agent code of the MBL data," excluding the "port of unloading," and detects a match between the two.

[0072] In the example in Figure 14, after removing "Port of Arrival," the HBL data for "Booking007" matches the MBL data for the MBL number "OSMB24100003."

[0073] Therefore, as shown in Figure 16, the association data generation unit 36 ​​generates association data that includes the HBL number "OSHB24100004" and the MBL number "OSMB24100003" (see Figure 9) of the HBL data for "Booking007" in which a match was detected, as well as the receiving port, loading port, unloading port, ship code, voyage number, delivery deadline, arrival date, departure date, local arrival date, agent code, and web booking number indicated in the MBL data, and stores this association data in the association data storage unit 18.

[0074] (Fourth detection pattern) Next, as shown in Figure 14, the third detection pattern detected a match between the HBL data and the MBL data, and it was found that the HBL data for "Booking008" and the HBL data for "BookingE01" did not match the MBL data.

[0075] In this case, the detection unit 32 considers the receiving location to be the same land as the loading port for the mismatched HBL data, and detects a match with the MBL data using a fourth detection pattern that excludes "unloading port". This is a detection pattern that combines the second and third detection patterns described above. Figure 15 shows the detection results using this fourth detection pattern.

[0076] In this case, the detection unit 32 considers the receiving location to be the same place as the loading port, and, excluding the "unloading port," compares the "receiving location, loading port, ship code, voyage number, delivery deadline date, and agent code of the HBL data" with the "receiving location, loading port, ship code, voyage number, delivery deadline date, and agent code of the MBL data" and detects a match between the two.

[0077] In the example in Figure 15, the receiving location is considered to be the same land as the loading port, and the "unloading port" is excluded. As a result, the HBL data for "Booking008" matches the MBL data for the MBL number "OSMB24100003".

[0078] Therefore, as shown in Figure 16, the association data generation unit 36 ​​generates association data that includes the HBL number "OSHB24100005" and the MBL number "OSMB24100003" (see Figure 9) of the HBL data for "Booking008" in which a match was detected, as well as the receiving port, loading port, unloading port, ship code, voyage number, delivery deadline, arrival date, departure date, local arrival date, agent code, and web booking number indicated in the MBL data, and stores it in the association data storage unit 18.

[0079] Furthermore, the detection unit 32 detects HBL data that does not match the MBL data in any of the first to fourth detection patterns, such as the HBL data for "BookingE01" shown in Figure 15, as error data. This error data is stored in the storage unit 2. The display control unit 33 displays the occurrence of error data via the output device 7. Subsequently, the detection unit 32 performs the above-mentioned match detection process excluding this error data. By performing the above-mentioned match detection process excluding the error data in this way, unnecessary match processing is avoided, and the match detection process can be completed quickly.

[0080] (Step S3) Next, in step S3, billing data and cost data for the consignor are generated in response to the operator's input. Based on this billing data and cost data, HBL (Housing Bank Balance) balance confirmation data is generated to verify the balance for each consignor, and MBL (Mobile Bank Balance) balance confirmation data is generated to verify the balance for each transporter.

[0081] Specifically, the operator enters the invoice amount for ocean freight and terminal handling charges, etc., into a billing data input screen (not shown), using the HBL number of each shipper, such as "TKHB24100001" or "TKHB24100002," as the invoice number. Terminal handling charges are the costs of handling the container, such as at the container terminal or during loading onto the vessel.

[0082] The billing data generation unit 37 generates billing data as exemplified in Figure 17 based on the operator's input and stores it in the billing data storage unit 19. This billing data can be displayed by the display control unit 33 via the output device 7 at a timing specified by the operator.

[0083] Furthermore, the operator uses the HBL number of each shipper, such as "OSHB24100004" and "OSMB24100005", as the invoice number and enters the cost amount for transshipment fees, etc., via a cost data input screen (not shown). Additionally, the operator uses the MBL number of each carrier, such as "OSHB24100004" and "OSMB24100002", as the invoice number and enters the cost amount for ocean freight, etc., via a cost data input screen (not shown).

[0084] The cost data generation unit 38 generates cost data showing the costs incurred for each shipper and each carrier, as illustrated in Figure 18, based on the operator's input, and stores it in the cost data storage unit 20. This cost data can be displayed by the display control unit 33 via the output device 7 at a timing specified by the operator.

[0085] Next, the HBL revenue and expenditure confirmation data generation unit 39 calculates the total amount of invoices for the same shipper by adding up the invoice amounts for each invoice data with the same slip number (=same HBL number) shown in Figure 17. In addition, the HBL revenue and expenditure confirmation data generation unit 39 detects the HBL number of each shipper and the MBL number of the vessel associated with each shipper's HBL number by referring to the association data shown in Figure 16.

[0086] Furthermore, the HBL revenue and expenditure confirmation data generation unit 39 detects the corresponding invoice amount and cost for each detected combination of HBL number and MBL number from the aforementioned invoice data and cost data. The HBL revenue and expenditure confirmation data generation unit 39 then generates HBL revenue and expenditure confirmation data, including the corresponding invoice amount and cost, for each detected combination of HBL number and MBL number.

[0087] Figure 19 shows an example of this HBL (Housing-Based Lending) balance confirmation data. As shown in Figure 19, the HBL balance confirmation data generation unit 39 generates HBL balance confirmation data that shows the HBL number for each shipper, the MBL number of the vessel used by each shipper, the total amount billed to each shipper, and the costs incurred for each shipper, and stores this data in the HBL balance confirmation data storage unit 22. This HBL balance confirmation data can be displayed by the display control unit 33 via the output device 7 at a timing specified by the operator.

[0088] In the HBL revenue and expenditure confirmation data shown in Figure 19, the HBL revenue and expenditure confirmation data for HBL number "OSHB24100004" and MBL number "OSMB24100003" in the third row from the bottom shows that the invoiced amount was "42,040 yen" and that a transshipment cost of "2,800 yen" was incurred. Similarly, in the HBL revenue and expenditure confirmation data shown in Figure 19, the HBL revenue and expenditure confirmation data for HBL number "OSHB24100005" and MBL number "OSMB24100003" in the second row from the bottom shows that the invoiced amount was "37,836 yen" and that a transshipment cost of "2,520 yen" was incurred.

[0089] Next, the MBL revenue and expenditure confirmation data generation unit 40 detects the cost data for each voucher number corresponding to the MBL number of the vessel from among the cost data shown in Figure 18. The MBL revenue and expenditure confirmation data generation unit 40 also detects the invoice data for the vessel (invoice data where the MBL number is the voucher number) from among the invoice data shown in Figure 17. In the example of Figure 17, there is no invoice data where the MBL number is the voucher number. In other words, in this example, there is no invoice amount for each vessel to the carrier.

[0090] Furthermore, the MBL revenue and expenditure confirmation data generation unit 40 refers to the association data shown in Figure 16 and detects the number of HBL data (= number of shippers) associated with the same MBL number for the same vessel.

[0091] Then, as shown in Figure 20, the MBL revenue and expenditure confirmation data generation unit 40 generates MBL revenue and expenditure confirmation data for each MLB number of each vessel, including the billing amount, cost, and the number of HBL data (= number of shippers) as the HBL count, and stores it in the MBL revenue and expenditure confirmation data storage unit 21. This MBL revenue and expenditure confirmation data can be displayed by the display control unit 33 via the output device 7 at a timing specified by the operator.

[0092] In the example shown in Figure 20, by referring to the association data shown in Figure 16 based on the MBL number "OSMB24100003", it can be seen that a total of three HBL numbers, "OSHB24100003" to "OSHB24100005", are associated with the MBL number "OSMB24100003". In this case, the MBL balance confirmation data generation unit 40 generates MBL balance confirmation data with the number of HBLs for the MBL number "OSMB24100003" set to "3", as shown in Figure 20.

[0093] Similarly, by referring to the association data shown in Figure 16 based on the MBL number "TKMB24100002", it can be seen that a total of two HBL numbers, "TKHB24100002" and "TKHB24100003", are associated with this MBL number "TKMB24100002". In this case, the MBL balance confirmation data generation unit 40 generates MBL balance confirmation data with the number of HBLs for the MBL number "TKMB24100002" set to "2", as shown in Figure 20.

[0094] (Step S4) Next, in step S4, the revenue and expenditure confirmation screen data generation unit 41 generates revenue and expenditure confirmation screen data that allows for the confirmation of revenue and expenditure for each consignor.

[0095] Specifically, when the operator requests the display of the revenue and expenditure confirmation screen, the display control unit 33 displays a revenue and expenditure confirmation screen (not shown) via the output device 7. This revenue and expenditure confirmation screen has an input field for the departure date. The operator enters the departure date of the vessel to be used in calculating the revenue and expenditure confirmation data (for example, from October 1, 2024 to October 31, 2024) into this departure date input field.

[0096] The revenue and expenditure confirmation screen data generation unit 41 refers to the association data shown in Figure 16 and detects association data entered by the operator that have a departure date between October 1, 2024 and October 31, 2024. In the example in Figure 16, all the association data are association data where the entered date is the departure date.

[0097] Next, the revenue and expenditure confirmation screen data generation unit 41 calculates the invoice amount, cost amount, gross profit, and gross profit margin for each shipper by performing the following calculations.

[0098] Invoice amount = Invoice amount for HBL data + (Invoice amount for MBL data / Number of HBL entries in MBL data) Cost = Cost of HBL data + (Cost of MBL data / Number of HBL entries in MBL data) Gross profit = Invoice amount - Cost amount Gross profit margin (%) = (Gross profit / Amount invoiced) × 100

[0099] For example, in the case of a shipper with HBL number "OSHB24100004", the revenue and expenditure confirmation screen data generation unit 41 refers to the HBL revenue and expenditure confirmation data shown in Figure 19 and the MBL revenue and expenditure confirmation data shown in Figure 20, and calculates the invoice amount by performing the following calculation.

[0100] Total amount billed = 42,040 yen + 0 yen = 42,040 yen

[0101] Furthermore, in the case of a shipper with HBL number "OSHB24100004", the revenue and expenditure confirmation screen data generation unit 41 refers to the cost data shown in Figure 20 and calculates the cost amount by performing the following calculation.

[0102] Cost = 2,800 yen + (94,116 yen / 3 items) = 34,172 yen

[0103] Furthermore, the revenue and expenditure confirmation screen data generation unit 41 calculates a gross profit of 7,868 yen for the shipper "OSHB24100004" by subtracting the calculated "34,172 yen" from the calculated invoice amount of "42,040 yen".

[0104] Furthermore, the revenue and expenditure confirmation screen data generation unit 41 calculates a gross profit of "18.72%" for the shipper "OSHB24100004" by dividing the calculated gross profit of "7,868 yen" by the calculated invoice amount of "42,040 yen" and multiplying by "100". (Rounded to the third decimal place or less.)

[0105] Next, the revenue and expenditure confirmation screen data generation unit 41 refers to the association data shown in Figure 16 and generates revenue and expenditure confirmation data for each shipper (for each shipper's HBL number), including the shipper's HBL number, the MBL number of the vessel transporting the shipper's cargo, the loading port, unloading port, ship code, voyage number, departure date, billing amount to the shipper, cost, gross profit, and gross profit margin, as shown in Figure 16, and stores it in the revenue and expenditure confirmation screen data storage unit 23.

[0106] The display control unit 33 reads the revenue and expenditure confirmation screen data stored in the revenue and expenditure confirmation screen data storage unit 23 at a timing specified by the operator and displays it via the output device 7. As a result, as shown in Figure 21, the revenue and expenditure confirmation screen corresponding to the departure date specified by the operator (for example, October 1, 2024 to October 31, 2024) can be displayed. Based on this revenue and expenditure confirmation screen, the operator recognizes the billing amount, cost, gross profit, and gross profit margin for each shipper and makes management decisions.

[0107] (Effects of the embodiment) As is clear from the above description, the business support device 1 of this embodiment can automatically associate each shipper with each transport entity, thereby preventing input errors or omissions. This enables rapid verification of revenue and expenses.

[0108] [Contribution to the United Nations-led Sustainable Development Goals (SDGs)] This invention can contribute to improving operational efficiency and promoting appropriate management decisions by companies, and therefore can contribute to SDGs Goals 8 and 9.

[0109] Furthermore, this invention can contribute to reducing waste and promoting paperless and digital processes, thereby contributing to SDGs Goals 12, 13, and 15.

[0110] Furthermore, this invention can contribute to strengthening control and governance, and therefore can contribute to achieving the 16 goals of the SDGs.

[0111] [Other embodiments] The present invention can be implemented in various different forms within the scope of the technical idea described in the claims, even in embodiments other than those described above.

[0112] For example, among the processes described in the embodiments, all or part of the processes described as being performed automatically may be performed manually. Alternatively, all or part of the processes described as being performed manually may be performed automatically by known methods or the like.

[0113] Furthermore, unless otherwise specified, the processing procedures, control procedures, specific names, registration data for each process, information including parameters such as search conditions, screen examples, and database configuration shown in the specification or drawings can be arbitrarily changed.

[0114] Furthermore, with respect to the business support device 1, each component shown in the diagram is a functional concept and does not necessarily have to have the physical configuration shown. For example, the processing functions of the business support device 1, particularly the processing functions performed by the control unit 3, may be implemented in whole or in any part by a program interpreted and executed by the control unit 3 (CPU: Central Processing Unit), or by hardware using wired logic.

[0115] The program is recorded on a non-temporary, computer-readable recording medium containing programmed instructions for the information processing device to execute the processes described in the embodiment, and is mechanically read by the business support device 1 as needed. In other words, the storage unit 2, such as ROM or HDD, records a computer program that works in cooperation with the OS (Operating System) to give instructions to the control unit 3 (CPU) and perform various processes. This computer program is loaded into RAM, unpacked, and executed by the control unit 3 as appropriate.

[0116] Furthermore, the business support program for this business support device 1 may be stored on another server device connected to the business support device 1 via any network, and all or part of it may be downloaded and executed as needed.

[0117] Furthermore, the business support program for executing the processes described in the embodiment may be stored on a non-temporary computer-readable recording medium, or it may be configured as a program product.

[0118] Here, any "portable physical medium" can be used as the "recording medium," such as memory cards, USB (Universal Serial Bus) memory, SD (Secure Digital) cards, flexible disks, magneto-optical disks, ROMs, EPROMs (Erasable Programmable Read Only Memory), EEPROMs (Registered Trademark) (Electrically Erasable and Programmable Read Only Memory), CD-ROMs (Compact Disk Read Only Memory), MOs (Magneto-Optical Disks), DVDs (Digital Versatile Disks), and Blu-ray (Registered Trademark) Discs.

[0119] Furthermore, "program" refers to a data processing method written in any language or writing method, regardless of its format, such as source code or binary code.

[0120] Furthermore, the term "program" is not necessarily limited to a single, monolithic entity, but also includes those that are distributed as multiple modules or libraries, and those that work in cooperation with other programs, such as an operating system, to achieve their functions.

[0121] Furthermore, for the specific configuration, reading procedure, and post-reading installation procedure for the business support device 1 of the embodiment, well-known configurations or procedures can be used.

[0122] The storage unit 2 is a storage means such as a memory device like RAM or ROM, a fixed disk device like a hard disk, a flexible disk, and an optical disk, and stores various programs, tables, databases, and web page files used for various processing or website provision.

[0123] Furthermore, the business support device 1 may be composed of a known personal computer device or an information processing device such as a workstation, or it may be composed of an information processing device to which any peripheral devices are connected. In addition, the information processing device may be implemented by implementing software (including programs or data, etc.) that realizes the processing described in the embodiment.

[0124] Furthermore, the specific forms of distribution and integration of the devices are not limited to those shown in the figures, and all or part of them can be configured by functionally or physically distributing or integrating them in any unit according to various additions or functional loads. In other words, the embodiments described above can be selectively implemented by arbitrarily combining the embodiments described above. [Industrial applicability]

[0125] The present invention is particularly suitable for use in the transportation management operations of transportation companies or transportation intermediaries that transport goods by land using automobiles or trucks, by sea using ships, or by air using aircraft. [Explanation of Symbols]

[0126] 1. Business support device for transportation intermediaries 2 Storage section 3. Control Unit 4. Communication Interface Section 5 Input / Output Interface Section 6 Input devices 7 Output device 11 Port Master Table 12 Ship Master Table 13. Customer Master Table 14. Ship's Schedule Information Storage Unit 15 Web booking information storage unit 16 MBL data storage unit 17 HBL Data Storage Unit 18. Associated data storage unit 19. Billing Data Storage Unit 20 Cost Data Storage Unit 21 MBL Income and Expenditure Confirmation Data Storage Unit 22 HBL Income and Expenditure Confirmation Data Storage Unit 23. Income and Expense Confirmation Screen Data Storage Unit 31 Data Generation Unit 32 Detection unit 33 Display Control Unit 34 MBL Data Generation Unit 35 HBL Data Generation Unit 36. Association Data Generation Unit 37. Billing Data Generation Department 38 Cost Data Generation Department 39. HBL Income and Expenditure Confirmation Data Generation Unit 40 MBL Income and Expenditure Confirmation Data Generation Unit 41. Data generation unit for the income and expenditure confirmation screen. 50 Networks 51. Shipper's terminal equipment 52 Terminal equipment for transporters 53. Server equipment for web booking systems

Claims

1. A transport entity data generation unit generates transport entity data for each transport entity, including transport entity information uniquely assigned to the transport entity, receiving location, stopover locations, final destination, delivery deadline, and a unique transport entity data identification number, based on the transport entity's operational schedule information. A shipper data generation unit generates shipper data for each shipper, including the shipper information of the transporting entity that transports the goods, the receiving location, the stopover locations, the final destination, the deadline for delivery by the transporting entity as reserved by the shipper requesting the transport of the goods, and a unique shipper data identification number. A detection unit comprising a first detection pattern for detecting the transporter data including the transporter information, The system includes an association data generation unit that generates association data indicating transporter data related to shipper data, including at least the shipper data identification number of the shipper data and the transporter data identification number of the transporter data in which a match was detected, An output control unit that outputs the aforementioned association data to the output target device, A business support device having the following features.

2. The detection unit includes a second detection pattern that considers the stopover location included in each of the shipper data to be the same land as the receiving location, and detects the transporter data including the transporter information, receiving location, stopover location, final destination, and delivery deadline that match the transporter information, receiving location, stopover location, final destination, and delivery deadline included in each of the shipper data, respectively. The business support device according to claim 1, characterized by the following:

3. The detection unit includes a third detection pattern for detecting the transporter data, which includes the transporter information, the receiving location, the stopover location, and the delivery deadline, respectively, that match the transporter information, the receiving location, the stopover location, and the delivery deadline included in each of the shipper data, excluding the final destination of the shipper data and the transporter data. A business support device according to claim 1 or claim 2, characterized by the above.

4. The detection unit includes a fourth detection pattern that detects the transporter data containing the transporter information, the receiving location, the stopping location, and the delivery deadline, respectively, which are the same location as the receiving location, with the exception of the final destination location in the consignor data and the transporter data. The business support device according to claim 3, characterized by the following:

5. A billing data generation unit generates billing data including the aforementioned shipper data identification number and the billing amount for the transportation of each shipper's goods entered by the operator for each of the aforementioned shipper data identification numbers, A cost data generation unit generates cost data including the transport entity data identification number or the shipper data identification number, the cost amount for each transport entity entered by the operator for each transport entity data identification number, and the cost amount for the shipper incurring costs, entered by the operator for each shipper data identification number. A shipper income and expenditure confirmation data generation unit generates shipper income and expenditure confirmation data by adding the invoice data and cost data with the same shipper data identification number to the associated data, The system further includes a transportation entity revenue and expenditure confirmation data generation unit that generates transportation entity revenue and expenditure confirmation data by adding the same transportation entity data identification number to the associated data, the billing data and cost data. The output control unit outputs the consignor revenue and expenditure confirmation data and the transporter revenue and expenditure confirmation data to the output target equipment. The business support device according to claim 4, characterized by the following:

6. The system further comprises a revenue and expenditure confirmation data generation unit that generates revenue and expenditure confirmation data including, together with the association data, the billing data and the cost data, a gross profit amount obtained by subtracting the cost amount shown in the cost data from the billing amount shown in the billing data, and a gross profit margin which is the ratio of the billing amount to the gross profit amount, The output control unit outputs the balance confirmation data to the output target device. The business support device according to claim 5, characterized by the following:

7. A transport entity data generation step involves a transport entity data generation unit generating transport entity data for each transport entity, based on the transport entity's operational schedule information, including transport entity information uniquely assigned to the transport entity, receiving location, stopover locations, final destination, delivery deadline, and a unique transport entity data identification number. The shipper data generation step involves the shipper data generation unit generating shipper data for each shipper, including the shipper information of the transporting entity that transports the goods as reserved by the shipper requesting the transport of the goods, the receiving location, the stopover locations, the final destination, the deadline for delivery by the reserved transporting entity, and a unique shipper data identification number. A detection step comprising a detection unit that detects the transport entity data including the transport entity information, the transport destination, the transport destination, the transport destination, and the transport deadline, which respectively match the transport entity information, the transport destination, the transport destination, the transport deadline included in each of the shipper data, The association data generation unit generates association data indicating transporter data related to the shipper data, which includes at least the shipper data identification number of the shipper data and the transporter data identification number of the transporter data for which a match was detected. The output control unit performs an output control step in which it outputs the associated data to the output target device, A business support method that has the following characteristics.

8. Computers, A transport entity data generation unit generates transport entity data for each transport entity, including transport entity information uniquely assigned to the transport entity, receiving location, stopover locations, final destination, delivery deadline, and a unique transport entity data identification number, based on the transport entity's operational schedule information. A shipper data generation unit generates shipper data for each shipper, including the shipper information of the transporting entity that transports the goods, the receiving location, the stopover locations, the final destination, the deadline for delivery by the transporting entity as reserved by the shipper requesting the transport of the goods, and a unique shipper data identification number. A detection unit comprising a first detection pattern for detecting the transporter data including the transporter information, The system includes an association data generation unit that generates association data indicating transporter data related to shipper data, including at least the shipper data identification number of the shipper data and the transporter data identification number of the transporter data in which a match was detected, Output control unit outputs the associated data to the target device. A business support program designed to function as such.

Images