JP3057868B2 - Data transfer equipment between databases - Google Patents

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 For example, in a large-scale production system such as an automobile assembly maker, various products are produced in various production processes, and a database storing production information is used for management of the production system. Is used.

In the case of a model production system as shown in FIG. 2, for example, in the case of a model production system as shown in FIG. 2, for example, in step J4, a part having a part number indicated by a hatched circle is produced by using a part having a part number indicated by a hollow circle, and is produced. It is configured as an accumulation of data or the like indicating supply to the process J7. In addition to this, for example, information indicating which part number is composed of which part number, information indicating which child part number required in the own process is produced in which preceding process, and information of the part All data useful for production management, such as unit prices, parts delivery timing, and the time required for parts production, are stored.
A person in charge of production management retrieves and extracts necessary data from the database, and manages production or processes using this data.

[0004]

However, this database is extremely enormous for a large-scale production system. In particular, in the case of a super-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 is very large. For this reason, it takes longer to extract data necessary for management of each factory, and the database has begun to become larger as the extraction time becomes longer than practical.

In order 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 management according to the actual situation can be performed 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.

Under 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 of course necessary to be able to send and receive data between the host and user databases. However, the user-side database should be configured so that data useful for management of each management unit can be easily extracted, and the host-side database should be configured so that data useful for centralized management of the production system can be easily extracted. For this reason, the data structure of both databases is usually different.

For this reason, at present, a system which uses the host side database and the user side database properly and maintains unification of data of both databases has not yet been realized. Therefore, in the present invention, a device that enables the transfer of data between databases having different data structures has been developed, so that both the host-side database and the user-side database can be used interchangeably while ensuring unified data. is there.

[0008]

For this purpose, according to the present invention, a data transfer apparatus whose concept is schematically shown in FIG. 1, that is, a host-side data storing production information.
Parts supplied from the process sent out from the base 2 (parent
Part number)-Parts supplied to the process (child part number)-Child
The allocation information 12, which indicates the relationship between the number of parts of the part number,
Part number)-of the process of supplying parts of the part number concerned (own process)
In-process information 14 showing the relationship, process (own process)-the own process
Parts (child part number)-supply parts of the child part number
Input the arrangement information 16 indicating the relationship of the process (previous process)
Parts supplied from the process (parent part number)-supplied to the process
Parts (child part number)-Relationship between the number of parts of the child part number
Configuration information 42 indicating the component configuration information,
Includes child part number included in the configuration information as parent part number
Component link information 4 indicating a link relationship with component configuration information
4. Process (own process)-Parts supplied from the process (own process)
Parts)-Parts supplied to the process (child part number)-
Process that shows the relationship of the process (pre-process) of supplying parts of the child part number
Process related information 46, process related information, and the process related information
Process related that includes the included previous process as its own process
The process link information 48 indicating the link relationship with the information
Created and stored in the user database 40 for managing the production system.
Data transfer device 20 between databases for transferring data
And manages the allocation information 12 in the database on the user side.
Means 22 for sorting by the parent part number of the production system
For each parent part number specified, the child part number corresponding to the parent part number-the child
Part configuration information indicating the relationship between the number of parts in the part number
Means 24 for storing in a database;
Search the component configuration information for each parent part number and find the component configuration information
And the child part number included in the component configuration information as the parent part number
Search for link relationship with included component configuration information
And store the search results in the user database
Means 26, in-process information 14 and arrangement information 16
Means 28 for sorting in its own process managed by the database;
For each of the sorted own processes, the own part number corresponding to the own process
-Process part information indicating the relationship between-child part number-previous process
Means 30 for storing in a database;
Search for process-related information for each process and search for process-related information
And the previous process included in the process-related information
Searching the link relationship between comprise that process related information
And store the search results in the user database
Device 2 for transferring data between databases having means 32
0 was created.

[0009]

The operation of the above-described data transfer apparatus will now be described using the production system model shown in FIG. 2 as an example. FIG. 2 shows that, for example, in the process J4, a child part whose part number is indicated by a hollow circle and a child part indicated by a hollow triangle are used to produce a part indicated by a hatched circle and supplied to the step J7, A production system for producing an article indicated by a hatched triangle and supplying the article to a process J8 is schematically illustrated. This production system is a production system in one factory or management unit, and there are a plurality of such production systems. Although FIG. 2 illustrates a very simple production system, it is obvious 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 on all the production systems is stored in a host-side database. Here, when data in the host-side database is transferred to the user-side database, only data related to the production system managed by the user-side database is extracted from the host-side database and sent out. More specifically, allocation information indicating the relationship between the parent product number, the child product number, and the used number of the child product numbers, in-process information indicating the relationship between the own product number and the own process, and arrangement information indicating the relationship between the own process, the child product number, and the previous process. Is 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.

In the data thus sent out, the allocation information is sorted by the parent part number sorting means 22 for each parent part number. The child part number-number data corresponding to the sorted parent part 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 a form in which the data of the child part number-number corresponding to the sorted parent part number is associated therewith. 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 component 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 7 and 5 are linked to the eye slot 6 is searched. Is done. Here, the eye slot is data that is referred to when searching for each component configuration information, and is one of information indicating an area where the component configuration information is stored.

[0012] Almost the same processing is performed on the in-process information and the order information. As a result, as shown in FIG. 4, the own process-own product number-child product number is associated with the sorted own process. Process related information indicating the relationship of the previous process is obtained,
In addition, information on the link relation of the process in which the previous process is the own process can be obtained. In this way, the information sent from the host database is transferred to the user database having a different data structure.

[0013]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Next, in order to more specifically describe the structure of the present invention, an embodiment embodying the present invention will be described.
FIG. 6 shows the configuration of a computer system that manages the production of factories 420, 520, etc. A host computer 200 is used to centrally manage production information of all factories, and the host computer 200 constructs a host-side database 200a. The host computer 200 is connected to host terminals 402, 502,... Provided at each factory via a communication line. This host computer 200 provides, for each host terminal,
Send out allocation information, in-process information and arrangement information. The arrangement information is composed of in-house arrangement information and outsourcing arrangement information. The host terminals 402, 502,... Save the transmitted data on the floppy disks 404, 504,.

In the figure, 400, 500... Indicate user-side computers 1, 2,.
The user side computer manages the user side database. The computers 400, 500,... Mainly include a data processing device, floppy disk drives 406, 506, consoles 408, 508,.
Auxiliary disk devices 410, 510, printer 41
2, 512, etc. Each user database is composed of component configuration information, component link information, process related information, and process link information.

The host-side database 200a first outputs a group of allocation texts constituting allocation information. As shown in FIG. 7, this allocation text group is a group of allocation texts each showing the relationship between the own product number, the child product number, and the number (in the case of the model of FIG. 2, as shown in the left column of FIG. Individual allocation texts).

Next, a work-in-progress text group constituting the work-in-progress information is output. As shown in FIG. 7, this in-process text group is a group of in-process texts indicating the relationship between the own product number and the own process one by one (in the case of the model of FIG. 2, as shown in the column in FIG. 7 in-process texts).

Next, among the arrangement information, an in-house arrangement text group constituting the in-house arrangement information is output. As shown in FIG. 7, this group of in-house arranged texts is a group of in-house produced texts each showing the relationship between child part number, own process, and previous process (in the case of the model of FIG. 2, the right column of FIG. 3). As shown in FIG. 2, the text is composed of ten in-house prepared texts.

Finally, out of the arrangement information, a group of subcontract arrangement texts constituting the arrangement information on the outsourced product is output. As shown in FIG. 7, this outsourcing arrangement text group is composed of a group of outsourcing arrangement texts that indicate the relationships among child part numbers, receivers, and suppliers one by one. For example, in the model of FIG. 2, if the process indicated by J2 is a subcontractor, the subcontracting arrangement text includes information indicating that a part having a child part number indicated by a hollow rectangle is delivered from the supplier J2 to the process J5. Is stored. Such text groups are stored in the floppy disks 404, 5 on the host terminals 402, 502,.
04 ... is written.

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 transmitted. When the terminal 502 is used, the production information of the factory 520 is transmitted. Since the operation by each user computer is the same, the case of the user computer 400 in the factory 420 will be described below.

The allocation information, in-process 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 side computer 400 is shown in FIG.
Execute the processing of First, in step S2, the allocation information is sorted by parent part number. As a result, in the allocation information illustrated on the left side of FIG. 3, the parent part numbers are arranged randomly,
As shown on the left side of FIG. 4, it is substantially converted into a state classified by the parent part number. Next, in step S4, for each sorted parent part number, the number of data of the child part number and the number 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 one child part number corresponds to a parent part number indicated by a hatched circle, and two child part numbers correspond to a parent part number indicated by a rectangle and two circles. It is done.

Thereafter, in step S6 in FIG. 5, the component configuration information file in the user database is formatted. Here, in the case of the data illustrated in FIG. 4, an area for storing one set of child part numbers and the number of pieces of data is secured in the first eye slot, and an area for storing one set of data is also stored in the second eye slot. The third eye slot is formatted so as to secure an area for storing two sets of data.

After the format is completed, step S8 follows.
Then, the data of the parent part number, the child part number, and the number are stored in the formatted area. In this way, the component configuration information indicating the relationship between the parent part number, the child part number, and the number is transferred to the user-side database. Next, in step S10, component configuration information is searched, and a link relationship of an eye slot having a child part number as a parent part number is searched.

As a result of the above processing, a data structure schematically shown in FIG. 8 is obtained. Here is eye slot 6,
5, 4, 7, and 2 are illustrated, and an eye slot 6
Stores two sets of data, two sets of data are also stored in the eye slot 5, and one 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 part number of the eye slots 5 and 7. The part number of the eye slot 5 is the child part number.
2 is a parent part number. In this way, the component link information shown in the lower left of FIG. 4 is obtained.

Since the data is relocated 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 processing time when searching for the number thereof is significantly reduced. Also, by using the component link information, the search of the component → the child component → the grandchild component can be performed very easily.
That is, the user database has a data structure that allows the user 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
Sorts the in-process text group, the in-house arranged text group, and the outsourced arranged text group using the own process as a key. As a result, FIG.
In the host-side database exemplified in FIG. 4, the data of the same self-process that exists randomly is converted into a state classified substantially for each self-process as shown in the upper right column of FIG.

Next, the number of data of own part number-child part number-previous step corresponding to the own step 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 product number, the child product number, and the previous process corresponding to the own process is secured for each own process. . 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, your own process,
An eye slot may be provided for each of the own product number, the child product number, and the previous process, and information for linking the eye slots may be separately stored, so that the own process, the own product number, the child product number, and the previous process may be associated with each other. FIG. 9 schematically shows that the links are made in this manner. However, as shown in FIG. 8, the format is such that the own process, own product number, child product number, and previous process are linked in one eye slot. You may.

When the formatting is completed, the process is stored in the storage area formatted in step S18 in FIG.
The data of own part number, child part number and previous process are stored. Thereby, process-related information is obtained. Finally, step S2
At 0, the process-related information is searched to obtain data for linking an eye slot having the previous process as its own process. In the case of FIG. 9, the pre-process of the own process J9 is J8 and J6, and the pre-process of J8 further indicates that J4 and J5 are pre-processes.

Thus, the process link information shown at the lower right of FIG. 4 is obtained. In this case, the previous process of the eye slot 15 is linked to the eye slots 16 and 14, the previous process of the eye slot 14 is linked to the eye slots 11 and 13, and the like. As a result, in the user database, the own product number, the child product number,
The data of the previous process is stored, and the data structure has a short search time. Also, the chain of the previous process can be easily searched from the process link information, and the information of the previous process affecting the own process can be easily searched.

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

[0030]

According to the present invention, since the host side database and the user side database having different data structures because of their different purposes of use can be selectively used in a state where the data is unified, all data can be used. It is possible to use both centralized management of the production system and fine-grained management for each management unit. Further, the data search time is shortened, and an extremely convenient database system can be realized.

[Brief description of the 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 description.

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 text group sent from a host-side database.

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

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

[Explanation of symbols]

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

────────────────────────────────────────────────── ─── Continued on the front page (58) Fields surveyed (Int. Cl. ⁷ , DB name) G06F 17/60 G06F 12/00 505 G06F 17/30 JICST file (JOIS)

Claims (1)

(57) [Claims] 1. Host-side data storing production information
Parts sent from the process sent from the base (parent products
No.)-Parts supplied to the process (child part number)-The child product
Allocation information indicating the relationship between the number of parts of the number, the part (own part number)
-The relationship between the process of supplying parts of the relevant part number (own process)
In-process information, process (own process)-supplied to the process
Parts (child part number)-the process of supplying parts of the child part number
Enter arrangement information indicating the relationship of (previous process), and supply parts (parent part number) from the process-supplied to the process
Parts (child part number)-Indicates the relationship between the number of parts of the child part number
Component configuration information, component configuration information, and
Component configuration that includes the included child part number as the parent part number
Part link information indicating the link relationship with the information,
Process)-Parts supplied from the process (own component)-
Parts supplied to the process (child part number)-parts of the child part number
Process-related information indicating the relationship between the supply process (previous process) and process
Process related information and the previous process included in the process related information
Relationship with process-related information that contains the process as its own process
And process link information to manage the production system.
Database to transfer data to the user side database
A data transfer device between production systems, and a parent of a production system that manages allocation information in a user database.
Means to sort by part number, and for each sorted parent part number, child part number corresponding to the parent part number
-Parts configuration information indicating the relationship between the number of parts of the child part number
Means for storing in the user-side database ; searching for component configuration information for each sorted parent part number;
Component configuration information and child part numbers included in the component configuration information
Relationship with component configuration information that contains the parent as part number
Search and record the search results in the user database.
The user side database manages the means to remember and the in- process information and the arrangement information
Means for sorting in the production process, and for each sorted process, the product number corresponding to the process
-Child part number-Process related information indicating the relationship between the previous process and the user side
Search the means for storing in the database and the sorted process-related information for each
And degree-related information, the step before being included in the related information about the Engineering
Relationship with process-related information that contains the process as its own process
Search and record the search results in the user database.
Means for transferring data between databases having means for remembering .