With the VDI 3805 Wizard, manufacturers from the TGA sector can[26] (building services for heating systems, pipes, pumps, etc.) can import their VDI catalog with eCATALOGsolutions and create a PARTsolutions catalog, which is then made available on PARTcommunity portals. The download formats currently offered 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 large number of sheets. Details are available on request. 5
The following figure shows the current editing status[27] of data sheets.
The following describes how you can easily create your VDI catalog using the VDI Wizard.
Open the wizard in PARTproject in the project selection [Project selection] via the context menu under Automation -> VDI 3805 Wizard.
VDI file [VDI File]: Use Browse to specify the directory in which the VDI files to be imported are located.
PDT file [28]by specifying a PDT file, you can subsequently enrich the classification. To do this, select the Enrich classification [Enrich classification] option under Mode.
The classification data is displayed in PARTdataManager under part information [Part information].
Individual attributes in the PDT file can be provided with translations.
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:
#deu#Druckminderer#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.
The translation of individual attributes in the PDT file should only be used if a translation via the configuration file does not make sense. The configuration file (
CADENAS_USER/vdi/vdi3805import.cfg) is written the first time the VDI Wizard is run.Media directory (optional): If preview images (png format) are not provided, they are generated automatically (as with Quick & Simple or PLMsynchro).
Level of detail: Determine the level of detail (Low quality [Low Quality] | High quality [High Quality] | Both | None ).
This affects the quality and structure of the geometry to be imported. Both are set by default. Depending on how complex the data is, more data can be imported with Low quality [Low Quality] than with High quality [High Quality] (tolerances, accuracies, compatibility).
Mode: Determine the import mode:
Standard [Default]: Catalog creation by importing a VDI or PDT file (one of the two must be specified).
(Currently the creation of geometry is only possible via VDI file.)
Skip geometry: The same process as under "Standard", but when importing into existing catalogs, correct 3dbs cannot be overwritten under any circumstances (and no dummy.3db files are created and attached in the event of an error). The process also runs faster.
Enrich classification: With this option, values from an existing catalog can be written from a PDT file to the classification (which are then also displayed again in the part information [Part information] ).
Process settings [Processing settings] -> Conversion strategy:
Standard [Default]: An attempt is made to create a standard 3db file. If this fails, an attempt is made to write an STP file as a fallback (corresponds to Quick and Simple).
Feature-based: It only attempts to create a standard 3db file. This is intended as a premium path. It may not be possible to create some geometries, but the rest will be of the highest quality (3db). If you only want to create content quickly and easily, select Standard [Default] ).
Catalog name: The catalog name is automatically set to the catalog from which the wizard was started, but it can also be changed (.. , which then creates a new catalog or imports it into another catalog. If you start the wizard via the root node, the field is empty.
Catalog license: As with every catalog import, a license (if required) must be entered here:
CNS2009*CATALOGS*KATALOGNAME
-> 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 characteristics were entered under Classification (VDI 3805) or Characteristics (VDI 3805).
Open the VDI catalog in the PARTdataManager in the parts selection [Part selection].
Open a project in the PARTdataManager in the parts view [Part view].
All existing features were created and filled in the VDI 3805 classification, 3D view and line preview images were created automatically. If preview images were stored in the media directory [Media directory], these are used.
![[Note]](https://webapi.partcommunity.com/service/help/latest/pages/cn/3dfindit/doc/images/note.png)
Process files are initially created during the first run of the wizard under $CADENAS_USER/vdi are created.
<Date>_<Catalog name>.csv: CSV showing import state. Here, you can quickly detect, which files have been successfully supported and for which the import failed.
Structure: The configuration file is divided into blocks with the corresponding sheet number as the designation. For example, the information in block 20 is relevant for sheet 20.[29]
The sheet numbers are reflected in PARTproject and in PARTdataManager in the index structure.
The names of the folder structure in PARTdataManager are given according to the information in the "_NAME" key or stored translations.
Each block contains the following keys:
_PATH: The path to be imported.
By default, the sheet number is given first, followed by a higher-level product description and then a description of the individual product.
(Theoretically, most diverse attributes can be used in order to individually assemble an path with any depth.)
_NAME: The translation of the path. You can specify as many parts as are available under Path.
_PATH= $SA010ID02. / $SA100ID04. / $SA110ID04. _NAME= Heizungsarmaturen / Ordner1/ Unterordner1
In this example, the folder is internally named according to the value under $SA100ID04., but the user would see "Folder1".
Normally only the translation for the sheet number is stated, so that the folder would not be named with "2" according to the sheet number, but with "Heating fittings".
Sheet catalogs built in this way will be compatibly synchronized during a new import/update. Other sub-structures may not be created manually in order for updates to be working.
You can explicitly determine the variables' sort sequence as is should then be displayed in the characteristic attribute table.
[20] _PATH=$SA010ID02./$SA100ID04./$SA110ID04. _NAME=Speicher und Durchlauferhitzer _SORT=SA010ID04,SA010ID03,SA010ID05 SA010ID03={"desc":{"deu":"Ausgabedatum (Monat) der Richtlinie","eng":"Issue date (month) ... SA010ID04={"desc":{"deu":"Herstellername","eng":"Manufacturer’s name"}} SA010ID05={"desc":{"deu":"Revisionsdatum der Datei","eng":"Revision data of the file"}} #SA010ID06={"desc":{"deu":"Webadresse des Herstellers","eng":"Manufacturer’s web address"}} #SA010ID07={"desc":{"deu":"Kommentarfeld","eng":"Comment"}}
[20] _PATH=$SA010ID02./$SA100ID04./$SA110ID04. _NAME=Speicher und Durchlauferhitzer _SORT=SA010ID05,SA010ID04,SA010ID03 SA010ID03={"desc":{"deu":"Ausgabedatum (Monat) der Richtlinie","eng":"Issue date (month) ... SA010ID04={"desc":{"deu":"Herstellername","eng":"Manufacturer’s name"}} SA010ID05={"desc":{"deu":"Revisionsdatum der Datei","eng":"Revision data of the file"}} #SA010ID06={"desc":{"deu":"Webadresse des Herstellers","eng":"Manufacturer’s web address"}} #SA010ID07={"desc":{"deu":"Kommentarfeld","eng":"Comment"}}
In each block there is a listing of the single variables (attributes). Attributes, which should not be visible can be commented out by "#".
Here, optionally translations can be saved.
text;deu;eng
The .pwp file is an XML file with all pipeline settings. You can open it with PARTdataCenter or the pipe editor.
By selecting individual nodes, you have access to a wide range of settings in the node editor. After making changes, save the file and run the wizard again.
Settings in the node PARTsolutionsExporter:
Order number: Manufacturer order number is entered by default.
NB (standard description): Default value is "$HERSTELLER_BESTELLNUMMER. ($LOD.)".
This value can be adjusted. If a part has an LOD (yellow field), the LOD must be entered in the NB.
LINA (parts list designation): Default value is "$HERSTELLER_BESTELLNUMMER."
![[Tip]](https://webapi.partcommunity.com/service/help/latest/pages/cn/3dfindit/doc/images/tip.png)
Standard eCATALOGsolutions/PARTprojectSystem requirements. See Chapter 2, System requirements in Installation Manual.
[26] Technical building equipment
[27] https://www.vdi.de/fileadmin/vdi_de/redakteur_dateien/gbg_dateien/VDI_3805_Bearbeitungsstand-05-21-2015.pdf
[28] A Product Data Template (PDT) is a machine-readable template that is used to structure information in the form of characteristics for any type of building object and make it interchangeable.
[29] The sheet numbers can also be found at the very beginning of the VDI or PDT file.
See the following example of a VDI file:
010;20;200602;Company 08/2015;20150810;Company.de;Armaturen aus Rotguss undEdelstahl, Revision by www.....de, Stand 01/2015;;;;;;DEU;DE; 100;5;5;Durchflusstrinkwassererwärmer;;;20120405; 110;1;1;Heizwasser;;;20120405; 200;4;nicht rostender Stahl; 300;3;wandhängend; 400;1;Geschlossen/druckfest; 450;1;monovalent;