IFC Parameters

Create IFC parameters in "Naviate IFCx v2016.2"

 This helpfile describes the IFC property handling in the Naviate IFCx 2016.


There is a lot of IFC properties that can be used, this function and helpfile focuses on the most frequently used.
The helpfile is based on the latest IFC exporter, If you are using an older version you may not get the full functionality.

All IFC software that analyzes data, eg. rulesets in Solibri, depends on standardized IFC Common property sets.

This function creates the shared parameters which are used in IfcCommon property sets.
Some of them is exported automatically, such as "LoadBearing" for IfcWall.
And some do not export unless you have these parameters.

For example "IfcSite.Name" might be a BIM requirement in your project.
Or you might want i just because it looks more professional.
In any case to export this property you need a "Project Info" parameter called "SiteName".
Simply give the parameter a value and it will export to IFC.



This function and page will be continuously updated according to the latest Naviate and opensource IFC exporters .
Additionally to what this function does, you can find information on how to override project-level GUID's here:



- This is the IfcCommon parameters this function creates and how you use them:

ZoneName 2,
ZoneName 3,
IFC CAD Layer,


A property to set the IfcBuildingStory.AboveGround.
It is found on Level instance Properties.

A property to set the IfcBuildingStory.EntranceLevel.
It is found on Level instance Properties.

For example checking both parameters in Revit returns both IFC properties "True".
Uncheking them will return "False".



A parameter to set Pset_BuildingCommon.BuildingID
In Revit it is found in Manage->Project Information:



A parameter to override the IfcEntity.Name property.
It could be used for most Revit Categories and also to override IfcEntityType.Name if found on Type Properties.
You can expand this to any Category and it will function as an override to Revits family and typenames..

We have choosen to use it on Levels thus setting IfcBuildingStorey.Name.
For instance you may want to display your Level name as "Plan First Floor" on drawings.
But still export the Level Name as "01" to IFC if required.
If you want to use it on other categories too just go to Manage -> Project Parameters.
Here you can change which Revit Categories this parameter is attached to.

Keep in mind that IFC has both Entity.Name (Instance) and EntityType.Name.(Type)
Some viewers like Solibri only displays the "instance" Entity.Name.
So if you specifically use IfcName on Type Properties then Solibri may not show it.

A parameter to set the IfcEntity.LongName property.
At this point we have chosen to use it on Levels but it can be used on any Revit Category.
It is found Level instance properties.


SiteName, SiteLongName and SiteLandTitleNumber
These are parameters to set the IfcSite properties. 
They are found in Manage->Project Information.

A property to set the IfcXxxCommon.IsExternal property.
It s found on Type Properties of Floors, Doors,,Roofs, Columns and Railings.
This is an override, if not set most categories will default to "True" meaning they become External.
For other categories like Walls this is automatically set from the Walls "Function" parameter.


- AcousticRating / SecurityRating

Putting your classifications on these parameters will put them in the standard common IFC property sets.
This is the default location where cost calculation software looks for these properties.




- ObjectTypeOverride

Useful for exporting "Provisions For Voids".
This is mostly voids made by ducts and pipes in building elements such as walls and floors.
Typically this is exported by MEP engineers and imported by architects.
Other BIM software may import them and create the necessary cutouts when they are approved for the actual walls.
For example "Tekla Structures" can import this information in "Hole Reservation Manager" to create voids.



- ZoneName, ZoneName 2, ZoneName 3 etc

The Room parameter "Zonename" allows you to create IfcZone objects.
Each Room can be related to multiple IfcZone categories.
For example "Room 101" can be related to both a security control zone and a acoustic zone.
You could decide you want to use "ZoneName" for security plans and "Zonename 2" for acoustic layouts like this:


This is drawings some need to make anyway.
The benefit of using these parameter names for making them becomes apparent when you export to IFC:




This type parameter decides the IfcClass on export just as "IFC Export Options" does.
It functions as an override to the "IFC Export Options" settings and is found on Type Properties.

It can be used not just to separate outlets from other Electrical Fixtures like dryers.
But to differentiate different types of outlets like this:

- Applicable example values for IfcExportAs:

If you just rely on the global "IFC Export Settings" then every Category will become the same IfcClass.
So using IfcExportAs is a smart thing to do and also allows predefining the IFC Export Class in your familys.




For some system familys like Floors you need to set the enumaration on this parameter.
You could use it to set properties like "BASESLAB" .


IFC CAD Layer (2016)

Yes IFC files has layers in the same way as CAD (dwg) files has.
This parameter lets you specify the layer for each FamilyType.
Tip: You could use the "Combine Parameters" function in Naviate to populate it.
It functions as an override to the default settings.
If not specified here Revit will use the cad layer table you have selected with the "IFC CAD Layers" function.



- Link to free IFC viewers:
FZK viewer - simple and fast 

Tekla Bimsight

Solibri Model Viewer





Var denne artikkelen nyttig?
1 av 1 syntes dette var nyttig
Har du flere spørsmål? Send oss en henvendelse

0 Kommentarer

Artikkelen er stengt for kommentarer.
Levert av Zendesk