4.1. Filling « AIA EDITOR »

A. Upload files

  • Load the files, to be done at each start of Revit, tab Ekkodale Suite>AIA Editor Settings :
    • At each phase, it will be necessary to load the settings file related to the current phase, which will make available the properties required for each category – fiches-gid_revit-params_xx-xxx_architect/structure/MEP (1)
    • It will be necessary to load the shared parameter file for all project phases – Fiches-gid_revit-shared-params-exp_archi/structure/mep.txt (2)
    • Complete the Classification Property field with (3): “BIMids Classification” – (for Configuration files before Version 1.4, you need to type “Classification BIMQ” instead of “BIMids Classification”)
    • It will be necessary to load once the shared parameter file for all the phases of the project

B. Fill in the properties

  • Display the properties window (AP shortcut if configured), Ekkodale Suite>AIA Editor tab

Depending on the loaded file (Archi, Structure or MEP) and the object selected in the view, the required properties will appear in the AIA EDITOR palette

  • For some Revit categories, it is necessary to specify a “subcategory” in order to display only the required properties in the AIA Editor window, see the difference between “Engineered Floor” and “Slab”, the properties specific to the “subcategory” are framed in green.

C. Precautions and details to avoid errors

  • You have to respect some Revit categories according to the IFC classes otherwise you will get only a part of the properties in your IFC export, see detailed table here point 4.3
  • You can proceed in the same way for all the objects of your project. The ideal is to create your types for each Revit family with integration of properties up to phase 5 of the project and the mapping will allow you to filter the properties to be exported or not phase by phase, this avoids re-encoding everything for each project. By proceeding in this way, when an object will have a type with the encoded properties (system or loadable family), we will be able to have this type for other projects via the Revit template by integrating a maximum of pre-encoded values and it will remain to complete the occurrence properties only (ID, …).
  • For classification, do not use the Assembly code and Assembly description fields, you must check that these fields are empty (occurrence and type), otherwise the value of these cells will be taken into account during export.
  • Some properties are not visible in the AIA plugin window, especially the type properties. These fields must be filled in the normal revit field in the type editor.
  • You can select several objects and modify their properties in a single operation
  • When you enter values in the fields of the window, be sure to apply the changes with the “APPLY” button, otherwise the changes are not saved
  • You have to load the Classification Manager XLSX file before filling the IfcExportAs field because the field is created by loading this file
  • It is necessary to load the configuration files for classification via AIA before assigning a classification because the classification fields are created via the AIA plugin and the configuration file
  • It often happens that you have to deselect and reselect an object so that all the properties are displayed, don’t hesitate to do so if some properties are not displayed.
  • For loadable families, it happens that the “IFCExortAs” property is already filled in, so you have to delete the value > apply with the APPLY button and then re-encode, in principle using the Classification Manager.

Tutorial des manipulations :

Next step in the guide: 4.3. Mapping Revit categories

Subscribe
Notify of
guest
0 Commentaires
Inline Feedbacks
View all comments
0
Would love your thoughts, please comment.x
()
x