What we automate

The whole path,
parameters to the files.

The sequence your engineers already follow, executed by software. One process, whatever the structure.

The pipeline, five stages

01

Parameters

You describe the structure.

Your structures repeat. Same family, same rules, same checks, and only the numbers change. So why not standardise the input and automate everything behind it? You enter it once, in the terms your engineer already thinks in. Nothing is modelled by hand after this.

You enterExamples, based on the structure
Geometry
Spans, levels, belt routing, bay spacing, the frame type.
What it carries
Belt and material, equipment, hoppers, cranes, access and walkways.
The site
One location. Terrain, altitude and exposure follow from it.
The code
EN 1990, EN 1991 and EN 1993, with the national annex of the country you build in.

A gallery needs belt routing and spans. A hall needs bay spacing and eaves. The list follows the structure.

02

Conditions and loads

The location shapes the loads.

Type the location. Snow, wind and thermal come back to EN 1991, from the national annex of that country, with terrain and altitude already in them. Each one is then applied where it acts, in the unit the member takes. Then every load combination required by EN 1990 is generated. All the work that used to take days, with no real engineering in it, is finished in minutes.

The tool buildsExamples, based on the structure
Site actions
Snow, wind and thermal to EN 1991, read from the location against the national annex.
Carried loads
Belt and material, equipment, hoppers, cranes and access.
Application
Point, line and area loads, kN, kN/m or kN/m², put on the members that carry them, with the loaded area of each one taken from the geometry.
Supports
Boundary conditions, constraints and member releases, set with the model.
Combinations
Every EN 1990 combination, in full. Hundreds of them, not the handful anyone assembles by hand.
Traceability
Every action and every factor carries the clause it came from.
03

Analysis, checks and optimisation

Your existing solver runs the analysis.

Any solver with a programmable API can be driven the same way, and SAP2000 runs in production today through its OAPI. The others follow the same route, and each one gets built when a contract needs it rather than before. DTJ automates around the tool your office already trusts and does not replace it.

  • SAP2000In production
  • ETABSRoadmap
  • STAAD.ProRoadmap
  • Autodesk RobotRoadmap
  • SCIA EngineerRoadmap
  • Code_AsterRoadmap
  • OpenSeesRoadmap

Each one gets built into the contract that needs it.

The tool runsExamples, based on the structure
Code checks
Cross section, buckling, stability and deflection, on every member and every combination.
The code
EN 1990, EN 1991 and EN 1993 today. AISC, IS and AS are roadmap, built into the contract.
Governing member
Found, marked in red, and given the section that fixes it.
Optimisation
A genetic algorithm searches whole section sets, so the structure you get is an efficient one and not the first one that passes. It saves engineering hours, and steel in the structure itself.
04

Documents

One run writes every document.

Written from the same run that produced the results, so nothing is retyped and nothing can disagree. The document you hand to the verifying engineer, plus the other documents a project needs.

You receiveExamples, based on the structure
Calculation report
The full document, front to back: the introduction and basis of design, the site with the code and national annex it follows, the environmental conditions, the materials and partial factors, the model, then every member check.
Foundation loads
Reactions at every support, in the form the civil engineer asks for.
Material takeoff
Raw material list and bill of material, measured off the model.
Formats
Word, ODT and PDF, so the document stays editable in your office.
05

Drawings

The same model becomes the drawing.

Drawn from the same geometry that was analysed, at the depth your office actually needs. The drawing agrees with the calculation because both came from the same source.

You receiveExamples, based on the structure
General arrangement
Cross sections, elevations, plans, parts list and notes, together on one sheet.
Details
Connections, base plates and foundations, drawn to the depth you agree.
Formats
Native AutoCAD files, DWG or DXF, that your drawing office opens and edits like any sheet on your server.
Scope
The drawing set is written into the contract, not fixed in advance.
Generated steelwork general arrangement sheet, softened, cross section, elevations, roof plan and connection details laid out on one sheet
Confidential

And again

A change late in the project costs one run.

Move a span, add a hopper, change the location. The chain runs from the top and every document comes out agreeing with every other, because they all came out of the same run. By hand, a late change means most of the five stages above, again. That is where the hours go, and it is the reason to automate your engineering.

The same structure, two ways

Measured in production, on a conveyor gallery
The work By hand With DTJ
Model setup Built node by node, member by member, click by click. Generated from the parameter set.
Loads and combinations Actions looked up in the annex, resolved onto members by hand, combinations assembled one by one. One location. Every action applied where it acts, every EN 1990 combination generated.
Section sizing Resize, rerun, compare. Stop at the first set that passes. An algorithm searches whole section sets for an efficient one.
Code verification Spreadsheets and hand checks, member by member, combination by combination. Full EN 1993 on every member and every combination, every run.
Documents The report assembled result by result, the foundation loads and the material lists counted off the model by hand. Report, foundation loads and material lists, all written from the run that produced the results.
Drawings The same geometry redrawn a third time for the drawing office. A dimensioned general arrangement from the same source data.
A change late in the project Most of the above, again. One rerun, and the whole package agrees again.
Engineering hours, one structure 150to200+ <5
Your pipeline

Which step would you automate first?

Tell us where your engineers lose the most hours. You get an answer on whether that step is worth automating, from the person who would write it.

No tracking, no analytics contact@dtjtech.eu