2007. Siemens Product Lifecycle Management Software Inc. All rights reservedSiemens PLM SoftwareWhos Best Practices?Mar LawrySiemens PLM SoftwarePage 2 200!. Siemens Product Lifecycle Management Software Inc. All rights reservedSiemens PLM SoftwareBackground: Two user communities in NX"ormer I#deas users and former $nigra%hics &$'( users )ring different *)est %ractices* with them+ often with strongly held o%inions. Page , 200!. Siemens Product Lifecycle Management Software Inc. All rights reservedSiemens PLM SoftwareBest practices review-hy were they ado%ted.'eneral design %rinci%les./om%any or industry standards.Software %erformance.Are they still valid.0as our design %rocess changed.0ave our standards changed.0as the software %erformance changed. Are new methods availa)le.Page 1 200!. Siemens Product Lifecycle Management Software Inc. All rights reservedSiemens PLM Software1. Use o datumsI#deas %ractices2Start with 3456 coordinate system &3ase 4r%han 5eference 6ode(3456 contains , %lanes+ , a7es+ 8 origin/reate datums first in the history tree/reate datums relative to other datums$' %ractices2Start with %rimitive )loc or datum9on:t create unused datum %lanes/reate datum %lanes when needed/reate datums relative to geometry Page ; 200!. Siemens Product Lifecycle Management Software Inc. All rights reservedSiemens PLM Software1. Use o datums continued6< changes &from $' or I#deas( that affect old %ractices29atum coordinate systems are now one entity in 69atum coordinate systems can )e reordered+ even to )e the first feature+ and associativity added.&?his is not %ossi)le in I#deas.(/reation of relative datum coordinate systems &4ffset /S@S( has )een im%roved.9is%lay of datum coordinate systems has )een im%roved to control siAe.Page B 200!. Siemens Product Lifecycle Management Software Inc. All rights reservedSiemens PLM Software1. Use o datumscontinued6< )est %ractices2?he 3456 coordinate system %ractice from I#deas is no longer reCuired )ased on software )ehavior+ )ut is still a good design %ractice.It is included in the Model tem%late./reate other datum coordinate systems as 4ffset /S@S with associativity to the first datum coordinate system+ similar to the 3456 method.Page 7 200!. Siemens Product Lifecycle Management Software Inc. All rights reservedSiemens PLM Software!. "ssociativit#I#deas %ractices2'oal to create associative features.Setch in Place %referred over setching on the wor %lane.$se "ocus to create associative geometry.$se "eature /o%y to su)divide %art design.$se A/" to create associative lins )etween %arts in an assem)ly.$' %ractices2Associativity is not the only goal.Dee% features inde%endent )ecause they are less %rone to sur%rises.Avoid inter%art lins to %revent inadvertent changes to released files.Page ! 200!. Siemens Product Lifecycle Management Software Inc. All rights reservedSiemens PLM Software!. "ssociativit#continued6< changes that affect %ractices2ParentEchild associativity is very visi)le in the Part 6avigator."ocus within a %art is not reCuired.Associativity )etween %arts is easier to create without -AFG 'eometry Liner or A/". &6< B(Page H 200!. Siemens Product Lifecycle Management Software Inc. All rights reservedSiemens PLM Software!. "ssociativit#continued6< )est %ractices23uild on the oldest+ most sta)le geometry.9atums should )e %referred over faces and edges.Avoid references to faces or edges ofdetailed design features lie chamfers or )lends.Associativity is most useful in the intermediate design %hase with highly engineered models."or early conce%t models+ it is not as necessary./onsider using Synchronous Modeling with 0istory#"ree mode for conce%t models or for manufacturing changes+ not for highly engineered models. &6< B(Page 80 200!. Siemens Product Lifecycle Management Software Inc. All rights reservedSiemens PLM Software$. %rgani&ing sketchesI#deas %ractices2Setches are =a)sor)ed> into features./onvert setches to reference curves to use in multi%le features.$se setches to define design intent./reate as many relationshi%s as %ossi)le in a setch.$' %ractices2Setches are se%arate features.Dee% setches sim%le and small+ one %er feature.Page 88 200!. Siemens Product Lifecycle Management Software Inc. All rights reservedSiemens PLM Software$. %rgani&ing sketchescontinued6< changes that affect %ractices2Setches can )e e7ternal or internal to features./onstraints and dimensions can s%an from one setch to another. &@ou cannot do this in I#deas.(Page 82 200!. Siemens Product Lifecycle Management Software Inc. All rights reservedSiemens PLM Software$. %rgani&ing sketchescontinued6< )est %ractices2$se the same setch for multi%le features. Page 8, 200!. Siemens Product Lifecycle Management Software Inc. All rights reservedSiemens PLM Software$. %rgani&ing sketchescontinued6< )est %ractices25euse setches and features using /o%y and Paste. Page 81 200!. Siemens Product Lifecycle Management Software Inc. All rights reservedSiemens PLM Software$. %rgani&ing sketchescontinued6< )est %ractices2$se constraints and dimensions )etween setches.4rganiAe design intent in setches in the most logical way.'ketch 1'ketch !'ketch $Page 8; 200!. Siemens Product Lifecycle Management Software Inc. All rights reservedSiemens PLM Software(. 'ketch)*ased eatures vs. orm eaturesI#deas %ractices2Almost all features are setch )ased.Primitive features are discouraged.$' %ractices2Primitive features were used.3est %ractice was to only use one %rimitive to start a model.Setched features were avoided )y some customers.Page 8B 200!. Siemens Product Lifecycle Management Software Inc. All rights reservedSiemens PLM Software(. 'ketch)*ased eatures vs. orm eaturescontinued6< changes that affect %ractices2Primitive features now have some associativity."orm features now use setches. &0ole command("orm features indicate designEmanufacturing intent.Page 87 200!. Siemens Product Lifecycle Management Software Inc. All rights reservedSiemens PLM Software(. 'ketch)*ased eatures vs. orm eaturescontinued6< )est %ractices2Setch#)ased features are still a )est %ractice to define design intent."orm features offer a )etter way to indicate designEmanufacturing intent in some circumstances.-hat is the )est way to mae the model understanda)le and edita)le )y others.Page 8! 200!. Siemens Product Lifecycle Management Software Inc. All rights reservedSiemens PLM Software+. ,Bush# tree- mode.ingI#deas %ractices2Advanced I#deas users use )ushy tree modeling.$' %ractices2$sers never heard of it.Page 8H 200!. Siemens Product Lifecycle Management Software Inc. All rights reservedSiemens PLM Software+. ,Bush# tree- mode.ingcontinued6< changes that affect %ractices2In 6 modeling. &$' instructors often recommend this+ )ut they don:t call it )ushy modeling.(?urn off ?imestam% 4rder to wor with multi%le )odies.Page 28 200!. Siemens Product Lifecycle Management Software Inc. All rights reservedSiemens PLM Software/. PatternsI#deas %ractices2$se of %atterns is encouraged.Patterns create one feature.$' %ractices2$se of %atterns was encouraged &instance arrays(.Patterns created one feature for each instance.Su%%ressing individual instances in the %attern was discouraged.Page 22 200!. Siemens Product Lifecycle Management Software Inc. All rights reservedSiemens PLM Software/. Patterns6< software changes2"eature arrays and geometry arrays are ty%es of %atterns. ?he new setch#)ased 0ole command can create an entire %attern of holes as one feature. &6< B(Page 2, 200!. Siemens Product Lifecycle Management Software Inc. All rights reservedSiemens PLM Software/. Patternscontinued6< )est %ractices2Patterns are an efficient way to model+ and also ca%ture design intent./onsider using the new setch#)ased 0ole command instead of using a %attern command+ es%ecially for irregular hole %atterns.Page 21 200!. Siemens Product Lifecycle Management Software Inc. All rights reservedSiemens PLM Software0. 1ontro..ing o*2ect visi*i.it#I#deas %ractices29is%lay "ilter is used %rimarily.Setches and tools are a)sor)ed into features.$' %ractices2Layers were used %rimarily./om%any standards e7isted for layer use.Setches and 3oolean tools were %laced on hidden layers.Page 2; 200!. Siemens Product Lifecycle Management Software Inc. All rights reservedSiemens PLM Software0. 1ontro..ing o*2ect visi*i.it#continued6< changes that affect %ractices2?here are several methods to control o)Iect visi)ility20ide commandShow command0ide and Show commandLayers5eference Sets # $sed to define what is shown in an assem)ly.Page 2B 200!. Siemens Product Lifecycle Management Software Inc. All rights reservedSiemens PLM Software0. 1ontro..ing o*2ect visi*i.it#continued6< )est %ractices2$se the 0ide and Show command or layers to control o)Iect visi)ility.9on:t use )oth at the same time )ecause the 0ide and Show command only wors with o)Iects on visi)le layers.Parts migrated from I#deas will have some o)Iects on s%ecific layers+ so you need to now a)out layers.$nderstand Layers and 5eference Sets when using assem)lies.Page 27 200!. Siemens Product Lifecycle Management Software Inc. All rights reservedSiemens PLM Software1onc.usion6< )est %ractices23est %ractices )ased on design %rinci%les and design intent are still valid.Associativity+ structured design+ use of datums+ reuse of setches and featuresSome )est %ractices )ased on software )ehavior are no longer reCuired+ )ut may still )e a good disci%line.3456 coordinate systemSoftware changes may o%en u% new )est %ractices.4rganiAing setches+ using design features+ hole %atternsPage 2! 200!. Siemens Product Lifecycle Management Software Inc. All rights reservedSiemens PLM SoftwareMar LawrySiemens PLM Software Learning Media 9evelo%mentMar.LawryJSiemens.com;8,.;7B.;B77