JP7437300B2 - Container information management system - Google Patents

Description

The present invention relates to a system for managing information on shipping containers, and particularly to a system suitable for managing import/export containers and empty containers transported within a country.

Container terminals scattered throughout Japan operate using their own unique code system, and the vessel movements and container information of ocean-going vessels that transport containers to and from overseas terminals are processed using an international standard data format. The information is transmitted and received after being converted into a code system.

On the other hand, if we focus on domestic container transportation, for example, container information managed by coastal ships and inland depots, as well as ship movement, booking, manifest, empty container pickup information, etc., cannot be communicated and managed using electronic data. The current situation is that information is exchanged between shipping companies, shipping companies, container terminals, container depots, and other related parties using analog methods such as email, fax, and telephone. be.

In view of these circumstances, a system as disclosed in Patent Document 1 has been proposed so that containers to be transported by land can be efficiently operated. In the system disclosed in Patent Document 1, an inland depot, shipping company, container leasing company, etc. inputs return and movement information regarding containers into a computer, and outputs it to a terminal owned by a trucking company, etc. that transports the container. Make it possible. It is said that efficient container usage can be achieved by matching usage requests from terminals based on input information.

Japanese Patent Application Publication No. 2002-169869

It is thought that if a system such as that disclosed in Patent Document 1 is used, it will be easier to share information regarding containers to be transported by land. However, many container terminals scattered throughout the country use their own terminal operation system (hereinafter referred to as TOS) as a system for managing container information. In addition, for reasons such as the fact that the international standard code (standard code) for container-related management information is difficult to understand intuitively, information management is performed using a container terminal-specific management information code (in-house code). This is often done. For this reason, when transmitting or receiving data regarding containers to the outside, it is actually necessary to convert and input management information codes one after another.

Furthermore, in domestic container transportation, there is no standard format for input data, so data is exchanged between companies in a unique format. Under these circumstances, it is necessary to input data again when applying TOS at each container terminal.

Furthermore, in the current situation where most terminals have TOS that is operated with unique specifications, it is virtually difficult to unify code systems related to data formats and containers. There is a real situation.

Therefore, an object of the present invention is to provide a container information management system that allows related information from outside to be easily applied to the company's own system while continuing to manage container information using the existing information management system. .

A container information management system according to the present invention to achieve the above object is a system for managing information on marine containers, and is connected to a plurality of user terminals via a network, and has a login screen to the system, A communication means that displays an input/output information screen and allows input of information via the user terminal, at least a company code arbitrarily agreed upon by each user regarding management information related to maritime containers, and a storage means for storing an internationally defined standard code for management information related to containers, a user ID, and a password of each user; and information stored in the storage means and information input via the communication means. The present invention is characterized by comprising a calculation means that performs an access permission determination process, an association process between the in-house code and the standard code, and a conversion process between the in-house code and the standard code, based on the information.

Furthermore, in the storage means in the container information management system having the above-mentioned characteristics, a format defining items of information to be registered and information to be read out is recorded for each user, and the calculation means is configured to perform processing according to a user's request. When displaying container information, it is preferable to rearrange and output the information according to the format item associated with the user ID. Having such characteristics makes it possible to register and read data in a format that matches the existing system on the user side.

Furthermore, a group of users who use the format can be registered in the storage means in the container information management system having the above characteristics. With such features, in a registered group, data can be shared only among related users.

According to the container information management system having the above characteristics, it becomes possible to easily apply related information from outside to the company's own system while continuing to manage container information using the existing information management system.

1 is a schematic diagram showing the configuration of a container information management system according to an embodiment. FIG. 3 is a diagram showing an example of registration of a user ID, password, and user-related information. FIG. 6 is a diagram showing an example of registration of standard codes and in-house codes stored for each user ID. FIG. 3 is a diagram showing an example of a format of registration items stored in a DB server. FIG. 3 is a diagram for explaining selection of output items. FIG. 3 is a diagram illustrating an example of the format of output items related to container information. It is a flow diagram for explaining the flow of user registration when operating the system. FIG. 2 is a flow diagram for explaining the flow for registering management container information when operating the system. FIG. 2 is a flow diagram for explaining the flow for checking a container list when operating the system.

Embodiments of the container information management system of the present invention will be described in detail below with reference to the drawings. The embodiments shown below are some of the preferred embodiments for carrying out the present invention, and the present invention may be implemented even if some of the configurations or names are changed as long as the embodiments are effective. It can be considered as part of

[composition]
First, with reference to FIG. 1, the configuration of a container information management system 10 according to this embodiment will be described. The container information management system 10 according to this embodiment is basically configured with a communication means, a storage means, and a calculation means. Note that each means may constitute a system as an internal element in one computer, or may constitute a system as a collection of individual elements. In this embodiment, each means is configured as an individual element, so in the following description, the communication means is the WEB server 12, the storage means is the database server (hereinafter referred to as DB server 14), and the calculation means is the application server. (hereinafter referred to as the AP server 16).

The web server 12 is an element responsible for communication with an external terminal such as a user terminal 30, which will be described in detail later, inputting information from the external terminal, and outputting information to the external terminal. The WEB server 12 has display functions such as an input screen for the user ID and password necessary for logging into the container information management system 10, and an input/output screen for management information related to maritime containers (none of which are shown). All you have to do is make it possible. Note that the actual display screen will be displayed on the display means 32 of the external terminal (user terminal 30) that has accessed the container information management system 10 via the WEB server 12.

The DB server 14 is an element for storing user IDs and passwords, company codes, standard codes, data formats, management information or data of data actually transmitted and received between users, and the like. The user ID and password are information required for a user who uses the container information management system 10 according to this embodiment to access the system. By storing each user's unique user ID and password in association with each other, access permission (login permission) can be determined by the AP server 16, which will be described in detail later.

The company code is a code arbitrarily agreed upon by each user regarding management information related to maritime containers (hereinafter simply referred to as containers), and is a code that is arbitrarily determined by each user regarding management information related to maritime containers (hereinafter simply referred to as containers). This is the display format shown. Further, the standard code is an internationally defined code for management information related to containers, and is a display format that indicates the size (length), type (kind), height, etc. of the container.

By correlating and recording each user ID, company code, and standard code, it becomes possible for the AP server 16 to perform mutual conversion between the company code and the standard code corresponding to the user ID. Note that the data format is an item field that includes data items necessary for container information management and elements for determining their arrangement order. The above-mentioned data management information is management information including the data format, and includes information such as the transmission date and time, the transmission source, the transmission destination, and the transmission data title (title), in addition to the data format. Furthermore, data refers to actual data that is actually transmitted and received.

The AP server 16 is an element that includes programs such as application software for performing various processes based on the information stored in the DB server 14 and the information input via the WEB server 12. The processing performed by the AP server 16 mainly includes access permission determination processing, association processing, conversion processing, and display data generation.

The access permission determination process is a process performed via a program for determining whether a user can log in to the container information management system 10. Specifically, a process is performed to determine whether the user ID and password input via the WEB server 12 match the user ID and password stored in the DB server 14. As a result of the determination, if the input user ID and password match the user ID and password stored in the DB server 14, a determination is made that authentication is permitted, and login to the container information management system 10 is permitted. . On the other hand, if the user ID and password do not match, a determination is made that authentication is not possible, and login to the container information management system is not permitted.

Here, as shown in FIG. 2, the user ID and password of each user are stored (input) in advance in the DB server 14 with necessary information associated with the user ID. Note that initial input of user information to the DB server 14 and input and management of various application software to the AP server 16 are performed by the system administrator via the input terminal 18 attached to the container information management system 10. You should do it.

The association process is executed by a program that associates input information according to predetermined items and stores the association in the DB server 14. Specifically, a process is performed in which the user ID and password input from the input terminal 18 or the user terminal 30, the user ID, the company code, the standard code, etc. are associated and stored in the DB server 14. By storing information in association with each other, by searching for predetermined information, it becomes possible to obtain other information associated with the search information.

The process of associating various information is performed for each user ID. For example, as shown in FIG. 3, it is sufficient that the standard code and the in-house code regarding the container are stored for each user ID so that they can be compared.

The conversion process is a process of comparing the in-house code and standard code input via the web server 12 with the in-house code and standard code stored in the DB server 14 (see Figure 3), and converting the in-house code into the standard code. , is executed by a program that converts standard code into proprietary code. The conversion from an in-house code to a standard code may be performed by, for example, searching for an in-house code stored in the DB server 14 and reading out the standard code associated with the stored in-house code.

The display process is executed by a program that displays the results of various processes executed by the AP server 16 via the WEB server 12. Note that the information regarding the container may be displayed in accordance with a predetermined data format.

Examples of data formats include a registration format in which registered items are shown as shown in Figure 4, a selection format for output items at the time of data output as shown in Figure 5, and a format for selecting output items at the time of data output as shown in Figure 6. An output format showing display items may be determined in advance, and data may be registered and output in accordance with this format.

Note that the user terminals 30 for accessing the WEB server 12 via the network 50 are owned by ocean-going shipping companies, domestic shipping companies, container terminals, inland depots, ocean freight/land transport companies, barge ship owners, etc. Any system such as a computer may be used. Therefore, each user terminal 30 or a system connected to the user terminal 30 is often configured with an individual information management system.

[Effect]
In the container information management system 10 having the basic configuration as described above, operation (system use) is performed after first registering a user. Therefore, the flow of user registration will be explained with reference to the user registration flow shown in FIG. 7, and the flow of use of the system will be explained with reference to the usage flows shown in FIGS. 8 and 9.

[User registration]
In user registration, first, a user accesses the WEB server 12 via the user terminal 30 (S110). When access to the WEB server 12 is approved, the WEB server 12 performs processing to display a login authentication screen (not shown). This process allows the user to view the login authentication screen via the display means 32 of the user terminal 30. Note that the login authentication screen is provided with items for inputting at least a user ID and password (SS120).

When the login authentication screen is displayed, the user inputs the user ID and password via the user terminal 30. When the user ID and password are input, the AP server 16 executes access permission determination processing. As a result of the access permission determination process, if authentication permission is determined, login to the container information management system 10 is permitted. On the other hand, if it is determined that authentication is not possible as a result of the access permission determination process, login to the container information management system 10 is not permitted, and the ID and password input screen is displayed again. In addition, in the access permission determination process, if authentication is determined to be impossible a predetermined number of times (for example, three times) in a row, processing such as locking the screen is performed to improve security. It is also possible to do so (S130).

If authentication permission is determined in the access permission determination process, registration is performed via the user terminal 30 to associate the in-house code with the standard code. The registration of the association between the in-house code and the standard code is performed by input via the WEB server 12, association processing by the AP server 16, and storage in the DB server 14 (S140). After registering the association between the in-house code and the standard code, the user defines (registers) the format (format: data format) such as input/output items and data order. The definition is performed by the AP server 16 associating the format input via the WEB server 12 (see, for example, FIG. 4) with the order of data stored in the DB server 14 (see, for example, FIG. 5), and This is done by storing it in the server 14 (S150). Furthermore, the user defines a group (range of users) that uses the defined format as necessary. To register a group, it is sufficient to input a user name, user ID, etc. on an input screen (not shown) displayed via the web server 12. The input user name and user ID are associated with each other by the AP server 16 and stored in the DB server 14. Note that the group referred to here is the party with whom the sending user (the user who registers the container and sends the information) performs the transaction, and defines the range in which the sent data can be viewed. Therefore, the number of groups is not limited to one, and a plurality of groups may be registered as necessary (S160). After completing the various registration processes, you can log out from the container information management system 10 by selecting a logout button (not shown) displayed via the web server 12 or closing the display screen. (S170).

[System usage: Send]
Next, with reference to FIG. 8, the use of the system when registering a management container will be described. The steps of accessing the WEB server 12 via the user terminal 30, inputting a user ID and password, and performing authentication regarding login permission are the same as the user registration described above (S210 to S230).

After logging into the container information management system 10, a list of information regarding managed containers (hereinafter referred to as a container list) is registered via the WEB server 12. Note that the method of registering the container list is not particularly limited. That is, the list contents may be copied and pasted for each item shown on the display screen via the web server 12 before transmission processing, or a list file compiled in advance within the company's system may be uploaded. It is also possible to do this. That is, a method can be adopted depending on the range of support on the container information management system 10 side.

In addition, when registering a user, uploading a file recorded according to the format requires less effort and errors. Alternatively, the data may be transmitted automatically by connecting to a TOS owned by the company via a network and providing the TOS with a function capable of transmitting data. When such a method is adopted, there is no need for the user to take any action.

Here, when determining the viewing range of the registered container list, any group can be selected from the groups set at the time of user registration. Note that if only one group is registered, the group may be automatically selected (S240).

When the container list is received via the WEB server 12, the AP server 16 performs a validity check and conversion process on the received data. Here, the validity check refers to whether the data recorded in the received container list has any missing items or data regarding unregistered items, and whether the data is recognized as corresponding to the specified form. Checks are made to see if the data that will be displayed has been recorded. As a result of the check, if it is clear that the data is not recorded according to the form, such as items that have not been registered in advance or the size and type data are reversed, It is preferable to output an error display to the user terminal 30 via the WEB server 12 (S250).

If the data recorded in the received container list is found to be valid as a result of the validity check, the AP server 16 performs code conversion processing. The code conversion process is performed according to the correspondence between the in-house code and the standard code recorded in the DB server 14 for each user ID (S260). The AP server 16 that has completed the code conversion process registers the container list for which the conversion process to the standard code has been completed in the DB server 14. Note that the management format of each data does not matter as long as it can be searched and used based on data management information. That is, the information is not limited to being saved as one file, and may be managed using separate files (S270).

After the registration process to the DB server 14, the AP server 16 outputs an output to display on the user terminal 30 via the WEB server 12 that the container list conversion process and the registration to the DB server 14 have been properly executed. conduct. This is because the user can confirm that the container list has been registered in the container information management system 10. The user logs out after receiving a message indicating completion of registration via the web server 12. Note that the timing of the user's logout is not limited, and it is possible to logout immediately after registering the container list (after S240). This is because if the container list is valid, subsequent processing can be handled by the container information management system 10 (S280).

[System usage: Reception]
Next, confirmation of the container list registered in the container information management system 10 (utilization of received data) will be described with reference to FIG. The steps of accessing the WEB server 12 via the user terminal 30, inputting a user ID and password, and performing authentication as to whether or not login is possible are the same as the user registration described above (S310 to S330).

After logging into the container information management system 10, a list of available containers will be displayed on the user terminal 30 via the WEB server 12 according to the user ID. Regarding the timing at which the user logs in to the container information management system 10, a notification may be sent from the source of the management information to the destination (parties registered as a group), and the user may log in based on this notification. Alternatively, the receiving side (destination) may log in on a daily basis as a routine task and check available lists. Here, the notification from the sender to the destination may be by means such as telephone or FAX in addition to mail (electronic mail). When using email as a notification method, when the creation of a data list by the AP server 16 (association processing) and the storage in the DB server 14 are completed, the information is automatically sent to the parties registered as a group (destinations). It is also possible to do so (S340).

When the user selects a container list that the user wants to use from among the displayed items (container lists), the AP server 16 refers to the DB server 14 and reads out the corresponding container list. Here, since the container list read by the AP server 16 is recorded using a standard code, the AP server 16 reads the information associated with the logged-in user ID and converts the standard code into the user ID. Perform the process of converting to a compatible in-house code. After completing the code conversion process for the data recorded in the container list, the AP server 16 performs a conversion process to change the display format of the data so that it matches the format corresponding to the logged-in user stored in the DB server 14. Execute (S350).

The container list that has been subjected to various conversion processes is displayed on the user terminal 30 via the WEB server 12 (S360). After reading the container list displayed via the web server 12, the user logs out. Note that reading the container list may be performed using various methods, similarly to registering the container list. In other words, you can copy and paste the data displayed on the screen into the input format of your company's system, or you can download the displayed data as a file and use it as is in your company's system. . Alternatively, data may be automatically received by connecting to a TOS owned by the company via a network and providing the TOS with a function capable of receiving data (S370).

[effect]
By using the container information management system 10 as described above, while continuing to manage container information using the existing data management system (including TOS) owned by the user, it is possible to import related information from outside into the company's own system. It can be easily applied. Therefore, it is not necessary to perform input processing to the existing system every time data is exchanged, and it is possible to reduce labor and prevent input errors caused by manual intervention.

In the above embodiment, the container information management system 10 is shown and explained as being composed of a plurality of servers and terminals. However, as long as the functions of each element can be provided, the system may be configured by a single device or computer. For example, the storage means can be a memory, a hard disk drive (HDD), a solid state disk (SSD), or the like. Further, the calculation means may perform various processes by executing programs stored in the storage means in cooperation with the IC and the CPU. Further, the communication means may process information input/output via the interface via an IC or CPU, and display various information on the user terminal 30.

Further, in the above embodiment, only information related to containers is handled, but by pre-registering items in the DB server 14, it is also possible to manage information other than information related to containers.

10...Container information management system, 12...WEB server, 14...DB server, 16...AP server, 18...Input terminal, 30...User terminal, 32...Display means , 50...Network.

Claims (2)

A system for managing information on maritime containers,
a communication means that is connected to a plurality of user terminals via a network, displays a login screen to the system and an input/output information screen, and enables information input via the user terminal;
At least, the company code arbitrarily decided by each user regarding management information related to sea containers, the internationally defined standard code for management information related to sea containers, the user ID and password of each user are memorized. storage means,
Based on the information stored in the storage means and the information input via the communication means, an access permission determination process, an association process between the in-house code and the standard code, and an association process between the in-house code and the standard code are performed. and a calculation means for performing conversion processing between the
The storage means further records a format defining information to be registered and items of information to be read out for each user,
The container information management system is characterized in that, when displaying container information in response to a user's request, the calculation means rearranges and outputs the information according to a format item associated with a user ID. 2. The container information management system according to claim 1 , wherein a group of users who use the format can be registered in the storage means.

Images