My ideas about PDM etc are now a bit old and out of date. Requirements on handling of graphics and the way this have to be integrated in the documentation of what has been developed during the Product Engineering process has changed a lot during the last 20 years or so. However, some of my ideas may still be useful.
My intentions was:
Besides being a personal site for me, this is a site where I try to share my Personal Experience with PDM, LCM and PLM and focus on some important PDM functionality.
I base this information on my perception on how a Globally Extended Enterprise, developing, manufacturing, selling and servicing configurable, complex Mechatronics Products should go about handling PDM information regarding information capture, information storage and accessibility to this .
I assume that some of you will already have some idea about why you need PDM (or LCM or PLM).
However, I will try to explain some aspects of what a good PDM application should do and a little about how and why.
I will also try to explain why you need to write down your own Requirements Specification for your PDM application. Do not outsource this to a vendor!
I do not
- present or evaluate any PDM/PLM Vendors and their products.
- present any news from the PDM/PLM Industry.
- provide any reason for why you and your company should have PDM/PLM, since this is very well done by John Stark:
Why do PDM?
So, what is PDM/LCM/PLM?
When you develop a product, you need to document it in order to know what you have developed and to make it possible for others to manufacture the product and market and sell the product etc. So, Product Documentation is a mandatory requirement! Since the documentation of a large, complex product is immense and that the documentation is growing over a considerable time, it will be necessary to also have some rules and standards that controls the way the documentation should be done and what it should look like. This is the management part of it. Hence, PDM.
LCM assumes that you will need and will have PDM. LCM or PLM is the more geared towards the life cycle of the Product Documentation and the life cycle of the Product: continuous further development through Engineering Change Orders and the development of new versions, adding new features and properties etc. and the management of this process.
How to read my descriptions?
The chapter Preconditions explains something about the Processes involved in PDM/LCM and what is meant by an Extended Enterprise. There is also something about Information Objects and Interfaces between Applications and Databases and who should ”own” these. I also present a list of some terms used in PDM Terminology. PDM as it is used in this website may encompass any buzz word for the phenomenon of documenting and managing the information created during the Product Development Process as defined under Processes on this site, including BoM, PIM, PLM, ERP, etc. Most vendors have adopted Product Lifecycle Management or PLM as a more comprehensive replacement for PDM. However, I persistently call it PDM since LCM involves processes. But be aware of the fact that PDM information frequently are being used in other processes than the Product Development Process and that the Product Development Process covers Product Engineering, Manufacturing Engineering, parts of Purchasing and even parts of Customer Support (or After Market) etc.
I hope the information found on Isene PDM Home will be of some use to you.
I do not ask for any compensation other than stated in the disclaimer below.
However, should you like my way of seeing PDM, do not hesitate to contact me.
I would be very pleased if some of you guys that read my advices on PDM and find them useful, would tell me.
I’m clearly out of circulation with regards to the subject of PDM/LCM or any new acronym in this area. But, it would still be very nice to know whether my thoughts were sound or just rubbish.
Use my email address: email@example.com and let me know!