Labs Index
This is the promoted lab layer inside 04 - Leads. It is intentionally smaller than the person layer. A lab only gets promoted when it groups multiple relevant signals or helps route more than one work package.
- Promote a lab when at least two people, work packages, or opportunities clearly point to it.
- Do not create a lab page if the relevant signal is really just one professor profile.
- Keep institutions even thinner than labs.
| Cluster |
Why It Matters |
Current State |
| OTH Regensburg digital-twin cluster |
one of the strongest applied Hochschule clusters for AI-supported product development and simulation |
routed in source layer; promote with a live Regensburg opportunity |
| KIT IMI and LESC |
strong digital-engineering and lifecycle systems lane |
routed in source layer; no active opportunity yet |
| KIT IPEK |
strong product-engineering methods and validation-process fit |
routed in source layer; methods lane not active enough yet |
| Fraunhofer SCAI NDV |
strongest CAE analytics and simulation-comparison route beyond ITWM |
routed in source layer; later-stage simulation lane |
| DLR Virtual Product House |
strong virtual-product-development and validation framing |
routed in source layer; relevant when aerospace case sharpens |
| TUM iwb and Fraunhofer IGCV manufacturing lane |
strong credibility and manufacturing transfer path in Munich |
routed in source layer; current wiki stays on more direct work-package fits |
| University of Augsburg data-driven product-engineering lane |
very strong Bavaria simulation and optimization fit |
routed in source layer; activate when geometry-to-CAE lane expands |
Open Questions
- Should TH Ingolstadt get its own lab/container page next, or stay person-led for now?
- Do we need a separate TU Darmstadt PLCM lab/container page in the next wave?
Sources
TextCAD/04_Marketing and Outreach/13_Universities/deep-research-report.mdTextCAD/04_Marketing and Outreach/13_Universities/RapidDraft Academic & Applied Research Partner Mapping (Monster Brief, v1).md