JP2007334393A - Method and system for managing parts list data - Google Patents

Abstract

<P>PROBLEM TO BE SOLVED: To enhance design efficiency and reduce load on designers by eliminating the complicated design operations due to the complications of the management of preparation history of parts list data in each process and related managements of parts lift data between processes. <P>SOLUTION: The latest first parts list data grouped in the first step and the latest second parts list data grouped in the second step positioned in the step on the downstream side of the first step and prepared before the first parts list data are merged in the step. The third parts list data grouped in the second process is prepared, and the prepared third parts list data is displayed. <P>COPYRIGHT: (C)2008,JPO&INPIT

Description

  The present invention relates to a technology for managing a bill of materials created in a series of operations of product sales, design, manufacture, procurement, and maintenance.

  Conventionally, various bills of materials (also called BOM: Bill of Material) have been created for each department and managed by each department. Recently, efforts have been started to improve the efficiency and quality of design work by integrating and managing the data structure of the bill of materials in one, realizing concurrent work and collaboration. However, unification of the parts table management system has been a challenge for many years, but it is difficult to realize it. This is because the data required for each business using the bill of materials is different. The product attributes that the planning department, the manufacturing department, and the procurement department should be aware of and the evaluation points at the time of design are different. Usually, the parts list for the downstream process is created in order from the parts table created for the upstream process. For example, the planning department designs data from the viewpoint of cost and adds data related to cost to the attribute of the bill of materials. The development and design department designs from the perspective of performance and quality, and adds performance and quality data to the BOM attributes. In the production department, data is designed from the viewpoint of assembly and work efficiency, and data related to the process and routing is added to the attributes of the BOM. (In this specification, the BOM data and the various attribute data are combined with the BOM data. Called). Recently, a design viewpoint in consideration of the environment is required, and a process of designing a viewpoint of chemical substance inclusion by the environmental design department is added to a series of design work. In this way, when a bill of materials with different purposes and styles is shared or linked among multiple departments and the items considered in the design work are multi-items and specialized, how easily and accurately the bill of materials can be diverted. In order to improve the efficiency and quality of design work by promoting reuse, it is an important management issue to reduce development lead time and cost.

  For example, according to Japanese Patent Laid-Open No. 2002-73708 (Patent Document 1), parts table data having different purposes and formats created in a plurality of processes, such as a function design process and a production design process, are held in a mutually correlated format. And a technique for reusing one part table data to another part table data based on the associated information.

JP 2002-73708 A

  The above prior art is effective in improving the design efficiency and reducing the load because the BOM information can be reused using the related information. On the other hand, in order to reuse the BOM information, The management of the creation history that is important in each process is not considered.

  In addition, there has been proposed a technology for managing the bill of material data and its creation history, and creating (restoring) another bill of material data using the creation history. This technology has the effect of ensuring reliability and quality in addition to efficiency because it can restore the latest BOM data from past creation history even if design changes occur, but it is created through multiple processes. It does not take into account the relevance of the bill of material data and the process of creation.

  The present invention solves the complexity of the design work associated with both the complexity of managing the parts table creation history in each process and managing the relevance of the parts table across multiple processes, as described above. Supporting the creation of a bill of materials that spans different processes by a computer, diverting the bill of material easily and accurately, promoting reuse, improving the efficiency and quality of design work, and reducing development lead time The purpose is to reduce costs.

  In order to achieve the above object, the present invention has a parts table data management for creating new parts table data by referring to the parts table data stored in a storage device having item information on parts and information on parts configuration. The technology is the latest first BOM data belonging to the first process, the second process positioned downstream from the first process, and created before the first BOM data and The parts table data management technology for merging the latest second parts table data in the process, creating third part table data belonging to the second process, and displaying the created third parts table data It is characterized by.

  According to an embodiment of the present invention, a bill of materials creation request is received, and the bill of material data created in the past stored in a bill of materials database (hereinafter referred to as a bill of material data DB) is read according to the contents of the request. Refer to the contents and creation history number of the BOM data such as the parent-child relationship of the parts that make up the BOM and the change of attribute values, and the related BOM information of the BOM data between processes, together with the creation date and time. A function to create a BOM history information table that can track the creation process of BOM data on the memory, check the BOM history, and create new BOM data using the BOM history information table. A bill of materials data management server is provided.

  In the present invention, the complexity of design work associated with both complexity of managing the creation history of the bill of materials in each process and managing the relevance of the bill of materials across multiple processes is solved, and the process spans multiple processes. Since the BOM data can be easily and accurately created by supporting the creation of the BOM, the development lead can be reused to promote reuse and improve the efficiency and quality of the design work. This has the effect of reducing time and costs.

  Hereinafter, embodiments of the present invention will be described with reference to the drawings.

  FIG. 1 is a conceptual diagram of parts table history information in the present invention. The parts table history information 100 has design steps 101, 102, and 103 for creating a parts table. In this example, a functional design process, an environmental design process, and a production design process are expressed from the upstream process toward the downstream process. The BOM data 104 indicates BOM data with a BOM1 name created in the function design process 101 and a creation history number of 1 and is expressed as BOM1_1. The BOM data 105 is BOM2 having a BOM2 name created in the environmental design process 102 and a creation history number of 1, and is represented as BOM2_1. Similarly, the parts table data 106 indicates part table data having a part table name created in the production design process 103 of BOM3 and a creation history number of 1, and is expressed as BOM3_1. The parts table data is created from the upstream process toward the downstream process as time passes. A solid line arrow 107 in the function design process 101 is a BOM creation history indicating that BOM1_2 has been created from the BOM data BOM1_1. BOM1_2 is a BOM data with a BOM name of BOM1 whose creation history number is 2. It is. The creation history number increases with time.

  A solid line arrow 112 connecting the BOM data 104 created in the functional design process 101 and the BOM data 105 created in the environmental design process 102 is related BOM information indicating that BOM2_1 has been created from the BOM data BOM1_1. It represents that BOM2_1 was created by diverting BOM1_1. The numbers in parentheses in FIG. 1 indicate the order of creation of the parts table data, and indicate the process in which each parts table is created by the procedure starting from (1) to (7). In this way, the storage with the passage of time of the creation contents of the parts table data such as the change in the parent-child relationship and the attribute value of the parts constituting the individual parts table is used as the part table creation history, and the creation history number is associated. This BOM creation history and the related BOM information of the BOM data between processes are referred to together with the creation date and time, and the BOM history information that can track the creation process of BOM data across processes (BOM history information described later) The feature of this embodiment is that the table 209) is provided. As will be described later, the BOM data management system of the present embodiment uses the BOM history created in the processes from (1) to (5), and goes through the processes of (6) and (7). BOM2_3 and BOM3_2 are created and provided. That is equivalent to creating and providing BOM2_3 from BOM2_2, as shown by dotted arrow 108, and creating BOM3_1 from BOM3_1, as shown by dotted arrow 109. Also, bold arrows 110 and 111 indicate related parts table information created in accordance with creation of BOM2_3 and BOM3_2.

  The overall configuration of the parts table data management system of this embodiment will be described with reference to FIG. A plurality of client machines 202 and a parts table data management server 203 (server machine) are connected to the network 201. The BOM data management server 203 includes a CPU 205 and a memory 206, and is connected to a storage device that holds a BOM data DB 208. Then, the parts table data management program 207 is arranged on the memory 206, and the CPU 205 executes this program, so that the parts table history information table 209 shown in the conceptual diagram of the parts table history information in FIG. 1 is created and held. The When creating the BOM history information table 209, the BOM data management program 207 reads out necessary data (to be described later) from the BOM data DB 208, expands it in the memory 206, and holds it.

  Details of the parts table history information table 209 are shown in FIG. The BOM history information table 209 used by the BOM data management program 207 is, for example, a two-dimensional array in which the vertical axis having a BOM identifier (BOM_ID) and a creation history number is time, and the horizontal axis is a process sequence indicated by process category. It is. As a specific example, “001” is set as the parts table identifier in the first row and first column of the parts table history information table 209, and “1” is set as the creation history number. “003” is set in the parts table identifier in the third row and third column, and “2” is set in the creation history number. The parts table identifier and the creation history number are collectively referred to as parts table identification information. The process classification may be represented by a part of the parts table identifier, or the process classification may be set as a component of the parts table identification information separately from the parts table identifier.

  Next, the data handled by the parts table data management system according to the present invention and the flow of processing will be described with reference to FIGS. 4 and 5 to 28. The BOM data management server 203 receives a BOM creation request from the client machine 202. The bill of material creation request is, for example, a request for diversion creation of bill of material data or a checkout request for changing bill of material data, and indicates whether the target bill of material identification information and process classification, diversion or change It is a command consisting of processing types (FIG. 5).

  In the first row of the bill of materials creation request data 501 shown in FIG. 5, the bill of material data created in the process “111” with the bill of material identifier (BOM_ID) “001” and the creation history number “3” is diverted. Then, a request is made to create the parts table data of the process “222” (indicated in the processing type). Similarly, the second line indicates that the BOM data created in the process “333” having the BOM identifier (BOM_ID) “003” and the creation history number “1” is checked out for editing. Ask. The processing type is designated as “change”. Note that parts table data may be newly created as a processing type, but the description thereof is omitted because it is as in the prior art.

  FIG. 16 is a processing flow for receiving a bill of materials creation request. The BOM data management program 207 receives the BOM creation request data shown in FIG. 5, and acquires BOM identification information, process classification, and processing type (S1601). Next, the BOM data management program 207 determines whether or not the processing type is “Diversion” (S1602), and if it is “Diversion”, the diversion candidate BOM identification information stored in the memory is acquired as a variable. The parts table identification information is set (S1603).

  When the parts table data management program 207 receives the parts table creation request, the parts table data management program 207 searches the parts table data DB 208 and creates the parts table history information table 209. The parts table data DB 208 stores a parts table management table 1201, an item information table 1301, a configuration management table 1401, a configuration information table 401, a related parts table information table 1801, and a parts table creation history table 1901.

  As shown in FIG. 12, the parts table management table 1201 has a parts table identifier (BOM_ID), a parts table name (BOM_NAME), a top-level part identifier (TOP_PID), and a configuration information table identifier (PS_TBL_ID) as attributes.

  As shown in FIG. 13, the item information table 1301 includes a parts table identifier (BOM_ID), a part identifier (PID), a part name (PNAME), a creation history number (OP_NO), a creator, a creation date, and an update date. Each component information that constitutes is included as an attribute.

  As shown in FIG. 14, the configuration management table 1401 has a configuration information table identifier (PS_TBL_ID), a configuration information table name (PS_TBL_NAME), and process categories assigned in ascending order according to the actual process order.

  For example, when the parts table data 601 having a tree structure as shown in FIG. 6 is displayed on the client requesting the parts table creation request, the corresponding configuration information table 401 stored in the parts table data DB 208 is shown in FIG. It becomes like this. The configuration information table 401-1 in FIG. 7 is a configuration information table for function design, for example, and 10001 is stored in the configuration management table 1401 together with the process category 111 as a configuration information table identifier. The numbers in parentheses shown in FIG. 6 are the part identifiers described in the item information table 1301 and are stored in the configuration information table 401-1 in a parent-child relationship in order to express the hierarchical structure of the parts table data (BOM_ID: 001). In addition, the configuration information table 401-1 has a number that is the number of child parts to be configured and a sequence number that is a function design specific attribute. In general, BOM data is stored in a parent-child relationship and is often displayed in a hierarchical structure when displayed on the screen of a client machine.

  Similarly, FIGS. 8 and 9 also show a configuration information table 401-2 corresponding to a display example of the parts table data 801 for environmental design. FIG. 8 shows that the parts table data shown in FIG. 6 was used. It shows that two parts indicated by 802 have been added under the “casing”. In FIG. 9, “2” is set in the creation history number (OP_NO) in the sixth row and the seventh row to indicate the addition of a component. A sub-material code is added as an attribute unique to the environmental design process, and a bond and a seal are set.

  10 and 11 show a configuration information table 401-3 corresponding to a display example of the parts table data 1001 for production design. In the configuration information table 401-3 for production design in FIG. 11, the assembly process is added to the personal computer in order from the 8th line to the 12th line, the board is deleted from the personal computer, the board is added to the assembly process, and finally It can be seen that the unnecessary bonds and seals for the production process have been deleted.

  Creation types such as addition and deletion will be described later with reference to FIG. In addition, the parts table management table 1201 has a relationship between the parts table identifier (BOM_ID) and the configuration information table identifier (PS_TBL_ID), and the configuration management table 1401 has a relation between the configuration information table identifier (PS_TBL_ID) and the process category. The table structure shows the parts table data created in which process by the join operation (FIG. 15). Each record of the parts table management table 1201 may have a “process category” attribute, and the configuration management table 1401 may be omitted. As described above, the BOM data that can be displayed on the client machine is stored in the BOM data DB 208 as the configuration information table 401, and the BOM data management program 207 is referred to when the BOM history information table 209 is created. To do.

  FIG. 18 is a diagram showing a data configuration of the related parts table information table 1801. The related parts table information table 1801 stores information about the relation of parts table information between processes. For example, in the first row of the table, the original process classification “111” that is the diversion source BOM creation process, the BOM identifier “001” and the creation history number “1” of the diversion source BOM data, and the diversion destination The previous process classification “222”, which is the parts table creation process, the parts table identifier “002” and the creation history number “1” of the used parts table data, and the creation date and time of the related parts table information are set.

  FIG. 19 is a diagram showing a data configuration of the parts table creation history table 1901. The parts table creation history table 1901 has a parts table identifier (BOM_ID), a creation history number (OP_NO), a creation type (OP_TYPE) such as addition, deletion, and modification of parts, a creation date and time (OP_DATE), and changes as attributes. The creation history of all the parts table data corresponding to the creation history number set in the configuration information table 401 described with reference to FIGS. 6 to 11 is stored. The contents of change store information added and deleted, and information before and after the change.

  FIG. 17 is a processing flow for creating parts table history information. The BOM data management program 207 searches the related BOM information table 1801 based on the BOM identification information acquired in the reception process of the BOM creation request, and acquires the related BOM identifier and process category (S1702). ). For example, if the data acquired in the parts table creation request acceptance process (represented as (parts table identifier, creation history number, process category)) is (001, 1, 111), the data in the first row (002, 1, 222) is acquired, and then the data (003, 1, 333) in the second row is acquired from the acquired data (002, 1, 222). While the related BOM identifier exists, the acquisition of the related BOM identification information and process category is repeated (S1701).

  Next, the BOM data management program 207 acquires a record that matches the BOM identifier acquired in step S1702 from the BOM generation history table 1901 and combines it with the process category to generate a generation history sort table (S1703). In creating the creation history sort table 2001, the parts table creation history records acquired as shown in FIG. 20 are sorted in ascending order of creation date and time.

In step S1704, the BOM data management program 207 creates a BOM history information table 209 with the process as the horizontal axis and the creation date and time as the vertical axis, and sets the BOM identifier and creation history number of the creation history sort table 2001 as one line. Set in order from the eye. A specific setting procedure is as follows, and setting is performed from the first column to the Nth column, from the first row to the Nth row. Let the parts table history information table 209 be T (i, j) {1 <= i <= max (number of rows), 1 <= j <= max (number of columns)}. In the case of FIG. 3, max (number of rows) = 8 and max (number of columns) = 3.
(1) The parts table identifier “001” and the creation history number “1” in the first row of the creation history sort table are set in the first row of the parts table history information table 209 and the first column of the process classification: 111 (T (Set to (1, 1)).
(2) The parts table identifier “002” and the creation history number “1” in the second row of the creation history sort table are set in the first row of the parts table history information table 209 and the second column of the process classification: 222 (T (Set to (1, 2)).
(3) The parts table identifier “002” and the creation history number “2” in the third row of the creation history sort table are set in the second row of the parts table history information table 209 and the second column of the process classification: 222 (T (Set to (2, 2)).
(4) The parts table identifier “003” and the creation history number “1” in the fourth row of the creation history sort table are set in the second row of the parts table history information table 209 and the third column of the process classification: 333 (T (Set to (2, 3)).
(5) The setting in the column direction and the setting in the row direction of the parts table history information table 209 are repeated for all records in the creation history sort table 2001 in order with reference to the process category and creation date and time.

  Next, the parts table history check process will be described with reference to the process flow of FIG. The parts table data management program 207 determines whether or not the process type acquired in step S1601 in FIG. 16 is “Divert” (S2101). If it is “Divert”, the process ends. Otherwise, the BOM data management program 207 starts from the cell in the next row of the same process category of the cell in which the BOM identification information to be “changed” is set, and moves the BOM history information table 209 horizontally. The cells are moved one by one to the left in order along the axis, and the number of movements of the cells until a cell in which BOM identification information is set appears is stored (S2102). Next, the BOM data management program 207 determines whether there is a cell for which BOM identification information is set (S2103). If there is no cell for which BOM identification information is set, the process ends. If there is a cell in which the parts table identification information is set, the part history information table 209 is moved downward along the vertical axis starting from that cell, and the last part table set in the cell in the relevant process category Identification information is acquired and used as diversion candidate parts table identification information (S2104). The reason why the last BOM identification information is set in the diversion candidate BOM identification information even though the process type is “change” is that when the change is made to the BOM data to be changed, This is because it is necessary to consider diversion of the parts table data indicated by the table identification information.

  FIG. 22 shows this state. In FIG. 22, since the process type acquired in step S1601 of FIG. 16 is “change”, the process proceeds to step S2102. Starting from the cell immediately below the BOM identification information (003, 5) to be changed, if one cell is moved along the horizontal axis, the BOM identification information is not set in the cell. Move one. Thus, when two cells are moved, the parts table identification information (001, 2) is found. Next, it moves downward along the vertical axis, acquires the parts table identification information (001, 3) set in the last cell in which the parts table identification information is set, and uses it as the diversion candidate parts table identification information.

  In FIG. 23, since the processing type acquired in step S1601 in FIG. 16 is “Divert”, the parts table identification information (001, 3) is set as the diversion candidate parts table identification information in step S1603 in FIG. . In this case, the check processing of S2102 to S2104 is not executed.

  Next, the parts table data creation processing of the parts table management server 203 shown in FIG. 4 will be described with reference to FIG. The BOM data management program 207 determines whether or not the diversion candidate BOM identification information is set (S2401). If (001, 3) is set in the diversion candidate parts table identification information, this is used as the first parts table identification information. Next, the parts table data management program 207 repeats the processing procedure from S2403 to S2406 by the number of movements (S2402). However, when the processing type is “Diverted”, the number of movements is set to 1. The parts table data management program 207 traces the history of the first parts table in the past (follows the vertical axis of the parts history information table 209) and has related parts information (the parts table identification information in the adjacent cell on the right side) The second part table identification information (001, 1) is specified (S2403). Next, the BOM data management program 207 acquires third BOM identification information (002, 1) associated with the related BOM information (S2404). Next, the BOM data management program 207 acquires the identification information (002, 2) of the fourth BOM that is the latest BOM from the acquired third BOM creation history (S2405). Next, the BOM data management program 207 applies the creation history from the second BOM to the first BOM to the fourth BOM data to create fifth BOM data (S2406). In the component history information table 209, fifth component table identification information is set. The detailed process of S2406 will be described later. The parts table data management program 207 transmits the created parts table data to the client machine 202 via the network 201. The client machine 202 displays the data on the display device in the formats as shown in FIGS. The parts table data management program 207 displays the created parts history information table 209 on the display device of the client machine 202.

  If the number of movements stored in the parts table history check process is 2 or more, the identification information of the fifth parts table created is set in the first parts table identification information, and the process is repeated (S2402). The parts table data management program 207 traces the history of the first parts table identification information (002, 3) in the past (follows the vertical axis of the parts history information table 209) and has related parts information (adjacent to the right). The second parts table identification information (002, 2) is specified (the cell in which the parts table identification information is set in the cell to be determined can be determined to have related parts information) (S2403). Next, the BOM data management program 207 acquires third BOM identification information (003, 1) associated with the related BOM information (S2404). Next, the BOM data management program 207 acquires identification information (003, 5) of the fourth BOM, which is the latest BOM, from the acquired third BOM creation history (S2405). Next, the BOM data management program 207 applies the creation history from the second BOM to the first BOM to the fourth BOM data to create fifth BOM data (S2406). In the component history information table 209, fifth component table identification information is set. The detailed process of S2406 will be described later. The parts table data management program 207 transmits the created parts table data to the client machine 202 via the network 201. The client machine 202 displays the data on the display device in the formats as shown in FIGS. The parts table data management program 207 displays the created parts history information table 209 on the display device of the client machine 202.

  FIG. 25 shows the first to fifth parts tables identified in the processing procedure until the parts table of identification information (002, 3) is created by diverting the parts table of identification information (001, 3). Show. In this case, even if an instruction to change the fourth bill of materials is given as the processing type, the same fifth bill of materials is created. FIG. 26 shows the first to fifth parts tables identified in the processing procedure from changing the parts table of identification information (003, 5) to creating the parts table of identification information (003, 6). Show.

  Next, the detailed processing procedure of S2406 will be described. Applying the change contents of the BOM creation history table 1901 interposed between the second BOM and the first BOM in the configuration information table 401 and the item information table 1301 related to the second BOM in order from the oldest. The configuration information table 401 and the item information table 1301 regarding the first parts table can be formed. If the configuration information table 401 and the item information table 1301 related to the first parts table are registered in the DB, the information can be used directly. Similarly, in the configuration information table 401 and the item information table 1301 regarding the third parts table, the contents of changes in the parts table creation history table 1901 interposed between the third parts table and the fourth parts table are changed in order from the oldest. When applied, the configuration information table 401 and the item information table 1301 regarding the fourth parts table can be formed. If the configuration information table 401 and the item information table 1301 related to the fourth parts table are also registered in the DB, the information can be used directly. When the item information and configuration of the configuration information table 401 and item information table 1301 related to the first parts table created are merged with the item information and configuration of the configuration information table 401 and item information table 1301 related to the fourth parts table, respectively. The configuration information table 401 and the item information table 1301 regarding the fifth parts table can be created. Here, “merging” is a combination of item information and configuration common to both items, and item information and configuration existing in one of the parts lists.

  In the bill of material data creation process, new related bill of material information and bill of material creation history are created, so the created related bill of material information and bill of material creation history are added as shown in FIGS. Here, the “change contents” of each part table creation history in the parts table creation history table 1901 is the difference in item information and configuration between the fourth and fifth parts tables.

  As described above, according to the present embodiment, when a bill of material creation request is received, the bill of material data created in the past stored in the bill of material data DB is read according to the request contents, and the bill of material history information table is stored in the memory. Provided is a BOM data management server having a function of checking the BOM history created above and creating new BOM data using the BOM history information table. This solves the complexity of the design work associated with both the complexity of managing the BOM creation history within each process and managing the relevance of the BOM across multiple processes, and parts that span multiple processes. The creation of the table is supported by a computer, and the parts table data can be created easily and accurately. Furthermore, it can contribute to shortening the development lead time and cost while improving the efficiency and quality of the design work by diverting the bill of material data and promoting the reuse.

  Note that the parts table history information table 209 exemplified in this embodiment may not be a two-dimensional array in which parts table identification information is set, but may have a data structure in which elements are connected by pointers. Further, the parts table history information table may be sent to the client machine and used as data for display on a display device such as a display connected to the client machine, thereby referring to the history information of the parts table. In addition, the parts table data DB 208 connected to the parts table data management server 203 may be on the same server or a different server. The creation history of the parts table data is not limited to the configuration information indicating the parent-child relationship, and may be the creation or change history of the item information that is the parts information.

It is a conceptual diagram of parts table history information. It is a figure which shows the whole structure of parts table data management system. It is a structural example of a parts table history information table created by a parts table data management program. It is a figure which shows the data and processing flow which a parts table data management system handles. It is a figure which shows the example of a structure of parts table preparation request data. It is a figure which shows the example of a display of parts table data (for function design). It is a figure which shows an example of a structure information table (for function design). It is a figure which shows an example of a display of parts table data (for environmental design). It is a figure which shows an example of a structure information table (for environmental design). It is a figure which shows an example of a display of parts table data (for production design). It is a figure which shows an example of a structure information table (for production design). It is an example of a structure of a parts table management table. It is an example of a structure of an item information table. It is an example of a structure of a structure management table. It is a figure explaining the reference relation of a parts table management table and a configuration management table. It is a flowchart showing the reception process of a parts table preparation request. It is a flowchart showing parts table history information creation processing. It is an example of a structure of a related components table | surface information table. It is an example of a structure of a parts table creation history table. It is a figure which shows an example of a creation log | history sort table. It is a flowchart showing parts table history check processing. It is an example of the parts table history information at the time of parts table data change. It is an example of the parts table history information when the parts table data is diverted. It is a flowchart showing parts table data creation processing. It is a figure explaining the creation procedure of parts table history information. It is a figure explaining the preparation procedure of parts table history information (continuation). It is a figure which shows an example of the related components table | surface information table which added information. It is a figure which shows an example of the components table preparation log | history table which added information.

Explanation of symbols

202: Client machine, 203: BOM data management server, 207: BOM data management program, 208: BOM data DB, 209: BOM history information table, 401: Configuration information table, 1301: Item information table, 1801: Related parts table information table, 1901: Parts table creation history table

Claims (10)

A BOM data management method for creating new BOM data with reference to BOM data stored in a storage device having item information on parts and information on parts configuration,
Obtaining the latest first parts table data belonging to the first step from the storage device;
Belonging to the second process positioned downstream from the first process, and is created before the first parts table data and the latest second parts table data in the process is acquired from the storage device;
The item information and the part configuration common to both the first parts table data and the second parts table data are set as common information, and the item exists in any one of the parts table data. By adding information and the parts configuration to the common information, the first parts table data and the second parts table data are merged, and the third parts table data belonging to the second step is obtained. make,
A parts table data management method comprising displaying the created third parts table data.   The identification information of the BOM data is expressed by a set of a BOM identifier and a creation history number, and the identification information of each of the first BOM data, the second BOM data, and the third BOM data is represented. A two-dimensional array including the identification information in a two-dimensional array so that one axis is a sequence of steps and the other axis is a time axis, and the two-dimensional array of the identification information is displayed. The parts table data management method according to claim 1.   2. The parts table data management method according to claim 1, wherein a set of identification information of the first parts table data and identification information of the third parts table data is registered in the database as related parts information. .   The fourth bill of material data, which belongs to the first step and uses the change from the fourth bill of material data created before the first bill of material data to the first bill of material data. The parts table data management method according to claim 1, wherein the first parts table data is created from the data.   The identification information of the BOM data is expressed by a set of a BOM identifier and a creation history number, and the BOM data belonging to the first process is such that one axis is a sequence of processes and the other axis is a time axis. 2. The parts table data according to claim 1, wherein the identification information and the identification information of the parts table data belonging to the second step are two-dimensionally arranged and the two-dimensionally arranged identification information is displayed. Management method.   A set of identification information of the first BOM data and identification information of the third BOM data is used as related component information, and the related component information, the BOM data belonging to the first step, and the first 6. The parts table data management method according to claim 5, wherein the identification information arranged two-dimensionally is created from a creation history of parts table data belonging to step 2.   2. The parts table data according to claim 1, wherein the third parts table data is created in response to an instruction of identification information of the first parts table data and a processing type meaning diversion. Management method.   2. The parts table data according to claim 1, wherein the third parts table data is created in response to an instruction of identification information of the second parts table data and a processing type meaning a change. Management method. A BOM data management system for creating new BOM data with reference to BOM data stored in a storage device having item information on parts and information on parts configuration,
The latest first BOM data belonging to the first process is acquired from the storage device, belongs to the second process positioned downstream from the first process, and before the first BOM data. The item information and the component configuration common to both the first parts table data and the second parts table data are acquired from the storage device and the latest second parts table data created and in the process is acquired. Is added to the common information by adding the item information and the component configuration existing in either of the parts table data to the first part table data and the second parts. A server machine that merges table data and creates third parts table data belonging to the second step;
A parts table data management system comprising: a client machine that receives and displays the third parts table data via a network. A program for causing a computer to function as an information processing apparatus having means for creating new parts table data by referring to parts table data stored in a storage device and having item information on parts and information on parts configuration The computer
Means for obtaining the latest first parts table data belonging to the first step from the storage device;
Means for acquiring from the storage device the second part table data that belongs to the second process positioned downstream from the first process, is created before the first part table data, and is the latest in the process. ,
The item information and the part configuration common to both the first parts table data and the second parts table data are set as common information, and the item exists in any one of the parts table data. By adding information and the parts configuration to the common information, the first parts table data and the second parts table data are merged, and the third parts table data belonging to the second step is obtained. A program for functioning as means for creating and means for displaying the created third parts table data.

Images