The instruction nobody knows how to act on
Across the engineering industry, the same conversation is happening in boardrooms: leadership wants AI integrated into the workflow, and engineering teams are left figuring out what that actually means in practice. It is a reasonable ask with an unclear answer — and most attempts stall because they start with the technology rather than the problem.
The practical question is not "how do we use AI?" It is "where does our workflow have repetitive, data-heavy steps that slow engineers down?" Those are the exact places where AI creates meaningful value.
The right mental model for AI in engineering
Think of AI the way you think of a highly capable junior analyst. Given clear, structured inputs and a well-defined task, the output is fast and reliable. Given vague instructions and messy data, the output is unreliable. The quality of what comes out is entirely dependent on the quality of what goes in.
This is why AI performs poorly when asked to "generate a 3D model" from scratch — the task is too open-ended and physics-blind. It performs well when asked to automate a specific, repeatable task where the rules are known. The engineering judgment stays with the engineer. The repetitive execution gets delegated to the machine.
AI in engineering is not about replacing the engineer's judgment. It is about removing the friction between the engineer and the design.
Three places where AI creates real value
| Use Case | What AI Does | What the Engineer Does |
|---|---|---|
| Scripting & automation | Writes code to automate repetitive simulation tasks | Reviews output, validates results |
| Software integration | Bridges data between CAD and simulation platforms | Defines requirements, checks accuracy |
| Physics-informed design | Iterates parameters within engineering constraints | Sets the physics rules, approves final design |
1. Automating repetitive simulation tasks
Most simulation software — Ansys, Abaqus, SolidWorks — has a scripting interface. Engineers currently spend significant time manually clicking through menus to run batch simulations, export contour plots, or compile results into reports. AI can write these automation scripts in minutes, turning a half-day task into a background process.
The value here is immediate and low-risk. No new infrastructure is needed. The engineer describes the repetitive task in plain language, the AI produces a working script, and the engineer validates it once before deploying. Hours of manual work become a single command.
2. Bridging disconnected software systems
Engineering teams routinely work across software from different vendors — a CAD platform from one company, a simulation suite from another, a reporting tool from a third. Moving data between them is often a manual, error-prone process. AI can read the API documentation of both platforms and generate the integration scripts that connect them, eliminating a class of work that currently falls on the most experienced engineers.
3. Physics-informed design iteration
This is the most significant use case, and it requires the most thoughtful implementation. Rather than asking AI to generate geometry directly — which produces unreliable results — the smarter approach is to use AI as a design agent that operates on engineering parameters, not shapes.
The engineer defines the governing physics equations and the design constraints. The AI iterates over the input parameters, checks each iteration against those constraints, and only proceeds to CAD generation once the math is valid. When simulation results come back, the AI reads them and adjusts the parameters for the next iteration. The engineer sets the rules; the AI runs the loop.
Where AI does not belong
Not every engineering workflow benefits from AI. If your team works primarily on custom, one-off projects with no repeating patterns, forcing AI into that process adds complexity without returning value. AI earns its place in workflows with volume — repeated simulations, standardized design families, batch processing of test data.
The other boundary to respect is physics. AI models that operate purely on language patterns will produce outputs that look correct but violate engineering constraints. Any AI application in a mechanical context needs physics rules explicitly built in — either as hard constraints in the workflow or through a human validation step before anything gets manufactured.
The bottom line
The engineering teams getting the most out of AI right now are not the ones chasing the most sophisticated applications. They are the ones who identified one high-friction, repetitive step in their workflow and automated it. That single change frees up engineering time for the work that actually requires an engineer — and builds the internal confidence to go further.
Start with automation, build toward integration, and only pursue physics-informed design loops once the foundations are in place. For a deeper look at the AI concepts underpinning these workflows — including how agents orchestrate multi-step tasks — see our article on From LLM to AI Agent: The Magic of Tool Calling.