Tekla Connection Libraries that Scale
Naming by intent, parameter discipline, fabricator-ready details.
For structural detailers maintaining a connection library across more than two projects. Naming conventions, parameter discipline, and the fabricator handoff.
- Apply intent-based naming to a connection library
- Limit user parameters without losing flexibility
- Build a fabricator-ready detail pack
- Maintain a library across three projects without forking
- 014 lessons · 60 min
Naming by intent
- 024 lessons · 60 min
Parameter discipline
- 035 lessons · 75 min
Detail pack standards
- 045 lessons · 75 min
Library maintenance
Tekla connection libraries grow organically. By the time a team has shipped three buildings, the connection folder reads like an archeology dig. This course is the curation discipline that keeps the dig site survey-able.
Articles from our editorial team
Connection design review automation in Tekla
Reviewing 5,000 connections manually is impossible. Rule-based filters reduce the review to a 30-line exception report.
Tekla custom components: the maintenance trap
A third of custom components break across major Tekla releases. Three habits keep them maintainable across version upgrades.
CIS/2 vs IFC for steel: when to choose each
CIS/2 is the steel industry's native format; IFC is the all-discipline lingua franca. Picking right depends on receiver, not personal preference.
- Revit Fundamentals
Revit Family Authoring
Parametric design, naming conventions, performance — author families that survive five projects.
- BIM Coordination
BIM Coordination Workflows
Clash detection, federated models, and the meetings that actually move work.
- Structural
AutoCAD for the Modern Office
Sheet sets, block standardisation, plot routines — the long tail of DWG work.