M323879

Setup Plant 3D to meet your BIM requirements

Peggy Lin
AECOM

David Manning
Autodesk

Learning Objectives
 Learn about how Plant 3D works inside out, the relationship between each
modules of Plant 3D, how they worked together;
 Learn about best practices, the Dos and the Doesn’t when you customize your
P&ID settings and the creation of catalogues. What you should do with your spec
and its update;
 Learn about customization of the database and your catalogues and specs;
 Setup Plant 3D to satisfy your project BIM requirements

Description
More and more projects nowadays have Building Information Modelling (BIM) or Digital
Engineering (DE) requirement. Asset owners realize the value of BIM or DE in asset
management. Employee Information Requirement (EIR) or Property Data Building Block (PDBB)
are given to you, it is expected that the submitted models contain the required information. This
class will introduce you on how Plant 3D works and how you can set it up correctly to achieve this
goal. I will first provide an overview to Plant 3D, then discuss about general Plant 3D
customization topic with some highlights, finally I will discuss methods to achieve your EIR or
PDBB requirements on the project.

Page 1
Speaker(s)
Peggy Lin is a Digital Engineering Technology Specialist
for AECOM ANZ. She works out of the AECOM Sydney
office in Australia. She is a BIM and technology evangelist
with 15 years of experience establishing BIM workflows
and standards around content, training and
interoperability. Her experience spans over multiple
discipline projects including water, highway and rail. She is
familiar with multiple software packages including Civil 3D,
Revit, Plant 3D, Inventor, Navisworks, Infraworks and 12D.
Teamed up with her capability on programming in C# and
dynamo enables her to create seamless workflow and
implement BIM collaboration workflows in various civil
infrastructure projects.

[email protected]

Page 2
Table of Contents
Introduction .................................................................................................................................................. 5
Plant 3D Overview ........................................................................................................................................ 5
About Plant 3D .......................................................................................................................................... 5
SQLite Database ........................................................................................................................................ 5
Plant 3D modules ...................................................................................................................................... 6
P&ID module ......................................................................................................................................... 7
Plant 3D Model module ........................................................................................................................ 7
Orthographic Drawings module ............................................................................................................ 7
Isometric Drawing module.................................................................................................................... 7
Plant 3D Advantages ................................................................................................................................. 7
Plant 3D Limitations .................................................................................................................................. 8
Plant 3D Customization............................................................................................................................... 10
XML files .................................................................................................................................................. 10
P&ID Customization ................................................................................................................................ 11
Plant 3D model Customization ............................................................................................................... 12
Pipe Number Setting ........................................................................................................................... 12
Isometric Customization ......................................................................................................................... 12
Catalogue Creation ................................................................................................................................. 13
What is Python? .................................................................................................................................. 16
How each module all sings together? ..................................................................................................... 17
BIM & Plant 3D............................................................................................................................................ 20
BIM .......................................................................................................................................................... 20
Data, Data, Data ...................................................................................................................................... 20
Implement EIR in Plant 3D ...................................................................................................................... 21
Model Quality ......................................................................................................................................... 22
Model Presentation ................................................................................................................................ 23
The Math behind the sense: ............................................................................................................... 24
What do you use Data for? ..................................................................................................................... 26

Page 3
Page 4
Introduction
Building Information Modelling (BIM) has two important aspects. As stated in the name, it is
Information and Model. Plant 3D is one of software that provides you means to create both model
and information at the same time. Plant 3D is an AutoCAD based software, it can be quite easily
learned if one has used AutoCAD before. The typically learning class for Plant 3D is three days.
However, to really understand and customise it properly, you need to understand the key of Plant
3D really is the way it manages data. 3D model is just a media that presents and carries data as
you would like it to be.

Plant 3D Overview
About Plant 3D
Plant 3D has been designed from the ground up specifically for process plant design. It use spec
driven piping technology, with auto-routing and a configurable branch table to enforce your design
standard. Piping is flexible and its auto routing capability make your modelling easy. You get Iso’s
created out of box. Plant 3D allow you to configure pretty much every aspect of your design and
output needs. It is very versatile and powerful. Plant 3D allow you to create catalogue item via
few different methods. It is easy to create a lot of catalogue items in relatively short period of time.

On the other hand, as it is very versatile, it does require you to invest some time on setting it up
in the first place. Therefore, it is important to understand the software and how to use it.

From data storage point of view, Plant 3D is very flexible, it supports SQLite and SQL server. If
you use SQLite as the method for data storage, it makes project rather contained. It means that
it can locate your network drive without the needs of setup servers. The downside of this is that
due to the nature of SQLite, you should not have more than three people read/write to project at
the same time. For more than three people in a project, you should use SQL server. Plant 3D
make the migration from SQLite to SQL server simple and easy.

From collaboration point of view with other parties, there are solution like Vault and BIM 360
TEAM that enables collaboration over different locations.

SQLite Database
What is the SQLite Database? According to SQLite official website: “The SQLite is a C-language
library that implements a small, fast, self-contained, high-reliability, full-featured, SQL database
engine. It is the most used database engine in the world. SQLite is built into all mobile phones
and most computers and come bundled inside countless other applications that people use every
day.”

There are many characters for SQLite database, the one that make Plant 3D easy to implement
is the self-contained. However, the downside of it is not designed for many users. It is perfect for
small projects. It is however easy to immigrate to SQL server if it comes the time that project
grows.

More readings:
SQLite: The Database at the Edge of the Network with Dr. Richard Hipp
Tools for browsing the data directly: https://sqlitebrowser.org/dl/

Page 5
Understanding AutoCAD Plant 3D and P&ID Database Operations

You can query data directly from SQL server via excel, refer to this document.

Plant 3D modules
Plant 3D has four modules including P&ID, 3D models, orthographic and isometric. Doesn’t matter
what data storage method you choose, generally each module has its own database and it is not
linked. The data structure is different to suit different needs for each module. You can see this
under the Plant 3D project folder.

Here we use a project setup using SQLite database as example. There five .dcf files saved under
project folder.

As you can see the name of these files are self-explanatory except
the ProcessPower.
 Iso.dcf file is the database for Isometric module;
 Ortho.dcf file is for orthographic module;
 Piping.dcf is for 3D models module, and
 the ProcessPower.dcf is for P&ID module.
Fig 1. Plant3D databases

When you use the collaboration system like BIM360 & Vault, it creates the local version of these
files in your machine. Then sync the differences with the database on BIM360 as design changed.

Fig 2. Autodesk Vault Plant Collaboration map

Page 6
 P&ID module
P&ID looks simple, however it is the most delicate and complicated module in Plant 3D
when it comes to customization and also drafting. It is a task that you need to plan it
carefully and have super clear picture of what outcome are to be achieved; how many
attributes are required; as well as what class of the object data that you need the output
for. I would suggest that you communicate with process engineers even clients to
understand the schedules that you need to create before you start doing customization.

Typically, this is a one-off exercise for one client standard. You might have to do minor
adjustment to it on the project bases, but you don’t need to redo it if you did it right.

Plant 3D Model module

Compare with P&ID, Plant 3D model module is much easier to deal with and can be very
forgetful. However, to create a good quality model, one does need to have good modelling
habit. You will need to pay attention to the spec creation as they are the key to enforce
the standard.

From customization point of view, you would like to make sure that the P&ID mapping to
Plant 3D model is done properly and the object tagging is set up as required.

Orthographic Drawings module

Orthographic drawings setting is the simplest one. It includes the layer mapping, BOM
data mapping. To gain the efficiency, similarly with P&ID, use object tagging as much as
possible. It is also customizable and can display the data from the object itself as needed.

Isometric Drawing module

Isometric module creates piping iso automatically and based on line number.

To create the isometric drawings successfully, it is important to consider the following:

 Catalogue/spec should be done correctly with SKEY and object type;
 Iso Symbol must be mapped and associate correctly with model item;
 Model must be done correctly, which means that the pipe is tagged, and model
elements must be connected without breakage; and
 Required iso symbol are in the place.

Plant 3D Advantages
The high Customizability is the best part of Plant 3D. You can customize the Plant 3D from few
different directions:
 Data structure and object classification: In P&ID module, Plant 3D allow you to add
and delete subclass under its base classification. It also allows you to add and delete the
properties in any level of classification. The inheritance of the properties from the parent
class to the child class is really the great feature. In both P&ID and Plant 3D module, you
can add custom properties to any object class as needed.

Page 7
 Smart annotation in Drawing production: In both P&ID and Ortho module, the smart
annotation functionality reads the data stores in the object and present it to you in the
format you defined. This is very powerful and provide you the means to check your data
visually and ability to update the drawing via excel which takes away the risk of double
data handling. What you see is what you designed.
 Standardize the look and feel of drawings for a project: The annotation styles seats in
project setting level, so when you change the look and feel of your annotation, it will sync
to all the drawings that you created.
 Tag concatenation: Tag concatenation is the great feature and I wish Revit has this. This
method of concatenating multiple properties to form a tag and check the uniqueness
against the concatenated tag reflects the fundamental of data decupling and is the
foundation for Plant 3D to be able to adopt to any client stands.

Plant 3D Limitations
 DWG format is the first limitation that you need to be aware particularly when it comes
dealing with big data. It is important to make sure the models are breakdown enough and
ensure that the model not exceeding the 10M threshold. Few things that you want pay
attentions under this category would be:
o Do not use high level details CAD block as custom part;
o Make sure you dump down the details of equipment if you get an equipment
model from manufacture as they typically created in SolidWorks or Inventor and
alike. Which usually contains a lot of voids, nut/bolts, detail faces. If it is not clean
up properly before imported, Plant 3D doesn’t like it and will take long time to
create ortho.
With the Plant 3D 2018 and above, you might not feel much of the pain during your 3D
modelling phase even when single model exceeding 20M. But when you start your Ortho
drawing production, it will take huge amount of time.

 Data verification/checking is not in its best. Plant 3D Validation tool does provide a
great list of checking item, as image shown below:

Fig 3. 3D Model to P&ID checks

After done, it provides you an interface which show the result and provide the links to the
item that has issues. However, it doesn’t save it in a database and can only be export to
a text-based file. So if you don’t address the issue right after you run the check. If you

Page 8
restart your project, you will have to re-run the check again. And it checks everything so if
you have a lot of models and P&ID to check, it will take you for long time. What I turn to
do is to export the P&ID data and Plant 3D model data as excel and check it from there. I
setup a template in Excel to do this cross checking and save it as track record evidence
for model QA.

Fig 4. 3D Models to P&ID checks result interface

Page 9
Plant 3D Customization
As discussed previously, Plant 3D supports pretty much all your needs on the customization. You
can modify the object classification to a limit within P&ID module. You can create a pick list as
needed to be used in everywhere of project to enforce your naming convention or data entry. You
can customize all your tagging to look the way your preferred and reading mostly any data that
you can have in the project. And more.

XML files
XML stands for eXtensible Markup Language, is a markup language that defines a set of rules
for encoding documents in a format that is both human-readable and machine-readable. It is a
build on open standard. The design goals of XML emphasize simplicity, generality and usability
across the internet.
In Plant 3D, xml files are running in background and used to either save the settings you chosen
in UI. Without enough knowledge for both xml and Plant 3D, do not try to make changes
manually to it. They are used every parts of Plant 3D module and as media to tell the other
module of Plant 3D how to react properly.
There are two types xml files in Plant 3D projects, one tells Plant 3D where the project modules
are, and the one store the configuration data that Plant 3D needs.
Mapping out Plant 3D modules Project settings
 PIP_Metric_PnIdPart.xml  DefaultConnectorsConfig.xml
 MiscPart.xml  PIDTo3dClassMapping.xml
 Metric_PipingPart.xml  PIDToSpecClassMapping.xml
 Metric_OrthoPart.xml  ProjectSetupSpecUpdateSettings.xml
 IsoPart.xml  SubstitutionPalettes.xml
 Project.xml  And some more for report templates,
import/export settings and isometric
settings

Page 10
P&ID Customization
There are four base classes. They are Engineering
Items, Non Engineering Items, Pipe Line Group
and Signal Line Group.

As all of classes are in database, theoretically you

should be able to schedule all of them if you wish.
However, from Plant 3D interface, you can only
create schedules for the following items as excel so
that you can export/import data
 P&ID drawings
 Equipment
 Instrument
 Line
 Nozzle
 Specialty Items
 Valve
 Control Valve

The tricky one is Control Valve, as it is a special

Fig 5. P&ID Class Definition class that falls under Instrumentation Inline
Instrument; This class has special behavior, you
must not touch is Symbol definition.

From scheduling point of view, you need to be aware

that it will also be presented in Instrument List unless
you filter it out.

You can also use report creator to create report

directly from database.

The key points:

 One character of P&ID Class Definition is the child class will automatically inherit the
setting of the parent class. But if you make changes to it, the automatic inherit will break
forever and cannot be reversed. Start from a brand new project, and make sure change
only on the parent level unless it is unique from one class to the other, avoid making any
changes on child level as much as you can. For example, you will modify the Type code
in Ball Valve class to be “BLV”, and Check Valve class to be “CKV”, but the
TagFormatName should be both as “Hand Valve Tag”. In this case, you will assign the
tag format in “Hand Valves” class level, then modify the Type code in Ball Valve and Check
Valve class respectively.
 Use Annotation to present you data in P&ID as much as possible. It is the great way to
enforce your CAD standard and make sure the information in the drawings are consistent
with object data. It is also the best way to save your time when it comes to standard update.

Page 11
Plant 3D model Customization
Layer and Color Settings:
I found it is better to use the following setting, due

to the following reason:

 Ability to visually check if pipeline are tagged with a
line number;
 Easier to manage the CAD layer colors when create
ortho drawings

P&ID Object Mapping

This is the setting provides the “linkage” between P&ID
class definition and Plant 3D Class Definition. If done
correctly, it reads the data from P&ID database and inject it
into Plant 3D model database. You need to understand
Fig 6. Plant 3D Drawing Settings there is no linkage between two databases.

Pipe Number Setting

This is another topic needs a lot of attention. As descripted ………………
Please refer to this document.

More reading: Tailoring AutoCAD P&ID and AutoCAD Plant 3D

Isometric Customization
From the version 2018 onwards, a lot of customisations can be performed from the Project
Setting UI under the Isometric Drawings Setting. The settings you choose are saved in
IsoConfig.xml files. Before that time, UI only provide some limited options, to make the iso
engine to produce desired result, the only way is to modify the IsoConfig.xml on related Iso
style.

Page 12
More reading: De-mystifying AutoCAD Plant 3D Isometrics

Catalogue Creation
Compare with Revit, since the pipe fittings’ and inline instruments’ geometry is quite similar, the
method Plant 3D used to create catalogue items or parts are much simpler. Plant 3D provided
the pre-programed parametric geometry for most of parts. User can pick the shape and enter the
dimension information for different size’s piping fittings and parts.
Catalogue builder is later introduced to further streamline the process. User can use the excel
sheet to batch enter large amount of data and create them in one go. Your focus here is to ensure
the data enter is done correctly. A proper auditing process should be introduced in your workflow
to ensure the catalogue item geometry is correct. Be aware that catalogue building is utilities
Microsoft.Office.Excel.Intercopt.dll as the engine to read /write the excel sheet, you might
sometime feel that your import/export excel is on idle and not going anywhere. You should go to
task manager to check how many of excel process is running on the background. You might
choose to kill one or two so it will frees up.
Plant 3D catalogue is a database, so remember to plan how you like to organize your catalogue
library in your organization. You might consider to split your catalogue based on the material type,
supplier or client. It is best not putting everything in one catalogue as it is a lot harder audit and
hard to search and pick the parts when create specs. You should consider adopting a naming
convention for parts, make sure you fill in the necessary information not only End type, Facing,
but also Material, Material code, Pressure class, schedule, design standards.
Apart from above discussed, the following attributes you need pay special attention:

Page 13
The Iso Symbol Type and Iso Symbol SKEY tells Plant 3D what symbol to use when generating
Isometric drawings for all parts. For valve object, Valve Body Type and Valve Alignment is used
to guide Plant 3D modelling module to load correct valve parts when model from P&ID. Valve
Alignment has the following value: inline, Angle, 3-Way and 4-Way.
P&ID ball valve symbol mapping to Plant 3D
class, in this case:
Any item in spec has Valve Body Type = Ball,
and Valve Alignment = Inline will be mapped
to this P&ID symbol.
So when modelling, Plant 3D will pick the
valve from matching spec name that is has
above values into the model space. At the
same time, any properties that you have
Fig 7. P&ID symbol mapped to spec item mapped with this class will automatically
pulled into Plant 3D model module.

Page 14
Furthermore, Plant 3D allows you to create the custom parts from AutoCAD block or python
scripts. However, both methods have its own pros and cons:
Out of box catalogue AutoCAD block Python script
 Some geometry very  Can take from supplier  Not suitable for people
symbolic, for example: library directly, simply don’t know the python
Valve; might not add ports and convert script
suitable when you it parts;  Can create
need to confirm  Need to do it one by geometrically correct
geometry constrain in one for all sizes parts, however still
the tie space and to  Can be very heavy for light weight for
some clients; AutoCAD and creates AutoCAD
 Light weight, issues on  Great portability, easy
AutoCAD friendly Orthographic drawing to copy the parts from
production one spec to the other
 Not friendly when copy  Not able to take all
the part from one spec actuator type
to other
 Not able to take all
actuator type

And with different type of method used, the following table summarise the possible combination
of the valve body and actuator are:
Actuator Create Type

Valve Body Catalogue Standard Catalogue Block Catalogue Python 3D Block

Catalogue Standard Yes Yes Yes
Catalogue block Yes Yes
Catalogue Python Yes
Custom Standard Yes Yes
Custom block
Reference: Link

I personally prefer to use python script parts as it allows you to create more realistic looking
parts and can be used to create large amount of parts via utilising catalogue builder. You can
also make the a slightly complicated script where can build multiple types in one script. It is
flexible.
If you are interesting about creating python script, you can refer to the following links for your
further reading.
Custom Python Scripts for AutoCAD Plant 3D – Part 1
Custom Python Scripts for AutoCAD Plant 3D – Part 2
Custom Python Scripts for AutoCAD Plant 3D – Part 3

Page 15
 What is Python?
Python is an interpreted, object-oriented, high-level, general-purpose programming
language. Python is dynamically typed and garbage-collected. It is first released in 1991.
Recent years, Python become more and more popular as its simple, easy to learn
syntax emphasizes readability. It supports modules and packages, which encourages
program modularity and code reuse. Python very popular in data since and AI
community.
Plant 3D utilities Python to create parts that is parametric constrained. The following are
few examples that what you can create by using python script.

Fig 9. Python scripted part – piping saddle

Fig 8. Python scripted part – dismantling joint

You can also use it to create supports:

Page 16
 Fig 10. Python scripted part – pipe support

How each module all sings together?

The Idea workflow of Plant 3D is to have P&ID created first, use P&ID information as guide or
map, user then click the line number and build the model, when it is done this way, Plant 3D will
import the information that is in P&ID into Plant 3D models. On the other hand, the spec carries
the information from catalogue and inject it into models. After adding the necessary iso
information, Plant 3D iso engine create isometric drawings based on the model information.

Page 17
 Fig 11. Plant 3D modules data mapping

Plant 3D catalogue is big piping & fitting store where it stores all the information about the parts.
There are four key properties that helps to link three different modules of Plant 3D together. If
these information are not correctly filled, Plant 3D will have no idea how to react when it sees
information from previous module. In Isometric module, the IsoSkeyAcadBlockMap.xml is the
key file that tells Plant 3D what SKEY means and what AutoCAD symbol block in
IsoSymbolStyles.dwg should be used by the iso engine.
On the other hand, the Valve Alignment and Valve Body Type property together with
PIDTo3dClassMapping.xml works together, so when you create the model from P&ID, Plant 3D
knows which and what type of valve should be used.
Now, you can create your own type of valve and symbol if it not exists out of box and still able to
create isometric drawings.

Fig 12. IsoSkeyAcadBlockMap.xml data example

Page 18
SKEY is typically a 4 letters code. First two letters presents type of object class, and the last two
letters presents the connection type of object. In Fig 12, <SkeyMap SKEY="EL??"
AcadBlock="Elbow"/> tells Plant 3D, when it sees a SKEY started with “EL”, which means it is
an Elbow, “??” means that any type of connection type of Elbow can use this Autocad block
named “Elbow” in IsoSymbolStyles.dwg.

More readings:
Plant 3D Orthographic Demystified

Page 19
BIM & Plant 3D
BIM
What is BIM? Building Information Modelling is a process supported by various tools, technologies
and contracts involving the generation and management of digital representations of physical and
functional characteristics of places.
The concept of BIM has existed since 1970s. But it did not become popular until 30 years later.
In 2002, Autodesk released a white paper entitled “Building Information Modelling”. Nowadays,
the term BIM has started to row over to Digital Engineering (DE). And use of it goes beyond the
planning and design phase of the project, extending throughout the building life cycle. And it
doesn’t stop there, it extending to any build assets that needs to be managed. It is used not only
in design and planning, it also used in construction planning, management, facility operation and
facility management.
So key ingredients of BIM and Digital Engineering are data and the process involved that creates,
updates and deletes the data. Plant 3D is a tool that can be used to create the BIM model, and it
is a good one with a great process in it.

Data, Data, Data

One of the key ingredients in BIM is Data. In asset life cycle, designers creates initial data about
an asset, it is high level on its concept design phase, and become more and more detail as it goes
into final design and pre-construction phase, during the procurement and construction phase,
some of information defined in design phase updated and added with extra information including
but not limit to installation date, operation and maintenance manuals. After handover to asset
owner, asset owner will use that information to create maintenance plan and schedule, and at the
same time to add any maintenance records.
Process plant design in nature is data heavy. When you receive the Employee Information
Requirement (EIR) from client, you need to make sure information is included in model and when
handover those information are filled correctly.
There are two approaches for filling data in models. One approach is to have all attributes required
in each object items. The other approach is to give all object item a classification and unique ID
so you can link a data source separately with model.
Approach All attributes in each object items Give all object a classification and
unique ID
Methodology  Add all parameters required to  Add a classification
the object class related; parameter, this classification
 Modeller need to fill the data or system should be universal in
use data manager to export as your company
excel and modify the data and  Add the exact same
import back to model parameter in project
 Data mapping depends on
object classification
Pros  Easy to setup  Engineers can work
separately in data sheet

Page 20
  Do not require changes to  Linked to model separately
catalogue  Will not effect the
design/modelling process
Cons  data export/import process can  Require planning and define
hold up the design /modelling a proper classification system
process and hard to keep track  Require making changes to
of version catalogues
 data import can be time
consuming when model set is
large

Implement EIR in Plant 3D

It is a two steps approach if you like to standardise your data flow from catalogue to model.
Step 1:
Plant 3D spec editor allow you to add custom parameters or properties into catalogue items. You
can add properties only to a selected part group in the catalogue. You can also add properties to
all part groups.
The parameter can be Numeric Value, Text or True/False. The example below shows two custom
parameters. The effective_Length is used for cost estimation, it is a Numeric Value.

Fig 13. Add Catalogue properties

Once created, it displayed in “Piping Component Properties” panels and is available to all parts
you can assigned a different value for each parts by utilising catalogue builder. You are not able
to input those data for each parts in Spec Editor if the value is different.

Page 21
Step 2:
You need to add these parameters in Project Setting  Plant 3D DWG Settings  Plant 3D
Class Definitions. The name must be exactly the same as defined in Step 1.

Fig 14. Added custom properties

Model Quality
The quality of Plant 3D model will affect the accuracy of Bill of Material output, if isometric creation
can be created successfully and the ease of orthographic drawing creation. It is actually very
important that individual modeller has good modelling habit and keeping the house clean.
A checklist for modeller:
 Review your spec to ensure the four key properties discussed in previous section “How
each module all sings together?” has correct data, the spec has all the parts required to
connect each other and it is approved by your mechanical engineer;
 Make sure Pipe Group has been planned in P&ID, before starting this task. Regardless if
those pipe group has assigned a proper number for the pipe number in P&ID (of course,
you can always assign a dummy number to P&ID as well), when modelling the pipeline,

Page 22
 make sure a dummy number is used for pipe group. This will save you a lot of time and
reduce the error if try to do this after the model is done;
 Make sure all pipe is connected, no unnecessary water drop present in your model;
 Make sure your pipe elements are in the correct pipe group as you planned using P&ID,
if decided to make changes on any pipe group, changes should be reflected back to P&ID.
Do not make the pipe group over complicated, as it makes iso engine generates cluttered
drawing unnecessarily. One can declutter it by making some setting changes on iso
creation interface, however, it will be custom changes on the isometric creation UI. For
better and consistent workflow, make pipe group simple should be the way to go. For
instance:
o When there is tee, the branch should be on different pipe group;
o Where there is a spec change, it should be a different pipe group;
o Where pipe goes underground, it should be a spec change and then it should be
a different pipe group;
o Where there is a size change, it should be a different pipe group;
Depending on your project needs, you can use more or less rules.

Model Presentation
We use Navisworks to review the model, however, you notice even after you installed the object
enabler, the Plant 3D data shown in Navisworks is really limited. All those extra parameters
created to fulfil the custom requirement is not presented, but the final delivery includes a federated
model. What can you do?
Step 1:
Export the model from Plant 3D as 3ddwf. You can pick and choose the properties that you like
to export using command. Beware that the coordinate system used in exported dwf file is different
with normal CAD, it rotated 90 degee along x axis. And this is because this file is designed for
Inventor.

Fig 15. Dwf file Axis Fig 16. AutoCAD and Revit Axis

You can see that the dwf files Z axis and Y axis is rotated around X axis for 90 degree.
Step 2:
Reposition the model in Navisworks.
Depending on your project, you might be able to make this change by simply rotate it along X axis
by 90 degree. If your project doesn’t need to be georeferenced, simply rotate it back using
Navisworks’ Units and Transform tool is enough.
If your project needs to be georeferenced and you used a project coordinate system, then you
need to do some extra work. I believe this one should be case for most of Plant projects. Last

Page 23
year, I presented a method which I wrote a plug-in in Navisworks to do this double rotation task.
The feedback is people would like to have more straight forward approaches. So let’s do some
math this year.
The Math behind the sense:
This is a 3D rotation question. Where we need to first rotate entire model along X axis and
then Z axis. But using Navisworks Units and Transform tool, you can only rotate once.
Let’s look at the Navisworks UI to see what is required.
 is the rotation angle
 is the rotation axis, this rotation axis is
a normalized axis value in axis x, y and z

We can see that in order to use Navisworks Units and Transform tool, you need to provide
a rotation angle and a rotation axis. When you only rotate the model along X axis for 90
degree, you will input:
Input Original Transformed

So, what is these 1,0,0 means? It is the normalized value that describe the X axis.
Is it possible only use one rotation angle and an axis to describe a combined rotation axis
and angle? Yes, it is possible. Based on the Euler's rotation theorem, in 3D space, any

Page 24
displacement of a rigid body such that a point on the rigid body remains fixed, is equivalent
to a single rotation of some axis that runs through the fixed point.
Let’s see how to achieve this?
Firstly, the rotation follows the Cartesian Coordination system, where we have three axis
– X, Y and Z. and the rotation are around particular axis. Under this coordination system,
the order of rotation in different axis will affect the final location of the object.
Example:
So, this rotation on each axis can be describe by a matrix using the following formula:

Fig 17. Rotation Fig 18. Rotation Fig 19. Rotation matrix
matrix on X axis matrix on Y axis on Z axis

More reading: Rotation Matrix

If the rotation angle on X axis is 90°, then the Rx(90°) should have the following value:

1.0000 0.0000 0.0000

0.0000 0.0000 -1.0000
0.0000 1.0000 0.0000

And if the rotation angle on Z axis is 82.163°, then the Rz(82.163°) equals to:

0.1364 -0.9907 0.0000

0.9907 0.1364 0.0000
0.0000 0.0000 1.0000

Based on the order of the rotation, we can work out the final transformation. So our rotation
order is XZ. In this case, it would be
0.1364 -0.9907 0.0000
Rx(90°) x Rz(82.163°) = 0.0000 0.0000 -1.0000
0.9907 0.1364 0.0000
m00 m01 m02
m10 m11 m12
m20 m21 m22

Then we need to turn this rotation matrix to a angle and a axis using the following formula:
 angle = acos(( m00 + m11 + m22 - 1)/2)
 x = (m21 - m12)/√((m21 - m12)2+(m02 - m20)2+(m10 - m01)2)

Page 25
  y = (m02 - m20)/√((m21 - m12)2+(m02 - m20)2+(m10 - m01)2)
 z = (m10 - m01)/√((m21 - m12)2+(m02 - m20)2+(m10 - m01)2)

we then have the angle as 115.58°

X Y Z
0.629938 -0.54917 0.549171

Now you have everything needed for your Navisworks transform.

What do you use Data for?

For design collaboration, one can create search set in Navisworks and used for clash detection
between disciplines and object types and help to provide consistent appearance in federated
model. It improves efficiency for the design team.
For construction, it can help create construction sequencing, provide better data for cost
estimation.

Page 26