JPH05174035A - Inter-data base data transfer device - Google Patents

Abstract

PURPOSE:To provide a data transfer device which can transfer the data between the data bases of different data structures by using a means which sorts the data and searches the specific link relation. CONSTITUTION:The reserved information 12 is sorted for each master product number by a master product number sorting means 22 out of those data sent from a host side data base 2. Meanwhile the slave parts number-piece number data corresponding to the sorted master product number are stored in an area secured by a parts component information storage area securing means 24. Thus the slave parts-piece number data are stored in response to the sorted master parts number. At the same time, a parts link information searching means 26 searches the link relation where a slave parts number is defined as a master parts number. The approximately same processing in also applied to the in process information 14 and the arrangement information 16. Thus the process related information is acquired in a mode related to the sorted its own process together with the link relation information on the process that defines the precedent process as its own process.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a technique for utilizing a database used for managing a production system.

[0002]

2. Description of the Related Art A large-scale production system such as an automobile assembly maker produces a wide variety of products in a variety of production processes, and a database that stores production information for managing the production system. Is used.

In the case of a model production system as shown in FIG. 2, for example, in the process J4, the database produces the parts of the own product number shown by the hatched circles using the parts of the product numbers shown by the hollow circles. It is configured as a collection of data and the like indicating supply to the process J7. In addition to this, in this database, for example, information indicating which part number of the part is composed of which part number, information indicating in which previous process the child part number required in the own process is produced, All the data useful for production management such as unit price, delivery timing of parts, time required to produce parts, etc. are accumulated.
The person in charge of production management retrieves and extracts necessary data from the above database, and uses this data to manage the production or process.

[0004]

However, this database becomes extremely huge in the case of a large-scale production system. Particularly in the case of an ultra-large-scale production system in which the production system is composed of a plurality of factories or management units, the host-side database that aggregates the production information of all factories becomes extremely large. Therefore, it takes a long time to extract the data necessary for the management of each factory, and the database is becoming large-scaled so that the extraction time becomes too long to be put to practical use.

To solve this problem, it is necessary to provide a database for each factory or each management unit. In this way, there is also an advantage that it is possible to manage in accordance with the actual situation for each factory or each management unit. However, this method requires data maintenance for each database and makes it difficult to centrally manage all production systems.

Due to such circumstances, both a single host side database and a database for each management unit, that is, a user side database are required. In this case, it is naturally necessary to be able to send and receive data between the database on the host side and the database on the user side. However, the user side database should be constructed so that the data useful for the management of each management unit can be easily extracted, and the host side database should be constructed so that the data useful for the unified management of the production system can be easily extracted. For this reason, the data structures of both databases are usually different.

For this reason, at the present time, a system that uses both the host-side database and the user-side database and keeps the data in both databases unified has not yet been realized. Therefore, in the present invention, an apparatus that enables the transfer of data between databases having different data structures is developed so that both the host side database and the user side database can be centralized while ensuring the proper use of both. is there.

[0008]

Therefore, in the present invention, the concept is schematically shown in FIG. 1, which is a data transfer apparatus, that is, a parent product number sent from a host side database 2 storing production information. The allocation information 12 indicating the relationship between the child product number and the number, the work-in-process information 14 indicating the relationship between the own product number and the own process, and the arrangement information 16 indicating the relationship between the own process-child product number-previous process are input, and the parent product number-child product number- Parts configuration information 42 showing the relationship of the number of pieces, parts link information 44 showing the link relationship of the parts configuration information having the child part number as the parent part number, process related information 46 showing the relationship of own process-own product number-child product number-previous process, User side database 4 including process link information 48 indicating a link relationship of process related information with the previous process as its own process
Device 20 for migrating data to 0, and the allocation information 12
22 for sorting the parent parts number by means of a parent part number, and a part configuration information storage area for storing a child part number-number relationship corresponding to the parent part number for each sorted parent part number.
0 means for securing in 0, means 26 for retrieving and storing in the user side database the information on the area for storing the data for the sorted parent part number with the child part number as the parent part number, the in-process information 14 and the A means 28 for sorting the arrangement information 16 in its own process, a process-related information storage area for storing, for each sorted own process, a relation of own product number-child product number-previous process corresponding to the own process Database 4
A database having a means 30 for securing in 0 and a means 32 for retrieving information related to an area for storing data related to a sorted own process having the previous process as its own process and storing it in the user side database 40. The data transfer device 20 between them was created.

[0009]

Now, the operation of the above-mentioned data transfer device will be described by taking the production system model shown in FIG. 2 as an example. In FIG. 2, for example, in step J4, a child part whose child part number is indicated by a hollow circle mark and a child part indicated by a hollow triangle mark are used to produce a part indicated by a hatched circle mark and supply it to step J7. The production system for producing the article indicated by the hatched triangle and supplying it to the step J8 is schematically shown. This production system is a production system in one factory or in a management unit, and there are a plurality of such production systems. Although FIG. 2 exemplifies a very simple production system, it goes without saying that the present invention is also useful for a more complicated production system.

In order to centrally manage all of the plurality of production systems, production information of all production systems is stored in the host side database. Here, when the data in the host side database is transferred to the user side database, only the data related to the production system managed by the user side database is extracted and sent out from the host side database. Specifically, allocation information indicating the relationship between the parent product number-slave product number-slave product number used quantity, work-in-process information indicating the relationship between own product number and own process, and arrangement information indicating the relationship between own process-child product number-previous process. And are sent out. In the case of the user side database that manages the production system in FIG. 2, the information illustrated in FIG. 3 is sent out.

Of the data sent in this way, the allocation information is sorted by the parent product number sorting means 22 for each parent product number. Further, the child product number-number data corresponding to the sorted parent product number is stored in the area secured by the component configuration information storage area securing means 24. Therefore, as illustrated in FIG. 4, the component configuration information is stored in such a manner that the sorted parent part numbers are associated with the corresponding child part number-number data. Further, the part link information search means 26 searches for a link relationship with the child part number as the parent part number. For example, the child part number of the part configuration information of the eye slot 6 in FIG. 4 is the parent part number of the eye slot 7 and the eye slot 5, and therefore the information that the eye slots 6 and 5 are linked is searched. To be done. Here, the eye slot is data that is referred to when searching each component configuration information, and is one of information indicating an area in which the component configuration information is stored.

[0012] Almost the same processing is executed for work-in-process information and arrangement information, and as a result, as shown in FIG. 4, the self-process-self-product number-sub-product number-in a manner related to the sorted self-process. Process related information showing the relationship of the previous process is obtained,
In addition, information about the link relation of the process in which the previous process is its own process can be obtained. In this way, the information sent from the host side database is transferred to the user side database having a different data structure.

[0013]

Next, in order to describe the constitution of the present invention more specifically, one embodiment of the present invention will be described.
FIG. 6 shows the configuration of a computer system that manages the production of factories 420, 520, .... A host computer 200 is used to centrally manage the production information of all factories, and the host computer 200 builds a host-side database 200a. The host computer 200 is connected to the host terminals 402, 502, etc. provided in each factory by a communication line. This host computer 200, for each host terminal,
Send allocation information, work in process information, and arrangement information. The order information includes in-house order information and outsourced order information. The host terminals 402, 502 ... Save the sent data in the floppy disks 404, 504.

In the figure, reference numerals 400, 500 ... Indicate user computers 1, 2, ...
The user-side computer manages the user-side database. The computers 400, 500 ... Focus on the data processing device, the floppy disk drives 406, 506 ..., The consoles 408, 508.
Auxiliary disk device 410, 510 ..., Printer 41
2, 512 ... Each user-side database is composed of parts configuration information, parts link information, process related information, and process link information.

From the host-side database 200a, first, an allocation text group forming allocation information is output. This allocation text group is, as illustrated in FIG. 7, a group of allocation texts each showing the relationship between its own product number-child product number-quantity (in the case of the model of FIG. 2, 10 as shown in the left column of FIG. 3). It consists of individual allocation texts).

Next, a work-in-process text group forming work-in-process information is output. This work-in-process text group is, as illustrated in FIG. 7, a group of work-in-process texts each showing the relationship between its own product number and its own process (in the case of the model of FIG. 2, as shown in the column in FIG. 3, It consists of 7 work-in-progress texts).

Next, among the arrangement information, an in-house production arrangement text group constituting arrangement information regarding in-house production is output. This in-house production arrangement text group is, as illustrated in FIG. 7, a group of in-house production texts each showing the relationship of child part number-self process-preceding process (in the case of the model of FIG. 2, the right column of FIG. 3). It is composed of 10 in-house production arrangement texts).

Finally, out of the order information, the outsourced order text group that constitutes the order information regarding the outsourced product is output. As shown in FIG. 7, this subcontracting order text group is composed of a group of subcontracting order texts each showing the relationship between the child part number, the receiving party, and the supplier. For example, in the model of FIG. 2, if the process indicated by J2 is a subcontractor, the subcontracting order text indicates that the subordinate part number indicated by a hollow rectangle is delivered to the process J5 from the supplier J2. Will be remembered. Such text groups are displayed on the host terminals 402, 502 ... Floppy disks 404, 5
Written in 04.

When the host terminal 402 is operated to extract data from the host side database 200a, the production information of the factory 420 is extracted and sent, and when the terminal 502 is used, the production information of the factory 520 is sent. Since the operation by each user side computer is the same, the case of the user side computer 400 of the factory 420 will be described below.

The allocation information, work-in-progress information, and arrangement information sent from the host-side database 200a and stored in the floppy disk 404 are stored in the user-side computer 40.
0 is set in the floppy disk drive 406 and read. Here, the user computer 400 is shown in FIG.
The process of is executed. First, in step S2, the allocation information is sorted by the parent product number. As a result, in the allocation information shown on the left side of FIG. 3, the parent part numbers are randomly arranged,
As shown on the left side of FIG. 4, it is substantially converted into the state classified by the parent product number. Next, in step S4, for each sorted parent part number, the child part number and the number of pieces of data corresponding to the same parent part number are counted. In the case of the example shown on the left side of Fig. 4, it is counted that the parent part number of the hatched circle corresponds to one child part number, and the parent part number indicated by the rectangle and two circles corresponds to two child part numbers. Is done.

Then, in step S6 of FIG. 5, the parts configuration information file in the user side database is formatted. Here, in the case of the data exemplified in FIG. 4, an area for storing one set of child part number and number of data is secured in the first eye slot, and an area for storing one set of data is also set in the second eye slot. It is secured, and the third eye slot is formatted so as to secure an area for storing two sets of data.

After the format is completed, next step S8
Then, the data of the parent part number, the child part number, and the number of pieces are stored in the formatted area. In this way, the component configuration information indicating the relationship of parent part number-slave part number-quantity is transferred to the user side database. Next, in step S10, the component configuration information is searched, and the link relationship of the eye slots with the child product number as the parent product number is searched.

As a result of the above processing, the data structure schematically shown in FIG. 8 is obtained. Here is the eye slot 6,
5, 4, 7 and 2 are illustrated, and the eye slot 6
2 sets of data are stored in the eye slot 5, 2 sets of data are stored in the eye slot 5, and 1 set of data is stored in the eye slots 4, 2 and 7. The child part number of the eye slot 6 is the parent of the eye slots 5 and 7. It is a product number and the child product number of eye slot 5 is eye slot 4
And 2 are parent product numbers. In this way, the part link information shown in the lower left of FIG. 4 is obtained.

Since the data is transferred to the user side database based on the above processing, the data is stored in the user side database in a state of being classified by the parent part number, and the child part number is stored based on the parent part number. The processing time when searching for or the number thereof is significantly shortened. Further, by using the part link information, it is possible to remarkably easily search for a part → a child part → a grandchild part.
That is, the user side database has a data structure that allows the user side to search and provide necessary information in a short time.

Next, the process related information will be described with reference to step S12 and subsequent steps in FIG. First, step S12
Sort the work-in-process text group, in-house production arrangement text group, and outsourced arrangement text group using your process as a key. As a result of this, FIG.
In the host-side database illustrated in FIG. 3, data of the same self-process which is randomly present is converted into a state in which the process is substantially classified as shown in the upper right column of FIG.

Next, the number of data of the own product number-child product number-preceding process corresponding to the own process classified in step S14 is counted. Next, in step S16, the process related information file is formatted. As a result, as schematically shown in FIG. 9, a storage area necessary for storing data indicating the relationship between the own process number, the slave product number, and the previous process corresponding to the own process is secured. .. As a result, linking between the own process and the own product number, linking between the own process and the child product number, and linking between the child product number and the previous process are performed. In this case,
An eye slot may be provided for each of the own product number, the child product number, and the previous process, and the information for linking the eye slots may be stored separately to associate the own process, the own product number, the child product number, and the previous process. FIG. 9 schematically shows linking by this method, but as shown in FIG. 8, formatting is performed by a method of linking own process-own product number-child product number-previous process in one eye slot. May be.

When the formatting is completed, next, in the storage area formatted in step S18 of FIG.
Memorize your own product number, child product number, and previous process data. This provides process-related information. Finally step S2
At 0, the process-related information is searched, and the data for linking the eye slot having the previous process as its own process is obtained. In the case of FIG. 9, the pre-processes of the own process J9 are J8 and J6, and the pre-process of J8 further shows J4 and J5 as the pre-processes.

In this way, the process link information shown in the lower right of FIG. 4 is obtained. In this case, the front process of the eye slot 15 is linked to the eye slots 16 and 14, and the front process of the eye slot 14 is linked to the eye slots 11 and 13. As a result, in the user side database, the product number, child product number,
The data of the previous process is stored, and the data structure is such that the search can be done in a short time. In addition, the chain of previous processes can be easily searched from the process link information, and the information of the previous process that affects the own process can be easily searched.

In this way, the data in the host side database is transferred to the user side database constructed with a data structure that is easy for the user to use.
In the above description, the simple production system illustrated in FIG. 2 is targeted for convenience of description. However, the present invention exhibits extremely practical utility in the case of a large-scale production system. For example, in the case of a system producing up to 20,000 kinds of parts, the present invention increases the search speed several hundred times. It becomes possible to do.

[0030]

According to the present invention, since the host side database and the user side database, which have different data structures because they have different purposes of use, can be used separately in the state where the data are integrated, It is possible to use both the integrated management of the production system and the detailed management of each management unit. Furthermore, the data retrieval time can be shortened, and an extremely easy-to-use database system can be realized.

[Brief description of drawings]

FIG. 1 is a diagram schematically showing the concept of the present invention.

FIG. 2 is a diagram showing a model of a production system used for explanation.

FIG. 3 is a diagram illustrating a data structure of information sent from a host-side database.

FIG. 4 is a diagram illustrating a data structure of user-side data.

FIG. 5 is a diagram showing an example of a processing procedure for data transfer.

FIG. 6 is a diagram showing an embodiment of a production management computer system.

FIG. 7 is a diagram showing a group of texts sent from the host side database.

FIG. 8 is a diagram schematically showing a data structure of parts configuration information in a user side database.

FIG. 9 is a diagram schematically showing a data structure of process-related information in a user database.

[Explanation of symbols]

 20 data transfer device 22 sorting means by parent part number 24 parts configuration information storage area securing means 26 parts link information searching means 28 sorting means by own process 30 process related information storage area securing means 32 process link information searching means

Claims (1)

[Claims] 1. Allocation information indicating a relationship between parent part number-slave part number-quantity, sent from a host side database storing production information, in-process information indicating a relationship between own part number and own process, own process-slave part number- Arrangement information indicating the relationship of the previous process is input, and part configuration information indicating the relationship between parent part number-slave part number-quantity, part link information indicating the link relationship of the part configuration information with the child part number as the parent part, own process- A device that transfers data to a user-side database that consists of process-related information that indicates the relationship between own process number, child process number, and previous process, process link information that indicates the link relationship between process-related information that uses the previous process as its own process, and Yes, means for sorting the allocation information by parent part number, child part number corresponding to the parent part number for each sorted parent part number-
A means for reserving a component configuration information storage area for storing the relationship of the number in the user side database, and a search for information on an area for storing data on a sorted parent part number with a child part number as a parent part number. Means for storing in the user side database, means for sorting the work in process information and the arrangement information in the own process, own product number corresponding to the own process for each sorted own process-
A means for reserving a process-related information storage area for storing the relationship between the child part number and the previous process in the database on the user side, and a region for storing the data related to the sorted own process with the previous process as the own process Means for retrieving information to be stored in the user side database, and a data transfer apparatus between the databases.