Steel Fabrication BIM Workflow: Getting Tekla Data Into Your ERP

Steel fabricators face a unique challenge. Your Tekla Structures model contains everything needed for production: exact member sizes, connection details, bolt counts, and cut lists. But your ERP system, which handles purchasing, scheduling, and costing, cannot read Tekla files. Getting detailed fabrication data from one system to the other requires either manual data entry or a solid integration strategy.

This article explores practical approaches for connecting Tekla Structures to ERP systems in steel fabrication environments.

Why Steel Fabrication Data Is Different

Steel fabrication data has characteristics that make BIM-to-ERP integration both more valuable and more complex than in other construction segments.

High Data Density

A typical steel structure might contain thousands of individual pieces, each with specific dimensions, grades, and finishes. Unlike architectural elements that might be specified generically, every steel member is a distinct item that needs to be procured and tracked individually.

Tight Tolerances

Steel fabrication works to millimeter tolerances. Data errors that might be acceptable in general construction can cause serious problems in the fab shop. A beam cut to the wrong length is scrap.

Complex Assemblies

Steel connections involve multiple components: plates, angles, bolts, welds. A single connection might have dozens of parts that all need to be procured and tracked together.

Production Sequencing

The order in which pieces are fabricated matters for shop efficiency. ERP systems need to understand production sequences that come from the detailed model.

What Data Tekla Contains

Tekla Structures is remarkably data-rich. A well-developed Tekla model contains:

• Member geometry: Exact lengths, section sizes, and orientations for every piece.
• Material specifications: Steel grades, surface treatments, and finishes.
• Connection details: Every plate, bolt, and weld in every connection.
• Assembly relationships: How individual pieces combine into shippable assemblies.
• Fabrication data: Cut angles, cope dimensions, hole patterns, and mark numbers.
• Quantities: Weights by grade, piece counts by type, bolt counts by size.
• Drawing references: Links between model elements and shop drawings.

Tekla Export Options

Tekla provides several ways to get data out of the model.

Reports and Lists

Tekla can generate reports in various formats including Excel, CSV, and HTML. These use templates that can be customized to include specific attributes. For simple ERP integration, reports might be sufficient.

NC Files

For CNC equipment, Tekla exports NC files in formats like DSTV. While these are primarily for machine control, they contain data that can also feed ERP systems.

IFC Export

Tekla can export to IFC format, which can serve as an intermediate step for integration. However, IFC may not preserve all the fabrication-specific data that Tekla contains.

Tekla Open API

For the most flexible integration, Tekla provides a programming interface that allows direct access to model data. This enables custom applications that can extract exactly what your ERP needs.

Mapping to ERP Requirements

The structure of Tekla data does not map directly to how ERP systems work. Some translation is always required.

Parts vs. Assemblies

Tekla distinguishes between parts (individual pieces) and assemblies (groups of parts that are fabricated and shipped together). Your ERP might track only one of these levels, or might need both with different relationships.

Material Procurement

Tekla tracks finished piece properties. ERP needs to order raw material. Converting from fabricated member weights to stock material requirements involves calculations for waste, cutting efficiency, and available stock sizes.

Bolt and Hardware

Tekla models individual bolts with precise specifications. ERP might track bolts as inventory items ordered in bulk quantities. Aggregating detailed bolt data into procurement quantities requires mapping bolt specifications to purchasable SKUs.

Cost Centers

Tekla organizes by phases and zones. ERP organizes by projects and cost codes. Aligning these structures determines how costs get allocated in your financial systems.

Integration Patterns

Steel fabricators typically use one of several patterns for Tekla-ERP integration.

Pattern 1: Periodic Export

At defined milestones (design freeze, revision releases), generate Tekla reports and import them into ERP. This works when designs are relatively stable and real-time updates are not critical.

Advantages: Simple to implement, works with standard Tekla reports, minimal infrastructure required.

Disadvantages: Data can become stale between exports, manual effort for each update cycle.

Pattern 2: Automated Sync

Set up automated processes that monitor Tekla models and push updates to ERP when changes occur. This keeps systems more closely aligned but requires more infrastructure.

Advantages: Near real-time updates, reduced manual intervention, catches changes quickly.

Disadvantages: More complex to set up, requires handling of conflicts and errors.

Pattern 3: Middleware Hub

Use a dedicated integration platform that sits between Tekla and ERP. This hub handles data transformation, validation, and routing. Multiple systems can connect through the hub.

Advantages: Flexible, scalable, can connect multiple source and destination systems.

Disadvantages: Additional system to maintain, potentially higher complexity.

Practical Considerations

Handling Revisions

Steel models go through multiple revisions. Your integration needs to handle:

• Detecting what changed between revisions.
• Updating existing ERP records without creating duplicates.
• Tracking revision history for audit purposes.
• Alerting when changes affect already-procured materials.

Shop vs. Site Bolts

Bolts used in the fabrication shop versus bolts shipped for site installation often need different treatment. Shop bolts might come from inventory while site bolts are shipped with the steel. Your integration should handle this distinction.

Subcontracted Work

Some fabrication might be subcontracted. Data for subcontracted assemblies needs different handling, perhaps as purchase orders rather than production orders.

Getting Started

If you are looking to improve data flow from Tekla to your ERP:

1. Audit current process: How does data move today? Where are the bottlenecks and error points?
2. Define scope: Which data matters most? Start with highest-value items like main members before tackling everything.
3. Standardize Tekla setup: Consistent naming, attribute usage, and model organization makes export much easier.
4. Test with real projects: Integration that works in theory might struggle with real project complexity.
5. Plan for change management: New workflows affect how people work. Get buy-in from fabrication and procurement teams.

The Bottom Line

Steel fabricators who successfully connect Tekla to their ERP systems gain real advantages: faster quoting with accurate material costs, better production planning with real quantities, and fewer procurement errors. The technical integration is achievable with current tools. The key is taking time to properly map between the detailed world of fabrication modeling and the transactional world of ERP systems.

Interested in connecting your Tekla workflow to ERP? Check out our steel fabrication integration capabilities or reach out to discuss your specific situation.