- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Denunciar
The Truss Family is easy to use, but it lacks a bunch of features that structural engineers and designers need. Below are some enhancements that would make the family a lot more useful
More Web Member types.
Issue: When a truss is engineered it is almost always designed with more than one web member size. The members in the center are usually smaller than at the ends. The vertical web members are almost always different in size to the diagonal web members.
Suggestion: There needs to be an ability to create different sizes along the truss so that an economical design can be modeled easily. Currently there is only 1 web member size. 1 top chord size and 1 bottom chord size.
Currently the sizes of the individual web members can be changed once the truss is in the project. Unfortunately this is an instance only ability and does not reflect how trusses are used in building construction.
Truss Types.
Issue: Trusses are always defined as a type. There maybe 10 different types of trusses engineered with hundreds of those types used in a facility. Currently it seems the only way to create a type of truss with varying web members is to bring in a truss family, tab and select the individual web members and change the member size. The ability to change the size of individual web members is available once the truss family is in place but there is no way to have this change occur to the other types of trusses that are identical on the project. The current work around for this is to create a "Group" of the truss then copy it around to the different location where it will exist. While this approach gets the job done, using groups has several draw backs. Firstly using Groups in the numbers required to frame a building degrades the performance of the model substantially. Secondly once grouped beams and framing members attaching to the group no longer behave correctly, they dont attach as they would if the truss wasnt grouped. Thirdly groups seem to create export errors when using navis, the members dont always show with the correct family.
Suggestion: Allow custom changes to be saved to the family as a type rather than an instance change.
Truss Depth
Issue: Trusses are always detailed with a truss height defined. Currently when using the truss family template the top and bottom chords are located by there center of gravity/Center "y" location. Hence the height of the truss varies depending on the size of the top and bottom chord members See below
As you can see, there is a WT bottom chord and a Wide Flange Top chord. each has different depths, while the center to center of these members is 10'-0" the Out to out size is different.
The only way to fix this is to look up the different sizes of the top and bottom chord and subtract half of their depth from the truss depth. While this works it is not ideal. The truss depth has to vary from truss type to truss type depending on the sizes used. when chord sizes vary by small fractions of an inch, truss depths become in accurate.Out to Out of truss is what is important when modeling, not analytical location to analytical location.
Suggestion: Allow the graphical location of the element being used as a top or bottom chord be defined as top or bottom. Currently only the analytical location can be defined.
Truss Gusset Web Connections
Issue: Truss use gusset plates at the connection of the web members to the top and bottom chords of the truss. These gussets can become very big and create coordination conflicts with other diciplines who need to route utilities through the truss space. There is currently no way to add additional members to the truss family to model these accurately or to create a no fly zone collission element where the truss connection is. Because of this, any design over LOD300 cannot use the OTB truss family as part of the model.
Solution: Allow connection components to be inserted into the truss
Truss top and bottom connection
Issue: Projects that use trusses normally have a truss top chord plan and a truss bottom chord plan. This is because trusses are normally in excess of 8'-0" deep. Currently you can only connect members such as purlins and bottom chord bracing to the bearing chord selected in the truss instance properties. (see below)
If additional members need to be attached they need to be assigned to a different level. these elements dont connect to the truss and as such, their symbolic offsets dont work creating graphical representation errors on plan. Because they dont attach, they also do not move with the element if trusses move during the building designs evolution.
Solution: allow framing members to attach to both the top and bottom chord of a truss
¡Resuelto! Ir a solución.