handout_1386_PD1386

8/20/2019 handout_1386_PD1386

http://slidepdf.com/reader/full/handout1386pd1386 1/27

Converting Existing Specs and Catalogs for Use in

Autodesk® AutoCAD® Plant 3DTarryn de Magalhaes – Caddman (Pty) Ltd

PD1386 As many of us know, changing from one software solution to another is not an easy task. n

most cases, com!anies must !ut a!!lications through a rigorous !rocess to set them u! to meetcom!any standards. "hen changing from one !rogram to another, it is ideal to maintain the largestamount of customi#ed data !ossi$le. This class co%ers con%erting your current &entley' AutoPLAT,ntergra!h' CA"or*', or C+-formatted s!ecs and catalogs into AutoCA Plant s!ecs andcatalogs. "e go through the !rocess for con%ersions as well as take an in-de!th look into the ma!!ingand the setu! of the ma!!ing inside of the AutoCA Plant +!ec /ditor.

Learning Objectives

At the end of this class, you will $e a$le to0

• escri$e the ma!!ing !rocess $ehind the con%ersion of the s!ecs and catalogs

• Customi#e the current ma!!ing in the AutoCA Plant +!ec /ditor

• +uccessfully con%ert s!ecs and catalogs from AutoPLAT, CA"or*, or C+-formatted files

• /*!lain the information !ro%ided $y the s!ec con%ersion re!ort

About the SpeakerI am a plant solutions consultant for an Autodesk reseller based in South Africa. I successfully

completed the Drawing Office Principles Basic & Adanced courses in !""#$!""%. As I had aworking knowledge of AutoAD I began presenting courses on the software as well as offering

support while obtaining this 'ualification. Oer time the courses I am certified to present hae

increased. I now present the beginner( intermediate( adanced and update courses for

AutoAD( AutoAD P&ID( AutoAD Plant )D and Autodesk Inentor. I also support(

implement and customi*e all of the preiously mentioned products. +y course reiews hae

always receied a rating of %,- and aboe and as mentioned preiously I hae trained

hundreds of people. I participated in the role of Ask the e/pert0 for the month of +ay !"1) for

Autodesk2s AutoAD Plant 3/change. I hae gained e/tensie knowledge in AutoAD Plant

)D and AutoAD P&ID through both the implementation and full customi*ation of these two

solutions.

tarrynd4caddman.co.*a

Understanding Conversion Mapping

8/20/2019 handout_1386_PD1386


Converting Existing Specs and Catalogs for Use in Autodesk® AutoCAD® Plant 3D

To successfully con%ert your current s!ecifications from an e*ternal format into the AutoCA

Plant +!ecs and1or Catalog format you may need to add1edit the ma!!ed !ro!erties within

the Class Ma!!ing ialogue &o*. 23ile 4 Con%ert 4 +ettings 4 5select a!!ro!riate o!tion5 (see

image 156. The ma!!ing configuration controls how the e*ternal +!ecs and1or Catalogs aretranslated into AutoCA Plant +!ecs and1or Catalogs.

!age 1

"hen adding or ad7usting e*isting classes you should $e sure to ad7ust the Class Ma!!ing,

8eometry Ma!!ing and the Pro!erty Translations.

Class Mapping

9

8/20/2019 handout_1386_PD1386



!age "

The Class Ma!!ing ta$ (Image ! ) is where the e*ternal format:s general !ro!erties are setu! to

match AutoCA Plant :s general !ro!erties.

The ad7ustments made within this ta$ are sa%ed inside a configuration file. These files are

ATPToPdClassMa!!ing.*ml, C+ToPdClassMa!!ing.*ml and C"ToPClassMa!!ing.*ml.

They are found inside of the AutoCA Plant route folder (C0;Program

3iles;Autodesk;AutoCA 9<=>;PLT).

8/20/2019 handout_1386_PD1386



Know the Diference between Global Properties and Class Specic

Properties

8lo$al !ro!erties are the common !ro!erties amongst all com!onents. These include Longescri!tion, Material, +hort escri!tion etc. These !ro!erties can $e ma!!ed glo$ally instead of

ha%ing to assign their AutoCA Plant e?ui%alent !ro!erty indi%idually.

Class s!ecific !ro!erties refer to !ro!erties uni?ue to a s!ecific ty!e of com!onent. An e*am!le

is a @< degree el$ow1$end. ne of the !ro!erties for an el$ow1$end in AutoCA Plant is

PathAngle, this field would $e ma!!ed to the e*ternal formats e?ui%alent, $ut this is uni?ue to a

certain ty!e of com!onent, and would therefore $e ma!!ed at a class le%el.

Class s!ecific !ro!erties o%erride 8lo$al !ro!erties. Therefore if you ha%e the same AutoCA

Plant field ma!!ed inside the 8lo$al and Class Pro!erties, the %alue in the Class Pro!erty

will $e a!!lied.

!age 3

f you would like a certain e*ternal class !ro!erty o%erride to $e a!!lied to one !ort only you will

make use of the BD sym$ol. (see image 6)

>

8/20/2019 handout_1386_PD1386



!age #

External Class name and Plant 3D matching class name:

f your +!ec1Catalog is failing to con%ert =<<E, one of the reasons may $e that the class of a

certain com!onent has not $een ma!!ed. Create a new class (see image , ) and s!ecify what the

corres!onding class is in AutoCA Plant (see image 7 ). nce that is done you can start

assigning !ro!erties from your e*ternal +!ec1Catalog to match the P !ro!erties (see image # ).

!age $

F

8/20/2019 handout_1386_PD1386



!age 6

“atch or !ppl"# Dened

"hen the apply o!tion is selected, for a row, the %alue1te*t underneath the B/*ternal Pro!erty

ameD column will $ecome the %alue1te*t for the !ro!erty that is listed underneath the BPlant

Pro!erty ameD column. ./. if there is a row underneath the column BPlant Pro!erty ameD

called PathAngle and that same row contains a %alue of @< underneath the B/*ternal Pro!erty

ameD column and the BMatch or A!!lyD column is set to A!!ly, the result will $e that the

PathAngle !ro!erty in the AutoCA Plant catalog will $e @<. (see image , )

G

8/20/2019 handout_1386_PD1386



!age %

"hen the match o!tion is selected the !ro!erty under the B/*ternal Pro!erty ameD column

re!resents a column with its own %alues1te*t inside of the e*ternal +!ec1Catalog. The match

o!tion lets the !ro!erty listed under the BPlant Pro!erty ameD take on whate%er %alue1te*t is

listed underneath that s!ecific column within the e*ternal +!ec1Catalog. (see image %( 8 and 1" )

H

8/20/2019 handout_1386_PD1386



!age 8

!age &

!age 1'

I

8/20/2019 handout_1386_PD1386



Geometry Mapping

!age 11

The 8eometry Ma!!ing ta$ (see image 11) is where the e*ternal !arametric dimensions are

translated into AutoCA Plant !arameters.

"e need to define the e*ternal com!onents !ro!erty1ies the con%erter will use to locate the

correct o$7ect and translate it into an AutoCA Plant com!onent. (see image 1! ).

@

8/20/2019 handout_1386_PD1386



!age 1"

nce this is defined we will then s!ecify which AutoCA Plant +ha!e the /*ternal o$7ect will

use when it is con%erted to a P o$7ect. (see images 1) and 16)0

!age 13

!age 1#

T/0 The AutoCA Plant com!onent name without an underscore e*tension can $e used

for $e%eled ends, $uttwelded ends or flanged ends. The underscore e*tension defines other end

ty!es e.g. J33 would indicate 9 !orts $oth either socketed or threaded.

The ne*t ste! is to define (in this instance) the /JCJ= and /JCJ9 (see image

1, ) so that the con%erter will choose the correct e*ternal com!onent and $ring it into a P

Catalog1+!ec accurately.

!age 1$

=<

8/20/2019 handout_1386_PD1386



ow we are ready to start matching the P Parameters with the corres!onding e*ternal

!arameters.

/ach AutoCA Plant +ha!e has its own list of !arameters (see image 17 ). These !arameterswill %ary from o$7ect to o$7ect.

!age 16

The P Parameters and the /*ternal Corres!onding Parameters can now $e matched

accordingly (see image 1# ).

!age 1%

==

8/20/2019 handout_1386_PD1386



Property ranslation

!age 18

The Pro!erty Translation Ta$ (see image 1% ) is used to ensure that %alues which a!!ly to all

com!onents from our e*ternal +!ec1Catalog are correctly translated when the con%ersion

!rocess takes !lace.

Kou are a$le to add in additional %alues and these will a!!ly to all the classes.

=9

8/20/2019 handout_1386_PD1386



Converting Specs!Catalogs"

$o Con%ert !&toPlant Specs'Catalogs

=. Access 3ile 4 Con%ert 4 AutoPlant +!ecs and Catalogs

9. +elect Add

. a%igate too and select the +!ecs, Catalogs or $oth that you would like to con%ert

=

8/20/2019 handout_1386_PD1386



>. Add the location you would like the con%erted +!ecs1Catalogs !laced in

F. +elect Con%ert

=>

8/20/2019 handout_1386_PD1386



G. Monitor the !rogress

H. e%iew esults

=F

8/20/2019 handout_1386_PD1386



I. iew and inter!ret the Log 3ile

=G

8/20/2019 handout_1386_PD1386



@. &ased on the results you can take a!!ro!riate action to ensure a =<<E successful

con%ersion.

=H

8/20/2019 handout_1386_PD1386



$o Con%ert C!D(orx Specs

=. Access 3ile 4 Con%ert 4 CA"or* +!ecs

9. +elect Add

. a%igate to and select the +!ec you would like to con%ert

=I

8/20/2019 handout_1386_PD1386



>. +elect the Li$rary containing eferenced 3iles

=@

8/20/2019 handout_1386_PD1386



ote0 The correct Path needs to $e selected for the Li$rary. t often ha!!ens that the

incorrect !ath is selected resulting in the CA"or* s!ecs not $eing con%erted.

L&JMM is T the correct folder $ut rather the folder one le%el u! (Plant3older).

9<

8/20/2019 handout_1386_PD1386



F. +elect the ata 3ile

9=

8/20/2019 handout_1386_PD1386



G. Add the location you would like the con%erted +!ecs !laced in

99

8/20/2019 handout_1386_PD1386



H. +elect Con%ert

I. Monitor the Progress

@. e%iew esults

9

8/20/2019 handout_1386_PD1386



$o )mport CS* +iles

=. "hen im!orting C+ files, it is %ital to ha%e the correct folder structure.

9. Access 3ile 4 Con%ert 4 C+ files. Add the folder containing the ataTa$les and MiscTa$les folders.

9>

8/20/2019 handout_1386_PD1386



>. +elect whether this C+ file needs to $e im!orted as a +!ec or a Catalog

9F

8/20/2019 handout_1386_PD1386



F. Add the location you would like the con%erted +!ecs !laced in

G. +elect Con%ert

H. Monitor the Progress

9G

8/20/2019 handout_1386_PD1386



I. e%iew esults

handout_1386_PD1386

Documents

Transcript of handout_1386_PD1386