1.0 Files (Information Containers)

 

(Refer to ISO19650-2 and the UK Annex for further details)

 

The Common Data Environment enables ruleset and automatic naming of files based on the metadata requirements. 

 

Each Information Container field/facet should be separated by a hyphen (-). Hyphens are reserved for separating file name fields and should never be used in elsewhere in a file name. Each field represents a specific piece of information or ‘metadata’ about the file. Below is a code breaker which indicates what each field/ facet represents. In the following sub sections each facet is described along with a list of permissible values.

 

e.g. WBP-EDO-00-XX-SP-Z-0001

 

Suitability, Classification (refer to Uniclass 2015 Project Management Table) and Revision held in meta-data.

 

1.1 Project Code

 

The following codes have been previously assigned to projects, each project code must be unique. When creating any new projects the code should be add to the list.

 

 

1.2 Originator Codes

 

A unique identifier should be defined for each organization on joining the project, to identify the organization responsible for producing the information within the container, and fixed within the project information standard. It is recommended that the code for the originator field be between three and six characters in length.

 

The below table contains all the defined organization codes and should be updated when another company is included on the project, also noting the number of digits set for codes.

 

 

1.3 Functional Breakdown

 

In accordance with UK Annex of the ISO:19650-2 the following functional breakdown codes can be used:

 

 

Note: This list can be expanded with project-specific codes. 

Note: Where a project involves several elements or one element with several phases, each element or phase
can be assigned an identifier.

Note: This could also include package of works codes, such as CAWS or NRM codes.

 

1.4 Spatial Breakdown

 

Refer to the Floor codes section.

 

1.5 Form Codes

 

In accordance with UK Annex of the ISO:19650-2:2018(2021) the following codes should be used.

 

 

Note: This list can be expanded with additional character project-specific codes. Examples below:

 

 

NOTE: The following list originally appeared in BS 1192:2007+A2:2016 Section 9.2 & BS19650-2:2018. Although it does not follow the above recommendation it is still used on many projects.

 

File Types for Drawings and Models

 

File Types for Documents

 

1.6 Discipline Codes

 

In accordance with UK Annex of the ISO:19650-2 the following Role codes are to be used and are a subset of the Uniclass 2015 Roles Code table.

 

Note: The Annex may vary per country, please ensure these codes are relevant to your requirements.

 

 

 

 

 

1.7 Number

A sequential number should be assigned to each information container when it is one of a series, not distinguished by any other of the fields.

 

The numbering for standard coding should be fixed within the project information standard and it is recommended that it be between four and six integer numeric digits in length.

 

 

2.0 Locations

 

2.1 Floors

 

In accordance with UK Annex of the ISO:19650-2 the following principles should be used to assign Spatial Breakdown codes to projects.

 

• Each code must be 2 digits.
• Should a location not be applicable then a generic ZZ or XX code should be used
  • ZZ refers to files which reference many levels, such as a site section or elevation
  • XX refers to files which do not relate to a level at all, such as a data sheet for equipment
• Above ground levels must start from 00 for ground/base level and increase incrementally
• Any mezzanine level should begin with an M followed by the level, e.g. M1 is Mezzanine above Level 01
• Basement Levels must start with a B followed by the level, e.g. B1 is basement level 1

 

Note:

Levels and Building Storeys are also considered to be Floors.

Consideration should also be given to external areas e.g. Car Park, Garden, Driveway, Path, Roads etc.

 

2.2 Spaces

 

Spaces within the portfolio will be named in accordance with the following standard.

 

Floor-Number (01-001)

 

Spaces should be named in clockwise order from the entry point of the Floor.

 

 

2.3 Zones

 

The following zone types are required for all spaces:

 

 

  

 

 

 

3.0 Systems

 

Systems shall be classified in accordance with the Information Structure section above.

 

System naming relates to the sub-systems within each classification. For instance, there may be only 1 partition classification used (Ss_25_12_65_65 - Panel Partition Systems) but many partition systems.

 

Systems should be named in alignment to the Specification.

 

 

4.0 Assets

 

4.1 Equipment Types

 

Equipment/Products should be named with a code as the Manufacturer and Model can change at both the Project and Operations phases. Using a coding system allows continuity of referencing even when switching equipment

 

The following coding structure should be used for all product types:

 

Delimiter must be a hyphen "-".

Example = RAD-B

 

4.2 Individual Assets

 

Individual assets should be named using the coding structure below. Similarly to the Types, this allows for the identifier to remain the same whilst the equipment details may change.

 

The following coding structure should be used for all assets and clearly labelled on any plans/specifications:

 

Delimiter must be a hyphen "-".

Example = RAD-B