Home / FAQs / Enterprise management system selection, implementation and integration
QUESTION & ANSWER

PLM vs. MES System Difference

PLM manages product definitions and life cycles, including BOM, drawings, documents, process preparation, version and design changes; MES manages on-site execution, including worksheets, reporters, quality, products in production and traceability. PLM answers which approved version should be produced, and MES records how it is produced on-site.

Answer the question.

First, give conclusions that can be used for decision-making

PLM and MES address different stages of problems without replacing each other. PLM/PDM is given priority in the frequent and graphic BOM chaos; MES is given priority in the execution of production and in the retroactive out-of-control.

DECISION FACTORS

What conditions need to be identified before judgement is made?

The same question may have different answers under different business, data and project phases. It is suggested that the following conditions be checked and that the common findings on the web be incorporated into their own projects.

Complexity of product structure, drawings and design changesWhether or not there is a need for work orders, reports, quality and traceability at the siteWhich system to approve and which process to publishHow ERP, PLM and MES interfaces and versions are managed and validated
ACTION STEPS

Suggested order of advance

01

First, we'll be clear about the target and the border.

Select a real product recovery design to the production process.

02

Validation Key Dependence

Identify the data responsibilities of products, BOM, processes and worksheets.

03

Development of assessable outcomes

Verify how a design change is passed and is effective.

04

Make sure you decide the next step with the real results.

Production and retrospective results feed back R & D and processes.

PRACTICAL EXAMPLE

How do you understand it in the actual business?

Example used to illustrate the method of judgement

The project cannot simply add interfaces, but also defines the effective date, processing of the worksheet, validation of the version, and retreat, thus avoiding on-site mixing. The examples do not represent the performance of a particular client, and the actual conclusions need to be verified in conjunction with the enterprise’s own business volume, sample, system, and liability boundaries.

COMMON RISKS

The easiest pit to step on.

Getting PLM to a normal disk.

BOM can be modified at any time in PLM, ERP and MES.

Interface only synchronizes with the latest version, not processing products in progress and historical traceability

ACCEPTANCE

How should we end up receiving and confirming?

The use of real products to validate BOM, drawings, processes, change approval, release of versions, worksheet references and site retroactives ensures that history and current versions are restored.

When preparing to communicate with suppliers or internal teams, it is recommended that current processes, representative samples, existing systems, planning time and budget levels be brought. First, the unknown items are clearly marked, and then the decision is made to use diagnostics, PoC, fixed-range projects or ongoing research and development, which is usually more reliable than a direct demand for a price and duration without borders.

Your project conditions are different from the examples above?

Operational objectives, existing systems, sample and planned time could be collated before consultants could make preliminary judgements in relation to actual boundaries.

Associate project consultants