Source: http://www.google.fr/patents/US20030182152?hl=fr
Timestamp: 2015-07-30 20:21:04
Document Index: 339416079

Matched Legal Cases: ['art 22', 'art 22', 'art 22', 'art 22', 'art 22', 'art 22', 'art 22', 'art 22', 'art 22']

Brevet US20030182152 - Parts list system which generates and manages a parts list simply and ... - Google�BrevetsRecherche Images Maps Play YouTube Actualit�s Gmail Drive Plus »Connexion Recherche avanc�e dans les brevets BrevetsA parts list system includes a parts list database and a parts list control section. The parts list database stores a parts list of an apparatus. The parts list relates a part number of a part of the apparatus, part data indicating properties of the part, and a status data indicating each stage of a...http://www.google.fr/patents/US20030182152?utm_source=gb-gplus-shareBrevet US20030182152 - Parts list system which generates and manages a parts list simply and effectively Recherche avanc�e dans les brevets Num�ro de publicationUS20030182152 A1Type de publicationDemande Num�ro de demandeUS 10/385,380 Date de publication25 sept. 2003 Date de d�p�t10 mars 2003 Date de priorit�25 mars 2002Autre r�f�rence de publicationCA2419881A1, US6944515 Num�ro de publication10385380, 385380, US 2003/0182152 A1, US 2003/182152 A1, US 20030182152 A1, US 20030182152A1, US 2003182152 A1, US 2003182152A1, US-A1-20030182152, US-A1-2003182152, US2003/0182152A1, US2003/182152A1, US20030182152 A1, US20030182152A1, US2003182152 A1, US2003182152A1 InventeursMamoru Nakajima, Masataka Yamamoto, Naoki Saitou, Katsunori Taguchi Cessionnaire d'origineHonda Giken Kogyo Kabushiki KaishaExporter la citationBiBTeX, EndNote, RefManCitations de brevets (5), R�f�renc� par (4), Classifications (6), �v�nements juridiques (6) Liens externes: USPTO, Cession USPTO, EspacenetParts list system which generates and manages a parts list simply and effectively
US 20030182152 A1 R�sum�
A parts list system includes a parts list database and a parts list control section. The parts list database stores a parts list of an apparatus. The parts list relates a part number of a part of the apparatus, part data indicating properties of the part, and a status data indicating each stage of a process of a design change. The parts list control section generates the status data based on the stage. The parts list control section makes relation among the status data, the part number and the part data, and stores the status data in the parts list database. Then, the parts list control section controls operations of changes of the part number and the part data in the parts list, based on the status data. Images(9) Revendications(18)
DESCRIPTION OF THE PREFERRED EMBODIMENTS [0068] An embodiment of a parts list system of the present invention will be described below with reference to the attached drawings. [0069] This embodiment is described by exemplifying a parts list used for designing an automobile. However, this may be applied to even designing the other apparatus provided with a number of parts. [0070]FIG. 1 is a view showing the configuration in the embodiment of the automobile designing system, wherein the parts list system of the present invention is applied. [0071] The automobile designing system includes a parts list system 1, a CAD figure management system 8-0. They are connected each other in a two-way through a network 9. The information terminals 8-1 to 8-n (n =1, 2, . . . ) can access the parts list system 1 and the CAD figure management system 8-0 in a two-way through the network 4 and can use it. [0072] Here, the parts list is the list generated, and used by an electronic method/an electronic apparatus like a computer. Each number of a part (hereafter, referred to as part number and PN) individually assigned to each part used for an automobile. The data in the parts list are the part number and the rest of the data (hereafter, referred to as part data). The part data related to each part is related to the part number of the part. [0073] The parts represented by the part numbers are divided into a plurality of groups for a plurality of items that constitutes the automobile. In each item, the parts are classified into a plurality of hierarchies, and arranged in a tree structure. For example, a part (a part number) of a first hierarchy is related to a relational tree of the first hierarchy. Also, a part of a second hierarchy constituting the part of the first hierarchy is related to a relational tree of the second hierarchy that is a lower order of the first hierarchy. Hereafter, they are similarly related. [0074] In the present invention, for an item (set of parts) and a part, data indicating their states are added to the part lists. The state defines the stage in the development process of the item and the part. it is exemplified by a concept stage, a designing stage and a stage completing the CAD figure and so on. By using the state of the part, it is possible to clearly judge whether the part is at the concept stage or at the designing stag in the parts list. Thus, it is possible to recognize how the part data should be treated. It is important because the part data should be treated differently at which stage the part is. Then, it is possible to treat the part data of the part from the concept stage through the designing stage to the stage completing the CAD figure continuously in one parts list. [0075] The parts list system 1 is a data processor exemplified as a workstation and a personal computer. It includes an main part section 2 and Input/Output (I/O) section 7. [0076] The main part section 2 includes a parts list control section 3 and a CAD figure control section 4, serving as programs. It also includes a parts list database 5-1, a state database 5-2, a part number rule database 5-3, a CAD figure database 6-1 and a CAD figure requirement database 6-2. [0077] The parts list control section 3 controls a change (a delete, an addition and the like) for various data of the part in the parts list, based on the state data of the part. The parts list is stored in the parts list database 5-1. [0078] Here, the state data indicates the state of the part. The state indicates the stage in the development process of the part. It is exemplified by a concept stage, a designing stage, a stage of checking the CAD figure, and a stage of completing the CAD figure and the like. [0079] The parts list database 5-1 stores the parts list 5-1′. The parts list 5-1′ is opened to the persons related to the development of the automobile. For example, engineers, persons in charge of a research, persons in charge of a technical evaluation, different designers, persons in charge of a purchase, persons in charge of a project, and the like. The opinion data, which is opinions to the parts list 5-1′ from the related persons, can be obtained at the parts list 5-1′ by the following methods. For example, allowing to write the opinion data only to a special region in the parts list 5-1′, or attaching the file including the opinion data to the parts list 5-1′, or establishing a link between the file including the opinion data and the parts list 5-1′. [0080] The state database 5-2 stores statuses A to D , a figure flag and a total flag, and the state data while they are related to each other. [0081] Here, the combinations of statuses A to D , a figure flag and a total flag indicate the state shown by the state data. [0082] The part number rule database 5-3 stores the part number rules, which defines rules for making a part number. [0083] The CAD figure control section 4 checks whether or not a CAD figure complies with the predetermined CAD figure requirement. It modifies the CAD figure, based on an input of a designer, when the CAD figure does not comply with the requirement. The figure is stored in a CAD figure database 6-1. [0084] The CAD figure database 6-1 stores CAD data of parts specified by the part numbers. Also, it has the part position shape data the region table, which are explain later. Each CAD figure is related to each part number. [0085] The CAD figure requirement database 6-2 stores a predetermined standard requirement of the CAD figures. [0086] Here, the CAD figure is come from a CAD data. The CAD data includes a part number, a CAD figure data (3D-figure), a title column data and a configuration part column data. The part number is a part number of a part to be drawn, and may be included in title column data. The CAD figure data (3D-figure) indicates three-dimensional figures of the part. The title column data indicates a title column of the CAD figure. The configuration part column data indicates a configuration part column of the CAD figure. [0087] The Input/Output (I/O) section 7 is the equipment for input/output on the workstation and the personal computer. The keyboard and the mouse are the examples of the input section. The display and the printer are the examples of the output [0088] The CAD figure management system 8-0 is a data processor exemplified as a workstation and a personal computer. It manages and permits the CAD figures of parts. [0089] The information terminals 8-1 to 8-n (n=1, 2, . . . ) are exemplified as personal computers, and they are the data processing terminals that can access the parts list system 1 and the CAD figure management system 8-0. They are used by designers, engineers, persons in charge of a research, persons in charge of a technical evaluation, other designers, persons in charge of a purchase, persons in charge of PL (Product Line), persons in charge of a trial department, persons in charge of a test and the like. [0090] The network 9 is a dedicated line exemplified as LAN (Local Area Network) or a communicable line, such as a public line and the like, exemplified as the Internet. [0091] The designer can view the opinion data from the related person by accessing the parts list 5-1′. Because the opinion data is written in, is attached as a file to or is linked to the part list 5-1′. That is, the opinion data of the related person can be easily checked on the parts list 5-1′. Thus, it is possible to decrease the time and the labor, and also possible to reduce the possibility of an oversight. [0092] Next, the parts list will be explained below in detail with reference to FIG. 2. FIG. 2 is a view showing an example of a display screen displaying the parts list. A display screen 10 includes: a part number display section 11 having a number 13, a hierarchy 14, a state 15, a part configuration 16 and an item/part name 17; and a configuration data display section 12. The part data specified by one part number is placed in one column of the display screen 10. [0093] The part number display section 11 displays the data to identify a part. The number 13 (No.) indicates a symbol, based on a predetermined rule. The hierarchy 14 (LVL) indicates the number showing the above-mentioned hierarchy. The state 15 indicates the state data as mentioned above. The part configuration 16 indicates an item and a part number of each hierarchy represented in a form of a relational tree structure, respectively. The item/part name 17 indicates names or class name or the like. [0094] The configuration data display section 12 displays the parts application data, the part configuration data, the PN position shape link data of the part, the link to the other data and the like, for each part (each column) [0095] The part configuration 16 has the relational tree structure as mentioned above. For example, in FIG. 2, below an item 16-1 (F01 20001), a part number 16-2 of a first hierarchy and apart number 16-3 of a second hierarchy are represented in the relational tree structure. The hierarchy of each part number is represented in the hierarchy 14. [0096] Here, the parts application data indicates which a part is used for the certain combination of equipment (a certain option). The part configuration data indicates the properties peculiar to apart, such as a part number, a part name, a number of parts, a material quality, a weight, a volume, a cost, a part analyzing method, a desirable parts manufacturer and the like. The PN position shape link data indicates the relation (linkage) between a part number and the part position shape data stored in the other database. The part position shape data indicates the position wherein apart is mounted in the automobile, the part shape and CAD figure (also referred to as a 3D (three-dimensional) data). The part position shape data is stored in the CAD figure database 6-1. [0097] The data structure of the parts list will be described below with reference to FIG. 3. [0098]FIG. 3 is a view describing the data structure of the parts list. The data of the parts list 5-1′ is composed of the data having respective attributes of an item 21, a part 22, a package 23, an application header 24, apart peculiarity 25 and a figure 26. Each data have relations with other data such that is shown by arrows in FIG. 3. [0099] The item 21 includes an item state data and an item data in which a part is included. The item state data indicates a state of an item such as a stage whether its data change or not. The item data corresponds to the item number of the part configuration 16 and the item name of the item/part name 17 in FIG. 2. [0100] The part 22 includes a part number, a part state data, a figure flag, and a figure state data. The part state data indicates a state of a part such as a stage whether its data may be changed or not. The figure flag indicates a presence or absence of a CAD figure. The figure state data indicates a stage whether the figure is admitted or not. The part number data corresponds to the part number of the part configuration 16 and the part number name of the item/part name 17 in FIG. 2. [0101] The package 23 includes the items and the part numbers composing a package (constituting a group of a set of figures to be collectively inspected), a package state data, and a total flag. The package state data indicates a state of the package such as a stage whether its data may be changed or not. The total flag indicates a validation of the data of the item and the part number. The items and the part numbers of the package corresponds to the CAD data in the CAD figure database 6-1 through the configuration data display section 12 in FIG. 2. [0102] The application header 24 includes a derivative data showing a derivative model to which a part indicated by a part number is applied. The derivative data corresponds to the derivative model. The derivative models are models derived from the objective model. The derivative data is written in the configuration data display section 12 in FIG. 2. [0103] The part peculiarity 25 includes an data peculiar to a part which is related to the part number, such as a part configuration data and the like. The data corresponds to the configuration data display section 12 in FIG. 2. [0104] The figure 26 includes a data of a figure of a part which is related to a part number and indicated by the part number. The data corresponds to the CAD data in the CAD figure database 6-1 through the configuration data display section 12 in FIG. 2. [0105] The combination of the item state data, the part state data, the figure flag, the figure state data, the package state data, and a total check flag corresponds to the state 15. [0106] The part 22, including the low hierarchy parts, has a relation to the item 21, such that the part 22 belongs to item 21. The part 22 has a relation to the part peculiarity 25 if the part has peculiar data. The part 22 also has a relation to the figure 26, such that the CAD figure (26) belongs to the part 22. The package 23 has a relation to the part 22, such that the part 22 is applied to the package 23. The package 23 also has a relation to the application header 24, such that the application header 24 is determined based on the package 23. [0107] These data structures are exemplified by the data generated by using object oriented program and the relational database system. These data in the parts list 5-1′ is not necessary in the one table (list). For example, tables, each of which includes some of the data of the parts list 5-1′, have relations each other. Each table is related by the part number as a key, like the relational database system. In this case, the parts list 5-1′ is the aggregation of all the tables. [0108] The parts list, explained with reference to FIGS. 2 to 3 and stored in the parts list database 5-1, will be described below in detail. The parts list database 5-1 stores the parts list 5-1′ (the data) shown in FIG. 4. [0109]FIG. 4 is a view illustrating the parts list 5-1′. The parts list 5-1′ has a hierarchy 28, a state 29, an item 30, a part number 32, a status A31, a status B33, a figure flag 34, a package 35, a status C36, a total flag 37, an application header 38, a status D39, an application 40, a part configuration 41, a configuration number 42, a configuration part number 43 and a link 27. [0110] The hierarchy 28 corresponds to the hierarchy 14 in FIG. 2. [0111] The state 29 corresponds to the state 15 in FIG. 2. [0112] The item 30 is the item data as mentioned above at FIG. 3. [0113] The part number 32 is the part number data as mentioned above at FIG. 3. [0114] The status A31 indicates the item state data as mentioned above at FIG. 3, and indicates states a1 to a4. [0115] The status B33 indicates the part state data as mentioned above at FIG. 3, and indicates states b1 to b3. [0116] The figure flag 34 indicates the figure flag as mentioned above at FIG. 3. [0117] The package 35 indicates the package as mentioned above at FIG. 3. [0118] The status C36 indicates the package state data as mentioned above at FIG. 3, and indicates states c1, c2. [0119] The total flag 37 indicates the total flag as mentioned above at FIG. 3. [0120] The application header 38 indicates a derivative data as mentioned above at FIG. 3. [0121] The status D39 indicates the figure state data as mentioned above at FIG. 3, and indicates a state d1. [0122] The application 40 is the parts application data. [0123] The part configuration 41 is the part configuration data. [0124] The configuration number 42 indicates a kind of a figure on which this part is drawn. [0125] The configuration number 43 indicates a part number of a part (a sub-part) constituting this part (a main-part). [0126] The link 27 is the data, such as the address, indicating link destinations with regard to other files, data, figures and the like. [0127] Among the above-mentioned data, some of them are cited from the data of CAD figure as the attributed data included in the CAD data. [0128] Next, the state database 5-2 is described. A state judgment list 5-2′ is stored in the state database 5-2. The state judgment list 5-2′ is a table in which status A to status D as state indicative data, a figure flag, a total flag, and the state data are related. [0129]FIG. 5 is a view illustrating the state judgment list 5-2′ in the state database 5-2. The state judgment list 5-2′ has respective data of a status A51, a status B52, a status C53, a status D54, a figure flag 55, a total flag 56 and a state 57. [0130] Each of the statuses A51 to D54 correspond to the status A31, the status B33, the status C36 and the status D39 of the parts list 5-1′ of FIG. 4. Similarly, the figure flag 55 and the total flag 56 correspond to the figure flag 34 and the total flag 37 of FIG. 4, respectively. [0131] The state 57 indicates the conditions (states) of the admission, the limitation and the inhibition with regard to the change of the data in FIG. 4. The state 57 is exemplified such as the states 1 to 4. In this case, the state 1 indicates that the operation to change the part number 32 and the application 40 is admitted. The state 2 indicates that the operation to delete the part number 32 is not admitted. The state 3 indicates that the operation to change the application 40 is not admitted. The state 4 indicates that the operation to change/add/delete the part number 32 is not admitted. [0132] Then, the state 57 is determined for a certain combination of the status A51, the status B52, the status C53, the status D54, the figure flag 55 and the total flag 56, in FIG. 5. Based on the determination, the state 29 in FIG. 4 is determined and then reflected in the state 15 in FIG. 2. [0133] That is, the state 15 (state data) in FIG. 2 is determined based on the combination of the four states and the two flags as mentioned above. Based on the combination, the state 15 is judged as each of the stages exemplified as a concept stage (the state 1 in FIG. 5), a designing stage (the state 2 in FIG. 5), a figure output stage a (the state 3 in FIG. 5) and a figure output stage b (the state 4 in FIG. 5). [0134] In the present invention, with regard to the item and the part, a data indicating its state (the state 29 in FIG. 4) is added to the parts list for each item and part. By checking the state of the part, it is easy to know what state (stage) the part is in. Even if the same parts list is referred, the using the state 29 related to the part number enables the allowable (executable) operation at each stage to be controlled, for each part discriminated by the part number. That is, the parts of the various states can be mixed within the same parts list. [0135] Also, the data peculiar to the part in the parts list can be operated without any dependence on the stages of the state 29 of the parts list, by providing the attribute of the part peculiarity 25. [0136] The display of the parts list as shown in FIG. 2 is one embodiment, and the present invention is not limited to this display. [0137] The person referring to the parts list can always obtain the data of the part indicated by the part number. Here, the data includes not only the data within the file of the parts list but also the data related (linked) to the file (or the item, the part number) of the parts list. It is carried out by finding out a proper part number from the part number 16 in FIG. 2 and looking at its row (highlighted in FIG. 2). [0138] Also, in the parts list, between the concept stage and the manufacturing stage of the automobile, the modification and the change of the part are carried out in many cases. However, their data is written to the file related to the parts list and the parts list itself. That is, the modification and the change of the part are reflected in the file at real time on each occasion. Thus, the concerned person can always know the newest situation of the development. [0139] The parts list may be generated for each classification or may be collectively generated for each model. Here, the classification implies a family (for example, a frame, an engine, a transmission and the like), a model (for example, a car model), a section (for example, a roof) and an item (for example, an airbag). [0140] In this embodiment, “relation” of data includes the relation between files, the relation between data within a file and a different file, and, the relation between data within file and data within a different file. Then, it is at a state that the one of data/file can be called out from the other data/file. For example, there is a relation method of storing a location of the other file/data (for example, a database name, a path to a database and an address of data within a database) in one file/data and then calling out by using it. Also, there is a relation method of storing a name of a database in which the different file/data is stored and a file name/part number and then calling out by using it, and the like. However, it is not limited to them. [0141] It is possible to use an approach of a conventional relational database to thereby carry out the relation based on various keys. [0142] The CAD figure will be described below with reference to FIG. 6. [0143]FIG. 6 is a view showing a display example of a CAD figure on a display screen, based on the CAD data. A CAD FIG. 45 has a configuration part column region 44-1, a title column region 44-3 and a 3D-figure region 44-2. The configuration part column region 44-1 and the title column region 44-3 include attribute data which indicate the attribute and properties of the part. The attribute data are included in part data of the parts list. [0144] The configuration part column region 44-1 is the region in which the configuration part column is generated. The configuration part column mainly displays the configuration part (sub-part) column data. The sub-parts configure the main-part drawn on the CAD figure. The configuration part column data include a configuration number (a hierarchy of a part constituting a part drawn on the CAD figure), the sub-part numbers (configuration part number)/the sub-part names, and the like. [0145] The title column region 44-3 is the region in which the title column is generated. The title column mainly displays the title column data of a main-part. The title column data include a part number of the main-part (a title part number), a part name, a design change number and the like, to specify a part drawn on the CAD figure. [0146] The 3D-figure region 44-2 is the region in which a 3D-figure is generated. The 3D-figure region 44-2 mainly displays the CAD figure data (3D-figure) of the main-part and, in some cases, the sub-parts. [0147] This embodiment describes the case of one title column and one part configuration column. However, the present invention is not limited to this case. [0148] The method of extracting the attribute data in the title column and the configuration part column can use, for example, the following process. [0149] (1) Predetermining the regions in the CAD figure in which the title column region 44-3/the configuration part column region 44-1 are generated, and the particular element to be used for writing data on these regions (44-3, 44-1). The regions are specified by the sets of coordinate in the display screen. The sets of coordinate are included in the region table stored in the CAD figure database 6-1. The particular element is a symbol (character) or font to be distinguished from other data. [0150] (2) Finding out a data group composed of particular elements within the title column region 44-3/the configuration part column region 44-1, based on the region table. [0151] (3) Extracting the attribute data from a position of the particular elements in each data group. Here, the attribute data have been composed of the particular elements. [0152] Here, the CAD data in the CAD figure database 6-1 is further explained. [0153]FIG. 7 is a view explaining a CAD data. The CAD data 6-1′ includes a part number 46, a title column 47, a configuration part column 48 and a CAD figure data 49. [0154] The part number 46 indicates the part number data (=the title part number) of a part drawn on a CAD figure. [0155] The title column 47 is the title column data, including attribute data, exemplified as a hierarchy, a item, a title part number, a part name and the like. [0156] The configuration part column 48 is the configuration part column data, including the attribute data, exemplified as a configuration number, a configuration part number and the like. [0157] The CAD figure data 49 is the CAD figure data of a part number 46. The CAD figure data 49 may be obtained from the design data of an already-designed other model or may be independently generated by the designer. [0158] The display of the figure as shown in FIG. 6 is one embodiment. It is not limited to this display. [0159] The attribute data of the title column 47 and the configuration part column 48 are related to the part data of the parts list stored in the parts list database 5-1. The CAD figure control section 4 outputs the attribute data, which is modified according to the modification of the CAD data, to the parts list control section 3. The parts list control section 3 receives the data and modifies the parts list, if the parts list is in the allowable state. [0160] The operation in the embodiment of the parts list system in the present invention will be described below with reference to the attached drawings. [0161]FIG. 8 is a flowchart showing the operation in the embodiment of the parts list system in the present invention. [0162] (1) Step S01. [0163] The designer makes the concept data of the objective model of the automobile, based on the various data required for the design. The concept data includes ideas of the change or generation of the design of the part, the contents of the part in the parts list. Then, based on the concept data and the input of the designer, the CAD figure control section 4 generates or modifies the CAD figure of the part. After generating or modifying the CAD figure, the parts list control section 3 generates or modifies the parts list 5-1′, based on the attribute data and the concept data, and the input of the designer if necessary. [0164] At this stage, statuses A31/B33/C36 of the part in the parts list 5-1′ are (or become) at a1/b1/c1. The combination of the statuses of a1/b1/c1 indicates that the data of the part can be freely changed, which is shown in the state judgment list 5-2′. It is indicated by the proper sign (or symbol) in the state 29 (and the display of the state 15). Here, status D39, the figure flag 34 and the total flag 37 are reset. [0165] (2) Step S02 [0166] The CAD figure control section 4 inspects whether or not the CAD figure complies with the standard requirement of the CAD figures in the CAD FIG. requirement database 6-2. [0167] The CAD figure is completed when it complies with the standard requirement. [0168] Based on the completion of the CAD figure, the parts list control section 3 sets a figure flag of a figure flag 33 of the part of the parts list 21-3′. [0169] The statuses A31/B33/C36 still remain at the a1/b1/c1. The combination of the statuses of a1/b1/c1 and the figure flag indicates that the delete of the part number 32 and the part configuration 41 of the part are not permitted, according to the state judgment list 5-2′ . It is indicated by the proper sign (or symbol) for the state 29 (and the display of the state 15). [0170] After that, when the CAD figure is completed, the operational flow proceeds to a step S04. When the CAD figure does not comply with the standard requirement and the CAD figure is not completed, the operational flow proceeds to a step S03. [0171] (3) Step S03 [0172] Since the CAD figure does not comply with the standard requirement of figures, the CAD figure control section 4 displays its fact and the content of the requirement that the CAD figure does not comply, for the designer. [0173] The designer modifies the CAD figure to satisfy the requirement. The operational flow returns back to the step S02. [0174] Here, the CAD figure control section 4 may have the program to be modified the CAD figure automatically in order to comply with the standard requirement of the CAD figures. In this case, the CAD figure is automatically corrected based on the standard requirement. [0175] (4) Step S04 [0176] The parts list control section 3 determines the relation between the item 30 and the part number 32 of the part used therein in the parts list 5-1′, based on the CAD figure. At the same time, it changes the statuses A31/B33/C36 to a2/b1/c1. The combination of the statuses of a2/b1/c1 and the figure flag indicates that the change of the application 40 (the parts application data of the configuration data display section 12) of the part is not permitted, from the state judgment list 5-2′. Here, also, the delete of the part number 32 and the part configuration 41 are not permitted, as mentioned above. It is indicated by the proper sign (or symbol) for the state 29 (and the display of the state 15). [0177] (5) Step S05 [0178] Based on a plurality of part numbers in the part number 32 of the parts constituting the item 30, the parts list control section 3 writes these part numbers to the package 35. At the same time, the statuses A31/B33/C36 are changed to a2/b1/c2. The combination of the statuses of a2/b1/c2 and the figure flag indicates that the operation (the delete, the change or the addition) of the part number 32 and the part configuration 41 of the part are not permitted, from the state judgment list 5-2′. Here, also, the change of the application 40 is not permitted, as mentioned above. It is indicated by the proper sign (or symbol) for the state 29 (and the display of the state 15). [0179] Here, the item 30 corresponds to the package. However, the package may be constituted by the set of parts, which is not limited to each item. In this case, the designer determines the set of the part number 32 constituting a package. The CAD figures of the package are collectively inspected at a unit of the design change. [0180] All parts in the package have finished the above steps of S01 to S05. Each of Steps S06 to S09 may be carried out for all parts in the package at the similar timing. [0181] (6) Step S06 [0182] The parts list control section 3 inspects totally whether or not the part numbers are correct, with regard to the item 30 and the plurality of part numbers 32 packaged at the unit of the design change. The points of the inspection are as follows. (a) Whether or not the part number complies with the part number rules, which is stored in the part number rule database 5-3? (b) Whether or not the same part number or item number is used for two or more different parts or items? (c) Whether or not there is the part number of the lower hierarchy, which is the same as the part number of the higher hierarchy? (d) Whether or not the relation between main-part and its subparts is correct? (e) Whether or not the part in the package is contained in a different package?
[0183] The total inspection of the CAD figure is completed when there is no problem in the total inspection. [0184] At this time, the parts list control section 3 sets the total flag of the total flag 37 of the part. However, the statuses A31/B33/C36 are still at the a2/b1/c2. The combination of the statuses of a2/b1/c2, the figure flag and the total flag indicates the completion of the total inspection of the part. This is indicated by the proper sign (or symbol) for the state 29 (and the display of the state 15), based on the state judgment list 5-2′. [0185] After that, when the total inspection of the CAD figure is completed, the operational flow proceeds to a step S08. When there is a problem and the total inspection is not completed, the operational flow proceeds to a step S07. [0186] (7)Step S07 [0187] Since there is a problem in the part number 32, the parts list control section 3 carries out the display indicating its fact and the problematic content, for the designer. [0188] The designer modifies the part number of the CAD figure and the parts list 5-1′, based on its content. [0189] Here, the parts list control section 3 may have the program to be modified the part number automatically in order to comply with the total inspection. In this case, the part number is automatically corrected based on above-mentioned inspection points. [0190] (8) Step S08 [0191] The package composed of the set of the CAD figures is completed based on the end of the total inspection. [0192] The parts list control section 3 outputs the CAD figures of the part for each package. The CAD figures are received by the CAD figure managing system 8-0 belonging to the managing department of the design. At the same time, it changes the statuses A31/B33/C36 to a3/b2/c2. The combination of the statuses of a3/b2/c2, the figure flag and the total flag indicates the output of the CAD figures of the part. This is reflected in the state 29 (and the display of the state 15), based on the state judgment list 5-2′. [0193] The designer also submits the printed CAD figures to the managing department. [0194] (9) Step S09 [0195] Based on the data indicating the permission of the design change from the CAD figure managing system 8-0, the parts list control section 3 formalizes the item 30 and the part number 32. At this stage, the design change (or new design) is formally registered in the corresponding portion (the part) of the parts list 5-1′ in the parts list database 5-1. It results in the situation that the change of the data regarding to the part in the parts list 5-1′ is not permitted. [0196] At, this time, the parts list control section 3 sets the status D39 from nothing to d1. The statuses A31/B33/C36 are still at the a3/b2/c2. The combination of the statuses of a3/b2/c2/d1, the figure flag and the total flag indicates the formal registration of the design change in the corresponding portion (the part) of the parts list 5-1′. This is reflected in the state 29 (and the display of the state 15), based on the state judgment list 5-2′. [0197] This state also indicates that the parts list control section 3 allows the operation (delete, change or addition) of data corresponding to the new (or other) part number in the part number display section 11 and the parts application data in the configuration data display section 12. [0198] (10) Step S40 [0199] If there is some other part requesting a design change in the parts list 5-1′, the operational flow proceeds to a step S01. If not so, it is ended. [0200] (11) Step S11 [0201] The parts list control section 3 changes the configuration of the item 30 (the item number) of the item, if it is necessary for the design change process, based on the input of the designer. [0202] At this time, the parts list control section 3 changes the statuses A31/B33/C36 of the other part of the item under the design change process to a1/b1/c1. This is reflected in the state 29 (and the display of the state 15), based on the state judgment list 5-2′. Here, status D39, the figure flag and the total flag are reset. [0203] (12) Step S02 [0204] The parts list control section 3 changes the configuration of the part number 32, if it is necessary for the design change process, based on the input of the designer. [0205] At this time, the statuses A31/B33/C36 are still at the a1/b1/c1. The operational flow returns back to the step S01. [0206] The designer executes this process, for all of the parts (and items) requesting the design changes. [0207] At each of the steps in the above-mentioned process, based on the states (the combination of the statuses A31/B33/C36/D39, the figure flag and the total flag), it is possible to discriminate between the states of the parts specified by the item 30 and the part number 32 (the concept stage, the figure checking stage, the totally checking stage, the figure output stage, the formalizing stage and the like). [0208] Consequently, even if the part data at the concept stage is written to the parts list before the formalization, whether or not it is formal can be precisely grasped. That is, even if the part data with regard to the parts at the various stages are mixed and noted on the same parts list, from the state data, it is possible to execute the strict management of the respective part data. [0209] Then, the usage of the same parts list enables the part data from the concept stage to the final determination to be unitarily managed. [0210] In the present invention, the parts list is opened. Thus, the data related to the development can be opened (disclosed) to the persons concerned in the development. Hence, it is possible to widely obtain the opinions from the persons concerned in the development at the suitable timings. Citations de brevets Brevet cit� Date de d�p�t Date de publication D�posant TitreUS21517334 mai 193628 mars 1939American Box Board CoContainerCH283612A * Titre non disponibleFR1392029A * Titre non disponibleFR2166276A1 * Titre non disponibleGB533718A Titre non disponible* Cit� par l'examinateur R�f�renc� par Brevet citant Date de d�p�t Date de publication D�posant TitreUS74401326 ao�t 200421 oct. 2008Microsoft CorporationSystems and methods for handling a file with complex elementsUS745115625 janv. 200611 nov. 2008Microsoft CorporationMethod and apparatus for maintaining relationships between parts in a packageUS766872829 avr. 200523 f�vr. 2010Microsoft CorporationTime polynomial arrow-debreu market equilibriumUS8015503 *28 mars 20076 sept. 2011Honda Motor Co., Ltd.Part table creating apparatus and part table creating method* Cit� par l'examinateurClassifications Classification aux �tats-Unis700/105 Classification internationaleG06F17/50 Classification coop�rativeY10S707/99938, G06Q10/06, Y02T10/82 Classification europ�enneG06Q10/06�v�nements juridiques DateCode�v�nementDescription25 ao�t 2003ASAssignmentOwner name: HONDA GIKEN KOGYO KABUSHIKI KAISHA, JAPANFree format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:NAKAJIMA, MAMORU;YAMAMOTO, MASATAKA;SAITOU, NAOKI;AND OTHERS;REEL/FRAME:014422/0963Effective date: 200302192 mai 2006CCCertificate of correction24 d�c. 2008FPAYFee paymentYear of fee payment: 426 avr. 2013REMIMaintenance fee reminder mailed13 sept. 2013LAPSLapse for failure to pay maintenance fees5 nov. 2013FPExpired due to failure to pay maintenance feeEffective date: 20130913Faire pivoterImage d'origineAccueil Google - Plan du site - T�l�chargements par lot sur l'USPTO - R�gles de confidentialit� - Conditions d'utilisation - � propos de Google�Brevets - Envoyer des commentairesDonn�es fournies par IFI CLAIMS Patent Services