Skip to content

Problem to Method to Lab Map

This starter map shows the intended summary logic for the university wiki.

flowchart LR
  A["Drawing Intelligence"] --> A1["Document vision"]
  A --> A2["Tolerance semantics"]
  A1 --> L1["Candidate labs"]
  A2 --> L1

  B["DFM and Manufacturing Reasoning"] --> B1["Feature recognition"]
  B --> B2["Manufacturing logic"]
  B1 --> L2["Candidate labs"]
  B2 --> L2

  C["CAE and Simulation Automation"] --> C1["Geometry abstraction"]
  C --> C2["Workflow automation"]
  C1 --> L3["Candidate labs"]
  C2 --> L3

How To Read This Map

  • Start at a RapidDraft problem space.
  • Move right into the technical method layers that matter most.
  • Only then map candidate labs, people, and institutions.

This prevents the landscape from collapsing into a university directory.

Starter Mapping Table

Problem Space Method Families To Map First Entity Target
Drawing intelligence document vision, semantics extraction, standards interpretation labs and people
DFM and manufacturing reasoning feature recognition, process-aware logic, engineering knowledge capture labs and people
CAE and simulation automation geometry abstraction, preprocessing, workflow orchestration labs and people

Open Questions

  • Should we later split the right-most node into separate lab and institution views?
  • Do we want a separate engagement overlay layer on this exact map?

Sources

  • Structure review and synthesis from the May 15, 2026 working session