File Name Builder
ISO 19650 · Container IDs · Any CDE. Build file names field by field, check them against the standard, and copy them straight into your CDE, file server or title blocks.
ISO 19650 · Container IDs · Any CDE. Build file names field by field, check them against the standard, and copy them straight into your CDE, file server or title blocks.
Collect names for a drawing list or transmittal. Each time you add a name, the number moves up by one.
| Field | Length | What it means | Example |
|---|---|---|---|
| Project | 2–6 | Single code for the whole project, set by the appointing party | RCC |
| Originator | 3–6 | The organization producing the information | VDC |
| Volume / system | 2 | Physical volume or system the information covers | ZZ |
| Level / location | 2 | Floor level or location | 01 |
| Type | 2 | Kind of information (model, drawing, report…) | DR |
| Role | 1–2 | Discipline of the task team | A |
| Number | 4–6 | Sequential number, unique within the other fields | 0001 |
| Status | 2 | Suitability, held as metadata | S2 |
| Revision | 3–5 | Version, held as metadata | P01 |
Field lengths and codes follow ISO 19650-2 and the UK National Annex. Your project's information standard can set its own codes and takes precedence.
The File Name Builder puts together information container IDs that follow the ISO 19650-2 naming convention:
Project-Originator-Volume-Level-Type-Role-Number, for example
RCC-VDC-ZZ-XX-DR-A-0001. Set the project and originator codes once, then pick the volume, level,
information type and role for each file. The builder checks the result against the standard as you type and
flags any field that doesn't match.
Status and revision are normally held as metadata in your CDE. If your platform or file server has no metadata fields, switch on the status and revision suffix to add them to the end of the name. Use the name list to build a drawing register or transmittal: each name you add moves the number up by one.
ISO 19650-2 and its UK National Annex name each information container with fields separated by hyphens: project, originator, volume or system, level or location, information type, role and a sequential number. Suitability status and revision are held as metadata alongside the name.
Yes. The type and role lists include the standard UK National Annex codes plus an Other option for project-specific codes. Your project's information standard always takes precedence over the defaults.
Your settings and name list are saved in your own browser so they are there next time you visit. Nothing is sent to a server.
Yes. The File Name Builder is free to use. If you need naming tools built around your own standards or platform, VDC Stack.io can build a custom tool for your team.
We build naming tools, CDE templates and project setups around your own standards and platform. Send a request or a suggestion to improve this builder.
Disclaimer. The File Name Builder is a reference tool provided for guidance only. VDC Stack.io is not responsible for incorrect results, omissions, or misalignment with project, client, contractual or standards requirements. Outputs are not contractual and do not form part of any agreement or scope of work. Verify all file names and codes against your project's information requirements before use.