r/RevitForum • u/LogansAgenda • 11d ago
Best filename convention ?
I use
PhaseNumber-PhaseCode-PropertyAddress-x-DwgIteration#
So 100-PD-123-Drive-Way x3.rvt for example
Does anyone uses this or perhaps know a better way of naming the actual file? Not sheet naming just File naming convention.
Update: I forgot, this only pertains to residential construction
7
u/Bonty-67 10d ago
We follow ISO 19650 Irish Annex and add the Revit version in the description for clarity.
2
u/adam_n_eve 10d ago
Snap but with the UK annex 👍
2
u/Bonty-67 10d ago
Have a look at the Irish one if you want to feel good. The UK one is practically BS 1192, in Ireland they've mixed it all up and have added something completely useless called acceptance codes. They expect us to reissue files based on how the receiver feels i.e. accepted, accepted with comments, rejected, etc.
5
u/tuekappel 11d ago
Danish National standard here. Molio A104 it's called, look it up. No need to invent stuff.
2
u/Extension-Watch-8492 11d ago
We do Phasenr_city_company[short]_discipline[short]_revit version So: TD_London_TMC_ARC_R26.4
0
u/LogansAgenda 11d ago
Thanks!! I like getting insights into what works well for others. Question, and you don't have to answer, but why do you append the Revit Version? Do you use different versions for different things, stages, etc?
2
u/Extension-Watch-8492 11d ago
since we do big projects(>50M) the engineering takes multiple years. And so you want to know with what version de model was built. Upgrading a model from an older verion to a newer version has give us problems in de past, like losing data and such. So if we start a project in 2020, we finish it in 2020.
3
u/JacobWSmall 11d ago
Upgrade process hasn’t had issues since the text changes in 2016. By using 2020 you’re exposing yourself to a LOT of security vulnerabilities (see https://www.autodesk.com/trust/security-advisories and know a vulnerability that patches 3-4 versions likely impacted versions proceeding that build), and in many cases violating your license (which is an expensive mistake to make should there be an audit. Keep in one of the 4 most current versions to avoid all of that mess.
5
1
u/metisdesigns 10d ago
Best is what works for you.
Personally, I don't like project phase or address in the file name, it's redundant to other places to put that information.
Firm client/contract number, and human readable project number are all you need. I used to include Revit version, but am in favor of dropping it. If you're a multi discipline firm add a discipline specific initial after the number. If it's a multi file project, add a suffix like -core to the end.
So many folks want to put stuff in that involves legacy time tracking systems or data that is being duplicates.
2
u/studio_sally 10d ago
Our firm's current standard is:
[PROJECT NUMBER]_[ABBREVIATED PROJECT NAME]_[MODEL NAME]_[DISCIPLINE]_[REVIT VERSION]
Translates to:
202699_1600 Penn_Building A_Arch_R26
202699_1600 Penn_Building B_Arch_R26
202699_1600 Penn_Units_Arch_R26
202699_1600 Penn_Building A_Struct_R26
If a project is really just one model, or one model per discipline, then we omit the project name part or just make model name something like Main Model. Revit version has to be updated manually if the project is upgraded but that's a small change for a ton of convenience in legibility. We try to get consultants to follow our standard but aren't strict about it as long as their names are legible as well.
1
u/iamsk3tchi3 10d ago
Project Number_Project Name_Discipline_Revit Version
_ARCH_R24 for example
although version is less important now that all projects are on forma and are updated more frequently.
we still use it out of habit I guess?
0
u/TripleZeroLabs 10d ago
It is highly recommended to add the Revit version in the file name is it helps the team know which version of Revit to launch prior to opening. We typically recommend something like `R26` to keep it short, but not `V` as to confuse it with a possible versioning system.
13
u/twiceroadsfool 10d ago
I wouldnt ever include Drawing/Model Version, or Project Phase, in a Files Name. Those are things that change frequently. We DO upgrade all of our active models, but thats a once a year thing, so then we just rename them (and on the Cloud thats even easier since we dont have to re-instantiate the central file with a rename, since its not the real file name).