Ground engineering AI
indomain knowledge.

Engineering knowledge and data for fastened joints

Connect standards, data and engineering experience.
Give engineers and software a shared technical foundation.

Expand an engineering problem Experience how AI verifies references

Explore engineering knowledge and use it in your work.

A continuously growing engineering knowledge mapselect a topic, explore associations

shared knowledge and dataATLASFrom the problem to the basis

Standards and MethodsVDI 2230

Use preload, loads and compliance to understand the basis and assumptions of a joint design.

THREAD DESIGNER^® ENGINEERING SUITE 4.0

Standards and DataKnowledge and Basisengineering and experience

downward exploration ↓

From an engineering question
to the underlyingrelationships.

Each knowledge entry shows how a concept works.
Inspect relationships, change inputs, review results and trace them to their source.
Follow the connection from preload to local response.

What happens to clamping force as external load increases?

The bolt and clamped members deform together. Part of the external axial load increases bolt force, while the remainder relieves clamping force. The residual clamping force determines whether the interface stays closed.

how to understand

While the interface stays closed, external load changes both bolt force and residual clamping force.

use conditions

This example uses a simplified coaxial linear elastic model. Check its assumptions for the joint you are studying.

basisTD Axiom · Preload connection relationship

Bring data
from a standardinto engineering practice.

Select a thread designation and follow its data from lookup to application.
Trace software inputs to the original engineering reference.

exploration specifications

Standard data summaryGB/T 196—2025

General-purpose threads · Basic dimensions

Each designation identifies a defined geometry.

Excerpt of basic thread dimensions, units in millimeters
specification	Major diameter d₂	basic minor diameter D₁

Excerpt from standard data · Edition and source retained

Basic dimensions and dimensional limits have their own definitions; tolerances and fits need to be selected separately.

structured parametersmm

M12 × 1.75Standard, numerical, and conditions are transmitted together

nominal diameter d: —
pitch P: —
basic major diameter d₂ / D₂: —
basic minor diameter D₁: —

With units, edition, and original table position

Geometric parameter preparationTD Forge

M12 × 1.75

From a common data foundation, start geometric parameter preparation.

Tolerance, model details, and engineering calculations are continued by professional software.

reference found

First clarify the standard version and specifications, so that the parameters have a verifiable starting point.

Numerical values are from the GB/T 196—2025 standard excerpt. Data transmission process is for functional demonstration.

An M30 joint
connects engineering knowledgeto actual results.

Under the same group of loads, thread profile, material, and data collection method
How does it change our understanding of local response?
Along the saved case in Forge, move from contour to individual tooth data

M30 × 3.5Common thread profile / MJ thread profile6 engaged threadsEngagement length 21 mm400 kN preloadthen lock adjustment length50 kN external loadaxial separation load

material modelanalysis step

Linear elasticity · final frame of external load · fine mesh

Kt · Actual thread-root area

M: 4.555
MJ: 4.230

The nominal stress is defined using the actual thread bottom area of each thread type, maintaining the same Kt diameter.

Let AI combine these conditions for explanation

Understand local response from stress concentration at each thread

Find evidence
forwith traceable evidence.

Raise questions and add conditions that influence judgment.
Charts, data, and explanations are associated accordingly
Each item can be expanded, and then proceed into specific engineering.

Atlas Engineering Knowledge Assistantready

engineer's question

It is the same M30 connection, why are the thread root responses different between M and MJ?

1
understanding problemsidentify engineering objects and goals
2
clear conditionsClarify the changes affecting the judgment
3
organization basisAssociate knowledge, standards, and usage conditions
4
form explanationReturn Conclusions to Evidence
5
engineering continuationBring the basis back to professional software

Problems and basis in the same viewwaiting to explore

First Clarify the Object, Then Define the Comparison Condition.

Understand the question before looking for evidence.

Click 'Start Collaborative Demonstration' to experience how a problem is clarified through conditions and forms a traceable professional explanation.

AI dialogue is pre-set guided; charts read existing cases, teaching curves are calculated locally. Each group retains its own object and conditions.

Use the same engineering knowledge
acrossdifferent projects.

Each software understands its own project and completes its own work.
Common knowledge, standards, and data enable professional capabilities to be interconnected.

TD Atlascommon knowledge and data

Method · Parameters · Evidence

Use with explicit version and conditions

TD Axiomunderstand current design

Trace each design input to its source.

From parameter definitions, material data, to VDI design methods, Atlas provides traceable references; Axiom combines current connections for design verification.

parameter definitionMaterial and StandardsTypical design case

AI collaboration direction within the software

Explain the Physical Meaning of This Input and Check if It is Suitable for the Current Operating Condition.

Explore TD Axiom

Take what you learn from one project
into thenext one.

Verified methods, organized experiments, and clearly explained failure cases are worth retaining.

Within clearly authorized scope, after organization and professional review, make engineering practice into reusable knowledge assets.

Start from real problems, test records, and design cases, retain the original conditions and results

engineering experienceRetain engineering experience

design casetest conclusionmethod validationteam knowledge

Build a shared knowledge base
one evidence-backed answerat a time.

The current prototype supports professional Q&A, standard queries, knowledge retrieval, and original text reading; it can trace references and data versions.

Professional problems and evidence co-displayStandard parameters and knowledge integrationSource and release version are traceable

TD Atlas real prototype, professional Q&A side shows knowledge citation, standard version, and original page number. — TD Atlas Prototype Real Interface · Professional Q&A and Source Reconsultation

Build and share
engineered knowledgeacross teams.

Bring the real problem in, leave the professional accumulation behind.
Welcome engineers, domain experts, developers, and industry partners.
Together improve the knowledge and data foundation of fastened joints.

engineer and team

Brings actual problems, trial scenarios, and verification feedback.

Domain Expert

Co-create specialized knowledge, engineering cases and professional verification

developer

Accessing standard data, knowledge and evidence services

industry and investment partners

Connect application requirements, content resources, and long-term construction.

Start from one worth solving professional problem.Contact us

Ground engineering AIindomain knowledge.

From an engineering questionto the underlyingrelationships.