COBie and Uniclass Explained For UK BIM Handover In BricsCAD

The transition from the dynamic, fast-paced environment of a construction site to the long-term, steady rhythm of facility management has historically been a point of failure for building data. Far too often, critical information is lost, buried in unsearchable PDFs, or left entirely undocumented. In the modern construction industry, this is no longer acceptable. The demand for accurate, machine-readable, and highly structured data is paramount, particularly within the United Kingdom.

If you are a BIM coordinator, an architect, or a project manager navigating this complex landscape, having COBie and Uniclass explained for UK BIM handover in BricsCAD is crucial. By mastering these two foundational pillars and integrating them into an efficient software environment, you can drastically reduce data loss, satisfy stringent client requirements, and create an asset that is as valuable digitally as it is physically.

This comprehensive guide will demystify the intricacies of UK BIM standards, explore the specific roles of Uniclass and COBie, and provide practical, actionable workflows for successfully managing and exporting this data using BricsCAD.

Understanding the Context: The UK BIM Framework

Before diving into the technical details of software workflows, it is essential to establish the regulatory and strategic environment governing construction data in the UK. The UK BIM Framework represents the overarching approach to implementing building information modelling across the built environment. It is the gold standard, driving the industry towards a digital-first methodology and supporting consistent BIM documentation.

Central to this framework is the ISO 19650 series of standards, which govern the organisation and digitisation of information about buildings and civil engineering works. A critical concept within this standard is the shift from merely delivering 3D models to delivering structured, validated data.

To achieve this, projects must strictly adhere to the UK BIM Framework asset information requirements (AIR). The AIR dictates exactly what data the facility management team will need to operate the building upon completion. This is where both Uniclass and COBie step into the spotlight. They provide the standardised language and the delivery vehicle, respectively, to ensure that the Asset Information Model (AIM) meets the client’s exact operational needs. Establishing an ISO 19650 compliant BIM workflow in BricsCAD ensures that the data you generate during the design and construction phases seamlessly translates into the final handover requirements.

Demystifying Uniclass: The Universal Language of BIM

If you have ever found yourself asking, “what is Uniclass UK?”, you are not alone. As BIM has evolved, the necessity for a unified naming and classification convention became undeniable. Without a standard taxonomy, a structural engineer might label a component a “load-bearing column”, an architect might call it a “pillar”, and a facility manager might refer to it simply as an “upright”. This lack of standardisation creates chaos during digital handovers.

To resolve this, the industry adopted Uniclass 2015. But what is Uniclass UK in practice? It is a unified classification system designed specifically for the construction industry, covering all sectors, including buildings, landscape, and infrastructure. Developed by the NBS (National Building Specification), it provides a consistent, hierarchical framework for naming and categorising everything from entire university campuses down to individual door hinges. The Structure of Uniclass

Uniclass classification BIM relies on a series of interconnected tables. Each table represents a different scale or perspective of the built environment. The primary tables include:

  • Complexes (Co): The largest scale, representing an entire site, such as a university campus or an airport.
  • Entities (En): Individual buildings or structures within a complex, like a specific library building on that campus.
  • Activities (Ac): The functions that take place within a space, such as “teaching” or “sleeping”.
  • Spaces/Locations (Sl): The rooms or zones where activities occur, such as a classroom or an office.
  • Elements (EF): The major components of a building, such as the roof, external walls, or floor systems.
  • Systems (Ss): Collections of products that work together to perform a function, such as a chilled water system or a pitched roof system.
  • Products (Pr): The individual, purchasable items that make up a system, such as a specific water pump, a brick, or a window blind.

When we discuss Uniclass bim, we are talking about assigning these specific alphanumeric codes (e.g., Pr_60_70_48 for a circulating pump) to the 3D geometry within our authoring software. This process ensures that when the model is shared, every project stakeholder understands exactly what a specific object represents, regardless of the software they are using. Why Uniclass Matters for UK Projects

For anyone working on public sector projects, understanding this system is non-negotiable. Using standard BIM classification for UK government projects is a mandatory requirement. It ensures that the government, as a major client and asset owner, receives data in a predictable, searchable format. The alignment of ISO 19650 Uniclass protocols means that your information management strategy must incorporate these codes from the very beginning of the Project Information Model (PIM) development.

Demystifying COBie: The Vehicle for Handover Data

If Uniclass provides the vocabulary, COBie provides the delivery mechanism. To answer the common question of what is COBie UK, we must look at its acronym: Construction Operations Building information exchange.

At its core, COBie is an international standard for the exchange of facility management data. It was designed to replace the massive, unmanageable piles of paper boxes containing Operation and Maintenance (O&M) manuals that were traditionally handed over at the end of a construction project.

The cobie format is essentially a highly structured relational database. While it can be viewed in several formats, it is most commonly presented as a multi-tabbed Microsoft Excel spreadsheet. This spreadsheet format is intentional; it makes the data accessible to anyone, requiring no expensive BIM software to read or edit. COBie vs. IFC: Understanding the Difference

A frequent point of confusion among professionals is the COBie spreadsheet vs IFC data exchange debate. It is vital to understand that these are not competing standards; they are deeply intertwined.

IFC (Industry Foundation Classes) is the open, vendor-neutral schema used to store and exchange both 3D geometry and metadata across different BIM platforms. It is the overarching container. COBie, on the other hand, is a specific subset of the IFC schema. It strips away all the heavy 3D geometric data and focuses purely on the alphanumeric facility management data—the lists of assets, their locations, their manufacturers, and their maintenance schedules.

In a robust digital workflow, you author your model in BricsCAD, export it as an IFC file, and then a software tool parses that IFC file to generate the COBie spreadsheet. The Structure of COBie Asset Data

To successfully manage UK BIM handover data, you must understand how COBie categorises information. A standard COBie spreadsheet contains several interconnected worksheets, the most critical being:

  • Facility: Details about the project and the overall building.
  • Floor: Information regarding the vertical levels of the facility.
  • Space: The individual rooms or areas within those floors.
  • Component: The specific, physical, maintainable assets within those spaces (e.g., a specific boiler or a specific air handling unit).
  • Type: The overarching category of a component (e.g., the manufacturer, model number, and warranty information that applies to all boilers of that specific make in the building).
  • System: A logical grouping of components that work together (e.g., the HVAC system).

Standardising facility management data with COBie ensures that when the building operator opens their Computer-Aided Facility Management (CAFM) system, they can instantly populate it with accurate, structured information. Furthermore, linking O&M manuals to COBie spreadsheets (often done via the “Document” tab in COBie) ensures that a maintenance worker can click a pump in their system and instantly open the manufacturer’s PDF manual.

The BricsCAD Advantage: Integrating COBie and Uniclass Workflows

Having established the theoretical framework, the next step is applying this within a digital authoring tool. BricsCAD BIM has emerged as a powerful, flexible, and highly efficient platform for managing complex data requirements. Because BricsCAD uses DWG as its native working file format and supports IFC import and export for open BIM exchange, it can be used as part of a structured data exchange workflow.

A successful COBie Uniclass BricsCAD workflow relies on ensuring that the 3D geometry you create is imbued with the correct metadata from day one. Here is a detailed breakdown of how to execute this process.

  1. Leveraging Smart Classification Tools

The foundation of accurate BIM documentation begins with correct object classification. If a wall is modelled but not classified as a wall in the software, it will not export correctly to IFC, and consequently, will not appear correctly in COBie.

BricsCAD offers a distinct advantage here. Instead of forcing you to manually categorise every single line and solid, you can use BricsCAD BIM smart classification tools. The software includes an AI-driven tool called BIMIFY. When activated, BIMIFY scans the entire 3D model, analyses the geometry and spatial relationships, and automatically classifies objects (e.g., identifying slabs, columns, beams, and windows) while generating spatial locations (buildings and storeys).

This automated process can reduce manual labour and help establish IFC classification and spatial structure, but the results still need to be reviewed before IFC export and COBie extraction. 2. Mapping BricsCAD BIM Objects to Uniclass Tables

Once the fundamental IFC classes are established, the next critical step is assigning the specific UK classifications. Mapping BricsCAD BIM objects to Uniclass tables is straightforward but requires meticulous attention to detail.

While BricsCAD supports custom property sets, the most efficient way to handle UK standards is by mapping Uniclass 2015 codes in BricsCAD via the properties panel. You can create specific custom property sets that align with the required COBie fields.

For instance, you will need properties for Uniclass Pr (Product) and Uniclass Ss (System). When you select an air handling unit in your model, you navigate to the BricsCAD BIM properties panel for data management. Here, you input the exact Uniclass code (e.g., Pr_60_65_03). Because BricsCAD allows for the bulk selection of objects based on criteria, you can easily select all identical air handling units across the project and apply the Uniclass classification simultaneously. 3. Implementing the NBS BIM Toolkit

To streamline the assignment of these codes, many UK practitioners look towards external databases. The NBS BIM Toolkit should not be treated as a current live platform. NBS states that the BIM Toolkit was retired in July 2022. For current workflows, use the NBS Uniclass website for the latest classification tables and the NBS Digital Plan of Work resources for guidance and templates.

By checking the current NBS Uniclass tables and recording the required Uniclass version for the project, BIM coordinators can reduce the risk of applying outdated or incorrect codes in BricsCAD. 4. Managing COBie Asset Data via the Properties Panel

For COBie to generate correctly, specific COBie asset data fields must be populated within the model. The BricsCAD BIM properties panel for data management is where this heavy lifting occurs.

Where COBie is required by the project information requirements, you must populate the required COBie fields for the relevant maintainable assets. These typically include:

  • CreatedBy: The email address of the person/organisation responsible for the data.
  • CreatedOn: The date the data was generated.
  • Category: This is where your Uniclass code lives.
  • Space: The room where the asset resides (BricsCAD handles this through spatial containment, automatically linking components to the BIM spaces they sit within).
  • AssetIdentifier: A unique tag for the specific item (e.g., PUMP-001).

You must also populate the “Type” data, which applies to all instances of a product. This includes the Manufacturer, Model Number, Warranty Guarantor, and expected Lifespan. By structuring your BricsCAD project so that “Type” properties are managed globally and pushed to individual instances, you maintain a lean, highly organised model.

Structuring Your Models for the Perfect Handover

Creating a visual 3D model is vastly different from structuring Asset Information Models for handover. An AIM is fundamentally a database disguised as a 3D building. The Importance of Spatial Logic

For COBie to function, the spatial hierarchy must be flawless. BricsCAD allows you to define the Site, Building, and Storeys clearly. Every maintainable asset (Component) must physically sit within a defined Room or Volume (Space). If a pump is modelled outside of a defined space boundary, it will generate an error during the COBie extraction process, as the facility manager will have an asset listed without a location. Ensure your spaces in BricsCAD are fully enclosed and properly classified. Linking Documentation

A critical aspect of structuring your model is managing external files. Linking O&M manuals to COBie spreadsheets begins in the authoring software. Within BricsCAD, document references can be held as properties where required, but whether they populate the COBie “Document” tab depends on the IFC property structure, export settings and the downstream COBie extraction or CDE workflow. This ensures that the final deliverable seamlessly ties the 3D geometry, the Uniclass metadata, and the external PDF warranties together in one cohesive package.

How to Prepare BricsCAD BIM Data for COBie Extraction

Preparing COBie data from BricsCAD BIM requires an understanding of the IFC export process, because BricsCAD can export the structured BIM data that downstream COBie tools or CDE platforms use to generate the COBie spreadsheet.

  1. Preparation and Purging: Before exporting, ensure your model is clean. Purge unused elements and run an audit.
  2. Property Mapping: Navigate to BricsCAD’s IFC export settings. Ensure that your custom property sets (where your COBie and Uniclass data reside) are mapped to standard IFC property sets (like Pset_ManufacturerTypeInformation).
  3. Exporting to IFC: Export the project using the IFC schema required by the project’s Exchange Information Requirements. BricsCAD BIM export options include IFC2x3, IFC4 Reference View, IFC4 Design Transfer View and IFC4X3. BricsCAD BIM is officially certified for IFC4 Reference View Architecture and IFC2x3 Coordination View, so the exported IFC should still be validated before COBie extraction or handover.
  4. Generating the Spreadsheet: Once you have a data-rich IFC file, you use a COBie extraction tool or an external Common Data Environment (CDE) platform. You upload the BricsCAD-generated IFC file, and the software parses the IFC data, filtering it through the COBie schema, and outputs the highly structured Excel spreadsheet ready for the client and your BIM documentation.

Quality Control: Ensuring Error-Free Data Drops

The UK BIM Framework requires information to be delivered through agreed information exchanges at defined project milestones. Handing over flawed data is as detrimental as handing over a building with a leaking roof. Therefore, robust quality assurance protocols are vital. Common Errors in COBie Data Drops

Understanding the pitfalls is the best way to avoid them. The most common errors in COBie data drops include:

  • Unclassified Assets: Components missing their Uniclass assignments, rendering them unsearchable.
  • Orphaned Components: Assets that are not spatially linked to a room, floor, or building.
  • Inconsistent Naming: A lack of uniformity in naming conventions (e.g., using both “AHU” and “AirHandlingUnit” in the same project).
  • Missing Type Data: Instances populated with data, but the overarching Type information (like the manufacturer) is left blank.
  • Broken Links: Document paths pointing to local C:\ drives instead of relative paths or cloud-hosted URLs.

Automated Data Validation for BIM Handover

Relying solely on visual checks is insufficient. To ensure an ISO 19650 compliant BIM workflow in BricsCAD, you must employ automated data validation for BIM handover.

Before exporting your final IFC, use BricsCAD’s data extraction and scheduling tools to create internal checking schedules. Generate a table within BricsCAD that lists all mechanical equipment alongside their Uniclass codes and Asset Identifiers. Any blank cells in this schedule instantly highlight missing data.

Furthermore, once the IFC is exported, it should be run through model-checking software (such as Solibri or BIMcollab ZOOM) before being submitted to the client. These tools can automatically cross-reference your BricsCAD IFC file against the project’s Asset Information Requirements, instantly flagging any object that fails to meet the COBie and Uniclass standards.

Best Practices for a Smooth Transition

To truly master the art of the digital handover, keep the following best practices at the forefront of your BricsCAD workflow:

  • Start Early: Do not wait until the construction phase to think about COBie. Begin structuring your BricsCAD BIM properties panel for data management during the early design stages.
  • Communicate with the FM Team: If possible, engage with the end-users. Understanding exactly how they intend to use the UK BIM handover data will help you tailor your Uniclass classifications and COBie inputs to provide maximum value.
  • Keep Geometry Lean: COBie is about data, not highly detailed 3D modelling. Do not model the internal gears of a pump; model a simple placeholder box, but pack it with rich, accurate metadata and Uniclass codes.
  • Standardise Your Templates: Create BricsCAD project templates pre-loaded with the necessary Uniclass custom property sets and COBie parameters. This guarantees consistency across all your firm’s projects and dramatically reduces setup time.

Conclusion: The Future of Building Data

The era of handing over fragmented, unstructured information at the end of a construction project is firmly in the past. Today, the digital asset is just as crucial as the physical building. Having COBie and Uniclass explained for UK BIM handover in BricsCAD provides a clear roadmap for navigating this demanding new landscape.

By thoroughly understanding what is Uniclass UK and applying its standard classifications, you ensure a universal language that spans the entire lifecycle of the asset. By embracing the cobie format, you guarantee that this heavily structured data is perfectly packaged for facility management systems. Finally, by leveraging BricsCAD BIM’s DWG based modelling environment and IFC export capabilities, you can manage structured BIM data for validation, exchange and downstream COBie production.

Creating a compliant Asset Information Model does not have to be an overwhelming chore tacked onto the end of a project. When approached methodically—utilising smart classification, rigorous property mapping, and automated validation—the production of flawless UK BIM handover data becomes a seamless, integrated part of your daily design and construction workflow. Embrace these tools, standardise your processes, and deliver assets that truly stand the test of time, both physically and digitally.

Q&A

Question: What are Uniclass and COBie, and why do they matter for UK BIM handover? Short answer: Uniclass is the UK’s standard classification system for naming and organising everything from whole sites to individual products, while COBie is the structured data format used to deliver facility management information at handover. Together, they turn your model into a machine-readable Asset Information Model aligned to ISO 19650 and the UK BIM Framework’s Asset Information Requirements. Uniclass supplies the common language (codes across tables like Systems and Products), and COBie provides the delivery vehicle (a standardised, FM-ready spreadsheet derived from IFC).

Question: How do COBie and IFC relate—are they alternatives or complementary? Short answer: They are complementary. IFC is the open, vendor-neutral schema that carries both geometry and metadata between platforms. COBie is a specific subset of IFC focused on FM-oriented, alphanumeric data (e.g., Components, Types, Systems, Spaces) without heavy 3D geometry. In practice, you export your BricsCAD model to IFC, then use a COBie extraction tool or CDE to parse that IFC and generate the COBie spreadsheet.

Question: How do I set up a robust Uniclass and COBie workflow in BricsCAD? Short answer:

  • Use BIMIFY to auto-classify objects and generate spatial structure (buildings, storeys), ensuring clean IFC classes from the start.
  • Map Uniclass 2015 codes via the Properties panel (e.g., Pr_ and Ss codes), using custom property sets; bulk-apply where possible.
  • Use the current NBS Uniclass website to check the required Uniclass tables and codes, and record the required Uniclass version for the project.
  • Populate COBie-critical fields in Properties: CreatedBy, CreatedOn, Category (your Uniclass code), Space (via spatial containment), AssetIdentifier, plus Type data (Manufacturer, Model, Warranty, Lifespan). This front-loads data quality so the subsequent IFC export and COBie generation are accurate.

Question: What spatial setup and documentation links are required for a valid COBie deliverable? Short answer: COBie depends on flawless spatial hierarchy and document references. Define Site, Building, and Storeys, and ensure every maintainable Component sits within a fully enclosed, correctly classified Space; orphaned assets will trigger errors. Add hyperlinks or document paths to objects in BricsCAD so that, when mapped through IFC, they populate the COBie Document sheet—linking assets directly to O&M manuals, warranties, and PDFs.

Question: How do I prepare BricsCAD BIM data for COBie extraction and avoid common errors? Short answer:

  • Prep and purge the model; audit for cleanliness.
  • Map your custom properties to standard IFC property sets (e.g., Pset_ManufacturerTypeInformation).
  • Export to IFC4 or IFC2x3 per the project EIR.
  • Generate COBie via an extraction tool or CDE that parses the IFC into the COBie spreadsheet. To avoid errors, watch for unclassified assets, orphaned components, inconsistent naming, missing Type data, and broken document links. Use BricsCAD schedules to flag missing fields, and run the exported IFC through model-checking tools (e.g., Solibri, BIMcollab ZOOM) against the AIR before submitting data drops. Additionally, start early, engage FM stakeholders, keep geometry lean, and standardise templates with required Uniclass and COBie properties.
Powered by DIT Innovations