The following tabular comparison clearly shows the difference in handling ENTERPRISE 3Dfindit with and without PDM coupling:
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 parts. A designer could inadvertently modify a part. All colleagues receive this modified part from 3Dfindit without realizing it. | 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's area and automatically checked into the PDM by 3Dfindit immediately afterwards. The local workspace can and should be deleted regularly. When the part is selected again in 3Dfindit (or when selected on another workspace), the part is copied from the PDM vault. As the vault is backed up anyway, nothing else needs to be considered in terms of 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. | |
3Dfindit is not integrated into the PDM processes, or error-prone special processes have to be defined for the manual work of the designers, which are generally difficult to handle and error-prone. |
3Dfindit always delivers parts "fresh" from the PDM. It makes no difference whether the standard part came via 3Dfindit or from an old PDM assembly. The processes are consistent. 3Dfindit geometries are no exception. No manual reworking is necessary thanks to the transfer of ERP information. 3Dfindit is "seamlessly" integrated between ERP and PDM as a supplier for standard, purchased and repeat parts. With ERP and PDM integration from 3Dfindit, there are no " process gaps" and no need for special handling of standard, purchased and repeat parts in the normal handling of CAD data. | |
[a] Primarily refers to PDM interfaces with "Direct PDM Coupling" (3Dfindit actively checks in and out; e.g. with: CIM-Database, PRO.FILE, SAP-PLM, SmarTeam, Vault, ...). With "Indirect PDM links", some things only apply to a limited extent (attribute transfer takes place indirectly via the CAD file; e.g. with: PDM9000, ProfiDB, DBWorks, ...). |