Professional Documents
Culture Documents
Auto
How
w to Manag
M
e Largge Pro
ojects
Large projjects are not handled by a single design
ner and so coorrespondingly, a large pro
oject should n
not
reside in a single DWG. Sounds logical, but how do you divid e up a large p
project so thaat many desiggners
can work together as a team. Split it up into lotss of DWGs! SSounds easy, but how?
This paper will give you
u some ideas as to how to
o organize youur Plant 3D prroject so thatt the project
remains as
a a single pro
oject for reporting and yet has many drrawing / modeel files, so thaat designers o
of
different disciplines
d
can work togetther and yet work
w
with maanageable datta sets so that modeling
response remains good
d. The way we
w will do thiss is through e xtensive use of XREFs.
And just as
a no two pro
ojects are the same, there are many diffferent ways tto organize a project. Well
suggest one way, but you
y can modify these sugggestions in ordder to suit yo
our project beetter.
Contents
Getting Started.............................................................................................................................................. 3
Setting Up Your Project ................................................................................................................................. 3
Controlling Rights Between Disciplines .................................................................................................... 4
Working With Xrefs. ..................................................................................................................................... 5
Simplifying Working With Xrefs ............................................................................................................... 5
Modeling Using Xrefs ............................................................................................................................... 6
Managing Drawing Sizes With Xrefs ........................................................................................................ 7
Data Management ........................................................................................................................................ 8
Working In a Distributed Environment ..................................................................................................... 8
Managing Deliverables.................................................................................................................................. 9
Piping Isometrics ....................................................................................................................................... 9
Orthographic Drawings ........................................................................................................................... 11
Working with a Master Model .................................................................................................................... 13
Working with Navisworks ....................................................................................................................... 14
SQL Server ............................................................................................................................................... 17
Vault ........................................................................................................................................................ 18
Conclusions ................................................................................................................................................. 18
Appendix 1 Managing Drawing Rights Access ......................................................................................... 19
Windows Folder Structure ...................................................................................................................... 19
Plant 3D Project Folder Structure ........................................................................................................... 21
Page 2
Getting Startted
Before yo
ou start to cre
eate the proje
ect in Plant 3D
D, take a big sstep backwarrds and look aat the project as a
whole. Th
hink about ho
ow to logicallyy split it up.
If it is a big site
e, mostly all on
o one level, like
l a refineryy, then look aat a site plan aand divide it u
up
nto areas. Eacch area may be
b a process unit, or it ma y be a logicall sub-division of a process unit,
in
but consider itt as an AREA.
In
n the case of a multi-story plant, you may want to tr eat each floo
or as an area aand then
su
ubdivide into physical areaas.
In the mid
ddle is a pipe rack which jo
oins up the se
eparate areass (Area 2). Thiis is considereed a separatee area
since we want
w
a design
ner to be resp
ponsible for considering
c
thhe layout of o
only the pipess in the rack. Area
13 is a serrvicing area and contains no
n plant item
ms (i.e. the m
models in this area are AEC models, not Plant
3D models) and so there are no P&IDs and no Plant models inn this area.
Within eaach area we have to consid
der Equipmen
nt, Structures and Piping. And if we havve different
designers focusing on each
e
disciplin
ne, we probab
bly want to diivide up our aareas into thee disciplines.
Settin
ng Up Your
Y
Pro
oject
Using the example abo
ove we have decided
d
that we
w will have 14 areas. Eacch area can m
managed by a lead
prising equipm
ment layout d
designers, Structural layout
designer, but each area has a design team comp
d
designers, and piping designers.
w have split the
t project up
p into three pprocess areass plus one utillities area wh
hich
In the case of P&IDs we
will span severral of the Pipiing
will contain all the Utility P&IDs (orr ULDs). The fact that thee P&ID area w
areas is no
ot important as Plant 3D will
w track and manage all t he lines and eequipment in
n the project.
AutoCAD Plant 3D Managging Large Projeccts
Page 3
So the pro
oject will lookk like this in Plant
P
3D Proje
ect Manager:
We have created
c
a Stru
uctural file in the Structure
es folder, an Equipment M
Modeling file iin the Equipm
ment
folder, and 2 Piping file
es in the Pipin
ng folder.
This structure keeps th
he file content small and manageable
m
a nd yet allowss maximum flexibility in
working in
n the project.. By using Xre
efs, the desiggner can focuus on the partt of the modeel he is particu
ularly
interested
d in at any mo
oment by unloading the Xrefs he does nt need. Theen when he n
needs more
informatio
on, simply reload the Xrefs for full mod
del realizationn.
Contro
olling Righ
hts Between Disciiplines
In some organizations,
o
, CAD Manage
ers feel more
e comfortablee controlling w
who has writee-access to
drawings based on the
e discipline. (So Structural designers ca nt change piiping configurrations and viceM
CAD Managers (or Pro
oject Adminisstrators) do t his by settingg access rightss at the foldeer
versa.) Many
level. In the
t above exaample, the hie
erarchy is are
ea-based and disciplines arre sub-folders of the area.. In
this case, the administrator will nee
ed to set rightts for every d iscipline in evvery area. No
ote that this w
would
a the project setup and th
he rights would only need tto be changeed when projeect personnell
be done at
change.
Page 4
No
ote that the ppump is in thee equipment Xref and thatt
sin
nce we were routing an 8 line and con
nnecting to a 10
no
ozzle, a 10 m
mating flange with a 10x8 rreducer was
plaaced in the p iping model. Also note the connection
n was
alsso placed which will give u
us the correctt bolts and gaasket.
Simpliffying Wo
orking Witth Xrefs
One usefu
ul way of man
naging the Area Xrefs is to
o have a mastter area draw
wing. This is eessentially an
empty mo
odel file with all the area models
m
loaded as Xrefs. I n this example, Area 6 in tthe master arrea
drawing iss Area6.dwg:
Itt is importantt that these X refs be loadeed as Attachm
ments. We
re
ecommend th
hat you use a relative path
h as shown beelow. (As thee files
are part of a project,
p
relatiive path will m
make movingg a project easier):
Page 5
Page 6
By unload
ding the structure and turn
ning off some
e of the pipingg layers, a bettter view is obtained makiing
piping eassier:
Managging Draw
wing Sizess With Xrrefs
The optim
mum size for a model file iss 5-10MB. De
epending on tthe hardwaree you are usin
ng and the typ
pe of
plant mod
del, it may be
e better to kee
ep the modell size smaller.. This can be especially tru
ue if you havee
objects th
hat are not Plaant 3D objectts (e.g importted from Inveentor or Revitt). This will reesult in more dwg
files, but good
g
model management
m
will maintain
n good perforrmance. It do
oesnt matterr how many fiiles
you have in the projectt, AutoCAD Plant 3D proje
ect manager ccan manage laarge numberss of drawingss.
With expe
erience, youlll be able to guesstimate
g
how
h many linees or how maany equipmen
nt items will b
be in
each mod
del file in orde
er to keep the
e sizes down, but there is nno problem aadding more m
model files ass the
project de
evelops. Thiss is especially true for pipin
ng files.
Some use
ers like to put all equipmen
nt in an area into
i
one dwg . Others like to split them
m up into sub--areas
where oth
hers may splitt the equipment up by levels on a struccture.
In the case of structure
es, many userrs will place a single struccture into a single model ffile. This is so
o the
structure can be exporrted for analyysis and then replaced withh a detailed sstructural model after the
detailed engineering
e
has been done
e. In some caases, the struccture may acttually extend across an areea
boundaryy. This is not a problem, sim
mply place th
he structural m
model in onee area and theen have the
master arrea model of the
t other are
ea(s) xref this structural moodel.
Pipe Rackks are typicallyy handled sep
parately too. This is to alloow the pipingg designer to optimize the
space avaailable on the rack and thiss is its own layyout problem
m. Thus the Pipe Rack areaa may also contain
AutoCAD Plant 3D Managging Large Projeccts
Page 7
sub-racks which will encroach into process areas. The best practices approach discussed so far handles
this approach easily.
Managing piping models can be done in many different ways. Since Plant3D allows intelligent
connections across Xrefs. Thus piping models can be divided into sub-areas or by line numbers, with
each designer allocated a certain number of lines. There are no constraints on how to divide up the
area.
Data Management
AutoCAD Plant 3D uses an SQL database to manage non-graphic data. The default SQL database engine
delivered with Plant 3D is SQLite (www.sqlite.org) Everything you need to manage the data within a
Plant3D project is delivered with Plant 3D and you do not need to be a database expert nor do you need
to understand SQL databases in order to use SQLite. SQLite is a simple and effective solution for
managing data in smaller projects where integration with enterprise databases is neither necessary nor
desirable. Thus small companies can use SQLite for their projects and Plant 3D Data Manager will be an
effective interface to the project and drawing data. For more information on SQLite visit
http://www.sqlite.org/about.html
For larger organizations who have large amounts of data stored within Enterprise Databases, Plant 3D
will support SQL Server. The inclusion of SQL Express in the Plant 3D allows you to select whether to use
SQLite or connect to your corporate database.
When should I stick with SQLite and when should I use SQL Server? This is a difficult question to answer
and it depends more on how you use the data than on how many users need to access the project
database. If you are already using corporate databases and want to share the Plant 3D data with other
database applications, then SQL Server is definitively the correct answer. If your project users are
distributed geographically, then SQL Server may be the best solution as the database server will manage
the distribution of the database, or manage the centralization of the data.
Regardless of whether you use SQLite or SQL Server, the Data Manager allows you to extract data to
Excel spreadsheets for non-CAD users to manipulate the data.
Page 8
Buzzsaw comes
c
with a Buzzsaw Syn
nc utility which allows you to sync local folders with those on Buzzzsaw.
Although Buzzsaw Sync allows you to
t have continual syncing,, you may find
d it more manageable to o
only
perform syncing
s
at cerrtain times of the day. (This avoids con tinual messagges to reload Xrefs.)
Manaaging Deliverab
bles
The most common deliverables that are generatted are Pipingg Isometrics aand Piping Orthographic
e generated per
p line numbber and orthoographics (orthos) are
drawings.. Generally, issometrics are
generated
d per area, with additionall drawings be
eing generated for sectionss and elevatio
ons. They aree
managed differently.
Piping Isometrics
AutoCAD Plant 3D Projject Managerr manages all the isometricc drawings fo
or you. It has separate fold
ders
e iso styles you need to cre
eate, and settting up the styyles and the llocations for tthese drawin
ngs is
for all the
managed through Project Manager > Properties:
Page 9
P
Page 10
Orthoggraphic Drawings
D
Orthograp
phic drawingss are created from a selecttion of files thhat are availaable in the Plaant 3D Drawin
ngs
under Sou
urce Files. The
e files are selected in the ortho
o
creatio n process, an
nd may be selected to creaate
Area plans, or master plans.
p
Sections and details include few
wer files since they are showing smaller
oject.
areas of the overall pro
P
Page 11
Layers can
n be used from the 3D mo
odels, or objeccts can be plaaced accordin
ng to specified
d layer settings.
To update
e the orthographic drawings, the mode
el must be chaanged first. Th
hen the user can open thee
ortho, select a viewport and use the
e Update View
w command.
P
Page 12
The above
e process may look like we
e will have maany files to m
manage, and tthis may be trrue. But by
managingg them in this way, drawinggs can be created at any tiime, even wh
hile modeling is going on aand
then draw
wings can be updated
u
conssistently.
P
Page 13
Workin
ng with Naviswor
N
ks
Dependin
ng on whether you want to
o work at a prroject level orr at an area leevel, the proccess is the sam
me.
Simply staart with the Master
M
Modell or the Area Model.
The first time
t
you set up
u for a Navissworks review
w, open the M
Master Modell DWG file. N
Now after
performin
ng any operattions you wan
nt to do, save
e the model a s a NWF. In ffuture review
ws, open the N
NWF
file and co
omments, maaterials are re
etained even after the DW
WG files which are referencced have been
n
updated.
Sometime
es you want to
t do reviews at a particulaar milestone and want to ssave the project for furtheer
reviews even though the project de
esign is contin
nuing. In thesse cases, open the Masterr Model or Area
Master DW
WG in Navisw
works, and then save as NW
WD. All the m
model entities are now savved in a singlee
source mo
odel which caan be viewed using Navisw
works.
For betterr performancce, make sure the nwc or nwd
n files get cclosed after tthey are read.
P
Page 14
P
Page 15
P
Page 16
SQL Server
The decision to use SQL Server is driven by the number of users modifying project data at one time. The
default database type, SQLite is valid for up to 2 TB per file, so the project file size is not the issue.
Because the SQLite database is a single file, successful read/writes depend on fast access. When more
users access the database at one time, they have a higher chance of hitting the database at the same
time (or close enough).
Due to network configurations, server performance, computer performance, network loads, and a host
of other factors, a precise number of users cannot be given. However, through experience with various
clients, most people start to see performance degradation with between 6 - 10 users.
If you know you will have more than 10 active users, you should implement SQL Server Express or SQL
Server.
You must also use SQL Server if you plan to use Plant 3D with Vault.
Database Types
SQL Server An enterprise-level product offering from Microsoft that includes a database server with
administration tools for replicating databases between sites, and other advanced features
SQL Server Express A free product offering from Microsoft that includes a database server without
advanced administration tools. You can still configure backups.
SQLite An open source file-based database used by developers world-wide. The database engine is fast
with good performance.
Versions
AutoCAD Plant 3D has been run with SQL Server 2005, SQL Server 2008, and SQL Server 2012.
Articles on setting up SQL Server Express and creating backups are available here:
http://www.pdoteam.com/series/plant3d-on-sql-express/
Page 17
Vault
Autodesk Vault (http://www.autodesk.com/products/autodesk-vault-family/features ) is document
management software that integrates with many products in the Autodesk portfolio. In 2014, Vault
became integrated into the Plant Project Manager.
Vault should be used in the following conditions:
Vault allows you to store the drawing data in a central location, and have satellite offices check in/out
drawings on an as-needed basis. Currently, all xrefs must reside within the project structure, as Plant
uses its own working directory for Vaulted projects.
Conclusions
This document is a guide to help you set up and manage a large project. It is a guide, not a bible, so feel
free to adjust the recommendations to suit the way you work. And remember, designers need to have
exclusive access to a model file while they work. So you need to have at least as many model files as
you have designers!
Page 18
Appe
endix 1 Manaaging Drrawing Rights Access
In this app
pendix we will give an example to show
w how you ca n manage a large project w
where differeent
disciplines will have read-only accesss to other discipline draw
wings. In ordeer to manage this the Wind
dows
folder stru
ucture is diffe
erent to the Plant
P
3D Proje
ect folder struucture.
Windo
ows Folde
er Structu
ure
Since we want
w
to give Structural De
esigners Write
e Access to thheir designs aand read-onlyy access to thee
Piping and
d Equipment Layout designs, then it maakes sense too create a fold
der for the Structures and a
different folder
f
for Pip
ping Designerss. If we also want
w
to manaage files at an
n area level, tthen we will ccreate
area folde
ers as well:
P
Page 19
In the abo
ove example we
w have assu
umed the user is a structurral designer s o we are den
nying him writteaccess to the Equipment and Pipingg Folder. Whe
en this user oopens a Pipingg or Equipmeent drawing, tthe
following message willl appear:
P
Page 20
Plant 3D
3 Projecct Folder Structure
e
In the pro
oject we wantt to create a structure
s
by area
a
and thenn by disciplinee as follows:
P
Page 21
P
Page 22