AVEVA™ E3D Design
3D Interoperability Tools
Best Practice Guidelines
Henrik Hultin
Version 1.3, 28 August 2023
© 2023 AVEVA Group plc and its subsidiaries. All rights reserved.
AVEVA, the AVEVA logos and AVEVA product names are trademarks or registered trademarks of aveva group plc or its subsidiaries
in the United Kingdom and other countries. Other brands and products names are the trademarks of their respective companies.
AVEVA Group plc
High Cross, Madingley Road
Cambridge CB3 0HB, UK
Tel +44 (0)1223 556655
Fax +44 (0)1223 556666
aveva.com
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
PAGE 2 OF 36
Table of contents
1. ABOUT THIS DOCUMENT..................................................................................................................... 4
2. OVERVIEW OF AVAILABLE 3D IMPORT / EXPORT TOOLS ...................................................................... 5
2.1. PLANT 3D MODEL FEATURES ................................................................................................................ 5
2.2. MARINE 3D MODEL FEATURES ............................................................................................................. 7
2.3. PLANT & MARINE 2D DRAWING FEATURES ........................................................................................... 9
2.4. PLANT & MARINE ANALYSIS INTERFACES ............................................................................................ 10
2.5. MARINE SPECIFIC ANALYSIS INTERFACES ............................................................................................ 10
3. RECOMMENDED APPROACH FOR IMPORT OF MECHANICAL CAD MODELS FOR SINGULAR OR
COMPOSITE EQUIPMENT ITEMS............................................................................................................ 11
3.1. CONTROL OVER MODEL CREATION OR EXPORT FROM SOURCE TOOL .................................................. 11
3.2. NO CONTROL OVER MODEL CREATION OR EXPORT FROM SOURCE TOOL ............................................ 13
3.3. ALTERNATIVE APPROACHES ............................................................................................................... 14
3.3.1. Equipment templates ....................................................................................................................... 14
4. RECOMMENDED APPROACH FOR IMPORT OF 3D PLANT DESIGN MODELS ......................................... 15
4.1. CONTROL OVER MODEL CREATION OR EXPORT FROM SOURCE TOOL .................................................. 15
4.2. NO CONTROL OVER MODEL CREATION OR EXPORT FROM SOURCE TOOL ............................................ 16
5. RECOMMENDED APPROACH FOR IMPORT OF 3D MARINE/SHIP MODELS .......................................... 17
6. EXPECTATIONS FOR IMPORT OF MECHANICAL CAD AND PLANT DESIGN MODELS.............................. 18
6.1. MODEL SIZE AND SCALABILITY............................................................................................................ 18
6.1.1. General expectations and guidelines ............................................................................................... 18
6.1.2. Using Model Simplification............................................................................................................... 20
6.2. CONVERTED MODELS ......................................................................................................................... 25
6.3. BEHAVIOR OF IMPORTED MODELS – GEOMETRY & MODELLING ......................................................... 25
6.3.1. General ............................................................................................................................................. 25
6.3.2. Use of Graphical Explorer ................................................................................................................. 28
6.3.3. Piping? .............................................................................................................................................. 28
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
PAGE 3 OF 36
6.3.4. Structural .......................................................................................................................................... 28
6.3.5. Cabling .............................................................................................................................................. 28
6.4. METADATA ........................................................................................................................................ 29
7. SPECIFIC RECOMMENTATIONS FOR DIFFERENT FILE FORMATS AND IMPORT TOOLS .......................... 30
7.1. IMPORT OF STEP, STL, IGS FILES AND NATIVE MECHANICAL CAD FORMATS ......................................... 30
7.1.1. MEI Import: STEP Files ...................................................................................................................... 30
7.1.2. MultiCAD Import: STEP Files & Native Mechanical CAD formats ..................................................... 30
7.1.3. STL and IGS Files ............................................................................................................................... 31
7.1.4. Model Simplification......................................................................................................................... 31
7.2. IMPORT OF IFC FILES .......................................................................................................................... 32
7.3. EXPORT OF IFC FILES .......................................................................................................................... 32
7.4. IMPORT OF DGN FILES ........................................................................................................................ 34
7.5. IMPORT FROM / EXPORT TO STRUCTURAL DESIGN ............................................................................. 34
7.5.1. Import from TEKLA ........................................................................................................................... 34
7.5.2. Export to TEKLA ................................................................................................................................ 35
7.5.3. BOCAD and E3D Structural Design ................................................................................................... 35
8. USE OF IMPORTED MODELS IN DRAWINGS ....................................................................................... 36
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
PAGE 4 OF 36
1. About this Document
This document aims to provide guidance to users of AVEVA E3D Design on how to best use the various 3D model
Import / Export tools. This includes:
1. An overview of the various tools available and for what use cases which tools is best suited, e.g. when to
use which tool.
2. Scalability expectations & recommendations, what model size / complexity that can be imported and how
this may affect the performance of the application, as well as how to work around this for larger models.
3. Some more specific guidance on how to best prepare models for import, and how to best use each tool.
While such guidance is provided, this document is really a complement to existing User Guides, and does not
provide all the detailed information about how to use each tool.
PAGE 5 OF 36
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
2. Overview of available 3D Import / Export Tools
2.1. Plant 3D Model Features
The below tables outline the relevant features for process plant design projects.
Plant 3D Model Import Features
Feature
Purpose
Input Formats
E3D Design
Format
Mechanical
Equipment
Interface and
STL
MultiCAD
Import
Vendor equipment import
STP, STL, SAT, IGES, XYZ
GENPRI
Vendor equipment and plant
model import
GENPRI +
Hierarchy & Data
Model
Simplification
Vendor equipment import
with simplification
Around 30 Native CAD formats. See the
User Guide and Release Notes for more
details on exact versions.
1) STP
2) A range of native CAD formats
IFC
Plant model import for
referencing and coordination
IFC 2X3 and 4
GENPRI +
Hierarchy & Data
CADENAS –
3DfindIT.com
Equipment import from
vendor catalogue
N/A
3D DGN
Vendor equipment and plant
model import
DGN
Standard Model
Library Equipment with
Native Primitives
POLYHE, POGO,
(GENSEC)
2D DWG/DXF
2D plant layouts / overlays for
3D modelling purposes
Steel Detailing Import
DWG/DXF
Aid elements
Steel Detailing Neutral File (OSDE)
SCTN, GENSEC,
PANEL
SCTN, GENSEC,
PANEL
Workpack
hierarchy
Native piping
elements
Native E3D Terrain
Surface
Elements &
Attributes
Native AVEVA E3D
Catalogues and
Plant models
SDNF
E3D Structural Steel Detailing Import
Design / Bocad
Work Packs
Import of WorkPacks
ABSI
PCF (E3D 4.0
onwards)
Terrain
Import of Pipe Spools
PCF
Import of terrain models
IGES, STEP, STL and XYZ
Excel
Import of Excel files
CSV, XLS, XLSX
(Intergraph
S3D / PDS)
Import of catalogues and plant
models.
S3D / PDS project data (project backup)
Excel file
GENPRI + Limited
Hierarchy & Data
PAGE 6 OF 36
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
Note: This is not an import
feature, but rather a
conversion service. Not
included in standard product delivered as a service.
Plant 3D Model Export Features
Feature
Purpose
Export Formats
IFC
Plant model export for referencing and
coordination
IFC 2X3 and 4
MEI
Plant Model export
STP, SAT, XGL
Review Model
Visualization and viewing
RVM
DGN
Plant Model export
DGN v7
DXF
Plant Model export
3D DXF
SDNF
Steel Detailing Neutral File (OSDE)
SDNF
IDF
ISODraft - Pipe spool export
IDF
E3D Structural Design /
BOCAD
Steel detailing export
ABSI
(Intergraph S3D)
Conversion of catalogues and plant models.
S3D native project data
Publish to AIM
Note: This is not an export feature, but
rather a conversion service. Not included in
standard product - delivered as a service.
Publish to AVEVA Asset Information
Management
EIWM and ZGL/XGL
PAGE 7 OF 36
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
2.2. Marine 3D Model Features
The below tables outline the relevant features for marine / shipbuilding projects.
Marine 3D Model Import Features
Feature
Purpose
Input Formats
E3D Design
Format
Surface Manager
Import of Hullform Surfaces
STP, SAT, IGS, DML
E3D Hull Surface
NAPA Import
1) Internal surfaces (decks,
bulkheads)
2) Compartments
Vendor equipment import
NAPA Surface Definition File
Format, STP, IGS
Polyface
Space
STP, STL, SAT, IGES, XYZ
GENPRI
Vendor equipment model
import
Around 30 Native CAD formats.
See the User Guide and Release
Notes for more details on exact
versions.
1) STP
2) A range of native CAD formats
GENPRI +
Hierarchy & Data
Mechanical Equipment
Interface and STL
MultiCAD Import
Model Simplification
Vendor equipment import
with simplification
IFC
Model import for
referencing and
coordination
Equipment import from
vendor catalogue
IFC 2X3 and 4
GENPRI + Limited
Hierarchy & Data
N/A
Vendor equipment and
outfitting model import
2D ship layouts / overlays for
3D modelling purposes
Steel Detailing Import
DGN
Standard Model
Library Equipment with
Native Primitives
POLYHE, POGO,
(GENSEC)
Aid elements
E3D Structural Design /
Bocad
Work Packs
Steel Detailing Import
ABSI
Import of WorkPacks
Excel file
PCF (E3D 4.0 onwards)
Import of Pipe Spools
PCF
Excel
Import of Excel files
CSV, XLS, XLSX
CADENAS –
3DfindIT.com
3D DGN
2D DWG/DXF
SDNF
DWG/DXF
Steel Detailing Neutral File (OSDE)
GENPRI + Limited
Hierarchy & Data
SCTN, GENSEC,
PANEL
SCTN, GENSEC,
PANEL
Workpack
hierarchy
Native piping
elements
Elements &
Attributes
PAGE 8 OF 36
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
Marine 3D Model Export features
Feature
Purpose
Export Formats
Surface Manager
Export of Hullform Surfaces – Hull only
STP, SAT, IGS, DML
IFC
Model export – Outfitting only
IFC 2X3 and 4
MEI
Model export – Outfitting only
STP, SAT, XGL
Review Model
Visualization and viewing – Hull & Outfitting
RVM
DGN
Ship Model export – Hull & outfitting
DGN v7
DXF
Ship Model export – Hull & Outfitting
3D DXF
SDNF
Steel Detailing Neutral File (OSDE) –
Outfitting Structures only
Steel detailing export – Outfitting Structures
only
Conversion of catalogues and outfitting
models.
Not included in standard product delivered as a service.
Publish to AVEVA Asset Information
Management – Hull & Outfitting.
Transfer the hull basic design model to
AVEVA Marine 12 series – Hull only.
Export hull design model as XML to third
party software - Hull only.
SDNF
E3D Structural Design /
BOCAD
(Intergraph S3D)
Publish to AIM
Transfer to AVEVA Marine
Export Hull Steel XML
ABSI
S3D native project data
EIWM and ZGL/XGL
Schema file + native DB
transfer
XML
PAGE 9 OF 36
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
2.3. Plant & Marine 2D Drawing Features
The below 2D drawing import/export features are applicable both for process plant as well as marine shipbuilding
projects.
Plant & Marine 2D Drawing Import Features
Feature
Purpose
DWG / DXF
Import 2D drawings,
DWG / DXF
backing sheets and symbol
templates
Bitmap images can be
Bitmap
added to drawings by
Copy/Paste
Add Excel tables etc to
MS Excel file
drawings
Image files
MS Excel
Input Formats
E3D Design Format
Native E3D Draw format
Bitmap embedded in
drawing
Image of excel file
embedded in drawing,
Excel file can be opened
by double click
Plant & Marine 2D Drawing Export Features
Feature
Purpose
Export Formats
DGN Export
Export of drawings in DGN format
DGN
DWG / DXF Export
Export of drawings in DWG and DXF format
DWG / DXF
PDF Export
Export of drawings in PDF format
PDF
SVG Export
Export of drawings in SVG format
SVG
Bitmap Export
Export of drawings in a raster image format
PNG, JPEG, IFF, BMP, GIF
AVEVA Plot File Export
(e.g. ISOs)
Export of drawings in AVEVA Plot File
Format – for historical compatibility only
AVEVA Plot File
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
PAGE 10 OF 36
2.4. Plant & Marine Analysis Interfaces
The below analysis features are applicable both for process plant as well as marine shipbuilding projects.
Plant & Marine Analysis Features
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
- For structural discipline in plant design projects
- For outfitting steel discipline in marine shipbuilding projects
2.5. Marine Specific Analysis Interfaces
The below analysis features are applicable only for marine shipbuilding projects.
Marine Specific Analysis Features
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 etc. (Hull only)
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
PAGE 11 OF 36
3. Recommended Approach for import of mechanical
CAD models for singular or composite equipment
items
This section covers import of singular equipment items such as pumps, centrifuges, heat exchangers etc.
as well as composite or more complex models such as processing modules, skids, cranes or conveyor
arrangements.
For these kinds of objects there are two main use cases, as follows:
3.1. Control over model creation or export from source tool
This case is where the E3D Design user has control over or can influence 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.
Recommendations:
•
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.
o
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.
o
For Autodesk Inventor specifically:
1. 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.
2. 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. For example, there is often a
requirement to be able to identify individual tagged objects further downstream in the
information chain. Even if a complex module might be acceptable to handle as a single unit
during the design of the plant, the OO typically wants to be able to identify the main tagged
components within. This is often more achievable when importing the model in pieces than as
one huge model.
•
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.
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
PAGE 12 OF 36
•
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:
•
o
This function typically provides better results with B-rep solid models that are not prejoined or shrinkwrapped.
o
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 advice 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 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 picture above 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.
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
PAGE 13 OF 36
3.2. No control over model creation or export from source 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 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.
Recommendations:
•
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.
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
PAGE 14 OF 36
3.3. Alternative approaches
3.3.1. Equipment templates
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.
This approach is particularly suitable:
•
Where the original CAD models are unnecessarily complex and may cause significant
performance issues if imported
•
Where the level of detail in E3D Design is not required to be especially high
•
Where the model has several small nozzles of interface points that need to be correctly
represented and that may be lost if model simplification is being used
•
Where several similar CAD models are to be imported and an equipment template can easily be
instantiated into several equipment instances using different parameter values
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
PAGE 15 OF 36
4. Recommended Approach for import of 3D Plant
Design models
This can be entire plant layout models, or parts of such models including equipment items, piping,
structure, cableways etc. to be 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.
Again, there are two different cases here:
4.1. Control over model creation or export from source tool
This case is where the E3D Design user has control over the creation and export of the plant models from
the authoring tool, for example where the plant was originally designed in-house and the original project
data and authoring tool is still available for use.
Recommendations:
•
When large models are to be imported, it is more manageable to break them up into pieces and
import each piece by itself, rather than trying to import it all as one single large file. This can for
example be done by area or discipline. Consider the final deliverables to help determine the
original model separation, for example tagged items that should be separately identifiable
•
Where possible, try to reduce the level of detail of exported models to a suitable level for what is
needed in E3D Design
•
The above advice 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.
•
It may be tempting to use Model Simplification to import complete plant models to E3D Design,
bt in most cases this won’t work when the plant models are too big. The Model Simplification
feature is adapted to being used on models of a reasonable size. See recommendations for
importable model sizes under 6.1 Model Size and scalability.
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
PAGE 16 OF 36
4.2. No control over model creation or export from source 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.
Recommendations:
•
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.
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
PAGE 17 OF 36
5. Recommended Approach for import of 3D
Marine/Ship models
The marine hull model can contain topological relations which needs to be taken into account when importing.
This can be achieved by importing dependent model elements first.
Importing or creating dependent model elements in E3D in advance such as Ship Grid and Mainhull Surface of
a Ship is highly recommended.
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
PAGE 18 OF 36
6. Expectations for import of mechanical CAD and
plant design models
6.1. Model Size and scalability
6.1.1. General expectations and guidelines
Importing large CAD models can significantly degrade the performance of many E3D Design functions,
such as Add-to-drawlist, 3D view navigation and manipulation, clash checks, and 2D drawing views of the
model. It may also affect data transfer / synch latency times for Global and Spectrum.
For this reason it is important to stay vigilant and avoid imports of too large / too many models, and to
adhere to the best practice guidelines where such imports can not be avoided.
It is difficult for AVEVA to provide any detailed recommendations on size, because the performance
impact on the E3D Design users will be affected by many different factors, such as hardware and
networks used, as well as the properties of the individual model. This means that some “large” models
may import and perform well, while smaller ones may cause performance issues.
This means that it is not possible to provide concrete guidelines on size limits of importable models, but
as a rule of thumb the following recommendations for different size ranges could be considered when
planning for importing CAD models to E3D Design.
AVEVA recommends making tests to establish the best approach for the individual project requirements.
Models up to around 10MB
•
Models of this size seldom cause any performance issues and can normally be freely imported in
full detail.
•
In case very many instances of these models will be used in the project, it could still be
considered to use Model Simplification to optimize the performance.
Models from around 10MB up to a few hundred MB
•
Some care should be applied when importing models in this size range. Some models imported in
full detail may work well without too much of a performance impact, but there can be cases of
scalability issues, especially if many models of this size range are to be imported into the project.
•
Where applicable, it should be considered to use Model Simplification to reduce the size of the
models and improve performance.
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
PAGE 19 OF 36
Models of many hundred MB size
•
For models of this size range, careful consideration should be applied to try and reduce the size
before importing, for example by using the Model Simplification tool.
•
If there will only be a handful of models of this size in the project, it could still work OK to import
and use these in full derail. But if there will be many models of this size it may become
unmanageable.
•
The alternative method of Equipment Templates as described above should also be considered.
•
If it is still decided to import models of this size, then AVEVA recommends to carefully test
performance of different E3D Design features while handling these models before introducing
them into the project for all users.
Models larger than 1GB
•
It is generally not recommended to import such large models to E3D Design because this will
quite often have a very notable negative impact on performance, and may in some cases make
the application unusable.
•
For such large models, it is highly recommended to break them down into smaller chunks before
separately importing each one.
•
This can be combined with using Model Simplification on each part or even considering the
alternative methods such as equipment templates mentioned above.
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
PAGE 20 OF 36
6.1.2. Using Model Simplification
When using Model Simplification to import CAD models, it should be expected that the import process
takes longer time due to the processing needed for simplification. The processing time is highly variable
depending on the model properties etc, but can be expected to take around 10x longer than importing
the fully detailed model through MultiCAD.
However, there will typically be a significant improvement in add-to-drawlist time, clashing, creation of
drawing views and other operations that involve processing of the imported geometry. Again the
improvement will be variable depending on model properties, simplification settings etc, but can often
give a 10x or more performance improvement, and this factor often increases as models get larger as can
be seen in the second picture below.
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
PAGE 21 OF 36
Please note that the results from Model Simplification may vary. Models that are badly connected or presimplified will usually not give as much improvement as others. Some models containing a lot of open
bodies may not give any significant performance improvement at all. Please see recommendations under
3.1 Control over model creation or export from source tool on how to obtain models most suitable for
simplification.
PAGE 22 OF 36
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
Here are a few example screenshots from a model suitable for simplification where the performance can be
significantly improved without affecting the visual fidelity too much.
Add to Drawlist me 3 s
Mul AD
Import
mport of fully
detailed model
Add to Drawlist me s
Model
Simpli ca on
mport of
simpli ed model
Mul
AD Import
Model Simpli ca on
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
PAGE 23 OF 36
PAGE 24 OF 36
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
Mul
AD Import
Model Simpli ca on
Mul
AD Import
Model Simpli ca on
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
PAGE 25 OF 36
6.2. Converted 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.
6.3. 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.
6.3.1. General
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 etc.
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 etc.
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.
One thing to note is that the dynamic snapping that is enabled by default may not work vey well on
imported models, as the application will try to dynamically identify snapping points when you move the
cursor over the model. With imported models containing large amounts of geometry elements this may
take a long time, for instance while taking measurements, and give the appearance of the mouse cursor
“lagging” as it is moved across the model. For this case it is recommended to disable the dynamic
element snapping and only enable when needed. For large models it may work best to zoom in closely
before enabling the element snapping, thereby reducing the amount of objects that the mouse will pass
over.
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
PAGE 26 OF 36
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
PAGE 27 OF 36
Another opportunity to optimize the performance of mouse movements can be to minimize the size of
the snapping aperture while working with large imported models. The size of the snapping aperture can
be adjusted in the backstage options page: File → Options → View → Selection and Snaps.
This will result in a smaller set of geometry being analyzed as the mouse moves over the model in the 3D
canvas.
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
PAGE 28 OF 36
6.3.2. Use of Graphical Explorer
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.
6.3.3. Piping
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 objects, 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.
6.3.4. Structural
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 primities.
6.3.5. Cabling
The procedure for connecting electrical cables for powering and control to equipment items that have
been imported is the same as for equipment items that have been natively modelled in E3D.
Users will have to create and place ELCONNs for the EQUI, to which the cables can later be connected.
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
PAGE 29 OF 36
6.4. Metadata
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.
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
PAGE 30 OF 36
7. Specific recommentations for different file formats
and import tools
7.1. 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
etc.
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 see 6.1
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.
Below is some more specific information about using each of the features for STEP files.
7.1.1. MEI Import: STEP Files
•
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.
7.1.2. MultiCAD Import: STEP Files & Native Mechanical CAD formats
•
MultiCad imports the full assembly hierarchy (as an E3D Design secondary hierarchy visible in the
MultiCAD Explorer). It does not name imported E3D Design elements, but does set descriptions.
It will do faceting of curved objects on import and it also imports metadata.
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
PAGE 31 OF 36
7.1.3. STL and IGS Files
•
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 foprmat if possible.
•
The terrain import continues to use the MEI import for these file types.
7.1.4. Model Simplification
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 check 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.
Please also see recommendations under 3.1 Control over model creation or export from source tool on
how to obtain models most suitable for simplification.
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
PAGE 32 OF 36
7.2. Import of IFC files
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.
1) IFC Import
•
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 there are requirements that go beyond the capabilities of the standard IFC
Import process, there is an opportunity to customize the process by using PML Objects. For
more information, see How to customize ifc import and export processes (aveva.com)
2) MultiCAD Import
•
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.
Transfering models from Autodesk Revit:
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.
Please also see the following documents that provide guidance on how to best prepare and export
models from Revit:
1) Suggested way to export model from Revit to E3D
2) Limiting number of elements exported from Revit to E3D, using Revit IFC interface
7.3. Export of IFC files
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.
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
PAGE 33 OF 36
Please refer to the IFC Export User Guide for more detailed recommendations of what settings can be
used etc.
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
PAGE 34 OF 36
7.4. Import of DGN files
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.
7.5. Import from / export to structural design
7.5.1. Import from TEKLA
There are several methods available to import structural design data from TEKLA. The main options are
outlined below 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 sch 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 Tekla 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.
Tekla Structures offers a number of Export Type options, see for example:
https://teklastructures.support.tekla.com/2019i/en/int_exporting_into_ifc
We recommend to use the "Surface geometry" option (for IFC 2x3) or "Reference View" (for IFC4) options
in Tekla to give the best results when the file is imported into E3D.
It is also important to do the IFC export from Tekla in a suitable scope per IFC file, it is better to export in
several smaller files than all in one big file. For example to create one IFC export file for each framework
in Tekla. This will allow to import each file in E3D under different owners, which will provide a more
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
PAGE 35 OF 36
meaningful navigable hierarchy in E3D, and will also avoid getting too many members within a certain
owner which could otherwise affect the performance in E3D, 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 Interoperability
TEKLA also offers a bespoke interoperability feature that can be used to transfer data to E3D. More
information can be found here:
https://support.tekla.com/doc/tekla-structures/2020/int_pdms_e3d
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.
7.5.2. Export to TEKLA
Here we also have the options to use either SDNF, IFC or TEKLA Interoperability, and the resulting model
in TEKLA will have to be assessed to determine which method gives the best results.
7.5.3. BOCAD and E3D Structural Design
When importing from / exporting to BOCAD and AVEVA E3D Structural Design, the E3D Structural Design
(ABSI) interface will give the best results.
AVEVA™ E3D Design - 3D Interoperability Best Practice Guidelines
PAGE 36 OF 36
8. Use of imported models in Drawings
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 your views and preparing the
drawings, and then swith to Global Hidden Line as you finalize the drawings.
•
The edge representation and DUNION attribute for civil drawings works best when using the IFC
Import.