Job overlap! this is part of any architectural project’s BIM Execution Plan - there’s a table where everyone working on a design decides what to call each floor, and what (usually two-character) code to give each one. Often, “GF” and “01”. “00” is then often used to refer to the wider site plans.

I’ll condense feedback for you:)
“We need consistency across our firm, that’s the most important thing...”
“…also; everyone should do it *my* way because tHaT iS tHE BeST...”
“…also, I’m not going to be part of a team to help document anything, but I do have a limitless supply of vague critique.”

Even nicer if it includes this attribute in the transmittal report xlsx export - this avoids some tedious work manually (or using API) to cross reference ACC’s “V6” to “P08”, which is actually written on the drawing title block

For ISO19650 in the UK it’s a nice feature, as we think of revisions primarily as being P01, P02,… (preliminary) and C01, C02,… (contractual) rather than simply incremental version numbers. It saves a long sideways scroll to see that attribute.

Werners_ai_art on instagram is an excellent resource for hilarious examples of ai having zero understanding of the real world :) www.instagram.com/reel/DCBYWzX...

*Every time* I’ve been involved in a team wanting to try to use a GenAI/LLM model in our practice, it has taken longer then “old” methods to get to any sort of useful output, and then it gets redone by a human anyway when they realise it’s all garbage.

Rayon is pretty neat and has a free tier - the trial/paid version has a massive library of blocks, helpful design guides, and dimensions are v slick. www.rayon.design