For the mapping from VDI 3805 attributes there are shared parameters prepared in the ifrevit.cfg. The attributes are already structured after VDI sheet categories.

So if certain class attributes are assigned to variables/values in the VDI classification, they are automatically transferred to Revit's Shared Parameters.

Each category initially starts with 3 lines:

[ClassMapping(hasClass(vdi3805,017-010)):include(ClassMapping)]
Mapping100=revit,RVT_SHARED_PARAMETER_FILES,RVT_SPF_PATH,?"$CADENAS_DATA\\datasetup\\
 classsystem\\vdi3805\\spf\\vdi3805_017_$CADENAS_LANGUAGE.txt"
Mapping101=revit,RVT_SHARED_PARAMETER_FILES,RVT_SPF_CLASSNAME,?"vdi3805_spf,vdi3805_spf_feat"
Mapping102=revit,RVT_SHARED_PARAMETER_FILES,RVT_SPF_PROPERTYGROUP,?"<PG_MECHANICAL>"

The output in the rfa files is only working if the needed VDI 3805 classification is available on the client which generates the rfa files.

The mapping is performed on the fly depending on the settings in the configuration file ifrevit.cfg during the rfa file is generated.

Because the mapping of the shared parameters is done in the ifrevit.cfg we don't need a shared parameter classification for VDI3805.

The required GUIDs are automatically generated.