The last episode made the case that your project history is worth something. This one asks why you can't use it. Two reasons keep coming up: the data means different things to different systems and different people, and it's scattered across far more places than anyone planned for.
Ariel Cooke-Zamora at Bimbeats explains how a data dictionary keeps an AI from misreading your data, and I add a caveat about keeping it pruned. Randall Stevens at AVAIL describes a customer running 180 applications, and says the best information is at the edges of the network. Aaron Vorwerk and Mike Soldan at Egnyte cover where the reasons behind a project's decisions end up, and why governance has to come before AI touches your files. Ross Wagner at Pirros asks how a firm captures what its one all-knowing person knows. Sasha Crotty at Autodesk talks about getting data out of Revit files and how much confidence you can put in it. Andy Rahden at Bentley, Dimitrie Stefanescu at Speckle, Chris Razzell at dRofus, Marty Rozmanith at Skema, and Jesper Wallgren at Finch take on shared language, minimum standards, and where the data should live. Matt Wash at Bimbeats, Scott Reynolds at UpCodes, Campbell Yule, and Theodoros Galanos add the habits, the documentation, and the reasons Theodoros says RAG doesn't work.
This episode is especially relevant for CIOs, BIM managers, and design technologists who've been told to get their data AI-ready and want to know what that means on a Monday morning.
Get all the show notes, links, and enter to win a pair of Ray-Ban Meta Smart Glasses, courtesy of series partner Graitec, at trxl.co/247
-----
Sign up to become a TRXL member.
- Free members get email notifications when new episodes are released and when new posts are published on TRXL.co
- Paid supporters of TRXL+ get ad-free podcast episodes, full show notes, and exclusive Leadership Edge email newsletters from TRXL
