JP3064619B2 - Production management database management device - 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 production management database.

[0002]

2. Description of the Related Art Production systems have become large-scale, and various parts or products have been produced in various production processes. In order to manage this, production-related data is stored intensively. In addition, a database that provides necessary data as needed is used. Such a database and its utilization technology are disclosed in Japanese Patent Application Laid-Open No. 1-112364 and Japanese Patent Application Laid-Open No. 1-112365. By using this database, it is possible to easily search which component is composed of which child component. can do.

[0003]

However, in order to perform production management rationally, it is not enough to know which parts are composed of which child parts, and it is not enough to know in which process they are produced. You need to know. For this reason, the database needs to store at least both data relating to the component configuration and data relating to the process.

[0004] Naturally, necessary data must be input to the database. Here, data and the like regarding a part and child parts necessary for producing the part are input from, for example, a design department. On the other hand, information such as in which process these parts are produced is input from, for example, a process management department. In this way, the input timing is shifted because data on the same event is input from different departments, and there is no data on the corresponding process even though the data on the component configuration is input in the database. Occurs. Further, when the production system becomes large-scale, the number of input data becomes enormous, and the possibility of inputting erroneous data increases.

In such a case, if necessary data is retrieved from the database to contribute to the production planning or the like, an erroneous production plan is made or the production plan cannot be made. I do. Therefore, in the present invention, an attempt is made to construct a database management device that does not output erroneous data erroneously and perform erroneous production management.

[0006]

In order to solve the above-mentioned problem, the concept of the present invention is a management device 14 schematically shown in FIG. 1, that is, a management device 14 of a production management database 16, and a parent component. Means 4 for inputting allocation information 2 indicating the relationship between the part and its constituent parts, determining whether the data is appropriate, and writing only the determined data to the production management database 16; Means 8 for inputting in-process information 6 indicating a relationship between production processes, judging the suitability of the data, and writing only the data judged to be appropriate to the production management database 16; The entered allocation information and the in-process information are mutually checked, and the data mutual checking means 10 for identifying inconsistent data is identified as inconsistent by the data mutual checking means 10. It has been banned output data, created a production management database management device 14 and a data output means 12 to allow the output of the other data.

[0007]

According to the management apparatus 14, the allocation information relating to the component configuration and the in-process information relating to the process are checked in advance.
Inconsistent data (for example, parent part A is child part B
And C, and the parent part A is the child part B
, And C and D) are not input to the production management database 16. If the data mutual checking means 10 does not match the data (for example, if there is allocation data relating to the component configuration of the parent part A, but there is no data on the process of producing the parent part A in the in-process information, the allocation is performed). Information and the in-process information) are specified, and the data output means 12 outputs the inconsistent data from the database 16.
Prohibited by. Therefore, no inconsistent data or inconsistent data is output from the database 16, and erroneous production management is prevented from being performed.

[0008]

FIG. 2 shows an in-company computer network system incorporating a production management database management device 14a according to the present invention. In the figure, reference numeral 20 denotes a company information database, which is a company information database management device 2.
2 manages data input / output. The production of this enterprise information database management device 22 is managed by input / output terminals 26 distributed in various places in the enterprise or the production management database 16a of this embodiment via an enterprise information communication network 24 which is a WAN between factories. Connected to the factory. In the figure, reference numeral 28 denotes a communication control device functioning as a gateway, through which data is transmitted between the enterprise information communication network 24 and the production management communication network 40 which is a LAN in the factory.

A production management database 16a is connected to the LAN 40 by a production management database management device 14a.
The data in the company information database 20 can be transferred to the production management database 16a. Further, the production management device 30 is connected to the LAN 40, and it is possible to make a production plan based on the data of the production management database 16a. Data necessary for the production management device 30 to make a production plan is sent to the LAN 40 by the production management database management device 14a.

The LAN 40 also has a production instruction device 3 for each process.
6 is connected, and instructs data such as what and when to produce each process based on a production plan drafted by the production management device 30. Further, a production result input device 38 for each process is connected to the LAN 40 to input production results. The data relating to the production result is sent to the production management device 30 and stored as production result information 34. Further, the production management device 30 compares the drafted production plan with the production results, and corrects the production plan as necessary. Thus, the production plan information 32 is adapted to the current state.

FIG. 3 shows the details of the management device 14a of the production management database 16a, which has a file for temporarily storing data transmitted and received between the LAN 40 and the production management database 16a. In the figure, reference numeral 50 denotes an allocation information reception file for temporarily storing allocation information sent from the company information database 20 via the LAN 40. As shown in FIG. 4, the allocation information is a certain product number (own product number).
This data is composed of data indicating how many child parts of which child part number are used by the part, and a data group including an expiration date of the data. The allocation information receiving file 50 is connected to the allocation information propriety judging / writing device 4a, and the applicability judging / writing device 4a processes according to the processing procedure of FIG. The process of FIG. 5 is started when the management apparatus 22 sends allocation information on the factory from the company information database 20. First, the allocation information reception file 50 is opened (S52), and the allocation information is stored in the file. 50 (S53), it is determined whether or not the same part number, which may be an error unique to the allocation information, is defined twice (S54). It is determined whether the relationship, that is, the parent-child relationship is defined twice (S55), and if any, an error process is performed (S6).
0), the allocation information receiving file 50 is closed (S5).
9). If there is no error, the production management database 16
a is opened (S56), and the allocation information is written into the database 16a (S57). Here, as shown in FIG. 10, data (record) having the child product number as its own product number is written together with information for linking. After the writing is completed, the production management database 16a is closed (S58), and the allocation information reception file 50 is also closed (S59).

In FIG. 3, reference numeral 54 denotes a work-in-process information receiving file, and the work-in-process information sent from the company information database 20 by the company information database management device 22 via the company information communication network 24 and the production management communication network 40. Can be temporarily stored. The in-process information receiving file 54 is connected to the production management database 16a via the in-process information appropriateness determination writing device 8a.

As shown in FIG. 6, the work-in-progress information is composed of a data group consisting of data indicating in which process the part indicated by which part number is produced according to what condition and an expiration date of the data. I have. The in-process information propriety determination writing device 8a processes the in-process information according to the processing procedure shown in FIG.

The process shown in FIG.
Is started when the in-process information is sent from the server (S7).
1) First, the process information receiving file 54 is opened (S)
72), and in-process information is written in the file 54 (S7).
3). Next, it is determined whether or not the same process that may be an error specific to the in-process information is defined twice (S7).
4) It is determined whether or not the data is a data that defines the relationship between the process and the product number twice (S75). If the data is any of them, an error process (S80) is performed, and the process information receiving file 54 is closed. On the other hand, if the data is not the double definition data, the production management database 16a is opened (S76), and the in-process information in the file 54 is written into the database 16a (S76).
77). Here, data for linking the in-process information to the order information described later is also written. That is, as illustrated in FIG. 11, in-process information having the same own process and arrangement information are linked. After the writing is completed, the database 16a is closed (S78), and the in-process information receiving file 54 is also closed (S79).

In FIG. 3, reference numeral 56 denotes an arrangement information receiving file, which is sent from the company information database 20 by the company information database management device 22 via the company information communication network 24 and the production management communication network 40. Arrangement information can be temporarily stored. The arrangement information receiving file 56 is connected to the production management database 16a via the arrangement information propriety determination writing device 58.

As shown in FIG. 8, in the order information, a child part indicated by a child part number is required in which step (own step), and the child part is arranged from which step (previous step) and under what conditions. The data group is composed of data indicating whether the data is to be transmitted and the expiration date of the data. The arrangement information propriety determination writing device 58 processes the arrangement information in accordance with the processing procedure shown in FIG.

The processing shown in FIG.
Execution is started when arrangement information is sent from the server (S9).
1) First, open the arrangement information receiving file 56 (S
92), the arrangement information is written in the same file 56 (S9)
3). Next, it is determined whether or not the data is the data that defines the same process that may be an error unique to the order information (S9).
4), it is determined whether or not the data is a data that double defines the relationship between the own process, the child product number, and the previous process (S95), and if it is any one, an error process is performed (S100), and the arrangement information reception file 56 is closed (S99). On the other hand, if the data is not the double definition data, the production management database 16a is opened (S96), and the arrangement information in the file 56 is written into the database 16a (S97). Here, as described above and as illustrated in FIG. 11, the information is stored in a state of being linked to the in-process information having the same own process. Further, data for linking arrangement information with the previous process as its own process is also stored. After the writing is completed, the database 16a is closed (S98), and the arrangement information receiving file 5 is further stored.
4 is also closed (S99). After the allocation information, the in-process information, and the arrangement information from which the unique error has been eliminated are written in the production management database 16a in this manner, the allocation / in-process / arrangement information mutual check device 10a executes the processing procedure shown in FIG. Is performed, and it is determined whether or not the data are consistent with each other.

The processing of FIG. 12 is executed at a predetermined time (S1
20) First, the production management database 16a is opened (S121), and then the allocation information is read (S12).
2) It is determined whether the own product number included in the lead allocation information is also present in the in-process information (S12).
3) Further, it is determined whether or not the child part number included in the allocation information is also stored as the child part number in the arrangement information (S).
124) If both exist, the data is consistent, so an OK flag is given to the allocation information (S12).
5) If any of these conditions are not satisfied, data consistency is not recognized, so an NG flag is added to the allocation information (S126).

Next, the in-process information in the production management database 16a is read (S127), and it is determined whether or not there is allocation information having the same own part number as the own part number included in the read in-process information. (S128) Further, it is determined whether or not there is order information that stores a part having the same own part number as a child part number (S129). If both are present, since the consistency between the data is ensured, an OK flag is given to the read in-process information (S130),
If any one of them does not exist, the in-process information is not consistent with other data, so an NG flag is given (S131).

Further, the arrangement information in the production management database 16a is read (S132), and it is determined whether or not data having the same part number as the child part number contained in the read arrangement information as the child part number exists in the allocation information. Is determined (S133),
Further, it is determined whether or not data including the preceding process included in the read arrangement information as its own process exists in the in-process information (S134). If both exist, since the consistency between the data is ensured, an OK flag is added to the read arrangement information (S135), and if neither of them exists, the arrangement information is replaced with another data. NG flag is added because it does not match (S13
6). After the above processing is completed, the production management database 16
a is closed (S137).

As shown in FIG. 3, the part management data transmission file 6 is stored in the production management database 16a.
2 are connected via a component development data editing device 12a. The part development data transmission file 62 sends out data necessary for a production plan to the production management device 30 via the LAN 40 as shown in FIG.

FIG. 13 shows the component development data editing device 12a.
The data in the database 16a is written to the file 62 according to the processing procedure shown in FIG. The processing in FIG. 13 starts to be executed when transmitting the component development data (S151),
First, the production management database is opened (S15
2). Next, allocation information, work-in-process information, and arrangement information are read (S153, S154, S155), and then the production management database is closed (S156).

Next, the own product number included in the in-process information to which the OK flag is added in step S130 of FIG. 12 is used as a key, and in the order information to which the OK flag is added in step S135 of FIG. It searches for arrangement information having its own product number as a key as a child product number, and extracts data linking it (S157). As a result, FIG.
Are linked.

After that, in step S135 in FIG. 12, the previous process included in the arrangement information to which the OK flag is added is used as a key, and in step S130 in FIG. The in-process information having the process as its own process is searched, and data linking the process is extracted (S158). As a result, FIG.
Are linked.

Further, in step S130 of FIG. 12, the own part number included in the in-process information to which the OK flag is added is used as a key, and in step S125 of FIG. 12, the key is used as the key in the allocation information to which the OK flag is added. A search is made for allocation information having the product number as its own product number, and data for linking the search is extracted (S159). As a result, the relationship shown in FIG. 14C is linked.

After the above processing is completed, step S in FIG.
At 160, the part development data transmission file 62 is opened, and the allocation information, the work-in-process information, the order information, and the information linking them (the link information shown in FIGS. 10 and 11 and the link information shown in FIG. 14; When the data is written into the management database 16a, the latter is extracted by the component development data editing device 12a.)
Is written to the component development data transmission file 62. Then, the component development data transmission file 62 is closed in step S162 of FIG.

The data in the part development data transmission file is sent to the production management device 30 shown in FIG. 2, and the production management device 30 makes a production plan using this data. Here, the data in the part development data transmission file, that is, the data sent to the production management device, is free from errors in the data itself, and is limited to data having consistency among the allocation, work in process, and arrangement information. This prevents the production management apparatus 30 from making an erroneous production plan or making it impossible to make a production plan.

Finally, as shown in FIG. 3, the database management device 14a further has a production management data book table editing device 66 and a data book table output device 64. Here, the data book table editing device 66 executes the processing shown in FIG.

As shown in FIG. 15, the production management data book table editing device 66 operates when the production management data book table is output (S180), and first receives a search key (S18).
1). When the search key is input, the production management database 16a is opened (S182), and data specified by the search key is searched (S183). Here, the search target is OK in steps S125, S130, and S135 in FIG.
S126, S13 as well as the data with the flag
1,136, the data to which the NG flag is added.
After the search is completed, the production management database is closed (S
184), and edited to a data structure suitable for book creation (S1).
85) The book table edited by the production management data book table output device 64 is printed out. Thus, the inconsistent data and the like can be known by the oplator.

In the present embodiment, the data on the process is composed of the work-in-process information and the order information. However, it is only necessary to have the data on the process and the product number, and the data on the process is necessarily composed of two or more types of data. You don't need to be.
In FIG. 3 showing the present embodiment, various files, discrimination writing devices 50, 54, 56, 4a, 8a, 58, a mutual data checking device 10a, and a component development data editing device 12a are displayed as blocks as different entities. But
These devices or files may not be independent and may be embodied in one computer system. The component development data editing device 12a
Is an embodiment of the data output means 12 which prohibits the output of inconsistent data and permits the output of other data.

[0031]

According to the present invention, the accuracy of data in the production management database is improved, and accurate production management becomes possible. In addition, information on parts and information on processes can be input independently from, for example, a design department, a process management department, a physical distribution management department, or the like, and even if they are input independently, it does not hinder production plan drafting. For this reason, data updating and change measures are remarkably facilitated, especially when switching to a new product, and the transition to a new product can be performed smoothly.

[Brief description of the drawings]

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

FIG. 2 is a production management database management device 14 of the present invention.
The figure which shows the structure of the in-company computer system which incorporated "a".

FIG. 3 is a diagram showing a configuration example of a production management database management device 14a.

FIG. 4 is a diagram schematically showing a data structure of allocation information.

FIG. 5 is a diagram showing a processing procedure by an allocation information propriety determining writing device.

FIG. 6 is a diagram schematically showing a data structure of in-process information;

FIG. 7 is a diagram showing a processing procedure by the in-process information propriety determination writing device.

FIG. 8 is a diagram schematically showing a data structure of arrangement information.

FIG. 9 is a diagram showing a processing procedure by an arrangement information propriety determining writing device;

FIG. 10 is a diagram showing a link relationship when writing in a production management database.

FIG. 11 is a diagram showing a link relationship when writing in a production management database.

FIG. 12 is a diagram showing a processing procedure by means for mutual checking of allocation, work in process, and arrangement information.

FIG. 13 is a diagram showing a processing procedure performed by the component development data editing device.

FIG. 14 is a diagram showing a link relationship by the component development data editing device.

FIG. 15 is a diagram showing a processing procedure by the production management data book table editing apparatus.

[Explanation of symbols]

 4: Assignment information suitability judging / writing means 4a: Assignment information suitability judging / writing device 6: In-process information suitability judging / writing means 6a: In-process information suitability judging / writing device 10: Data mutual checking means 10a: Assignment / work-in-progress / arrangement information Mutual check means 12: Data output means 12a: Data editing device for part development

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

Claims (1)

(57) [Claims] 1. A management device for a production management database, which inputs allocation information indicating a relationship between a parent part and child parts constituting the parent part, determines whether the data is appropriate, and outputs only the data determined to be appropriate. Means for writing to the production management database; input of in-process information indicating a relationship between a part and a process of producing the part; judging the suitability of the data; and writing only the data judged to be appropriate to the production management database. Means for reciprocally checking allocation information and work-in-progress information written in the production management database, and specifying data which does not match, data which is specified as inconsistent by the data mutual checking means. A data output means for prohibiting the output of data and permitting the output of other data.