Wiki source code of Tekla Base Tools 15.1

Last modified by Thomas Gitsas on 2019/04/01 14:31

Show last authors
1 (% class="row" %)
2 (((
3 (% class="col-xs-12 col-sm-8" %)
4 (((
5 = Introduction =
6
7 Tekla Base Tools is the software that transfers a large amount of data from Tekla Structures to IMPACT, including element properties and geometry. If you would like to know more about the possibilities of transferring data into IMPACT for planning, then visit our website: [[https:~~/~~/strusoft.com/products/impact>>https://strusoft.com/products/impact]]
8
9 This is a guide for the completely renovated and boosted with functionality Tekla Base Tools. New workflow, new icons, improved performance and many more features that will be analyzed in this page. If some of your questions are not answered through our guide please check out our [[FAQ>>doc:.FAQ.WebHome]] page. Otherwise contact the support department of your country.
10
11 == //New User Interface// ==
12
13 A whole new data grid is implemented with technology borrowed from our flagship applications. It is now possible to search, group and categorize entire projects in a similar manner to our other applications.
14
15 [[image:UI.jpg]]
16
17 == //Performance// ==
18
19 This update improves performance and speed by more than 500% of the previous application. The core of the software has been replaced leading to an entirely new program.
20
21 == //Cast-Unit/Assembly orientated// ==
22
23 The new application will actively search for Objects Parent Assembly or Cast-Units when linking data from Tekla. This means that there is no longer a need to swap selection mode when selecting objects in Tekla Structures. Preferably, you select everything as Assemblies. By doing this, TBT no longer needs to do so much guesswork and it also allows us to reach data in Tekla which was previously not available to us.
24
25 == //Improved log system// ==
26
27 Some of the log items are now clickable and will select the corresponding item in the grid that the log message refers to.
28
29 == //New Workflow// ==
30
31 [[image:flow.jpg]]
32
33 The new workflow is linear and contains three steps.
34
35 === __//Link//__ ===
36
37 (((
38 This is the equivalent to the old ‘Get Selected’ command. When a Tekla object is linked to TBT, it will be tracked by the software as it used to.
39 )))
40
41 === __//Map//__ ===
42
43 Tell TBT what your linked Tekla object should be represented as in IMPACT. This step is similar to the old ‘Profile Mapping’.
44
45 === __//Save//__ ===
46
47 This command interprets, converts and save data to the IMPACT database. This command replaces the old ‘Put’ command.
48
49
50
51 = New Ribbon Commands =
52
53 == //Linking// ==
54
55 //[[image:linking.jpg]]//
56
57 In order to link elements, press the Link icon in the ribbon. This is the equivalent to the ‘Get’ command from the previous Tekla Base Tools versions. Always remember to have selected the assemblies that you want to Link from Tekla. When pressing Link, the following window will pop up.
58
59 [[image:importsettings.jpg]]
60
61 The highlighted window from above illustrates where the selected elements will be assigned on Floor, Building and Phase in IMPACT.
62
63 [[image:link_grid.jpg]]
64
65 The highlighted grid above allows you to preview the Tekla items that you are about to link into IMPACT. The new interface allows to remove unwanted items easily by right-clicking and removing them along with their corresponding groups (if necessary).
66
67 [[image:link.jpg]]
68
69 If you accidentally erased some of the items in the Tekla, then the command "Retake Tekla selection" will refresh the grid with the selected items from Tekla Structures. When you are sure that all the correct items are left on the grid, then select command "Link" in order to finish with the first step.
70
71 == //Mapping// ==
72
73 There are two ways of mapping components in the new Tekla Base Tools and a new way of mapping element marks. Mapping refers to what item X in Tekla should be represented as in IMPACT.
74
75 [[image:mapping.jpg]]
76
77 === __Automatic Mapping__ ===
78
79 __[[image:profile mapping.jpg]]__
80
81 Automatic profile mapping works as before. Select any profiles in your project and choose an IMPACT component to use with it. Simply click the assign button to complete the mapping. You can even save the mapping for later use by sending the mapping to a common mapping. The common mapping is saved per computer and can be used in all TBT projects.
82
83 **P.S. Click inside any of the grids and press CTRL + F to search. Tip: You can freely search in almost all grids across the software using CTRL + F.**
84
85 === __Element Mapping__ ===
86
87 __[[image:element_mark.jpg]]__
88
89 Items are normally given IMPACT element marks when they are saved to the IIMPACT database. You can override this by manually assigning items element marks. This is a requirement if you want to use manual component mappings. The reason is that if you don’t, you may have items overriding each other’s element data, and you don’t want that. It’s a built-in safety.
90
91 === __Component Mapping__ ===
92
93 [[image:component_mapping.jpg]]
94
95 For items with manual element marks its possible to assign a specific IMPACT component (//such as linked, hollow core, solid wall, etc.//) that is overriding the automatic profile mapping. Use this if you have multiple objects with the same profile in Tekla but you want them to represent two different components in IMPACT.
96
97 == //Saving// ==
98
99 //[[image:saving.jpg]]//
100
101 Saves items to IMPACT. Same as the old ‘Put’ command, but with interpretation and conversion transformed into one.
102
103 == //Updating// ==
104
105 //[[image:updating.jpg]]//
106
107 Use this command to check for changes in Tekla and IMPACT.
108
109 [[image:Refresh.jpg]]
110
111 Refresh does not check for any updates, it just rereads data into the main grid. Users of Project Manager will recognize this feature.
112
113 == //Other// ==
114
115 [[image:settings.jpg]]
116
117 Opens the settings dialogue.
118
119 [[image:other.jpg]]
120
121 Shows the About dialogue with build and version numbers. If you call the support, they will likely kindly ask you to show them this.
122
123 = Data Grid =
124
125 You will feel right at home with this new grid as it is built on the same technology used in our other applications. Remember to explore the context menu by right-clicking in the grid to access additional features.
126
127 [[image:big_UI.jpg]]
128
129 The statuses above are explained in the following table
130
131 (% style="margin-right:auto" %)
132 |(% class="box infomessage" %)(((
133 (% style="color:null" %)Up to Date
134 )))|(% class="box infomessage" %)(((
135 (% style="color:null" %)The item is up to date
136 )))
137 |(% class="box infomessage" %)(((
138 (% style="color:null" %)New/Updated
139 )))|(% class="box infomessage" %)(((
140 Item was either newly linked/re-linked or the object was updated with new information
141 )))
142 |(% class="box infomessage" %)(((
143 Modified in IMPACT
144 )))|(% class="box infomessage" %)(((
145 TBT detected changes in IMPACT since the item was last saved
146 )))
147 |(% class="box infomessage" %)(((
148 Modified in Tekla
149 )))|(% class="box infomessage" %)(((
150 TBT detected changes in the Tekla Model since the item was last saved
151 )))
152 |(% class="box infomessage" %)(((
153 Modified in Both
154 )))|(% class="box infomessage" %)(((
155 Displayed if both modified statuses occur at the same time
156 )))
157 |(% class="box errormessage" %)(((
158 Deleted in IMPACT
159 )))|(% class="box errormessage" %)(((
160 TBT could not find or contact the Sync IMPACT item. This also occurs if the IMPACT items are marked as deleted from IMPACT
161 )))
162 |(% class="box errormessage" %)(((
163 Deleted in Tekla
164 )))|(% class="box errormessage" %)(((
165 TBT could not find or contact the Sync Tekla item. This also occurs if the Tekla items are deleted in Tekla
166 )))
167 |(% class="box errormessage" %)(((
168 Deleted in Both
169 )))|(% class="box errormessage" %)(((
170 This status is displayed if both the deleted statuses occur at the same time
171 )))
172 |(% class="box errormessage" %)(((
173 Unknown
174 )))|(% class="box errormessage" %)(((
175 The objects current sync status could not be determined
176 )))
177
178 == //Data Grid Settings// ==
179
180 You can show/hide data columns in the data grid settings dialogue. You access it by clicking the spanner icon in the upper right of the data grid. These settings are saved per computer and are remembered between sessions.
181
182 [[image:data_grid_settings.jpg]]
183
184 == //Data Grid Properties// ==
185
186 Displays the properties of the selected item. If the item contains changes, these are shown in bold text with a yellow colour patch. Note that the new system also accounts for Teklas object and IMPACT model history. This way you can detect changes even if they are not part of the standard comparison set.
187
188 Teklas History is a live value, but if you modify the Tekla model without saving it, the Tekla History will not be updated. Thus, you may see at times that the properties differ, even if the modified time remains the same.
189
190 [[image:properties.jpg]]
191
192 = Menu Commands =
193
194 == //Main // ==
195
196 [[image:Project_folder.jpg]]
197
198 Opens the folder in which all TBT project files, backups and logs are stored.
199
200 == //Edit// ==
201
202 [[image:settings_menu.jpg]]
203
204 Settings - general
205
206 [[image:general_set.jpg]]
207
208 Settings - CIM
209
210 [[image:CIM.jpg]]
211
212 Settings - Reinforcement
213
214 [[image:reinforcement.jpg]]
215
216 Settings - File transfer
217
218 [[image:file_transfer.jpg]]
219
220 Settings - Status transfer
221
222 [[image:status_transfer.jpg]]
223
224 == //Tools// ==
225
226 [[image:tools.jpg]]
227
228 These execute the same commands as described in the Ribbon commands chapter.
229
230 [[image:backup.jpg]]
231
232 The backup command creates a backup, which will be stored inside your Tekla model folder.
233
234 [[image:reset.jpg]]
235
236 You can, of course, reset a Tekla Base Tools project. Do this if only if know what you are doing. Please note that resetting the project ONLY affects the Teaka <-> IMPACT connection. It will not touch either your Tekla or IMPACT project. This command will give a second warning before It executes. Once committed, it will wipe the TBT project and restart itself, allowing you to start from scratch.
237
238 **P.S. From this version and onwards, the old folders named //IMPACT.SyncModel// is no longer used.**
239
240 == //Help// ==
241
242 //[[image:support.jpg]]//
243
244 Takes you to our online support page with telephone numbers and email addresses to our different support divisions. If you want support for Tekla Base Tools, call or email the IMPACT support.
245
246 [[image:about.jpg]]
247
248 Shows the About dialogue.
249
250
251
252 )))
253
254
255 (% class="col-xs-12 col-sm-4" %)
256 (((
257 (% class="box" %)
258 (((
259 **Contents**
260
261 {{toc/}}
262 )))
263 )))
264
265
266
267
268
269
270
271
272
273
274
275
276 )))
Copyright 2018 StruSoft AB
Impact Documentation