A Tekla Structures package should state what is modelled and to what level of detail, which Tekla version and environment the native model must open in, which exchange files are required (IFC, DWG/DXF, PDF, DSTV NC), how numbering and phasing are set up, and whether fabrication drawings are part of the scope. "Tekla model" on its own means very different things to different suppliers.
What is the difference between a model-only and a model-plus-drawings package?
A model-only package delivers a Tekla model at an agreed level of detail. A model-plus-drawings package adds the assembly, single-part and erection drawings a fabricator works from, along with the drawing checking and revision control they need. That difference changes price and schedule, so state which of the four scope types below you are buying.
| Scope type | Typical content | Typical use |
|---|---|---|
| Coordination model | Main members, approximate connections, correct envelopes | Clash checking, layout, piping coordination |
| Detailing model | All parts, bolts, welds and fittings; numbered | Basis for fabrication drawings and NC data |
| Model plus drawings | Detailing model plus assembly, single-part and erection drawings | Full fabrication package |
| Model update | Revisions to an existing client model | Brownfield or design changes |
At PetroHill we state this explicitly: fabrication drawings are additional unless they are included in the model scope.
Define the modelling scope and level of detail
Write down:
- Structures included: for example racks PR-01 to PR-04, platforms P-101 to P-108.
- Elements included: primary steel, secondary steel, grating, handrails, stairs, ladders, pipe support steel, embeds.
- Connection detail: full connection modelling, or simplified representations for coordination.
- Non-steel items: concrete foundations as reference objects, equipment as reference models.
- Level of detail: if you use LOD/LOI terminology, attach a definition. LOD labels are interpreted differently between organisations.
Which Tekla version should the model be in?
Tekla Structures is released in yearly versions; Trimble's documentation currently covers Tekla Structures 2026. Trimble's documentation states that Tekla Structures versions "are not backwards compatible": a saved model cannot be opened in older versions because of database differences. If your fabricator or EPC team uses a specific version, the supplier must model in that version or one you can open. Also confirm the environment (region and role settings), any firm folder, and the custom components or profiles your project uses. Mismatched environments produce different profiles, materials and drawing styles.
Which exchange formats should a Tekla package include?
Most industrial steel packages need the native model for future revisions, IFC for coordination with plant design tools, PDF for review and issue, DWG or DXF for CAD users and plate nesting, report files for quantities, and DSTV NC files only where the fabricator's machines use them. Agree each format, its version and its export template before modelling starts.
Trimble lists the formats Tekla Structures can import and export. The common ones for industrial steel packages are:
| Format | Typical purpose | Notes |
|---|---|---|
| Native Tekla model | Ongoing detailing, future revisions | Version-dependent; agree ownership |
| IFC (IFC2x3 / IFC4) | Coordination with plant design and other BIM tools | Agree the property sets required |
| DWG / DXF | 2D drawings for CAD users; DXF for plate nesting | Agree the layering and the export template |
| Review and issue drawings | Include revision and status | |
| DSTV NC (.nc1) | CNC machine data for profiles and plates | Tekla does not create DSTV NC files for curved beams, because the DSTV standard does not support them. Plates can be converted to DXF where the shop requires it |
| Reports (CSV/XLSX/PDF) | Member, bolt and part lists; MTO | Agree the template columns |
Numbering, phases and reports
Numbering assigns marks to identical parts and assemblies and must be complete before shop drawings are created. Agree the following in advance:
- the prefix and start-number convention by structure or area;
- whether phases represent areas, erection sequence or shipping lots;
- report templates for the MTO, bolt lists and assembly lists.
Changing the numbering convention halfway through a project is expensive, because it ripples through every drawing.
Handover checklist
- Native model in the agreed version, with the model folder and any custom attributes
- IFC export with the agreed property sets
- Drawings in PDF and DWG (if in scope), with a drawing register
- NC files organised by part mark
- Reports in the agreed templates
- List of custom components used and any limitations
- Open assumptions and holds list
Frequently asked questions
Can you work inside our existing Tekla model?
Often yes, by agreement. This requires a compatible version, a shared environment and a clear process for model sharing or merging.
Do we need IFC if we have the native model?
Usually, yes. Plant design and coordination tools commonly consume IFC rather than native Tekla files.
Are NC files always included?
No. NC data is a separate deliverable and should be requested explicitly, with the CNC format your shop uses.
Next step
Confirm your Tekla version, environment and deliverables with us before scoping. See 3D structural modelling and plant model support or confirm your setup.
References
Technical sources consulted. Standards are paid documents; confirm clauses against the licensed edition named in your project specification.
- Tekla Structures data exchange formats (2026) · Trimble (opens in a new tab)
- NC files (2026) · Trimble (opens in a new tab)
- Quick start to Tekla Structures drawings (2026) · Trimble (opens in a new tab)
- Save a model (2026) · Trimble (opens in a new tab)
