JP2600212B2 - Data processing device - Google Patents

Description

Description: TECHNICAL FIELD [0001] The present invention relates to a data processing apparatus that expands components from a child component to pull all parent components configured using the child component.

[Summary of the Invention] A data processing apparatus according to the present invention includes, in one record, a record key including a related child part name and a parent part name, and a development section indicating presence / absence of a high-level parent part following the child part. It is stored in the component configuration file as data, and when a component is expanded, a record that matches the child component name stored in the expanded file is collated and extracted from the component configuration file. The collated record is stored in the expanded work file or end work file according to the presence or absence of the parent part at the level, and when there is no longer a matching child part name, the contents of the expanded file are rewritten with the contents of the expanded work file. Then, in the same manner, the comparison is performed, and the records in the development file are compared until no high-level parent parts are found. Is stored in the end work file, the records are classified and aggregated.
The configuration can be made without requiring a large processing capacity.

[Prior Art] In the manufacturing industry, it is necessary to determine the type and quantity of components required for a product to be produced in a certain period, and conversely, what kind of product a certain component is used for. It is important to know. Products are usually made up of so-called parts and assembled parts in which the parts have been modified. In terms of manufacturing, there are in-house parts and outsourced parts. Therefore, if the production and procurement of sub-products in accordance with the process (schedule) were to be performed from the standpoint of production management, the required number of each component was calculated based on the component configuration table of the final product, and the number of on-hand inventory was reduced. The quantity must be manufactured or ordered and procured according to the base schedule.

Finding the types and quantities of components required for products to be produced in a certain period in this way is generally called component development. There are two types of component development: forward development and reverse development. The normal development is a development for obtaining the quantity of child parts from a parent product, such as calculation of required parts and their required quantities and calculation of required quantities of delivered parts, such as ordering and production (delivery from factory). Inverse development is development for searching for a parent product (or process product) from a child part as in production calculation. These parts deployment work can be done manually when the number of parts is small, but when the number of parts is large, it becomes a complicated and enormous work requiring computerization.

A data processing device such as a computer system is used to perform the above component development (reverse development). In such a data processing apparatus, for example, based on a component configuration table of the final products A and B as shown in FIG. Parts are deployed with reference to the configuration file.

[Problems to be Solved by the Invention] In the data processing apparatus as described above, when registering information such as the parent-child relationship in the component configuration file, the name of each component and the address relationship to the parent-child component are registered. Etc. and management information are registered, and component development (reverse development) is executed with reference to them. Therefore, complicated processing is required to perform component development, and there is a disadvantage that the data processing apparatus becomes large in size.

An object of the present invention is to make it possible to perform component development (reverse development) without requiring complicated processing.

[Means for Solving the Problems] The means of the present invention are as follows.

The component configuration file means 1 (refer to the functional block diagram of FIG. 1, the same applies hereinafter) indicates a record key including a related child component name and a parent component name, and the presence / absence of a high-level parent component following the child component. The data of a plurality of records including all combinations of child parts and parent parts are stored, with the development section as data of one record.

The expansion file means 2 stores the child component name to be extracted as a record key.

The expanded work file means 3 and the end work file means 4 are used as work areas, respectively.

The collation processing means 5 stores a record including a child part name corresponding to the child part name as the record key stored in the development file means 2 into the part configuration file means 1
From the extracted record, referring to the expansion section of the extracted record to detect the presence or absence of a high-level parent part, and if there is a high-level parent part, enter the parent part name of the extracted record The record key of the parent part name is rewritten and stored in the expanded work file means 3. If there is no high-level parent part, the extracted record is stored in the end work file means 4 and the expanded file means is stored. When the collation of all the records of No. 2 is completed, an end signal 6 indicating this is output.

Upon receiving the end signal 6 from the matching processing means 5, the classification processing means 7 checks the developed work file means 3 and if a record is stored in the developed work file means 3, the classification processing means 7 If the data is written in the development file means 2 and no record is stored in the development work file means 3, each record stored in the end work file means 4 is classified and totaled.

[Operation] The operation of the means of the present invention is as follows.

The collation processing means 5 collates and extracts from the component configuration file means 1, a record including a child part name matching the child part name as the record key stored in the development file means 2,
The presence / absence of a high-level parent part is detected by referring to the development section of the extracted record. At this time, if there is a high-level parent part, the parent part name of the extracted record is rewritten to the record key of the child part name and stored in the development work file means 3. If there is no high-level parent part, the extracted record is stored in the end work file means 4.
To be stored. Then, when the matching processing means 5 outputs an end signal 6 indicating that the matching of all records in the development file means 2 has been completed, the classification processing means 7
The developed work file means 3 is collated, and if a record is stored in the developed work file means 3, the data of the record is written to the developed file means 2, and the record is stored in the developed work file means 3. If not, the records stored in the end work file means 4 are classified and totaled.

Therefore, it is not necessary to register the address relationship and the like and the management information of the parent and child parts together with the names of the individual parts, and it is not necessary to execute the part expansion (reverse expansion) while referring to them one by one. It is possible to develop parts without requiring processing capacity.

Embodiment (1) Configuration of Embodiment FIG. 2 is a diagram showing a data processing device of an embodiment. In the figure, cf is “record key RK1” and “record key RK2” including the name of the related child part and the name of the parent part, and “expansion category” indicating the presence / absence of a high-level parent part following the above child part. "Is a part configuration file storing data of a plurality of records including rough matching of all child parts and parent parts as data of one record, and $ f designates a child part name to be extracted as a record key. This is the expanded file to be stored.
◇ fw and ○ fw are the unfolding work file and end work file used as the work area, respectively.
f is an end file in which the result of component development (reverse development) is stored.

11 compares and extracts, from the component configuration file cf, a record including a child part name that matches the child part name as the record key stored in the development file $ f, and executes the “expansion” of the extracted record. Classification "
The presence or absence of a high-level parent part is detected, and if there is a high-level parent part, the parent part name of the extracted record is rewritten to the record key of the child part name and stored in the expanded work file $ fw, If there is no high-level parent part, the extracted record is copied to the end work file ○
This is a collation processing device to be stored in fw. This collation processor
Also, when the collation of all the records of the development file $ f is completed, the reference is made to the development work file $ fw, and if data is stored therein, the end signal "$" is output.
fEND ", and if no data is stored, an end signal" @fw END "is output.

12, the end signal “$ f”
END "is received, the expanded work file $ fw is collated, the records of the expanded work file $ fw are sorted, written into the expanded file $ f, and then the contents of the expanded work file $ fw Is a classification processing device I. When receiving the end signal “◇ fw END” from the matching processing device 11, the classification processing device I
This is a classification processing device II that sorts and totals each record stored in fw, stores it in the end file ○ f, and outputs an end signal “END” indicating the end of the component development process. An output device 14 receives the end signal "END" from the classification processing device II13, and prints out the end signal "END" and the component development result stored in the end file ○ f, for example.

The “file name”, “record key RK1”, “record key RK2”,
Word data such as “deployment section” is input by an operator from an input device (not shown) through the matching processing device 11,
Input is stored in them. Further, the matching processing device 11 performs normal expansion or reverse expansion in response to an instruction from the input device (not shown), that is, a “normal expansion START” or “reverse expansion START” signal.

(2) Operation of Embodiment Hereinafter, the reverse expansion operation in the data processing device having the above configuration will be described. For example, suppose there are final products A and B represented by a parts configuration table as shown in FIG. As can be understood from the figure, the final product A is a component a,
b, and c, and the final product B is composed of parts a, b,
And d. And the part a is the part 01,0
The component c is composed of components 01 and 04, and the component d is composed of components 01 and 05.

When data is input by an operator from an input device (not shown) based on such a component configuration table, the matching processing device 11 converts the data into a component configuration file cf.
To be stored. In this case, as shown in FIG. 4, the operator sets “Record key RK1” and “Record key RK2” including the related child part name and parent part name, and the high-level parent part following the child part. The “expansion section” indicating presence / absence of “1” and “0” is sequentially input as each word data of one record, delimited by a delimiter. However, “(” is a record delimiter, “,” is a word data delimiter, and “/” indicates no data. In this manner, all parent-child relationships of parts are included. Record data is stored in the component configuration file.

Here, when it is desired to tow a parent part using the part 01, after inputting the name of the part, when a “reverse expansion START” signal is supplied from an input device (not shown) by the operator, the matching processing device 11 The reverse expansion operation as shown in the flowchart of FIG. 5 is started. That is, the child component (product) name, for example, component 01, input by the operator is stored in the development file $ f as shown in FIG. 6 (step S501).

Then, one record is read from the development file $ f (step S502). At this time, if there is a record in the expanded file $ f (step S503), the address pointer of the component configuration file cf (not shown) configured in the matching processing device 11 is updated (step S504). Then, the record of the component configuration file cf indicated by the address pointer is read (step S505), and the contents of the “record key RK1” of the read record and the “record key” of the record read from the development file $ f are read. RK1 ”.

If they match (step S506), then the “record key RK2” of the record read from the component configuration file cf is referred to. If there is no data there (step S507), the process returns to step S504. If there is data there (step S507), the contents of the "record key RK1" of the record are cleared (step S508),
The record is added to the end work file ○ fw (step S509).

Next, the “deployment section” of the record read from the component configuration file cf is referred to. If it is "0" (step S510), the process returns to step S504. If “1”, the contents of the “record key RK2” of the record read from the parts configuration file cf are written to the “record key RK1”, and the contents of the “record key RK2” are cleared. A new record is created (step S511). Then, after adding the new record to the development work file $ fw (step S512), the process returns to step S504.

In this way, the record is expanded and the work file ◇ fw
Alternatively, when the data is added to the end work file ○ fw, in step S506, the contents of the “record key RK1” of the record read from the component configuration file cf and the contents of the record read from the development file $ f "Record key RK1"
If the contents of the file no longer match,
It is confirmed whether or not the record read from is the last record stored in the component configuration file cf (step S512). If it is not the last record, the above step S504
Return to

If it is the last record, the address pointer of the expansion file $ f (not shown) configured in the collation processor 11 is updated (step S514), and the value of the address pointer of the component configuration file cf (not shown) is updated. Set to the start address of the component configuration file cf (step S51
Five). Then, the process returns to the step S502 to read the record of the development file $ f indicated by the address pointer of the development file $ f.

However, if there is no record to be read in the expansion file $ f (step S503), if there is a record in the expansion work file $ fw (step S5)
16), and outputs an end signal “$ fEND” to the classification processing device I12 (step S517). Then, the classification processing device I12
After waiting until a "sort END" signal is supplied (step S518), the process returns to step S502.

In the classification processing device I12, the matching processing device 1
Upon receipt of the end signal "$ fEND" from 1, the classification processing operation as shown in the flowchart of FIG. 7 is executed.
That is, the records of the expanded work file {fw} are sorted (step S701), and the result is added to the expanded file {fw}.
The content of f is rewritten (step S702). Then, after clearing the contents of the deployment work file $ fw (step
(S703), and outputs a “sort END” signal to the matching processing device 11 (step S704). At the end of the first classification processing operation, the expanded file $ f and the end work file
Are as shown in FIG.

Upon receiving the "sort END" signal from the classification processing device I12 (step S518), the matching processing device 11 repeats the above-described operation from step S502.

In this way, when there are no more records to be read in the expanded file $ f (step S503) and there are no more records in the expanded work file $ fw (step S516)
An end signal "@fw END" is output to the classification processing device II13 (step S519). That is, in this case, the record exists only in the end work file ○ fw as shown in FIG.

In the classification processing device II13, the matching processing device
When receiving the end signal "$ fw END" from 11, the classification processing operation as shown in the flowchart of FIG. 10 is executed. That is, the records of the end work file ○ fw are sorted and counted (step S101), and the result is stored in the end file ○ f.
(Step S102). Then, an end signal “END” is output to the output device 14 (Step S103). As a result of this classification processing operation, the contents of the end file ○ f are as shown in FIG.

The output device 14 outputs the end of the reverse expansion operation by the end signal “END”, and outputs the expansion result. That is,
According to the above example, the product names A, B, a, c, and d are printed out as products using the component 01.

[Effects of the Invention] According to the present invention, it is not necessary to register the names of the individual components, the address relations to the parent and child components, and management information, and the component development (reverse development) while referring to each of them
, It is possible to perform component development (reverse development) without requiring a large processing capacity. Therefore, parts development (reverse development) can be performed not only in a computer system having a large processing capability but also in a personal computer system having a small processing capability.

[Brief description of the drawings]

FIG. 1 is a functional block diagram of a data processing device of the present invention, FIG. 2 is a functional block diagram of a data processing device of an embodiment, FIG.
3 to 11 are diagrams for explaining the operation of the embodiment. FIG. 3 is a component configuration table, FIG. 4 is a diagram showing the contents of a component configuration file, and FIG. FIG. 6 is a flowchart of a part expanding (reverse expanding) operation, FIG. 6 is a diagram showing contents of an expanded file during the part expanding (reverse expanding) operation, FIG. 7 is a flowchart of a classification processing operation of the classification processing device I, FIG. 8 is a diagram showing the contents of an expanded file and an end work file in the middle of the above-described part expansion (reverse expansion) operation. FIG. 9 is an end work file in the middle of the above part expansion (reverse expansion) operation. Diagram showing the contents of the tenth
Figure is a flowchart of the classification processing operation of the classification processing device II,
FIG. 11 is a diagram showing the contents of an end file at the end of the above-described component expansion (reverse expansion) operation. 1 ... part configuration file means, 2 ... development file means, 3 ... development work file means, 4 ... end work file means, 5 ... collation processing means, 6 ... end signal,
7. Classification processing means.

Claims (1)

(57) [Claims] In a data processing apparatus for developing a part for pulling all parent parts constructed from child parts by using the child parts, a record key including a name of a related child part and a name of a parent part is provided. ,
A part in which a development section indicating whether or not the number of used high-level parent parts following the above-mentioned child parts is used is data of one record, and each record stores data of a plurality of records including all combinations of child parts and parent parts. A configuration file means, a development file means for storing a child part name to be extracted as a record key, a development work file means and an end work file means for use as a work area, and a record key stored in the development file means. The record including the child part name that matches the child part name is collated and extracted from the part configuration file means, and the presence or absence of a high-level parent part is detected by referring to the development section of the extracted record, If there is a high-level parent part, replace the parent part name of the extracted record with the record key of the child If there is no high-level parent part stored in the open work file means, the matching processing means stores the extracted record in the end work file means; When the comparison of the records is completed, the expanded work file means is compared. If a record is stored in the expanded work file means, the data of the record is written to the expanded file means, and the expanded work file means is written. If no records are stored in the end work file means, a classification processing means for classifying and totaling the records stored in the end work file means.