All models shall follow NLA coding for .rvt files:
Code_Phase_(Zone)(Block)_Discipline_ProjectVersion
Example:
320_DT_02A_ARC_01R.rvt
| Nomenclature | Example | Description |
| Code | 320 | Corresponds to the number of the project code |
| Phase | DT | Corresponds to the phase of the project that the files represent (ex. Licensing; Execution; etc.) |
| Zone | 02 | Corresponds to the zone of the project |
| Block | A | Corresponds to the Block ID inside the project |
| Discipline | ARC | Corresponds to the discipline |
| Version | 01R | Corresponds to the version of the project |
In the file designation, these parameters must be indicated without any separating characters between them, other than underscore (_), and the parameters Code and Phase must always be indicated. Zone and Block shall be used only if necessary.
When a new phase begins, the file must be copied and renamed according to the coding rule, with the new phase abbreviation, and stored in the proper folder.
If for some reason it is necessary to save a backup version of the file, it must be stored in the folder “04_Old” outside “03_Work”.
Leave a Reply