JPH0816639A - Data base for integrated management of product data and development management framework - Google Patents

Abstract

PURPOSE:To ensure the integrated management of various types of design data and production data which are generated in the development processes of products and also to perform the progress management of the development processes and the estimation of the development manhour. CONSTITUTION:When the development entry is accepted by an entry acceptance function 1, the product names and the progress management data are registered in a product data integrated management data base 14. Then various tools are started by a tool operation control manager function 3 and a development job is carried on. When this job ends, the design and production data are registered in the base 14. At the same time, the development progress states are also registered as data. It is possible to output the progress states of development processes by retrieving the base 14 with the product name used as a key. Then a development manhour estimation function 74 is started to estimate the development manhour of the product under development or to be developed based on various data on the existing products.

Description

Detailed Description of the Invention

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a method of processing data by manipulating the order or contents of data handled by a digital computer, and more particularly to a database and a framework, which is mainly used for parts assembly in the manufacturing industry. The present invention relates to a product data integrated management database and an incident management framework applied to the work performed in the technical department, design department, production technology department, manufacturing department, and management department of the equipment industry.

[0002]

2. Description of the Related Art FIG. 10 shows a conventional technique. When designing an arbitrary product 101, the worker 123 activates the design integration framework function 102. When the design integration framework function 102 starts up, the data storage area 103 has to be specified. Therefore, the worker 123 needs to specify the name of the machine 104 that stores the data files 109, 110, and 111 of the product 101,
The name of the directory 105 and the design integration framework function 102 are input.

The design integration framework function 102 sets the storage destination of the data files 109, 109a, 110, 111 created by the lower CAD tools 106, 106a, the CAE tool 107, and the CAT tool 108 to the input directory 105. After that, of the existing CAD tools 106, 106a,
Product 10 using CAD Tool 106 to use first
One is designed. As a result, the data file 109 created by the CAD tool 106 is created under the input directory 105. CAD to use first
After designing with tool 106, another CAD tool 106a
In designing the next process, the data file 109a created by the CAD tool 106a is also stored in the directory 105.

After completing a series of design procedures using the CAD tools 106 and 106a, the design integration framework function
When creating the manufacturing related data file 113 with the CAM tool 112 which is not under 102, the directory 105
The data file 109 existing thereunder is copied under the directory 115 of the CAM tool 112 itself via the file transfer programs 114 and 114a. As a result of the copy, the copy data file 109a is created. Then worker 123
Performs the processing of the CAM tool 112 via the copy data file 109a.

When performing the processing of the CAM tool 112, the operator 123 activates the conversion program 116 in order to convert the format of the data file 109a into a format unique to the CAM tool 112 as a preprocessing. As a result of starting the conversion program 116, an intermediate generation file 117 is created. Worker 12
In step 3, the conversion program 116 creates an intermediate generation file 117 and then activates the CAM tool 112. When processing with another CAM tool 112a different from the CAM tool 112, another conversion program 11 different from the conversion program 116
6a must be prepared and converted into the corresponding format of the CAM tool 112a.

If the version of the data file 109 created by the CAD tool 106 under the design integration framework function 102 is updated, the worker 123 uses the conversion program 116 and the intermediate generation file 117 again and , You have to go through the same procedure.

A tool 118 different from the CAM tool 112
Now, without using the data file 109, CAD
After printing the result of tool 106 on output page 119, digitizer
The method of reading using 120 must be adopted.

The design integration framework function 102 appends a record 122 to the log file 121 each time it controls the start and stop operations of the CAD tools 106 and 106a under it. From the contents of the file 121, CAD tools 106, 10
6a Each operation can be confirmed. However, the file 121 is not used as the development schedule progress management data of the product 101. Therefore, when managing the development schedule progress of the product 101, the design integration framework function 10
2 Workers who use CAD tools 106 and 106a under their control 123
Will refer to the self-report form 125 to be filled in. Further, the management of man-hours for development of the product 101, the forecast, and the cost forecast are carried out by hand calculation based on the data obtained by the worker's 123 self-report form 125 or by the progress management system after inputting the EDP.

C under the design integration framework function 102
Data file 109,109a created by AD Tool 106,106a
To deliver to another system 124, the file transfer programs 114 and 114a are used. In that case, since the states of the data files 109, 109a, 110, and 111 themselves are not managed, file transfer is possible even for data in the process of development.

As a publicly known material closest to the above-mentioned conventional technique, there is Japanese Patent Laid-Open No. 4-336382.

[0011]

The conventional techniques described above have the following problems.

First, the data files 109, 109a, 110, 111
Sharing the data contained in the CAD tool 106, 106a, CAE under the design integration framework function 102
Only the tools 107 and CAT tools 108 are used, and there is no way to manage the data files 113 of the CAM tools 112 and 112a. Therefore, it is necessary to recreate them using the conversion programs 116 and 116a. Further, since the location of the data file 113 can be easily changed, the data file 113 may be lost.

Secondly, according to the conventional method, for the progress management of the development schedule and the prediction of the development man-hour, the relevant data is collected by the self-report form 125 created by the worker 123, and based on the collected data, the manual calculation or the EDP input is performed. This is done in a later progress management system. With such a method, it is not possible to grasp the development progress in a timely manner and predict the development cost in a timely manner, and it becomes impossible to change the design for cost reduction.

Thirdly, in the conventional method, the data management dependent on the product 101 depends on the operator 123, and it is not managed where the data files 109, 109a, 110, 111, 113 actually exist.

[0015]

SUMMARY OF THE INVENTION The present invention decomposes all operations in developing and manufacturing an arbitrary product into minimum units,
A process management table that systematizes the business, adds the same identification number, and manages subordinate information by the product name and the same identification number, and a product process procedure master table that includes original data when the process management table is created In the process management table, a CAD (Computer Aided Design) tool, C
AM (Computer Aided Manufacturing) Tool, C
AT (Computer Aided Testing) Tool, CAE
(Computer Aided Engineering) Tool, and C
A process of receiving tool support of an APP (Computer Aided Process Planning) tool is extracted, subordinate information is managed by the product name and the same identification number, and the CAD is performed.
Tool, CAM Tool, CAT Tool, C
AE tool, product data table that specifies the storage destination of data created by the CAPP tool, and development management of data created by the CAD tool, the CAM tool, the CAT tool, the CAE tool, and the CAPP tool Includes a distribution address table that manages the subordinate information of the system address that is referenced when distributing to a system outside the framework's control, and a parts library table that centrally manages the parts used when developing products. WBS registered in the process management table for products designed in the past in the product data integrated management database
(Work Breakdown Structure) Basic process start time, end time, cumulative work time, work man-hours, statistical data table for managing evaluation points of the process, and statistics for recording statistical information parameters derived from products designed in the past A master table, a distribution management table that records management items related to the distribution work, the CAD tool, the CAM tool, the CAT tool, the CAE tool, the CAP.
An access method table that manages a method of automatically converting data created by an arbitrary tool of the P tool into a format compatible with the tool when another arbitrary tool reads the data. is there.

According to the present invention, all the operations for developing and manufacturing an arbitrary product are disassembled into the minimum units, the operations are systematized, the same identification number is added, and the product name and the same identification number are subordinate to each other. A process management table for managing information, a product process procedure master table including original data when creating the process management table, and a CAD) tool, a CAM tool, a CAT tool, a CAE tool among the process management tables, and A process of receiving tool support of a CAPP tool is extracted, subordinate information is managed by the product name and the same identification number, the CAD tool, the CAM tool, the CAT.
Tool, the CAE tool, a product data table that specifies the storage destination of the data created by the CAPP tool, and the C
Refer to the case where the data created by each of the AD tool, the CAM tool, the CAT tool, the CAE tool, and the CAPP tool is distributed to a system outside the management of the development management framework, and refer to the subordinate information of the system address. A product data integrated management database that includes a managed distribution address table and a parts library table that centrally manages the parts used when developing a product. A statistical data table that manages the start time, end time, accumulated work time, work man-hours, and evaluation points of the registered WBS basic process, and a statistics master that records statistical information parameters derived from products designed in the past. A table, a distribution management table recording management items related to the distribution work, the CAD tool, Access to manage a method for automatically converting data created by an arbitrary tool of the CAM tool, the CAT tool, the CAE tool, and the CAPP tool into a format compatible with the tool when another arbitrary tool reads the data. The CAD tool and the CAM tool registered in a process management table existing in a product data integrated management database including a method table,
The data of the CAD tool, the CAM tool, the CAT tool, the CAE tool, and the tool of the CAPP tool is created by controlling activation and stop of the CAT tool, the CAE tool, and the tool of the CAPP tool. A log file that stores the operation records of the CAD tool, the CAM tool, the CAT tool, the CAE tool, and the CAPP tool in the area described in the product data table in the manufacturing data integrated management database. And a tool operation control manager function to record in the CAD tool, the CAM tool, the CAT tool, the CAE tool, the CAP.
Design B / M that creates a parts table from the parts library management function that manages the parts library table referenced by an arbitrary tool of the P tool and the data created by the CAD tool
In a development management framework having a creation function, an entry reception for receiving an event of development start as a routine work and registering an instance of the WBS basic process in which the work content decomposed into the minimum units is described in the process management table Functions, a data management function that automatically performs data maintenance of the product data table, and a development schedule that displays the development schedule progress of the product registered by the entry acceptance function from the process management table and the log file. Progress management function, the CAD tool, the CAM tool, the CAT tool, the CAE tool, the CAP
A data distribution management function of transferring the data created by an arbitrary tool of the P tool to an external system according to the corresponding state, the CAD tool, the CAM tool, the CA
A method for automatically converting data created by any of the T tool, the CAE tool, and the CAPP tool so that the data format of the tool is compatible when another tool reads the product data table, From the process management table, the statistical data table, the statistical master table, the access method, and the log file, a development man-hour estimating function for estimating the development man-hour of the product registered by the entry receiving function, and the process management table From the statistical data table and the log file, a man-hour statistical information collecting function that collects man-hour statistical information of products developed in the past, and from the product data table, the statistical data table, the access method table, and the access method. , With the evaluation statistical information collection function that collects the evaluation point information of products developed in the past, Process management table, from the statistical data table, analyzes the statistics of products developed in the past, it is characterized in that it comprises a statistical analysis function for registering the result of the analysis on the statistical master table.

[0017]

Next, the present invention will be described with reference to the drawings. FIG. 1 is a block diagram showing an embodiment of the present invention.

FIG. 2 shows the relationship between the entry acceptance function, the product data integrated management database and the data management function in FIG. 1, and the tool operation control manager function for the method.

FIG. 3 is a process management table, a product process procedure master table, a product data table, a distribution address table,
An access method table, a distribution management table, a statistical data table, a statistical master table held by a product data integrated management database that includes a parts library table and a log file,
The process management table, the product process procedure master table,
The details of the product data table, the delivery address table, the parts library table, and the log file are shown.

FIG. 4 shows a design B / M for the access method table of the product data integrated management database shown in FIG.
The relation between the creating function and the process management table and the product data table of the product data integrated management database is shown.

FIG. 5 shows the relationship between the product data table of the product data integrated management database, the distribution address table, and the distribution management table for the data distribution management function in FIG.

FIG. 6 shows the relationship between the tool operation control manager function for the development schedule progress management function in FIG. 1, the process management table of the product data integrated management database, and the product process procedure master table.

FIG. 7 shows the relation of the component library management function in the development management framework with respect to the access method table and method of the product data integrated management database in FIG.

FIG. 8 shows the man-hour statistical information collecting function shown in FIG.
And evaluation statistical information collection function, statistical analysis function, development man-hour estimation function, entry acceptance function, and the above-mentioned product data integrated management database access method table, statistical data table, and statistical master table described above product data The relationship between the process management table of the integrated management database and the product process procedure master table is shown.

FIG. 9 shows the version management system.
The method of expressing the parent-child relationship is shown.

Next, with reference to FIG. 2, the relationship between the entry receiving function, the product data integrated management database, the data management function, the method, and the tool operation control manager function will be described in detail.

The tool operation control manager function 3 is C
AD tool 4, CAE tool 5, CAM tool 6, CA
It controls the operation and environment of the T tool 7 and the CAPP tool 8.
Ignition) Framework function is added to the above method loading function.

The entry acceptance function 1 is a function of registering a product to be newly developed and registering the development process of the product.

The product data integrated management database 14 is
CAD tool 4, CAM tool 6, CAT tool 7, C
It manages the data file 25 created by each tool of the AE tool 5 and the CAPP tool 8 and its access method. It describes the work contents when developing and manufacturing the product, and corresponds to the work flow management table. , The existing process management table 15, the product process procedure master table 16 that provides the original data of the process management table 15, the product data table 17 having the structure found in the file management method within the EDA framework, and the network It manages the correspondence between addresses and systems, and includes a distribution address table 47 corresponding to a conventional object dictionary, a parts library table 49 that has been present in the CAD tool, and a parts library table 49 that has been present in the CAD tool. It includes a log file 20 that contains A new definition of the access method table 22 for managing method which is also the data conversion program,
A newly defined distribution management table 48 for managing distribution to an external system, and a start time, end time, cumulative work time, work man-hour, and evaluation point of the process, which are registered in the process management table 15, are managed. A newly defined statistical data table 50 and a newly defined statistical master table 51 that records statistical information parameters derived from products designed in the past are included.

The data management function 2 automatically performs data maintenance of the product data table 17 in the product data integrated management database 14.

Upon receipt of the activation request 35 via the input / output device 13, the entry acceptance function 1 processes in the product data integrated management database 14 in order to prepare for development of the product name designated by the activation request 35. The management table 15 is searched to check whether or not the instance 21 having the product name input by the entry reception function 1 exists.

If the instance 21 does not exist,
Since the entry acceptance function 1 registers only the corresponding instances 21 in the process management table 15 with the product name and the WBS unit process as the search key, the operator 11 waits for the input work.

The WBS unit process is a work unit that constitutes the development work of the product, and is clearly defined by the standardization activity in the organization to which the worker 11 belongs. Normally, in the process management table 15, hundreds to thousands of WBS-unit processes per product are registered.

The WBS unit process is registered in the product process procedure master table 16. Entry acceptance function 1
When registering only the instance 21 corresponding to the WBS unit process in the process management table 15, the worker 11
On the input / output device 13, all the instances 36 displayed as a list search from the product process procedure master table 16 are selected.

When the arbitrary WBS unit process is not executed in the process of developing the above-mentioned product, the worker 11 may generate the discard event 29 on the input / output device 13.

After that, when the worker 11 generates the input end event 30, the corresponding instances 21 are registered in the process management table 15 with the product name and the WBS unit process as keys.

In particular, when the arbitrary WBS unit process in which the discard event 29 has occurred is registered in the process management table 15, the unadopted flag is set in the process adopted flag of the corresponding instance 21. The worker 11 can easily execute the instance 21 of the process management table 15 by the above method.
Can be registered.

The entry acceptance function 1 is the process management table 1
When the number of instances 21 corresponding to the product and the WBS unit process is registered in 5, the WBS unit process receiving the tool support is extracted, and the product name and the WBS described above are displayed in the product data table 17 in the product data integrated management database. The process instances 18 of the corresponding number are collectively registered with the unit process as a key.

The process instance 18 has a CAD
Each time the tool 4, the CAE tool 5, the CAM tool 6, the CAT tool 7, or the CAPP tool 8 newly generates the data file 25 related to the product, the storage machine of the data file 25 and the starting directory 26 Or, the state is entered.

When the worker 11 tries to start the CAD tool 4, the CAE tool 5, the CAM tool 6, the CAT tool 7, and the CAPP tool 8 to start the development, the tool operation control manager function 3 performs preprocessing. stand up. The tool operation control manager function 3 includes a subordinate CAD tool 4, CAE tool 5, CAM tool 6,
The startup control of each of the CAT tool 7 and the CAPP tool 8 is performed.

At the time of startup, the tool operation control manager function 3 requests the worker 11 to input the above-mentioned product name input by the entry acceptance function 1.

When the product name value 37 input by the entry acceptance function 1 is input through the input / output device 13, the tool operation control manager function 3 uses the product name value 37 as a key to display the product data table. The process instance 18 of 17 is searched, and the list is displayed on the input / output device 13. The worker 11
From the above list display, the corresponding process instance 18
Pick out.

When the process instance 18 can be searched and the above-mentioned storage machine where the data file 25 is arranged and the starting point directory 26 are described, the data file 25 already exists. In this case, the worker 11 inputs the version and access method designation 38 (designates either update replacement or new version) to the tool operation control manager function 3.

As a result of the tool operation control manager function 3 retrieving the product data table 17, the process instance 1
No. 8 exists, but when the storage machine, which is the allocation destination of the data file 25, and the starting point directory 26 are not described, it means that the work of the corresponding WBS unit process has not been performed yet.

In this case, the worker 11 operates the input / output device 13
Via the CAD tool 4, the CAE tool 5, the CAM tool 6, the CAT tool 7, and the CAPP tool 8, the storage machine to which the data file 25, which is the storage destination of the data generated by each tool, and the name of the starting directory 26 are stored. The data 39 is input to the tool operation control manager function 3.

The tool operation control manager function 3 overwrites the input storage machine and starting point directory 26 on the selected process instance 18.

Particularly, when the CAD tool 4 is integrated to form the EDA framework 9, the starting point directory 26 of the data file 25 collectively managed by the EDA framework 9 is described.

After that, since the data file 25 will be generated in the storage machine and the starting point directory 26, the tool operation control manager function 3 reads and writes in the selected process instance 18.
Lock it to prevent it from being used by other tools.

After that, the tool operation control manager function 3
Creates the key file 19 in which the product name input by the entry receiving function 1 is described, in the storage machine and under the starting point directory 26.

After that, the tool operation control manager function 3 starts from the process instance 18 selected by the worker 11 and manages the CAD tool 4, the CAE tool 5, the CAM tool 6, the CAT tool 7 under its control. To start any of the CAPP tools 8,
The activation event 42 is issued.

The tool operation control manager function 3 includes a subordinate CAD tool 4, CAE tool 5, CAM tool 6,
Each time the CAT tool 7 or the CAPP tool 8 is started up, a log record 24 is generated and appended to the file 20 of the determined machine.

A status ID item (start, interruption, end), a tool ID item, an event time item, a product name item, and a login name item are written in the file 20.

The data file 25 created by the tools of the CAD tool 4, the CAE tool 5, the CAM tool 6, the CAT tool 7 and the CAPP tool 8 activated by the tool operation control manager function 3 is the storage machine,
Also, it is created in a temporary file 27 different from the starting point directory 26.

However, since the corresponding process instance 18 in the product data table 17 is locked by the read & wite lock, the CAD tool 4, which is different from the above-mentioned tool in the activated state under the tool operation control manager function 3,
CAE tool 5, CAM tool 6, CAT tool 7, C
The data file 25 cannot be used from the tools of the APP tool 8.

The area for storing the temporary file 27 is described in the key file 19.

The tool operation control manager function 3 is a CA
D tool 4, CAE tool 5, CAM tool 6, CAT
When the processing by the tool 7 and the CAPP tool 8 is completed, the temporary file 27 written in the key file 19
From the storage area of C to the storage machine described in the process instance 18 and the starting point directory 26.
AD tool 4, CAE tool 5, CAM tool 6, CA
The data file 25 created by the T tool 7 and the CAPP tool 8 is moved.

At the time of the moving procedure, the tool operation control manager function 3 has the data file 25 created by the CAD tool 4, CAE tool 5, CAM tool 6, CAT tool 7, and CAPP tool 8 from the access method table 22. The unique global name 23 to be obtained is obtained.

After that, the tool operation control manager function 3
Replaces the data file 25 with the unique global name (2
3) and rename with the version extension.

As described above, when the tool operation control manager function 3 is started, if the process instance 18 includes the above-mentioned storage machine for storing the data file 25 and the starting point directory 26, the worker 11
Inputs a version designation and access method to the tool operation control manager function 3. The value of the version extension is determined according to the version designation and the access method.

After that, the tool operation control manager function 3
Releases the read & write lock of the corresponding process instance 18 of the product data table 17 and makes it accessible to other tools. After that, the path name of the temporary file 27 described in the key file 19 is deleted.

The data file 25 is the key file 19
9 is described in a format including the version extension as described in FIG. If the largest version extension is the latest version and is referred to using the method 31, the latest version is the target.

The tool operation control manager function 3 then creates a log record 24 and appends it to the file 20 of the determined machine.

At regular intervals, the data management function 2 is activated on the machine in which the product data integrated management database is installed.

When the data management function 2 is activated, the data management function 2 sequentially searches the product data table 17, and obtains the storage machine described in the process instance 18 and the path name of the starting point directory 26.

After that, the data management function 2 confirms the existence of the key file 19 from the storage machine and the starting point directory 26.

Due to disk capacity restrictions and product discontinuation,
CAD tool 4, CAE tool 5, CAM tool 6, C
The data file 25 created by the AT tool 7 and the CAPP tool 8 is a storage machine different from the storage machine and the start point directory 26, and the start point directory 2.
8 and the data file 25a is created, the data management function 2 read locks the relevant process instance 18 of the product data table 17.

Thereafter, the data management function 2 issues a start event 40 for starting the task 10 searching for the key file 19.

The started task 10 has a key file 19
The above-mentioned storage machine that belongs to and the starting directory 2
When 8 is found, the task 10 passes the above-mentioned storage machine and the information 43 of the starting point directory 28 to the data management function 2 and ends the processing.

The data management function 2 describes the path name of the storage machine and the starting point directory 28 in the process instance 18 of the product data table 17. Then, the above-mentioned re
ad unlock.

Here, when the worker 11 refers to the data file 25 created by the CAD tool 4 with the CAT tool 7 after starting the CAD tool 4, the tool operation control manager managing the CAT tool 7 Function 3 is
The access method table 22 is searched.

After that, the tool operation control manager 3 function determines the tool ID (CAD tool 4) of the tool to be linked.
Method) and the tool ID of the subordinate tool managed by itself (the ID of the CAT tool 7) as keys, the method 31 is searched from the access method table 22 to obtain method information 44. When there are a plurality of corresponding instances 45 of the method 31, the method 31 is specified by further specifying the instance ID in the access method table 22.

After that, the tool operation control manager function 3
Allocates the storage machine and the starting point directory 26 from the process instance 18 corresponding to the tool (the CAD tool 4) in the product data table 17.
After that, the tool operation control manager function 3 makes a method call 41 of the above-mentioned assigned method 31 by using the storage machine and the starting point directory 26 as arguments.

Then, the assigned method 31 is expanded from the method registration directory 32 into the memory 12 on the machine in which the data file 25 is stored, and the latest version of the desired tool (the CAD tool 4) is transferred. The data described in file 25 is
Data 3 of CAT tool 7 converted by method 31
3 is expanded on the memory 12 and then transferred to the machine on which the tool operation control manager function 3 is activated.

Referenced to create data 33,
The part that depends on the data file 25 of the other tool (tool 4) is not described in the data file 34 of the newly created CAT data 33. Due to work, the data 3
3 is required, the tool operation control manager function 3 uses the method 31 to store the memory 12 each time.
The data 33 is expanded on the top.

The tool operation control manager function 3 is installed with the number of tasks on the partner machine in which the data file 25 of the link desired tool is stored and the tool operation control manager function 3 immediately before reading the access method table 22. Is measuring the amount of traffic on the network that connects the machines that are running.

The tool operation control manager function 3 has a performance problem in executing the method 31, and when it is slow to expand the data 33 on the memory 12 via the method 31, the tool operation control manager 3 The data file 25 corresponding to the disk and the memory of the machine in which the function 3 is installed is copied and converted by the method 31 to obtain the data 33.

The data 33 can be made non-volatile. However, normally, the data 33 is deleted when the tool operation control manager function 3 ends.

At this time, the process instance 18 of the product data table 17 is locked by read & write as described above.

Referring to FIG. 4, design B / M creation function 8
9 is to output the design B / M based on the result of the PWB design. That is, when creating the above-mentioned design B / M, P
A CAD data file for which the WB design has been completed is required. When the design B / M creation function 89 is activated, the design B / M is created according to the following processing procedure. Design B
The / M creation function 89 firstly processes the process management table 15 (FIG. 3) based on the product name ID 54 input from the input / output device 13.
From, the WBS unit process I representing the PWB design process
D55 is obtained and the WBS unit process 5 is input to the input / output device 13.
Display the list of 5. The worker 11 selects the design B from the list.
The WBS unit process that created the CAD data file 90 that is the original data of / M91 is selected (WBS unit process ID 55 is determined).

Next, the design B / M creation function 89 searches the product data table 17 for a process instance 18 that satisfies the following conditions, and locates the CAD data file 90 (mounting machine ID 57, starting directory 58). When,
Tool ID used when creating the CAD data file 90
You get 56. The condition is that the product name ID 54 of the product data table 17 matches that input from the input / output device 13, and the WBS unit process ID of the product data table 17
55 matches the one selected from the WBS-unit process list. Further, the design B / M creation function 89 searches the access method table 22 for all that satisfy the following conditions 1 to 3 and obtains the method 31 to be used for data conversion. The condition 1 is that the “category 93” in the access method table 22 represents the PWB design, and the condition 2 is that the “own tool ID 94” in the access method table 22 is the output tool of the design B / M 91. The condition 3 is that the “used tool ID 95” in the access method table 22 matches the one obtained from the product data table 17. Design B /
The M creation function 89 reads the CAD data file 90, uses the method 31, and extracts the items (part ID, part name, circuit symbol, etc.) necessary for creating the design B / M 91,
After that, referring to the component library table 49 from that item, using the component ID of the CAD data file 90 as a key, the pseudo component is excluded or the component attribute (unit price, etc.) is added to create the design B / M 91.

Referring to FIG. 5, the data distribution management function 5
2 is a CAD tool 4, a CAE tool 5, a CAM whose operation is controlled by the tool operation control manager function 3.
The manufacturing data 60a created by using the tool 6, the CAT tool 7, and the CAPP tool 8 is transferred to the external system 53. The manufacturing data 60a must be up to date and valid. Data distribution management function 5
When No. 2 is activated, the manufacturing data 60a is distributed to the other system 53 according to the following processing procedure. The data distribution management function 52 first searches the process instance 18 from the product data table 17 based on the product name ID 54 input from the input / output device 13 and the WBS unit process ID 55, and locates the effective manufacturing data 60a ( Mounting machine I
D57, the starting point directory 58) is obtained, and the transfer file 59 is created by data copying. Data distribution management function 52
Next, based on the system name 61 of the transfer destination input from the input / output device 13, the TCP / IP address 62 of the system is obtained from the distribution address table 47, and the transfer file 59
Is transferred to another system 53 (becomes a data file 60).

Further, the data distribution management function 52 obtains the version number 63 of the previously transferred manufacturing data 60a from the distribution management table 48 based on the product name ID 54, the WBS unit process ID 55, and the system name 61, and the version number 63 One version up and register.

The production data 60a is discarded according to the following processing procedure. Data distribution management function 52
Is the product name ID 54, W input from the input / output device 13.
Based on the BS unit process ID 55, all the system names 61 to which the manufacturing data 60a is transferred are extracted from the distribution management table 48. Next, the data delivery management function 52 uses the delivery address table 47 to send the TCP of the system based on the system name 61.
/ IP address 62 is obtained, and the discard of the manufacturing data 60a is notified. At the same time, the data distribution management function 52 registers the status 65 of the distribution management table 48 for the system name 61 as "discard".

Referring to FIG. 6, the development schedule progress management function 66 is a CAD tool 4, a CAE tool 5, or a CA tool whose operation is controlled by the tool operation control manager function 3.
It is possible to easily grasp the progress of design work and the like performed using the M tool 6, the CAT tool 7, and the CAPP tool 8.

When the development schedule progress management function 66 is activated, the product name 54 input from the input / output device 13 (FIG. 4).
Based on the above, a list of the above-mentioned WBS unit processes is displayed from the process management table 15. When the worker 11 inputs the scheduled completion date for each WBS unit process listed above, the scheduled completion date is registered in the process management table 15 based on the product name 54 and the WBS unit process ID 55 (FIG. 4). To be done.

WBS when design work is in progress
The progress status list of the unit process 55 is displayed as in the screen display example 67. The mutual relationship of the WBS unit process ID 55 can be easily obtained from the product process procedure master table 16.

WBS unit process ID with tool support
55 and WBS unit process ID 55 without tool support
And, the method of registering the "completion date" item 68 for displaying the progress status in the process management table 15 is different. In WBS unit process ID55 without tool support, worker 1
The “completion date” item 68 entered by the user 1 through the input / output device 13 is
It is registered in the process management table 15.

On the other hand, the WBS unit process ID 55 with tool support is as follows. First CAD
When the design work by the tool 4 is finished, the worker 11 himself selects whether the design work is completed or the work is interrupted, and inputs it to the input / output device 13. When the design work itself is completed, the date when the tool operation control manager 3 completed the design work is set as the “completion date” item 68 in the process management table 15.
To automatically register as. On the other hand, when the work is interrupted, the registration is not performed.

Referring to FIG. 7, the parts library management function 96 is a CAD tool 4, a CAE tool 5, which controls operations by the tool operation control manager function 3.
CAM tool 6, CAT tool 7, CAPP tool 8
The component information for each tool used in (see FIG. 2) is converted into integrated component information (component name, component unit price, etc.) and managed by the component library table 49.

The worker 11 uses the product library management function 9
When 6 is activated, the registration right is determined by the login name of the worker 11.

If the registration right exists, the worker 11
From the WBS unit process ID 55 (FIG. 5) displayed in a list on the input / output device 13,
And enter the corresponding product name value 37 (FIG. 2). When the input WBS unit process ID 55 is processed by a tool that can be made into a library, the I / O device 13 requests the requested WBS basic process ID 55.
The drawing contents of the corresponding tool will be displayed. If the tool cannot process the error, an error is returned to the input / output device 13.

When the worker 11 clicks the part symbol drawn there with the mouse, the input / output device 13
Receives a request for inputting the part ID, the tool ID used, and the part attribute of the package. After that, the worker 11 makes the input / output device 13
Enter the applicable value in.

Thereafter, the product library management function 96
Based on the product name value 37 and the WBS unit process ID 55 input from the input / output device 13, the product data table 17
Use tool ID 56 is obtained from. After that, the access method table 22 is searched under the following conditions 4 and 5 to obtain the method 31 used for data conversion. The condition 4 is “own tool ID 94” in the access method table 22 (FIG. 4).
Is the parts library management function 96, and the above condition 5
Is the "other tool ID 9" in the access method table 22.
5 ”(FIG. 4) is consistent with that obtained from the product data table 17. When the method 31 is obtained, the product library management function 96 reads the CAD data file 90, extracts the part ID, the part name, and the circuit symbol from the text format data, and extracts the part ID and the used tool I.
It is registered in the parts library table 49 using D as a key.

For items other than the items obtained from the CAD data file 90, the product library management function 96 further performs the following processing. The product library management function 96 sequentially reads the product data table 17 based on the product name value 37 input from the input / output device 13, and obtains the used tool ID 56 corresponding to each WBS unit process ID 55.
After that, the access method table 22 is searched under the following conditions 6 and 7 to obtain the method 31 used for data conversion. The condition 6 is that the “own tool ID 94” (FIG. 4) in the access method table 22 is the parts library management function 96.
That is, the condition 7 is the access method table 22.
"Counterpart tool ID 95" (Fig. 4) is the product data table 17
That is consistent with what I got from.

When the method 31 is obtained, the product library management function 96 reads the data file 90a different from the CAD data file 90, extracts the part ID and other various data from the text data, and extracts the part ID,
And the tool ID is additionally registered in the parts library table 49 as a key.

FIG. 8 shows the man-hour statistical information collecting function, the evaluation statistical information collecting function, the statistical analysis function, the development man-hour estimating function, the entry receiving function, the access method table and the statistics of the product data integrated management database shown in FIG. The relation between the above-mentioned process management table of the above-mentioned product data integrated management database and the above-mentioned product process procedure master table with respect to the data table and the statistical master table is shown.

The development man-hour estimating function 74 uses the entry data receiving function 1 from the product data table 17, process management table 15, statistical data table 50, statistical master table 51, method 31, log file 20 in the integrated manufacturing data management database 14. It estimates the development man-hours of the product registered by.

The man-hour statistical information collecting function 71 is a function for collecting the man-hour statistical information of the products developed in the past from the process management table 15, the statistical data table 50, and the log file 20 in the integrated manufacturing data management database 14.

The evaluation statistical information collecting function 72 is used for the product data table 17, the statistical data table 50, the access method table 22, and the method 31 in the manufacturing data integrated management database 14.
Is a function for collecting evaluation point information of products developed in the past. The statistical analysis function 73 is a function of analyzing statistical information of products developed in the past from the process management table 15 and the statistical data table 50 in the integrated manufacturing data management database 14, and registering the analysis result in the statistical master table 51. is there.

Product 69 input by entry acceptance function 1
When a series of development work of was completed and mass production started,
From the production management system 70, the man-hour statistical information collecting function 71
The activation request event 42 to the event occurs. Request event 4
In accordance with 2, the manhour statistical information collecting function 71 is activated to perform the following manhour accumulating process.

In this case, with the product name of the product 69 as a key, the instance 3 corresponding to the WBS basic process registered in the process management table 15 and having the adopted flag is set.
Perform a list search of 6.

Thereafter, the man-hour statistical information collecting function 71 creates the instance 36 of the process management table 15 and the instance 76 of the same statistical data table 50. The key items of the statistical data table 50 are the name of the product 69 and the WBS unit process ID. Further, as data items of the statistical data table 50, there are process start time, end time, cumulative work time, work man-hours, number of startups, login name, and evaluation points. After that, the man-hour statistical information collecting function 71 sequentially searches the statistical data table 50 for the instance 76 using the name of the product 69 as a key.

The man-hour statistics information collecting function 71 reads one instance 76 and then, from the record 24 of the log file 20, the same product 6 as the read instance 76
A plurality of records 24 having the name of 9 and the above-mentioned WBS unit process ID are taken out and the number of records is counted. Thereafter, the man-hour statistical information collecting function 71 calculates the first start start time and the end time of the tool used in the corresponding WBS unit process ID, the cumulative work time, the number of start-ups, and the work man-hour from the record 24. After that, the man-hour statistical information collecting function 71 writes the starting time and the ending time, the cumulative working time, the starting frequency, and the working man-hour in the read instance 76. The evaluation point item 78 is not set in the read instance 76.

When the man-hour statistical information collecting function 71 processes the above-mentioned WBS unit process without tool support among the instances 76 of the statistical data table 50, the following setup is performed. As a first procedure, the man-hour statistical information collecting function 71 searches the process management table 15 for the ID of the tool-supported WBS unit process before and after the WBS-unit process without the tool support, using the name of the product 69 as a key. As a second procedure, the man-hour statistics information collecting function 71 uses the searched tool-support WBS unit process ID and the name of the product 69, which correspond to the previous step of the WBS unit process, as a key to record the record 24 of the log file 20. Search for the end time. As the third procedure, the man-hour statistics information collecting function 71 uses the retrieved tool support WBS unit process ID corresponding to the subsequent step of the WBS unit process.
Using the name of the product 69 as a key, the record 24 of the log file 20 is searched to find the start time. As the fourth procedure,
The man-hour statistical information collecting function 71 calculates the WBS unit process work time without the tool support from the difference between the final time and the start time, and calculates the man-hour.

If there are a plurality of log records 24 indicating the tool activation in the second procedure, the man-hour statistical information collecting function 71 terminates the log record 24 corresponding to the tool support WBS unit process of the previous process. The time is checked, and the log record 24 of the same tool-assisted WBS unit process having a maximum end time that is larger than the end time is searched. When the man-hour statistical information collecting function 71 is able to search, the end time of the log record 24 is adopted.

If there are a plurality of log records 24 describing the tool activation in the third procedure, the man-hour statistical information collecting function 71 causes the log record 24 corresponding to the tool assist WBS unit process of the subsequent process to be recorded. The start time is checked, and the log record 24 of the same tool-assisted WBS unit process that is smaller than the start time and has the minimum start time is searched. When the man-hour statistical information collecting function 71 can search, the start time of the log record 24 is adopted. In addition, even in the WBS unit process without the above tool support, when the record 24 of the log file 20 is created by e-mail or manual input, the man-hour statistical information collecting function 71 uses the log record 24 to start the above. The start time, the above-mentioned end time, the above-mentioned cumulative work time, and the above-mentioned number of times of starting are calculated to calculate the work man-hours.

The man-hour statistical information collecting function 71 activates the evaluation statistical information collecting function 72 immediately before ending the man-hour accumulating process. The evaluation statistical information collecting function 72 is provided in the data file 34 created or referenced by the CAD tool 4, CAE tool 5, CAM tool 6, CAT tool 7, or CAPP tool 8 used in the development phase of the product 69. The parameter 77 that most affects the tool activation time is taken out and set as the evaluation point 78.

The parameter 77 to be used as the evaluation point 78 and its calculation method 79 are registered in the determined method 31 existing in the method registration directory 75.
The evaluation statistical information collecting function 72 sequentially reads the statistical data table 50 using the name of the product 69 as a key. Then, the evaluation statistical information collection function 72 allocates the method 31 from the method table 22. After that, the evaluation statistical information collecting function 72 stores the method 3 existing in the method registration directory 75.
Call 1. Then, the evaluation point 78 is calculated.

After that, the evaluation points 78 are returned to the evaluation statistical information collecting function 72. After that, the evaluation statistics information collecting function 72 displays the name of the product 69 and the above-mentioned WBS unit process I.
Using D as a key, the instance 76 of the statistical data table 50 is read and the evaluation point item 78 is described. The evaluation statistical information collecting function 72 performs the above-mentioned work on all the instances 76 in which the product 69 of the statistical data table 50 matches. When the method 31 for calculating the evaluation point 78 cannot be defined, the evaluation statistical information collection function 72 activates the fixed value setting method 31a, and a pseudo evaluation point 78a is given.

The evaluation statistical information collecting function 72 activates the statistical analysis function 73 immediately before the processing is completed. The statistical analysis function 73 is activated each time new statistical target data is generated. The statistical analysis function 73 uses the process management table 1
Projection calculation processing for the pattern name item is added to 5 to obtain all pattern type information 80. After that, since the statistical analysis function 73 obtains the relationship between the evaluation points 78 and the development man-hours for every pattern type information 80, it matches the first pattern described in the all pattern type information 80.
The instance 36 of the process management table 15 is searched in a list. After that, the statistical analysis function 73 executes the WBS basic process I described in the instance 36 searched in the list.
All the instances 76 are obtained from the statistical data table 50 using D as a key, and the evaluation points 7 described in the instance 76
The natural logarithmic value 81 of 8 and the natural logarithmic value 82 of the total man-hours calculated are calculated.

The statistical analysis function 73 has an evaluation point 78.
The natural logarithmic value 81 of and the natural logarithmic value 82 of the total man-hours calculated by the above calculation are obtained for all the instances 76, and the value of the proportional coefficient K _pi and the exponential coefficient of the following equation (1) are calculated using the least square method. Estimate the value of tpi. The variance value σ _Npi is also obtained. By _{calculating the} K _pi value, the t _pi value, and the variance value σ _Npi , the man-hour corresponding to the arbitrary evaluation point 78 can be estimated. The statistical analysis function 73 processes the above with respect to all the instances 36 of the process management table 15 for each of the above-mentioned patterns, and with respect to all the patterns in the all-pattern type information a80. Nh _pi = K _pi * (P _i ) ^tpi (1) where Nh _pi is the estimated man-hour of the WBS unit process i under the process pattern p, and K _pi is W under the process pattern p.
The proportional coefficient of the BS unit process i, P _i is the evaluation point of the WBS unit process i under the process pattern p, tpi
Is an exponential coefficient of the WBS unit process i under the process pattern p.

Thereafter, the statistical analysis function 73 obtains all the instances 76 from the statistical data table 50, and the following (2) (3)
Calculate equation (4).

[0113] Here, H _pij is the distribution ratio of the WBS unit process i of the process pattern p product j to the total man-hours, Nhj _pij is the actual total man-hour of the WBS unit process i of the process pattern p product j, and Np is the all WBS unit processes of the process pattern p. It is an instance.

[0114]

Where γ _pi is the WB of the process pattern p
It is the average allocation rate of the S unit process i. After that, the statistical analysis function 73 uses the following data 85, 8
6, 87, 88 are registered in the statistical master table 51 using the process pattern p and the WBS unit process as a key. After that, the statistical analysis function 73 ends the process. WBS-unit process i proportional coefficient (85): K _pi WBS-unit process i exponential coefficient (86): tpi WBS-unit process i average allocation rate (87): γ _pi variance value σ _Npi , variance value σ _rpi (88) When starting the development man-hour estimation function 74, the worker 11 inputs 69 products. After that, the development man-hour estimation function 74
From the process management table 15 with the name of the product 69 as a key,
The instances 36 in which the “unfinished” or “finished” flag is added to the STATUS flag are sequentially searched.

As the development man-hour estimation function 74 searches, the product data table 17 is further searched for the tool support WBS unit process in the instance 36,
Allocate a process instance 18. Thereafter, the development man-hour estimation function 74 uses the WBS unit process ID having the read process instance 18 and the input product 6
The start time and end time of the tool are searched from the record 24 of the log file 20 that matches the name of 9 and the corresponding WBS
The pre-estimated man-hour Nhb _pi of the unit process is calculated. The result is written in the temporary file 83.

When the development man-hour estimation function 74 sequentially searches the instance 36, when processing is performed for the WBS unit process without tool support, the processing is performed as follows. As a first procedure, the development man-hour estimation function 74 searches the process management table 15 for the tool-supported WBS unit process ID before and after the WBS unit process without tool support, using the product 69 as a key. As a second procedure, the development man-hour estimation function 74 searches the record 24 of the log file 20 by using the searched tool support WBS unit process ID and the name of the product 69 corresponding to the previous step of the WBS unit process as keys. Then, the final end time is calculated. As a third procedure, the development man-hour estimation function 74 uses the WB
The record 24 of the log file 20 is searched with the key of the searched tool support WBS unit process ID and the name of the product 69 corresponding to the post-process of the S unit process as a key, and the first start time is determined. As a fourth procedure, the development man-hour estimation function 74 estimates the WBS unit process work time without tool support described above from the difference between the final time and the start time, and calculates the pre-estimated man-hour Nhb _pi . The result is entered in the temporary file 83. By the above-mentioned method, when the development man-hour estimation function 74 is activated, the WBS unit process work time which is finished and in progress is estimated, and the pre-estimated man-hour Nhb _pi is calculated. After that, the development man-hour estimation function 74
Is the evaluation point 78 from the method directory 75.
The method 31 for obtaining is evaluated and the evaluation point 78 is calculated from the data file 34 pointed to by the process instance 18. Then, the development man-hour estimation function 74 retrieves the process proportional constant and the exponential constant of the corresponding WBS unit process from the statistical master table 51, and calculates the post-estimated man-hour Nha _pi . The result is
Fill in the temporary file 84. After that, the development man-hour estimation function 74 performs the above process on all the instances 36 in which the “unfinished” or “finished” flag is added to the STATUS flag obtained from the process management table 15 with the name of the product 69 as a key. .

The development man-hour estimation function 74 then predicts the man-hours of the unprocessed WBS unit process corresponding to the instance 36 in which "unprocessed" is added to the STATUS flag of the process management table 15. Therefore, the development man-hour estimation function 74
Is the pre-estimated man-hour N described in the temporary file 83.
hb _pi is compared with the post-prediction man-hour Nha _pi described in the temporary file 84, and the parameters registered in the statistical master table 51, that is, the average distribution rate γ _pi of the WBS unit process i, the variance value σ _Npi , The variance value σ _rpi is _extracted and the following four parameters (5) (6) (7) (8) (9) are calculated. 1) Theoretical worst value Since each man-hour of the WBS unit process is independent, it is derived as follows. However, k is Nhb _pk -Nha _pk is Max process i
d and n are "finished" or "not finished" in the instance 36
It has a flag. 2) Usual theoretical upper limit 3) Theoretical optimum value This value is applied when the following formula (7) is satisfied in all WBS unit processes in which the instance 36 has the “finished” or “not completed” flag.

[0119]

[0120] 4) Theoretical best value Since each man-hour of the WBS unit process is independent, it is derived as follows. After that, the development man-hour estimation function 74 executes the above (5) (6) (8) (9).
The value derived from the value of the expression is displayed on the input / output device 13. Thereby, the worker 11 can predict the development man-hours. Further, the worker 11 can estimate the development cost of the development product 69 with the design B / M 91 created by the design B / M creation function 89.

[0121]

The effects of the present invention are as follows.

First, according to the product data integrated management database and development management framework of the present invention, atypically generated product data can be centrally managed, so that it can be obtained in a required format when needed. Therefore,
2 does not require the conversion procedure of the data files 25 and 25a, and as a result, the reliability of the data is improved.
Even if the locations of the data files 25 and 25a are changed, the data management function 2 of FIG. 2 performs automatic maintenance as much as possible, so that the reliability of the data is improved.

Secondly, according to the product data integrated management database and development management framework of the present invention, FIG.
Since the development man-hour estimation function 74 described in (2) presents the development progress in a timely manner, the development cost can be predicted.

Thirdly, according to the product data integrated management database and development management framework of the present invention, it is possible to centrally manage atypical product data, so that it can be obtained in a required format when needed. Therefore, the conversion procedure of the data files 25 and 25a shown in FIG. 2 is unnecessary, and as a result, the reliability of the data is improved.
Even if the locations of the data files 25 and 25a are changed, the data management function 2 of FIG. 2 performs automatic maintenance as much as possible, so that the reliability of the data is improved.

Fourthly, according to the present invention, the progress of development work can be grasped and managed regardless of the organization and the arrangement.

Fifth, according to the present invention, since the loose coupling method is adopted as the data holding method, the data holding is flexible.

[Brief description of drawings]

FIG. 1 is a configuration diagram of an embodiment of the present invention.

FIG. 2 is an example of an entry acceptance function, a product data integrated management database, a data management function, and a method of the present invention, and a tool operation for the entry acceptance function, the product data integrated management database, the data management function, and the method. It is a related diagram of a control manager function.

FIG. 3 is a process management table, a product process procedure master table,
Product data table, distribution address table, parts library table, access method table, distribution management table, statistical data table, statistical master table held by a product data integrated database including log files, and the process management table, product It is a definition diagram of a process procedure master table, a product data table, a distribution address table, a parts library table, and a log file.

FIG. 4 is a diagram showing the relationship between the design B / M creation function for the access method table of the product data integrated database of the present invention, and the process management table and product data table of the product data integrated database.

FIG. 5 is a diagram showing a relation between a product data table, a distribution address table, and a distribution management table of a product data integrated database for the data distribution management function in the embodiment of the present invention.

FIG. 6 is an embodiment of a development schedule progress management function of the present invention, which shows a tool operation control manager function for the development schedule progress management function, a process management table of a product data integrated database, and a product process procedure master table. FIG.

FIG. 7 is a relational diagram of the component library management function in the development management framework with respect to the access method table and method of the product data integrated database according to the present invention.

FIG. 8 is a flowchart showing a method for collecting man-hour statistical information, a function for collecting evaluation statistical information, a function for statistical analysis, a function for estimating man-hours for development, an acceptance function for entries, an access method table for a product data integrated database, and statistics. In one embodiment of a data table and a statistics master table, the man-hour statistical information collecting function, the evaluation statistical information collecting function, the statistical analysis function, the development man-hour estimating function, the entry receiving function, and the access to the product data integrated database according to the present invention are described. It is a related figure of the process management table of the said product data integrated database, and the product process procedure master table with respect to a method table, the said statistical data table, and a statistical master table.

FIG. 9 is a bell showing an embodiment of a version management system described in a key file of the present invention.

FIG. 10 is a configuration diagram of a conventional example.

[Explanation of symbols]

 1 entry acceptance function 2 data management function 3 tool operation control manager function 4 CAD tool 5 CAE tool 6 CAM tool 7 CAT tool, 8 CAPP tool 9 EDA framework 10 task 11 worker 12 memory 13 input / output device 14 integrated product data management Database 15 Process management table 16 Product process procedure master table 17 Product data table 18 Process instance 19 Key file 20 Log file 21 Instance 22 Access method table 23 Method 24 Log record 25, 25a Data file 26 Storage machine / Starting directory 28 Storage machine / Source directory 29 Discard event 30 Input end event 31 Method 31a Fixed value method 32 Method registration directory 33 Data 34 Data file 35 Startup request 36 Instance 37 Product name value 38 Version, Access method specification 39 Name data 40 Startup event 41 Method call 42 Startup event 43 Directory information 44 Method information 45 Instance 47 Delivery address table 48 Delivery management table 49 Parts library table 50 Statistical data table 51 Statistical master table 52 Data distribution management function 53 Other system 54 Product name ID 55 WBS unit process ID 56 Tool used ID 57 Mounted machine ID 58 Start point directory 59 Transfer file 60 Data file 61 System name 62 TCP / IP address 63 Version number 64 Date 65 Status 66 Development schedule progress management function 67 Screen display example 68 Completion date 69 Product 70 Production management system 71 Man-hour statistical information collection function 72 Evaluation standard Information collection function 73 Statistical analysis function 74 Development man-hour estimation function 75 Method directory 76 Instance 77 Parameters 78 Evaluation points 78a Pseudo evaluation points 79 Calculation method 80 All pattern type information 81 Natural logarithm of evaluation points 82 Natural logarithm of total man-hours 83 Temporary file 84 Temporary file 85 Proportional coefficient of WBS unit process 86 Exponential coefficient of WBS unit process 87 Average distribution rate of WBS unit process 88 Variance value 89 Design B / M creation function 90 CAD data file 90a CAD data file 91 Design B / M 92 classification flag 93 classification 94 own tool ID 95 partner tool ID 96 parts library management function 97 development management framework

Claims (2)

[Claims] 1. All business operations for developing and manufacturing an arbitrary product are disassembled into minimum units, the business operations are systematized, the same identification number is added, and subordinate information is provided by a product name and the same identification number. A process management table to be managed, a product process procedure master table including original data when the process management table is created, and a CAD (Computer Aided) among the process management tables
Design) tool, CAM (Computer Aided Man)
ufacturing) tool, CAT (Computer Aided Test)
ing) tool, CAE (Computer Aided Engineerin)
g) Tool and CAPP (Computer Aided Proc)
ess Planning) tool is extracted and the subordinate information is managed by the product name and the same identification number, and the CAD tool, the CAM tool, the CAT tool, the CAE tool, and the CAPP tool are created. A product data table designating a storage destination of data to be stored and data created by each of the CAD tool, the CAM tool, the CAT tool, the CAE tool, and the CAPP tool in a system outside the management of the development management framework. In the product data integrated management database that includes the distribution address table that manages the subordinate information of the system address, and the parts library table that centrally manages the parts used when developing products, which is referred to when distributing For products designed in the past, WBSs registered in the process control table ( ork Breakdown Structure) Statistical data table that manages the start time, end time, accumulated work time, work man-hours, and evaluation points of the process, and a statistical master that records statistical information parameters derived from products designed in the past. A table, a distribution management table for recording management items relating to the distribution work, and data created by any of the CAD tool, the CAM tool, the CAT tool, the CAE tool, and the CAPP tool, which are created by another arbitrary tool. A product data integrated management database comprising an access method table for managing a method of automatically converting data into a format suitable for the tool when reading. 2. All business operations for developing and manufacturing an arbitrary product are disassembled into minimum units, the business operations are systematized, the same identification number is added, and subordinate information is added to the product name and the same identification number. A process management table to be managed, a product process procedure master table including original data when the process management table is created, and a CAD) tool among the process management tables, CA
M tools, CAT tools, CAE tools, and CAP
The process of receiving the tool support of the P tool is extracted, the subordinate information is managed by the product name and the same identification number, and the C
AD tool, the CAM tool, the CAT tool, the CAE tool, a product data table designating a storage destination of data created by the CAPP tool, the CAD tool, the CAM tool, the CAT tool, the CAE
Tool, the distribution address table that manages the subordinate information of the address of the system, and refers to the case where the data created by each tool of the CAPP tool is distributed to the system outside the management of the development management framework, and the product is developed. A product data integrated management database including a parts library table for centrally managing the parts used at the time, and for products designed in the past, W registered in the process management table.
A statistical data table that manages the start time, end time, cumulative work time, work man-hours, and evaluation points of the BS basic process, and a statistical master table that records statistical information parameters derived from products designed in the past, A distribution management table recording management items related to the distribution work, and the CA
A method for automatically converting data created by an arbitrary tool of the D tool, the CAM tool, the CAT tool, the CAE tool, and the CAPP tool into a format compatible with the tool when another arbitrary tool reads the data. The CAD tool, the CAM tool, and the CA registered in the process management table existing in the product data integrated management database including the access method table to be managed.
The T tool, the CAE tool, and the CAPP tool are activated and stopped, and the CAD is controlled.
Tool, CAM Tool, CAT Tool, C
The data created by the AE tool and the tool of the CAPP tool is stored in the area described in the product data table in the integrated manufacturing data management database, and the CAD tool, the CAM tool, the CAT tool, the CA are stored.
E tool, the operation record of the tool of the CAPP tool,
A tool operation control manager function for recording in a log file, a part library management function for managing the part library table referred to by any of the CAD tool, the CAM tool, the CAT tool, the CAE tool, and the CAPP tool, In a development management framework that has a design B / M creation function that creates a parts list from the data created by the CAD tool, a development start event is received as a routine work, and the minimum unit is added to the process management table. An entry acceptance function for registering an instance of the WBS basic process that describes the business content decomposed into the data, a data management function for automatically performing data maintenance of the product data table, the entry from the process management table and the log file. Development date of the product registered with the reception function A development schedule progress management function for displaying progress, and transfer of the data created by any of the CAD tool, the CAM tool, the CAT tool, the CAE tool, and the CAPP tool to an external system according to a corresponding state. And a data delivery management function to perform, when another tool reads data created by any of the CAD tool, the CAM tool, the CAT tool, the CAE tool, and the CAPP tool,
A method for automatically converting so as to conform to the data format of the tool, the entry reception from the product data table, the process management table, the statistical data table, the statistical master table, the access method, and the log file. Development man-hour estimation function for estimating the development man-hour of the product registered by the function, and man-hour statistical information for collecting the man-hour statistical information of the product developed in the past from the process management table, the statistical data table, and the log file. A collecting function, an evaluation statistical information collecting function for collecting evaluation point information of a product developed in the past from the product data table, the statistical data table, the access method table, and the access method, the process management table, the statistics From the data table, the statistical information of the products developed in the past is analyzed, and the analysis results are shown in the statistical mass. A development management framework characterized by having a statistical analysis function registered in a data table.