The following outlines the analysis features applicable for process plant and marine shipbuilding projects.
Feature
Purpose
Caesar II Interface
Pipe stress analysis using Caesar II
Rohr 2 Interface
Pipe stress analysis using Rohr 2
Structural Analysis Interface
Structural analysis using STAAD Pro
Note:
For the structural discipline in plant design projects and for the outfitting steel discipline in marine shipbuilding projects
Feature
Purpose
Caesar II Interface
Pipe stress analysis using Caesar II
Rohr 2 Interface
Pipe stress analysis using Rohr 2
Structural Analysis Interface
Structural analysis using STAAD Pro

Feature
Purpose
Caesar II Interface
Pipe stress analysis using Caesar II
Rohr 2 Interface
Pipe stress analysis using Rohr 2
Structural Analysis Interface
Structural analysis using STAAD Pro
Note:
For the structural discipline in plant design projects and for the outfitting steel discipline in marine shipbuilding projects
Note:
For the structural discipline in plant design projects and for the outfitting steel discipline in marine shipbuilding projects

Feature
Purpose
Note:


The following outlines the analysis features which are applicable for marine shipbuilding projects only.
Feature
Purpose
Hull FEM Export (XML)
Export Idealized hull structural design model to third party software ( HyperMesh) for Finite Element Analysis. (Hull only)
OCX Export
Export of Hull Structural 3D arrangement model for class approval in DNVGL and so on (Hull only)
Feature
Purpose
Hull FEM Export (XML)
Export Idealized hull structural design model to third party software ( HyperMesh) for Finite Element Analysis. (Hull only)
OCX Export
Export of Hull Structural 3D arrangement model for class approval in DNVGL and so on (Hull only)
Feature
Purpose
Hull FEM Export (XML)
Export Idealized hull structural design model to third party software ( HyperMesh) for Finite Element Analysis. (Hull only)
OCX Export
Export of Hull Structural 3D arrangement model for class approval in DNVGL and so on (Hull only)

Feature
Purpose


Import of mechanical CAD models for singular or composite equipment items

Use the following as guidance on the import of singular equipment items such as pumps, centrifuges, heat exchangers and so on as well as composite or more complex models such as processing modules, skids, cranes or conveyor arrangements.


Control over model creation or export from source tool

This is where the E3D Design user has control over the creation and export of the mechanical CAD models from the authoring tool, for example where mechanical equipment are designed in-house within the same company or in close collaboration with an external company.
If possible try to make the exported model as light-weight as possible by removing unnecessary details already in the source tool before export, or where there are export options to reduce the level of detail.
There is one exception to this – where it is intended to use AVEVA Model Simplification for import, as this tools typically works best with a full solid model B-Rep model. In this case it may still be good to reduce the detail level before export, but avoid using shrinkwrap or any other simplification in the source tool that will produce an inconsistent or pre-joined exported model.
For Autodesk Inventor specifically:
Avoid using the function remove internal faces. This may make the model look okay when shaded and viewed from standard directions, but can break up b-rep models, making them open-shells.
Also see the INTERFACES_Inventor-to-E3D_BestPractices document.
For large or complex models, where suitable try to split it up and export / import as separate files rather than one big file. This can for example be done by area or discipline. Consider the final deliverables to help determine the original model separation.
As the MultiCAD Import supports a wide range of native CAD formats in parallel with more generic formats such as STEP, it is recommended to try out several options to find the transfer format that gives the best results. Tests carried out by AVEVA have indicated that using native CAD format models can often give better results than more generic STEP files.
Avoid importing models that have been through several format conversions, as this can often reduce the fidelity of the data as well as introduce errors in the import process. It is better to consistently use models directly from the original source tool where they have been created.
When using Model Simplification to import to E3D Design:
This function typically provides better results with B-rep solid models that are not pre-joined or shrink wrapped.
Models may generally contain B-Rep solids, Shells (open or not water tight bodies) and faceted bodies. A higher degree of B-Rep and less faceted bodies would yield better results. Open or not water tight bodies should also be avoided if possible as these do not process very well in Model Simplification.
The above guidance should be considered when preparing and exporting the CAD models from the source authoring tool. However, the results may vary depending on model properties and with different file formats, so we recommend trying different approaches to find the best option for your use case.
If possible try to make the exported model as light-weight as possible by removing unnecessary details already in the source tool before export, or where there are export options to reduce the level of detail.
There is one exception to this – where it is intended to use AVEVA Model Simplification for import, as this tools typically works best with a full solid model B-Rep model. In this case it may still be good to reduce the detail level before export, but avoid using shrinkwrap or any other simplification in the source tool that will produce an inconsistent or pre-joined exported model.
For Autodesk Inventor specifically:
Avoid using the function remove internal faces. This may make the model look okay when shaded and viewed from standard directions, but can break up b-rep models, making them open-shells.
Also see the INTERFACES_Inventor-to-E3D_BestPractices document.
If possible try to make the exported model as light-weight as possible by removing unnecessary details already in the source tool before export, or where there are export options to reduce the level of detail.
For large or complex models, where suitable try to split it up and export / import as separate files rather than one big file. This can for example be done by area or discipline. Consider the final deliverables to help determine the original model separation.
For large or complex models, where suitable try to split it up and export / import as separate files rather than one big file. This can for example be done by area or discipline. Consider the final deliverables to help determine the original model separation.
As the MultiCAD Import supports a wide range of native CAD formats in parallel with more generic formats such as STEP, it is recommended to try out several options to find the transfer format that gives the best results. Tests carried out by AVEVA have indicated that using native CAD format models can often give better results than more generic STEP files.
As the MultiCAD Import supports a wide range of native CAD formats in parallel with more generic formats such as STEP, it is recommended to try out several options to find the transfer format that gives the best results. Tests carried out by AVEVA have indicated that using native CAD format models can often give better results than more generic STEP files.
Avoid importing models that have been through several format conversions, as this can often reduce the fidelity of the data as well as introduce errors in the import process. It is better to consistently use models directly from the original source tool where they have been created.
Avoid importing models that have been through several format conversions, as this can often reduce the fidelity of the data as well as introduce errors in the import process. It is better to consistently use models directly from the original source tool where they have been created.
When using Model Simplification to import to E3D Design:
This function typically provides better results with B-rep solid models that are not pre-joined or shrink wrapped.
Models may generally contain B-Rep solids, Shells (open or not water tight bodies) and faceted bodies. A higher degree of B-Rep and less faceted bodies would yield better results. Open or not water tight bodies should also be avoided if possible as these do not process very well in Model Simplification.
When using Model Simplification to import to E3D Design:
The above guidance should be considered when preparing and exporting the CAD models from the source authoring tool. However, the results may vary depending on model properties and with different file formats, so we recommend trying different approaches to find the best option for your use case.
The above guidance should be considered when preparing and exporting the CAD models from the source authoring tool. However, the results may vary depending on model properties and with different file formats, so we recommend trying different approaches to find the best option for your use case.
Notes:
The Model Simplification feature is based on CADFix PPS from ITI. ITI also offers an interactive version of this tool, allowing more detailed analysis of models to be simplified. The image displayed shows an example of a model with a lot of red icons in the Model Tree.
These red icons indicate open, non-watertight bodies that are not possible to simplify, and will explain why this model does not simplify very much. As mentioned above, AVEVA recommends customers to obtain models suitable for simplification containing watertight closed bodies only.

Autodesk Inventor
remove internal faces
MultiCAD Import
Notes:


No control over model creation or export from source tool

This is where the E3D Design user does not have control over the creation and export of the mechanical CAD model, for example where existing STP files are to be imported, or where files have been received from a vendor or company where it is not possible to impact the creation or export of the model.
For any model files larger than around 10MB or so, please consider using the Model Simplification tool. This has the potential to significantly reduce the size and complexity of the imported model, thereby improving the performance when using add-to-drawlist and related features in E3D Design.


For some situations and use cases, rather than importing CAD model files it could be considered to instead create parametric equipment templates directly in E3D Design, and then instantiate these according to actual dimensions.


Use the following as guidance on the import of 3D plant design models. These can be for entire plant layout models, or parts of such models including equipment items, piping, structure, cableways and so on used in conjunction with additional plant modelling to be done in E3D Design.
For example where a plant has originally been designed with a different or legacy design tool, and users want to include this for reference while adding a new plant unit or extension in E3D Design. Or where buildings have been designed in an architectural design tool.


This case is where the E3D Design user does not have control over the creation and export of the mechanical CAD model, for example where the original project data and design tool is no longer available, and only an export data set exists in a format that can be imported by E3D Design.
No specific recommendations, other than trying to achieve control over how models are created or exported from the source tools
Model Simplification will typically not work for big plant models due to scalability issues.
No specific recommendations, other than trying to achieve control over how models are created or exported from the source tools
No specific recommendations, other than trying to achieve control over how models are created or exported from the source tools
Model Simplification will typically not work for big plant models due to scalability issues.
Model Simplification will typically not work for big plant models due to scalability issues.


Import of mechanical CAD and plant design models

Use the following as guidance on the import of mechanical CAD and plant design models.


Apart from model size, the quality of the file to be imported is also of importance. CAD files that have been through several format conversions or version upgrades before attempting to import to E3D Design can not be expected to import without problems. Such conversions may in many cases degrade the data quality and cause import errors, geometrical misrepresentations and degraded performance.
For this reason it is highly recommended to always obtain CAD files straight from the authoring tool and avoid any fomat conversions or version upgrades.


Behavior of imported models – geometry & modelling

It is important to be aware that imported models are built up of different kinds of geometrical definition to those that have been natively created in E3D Design. Because of this, the application behavior may be different and the ability to modify the imported models in E3D Design will be limited.


Most of the general 3D model capabilities of E3D Design works just as well with imported models as with models that have been natively created withing E3D Design. These include clash checking, picking, dimensioning and so on.
However, one difference between natively modelled and imported equipment is that the imported equipment will be represented by General Primitive (GENPRI) elements rather than boxes, cylinders ans so on. The GENPRI elements can be individually moved and rotated, but not scaled or modified in any other way that the native primitives can be.
Modelling activities for placing equipment on structural foundations and connecting pipes and cables heavily rely on snapping to P-Points and P-Lines as well as graphical snapping. Imported models will not have any P-Points or P-Lines, but the graphical snapping can still be used. However, many GENPRI elements from imported CAD models may have curves and details making it more difficult to find a distinct point to snap to, than with natively modelled equipment objects.


In projects were many or large and detailed CAD models have been imported, it may affect the overall performance of E3D Design. For this case it is recommended to only bring in the necessary parts of the 3D model into the view while working.
To view the entire project model or a larger section of it, AVEVA recommends using the Graphical Explorer which provides superior performance for large model viewing.


To be able to connect pipes to imported equipment items it is required to manually add nozzles. In many cases the geometrical representation of the nozzles are part of the imported model, but as these are not intelligent objectes, pipes can not be connected.
Depending on the object structure of the imported model, the nozzle geometry may be represented as a separate GENPRI. In that case this GENPRI can be deleted and replaced by a native / intelligent nozzle.
If the nozzle is not represented by a separate GENPRI, then deleting this may remove too much of the imported model and it may have to be left in place. For this case the native nozzle can be modelled as superimposed on top of the imported nozzle geometry.


To place equipment relative to existing steelwork, or to model new steelwork in relation to equipment items, the structural application relies on grips obtained by snapping. As mentioned above, the GENPRI allows graphical snapping to be done even if it sometimes can be difficult find an ideal snapping point on curved and detailed primitives.


AVEVA tries to conserve any metadata during imports where possible, but depending on the file format and tool used for import, some metadata may not be carried through the import process.
For such cases, we recommend to try and export the metadata separately from the source application, and import it into E3D Design using Excel Import.
Where AVEVA Engineering is being used it can also be considered to import the data there as this product has more possibilities for organizing and managing attribute data than E3D Design.


Import of STEP, STL, IGS files and native mechanical CAD formats

The Mechanical Equipment Interface (MEI) feature has long been available in E3D Design for import of STEP files.
With the release of E3D Design 3.1.4, a new feature called MultiCAD Import was introduced. This feature covers a wide range of native CAD formats, and is in many cases more efficient than MEI in terms of time taken to import the models as well as the efficiency of imported CAD models, for Add-to-Drawlist time and so on.
It is recommended to use the MultiCAD Import for this scenario, and AVEVA intends to fully replace MEI with MultiCAD over time and then deprecate the MEI Import function.
While MutiCAD Inport works well for relatively small or medium-sized models, it is recommended to use Model Simplification for larger models to improve performance of the imported model. Please refer to Model Size and scalability for more information.
For the moment, the MEI Import is able to create native E3D Design nozzles which MultiCAD Import is not. AVEVA intends to cover this gap in MultiCAD Import over time. Until then, for cases where nozzle creation is of particular importance, MEI can be used.

Model Size and scalability


When using the MEI Import, you will typically get the most performant models by enabling the Save facet data option, and setting the Tolerance to the same value as the Arc Tolerance in Drawlist Graphics Settings, by default 1mm.
MEI imports one level of any assembly hierarchy, names the E3D Design elements created, imports curved elements as E3D Design GENPRI elements but does not import metadata.

Save facet data


For a general import of STL and IGS files AVEVA recommend the use of MultiCAD import. Import of STL files attempts to recognize simple primitives from STL facets and if successful can produce usable models, but in many cases produces less efficient E3D Design models where it will be better to select a different file format if possible
The Terrain import continues to use the MEI import for these file types.
For a general import of STL and IGS files AVEVA recommend the use of MultiCAD import. Import of STL files attempts to recognize simple primitives from STL facets and if successful can produce usable models, but in many cases produces less efficient E3D Design models where it will be better to select a different file format if possible
For a general import of STL and IGS files AVEVA recommend the use of MultiCAD import. Import of STL files attempts to recognize simple primitives from STL facets and if successful can produce usable models, but in many cases produces less efficient E3D Design models where it will be better to select a different file format if possible
The Terrain import continues to use the MEI import for these file types.
The Terrain import continues to use the MEI import for these file types.


Managing the import process - it is recommended to have a separate DESI DB for importing CAD models, which is not part of the regular project MDB’s for users.
Models can then be imported to this DB with different Model Simplification settings together with a fully detailed model using the MultiCAD Import, and then checks to assess the simplification results with regards to visual fidelity/preservation of necessary details against the performance to find the right balance.
It is then also possible to manually adjust the imported models, for example to copy SUBE or GENPRI from the fully detailed import to the simplified model where any important details have gone missing in the simplification process. Or to delete some complex geometry and manually replace by a box.
Once a suitable level-of-detail has been found, the model can then be copied into the real project DESI DB.
Refer to the recommendations detailed in Control over model creation or export from source tool on how to obtain models most suitable for simplification.

Control over model creation or export from source tool


AVEVA E3D Design includes a legacy DGN file format import feature. However, support for DGN format is expected to arrive in an upcoming version of Hoops Exchange, which will enable the MultiCAD Import feature to also support this format.
Once available, AVEVA will evaluate the new options and create guidelines based on the results.


Use the following as guidance on the import from and export to structural design.


For importing IFC Files, there are two different import tools that can be used. Depending on the type of model to be imported and its properties, as well as the requirements and desired results, either of these functions may work best.
IFC Import
MultiCAD Import
Transfering models from Autodesk Revit
This is normally the best tool for importing a significant IFC Model
The IFC Explorer has extra facilities to handle elements of IFC classes groups and layers, and it always imports to an E3D Design Zone and stores repeated IFC property sets efficiently. In case the project requirements for IFC navigation are different than what the IFC Explorer provides then it is possible to configure an alternative flexible explorer for this purpose Sample Addin FlexibleExplorerAddin (aveva.com).
For cases where the requirements that go beyond the capabilities of the standard IFC Import process, there is an opportunity to customise the process by using PML Objects. For more information refer to How to customise ifc import and export processes (aveva.com).
This is normally the best tool for importing a significant IFC Model
This is normally the best tool for importing a significant IFC Model
The IFC Explorer has extra facilities to handle elements of IFC classes groups and layers, and it always imports to an E3D Design Zone and stores repeated IFC property sets efficiently. In case the project requirements for IFC navigation are different than what the IFC Explorer provides then it is possible to configure an alternative flexible explorer for this purpose Sample Addin FlexibleExplorerAddin (aveva.com).
The IFC Explorer has extra facilities to handle elements of IFC classes groups and layers, and it always imports to an E3D Design Zone and stores repeated IFC property sets efficiently. In case the project requirements for IFC navigation are different than what the IFC Explorer provides then it is possible to configure an alternative flexible explorer for this purpose Sample Addin FlexibleExplorerAddin (aveva.com).
For cases where the requirements that go beyond the capabilities of the standard IFC Import process, there is an opportunity to customise the process by using PML Objects. For more information refer to How to customise ifc import and export processes (aveva.com).
For cases where the requirements that go beyond the capabilities of the standard IFC Import process, there is an opportunity to customise the process by using PML Objects. For more information refer to How to customise ifc import and export processes (aveva.com).
The MultiCAD Import also offers an option to import IFC files which can be tried where the regular IFC Import does not provide the desired results
The MultiCAD Explorer does not have IFC specific groupings but can import to lower level elements, for example EQUI. The MultiCAD Import may therefore work better for importing for importing components rather than whole buildings
For 32bit versions of E3D Design, the MultiCAD Import can potentially import somewhat larger IFC files.
The MultiCAD Import also offers an option to import IFC files which can be tried where the regular IFC Import does not provide the desired results
The MultiCAD Import also offers an option to import IFC files which can be tried where the regular IFC Import does not provide the desired results
The MultiCAD Explorer does not have IFC specific groupings but can import to lower level elements, for example EQUI. The MultiCAD Import may therefore work better for importing for importing components rather than whole buildings
The MultiCAD Explorer does not have IFC specific groupings but can import to lower level elements, for example EQUI. The MultiCAD Import may therefore work better for importing for importing components rather than whole buildings
For 32bit versions of E3D Design, the MultiCAD Import can potentially import somewhat larger IFC files.
For 32bit versions of E3D Design, the MultiCAD Import can potentially import somewhat larger IFC files.
For cases where the model originates from Revit, MultiCAD Import also supports native Revit format. This might give better results than IFC depending on the model properties and requirements.
Refer to the following documents that provide guidance on how to best prepare and export models from Revit:
Suggested way to export model from Revit to E3D
Limiting number of elements exported from Revit to E3D, using Revit IFC interface.
For cases where the model originates from Revit, MultiCAD Import also supports native Revit format. This might give better results than IFC depending on the model properties and requirements.
For cases where the model originates from Revit, MultiCAD Import also supports native Revit format. This might give better results than IFC depending on the model properties and requirements.
Refer to the following documents that provide guidance on how to best prepare and export models from Revit:
Suggested way to export model from Revit to E3D
Limiting number of elements exported from Revit to E3D, using Revit IFC interface.
Refer to the following documents that provide guidance on how to best prepare and export models from Revit:

IFC Import
ultiCAD Import
Transfering models from Autodesk Revit


There are many factors affecting the process of creating an IFC file. As a result, it is very difficult to make absolute recommendations. However, there are several things to consider that affect the file size, the time taken to export and the time taken to import into the receiving system. Refer to the IFC Export User Guide for more information.


There are several methods available to import structural design data from TELKA. The main options are outlined as follows together with any particulars and considerations for each method.
SDNF
SDNF provides a way to import structural steel to E3D as intelligent elements, but has some limitations in what can be imported:
SDNF can import Linear elements such as UB, UC and PFC, as well as planar types (flat plates but not bent plates).
SDNF Cannot import Mechanical Items, and it can also not import Bolts or holes in linear elements. Holes in plates are possible but it depends if the source software can export them to the SDNF file.
During import Linear elements can be mapped to AVEVA Catalogue elements and can be edited in E3D.
IFC
Another option to import from TELKA is to use IFC which will be more complete, but the elements will not be native/editable and can only be used for referencing and coordination.
TELKA Structures offers a number of export type options refer to for example https://telastructures.support.telka.com/2019i/en/int exporting into ifc
AVEVA recommend the use of the Surface geometry (for IFC 2x3) or Reference view (for IFC4) options in TELKA to give the best results when the file is imported into E3D Design.
It is also important to do the IFC export from Tekla in a suitable scope per IFC file,(export in several smaller files than all in one big file). For example create one IFC export file for each framework in Tekla. Thus allowing the import of each file in E3D Design under different owners, which provides a more meaningful navigable hierarchy in E3D Design, and avoids getting too many members within a certain owner which could otherwise affect the performance in E3D Design, or even exceed the maximum number of members for an owner causing errors.
The Assembly level is stored as an AVEVA EQUI (Equipment) type and the single Part is stored as SUBE (Sub Equipment). All IFC imported elements are stored with the same Types in E3D regardless of their source application type. For example a Hole is also stored as a GENPRI under a SUBE under an EQUI.
There are also two DDSE (Data Sets) stored under each type, one dataset for the IFC attributes and the other for the attributes coming from the source application (Tekla). At Single part level (SUBE) again there are the two datasets and also the geometry which is stored as a GENPRI Element.
GENPRI Elements can be moved and rotated in E3D but their geometry cannot be modified. They cannot be changed or mapped to Catalogue items.
TEKLA also offers a bespoke interoperability feature that can be used to transfer data to E3D Design. Refer to https://support.tekla.com/doc/tekla-structures/2020/int_pdms_e3d for more information.
Note:
AVEVA is not able to provide more information about this option as it is developed and owned by TEKLA, but it seems that many AVEVA customers get better results using this capability than the other options of SDNF or IFC. But this may vary depending on the model data and requirements.

SDNF
IFC
Note:


Here we also have the option to use either SDNF, IFC or TELKA Interoperability, and the resulting model in TEKLA will have to be assessed to determine which method gives the best results.


When importing from/exporting to BOCAD and AVEVA E3D Structural Design, the E3D Structural Design (ABSI) interface will give the best results.


To get the best performance when working with model views in Draw:
Bring in the minimum needed for drawings in the draw list
Use a suitable Hidden Line Representation (HLR)
Global HLR Representation is better for larger models as it uses less resources
General wireframe mode provides better performance than hidden line. For this reason it is recommended to use the wireframe mode while arranging views and preparing the drawings, and then switch to Global Hidden Line to finalize the drawings
The edge representation and DUNION attribute for civil drawings works best when using the IFC Import.
Bring in the minimum needed for drawings in the draw list
Bring in the minimum needed for drawings in the draw list
Use a suitable Hidden Line Representation (HLR)
Use a suitable Hidden Line Representation (HLR)
Global HLR Representation is better for larger models as it uses less resources
Global HLR Representation is better for larger models as it uses less resources
General wireframe mode provides better performance than hidden line. For this reason it is recommended to use the wireframe mode while arranging views and preparing the drawings, and then switch to Global Hidden Line to finalize the drawings
General wireframe mode provides better performance than hidden line. For this reason it is recommended to use the wireframe mode while arranging views and preparing the drawings, and then switch to Global Hidden Line to finalize the drawings
The edge representation and DUNION attribute for civil drawings works best when using the IFC Import.
The edge representation and DUNION attribute for civil drawings works best when using the IFC Import.


IFC Export is supplied with a sample configuration based on the APS sample Project. This mapping configuration file can be modified according to requirements using the functionality available from the Edit IFC mapping file window. Any matching element mapping based on the AVEVA E3D Design element type, and for which the AVEVA E3D Design rule is valid and evaluates to True, is selected and used for IFC Export.
A mapping configuration file can be created, modified or deleted using the functionality available from the Edit IFC mappings file window and may be used for any number of exports.
The following information can also be specified:

Load a Mapping Configuration File
Modify a Mapping Configuration File
Load a Mapping Configuration File
Load a Mapping Configuration File
Modify a Mapping Configuration File
Modify a Mapping Configuration File
Which AVEVA E3D Design element corresponds to which IFC class.
Which AVEVA E3D Design elements should be excluded from IFC export.
Property set definitions.
Property mappings for each property set.
Whether mapped but UNSET attributes should be exported.
Which AVEVA E3D Design element corresponds to which IFC class.
Which AVEVA E3D Design element corresponds to which IFC class.
Which AVEVA E3D Design elements should be excluded from IFC export.
Which AVEVA E3D Design elements should be excluded from IFC export.
Property set definitions.
Property set definitions.
Property mappings for each property set.
Property mappings for each property set.
Whether mapped but UNSET attributes should be exported.
Whether mapped but UNSET attributes should be exported.
Note:
The mapping configuration file is validated against the mapping schema to warn the User against any error (syntax error or incorrect mapping file).

Load a Mapping Configuration File
Modify a Mapping Configuration File
IFC Export
Edit IFC mapping file
True
Edit
IFC mappings file
Load a Mapping Configuration File
Modify a Mapping Configuration File
UNSET
Note
:


The mapping configuration file contains the information about how the data is exported to an IFC file, primarily the element types and their attributes that need to be exported.

The Export mapped unset attributes check box controls all the mapped properties that are exported to the IFC file or only those properties which have a set value in AVEVA E3D Design. By default, the check box is not checked.
The values exported for UNSET or empty evaluated property values are:
Property Value Expression Data Type
Value used if unset
STRING
"
INTEGER
0
REAL
0.0
LOGICAL
FALSE
Property Value Expression Data Type
Value used if unset
STRING
"
INTEGER
0
REAL
0.0
LOGICAL
FALSE
The E3D to IFC - element mappings pane of the Edit IFC mapping file window displays the E3D Elements, E3D Rules and IFC Elements (mapped elements) in the currently selected configuration mapping file.

The IFC Element column of the E3D to IFC - element mappings pane controls how the mapped AVEVA E3D Design elements are exported. Double click on the ... next to the required element in the IFC Element column to display the Pick IFC element window.

Search
Use to search the IFC column for an IFC element.
Export as element
Use to select an IFC element type from the list of permitted element types for the currently selected IFC schema.
Export as part of owner
Use to export the geometry and attributes of the owning AVEVA E3D Design element.
Do not export
Use to specify that the geometry, attributes and any owned elements are not exported.
Note:
Once the Do not export radio button is selected, all IFC element types are greyed out. Click OK, the entry in the IFC Element column is replaced with Exclude.
Search
Use to search the IFC column for an IFC element.
Export as element
Use to select an IFC element type from the list of permitted element types for the currently selected IFC schema.
Export as part of owner
Use to export the geometry and attributes of the owning AVEVA E3D Design element.
Do not export
Use to specify that the geometry, attributes and any owned elements are not exported.

Property Value Expression Data Type
Value used if unset
STRING
"
INTEGER
0
REAL
0.0
LOGICAL
FALSE
Search
Use to search the IFC column for an IFC element.
Export as element
Use to select an IFC element type from the list of permitted element types for the currently selected IFC schema.
Export as part of owner
Use to export the geometry and attributes of the owning AVEVA E3D Design element.
Do not export
Use to specify that the geometry, attributes and any owned elements are not exported.
Note:
Once the Do not export radio button is selected, all IFC element types are greyed out. Click OK, the entry in the IFC Element column is replaced with Exclude.
Note:
Any mapped property values which upon evaluation are UNSET or empty are also exported (this can also be achieved by manually editing the mapping configuration .xml file to True).
Note:
Once the Do not export radio button is selected, all IFC element types are greyed out. Click OK, the entry in the IFC Element column is replaced with Exclude.

Export mapped unset attributes
Note
:
UNSET
True
UNSET
Property Value Expression Data Type
Value used if unset
STRING
"
INTEGER
0
REAL
0.0
LOGICAL
FALSE
E3D to IFC - element mappings
Edit IFC mapping file
E3D Elements
E3D Rules
IFC Elements
IFC Element
E3D to IFC - element mappings
...
IFC Element
Pick IFC element
Search
Export as element
Export as part of owner
Do not export
Note
:
Do not export
OK
IFC Element
Exclude


Define AVEVA _EntityParameters PropertySet

The AVEVA_EntityParameters PropertySet can be defined for each element mapping. A default AVEVA_EntityParameters PropertySet is applied to export each element if not defined. A Property defined in this PropertySet can be used to configure the attribute values for mapped IFC elements.
Two special Property can be configured to define relationship:
The ContainedIn property is configured to define containment relationship to the spatial structure element, to which the element is primarily associated.
The AggregateTo property is configured to define decomposition relationship being an aggregation. It determines that this element mapping is a part within an unordered whole/part decomposition relationship.
The ContainedIn property is configured to define containment relationship to the spatial structure element, to which the element is primarily associated.
The ContainedIn property is configured to define containment relationship to the spatial structure element, to which the element is primarily associated.
The AggregateTo property is configured to define decomposition relationship being an aggregation. It determines that this element mapping is a part within an unordered whole/part decomposition relationship.
The AggregateTo property is configured to define decomposition relationship being an aggregation. It determines that this element mapping is a part within an unordered whole/part decomposition relationship.
Note:
An element mapping can only be part of a single decomposition (to allow hierarchical structures only).
Note:
The supplied Sample mapping includes examples for AVEVA_EntityParameters PropertySet based on the APS Sample Project.

ContainedIn
AggregateTo
Note
:
Note
:


Use the Edit IFC mapping file window to define the spatial hierarchical mapping. AVEVA E3D Design elements type based on the E3DRule can be mapped to the inherited entity of IfcSpatialStructureElement.
The ContainedIn property can be defined as part of the AVEVA_EntityParameters Property Set to define the containment relationship to the spatial structure element.
A ContainedIn property value is a string PML Expression that evaluates to the name of the aggregation element it is aggregated to.
Note:
The supplied Sample mapping includes examples for ContainedIn property based on the APS Sample Project.

Edit IFC mapping file
IfcSpatialStructureElement
ContainedIn
ContainedIn
Note
:
ContainedIn


IFC Export
Settings
Settings
Settings
Browse for Mapping file
Select IFC Mapping file
Edit Mapping File
Edit IFC mapping file
Configuration name
Description
Save As


E3D to IFC Mappings
Settings
Browse for mapping file
Select IFC Mapping file
Open
E3D to IFC Mapping
Edit Mappings file
Edit IFC mapping file


For further information, refer to Element Mapping, Define AVEVA_EntityParameters_PropertySet, and Flexible Mapping Command Line IFC Export.

Load a Mapping Configuration File
Element Mapping
Define AVEVA_EntityParameters_PropertySet
Flexible Mapping Command Line IFC Export
Load a Mapping Configuration File
Save
Element Mapping
Define AVEVA_EntityParameters_PropertySet
Flexible Mapping Command Line IFC Export


An IFC file contains a single IfcProject container instance which is the root to which all other entities are linked.
There are several possible valid hierarchies of Ifc Spatial Structure instances, but the most common arrangement is:
The unique IfcProject usually contains (via an IfcRelAggregates instance) one or more IfcSite instances
The IfcSite instance(s) or the IfcProject contain (via IfcRelAggregates instance(s)) one or more IfcBuilding instances.
The IfcBuilding instance (s) usually contain (via IfcRelAggregates instance(s)) one or more IfcBuildingStorey instances
In addition IfcSite and IfcBuildingStorey instances may contain IfcSpace instances.
The unique IfcProject usually contains (via an IfcRelAggregates instance) one or more IfcSite instances
The unique IfcProject usually contains (via an IfcRelAggregates instance) one or more IfcSite instances
The IfcSite instance(s) or the IfcProject contain (via IfcRelAggregates instance(s)) one or more IfcBuilding instances.
The IfcSite instance(s) or the IfcProject contain (via IfcRelAggregates instance(s)) one or more IfcBuilding instances.
The IfcBuilding instance (s) usually contain (via IfcRelAggregates instance(s)) one or more IfcBuildingStorey instances
The IfcBuilding instance (s) usually contain (via IfcRelAggregates instance(s)) one or more IfcBuildingStorey instances
In addition IfcSite and IfcBuildingStorey instances may contain IfcSpace instances.
In addition IfcSite and IfcBuildingStorey instances may contain IfcSpace instances.
Note:
This is the hierarchy supported by E3D Design IFC Export. There are several ways in which you can set up this hierarchy

Note:


If your export mapping does not create an Ifc Spatial structure, the system will create a default one:
An IfcProject with name "Default Project"
No IfcSite is defined
An IfcBuilding with name "SYSTEM_DEFAULT_BUILDING" contained within the default IfcProject
No IfcBuilding Story or IfcSpace instances are created.
All Building Elements are "spatially contained" within that building
(Note that some systems require an IfcSite or IfcBuildingStorey to be present in the IFC file, if this is required you must define it with one of the mapping options below).


Map Existing E3D Elements to Spatial Entities

Depending on how the E3D Model is structured, and which parts are to be exported to IFC, there may already be E3D elements which can be mapped to Ifc Spatial entities, and the Ifc attributes can either be defined explicitly in the mapping, or by expressions referring to E3D attributes.
Example
In AREA02 of the AVEVA sample APS project, it is possible to use existing E3D elements with expressions to name the IfcSite and IfcBuildings appropriately (see example mapping ifc2x3_APS02.xml supplied with E3D Design, typically in the IFCSampleMappings folder %AVEVA_DESIGN_DFLTS%\IFCSampleMappings)
An E3D Site is mapped to an IfcSite, with the name of the IfcSite extracted from the name of the E3D Site by a text expression for the value of the Name property of the AVEVA_EntityParameters property set created for it.

E3D zone elements whose E3D name contains the string ‘BUILDING’ are mapped to IfcBuilding instances with an Ifc name derived from the E3D name by a text expression, and a ContainedIn property set to an expression evaluating to the Ifc name assigned to the IfcSite mapped from the owning E3D Site (property is in the AVEVA_EntityParameters property set).

E3D STRU elements whose E3D name contains the string ‘BUILDING’ are mapped to IfcBuildingStorey instances with an Ifc name derived from the E3D name by a text expression, and a ContainedIn property set to an expression evaluating to the Ifc name assigned to the IfcBuilding mapped from the owning E3D Zone (property is in the AVEVA_EntityParameters property set).
This produces the following corresponding hierarchies when SITE-STRUCTURAL_AREA02 is exported with this mapping (a number of the E3D elements are exported to the SYSTEM_DEFAULT_SITE and the SYSATEM_DEFAULT_BUILDING, as the assumptions made in the mapping file ifc2x3_APS02.xml do not cover all the cases perfectly).

Note
That these E3D elements must be included in the list of elements to be exported for the mappings to be processed, and that for an administrative element (for example a site or zone) to be exported it must have at least one member (an empty EQUI).

Note
Example
Name
ContainedIn
ContainedIn


Create Special Purpose E3D Administrative Elements to Map to IFC Spatial Entities

If the E3D elements in the project do not map naturally onto the Ifc spatial structure, it is possible to create a separate E3D Site containing dummy ZONES and EQUI for the mapping to recognise.
The properties of the Ifc spatial elements can be either be from data in the E3D database, or can be added in the mapping by a rule that only triggers for a single element.
Example
Add an E3D SITE with four named ZONEs, each with a name, and each containing an empty unnamed EQUI:

The mapping can then have a different element mapping with a rule matching the name to create the IFC spatial elements and their ContainedIn hierarchy.

Ordinary elements, for example a WALL can then be allocated to a Building storey by name, either fixed in the mapping, or by an expression.

Note
That these E3D elements must be included in the list of elements to be exported for the mappings to be processed, and that for an administrative element (eg a site or zone) to be exported it must have at least one member (an empty EQUI).

Note
Example
ContainedIn


Mapping Attributes and Containment of Spatial Elements

The example expressions that follow may not apply in a user's environment (for example they may use User Defined Attributes which are not defined in the user's projects).
In addition to the system-required AVEVA_EntityParameters property set, other standard or custom property sets (such as Pset_BuildingCommon) can be defined as required by the receiving system or other local standards.


The unique IfcProject Instance cannot be configured – default attributes are used.


The following attributes of an IfcSite instance can be set by similarly named properties in the AVEVA_EntityParameters property set defined in the mapping.
Property Name
Example Expressions
Name
'AVEVA Example Site'
Desc
Description
:IFC_DESCRIPTION_UDA
Object Type
LongName
'A sample site in Cambridge, United Kingdom'
Property Name
Example Expressions
Name
'AVEVA Example Site'
Desc
Description
:IFC_DESCRIPTION_UDA
Object Type

LongName
'A sample site in Cambridge, United Kingdom'

Property Name
Example Expressions
Name
'AVEVA Example Site'
Desc
Description
:IFC_DESCRIPTION_UDA
Object Type
LongName
'A sample site in Cambridge, United Kingdom'

Property Name
Example Expressions
Name
Description
Object Type
LongName


The following attributes of an IfcBuilding instance can be set by similarly named properties in the AVEVA_EntityParameters property set defined in the mapping.
Property Name
Example Expressions
Name
'EV Hub'
Description
|Electrical Vehicle Charging Hub|
ObjectType
LongName
:IFC_LONGNAME
Property Name
Example Expressions
Name
'EV Hub'
Description
|Electrical Vehicle Charging Hub|
ObjectType

LongName
:IFC_LONGNAME
The following other properties with special meanings can also be set in the AVEVA_EntityParameters property set:
Property Name
Meaning
Example Expressions
ContainedIn
The (IFC) Name of an IfcSite in which the building is contained. If this is not supplied the system default IfcSite is used.
'AVEVA Example Site'
:IFC_CONTAINED_IN
Property Name
Meaning
Example Expressions
ContainedIn
The (IFC) Name of an IfcSite in which the building is contained. If this is not supplied the system default IfcSite is used.
'AVEVA Example Site'
:IFC_CONTAINED_IN

Property Name
Example Expressions
Name
'EV Hub'
Description
|Electrical Vehicle Charging Hub|
ObjectType
LongName
:IFC_LONGNAME
Property Name
Meaning
Example Expressions
ContainedIn
The (IFC) Name of an IfcSite in which the building is contained. If this is not supplied the system default IfcSite is used.
'AVEVA Example Site'
:IFC_CONTAINED_IN

Property Name
Example Expressions
Property Name
Meaning
Example Expressions


The following attributes of an IfcBuildingStorey instance can be set by similarly named properties in the AVEVA_EntityParameters property set defined in the mapping.
Property Name
Example Expressions
Name
'EV Hub First Floor'
Description
|Coffee Shop Floor above the Charging bays|
ObjectType
LongName
:IFC_LONGNAME
Elevation
8.0m
Property Name
Example Expressions
Name
'EV Hub First Floor'
Description
|Coffee Shop Floor above the Charging bays|
ObjectType

LongName
:IFC_LONGNAME
Elevation
8.0m
The following other properties with special meanings can also be set in the AVEVA_EntityParameters property set.
Property Name
Meaning
Example Expressions
ContainedIn
The (IFC) Name of an IfcBuilding in which the building storey is contained. If this is not supplied the system default IfcBuilding is used
'EV Hub'
:IFC_CONTAINED_IN
Property Name
Meaning
Example Expressions
ContainedIn
The (IFC) Name of an IfcBuilding in which the building storey is contained. If this is not supplied the system default IfcBuilding is used
'EV Hub'
:IFC_CONTAINED_IN
Property Name
Example Expressions
Name
'EV Hub First Floor'
Description
|Coffee Shop Floor above the Charging bays|
ObjectType
LongName
:IFC_LONGNAME
Elevation
8.0m
Property Name
Meaning
Example Expressions
ContainedIn
The (IFC) Name of an IfcBuilding in which the building storey is contained. If this is not supplied the system default IfcBuilding is used
'EV Hub'
:IFC_CONTAINED_IN

Property Name
Example Expressions
Property Name
Meaning
Example Expressions


The following attributes of an IfcSpace instance can be set by similarly named properties in the AVEVA_EntityParameters property set defined in the mapping.
Property Name
Example Expressions
Name
'Charging Bay 15'
Description
Desc
ObjectType
|CCS/Chademo/AC EV Charger|
LongName
:IFC_LONGNAME
ElevationWithFlooring
0.2m
Property Name
Example Expressions
Name
'Charging Bay 15'
Description
Desc
ObjectType
|CCS/Chademo/AC EV Charger|
LongName
:IFC_LONGNAME
ElevationWithFlooring
0.2m
The following other properties with special meanings can also be set in the AVEVA_EntityParameters property set:
Property Name
Meaning
Example Expressions
ContainedIn
The (IFC) Name of an IfcBuildingStorey or IfcSite in which the space is contained.
'EV Hub Charging Floor'
:IFC_CONTAINED_IN
Property Name
Meaning
Example Expressions
ContainedIn
The (IFC) Name of an IfcBuildingStorey or IfcSite in which the space is contained.
'EV Hub Charging Floor'
:IFC_CONTAINED_IN

Property Name
Example Expressions
Name
'Charging Bay 15'
Description
Desc
ObjectType
|CCS/Chademo/AC EV Charger|
LongName
:IFC_LONGNAME
ElevationWithFlooring
0.2m
Property Name
Meaning
Example Expressions
ContainedIn
The (IFC) Name of an IfcBuildingStorey or IfcSite in which the space is contained.
'EV Hub Charging Floor'
:IFC_CONTAINED_IN

Property Name
Example Expressions
Property Name
Meaning
Example Expressions


The IfcElement entity and classes derived from it make up most of the physical objects in an Ifc model, and are usually directly or indirectly spatially contained within an instance of an IfcSpatialStructure derived entity.
Most mappings in a mapping configuration will therefore be element mappings, and there may be:
Multiple mappings from the same E3D Element type(s) to different IFC Elements (controlled by the E3D rule)
Multiple mappings to an IFC Element from different E3D elements
Mappings with an empty E3D Rule field, where the E3D element type(s) are enough to choose
Mappings with an empty E3D Elements field, where the E3D rule determines the IFC Element
Mappings with an empty IFC Element field which means Include E3D Elements of the specified types and matching any rule in the owning element – this includes geometry, and any relevant property sets
Mappings may have a special value in the IFC Element field, Exclude which means that the E3D element, and any geometry and properties and any children it has are completely excluded from the exported IFC file
Multiple mappings from the same E3D Element type(s) to different IFC Elements (controlled by the E3D rule)
Multiple mappings from the same E3D Element type(s) to different IFC Elements (controlled by the E3D rule)
Multiple mappings to an IFC Element from different E3D elements
Multiple mappings to an IFC Element from different E3D elements
Mappings with an empty E3D Rule field, where the E3D element type(s) are enough to choose
Mappings with an empty E3D Rule field, where the E3D element type(s) are enough to choose
Mappings with an empty E3D Elements field, where the E3D rule determines the IFC Element
Mappings with an empty E3D Elements field, where the E3D rule determines the IFC Element
Mappings with an empty IFC Element field which means Include E3D Elements of the specified types and matching any rule in the owning element – this includes geometry, and any relevant property sets
Mappings with an empty IFC Element field which means Include E3D Elements of the specified types and matching any rule in the owning element – this includes geometry, and any relevant property sets
Mappings may have a special value in the IFC Element field, Exclude which means that the E3D element, and any geometry and properties and any children it has are completely excluded from the exported IFC file
Mappings may have a special value in the IFC Element field, Exclude which means that the E3D element, and any geometry and properties and any children it has are completely excluded from the exported IFC file
Note:
That IFC 4 added many new IFC Element types, and the examples here may use both schemas.
Note:
Remember that, as always, order is significant First match wins

Note:
Note:


The following includes examples of different ways to map E3D elements to IFC Eeements – many others are possible.
An element mapping has an optional list of E3D element types, and also an optional Boolean expression. In many cases only one or the other is required, but in others both are needed.
Example
To distinguish between some E3D GENSEC elements which should be mapped to IfcBeam elements, and other that should be mapped to IfcColumn elements. Depending on how the structural model is defined, expressions may use text or geometric attributes such as:
For E3D Equipment it may well be desirable to use expressions based on full or partial text attributes, for example the complete name of the E3D element:
STRUCL EQ 'BEAM'
POSE[3] EQ POSS[3]
POSE[1] EQ POSS[1] AND POSE[2] EQ POSS[2]
namn eq 'Units-Heater'
MATCHWILD(Namn,'*METER*')
MATCHWILD(Desc,'*Pump*')
MATCHWILD(Namn,'*CONNECTION_BOX*') OR MATCHWILD(Namn,'ELECTRIC_JB_*')
:EQUI_SUB_GROUP eq 'Space Heater'
:EXPECTED_IFC_CLASS EQ 'IFCFLOWTERMINAL'
( TYPE OF OWNER EQ 'BRAN' )
( TYPE OF OWNER EQ 'BRAN' ) AND ( :HEAT_SYSTEM OF PIPE ) AND ( TYPE NE 'TUBI' )
'SUPPO' inset (AHLIST)
NOT ( UNSET ( MEM STRFLT ) AND UNSET (MEM RLADDR ) )
'TMPL' inset (AHLIST)
What is the Structural Classification of the section?
STRUCL EQ 'BEAM'
Are the Up coordinates of the two ends the same (a beam)?
POSE[3] EQ POSS[3]
Are the East and North coordinates of the two ends the same (a column)?
POSE[1] EQ POSS[1] AND POSE[2] EQ POSS[2]
What is the Structural Classification of the section?
STRUCL EQ 'BEAM'
What is the Structural Classification of the section?
Are the Up coordinates of the two ends the same (a beam)?
POSE[3] EQ POSS[3]
Are the Up coordinates of the two ends the same (a beam)?
Are the East and North coordinates of the two ends the same (a column)?
POSE[1] EQ POSS[1] AND POSE[2] EQ POSS[2]
Are the East and North coordinates of the two ends the same (a column)?
a partial name or description:
MATCHWILD(Namn,'*METER*')
MATCHWILD(Desc,'*Pump*')
MATCHWILD(Namn,'*CONNECTION_BOX*') OR MATCHWILD(Namn,'ELECTRIC_JB_*')
a UDA (these UDAs are examples, not recommendations)
:EQUI_SUB_GROUP eq 'Space Heater'
:EXPECTED_IFC_CLASS EQ 'IFCFLOWTERMINAL'
For Piping, HVAC and similar, useful expressions can include attributes of the direct or indirectly owning elements, such as any element directly owned by a BRANCH
( TYPE OF OWNER EQ 'BRAN' )
a combination - in this case selecting items directly owned by a branch of a pipe with a given UDA value, but excluding implicit tubing
( TYPE OF OWNER EQ 'BRAN' ) AND ( :HEAT_SYSTEM OF PIPE ) AND ( TYPE NE 'TUBI' )
Supports, fixtures and fittings often have deeper hierarchies, perhaps including templates, so expressions including AHLIST (the list of the types of elements above the CE) can be useful, for example to map a STRU element which is directly or indirectly below a SUPPO element to an IfcElementAssembly
'SUPPO' inset (AHLIST)
Map STRU, FRMW and SBFR elements which have at least one member which is a Stairflight or a RungLadder to an IfcStair
NOT ( UNSET ( MEM STRFLT ) AND UNSET (MEM RLADDR ) )
AHLIST is also very useful in expressions where there is no Ifc element required (the Ifc Element name is omitted – meaning that matching items should be included in the same Ifc Element as their owner, or where the special value Exclude is used, in which case geometry and attributes of the matching element should not be exported at all). For example: elements directly or indirectly below a Temple should not be exported separately.
'TMPL' inset (AHLIST)
a partial name or description:
MATCHWILD(Namn,'*METER*')
MATCHWILD(Desc,'*Pump*')
MATCHWILD(Namn,'*CONNECTION_BOX*') OR MATCHWILD(Namn,'ELECTRIC_JB_*')
a partial name or description:
a UDA (these UDAs are examples, not recommendations)
:EQUI_SUB_GROUP eq 'Space Heater'
:EXPECTED_IFC_CLASS EQ 'IFCFLOWTERMINAL'
a UDA (these UDAs are examples, not recommendations)
For Piping, HVAC and similar, useful expressions can include attributes of the direct or indirectly owning elements, such as any element directly owned by a BRANCH
( TYPE OF OWNER EQ 'BRAN' )
For Piping, HVAC and similar, useful expressions can include attributes of the direct or indirectly owning elements, such as any element directly owned by a BRANCH
a combination - in this case selecting items directly owned by a branch of a pipe with a given UDA value, but excluding implicit tubing
( TYPE OF OWNER EQ 'BRAN' ) AND ( :HEAT_SYSTEM OF PIPE ) AND ( TYPE NE 'TUBI' )
a combination - in this case selecting items directly owned by a branch of a pipe with a given UDA value, but excluding implicit tubing
Supports, fixtures and fittings often have deeper hierarchies, perhaps including templates, so expressions including AHLIST (the list of the types of elements above the CE) can be useful, for example to map a STRU element which is directly or indirectly below a SUPPO element to an IfcElementAssembly
'SUPPO' inset (AHLIST)
Supports, fixtures and fittings often have deeper hierarchies, perhaps including templates, so expressions including AHLIST (the list of the types of elements above the CE) can be useful, for example to map a STRU element which is directly or indirectly below a SUPPO element to an IfcElementAssembly
Map STRU, FRMW and SBFR elements which have at least one member which is a Stairflight or a RungLadder to an IfcStair
NOT ( UNSET ( MEM STRFLT ) AND UNSET (MEM RLADDR ) )
Map STRU, FRMW and SBFR elements which have at least one member which is a Stairflight or a RungLadder to an IfcStair
AHLIST is also very useful in expressions where there is no Ifc element required (the Ifc Element name is omitted – meaning that matching items should be included in the same Ifc Element as their owner, or where the special value Exclude is used, in which case geometry and attributes of the matching element should not be exported at all). For example: elements directly or indirectly below a Temple should not be exported separately.
'TMPL' inset (AHLIST)
AHLIST is also very useful in expressions where there is no Ifc element required (the Ifc Element name is omitted – meaning that matching items should be included in the same Ifc Element as their owner, or where the special value Exclude is used, in which case geometry and attributes of the matching element should not be exported at all). For example: elements directly or indirectly below a Temple should not be exported separately.


The following describes guidance o n and examples of AVEVA properties and attributes used during IFC Export.


A Property set named AVEVA_EntityParameters may be attached to each element mapping and is used to control a number of the values of attributes of and relationships between Ifc entities in the generated IFC file.
The property set is itself exported to the IFC file, and this can be useful when debugging mappings, to check that the values of the expressions are what was expected. Some of the properties in these property sets are automatically generated with default value expressions, but if the user chooses to supply own expression, which will be used instead of the default expression.
Here are the properties that can be added to the AVEVA_EntityParameters property set which have special meanings.
Name of the Property
Default Expression
Meaning
Entity
This property is used to transfer the IFC Entity name eg IFCBEAM. It should not be overridden.
UUID
IFCUID
This property is used to transfer the GlobalId attribute. It should not normally be overridden.
Name
FLNN
This becomes the Name attribute of the IFC Entity. It can be overridden if you do not want to use the E3D Name
Description
DESC
This becomes the Description attribute of the IFC Entity. It can be overridden if you do not want to use the E3D Desc.
ObjectType
NAMN OF SPREF
This becomes the ObjectType attribute of the IFC Entity. It can be overridden.
Tag
REFNO
This becomes the Tag attribute of the IFC Entity. It can be overridden.
E3DType
FULL
This is the E3D Element type of the E3D element. This is not otherwise used in the IFC files, but is included to aid understanding of the mapping.
ContainedIn
This property is used to define the Spatial hierarchy of the IFC element. It can be set both on Spatial elements (such as an IfcBuildingStorey – where it should be set to the Ifc name attribute of the containing IfcBuilding), and also on Ifc elements which are spatially contained within an Ifc spatial element.
In all case the expression should evaluate to a string which is the Ifc name of the containing element. If no suitable element with that name exists, an IfcBuilding is created.
AggregateTo
This property is used for elements that for part of another non-spatial element such as an IfcAssembly.The expression should evaluate to a string which is the Ifc name of the aggregating element.
Note:
That if AggregateTo has priority over ContainedIn. If an element has both AggregateTo and ContainedIn expressions defined, and the AggregateTo expression evaluates to a non-empty string, then ContainedIn is ignored. (Spatial containment is then managed at the aggregating element).
Layer
Refer to Presentation Layers
System
Refer to Systems
Material
Refer to Materials
Name of the Property
Default Expression
Meaning
Entity

This property is used to transfer the IFC Entity name eg IFCBEAM. It should not be overridden.
UUID
IFCUID
This property is used to transfer the GlobalId attribute. It should not normally be overridden.
Name
FLNN
This becomes the Name attribute of the IFC Entity. It can be overridden if you do not want to use the E3D Name
Description
DESC
This becomes the Description attribute of the IFC Entity. It can be overridden if you do not want to use the E3D Desc.
ObjectType
NAMN OF SPREF
This becomes the ObjectType attribute of the IFC Entity. It can be overridden.
Tag
REFNO
This becomes the Tag attribute of the IFC Entity. It can be overridden.
E3DType
FULL
This is the E3D Element type of the E3D element. This is not otherwise used in the IFC files, but is included to aid understanding of the mapping.
ContainedIn

This property is used to define the Spatial hierarchy of the IFC element. It can be set both on Spatial elements (such as an IfcBuildingStorey – where it should be set to the Ifc name attribute of the containing IfcBuilding), and also on Ifc elements which are spatially contained within an Ifc spatial element.
In all case the expression should evaluate to a string which is the Ifc name of the containing element. If no suitable element with that name exists, an IfcBuilding is created.
AggregateTo

This property is used for elements that for part of another non-spatial element such as an IfcAssembly.The expression should evaluate to a string which is the Ifc name of the aggregating element.
Layer

Refer to Presentation Layers
System

Refer to Systems
Material

Refer to Materials
Name of the Property
Default Expression
Meaning
Entity
This property is used to transfer the IFC Entity name eg IFCBEAM. It should not be overridden.
UUID
IFCUID
This property is used to transfer the GlobalId attribute. It should not normally be overridden.
Name
FLNN
This becomes the Name attribute of the IFC Entity. It can be overridden if you do not want to use the E3D Name
Description
DESC
This becomes the Description attribute of the IFC Entity. It can be overridden if you do not want to use the E3D Desc.
ObjectType
NAMN OF SPREF
This becomes the ObjectType attribute of the IFC Entity. It can be overridden.
Tag
REFNO
This becomes the Tag attribute of the IFC Entity. It can be overridden.
E3DType
FULL
This is the E3D Element type of the E3D element. This is not otherwise used in the IFC files, but is included to aid understanding of the mapping.
ContainedIn
This property is used to define the Spatial hierarchy of the IFC element. It can be set both on Spatial elements (such as an IfcBuildingStorey – where it should be set to the Ifc name attribute of the containing IfcBuilding), and also on Ifc elements which are spatially contained within an Ifc spatial element.
In all case the expression should evaluate to a string which is the Ifc name of the containing element. If no suitable element with that name exists, an IfcBuilding is created.
AggregateTo
This property is used for elements that for part of another non-spatial element such as an IfcAssembly.The expression should evaluate to a string which is the Ifc name of the aggregating element.
Note:
That if AggregateTo has priority over ContainedIn. If an element has both AggregateTo and ContainedIn expressions defined, and the AggregateTo expression evaluates to a non-empty string, then ContainedIn is ignored. (Spatial containment is then managed at the aggregating element).
Layer
Refer to Presentation Layers
System
Refer to Systems
Material
Refer to Materials
Note:
That if AggregateTo has priority over ContainedIn. If an element has both AggregateTo and ContainedIn expressions defined, and the AggregateTo expression evaluates to a non-empty string, then ContainedIn is ignored. (Spatial containment is then managed at the aggregating element).
Note:
Extra properties can be set with the same name as an attribute of the IFC element being created. For example IfcSpatialElement-derived elements, such as IfcBuilding, have a LongName attribute, and this can be set to a literal string or an expression by defining a LongName property in the AVEVA_EntityParameters property set.

Name of the Property
Default Expression
Meaning
Note:
Note:


The automatic property sets generated for all E3D attributes (either all attributes with a value, or all including unset attributes), have been available since the first release of IFC Export.
If you are providing a full mapping, you will probably not need to export these sets, but will chose to export "None":

This does not top the export of AVEVA_EntityParameters, or and other property sets defined in the mapping.


It is possible to attach standard or other custom property sets to IFC instances, for example

This example uses several expression types, and the units of the expression result are applied to the Ifc property value. In addition, the @@IFCPOSITIVERATIOMEASURE in the Desc column in an example of an explicit type-override to control
If the expression returns a list of values, then an IfcPropertyListValue will be exported, otherwise an IfcPropertySingleValue.


The datatype of the IfcProperty NominalValue, is where possible, chosen automatically from the data type of the E3D expression used to create it, where that type is refer to the table.
E3D Type
IFC Measure
Units
Distance
IfcLengthMeasure
millimetre
Bore
IfcLengthMeasure
millimetre
Area
IfcAreaMeasure
square metre
Volume
IfcVolumeMeasure
cubic metre
Angle
IfcPlaneAngleMeasure
radian
Mass
IfcMassMeasure
kilogram
Pressure
IfcPressureMeasure
pascal
Current
IfcElectricCurrentMeasure
ampere
Speed
IfcLinearVelocityMeasure
metre/second
Power
IfcPowerMeasure
kilowatt
Torque
IfcTorqueMeasure
newton metre
Volumetric Flow
IfcVolumetricFlowRateMeasure
cubic metre/second
Density
IfcMassDensityMeasure
kilogram/cubic metre
Force
IfcForceMeasure
newton
Temperature
IfcTherodynamicTemperatureMeasure
kelvin
EMF
IfcElectricVoltageMeasure
volt
E3D Type
IFC Measure
Units
Distance
IfcLengthMeasure
millimetre
Bore
IfcLengthMeasure
millimetre
Area
IfcAreaMeasure
square metre
Volume
IfcVolumeMeasure
cubic metre
Angle
IfcPlaneAngleMeasure
radian
Mass
IfcMassMeasure
kilogram
Pressure
IfcPressureMeasure
pascal
Current
IfcElectricCurrentMeasure
ampere
Speed
IfcLinearVelocityMeasure
metre/second
Power
IfcPowerMeasure
kilowatt
Torque
IfcTorqueMeasure
newton metre
Volumetric Flow
IfcVolumetricFlowRateMeasure
cubic metre/second
Density
IfcMassDensityMeasure
kilogram/cubic metre
Force
IfcForceMeasure
newton
Temperature
IfcTherodynamicTemperatureMeasure
kelvin
EMF
IfcElectricVoltageMeasure
volt
The following Unitless values are supported:
In addition to the above lists , it is possible to specify the following measure types by reserved values in the Desc column of the property definition.
Description Keyword
Ifc Measure
Underlying Type
@@IFCIDENTIFIER
IfcIdentifier
Text
@@IFCPOSITIVERATIOMEASURE
IfcPositiveRatioMeasure
Numeric
@@IFCPOSITIVELENGTHMEASURE
IfcPositiveLengthMeasure
Length
Description Keyword
Ifc Measure
Underlying Type
@@IFCIDENTIFIER
IfcIdentifier
Text
@@IFCPOSITIVERATIOMEASURE
IfcPositiveRatioMeasure
Numeric
@@IFCPOSITIVELENGTHMEASURE
IfcPositiveLengthMeasure
Length
E3D Type
IFC Measure
Units
Distance
IfcLengthMeasure
millimetre
Bore
IfcLengthMeasure
millimetre
Area
IfcAreaMeasure
square metre
Volume
IfcVolumeMeasure
cubic metre
Angle
IfcPlaneAngleMeasure
radian
Mass
IfcMassMeasure
kilogram
Pressure
IfcPressureMeasure
pascal
Current
IfcElectricCurrentMeasure
ampere
Speed
IfcLinearVelocityMeasure
metre/second
Power
IfcPowerMeasure
kilowatt
Torque
IfcTorqueMeasure
newton metre
Volumetric Flow
IfcVolumetricFlowRateMeasure
cubic metre/second
Density
IfcMassDensityMeasure
kilogram/cubic metre
Force
IfcForceMeasure
newton
Temperature
IfcTherodynamicTemperatureMeasure
kelvin
EMF
IfcElectricVoltageMeasure
volt
Description Keyword
Ifc Measure
Underlying Type
@@IFCIDENTIFIER
IfcIdentifier
Text
@@IFCPOSITIVERATIOMEASURE
IfcPositiveRatioMeasure
Numeric
@@IFCPOSITIVELENGTHMEASURE
IfcPositiveLengthMeasure
Length
IfcText
IfcReal
IfcInteger
IfcLogical
IfcText
IfcText
IfcReal
IfcReal
IfcInteger
IfcInteger
IfcLogical
IfcLogical
Note:
That restrictions on values (eg ensuring that a positive length measure is greater than zero) are not implemented.Future releases may increase the range of measures supported.

E3D Type
IFC Measure
Units
Description Keyword
Ifc Measure
Underlying Type
Note:


The following describes other IFC relationships.


The IFC Import User Interface (IFC Import) enables the processing of .IFC files in AVEVA Everything3D, the available functionality is the default.


The IFC Import window is displayed as a dockable window, initially docked at the right-hand side of the screen.

For further information, refer to Source, Destination, Settings, Logging, Import Using the Command Line, IFC Flexible Explorer.

Source
Destination
Settings
Logging
Import Using the Command Line
IFC Flexible Explorer
IFC Import
Source
Destination
Settings
Logging
Import Using the Command Line
IFC Flexible Explorer


Defines the details of the source data of the imported model.

When an import transaction is completed and the IFC Import window is closed, the window settings are saved to a default file in the AVEVA_DESIGN_USER directory. The file is named ifcimport.impsav. When the IFC Import window is re-invoked, the System searches for this file and restores all but one of the IFC Import window values at the time of closing the IFC Import window.
All of the IFC Import window settings can be saved to a file, and reloaded into the IFC Import window.
Load:
Use a file browser to select a previously created file to populate the IFC Import window fields. On loading a settings file, all the fields are repopulated except the field defining the import site destination. This makes sure that the import location is stated.
Reset:
Clears all fields and sets them to the System default values.
Imports a single .IFC file or a folder containing a set of IFC files as the import source (the default is File).

Enter the file name/folder path or browse to locate the required file or folder.
Once the source data has been correctly defined, click Next to proceed to the Destination window.
For further information, refer to Destination, Settings, and Logging.

Destination
Settings
Logging
IFC Import
IFC Import
IFC Import
IFC Import
IFC Import
IFC Import
Load:
IFC Import
Reset:
Source File or Folder
File
Next
Destination
Destination
Settings
Logging


This section defines the details about the destination of the imported model. The main model is imported into the normal SITE, ZONE hierarchy.

Activates a file browser which creates a file that can be used to repopulate the Import IFC window fields. The saved file is suffixed .impsav. For example:
The file can be used as a basis for a User-developed PML interface that can run in command line mode.
If required, a SITE element in the Model Explorer may be defined for the destination, specify the name of a SITE element or navigate to one and click CE.
Specify the name of a GPWL element or navigate to one and click CE. In order to be able to view the data in a form similar to the IFC import file, GPWL elements are created to reconstruct that hierarchy.
By default, IFC Import creates a GPWL element named /IFC_Import with a Function attribute set to IMPORT. Unless otherwise stated, subsequent import transactions will generate Group Set GPSET elements in that GPWL element.
However, other GPWL elements can be created/chosen to receive the imported data. It is not essential to define a destination GPWL element, leaving the field blank means the default GPWL will be used.
Use the Reference Datum part of the Destination window to select a Reference Datum from the populated list, create a Reference Datum, edit or delete an existing one. The Reference Datum is a holder for information about the transformation coordinate system, which allows the relocation of the imported model’s origin and orientation.

If a Reference Datum is not required, leave the Use Reference Datum check box unselected. (By default the Use Reference Datum check box is not selected).
Use the functionality available for selection from the Reference Datum window to name, locate and orientate the datum.

Format
Defines the position axis using the Format drop-down lists, East/West, North/South and Up/Down. Explicit position values can be typed into the Position fields.
Offset
Moves an element(s) a specified distance in a specified direction, relative to its current position.
Lock
Select the check box to lock the specified coordinates.
Orientation
Defines the axes (fixed reference lines) of an element using explicit orientation values.
Edit
Defines the axes (fixed reference lines) of an element using explicit orientation values or the axes of an existing element. For further information, refer to Orientate.
Scale
Displays the current scale.
Format
Defines the position axis using the Format drop-down lists, East/West, North/South and Up/Down. Explicit position values can be typed into the Position fields.
Offset
Moves an element(s) a specified distance in a specified direction, relative to its current position.

Lock
Select the check box to lock the specified coordinates.
Orientation
Defines the axes (fixed reference lines) of an element using explicit orientation values.
Edit
Defines the axes (fixed reference lines) of an element using explicit orientation values or the axes of an existing element. For further information, refer to Orientate.
Scale
Displays the current scale.
Use the functionality available for selection from the Reference Datum window to modify the name, location and orientation of the Reference Datum.

Deletes the currently selected Reference Datum. A Confirm window is displayed asking to confirm the deletion.

For further information, refer to Settings, Logging, and IFC Flexible Explorer.
Format
Defines the position axis using the Format drop-down lists, East/West, North/South and Up/Down. Explicit position values can be typed into the Position fields.
Offset
Moves an element(s) a specified distance in a specified direction, relative to its current position.
Lock
Select the check box to lock the specified coordinates.
Orientation
Defines the axes (fixed reference lines) of an element using explicit orientation values.
Edit
Defines the axes (fixed reference lines) of an element using explicit orientation values or the axes of an existing element. For further information, refer to Orientate.
Scale
Displays the current scale.
Note:
This is not necessarily the hierarchy of the source program from which the IFC import file comes.
Note:
Any previously set Function attribute of the User-defined GPWL element will be overwritten by IMPORT so that the GPSET element would then be viewable in the Flexible Explorer.
Note:
The IFCGLOBAL Reference Datum is not modifiable (by default E0N0U0 / Y is N and Z is U). If accidentally deleted, it is regenerated.
Note:
The functionality of the Reference Datum window is explained. For further information, refer to Create Reference Datum.

Settings
Logging
IFC Flexible Explorer
SITE
ZONE
Import IFC
-- IMPORT
-- If you wish to use this as a source for your own IFCImporterObj based
-- interface, change '!this' to the name of your export object variable.
!this.setUserFileFolder('C:\Users\Public\DOCUME~1\AVEVA\USERDATA\')
!this.setSrcFolderFlg(FALSE)
!this.setSource('C:\Users\james.barrett\Desktop\1.ifc')
!this.setRootDir('C:\Users\Public\Documents\AVEVA\Projects\E3D2.1\AvevaPlantSample')
!this.setDbTarget(=2013286748/50)
!this.setRefDatumByName('IFCGLOBAL')
!this.setScale(1)
!this.setGroupWorld(=2013286748/47)
!this.setRefDatumOption(TRUE)
!this.setPrefix('')
!this.setCacheFacets(TRUE)
!this.setTolerance(10mm)
!this.setBucketSize(100)
!this.setUseBucketSize(true)
!this.setLogFile('C:\Users\Public\Documents\AVEVA\Projects\E3D2.1\AvevaPlantSample\IFC_Export.log')
!this.setLogDetail(2)
SITE
Model Explorer
SITE
CE
GPWL
CE
GPWL
Note
:
GPWL
/IFC_Import
Function
IMPORT
GPSET
GPWL
GPWL
GPWL
GPWL
Note
:
Function
GPWL
IMPORT
GPSET
Flexible Explorer
Reference Datum
Destination
Use Reference Datum
Use Reference Datum
Reference Datum
Format
Format
East/West
North/South
Up/Down
Position
Offset
Lock
Orientation
Edit
Orientate
Scale
Reference Datum
Note
:
IFCGLOBAL Reference Datum
Note
:
Reference Datum
Confirm
Settings
Logging
IFC Flexible Explorer


Use the Settings window to define the settings for model import to be selected. By default (currently) the Settings window is correctly filled in and the blue tick icon is displayed and the Import functionality is available.

Use the Tolerance part of the Settings window to Save Facet Data, select the Save Facet Data check box (a valid tolerance value must be entered), by default the Save Facet Data check box is not selected.
The default tolerance setting is that which is current in the graphics representation when the Settings window is displayed.
Use the Storage part of the Settings window to specify the number of elements contained in each ZONE.
Select the Limit no. of import elements per ZONE check box. A valid number of import elements per ZONE value must be entered. By default, the Limit no. of import elements per ZONE check box is not selected.
The default number of import elements per ZONE setting is 100. A value of less than 25 or more than 1000 cannot be entered.
When the model is imported, subsequent ZONE names are based on the name of the original ZONE.

The Naming functionality available from the Settings window, using a model prefix in the naming of the GroupSets and main model. If a prefix is not entered then the automatic naming functionality will be used based on the input file name.
In setting the model prefix, there maybe some tidying up and name validation required, and during the import process, there are checks to avoid duplicate names.
Below is the Model Explorer Group Set structures when a prefix of TestModel has been supplied.

And here is the default situation when no prefix is given.

For further information, refer to Logging.
Note:
No facet data will be saved by default.
Note:
If the Save Facet Data check box is selected but no valid tolerance is entered, the orange triangle is displayed.
Note:
Automatic naming can be overridden using the PML object and the userPostProcess function. In that User-developed function, it can be determined whatever post processing to undertake after the model is imported. Naming of elements is one aspect of this.

Logging
Settings
Settings
Import
Note
:
Tolerance
Settings
Save Facet Data
Save Facet Data
Save Facet Data
Note
:
Save Facet Data
Settings
Storage
Settings
ZONE
Limit no. of import elements per ZONE
ZONE
Limit no. of import elements per ZONE
ZONE
ZONE
ZONE
Naming
Settings
GroupSets
Note
:
userPostProcess
TestModel
Logging


Use the Logging window to record the IFC Import process in a log file (the System automatically produces a log file).

Type
Specifies the level of content in the log file:
Brief - To the industry standard.
Full - To a level where problems can be isolated.
Location
Displays the Select log file window to navigate to the required log file.
Note:
The log file location field cannot be empty.
If required, specify a name and alternative location.
Note:
When the source file or folder is selected on the first page, a default file name is generated based on the source name. So the log file will be placed next to the source file or folder.
Type
Specifies the level of content in the log file:
Location
Displays the Select log file window to navigate to the required log file.
If required, specify a name and alternative location.
For further information, refer to Source.
Type
Specifies the level of content in the log file:
Brief - To the industry standard.
Full - To a level where problems can be isolated.
Location
Displays the Select log file window to navigate to the required log file.
Note:
The log file location field cannot be empty.
If required, specify a name and alternative location.
Note:
When the source file or folder is selected on the first page, a default file name is generated based on the source name. So the log file will be placed next to the source file or folder.
Brief - To the industry standard.
Full - To a level where problems can be isolated.
Brief - To the industry standard.
Brief - To the industry standard.
Full - To a level where problems can be isolated.
Full - To a level where problems can be isolated.
Note:
The log file location field cannot be empty.
Note:
When the source file or folder is selected on the first page, a default file name is generated based on the source name. So the log file will be placed next to the source file or folder.

Source
Logging
Type
Brief
Full
Location
Select log file
Note
:
Note
:
Source


The IFC model is imported into a flat structure, however, the IFC file contains structural information so that another view of the data may also be generated that better represents the IFC file.
The secondary IFC file hierarchy is created in the Group World (GPWL), using Group Sets (GPSET) and Group Items (GPITEM). Four data structures are created in the GPWL:
The reason for this apparent duplication is that the Flexible Explorer, which has a clearer presentation of the data than the Model Explorer is not available in PDMS 12.1. However the data in the Model Explorer can be viewed in PDMS 12.1 in a format similar to the Flexible Explorer but in a diminished mode called the IFC Flexible Explorer.

Currently there are four logical groupings that can be seen in the IFC Flexible Explorer:
Imported IFC files have a set of aggregate elements and set of spatial elements. A spatial project structure might define as many levels of decomposition as are necessary for the building project.

Elements within the spatial project structure are:
The spatial structure elements are linked together by a relationship object. If there are building elements and/or other elements directly related to the IfcBuildingStorey (like most building elements, such as walls, columns and so on), they are associated with the IfcBuildingStorey by using another relationship object.
A recursive hierarchy of GPSETs and referenced IFC elements contained in GPITEMs shows these relationships that exist in the imported IFC file.

Sorting elements according to their IFC class or group allows an alternative view of the data in the IFC Flexible Explorer. The model can be viewed and inspected according to the IFC class or group as well as using additional functionality available from the IFC Flexible Explorer right-click menu to highlight, unhighlight, add, remove, view attributes, rename or delete a given IFC class.

Use to highlight all the items of a given IFC class in the 3D view, for example: highlight all the IFCWallStandardCase imported from the IFC model.

Used to delete all the IFC elements or remove a specific IFC element.

Use to add or remove all items of a given IFC class or group to/from the 3D view, for example Remove all ifc roof elements from the 3D view.

Imported IFC elements might have an associated IFCPropertySet or sets which contain a set of IFCPropertySingleValue. The IFC Flexible Explorer will display each element's associated properties that are stored in data sets.
There are IFCQuantity elements also associated with elements, the interface imports these into data sets as well.
The property node name that appears in the IFC Flexible Explorer is a concatenation of the imported Property Name and Property Value (highlighted in red). Selecting an IFC element Property navigates to the equivalent element in the Model Explorer.

Use to display the Attribute window populated with all the attributes for the currently selected IFC class.

Use to rename the currently selected IFC element, the node name displayed in the IFC Flexible Explorer is based on the Function attribute value on the GPSET. Changing the GPSET Function attribute will change the node name in the IFC Flexible Explorer.

Use to highlight selected IFC entities in the 3D view.

Use to unhighlight selected IFC entities in the 3D view.

The IFC System Representation element contains a grouping based on the IFC system, providing an alternative view of the data in the IFC Flexible Explorer. The model can be viewed and inspected, right-click on IFC elements in the IFC Flexible Explorer to highlight/unhighlight, add, remove and view the attributes of the elements.

The Layer Hierarchy Representation element groups and displays data in a layer hierarchy in the IFC Flexible Explorer. The layers of the model can be viewed and inspected, right-click to highlight/unhighlight, add, remove or view the attributes of the layers. The layers can also be renamed or deleted (see below).

The imported IFC model can be viewed in Draw, if required, the hierarchy of the imported model and/or the IFC element type can be viewed, launch the IFC Flexible Explorer from the menu bar.

Use the functionality available from the IFC Flexible Explorer right-click menu in Draw to highlight/unhighlight, add or remove elements.
Use to add, remove, highlight or unhighlight IFC elements, provided the 3D View is active.

Use to view the attributes associated with IFC elements, the IFC imported model viewed in Draw is read only.

Use to create a plan view for a specific IFC class, type or a building storey by selecting elements in the IFC Flexible Explorer.

Navigate from the Model Explorer, 3D View or Drawing Sheet to the equivalent IFC Flexible Explorer node provided that its parent node is expanded in the IFC Flexible Explorer. Or navigate from the IFC Flexible Explorer to the equivalent element in the 3D view or the Model Explorer.
It is strongly advised against reordering the Hierarchical, Class Type representation or any logical grouping shown in the IFC Flexible Explorer. This is the representation of IFC model in the source file, and any kind of reordering will disrupt this representation and will probably result in a broken display.
Grouping in the IFC Flexible Explorer
IFC Hierarchical Representation
IFC Class or Group Representation
IFC System Representation
IFC Layer Hierarchy Representation
IFC Flexible Explorer in Draw
Special conditions for the IFC Flexible Explorer
Navigation Functionality
Reordering
Grouping in the IFC Flexible Explorer
Grouping in the IFC Flexible Explorer
IFC Hierarchical Representation
IFC Hierarchical Representation
IFC Class or Group Representation
IFC Class or Group Representation
IFC System Representation
IFC System Representation
IFC Layer Hierarchy Representation
IFC Layer Hierarchy Representation
IFC Flexible Explorer in Draw
IFC Flexible Explorer in Draw
Special conditions for the IFC Flexible Explorer
Special conditions for the IFC Flexible Explorer
Navigation Functionality
Navigation Functionality
Reordering
Reordering
One data structure to match the containment/decomposition hierarchy.
The next data structure to collect items according to their IFC class.
The next data structure to collect the items based on the System it is associated to.
Finally, the data structure to group items based on Layer or display the Layer Hierarchy.
One data structure to match the containment/decomposition hierarchy.
One data structure to match the containment/decomposition hierarchy.
The next data structure to collect items according to their IFC class.
The next data structure to collect items according to their IFC class.
The next data structure to collect the items based on the System it is associated to.
The next data structure to collect the items based on the System it is associated to.
Finally, the data structure to group items based on Layer or display the Layer Hierarchy.
Finally, the data structure to group items based on Layer or display the Layer Hierarchy.
IFC Hierarchical Representation
IFC Class or Group Representation
IFC System Representation
IFC Layer Hierarchy Representation
IFC Hierarchical Representation
IFC Hierarchical Representation
IFC Class or Group Representation
IFC Class or Group Representation
IFC System Representation
IFC System Representation
IFC Layer Hierarchy Representation
IFC Layer Hierarchy Representation
Site as IfcSite,
Building as IfcBuilding,
Storey as IfcBuildingStorey,
Space as IfcSpace.
Site as IfcSite,
Site as IfcSite,
Building as IfcBuilding,
Building as IfcBuilding,
Storey as IfcBuildingStorey,
Storey as IfcBuildingStorey,
Space as IfcSpace.
Space as IfcSpace.
Highlight/Unhighlight all items of a given IFC class or group
Delete IFC elements of a given IFC class or group
Add/Remove items of a given IFC class or group
View attributes of the currently selected IFC element
Rename a given IFC element
IFC entities in the 3D view
Highlight/Unhighlight all items of a given IFC class or group
Highlight/Unhighlight all items of a given IFC class or group
Delete IFC elements of a given IFC class or group
Delete IFC elements of a given IFC class or group
Add/Remove items of a given IFC class or group
Add/Remove items of a given IFC class or group
View attributes of the currently selected IFC element
View attributes of the currently selected IFC element
Rename a given IFC element
Rename a given IFC element
IFC entities in the 3D view
IFC entities in the 3D view
IFC Flexible Explorer Right-click Menu in Draw
IFC Flexible Explorer Right-click Menu in Draw
IFC Flexible Explorer Right-click Menu in Draw
3D View
Attributes
Quick View Creation
3D View
3D View
Attributes
Attributes
Quick View Creation
Quick View Creation
Navigation Functionality
Reordering
Navigation Functionality
Navigation Functionality
Reordering
Reordering
Note:
Selecting an IFC element from the IFC Flexible Explorer navigates to the equivalent element in the 3D view and to Model Explorer.
Note:
Renaming elements in the IFC Flexible Explorer operates on the GPSET/GPITEM hierarchy, and not on the initial imported data structure. Additionally, the configuration of the IFC Flexible Explorer might mean that the displayed name of the GPSET or GPITEM is not the actual name in the Model Explorer.

Flexible Explorer
Model Explorer
PDMS 12.1
Model Explorer
PDMS 12.1
Flexible Explorer
IFC Flexible Explorer
IFC Flexible Explorer
IfcSite
IfcBuilding
IfcBuildingStorey
IfcSpace
IfcBuildingStorey
IfcBuildingStorey
Note
:
IFC Flexible Explorer
IFC Flexible Explorer
IFC Flexible Explorer
IFCWallStandardCase
Remove all ifc roof elements from the 3D view
IFCPropertySet
IFCPropertySingleValue
IFC Flexible Explorer
IFCQuantity
IFC Flexible Explorer
Property
Model Explorer
Attribute
IFC Flexible Explorer
Function
Function
IFC Flexible Explorer
Note
:
IFC Flexible Explorer
IFC Flexible Explorer
Model Explorer
IFC Flexible Explorer.
IFC Flexible Explorer
IFC Flexible Explorer.
IFC Flexible Explorer
IFC Flexible Explorer
Attributes
IFC Flexible Explorer
IFC Flexible Explorer
IFC Flexible Explorer
IFC Flexible Explorer
IFC Flexible Explorer


The import process is performed using a PML object IFCImporterObj. The UI provides a front end to prepare and validate the data before initiating the import. It is recommended to use this functionality if a User wishes to import their framework.
The command line syntax for importing an IFC file or folder is illustrated in the "railtrack" diagrams below.
As it has been indicated in the UI, there are four steps to building up the command line:
When constructing the command line, there are more checks that have to be made in order to provide a valid command. These checks are made in the UI.
The full command is:

The individual components to this command are detailed below. As can be seen, certain parts can be bypassed. The implications of bypassing these parts are given.

The target element will be a SITE, under which a ZONE will be created for each IFC file to be imported. If this part of the syntax is not used, the current element is implied.
The IFC specific import options are as below, as can be seen from the diagrams above, these are optional components to the command line syntax.

Define the Reference Datum with the WRT or IN command component, the gid is a general PDMS element ID of a name or Reference Number.
The Group World that is to receive the GPSET's hierarchy is defined using the GPWL syntax component.
To rescale the imported model in a uniform scaling factor, use the SCALE syntax command.

Logging is performed using the syntax below.

A log file will be produced by default, the log file can be turned off. To produce a log file, select one of the options and provide a valid file path. If this is an existing file, it will be overwritten.

When GENPRIs are displayed, the prevailing value of REPRE DARCTOL is used for the facet tolerance (that is by default 10 mm in PDMS and 1 mm in AVEVA Everything3D). If a GENPRI is imported with an explicit CTOL value set (Save Facet Data set in the UI) then these facets will be cached inside the DB (Database).
The cached facets will only be reused for display if the desired REPRE DARCTOL is close enough (between a factor of 0.8 and 4.0 times CTOL); otherwise they will be ignored. The GENPRI's underlying data will be faceted again from scratch with the desired tolerance. These facets will be discarded after use: that is the cached facets in the DB will not be overwritten.
To work with lighter geometric data, by slackening off the tolerance, they must change DARCTOL for everything; and if the facet data was saved with an unsuitable CTOL, it will not be useful.
If the CTOL value is unset, a default value is taken depending on the arc tolerance settings at the time.

IFCImporterObj
WRT
IN
gid
SCALE
REPRE DARCTOL
CTOL
Save Facet Data
REPRE DARCTOL
CTOL
DARCTOL
CTOL
CTOL