DUCTILE: Agentic LLM Orchestration of Engineering Analysis in Product Development Practice
Organizations: Product Development Division, Department of Mechanical Engineering, Chalmers University of Technology, Gothenburg, Sweden · GKN Aerospace Engine Systems, Trollhättan, Sweden
Abstract
Engineering analysis automation in product development relies on rigid interfaces between tools, data formats and documented processes. When these interfaces change, as they routinely do as the product evolves in the engineering ecosystem, the automation support breaks. This paper presents a DUCTILE (Delegated, User-supervised Coordination of Tool- and document-Integrated LLM-Enabled) agentic orchestration, an approach for developing, executing and evaluating LLM-based agentic automation support of engineering analysis tasks. The approach separates adaptive orchestration, performed by the LLM agent, from deterministic execution, performed by verified engineering tools. The agent interprets documented design practices, inspects input data and adapts the processing path, while the engineer supervises and exercises final judgment. DUCTILE is demonstrated on an industrial structural analysis task at an aerospace manufacturer, where the agent handled input deviations in format, units, naming conventions and methodology that would break traditional scripted pipelines. Evaluation against expert-defined acceptance criteria and deployment with practicing engineers confirm that the approach produces correct, methodologically compliant results across 10 repeated independent runs. The paper discusses the paradigm shift and the practical consequences of adopting agentic automation, including unintended effects on the nature of engineering work when removing mundane tasks and creating an exhausting supervisory role.
Figures & tables
| Req. | Requirement name | Description | Supporting literature |
|---|---|---|---|
| R1 | Inspectability | Agentic application (prompts, plans, tool calls, intermediate artifacts) must be directly inspectable by engineers/auditors; no hidden state. | [ 17 , 18 ] |
| R2 | Reproducibility | Model, prompt, tool versions and inputs must be pinned and logged; runs are reproducible or cause - attributable despite stochastic LLM steps. | [ 18 , 17 ] |
| R3 | Deterministic execution boundary | Safety/engineering computations run in verified, deterministic tools; the LLM performs orchestration and code generation only. | [ 18 , 51 ] |
| R4 | Traceability & auditability | Every artifact is trace - linked to the generating step (arguments, stdout/stderr, checksums, timestamps) to support do/check/approve reviews. | [ 17 , 18 ] |
| R5 | Data governance | Deployment mode (on - premises/API) and data flows comply with confidentiality/export/privacy rules and are justified. | [ 17 , 18 ] |
| R6 | Human oversight & accountability | Engineers review plans and sign off on outputs; autonomy is limited to orchestration, not engineering judgment. | [ 17 ] |
| S-Basis | B-Basis | A-Basis | |
| Pass probability | |||
| Required | 5 | 29 | 299 |
| DUCTILE recommended values | |||
| Development | |||
| Deployment | |||
| Deviation | What changed | Impact on automation |
|---|---|---|
| File format | YAML instead of JSON | Requires new parser |
| Unit system | Imperial instead of SI | Silent error |
| Node naming | right/left instead of port/starboard | FEM run fails downstream |
| Method change | 1.04 factor on Fx forces | Silent error |
LLM Agent Orchestration
Large language model agent orchestration coordinates models, tools, and workflows to complete complex tasks reliably and efficiently.
See all 458 papers