Harbor work support system, harbor work support method, and harbor work support program

Abstract

To provide a technique for supporting a procedure related to port business and supporting progress management of the whole business.SOLUTION: Registration of basic information corresponding to a business type of port business is received, the basic information is associated with identification information, one or a plurality of business flows corresponding to the business type are stored, the identification information is acquired, and procedure processing corresponding to a status of the business flow is executed for an object specified by the identification information.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present invention relates to a port operation support system, a port operation support method, and a port operation support program. [Background technology]

[0002] Traditionally, procedures and documentation related to customs clearance and port entry / departure operations in the maritime transport business have been carried out manually or through separate systems, which has led to inefficient information sharing between the parties involved, resulting in frequent delays in procedures and incomplete documentation.

[0003] To solve these problems, a system that facilitates information sharing among all parties involved (shippers, ocean freight forwarders, customs brokers, warehouse operators, land transport companies, container terminals, and shipping companies) was needed. In recent years, digital platforms to achieve this have been developed and are being introduced. These platforms allow all parties involved to access information via the Internet and share information in real time.

[0004] Patent Document 1 discloses a port-related data sharing infrastructure system. This system has an authority setting table in which a computer grants access to and write permissions for each document based on business patterns. This allows shippers, freight forwarders, customs brokers, warehouse operators, land transport companies, container terminals, and shipping companies to input new request information, select transaction types, confirm patterns, determine authorized personnel, and view information. In particular, the system is designed so that only authorized personnel can access document information, strengthening security.

[0005] Patent Document 2 discloses a technology for highly accurate search of arrival schedule information for imported cargo at a port of discharge. This patent document describes a means by which an import cargo tracing device acquires cargo details, customs clearance information, and ship operation information based on cargo identification information, and extracts arrival schedule information from this information. Specifically, the patent document describes a method for acquiring necessary information from a cargo details database, a customs clearance information database, and a ship operation information database, and combining them to provide highly accurate arrival schedule information. This technology makes it possible to more accurately grasp the arrival schedule of cargo in port operations. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] Patent Publication No. 2021-189488 [Patent Document 2] Japanese Patent Application Laid-Open No. 2016-016979 Summary of the Invention [Problem to be solved by the invention]

[0007] Patent Document 1 discloses that document information can be shared between clients and traders. However, there is insufficient cooperation between the container logistics platform and other platforms, and there are issues in terms of improving operational efficiency, such as the difficulty of grasping the progress of port operations as a whole.

[0008] Patent Document 2 discloses that it is possible to search for information on the expected arrival of cargo at the port of discharge. However, it does not disclose how the acquired expected arrival information can be used in conjunction with other platforms, which poses a problem in terms of improving the efficiency of port operations overall.

[0009] The present invention aims to provide a technology for supporting procedures related to port operations and managing the progress of the entire operation. [Means for solving the problem]

[0010] [1] A port business support system comprising: a registration unit that accepts registration of basic information according to the type of port business and links it to identification information; a memory unit that stores one or more business flows corresponding to the business type; an acquisition unit that acquires the identification information; and a procedure processing unit that executes procedure processing according to the status of the business flow for an object identified by the identification information. [2] The procedural processing unit generates procedural documents according to the status of the business flow based on the basic information and executes procedural processing to submit the procedural documents, in the port business support system described in [1]. [3] The port business support system described in [2], wherein the memory unit stores a verification check table and is equipped with a verification unit that refers to the verification check table and verifies specific items of the procedural documents. [4] A port business support system described in any of [1] to [3], in which the status of the business flow is linked to one or more procedural information, and the procedural processing unit updates the status by completing the procedural processing of all necessary procedures of the procedural information. [5] A port business management system described in any of [1] to [4], which is equipped with an output unit that generates a progress management screen for the business flow according to the status of the business flow identified by the identification information. [6] A port business support system described in any of [1] to [5], wherein the registration unit links basic export / import information with identification information of the luggage, the identification information of the luggage being physically attached to the luggage as a two-dimensional code or an electronic tag, and the acquisition unit acquires the identification information of the luggage by reading the two-dimensional code or the electronic tag via a reading device. [7] A port operation support system described in any of [1] to [6], wherein the registration unit links basic information of port entry and departure operations with identification information of the ship, the basic information including port information, and the acquisition unit acquires the identification information of the ship by detecting the location information of the ship within a specified area set in the port information.

[0011] The invention of [1] can assist in carrying out appropriate procedures according to the status corresponding to the type of business.

[0012] The invention related to [2] makes it possible to automatically generate procedural documents according to the status of the business flow, thereby enabling procedures to be carried out efficiently.

[0013] [3] The invention of the present invention allows specific items of procedural documents to be verified using a verification check table, thereby improving the accuracy of document drafts.

[0014] The invention of [4] makes it possible to appropriately update the status of the business flow according to the procedural processing of the procedural information.

[0015] The invention related to [5] generates a screen display according to the status, and supports progress management of port operations by visualizing progress.

[0016] [6] The invention of the present invention allows for appropriate and efficient procedures to be carried out according to the actual state of the package by reading the identification information physically attached to the package.

[0017] The invention in [7] makes it possible to detect the approach of a ship to a port and to carry out appropriate and efficient procedures according to the actual situation of the ship. [Effects of the Invention]

[0018] According to the present invention, it is possible to support procedures related to port operations and provide a technology for managing the progress of the entire operation. [Brief explanation of the drawings]

[0019] [Figure 1] FIG. 1 is a block diagram of a system according to an embodiment of the present invention. [Figure 2] FIG. 2 is a diagram illustrating a hardware configuration of the present embodiment. [Figure 3] FIG. 1 is a schematic diagram of port operations according to an embodiment of the present invention. [Figure 4] FIG. 2 is a block diagram of the device and storage unit of the present embodiment. [Figure 5] FIG. 2 is a schematic diagram of a business flow according to the present embodiment. [Figure 6] 10 shows an example of the data configuration of business flow information according to the present embodiment. [Figure 7] 10 shows an example of the data configuration of progress management information for a package according to the present embodiment. [Figure 8] 3 shows an example of the data configuration of progress management information for port entry / departure operations in this embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0020] The following describes a port operation support system and a port operation support method according to an embodiment of the present invention, with reference to the accompanying drawings. Note that the embodiment shown below is an example of the present invention, and the present invention is not limited to the embodiment below, and various configurations can be adopted.

[0021] In this embodiment, the configuration, operation, etc. of a port operation support system and a port operation support device are described, but a port operation support method, a computer program, and a program recording medium on which the program is recorded, each having a similar configuration, also achieve the same effects. For example, by using a program recording medium, the program can be installed on a computer. The series of processes according to this embodiment described below are provided as a computer-executable program, and can be provided via a non-transitory computer-readable recording medium such as a CD-ROM or a flexible disk, or even via a communication line.

[0022] The port operation support system is composed of multiple computer devices. The first computer device has an arithmetic device such as a CPU (Central Processing Unit) and a storage device. The computer device can function as a port operation support device by executing a first program stored in the storage device using the arithmetic device. The second computer device has an arithmetic device such as a CPU and a storage device. The computer device can function as a user terminal by executing a second program stored in the storage device using the arithmetic device. The port operation support method is realized by processing of the computer devices including the port operation support device and the user terminal.

[0023] Port operations in this explanation include import / export operations and port arrival / departure operations. Import / export operations include reservation operations for ships, containers, various businesses, etc., and logistics operations such as carrying in cargo, customs clearance, loading, and transportation. Port arrival / departure operations include various arrangements and application procedures related to ships' arrival and departure from the port.

[0024] FIG. 1 shows a block diagram of a port operations support system 1. The port operations support system 1 comprises a port operations support device 2, a user terminal 3, and a memory unit 5. The port operations support device 2, the user terminal 3, and the memory unit 5 are each connected to a communication network NW and configured to be able to communicate with each other. The memory unit 5 is configured as a database installed inside or outside the port operations support device 2, and is configured to be able to communicate data with at least the port operations support device 2. Each port-related person (user) has a user terminal 3, and there are multiple user terminals 3.

[0025] The port business support device 2 has, as functional components, a registration unit 21 that accepts registration of various information, an acquisition unit 22 that acquires identification information, a procedure processing unit 23 that executes various procedure processes, a verification unit 24 that executes verification processes for specific items in the procedure processes, an output unit 25 that outputs various information, and a calculation unit 26 that calculates work days and procedure deadlines.

[0026] The user terminal 3 is a terminal device operated by those involved in port operations. The user terminal 3 functions as an input / output interface for the port operations support system 1. The user terminal 3 can transmit various input information to the port operations support device 2. The user terminal 3 can also receive various outputs from the port operations support device 2. The user terminal 3 may also have the function of a reading device, which will be described later.

[0027] The memory unit 5 stores various information. In this embodiment, the memory unit 5 includes a business flow memory unit 51 that stores business flow information, a verification information memory unit 52 that stores verification information, a baggage information memory unit 53 that stores baggage information, a port arrival / departure information memory unit 54 that stores port arrival / departure information, and a submission information memory unit 55 that stores submission information. The business flow information and verification information are stored in the memory unit 5 as master data. The baggage information, port arrival / departure information, and submission information are stored in the memory unit 5 in response to a registration instruction from the user terminal 3. In this embodiment, the baggage information and port arrival / departure information are defined as basic information.

[0028] FIG. 2(a) shows a hardware configuration diagram of port operations support device 2. Port operations support device 2 has a hardware configuration including a control device 201, a storage device 202, and a communication device 203, with each component device connected via a bus interface. In this embodiment, port operations support device 2 may use a computer device such as a server device or a personal computer. Port operations support device 2 may be configured with multiple computer devices, and is not limited to the configuration shown in the example, as long as it can realize the above-described functional components (21-26) as a whole.

[0029] The control device 201 is configured with one or more processors such as a CPU, and controls the overall processing of the port operation support device 2 by executing the port operation support program, an OS (Operating System), and other applications. The storage device 202 is a hard disk drive (HDD), solid state drive (SSD), flash memory, RAM (Random Access Memory), etc., and stores the port operation support program and various data. The communication device 203 is a communication interface for wired communication, wireless communication, etc., and controls data communication with external devices. The communication device 203 realizes data communication with external devices by controlling communication with the communication network NW.

[0030] 2(b) shows a hardware configuration diagram of the user terminal 3. The user terminal 3 includes, as its hardware configuration, a control device 301, a storage device 302, a communication device 303, an input device 304, and an output device 305. The user terminal 3 may also include a GPS communication device. In this embodiment, the user terminal 3 may be a smartphone, a personal computer, a tablet terminal, or the like.

[0031] The control device 301 is composed of one or more processors such as a CPU, and controls the overall processing of the user terminal 3 by executing terminal programs, an OS, other applications, etc. The storage device 302 is an HDD, SSD, flash memory, RAM, etc., and stores a browser application and various data. The communication device 303 controls communication with the communication network NW and realizes data communication with at least the port operation support device 2. The input device 304 is an input interface that accepts input operations by the user, and is composed of a microphone, touch panel, mouse, keyboard, etc. The output device 305 is composed of a display that displays and outputs, etc. The GPS communication device can acquire the position coordinates of the user terminal 3 via GPS communication.

[0032] In this embodiment, the user terminal 3 may be configured as a reading device. The reading device includes a reading module that reads a two-dimensional code or an electronic tag. In this embodiment, the two-dimensional code or electronic tag is physically attached to the baggage and records the identification information of the baggage. The reading device includes an imaging device or optical reading device for reading the two-dimensional code, an antenna device for reading the electronic tag, or both of these as a reading module. Two-dimensional codes include barcodes and QR Code (registered trademark). Two-dimensional codes also include text representations of numbers or symbols, and may be obtained by optical character recognition (OCR) using an imaging device. The reading device may be configured as a device separate from the user terminal 3 and transmit the read identification information to the port work support device 2 via the user terminal 3, or transmit the read identification information to the port work support device 2 via wireless communication.

[0033] Figure 3 is an overview diagram explaining the flow of import and export operations. In Figure 3, the operations at the exporting country are shown on the left side, and the operations at the importing country are shown on the right side. In import and export operations, goods are transported by sea from the exporter to the importer by ship. In sea transport, there are operations for ships entering and leaving ports, but the details of these are omitted in Figure 3.

[0034] In import / export operations, a contract for the import / export of cargo is first concluded between the exporter and importer (S1). The exporter submits a shipping request to the forwarder (including customs brokers and freight forwarders) along with the contracted cargo (S2). The forwarder submits an export declaration to customs (S3). If customs permits the export, it issues an export permit to the forwarder (S4). Based on the export permit, the forwarder requests a shipping company to load the cargo (S5). The shipping company issues a bill of lading to the exporter (S6) and transports the cargo by sea to the import destination. The exporter submits the bill of lading and documentary bill to the bank (S7), and the bank pays the settlement amount to the exporter (S8).

[0035] The importer pays the settlement amount at a local bank (S9) and receives the bill of lading for the imported cargo (S10). The forwarder submits an import declaration to customs (S11). If customs permits the import, it issues an import permit to the forwarder (S12). The exporter submits the bill of lading to the shipping company via the forwarder (S13). The shipping company transports the cargo to the importer via the forwarder (S14), and the cargo is then handed over from the exporter to the importer.

[0036] Figure 3 shows an overview of import and export operations, and in reality, various procedures are carried out among many different parties. The port operations support system 1 supports these various procedures using user terminals 3 operated by each of these parties.

[0037] User terminal 3 can transmit information including the attributes of parties involved in port operations (hereinafter referred to as party attributes) to port operations support device 2. Party attributes include exporters, customs brokers, freight forwarders, CY operators, customs, inspection companies, shipping companies, captains, importers, banks, insurance companies, transport companies, warehouse companies, immigration, port administrators, port traffic control offices, coast guards, quarantine stations, and even companies commissioned to handle various port operations. Party attributes are not limited to these, and may include entities with relationships such as outsourcing contracts in port operations. Party attributes are also intended to distinguish between parties at the exporting and importing locations.

[0038] The related party attributes are used to identify the person making the procedure and the recipient of the procedure for various port operations procedures. For each type of procedure, the person making the procedure and the recipient of the procedure are set, and by referencing the related party attributes on the user terminal 3, the person making the procedure can complete the specified procedure with the recipient of the procedure.

[0039] 4 shows a block diagram of the port operation support device 2. The business flow memory unit 51 stores business flow information set by the administrator. The verification information memory unit 52 stores verification information set by the administrator.

[0040] The registration unit 21 accepts registration of basic information via the user terminal 3. In this embodiment, the basic information includes at least one of cargo information and port arrival / departure information. The registration unit 21 stores the basic information in association with identification information in accordance with the registration. The registration unit 21 accepts registration of cargo information, associates it with the cargo identification information, and stores it in the cargo information storage unit 53. The registration unit 21 accepts registration of port arrival / departure information, associates it with the ship identification information, and stores it in the port arrival / departure information storage unit 54.

[0041] Cargo information is registered when a sales contract is concluded between an importer and an exporter. Cargo information includes cargo type (container (FCL), container (LCL), bulk), item name, quantity, shipper, request date, receipt date, destination, destination country, notification date, transportation method, etc. When cargo is placed in a container through the panning procedure, the cargo information is linked to the identification information of the container.

[0042] In this embodiment, the identification information of the baggage information is physically attached to the baggage as a two-dimensional code or an electronic tag. The reading device acquires the identification information of the baggage by reading the two-dimensional code or the electronic tag, and transmits it to the port operation support device 2, thereby enabling the target baggage to be identified.

[0043] Port entry / departure information is registered when arrangements are made for a ship to enter port. The port entry / departure information includes port information, ship information, and port entry / departure dates. The port information is information about the port where the ship will enter, and includes the port name, port location, set area, etc. The set area indicates an area that is set to detect whether the target ship is approaching the port as scheduled. The ship information includes ship identification information, ship location, etc. The ship information may be obtained from an external database. In this embodiment, ships approaching a port are distinguished and managed as being in a state of preparation for entry.

[0044] Container information includes the container number, shipper, destination, and transport vessel. The container number is the container's identification information and is physically assigned to the container using a two-dimensional code or electronic tag. Container information is registered when booking for import / export operations. When booking, the vessel that will load the container is specified, and the container information is linked to the vessel's identification information.

[0045] When cargo information is registered, workflow information related to import / export operations is referenced and workflow management is initiated. When port arrival / departure information is registered, workflow information related to port arrival / departure operations is referenced and workflow management is initiated. The initiated workflow information is associated with the corresponding cargo identification information or ship identification information, and each is managed as an individual workflow.

[0046] The acquisition unit 22 acquires identification information. The identification information includes at least one of the identification information of the cargo and the identification information of the ship. The cargo and the ship move during the logistics process. At each stage of the logistics process, they require specific procedures. The acquisition unit 22 can identify when, where, and from whom the identification information was acquired, and can thereby present the corresponding procedures to the user. It can also present to the user which stage of the logistics the target is in.

[0047] The acquisition unit 22 acquires the identification information of the parcel by reading the two-dimensional code or electronic tag via a reading device. The acquisition unit 22 acquires the identification information of the reading device together with a timestamp, and can identify the user's related party attributes and work date. The acquisition unit 22 references the status and schedule linked to the parcel's identification information and verifies whether they match the acquired related party attributes and work date. If they match, the acquisition unit 22 allows the execution of the subsequent procedure process; if they do not match, it may output an error message or record that a work delay or the like has occurred.

[0048] The acquisition unit 22 acquires identification information of ships detected within a predetermined area where the ship's location information is set in the port information. This allows ships approaching the port to be presented with predetermined procedures. The acquisition unit 22 may acquire a timestamp along with the ship's identification information. The acquisition unit 22 can adjust the port arrival / departure dates and schedules in the port arrival / departure information according to the acquired timestamp.

[0049] The procedure processing unit 23 executes procedure processing according to the status of the business flow for the target identified by the identification information. The procedure processing unit 23 generates procedure documents according to the status of the business flow based on the basic information, and executes procedure processing to submit the procedure documents. In this embodiment, the procedure documents include related documents exchanged between related parties and NACCS procedures, which are applications to related administrative agencies such as customs. The contents of each processed procedure document are linked to cargo information or port entry / departure information as submission information and stored in the submission information storage unit 55.

[0050] The verification unit 24 refers to the verification check table stored in the verification information storage unit 52 and verifies specific items of the procedural documents to be submitted by the procedure processing unit 23. After the verification unit 24 has performed the verification, the procedure processing unit 23 can execute the procedural processing to submit the procedural documents.

[0051] The verification check table is data that associates check items that must be addressed with each procedural document. The verification unit 24 presents information that must be referenced for the check items. The verification unit 24 also outputs classification results for the input items of the procedural documents according to the check items. The procedural processing unit 23 can input the input items by referring to the presented information and classification results, and execute the procedural processing.

[0052] The output unit 25 generates a progress management screen for the workflow in question according to the status and procedure information of the workflow identified by the identification information. The progress management screen displays at least one of the status and schedule of various procedures. The status and schedule of procedures on the progress management screen are indicated by the procedure deadlines and work dates calculated by the calculation unit 26.

[0053] FIG. 5 is an explanatory diagram outlining the workflow information in this embodiment. Different workflows are set for the workflow information depending on the workflow type. In this embodiment, the workflow types are broadly categorized into import / export workflows and port arrival / departure workflows. The workflow types are further divided into export > charterparty, export > container (FCL), export > container (LCL), import > conventional cargo, import > container (FCL), import container (LCL), and port arrival / departure workflows. Note that the workflow types are not limited to these and may be further subdivided, or other types may be added.

[0054] The workflow information has a workflow ID, a workflow type, a status, and procedure information. As shown in Figure 5, the workflow of the workflow type T1 has multiple statuses (A1, A4, etc.). The statuses are defined for each stage of the work and are used to manage the progress of the work. The status is linked to one or more procedure information (procedures P1, P4 to P6, etc.). The procedure information indicates the related documents required for that status and various procedures such as NACCS procedures. The workflow information is linked to the corresponding status and procedure information according to the work type. There are no restrictions on the type or quantity of status and procedure information, and they are set according to the work type.

[0055] Each status has a work date on which the work is performed. Procedure information has a procedure deadline, which is the deadline for creating the procedure information. The procedure deadline is set before the work date, and the corresponding procedure information is created by the procedure deadline. On the actual work day, the work is performed while checking the procedure information created in advance. For example, if it is confirmed that the contents of the package match the procedure information, the work corresponding to each status is completed by carrying out the submission procedure for the created procedure information.

[0056] Statuses are broadly divided into reservation operation statuses and logistics operation statuses. Reservation operations include, for example, reservations for ships, containers, etc. that transport cargo, and operations related to reservations for companies that undertake ship docking operations. Logistics operations include, for example, operations related to cargo logistics such as customs clearance, CY loading, export permits, shipping, marine transport, import permits, and land transport, as well as port entry and departure operations such as advance ship notifications, port entry notifications, and port departure notifications. In logistics operations, operations related to logistics are carried out by the objects reserved through reservation operations and the respective parties involved. In logistics operations in this embodiment, statuses are managed as objects including cargo, containers, ships, etc. move.

[0057] 6(a) shows an example of the data configuration of workflow information related to the business type of Export > Charterparty. The workflow information has multiple status IDs and one or more procedural information items linked to the status IDs.

[0058] The procedure information includes a procedure ID, a work classification, related documents, a NACCS procedure, a procedure performer, and a procedure recipient. At least one of the related documents and the NACCS procedure is present for a procedure ID, but it is possible that one does not exist or both exist.

[0059] The procedure information is set to the necessary procedures according to the cargo information. For example, if the cargo information item is a dangerous goods, the necessary procedures include the dangerous goods specification, the dangerous goods specification information registration, and related documents, as well as the NACCS procedure.

[0060] In Figure 6(a), status A1 indicates the status at the stage of the sales contract. Status A4 indicates the status at the stage of securing a transport vessel. Work classifications are sub-classifications according to the work content performed at each status, and one or more work classifications are set within each status. Each work classification is linked to one or more related documents, one or more NACCS procedures, or both.

[0061] Figure 6(b) shows an example of the data structure of workflow information for the Export > Container (FCL) business type. In Figure 6(b), status A24 indicates the status at the stage of securing a transport vessel, and status A25 indicates the status at the stage of loading procedures. Procedures P24 and P25 are procedures related to booking space on the vessel. Procedure P25 is a required procedure if the cargo items include dangerous goods.

[0062] Figure 6(c) shows an example of the data structure of workflow information related to the port entry / departure work type. In Figure 6(c), status A101 indicates the procedures of each party involved in the port entry arrangement stage, status A102 indicates the procedures of each party involved in the work arrangement stage, and status A103 indicates the procedures of each party involved in the stage before port entry.

[0063] The mechanism for managing the workflow by referring to the workflow information in the port operation support system 1 will be described in detail below.

[0064] <Example of export business> The registration unit 21 accepts basic information (cargo information) for import / export operations, associates it with the identification information of the cargo, and stores it in the cargo information storage unit 53. When the cargo information is registered, the business flows of export > charter party and export > container (FCL or LCL) are set. The set business flows are associated with the cargo information and managed individually. The cargo information is registered, for example, by the sales contract of procedure P1 shown in Figure 6(a).

[0065] Export > Charter party statuses include sales contract, ocean transport request, land transport request, securing transport vessel, shipping procedures, land transport, customs clearance, customs application, export declaration, export permit, shipping, and ocean transport. Export > Container (FCL) statuses include sales contract, ocean transport request, land transport request, securing transport vessel, shipping procedures, land transport, customs clearance, CY entry, customs application, export declaration, export permit, shipping, and ocean transport. Export > Container (LCL) statuses include sales contract, ocean transport request, land transport request, securing transport vessel, shipping procedures, land transport, customs clearance, CFS entry, customs application, export declaration, export permit, CY entry, shipping, and ocean transport. For each status, the period up to shipping procedures corresponds to booking operations, and the period after land transport corresponds to logistics operations.

[0066] Once the business flow is set, a schedule is set for the status described above. The schedule is determined by referencing the ship's port arrival and departure information based on the charter party procedural information registered when the transport ship is secured. The schedule includes procedural deadlines and work dates. The output unit 25 provides these schedules to the user terminal 3 as a progress management screen. The output unit 25 can also output notifications to each user terminal 3 based on the procedural deadlines or work dates set in the schedule. It should be noted that progress management screens corresponding to export and import are provided.

[0067] The procedure processing unit 23 executes procedure processing of the charter party procedure information in the Export > Charter party transport vessel securing status. The charter party procedure information includes the vessel information of the vessel transporting the cargo, and this procedure processing links the cargo information with the vessel information. The charter party procedure information is, for example, the charter party of procedure P4 shown in Figure 6(a).

[0068] The procedure processing unit 23 executes the procedure processing of the booking procedure information in the export > container transport ship secured status. The booking procedure information includes the ship information of the ship transporting the container, and this procedure processing links the container information with the ship information. The booking procedure information is, for example, the booking request form of procedure P24 shown in Figure 6(b).

[0069] The procedure processing unit 23 executes the panning procedure in the container (FCL) shipping procedure. The panning procedure information includes container information of the container that holds the cargo, and this procedure links the cargo information with the container information. The panning procedure information is, for example, the panning of procedure P41 shown in Figure 6(b). After the container (FCL) is panned, the entire container undergoes customs clearance procedures.

[0070] On the other hand, the procedure for panning cargo into containers (LCL) is carried out after each individual cargo has cleared customs and been approved for export. Container (LCL) panning is linked to the status of the export permit, and at the export permit stage, cargo information and container information are linked. In this way, export > container (FCL) and export > container (LCL) are linked to different panning statuses, and procedures are managed according to the business flow information for each business type.

[0071] In logistics operations, the acquisition unit 22 acquires identification information of a parcel or container and identifies the parcel or container in question. In logistics operations, the identification information of the parcel or container to be transported is read by a reading device using a two-dimensional code or an electronic tag. The procedure processing unit 23 generates a procedure screen (not shown) based on the identification information of the parcel or container, the related party attributes of the sender, and the status, and presents it to the user terminal 3. When the procedure processing of all necessary procedures for the procedure information associated with the status has been completed, the procedure processing unit 23 accepts a status update instruction via the procedure screen and updates the status.

[0072] The procedure for panning a container (LCL) will be explained as a specific example. The procedure processing unit 23 executes the panning procedure when the container (LCL) has an export permission status. At this time, the acquisition unit 22 acquires the identification information of the cargo via a reading device operated by the cargo handling company, and the procedure processing unit 23 generates a panning procedure screen when the cargo is in export permission status. When an export permit (related documents) and removal confirmation registration (NACCS procedure) associated with the export permission status have been submitted to customs by the forwarding agent, the procedure processing unit 23 accepts the registration of procedural information for panning (related documents) and panning information registration (NACCS procedure). This completes the panning procedure, completes the export permission status, and updates the status to CY entry.

[0073] When the shipping status is completed, the procedure processing unit 23 carries out the procedure processing related to the issuance of a bill of lading by the shipping company to the exporter, updates the status from shipping to sea transport, and completes the business flow of the export business.

[0074] As described above, export operations from the sales contract to sea transportation are managed by updating the status, and the cargo is exported.

[0075] <Example of import business> In the import business, the business flow of import > conventional cargo and import > container (FCL or LCL) is set based on the cargo information registered in the export business.

[0076] Import > Conventional cargo statuses include ocean transport, unloading, customs clearance application, import declaration, import permit, collection, and land transport. Import > Container (FCL) statuses include ocean transport, unloading, CY entry, customs clearance application, import declaration, import permit, CY exit, collection, and land transport. Import > Container (LCL) statuses include ocean transport, unloading, CY entry, CFS entry, customs clearance application, import declaration, import permit, collection, and land transport. All import business statuses fall under the category of logistics business.

[0077] The acquisition unit 22 acquires identification information of ships detected within a specified area where the ship's location information is set in the port information. The procedure processing unit 23 extracts cargo information and container information associated with the acquired ship's identification information. The procedure processing unit 23 notifies the shipping company's user terminal 3 of the arrival notification procedure information associated with the maritime transport status for the extracted cargo information and container information. The procedure processing unit 23 accepts registration of procedure information including an arrival guide via the user terminal 3, executes procedure processing, and updates the status from maritime transport to unloading.

[0078] The procedure processing unit 23 also extracts cargo information associated with the ship identification information acquired by the acquisition unit 22, and executes procedure processing of procedural information related to cargo delivery. Cargo delivery is a procedure carried out by the importer and CY operator to the customs broker, and includes the procedure of submitting related documents including the bill of lading and delivery instructions.

[0079] The procedure processing unit 23 executes various procedures for the target cargo based on the identification information of the cargo acquired via the reading device, regarding procedures related to each status of unloading, CY delivery, customs clearance application, import declaration, import permission, collection, and land transportation. Completion of land transportation completes the workflow of the import business.

[0080] As described above, import operations from sea transport to land transport are managed by status updates, and the cargo is delivered to the importer.

[0081] <Example of port entry and departure procedures> The registration unit 21 accepts basic information on port entry and departure operations (port entry and departure information), links it to the ship's identification information, and stores it in the port entry and departure information storage unit 54. When the port entry and departure information is registered, the business flow for port entry and departure operations is set. The business flow for port entry and departure operations is managed by the ship's identification information. The port entry and departure information is registered by a procedure request of procedure P101 shown in Figure 6(c).

[0082] The status of port entry and departure operations includes port entry arrangements, work arrangements (arrival), before arrival, after arrival, work arrangements (departure), and after departure. Here, the status of port entry arrangements and work arrangements (arrival or departure) corresponds to reservation operations, and the status of before arrival, after arrival, and after departure corresponds to logistics operations.

[0083] When the workflow for port entry / departure operations is set, a schedule including the procedure deadlines and work dates is set in the status described above. The output unit 25 provides these schedules to the user terminals 3 as a progress management screen. It can also notify each user terminal 3 of the procedure deadlines and work dates.

[0084] The procedure processing unit 23 accepts registration of procedure information for each party involved in the status of port entry arrangements and work arrangements related to reservation operations, and executes the procedure processing. In the work arrangements, arrangements are made for insurance, loading goods, pilots for docking work, escort boards, tugboats, and cargo handling companies.

[0085] The acquisition unit 22 acquires the identification information of a ship detected within a predetermined area where the ship's location information is set in the port information. The procedure processing unit 23 can execute procedure processing for the status procedures before entering, after entering, and after departing from port of a ship identified by the acquired ship identification information.

[0086] Procedural information associated with the status before port arrival includes insurance contract information, ship security information, advance notification, application for permission to enter and exit a closed port, application for permission to use mooring facilities, notification of mooring facility use, quarantine notification, sea route notification, application for loading of dangerous goods, etc. Procedural information associated with the status after port arrival includes port entry notification (customs, port authority, harbor master, immigration, declaration), report on matters related to crew and passengers, ship's stores inventory, report on matters related to cargo, application for crew landing permission, etc. Procedural information associated with the status after departure includes port departure notification (customs, port authority, harbor master, immigration), declaration of tonnage payment, notification of movement, etc.

[0087] The schedule for ship arrival and departure operations fluctuates depending on navigation delays, etc. Therefore, by presenting the necessary procedures at the appropriate time in response to the actual approach of the ship to the port, it is possible to provide efficient support for port arrival and departure operations.

[0088] The verification unit 24 performs verification processing by referring to the verification check table for the verification items corresponding to each piece of procedure information. The verification information storage unit 52 has a law check table and an item check table.

[0089] The law check table stores laws and regulations corresponding to the procedural information. The verification unit 24 refers to the law check table and verifies the verification items of the corresponding procedural information. For example, the deadline for submitting procedural information related to port entry and departure operations is set by law to be a specified period before the ship enters port. In addition, the submission deadline may differ depending on the procedural information items, such as the ship type, gross tonnage, port of call, port of entry, navigation area, ship length, and type of dangerous goods carried. The verification unit 24 can output the submission deadline for each procedure by verifying these verification items.

[0090] The item check table stores a table that determines whether an item in the package information is a dangerous item or which of the item classifications for customs clearance applications it falls under. The verification unit 24 references the item check table and outputs the item classification results. If the classification result indicates that the item is a dangerous item, the verification unit 24 outputs a warning notice. Furthermore, the verification unit 24 outputs the tax rate and tax amount for the item classification as a result of the classification.

[0091] Figure 7 shows an overview of package progress management information. Progress management information is used to manage schedules for procedure deadlines and work days. Package progress management information includes schedule information shown in Figure 7(a) and procedure progress information shown in Figure 7(b). Progress management information is generated according to the status of package information and procedure information. The output unit 25 generates a progress management screen based on the progress management information and outputs it to each user terminal 3. This allows users to check the schedule and procedure progress of the package in question.

[0092] The calculation unit 26 can calculate the work dates and procedure deadlines included in the progress management information. The calculation unit 26 obtains the port arrival and departure dates included in the port arrival and departure information, and calculates the work dates for port operations corresponding to each status. The calculation unit 26 obtains the work dates for each status, and calculates the procedure deadlines corresponding to each procedure information. The business flow memory unit 51 stores work day calculation data that sets work dates for port arrival and departure dates, and procedure deadline calculation data that sets procedure deadlines for work dates. The work day calculation data can set different work days for each status. Furthermore, the procedure deadline calculation data can set different procedure deadlines for each procedure deadline. When there is a change in the port arrival and departure dates or status, the calculation unit 26 can reflect the changes to the schedule by referring to the work day calculation data and the procedure deadline calculation data.

[0093] As shown in FIG. 7(a), the schedule information includes identification information (baggage ID), the item name, and a schedule for each status. The schedule is indicated as the completion date or planned date (work date) of the work for that status. When the procedure processing unit 23 completes the procedure for each status, it records that date as the completion date. In this embodiment, the schedule corresponding to each status includes container arrangement (securing an export vessel), export permission, receipt (land transport), CFS (CFS delivery), CY (CY delivery), customs clearance date (customs clearance application), completion of loading, departure date, arrival date, CY, CFS, import permission, customs clearance date, delivery (collection), delivery (land transport), and delivery (land transport completion). The departure date and arrival date may refer to the port entry / departure information of the vessel associated with the baggage information.

[0094] As shown in Figure 7(b), the processing progress information includes package identification information, product name, and processing status for each status. The processing status becomes "completed" when processing of all required procedures for processing information set for each status of the target package information is completed. Note that the processing status may also indicate whether each processing information for the target package information is incomplete. In addition, in the illustrated example, the processing status displays the names of the parties involved who will be subject to processing. The processing status may also display the processing deadline.

[0095] Figure 8 shows an overview of progress management information for ship entry and departure procedures. The progress management information for ship entry and departure procedures includes schedule information shown in Figure 8(a) and procedural progress information shown in Figure 8(b). The progress management information is generated according to the status of the port entry and departure procedures and the procedural information. The output unit 25 generates a progress management screen based on the progress management information and outputs it to the user terminal 3. This allows the user terminal 3 to check the schedule and procedural progress of the target ship.

[0096] As shown in Figure 8(a), the schedule information includes the ship name, the ship's identification information (IMO, call sign), and the port arrival / departure schedule. The port arrival / departure schedule includes the name of the port where the ship will arrive / depart, the details of port operations (berthing, berthing, cargo handling, etc.), and the dates of those operations.

[0097] As shown in Figure 8(b), the procedural progress information includes the ship name, the ship's identification information, and the procedural status of each procedural information. The procedural status indicates whether procedural information related to each status of port entry and departure operations has been completed. In addition, as shown in Figure 8(c), the procedural progress information includes the procedural status related to arrangements for each company such as insurance, loading goods, pilots for docking operations, escort boards, tugboats, and cargo handling operations. The procedural status related to arrangements may further display the names of the parties to whom arrangements are made. [Explanation of symbols]

[0098] 1. Port operations support system 2 Port operations support equipment 21 Registration Department 22 Acquisition Department 23 Proceedings Department 24 Verification Department 25 Output section 3. User terminal 4 Ship equipment 5 Storage section 51 Business flow memory unit 52 Verification information storage unit 51 Baggage information storage unit 52 Ship information storage section 53 Submission information storage section

Claims

1. a registration unit that accepts registration of basic information according to the type of port business and associates it with identification information; a storage unit that stores one or more business flows corresponding to the business type; an acquisition unit that acquires the identification information; A port business support system comprising: a procedure processing unit that executes procedure processing according to the status of the business flow for an object identified by the identification information.

2. The port business support system of claim 1, wherein the procedure processing unit generates procedure documents corresponding to the status of the business flow based on the basic information and performs procedure processing to submit the procedure documents.

3. the storage unit stores a verification check table; 3. The port operation support system according to claim 2, further comprising a verification unit that refers to the verification check table and verifies specific items of the procedural documents.

4. The status of the business flow is linked to one or more pieces of procedure information, 3. The port operation support system according to claim 1, wherein the procedure processing unit updates the status by completing the procedure processing of all required procedures in the procedure information.

5. 3. The port operation support system according to claim 1, further comprising an output unit that generates a progress management screen for a business flow according to the status of the business flow identified by the identification information.

6. The registration unit links basic information about import and export transactions with identification information about packages, The identification information of the package is physically attached to the package as a two-dimensional code or an electronic tag, 3. The port operation support system according to claim 1, wherein the acquisition unit acquires identification information of the luggage by reading the two-dimensional code or the electronic tag via a reading device.

7. The registration unit links basic information on port entry and departure operations with identification information of the ship, The basic information includes port information, 3. The port operation support system according to claim 1, wherein the acquisition unit acquires identification information of a ship whose location information is detected within a predetermined area set in the port information.

8. Accepts registration of basic information according to the type of port operation, links it to identification information, storing one or more business flows corresponding to the business type; Acquire the identification information; A port business support method in which a computer executes each process by carrying out procedural processing according to the status of the business flow for the target identified by the identification information.

9. a registration unit that accepts registration of basic information according to the type of port business and associates it with identification information; a storage unit that stores one or more business flows corresponding to the business type; an acquisition unit that acquires the identification information; A port business support program that causes a computer to function as a procedure processing unit that executes procedure processing according to the status of the business flow for an object identified by the identification information.

Images