Speckle Impl Tekla

speckle-impl-tekla

Quick Reference

Connector Capabilities

Data Schema Hierarchy

Root Collection
  └── Tekla File
        └── Type (Beam, Column, Plate, etc.)
              └── TeklaObject

Critical Warnings

NEVER attempt to receive/load data INTO Tekla Structures -- the Tekla connector is PUBLISH-ONLY. There is NO receive functionality. If a workflow requires loading data into Tekla, use an intermediate format (IFC) or request the feature via the Speckle Community Forum.

NEVER expect assemblies in the published output -- Tekla assemblies are NOT published to Speckle. Only individual parts (beams, plates, bolts, etc.) are converted.

NEVER publish from a Tekla drawing view -- the connector ONLY works from the model viewport. Attempting to publish from drawing views ALWAYS fails. ALWAYS switch to the model viewport before publishing.

NEVER expect drawing layouts, title blocks, or annotation data in the Speckle output -- drawings are NOT part of the published data.

NEVER expect numbering series or sequence settings to appear in the published model -- these Tekla-specific organizational constructs are NOT converted.

NEVER expect nested TeklaObjects -- TeklaObjects do NOT contain child TeklaObjects. Each structural element is a flat, independent object in the hierarchy.

Publish-Only Architecture

The Tekla connector is fundamentally different from bidirectional connectors (Revit, Rhino, Blender). It supports ONE direction only:

Tekla Structures  ----[publish]---->  Speckle Server
                  <---[receive]----  NOT SUPPORTED

Why This Matters

• Coordination workflows: Tekla models can be federated with Revit/Rhino/Archicad models in Speckle for visual review, but changes NEVER flow back into Tekla automatically.
• Round-trip is impossible: Any modifications in Speckle or other tools ALWAYS require manual re-creation in Tekla.
• Automation scope: Speckle Automate functions can analyze Tekla data but NEVER push results back into Tekla.

TeklaObject

Type Definition

TeklaObject extends DataObject with the following structure:

Properties.Report Contents

The properties.Report dictionary contains aggregated Tekla-native data:

Geometry

• ALWAYS stored in displayValue as an array
• Typically Brep (boundary representation) format for steel profiles
• Plates and other flat elements also use Brep
• Bolts are represented as simplified geometry

Publishable Objects

Supported Elements

ALL selectable model objects in the Tekla model viewport:

NOT Published

Publishing Workflow

Step-by-Step

1. Open model viewport -- ALWAYS verify you are in the model viewport, NOT a drawing view
2. Select objects -- Select the structural elements to publish, or use filters
3. Open Speckle connector -- Access via Tekla Extensions menu
4. Choose project/model -- Select the Speckle project and model to publish to
5. Publish -- Send selected objects to Speckle

Selection Strategies

Federation with Other Connectors

Tekla models are ALWAYS consumers in federated views, never the destination for incoming data:

Revit Model --------\
Rhino Model ---------+--> Speckle Server --> Federated View (Viewer/Power BI)
Tekla Model --------/                   \--> NEVER back to Tekla

Common Federation Patterns

Proxy Architecture

The Tekla connector uses ONLY one proxy type:

RenderMaterial Proxy

• Material appearance data stored at Root Collection level
• Referenced by TeklaObjects via applicationId
• Contains color, opacity properties
• Does NOT contain textures (Speckle NEVER transfers textures)

Platform Constraints

Reference Links

• references/methods.md -- TeklaObject properties, publish API, selection methods
• references/examples.md -- Working publish workflows, federation patterns, downstream data access
• references/anti-patterns.md -- What NOT to do with the Tekla connector

Official Sources

• Tekla Connector (User Docs): https://docs.speckle.systems/connectors/tekla.md
• Tekla Schema: https://docs.speckle.systems/developers/data-schema/connectors/tekla-schema.md
• Speckle Community Forum: https://speckle.community/