WP-06 Agentic CAD to CAE Orchestration
| Field |
Value |
| Priority |
Medium-high |
| Status |
Framing |
| Problem Space |
CAE and simulation automation |
| Linked Capability |
workflow orchestration, simulation setup, uncertainty-aware control |
| Best Collaboration Shape |
thesis + prototype + later applied project |
| Owner |
unassigned |
What This Work Package Is
Coordinate multiple CAD-to-CAE workflow steps with agentic checkpoints, instead of optimizing only one preprocessing subtask in isolation.
Why It Matters To RapidDraft
- moves from point automation to workflow automation
- supports a stronger "engineering copilot" story
- creates room for evaluation on real multi-step tasks
Candidate Lanes
| Lane |
People or Group |
Why They Matter |
Best First Ask |
Priority |
| Fraunhofer ITWM |
Joachim Linn |
strongest current signal for model-reduction and simulation orchestration |
later-stage applied project fit-check |
High |
| TH Ingolstadt CA-methods lane |
Thomas Binder |
practical student-project angle for CAE workflow assistant behavior |
thesis or student-project discussion |
High |
| Hochschule München execution lane |
Vahid Salehi Douzloo |
practical execution route with local speed |
applied prototype discussion |
Medium |
| Fraunhofer IGD interactive engineering |
Daniel Weber |
useful where orchestration needs engineering-facing interaction and acceleration |
technical exchange |
Medium |
Recommended Next Actions
- Define the first orchestrated workflow boundary clearly.
- Avoid turning this into a broad autonomous-agent narrative too early.
- Keep evaluation focused on engineering-time reduction and failure handling.
Open Questions
- Which exact handoff points should the first orchestration prototype cover?
- Is uncertainty-aware control necessary in v1 or only later?
Sources
TextCAD/04_Marketing and Outreach/13_Universities/deep-research-report Balanced.mdTextCAD/04_Marketing and Outreach/13_Universities/deep-research-report Monster.md