WP-04 Standards as Data for Engineering Review
| Field |
Value |
| Priority |
High |
| Status |
Framing |
| Problem Space |
PLM and digital thread automation |
| Linked Capability |
standards formalization, explainability, lifecycle context |
| Best Collaboration Shape |
thesis + prototype + later grant framing |
| Owner |
unassigned |
What This Work Package Is
Turn engineering standards and review logic into structured, queryable, and auditable data that can support engineering copilots and review workflows.
Why It Matters To RapidDraft
- strengthens review and compliance logic
- creates traceable output rather than opaque suggestions
- is publishable and grantable if scoped well
Candidate Lanes
| Lane |
People or Group |
Why They Matter |
Best First Ask |
Priority |
| TU Darmstadt digital-engineering lane |
Benjamin Schleich |
strong PLM, digital twin, and engineering automation overlap |
thesis or prototype discussion on standards-aware engineering workflows |
High |
| FAU KBE and design-methods lane |
Sandro Wartzack |
useful for formalization and explainable review logic |
advisory framing call on standards + design methods |
High |
| RWTH / Fraunhofer IPT transfer lane |
Robert H. Schmitt |
strong AI-in-manufacturing and industrial quality context |
later-stage applied package once scope is sharper |
Medium |
Recommended Next Actions
- Narrow the first standards family before outreach.
- Decide whether the first artifact is schema, retrieval, or rule execution.
- Keep this tied to one product workflow rather than abstract compliance formalization.
Open Questions
- Which standards family gives the best first wedge?
- Is this better anchored in drawing review or DFM review?
Sources
TextCAD/04_Marketing and Outreach/13_Universities/deep-research-report Balanced.md