BIM UK Compliant file naming confusion

[ACS-Chris]

Is there anybody in a UK consultancy at BIM level compliancy that can explain how they name their dwg files?

My previous company (which was not compliant) would do the following as an example 12345 - 100 Rev A - Site Location Plan, (Job Number - Drawing Number Revision A - Drawing Name). If there were multiple drawings in one dwg, the file would be named "12345 - 100A, 101A, 102B - Site Plans" and so forth.

I understand the AEC BIM file naming system of eg. ABC-XYZ-CI-ZZ-00-M3-0001, but how does this translate to a dwg file that has multiple drawings in the model space? I'm guessing ABC-XYZ-CI-ZZ-00-M3-0001-0002-0003 is not the correct way to do it, nor do i particularly want to to that. Is it bad practice to have a single dwg with multiple drawings/sheets, should we instead be creating a new dwg for every drawing and using an x-ref system instead?

Ideally we would like to use this new file naming system for both Autocad and Revit.

[RobDraw]

I know nothing about that standard but, from what you are saying, I would not use it for working files for a couple of reasons. I would rather create submittal files to meet the requirements and use an internal file naming system that fits our workflow.

BTW, typical Revit files can have multiple revisions and many sheets in them that might include entire sets for multiple trades. That file naming convention can't work with Revit.

[ACS-Chris]

Are you saying that you would create files for internal use named in one format, and files for issue under a different format? That seems like it could add another layer of potential errors down the line with one file having two different names.

Apologies but i dont understand your second point, to my knowledge the ABC-XYZ-CI-ZZ-00-M3-0001 IS the BIM compliant way of naming Revit files.

[RobDraw]

---

@ACS-Chris wrote:
Are you saying that you would create files for internal use named in one format, and files for issue under a different format?

---

Yes. Every office that I've worked has a file naming standard. Every project uses it. Outgoing or submittal files get a different naming convention. Sometimes it is client driven.

---

@ACS-Chris wrote:
That seems like it could add another layer of potential errors down the line with one file having two different names.

---

One file cannot have two different names. The outgoing/submittal files get renamed to avoid any confusion.

---

@ACS-Chris wrote:
Apologies but i dont understand your second point, to my knowledge the ABC-XYZ-CI-ZZ-00-M3-0001 IS the BIM compliant way of naming Revit files.

---

Maybe you don't understand Revit. That file naming format cannot work for Revit. I think I explained it pretty well already. One Revit file can contain an entire project through the life of the project from conception and presentation to construction documents, all trades, all drawings, all revisions, etc...

[ACS-Chris]

With all due respect, if you had explained it pretty well then i would not have asked for further clarification. I do not claim to fully understand Revit, which is why i am here asking for guidance, though i am not sure why you have chosen to take such a stand-offish tone with your last reply. Apparently i have insulted you with my lack of understanding. As i said, the naming structure is what i have gleaned from the ISO and AEC UK standards and i am happy to see an example of how it SHOULD be done, though i would prefer it to be done in a less imperious way, or not at all. I'm sure you didnt understand Revit when you first loaded it up.

[pendean]

@ACS-Chris Autocad and Revit are like comparing Apples with bowling balls: unless you all use REVITLT (single files, one user at a time in it, the need to have dozens and dozens of files) which is more like AutoCAD, REVIT the full product with REVIT SERVER installed is designed to be a one-single-file tool where everyone on the project team taps that one single file for its entire life from concept to building owner management.

Reach out to your reseller and inquire about introduction classes for best workflows for using both programs if they do not have a specialist you can hire for the day to come to your office to help you folks with project workflows with both programs.

HTH

[ACS-Chris]

Thanks for your input, my previous company only made use of Revit in a single file, one user type way as you mentioned so i have no real experience in its collaberation tools. I have reached out to our reseller for advice but i often like to get real world examples.

[RobDraw]

---

@ACS-Chris wrote:
With all due respect, if you had explained it pretty well then i would not have asked for further clarification. 

---

That is why I explained it more detail.

---

@ACS-Chris wrote:
I do not claim to fully understand Revit, which is why i am here asking for guidance, 

---

I kind of figured that, which is why I explained it again in more detail. BTW, this is the AutoCAD forum.

---

@ACS-Chris wrote:
you have chosen to take such a stand-offish tone with your last reply. Apparently i have insulted you with my lack of understanding. 

---

There was no tone in my response. Anything that you put on my message in that aspect is all on you. Again, I did try to explain things so that you might understand. Apparently, you can't.

---

@ACS-Chris wrote:
As i said, the naming structure is what i have gleaned from the ISO and AEC UK standards and i am happy to see an example of how it SHOULD be done

---

Maybe so, but you have no idea of how to apply it because it doesn't work with today's workflows. It starts failing as soon as you get into multiple sheet files. You alluded to this but haven't tried to put it into practice. It cannot be sustained in a working environment. Until you've actually worked in a team environment with solid standards, you wouldn't understand how having a single standard for internal working files is invaluable. Conforming to client standards is for submittal files which are separate files from actual working project files. Once you get your head around that, you should be able to understand.

---

@ACS-Chris wrote:
i would prefer it to be done in a less imperious way, or not at all. I'm sure you didnt understand Revit when you first loaded it up.

---

Your asking for help from people more experienced than you. If you put your big boy pants on, you might actually understand what I'm saying instead of being blinded by something perceived.

[MikeFW]

Hi Chris, 

I'm a project lead from the UK and this how we name our files; 

For example AutoCAD 'central files' - ABC-MCS-XX-XX-M2-X-00001.

Where M2 represents a CAD central file. 

And the drawings saved on sheets within that file would be named something like - ABC-MCS-XX-XX-DR-X-12500.

DR represents a drawing file. 

Revit 'central files' are named - ABC-MCS-XX-XX-M3-X-00001.

M3 represents a central model. 

Like AutoCAD, the drawings follow this naming system - ABC-MCS-XX-XX-DR-X-13500.

Everything is saved in one file, and because we are following the latest BS EN 19650 naming requirements we will be working to the same standard that the BEP will set out from any contractor. 

The best way to manage this in AutoCAD is utilising the sheets, that way you only need one dwg file. I have attached a screenshot below. 

I hope this answers your question. The other user answering seemed to be very rude and clueless of UK standards. 

[RobDraw]

---

@MikeFW wrote:

The other user answering seemed to be very rude and clueless of UK standards. 

---

Hey, didn't I start out by saying just that?

I was rude only after that unreasonable response from the OP.

Good day.

[ACS-Chris]

Mike,

Thanks for your example, thats more or less what i was hoping to see and akin to what i had in mind. A single dwg/rvt containing all our project drawings would not work very well so i was considering using a drawing register, perhaps with a headed central file, then sub headings for each drawing tab contained with it.

May i ask how you keep track of revisions? For example if one of your Autocad central model files had 10 different drawings at various revisions.