Manufacturing based PLM Enterprise Informationization (E-based)
preface
Intense market competition, entrepreneurs have made the pursuit of the pursuit of product profits, the most common method, and use information method management to achieve the best reason to improve the product cycle. However, as shown in the current authority survey, companies successfully implemented E-chemical companies less than 30%, why? After years of experience, the author has drawn:
1. E chemical should be carried out based on the life cycle of the product.
2. Implemented the implementation of the product characteristics.
3. It should be based on long-term strategic improvement, don't hurt, hand pain, hand pain.
What is PLM?
Since PLM is a very fast, a new information field, she is not a tool, is a kind of ideology, and some consulting companies in this area, manufacturers have some different insights, so There is no recognized definition of PLM. Here I lists I prefer the interpretation method (other can enter from the links), PLM is overwriting from the product lifecycle, open, interoperable application solutions. The key to building such an enterprise information environment is that there must be a record of all product information, systematic central product data knowledge base. This knowledge base is used to protect data, implement task-based access (eg, frequently used three-dimensional performance) and use a collaborative platform to share applications, data, and implement data accesses all firewalls. The role of PLM can be covered to a product from concept, manufacturing, and use until every part of the scrap.
Related PLM consulting company website
Aberdeen
http://www.aberdeen.com
Cimdata http://www.cimdata.com
Collaborative Visions http://www.collaborativevisions.com/
AMR http: // www.amrresearch.com.com
EDS http://www.eds.com
Glossary
PLM: Product lifecycle http://www.pdmin.com/
PDM: Product Data Management http://www.pdmic.com/
ERP:
Enterprise
Resource Planning. Http://erp.ittoolbox.com/
CRM: Customer Relationship Management http://crm.ittlebox.com/
SCM: Supply Chain Management http://supplychain.ittoolbox.com/
Manufacturing PLM E-vertical chain
PDM ----------> ERP ----------> CRM --------> (r) PDM ----------> ( R) ERP -----------> (r) CRM
This is a loop repeated process and is also called continuous improvement. This is the simplest life cycle that the product must pass. Now explain the product life cycle of the system:
PDM (Product Data Management): Product Data Management (PDM is not a Physical Data Model), the key management product-related properties, management is the development phase of the product, including product formulation, structure, manufacturing instructions, product version Record, etc..
ERP (Enterprise Resource Planning): Product Manufacturing Information Management, focusing on managing reasonable configuration of various links. The focus is in the manufacturing stage, including material amount statistics, material demand procurement, production site control, financial management, shipping management, etc. Introduced SCM focus in the later ERP system is to resolve resources.
CRM (Customer Relationship Management): Customer Relationship Management, Key Management Products After selling to the market, customers reply, complaints, including customers, product satisfaction management, product market analysis, and more. Let's talk about the E-vertical chain, of course, can also be deployed according to the level of the enterprise E-based information system, such as OA, KM, EKP, EIP, etc.
System interface
Above we have talked about each system, we discussed how to achieve inter-system joints from the perspective of technology, of course, different manufacturers have different software, interface mode.
Three most common interface methods
1. Passive: The system needs to be read when the system needs to be required.
2. Active: That is, the data source system actively writes the data to the system that needs to be read.
3. Independent: That is, the data source system writes the data into an intermediate data (XML), then the demand data system reads the intermediate data.
These three ways have advantages and disadvantages, and the first two ways are more suitable for their own development systems, but they all need to write or read permissions, which is unfavorable to the database, but these two ways data consistent Sexual stays very well. In the third way, it is not necessary to read and write permissions between databases, which is convenient for the management of the database, but the consistency of data is often not good. Here I am more advocated in the third way.
System distribution
PDM is mainly distributed inside the plant.
ERP is mainly distributed within the factory.
SCM is distributed in all customer groups.
Synchronize with industry systems
Everyone may have such experiences, and the system you are now developing needs to be diverted with old systems or other systems, always generates differences on the data interface. The source of the root is that there is no use of standard interfaces, and there is no reserved interface when designing the system. Then how should I deal with the PLM thinking to solve the interface of the manufacturing E-based system?
First of all, we have two interfaces, PDM to ERP, ERP to CRM, most friends may think of the employee single number. PLM is based on product lifecycle completion of enterprise E-based construction, so I am talking about using the product structure, the BOM method. This method has the following good
1. Directly, the product structure changes in the PDM phase, and other phases are unaffected (because other stages are passive).
2. The product structure is clear in various stages.
3. The system is more flexible.
BOM in each stage
1. The manufacturing of the PDM development BOM to ERP is single-to-list.
2. ERP manufacturing BOM to CRM market BOM is single.
We now use practical issues to discuss product structure changes, changes in the PLM systems.
Question: Nike has a product NIKE_S001, ERP has issued a plan for NIKE_S001 products and is being produced and purchased, but Nike wants to change the NIKE_S001 BOM structure, then how should our PLM's E-based E-based E-system?
Do you have any analysis, in fact, this problem can be set with our previous vertical e-chain chain
PDM ----------> ERP ----------> CRM --------> (r) PDM ----------> ( R) ERP -----------> (r) CRM
ERP adjustment
The change of the product BOM is actually the R-PDM, which will generate the difference BOM, you can also call it for different versions (if you call different versions, there will be more troubles). If we use the above mode, we can do this, design PDM is available for multiple releases, that is, first publishing the main procurement and manufacturing pieces, and then ERP production (I will not talk about it here); then design, PDM is released again (in fact, the structure is changed, but we don't call), and then ERP is subjected to the difference BOM according to PDM, and it is repeated until it is completed. Here, it will be described here. Perhaps per release may only be supplemented throughout the product BOM, rather than letters (very emphasized this) b. We have canceled, produced, produced, warehousing (Because I have previously released a component of the product BOM, not the entire BOM), of course, product changes are definitely a change, if the product is changed, it is not called product changes, it should be called the product refurbishment, so the component changes, There is also a part of the components to scrap (for this product, not usually scrapped). So next, we can open a new work order, produce a component of a change (again, not the entire BOM, but a BOM one).
CRM adjustment
Connected, if the product is changed, there is no need to generate new product coding. Of course, the old code is extended. If new encoding is generated, we only need to make BOM to generate more than one CRM.
We have the focus here that the BOM is just a component of the BOM, not the entire BOM, so when the product structure changes, it is only supplemented by the original product structure, not the wrong.
Because the author is limited, the manuscript is wrong, please correct it, thank you
Victor
May 17, 2004
Lizhongde808@hotmail.com
