We used it for several years before going to PDM about 10 years ago. At that time, it (SAP) certainly in not as user friendly as PDM (it may have changed since we used it). However, it was convenient that both the PDM and ERP systems were combined. Hopefully your CEO will allow for due diligence and not just go with his gut because some other CEO told him it was the way to go (every business is differnt).
PDM, PLM, MRP, ERP they are all different even though there are some overlapping features which vary from vendor to vendor.The bottom line is that there's no one solution that DOES IT ALL, especially if you plan to tie in CAD File management. Try to explain that SolidWorks is relational in nature; one cannot simple upload SW files into a system with out impacting integrity and/or productivity. Contact your VAR, they surely have some Case Studies on why PDM is beneficial in addition to ERP or any other Business System.
Hi Solid Air
Thanks for your reply...
So you used Solidworks 200? and managed the CAD data only by SAP 10 years ago?
Why did you switched to the PDM then?
Could you handle fairly efficient not only the basic functions like:
> copying assemblies, with subassemblies and subparts including its drawings in one batch?
> renaming existent files?
> replacing files?
But as well the more complex functions like:
> modification process:
modifications on parts /assemblies (what happens to all released asseblies with this part included?) and there history?
> dynamic favorit folders / saved search folders...
> copying an existing drawing and substitue its associated 3D-model to another one with a following "save as"?
Sorry for so many questions
In the good old days, it may have made sense to leave the responsibility of PLM/PDM/CAD data to an ERP system.
However, it has always been a quirky process, mainly because product data is meant to flow naturally downstream from engineering (PDM/CAD) to manufacturing (ERP), not the opposite.
However, now that there are state-of-the-art PLM PDM CAD to ERP integration solutions that can bidirectionally integrate product data, it really makes very little sense to use that strategy any longer.
This may sound a bit self-serving, but we know from experience that an increasing number of ETO manufacturers tend to trust PDM systems for PDM, for excellent reasons.
I bet your CEO is not engineer ;-)
Hope this helps,
Product data management (PDM) or Product information management (PIM) is the business function often within product lifecycle management (PLM) that is responsible for the management and publication of product data. The goals of product data management include ensuring all stakeholders share a common understanding, that confusion during the execution of the processes is minimized, and that the highest standards of quality controls are maintained.
PDM can also be used in SAP Module. With the help of SAP Training you can easily work in SAP software which consist SAP MM, SAP ERP and SAP CO Modules that will helps to work in PDM as well. If you want to gain knowledge and skills then you can join sap training course in noida.
Although PDM is part of PLM, it does not mean that both domains have the same scope. While PLM usually has an enterprise-range audience, in most organizations, PDM is contained within the engineering (especially its file storage component) and occasionally, manufacturing departments.
That is why it usually makes sense to keep PDM outside of the ERP system, while maintaining PLM functionality within the ERP system.