Prepare the Tekla model for Fabbim

Importing an IFC model into Fabbim does not really begin when the file is exported. It starts much earlier, in the way the fabrication model has been organized in Tekla Structures. A well-prepared model allows Fabbim to correctly understand assemblies, retrieve the right properties, and turn this information into usable tracking data for the workshop, loading operations, galvanizing partner, and construction site.

On the other hand, a poorly structured model can create immediate difficulties: assemblies that are too large or badly broken down, inconsistent marks, missing useful properties, confusion between parts and sub-assemblies. The goal of this page is therefore to explain how to prepare Tekla so that the import into Fabbim is simple, logical, and reliable.

Purpose of model preparation

Fabbim needs a clear structure to connect the digital model to real field operations. That means the model must make it easy to find what will actually be physically handled: an assembly, a part, a lot, a package, or a logistics flow depending on how the project is organized.

Model preparation therefore aims to:

• identify the right assemblies to track;
• ensure consistency of marks and properties;
• facilitate IFC export;
• make the import more readable in Fabbim;
• prepare label printing and field scans;
• reduce errors in fabrication and transport workflows.

Organize assemblies properly

In Tekla Structures, the assembly is one of the most important building blocks for Fabbim. It is often what will serve as the field reference: it is isolated in 3D, its label is printed, it is scanned, loaded, and received.

In practice, it is recommended that each assembly corresponds to a logical and transportable element. Depending on the project, this may be:

• an assembled column;
• a beam;
• a truss;
• a façade element;
• a staircase;
• a sub-assembly ready to be handled.

When assemblies are too large, too abstract, or too far removed from workshop and site reality, tracking becomes less practical. Fabbim works better when the model structure reflects the objects that are actually handled.

What is better to avoid

• huge assemblies grouping too many heterogeneous elements;
• unstable assembly marks;
• objects not attached to the correct parent assembly;
• a modelling logic that does not match the real project flow.

Attach parts correctly

Fabbim does not only display a general mark. The platform also uses the individual parts that make up an assembly. This makes it possible to view details, calculate weights, visualize elements in the 3D model, and build more accurate logistics workflows.

Each part must therefore be attached to the right assembly. This consistency is essential in order to:

• avoid a part ending up in the wrong assembly;
• improve readability at import stage;
• achieve better traceability by mark;
• make exports and label printing more reliable.

Take care of marks and naming

In a structural steel project, marks are at the heart of communication between the engineering office, workshop, logistics teams, and construction site. If marks are unclear, duplicated, or unstable, the whole tracking system becomes less efficient.

It is therefore advisable to check that:

• assembly marks are clearly defined;
• part marks are consistent with your production method;
• the names used will remain understandable in Fabbim, on labels, and during scanning;
• any lots, zones, or workflows are usable through exported properties.

Check the properties useful to Fabbim

Fabbim relies on the information contained in the IFC file to structure the project. Good preparation therefore also means checking the properties that will actually be exported.

Among the information generally useful, you will find:

• the IFC GUID;
• the assembly name or mark;
• part marks;
• the profile;
• the material;
• the length;
• the weight;
• lot, phase, zone, or workflow information depending on your organization.

This data is not only used to display a row in a table. It allows Fabbim to generate a usable project view, feed exports, prepare shipping lists, and track status changes.

Prepare the workflow logic

One of Fabbim’s main strengths is extending the model into real logistics operations. That is why it is useful to anticipate, from the model preparation stage, the workflow logic you want to track afterwards.

For example, a flow can be structured as follows:

1. workshop fabrication;
2. departure preparation;
3. truck loading;
4. sending to galvanization;
5. return to workshop;
6. delivery to site;
7. reception;
8. installation.

If groups, phases, zones, or logistics routes are already identifiable in the model or associated data, the integration into Fabbim will be much more powerful. The platform will be better able to filter, group, and display information.

Checks to perform before IFC export

Before launching the IFC export, it is recommended to carry out a few simple checks. These checks can avoid a large share of import problems.

• check that the important assemblies are properly created;
• check mark consistency;
• check that parts belong to the correct assembly;
• confirm that the necessary properties are properly filled in;
• avoid unwanted or useless objects for traceability;
• make sure the project breakdown logic remains understandable.

This control step does not necessarily take much time, but it greatly improves the quality of the final result in Fabbim.

What you gain in Fabbim

A well-prepared Tekla model immediately produces better results in Fabbim:

• a cleaner import;
• assemblies that are easier to find;
• more readable 3D views;
• more relevant labels;
• a better link between design office, workshop, and site;
• more reliable traceability throughout the project.

In other words, model quality directly influences field usability. That is why this preparation stage is so important.

Recommended best practices

To summarize, here are the main best practices to keep in mind before exporting to Fabbim:

• think of assemblies as elements that are actually handled;
• stabilize marks;
• structure parts clearly;
• fill in properties useful for production and logistics;
• anticipate label, scan, and workflow needs;
• check the model before IFC export.

Conclusion

Properly preparing the Tekla model is one of the best ways to obtain a Fabbim project that is clear, reliable, and directly usable. A good assembly structure, consistent marks, and well-filled properties make it possible to go far beyond the technical import of a file: they lay the foundation for real operational traceability.

The more the model reflects fabrication and logistics reality, the more useful Fabbim becomes on a daily basis for the workshop, transport, and site teams.

FAQ

See also