Based on the following tabular comparison the difference in the use of PARTsolutions with or without PDM linking is made clear:
Total integration with PDM linking[a] | ||
|
Automatic transfer of meta information (manufacturer designations, standard designations, ERP numbers, material information) and automatic classification in PDM. The geometry document immediately arrives in CAD as a validly managed PDM standard part / purchased part. The status (e.g. released and unchangeable) is also always correct. Meta information is entered in the corresponding fields of the PDM system during creation. The parts list and the where-used list are correct. Important: This happens in the background - without the CAD user needing to know the details!
| |
Restricted write-protection on all parts. An engineer could have accidentally modified a part. All colleagues receive this modified part directly from PARTsolutions without noticing. | The part comes as a modified PDM standard / supplier part into the CAD and is thus also write protected. | |
The parts in the pool are installed multiple times. However, deletion of the parts is not prevented. If they are accidentally deleted, old assemblies are probably damaged (without knowing which ones, as there is no where-used list). Even recreating the part can only restore the assemblies in a few CAD systems, as the surface and part IDs have changed, which means that the installation relationships are lost. This makes a separate backup of the pool necessary. |
Safety from accidental deletion of files from the general pool. Respectively no special solution for the replication and securing of the pool data necessary. A global pool no longer exists. The parts are created in the user area and automatically directly checked into the PDM by PARTsolutions. The local workspace can and should be regularly deleted. During new parts selection in PARTsolutions (or for selection on a different work station) the part is copied from the PDM safe. Since the safe is backed up anyway, nothing must be done concerning data backup. | |
Every time an assembly is opened, all standard and supplier parts are loaded into the main storage pool of the CAD via the network. |
Performance improvement of assemblies through minimal network load. You only have to wait when checking the assembly in and out of the vault into the local working folder once. All standard and purchased parts are now also copied. Work is carried out locally while the assembly is being worked on. | |
PARTsolutions is not integrated in the PDM processes, in other words erroneous special processes must be defined for the manual work of the engineers, which are usually difficult to handle and error-ridden. |
PARTsolutions always delivers parts "fresh" from the PDM. It makes no difference whether the standard part came from PARTsolutions or from an old assembly in the PDM. The processes are continuous. PARTsolutions geometries are not an exception. By passing on of ERP information, no manual additional work is necessary. PARTsolutions is "seamlessly" integrated between ERP and PDM as a supplier of standard, manufactured, and repeat parts. With ERP and PDM integration from PARTsolutions, there are no "process gaps" and no special handling is required for standard, purchased and repeat parts in the normal handling of CAD data. | |
[a] Refers mainly to PDM interfaces with "direct PDM linking" (PARTsolutions actively checks in/out; ex. for: CIM database, PRO.FILE, SAP-PLM, SmarTeam, Vault, ...). With "indirect PDM linking" some things count only limited (attribute allocation occurs directly via the CAD file; ex. for: PDM9000, ProfiDB, DBWorks, ...). |