TRXL 247: It's on the Server Somewhere
15 snips
Oct 22, 2026 Guest
Theodoros Galanos
Guest
Jesper Wallgren
Guest
Chris Razzell
Guest
Sasha Crotty
Guest
Aaron Vorwerk
Guest
Randall Stevens
Theodoros Galanos, an AEC technology and AI practitioner; Jesper Wallgren, Finch co-founder; Chris Razzell, a building-information specialist; Sasha Crotty, an Autodesk data-platform leader; Aaron Vorwerk, an architect and information strategist; and Randall Stevens, an AEC integration expert, explore why firms struggle to use project history. They discuss fragmented systems, hidden decisions, Revit data, shared language, federated information, knowledge capture, governance, and why basic RAG fails on messy AEC data.
AI Snips
Chapters
Transcript
Episode notes
Use Shared Meaning Instead Of One Universal Language
- Firms need enough shared meaning for data to move across disciplines, not identical terminology everywhere.
- Andy Radin warns that forcing one monolithic standard creates resistance and workarounds that undermine compliance.
AI Lowers The Minimum Data Standard
- LLMs can recognize inconsistent names and write queries around historical typos, reducing the need to normalize everything first.
- Teams still need minimum rules for active projects where reporting and client commitments require reliable data.
Build Confidence Into Future Project Data
- Distinguish usable data from trustworthy insight by tracking mapping confidence between fields such as “fire rating” and “FR.”
- Define standards for new projects while using AI to map older projects toward them.