Community Tip - When posting, your subject should be specific and summarize your question. Here are some additional tips on asking a great question. X
Hi,
I would like to know the differences between PDMLINK and MPMLINK
I have been told MPMLINK is a layer above PDMLINK, but i am not sure
regards
Laurent
PDMLink is for the design engineering department as it captures the parts, assemblies and drawings needed to manufacture a part. It also includes change management for capturing incidents, problems and change requests that may drive a part to a revision.
MPMLink is the manufacturing side for the part. Once released by PDMLink, it can be planned for its manufacture on the shop floor. With assemblies, the engineering eBOM is not always the way the parts are assemblied. MPMLink provides you a method of creating a mBOM for the process flow that the shop uses.
In order to use MPMLink, you must have PDMLink installed.
Yes . MPMLink is the manufacturing addon to PDMLink:
-Tools to create/maintain equivalent mBOMs from an eBOM
-Tools to create Process Plan (ie Routings) which consume the mBOMs and associated Tooling, Skills, Workcenters etc ...
-Tools to document and automatically generate Work Instructions from the Process Plan with CAD 3D models
-Tools to integrate CAM files with Process plan's Operations
-Tools to integrate CAD models for Quality Control Characteristics definition
Laurent,
MPMLink is an optional add-on to PDMLink. In true PLM-centric systems / operations, it provides a logical gateway between ERP systems as well as what is known as Manufacturing Execution Systems (MES). Many companies either do not have a budget to purchase these products, use alternative platforms, custom software, or feel they can survive without them. However, a lot of companies just do not grasp this segment of the PLM 360 degree circle.
The best way to visualize how MPM fits into the cycle is to cite software application development. Software is made of subcomponents so you do not have to reproduce all functionality every time. The software is typically manufactured ( written ) to adhere to quality standards and perhaps segments are produced by multiple teams, multiple vendors, and operates on a certain set of explicit components: Smartphones, Desktop computers, Data centers, etc.
When the software is developed, it is also typically packaged, shipped, and requires patches or updates.
PTC's product Integrity addresses some of this, but the reason I mention this is because of Application Lifecycle management, it is a subset of Product Lifecycle Management. Product data Management (PDM) inside PDMLink is also just one of many subset, phases, or component of PLM. ALM now commonly interchanged with a word called DevOps is short for Development Operations. The idea is during engineering, manufacturing, and operations, a continuous integration and flow of information occurs which permits a feedback mechanism to build a better product.
If in the physical product, equipment, hardware world, MPMLink allows you manufacturing management to plan the assembly line like process step-by-step. In doing so, MES, can receive the plans and execute them as tasks. Think Microsoft Project for planning and execution of the project according to that defined project plan. The planning challenges assumptions, inventory constraints, licensed and skilled employees, and even better: the means for manufacturing engineering to inquire with the upfront mechanical, electrical, and software engineering should they design a part or sub-assembly that is inefficient to manufacture, low in supply, time consuming, or too expensive. They also challenge on molds for plastic, metals, etc. that are used to make or cut out appropriate shaped parts. These parts for molds are NOT in the EBOM, but would show up in the MBOM and what MPMLink denotes as the "Process Plan". The MBOM may call for adhesive, paint colors (think cars, furniture), casting molds, work instructions (best practices, internal standard operating procedures), other relevant documentation. That way when you view an exploded Manufacturing Bill of Materials (MBOM) inside MPMLink, you know what is required to actually perform the manufacturing of something. Quality, supply chain, and purchasing are also able to be synchronized this way although classically some places have opted to step through ERP systems to handle this. It is not that this is wrong, it is just more difficult to shift between an Engineer Bill of Material and Manufacturing Bill of Material as well as views such as: As-designed, As-built, As-packaged, As-shipped.
Speaking with those who have trained or received college degrees in industrial engineering certainly can help explain this even more.
This picture best depicts how MPM fits into the picture:
The picture above is courtesy of an article AutomationWorld. URL to article follows below:
Connecting MES and PLM | Automation World
Note that similar operations for DevOps / software engineering can be seen here courtesy of Hewlett Packard:
Left to Right:
Circle 1: Development / Engineering
Circle 2: Manufacturing Planning, Execution, Resource Management, and QA
Circle 3: Aftermarket, Shipped, Purchased, Installed/Deployed - Feedback from customers, recalls, defects, sales, replacement parts
Personally, having used MPMLink, I highly recommend it, but it can be hard to sell management stuck in its ways.
Feel free (anybody) who wants more information to respond with follow up questions to contact me direct or reply here.
Ok thank you very much
laurent