Getting Started

Contents

Introduction to braced

Braced is a web app where you can solve your structural steel joints. You can do calculations in the cloud, save them, and then serve to your Tekla modelers. We try to document everything so you will be aware at any time of what are you doing. An insight in forty seconds:



First Steps

Well, if you want to get started with this app, you will need to register. Keep in mind that you cannot do anything but create the connection in Tekla. The whole thing resides here, in braced.io.

Input dimensions, forces, solve the connection, all here. Manage calcs, publish/hide to Tekla, all here. Manage projects, structures, materials and profile libraries, all here. Once you get the work done here, our plugins will do the job for you in Tekla Structures. And that's it.

The next video shows you how to sign up and make your first joint in Tekla with a built-in example. You will have those example once you sign up.



Workflow

The braced.io workflow is divided into two steps:

  • Connection design through the web interface
  • Connection modelling through the tekla plugins

Example: an engineer opens a braced enginesheets and configures her joint. She then gets the results computed in the cloud and verifies them.

Now, she can save PDF or TXT reports to her desktop and include them in calculation notes. Then, she saves calculations and the BIM modelers can access directly through the Tekla Structures plugins. The concept of saving a calculation is slightly different from the ussual. You will save the calc in the cloud. Meaning, the calc will be accesible and may be published to Tekla. It is very usefull and the core of braced workflow. Nothing else to do.

Working in braced, each user creates a lot of data. Of course if you want you can bulk view, download or delete all your data.

Tekla workflow schema

Builtin Database

There are several builtins: materials, profiles, bolts, etc. These are the most used items in Europe. You can use them or you can build your own. Everything is managed from the "Database" panel.

When setting up your own items, you have a form to specify the item properties. When saving, they will be automatically available in the enginesheets. You can upload tekla *.lis files and the cloud system will try to import as many as it can.

Data Structure: Teams, Projects, Structures, Users

This section covers the main arrangement of the data in the platform.

Tekla workflow schema

You have a relational drawing above. Teams are composed by users. Project, structures, custom materials, custom profiles and calculations, all belong to teams. If a user has no team, she will actually belong to a default one-user-team.

In the following table, we review each element properties:

Element Belongs to Has
Team --- Every element created
User Team User preferences.
Project Team Structures
Structure Project Calculations
Calculation Structure A creator (user), database elements, etc.
Custom Database Team Materials, profiles, bolts.