Manual
Login
Top Links
Manual
 |
With the help of VDI 3805 importer, manufactures from the TGA field [35] (building services for heatings, pipes, pumps, etc.) can import their VDI catalog and create a PARTsolutions catalog, which then can be provided on PARTcommunity portals. Provided download formats currently are the neutral formats STEP/IGES (3D) and DWG/DXF (2D).
Geometry and meta data specific to certain sheets are imported.
Currently only the import of static data is supported.
Data can be updated constantly.
VDI 3805 controls product data exchange in the TGA by different data sheets. Each sheet defines a specific product range with details on all attributes and detailed product descriptions.
PARTsolutions supports a range of sheets. Details on this are available on request.
The following figure shows the current editing status[36] of data sheets.
In the following you can find a description on how to simply create your own VDI catalog with the help of the VDI Wizard.
-
Open the Wizard in PARTproject, in the Project selection via context menu under Automation -> VDI 3805 Wizard.
-
VDI File: Determine the directory of the VDI files to be imported via search button .
-
PDT file [37]: When specifying a PDT file you can enrich the classification subsequently. For this, under Mode, select the option Enrich classification.
Classification data is shown in PARTdataManager under Part information.
Single attributes in the PDT file can also be translated.
If you have "Pressure reducer" in the attribute SA100ID04 and want to translate this term, the entry in the Excel file (PDT file) looks like this:
#gbr#Pressure reducer#fra#Réducteur de pression#ita#Riduttori di pressione
The country code has to be according to ISO 3166 ALPHA-3 and the values have to be stated in one line.
Translating of single attributes in the PDT file should only be used if translating via configuration file doesn't make sense. The configuration file (
CADENAS_USER/vdi/vdi3805import.cfg) is written in the first run of the VDI Wizard.Media directory (optionally): If no preview images (png format) are provided, they will be automatically generated (as with Quick & Simple or PLMsynchro as well).
-
Level of detail: Determine the level of detail (Low Quality | High Quality | Both | None).
This concerns quality and structure of geometry to be imported. Default is Both. Depending on how complex data are, with Low Quality more data can be imported as with High Quality (tolerances, accuracy, compatibility).
-
Mode: Determine the import mode:
-
Default: Catalog creation by importing a VDI or PDT file (one of the two has to be specified).
(Currently the creation of geometry is only possible via VDI file.)
-
Enrich classification: With this option, values of a PDT file can be written into the classification of an already existing catalog, (which then are also shown in the Part information.
-
-
Processing settings –> Conversion strategy:
Default: An attempt is made to create a standard 3db file. If this fails an attempt is made to write a STP file as fallback (corresponds to Quick and Simple).
Feature-based: There is only an attempt to create standard 3db files. This is meant as premium method. Possibly same geometries cannot be created, the rest however, is of the highest quality (3db). If the scope is on just producing content, select Default).
-
Catalog name: Catalog name is automatically set on that catalog where the Wizard had been started from, however, it can be changed (), whereby a new catalog is created or the import goes into another catalog. If the Wizard started on the root node the field remains empty.
-
Catalog license: As usual when importing a catalog a license has to be inserted, if required:
CNS2009*CATALOGS*CATALOGNAME
-
-> The import and the catalog creation are started. Depending on size of source file and chosen settings (preview images, LOD) this may last some minutes or hours.
-> Classes and features have been inserted under Classification (VDI 3805) or Attributes (VDI 3805).
-
Open the VDI catalog in PARTdataManager, in the Part selection.
-
Open a project in PARTdataManager, in the Part view.
All existing attributes have been applied and filled in the Classification VDI 3805, 3D view and line preview images have been automatically created. If preview images had been stored in the Media directory these are used.
![[Note]](/community/externals/manuals/ecatalogsolutions_en/v11/images/note.png)
Process files are initially created during first start of the Wizard in CADENAS-User directory ($CADENAS_USER/vdi).
-
CSV showing import state: Here, you can quickly detect, which files have been successfully supported and for which the import failed.
-
Beside import paths also those attributes can be configured, which should be visible in the catalog.
[2] Path=$Blatt./$Armaturenart./$Armaturen-Typbezeichnung. Name=$Blatt Beschreibung. - $Blatt. [3] Path=$Blatt./$Bauart des Wärmeerzeugers./$Feuerungsart. Name=$Blatt Beschreibung. - $Blatt. [4] Path=$Blatt./$Produktbezeichnung./$Armaturen-Typbezeichnung. Name=$Blatt Beschreibung. - $Blatt. [5] Path=$Blatt./$Durchlasstyp./$Durchlassserie. Name=$Blatt Beschreibung. - $Blatt. etc.
When building the catalog structure, the sheet number is created as directory below the catalog name during import. These sheet catalogs will also be compatibly synchronized when importing/updating again. Further sub-structures may not be created manually, in order for updates to be properly working.
<chosen catalog name> o 17 O 20
-
Here, optionally translations can be saved.
text;deu;eng
-
The .pwp file is a XML file with all pipeline settings. You can open it with PARTdataCenter or the Pipe editor.
By selecting individual nodes in the Node Editor, you can access multiple settings. After changes save the file and execute the Wizard again.
Standard eCATALOGsolutions/PARTproject system requirements. See Chapter 2, System requirements in Installation Manual.
[35] Technical building services
[36] https://www.vdi.de/fileadmin/vdi_de/redakteur_dateien/gbg_dateien/VDI_3805_Bearbeitungsstand-05-21-2015.pdf
[37] A Product Data Template (PDT) is a machine-readable template, which serves to structure information in the form of attributes for any kind of objects in the building sector and make it exchangeable.
