KR20130055239A - A method of making standard items for plm and erp system and the system thereof - Google Patents

Abstract

PURPOSE: An integrated reference information generation method of PLM(Product Lifecycle Management) and ERP(Enterprise Resource Planning) and a system thereof are provided to integrate item definition as one and to define a plurality of related items as one item generation condition, thereby efficiently managing the plurality of related items. CONSTITUTION: A reference information system registers an item catalog and inputs a plurality of attributes and attribute candidate values(S10). The reference information system brings the item catalog and defines an item generation condition(S20). The reference information system selects an attribute value and sets a relation between the attributes. The reference information system defines an item by the attribute value(S30). [Reference numerals] (AA) Start; (BB) End; (S10) Register an item catalog; (S20) Define an item generation condition; (S30) Define an item

Description

A method of making standard items for PLM and ERP system and the system eg}

The present invention generates item creation conditions of a reference information system by an item catalog, and PLM and ERP integration reference information defining items in a product lifecycle management (PLM) system and an enterprise resource planning (ERP) system according to the item creation conditions. It relates to a production method and system.

In general, PLM (Product Lifecycle Management) system is a system that consistently manages the entire process from product blueprint to final product production, which can increase product added value and reduce cost. In addition, the Enterprise Resource Planning (ERP) system is an optimal management of all resources of a company, and is a computer system that efficiently and automatically regulates the flow of all tasks such as purchasing, production, and sales.

In particular, since the shipbuilding industry assembles and processes a large number of parts to manufacture one huge ship and its components, the PLM system manages from the lifecycle perspective of the product, and distributes the parts and resources required for all the various ships and their components. And an ERP system to manage them. In other words, the PLM system mainly supports design-related information, and the ERP system is a system for procuring and producing actual parts.

PLM and ERP systems manage and develop components, products, or resources from different perspectives and are independent of each other. Therefore, PLM system and ERP system were separately constructed and managed for ship manufacturing.

Since PLM and ERP are separate systems, the data systems created and managed by each system (data systems for resource management such as parts) are different. For example, in a PLM system, only the master bill of material (BOM) is managed, whereas in an ERP system, the project bill of materials (BOM) can be managed separately from the master bill of material (BOM). An item master that manages the definition of an item, or a project BOM that documents and manages items hierarchically, exists in both the PLM and ERP systems.

In addition, both PLM and ERP use reference information, but tools for managing each reference information separately and generating and managing the information are different. In the PLM, the management is managed by a part family that is registered from the upper classification to the lower classification step by step. In the ERP system, the upper classification and the lower classification reference information are individually managed in a key-in manner.

As such, since the PLM and the ERP system are operated separately, there are the following problems.

The PLM and ERP systems are managed separately, but the data actually goes from the PLM system to the ERP system. That is, since the data flow is a process of transferring information from the PLM to the ERP, there is a fear of an error in item (ITEM) / BOM consistency by separately managing the reference information in the programs of both systems.

Also, in both PLM and ERP systems, there is a lot of waste by managing duplicated reference information. For example, even if one change is made, the same changed information is updated to both systems. In particular, for manufacturers with multiple production bases (ship drier), there are as many ERP systems to update as there are ERP systems for each dry base. As a result, more manpower and time are consumed.

In addition, there is no route to share information on the reference information classification system between PLM and ERP.

In addition, there is a difference in the information management method between the project BOM and the PLM / ERP of the item master. Bill of Material (BOM) is data on which parts of a specific product are composed. Engineering Bill of Material (E-BOM) is used in a PLM system, and a manufacturing BOM (M-BOM) is used in an ERP system. An E-BOM is a product structure made by design, and an M-BOM is a BOM based on the assembly sequence for production.

When the E-BOM is completed, it creates an M-BOM, which takes all the parts in the E-BOM and restructures the product structure. In other words, the component used in the E-BOM is used as it is and only the configuration is rebuilt. If you look at the product structure, it looks like a tree. The leaf at the far end is the part, and the branch meets the assembly. The data from E-BOM to make M-BOM is the leaf part. You can also import the assembly if needed. However, when you create an M-BOM, you are not just making parts from the E-BOM. This is because there are parts and materials that are necessary for production but are not reflected in the design.

At this time, by the system, the E-BOM information is converted to the M-BOM by a specific logic (LOGIC). However, since the M-BOM-related information does not exist in the PLM, an error occurs frequently during the transmission of the JOB ORDER ITEM.

In addition, the item category (ITEM CATALOG) management concept, PLM is managed as a FART FAMILY, but ERP is managed as an item master (ITEM MASTER), so there is a consistency error according to the information management method difference.

The item category (ITEM CATALOG) or part family (FART FAMILY) is similar, but is a part information management structure to distinguish many parts and define them into a single family of parts. For example, there may be hundreds or thousands of screws, depending on the shape, length, pitch of the screws, and the like. It is convenient to classify them and manage similar parts as a single item. In order to easily define and distinguish such items, an item category (ITEM CATALOG) or a part family (FART FAMILY) is used in advance.

However, if these item categories (ITEM CATALOG) or parts family (FART FAMILY) are different from each other, there is a significant difference between the information management structure and method of the two systems for managing items, so that consistent item management is difficult.

An object of the present invention is to solve the above problems, an item category that can be defined in common in a product lifecycle management (PLM) system and an enterprise resource planning (ERP) system, and creation for creating items It is to provide a method and system for generating PLM and ERP integration reference information that integrates and defines conditions.

It is also an object of the present invention to generate an item creation condition of a reference information system by an item catalog, and to define an item in a product lifecycle management (PLM) system and an enterprise resource planning (ERP) system according to the item creation condition; It is to provide a method and system for generating ERP integrated reference information.

In order to achieve the above object, the present invention relates to a method for generating PLM and ERP integrated reference information defining items in a product lifecycle management (PLM) system and an enterprise resource planning (ERP) system according to an item creation condition of a reference information system. (a) the reference information system registering an item catalog, and inputting property values (hereinafter, property candidate values) that may have a plurality of properties and the properties in the item catalog; (b) the reference information system importing the item catalog to define item creation conditions, selecting property values from among property candidate values of the catalog, and setting relationships between property values of different properties; And (c) the PLM or ERP system defining the item by a property value, wherein the property value of the item satisfies a condition for generating the item.

In addition, in the method of generating the PLM and ERP integrated reference information, the present invention is characterized in that in the step (a), it is possible to set the relationship between the property candidate values of different physical properties in the item catalog.

In addition, the present invention, in the method for generating the PLM and ERP integrated reference information, in the step (b), if one property (hereinafter referred to as the first physical property) and other properties (hereinafter referred to as the second physical property) in relation to the first, The properties (hereinafter, referred to as individual relationships) may be set by selecting the property values of the second property with respect to all property values belonging to the property.

In addition, the present invention provides a method for generating the PLM and ERP integrated reference information, in step (b), if at least one property value of the second property is not selected with respect to the property value of the first property, all property values of the second property are determined. It is characterized by judging by the selection.

In addition, the present invention, in the method of generating PLM and ERP integrated reference information, in step (c), if the physical property (hereinafter, the corresponding physical property) of the item creation conditions has one physical property value (hereinafter, the corresponding physical property value), the corresponding item of the item The physical properties are automatically set to the corresponding physical property values.

In addition, according to the present invention, in the method for generating the PLM and ERP integrated reference information, the item catalog is classified into a standard product and a non-standard product. Characteristic value can be input.

In addition, the present invention, in the method for generating the PLM and ERP integrated reference information, if there is an item catalog of the standard product by searching the item catalog of the standard product that satisfies all the item generating conditions created by the catalog of the non-standard product, the item creation condition is And item creation conditions of the item catalog of the standard product.

The present invention also relates to a computer-readable recording medium having recorded thereon a program for performing the method for generating the PLM and ERP integrated reference information.

In addition, the present invention relates to a system for generating PLM and ERP integrated reference information defining item creation conditions for use in a product lifecycle management (PLM) system and an enterprise resource planning (ERP) system. A catalog registration unit for inputting a plurality of properties and property values (hereinafter, property candidate values) that the properties can have; And a generation condition definition unit for defining an item creation condition by importing the item catalog, selecting a property value from among property candidates of the catalog, and setting a relationship between property values of different properties, wherein the item is defined by a property value. As defined, the physical property value of the item is characterized in that it is defined to satisfy the creation conditions of the item.

In addition, the present invention is a method for generating PLM and ERP integrated reference information, characterized in that the catalog register can set the relationship between the property candidate values of different physical properties in the item catalog.

In addition, the present invention is a method for generating PLM and ERP integrated reference information, wherein the generation condition defining unit is set to the first physical property when the other property (hereinafter referred to as the second physical property) is set in relation to one physical property (hereinafter referred to as the first physical property). The properties (hereinafter, referred to as individual relationships) may be set by selecting property values of the second property with respect to all property values belonging thereto.

In addition, according to the present invention, in the method for generating the PLM and ERP integrated reference information, the item catalog is classified into a standard product and a non-standard product. Characteristic value can be input.

As described above, according to the method and system for generating the PLM and ERP integration reference information according to the present invention, the item definitions used in the PLM and ERP are integrated into one, and a plurality of related items are defined as one item creation condition. A manageable effect is obtained.

According to the method and system for generating PLM and ERP integrated reference information according to the present invention, it is possible to selectively standardize and manage the property values for non-standard products, and in the case of standard products, it is possible to increase the consistency of the property values, thereby contributing to the improvement of utilization of the reference information of the following sector. Effect is obtained.

1 is a diagram showing a configuration of an overall system for carrying out the present invention.
2 is a flowchart illustrating a method of generating PLM and ERP integration reference information according to an embodiment of the present invention.
3 is a flowchart illustrating a method of registering an item catalog according to an embodiment of the present invention.
4 is an example of a screen for registering a catalog according to the present invention.
5 is an example of a screen for setting conditions for generating an item according to the present invention.
Figure 6 illustrates an example of setting the relationship between the properties in accordance with an embodiment of the present invention.
7 is a block diagram of the configuration of the PLM and ERP integration reference information generation system according to an embodiment of the present invention.

DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, the present invention will be described in detail with reference to the drawings.

In the description of the present invention, the same parts are denoted by the same reference numerals, and repetitive description thereof will be omitted.

First, examples of the configuration of the entire system for carrying out the present invention will be described with reference to Fig.

As shown in FIG. 1, an example of the whole system for implementing this invention consists of the PLM system 10, the ERP system 20, and the reference information system 30. As shown in FIG. In addition, it may be configured to further include a database (40).

The PLM system 10 is an integrated software system composed of design (support) modules in order to systematically organize and utilize design, production data and information about a product (or project). The PLM system 10 is composed of modules that support BOMs, drawings, documents, design procedures, and the like. The PLM system 10 in the shipbuilding industry manages the drawings and the bill of materials (BOM) as essential data.

Bill of Materials (BOM) is a hierarchical structure of data about which parts a product (or vessel, its components) is composed of. In this case, the product, part, material, or materials are defined as one item in the BOM. Therefore, the BOM is a data structure that defines information about which item is composed of a certain item and a relationship between items.

In the PLM system 10, a user or an administrator creates and manages each item. An item is created by referring to an item catalog. An item may be created using the property values (or property values) specified in the item catalog as it is, or a specific property (or property, or property) may be selected among the property values selectable from the item catalog. It can also be created by selecting an attribute). An item catalog is created by the reference information system 30. That is, an item catalog is created in advance and registered in the system, and a user (or administrator) creates an item by referring to a registered item catalog.

Next, the ERP system 20 is an integrated software system composed of modules that procure and manage resources as a resource. In an ERP system, a product or part is managed as an item data structure, and a bill of material (BOM) that includes these items is also constructed.

In this case, the ERP system 20 may use an item or a BOM generated by the PLM system 10 or may generate and use an item or a new BOM. The ERP system 20 also generates an item by referring to an item catalog generated by the reference information system 30.

Next, the reference information system 30 generates and manages reference information used in the PLM system 10 and the ERP system 20. Reference information refers to information on standards and standards that assign or set parts, BOM properties, product information, product / part group properties, classification systems, drawing properties, size forms, part codes, and drawing numbers.

In particular, the reference information system 30 defines and creates an item catalog, which is a template for creating an item. The item catalog is composed of physical properties that an item should have, and physical property values that the physical property may have. The item catalog also includes a relationship between property values belonging to different properties. By specifying each property value in the item catalog, an item is specified. At this time, the property values of the item should be specified to satisfy the property value relationship of the item catalog.

Next, the database 40 is composed of a reference information DB 42 for storing reference information and a catalog DB 41 for storing an item catalog. However, the configuration of the database 40 is only a preferable example, and in the development of a specific device, in consideration of the ease and efficiency of access and retrieval, the database 40 may be configured in a different structure.

Next, a method of generating PLM and ERP integration reference information according to an embodiment of the present invention will be described in more detail with reference to FIG. 2.

As shown in FIG. 2, the PLM and ERP integration reference information generating method may include generating an item catalog (S10), defining an item generating condition for creating an item (S20), and an item according to an item generating condition. It is made to the step (S30).

First, the reference information system registers an item catalog, but inputs a plurality of properties and property values (hereinafter, property candidates) that may have a plurality of properties in the item catalog (S10).

Registering the item catalog is shown in more detail in FIGS. 3 and 4. 3, first, if the item type is not registered, the item type is registered (S11). The item type registration screen is shown in FIG. 4A.

In addition, the part family of the item (part family) is specified separately. The part family is a data structure managed by the PLM system 10 and is a structure for classifying and managing items. When registering an item catalog, a part family is also specified and specified (S12). At this time, the categories are classified (S13), and if there is no category, a category is newly input (S16) and the category is classified (S13). Related screens are shown in FIGS. 4B and 4C.

When the item type or item catalog is registered, the registered information is also registered in a corresponding data structure in another associated system, that is, the PLM system 10 or the ERP system 20. That is, it registers in the PLM parts family, TPI catalog, and ERP reference information.

The item catalog may be classified into a standard product and a non-standard product and registered. If the item catalog is a non-standard product, a property value other than the property candidate value of the item catalog may be input in an item generating condition.

That is, when registering an item catalog, the item catalog can be classified into a standard product and a non-standard product. Standards can be set as standard and property values can be set only within the specification of the standard, whereas non-standards are parts (or materials) into which any property value can be entered.

As shown in Fig. 3, in the case of a standard product, a part standard is registered (S17). The parts standard includes not only the physical properties of the item catalog but also matters to be followed in a standard such as specifications.

In addition, in the case of the standard product, the properties of the item catalog are set or updated (S18). In this case, the property values that may have properties of the item catalog may be set.

On the other hand, the relationship between the property candidate values of different physical properties in the item catalog can be set. The method of setting the relationship between the property candidate values is the same as the method of setting the relationship of the item generating conditions to be described below.

Next, the reference information system loads the item catalog to define item creation conditions, selects property values from among property candidate values of the catalog, and sets relationships between property values of different properties (S20).

In particular, when one property (hereinafter referred to as "first property") is set to another property (hereinafter referred to as "second property") as a relation, the property value of the second property is selected for all property values belonging to the first property (hereinafter, the individual properties). Relationship). In this case, when none of the physical property values of the second physical property are selected with respect to the physical property values of the first physical property, it is determined that all the physical property values of the second physical property are selected. In addition, when the physical properties (hereinafter, the corresponding physical property) of the item generating condition has one physical property value (hereinafter, the corresponding physical property value), the corresponding physical property of the item is automatically set to the corresponding physical property value.

In the example of FIG. 5A, the item catalog defines item creation conditions with reference to catalog 2PO. The physical properties of an item catalog consist of pipe diameter, material, thickness, and so on. Each property has a property value (or property candidate value) that it can have. For example, the pipe diameter may have 6A, 8A, 10A, 15A, 16A, 20A, 100A, 120A, 1000PHI, 1050PHI and the like. In addition, the material may have STP (stainless steel), SPP, COP (copper) and the like.

First, the property values within the properties can be selected. As shown in circle 2 of FIG. 5B, 6A, 8A, and 10A are selected as the property values in the properties of the pipe diameter. At this time, the property values which can be selected among the property values 6A, 8A, 10A, 15A, 16A, 20A, 100A, 120A, 1000PHI, and 1050PHI of the item catalog are limited to 6A, 8A, and 10A.

In addition, the relationship between the property values of different physical properties is set. Set the pipe diameter properties as a dependency of the material properties. If circle 1 of FIG. 5A is selected, a screen such as circle 1 of FIG. 5B is popped up to select which properties to set. Here, the pipe diameter physical properties can be set.

When the properties of the dependency are set, all properties of the properties are set for each of the properties of the dependency. In FIG. 5A, the STP property value of the material property is expressed as 6A / 8A / 10A, and the relationship is set to 6A, 8A, and 10A. This means that pipes with diameters of 6A, 8A, and 10A are STP capable. Therefore, if the diameter is 15A, 16A, 20A, 100A, etc., the material cannot be made of STP. In addition, in the case of copper, it can be seen that only 1000PHI and 1050PHI are possible.

As shown in FIG. 6, the relationship between the properties may be represented by the relationship between the property sets. Physical property F1 has only physical property M1 and M2, and physical property F4 has only physical property M5. In contrast, the physical property M5 may have physical properties F3, F4, and F5. 5 is one example of inputting a property relationship, and may be input in a set relationship as shown in FIG. 6.

On the other hand, as shown in circle 3 of FIG. 5A, if nothing is defined (if not specified), it is automatically set to have all property values.

Next, the PLM or ERP system defines the item by the property value, but defines the property value of the item to satisfy the conditions for generating the item (S30).

As described above, one item group is formed by generating an item by satisfying the item generating condition with reference to the item catalog. In the example of FIG. 5, a case in which the property values of the pipe diameters are selected as 6A, 8A, and 10A, and the material properties are set to 6A, 8A, and 10A only in STP will be described as an example. At this time, if only the diameter and material can be divided, only 6A STP pipe, 8A STP pipe, 10A STP pipe can be generated. As another example, if all properties of the pipe diameter are selected, the items that can be created are as follows. 6A STP pipe, 8A STP pipe, 10A STP pipe, 100A SPP, 120A SPP, 1000PHI COP pipe, 1500PHI COP pipe, SU1 pipe of all diameters.

Preferably, when the property (hereinafter, the corresponding property) of the item generating condition has one property value (hereinafter, the property value), the property of the item is automatically set to the property value. For example, in the example of FIG. 5A, if only 1000 PHI is described as a dependency relationship between the material property value COP of the material property, the diameter of the item for which the material property is set to COP is automatically set to 1000 PHI.

On the other hand, the item catalog is classified into a standard product and a non-standard product and registered, and if the item catalog is a non-standard product, it is possible to input a property value other than the property candidate value of the item catalog under item creation conditions. In particular, if there is an item catalog of a standard product that searches for an item catalog of a standard product that satisfies all of the item generating conditions created by the non-standard product catalog, the item generating condition is set to an item generating condition of the item catalog of the standard product.

When the item catalog is registered as a standard product, as described above, the item can select attribute values only within the registered item catalog and its creation condition. That is, when registered as a non-standard product, a preset value or relationship may be selected within an item catalog or a condition for generating the item, or newly generated attribute values may be freely input. In addition, the item code of the standard product is specified and generated according to the attribute value, but the item code of the non-standard product differs from the attribute value in that it is changed in the generation order and the item code is generated.

At this time, when one item is generated as a non-standard product, the reference information system 30 searches whether there is an item catalog or a creation condition of the standard product satisfying the attribute values of the item and their relationship. If it is found, it is registered as the item catalog of the searched standard item or the item of creation condition.

Next, the PLM and ERP integration reference information generation system according to an embodiment of the present invention will be described in more detail with reference to FIG. 7.

The reference information generation system 30 is the same as the reference information system 30 described above.

As shown in FIG. 7, the reference information generation system 30 according to an embodiment of the present invention includes a catalog register 31 and a generation condition definition unit 32.

The catalog registration unit 31 registers an item catalog, but inputs a plurality of physical properties and a physical property value (hereinafter, physical property candidate value) to have a plurality of physical properties in the item catalog.

In particular, the catalog registration unit 31 may set the relationship between the property candidate values of different physical properties in the item catalog.

The generation condition definition unit 32 calls up an item catalog and defines an item generation condition, selects a property value from among property candidate values of the catalog, and sets a relationship between property values of different properties. In particular, when the generation condition defining unit 32 sets one physical property (hereinafter referred to as a first physical property) to another physical property (hereinafter referred to as a second physical property), all properties of the second physical property belong to the first physical property. Select a property value to set the relationship (hereinafter referred to as individual relationship).

On the other hand, the item catalog is classified into a standard product and a non-standard product and registered, and if the item catalog is a non-standard product, it is possible to input a property value other than the property candidate value of the item catalog under item creation conditions.

A description omitted from the reference information generating system 30 refers to the reference information generating method described above.

As mentioned above, although the invention made by this inventor was demonstrated concretely according to the said Example, this invention is not limited to the said Example and can be variously changed in the range which does not deviate from the summary.

10: PLM system 20: ERP system
30: reference information system 31: catalog register
32: generation condition definition unit
40: Database 41: Catalog DB
42: reference information DB

Claims (12)

In the method for generating PLM and ERP integrated reference information defining items in a product lifecycle management (PLM) system and an enterprise resource planning (ERP) system according to item creation conditions of the reference information system,
(a) the reference information system registering an item catalog, and inputting property values (hereinafter, property candidate values) that may have a plurality of properties and the properties in the item catalog;
(b) the reference information system importing the item catalog to define item creation conditions, selecting property values from among property candidate values of the catalog, and setting relationships between property values of different properties; And
(c) the PLM or ERP system, wherein the item is defined by a property value, the property value of the item comprising the step of defining so as to satisfy the conditions for generating the item.
The method of claim 1,
In the step (a), it is possible to set the relationship between the property candidate values of different properties in the item catalog, PLM and ERP integrated reference information generation method characterized in that.
The method of claim 1,
In the step (b), when one property (hereinafter referred to as the first property) is set to another property (hereinafter referred to as second property), the property values of the second property are selected for all property values belonging to the first property. PLM and ERP integrated reference information generation method, characterized in that for establishing a relationship (hereinafter referred to as individual relationship).
The method of claim 3,
In the step (b), if none of the physical property values of the second physical property is selected for the physical property values of the first physical property, it is determined that all the physical property values of the second physical property are selected. .
The method of claim 3,
In the step (c), if the property (hereinafter, the corresponding property) of the item creation condition has one property value (hereinafter, the corresponding property value), the corresponding property of the item is automatically set to the corresponding property value, PLM and ERP How to create integrated baseline information.
The method of claim 1,
The item catalog is classified into a standard product and a non-standard product and registered, and when the item catalog is a non-standard product, property values other than the property candidate values of the item catalog can be input in the item creation condition. How to produce.
The method according to claim 6,
If the item catalog of the standard product is found by satisfying all of the item generating conditions created by the catalog of the non-standard product, and there is an item catalog of the standard product, the item generating condition is set to the item generating condition of the item catalog of the standard product. How to generate PLM and ERP integration criteria information.
A computer-readable recording medium having recorded thereon a program for executing the method for generating the PLM and ERP integrated reference information according to any one of claims 1 to 7.
In the PLM and ERP integrated reference information generation system that defines the conditions for creating items used in the PLM (Product Lifecycle Management) system and the Enterprise Resource Planning (ERP) system,
Registering an item catalog, the catalog registration unit for inputting a plurality of physical properties and property values (hereinafter, property candidates) that may have a plurality of physical properties in the item catalog; And
Importing the item catalog to define the item creation conditions, including a creation condition definition unit for selecting a property value from the property candidates of the catalog, and setting the relationship between the property values of different properties,
The item is defined by a property value, the property value of the item is PLM and ERP integrated reference information generation system, characterized in that it is defined to satisfy the creation conditions of the item.
10. The method of claim 9,
The catalog registration unit PLM and ERP integrated reference information generation system, characterized in that the relationship between the property candidate values of different properties in the item catalog.
10. The method of claim 9,
When the generation condition definition unit sets one property (hereinafter referred to as a first property) to another property (hereinafter referred to as a second property) as a relation, the property condition of the second property is selected for all property values belonging to the first property. PLM and ERP integrated reference information generation system, characterized in that for setting (hereinafter referred to as individual relationship).
10. The method of claim 9,
The item catalog is classified into a standard product and a non-standard product and registered, and when the item catalog is a non-standard product, property values other than the property candidate values of the item catalog can be input in the item creation condition. Generating system.

Images