Precast Custom ComponentsPrecast_Custom_Components
Embed Size (px)
Transcript of Precast Custom ComponentsPrecast_Custom_Components
Tekla Structures User Meeting 2008
Custom ComponentsBy: Glen Hutchinson
Custom Component QuizA. Column to SpandrelB. Column to IT BeamC. Spandrel to Double TeeD. Pad Footing to ColumnPosition TypeEndend PlaneMiddle PlaneCollision PlaneBox Plane
Custom Components QuizMiddle PlaneA. Column to Spandrel
Custom Components QuizBox PlaneB. Column to IT Beam
Custom Components QuizCollision Plane
Custom Components QuizEndend Plane
Custom Components AgendaCCs and Database SizeASCII FilesCreate an ASCII fileCC .INP BackupCC LocationBest Practices
- CCs & Database Size V13.1
CCs & Database Size V14.0 >On average, 5 are not defaultStore 10,000 Attributes50% less
ASCII FilesASCII simple text fileAmerican Standard Code for Information InterchangeTab delimited Columns
ASCII FilesScenario6 Plates, varying in size
Parameters vs. ASCIIParameters = 11, Dist. = 2, Tot. = 13
ASCII = 6, Dist. = 2, Tot. = 8
Benefits of using ASCIIModifying the CC is much EasierDont have to mess with the .inp filesAdding Variables, much easierThe R&C are organized, tableLess attributes in the model
Custom Component .INPSave a Custom Component an .inpAlso a .inp.bakUseful when creating CCs that contain pictures in them.
Model folders contain CustomComponentsDialogFilesAll CC .inp and .inp.bak are stored
Best PracticesKeep It Light Only Bind objects that you have toKeep intelligence to a minimumKeep It SimpleDont detail every little thingModel only what you have to, so you can understand what the object is in the drawings.
Tips and TricksAdd a line separating the variables CCEdit the ***.inp located in CustomComponentsDialogFilesChange numberSave ***.inpReopen the Model
Tips and TricksProtect CCs with a PasswordName = PasswordType =TextValue = Your PasswordCannot be edited without the Password
The technical change was that in previous versions we stored all attributes of a component for each instance of that component. So e.g. if component contained 30 attributes (bindings, dimensions,parameters . . .), and in the model were 2000 components, we stored 60000 attributes in db1.
In 14.0 we store for each component instance only those attributes that have been changed from the default value. So if you have the same component containing 30 attributes, and on average 5 of them with non-default values, we end up in storing 10000 attributes, so only 20% compared to theprevious version.
Lets say that we have 6 standard plates as an example. *In reality you have 6 individual Custom Components, which is fine. *For the purposes of a demonstration of this functionality we are going to say that we have 6 standard Jumper Plates. *Rather than knowing what each individual dimension is we can us a file. *This file will have all of our standards in it. We can then reference this file in a Custom Component, similar functionality to Vlookup in Excel.* The Format that we will use is a .dat format which is an ASCII file.Dont have to mess with .inp filesAdding variables is much much easierThe Rows & Columns are organized in a table like environmentThere will be less attributes in the model